Skip to Content

Multitenancy Management tool setup, new features in BI 4.1

Multitenancy management tool is built to use a single instance of BI 4.x runs on a server, serving multiple client organizations (tenants). BI 4.x can be designed to virtually partition its data and configuration and each client can have access to their own data only.
The SAP BusinessObjects Business Intelligence platform Multitenancy Management Tool is a Java-based program that SAP OEM partners can use to standardize and automate the creation of objects and settings for new customers in a multitenant BI platform deployment.
The traditional way of configuring a multitenant environment is to create separate user groups, folders for each tenant and apply security manually, but the multitenancy management tool automates these steps and makes it easier to create new tenants.
Let’s begin to configure a simple multitenant environment:
Step – 1: Create Tenant Template:
  1. Create a user group name “$TemplateToken$”.
  2. Create a public folder named $TemplateToken$ atthe root level.
  3. Assign required rights to “$TemplateToken$” user group on $TemplateToken$ folder.
Step – 2: Create Tenant Configuration file:
The file is located in the multitenancyManager folder at:
Windows: <InstallDir>\SAP BusinessObjects EnterpriseXI4.x\java\apps\multitenancyManager\jars\
Unix: <InstallDir>/sap_bobj/enterprise_xi4x/java/apps/multitenancyManager/jars/
  • Take a backup of the properties file and open the original one in a text editor.
  • Under (Mandatory) Name of the tenant being added, change the value for the tenant Name option to the name of the new tenant you are defining.
  • Under (Mandatory) Template token identifier used for tenant name replacing, change the value for the templateToken option to thestring used to identify your template folders and user group. Use the string “$TemplateToken$,” as we did in step – 1.
  • Under (Mandatory) Logon information provide CMS Server name, Authentication type, User name (an admin user who has permissions to perform the task), its password.
  • Under (Optional) Document folder template, change the value for the templateContentFolder option to specify the top-level template folder paths. Separate multiple values with a semicolon, and include the full path of the public root folder.
  • Save and close the file.
Step – 3: Run the Multitenancy Management Tool:
  • Open Command prompt and navigate to the location, <InstallDir>\SAP BusinessObjects Enterprise XI 4.0\java\apps\
  • Type following command.
         java -jar multitenancymanager.jar -configFile
  • Likewise you can simple change the value “Name of the tenant being added” as we did in Step – 2.2, save the file and run the tool.
  • After the tool successfully finish creating the tenant logon to CMC, go to Multitenancy and you should see the tenant name populated here.
  • Right click on the tenant name and go to properties. From here you can manage the number of concurrent logon sessions.


  • You can also manage concurrent user sessions from


  • You can add groups to tenant.
  • You can delete a tenant and all its associate infoobjects with the option to exclude certain infoobjects.


  • You can track system usage by tenant using auditing by enabling and configuring audit events as per the requirements.
  • To determine which auditing event is generated by which tenant use 2 new lookup tables in the auditing database: ADS_TENANT and ADS_USER.

For detailed overview please visit following blog:

You must be Logged on to comment or reply to a post.
        • Hi Jawahar and Sohel,

          I talked to Christina Obry (Product Owner) not long ago and it appears that 4.1 in fact supports .UNX in multitenancy solution.



          • Hi Tomasz,

            Thanks for the correction, The 4.1 MMT document which I had was released on 2013-03-25 in this document it is mentioned “This release supports only classic universes (.unv files); it doesn’t support .unx files.”,

            I just referred to the link which Jawahar had provided earlier and this document is released on 2013-05-14 and here it is mentioned “This release supports classic universes (.unv files) with limited support for DSL universes (.unx files, with exceptions that include Access Restrictions (Security Profile) and multi-connection DSL universes).”

            Thanks again,


  • We manage reporting for 50+ Line of Business groups and their BOE platform .NET SDK applications for CR-2013 report delivery, from a single central BO-BI (soon to be 4.1) environment.

    Our licenses are still on the Old CPU-based model, but our individual UserAccounts are created with Connection Type = Concurrent User, so this Multitenancy “License-Quota” model is very interesting.

    It could help us with developing both a charge-back model for our BI Platform services, and let us manage High-Prioity (100’s of Concurrent Users) vs. Low-Priority traffic (5 – 10 Concurrent Users) for different Line of Business groups (ie. Tenants).

    [QUESTION #1] Does Multitenancy only manage the number of UserAccounts that can be created/assigned under a specific Tenant profile – or does it also LIMIT the number of Concurrent Sessions that can be open against the CMS by Users that are in groups under that Tenant…?

    [QUESTION #1a] If we have One (1) UserAccount (eg. Unique ApplicationService account per .NET SDK app) –  would Multitenancy allow us to say that ApplicationAccount-A has access to 50 Concurrent Sessions – but

    ApplicationAccount-B has ONLY access to 10 Concurrent Sessions…?

    Looking forward to playing around with this during “Ramp Up” of 4.1.

  • Hi

    What kinds of objects are supported by multitenancy ?

    • Groups
    • Folders
    • Users
    • Crystal Reports
    • Webintelligence
    • Universe
    • Connections
    • Dashboards
    • Web Services
    • Explorer



    • Hi,

      Operations automated by the tenant provisioning tool

      •   Creating user groups
      •   Creating folders
      •   Setting ACL (Access Control List) on folders
      •   Copying documents and universes from template folder to individual tenant folder
      •   Adding universe restrictions for UNV only
      •   Creating connections

      Supported Document scenarios

      • Direct to data:
        • CR
        • CR4Ent
      • Shared database and semantic layer
        • CR4Ent connected to single-source unx,pquery and BICS
        • WebI connected to unv including universe restriction overload
        • WebI connected to single-source unx, BICS (as of 4.1)
      • Separate database with distinct semantic layer
        • CR4Ent connected to single source unx
        • WebI connected to unv and single-source unx (as of 4.1.)
      • Separate database with shared semantic layer
        • WebI connected to unv using universe connection overload

      Not supported

      • Dashboards
      • Web Services
      • Explorer

      Hope this helps,


  • Hi Sohel,

    This is with regards to SAAS enabled BOBIP solution where tenant are on-boarded using MTM. I had experienced few issues while on-boarding tenants using MTM. Hence I would request you go through thread Promote an idea – Enhance Promotion & distribution in SAAS enabled BOBIP solution stating the problem case in particular deployment scenario.

    If you are convinced with the issues highlighted and ideas stated will you please promote it.


    Sandeep Rana

    • Hi Sandeep,

      I would suggest you to contact SAP via incident and share these issues if these should be tracked as ADAPT or an IDEA. And its always best practice to segregate these issues while submitting idea or bug request.



      • Sohel,

        All the issues had been logged with SAP support over the period of time. Hence, on their request i had placed it on idea space.


        Sandeep rana

        • Hi Sandeep,

          I have promoted the IDEAS place created by you, as explorer is not supported
          with MTM yet this could be a cause that it loosing the association, regarding
          the third Business requirement

          “Exploration: Distribution
          of Infospace via MTM across environments without losing their association with
          the universes in the tenant on-boarded.”



  • Very informative blog Sohel.

    Thanks to Mani and Christina for additional inputs which clears a lot of questions.

    I still have a question though.

    With mutitenancy handle usage of server groups.

    What i mean is if a user 1 who is a general user (not a part of any tenant) schedules a report without selecting a server group, it goes to one of the available AJS.

    But if i put this user 1 under one of the tenants, is it possible that every schedule of this user will only run on a specific server group?

    I hope you all may understand where I am coming from and why i am trying to seek my answers in multitenancy.

    for others, we have a system where we have >30 line of businesses. About 15 of them uses servers groups. There are situation when the LOBs who don’t have server groups run schedules on the AJSs which fall under server groups of those 15 LOBs i mentioned. This blocks the bandwidth of the LOBs who own those server groups. So if we create tenants for those 15 LOBs with their respective server groups, would a user from general population be able to use those servers of server groups under tenants or not?

    • Hi Prakhar,

      I’m sorry for the late reply.

      I haven’t seen server group security completely functional in BO there are many bugs/enhancements/ideas posted for this.

      While working with a customer on same kind of requirements (For 3.1) what I found is that even though you don’t give view rights on a particular server group and while scheduling the report if he chooses first available server, the request may go to the server part of the server group on which user doesn’t have view access.

      The workaround is to do some tweaks in the scheduling page code where in you can set the default option as use only the servers belonging to the server group instead of first available server, and setup server group security. It worked for me in 3.1 haven’t tried this in 4.1 but I feel it should work.