How do I edit the config.xml file?

A. 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:

􀁺 Use the Administration Console. See “Using the Administration Console” in the

Administration Console Online Help.

􀁺 If you want to create scripts that automate domain management, use the weblogic.Admin

utility. See “weblogic.Admin Command-Line Reference” in the WebLogic Server

Command Reference.

􀁺 If you want to create Java-based management applications, use the Java Management

Extensions (JMX) Application Programming Interface (API). See the Programming

WebLogic Management Services with JMX guide.

􀁺 If you want to edit the config.xml file directly (not recommended), see the BEA

WebLogic Server Configuration Reference.

What is the easiest way to set the classpath?

WebLogic Server installs the following script that you can use to set the classpath that a server

requires:

WL_HOME\server\bin\setWLSEnv.cmd (on Windows)

WL_HOME/server/bin/setWLSEnv.sh (on UNIX)

where WL_HOME is the directory in which you installed WebLogic Server. For more information,

see “Setting the Classpath” in the WebLogic Server Command Reference.

Can I start a Managed Server if the Administration Server is unavailable?

FAQs: Administration and Configuration

12

A. By default, if a Managed Server is unable to connect to the specified Administration Server

during startup, it can retrieve its configuration by reading a configuration file and other files

directly. You cannot change the server’s configuration until the Administration Server is

available. A Managed Server that starts in this way is running in Managed Server Independence

mode. For more information, see “Starting a Managed Server When the Administration Server Is

Not Accessible” in Configuring and Managing WebLogic Server.

How do I provide user credentials for starting a server?

Q.

A. When you create a domain, the Configuration Wizard prompts you to provide the username

and password for an initial administrative user. If you create the domain in development mode,

the wizard saves the username and encrypted password in a boot identity file. A WebLogic Server

instance can refer to a boot identity file during its startup process. If a server instance does not

find such a file, it prompts you to enter credentials.

If you create a domain in production mode, or if you want to change user credentials in an existing

boot identity file, you can create a new boot identity file. WebLogic Server does not support

copying a boot identity file from one server root directory to another. For information on creating

and using boot identity files, see “Boot Identity Files” in Administration Console Online Help.