Configuring BMC Remedy Mid Tier as a shared service
This topic provides the configuration steps for BMC Remedy Mid Tier as a shared service so that the multitenant mid tier can serve requests from multiple customers.
Before you perform the configuration steps for BMC Remedy Mid Tier as a shared service:
- Set up the enterprise centralized configuration server or servers.
- Create a BMC Remedy Mid Tier cluster.
- Install tenants or upgrade the platform components for the existing tenants.
To configure the mid tier as a shared service
Add the first tenant to the cluster by onboarding a new tenant on a BMC Remedy Mid Tier
Onboard a new tenant on a BMC Remedy Mid Tier in the cluster. Configure the 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 Tiers in the cluster, only configure the ECCS and provide the Cluster Identifier that is the same as for the first BMC Remedy Mid Tier. The Cluster Identifier for the cluster should be unique.
|2||Create a good cache and back up the Mid Tier cache||A copy of the cache is used to restore the cache if it gets corrupted.|
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||Configuring the load balancer||Configure the load balancer to ensure that the user requests for the new tenant are diverted to this cluster. Test the cluster and provide access to the new tenant.|
|6||Add the remaining tenants||Add the remaining tenants to the cluster one by one by following steps 4 through 8.|
|7||(Optional) Add (n+1)th BMC Remedy Mid Tier to the cluster|
If required, add an extra BMC Remedy Mid Tier to the cluster.
|8||(Optional) Offboarding a tenant on a BMC Remedy Mid Tier cluster|
If a tenant needs to be moved from a cluster or is unsubscribed from the environment, offboard the tenant.