Configure High Availability with CA Business Intelligence

High Availability (HA) is the ability for the system to continue functioning after the failure of one or more of the servers. A part of High Availability is failover. Failover is the ability for user connections to migrate from one server to another. If there is a server failure, the user applications can continue to operate. Enabling High Availability (HA) helps achieve load balancing, failover, and scalability features. cabi JasperReports® Server uses an HTTP Server. As a result, the failover occurs for e-node and the load balancer or router is appropriate for HTTP Server-based application. For more information, see the CA Business Intelligence documentation.
capm350
High Availability (HA) is the ability for the system to continue functioning after the failure of one or more of the servers. A part of High Availability is failover. Failover is the ability for user connections to migrate from one server to another. If there is a server failure, the user applications can continue to operate. Enabling High Availability (HA) helps achieve load balancing, failover, and scalability features.
CA Business Intelligence
 JasperReports® Server uses an HTTP Server. As a result, the failover occurs for e-node and the load balancer or router is appropriate for HTTP Server-based application. For more information, see the CA Business Intelligence documentation.
Enable User Synchronization in a CABI HA Environment
If you have HA configured for CABI, the integration with 
CA Performance Management
 requires you to configure user synchronization.
Follow these steps:
  1. Install Tomcat on the host where the load balancer installed.
  2. Stop Tomcat and the Apache web server (httpd).
  3. Add the following line to the
    tomcat_home_directory
    /conf/server.xml
    file to enable the AJP 1.3 connector on port 8009:
    <Connector port="8009" protocol="AJP/1.3"/>
  4. Copy the CABISync.war file to the
    tomcat_home_directory
    /webapps
     directory.
  5. Modify the
    apache_web_server_directory
    /conf/workers.properties 
    file as follows:
    worker.list=loadbalancer,status,sync_listaner 
    worker.node1.port=8009 
    worker.node1.host=node1's server name/ip address
    worker.node1.type=ajp13
    worker.node1.lbfactor=1 
    worker.node2.port=8009 
    worker.node2.host=node2's server name/ip address 
    worker.node2.type=ajp13 
    worker.node2.lbfactor=1 
    worker.loadbalancer.type=lb 
    worker.loadbalancer.balance_workers=node1,node2 
    worker.loadbalancer.sticky_session=1 
    worker.status.type=status
    worker.sync_listaner.type=ajp13
    worker.sync_listaner.port=8009
    worker.sync_listaner.host=localhost
  6. Modify the
    apache_web_server_directory
    /conf/mod-jk.conf
    file as follows:
    LoadModule jk_module modules/mod_jk.so 
    JkWorkersFile conf/workers.properties 
    JkLogFile logs/mod_jk.log 
    JkLogLevel info 
    JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" 
    JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories 
    JkRequestLogFormat "%w %V %T" 
    JkMount /
    <application-name>
    loadbalancer 
    JkMount /
    <application-name>
    /* loadbalancer
    Jkmount /CABISync sync_listaner
    Jkmount /CABISync/* sync_listaner
    JkShmFile logs/jk.shm 
    <Location /jkstatus> 
    JkMount status 
    Order deny,allow 
    Allow from all 
    </Location>
    • <application-name>
      The name of CABI application, usually "
      jasperserver-pro
      "
8. Start Tomcat and the Apache web server.