Default language.

Setting up a cluster with multiple tenants

You must set up a cluster with multiple tenants in the following circumstances:

  • Creating a new cluster environment
  • Migrating to a cluster environment 
  • Setting up new hardware
  • Testing a cluster for performance

You can also add global and local level configurations for the tenants. Local level configurations are applicable for a particular tenant in a cluster. Global level configurations are applicable for all tenants in a cluster. For more information about local and global level configurations, see Managing-AR-Server-Group-components-by-setting-global-level-and-local-level-configurations.

Before you begin

Ensure that the following prerequisites are met:

Best practices

  • Set the Maximum Heap Size property value based on the number of tenants. For example, if you are setting up a cluster with 8 tenants, ensure that the Maximum Heap Size is 6 GB for all the mid tiers in the cluster.
  • Change the arsystem.ehcache.referenceMaxElementsInMemory property value ( located at C:\Program Files\BMC Software\ARSystem\midtier\WEB-INF\classes\config.properties ) based on the number of tenants. For example, for 8 tenants, set the value of this property to 14000. For more information, see JVM runtime analysis in the BMC Remedy ITSM Deployment documentation.

To set up a cluster with multiple tenants

  1. Ensure that only one mid tier is up and running in the cluster.
  2. Enable preload for all Tenant AR Configuration servers on this mid tier.

  3. Start the preload for all Tenant AR Configuration servers by clicking the Preload button for each of the Tenant AR Configuration server on the Cache Settings page.

    Note

    Preload is a time-intensive process. It might approximately take an hour for the preload to complete for all tenants. For example, if you have 8 tenants, preload takes an hour to complete on all the tenants.

  4. Verify that the preload is completed successfully for all Tenant AR Configuration servers.
    preload_status.png

    Note

    If any one of preload statuses is Aborted, start preload again for that Tenant AR Configuration server by clicking the Preload button.

  5. Wait for the mid tier CPU to almost reach to 0%.
  6. Disable preload on all Tenant AR Configuration servers by clearing the Pre-load check box on the AR Server Settings > Edit AR Server page.

  7. Gracefully shut down Tomcat.

    Warning

    Do not kill the Tomcat process. As an example, for 8 tenants, it takes about 10 minutes to shut down Tomcat.

  8. Verify whether the shut down status shutdown_completed appears in the <midtierInstallation>/cache.lck file.
  9. Use the cache Backup utility to back up and restore the good cache on other mid tiers in the cluster.

Related topics

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*