This documentation supports the 19.08 version of Remedy Action Request System.

To view an earlier version, select the version from the Product version menu.

Setting up BMC Remedy Smart Reporting as a cluster and onboard users

This topic describes the procedure to set up BMC Remedy Smart Reporting as a cluster. 

Consider the following points for installing BMC Remedy Smart Reporting in a clustered environment:

  1. Install primary BMC Remedy Smart Reporting server with a new or existing database.
  2. Install Secondary server with the database used by the primary node.
  3. Two types of clusters are available, Dynamic and Repository. The Dynamic cluster stores the node information in the memory, and the Repository cluster stores the node information in the centralized database. From version 18.08, the ClusterType parameter is set to Repository.

If you have already performed the Onboarding process before the installation of the secondary server, then do not install the secondary node with the same database. Instead, create a blank or dummy database for the secondary server installation. After the successful installation, change the secondary node database details. For more information, see  How To Change Smart Reporting Repository Database HostName On Existing Deployment.

The installation may overwrite the existing tables. Hence, BMC recommends installing the secondary node with a dummy database. If it is not possible to create a dummy database, then you can clone the primary server. 

Click to view a quick video for an example on setting up BMC Remedy Smart Reporting as a cluster.

  1. 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.

  2. Install the BMC Remedy Smart Reporting on each node.

  3. On each node update the web.xml file located at <SmartReportingInstallDir>/appserver/webapps/ROOT/WEB-INF:  

    1. 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>REPOSITORY</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>
      <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>
       <load-on-startup>11</load-on-startup>
      </servlet>

      Note

      If the AutoTaskDelegation parameter is set to true, the background tasks are automatically delegated to the next available node if the server goes down.

    2. 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>
    3.  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>
    4. Perform this step 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"/>

      proxyPort is the port of the LB (F5)


    5. (Only for Dynamic cluster type) Add the following lines of code to the catalina.sh file on a Linux system or the catalina.bat file on a Windows system:

      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"

      Note

      Ensure that the multi-cast IP Address that you specify is available and the multi-cast Port is listening.

  4. After the cluster is set up, on board the tenant.
    For more information, see  Onboarding users and importing content in Remedy Smart Reporting .  

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Andreas Wiencek

    There is an error in the web.xml excerpt.

    <param-value>b         
    REPORT_BROADCAST_BROADCASTTASK,
    

    With the "b" broadcast won't start.

    Jan 31, 2020 01:03
    1. Vrishali namdev Galinde

      Hello Andreas, Thank you for pointing this out. We have updated the documentation.

      Thanks & Regards, Vrishali

      Apr 02, 2020 12:16
  2. Brijesh Patel

    Section 3e - does it matter where in the .bat file we add the code? Looking at the bat file there are a number of labels, and the last one is ":end". Should we create a new label above it and add, or just put it under the ":end" label?

    May 02, 2020 06:51
    1. Vrishali namdev Galinde

      Hello Brijesh Patel,

      I need to check this with the R&D team. I shall get back to you on this soon.


      Thanks & Regards,

      Vrishali

      May 04, 2020 05:19
      1. Brijesh Patel

        Hi Vrishali,

        Any update on this?

        Jun 08, 2020 06:29
        1. Vrishali namdev Galinde

          Hello Brijesh Patel,

          Apologies for the delayed response. I checked with the R&D team. You need to add it just before the actual code begins.

          Please find below screenshot for the same:


          Hope this helps.


          Thanks & Regards,

          Vrishali

          Jun 08, 2020 06:45