...
The configuration of B2BConnector is defined as shown in the following figure.
Figure 1: B2BConnector Configuration Property Sheet
...
Figure 3: MTBID Selection Dailog box
Figure 4: Selected MTBIDs with Mode
Receive All Partners
If enabled, it will receive messages from all the hosts and create a single output port for the Receiver(Host). The component will receive the messages from all hosts configured in B2B Dashboard.
Figure 5: Selected receive all partner property
Use MTBID from Input
Enabling this will create a single input and output port i.e., a generic port for the Sender (Remote Partner). The component will be expecting a String property 'partnermtbid' which holds the Receiver's MTBID (Host); otherwise the component throws an error. So the string property should be added as a JMS header before the message reaches the B2BConnector when configured for Send mode. The component will then process the request based on the selected Partner's Configuration in the Dashboard. The status message will be received from the output port.
Figure 6: Selected Use MTBID from Input property.
| Note |
|---|
If the Receive All Partners property or the Use MTBID From Input property is enabled, transport calls will not be made to MTBID configured in the MTB ID Selection Configuration dialog box. |
| Anchor | ||||
|---|---|---|---|---|
|
The following sample flow consists of B2BConnector with two MTBIds, one with Mode as 'Send' and other as 'Receive'. Sample message is sent from Feeder and status message is sent on send_output port stating that message sending to B2B Core Event Process is successful. The receive_output port recieve the message from B2B Core Event Process.
Following is the sample event process:
\
Figure 57: Sample Event Process
Figure 68: Selected MTBIds with Mode in SampleB2B CPS
Figure 79: Sample Input Message sent to B2b Core Event Process
Figure 810: Status Message stating message sending to B2B Core Event Process is successful
Figure 911: Message received from the Core B2B Event Process
...