|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
|
Previous |
Next |
This chapter describes issues and workarounds for the following Oracle Application Server application adapters (OracleAS adapters):
Oracle Application Server Adapter for J.D. Edwards OneWorld (OracleAS Adapter for J.D. Edwards)
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)
It 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"
The following topics discuss general issues that pertain to the Oracle Application Server adapters.
To configure the adapter, you must copy the 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.
When using a JCA implementation, you must redeploy Oracle Application Server Adapter JCA (OracleAS Adapter JCA) or restart Oracle Containers for J2EE (OC4J) to refresh the repository and see the new target in the JCA Test Servlet (the default URL is http://hostname:port/iwjcaivp) after it is created in Oracle Application Server Adapter Application Explorer (Application Explorer). This applies to OracleAS Adapter JCA only, not OracleAS Adapter Business Services Engine (BSE). It also does not affect the first target created for a given EIS. It only affects the targets created after that first one for that EIS.
After receiving an invalid request from the hub, you must restart the OracleAS Integration InterConnect EIS Adapter Plugin (EIS Adapter Plugin); otherwise subsequent requests will not go through.
When starting the EIS Adapter Plugin while OracleAS Adapter Business Services Engine (BSE) is unavailable, a ÒWhitespace requiredÓ exception error appears.
The error message "unable to connect to URL http://host:port/ibse..." will appear in the next release.
When starting OracleAS Adapter 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 the OracleAS Adapter for PeopleSoft.
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.1.603 and higher |
| UNIX (HP-UX, Solaris) | Windows, AIX, HP-UX, Linux | 8.4 | 8.40.05 and higher |
| UNIX (HP-UX, Solaris) | Solaris | 8.1 | 8.1.603 and higher |
| UNIX (HP-UX, Solaris) | Solaris | 8.4 | 8.40.05 and higher |
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 the OracleAS Adapter for PeopleSoft.
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, a Null Pointer Exception error occurs.
If you receive this error, 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, a Null Pointer Exception error occurs.
If you receive this error, 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, 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, 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
As a 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, see 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's 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. Symptoms of this behavior include errors when generating the Java APIs in the PeopleSoft Application Designer.
If you encounter errors while generating the Java APIs, 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 are fixed before continuing.
Workaround
Fix the Component Interface using PeopleTools.
Explanation
Differences between Component Interfaces and standard application behavior relating to panel processing have been observed. Among the possible symptoms of these differences are messages such as, "First Operand of . is NULL". The 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 behavior and adapter behavior, verify that the difference is 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, see PeopleSoft Resolution 200731449.
Explanation
Related display fields are not supported by Component Interfaces. PeopleSoft has acknowledged this limitation.
Workaround
For more information, see 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 behave 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 newer 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, 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, which 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 displays:
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 the OracleAS Adapter for PeopleSoft to find the component interface. This behavior 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), OracleAS Adapter Application Explorer (Application Explorer) will not recognize such names.
Workaround
Begin Component Interface names with the letters A-Z or the integers 0-9.
The following topics discuss issues that pertain to the OracleAS Adapter for SAP.
The following table indicates which combinations of adapter platforms, SAP releases, and APIs are supported.
| Adapter Platform | SAP Release | API |
|---|---|---|
| UNIX (HP-UX, Solaris) | 4.0B, 4.5B, 4.6B, 4.6C, 4.6D, 4.7 (6.20) and higher | SAP Java Connector (SAP JCo) 2.14 and higher |
Explanation
When using IDocs during inbound processing (service mode), if the DOCNUM field does not have a unique document number for each IDoc, 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 OracleAS Adapter BSE.
Workaround
For Solaris, before connecting to an SAP target in OracleAS Adapter BSE, set the environment variable LD_LIBRARY_PATH to OracleAS_home/adapters/application/lib.
For HP-UX, before connecting to an SAP target in OracleAS Adapter 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 OracleAS Adapter BSE and OracleAS Adapter JCA events and services.
Workaround
This will be fixed in a future release.
The following topics discuss issues that pertain to the OracleAS Adapter for Siebel.
Explanation
When connecting to releases prior to Siebel 7.7 using the Java Data Bean Interface, you cannot reconnect after initial connection loss. This might occur when OracleAS Adapter Application Explorer (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
Restart your application server and Application Explorer in order to log in successfully to the Siebel application. This is a known Siebel API issue. See Siebel Alert 984 for more information
Explanation
Unable to connect to a Siebel target in JCA.
Workaround
For OracleAS Adapter BSE (and runtime OracleAS Adapter JCA), set the JVM encoding to ISO8859_1.
For OracleAS Adapter JCA (design time), modify iwae.sh and Oracle Application Server as follows:
$JAVACMD $remdbg -classpath $LOCAL_CLASSPATH -Dfile.encoding=ISO8859_1 com.ibi.bse.gui.BseFlashScreen $CLASSPATH
Explanation
Unable to connect to a Siebel target in OracleAS Adapter BSE.
Workaround
Before connect to a Siebel target in OracleAS Adapter BSE, add the following Java file encoding option to iwae.sh and Oracle Application Server: -Dfile.encoding-ISO8859_1.
Explanation
An adapter exception error is returned if the Siebel request document contains Japanese characters in OracleAS Adapter JCA. The same request works in OracleAS Adapter BSE.
Workaround
This will be fixed in a future release.
This section describes known errors in the documentation.
This section describes corrections and clarifications to Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Initiating Events in J.D. Edwards"
Page: 2-20
Add the following procedure, Initiating Events in J.D. Edwards.
During design time, create a channel and a port in 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 the DTD that will be used in iStudio and OracleAS InterConnect with the XML payload in a third-party tool, such as XML Spy.
This section describes corrections and clarifications to Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Creating an Event Port"
Page: 2-16
The sentence "Application Explorer enables you to create event ports from the Adapters node or from the Events node" should read as follows: "You must create event ports from the Events node in Application Explorer". The procedure "Creating an Event Port from the Adapters Node" should be deleted.
This section describes corrections and clarifications to Oracle Application Server Adapter for PeopleSoft User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Creating an Event Port from the Adapters Node"
Page: 2-16
Steps 1 and 2 should state the following:
Right-click any node under Messages.
Select Create Event Port. You should not select Add Port.
The Create Event Port dialog opens.
This section describes corrections and clarifications to Oracle Application Server Adapter for SAP R/3 User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Creating an Event Port from the Adapters Node"
Page: 2-15
The introduction to the procedure and Steps 1 and 2 should state the following: You cannot create an event port from the Services node; you must create it from the Adapters node.
To create an event port from the Adapters node:
Right-click a node under BAPI, RFC, or IDOC.
Select Create Event Port. You should not select Add Port.
The Create Event Port dialog opens.
This section describes corrections and clarifications to Oracle Application Server Adapter for SAP R/3 User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Creating an Event Port for RMI"
Page: 2-16
In step 3c, the URL should be as follows:
rmi://host:port;RemoteObject=[APPNAME]
APPNAME must be in uppercase. It is the adapter name you configured for the EIS Adapter Plugin.
In step 3d, the table row containing the errorTo parameter and description should be deleted.
This section describes corrections and clarifications to Oracle Application Server Adapter for Siebel User's Guide.
Chapter: 2, "Adapter Configuration Using Application Explorer"
Heading: "Creating an Event Port from the Adapters Node"
Page: 2-21
Step 2 should state the following: Right-click the Integration Object event and select Add IO Node. You should not select Add Port.
Add the following as Step 3:
There are two ways to create a DTD for a Siebel event:
Right-click on the IO node under Integration Objects, and select Create Web Service. A DTD created this way will have the name of <Node_Name>_request.dtd.
Or
Right-click the IO node under Integration Objects, and select Create Event Port. A DTD created this way will have a name of <Node_Name>_event.dtd. Import the DTD with this name into iStudio.
This section describes a correction to the following books:
Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide
Oracle Application Server Adapter for PeopleSoft User's Guide
Oracle Application Server Adapter for SAP R/3 User's Guide
Oracle Application Server Adapter for Siebel User's Guide
Chapter: 4, "Examples"
Heading: "OracleAS Integration InterConnect Design Time"
The screen images depicting Oracle Application Server InterConnect reflect Release 9.0.4, but should reflect 10g Release 2 (10.1.2). The directory in which the start.bat file is located should, but does not, reflect 10g Release 2 (10.1.2) of Oracle Application Server InterConnect.
This section describes corrections and clarifications to Oracle Application Server Adapter Installation Guide.
Chapter: 2, "Installation and Configuration"
Heading: 2.2.5, "Configuring OracleAS Adapter Application Explorer
Page: 2-6
The path for iwae.sh (not ae.sh) on UNIX should be as follows:
$ORACLE_HOME/adapters/application/tools/iwae.sh
Add executable permission as follows:
chmod u+x $ORACLE_HOME/adapters/application/tools/iwae.sh
