Intellicus Enterprise Reporting and Business Insights 18.1

Deploying Repository Bundle

0 views 0

Deploying the repository bundle on report server

Intellicus allows you to deploy the repository bundle objects on report server when you are upgrading application version or migrating from one server to another. Intellicus’ iPackager extracts references of the selected information (repository objects/users preferences/configuration settings) from the repository or file system and stores as .conf file (saved on the Web Server with a default name ‘Untitled.conf’).  You can open a configuration file and make changes to it.  A configuration file is then used to build the cab file.  This cab file is later deployed on the Intellicus server.

You can deploy the repository bundle (cab file) to your report server so that the server can access the required bundle after your application is deployed.

This page discusses the steps to deploy the repository bundle to the server.

Note: A repository bundle is also referred as ‘Package’, ‘Bundle’ or ‘CAB’.

A cab file may have any of the following:

  • Repository objects like categories, reports, query objects, parameter objects, analytical objects, dashboards and dashboard widgets
  • Approval process details
  • Report Schedules
  • Organization, user, user access rights and user mappings
  • User created private objects
  • User/Organization preferences
  • Data connection information (along with access rights information)
  • Printer settings
  • Web client properties
  • Report Server configuration files
  • License File
  • Templates

To upload and deploy customizations in a repository bundle, you need to have super administrator user privileges.

  1. On Intellicus portal, click Navigate > Repository > Deploy Repository Bundle.

    Deploy Repository Bundle
    Figure 1: Deployment of the Repository Bundle

    Note: If Intellicus is running under security disabled, specify following URL in the browser’s address bar to get this page.

    If you are using the computer used as web server,


    In other cases,

    http://<IP of the server>/Intellicus/pattern/cab

  2. In the entry box provided under Step 1, specify the cab file name along with its path. If required, use Browse button to locate the file name.
  3. Click Upload The content gets uploaded and information regarding categories and report is displayed on the page.  (Information on Legends is provided below these steps).
  4. Information about Repository bundle
    Figure 2: Information about the uploaded Repository Bundle

  5. Click Deploy to go ahead with the deployment process. Click Cancel to discontinue with deployment process.

After you click the Upload button, information about objects in the bundle being deployed, appears.

The legends are displayed just below the Deploy button.  Information about each of the component in the bundle is displayed in respective tabs like Category, Users and Roles, Server Configuration etc.

Note: Whether an existing object should be replaced by the one being deployed or not, is set while creating the bundle.

A log file with the deployment details will be created if Create Log File checkbox is selected.

The content is deployed and is visible on respective portal pages.

Deployment status indicators

On uploading the repository bundle, you can see information about objects with the help of legends below:

  • Object will be updated red button : Object exists in repository, it will be replaced by the one being deployed.
  • Object will not be updated yellow button : Object exists in repository, it will not be replaced by the one being deployed.
  • New object green button : Object presently does not exist in repository and it will be deployed.
  • Deny deploying violet button : The object will not be deployed because of any of the reasons specified below.

In case a Category has,

  • Same name, same id, different scope
  • Different name, same id, different scope
  • Same name, different id, different scope

In case a Report has,

  • Same name, same id, different scope
  • Different name, same id, different scope