Database settings
System database selection begins in Connections.json; General Setup is then loaded from the selected VxConfig as the VX_SETUP module. Do not confuse these system roles with reusable DB Connection modules used inside integrations.
| Role | Purpose | Important boundary |
|---|---|---|
| Config / ConfigTest | VxConfig modules, relationships and setup for production/test | Determines the configuration context loaded by Designer and services |
| Log / LogTest | Logical log database mapping | Reviewed core SQLL resolves to the active configuration connection for VX_LOG*; verify the deployed schema before assuming a separate log server |
| Data / DataTest | VxData business transaction data | Separate from configuration; access and schema depend on the integration/portal deployment |
The Connections.json database profile controls engine type, host, database, authentication, username/password, driver and certificate trust. Change those values through the environment procedure, not as a speculative General Setup tuning action.
Safe validation
- Confirm the current connection key and test/production context.
- Verify actual Config/Log/Data hosts and databases against the approved environment record.
- Test under both the interactive and service identities.
- Confirm schema updates are applied before service start; reviewed service startup does not run the upgrade check.
- Run a controlled read/write Flow and inspect the actual output and log persistence.
See environment properties and the DB Connection guide for integration databases.