APP_MSG_ADMINISTRATOR for Integration Broker batch error notifications

Open the Role APP_MSG_ADMINISTRATOR
Go to Workflow tab and remove the associated Rolequery and deselect 'Use Query to Route Workflow' check box. Save.
Attach this role to appropriate user profiles.
Note 1 :
App engine can be run from:
PeopleTools>Integration Broker>Service Operations Monitor>Monitoring>Asynchronous Details
Note 2 :
If there are any messages in either Error or Timeout status, then the app engine PT_AMM_WF sends the notification to the users with APP_MSG_ADMINISTRATOR role . App engine calls a CI based on a dummy component which in turn triggers the traditional workflow event.
Delivered Role APP_MSG_ADMINISTRATOR filters the list of users to be notified based on a role query.
We need to make the Role APP_MSG_ADMINISTRATOR to be the static role to make sure only appropriate users get notified.
The app engine could be scheduled to run at a desired frequency on proc server.

Subscription Process Problems

Possible subscription process problems include:


Subscription contract is not created.
Subscription contract is in NEW status.
Subscription contract is in STARTED status.
Subscription contract is in WORKING status.
Subscription contract is in ERROR status.
Subscription contract is in EDIT status.

Sub Contract Is not Created
No handler exists for the service operation.
Service operation handler is missing method.
Queue routing rules not set up properly.

Sub Contract Is in NEW Status
Application Server down.
Pub/Sub processes not configured on Application Server domain.
The Subscription Dispatcher has crashed or has been brought down.
Receiving queue is paused.
Receiving node is paused.
Previous service operation had errors or timed out.
No row was inserted into PSAPMSGSUBPRCID, To insert a row enter the following SQL statement in your Query tool use the following statement:
insert into PSAPMSGSUBPRCID values(0) Sub Contract Is in STARTED Status
Subscription Handler is down.
Target component is not valid.

Sub Contract Is in WORKING Status
Subscription Handler crashed while processing message.

Sub Contract Is in ERROR Status
Queue property if Ordered enables subscription contracts to go in random order, which causes FULLSYNC service operations to error out when the transaction is subscribed before the header.
Service operation handler PeopleCode errors exist.
Application data errors exist.

Sub Contract Is in EDIT Status
Possible cause is that the XML was edited and is not yet resubmitted for processing.

Unable to find a Routing corresponding to the incoming request message

Unable to find a Routing corresponding to the incoming request message

You are sending an async service operation from node A to target node B. The nodes are pingable. The routing on target database and source database exist and are correct. The same service operation works fine if you use and “ANY TO LOCAL” routing.

The “ANY TO LOCAL” routing type uses a virtual node ANY when node passwords fail and eliminates node authentication from the equation. If “ANY TO LOCAL” works, but a standard point to point routing fails, reset the node authentication option to NONE rather than password and try again. If this works, then the node passwords were incorrect. Resetting these should resolve the problem.

Note: You can also see this error if the Message name does not match the externalservice operation name. They have to Match.

Publication Process Problems

Publication Process Problems
Possible publication process problems include:


Publication contract is not created.
Publication contract is in NEW status.
Publication contract stays in RETRY status.
Publication contract is in WORKING status.
Publication contract is in TIMEOUT status.
Publication contract is in ERROR status.
Pub Contract Is Not Created
No publication PeopleCode exists.
Publication PeopleCode is incorrect.
No outbound routings exists for the service operation.

Pub Contract Is in NEW Status
Sending queue is paused.
Publication Dispatcher crashed or was brought down.
Sending node is paused.
Previous service operation had a status of Retry, Error, or Timeout.
Sending domain is not active.
After an unsuccessful ping, a row may be added to the table PSNODESDOWN; which will hold up the message queue; query the table PSNODESDOWN.

Pub Contract Stays in RETRY Status
The remote node cannot be pinged successfully; the publication contract will be processed when the remote node comes back up.
No publication handler is available, either because it crashed or it was brought down.
Receiving Node URL is incorrect in integrationGateway.properties file.

Pub Contract Is in WORKING Status
The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
Single threading on the application server is slowing processing.

Pub Contract Is in TIMEOUT Status
An exception occurred on the target application server (look in APPSRV.LOG file for details); verify that:
The reply is incorrectly routed; check Gateway for correct machine address of target node.
Bad XML syntax.

Pub Contract Is in ERROR Status
Receiving node user profile not authorized to service operation.
Inbound routing is not set up on the receiving system.
Service operation is not active on the receiving system.
Service operation has not been granted security access on the receiving system.
The source node is not defined in the target database.
Handler PeopleCode is bad.
Remote application server is down.
Receiving Node is not defined in the integrationGateway.properties file.
Receiving PeopleSoft node has not been added to single signon.
Service operation version on target is not active.