Setting up B2B capabilities
The Community Manager has B2B capabilities that define the
types of documents the Community Manager can send and receive.
You use the B2B Capabilities feature to associate the Community
Manager's B2B capabilities with a document flow definition.
Use the following procedure to set the B2B capabilities of the
Community Manager.
- Click Account Admin > Profiles > Community Participant.
- Enter search criteria and click Search,
or click Search without entering any search criteria
to display a list of all participants.
- Click the View details icon next to the
Community Manager.
- Click B2B Capabilities. The B2B capabilities
page is displayed. The right side of the page shows the packages,
protocols, and document flows supported by the system as
document flow definitions.
- Click the Role is not active icon under
the Set Source column for the Packages on the
right that contain documents the Community Manager will
send to participants.
- Select Set Target if you will receive
those same documents from participants. The Community Console
displays a check if the document flow definition is enabled.
Note: The selection of Set Source will be the same for
all actions in a 2-way PIP regardless of the fact that the request
will originate from one participant and the corresponding confirmation
from another. This also applies to Set Target.
- Click the Expand icon at the Package level
to expand an individual node to the appropriate document flow definition
level, or select a number from 0-4 or All to expand
all displayed document flow definitions to the selected level.
- Again, select the Set Source, Set Target,
or both roles for the lower Protocol and Document Flow levels
for each document flow definition your system supports.
If a definition is activated at the Document Flow level,
the Action and Activity definitions
(if any exist) will be activated automatically.
- Optionally click Enabled under the Enabled column
to place a document flow definition offline. (When you select Set Source or Set Target,
the record is automatically enabled.) Click Disabled to
place it online.
If a package is disabled, all lower-level document flow
definitions in that same node are also disabled, regardless of whether
their individual status was enabled. If a lower-level document flow
definition is disabled, all higher-level definitions within the
same context remain enabled. When a document flow definition is disabled,
all preexisting connections and attributes continue to function.
The disabled document flow definition only restricts the creation
of new connections.
- Click the Edit icon to edit any of the
attributes of a protocol, package, document flow, action, activity,
or signal. You then see the settings for the attributes (if any attributes
exist). You can modify the attributes by entering a value or selecting
a value from the Update column and then clicking Save.
As
mentioned in step 10, the
Community Manager can (and in some cases must) have multiple business
IDs assigned. If the participant has a requirement to receive only
one form of the ID, you must select the appropriate value for the
ID. To select the ID:
- Click the Edit icon next to None.
You see the attribute (AS Business ID)
associated with the None package.
- From the Update list, select the AS2 Business
ID that is in the format acceptable by your participant.
- Click Save.
Note: If you set the attribute on the B2B Capabilities
screen, it applies to all exchanges that originate from the Community
Manager with the None package. To make the selection more specific
to a particular connection, you can set the value (or override the
value you set here) at the connection level. Refer to Activating participant connections.
