Exchanging RNIF Payload with Attachments Along with Payload Validation

Edit online

When a partner (sender) wants to send a PIP 2A9 request with an attachment and send it to another partner over an RNIF-OUT channel. And the receiver, in turn sends a PIP 2A9 response with attachment synchronously over the same connection. IBM® webMethods B2B validates the payload before it sends it and after it receives it as well.

Consider two partners, car-steering supplier(enterprise-sender) and car-seat supplier(receiver).

The following image illustrates the exchange:

Before You Begin

Edit online

You need the following design-time assets at sender's side:

  • Enterprise partner profile (car_steering_supplier) and receiver partner profile (car_seat_supplier) configured with appropriate partner users.
  • RNIF-IN and RNIF-OUT communication channels for both the sender and receiver partner profiles.
  • Partner-specific TPA (sender: car_steering_supplier and receiver: car_seat_supplier with document type Pip2A9QueryRequest )
  • Document types (Pip2A9QueryRequest and Pip2A9QueryResponse)
  • Processing Rule (Deliver2A9WithAttachmentToCar_seat_supplier: To send the document to partner)

You need the following design-time assets at receiver's side:

  • Enterprise partner profile ( car_seat_supplier) and receiver partner profile (car_steering_supplier) configured with appropriate partner users.
  • RNIF-IN and RNIF-OUT communication channels for both the sender and receiver partner profiles.
  • Partner-specific TPA (sender: car_steering_supplier and receiver: car_seat_supplier with document type Pip2A9QueryRequest )
  • Document types (Pip2A9QueryRequest and Pip2A9QueryResponse)
  • Processing Rule (Generate&Send2A9ResponseWithAttachmentToCar_steering_supplier: To send the document to partner)
  • Ensure your execution in processing rule is set to synchronous if you want to send the response synchronously.

On the Sender's (car_steering_supplier) Side

Edit online

  1. A PIP2A9Request document is submitted to IBM webMethods B2B (Enterprise car_steering_supplier) from IBM webMethods Integration.

  2. The enterprise sender car_steering_supplier sends this document over an RNIF Outbound channel using RNIF-partner-specific TPA(Payload validation = Outbound set in TPA) using a custom processing rule: Devlier2A9WithAttachmentToCar_seat_supplier.

    The payload is validated by IBM webMethods B2B before it is sent.

    The RNIF PIP2A9Request was sent to car_seat_supplier.

At the Receiver's (car_seat_supplier) End

Edit online

  1. The receiver car_seat_supplier receives a PIP2A9 request with attachments from car_steering_supplier over synchronous RNIF IN channel as shown in the following images:

    The RNIF document is received as shown in the following image:

    The incoming payload is validated by IBM webMethods B2B as follows:

  2. The Transaction summary displays the RNIF PIP2A9Response document details that are sent by car_seat_supplier.

    The content of the document is as follows:

    The content is received with the attachments highlighted in the following image:

  3. Generated PIP2A9Response with attachments is received by Enterprise car_steering_supplier from partner car_seat_supplier.

    The attachments are highlighted as follows:

    With this, the sender's payload is validated by IBM webMethods B2B before it is sent and validated at the receiver's when it is received.