This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Setting database options

You can view and configure information about the database that you are using.

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 a 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.
    AR System Administration: Server Information form—Database tab

    The information displayed on this tab varies depending on the relational database you have installed.
  3. Edit the options, as needed:

    Database tab fields

    Field NameDescription
    Database Type

    Displays the type of database that the AR System server is using.

    Database Home

    (UNIX only) Displays the directory path of the underlying database that the AR System server is using.

    Database Name

    Displays the name of the database created for AR System in the underlying database server.

    Database Version

    Displays the version of the database that the AR System server is using.

    Database User Name

    Displays the user name that AR System uses to access the database.

    Database Password

    (Oracle, Microsoft SQL Server databases only) Enables you to define the password that AR System uses to access the database. The existing password is not displayed. To change the password, enter a value in the Database Password field. The default database password created by AR System is AR#Admin#. If you changed the password and do not remember it or if you changed it outside AR System and must reflect the change in AR System, log on to the database as the database administrator and change it back to the default. If the encrypted password is in the ar.conf configuration file, delete it from that file. Important: The AR System server does not accept a single character as database password. We recommend having a password between 5 to 30 characters.

    Database Configuration File

    Displays the contents of the ardb configuration file used by the advanced AR System feature that appends clauses to the SQL statements that create tables and indexes. For more information about the ardb file, see ardb.cfg or ardb.conf.

    Database Case SensitiveIndicates whether the database in use is case-sensitive. This field is read-only.
    Request ID Uses Clustered Index(Microsoft SQL Server only) Indicates whether AR System creates the Request ID field as a clustered index to boost performance. By default, this option is selected.
    Store CLOB In-Row

    (Oracle databases only) Specifies how Oracle CLOBs are stored:

    By default, this option is selected, and CLOBs are created "in row." In-row CLOBs can increase CPU usage, but In-Row CLOBS perform better than Out-Row CLOBS. If the CLOB data in a specific row gets too large, it is automatically moved to "out row."

    If you do not select this option, CLOBs are created "out row." Out-Row CLOBs can cause the database to grow rapidly and will take longer to retrieve the CLOB data.

    Before installing AR System applications, select this option so that all database tables for applications are created in the desired manner.

  4. Click Apply.

Best practices when generating reports against a read-only database

You must restart the AR System server before generating reports against a read-only database that contains modified or customized objects such as forms, fields, or active links. 
Restarting the AR System server ensures that the changes you made to the schema are reflected in your report.

This recommendation is applicable to all objects that are cached by the AR System server . You can modify the objects through Developer Studio , Innovation Studio, D2P deployment, or any other mechanism that you follow to modify the objects.

(SaaS subscribers) If there are any changes in the production system and you want those changes to be reflected in a report, contact BMC support Open link .

(Only for on-premises deployments) 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. For information about how to run the Java Driver program, see Runtime configuration.

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.

FeatureID
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 a 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.

Was this page helpful? Yes No Submitting... Thank you

Comments