Configuring the Sender CIDX Adapter

We recommend using the communication channel templates provided in the shipment. If you do not use the templates, make the required specifications for the adapter.

More information: Configuring the CIDX Adapter with Communication Channel Template

• You have created a party and a communication component.

  More information: Using Conventions for Communication Component Names

• You are defining the scenario Single-Action Initiator.

  More information: Single-Action Initiator

1. Select the Transport Protocol:
   • HTTP 1.1
   • HTTPS
2. The Message Protocol is RNIF 1.1.
3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.
4. Select the Process Specification tab page.
5. The Configuration Type is Single-Action Asynchronous Request.

Define Message Protocol Specific Information

1. Under Process Name, enter the name of the Chem eStandard business transaction, for example OrderCreate.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessCode

2. Under Current Business Service Code, specify which value is to be set before the service.

   For example, if the role of the Integration Server is Seller, the value of the field is Seller Service.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ServiceRoute/toService.BusinessServiceDescription/GlobalBusinessServiceCode

3. Under Partner Business Service Code, specify which value is to be set before the service.

   For example, if the role of the partner is Buyer, the value of the field is Buyer Service.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ServiceRoute/fromService.BusinessServiceDescription/GlobalBusinessServiceCode

4. Supply Chain Code is defined in the RNIF 1.1 standard. The values are available in the DTDs of the signal messages.

   The order is not relevant.

Define chemXML Transaction Information

1. Enter the Code.

   Use the value from Appendix D of the Chem-eStandards - ChemXML Transaction Code, for example E41.

   Protocol field in the Chem eStandard message:

   ServiceHeader- ProcessControl/ ProcessIdentity/ GlobalProcessIndicatorCode

2. Specify the Version of the Chem eStandard business transaction.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ProcessIdentity/VersionIdentifier

3. Under Requesting Message, enter the name of the Chem eStandard business transaction.

   Do not use blanks. For example, enter OrderCreate.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/GlobalBusinessActionCode

4. Under Current Role, specify the role of the Integration Server.

   Use the value from the Chem eStandards business transaction specification. For example, enter Buyer.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/PartnerRoleRoute/toRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

5. Under Partner Role, specify the role of the partner.

   Use the value from the Chem eStandards business transaction specification. For example, enter Seller.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/PartnerRoleRoute/fromRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

Define Message Exchange Controls

1. Under Number of Retries, specify how often the partner can attempt to resend messages.
2. Select the Receipt Acknowledgment:
   • Weak

     The signal message (confirmation/exception) is sent before message processing on the Integration Server is complete.

   • Strong

     The signal message (confirmation/exception) is not sent until confirmation has been received from the Integration Server.

Define Security Policy

1. If you want the action message to be signed, select Sign Action Message.
2. If you want the signal message to be signed, select Sign Signal Message.
3. If you want to request a non-repudiation log for the transaction, select Non-Repudiation.
4. Make the entries for the certificates in the Sender Agreement.

   More information: Configuring Security in the CIDX Adapter

Define Transport Parameters

1. Select the Source tab page.
2. Under URL, enter the partner address to which the adapter is to send the signal message.
3. Under Persist Duration, specify the length of time in days, hours, minutes, and seconds that messages are to be stored in the Adapter Framework message store, depending on the communication channel.

Define Authentication

1. The specifications for Authenticationdepend on the transport protocol you have selected:
   • If a client authentication is required for transport protocol HTTP 1.1, select Client Authentication Required.

     Enter the User Name of the partner and the Password, and confirm.

   • Select the Authentication Mode for transport protocol HTTPS:
     • User Name/Password

       Enter the User Name of the partner and the Password, and confirm.

     • Certificate Logon

       Select the Keystore View and the Keystore Entry.

Define Inbound Security Checks

1. Under Inbound Security Checks, select the HTTP Security Level for inbound messages.
   • HTTP
   • HTTPS without client authentication
   • HTTPS with client authentication

Define Adapter-Specific Message Properties

1. To save adapter-specific attributes in the message header of the PI message, select Set Adapter-Specific Message Properties.
2. To apply the following attributes in the PI message header, set the corresponding indicators:
   • Process Instance Identifier (technical name: Proc Inst Identifier)

     A unique alphanumeric ID that stands for a specific instance of a business process.

   • Message Identifier (technical name: Message Identifier)
   • Document Identifier (technical name: Document Identifier)

     A unique alphanumeric ID that stands for the PIP business document.

   • Document Date Timestamp (technical name: Document Date Time)

     Date and time that message is sent to partner.