Business Process Automation

Message Hub Manager

This page is accessed via Business Process Automation > Integration > Message Hub Manager.

The Message Hub is used to track XML messages between the system and a device or driver. The Message Hub is separate from the Message Center, which is a centralized message board that displays messages when specific events occur such as when business objects are created or modified, or status changes. Some messages in the Message Hub may be configured to appear in the Message Center.

Manually Entering a Message

If the message is inbound, select the Inbound check box. If the check box is not selected, then the message is outbound.

  1. Enter a Message Date or accept the default.
  2. Select a Status.
    • ERROR: An error occurred during the processing of a message.
    • PENDING: The message is awaiting the determination of the recipient. Such as, the device has not been assigned to a driver yet.
    • PROCESSED: An inbound or outbound message was successfully processed.
    • PROCESSING: The message is being processed.
    • RECEIVED: The message has been received but the message header has not yet been parsed.
  3. When manually entering a message, you do not need to enter a Processing Error Code.
  4. Enter a Priority. A priority of 1 is the highest priority and will be processed first.
  5. Enter the Sender Message ID to specify the identifier for the message. For outbound messages this is the person composing the message. When viewing inbound messages this value is designated by the sending system.
  6. For outbound messages that have been received by their destination, the Reference Message ID represents the reference identifier from an acknowledgement from the receiving system.
  7. Enter a Message Type ID.
  8. Enter a Stylesheet Profile ID. For outbound messages, it indicates the stylesheet applied to the output. For inbound messages the listed  stylesheet profile indicates how the message should be parsed.
  9. Enter a Message Profile ID. This field is only used for inbound messages.
  10. Enter a Contact ID. This is the contact from whom this message is received, or the contact receiving the message.
  11. Enter a Device ID.
  12. Enter an External Device ID of the sender. On an inbound message, this may be used to look up the device.
  13. Enter a Driver ID if the message is associated with a driver.
  14. Enter a Power Unit ID if the message is associated with a power unit.
  15. Enter the Equipment ID if the message is associated with equipment.
  16. Enter the Location ID associated with this message.
  17. Enter the Latitude and Longitude of the sender.
  18. Enter your Cell Phone Number. If this is an inbound message, the cell phone number can be used to look up the contact.
  19. Enter your Email Address. If this is an inbound message, the email address can be used to look up the contact.
  20. Enter an Acknowledgement Com Method ID to specify the communication method to use when sending the message report.
  21. Enter an Acknowledgement Contact ID to specify the contact or recipient of the message report.
  22. Enter an Acknowledgement  Option to generate the message report. Options include:
    • Error: The message report is only generated if there is an error.
    • Yes: The message report is always generated.
    • No: The message report is not generated.
  23. Enter a Title for the message. The title is used as the subject of the message in the Message Center.
  24. Enter the Message Content.
  25. Click Finished.

Acknowledgements

The Acknowledgements section tracks responses to messages. The Manually Act on Message action will enter information into this section, for example. Other acknowledgements from external systems may be tracked here as well. This section should not be completed if creating a message from the Message Hub.

Manually Entering an Acknowledgement:

  1. Enter a Sequence Number.
  2. Enter a Status.
  3. Enter a Reason.
  4. Enter a Date.
  5. Click Save for each sequence number you enter.

Related Topics