Audit and CMS Databases¶
Connect MetaMiner to an environment's BusinessObjects Audit database for activity history, and to its CMS system database for faster change detection.
How it works¶
Both connections are optional and read-only. You configure them on the Audit DB and CMS DB tabs of the environment dialog.
| Connection | Tab | What MetaMiner does with it | Without it |
|---|---|---|---|
| Audit database | Audit DB | Reads audit events and sessions into the MetaMiner Database (MMDB) | Historical metrics, user activity and deleted content are not available |
| CMS system database | CMS DB | Reads the CMS object table directly to find new, changed and deleted objects, then fetches only those through the BusinessObjects SDK | MetaMiner finds changes through CMS queries, which is slower on large systems |
Large systems
MMA recommends a live CMS database connection for large systems to reduce load on the CMS and speed up pulls.
Audit DB tab¶
| Field | What it does |
|---|---|
| Retrieve Audit Data? | Turns audit collection on for this environment |
| Audit DB Type: | SQL Server, Oracle, DB2, SQL Anywhere, MySQL, SAP HANA or Postgres |
| DBMS Host: / Port: | Database server and port |
| DB Name: | Audit database name |
| Username: / Password: | A read account on the Audit database |
| Type-specific fields | Oracle: SID: or Service:, TCPS, TrustStore location. SQL Server: Use Integrated Security. DB2: Schema:, SSL, TrustStore location. SAP HANA: Database Name:, Trace. |
| Test Connection | Opens a test connection and shows the result on the button |
Audit collection also needs:
- an edition that includes audit data extraction (not Community),
- Pull Audit Data switched on under Preferences > Settings... > Audit (on by default). See Audit settings.
First audit pull
On the first pull MetaMiner reads up to 550 days of history (setting Audit # days history to pull). Size the MMDB for this or lower the value first. After that it reads new events every 20 minutes (Audit pull delay) and re-reads recent days to catch late events.
Image of the Audit DB tab with Retrieve Audit Data? checked, SQL Server selected and Test Connection showing success
../../images/admin/bo-environment-audit-db.png
CMS DB tab¶
| Field | What it does |
|---|---|
| Use live connection to the CMS RDBMS? | Turns on direct reads from the CMS system database |
| CMS DB Type: | SQL Server, Oracle, DB2, SQL Anywhere, MySQL or SAP HANA |
| Connection fields | Same as the Audit DB tab |
| Test Connection | Tests the connection |
When you switch on the CMS DB tab after filling the Audit DB tab, MMA offers to copy the matching fields. Change the database name afterwards.
MetaMiner opens one read-only connection per environment to the CMS database and reads only the CMS object table.
Image of the CMS DB tab with Use live connection to the CMS RDBMS? checked and connection fields filled
../../images/admin/bo-environment-cms-db.png
Steps¶
- Select the environment and click Edit.
- Open the Audit DB tab, check Retrieve Audit Data?, choose the database type and fill in the connection.
- Click Test Connection and wait for a success mark.
- Optional: repeat on the CMS DB tab with Use live connection to the CMS RDBMS?.
- Click Apply.
A failed database test disables the environment
If the Audit or CMS database test fails on Apply, MMA saves the values but marks the environment Failed and disables it. Fix the connection and apply again.
Troubleshooting¶
Error validating Audit DB connection
Check host, port, database name and account. Make sure the MetaMiner Server can reach the database port through firewalls.
Audit data does not appear
Check that Pull Audit Data is on in Settings > Audit, that auditing is enabled in the BusinessObjects CMC, and that your edition includes audit extraction. Audit data is read every Audit pull delay minutes.