Onboarding a new tenant

Before you begin

Ensure that you have n Mid Tiers that are:

• Set up as a Tomcat cluster (see Configuring-a-cluster)
• Configured for SSO (see Getting started)

To onboard a tenant on the first mid tier in the cluster

1. Log on to Mid Tier Configuration Tool:
   • If the Mid Tier is installed on the local computer using the default context path, enter http://localHost/arsys/shared/config/config.jsp in your browser.
     
   • If the Mid Tier is not installed on the local computer, open a browser and enter the URL in the following format:
     http://hostName:portNumber/contextPath/shared/config/config.jsp
     • hostName is the name of the host computer for the Mid Tier.
     • portNumber is an optional port number; it is required if the web server is not using the default port (port 80).
     • contextPath is the path to the location of the Mid Tier in the Oracle JSP engine (arsys, by default).
2. When the Login page appears, enter the logon password for the Mid Tier Configuration Tool.
3. Click the Tenant Onboarding link.
4. (Optional) In the Centralized Configuration Server Settings page, shown in the following figure, configure the Centralized Configuration Server settings.
   For more information, see Configuring-the-AR-System-server-as-a-Centralized-Configuration-server. 
   
5. Click the Next step button or the Tenant AR Server tab.
   The AR Server Settings page opens:
   
6. Configure AR System servers that the mid tier uses:
   • Ensure that the Pre-load check box is selected. If you do not select this check box, the Preload button will not be available on the Cache Settings page.
   • Ensure that you enter the tenant virtual host name (for example, http://Tenant1.onbmc.com/contextPath ) in the Default Web Path and Email Notification Web Path fields in the Advanced tab of the Server Information form. The values of these fields are used in various IT Service Management workflows; therefore, you must enter the tenant-based URL in these fields so that customers receive the correct URL. For information about the Default Web Path and Email Notification Web Path fields, see Setting-performance-and-security-options .
7. Click the Next step button or the Tenant Creation tab.
   The Tenant Settings page opens, as shown in the following figure:
   
8. Add a new tenant with a name such as tenant1.
   Ensure that the tenant name does not contain any special character. 
9. (Optional) Select a tenant and click the Next Step button or the Tenant Configuration tab. 
10. In the Edit Tenant page, make changes to tenant-specific properties. 
11. Click the Preload New Tenant tab.
    The Cache Settings page opens.

12. Click Preload for the tenant AR System server.
    (The Preload button is not available if you did not select the Pre-load check box in the AR Server Settings page in step 6.)
    You will see that initially the status of the preload is shown as Not Running.

    Best practice
    We recommend that you perform a preload when your system has a lesser load and that you use the round-robin method to preload servers one at a time.

13. After the preload is completed, configure your load balancer to start sending requests to this tenant using the virtual host name.
    For example, the virtual host name of the tenant1 tenant can be http://tenant1.onbmc.com .
14. Verify whether the tenant is successfully added by logging on to the BMC Helix ITSM application, using the virtual host name of that tenant.

To onboard a tenant on the other Mid Tiers in the cluster

Perform the appropriate action:

• If the Centralized Configuration Server is not configured, perform all the steps in To onboard a tenant on the first mid tier in the cluster.
• If the Centralized Configuration Server is configured, review all the steps in To onboard a tenant on the first mid tier in the cluster and make changes, if required. 
  However, you must explicitly preload the tenant AR System server. For information, see Setting-up-a-cluster-with-multiple-tenants.