Checking for BI Services compatibility

The BI Services Compatibility Check tool checks the selected repository database for BI Services compatibility and points out existing compatibility conflicts and their solutions. BI Services compatibility of a repository database in this context means that the repository is ready to run in the Infor Cloud. You can use the BI Services Compatibility Check tool to create a list of existing compatibility conflicts. The compatibility conflicts must be cleaned up manually.

To check the current repository database for BI Services compatibility:

  1. Right-click the registration in the tree (there must be a connection) and select All Tasks > Check BI Services Compatibility. The dialog BI Services Compatibility Check opens.
  2. Under Project Structure, the resulting BI Services compatibility check of the project structures is shown:
    Icons Description
    Projects in the tree that are compatible with BI Services are identified by this icon.
    Projects in the tree that are not compatible with BI Services are identified by this icon.
    Note: 

    A project that is compatible with BI Services must meet these requirements:

    • The project may only contain one node of each type. Projects must be split into several projects where this rule is not met.
    • The project must contain a Dashboard Catalog.
    • The project must contain one single default language.
    • Only one OLAP Permission Management, one Application Studio report catalog, one Dashboard Catalog, and a DataLink Model are allowed in a project.

    When you expand a project that is not compatible with BI Services, messages point to the project structures that do not meet BI Services requirements. For example:

    • If several OLAP catalogs exist in a project, the message Only one OLAP catalog is allowed. is displayed.
    • If a Financial Consolidation, Visual Framework, or Office Plus report catalog is part of the project structure, the message Not supported. is displayed.
  3. Click Next. Under Repository Roles the resulting BI Services compatibility check of the Repository Permission Management Roles and the User Management Roles is shown:
    Icons Description
    Role configurations that are compatible with BI Services are identified by this icon.
    Role configurations that are not compatible with BI Services are identified by this icon.
    Note: The Repository Permission Management roles and the User Management roles (SSO roles) have been merged into Repository Roles in BI Services. To use the repository in a BI Services environment, matching pairs of roles that have identical names in the Repository Permission Management and the User Management must exist. A Repository Role is consistent, if a role with the same name exists on Repository Permission Management and User Management level. The same users and groups must be assigned to both roles.

    When you click a role configuration that is not compatible with BI Services, a message under Issues points out the reason for the BI Services incompatibility. Example for inconsistent user and group assignments: Repository Administrator - The user and group assignments of the two roles differ.. Example for a missing role: A matching Repository Administrator role with the same name is missing..

  4. Click Next. Under Application Roles the resulting BI Services compatibility check of project roles, report catalog roles, Dashboard Catalog roles, and OLAP roles is shown:
    Icons Description
    Projects and role configurations that are compatible with BI Services are identified by this icon.
    Projects and role configurations that are not compatible with BI Services are identified by this icon.
    Note: 

    Project roles, report catalog roles, Dashboard Catalog roles, and OLAP roles have been merged into Application Roles in BI Services. To use the repository in BI Services, matching roles that have identical names in all nodes of a project must exist. All matching roles that build an Application Role must be assigned to the same users and groups as the project role.

    • It is allowed to have one single OLAP role. It is not allowed to have an OLAP role and the same role on one other role level. The role must exist either on all role levels or as a single OLAP role.
    • It is not allowed to define the Edit permission without the Delete permission and vice versa in all nodes of a project, because the two permissions have been merged into the Edit permission in BI Services.
    • If the Administer permission is given in any role, all matching roles must contain it as well.

    When you click a project or a role configuration that is not compatible with BI Services, a message under Issues points out the reason for the BI Services incompatibility. For example: DesignerRole - The matching roles must be given in all existing models. These matching roles are missing: Dashboard, OLAP. or The user and group assignment of DesignerRole role differs from the assignments on the project.

  5. Click Next. Under Other the resulting compatibility check of other BI Services requirements is shown:
    Icons Description
    Configurations that are compatible with BI Services are identified by this icon.
    Information is identified by this icon.
    Configurations that are not compatible with BI Services are identified by this icon.
    Note: 

    These are additional BI Services requirements that a repository must meet:

    • The repository must not be linked to the user management of another repository.
    • No role must have the permission Total Control except the Supreme Administrator built-in role.
    • Only database interface version 1.14 must be enabled to prevent on-premise applications to access the repository while it is being used in an BI Services environment.
    • The repository may only use authentication system providers that are supported by BI Services. Besides Basic authentication, supported authentication system providers are Windows and Infor Federation Services.
    • The repository must contain the Administration application, which allows to administer the repository in the web. Use the Farm Expert tool to add the Administration application to the repository when registering the repository to the Farm.
    • The repository must contain users who have the Farm Administrator role. Use the Farm Expert tool to add the Farm Administrators to the repository.
    • The repository must contain users who have the Repository Administrator role. Use the Farm Expert tool to add the Repository Administrators to the repository.
    • The repository must contain users who have the Application Creator role. Use the Farm Expert tool to add the Application Creator role to the repository.

    When you click a configuration that is not compatible with BI Services, a message under Issues points out the reason for the BI Services incompatibility and a solution to solve the problem. For example: The repository does not contain users with 'Farm Administrator' role. - To add Farm Administrators, use the Farm Expert tool.

    A complete list of the BI Services compatibility rules is shown here:

    Repository content check list for BI Services compatibility

  6. To copy a list of the compatibility check results to clipboard, click Copy All To Clipboard. You can use the list to go through the identified compatibility conflicts step by step and solve the issues.
  7. To close the BI Services Compatibility Check tool, click Finish.