Asset Suite / PassPortGeek

Go to the Message Monitor Overview via PeopleTools > Integration Broker > Monitor - Monitor Message - Overview tab. Filter with Publish Node blank, Last 1 Days, Archived blank, Queue Type is Message Instance, and Group By Channel.

Does the message's Channel Name appear?

If not, does the value for the Last filter go back far enough? Note that "1 Days" is 24 hours. If the message still doesn't appear, it's probably a setup issue.

The message should appear in the Contracts Created link. If the message is not in Contracts Created, for example it's in New or Started and stays in New or Started for several minutes, it's probably a setup issue.

If the message is in New or Started and stays there for several minutes, it's an indication that the pub/sub dispatcher processes have stopped functioning correctly. Bounce the pub/sub dispatcher processes. The dispatcher processes will stop working properly if they loose their database connections. They differ from other PS processes in that they do not survive a database bounce.

Check message coming into PeopleSoft, that is, PS is subscribing to the message.

Go to PeopleTools > Integration Broker > Monitor - Monitor Message, Sub Contracts tab. Filter with Publish Node blank, Last 1 Days, Archived blank, Channel Name being the message's channel, Status blank, Message Name blank.

Click the Pub ID column header to sort data in processed order.

Is the message's key data in Result, column Sub Channel? If not, check that the value for Last goes back far enough and that Status is blank. If the message does not appear, check the publishing application for errors, or there might be a setup issue.

Drill into the message status by sliding right and clicking the Details link.

In Subscription Contracts, is Status = Done? If so, the message should have processed OK. Is Status = Error? Click the Message Errors. A meaningful message (assuming you're a PeopleSoftGeek) should appear. "Not Authorized" means the user ID used by the application server to connect to the database does not have full access to Component Interfaces.

If you're able to resolve the problem, the message can be resubmitted via the Message Details tab and the Resubmit button.

Completely off the wall messages might be an indication that bad data is being passed and tighter checks need to be implemented.

Check published messages, that is, outgoing from PeopleSoft

Go to PeopleTools > Integration Broker > Monitor - Monitor Message, Message Instances tab. Filter with Publish Node blank, Last 1 Days, Archived blank, Channel Name being the message's channel, Status blank, Message Name blank.

Click the Pub ID column to sort in processed order.

Most likely messages are being published utilizing the Effective Date Publish Utility, so there should be two messages with equivalent values in Sub Channel. There are 2 messages because the first message is published to PeopleSoft itself, The _EFF message subscribes to the first message to check it for effective dating and if it is effective, the _EFF message is published to the target node. Data superseded by effective date or future effective dated is not published at this time.

PeopleSoft ver 8.8 was still using Web Logic. If there is no sign of the messages, check out the Tuxedo Web Logic logs. You're going to need access to the web server. The logs will look like ../APPLICATIONS/PEOPLESOFT/PSIGW/ERRORLOG.HTML.