Configuring the Receiver 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 Responder

1. Select theTransport 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.

   Do not use blanks. For example, enter OrderCreate .

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessCode

2. Under Transaction Name, 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/TransactionIdentity/GlobalTransactionCode

3. Under Message Version, enter the version of the Chem eStandard business transaction.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/VersionIdentifier

4. Under Current Business Service Code, specify the role of the Integration server and 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/fromService.BusinessServiceDescription/GlobalBusinessServiceCode

5. Under Partner Business Service Code, specify the role of the partner and Service.

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

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/ServiceRoute/toService.BusinessServiceDescription/GlobalBusinessServiceCode

6. The Current Classification Code is not specified in the Chem eStandard.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/PartnerRoute/fromPartner.PartnerDescription/BusinessDescription/GlobalPartnerClassificationCode

7. The Partner Classification Code is not specified in the Chem eStandard.

   Protocol field in the Chem eStandard message:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/PartnerRoute/toPartner.PartnerDescription/BusinessDescription/GlobalPartnerClassificationCode

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/fromRole.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/toRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

6. The Document Schema Specification is not relevant.

Define Message Exchange Controls

1. Specify the Number of Retries.

   The adapter makes the specified number of attempts to send to the partner.

2. Under Time to Acknowledge Receipt, specify the length of time after which business action messages are to be resent if the partner does not return a confirmation.

Define Security Policy

1. If you want the action message to be signed before sending, select Sign Action Message.
2. If you want the signal message to be signed before receipt, 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 Receiver Agreement.

   More information: Configuring Security in the CIDX Adapter

Define Transport Parameters

1. Select the Target tab page.
2. Under URL, enter the partner address to which the action message is to be sent.
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 message 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 message 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.