ORDSwatch

Hosted edition

Managing ORDS configuration

Configuration → Manage lets you view and change an instance's ORDS configuration from ORDSwatch: settings, database pools, pool passwords and ORDS users. The agent on the ORDS server makes every change with ORDS's own command line (ords config …), so ORDS checks each value before saving it and pool passwords go into its encrypted wallet. Available on the Professional and Enterprise plans, in both the hosted and the self-hosted edition, with ORDSwatch agent 2.10 or later.

Everyone can look; only admins can change anything. Every change is recorded in the ORDSwatch log with the name of the person who made it.

Settings

Choose the instance and the database pool. The list shows every setting ORDS knows for that pool, with its current value and where the value comes from:

  • This pool — set for this pool only;
  • Global — set for all pools of the instance;
  • Default — not set, ORDS's built-in default applies;
  • Wallet — a password, always shown as ******.

Use the buttons above the list to narrow it to pool size, database, features, HTTP server, security or cache settings, or tick Changed only.

Click Edit to see ORDS's own description and default, enter a new value and choose whether it applies to this pool or to every pool. Settings that only exist for the whole instance (for example the HTTP port) are always saved globally. Reset to default removes a value you set, so the pool goes back to the global value or ORDS's default. Add setting sets one that is not listed yet; ORDS refuses names it doesn't know.

ORDS reads most settings when it starts. After a change, ORDSwatch shows Restart ORDS — restart when it suits you.

Pools

The Pools card lists the pools configured for the instance and whether each one is open in the running ORDS.

  • Password stores a new password for the pool's database user in ORDS's wallet. Change the password in the database first; ORDS uses the new one from its next restart. The password is passed to ORDS on the server and is never stored or logged by ORDSwatch.
  • Recycle closes all the pool's connections in the running ORDS; ORDS opens fresh ones on the next request, with no restart. Use it after a database failover or when connections are stuck.
  • Add pool adds the connection details for a new pool — host, port and service name, or a TNS alias — and its database user. It only writes ORDS's configuration (ords install --config-only); nothing is changed in the database, so ORDS must already be installed there. Restart ORDS to open it.

ORDS users

The users in ORDS's own credentials file — for example the user ORDSwatch creates for Metrics, or administrators of the Instance API. Admins can add a user with one or more roles, or remove one. The user ORDSwatch uses for Metrics can't be removed here.

Installing, upgrading or removing ORDS in the database is not available from ORDSwatch — do that with ords install on the server.