Skip to content

Verify the First Pull

Confirm that the MetaMiner Server pulled your BusinessObjects environment and that the client shows it.

Before you begin

  • The MetaMiner Server is started and the environment is enabled. See Initial Setup in MMA.
  • You can open files in server\logs\ on the MetaMiner host.

Steps

  1. In the MetaMiner Administrator, choose File > Open Log Folder and open slc.log in a text editor. This is the service lifecycle log: starts, stops and pull stages.

  2. Find the server start line:

    server\logs\slc.log (excerpt)
    MetaMiner Service for Windows® started

  3. Find the pull stages for your environment. Each line names the CMS host and the display name:

    server\logs\slc.log (excerpt)
    CMS bocms01/BI4 - Production Europe pull #1 state changed: Initial Pull Started
CMS bocms01/BI4 - Production Europe pull #1 state changed: Initial Pull Done

    Initial Pull Done means all objects (and audit data, if configured) are loaded and the environment is ready for clients. Later cycles log Pull Started and Pull Done. 4. Start the MetaMiner Client and connect to the server. See Install the Client. 5. Select the environment in the Connection Manager and click Apply. The CMS Explorer shows the folder tree of the environment. 6. Compare a few counts with the CMC, for example the number of documents in a known folder or the number of users.

Image of the MetaMiner Client CMS Explorer after the first pull, with the folder tree expanded and the status bar showing the load time

../images/get-started/mmc-first-pull-cms-explorer.png

How long the first pull takes

The first pull reads every object; later pulls read only changes. Time depends on the number of objects, the CMS load, and whether deep processing of documents and universes is on. Deep processing continues in the background after Initial Pull Done, so document details (queries, SQL, universe objects) appear over the following cycles.

TODO: give typical first-pull durations

Add measured examples, for example per 10,000 / 100,000 / 1,000,000 CMS objects, with and without a CMS database connection.

Verify

  • slc.log shows Initial Pull Done for every enabled environment.
  • The client shows the environment in the CMS Explorer with the expected folders.
  • Help > Data Integrity Status in the MetaMiner Administrator opens the status page without errors. See Data Integrity Status.

Troubleshooting

The log shows Error instead of Initial Pull Done

Read server\logs\server.log around the same time for the cause. Typical causes are a lost CMS connection, a password change on the service account, or insufficient rights. See Pull Problems.

Initial Pull Started appears but nothing follows for a long time

A large CMS can take a long time on the first pull. Check that server.log is still growing. If nothing changes for an extended period, see Pull Problems and Performance and Memory.

The client shows fewer objects than the CMC

MetaMiner sees only what the service account can see. Check that the account is in the Administrators group. Also check do-not-disturb windows and object-type exclusions in Pull Schedule and Exclusions.

Web Intelligence details are missing

Web Intelligence deep processing needs the RESTful Web Service on BI 4.x and an edition that includes it. See Web Intelligence Processing Failures and Document Processing.

Next steps