Skip Headers

# Configuring RMI Registry Naming Service Information

Previous

Next

The session's message transport service uses a naming service when it looks up connections to other sessions in the coordinated cache. If you choose to use an RMI registry naming service, you can configure RMI registry naming service options.

Table: Coordinated Cache Support for JNDI Naming Service Configuration summarizes which coordinated caches support RMI registry naming service configuration.

Coordinated Cache Support for RMI Registry Naming Service Configuration

Coordinated Cache | Using TopLink Workbench | Using Java
--- | --- | ---
JMS Coordinated Cache |  |
RMI Coordinated Cache |  |
CORBA Coordinated Cache |  |
Custom Coordinated Cache |  |

For an RMI coordinated cache, when a particular session's coordinated cache starts up, the session binds its connection in its RMI registry, creates an announcement message (that includes its own naming service information), and broadcasts the announcement to its multicast group (see "Configuring a Multicast Group Address" and "Configuring a Multicast Port"). When a session that belongs to the same multicast group receives this announcement, it uses the JNDI naming service information in the announcement message to establish bidirectional connections with the newly announced session's coordinated cache. The coordinated cache is ready when all participating sessions are interconnected in this way, at which point, sessions can start sending and receiving object change messages. You can then configure each session with RMI registry naming information that identifies the host on which the session is deployed.