How to launch a business process in Sterling B2B Integrator when an event is raised in a Global Mailbox

In this scenario topic, a Sterling B2B Integrator administrator is trying to understand the configuration that is required to launch a business process in Sterling B2B Integrator when an event is raised in a Global Mailbox.

Ensure that the following requirements are met:

Global Mailbox is installed and Global Mailbox management tool is available and accessible.
Sterling B2B Integrator is installed and available and accessible.
WebSphere® MQ is installed and configured between Global Mailbox and Sterling B2B Integrator.

Get an understanding of the end-to-end configuration required to launch a business process in Sterling B2B Integrator when an event is raised in the Global Mailbox.

To launch a business process, complete the following steps:

Ensure that com.ibm.mailbox.messaging.event.notification.enabled property is set to true in the mailbox.properties file when installing the Global Mailbox server. If the property is not enabled, enable the property.
Configure event notification (part of appConfigUtility.sh).
Configure a business process in Sterling B2B Integrator.
Configure and enable the Global Mailbox Event Rule adapter in Sterling B2B Integrator.
Create an event rule. When configuring the event rule, select the business process that you have configured in Sterling B2B Integrator.
Important: A predefined business process, RoutingRuleDMMsgStatusMonitor, which is associated with the Global Mailbox Event Rule adapter, monitors the status of the business process that is specified in the event rule, and updates the status accordingly on the Global Mailbox management tool Event History page. Following is a list of the status that is displayed:

Unprocessed

The business process is yet to launch and message processing is yet to start.

Processing

The business process is running and message processing is in progress.

Success

The business process (message processing) completed successfully.

Failed

The business process (message processing) failed. Message processing can fail because a business process fails, or because the data center goes offline before processing is complete.
Message processing can also fail if the event rule configuration does not match with the configuration in Sterling B2B Integrator. For example, the business process or user who is specified in the event rule are not available in Sterling B2B Integrator or the system business process (RoutingRuleDMMsgStatusMonitor) is deleted. In such cases, the Global Mailbox administrator or Sterling B2B administrator must make appropriate changes to the event rule configuration or the business process and resend the events.
Important: To see the reasons for failure, verify the running instances of the RoutingRuleDMMsgStatusMonitor business process or monitor the Sterling B2B Integrator system logs (Operation/System/logs)

Process data for immediate mode processing

The Global Mailbox Event Rule adapter, which is configured in the immediate mode, extracts the following data related to the message that was put in the Global Mailbox and passes the data to the business process specified in the event rule:

<ProcessData>
  <EndpointName>FTEQueue</EndpointName>
  <RoutingRequest>
    <RoutingRequest>
      <MessageId>b692b5a0-292e-11e4-bb90-67e28453219b<StorageId>000000020028aeec005241363333323132353800000000000f4ed57a5dc73fd90000014893094d27</StorageId>
        <MessageName>myConsumer</MessageName>
        <MailboxPath>/Consumer/Inbox</MailboxPath>
        <CreatorUserId>admin</CreatorUserId>
      </MessageId>
    </RoutingRequest>
  </RoutingRequest>
</ProcessData>

Process data for batch mode processing

The Global Mailbox Event Rule adapter, which is configured in the batch mode, extracts the following data related to the message that was put in the Global Mailbox and passes the data to the business process specified in the event rule. For example, if a batch contains five messages, and business process x is specified for two messages, and business process y is specified for three messages, the messages are picked and processed by the business processes specified in the event rule, specific to the event.

<?xml version="1.0" encoding="UTF-8"?>
<ProcessData>
  <RoutingRequest>
    <RoutingRequest>
      <MessageId>ee21bb70-3981-11e4-aa1c-59b2a44fdbb7</MessageId>
      <MessageId>ee5b6910-3981-11e4-aa1c-59b2a44fdbb7</MessageId>
      <MessageId>eee866d0-3981-11e4-aa1c-59b2a44fdbb7</MessageId>
      <MessageId>ef47c4e0-3981-11e4-aa1c-59b2a44fdbb7
        <StorageId>0000000200285946183173745f70726f766973696f6e6564118215e49b78581400000148fe0631fe</StorageId>
        <StorageId>00000002002805de183173745f70726f766973696f6e656431d33a6fb0c6b99d00000148fe063566</StorageId>
        <StorageId>000000020028c0e0183173745f70726f766973696f6e6564029e0ccfd557902f00000148fe063ae3</StorageId>
        <StorageId>00000002002851d7183173745f70726f766973696f6e6564781bd598e3758fff00000148fe063d59</StorageId>
        <MessageName>RQM.xls</MessageName>
        <MessageName>RQM_New.xlsm</MessageName>
        <MessageName>RQM_New.xlsx</MessageName>
        <MessageName>SCP.txt</MessageName>
        <MailboxPath>/test_Prod/totest_Cons1</MailboxPath>
        <MailboxPath>/test_Prod/totest_Cons1</MailboxPath>
        <MailboxPath>/test_Prod/totest_Cons1</MailboxPath>
        <MailboxPath>/test_Prod/totest_Cons1</MailboxPath>
        <CreatorUserId>admin</CreatorUserId>
        <CreatorUserId>admin</CreatorUserId>
        <CreatorUserId>admin</CreatorUserId>
        <CreatorUserId>admin</CreatorUserId>
        <UseDistributedMailboxes>Yes</UseDistributedMailboxes>
        <UseDistributedMailboxes>Yes</UseDistributedMailboxes>
        <UseDistributedMailboxes>Yes</UseDistributedMailboxes>
        <UseDistributedMailboxes>Yes</UseDistributedMailboxes>
      </MessageId>
    </RoutingRequest>
  </RoutingRequest>
  <TRACKINGID>dublr190vm:node1:1486380a34e:6808</TRACKINGID>
</ProcessData>