FAQs: Administration and Configuration

 

• What are safeguards for modifying the config.xml file?

• How do I edit the config.xml file?

What are safeguards for modifying the config.xml file?

BEA recommends that you use the WebLogic Server Administration Console to edit the config.xml file. If you need to edit the config.xml file directly, we recommend that:

• You always save a copy of your config.xml file before editing it. If your edits cause errors that prevent you from booting, you can at least revert to your saved version.

• You manually edit the config.xml file for a domain when a domain is not active. If you edit the configuration file while the domain is active, any changes you make manually will likely be overwritten by the system. Furthermore, all changes you make by hand while the domain is active are ignored by the system at run time.

• Because there is no validation or value checking when you edit config.xml manually, type-checking occurs when you load the configuration file for the first time, that is, when you restart the Administration Server. At that point, any invalid XML or attribute value is detected and the domain fails to boot.

How do I edit the config.xml file?

The persistent configuration for a domain of WebLogic Servers and clusters is stored in an XML configuration file (config.xml). You can modify this file in the following ways:

• The recommended way for users to modify or monitor a domain's configuration is to use the Administration Console.

• WebLogic Server includes a configuration Application Programming Interface (API), which programs can use to modify configuration attributes of resources in the domain.

• You can access the attributes of a domain with the WebLogic Server command-line utility. This utility is provided for people who want to create scripts to automate domain management. See Commands for Managing a WebLogic Domain in the Administration Guide.