InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.3b: Working with server configuration files, using the Web administrative console

6.6.0.3b: Working with server configuration files, using the Web administrative console

Using the default configuration file

By default, when you open the console, the default server configuration file is loaded.

The following tasks describe how to switch to a different configuration file, either after opening the console, or for the next time you open the console.

Opening other server configuration files after starting the console

To open a server configuration file other than one that is currently loaded:

  1. Recommended. Save the configuration file that you are working with now, so that its changes are not lost.
  2. View the Configuration Files panel by either:

    • Clicking Open a configuration file to edit with the console link on the console home page.
    • Clicking the Configuration menu item.
  3. On the Configuration Files panel, specify the configuration file to open. To do so, you can either:

    • Select from among the files in the config directory.
    • Enter the full path to the file on the server.
  4. Click OK. The specified file will be loaded.
Specifying a server configuration file to load when the console opens

When you open the administrative console, you can specify to use a particular configuration file by passing the file name as a parameter in the browser URL.

For example, the browser URL could be:

http://localhost:9091/admin/edit?configFile=c:/temp/myConfigFile.xml

The above example will load myConfig.xml from the c:/temp directory.

Reviewing and correcting potential problems with a configuration file

It is a good practice to review the problems page and resolve any problems prior to saving your server configuration.

If you make any changes that could result in potential problems with the server configuration file, a link specifying "additional problems have been reported" will be displayed at the top of every page that you view. Click the link to view the problems page.

Prior to saving the configuration file, read the descriptive text about the problems, as some types of problems can result in unwanted behavior if an application server is restarted using the configuration file that has the problems.

The problem page format includes an Object ID that you can use to locate each problem in the configuration file:

  1. Recommended. Save a backup copy of the configuration to a temporary file (see below for instructions) in case subsequent changes aggravate the problem.
  2. Open the original server configuration file in a text editor or XML editor and search for the problem ID.
  3. The XML element with the problem ID is the element that has problems.
  4. Return to the console, and look at the configuration for the object type pertaining to the element that was found to have problems. For example, it could be the XML element pertaining to the virtual host object in the console. Adjust the configuration to eliminate the error.
  5. Determine whether the "additional problems have been reported" link is still visible (indicating that errors remain).
  6. Repeat the above steps until all errors have been eliminated.
  7. When all errors have been eliminated, save the configuration file.
Saving configuration files

To save a configuration file:

  1. View the Save Configuration panel by either:

    • Clicking Save link on the console home page.
    • Clicking the Save menu item.
  2. Select the Save radio button.
  3. Click OK.
Saving configuration files under different names

To save a configuration file using a different name than its current name:

  1. View the Save Configuration panel by either:

    • Clicking Save link on the console home page.
    • Clicking the Save menu item.
  2. Select the Save As radio button.
  3. Specify the full server path and name of the new file.
  4. Click OK.

A copy of the current file is created under the new name and your changes are saved to the new file. (The original configuration file is left unchanged.) The new file is loaded into the console.

Creating new configuration files

To create a new configuration file by using an existing file as a template.

  1. Recommended. Save the configuration file that you are working with now, so that its changes are not lost.
  2. Click the Create link on the console home page to display the Configuration Files panel.
  3. Select an existing configuration file to use as template. To do so, you can either:

    • Select from among files in the config directory.
    • Enter the full path to the file on there server.
  4. Specify the name of the new file to create. Specify the full path to the file on the server.
  5. Click OK. The new file will be created and loaded into the console.
Temporary configuration files resulting from session timeout

If the console is not used for 15 minutes or more, the session times out. The same thing happens if you close the browser window without saving the configuration file. The changes to the file will be saved to a temporary file when the session times out, after 15 minutes.

When a session times out, the configuration file in use is saved under the userid/timeout directory under the ServletContext's temp area. This is value of the javax.servlet.context.tempdir attribute of the ServletContext. By default, it is:

product_installation_root/temp/hostname/Administration/admin/admin.war

You can change the temp area by specifying it as a value for the tempDir init-param of the action servlet in the deployment descriptor (web.xml) of the administrative application.

The next time you log on to the console, you are prompted to load the saved configuration file. If you decide to load the saved file:

  1. If a file with the same name exists in the product_installation_root/config directory, that file is moved to the userid/backup directory in the temp area.
  2. The saved file is moved to the product_installation_root/config directory.
  3. The file is then loaded.

If you decide not to load the saved file, it is deleted from the userid/timeout directory in the temp area.

The configuration file is also saved automatically when the same user ID logs into the non-secured console again, effectively starting a different session. This process is equivalent to forcing the existing user ID out of session, similar to a session timeout.

Go to previous article: Format of problems page for server configuration Go to next article: Starting, stopping, and logging into the Web administrative console

 

 
Go to previous article: Format of problems page for server configuration Go to next article: Starting, stopping, and logging into the Web administrative console