Activating participant connections
Participant
connections contain the information necessary for the proper exchange
of each document flow. A document cannot be routed unless a connection
exists between the Community Manager and one of its participants.
The system automatically creates connections between the Community
Manager and participants based on their B2B capabilities.
You search for these connections and then activate them.
When selecting a Source and a Target, observe the following guidelines:
- The Source and Target must be unique.
- Do not mix a production gateway with a test gateway when selecting
Source and Target; otherwise, an error occurs.
- Both the Source and the Target must be production or test gateways.
Use the following procedure to perform a basic search for connections
and then activate the connections.
- Click Account Admin > Participant Connections.
The Manage Connections page is displayed.
- Under Source, select a source. For example,
if you are setting up an exchange that originates from the Community
Manager, select the Community Manager.
- Under Target, select a target. For example,
if you are setting up an exchange that will be received by a participant,
select that participant.
Note: When you create a new connection, the Source and
Target must be unique.
- Click Search to find the connections that
match your criteria.
Note: You can also use the Advanced Search page if you
want to enter more detailed search criteria.
- To activate a connection, click Activate.
The Manage Connections page is redisplayed, this time with the connection
highlighted in green. This page shows the package, protocol, and
document flow for the source and target. It also provides buttons
you can click to view and change partner-connection status and parameters.
- To specify attributes for the source or target or to select
a connection profile, see Specifying or changing attributes.
For a two-action PIP, activate the connection in both directions
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.
For EDI, XML, or ROD documents for which you have defined more
than one interaction, make sure you activate all the connections
associated with the interactions.
