Skip to content

Add an Environment

Connect a SAP BusinessObjects cluster (CMS) to MetaMiner so the MetaMiner Server (MMS) starts pulling its metadata.

Before you begin

  • MMA is running as administrator on the MetaMiner Server machine.
  • You have a BusinessObjects Enterprise account for MetaMiner:
    • a dedicated account such as MetaMinerAdmin, not the built-in Administrator,
    • a direct member of the Administrators group,
    • with access to the Public Folders root,
    • not set to change its password at next logon.
  • The MetaMiner Server can reach the CMS port (6400 by default) and the BusinessObjects web tier that hosts the RESTful Web Service. See Network Ports and Firewall.
  • Optional: connection details and a read account for the Audit database and the CMS system database. See Audit and CMS Databases.
  • Your license allows another enabled environment. See Editions and Licensing.

Steps

  1. In the MMA main window, click Add CMS. The Add SAP BusinessObjects Environment dialog opens.
  2. Under BusinessObjects System Configuration, enter:
    • Display name: the name users see in the MetaMiner Client (MMC).
    • CMS Host: the CMS host name, or host:port when the CMS does not use port 6400.
    • Username and Password of the MetaMiner account.
  3. Optional: enter BI LaunchPad, the base URL of the BusinessObjects web tier without the application path (for example https://bi.example.com:8443). MMC uses it for Open in Browser, universe remap and report validation.
  4. Leave REST API URL on auto-discovery unless your web tier is behind a load balancer or proxy. See Connection and Logon.
  5. Click Test REST to check the Web Intelligence RESTful Web Service. See Validate an Environment.
  6. Optional: configure the Audit DB and CMS DB tabs. See Audit and CMS Databases.
  7. Optional: set "Do Not Disturb" windows on the Advanced tab. See Pull Schedule and Exclusions.
  8. Click Apply.

If the username is Administrator, MMA asks you to confirm and recommends a dedicated account. MMA then reminds you that the account must not be set to change its password at next logon.

MMA validates the environment (connection, version, permissions, databases, REST service). On success the dialog closes, the environment appears in BI Environments as enabled, and MMS starts its first pull.

Image of the Add SAP BusinessObjects Environment dialog with Display name, CMS Host, BI LaunchPad, Username and Password filled

../../images/admin/add-bo-environment.png

Failed validation disables the environment

If any validation step fails, MMA still saves what you entered, but marks the environment Failed and disables it. Fix the cause, then edit the environment and click Apply again.

Verify

  • The environment row shows a version in Version and no error in Status.
  • After the first pull completes, the environment appears in MMC. See Verify the First Pull.
  • The Data Integrity Status page lists the environment.

Troubleshooting

Can not resolve host / Can not reach host

The MetaMiner Server cannot resolve the CMS host name or reach its port. Check DNS, the host name spelling and firewalls between the two machines.

The user does not have access rights to the Public Folders root

Grant the MetaMiner account access to the Public Folders root in the CMC, or use an account in the Administrators group.

Unable to detect your CMS version

The account cannot read the platform version. Use an Administrator-level account.

CMS environment with this host name already exist

Each CMS host can be added once. To change the account for an existing environment, select it and click Edit.

Web Intelligence REST API validation failed

See Validate an Environment.

Next steps