weblogic.Server Command-Line Reference

weblogic.Server Command-Line Reference

Contents

Environment and Syntax
Default Behavior
Configuration Options
Start a Server Instance
Create a Domain
Verify Attribute Values

See also:

Starting Administration Servers
Starting Managed Servers
Overview of Node Manager

Overview

The weblogic.Server class is the main class for a WebLogic Server instance. You start a server instance by invoking weblogic.Server in a Java command. You can invoke the class directly in a command prompt (shell), indirectly through scripts, or through the Node Manager.

Environment

To set up your environment for the weblogic.Server command:

Install and configure the WebLogic Server software, as described in the WebLogic Server Installation Guide.
Add WebLogic Server classes to the CLASSPATH environment variable, as described in Setting the Classpath.
Include a Java Virtual Machine (JVM) in your PATH environment variable. You can use any JVM that is listed in the Supported Configurations page at http://e-docs.bea.com/wls/certifications/index.html.
If you do not include a JVM in the PATH environment variable, provide a pathname for the Java executable file that the JVM provides.

Setting the Classpath

The Java Virtual Machine (JVM) uses a setting called classpath to locate essential files and directories.
You can use the following script to set the classpath for a WebLogic Server:
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.
Instead of using setWLSEnv, you can use an environment variable or the -classpath argument in the startup command. Regardless of the method you choose, include the following in the classpath for the JVM that runs instances of WebLogic Server:
WL_HOME/server/lib/weblogic_sp.jar
Depending on which WebLogic Server release, service pack, or patch that you have installed, this file might not exist on your system. Regardless of whether the file currently exists on your system, we recommend that you include WL_HOME/server/lib/weblogic_sp.jar in your classpath to ensure compatibility with any updates. You must add this file to the classpath before you add weblogic.jar.
WL_HOME/server/lib/weblogic.jar
If you use the trial version of PointBase, an all-Java database management system, then include the following files:
WL_HOME/common/eval/pointbase/lib/
pbserver43.jar and pbclient43.jar
If you use WebLogic Enterprise Connectivity, include the following files:
WL_HOME/server/lib/wlepool.jar
WL_HOME/server/lib/wleorb.jar

The shell environment in which you run a server determines which character you use to separate path elements. On Windows, you typically use a semicolon (;). In a BASH shell, you typically use a colon (:).

Syntax

The syntax for invoking weblogic.Server is as follows:
java [options] weblogic.Server [-help]
The java weblogic.Server -help command returns a list of frequently used options.

Default Behavior

If you have set up the required environment described in Environment, when you enter the command java weblogic.Server with no options, WebLogic Server does the following:

Looks in the current directory for a file named config.xml.
If config.xml exists in the current directory, WebLogic Server does the following:

If only one server instance is defined in ./config.xml, it starts that server instance.
For example, if you issue java weblogic.Server from WL_HOME\samples\domains\medrec, WebLogic Server starts the MedRec server.
If there are multiple server instances defined in ./config.xml, WebLogic Server looks for a server configuration named myserver. If it finds such a server configuration, it starts the myserver instance.
If it does not find a server named myserver, WebLogic Server exits the weblogic.Server process and generates an error message.

If there is no config.xml file in the current directory, WebLogic Server asks if you want to create a domain and server instance. If you answer yes, WebLogic Server does the following:

Creates an server configuration named myserver, and persists the configuration in a file named ./config.xml.
Any options that you specify are persisted to the config.xml file. For example, if you specify -Dweblogic.ListenPort=8001, then WebLogic Server saves 8001 in the config.xml file. For any options that you do not specify, the server instance uses default values.
WebLogic Server also creates a config.xml.booted file, which is a copy of the config.xml file in its state just after the server successfully boots. If the config.xml becomes corrupted, you can boot the server with this config.xml.booted file.
Uses the username and password that you supply to create a user with administrative privileges. It stores the definition of this user along with other basic, security-related data in files named DefaultAuthenticatorInit.ldift and SerializedSystemIni.dat.
WebLogic Server also encrypts and stores your username and password in a boot.properties file, which enables you to bypass the login prompt during subsequent instantiations of the server. For more information, refer to "Boot Identity Files in the Administration Console Online Help.
Creates two scripts, startmydomain.cmd and startmydomain.sh, that you can use to start subsequent instantiations of the server. You can use a text editor to modify startup options such as whether the server starts in production mode or development mode. The startmydomain script contains comments that describe each option.

Note that the server starts as an Administration Server in a new domain. There are no other servers in this domain, nor are any of your deployments or third-party solutions included. You can add them as you would add them to any WebLogic domain.

weblogic.Server Configuration Options

You can use weblogic.Server options to configure the following attributes of a server instance:
JVM Parameters
Location of License and Configuration Data
Server Communication
SSL
Security
Message Output and Logging
Other Server Configuration Options
Clusters

Unless you are creating a new domain as described in Using the weblogic.Server Command Line to Create a Domain, all startup options apply to the current server instantiation; they do not modify the persisted values in an existing config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.
For information on verifying the WebLogic Server attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.

JVM Parameters

The following table describes frequently used options that configure the Java Virtual Machine (JVM) in which the server instance runs. For a complete list of JVM options, refer to the documentation for your specific JVM. For a list of JVMs that can be used with WebLogic Server, refer to the Supported Configurations page at http://e-docs.bea.com/wls/certifications/index.html.

Option
Description
-Xms and -Xmx Specify the minimum and maximum values (in megabytes) for Java heap memory. For example, you might want to start the server with a default allocation of 200 megabytes of Java heap memory to the WebLogic Server. To do so, you can start the server with the java -Xms200m and -Xmx200m options. For best performance it is recommended that the minimum and maximum values be the same so that the JVM does not resize the heap.The values assigned to these parameters can dramatically affect the performance of your WebLogic Server and are provided here only as general defaults. In a production environment you should carefully consider the correct memory heap size to use for your applications and environment.
-classpath The minimum content for this option is described under Setting the Classpath. Instead of using this argument, you can use an environment variable named CLASSPATH to specify the classpath.
-client
-server Used by some JVMs to start a HotSpot virtual machine, which enhances performance. For a list of JVMs that can be used with WebLogic Server, refer to the Supported Configurations page at http://e-docs.bea.com/wls/certifications/certifications/index.html.

Location of License and Configuration Data

All server instances must have access to license and configuration data. The following table provides options for indicating the location of this data.

Option

Description
-Dbea.home=bea_home Specifies the location of the BEA home directory, which contains licensing and other essential information.By default, weblogic.Server determines the location of the BEA home directory based on values in the classpath.
-Dweblogic.RootDirectory=path Specifies the server's root directory. By default, the root directory is the directory from which you issue the start command. For more information, refer to "A Server's Root Directory in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ConfigFile=
file_name Specifies a configuration file for your domain. The file_name value must refer to a valid XML file that conforms to the schema as defined in the "BEA WebLogic Server Configuration Reference."The XML file must exist in the Administration Server's root directory, which is either the current directory or the directory that you specify with -Dweblogic.RootDirectory.The file_name value cannot contain a pathname component. For example, the following value is invalid:-Dweblogic.ConfigFile=c:\mydir\myfile.xml Instead, use the following arguments:-Dweblogic.RootDirectory=c:\mydir
-Dweblogic.ConfigFile=myfile.xml If you do not specify this value, the default is config.xml in the server's root directory.
-Dweblogic.management.GenerateDefaultConfig=true Prevents the weblogic.Server class from prompting for confirmation when creating a config.xml file.Valid only if you invoke weblogic.Server in an empty directory. See Default Behavior.
-Dweblogic.Domain=domain Specifies the name of the domain. If you are using weblogic.Server to create a domain, you can use this option to give the domain a specific name.In addition, this option supports a directory structure that WebLogic Server required in releases prior to 7.0 and continues to support in current releases. Prior to 7.0, all configuration files were required to be located at the following pathname:.../config/domain/config.xml where domain is the name of the domain.If your domain's configuration file conforms to that pathname, and if you invoke the weblogic.Server command from a directory other than config/domain, you can include the -Dweblogic.Domain=domain argument to cause WebLogic Server to search for a config.xml file in a pathname that matches con fig/domain/config.xml.

For information on how a Managed Server retrieves its configuration data, refer to the -Dweblogic.management.server entry in Table 4-3 on page 11.
The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.

Examples

The following example starts an Administration Server instance named SimpleServer. In the example, the config.xml file has been renamed to SimpleDomain.xml and it is located in a directory named c:\my_domains\SimpleDomain. The command itself is issued from the D:\ directory after running WL_HOME\server\bin\setWLSEnv.cmd (where WL_HOME is the directory in which you installed WebLogic Server):
D:\> java -Dweblogic.Name=SimpleServer -Dweblogic.ConfigFile=SimpleDomain.xml -Dweblogic.RootDirectory=c:\my_domains\SimpleDomain weblogic.Server
The following example starts a Managed Server instance named SimpleManagedServer. Specifying a config.xml file is not valid because Managed Servers contact the Administration Server for their configuration data. Multiple instances of WebLogic Server can use the same root directory. However, if your server instances share a root directory, make sure that all relative filenames are unique. In this example, SimpleManagedServer shares its root directory with SimpleServer. The command itself is issued from the D:\ directory after running WL_HOME\server\bin\setWLSEnv.cmd:
D:\> java -Dweblogic.Name=SimpleManagedServer -Dweblogic.management.server=http://localhost:7001 -Dweblogic.RootDirectory=c:\my_domains\SimpleDomain weblogic.Server

Server Communication

The following table describes the options for configuring how servers communicate.

Option

Description
-Dweblogic.management.server=
[protocol://]Admin-host:port Starts a server instance as a Managed Server and specifies the Administration Server that will configure and manage the server instance. The domain's configuration file does not specify whether a server configuration is an Administration Server or a Managed Server. You determine whether a server instance is in the role of Administration Server or Managed Server with the options that you use to start the instance. If you omit the -Dweblogic.management.server option in the start command, the server starts as an Administration Server (although within a given domain, there can be only one active Administration Server instance). Once an Administration Server is running, start all other server configurations as Managed Servers by including the -Dweblogic.management.server option in the start command.For protocol, specify HTTP, HTTPS, T3, or T3S. The T3S and HTTPS protocols require you to enable SSL on the Managed Server and the Administration Server and specify the Administration Server's SSL listen port.
Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.For Admin-host, specify localhost or the DNS name or IP address of the machine where the Administration Server is running.For port, specify the Administration Server's listen port. If you set up the domain-side administration port, port must specify the domain-wide administration port.For more information on configuring a connection to the Administration Server, refer to "Configuring a Connection to the Administration Server" in the Administration Console Online Help.
-Dweblogic.ListenAddress=host Specifies the address at which this server instance listens for requests. The host value must be either the DNS name or the IP address of the computer that is hosting the server instance.This startup option overrides any listen address value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.For more information, refer to "Configuring the Listen Address in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ListenPort=
portnumber Enables and specifies the plain-text (non-SSL) listen port for the server instance. This startup option overrides any listen port value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.The default listen port is 7001.For more information, refer to "Configuring the Listen Ports in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ssl.ListenPort=
portnumber Enables and specifies the port at which this WebLogic Server instance listens for SSL connection requests.This startup option overrides any SSL listen port value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.The default SSL listen port is 7002.For more information, refer to "Configuring the Listen Ports in the Configuring and Managing WebLogic Server guide.
-Dweblogic.management.
discover={true | false} Determines whether an Administration Server recovers control of a domain after the server fails and is restarted.A true value causes an Administration Server to communicate with all knows Managed Servers and inform them that the Administration Server is running.A false value prevents an Administration Server from communicating with any Managed Servers that are currently active in the domain.
Caution: Specify false for this option only in the development environment of a single server. Specifying false can cause server instances in the domain to have an inconsistent set of deployed modules.For information on re-establishing administrative control over Managed Servers after an Administration Server has already started, refer to DISCOVERMANAGEDSERVER.

The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.

SSL

Each Weblogic Server instance uses an instance of weblogic.management.security.SSLMBean to represent its SSL configuration. All of the options in the following table that start with -Dweblogic.security.SSL modify the configuration of the server's SSLMBean. For example, the -Dweblogic.security.SSL.ignoreHostnameVerification option sets the value of the SSLMBean's ignoreHostnameVerification attribute.
The following table describes the options for configuring a server to communicate using Secure Sockets Layer (SSL).

Option

Description
-Dweblogic.security.SSL.
ignoreHostnameVerification=
true Disables host-name verification, which enables you to use the demonstration digital certificates that are shipped with WebLogic Server.By default, when a WebLogic Server instance is in the role of SSL client (it is trying to connect to some other server or application via SSL), it verifies that the host name that the SSL server returns in its digital certificate matches the host name of the URL used to connect to the SSL server. If the host names do not match, the connection is dropped.If you disable host name verification, either by using this option or by modifying the server's configuration in the config.xml file, the server instance does not verify host names when it is in the role of SSL client.
Note: BEA does not recommend using the demonstration digital certificates or turning off host name verification in a production environment.This startup option overrides any Host Name Verification setting in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.For more information, refer to "Using Hostname Verification in the Managing WebLogic Security guide.
-Dweblogic.security.SSL.
HostnameVerifier=
hostnameverifierimplmentation Specifies the name of a custom Host Name Verifier class. The class must implement the weblogic.security.SSL.HostnameVerifier interface.
-Dweblogic.security.SSL.
sessionCache.size=
sessionCacheSize -Dweblogic.security.SSL.
sessionCache.ttl=
sessionCacheTimeToLive Modifies the default server-session caching size and time-to-live for SSL session caching.The sessionCacheSize value specifies the number of items in session cache and the sessionCacheTimeToLive value specifies (in seconds) the session cache time-to-live. For sessionCache.size:
The minimum value is 1

The maximum value is 65537

The default value is 211
For sessionCache.ttl:
The minimum value is 1

The maximum value is Integer.MAX_VALUE

The default value is 600

-Dweblogic.management.
pkpassword=pkpassword Specifies the password for retrieving SSL private keys from an encrypted flat file. Use this option if you store private keys in an encrypted flat file.
-Dweblogic.security.SSL.
trustedCAKeyStore=path Deprecated and ignored by default.If you configure a server instance to use the SSL features that were available before WebLogic Server 8.1, you can use this argument to specify the certificate authorities that the server or client trusts. The path value must be a relative or qualified name to the Sun JKS keystore file (contains a repository of keys and certificates).If a server instance is using the SSL features that were available before 8.1, and if you do not specify this argument, the WebLogic Server or client trusts all of the certificates that are specified in JAVA_HOME\jre\lib\security\cacerts. We recommend that you do not use the demonstration certificate authorities in any type of production deployment.For more information, refer to "Configuring SSL in the Managing WebLogic Security guide.

The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.

Setting Additional SSL Attributes

To set additional SSL attributes from the startup command, do the following:

To determine which SSL attributes can be configured from startup options, view the WebLogic Server Javadoc for the SSLMBean and ServerMBean. The Javadoc also indicates valid values for each attribute.
Each attribute that SSLMBean and ServerMBean expose as a setter method can be set by a startup option.
To set attributes in the SSLMBean, add the following option to the start command:
-Dweblogic.ssl.attribute-name=value
where attribute-name is the name of the MBean's setter method without the set prefix.
To set attributes in the ServerMBean, add the following option to the start command:
-Dweblogic.server.attribute-name=value
where attribute-name is the name of the MBean's setter method without the set prefix.

For example, the SSLMBean exposes its Enabled attribute with the following setter method:
setEnabled()
To enable SSL for a server instance named MedRecServer, use the following command when you start MedRecServer:
java -Dweblogic.Name=MedRecServer


   -Dweblogic.ssl.Enabled=true weblogic.Server
The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Security
The following table describes the options for configuring general security parameters.
Table 4-5 Options for General Security Parameters

Option

Description

-Dweblogic.management.
username=username

Specifies the username under which the server instance will run.
The username must belong to a role that has permission to start a server. For information on roles and permissions, refer to "Security Roles in the Securing WebLogic Resources guide.
This option prevents a server instance from using any boot identity file and overrides other startup options that cause a server to use boot identity files. For more information, refer to "Boot Identity Files in the Administration Console Online Help.

-Dweblogic.management.
password=password

Specifies the user password.
This option prevents a server instance from using any boot identity file and overrides other startup options that cause a server to use boot identity files. For more information, refer to "Boot Identity Files in the Administration Console Online Help.

-Dweblogic.system.
StoreBootIdentity=true

Creates a boot.properties file in the server's root directory. The file contains the username and an encrypted version of the password that was used to start the server.
Do not specify this argument in a server's ServerStartMBean (Remote Startup tab in the Administration Console). For more information, refer to "Specifying User Credentials When Starting a Server with the Node Manager in the Administration Console Online Help.
BEA recommends that you do not add this argument to a startup script. Instead, use it only when you want to create a boot.properties file.
For more information, refer to "Boot Identity Files in the Administration Console Online Help.

-Dweblogic.system.
BootIdentityFile=filename

Specifies a boot identity file that contains a username and password.
The filename value must be the fully qualified pathname of a valid boot identity file. For example:
-Dweblogic.system.BootIdentityFile=C:\BEA\
wlserver8.1\user_config\mydomain\myidentity.prop
If you do not specify a filename, a server instance or the weblogic.Admin SHUTDOWN and FORCESHUTDOWN commands use the boot.properties file in the server's root directory.
If there is no boot identity file:
When starting a server, the server instance prompts you to enter a username and password.

When using the weblogic.Admin SHUTDOWN and FORCESHUTDOWN commands, use the -username and -password arguments to provide user credentials.

-Dweblogic.system.
RemoveBootIdentity=true

Removes the boot identity file after a server starts.

-Dweblogic.security.anonymous
UserName=name

Assigns a user ID to anonymous users. By default, all anonymous users are identified with the string <anonymous>.
To emulate the security behavior of WebLogic Server 6.x, specify guest for the name value and create a user named guest in your security realm.
For more information, refer to "Users and Groups in the Securing WebLogic Resources guide.

-Djava.security.manager
-Djava.security.policy[=]=
filename

Standard J2EE options that enable the Java security manager and specify a filename (using a relative or fully-qualified pathname) that contains Java 2 security policies.
To use the WebLogic Server sample policy file, specify WL_HOME\server\lib\weblogic.policy.
Using -Djava.security.policy==filename causes the policy file to override any default security policy. A single equal sign (=) causes the policy file to be appended to an existing security policy.
For more information, refer to "Using the Java Security Manager to Protect WebLogic Resources in the Programming WebLogic Security guide.

-Dweblogic.security.
fullyDelegateAuthorization=true

By default, roles and security policies cannot be set for an EJB or Web application through the Administration Console unless security constraints were defined in the deployment descriptor for the EJB or Web application.
Use this option when starting WebLogic Server to override this problem.
This startup option does not work with EJBs or EJB methods that use <unchecked> or <restricted> tags or Web applications that do not have a role-name specified in the <auth-constraint> tag.

-Dweblogic.management.
anonymousAdminLookupEnabled=true

Enables you to retrieve an MBeanHome interface without specifying user credentials. The MBeanHome interface is part of the WebLogic Server JMX API.
If you retrieve MBeanHome without specifying user credentials, the interface gives you read-only access to the value of any MBean attribute that is not explicitly marked as protected by the Weblogic Server MBean authorization process.
This startup option overrides the Anonymous Admin Lookup Enabled setting on the Security —> General tab in the Administration Console.
By default, the MBeanHome API allows access to MBeans only for WebLogic users who are in one of the default security roles. For more information, refer to "Security Roles in the Securing WebLogic Resources guide.

-Dweblogic.security.
identityAssertionTTL=seconds

Configures the number of seconds that the Identity Assertion cache stores a Subject.
When using an Identity Assertion provider (either for an X.509 certificate or some other type of token), Subjects are cached within the server. This greatly enhances performance for servlets and EJB methods with <run-as> tags as well as for other places where identity assertion is used but not cached (for example, signing and encrypting XML documents). There might be some cases where this caching violates the desired semantics.
By default, Subjects remain in the cache for 300 seconds, which is also the maximum allowed value. Setting the value to 0 disables the cache.
Setting a high value generally improves the performance of identity assertion, but makes the Identity Assertion provider less responsive to changes in the configured Authentication provider. For example, a change in the user's group will not be reflected until the Subject is flushed from the cache and recreated.

The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Message Output and Logging
The following table describes options for configuring a server instance's message output.
Table 4-6 Options for Configuring Message Output

Option

Description

-Dweblogic.Stdout="filename"

Redirects the server and JVM's standard output stream to a file. You can specify a pathname that is fully qualified or relative to the WebLogic Server root directory.
For more information, refer to "Redirecting System.out and System.err to a File in the Administration Console Online Help.

-Dweblogic.Stderr="filename"

Redirects the server and JVM's standard error stream to a file. You can specify a pathname that is fully qualified or relative to the WebLogic Server root directory.
For more information, refer to "Redirecting System.out and System.err to a File in the Administration Console Online Help.

The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Setting Logging Attributes
Each Weblogic Server instance uses an instance of weblogic.management.configuration.LogMBean to represent the configuration of its logging services. To set values for LogMBean attributes from the startup command, do the following:

To determine which log attributes can be configured from startup options, view the WebLogic Server Javadoc for the LogMBean. The Javadoc also indicates valid values for each attribute.
Each attribute that the LogMBean exposes as a setter method can be set by a startup option.
Add the following option to the start command:
-Dweblogic.log.attribute-name=value
where attribute-name is the name of the MBean's setter method without the set prefix.
The LogMBean exposes its FileName attribute with the following setter method: setFileName() To specify the name of the MedRecServer instance's local log file, use the following command when you start MedRecServer: java -Dweblogic.Name=MedRecServer
-Dweblogic.log.FileName="C:\logfiles\myServer.log"
weblogic.Server The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Other Server Configuration Options
The following table describes options for configuring additional attributes of a server instance.
Table 4-7 Options for Configuring Server Attributes

Option

Description

-Dweblogic.Name=
servername

Specifies the name of the server instance that you want to start. The specified value must refer to the name of a server that has been defined in the domain's config.xml file.

-Dweblogic.ProductionModeEnabled=
{true | false}

Determines whether a server starts in production mode.
A true value prevents a WebLogic Server from automatically deploying and updating applications that are in the domain_name/applications directory.
If you do not specify this option, the assumed value is false.
For information on the differences between development mode and production mode, refer to "Differences Between Configuration Startup Modes."

-Dweblogic.management.
startupMode=STANDBY

Starts a server and places it in the STANDBY state. To use this startup argument, the domain must be configured to use the domain-wide administration port.
For information about administration ports, refer to "Enabling the Domain-Wide Administration Port in the Configuring and Managing WebLogic Server guide.
This startup option overrides any startup mode setting in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.
If you do not specify this value (either on the command line or in config.xml), the default is to start in the RUNNING state.

-Dweblogic.apache.xerces.
maxentityrefs=numerical-value

Limits the number of entities in an XML document that the WebLogic XML parser resolves.
If you do not specify this option, the XML parser that WebLogic Server installs resolves 10,000 entity references in an XML document, regardless of how many an XML document contains.

-Dweblogic.jsp.windows.caseSensitive=true

Causes the JSP compiler on Windows systems to preserve case when it creates output files names.
See "Running JSPC on Windows Systems" in Programming WebLogic JSP.

The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Clusters
The following table describes options for configuring additional attributes of a cluster.
Table 4-8 Options for Configuring Cluster Attributes

Option

Description

-Dweblogic.cluster.
multicastAddress

Determines the Multicast Address that clustered servers use to send and receive cluster-related communications. By default, a clustered server refers to the Multicast Address that is defined in the config.xml file. Use this option to override the value in config.xml.
Note: The Administration Console does not display values that you set on the command line. For information on verifying the attribute values that you set, refer to Verifying Attribute Values That Are Set on the Command Line.
Regardless of how you set the Multicast Address, all servers in a cluster must communicate at the same Multicast Address.

Using the weblogic.Server Command Line to Start a Server Instance
A simple way to start a server instance is as follows:

In a command shell, set up the required environment variables by running the following script:
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 the WebLogic Server software.
In the command shell, change to the directory that contains your domain's config.xml file. For example, change to the WL_HOME\samples\domains\medrec directory.
To start an Administration Server, enter the following command:
java -Dweblogic.Name=servername weblogic.Server
where servername is the name of a server configuration that already exists in the config.xml file.
For example, enter the following command to start the MedRec server:
java -Dweblogic.Name=MedRecServer weblogic.Server
If the domain's Administration Server is already running, and if you have already defined a Managed Server in the config.xml file, you can start a Managed Server as follows:
java -Dweblogic.Name=managed-server-name
-Dweblogic.management.server=url-for-Administration-Server
weblogic.Server
For example, if you create a Managed Server named MedRecManagedServer in the MedRec domain, you can enter the following command:
java -Dweblogic.Name=MedRecManagedServer
-Dweblogic.management.server=localhost:7001
weblogic.Server

Using the weblogic.Server Command Line to Create a Domain
You can use weblogic.Server to create a domain that contains a single server instance. You cannot use weblogic.Server to add Managed Server instances to a domain, nor can you use weblogic.Server to modify an existing domain. As described in Default Behavior, if weblogic.Server is unable to find a config.xml file, it offers to create the file. Any command option that you specify and that corresponds to an attribute that is persisted in the config.xml file will be persisted. For example, the -Dweblogic.Name and -Dweblogic.Domain options specify the name of a server configuration and the name of a domain. If weblogic.Server is unable to find a config.xml file, both of these values are persisted in config.xml. However, the -Dweblogic.system.BootIdentityFile option, which specifies a file that contains user credentials for starting a server instance, is not an attribute that the config.xml file persists. To create and instantiate a simple example domain and server, do the following:

In a command shell, set up the required environment variables by running the following script:
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 the WebLogic Server software.
In the command shell, create an empty directory.
In the empty directory, enter the following command:
java -Dweblogic.Domain=SimpleDomain -Dweblogic.Name=SimpleServer
-Dweblogic.management.username=weblogic
-Dweblogic.management.password=weblogic   -Dweblogic.ListenPort=7701
weblogic.Server 
After you enter this command, WebLogic Server asks if you want to create a new config.xml file. If you enter y, it asks you to confirm the password. Then it instantiates a domain named SimpleDomain. The domain's Administration Server is configured as follows:
The name of the Administration Server is SimpleServer. The domain's security realm defines one administrative user, weblogic, with a password of weblogic. For the listen address of the Administration Server, you can use localhost, the IP address of the host computer, or the DNS name of the host computer. For more information about setting the listen address, refer to "Configuring the Listen Address in the Administration Console Online Help. The Administration Server listens on port 7701.
Entering the weblogic.Server command as described in this section creates the following files:
config.xml DefaultAuthenticatorInit.ldift and SerializedSystemIni.dat, which store basic security-related data. boot.properties file, which contains the username and password in an encrypted format. This file enables you to bypass the prompt for username and password when you start the server. For more information, refer to "Boot Identity Files in the Administration Console Online Help. startmydomain.cmd and startmydomain.sh, that you can use to start subsequent instantiations of the server.

Verifying Attribute Values That Are Set on the Command Line
The Administration Console does not display values that you set on the command line because the startup options set attribute values for the server's Local Configuration MBean. To see the values that are in a server's Local Configuration MBean, use the weblogic.Admin utility as follows: java weblogic.Admin -url url-for-server-instance -username username -password password GET -type MBean-nameConfig -property attribute-name For example, to determine the multicast address that a cluster member is using, enter the following command, where MRMachine1:7041 is the listen address and port of the cluster member:
java weblogic.Admin -url MRMachine1:7041 -username weblogic -password weblogic GET -pretty -type ClusterConfig -property MulticastAddress To determine the severity level of messages that the example MedRecServer prints to standard out, enter the following command: java weblogic.Admin -url localhost:7001 -username weblogic -password weblogic GET -pretty -type ServerConfig -property StdoutSeverityLevel For more information about Local Configuration MBeans, refer to "Overview of WebLogic JMX Services in the Programming WebLogic Server Management Services with JMX guide. For more information on using the weblogic.Admin utility, refer to weblogic.Admin Command-Line Reference.

Option	Description
-Dweblogic.security.SSL. ignoreHostnameVerification= true	Disables host-name verification, which enables you to use the demonstration digital certificates that are shipped with WebLogic Server.By default, when a WebLogic Server instance is in the role of SSL client (it is trying to connect to some other server or application via SSL), it verifies that the host name that the SSL server returns in its digital certificate matches the host name of the URL used to connect to the SSL server. If the host names do not match, the connection is dropped.If you disable host name verification, either by using this option or by modifying the server's configuration in the config.xml file, the server instance does not verify host names when it is in the role of SSL client. Note: BEA does not recommend using the demonstration digital certificates or turning off host name verification in a production environment.This startup option overrides any Host Name Verification setting in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.For more information, refer to "Using Hostname Verification in the Managing WebLogic Security guide.
-Dweblogic.security.SSL. HostnameVerifier= hostnameverifierimplmentation	Specifies the name of a custom Host Name Verifier class. The class must implement the weblogic.security.SSL.HostnameVerifier interface.
-Dweblogic.security.SSL. sessionCache.size= sessionCacheSize -Dweblogic.security.SSL. sessionCache.ttl= sessionCacheTimeToLive	Modifies the default server-session caching size and time-to-live for SSL session caching.The sessionCacheSize value specifies the number of items in session cache and the sessionCacheTimeToLive value specifies (in seconds) the session cache time-to-live. For sessionCache.size: The minimum value is 1 The maximum value is 65537 The default value is 211 For sessionCache.ttl: The minimum value is 1 The maximum value is Integer.MAX_VALUE The default value is 600
-Dweblogic.management. pkpassword=pkpassword	Specifies the password for retrieving SSL private keys from an encrypted flat file. Use this option if you store private keys in an encrypted flat file.
-Dweblogic.security.SSL. trustedCAKeyStore=path	Deprecated and ignored by default.If you configure a server instance to use the SSL features that were available before WebLogic Server 8.1, you can use this argument to specify the certificate authorities that the server or client trusts. The path value must be a relative or qualified name to the Sun JKS keystore file (contains a repository of keys and certificates).If a server instance is using the SSL features that were available before 8.1, and if you do not specify this argument, the WebLogic Server or client trusts all of the certificates that are specified in JAVA_HOME\jre\lib\security\cacerts. We recommend that you do not use the demonstration certificate authorities in any type of production deployment.For more information, refer to "Configuring SSL in the Managing WebLogic Security guide.

Option	Description
-Dweblogic.management. username=username	Specifies the username under which the server instance will run. The username must belong to a role that has permission to start a server. For information on roles and permissions, refer to "Security Roles in the Securing WebLogic Resources guide. This option prevents a server instance from using any boot identity file and overrides other startup options that cause a server to use boot identity files. For more information, refer to "Boot Identity Files in the Administration Console Online Help.
-Dweblogic.management. password=password	Specifies the user password. This option prevents a server instance from using any boot identity file and overrides other startup options that cause a server to use boot identity files. For more information, refer to "Boot Identity Files in the Administration Console Online Help.
-Dweblogic.system. StoreBootIdentity=true	Creates a boot.properties file in the server's root directory. The file contains the username and an encrypted version of the password that was used to start the server. Do not specify this argument in a server's ServerStartMBean (Remote Startup tab in the Administration Console). For more information, refer to "Specifying User Credentials When Starting a Server with the Node Manager in the Administration Console Online Help. BEA recommends that you do not add this argument to a startup script. Instead, use it only when you want to create a boot.properties file. For more information, refer to "Boot Identity Files in the Administration Console Online Help.
-Dweblogic.system. BootIdentityFile=filename	Specifies a boot identity file that contains a username and password. The filename value must be the fully qualified pathname of a valid boot identity file. For example: -Dweblogic.system.BootIdentityFile=C:\BEA\ wlserver8.1\user_config\mydomain\myidentity.prop If you do not specify a filename, a server instance or the weblogic.Admin SHUTDOWN and FORCESHUTDOWN commands use the boot.properties file in the server's root directory. If there is no boot identity file: When starting a server, the server instance prompts you to enter a username and password. When using the weblogic.Admin SHUTDOWN and FORCESHUTDOWN commands, use the -username and -password arguments to provide user credentials.
-Dweblogic.system. RemoveBootIdentity=true	Removes the boot identity file after a server starts.
-Dweblogic.security.anonymous UserName=name	Assigns a user ID to anonymous users. By default, all anonymous users are identified with the string <anonymous>. To emulate the security behavior of WebLogic Server 6.x, specify guest for the name value and create a user named guest in your security realm. For more information, refer to "Users and Groups in the Securing WebLogic Resources guide.
-Djava.security.manager -Djava.security.policy[=]= filename	Standard J2EE options that enable the Java security manager and specify a filename (using a relative or fully-qualified pathname) that contains Java 2 security policies. To use the WebLogic Server sample policy file, specify WL_HOME\server\lib\weblogic.policy. Using -Djava.security.policy==filename causes the policy file to override any default security policy. A single equal sign (=) causes the policy file to be appended to an existing security policy. For more information, refer to "Using the Java Security Manager to Protect WebLogic Resources in the Programming WebLogic Security guide.
-Dweblogic.security. fullyDelegateAuthorization=true	By default, roles and security policies cannot be set for an EJB or Web application through the Administration Console unless security constraints were defined in the deployment descriptor for the EJB or Web application. Use this option when starting WebLogic Server to override this problem. This startup option does not work with EJBs or EJB methods that use <unchecked> or <restricted> tags or Web applications that do not have a role-name specified in the <auth-constraint> tag.
-Dweblogic.management. anonymousAdminLookupEnabled=true	Enables you to retrieve an MBeanHome interface without specifying user credentials. The MBeanHome interface is part of the WebLogic Server JMX API. If you retrieve MBeanHome without specifying user credentials, the interface gives you read-only access to the value of any MBean attribute that is not explicitly marked as protected by the Weblogic Server MBean authorization process. This startup option overrides the Anonymous Admin Lookup Enabled setting on the Security —> General tab in the Administration Console. By default, the MBeanHome API allows access to MBeans only for WebLogic users who are in one of the default security roles. For more information, refer to "Security Roles in the Securing WebLogic Resources guide.
-Dweblogic.security. identityAssertionTTL=seconds	Configures the number of seconds that the Identity Assertion cache stores a Subject. When using an Identity Assertion provider (either for an X.509 certificate or some other type of token), Subjects are cached within the server. This greatly enhances performance for servlets and EJB methods with <run-as> tags as well as for other places where identity assertion is used but not cached (for example, signing and encrypting XML documents). There might be some cases where this caching violates the desired semantics. By default, Subjects remain in the cache for 300 seconds, which is also the maximum allowed value. Setting the value to 0 disables the cache. Setting a high value generally improves the performance of identity assertion, but makes the Identity Assertion provider less responsive to changes in the configured Authentication provider. For example, a change in the user's group will not be reflected until the Subject is flushed from the cache and recreated.

Option	Description
-Dweblogic.Name= servername	Specifies the name of the server instance that you want to start. The specified value must refer to the name of a server that has been defined in the domain's config.xml file.
-Dweblogic.ProductionModeEnabled= {true \| false}	Determines whether a server starts in production mode. A true value prevents a WebLogic Server from automatically deploying and updating applications that are in the domain_name/applications directory. If you do not specify this option, the assumed value is false. For information on the differences between development mode and production mode, refer to "Differences Between Configuration Startup Modes."
-Dweblogic.management. startupMode=STANDBY	Starts a server and places it in the STANDBY state. To use this startup argument, the domain must be configured to use the domain-wide administration port. For information about administration ports, refer to "Enabling the Domain-Wide Administration Port in the Configuring and Managing WebLogic Server guide. This startup option overrides any startup mode setting in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file. If you do not specify this value (either on the command line or in config.xml), the default is to start in the RUNNING state.
-Dweblogic.apache.xerces. maxentityrefs=numerical-value	Limits the number of entities in an XML document that the WebLogic XML parser resolves. If you do not specify this option, the XML parser that WebLogic Server installs resolves 10,000 entity references in an XML document, regardless of how many an XML document contains.
-Dweblogic.jsp.windows.caseSensitive=true	Causes the JSP compiler on Windows systems to preserve case when it creates output files names. See "Running JSPC on Windows Systems" in Programming WebLogic JSP.

Option	Description
-Xms and -Xmx	Specify the minimum and maximum values (in megabytes) for Java heap memory. For example, you might want to start the server with a default allocation of 200 megabytes of Java heap memory to the WebLogic Server. To do so, you can start the server with the java -Xms200m and -Xmx200m options. For best performance it is recommended that the minimum and maximum values be the same so that the JVM does not resize the heap.The values assigned to these parameters can dramatically affect the performance of your WebLogic Server and are provided here only as general defaults. In a production environment you should carefully consider the correct memory heap size to use for your applications and environment.
-classpath	The minimum content for this option is described under Setting the Classpath. Instead of using this argument, you can use an environment variable named CLASSPATH to specify the classpath.
-client -server	Used by some JVMs to start a HotSpot virtual machine, which enhances performance. For a list of JVMs that can be used with WebLogic Server, refer to the Supported Configurations page at http://e-docs.bea.com/wls/certifications/certifications/index.html.

Option	Description
-Dbea.home=bea_home	Specifies the location of the BEA home directory, which contains licensing and other essential information.By default, weblogic.Server determines the location of the BEA home directory based on values in the classpath.
-Dweblogic.RootDirectory=path	Specifies the server's root directory. By default, the root directory is the directory from which you issue the start command. For more information, refer to "A Server's Root Directory in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ConfigFile= file_name	Specifies a configuration file for your domain. The file_name value must refer to a valid XML file that conforms to the schema as defined in the "BEA WebLogic Server Configuration Reference."The XML file must exist in the Administration Server's root directory, which is either the current directory or the directory that you specify with -Dweblogic.RootDirectory.The file_name value cannot contain a pathname component. For example, the following value is invalid:-Dweblogic.ConfigFile=c:\mydir\myfile.xml Instead, use the following arguments:-Dweblogic.RootDirectory=c:\mydir -Dweblogic.ConfigFile=myfile.xml If you do not specify this value, the default is config.xml in the server's root directory.
-Dweblogic.management.GenerateDefaultConfig=true	Prevents the weblogic.Server class from prompting for confirmation when creating a config.xml file.Valid only if you invoke weblogic.Server in an empty directory. See Default Behavior.
-Dweblogic.Domain=domain	Specifies the name of the domain. If you are using weblogic.Server to create a domain, you can use this option to give the domain a specific name.In addition, this option supports a directory structure that WebLogic Server required in releases prior to 7.0 and continues to support in current releases. Prior to 7.0, all configuration files were required to be located at the following pathname:.../config/domain/config.xml where domain is the name of the domain.If your domain's configuration file conforms to that pathname, and if you invoke the weblogic.Server command from a directory other than config/domain, you can include the -Dweblogic.Domain=domain argument to cause WebLogic Server to search for a config.xml file in a pathname that matches con fig/domain/config.xml.

Option	Description
-Dweblogic.management.server= [protocol://]Admin-host:port	Starts a server instance as a Managed Server and specifies the Administration Server that will configure and manage the server instance. The domain's configuration file does not specify whether a server configuration is an Administration Server or a Managed Server. You determine whether a server instance is in the role of Administration Server or Managed Server with the options that you use to start the instance. If you omit the -Dweblogic.management.server option in the start command, the server starts as an Administration Server (although within a given domain, there can be only one active Administration Server instance). Once an Administration Server is running, start all other server configurations as Managed Servers by including the -Dweblogic.management.server option in the start command.For protocol, specify HTTP, HTTPS, T3, or T3S. The T3S and HTTPS protocols require you to enable SSL on the Managed Server and the Administration Server and specify the Administration Server's SSL listen port. Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.For Admin-host, specify localhost or the DNS name or IP address of the machine where the Administration Server is running.For port, specify the Administration Server's listen port. If you set up the domain-side administration port, port must specify the domain-wide administration port.For more information on configuring a connection to the Administration Server, refer to "Configuring a Connection to the Administration Server" in the Administration Console Online Help.
-Dweblogic.ListenAddress=host	Specifies the address at which this server instance listens for requests. The host value must be either the DNS name or the IP address of the computer that is hosting the server instance.This startup option overrides any listen address value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.For more information, refer to "Configuring the Listen Address in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ListenPort= portnumber	Enables and specifies the plain-text (non-SSL) listen port for the server instance. This startup option overrides any listen port value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.The default listen port is 7001.For more information, refer to "Configuring the Listen Ports in the Configuring and Managing WebLogic Server guide.
-Dweblogic.ssl.ListenPort= portnumber	Enables and specifies the port at which this WebLogic Server instance listens for SSL connection requests.This startup option overrides any SSL listen port value specified in the config.xml file. The override applies to the current server instantiation; it does not modify the value in the config.xml file. Use the Administration Console or the weblogic.Admin command to modify the config.xml file.The default SSL listen port is 7002.For more information, refer to "Configuring the Listen Ports in the Configuring and Managing WebLogic Server guide.
-Dweblogic.management. discover={true \| false}	Determines whether an Administration Server recovers control of a domain after the server fails and is restarted.A true value causes an Administration Server to communicate with all knows Managed Servers and inform them that the Administration Server is running.A false value prevents an Administration Server from communicating with any Managed Servers that are currently active in the domain. Caution: Specify false for this option only in the development environment of a single server. Specifying false can cause server instances in the domain to have an inconsistent set of deployed modules.For information on re-establishing administrative control over Managed Servers after an Administration Server has already started, refer to DISCOVERMANAGEDSERVER.