Content-Based-Routing Routing Scenario

In this example of a content-based routing routing scenario, your organization receives a document from a Partner.

Depending on the size of a property in that document we want to either send that document to an endpoint DataBig or an endpoint DataSmall.

Figure 1. Content-Based Routing Routing Scenario Overview

Background Reading

Actors, Relationships and Artifacts: Introduces foundational PortX terminology.
Transaction-Processing Framework: Explains how PortX works.

In this scenario, there are three Actors:

There are two Relationships in this scenario:

Table 1. Content-Based Routing Scenario Relationships
Relationship	Description	Contains
YourCompany B2B : Any	Universal relationship between your company any partner	Contains Artifacts used across all partners with whom you do business
YourCompany B2B : PartA	Your organization’s relationship with the partner with whom you are doing business (in this case, PartA)	Contains Artifacts used only with Partner PartA

Figure 2. Content-Based Routing Scenario Artifacts

This section identifies:

Artifacts that must be configured in order for the document in this scenario to be routed (that is, not rejected)
The Relationship (either YourCompany B2B : Any or YourCompany B2B : PartA) in which the artifacts are configured

Table 2. Content-Based Scenario Artifacts - *YourCompany B2B* : Any
Artifact	Artifact Name	Description	Configured on page
Document Type	X	Document Type you use internally in your company	Document Types
Document Type	Y	Document Type you expect to receive from a partner	Document Types
Map	Y-to-X	Transforms a document of Document Type Y to a document of Document Type X	Maps
Endpoint	DATASmall	Endpoint that points to your internal database for Small type	Endpoints
Endpoint	DATABig	Endpoint that points to your internal database for Big type	Endpoints
Target Channel	X-to-DATASmall	Channel that sends a document of the internal Document Type X to Endpoint DATASmall	Channels
Target Channel	X-to-DATABig	Channel that sends a document of the internal Document Type X to Endpoint DATABig	Channels

Table 3. Content-Based Scenario Artifacts - *YourCompany* B2B : PartA
Artifact	Artifact Name	Description	Configured on page
Endpoint	RecFromA	Endpoint on which you expect to receive documents from PartnerA.	Endpoints
Transaction	Transaction DocY-to-DocX-to-DataSmall	Combination of the Source Channel DocY-to-DocX and the Target Channel DocX-to-DataSmall. It includes a filter that evaluates whether a propertyA is less Than 10. If a Document Type DocY matches this filter then it will be a transaction that receives DocY, maps it to and then sends it to the database DATASmall. This transaction has the From Partner set to PartA and the To Partner set to YourCompanyB2B.	Transaction Designer
Transaction	DocY-to-DocX-to-DataBig	This transaction is the combination of the Source Channel DocY-to-DocX and the Target Channel DocX-to-DataBig. It includes a filter that evaluates whether a propertyA is greater than or equal to 10. If a Document Type DocY matches this filter then it will be a transaction that receives DocY, maps it to and then sends it to the database DATABig. This transaction has the From Partner set to PartA and the To Partner set to YourCompanyB2B.	Transaction Designer

Figure 3. Content-Based Routing Routing Scenario Outcome, Route to DataSmall

PortX:

Receives DocY
Attempts to resolve routes
Finds two Transactions DocY-to-DocX-to-DataSmall and DocY-to-DocX-to-DataBig
Evaluates Filters
- Checks PropertyA for Value
- Finds PropertyA < 10
  - Executes that transaction, which maps the transaction to Document X
  - Sends Document X to Endpoint DATASmall.

Figure 4. Content-Based-Routing Routing Scenario Outcome, Route to DataBig

Integration Manager:

Integration Manager: