Routing Scenarios

Pages in this section present examples of scenarios that identify and illustrate:

Background Reading

Actors, Relationships and Artifacts

Introduces foundational IHub terminology.

Transaction-Processing Framework

Explains how IHub works.

Basic

img-basic-routing-scenario-overview
Figure 1. Basic Routing Scenario Overview
Scenario

Transmit document from one actor to another by configuring a transaction.

Example

Your organization receives a document from a Partner. If IHub has been configured to receive a document of this Document Type, IHub routes the document to an internal API. If IHub has not been configured to receive a document of this Document Type, IHub rejects the document.

Shared

img-shared-routing-scenario-overview
Figure 2. Shared Routing Scenario Overview
Scenario

Same action as in Basic, but configured in a manner that facilitates the document type going to or coming from multiple Partners.

Example

Your organization wants to receive a document Document from two Partners, map it to an internal standard, and send it to a backend database.

Override

img-override-routing-scenario-overview
Figure 3. Override Routing Scenario Overview
Scenario

Many Partners use the same Document Type, so that you can reuse a configuration across those partners. This scenario takes into account the possibilityt that some Partners may have slightly different Document Types, requiring the use of a different map.

Example

Your organization expects to receive documents of a single Document Type from multiple Partners.

If IHub has been configured to receive a document of this Document Type, IHub routes the document to an internal API.

However, one partner uses a variation of the Document Type, so you must override the standard Map that you use to transform that partner’s Document Type to your internal Document Type before routing.

If IHub has not been configured to receive a document of this Document Type, IHub rejects the document.

Multi-Route

img-multi-route-routing-scenario-overview
Figure 4. Multi-Route Routing Scenario Overview
Scenario

A single Document Type is processed by more than one Transaction.

Example

Your organization receives a document from a partner. IHub has been configured to process the document in two ways:

  • Route a copy of the document to an internal API

  • Route a copy of the document directly to a destination you use to backup received documents. This routing is referred to as passthru because it does not require a map.

Multicast

img-multicast-routing-scenario-overview
Figure 5. Multicast Routing Scenario Overview
Scenario

A Document Type has no To field; therefore, it is sent to all Relationships that have Transactions including the Document Type.

Example

An Application sends a document to three other Applications. Two of the Applications require the document as-sent; the third requires the payload to be mapped.

Chained Transactions

img-chained-transactions-routing-scenario-overview
Figure 6. Chained Transactions Routing Scenario Overview
Scenario

A Document Type is exchanged between Applications and Partners, where the data is separated into each domain.

Example

An Application sends a document to a Partner.

Content-Based-Routing

img-content-based-routing-routing-scenario-overview
Figure 7. Content-Based Routing Routing Scenario Overview
Scenario

A Document Type is sent to a specific Transaction or Endpoint based on the content contained inside the Document or on the Endpoint.

Example

Your organization receives a document from a Partner. Depending on the size of a property in that document, Integration Hub routes the document to an endpoint DataBig or an endpoint DataSmall.