1 / 12

ICX Remote Message Manager

ICX Remote Message Manager. Presented by Robert Zaremba. Requirements. 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

mirari
Download Presentation

ICX Remote Message Manager

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICX Remote Message Manager Presented by Robert Zaremba

  2. Requirements • 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

  3. Necessary Components • 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

  4. Java System Application Server 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

  5. Java Message Service (JMS) 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

  6. Java Naming and Directory Interface (JNDI) 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

  7. Java API for XML Web Services (JAX-WS) Java API for creating Web services Incorporates annotations to abstract away complex details Replacement for JAX-RPC, the former Java API for Web services.

  8. Initialization of Remote Communication • 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

  9. Initialization Document ID provided before communication is started Password provided before communication is started Security Token for use by the destination server IP Address ofRemoteMessageTransfer Web service Port of RemoteMessageTransfer Web service

  10. Returned Document Security Token for use by the originating server IP Address of RemoteMessageTransfer Web service Port of RemoteMessageTransfer Web service

  11. Message Transfer 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

  12. Status • 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

More Related