Presenting the Binary AS2 over HTTP multi-step use case - IBM Websphere

This section outlines a specific use case for sending binary messages that are not wrapped by the AS2 or AS3 protocol. The B2B Gateway often receives these messages via a protocol, such as WebSphere MQ, HTTP, or FTP, that do not have the same routing headers as AS2 or AS3.

These inbound messages must (currently) be processed using a multi-step process. This multi-step process allows messages to be transformed that contain customized header information in order to route these messages properly to the B2BGW. The Multi-Protocol Gateway object allows us to provide this processing step, sort of a preprocessor step.

This use case consists of two Trading Partner systems, Partner Binary System and Hub Binary System. The Hub Binary System consists of a hub application, which runs on a server in the hub owner’s enterprise. The Hub Binary Application is associated with the Hub Binary MPGW in the Hub Binary enterprise. The Partner Binary System consists of a partner application, which runs on a server in the partner’s enterprise. The partner application is associated with the Partner B2B Gateway (B2BGW) in the Partner Binary enterprise.

This shows HTTP To AS2 binary processing transaction flow.

HTTP To AS2 binary processing transaction flow

HTTP To AS2 binary processing transaction flow


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

IBM Websphere Topics