Product Documentation

Configuring Cross-Tenant Reporting with Role Restrictions

Jan 31, 2013

You can view summarized data in Multi-Tenant Console individual tenants through a cross-tenant reporting capability. You can group individual tenants into different views and configure restricted access to the tenant information by using role-based access control (RBAC). You can also establish implementations that define the data that is available to specific Multi-Tenant Console administrators.

You can configure the following two scenarios for partner implementations within Multi-Tenant Console:
  • New Multi-Tenant Console installation with initial partner implementation.
  • Upgrade of existing deployment with new partner capability.
Most of the data for these cross-tenant reports is collected from the XenMobile Device Manager or from the Multi-Tenant Console tenants. Otherwise, you can populate the data manually. For Multi-Tenant Console deployments on the organizations' premises, the following fields are populated from an external database source:
Note: For XenMobile cloud deployment hosted customers, these fields are populated from the cloud deployment provisioning database.
  • Hosting Region (a combination of Region + Country, in case of organizations outside of the United States)

    In the reports, for Hosting Region values, the "region" column has these values:

    • US East = United States East
    • USWEST = United States West

    All others appear as region(country) in the reports.

  • Type (for example, Trial or Subscribed)

    In the reports, for Type, the "buy_status" column has these values:

    • 0 = Trial
    • 1 = Subscribed
Note: The values for U.S customers in the "cloud_user" table "region" should be match exactly to the values mentioned in this topic; for example, US East and USWEST.

To provide data manually for cross-tenant reports

  1. Open Multi-Tenant Console database server page and create a new record.
  2. Run the following SQL statements from the Multi-Tenant Console database.



    Important: Change the ? for DB_SERVER_ID to the newly created Database Server record also make sure there is only one row in the DB_SERVER table with CLOUD_DB_CHECK field set to 'Y' per partner.
  3. Connect to the newly created Database Server and execute the following SQL script. CREATE DATABASE zen_front; USE zen_front; CREATE TABLE cloud_user (id BIGINT, preferred_domain_word VARCHAR(255), region VARCHAR(255), country VARCHAR(255), buy_status VARCHAR(255) );
  4. Populate the cloud_user table with customer data. The preferred_domain_word column is used to map the tenants so you must give the column the same name as the name of the tenants in the Multi-Tenant Console tenant table. Also the preferred_domain_word column name should be unique.
    1. Create insert scripts and execute the scripts. For example: INSERT INTO cloud_user VALUES(1,'foo','EU','France','0'); INSERT INTO cloud_user VALUES(2,'bar','EU','France','1');
    2. Create CSV files and populate the cloud_user table by using the CSV files.

To set up an initial Multi-Tenant Console partner implementation

  • Ant is setup on the build server (in case a Web application ARchive (WAR) file is not available).
  • The upgraded WAR file or the upgraded Multi-Tenant Console source stack is available.
  1. Stop the Multi-Tenant Console application Tomcat server.
    Note: If an upgraded Multi-Tenant Console WAR file is available, you can skip Steps 2 and 3.
  2. Run Ant from trunk. This will set up all the required libraries (.jar files).
  3. Run Ant from the service_provider dir. This will build the Multi-Tenant Console WAR file.
    Important: There are now two build.xml files. The build.xml original file is for Windows distribution and the build-linux.xml file is for Linux. Please use the correct file to build the WAR file.
    Note: If the application is running with grails run-app, you can skip Step 4. You should, in this case, download gwt-window-1.5.3 from the Google Web Toolkit and set the GWT_HOME environment variable. If you are using zdm_mtc.bat or, make sure it has the GWT_HOME defined.
  4. Place the newly created WAR file in web-app tomcat folder.
  5. Start the Tomcat service.