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
Step | Action | Additional information |
---|---|---|
1 | 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. | |
2 | A copy of the cache is used to restore the cache if it becomes corrupted. | |
3 | Perform this step if you have installed BMC Atrium Single Sign-On as a High Availability (HA) cluster environment for multitenancy support. | |
4 | Perform the BMC Service Management Process Model (SMPM) configuration procedures. | |
5 | Configure the load balancer to ensure that the requests for the new tenant are diverted to the cluster. |
Related topics
Topic | Additional information |
---|---|
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 an extra BMC Remedy Mid Tier to the cluster. | |
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. | |
Configures the tenant server to work with the chat server. | |
Known and corrected issues | - |
Troubleshooting | - |
Comments
Log in or register to comment.