Reviewing B2B capabilities

Note:
In smaller installations, this process might be performed by the Hub Admin.

Use this feature to view and edit predefined hub-wide B2B capabilities, and to enable additional local B2B capabilities, if required.

A B2B capability identifies a specific type of business process that can be exchanged between you and other community members. B2B or document processing capabilities are defined using document flow definitions. A document flow definition gives the system all of the necessary information to receive, process, and route documents between community members.

Each capability consists of up to five different document flow definitions:

Package. Identify document packaging formats used to transmit documents over the internet. For example, RNIF, AS1, and AS2.

Protocol. Identifies structure and location of information in the document. The system needs this information to process and route the document.

Document flow. Identifies the business process that will be processed between the Community Manager and its participants.

Activity. The business function the process performs.

Action. The individual documents that make up a complete business process. The documents are processed between the Community Manager and participant.

Each document flow definition contains attributes (that is, information) that define the definition's functionality. An attribute is a piece of information that is associated with a specific document flow. The system uses this information for various functions such as validating the documents or checking for encryption.

Reviewing and editing B2B capabilities:

  1. Click Account Admin > Profiles > B2B Capabilities. The system displays the B2B Capabilities screen.
    Note:
    The target, source, or both capability must be set before you can enable it.
  2. Set the capability to initiate (Set Source), receive (Set Target), or initiate and receive the document flow context. In a 2-way PIP, Set Source and Set Target are the same for all actions, regardless of the fact that the request originates from one participant and the corresponding confirmation originates from another.
  3. Set the capability to initiate (Set Source), receive (Set Target), or initiate and receive for each lower level document flow definition.
  4. Click the Edit icon to view and, if desired, change lower level document flow definitions (for example Protocol or Document Flow). You can also change a document flow definition's attributes (for example, Time to Perform or Retry Count). When you use this screen for the first time, attributes are set at the global level. However, you can reset them at the local level, if desired. Setting an attribute at the local level overrides the global setting in your environment, but it does not change the global setting.

    If you changed an attribute, click Save.

Copyright IBM Corp. 2003, 2005