Product Documentation

To add a new tenant on Multi-Tenant Console

Sep 10, 2014

A tenant is an instance of XenMobile Device Manager. The tenant is running on a specific tenant host, using a specific connector on a specific Tomcat server and storing the data on a specific database on a database server.

  1. Click New Tenant.
  2. Complete the following fields:
    1. Name. Enter a name for the tenant.
    2. Description. Enter a description of the tenant.
    3. XDM Application. Select the XenMobile application release to be used by the tenant.
    4. Tomcat Servers. Select one or more servers on which the tenant should run.
    5. HTTPS Connector. Select the HTTPS connector to be used.
    6. External DNS Name. Specify the name of the server as seen from the devices.
    7. Generate or import SSL certificates. Select whether you want to generate a new certificate chain for the tenant or import an existing certificate. If you choose to import the certificates, you are prompted for the patch to all the certificates.
    8. Check Enable iOS. Select this option to enable iOS devices management and to allow the import of your APNs certificate. In this case, select a Web HTTPS Connector for iOS enrollment, your APNs certificate file, and specify your APNs Certificate private key password.
    9. Instance Name. Enter the name of the XenMobile instance. You should append this value to the server Web address to reach the tenant; for example, http://my_server/my_instance
    10. XenMobile Device Manager admin name. Enter the XenMobile administrator user name and password. These are the credentials to be used on the console.
    11. Remote support secret authentication code. Enter the authentication code used as a shared secret during the remote support sessions. The default is Zenprise.
    12. Crystal Report key code. If you want to be able to generate and use the reports in the XenMobile Administration Console, enter a Crystal Report license key.
    13. Database server. Select the database server to use to store Device Manager data.
    14. Database Name. Enter the name of the database to be created on the database server.
    15. Database user. Enter the credentials of the user to be created on the database to handle the tenant’s data.
    16. NAT Device Access. Leave a default value to reuse the Tomcat server configuration and remote support tunnel definition.
    17. Enable Cluster. Select the check box if the tenant is to be deployed on clustered Tomcat servers. If you select this option, the following advanced parameters appear:

      Broadcast UDP Port, P2P TCP Port, and OSCache Multicast UDP Port. Edit each port so that the ports do not overlap with another tenant.

To view the parameters for each tenant you have added to Multi-Tenant Console, click the Tenants tab. The following information appears for each declared tenant:
  • Deploy Status. The colored bullet has the following meaning:
    • Green. Deployed.
    • Orange. To be redeployed or not-deployed.
    • Red. Does not belong to a Tomcat server but is not un-deployed.
    • White. Not associated with a Tomcat server.
  • Name. Name of the tenant
  • XenMobile Application. XenMobile application used by the tenant.
  • Last Modified Date. Last modification date of the tenant.
  • Tomcat Servers. Tomcat server running the tenant.
  • HTTPS connector. HTTPS connector used by the tenant.
  • Instance Name. Name of the XenMobile instance. You should append this value to the server Web address to reach the tenant; for example, http://my_server/my_instance
  • Database Server. Database server used to store the tenant data.

To edit or delete a tenant

  1. To edit the tenant, click Edit.
  2. After you make changes to the tenant parameters or to redeploy the tenant, click Apply.
  3. To apply a patch from a XenMobile Application, click Patch. You will install a patch without the need to redeploy the tenant.
  4. To remove a tenant, click Uninstall/Delete. The tenant is undeployed from the Tomcat server and the declaration is deleted.