Actors, Relationships, and Artifacts

This page introduces and defines Integration Hub’s fundamental building blocks: Actors, Relationships, and Artifacts.

Actors

An IHub Actor is an entity that you can pair with another Actor to form a Relationship.

An Actor contains:

There are four types of Actors:

Partners

A Partner is an organization that exchanges B2B documents with your organization, such as PartA in Basic Routing Scenario.

Applications

An Application is a software program, or group of programs, that have a role within your organization, such as AppA in Chained Transactions Routing Scenario.

YourCompany B2B

YourCompany B2B is your organization’s gateway between its applications and its Partners. You can see how this Actor works in Basic Routing Scenario.

Any

Any refers to all shared application-specific information. You can see how this Actor works in Basic Routing Scenario.

Relationships

You can connect one Actor to another to form a Relationship. A Relationship is the union of an Actor with another Actor for the purpose of partitioning Artifacts. For example, Basic Routing Scenario illustrates the use of two Relationships:

YourCompany B2B : Any

Universal Relationship between your company and any Actor

YourCompany B2B : PartA

Your organization’s Relationship with the Partner with whom you are doing business (in Basic Routing Scenario, this is PartA)

Artifacts

An Artifact is a software component of the IHub system that resides in a Relationship. This section identifies all IHub Artifacts.

Document Type

Identifies types of documents based on values such as Standard and Message Type.

Endpoint

Entry point to a service, process, queue or topic destination.

Channel

Grouping of Artifacts specific to a transmission.

Map

Transforms one Document Type to another Document Type.

Transaction

The end-to-end processing of a single instance of a document from receipt at an Endpoint all the way to the appropriate business service.