Creating connections to participants

The following process describes how to create a connection between a back-end system and a participant. Note that you must create a connection for each PIP that you want to send and one for each PIP that you want to receive.

Before you begin, ensure that the following conditions apply:

To create a connection for a particular PIP, do the following:

  1. Create the interaction for the connection:
    1. Click Hub Admin > Hub Configuration > Document Flow Definition.
    2. Click Manage Interactions.
    3. Click Create Interaction.
    4. Expand the source Document Flow Definition tree to the Action level and expand the target Document Flow Definition tree to the Action level.
    5. In the trees, select the Document Flow Definitions to use for the source context and the target context. For example, if the participant is the initiator of a 3C6 PIP (a one-action PIP), select the following Document Flow Definitions in the trees:
      Table 1. 3C6 PIP initiated by a participant
      Source Target

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3C6 (V01.00)
      Activity: Notify of Remittance Advice
      Action: Remittance Advice Notification Action

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3C6 (V01.00)
      Activity: Notify of Remittance Advice
      Action: Remittance Advice Notification Action

      If the back-end system is the initiator of the 3C6 PIP, select the following Document Flow Definitions from the trees:

      Table 2. 3C6 PIP initiated by a back-end system
      Source Target

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3C6 (V01.00)
      Activity: Notify of Remittance Advice
      Action: Remittance Advice Notification Action

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3C6 (V01.00)
      Activity: Notify of Remittance Advice
      Action: Remittance Advice Notification Action

      For a two-action PIP such as 3A4 initiated by a participant, select the following Document Flow Definitions for the first action:

      Table 3. 3A4 PIP initiated by a participant
      Source Target

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Request Action

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Request Action

      If a back-end system initiates the two-action 3A4 PIP, select the following Document Flow Definitions for the first action:

      Table 4. 3A4 PIP initiated by a back-end system
      Source Target

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Request Action

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Request Action

    6. In the Action field, select Bi-Directional Translation of RosettaNet and RosettaNet Service Content with Validation.
    7. Click Save.
    8. If you are setting up a two-action PIP, repeat steps c-g to create the interaction for the second action. For example, select the following Document Flow Definitions for the second action for a 3A4 PIP initiated by a participant. This is the action in which the back-end system sends the response.
      Table 5. 3A4 PIP initiated by a participant (second action)
      Source Target

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Confirmation Action

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Confirmation Action

      For the second action for a back-end system initiated 3A4 PIP, select the following Document Flow Definitions:

      Table 6. 3A4 PIP initiated by a back-end system (second action)
      Source Target

      Package: RNIF (V02.00)
      Protocol: RosettaNet (V02.00)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Confirmation Action

      Package: Backend Integration (1.0)
      Protocol: RNSC (1.0)
      Document Flow: 3A4 (V02.02)
      Activity: Request Purchase Order
      Action: Purchase Order Confirmation Action

  2. If a participant profile does not exist for the participant, create it. See Creating participants for information on how to do this. There must also be a participant profile of the Community Manager type for the back-end system.
  3. If a gateway with the supported protocol does not exist between the participant and Business Integration Connect or between a back-end system and Business Integration Connect, create it. See Creating gateways for information on how to do this. The supported protocols for RosettaNet messages between a participant and Business Integration Connect are HTTP and HTTPS. The supported protocols for RosettaNet messages between a back-end system and Business Integration Connect are HTTP, HTTPS, and JMS.
  4. Activate the Document Flow Definitions that Business Integration Connect uses to process the PIP. To do this, activate the participant's and back-end system's definitions for the Package, Protocol, and Document Flow for the PIP. The direction of the message determines which one is the source and which one is the target. Business Integration Connect automatically activates the Activity, Actions, and Signals when you activate the parent Document Flow. For information on how to activate the Document Flow Definitions, see Setting up B2B capabilities.

    Participant

    back-end system

  5. Activate the connection by setting the source and target in the Participant Connections screen. If the participant is the initiator of the PIP, set the source to the participant's profile and the target to the Community Manager profile. If the initiator is a back-end system, set the source to the Community Manager profile and set the target to the participant's profile. See Creating interactions for information on searching for connections and activating them. If the PIP is a two-action PIP, you must also activate the connection in the other direction to support the second action of the PIP. To do this, the source and target of the second action are the opposite of the source and target of the first action.
  6. If Business Integration Connect does not have a target defined for each of the protocols, create it. See Setting up targets for information on how to do this.

Copyright IBM Corp. 2003, 2004