DBaasNow V3

Post-installation setup

Step 10 of the installation sequence. After completion and first login, the Lifecycle Manager administrator completes the tasks below.

All required readiness tasks must be completed before creating the first project to provision a new target database service. If an item was prepared by the installer or another administrator, verify it and record it as complete.

Required platform readiness checklist

Order Task and guide Required outcome Impact if omitted
1 Change the initial administrator password Fresh admin/admin password replaced and account ownership established The publicly documented initial password remains usable
2 Activate the licence Valid licence with intended technologies and capacity Required catalogue services or capacity may be unavailable
3 Review general settings Customer settings and operational defaults reviewed Incorrect defaults can affect forms, presentation or operations
4 Configure organizations Required organization records exist Ownership and assigned access may be incomplete
5 Configure applications Intended application association is available Project/application selection can be incomplete or rejected
6 Create named Broker users Appropriate roles and assigned organizations confirmed Operators may be unable to access or perform the required work
7 Verify System Integration Broker, Plugin and Monitor records match the installed services and functions are reachable Operations, result updates or monitoring may fail
8 Register service credentials Required remote access credentials exist and work on the selected targets Target provisioning or administration cannot connect
9 Prepare and register target servers Intended hosts meet the engine requirements and are selectable Required hosts may be unavailable or fail validation
10 Review catalogue and service settings A licence-granted service and its applicable reference settings are ready An unavailable offering or unsuitable selection can block the request
11 Prepare database versions Selected target database version and its package are available Provisioning can fail because the target engine package is missing
12 Configure monitoring and alerting Required alert rules, contact points and routing prepared; notification delivery tested where offered A provisioned database may have no effective threshold notifications
13 Confirm connectivity Routes between Lifecycle Manager, targets, members and clients are ready for the chosen deployment Discovery, installation, replication, collection or application access can fail
14 Agree operational ownership and backups Owners, backup responsibilities, retention and support contact recorded Recovery and service handover are unclear

System Integration values are established during installation. Review them; change them only when the installed deployment requires an approved correction.

The catalogue is licence-granted. Reviewing it does not mean creating arbitrary new database offerings.

Repository password handover

Confirm that the three Repository passwords use approved production values and are recorded through the customer's protected credential process. The supplied presets are shared defaults. Editing installation_config.yml after a completed installation does not rotate existing account passwords; agree any required password change with DBaasNow.

Keep Repository credentials separate from named Broker accounts and target database service credentials.

Installation files versus target database packages

The installer's --download-binaries stage prepares Lifecycle Manager installation files. Database Version Control prepares packages for the target PostgreSQL, MongoDB or Neo4j version you intend to provision.

A version record alone does not establish that its package is available. Review download/status information through the version-management UI before the first provisioning request.

Monitoring readiness before and after the first project

Before provisioning, prepare the Monitor connection, alert rules, notification destinations and policies. Test delivery where the UI offers a test.

After the target is provisioned and monitored, verify DNCollector collection, project configuration/versions, actual metric freshness and rule evaluation against the target's observations. Follow Verify project monitoring.

May the customer skip a task?

Do not omit required readiness tasks for the first new provisioning request. Already completed settings need verification rather than unnecessary changes.

Some missing items block a form or operation immediately; others leave access, notifications or recovery incomplete even if provisioning technically succeeds. Completion of the installer alone is not sufficient operational readiness.

Ready to start

The administrator confirms the checklist is complete and hands over:

  • Broker URL and named accounts with the required access.
  • The intended licence-granted service and target database version.
  • Prepared target hosts and usable service credentials.
  • Working component integration and target connectivity.
  • Prepared alerting and the operational/support responsibilities.

Then follow Create your first project. For existing-database monitoring, use Onboard an existing database with the appropriate discovery and collection setup.


Getting started ยท Installation sequence