Oracle® Fusion Middleware Application Adapter for PeopleSoft User's Guide for Oracle WebLogic Server 11g Release 1 (11.1.1) Part Number E17055-01 |
|
|
View PDF |
This chapter explains the limitations and workarounds when connecting to PeopleSoft. The following topics are discussed:
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.
This topic provides troubleshooting information for PeopleSoft, separated into four categories:
Application Explorer
PeopleSoft
Oracle Adapter J2CA
Oracle Adapter Business Services Engine (BSE)
Note:
Log file information that can be relevant in troubleshooting can be found in the following locations:The Oracle Adapter J2CA trace information can be found under the following directory:
C:\oracle\Middleware\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\config\config_name\log
BSE trace information can be found under the following directory:
C:\oracle\Middleware\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:
C:\oracle\Middleware\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\tools\iwae\bin
Application Explorer
To use Application Explorer on Windows for debugging or testing purposes:
Ensure that Oracle WebLogic Server is started, which is where Application Explorer is deployed.
Start Application Explorer by clicking the Windows Start menu, selecting All Programs, Oracle Application Adapters, and clicking Application Explorer.
You can also start Application Explorer by executing the ae.bat file, which is located in the following directory:
C:\oracle\Middleware\home_0309\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\tools\iwae\bin\ae.bat
It is a good practice to create a shortcut for the ae.bat file on your desktop.
If you are using a UNIX or Linux platform you can start Application Explorer by executing the iwae.sh file.
PeopleSoft
Oracle Adapter J2CA
Error | Solution |
---|---|
In Application Explorer, the following error message appears when you attempt to connect to an Oracle Adapter J2CA configuration: | In the Details tab in the right pane, ensure that the directory specified in the Home field points to the correct directory, for example:
C:\oracle\Middleware\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\tools\iwae\bin\..\..\..\ |
This topic discusses the different types of errors that can occur when processing Web services through Oracle WebLogic Server Adapter Business Services Engine (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.
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>