| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Linux x86 Part Number B31014-11 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Linux x86 Part Number B31014-11 |
|
|
View PDF |
This chapter describes issues and workarounds for the following Oracle Application Server adapters (OracleAS adapters):
Oracle Application Server Adapter for PeopleSoft (OracleAS Adapter for PeopleSoft)
Oracle Application Server Adapter for MySAP ERP (OracleAS Adapter for MySAP ERP)
Oracle Application Server Adapter for Siebel (OracleAS Adapter for Siebel)
Oracle Application Server Adapter for J.D. Edwards OneWorld (OracleAS Adapter for J.D. Edwards OneWorld)
This chapter includes the following topics:
Section 6.1, "OracleAS Adapters: General Issues and Workarounds"
Section 6.3, "OracleAS Adapter for PeopleSoft: Issues and Workarounds"
Section 6.4, "OracleAS Adapter for MySAP ERP: Issues and Workarounds"
Section 6.5, "OracleAS Adapter for Siebel: Issues and Workarounds"
Section 6.6, "OracleAS Adapter for J.D. Edwards OneWorld: Issues and Workarounds"
The following topics discuss general issues that pertain to Oracle Application Server adapters, OracleAS Adapter J2CA (J2CA), and OracleAS Adapter Business Services Engine (BSE):
Section 6.1.5, "Using Business Services Engine for Inbound Processing"
Section 6.1.6, "Using Business Services Engine with a File Repository"
Section 6.1.17, "Invoking a Run-Time Message When BSE Is Unavailable"
Section 6.1.18, "Invoking Outbound BPEL Process at Run Time Using BSE"
Section 6.1.21, "Using the J2CA Test Tool for Outbound Only"
Section 6.1.22, "J2CA Test Tool Does Not Support DBCS Input"
Section 6.1.23, "BSE Web Services Browser Pages Do Not Support DBCS Input"
The purpose of an XML namespace is to allow the deployment of XML vocabularies (where element and attribute names are defined) in a global environment and to reduce the risk of name collisions in a given document when vocabularies are combined. Qualified namespaces are used for stricter schema validation. In documents conforming to this specification, element and attribute names appear as qualified names. Syntactically, they are either prefixed names or unprefixed names. An attribute-based declaration syntax is provided to bind prefixes to namespace names and to bind a default namespace that applies to unprefixed element names. These declarations are scoped by the elements on which they appear so that different bindings may apply in different parts of a document. Processors conforming to this specification must recognize and act on these declarations and prefixes.
In the 10.1.3.1.0 SOA release, the recommendations for BPEL and ESB based on W3C, is to perform stricter name space validations. As a result, Application Explorer generates Web services for the backend with the namespace marked as "Qualified". This means that during testing or usage of this service by BPEL or ESB, the request XML document that is being used should adhere to the schema and WSDL document. Once again, it is important to remember that the namespaces are qualified. To further understand this point, the difference is illustrated with the following example:
Input XML for ESB and BPEL, based on unqualified namespaces:
<?xml version="1.0" encoding="UTF-8"?> <CompanyCode.GetDetail> <COMPANYCODEID>1000</COMPANYCODEID> </CompanyCode.GetDetail>
Input XML for ESB and BPEL, based on qualified namespaces:
<?xml version="1.0" encoding="UTF-8"?> <bapi:CompanyCode.GetDetail xmlns:bapi="urn:sap-com:document:sap:business" CompanyCodeId="1000"> </bapi:CompanyCode.GetDetail>
Note : If you are passing an unqualified input against a WSDL document that is expecting qualified namespaces, the ESB will throw the exception as "Unable to process input xml...."
The BPEL console allows you to test deployed BPEL processes. Once a process is deployed, you can manage, monitor, and run an end-to-end scenario using the Initiate tab in the console. The iWay Adapters are certified for testing using the XML Payload option and the option of running using Through Java Delivery API. It is recommended that developers use this method for testing the iWay Adapters.
When testing an outbound BPEL process from the BPEL console or an outbound ESB process from the Enterprise Manager (EM) console, do not use the XML envelopes that are generated by these consoles. Instead, remove them and use the XML payloads that are generated from the schemas, which conform to the WSDLs for namespace qualifications.
The ESB data flows can be tested using the EM console. When creating an ESB data flow and interactions, the Web services are created and registered with the Oracle Application Server. For more information on testing Web services, see your Oracle Application Server administrator and the following documentation:
Oracle Application Server Adapter for PeopleSoft User's Guide
Oracle Application Server Adapter for MySAP ERP User's Guide
Oracle Application Server Adapter for Siebel User's Guide
Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide
Root validation, namespace validation, and schema validation for inbound processing (events) are only supported for the OracleAS Adapter for MySAP ERP with 10.1.3.1.0 BPEL. This validation is not supported for the OracleAS Siebel, OracleAS PeopleSoft, and OracleAS J.D. Edwards OneWorld Adapter.
In the following procedure, MATMAS is being used as an example for inboundprocessing.
To validate inbound processing using the OracleAS Adapter for MySAP ERP, perform the following steps. This procedure uses MATMAS as an example for inboundprocessing.
Start Application Explorer.
Connect to the MySAP target.
Expand the ALE/IDOCs node.
Verify that you have already created a channel for the MySAP adapter.
Select and expand the MATMAS – Material Master node.
Right-click MATMAS01 select Create Inbound JCA Service (event) from the context menu.
The WSDL and Validation details pane opens and includes three new check boxes for Root, Namespace, and Schema validation.
Selection of multiple validation options is allowed.
Root validation is used to validate the root element in the inbound XML document.
Namespace validation is used to validate the namespace in the inbound XML document.
Schema validation is used to validate the inbound XML document with the schema in the WSDL document.
During run time, validation is processed based on the order of the validation options that are selected.
If more than one validation option is selected, during run time if the first validation option fails, the remaining validation options are not processed.
Root and namespace validations are considered modest levels of validation. Schema validation is a stricter validation level.
It is recommended to use root and namespace validation options together, unless the the root element and namespace are different between the IDOCs in the SAP environment.
Generate the WSDL document and create the BPEL process.
Trigger the transactions (IDOCs) from the SAP GUI.
Inbound transactions that fail for the validation are shown in the SAP Transaction Monitor (SM58).
The status text field shows "java.lang.exception" for the documents that have failed the validation process.
J2CA users can create an HTTP repository connection, which enables them to generate and store WSDL documents remotely. Perform the following steps to create an HTTP repository connection in Application Explorer. To use the HTTP repository, make sure that the iwjcaivp test tool(jca-app-adapter-test) is successfully deployed and running.
Start the Application Explorer.
Right-click the Configurations node in the left pane and select New.
The New Configuration dialog box opens.
Type a name for the configuration and click OK.
Select JCA from the Service Provider list box and enter an HTTP target value in the Home field.
Use the following format for the HTTP target value:
http://hostname:port/iwafjca/JCAServlet
For example:
http://iwserv14:7777/iwafjca/JCAServlet
Click OK.
The new HTTP repository connection is added to the Configurations node.
Once you connect to the remote server, you can create new Adapter targets, generate WSDL documents, and store them in the remote server.
Note: When you configure an Adapter target with the J2CA HTTP repository, you are not required to restart the Oracle Application Server for run time purposes.
Using Business Services Engine (BSE) for inbound processing is not supported. BSE only supports services.
If you are using Business Services Engine (BSE) on IBM-AIX platforms, do not use the File repository since there are limitations present. As a workaround, use the Database repository.
Synchronous event handling is not supported for the OracleAS MySAP ERP, OracleAS Siebel, OracleAS PeopleSoft, and OracleAS J.D. Edwards OneWorld Adapter.
The ports option for inbound processing is not supported for J2CA events. Only the no-ports option is supported.
iWay will do its best effort to support the custom objects of the EIS. However, iWay cannot guarantee the support for all custom objects at the customer environment. Support to the custom object will be considered on a case by case option. Custom objects could fall under any of the following category:
SAP
BAPIs, RFCs, and ALE/IDOCs
Siebel
Business Objects, Business Services, and Integration Objects
PeopleSoft
Component Interfaces and Messages
J.D. Edwards OneWorld
Business Functions and Transaction Types
It is recommended that customers who wish to troubleshoot an issue with the custom objects of an EIS, provide the following to iWay:
Data and definition of custom objects.
Request and response XML documents for the custom objects.
Reproduction steps for the custom object.
Windows shortcuts for the Business Services Engine (BSE) Servlet and JCA Test Servlet don't work from the Programs menu. As a workaround, invoke the shortcuts and update the URL by providing the correct host name , port number, and application name. You can also invoke the URL directly from the browser.
The following error message is displayed when OPMN is started or the JCA Test Servlet page is accessed on a Windows platform:
The application has failed to start because iwsiebel.core.dll was not found. Re-installing the application may fix this problem.
This error message can be ignored.
The OracleAS Adapters are certified with 10.1.3.1.0 BPEL and ESB only. Any other method of invoking the adapters is not certified and is not supported as a result. This includes invoking the adapters through a JAVA CCI program.
To configure an adapter, you must copy the enterprise information system (EIS) client lib files associated with the target system into your lib directory, OracleAS_home \adapters\application\lib. You cannot have multiple versions of the client lib files in the same lib directory. Therefore, you cannot have one instance of the adapter configured to connect to different EIS versions at the same time.
Installing the OracleAS adapters and iWay 55 (iWay Service Manager and the iWay adapters) on the same machine is currently not a supported configuration. As a workaround, use a separate machine for each version.
The OracleAS adapters support only UTF-8 encoding.
When using a J2CA implementation, you must redeploy J2CA or restart Oracle Containers for J2EE (OC4J) to refresh the repository and see the new target in the J2CA Test Servlet after it is created in Oracle Application Server Adapter Application Explorer (Application Explorer). The default URL is:
http://hostname:port/iwjcaivp
This applies to J2CA targets only, not BSE targets. It does not affect the first target created for a given EIS. It only affects the targets created after the first one for a given EIS.
When invoking a run-time message while BSE is unavailable, a "Whitespace required" exception error occurs.
The error message "unable to connect to URL http://host:port/ibse..." appears.
When invoking an outbound BPEL process at run time using BSE, a "Not able to find SoapRouter" message appears.
Workaround: Add the following element in the respective bpel.xml file:
<property name "optSoapShortcut">false</property>
The "Java command is not found" error appears when iwae.sh opens.
You must set the JAVACMD path in iwae.sh to OracleAS_home/jdk/bin/java.
The ApplicationsWSDLHome parameter found in the collaxa-config.xml file specifies the location where the application WSDLs are exported. The property value is incorrectly set to: /oracleas\adapters\application\wsdls.
You must correct the value of the property as follows: /oracleas/adapters/application/wsdls.
The J2CA Test Tool must be used only for outbound (services). Inbound (events) activity options available in the tool are not supported.
When using a J2CA configuration, the browser-based test tools add encodings to the content being sent. The J2CA test tool causes characters to become garbled due to these added encodings. Therefore, you cannot perform a test using input that contains Japanese characters. You cannot test create, insert, or update type of functions using Japanese characters in J2CA for any adapters in any releases.
When using a BSE configuration, the browser-based test tools add encodings to the content being sent. The BSE test tool causes characters to become garbled due to these added encodings. Therefore, you cannot perform a test using input that contains Japanese characters. A possible workaround is to use a tool that can send pure SOAP requests.
Users who want to create an ESB process for a Web service, must create the ESB process using the SOAP Service.
Start Oracle JDeveloper.
Open a new ESB project.
Right-click the work area, select Create ESB Service from the context menu and click SOAP Service.
iWay Adapters are certified with the English language. However, on specific release levels, some iWay Adapters are also certified with the Japanese language. If you have encountered issues with other languages, please contact iWay Customer Support for a workaround.
The following topics discuss issues that pertain to OracleAS Adapter Application Explorer:
When starting Application Explorer, ensure the following:
Set the environment variable $IWAY55 to $ORACLE_HOME/adapters/application
Add executable permission as follows:
chmod u+x $ORACLE_HOME/adapters/application/tools/iwae.sh
OracleAS Adapter Application Explorer cannot be used to connect to remote machines for a J2CA configuration when using a File or DB repository. When using a J2CA configuration, OC4J must be installed on the same machine that is being used as the container for the adapters. If you need to use OracleAS Adapter Application Explorer to connect to the OC4J on a remote machine, configure an HTTP repository instead. For more information on how to create a connection using an HTTP repository, see "HTTP Repository Connection".
The following topics discuss issues that pertain to OracleAS Adapter for PeopleSoft:
Section 6.3.1, "PeopleSoft Versions and PeopleTools Release Levels Supported"
Section 6.3.2, "PeopleSoft Versions and PeopleTools Release Levels Supported"
Section 6.3.3, "PeopleSoft Library Files and Component Interface Java API Files"
Section 6.3.4, "PeopleSoft LDAP Authentication Incompatible"
Section 6.3.11, "Limitation When Inserting a Second Row for Level 1, 2, or 3 Scrolls"
Section 6.3.12, "Limitation when Creating a Schema for Multilevel Component Interfaces"
Section 6.3.15, "Differences Between Component Interface Functionality and Adapter Functionality"
Section 6.3.16, "Missing Field Errors When Using a Component Interface"
Section 6.3.18, "Differences Between Component Interface Functionality and Adapter Functionality"
Section 6.3.23, "Component Interface Java API Compilation Errors (People Tools 8.46)"
The following table indicates which combinations of adapter platforms and PeopleSoft platforms are supported, and for each combination, which PeopleSoft release and PeopleSoft Tools release is supported.
| Adapter Platform | PeopleSoft Platform | PeopleSoft Release | PeopleTools Release Level |
|---|---|---|---|
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 8.1 | 8.16.03 - 8.22 |
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 8.4 | 8.40.05 - 8.48 |
| UNIX (HP-UX, Solaris) | Solaris | 8.1 | 8.16.03 - 8.22 |
| UNIX (HP-UX, Solaris) | Solaris | 8.4 | 8.40.05 - 8.48 |
The following table indicates which combinations of adapter platforms and PeopleSoft platforms are supported, and for each combination, which PeopleSoft release and PeopleSoft Tools release is supported.
| Adapter Platform | PeopleSoft Platform | PeopleSoft Release | PeopleTools Release Level |
|---|---|---|---|
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 8.1 | 8.16.03 - 8.22 |
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 8.4 | 8.40.05 - 8.48 |
| UNIX (HP-UX, Solaris) | Solaris | 8.1 | 8.16.03 - 8.22 |
| UNIX (HP-UX, Solaris) | Solaris | 8.4 | 8.40.05 - 8.48 |
When installing the OracleAS Adapter for PeopleSoft, make sure the psjoa.jar library file and PeopleSoft Component Interface Java API files are copied into the following directories:
$oraclehome\adapters\application\lib
$oraclehome\j2ee\home\connectors\jca-app-adapter\jca-app-adapter
Explanation
PeopleSoft LDAP authentication relies on sign-on PeopleCode. However, the authentication services that PeopleSoft provides with component interfaces do not invoke sign-on PeopleCode, so you cannot use PeopleSoft LDAP authentication with OracleAS Adapter for PeopleSoft.
Workaround
None.
Explanation
OracleAS Adapter for PeopleSoft does not automatically reconnect when a connection to PeopleSoft becomes unavailable.
Workaround
None.
Explanation
OracleAS Adapter for PeopleSoft does not support the HTTPS protocol for events.
Workaround
None.
Explanation
OracleAS Adapter for PeopleSoft uses messages only for events and not for services.
Workaround
None.
Explanation
PeopleSoft has acknowledged a limitation with component interfaces that contain level 2 scrolls. If you try to insert a new row on a level 2 scroll, then a Null Pointer Exception error occurs.
If you receive this error, then you must upgrade your PeopleSoft release level.
This limitation is fixed in PeopleTools Version 8.16.08, and PeopleTools Version 8.17.02 in the 8.1x code line. It is tracked by PeopleSoft Incident T-MZYGAR-2C5YS.
In the 8.4x code line, this limitation is tracked by PeopleSoft Incident T-TCHURY-YZ9FR and is fixed in PeopleSoft 8.41.
Workaround
None.
Explanation
PeopleSoft has acknowledged a limitation with component interfaces that contain level 3 scrolls. If you try to insert a new row on a level 3 scroll, then a Null Pointer Exception error occurs.
If you receive this error, then you must upgrade your PeopleSoft release level.
This limitation is fixed in PeopleTools Version 8.18 and is tracked by PeopleSoft Incident T-MZYGAR-D2529. However, this is still a limitation in PeopleSoft 8.41 and 8.42 (PeopleSoft Incident T-MZYGAR-3F72X). PeopleSoft has reported that this will be fixed in 8.43 (PeopleSoft incident report, 562734000).
Workaround
None.
Explanation
PeopleSoft has acknowledged that there is a limitation with effective dating and multiple transactions. If you want to insert multiple effective dated rows for the same primary keys, then you must use two separate transactions. This limitation is tracked by PeopleSoft Incident T-ACESAR-BS362.
Workaround
None.
Explanation
If you are trying to insert a level 1, 2, or 3 scroll and the following conditions exist:
There is exactly one row for the level 1, 2, or 3 scroll.
There are required field names that end in a numeric value.
An error message appears, in the following format:
This is an invalid property {ADDRESS_1} (91,15)
This example was created using the VNDR_ID Component Interface from the Financials application. Note that the actual property name is ADDRESS1.
Workaround
As a workaround, perform the following steps:
In the PeopleSoft Application Designer, open the component interface with which you are working.
Select the property that ends in a numeric value.
Right-click and select Edit Name from the context menu.
Change the name of the property.
You can select a name that does not end in a number (for example, ADDRESSA), or you can add an underscore (for example, ADDRESS_1).
Save the component interface.
Regenerate the Java APIs for the component interface.
Use the revised property name in your XML transaction.
Explanation
In later releases of the 8.1x series, if you try to create a schema for a multilevel component interface, then the following error occurs:
Index: -1, Size: 0
This is a result of a change in the back-end PeopleSoft interface in later versions of the 8.1 series.
Workaround
Retain the iwpsci84.jar file and delete the iwpsci81.jar file from the OracleAS_home \adapters\application\lib directory.
See Also:
Oracle Application Server Adapters Installation Guide
Oracle Application Server Adapter for PeopleSoft User's Guide
Explanation
The YYYY-MM-DD date format does not work for a component interface key.
PeopleSoft has acknowledged this limitation for most releases of PeopleTools and has addressed it in the newest releases. For more information, refer to PeopleSoft Resolution ID 200730918.
Workaround
Use the MM/DD/YYYY format. Alternatively, you can write a PeopleSoft method that takes a date format of YYYY-MM-DD, changes the date to a string, reformats it to DD/MM/YYYY, and passes it to the component interface date.
Explanation
It is possible to create component interfaces within PeopleSoft that are internally inconsistent. Inconsistencies in component interface templates delivered by PeopleSoft have been observed. Indicators of this problem include errors when generating the Java APIs in the PeopleSoft Application Designer.
If you encounter errors while generating the Java APIs, then the component interface is likely to malfunction and can possibly corrupt your database. The correct operation of component interfaces when errors appear during API generation cannot be guaranteed. In addition, it is strongly recommended that the source of the errors is fixed before continuing.
Workaround
Fix the component interface using PeopleTools.
Explanation
Differences between component interfaces and standard application functionality relating to panel processing have been observed. Among the possible symptoms of these differences are messages such as, "First Operand of . is NULL." OracleAS Adapter for PeopleSoft should replicate the functionality of a PeopleSoft Component Interface, but only when the component interface is run through the PeopleSoft application server in three-tier mode.
If you notice differences between expected component interface functionality and adapter functionality, then you must verify that the differences are real by running the component interface with the PeopleTools Component Interface test tool in three-tier mode.
Workaround
Test the component interface using the PeopleTools Component Interface testing tool in three-tier mode only.
Explanation
When using a component interface, it is difficult to determine which of the required fields are missing when you receive a PeopleSoft error message that states, "The highlighted field is required." PeopleSoft has acknowledged this limitation.
Workaround
You can edit the message in the PeopleSoft message catalog to pass a variable for the field name. For more information, refer to PeopleSoft Resolution 200731449.
Explanation
Related display fields are not supported by component interfaces. PeopleSoft has acknowledged this limitation.
Workaround
For more information, refer to PeopleSoft Resolution 200731974, which offers several workarounds.
Explanation
PeopleSoft has acknowledged problems in the component interface back-end processor which will cause the adapter to act differently than the component interface test tool in three-tier mode for certain component interfaces.
PeopleSoft Case 1965239 describes a problem with the CI_JOB_DATA_HIRE Component Interface in HR 8.1x. In this situation, the NAME field is not populated by PeopleCode correctly. The workaround is to manually populate the NAME field through the XML.
PeopleSoft Resolution ID 200728981 describes a problem with the JOBCODE Component Interface which does not allow the REG_TEMP field to be changed to empty. As a workaround, customers must upgrade to a later release of PeopleTools.
Workaround
The workaround is dependent on the component interface.
Explanation
A failure occurs when inserting multiple effective dated rows.
Workaround
If you want to insert multiple effective dated rows for the same primary keys, then you must use two separate transactions. This limitation is tracked by PeopleSoft Incident T-ACESAR-BS362.
Explanation
For certain releases of PeopleTools 8.4x, you may receive the following message in your debug window:
PSProperties not yet initialized!
This is a PeopleSoft warning message you can ignore.
Workaround
None.
Explanation
When you attempt to access the LOCATION Component Interface using the Human Resources application, release 8.80.000, a failure occurs during runtime and the following message is displayed:
Component Interface Not Found
This is due to a problem in the way the PeopleSoft application has been delivered and is not related to the PeopleTools release.
Workaround
Perform the following steps:
Open the component interface in the PeopleTools Application Designer.
Make a small change to the component interface.
Undo the change.
Save the component interface.
This procedure resets certain internal PeopleSoft data structures, which enables OracleAS Adapter for PeopleSoft to find the component interface. This has been observed in the LOCATION Component Interface running on the Human Resource applications release 8.8.000 on several different releases of PeopleTools, but it may occur in other component interfaces as well.
Explanation
Although PeopleSoft permits component interface names that begin with certain special characters (such as an underscore), Application Explorer does not recognize such names.
Workaround
Begin component interface names with the letters A-Z or the integers 0-9.
Explanation
When you compile all Java APIs for the component interfaces using People Tools 8.46, you may encounter compilation errors with some of the component interfaces.
Workaround
You can manually correct the Java source code of the failing component interfaces. Alternatively, if the failing component interfaces are not going to be used, then remove them from the API build process and do not include them in the build.
The following topics discuss issues that pertain to OracleAS Adapter for MySAP ERP.
Section 6.4.2, "Intermediate Documents (IDocs) During Inbound Processing"
Section 6.4.4, "SAP IDoc Data with Japanese DBCS Characters Overflows and Truncates Characters"
Section 6.4.5, "No Values Set for Code and Details in Binding Fault"
The following MySAP ERP platforms are supported by OracleAS Adapter for MySAP ERP:
SAP R/3 Enterprise 47x100
SAP R/3 Enterprise 47x200
MySAP ERP Central Component (ECC) 5.0, deployed on SAP NetWeaver 2004
MySAP ERP Central Component (ECC) 6.0, deployed on SAP NetWeaver 2004s
SAP Java Connector (SAP JCo) Version 2.18.
For the current release status of the SAP Java Connector, refer to SAP Note #549268 in the SAP Service Marketplace.
Release versions may vary by product component. In addition, SAP functions may vary by SAP product version and support package.
Note: The OracleAS Adapter for MySAP ERP supports only the versions listed above. It is not recommended to use the OracleAS Adapter for MySAP ERP with older versions of SAP R/3. If you plan to use the adapter with older versions of SAP R/3 for example SAP R/3 4.6C, prior approval from iWay Software Product Management is required.
SAP R/3 Adapter Support
The SAP R/3 Adapter (iwsap.jar) is not certified and not supported for the 10.1.3.1.0 release even though it is available with the OUI installer. Only the MySAP ERP Adapter (iwmysap.jar) is certified and supported for this release.
Explanation
When using IDocs during inbound processing (service mode), if the DOCNUM field does not have a unique document number for each IDoc, then the system creates an IDoc for each header record in the IDoc file and duplicates the data for each IDoc.
Workaround
Do not change the columns in a table used by an Oracle Database adapter interaction after deployment.
Explanation
Unable to connect to an SAP target in BSE.
Workaround
For Solaris, before connecting to an SAP target in BSE, set the environment variable LD_LIBRARY_PATH to OracleAS_home/adapters/application/lib.
For HP-UX, before connecting to an SAP target in BSE, set the environment variable SHLIB_PATH to OracleAS_home/adapters/application/lib.
Explanation
SAP IDoc data with Japanese DBCS characters overflows and truncates characters in all BSE and J2CA events and services.
Workaround
This will be fixed in a future release.
Explanation
If you use the wrong request XML to invoke a SAP outbound process in Oracle BPEL Console, then the instance will be faulted and a binding fault will be thrown. Log in to Oracle BPEL Console, select the faulted instance, and click Audit. No values are set for Code and Details in the binding fault.
Workaround
None.
Explanation
When using the OracleAS Adapter for MySAP ERP during outbound processing, the following type of exception from the BPEL or ESB layer may occur in certain situations:
failed due to: Error in processing the input document.; nested exception is: javax.resource.ResourceException: Error in processing the input document.
At the same time, the JCA log file that is generated by the adapter shows the exact error message. For example, if you use the GetDetail method for the CompanyCode SAP BAPI in your outbound processing, the following error message is shown in the JCA log file:
MySAP response error: BapiError: Company code 1010 does not exist
Workaround
Perform the following steps:
Start OracleAS Adapter Application Explorer and connect to an appropriate configuration.
Expand the MySAP adapter node to view the available targets.
Right-click an available MySAP target node and select Edit.
The Application Server dialog box displays the target connection information.
Click the Advanced tab.
From the Error Handling drop-down list select Creates Error Document.
Click the User tab.
In the Password field, type a valid password for the MySAP ERP application.
Click OK.
Restart OracleAS Adapter Application Explorer.
Oracle BPEL or ESB generates the error message in the response XML document. For example, if you use the GetDetail method for the CompanyCode SAP BAPI in your outbound processing, the following error message is shown in the XML response:
<companycode_get_detail_oct24ProcessResponseurn:sap-com:document:sap:business.responsehttp://xmlns.oracle.com/companycode_get_detail_oct24> <COMPANYCODE_ADDRESS> </COMPANYCODE_ADDRESS> <COMPANYCODE_DETAIL> </COMPANYCODE_DETAIL> <RETURN> <TYPE>E</TYPE> <CODE>FN020</CODE> <MESSAGE>Company code 1010 does not exist</MESSAGE> <LOG_MSG_NO>000000</LOG_MSG_NO> <MESSAGE_V1>1010</MESSAGE_V1> </RETURN> </companycode_get_detail_oct24ProcessResponse>
The following topics discuss issues that pertain to OracleAS Adapter for Siebel.
Section 6.5.3, "Additional Configuration in the Siebel Environment"
Section 6.5.5, "Updating or Deleting Siebel Records Using OracleAS Adapter for Siebel"
Section 6.5.6, "Adapter Exception Error If Siebel Request Document Contains Japanese Characters"
Section 6.5.9, "Siebel Schema Issue When Generating Multiple WSDL Files"
The following table indicates which combinations of adapter platforms and Siebel platforms are supported, and for each combination, which Siebel release and Siebel APIs are supported.
| Adapter Platform | Siebel Platform | Siebel Release | API |
|---|---|---|---|
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 6.3 - 7.8 | Java Data Bean |
| UNIX (HP-UX, Solaris) | Solaris | 6.0.1 - 7.8 | Java Data Bean |
The following table indicates which combinations of adapter platforms and Siebel platforms are supported, and for each combination, which Siebel release and Siebel APIs are supported.
| Adapter Platform | Siebel Platform | Siebel Release | API |
|---|---|---|---|
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 6.3 - 7.8 | Java Data Bean |
| UNIX (HP-UX, Solaris) | Solaris | 6.0.1 - 7.8 | Java Data Bean |
Some out-of-the-box Siebel business services may require additional setup steps in the Siebel environment before they can be run successfully. For example:
When using a business service such as EAI XML Converter, before generating the XSD for the integration object, you should use Siebel tools to remove the 'xml container element' tag in the integration components you plan to use.
When building a solution with the EAI dispatch service business service, you may need to set up a named subsystem to handle HTTP requests.
Explanation
When connecting to Siebel using the Java Data Bean Interface, you cannot reconnect after initial connection loss. This might occur when Application Explorer experiences a brief loss of network connection or if the Siebel Server or Gateway Service is restarted while Application Explorer is logged into the Siebel application.
Workaround
To log in successfully to the Siebel application, restart your application server and Application Explorer. This is a known Siebel API issue. Refer to Siebel Alert 984 for more information.
Explanation
If you are logged in as a Siebel user that does not belong to the team that owns the record being updated or deleted, then you cannot perform the action. By default, the adapter is set to 'My' view. However, in Siebel Access Control there are other views, such as 'All' view and 'Organization' view. Therefore, even if the user does not belong to the team and the record is not visible in 'My' view, the user may be able to update or delete the record through another view in the Siebel front end. This is not possible through the adapter. The adapter requires that the user is part of the team of the record being updated or deleted.
Workaround
There are two possible workarounds:
Log in through the Siebel adapter as a user that is already part of the team that owns the record you need to update or delete.
Add the user to the team that owns the record you need to update or delete.
Explanation
An adapter exception error is returned if the Siebel request document contains Japanese characters in OracleAS Adapter J2CA. The same request works in BSE.
Workaround
This will be fixed in a future release.
Explanation
OracleAS Adapter for Siebel does not support the HTTPS protocol for services and events.
Workaround
None.
Explanation
OracleAS Adapter for Siebel does not support Multi-Value Groups (MVG) with join specifications.
Workaround
None.
Explanation
When you attempt to generate two different WSDL files for different Siebel objects, the second generated WSDL file contains the same schema information as the first one.
Workaround
Follow these steps to avoid this issue:
Generate the WSDL for the first Siebel object.
Before you generate WSDL for another Siebel object, remove the existing schemas from the following folder:
<Oracle_Home>\adapters\application\config\<configuration_name>\schemas\Siebel\<target_name>
Generate the WSDL for the next Siebel object.
When the OracleAS Siebel Adapter invokes Siebel Business Service – EAI XML Converter with the method "IntObjHierToXMLDOC", the following error is generated:
In BSE:
The XML Document cannot be converted to an XML Hierarchy.(SBL-EAI-04110)
In J2CA:
javax.resource.ResourceException: Error in processing the input document
iWay has opened a Service Request (SR# 38-3296542173) with Siebel Customer Support for this issue. Other Business Services that convert XML to the property set may also encounter this error message. Release Notes will be updated once a resolution is provided by Siebel.
You must perform the following steps to connect to your Siebel system (version 6.2 and lower) using COM connectivity for a JCA configuration.
Install Siebel thick client on the same machine where the adapters are installed.
Install the database client (Microsoft SQL Server or Oracle) on the same machine.
The Siebel .DLL files (iwsiebel.local.dll and iwsiebel.core.dll) in the adapter lib folder must be added to the Application server path.
Edit the uagent.cfg file and change the data source parameter value from "local" to "server".
The uagent.cfg file can be found in the following Siebel thick client folder:
c:\sea\client\bin
Edit the data source for SEA MSQl with appropriate parameters.
You can edit a data source in Windows by accessing the Control Panel, Administrative Tools, and Data Sources (ODBC).
Use the following target type when creating the adapter target connection:
Siebel 6.2 - (Local COM Access Implementation)
Provide the full path to the uagent.cfg file when creating an adapter target connection, for example:
c:\sea\client\bin\uagent.cfg
The following topic discusses issues that pertain to OracleAS Adapter for J.D. Edwards OneWorld.
Section 6.6.1, "J.D. Edwards OneWorld Platforms, Products, and Releases Supported"
Section 6.6.2, "J.D. Edwards OneWorld Inbound WSDL Generation on UNIX Platforms"
Section 6.6.4, "J.D. Edwards OneWorld Versions and Library Files"
The following table indicates which combinations of adapter platforms and J.D. Edwards OneWorld platforms are supported, and for each combination, which J.D. Edwards OneWorld products and releases are supported.
| Adapter Platform | J.D. Edwards OneWorld Platform | J.D. Edwards OneWorld Product and Release |
|---|---|---|
| Windows, AS400, HP 9000/B, Sun or IBM RS/6000 | Windows, AS400, HP 9000/B, Sun or IBM RS/6000 |
|
You cannot generate inbound WSDL documents for J.D. Edwards OneWorld on UNIX platforms. As a workaround, generate the WSDL documents on a Windows platform and use the same WSDL documents on a UNIX platform. However, you must ensure that the adapter target and channel on the Windows and UNIX platforms have identical configuration details.
The following section provides information on the J.D. Edwards OneWorld Unit of Work (UOW).
iWay recommends the customer to generate individual business functions of J.D. Edwards OneWorld and then group them together.
Generating the individual business functions and grouping them together is completely based on the experience and knowledge related to the business functions of J.D. Edwards OneWorld. There is no documentation on generating the UOW.
To create the XML Schema Document (XSD) files that can be used for UOW, perform the following steps:
Trigger the appropriate event from the J.D. Edwards OneWorld GUI and generate an XML output file based on the event.
Using the XML file, create an XSD file using an XML editor, such as XMLSPY.
When creating the XSD, make sure that the XSD satisfies the SOA 10.1.3.1 namespace requirements. Manually add the namespace, target namespace, and other items that are required for SOA 10.1.3.1.
Once generated, copy the XSD files for the UOW into the repository folder. This repository folder is automatically configured on your file system when a J.D. Edwards OneWorld target is created using Application Explorer.
The following table lists the library files by version that are required for the OracleAS Adapter for J.D. Edwards OneWorld.
| J.D. Edwards OneWorld Version | Required Library Files |
|---|---|
| XE (B7333) | Connector.jar and Kernel.jar |
| ERP 8.0 (B7334) | Connector.jar and Kernel.jar |
| EnterpriseOne 8.9 (B9) | Connector.jar, Kernel.jar, jdeutil.jar, and log4j.jar |
| EnterpriseOne 8.10 | Connector.jar, Kernel.jar, jdeutil.jar, and log4j.jar |
| EnterpriseOne 8.11 | Connector.jar, Kernel.jar, jdeutil.jar, and log4j.jar |
Oracle OEM 10.1.3.1 WSDL generation has a new feature, which allows generating the outbound and inbound WSDLs for both qualified and unqualified namespaces. In earlier versions, schemas were created for unqualified namespaces and WSDLs were generated for qualified namespaces. This was creating issues for namespace prefixes. Hence, this patch allows WSDLs to be generated for both qualified and unqualified namespaces. Please note, this is applicable only to the J2CA configurations.
The Java archive (.jar) files that have changed as a result of this new feature include:
iwafcont.jar
iwae.jar
iwaeutil.jar
iwafjca15.jar
orabpel-adapters.jar
The following table lists the deployments of the .jar files.
Table 6-1 Location of JAR Files
| SI. No | Jar File | Folders |
|---|---|---|
|
1. |
iwafcont.jar |
$ORACLE_HOME\adapters\application\lib and $ORACLE_HOME \j2ee\home or oc4j_soa\connectors\jca-app-adapter\jca-app-adapter |
|
2. |
iwae.jar |
$ORACLE_HOME\adapters\application\lib and $ORACLE_HOME \j2ee\home or oc4j_soa\connectors\jca-app-adapter\jca-app-adapter |
|
3. |
iwaeutil.jar |
$ORACLE_HOME\adapters\application\lib and $ORACLE_HOME \j2ee\home or oc4j_soa\connectors\jca-app-adapter\jca-app-adapter |
|
4. |
iwafjca15.jar |
$ORACLE_HOME \j2ee\home or oc4j_soa\connectors\jca-app-adapter\jca-app-adapter |
|
5. |
orabpel-adapters.jar |
$ORACLE_HOME\adapters\application\lib and $ORACLE_HOME \adapters\lib |
Note: Oracle Application Server should be stopped and restarted when deploying the .jar files.
Generating WSDLs With Qualified Namespaces
Perform the following steps to generate WSDLs with qualified name spaces:
Start OracleAS Adapter Application Explorer.
Connect to a J2CA configuration.
Connect to an adapter target, for example, MySAP.
Select ALE(IDOCS).
Select any IDOC, for example MATMAS and expand the node.
Right-click MATMAS01 and select Create inbound JCA Service (event) from the context menu to generate an WSDL for the business object.
The Export WSDL dialog box opens.
The Element Form Default field is new and provides two options:
qualified (selected by default)
unqualified
Select qualified and click OK.
The WSDL is generated with a qualified namespace.
Generating Outbound WSDLs With Qualified Namespaces
Perform the following steps to generate outbound WSDLs with qualified name spaces:
Start OracleAS Adapter Application Explorer.
Connect to a J2CA configuration.
Connect to an adapter target, for example, MySAP.
Select Business Object Repository, Financial Accounting, Company Code, and GetList.
Right-click GetList and select Create outbound JCA Service (Request / Response) from the context menu to generate an WSDL for the business object.
The Export WSDL dialog box opens.
The Element Form Default field is new and provides two options:
qualified (selected by default)
unqualified
Select qualified and click OK.
The outbound WSDL is generated with a qualified namespace.
Support for Different WSDL Types
Only qualified WSDLs are supported for the OEM adapters and unqualified WSDLs are not supported.
This section describes known errors in the documentation. It also identifies sections where further clarifications are necessary.
The following is an amendment to Step 9 in the section "Configuring the Database Repository for J2CA" for the J.D. Edwards, MySAP, PeopleSoft, and Siebel user guides:
Oracle database JDBC drivers should be copied to the following folder:
OracleAS_home\adapters\application\lib
Where OracleAS_home is the directory where Oracle Application Server is installed.
This section provides clarification to Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide.
Appendix: A, "Configuring J.D. Edwards OneWorld for Outbound Transaction Processing"
Heading: "The Data Export Control Table and the Processing Log Table"
Page: A-2
Modify the second paragraph in this section as follows:
The records in the Data Export Control table are used to determine the vendor-specific objects to call from the Outbound Subsystem batch process (R00460). Perform the following steps:
Start the subsystem R00460 manually.
The subsystem should be always running (Job Status).
Assign the separate job queue in the jde.ini file.
Assign the same queue for the XJDE0001 version of R00460.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|