Chapter 3 Customizing Configuration Files

This chapter explains the configuration settings for customizing the operations of Sun Update Connection – Enterprise through the command-line. In addition, this chapter explains how to configure the Apache logs of the server application, outside of the configuration files.

This chapter covers the following topics:

• Viewing and Changing Configuration Files

• Overriding Configurations

• Configuring Sun Update Connection – Enterprise to Create Apache Logs

Viewing and Changing Configuration Files

This section explains how to access the uce.rc configuration file. It is strongly recommended that you do not change this file; open for viewing only. To make changes to the configuration of an application, change the .uce.rc override file.

The server, Dependency Manager (DM), agents, and the console each has a uce.rc file:

• Server - /usr/local/uce/_server/cgi_bin/uce.rc

• Dependency Manager - /usr/local/uce/engine/bin/uce.rc

• Agents (on the host) - /opt/local/uce/agent/bin/uce.rc

• Console - ~/.uce_console/uce.rc (where ~ is the home of the installation user)

  The most common configuration parameters are offered for viewing and changing from within the console, in the Settings window.

  You can overwrite other values of the factory default configuration file with the .uce.rc override file, which is stored in the same directory as the uce.rc file.

• uce.rc file - Complete list of factory default parameters and values

• .uce.rc file - User configured environment created by ezInstaller, contains only those parameters that override the factory defaults

  To view all parameters, open the uce.rc file. To override a parameter, copy the parameter line from the default file (close without saving) to the .uce.rc file and make the change in the parameter value.

  The following table shows the commands to open override files.

  ---

  Note –

  Use a text editor, such as emacs, gedit, or vi to edit the files. The vi text editor is used in this document.

  ---

When you change a value with a copied parameter to .uce.rc, the new value is always applied, until you delete the line. The next section explains how to override configuration values for one session.

Overriding Configurations

You can start the console with override values, which supersede .uce.rc values (and therefore also the uce.rc values).

To find the correct parameter name, open the uce.rc file (but do not change this file!). If you look at a line from the right (the end) and go leftward, the parameter name ends to the left of the comma (separating the parameter and the value), and begins to the right of the first dot that you encounter:

( invisible.debug.__group1.debug_mode, false );

You can start the console from the command line, with an explicit parameter value, for the current session. The parameter value reverts to the .uce.rc value (or to the uce.rc value if it does not appear in the override file) when you restart the application.

Syntax: uce_console -<parameter> <value>

uce_console -update_director_mode true- For updating remote agents

uce_console -debug_mode true -debug_log_level 5- For debugging; technical support might ask you to turn on these parameters, to help them find and fix problems.

Configuring Sun Update Connection – Enterprise to Create Apache Logs

The server application in the system dependency server can create logs for the embedded Apache server. To regulate the size of the Apache-Sun Update Connection – Enterprise logs, go to the logrotate file; controls over these specific logs are not in the uce.rc file.

To Control Apache Sun Update Connection – Enterprise Logs

1. Check if you have the logrotate file: /etc/logrotate.d/uce_server

   If this file is not on your system, create a new file with this path name.

   If you do not have the logrotate application, use Sun Update Connection – Enterprise to install it on the SDS system. Use a cron job to run the log rotations hourly, or daily.

2. Open /etc/logrotate.d/uce_server for editing.

   Its content should include:

   /var/log/uce_server/access_log
   /var/log/uce_server/error_log
   /var/log/uce_server/ssl_engine_log
   /var/log/uce_server/ssl_request_log
   {
       rotate 2
       missingok
       size=100M
       compress
       sharedscripts
       postrotate
           /etc/init.d/uce_server graceful
       endscript
   }

   If this content is not in the file, add it.

3. To have more rotating files, increase the value of the rotate parameter.

4. To ensure your logs are small, decrease the value of the size parameter.