A Sample Oracle On Track High Availability Configuration

This appendix provides an example of installing Oracle On Track in a high availability configuration. This is one way of configuring the Oracle On Track cluster with Oracle WebLogic Server.

The appendix consists of the following sections:

• Requirements

• Installing Oracle On Track High Availability Configuration

Requirements

Before performing the procedure described in this appendix, ensure that you have performed the following:

• Install Oracle WebLogic Server on all the nodes.

• Ensure that you use the same operating system path on all nodes.

Installing Oracle On Track High Availability Configuration

The steps to install Oracle On Track High Availability Configuration are as follows:

1. Run config.sh on the first node. The Welcome screen opens. For more information, see Welcome.

2. Select the domain source. For more information, see Select Domain Source.

3. Specify the domain name and the location. For more information see Specify Domain Name and Location.

4. Configure administrator user name and password. For more information, see Configure Administrator User Name and Password.

5. Configure server start mode and JDK. Select Production Mode. For more information, see Configure Server Start Mode and JDK.

6. Configure the JDBC Component Schema. For more information, see Configure JDBC Component Schema.

7. Test the Component Schema. For more information, see Test Component Schema.

8. Select the optional configuration. You can either select Administration Server, Managed Servers, Clusters and Machines, and Deployments and Services.

9. Configure Managed Servers. Assign the following values:

   ontrack01 7003

   ontrack02 7004

10. Configure the clusters.

    Specify Name: OnTrackCluster

    Assign the servers to the clusters:

    ontrack01 OnTrackCluster

    ontrack02 OnTrackCluster

11. Configure the machines.

    Specify Names:

    machine01.us.oracle.com

    machine02.us.oracle.com

    Assign the servers to the machines:

    Admin Server

    machine01.us.oracle.com

    ontrack01

    machine01.us.oracle.com

    ontrack02

    machine02.us.oracle.com

12. Target Deployments to Clusters or Servers. For Oracle On Track Cluster, check Select All.

13. Target Services to Clusters on Servers. For Oracle On Track Cluster, check Select All. For Admin Server, check Select All.

14. Run config.sh on the remaining nodes. Select Create the Domain only. Fill in the database credentials.

15. Start servers on all the machines. Start the Admin Server. Start the Managed Server ontrack01. Start the Managed Server ontrack02.

Post-Installation Tasks

After installing Oracle On Track in the high availability configuration, perform the following steps:

1. Ensure that Node 1 is up and running.

2. Start the Admin Server.

3. Start the first Managed Server.

4. Enter the following commands using WLST:

   wls:/offline> connect();
   Please enter your username [weblogic] :weblogic
   Please enter your server URL [t3://localhost:443] :t3://  dc6170751.us.oracle.com:7003
   wls:/ontrack_domain/serverConfig> custom();
   wls:/ontrack_domain/custom> cd ('OnTrack(1.0.0.0).Configuration')
   wls:/ontrack_domain/custom/OnTrack(1.0.0.0).Configuration> cd ('OnTrack(1.0.0.0).Configuration:type=Cluster');
   wls:/ontrack_domain/custom/OnTrack(1.0.0.0).Configuration/OnTrack(1.0.0.0).Configuration:type=Cluster> ls();
   -rw-   waggle.server.backchannel.router.listen.addresses null
   -rw-   waggle.server.backchannel.router.peer.addresses null
   -rw-   waggle.server.object.cache.listen.addresses null
   -rw-   waggle.server.object.cache.peer.addresses null
   

   Note:

   When you enter the server URL, ensure that you connect to Managed Server and not Admin Server.

   Use the following format for port settings in the managed servers:

   <WLS ManagedServer Name>/<Network Bind Address>:<Port to Bind on>, <WLS ManagedServer Name>/<Network Bind Address>:<Port to Bind on>,...
   

   For example:

   -rw-   waggle.server.backchannel.router.listen.addressesOnTrack01/machine1:10100,OnTrack02/machine2:10101
   -rw-   waggle.server.backchannel.router.peer.addressesOnTrack01/machine1:10100,OnTrack02/machine2:10101
   -rw-   waggle.server.object.cache.listen.addresses  OnTrack01/machine1:10200,OnTrack02/machine2:10201
   -rw-   waggle.server.object.cache.peer.addresses    OnTrack01/machine2.us.oracle.com:10200,OnTrack02/adc6170612.us.oracle.com:10201
   

   To set the ports:

   set('waggle.server.backchannel.router.listen.addresses','OnTrack01/machine1:10100,OnTrack02/machine2:10101')
   

   Note:

   While setting the ports, note the following points:

   • For the listen settings, the address of the machine that matches the current one is unavailable. For the peer settings, the addresses of the machines that do not match the current address are unavailable.

   • In the listen settings, you can list a machine more than once. This might be of help in cases where the machine has multiple homes. In the peer settings, you can list a machine only once.