VPxM provides downloadable distributed messaging modules. Users can simply download these modules and plug them into their existing Web services environments. These modules serve as messaging agents for Web services servers and clients in a pluggable fashion, eliminating needs for application integrations.

VPxM Distributed Messaging Agents

There are three different messaging agents which collaboratively form the backbone of a virtual private messaging framework:

• VPxM Sender
  
  
  • As a messaging agent, the VPxM sender sends Web services requests on behalf of ordinary Web services clients. Along with the other VPxM messaging agents, it forms an essential part of the distributed messaging framework.
  
  
  • The sender has a built-in persistence engine and robust queue management system to enable reliable messaging. Equipped with its own digital key and certificate, the sender ensures secure message delivery to the destined recipients.
  
  
  • The sender should be configured on a secure network behind a firewall. An admin tool is available for configuration and administrative maintenance.


• VPxM Receiver
  
  
  • As the counterpart of the VPxM sender, the VPxM receiver receives Web services requests on behalf of ordinary Web services servers.
  
  
  • Like the senders, the receiver has a built-in persistence engine and robust queue management system for reliable messaging. Its digital key and certificate along with the sender's own set of key and certificate enable secure communications in between the two messaging agents.
  
  
  • The receiver should be configured on a secure network behind a firewall. An admin tool is also available.


• VPxM Connector
  
  
  • Senders and receivers do not communicate directly. The VPxM connector serves as the messaging broker in between the sender and the receiver. During the service activation of a receiver, a connector will be initialized via the receiver's admin tool.
  
  
  • This connector is the external partner agent of the receiver. It also ensures secure communications at the transport layer for the receiver and any authorized senders. In addition, the connector is responsible for messaging agent authentication upon transmission requests.
  
  
  • The connector requires a routable IP address. It's usually configured on a DMZ (De-Militarized Zone) or outside firewalls.