| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for HP-UX PA-RISC (64-bit) B25187-09 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for HP-UX PA-RISC (64-bit) B25187-09 |
|
Previous |
Next |
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 SAP R/3 (OracleAS Adapter for SAP)
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)
This chapter includes the following topics:
Section 12.1, "OracleAS Adapters: General Issues and Workarounds"
Section 12.2, "OracleAS Adapter Application Explorer: Environment Variable and Permission Settings"
Section 12.3, "OracleAS Adapter for PeopleSoft: Issues and Workarounds"
Section 12.4, "OracleAS Adapter for SAP: Issues and Workarounds"
Section 12.5, "OracleAS Adapter for Siebel: Issues and Workarounds"
Section 12.6, "OracleAS Adapter for J.D. Edwards: 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).
Adapter Compatibility
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.
Unsupported Configuration
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.
Encoding Support
The OracleAS adapters support only UTF-8 encoding.
New OracleAS Adapter J2CA Targets
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.
Starting the EIS Adapter Plugin When BSE Is Unavailable
When starting the EIS Adapter Plugin while BSE is unavailable, a ÒWhitespace requiredÓ exception error occurs.
The error message "unable to connect to URL http://host:port/ibse..." appears.
Invoking a Run-Time Message When BSE Is Unavailable
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.
Invoking Outbound BPEL Process at Run Time Using BSE
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>
Restarting the EIS Adapter Plugin After Restarting BSE
After you restart BSE, you must also restart the EIS Adapter Plugin.
Using J2CA Event WSDL With an Oracle Database Repository
If you are using an Oracle database repository with a J2CA configuration, you must perform the following steps.
After you create an inbound J2CA service (event) in Application Explorer, you must manually update the generated WSDL file and add the database connection details. This is necessary to enable the adapter to find the appropriate configuration.
Locate the generated WSDL file.
By default, the WSDL files you generate in Application Explorer are saved in the following directory: OracleAS_home\adapters\application\wsdls\. For example, C:\OraHome\adapters\application\wsdls\PERSONSYNC_receive.wsdl).
Edit the generated WSDL file to include the ra.IWayRepoURL, ra.IWayRepoUser, and ra.IWayRepoPassword parameters in the jca:address section, as shown in the following example of an edited WSDL file.
For example, an unedited WSDL file may look like this:
<jca:address ResourceAdapterClassName="com.iwaysoftware.afjca15.IWAFResourceAdapter" ra.IWayHome="C:\OraHome\adapters\application\tools\.." ra.IWayConfig="jca_sample" ra.LogLevel="DEBUG" />
The file must be edited as follows:
<jca:address ResourceAdapterClassName="com.iwaysoftware.afjca15.IWAFResourceAdapter" ra.IWayHome="C:\OraHome\adapters\application\tools\.." ra.IWayConfig="jca_sample" ra.LogLevel="DEBUG"ra.IWayRepoURL="jdbc:oracle:thin:@hostname:1521:orcl" ra.IWayRepoUser="scott" ra.IWayRepoPassword="tiger" />
If you do not change the WSDL as described, the adapter will not be able to find the appropriate configuration. An error similar to the following will occur:
java.lang.IllegalArgumentException: Channel 'ChannelName' not available for adapter 'PeopleSoft'
Using the Ports Option
When you associate an event schema with an event port, you can assign only one port to a channel. The adapters do not validate the output XML published by the EIS with the schema generated for a particular event. Therefore, you must create a different channel for every event port.
J2CA Test Tool Does Not Support DBCS Input
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.
BSE Web Services Browser Pages Do Not Support DBCS Input
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.
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
The following topics discuss issues that pertain to OracleAS Adapter for PeopleSoft:
Section 12.3.1, "PeopleSoft Versions and PeopleTools Release Levels Supported"
Section 12.3.2, "PeopleSoft LDAP Authentication Incompatible"
Section 12.3.9, "Limitation When Inserting a Second Row for Level 1, 2, or 3 Scrolls"
Section 12.3.10, "Limitation when Creating a Schema for Multilevel Component Interfaces"
Section 12.3.13, "Differences Between Component Interface Functionality and Adapter Functionality"
Section 12.3.14, "Missing Field Errors When Using a Component Interface"
Section 12.3.16, "Differences Between Component Interface Functionality and Adapter Functionality"
Section 12.3.21, "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.47 |
| UNIX (HP-UX, Solaris) | Solaris | 8.1 | 8.16.03 - 8.22 |
| UNIX (HP-UX, Solaris) | Solaris | 8.4 | 8.40.05 - 8.47 |
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:
|
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 SAP.
Section 12.4.3, "Intermediate Documents (IDocs) During Inbound Processing"
Section 12.4.5, "SAP IDoc Data with Japanese DBCS Characters Overflows and Truncates Characters"
Section 12.4.6, "No Values Set for Code and Details in Binding Fault"
The following table indicates which combinations of adapter platforms, SAP releases, and APIs are supported.
| Adapter Platform | SAP R/3 Release | API |
|---|---|---|
| UNIX (HP-UX, Solaris, AIX) | SAP R/3 4.6C, 4.6D | SAP Java Connector
(SAPJCo) 2.1.6** |
| UNIX (HP-UX, Solaris, AIX) | SAP R/3 Enterprise 47x100 and 47x200* | SAP Java Connector
(SAPJCo) 2.1.6** |
*SAP R/3 Enterprise Version 47x100 and 47x200 is supported on the SAP RFC Library Versions 6.20 and 6.40.
**For the current release status of the SAP Java Connector, refer to SAP Note #549268 in the SAP Service Marketplace.
Explanation
When you use OracleAS Adapter for SAP to browse certain types of objects within the RFC, you will be unable to generate WSDL for certain RFCs in Application Explorer. This is due to the limitation enforced by jcode API, a library file provided by SAP. This limitation includes RFCs that have non-structured types in SAP (Data Elements, Domains, Built-in types).
Workaround
You can use any tool (for example, an SAP tool named WAS 6.40) to generate the WSDL from the SAP system, and then modify the WSDL to match the requirements of the Oracle environment.
Important: This workaround is only supported for release 10.1.2.0.2. It may not be supported in future releases.
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.
The following topics discuss issues that pertain to OracleAS Adapter for Siebel.
Section 12.5.2, "Additional Configuration in the Siebel Environment"
Section 12.5.4, "Unable to Connect to a Siebel Target in J2CA"
Section 12.5.5, "Unable to Connect to a Siebel Target in BSE"
Section 12.5.6, "Updating or Deleting Siebel Records Using OracleAS Adapter for Siebel"
Section 12.5.7, "Adapter Exception Error If Siebel Request Document Contains Japanese Characters"
Section 12.5.10, "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 |
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
Unable to connect to a Siebel target when using a J2CA configuration. The error message may indicate that the encoding is not supported, for example:
Error: Problem activating adapters -- UTF-8 is not supported. Check logs for more information.
Workaround
For BSE (and run-time J2CA), set the JVM encoding to ISO8859_1.
For OracleAS Adapter J2CA (design time), do the following:
Modify iwae.sh as follows:
$JAVACMD $remdbg -classpath $LOCAL_CLASSPATH -Dfile.encoding=ISO8859_1 com.ibi.bse.gui.BseFlashScreen $CLASSPATH
Log in to the Oracle Application Server console, go to the OC4J_BPEL home page, click Administration, then Server Properties, and under Command Line Options, edit the Java Options field to include the -Dfile.encoding option:
-Dfile.encoding="ISO8859_1"
Explanation
Unable to connect to a Siebel target when using a BSE configuration. The error message may indicate that the encoding is not supported, for example:
Error: Error getting target [Siebel] -- UTF-8 is not supported.
Workaround
Before attempting to connect to a Siebel target in BSE, do the following:
Add the following Java file encoding option to iwae.sh:
-Dfile.encoding="ISO8859_1"
Log in to the Oracle Application Server console, go to the OC4J_BPEL home page, click Administration, then Server Properties, and under Command Line Options, edit the Java Options field to include the -Dfile.encoding option:
-Dfile.encoding="ISO8859_1"
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.
The following topics discuss issues that pertain to OracleAS Adapter for J.D. Edwards.
The following table indicates which combinations of adapter platforms and J.D. Edwards platforms are supported, and for each combination, which J.D. Edwards products and releases are supported.
| Adapter Platform | J.D. Edwards Platform | J.D. Edwards Product and Release |
|---|---|---|
| Windows, AS400, HP 9000/B, Sun or IBM RS/6000 | Windows, AS400, HP 9000/B, Sun or IBM RS/6000 |
|
This section describes known errors in the documentation. It also identifies sections where further clarifications are necessary.
This section provides clarification to Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide.
Chapter: 2, "Configuring OracleAS Adapter for J.D. Edwards OneWorld"
Heading: "Configuring an Event Adapter"
Page: 2-19
Add the following section, titled "Initiating Events in J.D. Edwards".
Initiating Events in J.D. Edwards
During design time, create a channel and a port using Application Explorer.
Send an event from J.D. Edwards.
Capture the XML payload of the J.D. Edwards event message in the BSE log located at
OracleAS_HOME\j2ee\home\applications\ws-app-adapter\ibse\ibselogs
Create a DTD.
