In the Maximo Integration --> End point application, we can configure JMS Handlers.
The Java Messaging Service (JMS) handler is a Java component that consists of several properties.
The handler delivers XML data into a messaging system that is enabled through JMS. The system places messages in a virtual channel called a queue or topic, based on your defined messaging model.
In a single server environment, we can point the provider URL using the IIOP legacy format - iiop://localhost:1xxx . port is the BOOTSTRAP_ADDRESS of the application server.
In a clustered multiple server environment, we can set the provider url using flexible CORBA object URL - corbaloc::localhost:1xxx,:localhost:2xxx ; ports are the BOOTSTRAP_ADDRESSes of the individual application servers.
This information is not available in Maximo integration guide 7.1. Sometimes, pointing the provider URL to only one application server in clustered environment may lead to communication error when the configured single server is down or having issues.
We may get javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://localhost:xxxx". Make sure that any bootstrap address information in the URL is correct and that the target name server is running.
A bootstrap address with no port specification defaults to port xxxx. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=<IP>,port=XXXX vmcid: IBM minor code: E02 completed: No]
Reference: https://goo.gl/zqioXd
