Configuration

Open the Confluence space, then open Space settings, Apps, and BoomiSight Configuration.

Enter:

• Boomi account ID.
• Boomi username. BoomiSight accepts the Boomi token-auth username format and stores a normalized username during save.
• Boomi API token.
• Automatic refresh interval from 24 to 168 hours.
• Dataset flags for runtime, API, execution, and connector data.

After saving, run Verify Connection & Access. BoomiSight checks basic authentication first, then reports readiness for core dashboards, deployment history, execution monitoring, and optional API governance enrichment.

APIM access is optional. If APIM probes are blocked or unsupported, BoomiSight can still show core runtime and deployment views when those permissions are available.

Saving a complete configuration also creates the BoomiSight configured-space marker. The marker does not contain Boomi credentials or cached operational data; it tells Confluence which spaces should show configured-space surfaces such as the Boomi Architecture and Boomi APIs bylines. After upgrading an existing space to BoomiSight 3.0, save the complete configuration once to create this marker.

Dataset Flags

• Runtime health and deployment datasets support environment comparison, atom health, environment summaries, process snapshots, deployment history, release notes, and picker-first macro configuration.
• API visibility dataset supports API Snapshot and API Governance.
• Execution monitoring dataset supports Execution Dashboard, Process Executions, and Business Process Health Badge.
• Connector inventory dataset supports Connector Inventory and Process Blast Radius.

Refresh And Cache Behavior

BoomiSight caches data per Confluence space. The scheduler performs a lightweight hourly eligibility check, but automatic refresh can be set only from 24 to 168 hours. Existing saved values below 24 hours are treated as 24 hours. A space that is not yet due does not reload its Boomi snapshots or report a completed refresh.

Manual dashboard and macro refresh actions can request fresh data immediately when users need current evidence. The automatic interval does not delay those actions. Ordinary dashboard refreshes do not scan Confluence pages for Documentation Health.

Transient throttling, overlapping refreshes, or an upstream Boomi failure can leave the last good cache visible with a stale, partial, in-progress, or retry-later state. Check the displayed freshness before treating a view as current.

Admin-Safe Maintenance

• Clear cached data removes non-secret cached facts and scan state for the space while keeping the Boomi account, username, API token, scheduler settings, configured-space registry entry, and configured-space marker.
• Disconnect and purge space data removes the stored token, configuration, sync metadata, cached data, configured-space registry entry, and configured-space marker. The action remains disabled until the admin enters the confirmation phrase shown in the product.

Use Clear cached data when the connection should remain configured but its snapshots need to be rebuilt. Use Disconnect and purge space data when the space must stop using BoomiSight and its stored app data should be removed.

Access Diagnostics

Verify Connection & Access reports each feature area separately:

• Basic API authentication.
• Core runtime and deployment dashboards.
• Deployment history and release notes.
• Execution monitoring.
• API governance enrichment.

If a feature area is limited, use the impact text in the diagnostics result to decide whether to expand the Boomi identity’s permissions or keep that dataset disabled.

After the first successful save and verification, open Documentation Health and run Scan Space Pages if the space needs page-level findings. Scans are explicit, space-admin initiated, and separate from Boomi dataset refreshes.