Handling Common Issues

Use this table to handle common issues in PeopleSoft Integration Broker:

Area or Suspected Issue Debugging Suggestion

Application server exceptions.

Check the application server log:

<PS_CFG_HOME>\appserv\<Domain>\LOGS\ appsrv.log

Message handlers are not running.

Check the application server domain status or queue status in the PeopleSoft Application Server Administration menu (PSAdmin). Select Domain Status, Server Status or Domain Status, Queue Status.

Integration gateway.

Check the integrationGateway.properties file and verify the property settings.

The default file location is <PIA_HOME>\webserv\<DOMAIN>\applications\peoplesoft\PSIGW.war.war\WEB-INF\integrationGateway.properties.

Integration gateway.

Check the integration gateway message log.

The default file location is <PIA_HOME>\webserv\<DOMAIN>\applications\peoplesoft\PSIGW.war.war\msgLog.html.

Queues are paused.

Check the Service Operations Monitor. Select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Administration, and then Queue Status.

A node is paused.

Check the Service Operations Monitor. Select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Administration, and then Node Status.

Incorrect gateway uniform resource locator (URL).

Check the Gateways component to verify that the integration gateway URL is correct. Select PeopleTools, and then Integration Broker, and then Configuration, and then Integration Gateways.

Node inactive.

Check the node definition. Select PeopleTools, and then Integration Broker, and then Integration Setup, and then Node Definitions.

Subscription PeopleCode is missing or incorrect.

Check the Service Operations Monitor. Select PeopleTools, and then Integration Broker, and then Monitoring, and then Monitor Asynchronous Services, and then Subscription Contracts.

A service operation is inactive.

Check the service operation definition in the PeopleSoft Pure Internet Architecture. Select PeopleTools, and then Integration Broker, and then Integration Setup, and then Service Operation Definitions.

There are transform problems.

  • Check the Application Engine object in PeopleSoft Application Designer.

  • For before and after images, check the Service Operations Monitor.

    For asynchronous service operations, select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Monitoring, and then View Asynchronous Details. Click the View XML link for the publication contract or subscription contract.

    For synchronous service operations, select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Monitoring, and then View Synchronous Details. Use the Log Type drop-down list box to select Request Transformed or Response Transformed, and then click View XML.

  • Verify that the TraceAE flag in the following directory equals 8192:

    <PS_CFG_HOME>\appserv\<Domain>\psappsrv.cfg

    Setting the TraceAE flag in the psappsrv.cfg file instructs the application server to generate a transformation trace log with the .aet extension, written to the following directory:

    <PS_CFG_HOME>\appserv\<Domain>\LOGS\ <operID>_<machine name>.AET

    The log file contains:

    • The original XML structure as it entered the transformation engine.

    • The output of the XML as it passed through each step of the transform program.

Integration Broker security

Set the application server logging level to 4 or greater to capture information related to the following situations:

  • No routing at source node.

  • No routing at target node.

  • User invoking a service operation has different permissions than specified on the service operation on the source node.

  • No node password found on source node.

  • No node password found on target node.

  • Mismatched node password on source and target nodes.

  • No permissions set for the service operation on the source node.