Database Information application

The Database Information application provides information and access for database objects and attributes. You can make limited changes to data structures, such as associating a domain with an attribute, making an attribute required, or changing the search type.

You configure changes in the application in the nonproduction environment. Apply the changes or configure changes in Admin mode. The following table contains information about the differences between applying changes and configuring with Admin mode:

Table 1. Configuration options
Option Description Actions
Apply Changes Full live configuration. Use only when few users are logged in and no transactions are expected. Applies changes without logging users out of the system. Cache is deleted and re-created, so if transactions occur while the cache is being changed, the transactions can be lost.
Manage Admin Mode Allows you to turn on Admin mode and specify a number of minutes after which users are logged out. In Admin mode, partial live configuration is turned on. No transactions can occur during Admin mode. To receive email reports, set the mail.smtp.host property.

When configuration is complete, turn off Admin mode.

Logs users out of the system with exception of the administrator with permission to log in during Admin mode. Suspends cron tasks and disables event listeners. If an affected table cannot be changed with data in it, table data is backed up first.

After you configure your changes, you export the updated configuration to a .json file with the Application Export action. Then import that file to your production environment with the Application Import action in that environment.

When you import changed files from the nonproduction to the production environment, be aware of data dependencies. Import data in order of fewest dependencies first. For example, if you were to add a domain, associate the domain with an extra field, and then add the extra field to a presentation, you import the exported files in this order:
  1. .json file for the domain change
  2. .json file for the database information change
  3. .xml file for the application presentation