Avoiding Messaging Errors

Review your security settings. This helps you avoid situations in which a published message remains in New status rather than completing its path and changing status to Done, or in which the message does not appear in the Service Operation Monitor after the process to generate it is complete.

To check security settings:

  1. Navigate to PeopleTools, and then Security, and then Permissions & Roles, and then Permission Lists.

  2. Enter a Permission List value.

  3. Select the Service Operations Monitor tab.

  4. Determine whether the channel(s) appear there.

  5. If the channels do not appear, enter HR_SETUP and STUDENT_ADMIN_ACCOUNTING in the Channel Name fields.

  6. Based on your security business rules, select Full or Read Only access for each channel.

  7. Save the changes.

    You can now return to the Service Operation Monitor and search for a particular message/channel.

Verify your channel settings in Application Designer. Verify these items in both the Contributor Relations and Financials databases. The following tips apply to the messages BUS_UNIT_AV_FULLSYNC, BUS_UNIT_AV_SYNC, and STUDENT_ADV_ACCTG_LINE:

  • Open the Message Definition, go to Message Properties, make sure that the Active Status check box is selected.

  • Make sure that the correct Queue is specified for the Message Definition (that is, HR_SETUP channel is for the business unit messages and STUDENT_ADMIN_ACCOUNTING channel is for the accounting line message).

  • In Service Operation Monitor, check the Channel Status tab. The channel status must be Running.

  • Message Nodes are set up correctly, including the correct Location/URL.

Verify your message definition settings in Application Designer. Verify statuses for the Contributor Relations message subscription STUDENT_ADV_ACCTG_LINE and the Financials 8.4 or 8.8 message subscriptions BusUnitAVFullSync, BusUnitAVSync, and StudentAdvancementAcctgLine.

To verify status:

  1. Open the Message Definition, then the Message.

  2. Right-click the Message Subscription.

  3. Make sure the Active Status check box is selected.

Ping the publishing and subscribing database nodes.

To ping a database node:

  1. Sign on to the Contributor Relations database.

  2. Navigate to PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Administration, and then Node Status.

  3. Enter the Message Node Name.

  4. Click the Ping Node button.

  5. If the node does not ping successfully, the gateway is bad; check the Node and Node URL.

  6. If the node pings successfully, sign on to the Financials database and ping the Contributor Relations database node using Integration Broker.

    See PeopleTools: Integration Broker.

If changes are made to Queues and/or Message Nodes, it is a good idea to stop and then start the Application Server. You can also delete the Application Server cache.