Migration from JDK 1.4 to JDK 1.5

Hi All,
Presently our application is pointed to JDK 1.4 could you pls let us know how to migrate out application to 1.5 we are in "10.1.2.3.0" i.e 10g R2 OAS.
Regards
Yeshwant

Before replacing the JDK with a new version, the certification should be checked. This is available at the below link for the various Fusion Middleware releases:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
It should be noted on this page for Oracle products installed with a JDK, you can replace with a newer xx version (e.g. 1.4.2xx) without any problem regarding support/certification. Replacing with an entire JDK (e.g. 1.4.2 to 1.5) is something considered for certification. The only release where this is available is the 10.1.3 release, where the installed 1.5 may be updated to Java 6 and some application specific exceptions. More details in the certifications guides for your release and in the following document:
Java SE (J2SE) End of Life and Oracle Fusion Middleware Policy (Doc ID 952075.1)
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=952075.1
(requires login)
...Ken

Similar Messages

XML Transformation - Migration from JDK 1.4 to JDK 1.6

Hi all,
I am switching from JDK 1.4 to JDK 1.6 but my XSLT transformations are outputting different XML (although structurally sound). JDK 1.6 outputs the namespaces for each element rather than placing them at the top level node.
I've included the settings and the code below. I expect that there is a feature or a way to handle this but I have not been able to find it now for several days.
Any recommendations would be greatly appreciated.
Regards
Paul
JDK1.4
JAXP: loaded from fallback value: org.apache.xalan.processor.TransformerFactoryImpl
JAXP: loaded from fallback value: org.apache.crimson.jaxp.SAXParserFactoryImpl
<?xml version="1.0" encoding="UTF-8"?>
<ex1:IE518 xmlns:xdata="http://www.edifecs.com/xdata/100" xmlns:exe="http://test.com/schemas/ex1/elements/v1" xmlns:ext="http://test.com/schemas/ex1/extypes/v1" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:ex1="http://test.com/schemas/ex1/MSG/v1">
<ext:Common>
<exe:SyntaxID>UNOC</exe:SyntaxID>
<exe:MessageID>00000000000000</exe:MessageID>
<exe:IEMessageType>MsgType</exe:IEMessageType>
</ext:Common>
<ext:Header>
<exe:SpecificCircumstanceIndicator>B</exe:SpecificCircumstanceIndicator>
<exe:Transit>0</exe:Transit>
<exe:CommercialReferenceNumber>DHL11-7-43</exe:CommercialReferenceNumber>
</ext:Header>
</ex1:IE518>
JDK 1.6
JAXP: loaded from fallback value: com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
JAXP: loaded from fallback value: com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
<?xml version="1.0" encoding="UTF-8"?>
<ex1:IE518 xmlns:ex1="http://test.com/schemas/ex1/MSG/v1">
<ecc:Common xmlns:ext="http://test.com/schemas/ex1/extypes/v1">
<exe:SyntaxID xmlns:exe="http://test.com/schemas/ex1/elements/v1" >UNOC</ece:SyntaxID>
<exe:MessageID xmlns:exe="http://test.com/schemas/ex1/elements/v1" >00000000000000</ece:MessageID>
<exe:IEMessageType xmlns:exe="http://test.com/schemas/ex1/elements/v1" >MsgType</ece:IEMessageType>
</ecc:Common>
<ecc:Header xmlns:ext="http://test.com/schemas/ex1/extypes/v1">
<exe:SpecificCircumstanceIndicator xmlns:exe="http://test.com/schemas/ex1/elements/v1" >B</ece:SpecificCircumstanceIndicator>
<exe:CommercialReferenceNumber xmlns:exe="http://test.com/schemas/ex1/elements/v1" >DHL11-7-43</exe:CommercialReferenceNumber>
</ecc:Header>
</ex1:IE518>
try {
     byte[] transformed;
     StreamSource inputData = new StreamSource( new ByteArrayInputStream( xml_ecs.getBytes( ) ) );
     FileInputStream xsltData = new FileInputStream( xsl_file_path );
     StreamSource transformationData = new StreamSource( xsltData );
     StreamResult streamResult = new StreamResult(new ByteArrayOutputStream( ));
     //create transformer factory
     TransformerFactory tFactory = TransformerFactory.newInstance( );
     Transformer transformer = tFactory.newTransformer( transformationData );
     //perform transformation
     transformer.transform( inputData, streamResult );
     transformed = ((ByteArrayOutputStream) (streamResult.getOutputStream( )))
          .toByteArray( );
     System.out.println ("TRANSFORMED OUTPUT [" + new String(transformed) + "]");
catch (TransformerException texsc) {
     System.out.println( "TransformerException caught: "
               + texsc.getMessage() );
     throw texsc;
catch (Exception ex) {
     ex.printStackTrace();
     System.out.println(ex.getMessage());
}

Can you post relevant pieces of your input document and the xsl?

Do we need to compile the code migrating from JDK 1.4.2.11. to 1.4.2.15

Hi
Currently our application is running in JDK 1.4.2.11 and because of the SSL vulnerability issues we are planning to upgrade the JDK to 1.4.2.15 version.
Just wanted to know do we need to complie the code for this change.

In general, no. However, if your code depends on code that was changed as part of a bugfix, you may have to make source changes, and then recompile.
Test and see. And review the release documents for the versions involved.

CORBA problem after migration to JDK 1.5.0_05

Hi,
I faced some errors with CORBA, after performing migration from JDK 1.4.1 to JDK 1.5.0_02
on Solaris 8 2/02 (SPARC version).
I've spend few days on digging in java.sun.com bug database and google archive,
but haven't found similar case.
The problem occurs in a web application launched on Tomcat 5.5.7, if JDK 1.5.0_02 is used and trying to connect with CORBA server.
If using JDK 1.4.1 the CORBA stuff works fine.
I isolated the problem code and found out, that Tomcat
can not cause the error, because i receive the same error while invoking test class from command line.
I use IOR file for obtaining the object reference and default JDK Orb.
The stacktrace(see below) goes through new package in JDK 1.5 com.sun.corba.se.impl.* and java.lang.Class which was
rewriten in JDK 1.5 in order to use generics. Is it possible that the bug lies somewhere in this classes?
I've already spent few days on searching cause of the bug, and found no clues.
Is this a known issue? Does anyone have a workaround?
Have you seen some similiar behavior associated with migration to JDK 1.5.0 ?
I'm running out of ideas, on debugging this stuff, any help or suggestion could be helpful.
Thanks In Advance, Kuba
PS. I attach the received stack trace below:
org.omg.CORBA.BAD_OPERATION:   vmcid: 0x0 minor code: 0 completed: Maybe
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:897)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:99)
        at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:572)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:430)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:326)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129)
        at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
        at generated.from.idl.package._ServerFactoryStub.FindServer(_ServerFactoryStub.java:25)

Hi,
I replying to my own post for persons who, have a similar problem.
I've used external ORB implementation, and the stuff started working properly.
www.jacorb.org.

Identifying problems when migrating to JDK 5/6

We are interested in migrated from JDK 1.4 to 6.
I found an article on walmart.com's experience.
"Java 1.5 introduced several changes or enhancements to its XML API (SAX, DOM and XSLT in particular). These changes first became apparent when running code that relied on JSP’s imports. Previous versions of the XML API allowed the same XML attribute to be defined more than once in a single JSP. Quite a few JSP pages, dynamic and static, broke when running under Java 1.5 because of the attribute repetition. "
[http://www.theserverside.com/tt/articles/article.tss?l=MigratingtoJava5]
Please identify what the author means exactly by "XML attribute" and provide an example of this behavior/bug. I'm trying to understand this so I can identify if we have this in our codebase or not. thx.

The migration from Designer 6.0 to 6i requires careful planning. Please read the migration guide on OTN (http://www.oracle.com/technology/products/designer/index.html) for advice and to assist you with the migration.
Regards
Sue

Migration problems from Jdk 1.3 to Jdk 1.4.2_05

?Hi,
We have migrated our code from Jdk 1.3 to Jdk 1.4.2_05 and we are facing the following issue:
We have a table which displays results retrieved from DB,
When we migrated the table headers were not displayed properly due to some width parameters, so when we hardcoded the width to increase by 10, the headers are seen properly. But there is a gap between each header names.It is not set to the whole column width.
We are getting the width of the comp as follows:
Component comp = renderer.getTableCellRendererComponent(table,
col.getHeaderValue(),false,
false, 0, 0);
return comp.getPreferredSize().width + 10;
And we are setting the column width as below:
We are checking whether the cellcontent width or the header width is greater and we are passing the max width.
col.setPreferredWidth(width);
Kindly help me in this regard,
Thanks in advance,
Kala

You may get a better response posting this question in a more appropriate forum such as the Java Swing forum or the AWT forum. See forums below:
http://forum.java.sun.com/forum.jsp?forum=57
http://forum.java.sun.com/forum.jsp?forum=5

Migrating application from jdk 1.4 to 1.5

Hi,
I am planing to migrate my application from JDK 1.4 TO 1.5 . I am also using AJAX4JSF in application.Did anyone encounter any issue after migrating or during the migration to JDK 1.5 ?
Thanks in advance

You should be calling wrap() to wrap your keys, not doFinal(), or alternatively initializing your cipher to be ENCRYPT'ing, not WRAP'ing.

Upgrade from JDK 1.2.2 to JDK 1.4.2. Any code changes required?

Hi,
We are in the processes of upgrading the JDK versions on servers to JDK 1.4.2 to support other software upgrades.
The JDK versions on each of the servers are at different versions. On one of the servers, the version of JDK is currently at JDK 1.2.2_10. Can somebody please advise me if there would be any code changes required to support this upgrade (such as some methods being depreciated)?
We are also evaluating if we need to upgrade to JDK 1.4.5. In such a case, would there be any code changes required to upgrade from JDK 1.4.1_x to JDK 1.4.5. I assume there wouldn't be any changes for this minor upgrade but just want to confirm.
I would really appreciate an early reply.
Thanks in advance.
Regards,
Vamshi

"1.4.5" - you meant "1.5" ? :)
About deprecations -- you will be warned by the compiler. E.g. "assert", "enum" are keywords and cannot be used as method names.
The rest depends on your application. The more complex it is, the more differences can be encountered. You certainly need to run a test cycle for it with the new platform.
From my experience, I can list some issues that I have read about or have experienced myself:
1) serialization: the algorithm used to calculate the serialVersionUID had some changes between Java versions, due to compiler-added extra methods.
If you don't have serialized instances, or your serialVersionUID is specified explicitly, you are safe.
2) class loading order can be different in different platforms
Once ago I have seen a paper from BEA Systems highlighting some open topics that can arise when migrating between different vendor's JVMs. Probably, it is the one:
http://edocs.bea.com/jrockit/geninfo/devapps/codeprac.html
In my friend's case, there was some class-initialization logic, that behaved differently when class loading order changed.
3) Swing applications can sometimes behave slightly different.
E.g., I observed some changes in focus handling, although minor ones. Fixed with several lines of code.
4) Some libraries can depend on particular J2SE version. E.g. J2EE ones.
E.g. I was not able to run J2EE 1.4 thick client application with JRE 1.5. The j2ee library used by the app either had some dependencies on sun.* classes, or on some protocols (not sure, I don't remember it well).
5) Regression bugs are sometimes encountered. I.e. something that worked, does not work now.
Summary: You need testing.

Planning to upgrade my application from JDK 5 to JDK 6

Hi All,
We are planning to upgrade JDK from JDK 5 to JDK 6. I would like to the stable release or update in JDK 6.
Our development environment is Windows and Production environment is Red Hat Linux 5.4 (64bit).
Please suggest the stable release in JDK 6 to upgrade my application.
Regards,
Kiran

Apple's USB drive won't work with your computer at all.

Configuring JDev to use javac from JDK

Is there anyway to make JDevleoper use Javac from JDK. We are seeing some discrepancies in the code generated by ojc.
Thanks.
Suhas.

Starting with JDeveloper 9.0.3 Preview Release, you can use ANT to build your project
and with ANT you can use Javac.

Migrating from 10g to 11g checklist

Hi,
we are migrating from oracle 10.2.0.4.0 to 11g. we have Apex 3.1.2.00.02 installed in 10g.Will migrating to 11g will have any issues in our applications?.i have read that what comes with 11g is apex 3.0.
it would be so helpful if you could give a checklist/steps on migarting to 11g.
Many Thanks,
Cklp.

Thank you Shay. I tried to migrate our application to 11g without choosing Trinidad, when I want to deploy it i get follwoing exception
eblogic.application.ModuleException: Failed to load webapp: 'enlogixcis'
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.view.faces.webapp.ResourceServlet
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     Truncated. see log file for complete stacktrace
there is adf-faces-impl.jar in path when I open its I see following
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: Apache Maven
Built-By: asghosh
Package: oracle.adfinternal.view.faces
Build-Jdk: 1.4.2_16
Extension-Name: adf-faces-impl
Specification-Title: ADF Faces Implementation
Specification-Vendor: Oracle Corporation
Implementation-Title: oracle.adfinternal.view.faces
Implementation-Vendor: Oracle Corporation
Implementation-Version: 10_1_3_4_0
it seems it is for app server 10.1.3.4

Problem migrating from JSF Mojarra 1.2 to 2.0

As my subject suggests, I am having a problem migrating from JSF 1.2 to JSF 2.0.
As a first step, all that I had done was to replace both 'jsf-api.jar' and 'jsf-impl.jar' with the newer version 2.0 and restart my server.
As expected, server failed to publish with the following error message on the console. Any hint on solving this issue is highly appreciated.
The error message goes as below:
<Jun 30, 2009 10:31:54 AM PDT> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application D:\MalcolmX\web. Please make sure that the annotations are valid. The error is com.sun.faces.taglib.jsf_core.BeanValidatorTag>
<Jun 30, 2009 10:31:54 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application '_auto_generated_ear_' due to error weblogic.application.ModuleException: Failed to load webapp: '/'.
weblogic.application.ModuleException: Failed to load webapp: '/'
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: com.sun.faces.taglib.jsf_core.BeanValidatorTag
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     Truncated. see log file for complete stacktrace
Thanks.

SirG wrote:
As expected, server failedWow :P
The error message goes as below:
java.lang.ClassNotFoundException: com.sun.faces.taglib.jsf_core.BeanValidatorTagIs it in classpath? Exception says it is not.
Don't you have some JSF 1.2 libraries around somewhere else in classpath? Appserver/lib? JDK/lib? Etc. You might have a mix of JSF 1.2 and JSF 2.0 in the classpath and the exception is just been caused by this collision.

Migration from SAP BC To SAP P.I

HI Experts ,
I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
1) What kind of challenges can be faced during migration from BC to XI?
2) What is the best practise for doing the same?
3) Can you share some scenario from where i can have some idea how to do migration?
4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
Would appreciate your valuable inputs on the same!
I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
Regards
Saras Jain

Hi Saras,
I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
Scenario
SAP Business Connector enables data exchange between an SAP system and
external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
replaces SAP Business Connector (SAP BC).
We distinguish between standard scenarios (that do not contain customer-specific
development) and individual scenarios (that do contain services or mappings created
by the customer). The following sections describe how to migrate both types of
scenarios to SAP XI.
Scenario 1 (IDoc HTTP, HTTP IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner by using HTTP.
An external business partner sends an XML document by using HTTP to SAP BC or
to SAP XI. The document is converted to an IDoc and sent to a connected SAP
system in the internal system landscape.
Scenario 2 (IDoc Mail, Mail IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner as an e-mail.
An external business partner sends an e-mail to SAP BC or to SAP XI. The
document is converted to an IDoc and sent to a connected SAP system in the
internal system landscape.
Flow Services
Flow services are services that are written in the proprietary graphical-based flow
language of SAP BC.
Java Services
Java services are services that are written in the Java language.
There are several platforms that support Java, including SAP XI. However, the data
model used in the Java services in SAP BC is proprietary.
Stylesheet Transformations
Stylesheet transformations are often used for mapping purposes. They take an XML
document as input, convert it according to rules defined in the stylesheet, which is
also an XML document, and produce an XML document as output.
The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
SAP NetWeaver is the open integration and application platform from SAP. With
NetWeaver 04, there is a significant overlap between the functions of SAP
NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
mapping, routing, and adapters to connect to a large number of third-party back-end
systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
based on SAP NetWeaver. Customers looking for a strategic integration solution for
the complete application landscape should therefore now favor SAP NetWeaver.
The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
BC has not been developed further since this release. SAP BC is not released for
any further platforms (such as Windows 2003) and does not support any further JDK
versions, including the current version (Version 1.4).
For information about the supported SAP BC versions, JDKs, and operating systems,
see SAP Note 309834. For information about the support and maintenance strategy
for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
aware of the following:
A solution based on SAP BC cannot be a strategic, long-term solution.
A solution based on SAP BC is based on technology that was implemented in
2003 and that is no longer further developed.
SAP BC is supported on limited platforms and for limited JDKs only. Vendor
support for some of these platforms and JDK versions will soon be
discontinued.
SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
on webMethods proprietary Integration Server, whereas SAP NetWeaver is based
on open standards, such as BPEL4WS (business process execution language for
web services). Therefore, only parts of an SAP BC implementation, such as XSLT
mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
programming based on SAP BC, such as SAP BC flow language, is unlikely to be
reusable in the SAP NetWeaver context.
Purpose of this Migration Guide
The purpose of this migration guide is to provide scenario-based descriptions of the
migration from a companys system landscape that uses SAP BC to exchange
documents with business partners, to a system landscape that uses SAP XI instead.
This migration guide outlines, for certain scenarios, the individual steps a company
has to take to replace an existing SAP BC implementation with SAP XI.
The basic steps in the back-end systems are:
Defining the logical systems
Maintaining the ALE distribution model
Maintaining partner profiles and EDI ports
Maintaining RFC destinations
The basic steps in the SAP XI system are:
Maintaining the System Landscape Directory
Configuring the IDoc adapter
Maintaining the receiver determinations, interface determinations, and
interface agreements
Maintaining the communication channels
The type of scenario to migrate typically has an impact on the communication channels only.
Scenario 1 IDoc/HTTP
IDoc HTTP Using SAP BC
Within the system landscape of a company, an SAP system sends an IDoc
asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
document. The fields of the IDoc are not modified, that is, the conversion does not
involve any mapping of source fields to target fields. After conversion, SAP BC uses
HTTP to send the XML document synchronously to an external URL of a business
partner.
System Landscape
An SAP system and SAP BC are installed within the same system landscape
of a company.
The following information is defined in the SAP system to allow data
exchange between the SAP system and SAP BC:
o An RFC destination and a logical system for SAP BC
o The distribution model is maintained, if necessary
The following information is defined in SAP BC:
o An SAP server with an alias is defined. For this SAP server, the
information that the SAP BC requires to connect to the SAP system is
specified.
o A listener is configured to listen to requests from the SAP system.
o A routing rule with the transport type XML is configured for the
specific sender, receiver, and message type. The routing rule
determines how a message is to be routed and where it is to be routed
to. The scenario described does not use an ACL, (Access Control List
to restrict execution permissions for this routing rule) or pre-processing
or post-processing SAP BC services.
4.2 IDoc HTTP Using SAP XI
Check the prerequisites described above under Prerequisites for Standard
Scenarios.
The IDoc adapter is used to receive an IDoc from an SAP back-end system and
convert it to XML.
The adapter used to post this XML to an external destination is the plain HTTP
adapter.
To set up the communication channel, perform the following steps:
1. Locate the routing rule in SAP
Business Connector.
In the Administration View, choose
Adapters Routing to navigate to
Routing Rules.
2. Select the details of the relevant routing rule.
To display the details, choose the green triangle (Edit).
Transport is typically set to XML and a URL is specified. You can use this
URL in your SAP XI settings.In some cases, Transport is set to
B2B Service and the parameters Server Alias, Folder and Service
exist. This is the same as when Transport is set to XML and has the
URL http://<serverhost>:<port>/invoke/<folder>/<service>.
You can find <serverhost> and<port> in the definition of the
remote server under Settings >Remote Server in the Administration
View.
3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
Use the following settings:
Adapter Type: HTTP Receiver
Transport Protocol: HTTP 1.0
Message Protocol: XI Payload in HTTP Body
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
regards
Aashish Sinha
P : Reward points if helpful

Application Migration from HP-UNIX to SUN Solaris

Hi Gurus,
Need help on the application migration from HP-UNIX to Sun Solaris . Copied the filesystems APPL_TOP, OA_HTML, OA_JAVA, COMMON_TOP/util and COMMON_TOP/_pages from SOURCE( HP) to TARGET SUN-solaris as per 238276.1
Now trying to clone Autoconfig XML context file on the TARGET System
perl adclonectx.pl migrate java=\opt\java1.4 \
contextfile=\ul01\app\applmgr\lasrx\admin\LASRX_fiapd4.xml
Error: source context file ul01appapplmgrlasrxadminLASRX_fiapd4.xml does not exist.
Questions:
======
1. we still need to install jdk in the TARGET or copy the file system from source(HP) to target( Solaris) bring the JDK and how to check jdk on Solaris?
2. In clone autoconfig XML, contextfile=? Is the location of SOURCE or TARGER?
3. I think running above with root permission.
Please help somebody on this issue.
Thank You.

Hi Hussein,
I need your help on the Application migration from HP-UNIX to SUN Solaris. As per the note 238276.1 we dont copy $806_ORACLE_HOME for cross platform migration, Copied all the filesystem from SOURCE to TARGET but rename it because it suppose to create while installing Middle tier.
Issue:1
=====
When i start to set environment like below, i get the error and
. /ul01/app/applmgr/lasrx/APPSORA.env
ksh: /ul02/app/oracle/lasrx/8.0.6_new/LASRX_fiapd4.env: not found
I am trying to install Middle Tier Technology Stack on SUN server ( Migrating from HP-UNIX to SUN solaris)
Issue 2: ( Display error) while install Tech Stack
=====
./rapidwiz -techstack
Rapid Install Wizard is validating your file system......
>> Wizard requires the DISPLAY variable to be set.
>> Please set your DISPLAY variable and restart Rapid Install Wizard.
even i can not see
echo $DISPLAY because not set the environment.
Need your help and suggetions on this.
Thank You.

OIM 9102 BP12 Migration from WebSphere 6.1 to Weblogic 10.3

Hello,
We're planning to move(9102BP12) from WebSphere6.1 to Weblogic10.3.
I found Oracle metalink which says -
================================================
JDK Migration restriction:
You can only migrate to JDKs that falls with in the same groupings.
Group 1: Sun JDK, Oracle JRockit, HP JDK
Group 2: IBM JDK.
Example: If you are running OC4J using Sun JDK then you can migrate to Oracle WebLogic Server using Sun JDK, Oracle JRockit or HP JDK. However, you can't migrate to IBM JDK.
==============================================
This is because the data in the OIM schema is encrypted using the IBM's encryption libraries which are not available for Sun JDK. What i understand is that the IT resource configuration details are encrypted with installed JDK. However, if we re-configure the IT resource with Weblogic setup (after installing oim on Weblogic poining to the existing database), we could proceed with this migration.
Has anyone executed Websphere to Weblogic migration before for OIM? Any input will help.
Thanks,

Sorry for the delay as I got busy with my current project. Here are the answers to your questions.
1) If i install WLS point to existing OIMDB, do i necessarily need to copy old .databasekey from WAS environment?
<Abhi>: Yes, you will have to copy these files to the WLS environment.
2) During WLS install, it'll ask for xelsysadm password. Will this password overrides to existing one in OIM DB? And later on when i'll try to login to OIM-WLS using this password, will that work?
<Abhi>: Yes, but are you planning to have different passwords. The xelsysadm password is stored in OIM database. So if you update it, it will reflect in all the OIM middle-tier instances attached to this database.
How about handling the encrypted values in WLS environment:
(1) IT resource params - reconfigure them after migration - through design console in Weblogic environment
<Abhi>: Yes. you may have to review the values in the IT resource params and the other atrifacts as RO, process forms etc. But most of the work will be done by the deployment manager export/import functionality.
(2) User password and security Q&A - We're using SSO to login to OIM, so not a concern
<Abhi>: You are good with this.
(3) UDF encrypted attribute - After doing the migration, if we run the user trusted recon 1 more time.. then all the user attrs values would be overriden (including encrytped UDF).
<Abhi>: If there is an encrypted UDF field, you will have to take care of this manually. BTW, is this field encrypted on the OIM side as well as the application side.
(4) Encrypted object/process forms - i've pending task to analyze if we've any such attrs(process form encrypted 'password' to target(e.g. AD) - i could think of such cases)
<Abhi>: If there is something like this, you will have to take care of this manually. Check the possibility of writing a custom code to go thru the OIM users and dump the decrypted data in some file. Later you can update the selective user data in the new environment
Did you follow the similar process? What issues did you face because of the IBM to SUN JDK use?
<Abhi>: Yes, I followed the same steps and did not faced much issues. It was pretty straight-forward. Just make sure that the export/import using Deployment manager is successful.
Please let me know if you have more questions.

Migration from JDK 1.4 to JDK 1.5

Similar Messages

Maybe you are looking for