WebSphere Adapter for Oracle E-Business Suite, version 7.5.0.3 notes

This document contains the following sections:
Enhancements and fixes
New and modified connector properties
Upgrade notes

This table lists the enhancements and fixes in fix pack version 7.5.0.3
Enhancements
#CRAPARTitleDetails
There are no enhancements in this fix pack.
Fixes
#RTCAPARTitleDetails
17176EMD fails when selecting multiple Stored Procedures using Oracle EBS Adapter on Rational Application Developer
Symptom: After metadata discovery if we select 2 or more stored procedure having nested type parameters fails while completing Enterprise Metadata Discovery.
Resolution: EMD works fine with multiple Stored Procedure selection.



This table lists the enhancements and fixes in fix pack version 7.5.0.1.
Enhancements
#CRAPARTitleDetails
There are no enhancements in this fix pack.
Fixes
#CRAPARTitleDetails
1103704JR39584IBM WebSphere Adapter for Oracle EBS is unable to generate interface.
Symptom: When a Complex Type contained in Record/Table/ArrayObject has different owner type (i.e from different schema) than the schema in which Record/Table/Array has been defined, then Adapter will not discover the Complex Type. This is because the adapter retrieves the metadata of Type which are present in same schema, which will cause wrong type found error or type not found error.
Resolution: Adapter can now discover types from different schemas too.
2103706JR39285Oracle EBS- ESD fails for procedure without parameters with NPE.
Symptom: When binding a noparam procedure NPE is thrown and can not finsh EMD process.
Resolution: NULL check has been added to handle the NPE if none of the Input/Output parameters are specified.
3103707JR39340Oracle EBS- Incorrect schema created for ROWTYPE records.
Symptom: When Adapter reads a procedure from Oracle, if there is a record or table which is of type ROWTYPE, then adapter will not retrieve the metadata of ROWTYPE and hence will not build the record business object correctly.
Resolution: Type ROWTYPE is supported now and Adapter can discover and build business objects correctly.
4JR40955Hostname in EMD is not trimmed for Oracle EBS XML Gateway 12.1 version
Symptom: If we input a value to hostname field in EMD with a white space the adapter returns "Unknown Host" error
Resolution: The HostName value is trimmed to remove any invalid spaces present.
5JR40956Hostname wont get populated automatically during iterative emd for Ora EBS adapter
Symptom: Hostname field in the EMD screen does not get populated automatically during iterative edit. This behaviour is also observed while creating second external service.
Resolution: Hostname value is now getting populated successfully for edit binding.
6JR40970Changes to the Connection retry properties are not updated in artifacts
Symptom: The connection retry settings updated through EMD is not updated in import and importex files generated for Ora EBS Outbound module..
Resolution: Any change to the connection retry properties are been logged into the artifacts successfully.


This table lists new and modified connector properties
#VersionAdded or ModifiedPropertyLocation
There is no new connector property introduced/modified for this version of fix pack.


To upgrade to the fix pack version 7.5.0.1, do the following.
1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding.
2. If you need to use the Interim Fix for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files.
   a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab.
   b. Open the dependency editor and remove the connector project.
   c. Delete the connector project from the workspace.
   d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed.
   e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab.
   f. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module.
3. If you need to update deployed applications on WebSphere Process Server, do the following:
   a. Stop the deployed application.
   b. Select Update for the corresponding application on the WebSphere Process Server administrative console.
   c. Select Replace or add a single file with a relative path as name of the RAR file - CWYOE_OracleEBS.rar.
   d. Click Browse on the local file system to select the updated RAR file that has the changes.
   e. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated.
   f. Start the application again.


Sep 25th, 2012 6:00 PM
(C) 2012 IBM Corporation. Proprietary and Confidential. All Rights Reserved.