This Plexus Message Broker solution features the following technology: legacy protocols, message format translation, and Web Services. This solution’s site and Plexus Message Broker configurations touch on these features below.
As illustrated below, this site has a single physical server that contains a single instance of the Plexus Message Broker. The site maintains a hot standby of the physical server.
As with all Plexus Message Broker installations, adding physical servers, increasing Plexus Message Brokers instances per physical server, or transitioning to run the Plexus Message Broker in a virtual machine (VM) environment is only a matter of installation and configuration. No other Plexus Message Broker modifications are necessary. Resources are typically added for performance reasons, local redundancy reasons, or both.
Plexus Message Broker Configuration
As illustrated below, this site maintains a single physical server that contains a single instance of the Plexus Message Broker. The Plexus Message Broker consists of a Request (To Nlets) Message Server and a Response (From Nlets) Message Server.
Plexus Message Server Functions
|To Nlets||Receives a proprietary TCP request from the State Switch; retrieves the message; wraps the message in a Web Services format; and sends the message to Nlets via a Web Services call.|
|From Nlets||Receives a Web Services call from Nlets; unwraps the message; establishes a proprietary TCP protocol connection with the State Switch; and send the message to the switch via the TCP connection.|