4.4 Modifying a Configuration

After you create a configuration and create instances from it, you might need to change some of the settings—log preferences, performance parameters, virtual server listener, origin-server pools, and so on.

You can modify a configuration by using either the administration console or the CLI.

Note:

The CLI examples in this section are shown in shell mode (tadm>). For information about invoking the CLI shell, see Section 2.3.1, "Accessing the Command-Line Interface."

Modifying a Configuration Using the Administration Console

To modify a configuration by using the administration console, do the following:

1. Log in to the administration console, as described in Section 2.3.2, "Accessing the Administration Console."

2. Click the Configurations button that is situated at the upper left corner of the page.

   A list of the available configurations is displayed.

3. Select the configuration that you want to modify.

4. In the navigation pane, you can select the following additional categories of settings for the configuration. The parameters relevant to the selected category are displayed on the main pane.

   • SSL

     • Settings for PKCS#11 Tokens. For more information, see Section 11.5, "Managing PKCS#11 Tokens."

     • Schedule and manage CRL-update events. For more information, see Section 11.6.2, "Installing CRLs Automatically."

     • SSL/TLS caching preferences. For more information, see Section 15.6.1, "SSL/TLS Session Caching."

   • Logging

     • Set and change parameters for the server log file—name and location of the log file, log level, date format, and so on.

     • Enable and disable the access log.

     • Set and change parameters for the access log file—name and location of the log file and log format

     • Schedule and manage events to rotate the server and access log files.

     • Configure access-log buffer settings to tune performance.

     For more information, see Chapter 12, "Managing Logs."

   • Advanced Settings

     • Specify general settings: the server user ID, the temporary directory in which the process ID and socket information for the instances of the configuration are stored, and the localization preferences.

     • Configure DNS lookup and cache settings.

       For more information, see Section 15.5, "Tuning DNS Caching Settings."

     • Create, enable, disable, view, delete events for the configuration. For more information, see Section 5.6, "Controlling Oracle Traffic Director Instances Through Scheduled Events."

     • View a list of available backups for the configuration and restore from a backup configuration. For more information, see Section 4.9, "Restoring a Configuration from a Backup."

   • HTTP, under Advanced Settings: Set and change parameters to tune the performance of the virtual servers defined for the configuration—such as, request buffer size, response buffer size, timeout thresholds for the request body and header, thread-pool settings, and keep-alive settings.

     For more information, see Section 15.4, "Tuning HTTP Request and Response Limits."

   • Monitoring, under Advanced Settings

     • Enable and disable statistics collection, profiling, and the SNMP subagent.

     • Specify the statistics-collection interval.

     For more information, see Chapter 13, "Monitoring Oracle Traffic Director Instances."

   Note:

   For information about modifying origin servers, origin-server pools, listeners, and virtual servers, see:

   • Section 6.3, "Modifying an Origin-Server Pool"

   • Section 7.3, "Modifying an Origin Server"

   • Section 8.3, "Modifying a Virtual Server"

   • Section 10.3, "Modifying a Listener"

5. Specify the parameters that you want to change.

   On-screen help and prompts are provided for all of the parameters.

   When you change the value in a field or tab out of a text field that you changed, the Save button near the upper right corner of the page is enabled.

   At any time, you can discard the changes by clicking the Reset button.

6. After making the required changes, click Save.

   • A message, confirming that the updated configuration was saved, is displayed in the Console Messages pane.

   • In addition, the Deployment Pending message is displayed at the top of the main pane. You can either deploy the updated configuration immediately by clicking Deploy Changes, or you can do so later after making further changes as described in Section 4.3, "Deploying a Configuration."

   Caution:

   In the Advanced Settings page, if you change the Temporary Directory value, you should first stop all the instances of the configuration, deploy the changes, and then start the instances.

   If you deploy the changes without stopping the running instances, an error would occur when you attempt to stop the instances later. For information about solving this problem, see Section 16.2.8, "Unable to stop instance after changing the temporary directory."

Modifying a Configuration Using the CLI

The CLI provides several commands (see Table 4-1) that you can use to change specific parameters of a configuration.

Note:

For information about the CLI commands to change the properties of virtual servers, listeners, origin server pools, and origin servers in a configuration, see the following chapters:

• Chapter 6, "Managing Origin-Server Pools"

• Chapter 7, "Managing Origin Servers"

• Chapter 8, "Managing Virtual Servers"

• Chapter 10, "Managing Listeners"

Table 4-1 CLI Commands for Modifying a Configuration

Task	CLI Commands
Change the server user and temporary directory	set-config-prop
Change access-log buffer properties	set-access-log-buffer-prop get-access-log-buffer-prop
Change caching properties	set-cache-prop get-cache-prop
Change DNS properties	set-dns-prop get-dns-prop
Change DNS caching properties	set-dns-cache-prop get-dns-cache-prop
Change HTTP request properties	set-http-prop get-http-prop
Change keep-alive settings for client connections	set-keep-alive-prop get-keep-alive-prop
Change the default language	set-localization-prop get-localization-prop
Change error log settings	set-log-prop get-log-prop
Change PKCS #11 encryption settings	set-pkcs11-prop get-pkcs11-prop
Change QoS settings	set-qos-prop get-qos-prop
Enable SNMP	set-snmp-prop set-snmp-prop
Change SSL/TLS session caching properties	set-ssl-session-cache-prop get-ssl-session-cache-prop
Change statistics collection properties	set-stats-prop get-stats-prop
Change HTTP thread pool properties	set-thread-pool-prop get-thread-pool-prop

For example, the following command changes the location of the error log file for the configuration soa to /home/log/errors.log.

tadm> set-log-prop --config=soa log-file=/home/log/errors.log
OTD-70201 Command 'set-log-prop' ran successfully.

For the updated configuration to take effect, you should deploy it to the Oracle Traffic Director instances by using the deploy-config command.

For more information about the CLI commands mentioned in this section, see the Oracle Traffic Director Command-Line Reference or run the commands with the --help option.