weblogic.Admin Command-Line Reference

WebLogic Server Command Reference

FORCESHUTDOWN

Terminates a server instance without waiting for active sessions to complete. For more information, refer to "Forced Shutdown" in the Configuring and Managing WebLogic Server guide.

If a server instance is in a deadlocked state, it can respond to weblogic.Admin commands only if you have enabled the domain-wide administration port. (A deadlocked server is one in which all threads are struck trying to acquire locks held by other threads.) If you have not already enabled the domain-wide administration port, your only option for shutting down the server instance is to kill the Java process that is running the server. You will lose all session data. For information on enabling the domain-wide administration port, refer to "Enabling the Domain-Wide Administration Port" in the Administration Console Online Help.

Syntax

java [ SSL Arguments ] 
   [-Dweblogic.system.BootIdentityFile=filename 
     [-Dweblogic.RootDirectory=path]
   ]
   weblogic.Admin 
   [ Connection Arguments ] 
   [ User Credentials Arguments ]
   FORCESHUTDOWN [targetServer]

Argument	Definition
`-Dweblogic.system.BootIdentityFile=filename` `[-Dweblogic.RootDirectory=path]`	Cause the command to retrieve encrypted user credentials from a boot identity file. See "Boot Identity Files" in the Administration Console Online Help. Use these arguments if you invoke this command from a script, you have not created a user configuration file, and you do not want to store user credentials in your script. If you do you not use the `-username` argument or a user configuration file to specify credentials (see User Credentials Arguments), the command retrieves user credentials from a boot properteis file as follows: If you invoke the command from a server's root directory, and if the server's root directory contains a valid `boot.properties` file, it retrieves credentials from this file by default. For information about a server's root directory, refer to "A Server's Root Directory." If you invoke the command from a server's root directory, but the server's boot identity file is not in the server's root directory or is not named `boot.properties`, the command can use a boot identity file if you include the following argument: `-Dweblogic.system.BootIdentityFile=`filename where filename is the fully qualified pathname of a valid boot identity file. If you do not invoke the command from a server's root directory, the command can use a boot identity file if you include both of the following arguments in the command: `-Dweblogic.system.BootIdentityFile=`filename `-Dweblogic.RootDirectory=`path where filename is the fully qualified pathname of a valid boot identity file and `path` is the relative or fully-qualified name of the server's root directory. If you have not created a boot identity file for a server, or if you do not want to use it, you must use the `-username` and `-password` arguments to provide user credentials. If you specify both `-Dweblogic.system.BootIdentityFile=`filename and `-username` and `-password`, the command uses the credentials specified in the `-username` and `-password` arguments.
`targetServer`	The name of the server to shut down. If you do not specify a value, the command shuts down the server that you specified in the `-url` argument.

Argument

Definition

-Dweblogic.system.BootIdentityFile=filename
[-Dweblogic.RootDirectory=path]

Cause the command to retrieve encrypted user credentials from a boot identity file. See "Boot Identity Files" in the Administration Console Online Help.

Use these arguments if you invoke this command from a script, you have not created a user configuration file, and you do not want to store user credentials in your script.

If you do you not use the -username argument or a user configuration file to specify credentials (see User Credentials Arguments), the command retrieves user credentials from a boot properteis file as follows:

If you invoke the command from a server's root directory, and if the server's root directory contains a valid boot.properties file, it retrieves credentials from this file by default. For information about a server's root directory, refer to "A Server's Root Directory."

If you invoke the command from a server's root directory, but the server's boot identity file is not in the server's root directory or is not named boot.properties, the command can use a boot identity file if you include the following argument:

-Dweblogic.system.BootIdentityFile=filename
where filename is the fully qualified pathname of a valid boot identity file.

If you do not invoke the command from a server's root directory, the command can use a boot identity file if you include both of the following arguments in the command:

-Dweblogic.system.BootIdentityFile=filename -Dweblogic.RootDirectory=path
where filename is the fully qualified pathname of a valid boot identity file and path is the relative or fully-qualified name of the server's root directory.

If you have not created a boot identity file for a server, or if you do not want to use it, you must use the -username and -password arguments to provide user credentials.

If you specify both -Dweblogic.system.BootIdentityFile=filename and -username and -password, the command uses the credentials specified in the -username and -password arguments.

targetServer

The name of the server to shut down.

If you do not specify a value, the command shuts down the server that you specified in the -url argument.

Example

The following command instructs the Administration Server to shut down a Managed Server:

java weblogic.Admin -url AdminHost:7001 -username weblogic 
   -password weblogic FORCESHUTDOWN MedRecManagedServer

After you issue the command, MedRecManagedServer prints messages to its log file and to its standard out. The messages indicate that the server state is changing and that the shutdown sequence is starting.

If the command succeeds, the final message that the target server prints is as follows:

<Oct 12, 2002 11:28:59 AM EDT> <Alert> <WebLogicServer> <000219> <The
shutdown sequence has been initiated.>

In addition, if the command succeeds, the weblogic.Admin utility returns the following:

Server "MedRecManagedServer" was force shutdown successfully ...

For more information about the environment in which this example runs, refer to Example Environment.

In the following example, the Administration Server is not available, so the command instructs the Managed Server to shut itself down:

java weblogic.Admin -url ManagedHost:8001 -username weblogic 
-password weblogic FORCESHUTDOWN

The following example provides user credentials by referring to a boot identity file. The example specifies the server's root directory and boot identity file name so that it can be invoked from any directory:

java -Dweblogic.system.BootIdentityFile=c:\mydomain\boot.properties
 -Dweblogic.RootDirectory=c:\mydomain
 weblogic.Admin -url AdminHost:7001 FORCESHUTDOWN