Custom Search SOABYTE here

Tuesday, June 29, 2010

Upgrading Oracle SOA Suite Client Applications

The client applications that depend on the 11g SOA applications should be reviewed, upgraded and tested.
Use the following list to analyze client applications for required updates that will allow them to work with newly upgraded 11g Oracle SOA Suite environment:
Ø  Review the client applications to understand which remote Oracle SOA Suite APIs they are using.
Ø   Search your client applications for any references to Oracle SOA Suite HTTP URLs. The syntax of the Oracle SOA Suite 11g HTTP URLs has changed from 10g. To obtain the new URL that a client can use to access a deployed Oracle SOA Suite 11g application, use the home page of the application deployment in Oracle Enterprise Manager Fusion Middleware Control. 

Ø   If any of the client applications are using Web Services Addressing (WS-Addressing), then you must modify the client. Oracle SOA Suite 11g supports WS-Addressing 1.0 for clients. As a result, you must either use a SOAP processor that understands WS-Addressing 1.0, or if you are using a SOAP processor that does not support WS-Addressing 1.0, then you must manually modify the 11g WSDL and change the client to get or set the WS-Addressing 1.0 headers.
Ø    Review your client applications for references to message targets, such as JMS queues and data source. Any references to these resources must be updated to point to the upgraded, Oracle SOA Suite 11g environment.
 If a client application is using Oracle Service Bus (OSB) to invoke an Oracle BPEL Process Manager process with the optimized transport, you must modify the client application so it uses SOAP/HTML to invoke the Oracle BPEL Process Manager process.


Post a Comment

Blogger Profile