Integration Broker logging can be very useful for troubleshooting messaging issues.

 

Integration Broker logging can be very useful for troubleshooting messaging issues. It can be enabled through:

PeopleTools > Integration Broker > Configuration > Gateways.

Open your local Gateway (usually called LOCAL) and click on the Gateway Setup Properties.

Login to the gateway properties using the default user ID and password (they are provided on the page). You may need to ask your system administrator for the appropriate credentials if the default values do not work.

Once you login, click on the Advanced Properties Page link. This will open the integrationGateway.properties file and allow you to edit it.

Scroll through the integrationGateway.properties file until you find the logging section. The following line is what sets the logging level (2 is the default):

ig.log.level=2

The logging levels are:

Level	Value
-100	Suppress any logging
-1	Language Exception
1	Standard Gateway Exception
2	Errors and Warnings
3	Important information, errors and warnings
4	Standard and important information, errors and warnings
5	Low importance, standard, and important information, errors and warnings

The default log level of 2 should be sufficient for troubleshooting. Remember with logging less is more. It is easier to dig deeper once you've found the relevant issue rather than creating a haystock of log output.

 

You can view the message and error logs using your browsing by pointing to:

·        https://server:port/PSIGW/msgLog.html for the message log

·        https://server:port/PSIGW/errorLog.html for the error log

If you are having trouble determining the URL for these, look at your local gateway URL or ping it and use the same URL up to the PSIGW/ and then enter the appropriate message log page name.

NOTE: the names of the HTML files are case sensitive! So errorlog.html may not work while errorLog.html (capital L in log) will work.

If there have been no messages or errors logged then these files won't exist. Their locations/names may also have been changed in the integrationGateway.propertie file.

Check the values of:

·        ig.messageLog.filename

·        ig.errorLog.filename

 

 The application server logs (APPSRV_MMDD.LOG) was slighty more informative, giving the following messages:

1. Error in service HomepageT, CREF with URL can not be found:

2. http://webserver.com:8000/psp/ps/EMPLOYEE/HRMS/?tab=DEFAULT

3. Failed to execute HomepageTemplate request 

4. Service HomepageT failed

Turns out, that the HRMS node had been made inactive. This was the node being used by the EMPLOYEE portal for HRMS/Campus Solutions, so it needed to be active. You can check the nodes being used by looking at the PORTAL_HOSTNODENAM field in PSPRDMDEFN.

Updating the node to active, by setting ACTIVE_NODE = 1 in PSMSGNODEDEFN for the HRMS node, stopping the application server, physically deleting the cache files, and restarting the application server resolved the issue.