Chained Transactions Routing Scenario

In this example of a chained-transactions routing scenario, an Application sends a Document to a Partner.

Figure 1. Chained Transactions Routing Scenario Overview

Background Reading

Introduces foundational PortX terminology.

Explains how PortX works.

There are four Relationships in this scenario:

Relationship	Description	Contains
AppA : Any	Universal Relationship between Application A and any other Application	Contains Artifacts specific to transactions between Application A and any other Application.
YourCompany B2B : Any	Universal relationship between your company and any partner	Contains Artifacts used across all partners with whom you do business
YourCompany B2B ; AppA	Relationship between this applcation and the Home Partner (YourCompany B2B)	Contains Artifacts specific to transactions between Application A and the Home Partner
YourCompany B2B : PartA	Your company’s relationship with the partner with whom you are doing business (in this case, PartA).	Contains artifacts used only with this partner

Relationship

Description

Contains

AppA : Any

Universal Relationship between Application A and any other Application

Contains Artifacts specific to transactions between Application A and any other Application.

YourCompany B2B : Any

Universal relationship between your company and any partner

Contains Artifacts used across all partners with whom you do business

YourCompany B2B ; AppA

Relationship between this applcation and the Home Partner (YourCompany B2B)

Contains Artifacts specific to transactions between Application A and the Home Partner

YourCompany B2B : PartA

Your company’s relationship with the partner with whom you are doing business (in this case, PartA).

Contains artifacts used only with this partner

Figure 2. Chained Transactions Routing Scenario Artifacts

This tables and flow diagrams in this section identifies:

Artifacts that must be configured in order for a given document to be routed (that is, not rejected)
The Relationship in which the artifacts are configured

Table 1. Application Sends to Partner Routing Scenario Artifacts - **AppA : Any**
Artifact	Artifact Name	Description	Configured on page
Document Type	Y	Document Type you expect to receive from this Application	Document Types

Table 2. Application Sends to Partner Routing Scenario Artifacts - *YourCompany* B2B : Any
Artifact	Artifact Name	Description	Configured on page
Document Type	X	Document Type your company uses internally	Document Types
Endpoint	Router	Endpoint used to route Documents	Endpoints
Target Channel	X-to-Router	Sends Document of Document Type X to PortX	Channels
Source Channel	X-to-Passthru	Sends Document of Document Type X to selected Target Channel.	Channels

Table 3. Application Sends to Partner Routing Scenario Artifacts - **AppA : *YourCompany* B2B**
Artifact	Artifact Name	Description	Configured on page
Map	Y-to-X	Transforms a document of Document Type Y to a Document of Document Type X	Maps
Source Channel	Y-to-X	Maps document of Document Type Y to a Document of Document Type X.	Channels
Transaction	Y-to-X-to-Router	Combination of the Source Channel Y-to-X and the Target Channel X-to-Router. Receives a document of Type Y, maps it to a document of Type X, then sends it to the Router Endpoint. This transaction has From Partner configured as AppA and To Partner configured as Your Company B2B.	Transactions Designer

Table 4. Application Sends to Partner Routing Scenario Artifacts - *YourCompany* B2B : AppA
Artifact	Artifact Name	Description	Configured on page
Endpoint	PartA	Endpoint that points to an external Partner	Endpoints
Document Type	Z	Document Type your parter expects to receive from your company	Document Types
Map	X-to-Z	Transforms a document of Document Type X to a Document of Document Type Z	Maps
Target Channel	X-to-Z-to-PartA	Maps document of Document Type X to Document Type Y and sends it to PartA	Channels
Transaction	X-to-Z-to-PartA	Sends Document of Document Type X to selected Target Channel.	Transaction Designer

PortX: