Validate an Environment¶
Check that MetaMiner can log on to an environment, read its content, reach its databases and read Web Intelligence documents through REST.
When validation runs¶
- When you click Apply in the environment dialog.
- When MMA starts: every environment is validated in parallel and the Status column is updated.
- When you click Test REST (REST checks plus a document probe) or Test Connection on a database tab.
An environment that fails validation is marked Failed and disabled. MMS does not pull a disabled environment.
Validation checks¶
| # | Check | On failure |
|---|---|---|
| 1 | The CMS host name resolves | Fails: "Can not resolve host" |
| 2 | Logon to the CMS with the configured account | Fails: "Server Is Not Found or Down" or "Authentication Failed" |
| 3 | The platform version can be read | Fails: "Unable to detect your CMS version" |
| 4 | The account can read the Public Folders root | Fails: "The user does not have access rights to the Public Folders root" |
| 5 | The account is a direct member of Administrators | Warning only: "User should belong directly to the Administrators group" |
| 6 | Audit database connection, if configured | Fails: "Audit DB connection failed" |
| 7 | CMS database connection, if configured | Fails: "CMS DB connection failed" |
| 8 | RESTful Web Service reachable and logon works | Fails: "Web Intelligence REST API validation failed" |
MMA tries every BusinessObjects SDK version shipped with MetaMiner and keeps the first that logs on, so you do not choose the version yourself. The detected version appears in the Version column.
Web Intelligence REST probe¶
Test REST runs in two stages.
- Service checks: MMA finds the REST address (auto-discovered or custom), confirms the RESTful Web Service answers, then logs on to it.
- Document probe: the Verifying WebI documents dialog reads the newest public Web Intelligence documents end to end through REST, in random order, until five return a complete document. The whole probe stops after 5 minutes.
The probe table shows one row per document: #, Document, SI_ID, Result, ms, Code / message. The final verdict is one of:
| Verdict | Meaning |
|---|---|
| PASS | Enough documents were read completely |
| FAIL | Documents could not be read |
| INCOMPLETE | Some documents were read but not enough before the time limit |
| INCONCLUSIVE | Not enough suitable documents to decide |
The probe is read-only. It writes nothing to the MetaMiner Database or to BusinessObjects.
Image of the Verifying WebI documents dialog with five rows and a PASS verdict
../../images/admin/webi-rest-probe.png
Steps¶
- Select the environment and click Edit.
- Click Test REST and wait for the verdict.
- On the Audit DB and CMS DB tabs, click Test Connection if those connections are on.
- Click Apply to run the full validation and save.
Troubleshooting¶
REST SDK not deployed / REST API returned HTTP 404
The URL does not point to a web tier with the RESTful Web Service. Check the WACS or Tomcat deployment in BusinessObjects, or enter the correct address with Custom URL.
Cannot connect to REST API / Cannot resolve hostname
The auto-discovered address may be an internal or load-balancer name. Check Custom URL and enter an address the MetaMiner Server can reach, then test again.
Certificate not trusted / hostname mismatch
Test REST shows the certificate and offers to trust it. Trusting a certificate adds it to MetaMiner's own trust store only. See Trusted Certificates.
Validation passes in MMA but the environment shows Failed after restart
MMA validates every environment again at each start with the same checks. A changed password, an expired account or a REST address that is no longer reachable shows up then. Check Status and admin.log.