Presented by Robert Zaremba

 Remote messages must be sent to a message queue so that components are decoupled  Both sides of a communication must be able to receive messages asynchronously, so both sides must be able to act as servers  Messages may contain confidential information so security is a concern

 Application Server Hosts the Web services as well as other components  Message Service Provides the message queues that will be used to hold incoming and outgoing messages  Component Directory Facilitates loose coupling between components such as Web services and message queues

 Developed by Sun Microsystems and donated to Project Glassfish  Delivers server-side Java applications and Web services  Needs to be installed on the machines of all parties that must receive messages

 Provides a queue that can be used to store messages  A connection factory, used to provide access to the service, can be accessed through a component discovery service  An implementation is included in the Java System Application Server

 Stores objects or references to objects according to names  Allows for the decoupling of system components  An implementation is included in the Java System Application Server

 Java API for creating Web services  Incorporates annotations to abstract away complex details  Replacement for JAX-RPC, the former Java API for Web services.

 A simple XML document is transferred to the remote server via the InitializeCommunication Web service  The XML document provides the information needed to add the originator’s RemoteMessageTransfer Web service to the destination’s JDNI for later use  An XML document is returned from the InitializeCommunication Web service invocation which allows for the originator to add the destination’s RemoteMessageTransfer Web service into its own JDNI  A security token as well as an ID and password are included in the initialization document and a security token is included in the return document

 ID provided before communication is started  Password provided before communication is started  Security Token for use by the destination server  IP Address of RemoteMessageTransfer Web service  Port of RemoteMessageTransfer Web service

 Security Token for use by the originating server  IP Address of RemoteMessageTransfer Web service  Port of RemoteMessageTransfer Web service

 If a message must be sent to a remote IC system then the IC manager looks up the RemoteMessageTransfer Web service in the JDNI and then invokes that service  The actual message is passed in XML format as a parameter in the RemoteMessageTransfer Web service invocation

 The Web services have been created and deployed to the Java System Application Server  Currently messages that are passed via the RemoteMessageTransfer Web service are sent to standard output  The JMS and JNDI have not been configured properly as of yet  Security has not been implemented