Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Universal Messaging | Universal Messaging Enterprise Manager | Cluster Administration | Setting Up Inter-Realm Communication
 
Setting Up Inter-Realm Communication
 
Setting Up Non-Encrypted Inter-Realm Communication
Setting Up Encrypted Inter-Realm Communication
Switching from Non-Encrypted to Encrypted Inter-Realm Communication
Note on Public/Private Keys Used for Inter-Realm Handshake
Communication between realms can occur in various configurations:
*between realms in the same cluster.
*between realms in a zone.
*between realms in connected clusters.
The communication between realms can be secure (encrypted) or non-secure (non-encrypted). The communication is implemented by defining one or more interfaces on each realm. The required setup of the interfaces is the same, regardless of which of the above configurations you use for the communication between realms. For example, the attribute Allow for InterRealm must be activated on the interface that you use, otherwise the communication between realms is not possible.
The following description uses some examples from working with a cluster, but the principles apply to all configurations.
Since all realms in a cluster are required to have the same configuration (so that for example if the master realm goes offline, one of the other realms can become the new master), you must ensure that any interface definitions on one realm match the interface definitions on all other realms in the cluster.
For non-encrypted inter-realm communication, you can set up the interfaces to use either NSP (Socket Protocol) or NHP (HTTP Protocol). In general, we recommend you to use NSP rather than NHP for non-encrypted inter-realm communication.
For encrypted inter-realm communication, you can set up the interfaces to use either NSPS (Secure Socket Protocol) or NHPS (Secure HTTP Protocol). In general, we recommend you to use NSPS rather than NHPS for encrypted inter-realm communication.