Integration and Administration Tasks
Operational responsibilities
Administration covers deployment, migration, and integration. The RPD and the catalog are the two assets that must be migrated between environments, and they are migrated separately. Use the repository merge facility to combine development changes into a shared repository, and use catalog archive utilities to move content. Agents schedule analyses and deliver results; they depend on the scheduler and on delivery devices configured for users. Usage tracking records query activity into a table for auditing and tuning.
Integration patterns
Oracle BI integrates with external systems through several channels: web services for programmatic access, action framework for invoking external actions from dashboards, and single sign-on for identity propagation. Data integration typically loads a warehouse that the BI Server queries, but the BI Server can also federate multiple sources through its physical layer. Know that logical SQL is the integration contract between presentation and server.
Traps to watch
A common trap is assuming the RPD and catalog migrate together - they do not. Another is confusing agents with dashboards: agents run on a schedule and deliver output, while dashboards are interactive. Questions may test that usage tracking must be enabled and writes to a configured table, or that repository merge requires compatible source repositories. Also watch for wording that treats the scheduler as always available - it is a separate component that must be configured.
Rule of thumb
For migration questions, ask "metadata or content?" Metadata means the RPD; content means the catalog. For automation questions, ask "scheduled delivery or interactive?" Scheduled means an agent.