Creating a "One-Way" Cluster Gateway
Organizations might often want to create what is known informally as a "one-way" cluster gateway, meaning that they might want documents to flow only in one direction. For example, a cluster that handles employee-related documents might want to broadcast certain documents to, but never receive documents from, a cluster that handles customer support documents.
To create this type of cluster gateway, you must create a complete cluster gateway (that is, you must create and configure both cluster gateways in the cluster gateway pair). Creating a one-way cluster gateway does not mean that you create only one side of a cluster gateway connection. To achieve the "one-way" nature of this type of connection, you must configure the permission settings on each cluster gateway to restrict the flow of documents to one direction.
For example, if you want to limit the flow of documents from the employee cluster (EMP) to the customer support cluster (CUST), you would set permissions as follows:
On cluster gateway EMP>CUST:
Assign this permission... | To... |
Allow Forward | All document types that are permitted to travel to the CUST. |
Allow Receive | None. |
On cluster gateway CUST>EMP:
Assign this permission... | To... |
Allow Forward | None. |
Allow Receive | All document types that the EMP cluster will forward to this cluster (CUST), with restrictive filters, if necessary. |