Remedy Smart Reporting deployment

You can deploy Remedy Reporting in the following ways:

Best practice
Consider the following best practices for on-premises deployments of Remedy Smart Reporting.

It is recommended that you install Remedy Smart Reporting on a separate server for better performance.
Though you can deploy Remedy Smart Reporting in different ways, BMC recommends you to deploy Remedy Smart Reporting in an environment where data is fetched from replicated Action Request System (AR System) database.
- For 9.1.00 Service Pack 2 or later, use the read-only replicated AR System database.
- For releases older than 9.1.00 Service Pack 2, you must apply the hotfix to use the replicated AR System database. Contact BMC Support to obtain the hotfix.

Deploying in a standalone environment where data is fetched from the AR System production database

When you have a standalone deployment of Remedy Smart Reporting that fetches data from the AR System production database:

Remedy Smart Reporting is deployed on a separate Tomcat cluster.
Remedy Smart Reporting uses a database that is different from AR System database.

The following diagram illustrates the deployment model.

Remedy Smart Reporting uses Smart Reporting database for its own data and metadata.

Deploying in a standalone environment where data is fetched from the replicated AR System database

When you deploy Remedy Smart Reporting that fetches data from the replicated AR System database:

Remedy Smart Reporting is deployed on a separate Tomcat cluster.
Remedy AR System production database is replicated and used for reporting.
Remedy Smart Reporting uses a separate database which is different from AR System production and AR System replicated databases. Remedy Smart Reporting database must always be in read and write mode.

Note:

For releases older than 9.1.00 Service Pack 2: To use the replicated AR database, you must apply the hotfix. Contact BMC Support to obtain the hotfix.
For 9.1.00 Service Pack 2 or later: Remedy AR System Server supports a read-only replicated database for reporting operations.
- This enhancement is useful if you want the AR production data to be unaffected but allow Remedy Smart Reporting users to continue with the reporting operations.
- Remedy Smart Reporting users connect with the read-only replicated AR database.
- To avoid license update related issues, you must perform the user onboarding process by connecting with the AR production database. After completing the onboarding process, connect your AR System data source with read-only replicated AR database. For instructions, see Installing-BMC-Remedy-Smart-Reporting.

Remedy AR System components are deployed on the replicated Remedy AR System server.
The following video demonstrates the deployment method for Remedy Smart Reporting in which reports and dashboard data is fetched from replicated read-only AR System database.

The following diagram illustrates the deployment model.

BMC suggests you to keep the AR System server consumed by Remedy Smart Reporting separate. Do not include it in the server group consumed by production environment.

Deploying on the same Remedy AR System server

Note

This deployment method must be considered only for testing purpose. Do not deploy Remedy Smart Reporting on the same AR System server in the production environment.

When you deploy Remedy Smart Reporting in a Remedy AR System environment:

You don't need a separate environment for Remedy Smart Reporting.

Install a different Tomcat to deploy Remedy Smart Reporting. For more information, see Preparing-your-web-server.

Deploying Remedy Smart Reporting in a cluster

You can cluster Remedy Smart Reporting on multiple servers to support high availability and load balancing. You can load balance with a hardware load balancer or load balancing software.

The load balancing infrastructure must deliver network traffic to the Remedy Smart Reporting application server transparently—as if the packets were connecting directly to the application server. If Session Replication is not enabled, the load-balancing infrastructure must provide “sticky-session” functionality. This is where traffic for a user’s session is sent to the same node for the duration of their session.

For more information, see Setting up BMC Remedy Smart Reporting as a cluster and onboard tenant in Remedy AR System documentation.