Clustering › How to Set Up Vertical Clustering for Service View › Updates Made Automatically When You Set Up a Cluster › New Windows Service

New Windows Service

Running the ant command to create a Service View cluster automatically creates a Windows service, as follows:

• Creates a folder named viewn and a new Windows service named CA Service Viewn. For both the folder name and service name, the number n is copied from the view.node.id=number parameter in the cluster.properties file.

  For example, when you first run this command, suppose you specify view.node.id=1 in the cluster.properties file. In that case, the command creates a folder named view1 and a new Windows service named CA Service View1.

  Similarly, when you run this command for the second time, suppose you specify view.node.id=2 in the cluster.properties file. In that case, the command creates a folder named view2 and a new Windows service named CA Service View2.

  Likewise, when you update the file again and run this command again each successive time, it creates the folder and service, and names them accordingly.

• Runs the following command in %USM_HOME%\View\bin:

  viewservice.bat -i
  

  The new Windows Service named CA Service Viewnumber is created, where number is the same as the view.node.id=number parameter in the cluster.properties file.

  A sample service name is CA Service View3.

• Opens the viewservice.bat file and specifies the path name to the viewservice.conf for the new service.
• Starts the new service.

  This action creates a log file named tomcat_viewnumber.log in the folder named %USM_HOME%\logs\view_logs. The number is the same as the view.node.id=number parameter in the cluster.properties file. A sample file name is tomcat_view3.log.

Note: To remove the CA Service Viewn service, enter the command: viewservice.bat –r.

Verify the Server.xml Files

Verifying the server.xml files is a required task when you set up a cluster.

To verify the server.xml files

1. Review the updates made by the ant command, especially the updates to the server.xml file.
2. Open each server.xml file and perform the remaining steps.
3. Locate the following line and verify that the file specifies a unique jvm route name:

   <Engine name="Standalone" defaultHost="localhost" debug="0" jvmRoute="_hostname_{usmviewnumber|cawfnumber}">
   

4. Update the jvm route name to a unique value, if any other server.xml file specifies the same value.
5. Locate the following lines and verify that the file specifies a unique tcplisten port number:

   <Receiver
                   className="org.apache.catalina.cluster.tcp.ReplicationListener"
                   tcpListenAddress="auto"
                   tcpListenPort="4002"
                   tcpSelectorTimeout="100"
                   tcpThreadCount="6"/>	<Receiver
   

6. Update the tcplisten port number to a unique value, if any other server.xml file specifies the same value.

You have verified the server.xml files.