Repository and Broker setup
This page explains Repository and Broker setup and the other platform component stages performed during step 8, full installation. Follow the four-command installation sequence to run it.
What the installer establishes
For a successful fresh installation with ./install_dbaasnow --components all, the installer performs the following stages in order.
| Order | Stage | What is established |
|---|---|---|
| 1 | Repository database service | Installs and configures the Repository database service using the system-administrator credential |
| 2 | Repository configuration | Creates or verifies the Repository container, schema and required accounts; loads the supplied lifecycle configuration and initial records; prepares the initial Broker account and product-managed access policy |
| 3 | Broker | Installs and starts the customer console service and completes its Repository connection and platform service interfaces |
| 4 | Coordinator | Installs and starts the coordination service used by the database workflows that require it |
| 5 | Plugin | Deploys and starts the database automation service and registers its connection in Lifecycle Manager |
| 6 | Monitor | Installs the metrics and dashboard services, applies the supplied monitoring configuration and registers the monitoring connection |
| 7 | Gateway | Configures and starts web routing for the Broker and monitoring views, then checks the configured route |
The Repository configuration stage and the Broker service stage are separate. A completed Repository stage alone does not establish that the console, automation and monitoring services are ready. Review each stage's result and verify the completed installation.
Customer setup after installation
The installer prepares platform services and supplied initial records. The Lifecycle Manager administrator then reviews and completes licence activation, customer settings, organizations, applications, named users, service credentials, target-server records, database-version packages and notification rules.
Follow the post-installation readiness checklist before provisioning the first target database project. Product installation does not populate the customer's complete database inventory or activate a customer licence automatically.
DNCollector and target databases
DNCollector is the target-host component of Lifecycle Manager. It is installed automatically when an existing database service is onboarded through Discovery or a new database service is provisioned.
Target PostgreSQL, MongoDB and Neo4j services are onboarded or provisioned through those later workflows. See Getting Started and DNCollector automatic installation.
Repository credentials and customer access
The customer configuration contains three independently configurable Repository passwords: system-administrator, container-administrator and Repository application-account access. The installer uses configured values or requests blank values twice.
The installer manages the required product settings. Customers do not supply a separate setup-administrator username, email or password. Customer administration is performed through the Broker.
A fresh Broker installation creates the initial customer console account admin/admin. Use it for the first console login and change its password immediately. Repository passwords do not replace the Broker login.
See Installation configuration and credentials.
Interrupted or existing installation
An interrupted run may have established some components and product records. Preserve those records and the installation log. A completed matching Repository rerun checks the installation and reapplies its product access policy without replaying the import or resetting existing container-administrator passwords. A different package version requires an agreed upgrade or recovery path.
Do not delete the Repository or installation directories to force a new installation. A populated installation or a retry against a different package needs the recovery/deployment plan agreed with DBaasNow.
What happens next?
After the full installer finishes:
- Copy the printed console URL.
- Verify installation and login.
- Complete all post-installation readiness work.
- Start the applicable Getting Started path.