Show TOC

Using Conventions for Communication Component NamesLocate this document in the navigation structure

Use

If you are using an RNIF 2.0 adapter, there is a convention for naming the communication component that the communication channel is assigned to.

Procedure
  1. Create a communication component (in Integration Directory).
  2. Adhere to the following convention when naming the communication component:

    Name: PIP<PIP Code>_<PIP Version>_<PartnerRole>

    • <PIP Code>: PIP standard code

      Example: PIP3A7

    • <PIP Version>: PIP version

      Enter the value of the PIP version identifier from the title page of the PIP specification document.

      Example: The PIP version identifier in the specification document is V0202. The PIP version is V02.02.01.

    • <PartnerRole>:

      Take the value from the Role Name Column of Partner Role Descriptions table in the PIP specification for the currently executed PIP.

      The partner role must match the role assumed by the partner for which the communication component is defined.

Result

Assigning a name for the communication component is runtime-relevant. The RNIF 2.0 adapter determines the name of the communication component of the partner and the local name of the communication component for an inbound RosettaNet action message that is based on the selected header fields of the RNIF 2.0 protocol service header. The adapter then constructs the name according to the above-mentioned rules as follows:

<PIP Code> := /ServiceHeader/ProcessControl/pipCode.GlobalProcessIndicatorCode

<PIP Version Identifier> := /ServiceHeader/ProcessControl/pipVersion.VersionIdentifier

<Partner Role> := /ServiceHeader/…/MessageControl/fromRole.GlobalPartnerRoleClassificationCode

The name of the service for the local role would have the following form:

<Local Role> := /ServiceHeader/…/MessageControl/toRole.GlobalPartnerRoleClassificationCode