Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

The multitenant BMC Mobility for Remedy ITSM platform is primarily used in an on-demand environment, but can also be used in an on-premise environment.

To configure multitenancy in an on-premise environment

  1. Log on to the BMC Mobility Administration console with an administrator account. 
  2. In the Mobility Administration: Tenant form, in the Default Tenant record, update the Mobility Server Host field to your BMC Mobility server name.
  3. In the BMC Mobility Administration console, click the Applications tab.
    The Applications pane appears.
  4. In the Applications pane, create persistent data stores, and link them to BMC Mobility applications.
  5. In the Mobility Administration: Push Notification Cert form, enter push notification certificate information for each application.
  6. If needed, modify the cluster settings, such as the log level.
  7. Create a default profile.
  8. If needed, customize the data source query and configure the audit settings.

To configure multitenancy in an on-demand environment

Perform the steps associated with your role.

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 the Mobility Administrator Group.
    That user is the Mobility Administrator.
  4. Grant the Mobility Administrator Group hidden access to the Group form.

If you are a BMC Mobility server administrator

  1. In the Mobility Administration: Tenant form, create BMC Mobility tenants.
  2. In the BMC Mobility Administration console, click the Applications tab.
    The Applications pane appears.
  3. In the Applications pane, create persistent data stores for each tenant, and link them to BMC Mobility applications.
  4. In the Mobility Administration: Push Notification Cert form, the enter push notification certificate information for each application for all tenants.
  5. If needed, modify the cluster settings, such as the log level.
  6. In each tenant's data store (the ITSM ARServer), create an entry in the Mobility Message Queue: Web Server Info form for that tenant. If the entry already exists, 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 BMC Mobility Administration application.
    • Ensure that the BMC Mobility web server name and port are the host and port that are mapped to the BMC Mobility server cluster through the internal load balancer.
  7. In each of the Mobility Server(s), Under directory <MobilityServer>\WEB-INF\classes\certification , Create the folders with the name of tenants and copy the following certificates that you can find in  <MobilityServer>\WEB-INF\classes\certification to each of the tenant folders:

    • BMCiOSAPNSApprovalsMobile.p12

    • BMCiOSAPNSApprovalsMobileAppStore.p12

    • BMCiOSAPNSApprovalsMobileDeveloper.p12

    • BMCiOSAPNSIncidentsMobile.p12

    • BMCiOSAPNSIncidentsMobileAppStore.p12

    • BMCiOSAPNSIncidentsMobileAppStoreNative.p12

    • BMCiOSAPNSIncidentsMobileDeveloper.p12

If you are a BMC Mobility tenant

  1. Create a default profile
  2. If needed, customize the data source query and configure the audit settings.
  • No labels