Administrator's Configuration File Reference

compared with
Current by Sudha.Bhat
on Jun 07, 2009 21:47.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View page history
The {{obj.conf}} file contains directives for HTTP request processing. The {{obj.conf}} file is located in the {{_instance_dir_/config}} directory.
During Web Server installation an {{obj.conf}} file is created. If you configure multiple virtual servers using the Admin Console or CLI, separate {{obj.conf}} files may be created for each virtual server. These files are named {{virtual-server-name-obj.conf}}, where {{virtual-server-name}} is the name of the virtual server. The newly created {{virtual-server-name-obj.conf}} becomes functional. This can be verified from the {{server.xml}}, where the name of the functional {{obj.conf}} gets is updated.

When changes made through Admin Console or CLI does not impact the {{obj.conf}}, for example changing log-level, no new virtual server specific {{obj.conf}} files are created and the default {{obj.conf}} will be used for all the virtual servers of the configuration.
From this point onwards, the {{obj.conf}} file is neither updated, used, nor deleted. However, if the user wants to modify the {{obj.conf}} file for either of the two virtual servers, they should edit the respective file only and not the original {{obj.conf}} file.
{info:title=Note -}When another new virtual server vs3 is added, a new vs3-obj.conf should be created, updated in the server.xml and become functional. However, this fails to happen and the existing obj.conf is shared by the vs3. This behavior is a known issue and is recorded as a bug CR 6754145.
{info:title=Note -}When another new virtual server {{vs3}} is added, a new {{vs3-obj.conf}} should be created, updated in the {{server.xml}} and become functional. However, this fails to happen and the existing {{obj.conf}} is shared by the {{vs3}}. This behavior is a known issue and is recorded as a bug {{CR 6754145}}.
{info}

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact