Installation Guide › Server Installation › Report Server › High Availability Report Server

High Availability Report Server

To support a high availability report server, this chapter describes installing CA Business Intelligence on Linux platform using Apache Tomcat as the application server. The Apache HTTP Server is used as a load balancer. See the following diagram for details on this architecture.

Prerequisites

Complete the following prerequisites:

1. Install the required Linux prerequisite patches to install CA Business Intelligence on System3 and System4.
2. Install the required Linux prerequisite patches to install Oracle Client on System3 and System4.
3. Install the required Linux prerequisite patches to install Oracle Server on System1.
4. Make sure NFS Server is installed on System2.
5. Make sure NFS Client is installed on System3 and System4.

System1 (Database Server)

Install the Oracle server and create two databases, one for CMS and one for Auditing. See the Oracle documentation for instructions on how to install Oracle on Linux and how to create databases on Linux after installing Oracle.

System2 (File Repository Server)

Perform the following steps on the File Repository Server system to configure and to start the NFS Server.

1. Log in to the system as root.
2. Open a terminal window and execute the following command:

   service nfs start 
   service nfs status
   mkdir -p /home/nfs/cabi 
   useradd -s /bin/bash cabiuser
   chown cabiuser /home/nfs/cabi
   id cabiuser 
   

3. Reflect the cabiuser id and gid in the following line:

   append /home/nfs/cabi System*(rw,all_squash,anonuid=501,anongid=501) to /etc/exports file
   exportfs -a
   showmount -e System2
   su cabiuser
   mkdir frsinput frsoutput 
   

System3

1. Install the Oracle client.
2. Create a non-root user with the name cabiuser.

   This non-root user creation is mandatory to install CA Business Intelligence on Linux.

3. Create a group with the name cabiuser.
4. Add this user to group cabiuser.
5. Install CA Business Intelligence as follows:
   1. Use the New install option.
   2. Provide the System1 database details in the CMS and Audit DB section.
   3. Choose Tomcat as application server.

   See the CA Business Intelligence implementation guide for more information about the installation process.

Once the installation is complete, make sure that you are able to log in to CMC through the web URL.

http://System3:8080/CmcApp

System 4

1. Install the Oracle client.
2. Create a non-root user with the name cabiuser.
3. Create a group with the name cabiuser.
4. Add this user to group cabiuser.
5. Install CA Business Intelligence as follows:
   1. Choose the Custom or Expand Install option. In the next screen, clear MySQL from Server Components to make this server the second node in the cluster.
   2. Provide the System 3 details as the primary CMS in the next screen.
   3. Provide the System1 database details in the CMS and Audit DB section.
   4. Choose Tomcat as application server.

   See the CA Business Intelligence implementation guide for more information about the installation process.

Make sure that you can log in to the CMC through the web URL:

http://System4:8080/CmcApp

Setup NFS client on both CA Business Intelligence systems:

Perform the following steps on both CA Business Intelligence systems (System3 and System4) to set up the NFS client, which is required to access a shared location in the file repository server.

1. Log in as root.
2. Open a terminal window and execute the following:

   mkdir -p /home/nfs/cabi 
   

   useradd -s /bin/bash -m cabiuser
   

   chown cabiuser /home/nfs/cabi
   

   add bansr02-I53529:/home/nfs/cabi /home/nfs/cabi nfs defaults 0 0 to /etc/fstab
   

   mount -a 
   

   mount
   

   su -cabiuser
   

   cd /home/nfs/cabi
   

   touch a
   

   rm a
   

   ls -alrt
   

   cd /opt/CA/SharedComponents/CommonReporting3/bobje
   

   ./stopservers
   cd data/frsinput
   cp -r * /home/nfs/cabi/frsinput
   cd ../frsoutput
   cp -r * /home/nfs/cabi/frsoutput
   cd ../..
   ./startservers
   ./ccm.sh -disable all -username Administrator -password adminpassword
   

After completing the preceding steps on any system, perform the following steps:

1. Log in to the CMC URL as Administrator.
2. Click Servers, Core Services and double click System3.InputFileRepository.
3. In the Input FileStore Service section, set /home/nfs/cabi/frsinput to File Store Directory and /home/nfs/cabi/frsinput/temp to Temporary Directory.
4. Do the similar activity for Output FileStore Service.
5. Restart the services.
6. Run this command in terminal as a cabiuser ./ccm.sh –enable all –username Administrator –password adminpassword

System 5

Perform the following steps to configure nodes in the cluster environment on the load balancer server (System5) as a root user. Be sure that the Apache httpd server is installed.

1. Login as a root and open terminal.
2. /etc/init.d/httpd start
3. View the test page at http://system5/
4. Change directory to /etc/httpd.
5. Go to the CA Support site to obtain the mod_jk.so file.
6. Copy the mod_jk.so file to the modules folder.
7. Insert the following lines in the conf/httpd.conf file before the Listen 80 line.

   LoadModule jk_module /etc/httpd/modules/mod_jk.so
   JkWorkersFile "/etc/httpd/conf/workers.properties"
   JkMountFile conf/uriworkermap.properties
   JkMount /servlet/* balancer
   JkMount /*.jsp balancer
   JkMount /jkmanager/* jkstatus
   

8. Create a conf/worker.properties file with following contents:

   worker.list=balancer,jkstatus
   worker.jkstatus.type=status
   
   worker.worker1.port=8009
   worker.worker1.host=System3
   worker.worker1.type=ajp13
   worker.worker1.lbfactor=1
   
   worker.worker2.port=8009
   worker.worker2.host=System4
   worker.worker2.type=ajp13
   worker.worker2.lbfactor=1
   
   worker.balancer.type=lb
   worker.balancer.balance_workers=worker1,worker2
   worker.balancer.sticky_session=true
   

9. Create conf/uriworkermap.properties file with the following contents:

   /jmx-console=balancer
   /jmx-console/*=balancer
   /web-console=balancer
   /web-console/*=balancer
   /*=balancer
   /=balancer
   /etc/init.d/httpd stop
   /etc/init.d/httpd start
   

Load balancing configuration on both CA Business Intelligence systems:

Configure both nodes in the cluster to accept requests from the load balancer server. Perform the following steps in CA Business Intelligence servers (System3 and System4).

Open /opt/CA/SharedComponents/CommonReporting3/bobje/tomcat/conf/server.xml.

1. Comment out all Connector tags and add the following line:

   <Connector port="8009" enableLookups="false" redirectPort="8443" tomcatAuthentication="false" maxThreads="400" minSpareThreads="25" maxSpareThreads="100" protocol="AJP/1.3" />
   

   An Engine tag exists below this line. Append the extra attribute jvmRoute="worker1" to this tag. (In the second CABI server, make the value"worker2").

2. Restart servers on both Report Server systems.
3. Restart the HTTP server in the load balancer.

Now you can access CMC using the following URL:

http://system5/CmcApp

You can also access Infoview using the following URL:

http://system5/InfoViewApp