This documentation supports the 18.08 version of Remedy Deployment.

To view the latest version, select the version from the Product version menu.

Configuring the tenants for BMC Remedy ITSM shared services

This topic provides the onboard steps and configuration steps for the tenants for the BMC Remedy ITSM shared services.

To configure a tenant for BMC Remedy ITSM shared services

StepActionAdditional information

Onboard a new tenant on the BMC Remedy Mid Tier Open link

Onboard a new tenant on a BMC Remedy Mid Tier in the cluster. Configure the Enterprise centralized configuration server (ECCS) and provide the Cluster Identifier, add the tenant AR server, and edit the tenant-specific properties for the BMC Remedy Mid Tier. For all other BMC Remedy Mid Tier instances in the cluster, configure only the ECCS, and provide the same Cluster Identifier as used for the first BMC Remedy Mid Tier. The Cluster Identifier must be unique.

Create a good cache and back up the Mid Tier cache Open link

A copy of the cache is used to restore the cache if it becomes corrupted.

(Optional) Configure BMC Atrium Single Sign-On for new Tenant Open link

Perform this step if you have installed BMC Atrium Single Sign-On as a High Availability (HA) cluster environment for multitenancy support.


Configuring SMPM for a tenant Open link

Perform the BMC Service Management Process Model (SMPM) configuration procedures. 

Configuring a hardware load balancer with BMC Remedy AR System Open link

Configure the load balancer to ensure that the requests for the new tenant are diverted to the cluster.  

 Related topics

TopicAdditional information

Configuring the mid tier for multitenancy Open link

Multitenancy for BMC Remedy Mid Tier is implemented by first adding the tenants to the BMC Remedy Mid Tier and then configuring the tenant-specific properties.   

Adding (n+1)th BMC Remedy Mid Tier to the cluster Open link

Adding an extra BMC Remedy Mid Tier to the cluster.

Offboarding a tenant Open link

A tenant in BMC Remedy Mid Tier cluster is offboard, if a tenant needs to be moved from a cluster or is unsubscribed from the environment.

Configuring chat Open link

Configures the tenant server to work with the chat server.
Known and corrected issues
Troubleshooting -
Was this page helpful? Yes No Submitting... Thank you