Using a Channel to Construct a Message Flow

In this section:

The use of iWay Service Manager utilizes a channel, which is a container for all the iWay business components used in a HIPAA message flow.

At a high level, a channel accepts input data via an inlet, processes the data via a route, and outputs the resulting data via an outlet. Another component in the process is an Ebix (e-Business Information Exchange). An Ebix provides an archiving executable solution for e-business metadata components, which allows integration with iWay Service Manager for end-to-end e-business document processing.

The following diagram shows the channel components available in the construction of a message flow.

In the following diagram, the value n underneath a component name indicates how many instances of that component you can have in a channel configuration—zero, one, or more than one. For example, n = 1 for Inlet means that you can have only one inlet on the channel.

Required components are in boldface type.


Top of page

x
Components of a Channel

A channel consists of:

iWay Service Manager provides a design-time repository called the Registry, where you assemble and manage the components in a channel.

An inlet can contain:

A route can contain:

An outlet can contain:

For details on the preceding components, see the iWay Service Manager User's Guide.


iWay Software