9 Troubleshooting and Error Messages

This chapter explains the limitations and workarounds when connecting to PeopleSoft. It contains the following topics:

Troubleshooting
BSE Error Messages

The adapter-specific errors listed in this chapter can arise whether using the adapter with an Oracle Adapter J2CA or with an Oracle Adapter Business Services Engine (BSE) configuration.

Troubleshooting

This topic provides troubleshooting information for PeopleSoft, separated into four categories:

Application Explorer
PeopleSoft
Oracle Adapter J2CA
Oracle Adapter Business Services Engine (BSE)

Log file information that can be relevant in troubleshooting can be found in the following locations based on your adapter installation:

The Oracle Adapter J2CA trace information can be found under the following directory:

For Oracle SOA Suite:

<ORACLE_HOME>\soa\thirdparty\ApplicationAdapters\config\configuration_name\log

For OSB:

<OSB_HOME>\Oracle_OSB1\3rdparty\ApplicationAdapters\config\configuration_name\log

BSE trace information can be found under the following directory:

<ADAPTER_HOME>\user_projects\domains\base_domain\servers\soa_server1\stage\ibse\ibse.war\ibselogs

The log file for Application Explorer can be found under the following directory:

For Oracle SOA Suite:

<ORACLE_HOME>\soa\thirdparty\ApplicationAdapters\tools\iwae\bin

For OSB:

<OSB_HOME>\Oracle_OSB1\3rdparty\ApplicationAdapters\tools\iwae\bin

Application Explorer

This topic discusses the different types of errors that can occur when using Application Explorer.

Error	Solution
Cannot connect to Oracle Application Adapter for PeopleSoft from Application Explorer. The following error message appears: `Problem activating adapter`	Ensure that: PeopleSoft is running. The PeopleSoft user ID and password are correct. The port number is correct. The custom component interface is properly installed.
The following error message appears: java.lang.IllegalStateException: java.lang.Exception: Error Logon to PeopleSoft System	You have provided invalid connection information for PeopleSoft or the wrong `psjoa.jar` is in the lib directory. The `psjoa.jar` file version is specific to the PeopleTools release.
PeopleSoft does not appear in the Application Explorer Adapter node list.	Ensure that the PeopleSoft JAR files, `iwpsci84.jar` (or iwpsci81.jar) and `psjoa.jar,` are added to the `lib` directory.
Logon failure error at run-time.	If the password for connecting to your PeopleSoft system is not specified when creating a target or with the Edit option in Application Explorer, you will be unable to connect to PeopleSoft. The connection password is not saved in `repository.xml`. Update the password using the Edit option in Application Explorer, then restart the application server.
The following error message appears: Jolt Session Pool cannot provide a connection to the appserver. This appears to be because there is no available application server domain. [Fri Aug 27 13:06:27 EDT 2004] bea.jolt.ServiceException: Invalid Session	The host name or port number for PeopleSoft is incorrect.
Properties are not displayed for a component interface.	You are using the wrong `iwpsci8x.jar` file.
Cannot generate schemas.	If the error message “Index: -1, Size:0” appears, or if you can log on to Application Explorer but you cannot see any Component Interfaces or Messages, then you may have both the `iwpsci81.jar` and `iwpsci84.jar` files in your `lib` directory. Stop your server, remove the unrequired jar file, and restart the server.
The following exception occurs when you start Application Explorer by activating `ae.bat` (not `iaexplorer.exe`): `java.lang.ClassNotFoundException: org.bouncycastle.jce.provider.BouncyCastleProvider`	This is a benign exception. It does not affect adapter functionality. Download BouncyCastle files from: `ftp://ftp.bouncycastle.org/pub`
Unable to start Application Explorer in a Solaris environment. The following exception is thrown in the console: `javax.resource.ResourceException: IWAFManagedConnectionFactory: License violation.at com.ibi.afjca.spi.IWAFManagedConnectionFactory.createConnectionFactory(IWAFManagedConnectionFactory.java:98)at com.iwaysoftware.iwae.common.JCATransport.getConnectionFactory(JCATransport.java:133)` `at com.iwaysoftware.iwae.common.JCATransport.initJCA(JCATransport.java:69)at com.iwaysoftware.iwae.common.JCATransport.<init>(JCATransport.java:62)at com.iwaysoftware.iwae.common.AdapterClient.<init>(AdapterClient.java:85)at com.ibi.bse.ConfigWorker.run(ConfigWorker.java:41)at java.lang.Thread.run(Thread.java:534)` `Could not create the connection factory.`	`JAVACMD` is not set on the user system. Before starting Application Explorer, export `JAVACMD` as follows: `JAVACMD=/<jdk_home>/bin/java`, where `<jdk_home>` is the directory where JDK is installed on your system.

PeopleSoft

Error	Solution
Services are not working properly when using the PeopleSoft Component Interface testing tool in three-tier mode.	To test properly using the Component Interface testing tool: Open Application Designer. Select the Component Interface. Use the test tool. If service works in test tool, then review the XML and check for redundant fields in XML.
The following error message appears: `Jolt Session Pool cannot provide a connection to the appserver. This appears to be because there is no available application server domain. [Fri Aug 27 13:06:27 EDT 2004] bea.jolt.ServiceException: Invalid Session`	The host name or port number for PeopleSoft is incorrect.
Component Interfaces and Messages do not appear in the adapter tree.	The project is not installed properly on the PeopleSoft system.
Return error code `-1` is received from PeopleSoft at run-time, for example: `<LOCATIONProcessResponse xmlns="http://xmlns.oracle.com/LOCATION">` `<error xmlns="">-1</error>` `</LOCATIONProcessResponse>`	You are either using the incorrect version of `psjoa.jar`, or have both the `iwpsci81.jar` and `iwpsci84.jar` files in your `lib` directory. In the second case, you must delete the unused JAR file, and then restart the server. The `psjoa.jar` file version is specific to the PeopleTools release.
Pstools.properties file has not been initialized.	This file is required for PeopleSoft 8.1. If you are using PeopleSoft 8.1, you should add this file. If you are not using PeopleSoft 8.1 and this error message still appears, ignore the message.
The following error message appears: `Cannot find Component Interface {CI name}`	The reason may be either of the following: The Java API for the selected component interface is not found in the API JAR file. Please check the Java API for the class file for the CI. If not found, please add the class file for the CI. The component interface name is mentioned incorrectly in the request document.
The following error message appears: `Not Authorized (90,6) Failed to execute PSSession request`	The component interface does not have the necessary access to perform the operation. Change the permission settings in the PeopleSoft > Security > Permission list for the component interface.
The following error message appears: `Must also provide values for keys {keyname}`	The reason may be any of the following: The request XML document does not have the element for the mandatory key. Please include the keyname and the value in the request document. The Key field name is mentioned incorrectly in the request document. The Perform operation is mentioned incorrectly in the request XML document.

Oracle Adapter J2CA

Error	Solution
In Application Explorer, the following error message appears when you attempt to connect to an Oracle Adapter J2CA configuration: `Could not initialize JCA`	In the Details tab in the right pane, ensure that the directory specified in the Home field points to the correct directory, for example: `<ADAPTER_HOME>`\soa\thirdparty\ApplicationAdapters\tools\iwae\bin\..\..\..\

BSE Error Messages

This topic discusses the different types of errors that can occur when processing Web services through Oracle WebLogic Server Adapter Business Services Engine (BSE).

General Error Handling in BSE

BSE serves as both a SOAP gateway into the adapter framework and as the engine for some of the adapters. In both design time and run-time, various conditions can cause errors in BSE when Web services that use adapters run. Some of these conditions and resulting errors are exposed the same way, regardless of the specific adapter; others are exposed differently, based on the adapter being used. This topic explains what you can expect when you encounter some of the more common error conditions on an adapter-specific basis.Usually, the SOAP gateway (agent) inside BSE passes a SOAP request message to the adapter required for the Web service. If an error occurs, how it is exposed depends on the adapter and the API or interfaces that the adapter uses. The APIs are generated from PeopleTools and are specific to the PeopleTools release. A few scenarios cause the SOAP gateway to generate a SOAP fault. In general, anytime the SOAP agent inside BSE receives an invalid SOAP request, a SOAP fault element is generated in the SOAP response. The SOAP fault element contains fault string and fault code elements. The fault code contains a description of the SOAP agent error.The following SOAP response document results when BSE receives an invalid SOAP request:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">  
 <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Client</faultcode>
         <faultstring>Parameter node is missing</faultstring>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

In this example, BSE did not receive an element in the SOAP request message that is mandatory for the WSDL for this Web service.

Adapter-Specific Error Handling

When an adapter raises an exception during run-time, the SOAP agent in BSE produces a SOAP fault element in the generated SOAP response. The SOAP fault element contains fault code and fault string elements. The fault string contains the native error description from the adapter target system. Since adapters use the target system interfaces and APIs, whether an exception is raised depends on how the target systems interface or API treats the error condition. If a SOAP request message is passed to an adapter by the SOAP agent in BSE, and that request is invalid based on the WSDL for that service, the adapter may raise an exception yielding a SOAP fault. While it is almost impossible to anticipate every error condition that an adapter may encounter, the following is a description of how adapters handle common error conditions and how they are then exposed to the Web services consumer application.

Oracle Application Adapter for PeopleSoft Invalid SOAP Request

If the PeopleSoft agent receives a SOAP request message that does not conform to the WSDL for the Web service being executed, then the following SOAP response is generated.

<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
  <SOAP-ENV:Body>
   <m:CARRIERResponse xmlns:m="urn:schemas-iwaysoftware-com:iwse"
   xmlns="urn:schemas-iwaysoftware-com:iwse"
   cid="2A3CB42703EB20203F91951B89F3C5AF">
   <PS8> 
      <error>Cannot find Component Interface {VARRIER}    (91,2)Initialization
    failed (90,7)Not Authorized (90,6)Failed to execute PSSession request Cannot find Component Interface {VARRIER} (91,2)</error> 
        </PS8>
      </m:CARRIERResponse>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Empty Result From PeopleSoft Request

If Oracle Application Adapter for PeopleSoft executes a component interface as a Web service using input parameters passed in the SOAP request that do not match records in PeopleSoft, then the following SOAP response is generated.

<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
 <SOAP-ENV:Body>
  <m:CARRIERResponse xmlns:m="urn:schemas-iwaysoftware-com:iwse" 
xmlns="urn:schemas-iwaysoftware-com:iwse" cid="2A3CB42703EB20203F91951B89F3C5AF">
    <PS8>
        <error>No rows exist for the specified keys. {CARRIER} (91,50)Failed to execute PSBusComp request</error>
    </PS8>
  </m:CARRIERResponse>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Failure to Connect to PeopleSoft

If Oracle Application Adapter for PeopleSoft cannot connect to PeopleSoft, then the following SOAP response is generated.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
  <SOAP-ENV:Fault>
   <faultcode>SOAP-ENV:Server</faultcode>
  <faultstring>java.lang.Exception: Error Logon to PeopleSoft 
   System<faultstring>
 </SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Invalid SOAP Request

If Oracle WebLogic Server Application Adapter receives a SOAP request message that does not conform to the WSDL for the Web services being executed, then the following SOAP response is generated.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
 <SOAP-ENV:Fault>
  <faultcode>SOAP-ENV:Server</faultcode>
  <faultstring>RPC server connection failed: Connection refused: connect</faultstring>
 </SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Empty Result From Oracle WebLogic Server Application Adapter Request

If the adapter executes a SOAP request using input parameters passed that do not match records in the target system, then the following SOAP response is generated.

Note:

The condition for this adapter does not yield a SOAP fault.

<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
   <SOAP-ENV:Body>
      <m:RunDBQueryResponse xmlns:m="urn:schemas-iwaysoftware-com:iwse"
        xmlns="urn:schemas-iwaysoftware-com:iwse"
        cid="2A3CB42703EB20203F91951B89F3C5AF">
        <RunDBQueryResult run="1" />
     </m:RunDBQueryResponse>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>