There are two ways to configure failover between two Naming Services:

• Configure a second Naming Service into your IAS installation.
• Install a second IAS and configure the Naming Service in one IAS as the master and, in the second IAS, configure it as the slave.

Configuring a second Naming Service into your IAS installation

1. Create a second Naming Service. See "Creating a new Container" in chapter 3 of the IAS User's Guide. This shows how to create a second EJB Container; use similar steps and create an additional Naming Service.
2. Give the two Naming Service configurations suitably different service.name (and service.description) values.
3. Set both Naming Services to be out-of-process due to their use of vbroker.se.iiop_tp.scm.iiop_tp.listener.port with different values.
4. List both Naming Services in the three services.* properties in server.properties.

To install a second IAS and configure master and slave Naming Services

You will have to rename the Naming Service in either the master or the slave so you have two unique names. You will also need to disable the JDataStore in one of the servers. See the steps that follow.

1. Set an adequate service.startup.delay in jdatastoreservice/service.properties.This ensures the server doesn't move on to start the Naming Service before the JDataStore is ready.
2. Set an "adequate" service.startup.service_ready.max_wait in service.properties for both Naming Services. This timeout is when the server gives up waiting for the Naming Service to be ready for work. If the service is ready before the timeout, the server moves on; otherwise, the server only moves on at the timeout. The timeout occurring does not cause the server to stop or otherwise control the service. It just means the server moves on to the next startup task.

Note: We used 20000 (20 seconds) on our P400 NT testing.

3. Set the vbroker.properties so that the Naming Services are properly configured.

Note: You are using InMemory. Failover only works with a real backing store (which is shared by the master and slave Naming Services). We have provided details here for using JDataStore as the backing store.


    vbroker.naming.enableSlave=1
    vbroker.naming.masterHost=IP_address
    vbroker.naming.masterPort=18001
    vbroker.naming.slaveHost=IP_address
    vbroker.naming.slavePort=18002
    # These two are the names of the naming services you have configured
    vbroker.naming.masterServer=namingservice_master
    vbroker.naming.slaveServer=namingservice_slave

    vbroker.naming.backingStoreType=JDBC
    vbroker.naming.poolSize=5
    vbroker.naming.jdbcDriver=com.borland.datastore.jdbc.DataStoreDriver
    vbroker.naming.loginName=VisiNaming
    vbroker.naming.loginPwd=
    vbroker.naming.jdsSvrPort=2508
    # Change localhost if you're using two servers on different machines.
    vbroker.naming.url=jdbc:borland:dsremote://localhost/adm/datastore/namingDB.
    jds

4. Set javaservice.properties for each naming service, where port is the appropriate port for the master and slave as configured in vbroker.properties.

       javaservice.jvm.arguments=-Dvbroker.se.iiop_tp.scm.iiop_tp.listener.port=port