Asset Suite / PassPortGeek

The original message published by PeopleSoft is EXAMPLE_MSG and the effective dated messsage is EXAMPLE_MSG_EFF. Add both messages to the default local node as both inbound and outbound asynchronous. You might have a hard time verifying this in the PS documentation, I know I couldn't find it.

EXAMPLE_MSG's message subscription name must end in _EFF. Example: EXAMPLE_MSG_EFF. The subscription's PeopleCode calls the Effective Date Publish utility and it removes future dated data and writes it to the effective date delay table.

Add EXAMPLE_MSG_EFF to the publish node as outbound asynchronous.

PS effective dated messages with effective date equal to current date first run their own messages subscription and then are published by the Effective Date Publish utility as an _EFF message.

Effective dated messages with effective date greater than current date first run their own message subscription and end up in delay table PS_EO_EFFDELAY.

The customized Effective Date Utility (change EOP_PUBLISHE so that the full message is published whenever a date in needed data becomes effective) processes messages from the effective date delay table, PS_EO_EFFDELAY, when the data becomes current.


TROUBLE SHOOTING


For PS 8.8, verify JOLT settings in the region's integrationgateway.properties file.
\\server\PSOFT\regiondirectory\WEBSERV\region\APPLICATIONS\PEOPLESOFT\PSIGW\WEB-INF\INTEGRATIONGATEWAY.PROPERTIES
* Lower case directories change with the PeopleSoft region.

Verify that nodes that shouldn't be active are not. These active nodes mess up PS's internal report distribution. Set PS delivered nodes PSFT_IM and PT_LOCAL to inactive.

Adding EXAMPLE_MSG's channel to a Permission List with all pages and full access will allow users with the Permission List to see the messages in Monitor Message.