Adding tenants and setting the AR System server for authentication
To configure the for multitenancy, first add tenants to the and then configure the tenant-specific properties.
To add a tenant
- In a browser, open the Remedy Mid Tier Configuration Tool at http://hostname:portnumber/arsys/shared/config/config.jsp.
- Click the Tenant Settings link.
- On the Tenant Settings page, click Add Tenant.
- On the Add New Tenant page, enter the following information.
- In the Tenant Name field, enter the name of the tenant (for example, Tenant1).
In the Virtual Host Name field, enter the virtual name of the host (for example, Tenant1.bmc.com).
You must map this virtual host name with the pool name in the f5 load balancer. For more information, see F5-load-balancer-sample-configuration-in-AR-System.
- In the Web Reports Base URL field, enter the base URL (for example, https://Tenant1.onbmc.com:8080/).
- (Optional) From the Tenant Configuration Server list, select an as your configuration server.
This list is populated based on the that are added to the . For more information, see Configuring-AR-System-servers-that-the-mid-tier-uses. - (Optional) Click Browse to specify the location of the config.properties file.
By default, the existing config.properties file is located in the midTierInstallationDirectory\WEB-INF\classes folder. - (Optional) Clear the Also add to tenant's server list check box.
The configuration server is not added as a server to the tenant. By default, this check box is selected.
- Click Save.
Ensure that the virtual host is accessible to the users by making appropriate changes in DNS or load balancer settings.
The tenant is added to the . Each tenant that is added to the has a corresponding tenant-specific property file. For example, if you add a tenant named Tenant1, the config.Tenant1.properties file is added to the midTierInstallationDirectory\WEB-INF\classes\tenants\ folder.
If you add a tenant with the name of a tenant that was previously deleted or offboarded from any mid tier, a warning message is displayed. When you delete a tenant, the tenant is deleted but the tenant configuration is not deleted from the Centralized Configuration forms. For more information, see Configuring-the-AR-System-server-as-a-Centralized-Configuration-server.
To edit tenant-specific properties
On the Tenant Settings page, select a tenant that you want to edit, and click Edit.
- On the Edit Tenant page, edit the tenant-specific properties that you want to change for this tenant.
- Click Save Tenant.
To delete a tenant
- In a browser, open the Remedy Mid Tier Configuration Tool at http://hostname:portnumber/arsys/shared/config/config.jsp.
- Click the Tenant Settings link.
- From the Tenant Settings page, select the check boxes in the Delete/Edit column for one or more tenants.
- Click Delete.
Use caution when deleting a tenant. Ensure that the users who are logged through the tenant's virtual URL stop accessing the mid tier; otherwise, they might see unexpected behavior.
Mapping a tenant to multiple
You can add multiple s to a tenant; however, only one will be the primary server used for authenticating, setting preferences, the home page, and the data visualization module. For more information, see Configuring-AR-System-servers-that-the-mid-tier-uses.
You cannot map a single to more than one tenant.
Configuring global settings for all tenants
You can configure global configuration settings for tenants such as the cache settings, report settings, and log settings. For more information, see Configuring Mid Tier.
Identifying whether the is in multitenant mode
When you access the using the virtual host name, the is in multitenant mode. For example, if your URL starts with http://Tenant1.onbmc.com/arsys/forms/, you are using a that is in multitenant mode. If your URL starts with http://hostName/arsys/forms/, you are accessing a that is not in the multitenant mode.
For a to be accessed in multitenant mode, ensure that at least one tenant with a virtual host name is added to the .
The administrator can access the Mid Tier Configuration Tool only by using the actual mid tier host name, not the virtual host name.