5 Troubleshooting and Error Messages

This chapter explains the limitations and workarounds when connecting to PeopleSoft. The following topics are discussed:

Troubleshooting
BSE Error Messages

The adapter-specific errors listed in this chapter can arise whether using the adapter with an OracleAS Adapter JCA or with a BSE configuration.

Troubleshooting

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

Application Explorer
PeopleSoft
OracleAS Adapter JCA
BSE

Note:

Log file information that can be relevant in troubleshooting can be found in the following locations:

The OracleAS Adapter JCA trace information can be found under the OracleAS_home\opmn\logs directory.
BSE trace information can be found under the OracleAS_home\j2ee\home\applications\ws-app-adapter\ibse\ibselogs directory.
The log file for Application Explorer can be found under the OracleAS_home\adapters\application\tools directory.

Application Explorer

To use Application Explorer on Windows for debugging or testing purposes, invoke the ae batch script, ae.bat, found under OracleAS_home\adapters\application\tools or on UNIX invoke the ae script, ae.sh, found under OracleAS_home/adapters/application/tools.

Error	Solution
Cannot connect to the OracleAS Adapter for PeopleSoft from Application Explorer.	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.
PeopleSoft does not appear in the Application Explorer Adapter node list.	Ensure that the PeopleSoft JAR files, `iwpsci84.jar` and `psjoa.jar,` are added to the lib directory.
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.

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.

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.

OracleAS Adapter JCA

Error	Solution
In Application Explorer, the following error message appears when you attempt to connect to an OracleAS Adapter JCA 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, `OracleAS_home`\adapters\application

BSE Error Messages

This topic discusses the different types of errors that can occur when processing Web services through Oracle Application 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 execution time, various conditions can cause errors in BSE when Web services that use adapters are running. 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. 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 execution, 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 or not 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 Server Adapter for PeopleSoft Invalid SOAP Request

When the PeopleSoft agent receives a SOAP request message that does not conform to the WSDL for the Web service being executed, 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

When the OracleAS 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, 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

When the OracleAS Adapter for PeopleSoft cannot connect to PeopleSoft, 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

When the Oracle Application Server Adapter receives a SOAP request message that does not conform to the WSDL for the Web services being executed, 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 Application Server Adapter Request

When the adapter executes a SOAP request using input parameters passed that do not match records in the target system, 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>