Environments and Pulls¶
An environment is one BusinessObjects cluster that MetaMiner pulls; this page explains what is pulled from it, how often, and what happens to deleted content.
How it works¶
You add an environment in the MetaMiner Administrator by giving its CMS host, a service account, and optionally its audit and CMS databases. Each environment has an Enabled check box: only enabled environments are pulled and shown to clients. One MetaMiner Server can pull many environments of different BusinessObjects versions at once.
Environment IDs are unique across the whole installation, so content from different clusters never mixes in the MetaMiner Database.
What is pulled¶
| Object group | Examples | Notes |
|---|---|---|
| Users and groups | Users, user groups, memberships, Windows AD aliases | |
| Folders and categories | Public folders, favorites, inboxes, categories | |
| Documents | Web Intelligence, Crystal Reports, publications, Analysis for Office, Design Studio / Lumira, Xcelsius, Excel, PDF and other files, shortcuts, hyperlinks | Instances are included |
| Universes and connections | UNV and UNX universes, relational and OLAP connections, overloads, security profiles | |
| Platform | Servers and server groups, services, sessions, events, calendars, custom roles, profiles, custom attributes | |
| Security | Rights on folders, categories, universes and connections | Extracted on a schedule |
| Document content (deep) | Web Intelligence data providers, queries, SQL, variables; universe objects and joins; Crystal tables, fields and commands | Depends on edition |
| Audit (optional) | Events and sessions from the audit database | Requires an audit database connection and a license that includes audit extraction |
How often¶
| Item | Default | Where to change |
|---|---|---|
| Object types (shallow) | Every 5 minutes per type | Pull Schedule and Exclusions |
| Web Intelligence and universe deep processing | Every 5 minutes | Pull settings |
| Re-check for imported or missed objects | Every 15 minutes | Not configurable in the MMA |
| Audit database | Every 20 minutes; first pull up to 550 days back | Audit settings |
| Server metrics | Every 300 seconds | Pull settings |
Use do-not-disturb windows to stop selected object types from being pulled during busy hours, for example a nightly batch window.
Deletions¶
When an object disappears from the CMS, the next pull removes it from the MetaMiner Database, including its dependent rows. By default MetaMiner keeps no "deleted" copy of the object metadata itself.
If you need a history of deleted content, connect the audit database: audit events record the deletion and stay in the MetaMiner Database.
A large drop in object count triggers a warning
If one pull detects more deletions than the configured threshold, MetaMiner sends a warning e-mail (when e-mail is configured). Check the CMS before assuming content was removed on purpose. See Notifications.
Key terms¶
| Term | Meaning |
|---|---|
| Enabled environment | An environment the server pulls and clients can load |
| First (initial) pull | The full read after an environment is added or the server starts with an empty database |
| Incremental pull | A read of objects changed since the last stored change time |
| Imported objects | Objects present in the CMS but missing or outdated in the MetaMiner Database |