Setting database options

You can view and configure information about the database that you are using from the Server Information form. 

Best practice
We recommend using the AR System Management Console to set the database options. For more information, see Setting-global-level-and-local-level-configurations-for-a-server-group

To display and update information about the database

Important

This form shows the local level value of the configuration. If a local value does not exist, the form displays the global level configuration. If you modify the value on this form, the local level configuration value is modified.

For example, if a configuration shows global level value and you modify the value by using this form, the local level value gets created for the configuration.

  1. In a browser, open the AR System Administration Console, and select System > General > Server Information. 
    The AR System Administration: Server Information form appears. 
  2. Click the Database tab.
    The information displayed on this tab varies depending on the relational database that you have installed. 
    221_ServerInfo-Database.png
     

  3. Enter the following information as needed:
    Database tab fields

     

  4. Click Apply.

Considerations when generating reports against a read-only database

When you generate reports against a read-only database, and you modify objects such as forms, fields, or active links, you must restart the AR System server pointing to the read-only database so that the schema changes are reflected.

This applies to all objects that the AR System server caches. The objects can be modified through Developer Studio, Innovation Studio, D2P deployment, bundle deployment, or any other mechanism.

Using a read-only database

The AR System server automatically detects if you have a read-only database. AR System does not support the following features with a read-only database. You need to disable the following features through Java Driver when you are using a Read-only database. Refer to Runtime-configuration to run the Java Driver program.

Use the procedure shown below in the example to disable the features.

Example — Using Java Driver command to disable archiving for server group
Command: ssi
SET SERVER INFO
   Number of server info operations (0): 1
    Operation (1-443) (1):419
Datatype
Null/Key/Int/Real/Char/DiaryList/Enum/Time/Bitmask/Byte   
Decimal/attach/currency/date/timeofday/join/trim/control/Table/Column/ulong/coords/view/display
(0 - 14, 30-34, 40-43) (0): 2
Integer Value (0): 1
Set Server Information Status
ReturnCode:  OK
Status List : 0 items 

Enter the ID for the feature to be disabled on the line below:

Operation (1-443) (1):419

Replace 419 with the ID for the feature to be disabled. Refer to the table below for IDs.

Feature

ID

Archiving 

ID for single server environment – 191

ID for server group environment – 419

Escalation

ID for single server environment – 143

ID for server group environment – 422

Full Text Search

ID – 190

Vendor form search

You cannot search Vendor form if you have read-only database because Vendor form search results in creating temporary tables.

Important

To recreate hash for a database password, update the new database password in the ar.cfg file or Centralized Configuration by using the Db-password parameter. Set the password in clear text and restart the server. After restart, the server hashes the clear text string.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*