The following table describes optional arguments that are frequently used. The description of each argument indicates whether it can also be set through the Administration Console or some other WebLogic Server command. Any argument that sets an attribute for a Managed Bean (MBean) can also be set through the MBean’s API. The next section,“Other Optional Arguments” on page 2-25, describes setting MBean attributes.
Table 2-3 Frequently Used Optional Arguments
Argument Description
-Dweblogic.RootDirectory=path Specifies the server’s root directory. For more information, refer to
“A Server’s Root Directory” on page 2-27.
-Dweblogic.ConfigFile= file_name
Specifies a configuration file for your domain. Thefile_name
value must refer to a valid XML file that conforms to the
config.dtd. 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. Thefile_namevalue 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
For information aboutconfig.dtd, refer toBEA WebLogic Server Configuration Reference.
If you do not specify this value, the default isconfig.xml.
-Dweblogic.management. username=username
Specifies the username.
The username must belong to a role that has permission to start a server. For information on roles and permissions, refer to
“Protecting System Administration Operations” on page 3-1. Instead of using this argument, you can use a boot identity file. For more information, refer to“Bypassing the Prompt for Username and Password” on page 2-7.
-Dweblogic.management. password=password
Specifies the user password.
Instead of using this argument, you can use a boot identity file. For more information, refer to“Bypassing the Prompt for Username and Password” on page 2-7.
-Dweblogic.ListenAddress=host Specifies a listen address for this server. Thehostvalue must be either the DNS name or the IP address of the server.
This option sets the value of thelistenAddressattribute in the
ServerMBean, which is also accessible from the Administration Console under Server→Configuration→General→Listen Address. If you do not specify a Listen Address, a server uses either the machine’s DNS name or the IP address.
We recommend that you specify a known IP address or DNS name and that you use the Administration Console instead of this argument to do so.
For more information, refer toConfiguring Network Resources.
-Dweblogic.ListenPort= portnumber
Enables and specifies the plain-text (non-SSL) listen port for this server.
The argument sets the value of thelistenPortattribute in the
ServerMBean, which is also accessible from the Administration Console under Server→Configuration→General→Listen Port. If you do not specify a Listen Port, a server uses 7001 as the default. For more information, refer toConfiguring Network Resources.
-Dweblogic.ssl.ListenPort= portnumber
Enables and specifies the port at which this WebLogic Server listens for SSL connection requests.
The argument sets the value of thelistenPortattribute in the
SSLMBean, which is also accessible from the Administration Console under Server→Connections→SSL Ports→SSL Listen Port. If you do not specify a Listen Port, a server uses 7002 as the default. For more information, refer toConfiguring Network Resources.
Table 2-3 Frequently Used Optional Arguments
Starting an Administration Server
Administration Guide 2-21
-Dweblogic.system. StoreBootIdentity=true
Creates aboot.propertiesin the server’s root directory. The file contains the username and an encrypted version of the password that you used to start the server.
For more information, refer to“Bypassing the Prompt for Username and Password” on page 2-7.
-Dweblogic.system.
BootIdentityFile=filename
Specifies a boot identity file that contains a username and password. Thefilenamevalue must be the fully qualified pathname of a valid boot identity file. For example:
-Dweblogic.system.BootIdentityFile=C:\BEA\ wlserver7.0\user_config\mydomain\myidentity.pr op
If you do not specify a filename, a server uses the
boot.propertiesin the server’s root directory. If there is no boot identity file, the server prompts you to enter a username and password.
-Dweblogic.system. RemoveBootIdentity=true
Removes the boot identity file after a server starts.
-Dweblogic.management. pkpassword=pkpassword
Specifies the password for retrieving Secure Socket Layer (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
If you use SSL, 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 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.
Table 2-3 Frequently Used Optional Arguments
-Dweblogic.security.SSL. ignoreHostnameVerification= true
Disables host-name verification.
Include this argument if you want to use the demonstration digital certificates that are shipped with WebLogic Server.
Note: BEA does not recommend using the demonstration digital certificates or turning off host name verification in a production deployment.
If you do not specify this argument, the Host Name Verifier in WebLogic Server compares the SubjectDN of a digital certificate with the host name of the server that initiated the SSL connection. If the SubjectDN and the host name do not match, the SSL connection is dropped.
-Dweblogic.security.SSL. HostnameVerifier=
hostnameverifierimplmentation
Specifies the name of a custom Host Name Verifier class. The class must implement the
weblogic.security.SSL.HostnameVerifierinterface. -Dweblogic.security.SSL. sessionCache.size= sessionCacheSize -Dweblogic.security.SSL. sessionCache.ttl= sessionCacheTimeToLive
Modify the default server-session caching size and time-to-live for SSL session caching.
ThesessionCacheSizevalue specifies the number of items in session cache and thesessionCacheTimeToLivevalue specifies (in seconds) the session cache time-to-live. ForsessionCache.size:
! The minimum value is1
! The maximum value is65537
! The default value is211
ForsessionCache.ttl:
! The minimum value is1
! The maximum value isInteger.MAX_VALUE
! The default value is600
Table 2-3 Frequently Used Optional Arguments
Starting an Administration Server
Administration Guide 2-23
-Djava.security.manager -Djava.security.policy= filename
Enable the Java 2 security manager, which prevents untrusted code from performing actions that are restricted by the policy file. The-Djava.security.policyargument specifies a filename (using a relative or fully-qualified pathname) that contains Java 2 security policies.
The WebLogic Server sample policy file, which you can edit and use, isWL_HOME\server\lib\weblogic.policy. For more information, refer toModifying the weblogic.policy File for General Usein the Managing WebLogic Security guide.
-Dweblogic.security.anonymous UserName=guest
Enables support for theguestuser account. If you start a WebLogic Server instance with this argument, you must also add the
guestuser to the Authentication provider in the default security realm.
For more information, refer toDefining Usersin the Managing
WebLogic Security guide. -Dweblogic.management.
startupMode=STANDBY
Starts a server and places it in theSTANDBYstate. To use this startup argument, you must configure a server to use a separate
administration port.
For information about administration ports, refer toConfiguring a Domain-Wide Administration Portin the Creating and Configuring
WebLogic Server Domains Guide.
This value overrides anystartupModevalue specified in the Administration Console under Server→Configuration→General tab for the current session only.
If you do not specify this value (either on the command line or in
config.xml), the default is to start in theRUNNINGstate.
-Dweblogic.ProductionModeEnab led=
{true | false}
Determines whether a server starts in production mode.
Atruevalue prevents a WebLogic Server from
automatically deploying and updating applications that are in thedomain_name/applicationsdirectory.
If you do not specify this option, the assumed value isfalse. For more information, refer to“Development Mode vs. Production Mode” on page 2-26.
Table 2-3 Frequently Used Optional Arguments
-Dweblogic.management. discover={true | false}
Determines whether an Administration Server recovers control of a domain after the server fails and is restarted.
Atruevalue causes an Administration Server to refer to its
running-managed-servers.xmlfile, which contains information about the deployment state of deployable modules and a list of all Managed Servers that are currently running. When the Administration Server starts with this specified astrue, it communicates with the Managed Servers and informs them that it is running.
Afalsevalue prevents an Administration Server from referring to this file and thus prevents it fromcommunicating with any Managed Servers that are currently active in the domain.
Caution: Specifyfalsefor this option only in the development environment of a single server. Specifyingfalsecan cause server instances in the domain to have an inconsistent set of deployed modules.
If you do not specify this option, the assumed value istrue.
-Dweblogic.Stdout="filename" Redirects the 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.
Use this option to keep a record of the messages from the JVM that are not sent to a WebLogic Server log. For example, a JVM can print
verbosegcmessages to standard out but not to the WebLogic Server log. For more information, refer to“JVM Messages” on page 4-11.
-Dweblogic.Stderr="filename" Redirects the 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.
Use this option to keep a record of the error messages from the JVM that are not sent to a WebLogic Server log. For more information, refer to“JVM Messages” on page 4-11.
Table 2-3 Frequently Used Optional Arguments
Starting an Administration Server
Administration Guide 2-25