 |
 |
 |
 |
|
|
 |
A Message Server client can use a Message Server cluster in the same way as a Standalone Message Server, except that the client is required to supply the URL of one of the running Message Server cluster nodes, as java.naming.provider.url property in the client's properties file/object, jndi.props. The jndi.props file is used to create an InitialContext while looking up administered objects.
If the client specifies the URL of only one node in the properties file, that node should be running when the client connects. There should be at least two nodes running for failover to occur. If the second node comes up after the client connects, the client will not have any information of this node and will not failover as the client gets informed of the participating nodes only while creating the IC.
The client can specify a composite URL: URLs of two or more Message Server cluster nodes separated by commas. This ensures fail-safe acquisition of ICs so that the client can connect to any running node. For example, rmi://192.168.1.29:2001, rmi://192.168.1.29:2002
Other properties are similar to those specified for a Standalone Message Server:
java.naming.factory.initial is com.pramati.naming.client.PramatiClientContextFactoryjava.naming.provider.url is the URLjava.naming.security.principal is <user-name>, and the default value is rootjava.naming.security.credentials is <password>, and the default value is pramaticom.pramati.naming.realm is <realm-name>, and the default realm is system
Related Topics:
 |
|
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |