Remedy Smart Reporting - How to configure in cluster/ load balancer

Version 5
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    ITSM In-App Reporting 9.1.00


    APPLIES TO:

    BMC Remedy Smart Reporting 9.0\9.1.x



    QUESTION:

    What are the steps to configure cluster/load balancer for Remedy Smart Reporting?


    ANSWER:

     

       
       To set up BMC Remedy Smart Reporting as a cluster (Tomcat only), perform the following steps:  
       

    Note:

       
        
    • Before you configure the cluster, ensure that all the severs in cluster are in same time zone and are in sync.
    •   
    •  Also, ensure that BMC Remedy Smart Reporting is installed on all the nodes pointing to primary node repository.
    •  
      
      
       
    1. Install the BMC Remedy Smart Reporting on each node.
    2.  
    3. On each node update the web.xml file located at <SmartReportingInstallDir>/appserver/webapps/ROOT/WEB-INF:
      
       
    • Update and add the following:
      
       
    <!-- Cluster Management --><servlet><servlet-name>ClusterManagement</servlet-name> <servlet-class>com.hof.mi.servlet.ClusterManagement</servlet-class> <init-param>            <param-name>ClusterType</param-name>            <param-value>DYNAMIC</param-value> </init-param> <init-param>            <param-name>SerialiseWebserviceSessions</param-name>            <param-value>true</param-value> </init-param> <init-param>            <param-name>CheckSumRows</param-name>            <param-value>true</param-value> </init-param> <init-param>            <param-name>EncryptSessionId</param-name>            <param-value>true</param-value> </init-param> <init-param>            <param-name>EncryptSessionData</param-name>            <param-value>true</param-value> </init-param> <init-param>            <param-name>AutoTaskDelegation</param-name>            <param-value>true</param-value> </init-param> <load-on-startup>11</load-on-startup></servlet>
        

    If you are upgrading to Remedy Smart Reporting version 19.02, then in the web.xml file,  under Cluster Management, add the following code:
     

       
    <init-param>           <param-name>TaskTypes</param-name>           <param-value>         REPORT_BROADCAST_BROADCASTTASK,  FILTER_CACHE,    REPORT_BROADCAST_MIREPORTTASK,       SOURCE_FILTER_REFRESH,  SOURCE_FILTER_UPDATE_REMINDER,  ORGREF_CODE_REFRESH,  THIRD_PARTY_AUTORUN       </param-value> </init-param> <init-param>     <param-name>MaxParallelTaskCounts</param-name>  <param-value>              5,          5,  5,  5,  5,            5,  5  </param-value> </init-param>
        
        
    • On the MIStartup Servlet block, update the following: 
    •  
       
    <init-param>        <param-name>DisableTaskScheduler</param-name>        <param-value>TRUE</param-value> </init-param>
       

    Note: In a clustered environment, each Smart Reporting node is configured by default to run background tasks that also includes publishing reports. This could result in sending the reports multiple times. Thus, it is recommended that you enable the background tasks on only one node. You can do this by changing the param-value to FALSE and save the web.xml file.

       
        
    • Comment the following: 
    •  
       
    <servlet>              <servlet-name>SystemTaskManager</servlet-name>             <servlet-class>com.hof.servlet.SystemTaskManager</servlet-class>             <load-on-startup>8</load-on-startup> </servlet>
       
        
    • Add <distributable/> tag. The following is a sample snippet:
    •  
       
    <web-app>             <distributable/>              <!-- System Event and Debug classes -->             <listener>                         <listener-class>com.hof.servlet.SysSessionListener</listener-class>                               </listener>
       
        
    • Perform below steps if HTTPS traffic is offloaded at Load Balancer and Smart Reporting is configured to run on HTTP:
    •  
       
       In the     server.xml file (Tomcat configuration file), set the HTTP Connector     proxyPort and     scheme to the values displayed in the following code snippet. The path of     server.xml file is     <AR Installation Path>\SmartReporting\appserver\conf\server.xml  
         
    <Connector  port="8080" protocol="HTTP/1.1" connectionTimeout="20000" proxyPort="443" scheme="https" disableUploadTimeout="true"/>
         Note: proxyPort is the port of the LB (F5)  
         
         
    • Add the following lines of code to the catalina.sh file:
    •   
         
    JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" JAVA_OPTS="$JAVA_OPTS -Djgroups.udp.mcast_addr=<multi-cast IP Address>" JAVA_OPTS="$JAVA_OPTS -Djgroups.udp.mcast_port=<multi-cast Port>" Example: JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" JAVA_OPTS="$JAVA_OPTS -Djgroups.udp.mcast_addr=228.0.0.5" JAVA_OPTS="$JAVA_OPTS -Djgroups.udp.mcast_port=5555"
        
         
    • After the cluster is set up, on board the tenant. 
    •   
       
      

     


    Article Number:

    000120703


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles