|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25335-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25335-01 |
|
|
Previous |
Next |
This chapter describes issues and workarounds for Oracle Application Server packaged-application and legacy adapters.
It includes the following topics:
Section 11.1, "Packaged-Application Adapters: General Issues and Workarounds"
Section 11.2, "OracleAS Adapter for PeopleSoft: Issues and Workarounds"
Section 11.3, "OracleAS Adapter for SAP: Issues and Workarounds"
Section 11.4, "OracleAS Adapter for Siebel: Issues and Workarounds"
Section 11.5, "OracleAS Adapter for J.D. Edwards OneWorld: Issues and Workarounds"
The following topics discuss general issues that pertain to the Oracle Application Server adapters for packaged applications:
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.
When using a J2CA implementation, you must redeploy Oracle Application Server Adapter J2CA (OracleAS Adapter J2CA) or restart Oracle Containers for J2EE (OC4J) to refresh the repository and see the new target in the J2CA 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 J2CA 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.
When starting the EIS Adapter Plugin while BSE is unavailable, a "Whitespace required" exception error appears.
The error message "unable to connect to URL http://host:port/ibse..." appears.
When invoking a runtime message while BSE is unavailable, a "Whitespace required" exception error appears.
The error message "unable to connect to URL http://host:port/ibse..." appears.
When invoking an outbound BPEL process at runtime using BSE, a "Not able to find SoapRouter" message appears.
To solve this problem, add the following element in the respective bpel.xml file:
<property name "optSoapShortcut">false</property>
The following topics discuss issues that pertain to OracleAS Adapter for PeopleSoft:
Section 11.2.1, "PeopleSoft Versions and PeopleTools Release Levels Supported"
Section 11.2.2, "PeopleSoft LDAP Authentication Incompatible"
Section 11.2.6, "Limitation When Inserting a Second Row for Level 1, 2, or 3 Scrolls"
Section 11.2.7, "Limitation when Creating a Schema for Multilevel Component Interfaces"
Section 11.2.10, "Differences Between Component Interface Behavior and Adapter Behavior"
Section 11.2.11, "Missing Field Errors When Using a Component Interface"
Section 11.2.13, "Differences Between Component Interface Behavior and Adapter Behavior"
Section 11.2.18, "Component Interface Java API Compilation Errors (People Tools 8.46)"
Section 11.2.19, "Invalid Response While Querying Nonexisting Account"
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 |
|---|---|---|---|
| Windows | Windows | 8.1 | 8.1.603 and higher |
| Windows | Windows | 8.4 | 8.40.05 and higher |
| Windows | Solaris | 8.1 | 8.1.603 and higher |
| Windows | Solaris | 8.4 | 8.40.05 and higher |
| Windows | AIX | 8.1 | 8.1.603 and higher |
| Windows | AIX | 8.4 | 8.40.05 and higher |
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. There is no workaround available at present.
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. There is no workaround available at present.
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). There is no workaround available at present.
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. There is no workaround available at present.
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.
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.
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.
As a workaround, retain the iwpsci84.jar file and delete the iwpsci81.jar file from the OracleAS_home \adapters\application\lib directory.
|
See Also:
|
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.
To workaround this problem, 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.
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 is fixed before continuing.
To solve this error, fix the Component Interface using PeopleTools.
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". 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.
To workaround this problem, test the Component Interface using the PeopleTools Component Interface testing tool in three-tier mode only.
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.
To avoid this error, 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.
Related display fields are not supported by Component Interfaces. PeopleSoft has acknowledged this limitation.
For more information, see PeopleSoft Resolution 200731974, which offers several workarounds.
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.
The workaround is dependent on the Component Interface.
A failure occurs when inserting multiple effective dated rows.
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.
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.
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.
To workaround this problem, 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 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.
Although PeopleSoft permits Component Interface names that begin with certain special characters (such as an underscore), Application Explorer does not recognize such names.
Begin Component Interface names with the letters A-Z or the integers 0-9.
When you compile all Java APIs for the Component Interfaces using People Tools 8.46, you may encounter compilation errors with some of the CIs.
You can manually correct the Java source code of the failing CIs. Alternatively, if the failing CIs are not going to be used, 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 11.3.1, "OracleAS Adapter for SAP Version and API Information"
Section 11.3.4, "SAP IDOC Data with Japanese DBCS Characters Overflows and Truncates Characters"
Section 11.3.5, "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 Release | API |
|---|---|---|
| Windows | 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 |
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.
Do not change the columns in a table used by an Oracle Database adapter interaction after deployment.
You do not have the MSVC 7.0 (MS Visual Studio 2003) runtime component DLLs with the following components:
SAPJCO 2.14
RFC library 6.40
You must download and install the file msdlls.zip with the sapjco214, and then execute R3DLLINS.EXE.
However, customers must download the SAP note 684106 attachment R3DLLINST.SAR and unpack it with the SAPCAR.EXE shipped with SAP 6.40 RFC library. The command sequence is: "SAPCAR -xvf R3DLLINST.SAR. "
SAP IDOC data with Japanese DBCS characters overflows and truncates characters in all BSE and OracleAS Adapter J2CA events and services.
This will be fixed in a future release.
If you use the wrong request XML to invoke a SAP outbound process in Oracle BPEL Console, 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. There is no workaround available for this problem.
The following topics discuss issues that pertain to OracleAS Adapter for Siebel.
Section 11.4.2, "Adapter Exception Error If Siebel Request Document Contains Japanese Characters"
Section 11.4.3, "Invalid Response While Querying Nonexisting Account"
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 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.
To log in successfully to the Siebel application, restart your application server and Application Explorer. This is a known Siebel API issue. See Siebel Alert 984 for more information
An adapter exception error is returned if the Siebel request document contains Japanese characters in OracleAS Adapter J2CA. The same request works in BSE.
This will be fixed in a future release.
The following topics discuss issues that pertain to OracleAS Adapter for J.D. Edwards OneWorld:
This section discusses the workarounds and issues that pertain to the following OracleAS adapters for legacy applications:
OracleAS Adapter for Tuxedo
OracleAS Adapter for CICS
OracleAS Adapter for VSAM
OracleAS Adapter for IMS/TM
OracleAS Adapter for IMS/DB
When connecting to multiple legacy systems without providing any password or trying anonymous access, you cannot specify the values for legacy systems in any order. For example, you may need to connect to two legacy systems with the following configuration:
mvs08, 2554, demo, use4demo
localhost, 2551, (anonymous access without specifying the username and password)
In such a scenario, you cannot specify values for the properties in the following order:
| Property | Order of Values Not Accepted |
|---|---|
LegacyServer
|
localhost, mvs08
|
LegacyPort
|
2551,2554
|
LegacyUser
|
,demo
|
LegacyUserCredential
|
,use4demo
|
If the value for the user or password field is null, then it should be specified as null in the collaxa-config.xml file. For example, you can specify the values in the order shown in the following table:
| Property | Values listed in Acceptable Order |
|---|---|
LegacyServer
|
localhost, mvs08
|
LegacyPort
|
2551,2554
|
LegacyUser
|
null,demo
|
LegacyUserCredential
|
null,use4demo
|
This section describes known errors in the documentation. It also identifies sections where further clarifications are necessary:
This section describes clarifications to Oracle Application Server Adapter for J.D. Edwards OneWorld User's Guide.
On page 2-22, 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 a DTD.
This section describes clarifications to Oracle Application Server Adapter for Siebel User's Guide.
On page 5-2, add the following additional explanation after step 7:
For Siebel 7.5 and higher: Generate XSD schemas directly from Siebel tools. These XSD schemas are used to create Web services directly using Application Explorer. After you generate an XSD schema through Siebel tools, use it to create an IO node and Web service.
For Siebel 7.0: You cannot generate XSD schemas directly from Siebel tools; only XDR schemas can be created. Therefore, to create a Web service, Application Explorer must first generate an XSD schema from the XDR schema.
|
Note: This clarification also applies to the equivalent section in Chapter 6, "InterConnect Integration Examples", on page 6-2. |
