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:

Install primary BMC Remedy Smart Reporting server with a new or existing database.
Install Secondary server with the database used by the primary node.

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.

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.
Install the BMC Remedy Smart Reporting on each node.

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. Additionally, if the AutoTaskDelegation parameter is set to true, the background tasks are automatically delegated to the next available node if the server goes down.

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 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)

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.

After the cluster is set up, on board the tenant.
For more information, see Onboarding users and importing content in BMC Remedy Smart Reporting .
&lt;p&gt;&lt;br/&gt;&lt;/p&gt;

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

Comments