InfoCenter Home > 6.6.0.3b: Working with server configuration files, using the Web administrative console
Using the default configuration fileBy 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 consoleTo open a server configuration file other than one that is currently loaded:
Specifying a server configuration file to load when the console opensWhen 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 fileIt 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:
Saving configuration filesTo save a configuration file:
Saving configuration files under different namesTo save a configuration file using a different name than its current name:
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 filesTo create a new configuration file by using an existing file as a template.
Temporary configuration files resulting from session timeoutIf 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:
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. |
| ||
|