Testing-inbound flow and outbound flow - IBM Websphere

Everything has been successfully configured and the infrastructure is “up and running,” so now it is time to test our scenario and actually see the transaction results in our Transaction Viewer and the system logs. In the interest of simplicity, testing is divided into inbound flow and outbound flow.

Inbound flow

Before we actually start with the testing, we review the overview of the inbound flow and the actual steps that will be performed. Refer to Figure below.

Inbound flow steps for HIPAA scenario

Inbound flow steps for HIPAA scenario

Here are the steps and their explanations. Messages can be sent using an HTTP utility. In our case, we use NetTool:

  1. The message (HIPAAdata.txt) is sent to the http HIPAA_Partner_HttpSFH(10073), which is in HIPAA_Partner_B2BGW service.
  2. Sample of how to perform an HTTP message using NetTool

    Sample of how to perform an HTTP message using NetTool

  3. The message is wrapped in AS2 and sent using HIPAA_Provider profile AS2Destination to port 10070.
  4. The AS2 Message is received by HIPAA_Provider_B2BGW with
    HIPAA_Provider_AS2FSH (10070) and sends MDN back to port 10071.
    HIPAA_Partner_B2BGW receives MDN within the same connection.
  5. Message is unwrapped and sent to MQ using HIPAA_provider_int profile with MQ_2_Backend destination (Q1).
  6. WTX is listening on Q1 and transforms the message using Inbound_system.msl.
  7. The flat file is put on Q2.

Testing results
This shows how our inbound flow looks in the B2B Transaction Viewer.Note the Gateway Name column and the inbound successful results.

Transaction Viewer of the inbound flow

Transaction Viewer of the inbound flow

you can see in the Document Type column that this message is an X12 837 message.

Detail on Transaction Viewer of Document ID and Type

Detail on Transaction Viewer of Document ID and Type

If we click any of the Transaction Set ID hyperlinks, we can see various parts of the document as depicted.

Detail of how to download and show various content

Detail of how to download and show various content

Outbound flow

Now, we review an overview of the outbound flow and the steps that are performed. To get started, refer to Figure below.

Outbound flow steps for HIPAA scenario

Outbound flow steps for HIPAA scenario

Next, we describe each step. An MQ utility is used to put messages on queues. In our case, we used RfhUtil:

  1. The message (Flat_Payment_Advice.txt) is put on Q3.
  2. Putting the test message into Q3 using RfhUtil

    Putting the test message into Q3 using RfhUtil

  3. WTX transforms the message into an 837 HIPAA format and puts its result in Q4.
  4. The message is received in HIPAA_Provider_B2BGW with MQ_FSH.
  5. The message is wrapped in AS2 and sent to HIPAA_Partner_B2BGW using the HealthPartner profile (AS2_2_Healthpartner destination, on port 10071) which receives the message.
  6. An MDN is sent through 10071 to HIPAA_Provider_B2BGW.
    HIPAA_Partner_B2BGW receives the AS2 message using
    HIPAA_Partner_AS2FSH, which is included in it.
  7. HIPAA_Partner_B2BGW unwraps the message and sends it back through the back end, putting it on Q6.

Testing results
this shows the outbound flow in the Transaction Viewer. This view is a comprehensive view of the message flow.

Transaction Viewer of the outbound flow

Transaction Viewer of the outbound flow

you can see in the Document Type column that this message is an X12 835 message.

Transaction Viewer detail of the Document ID and Type

Transaction Viewer detail of the Document ID and Type

This depicts the message content at Q6, which arrived successfully as expected.

Output content coming from Q6 browsed with RfhUtil

Output content coming from Q6 browsed with RfhUtil


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics