Cross Tenant

Cross Tenant Nodes allow you to send messages from your Tenant to another Tenant in EchoStream or receive messages from other Tenants in EchoStream, without exiting the EchoStream Cloud.

Cross Tenant Nodes are implemented as a pair of Nodes. Cross Tenant Sending Nodes exist in the sending Tenant and are paired with a Cross Tenant Receiving Node in the receiving Tenant.

Why does EchoStream have Cross Tenant Nodes?

There are two primary use cases for sending messages between Tenants; tranferring messages between Tenants that you own, and transferring methods to a foriegn Tenant owner by a business partner.

Cross Tenant Nodes enable the simple and straightforward implementation of these use cases.

Transferring messages between your Tenants

For large organizations, the number of processing flows and that number of teams that have responsibility for those flows can also be large. While EchoStream puts no limits on the number of Nodes in a Tenant's processing network and through the use of directional graphing provides a powerful mechanism for managing those Nodes, at extreme scale this can become difficult for human beings to visualize and work with. Furthermore, any user in a Tenant (except the read_only users) has the ability to modify the Tenant's processing network, and a large organization may want to seperate concerns and responsiblitities more granularly than that.

For example, consider a large, multi-region Hospital Integrated Delivery Network (IDN). In this sort of business, each hospital has it's own processing requirements, each region has regional processing requirements, and the central office has centralized processing requirements. In this scenario, the IDN may choose to have a Tenant for each hospital/region/cental office, managed by personnel at each level. This provides for seperation of concerns and responsibilities. However, certain messages must be passed between these various Tenants to implement the overall integration of the IDN.

Cross Tenant Nodes allow the IDN to transfer selected messages between the Tenants within the IDN, once again without ever exiting the EchoStream Cloud.

Transferring messages to a foriegn Tenant

While you can transfer messages to/from a foriegn entity using an External Node or a Managed Node, this solution is sub-optimal if that foriegn entity also has a Tenant in EchoStream.

For example, consider a manufacturer that has several suppliers that provide raw materials to the manufacturing process. This manufacturer uses EDI to process orders to its suppliers, to receive and process invoices from its suppliers, and for many other business transactions with its suppliers. Likewise, the suppliers have some fairly significant processing requirements to manage the orders from and invoices to the manufacturer (and may supply multiple manufacturers).

If one or more of the suppliers also has an EchoStream Tenant, the manufacturer can transfer the EDI messages directly to that supplier's Tenant processing network via Cross Tenant Nodes, thereby eliminating the need for either side of the transaction to build custom integration servers.