Using the Administration Console to configure multi-tenancy

The multi-tenantcy Mobility platform is primarily used in an OnDemand environment, but can also be used in an On Premise environment. 

• • To configure On Premise
  • To configure OnDemand
    • If you are a BMC Remedy AR System server administrator
    • If you are a Mobility server administrator
    • If you are a Mobility tenant

To configure On Premise

The configuration steps for an On Premise environment are:

1. Login in to the console as ARAdmin. In the Mobility Administration: Tenant form, in the Default Tenant record, update the Mobility Server Host field to your Mobility server name.
2. In the BMC Mobility Administration console, click the Applications tab. The Applications panel appears.
3. In the Applications panel, create persistent data stores, and link them to Mobility applications.
4. In the Mobility Administration: Push Notification Cert form, the enter Push Notification certificate information for each application.
5. If you are using the iOS client, then copy your iOS push notification certificates to the certificate directory (<mobility server dir>/MobilityServer/WEB-INF/classes/certification).
6. If needed, modify the cluster settings, such as the log level.
7. Create profiles and profile-to-group mappings.
8. If needed, customize the data source query and configure the audit settings.

To configure OnDemand

The configuration steps for an OnDemand environment are:

If you are a BMC Remedy AR System server administrator

1. Create a Tenant Group for each tenant.
2. Create tenant users. The tenant user is in both the Tenant Group and the Mobility Group.
3. Create a user in "Mobility Administrator Group”. That user is Mobility Administrator.
4. Grant the Mobility Administrator Group hidden access to the Group form.

If you are a Mobility server administrator

1. In the Mobility Administration: Tenant form, create Mobility tenants.
2. In the BMC Mobility Administration console, click the Applications tab. The Applications panel appears.
3. In the Applications panel, create persistent data stores for each tenant, and link them to Mobility applications.
4. In the Mobility Administration: Push Notification Cert form, the enter Push Notification certificate information for each application.
5. If the tenant uses iOS clients, then copy their iOS push notification certificates to the certificate directory of allMobility servers in the cluster.
   • In the Mobility server certificate directory (<mobility server dir>/MobilityServer/WEB-INF/classes/certification), create a sub-directory with the tenant's name.
   • Copy the iOS certificate file to that sub-directory.  
6. If needed, modify the cluster settings, such as the log level.
7. In each tenant’s data store (the ITSM ARServer), create an entry in the Mobility Message Queue: Web Server Infoform for that tenant. If the entry already exists, then modify the existing one.
   • Ensure that the Tenant GUID field contains the tenant’s Tenant GUID, which is defined in the Mobility Administration: Tenant form for the Mobility Administration application.
   • Ensure that the Mobility Web Server Name and Mobility Web Server Port are the host and port that are mapped to the Mobility server cluster through the internal load balancer.

If you are a Mobility tenant

1. Create a profile and profile-to-group mapping.
2. If needed, customize the data source query and configure the audit settings.