|
|
| |
WebLogic Server Command-Line Interface Reference
The following sections discuss the WebLogic Server command-line interface syntax, and describe each WebLogic Server administration, connection pool administration, and Mbean management command:
About the Command-Line Interface
As an alternative to the Administration Console, WebLogic Server offers a command-line interface to its administration tools, as well as to many configuration and run-time Mbean properties.
Use the command-line interface if:
The examples in this document are based on the following assumptions:
c:/weblogic
directory.
c:/java
directory.
Before you can run WebLogic Server commands, you must do the following:
CLASSPATH
correctly. See Setting the Classpath Option.
An administrator must have the appropriate access control permissions to run commands used to manage run-time MBeans.
See the following sections:
Mbean Management Command Reference
Using WebLogic Server Commands
This section presents the syntax and required arguments for using WebLogic Server commands. WebLogic Server commands are not case-sensitive.
Syntax
java weblogic.Admin [-url URL]
[ { -username username [-password password] } | { [-userconfigfileconfig-file
] [-userkeyfileadmin-key
] } ]COMMAND
arguments
Connection and User Credentials Arguments
Note: When you invoke most weblogic.Admin
commands, you specify the arguments in Table 21-1 to connect to a WebLogic Server instance and to specify the user credentials of a WebLogic Server user who has permission to invoke the command.
Argument |
Definition |
---|---|
|
Specifies one of the following:
The format is |
|
Username that has permission to invoke the command you specify. If you do not specify this argument, |
|
The password that is associated with the username. If you specify If WL_HOME |
|
Specifies the name and location of a user-configuration file, which contains an encrypted username and password. The encrypted username must have permission to invoke the command you specify. If you do not specify |
|
Specifies the name and location of the key file that is associated with the user-configuration file you specify. When you create a user-configuration file, the If you do not specify |
Note: The exit code for all commands is 1 if the Administration client cannot connect to the server.
Summary of User Credentials Arguments
Table 21-1 describes the alternatives that the weblogic.Admin
utility provides for passing usernames and passwords to a server instance.
In a development environment in which security is not a top priority, you can use the -username
and -password
arguments when invoking the weblogic.Admin
utility directly on the command line or in scripts. With these arguments, the username and password are not encrypted. If you store the values in a script, the user credentials can be used by anyone who has read access to the script.
In an environment in which security is a top priority, create user-configuration files and key files. A user-configuration file contains encrypted user credentials that can be decrypted only by a single key file. You can include the -userconfigfile
config-file
and -userkeyfile
admin-key
arguments in scripts without exposing the plain text user credentials to those with read privileges for the script. For information about creating a user-configuration and key file, see STOREUSERCONFIG.
The following list summarizes the order of precedence for the weblogic.Admin
user-credentials arguments:
-username
username
-password
password
, the utility passes the unencrypted values to the server instance you specify in the -url
argument.
These arguments take precedence over the { -userconfigfile
config-file
-userkeyfile
admin-key
}
arguments. If you specify both { -username
username
-password
password
}
and { -userconfigfile
config-file
-userkeyfile
admin-key
}
, the weblogic.Admin
utility uses the { -username
username
-password
password
}
arguments and ignores the user-configuration and key file arguments.
-username
username
, the utility prompts for a password. Then it passes the unencrypted values to the server instance you specify in the -url
argument.
This argument also takes precedence over the { -userconfigfile
config-file
-userkeyfile
admin-key
}
arguments.
{ -userconfigfile
config-file
-userkeyfile
admin-key
}
and do not specify { -username
username
[-password
password
]}
, the utility passes the values that are encrypted in config-file
to the server instance you specify in the -url
argument.
{ -username
username
[-password
password
] }
nor { -userconfigfile
config-file
-userkeyfile
admin-key
}
, the utility searches for a user-configuration file and key file at the default path names. The default path names vary depending on the JVM and the operating system. See Configuring the Default Path Name.
Examples of Providing User Credentials
The following command specifies the username weblogic and password weblogic directly on the command line:java weblogic.Admin -username weblogic -password weblogic
COMMAND
The following command uses a user-configuration file and key file that are located at the default pathname:java weblogic.Admin
COMMAND
See Configuring the Default Path Name.
The following command uses a user-configuration file named c:\wlUser1-WebLogicConfig.properties
and a key file named e:\secure\myKey
:java -userconfigfile c:\wlUser1-WebLogicConfig.properties
-userkeyfile e:\secure\myKey COMMAND
WebLogic Server Administration Command Reference
The following sections provide information about the WebLogic server administration commands.
Table B-1 presents an overview of WebLogic Server administration commands. The following sections describe command syntax and arguments, and provide an example for each command.
See also WebLogic Server Connection Pools Administration Command Reference.
Task |
Command |
Description |
---|---|---|
Cancel shut down a WebLogic Server |
Cancels the SHUTDOWN command for the WebLogic Server that is specified in the URL. |
|
Connect to WebLogic Server |
Makes the specified number of connections to the WebLogic Server and returns two numbers representing the total time for each round trip and the average amount of time (in milliseconds) that each connection is maintained. |
|
Get Help for one or more commands |
Provides syntax and usage information for all WebLogic Server commands (by default) or for a single command if a command value is specified on the HELP command line. |
|
View WebLogic Server licenses |
Lists the licenses for all the WebLogic Server instances installed on a specific server. |
|
List JNDI naming tree node bindings |
Lists the bindings of a node in the JNDI naming tree. |
|
Lock WebLogic Server |
Locks a WebLogic Server against non-privileged logins. Any subsequent login attempt initiates a security exception which may contain an optional string message. |
|
Verify WebLogic Server listening ports |
Sends a message to verify that a WebLogic Server is listening on a port, and is ready to accept WebLogic client requests. |
|
Displays the server log file generated on a specific server. |
||
Shut down a WebLogic Server |
Shuts down the WebLogic Server that is specified in the URL. |
|
Encrypt user credentials in a file |
Creates an encrypted user-configuration file and its associated key file. You can pass the encrypted values to a server instance instead of entering a username and password on the command line. |
|
View threads |
Provides a real-time snapshot of the WebLogic Server threads that are currently running. |
|
Unlock a WebLogic Server |
Unlocks the specified WebLogic Server after a LOCK operation. |
|
View WebLogic Server version |
Displays the version of the WebLogic Server software that is running on the machine specified by the value of |
Note: The exit code for all commands is 1 if the Administration client cannot connect to the server.
CANCEL_SHUTDOWN
The CANCEL_SHUTDOWN command cancels the SHUTDOWN command for a specified WebLogic Server.
When you use the SHUT_DOWN command, you can specify a delay (in seconds). An administrator may cancel the shutdown command during the delay period. Be aware that the SHUTDOWN command disables logins, and they remain disabled even after cancelling the shutdown. Use the UNLOCK command to re-enable logins.
java weblogic.Admin [Connection and User Credentials Arguments]
CANCEL_SHUTDOWN
In the following example, a system user named system
with a password of gumby1234
requests to cancel the shutdown of the WebLogic Server listening on port 7001 on machine localhost
:
java weblogic.Admin -url t3://localhost:7001 -username system -password gumby1234 CANCEL_SHUTDOWN
Makes the specified number of connections to the WebLogic Server and returns two numbers representing the total time for each round trip and the average amount of time (in milliseconds) that each connection is maintained.
java weblogic.Admin [Connection and User Credentials Arguments]
CONNECT count
Argument |
Definition |
---|---|
|
Number of connections to be made. |
In the following example, a user with the name adminuser
and the password gumby1234
runs the CONNECT
command to establish 25 connections to a server named localhost
and return information about those connections:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 CONNECT 25
HELP
Provides syntax and usage information for all WebLogic Server commands (by default) or for a single command if a command value is specified on the HELP command line.
Syntax
java weblogic.Admin HELP [COMMAND
]
Example
In the following example, information about using the PING
command is requested:
java weblogic.Admin HELP PING
The HELP
command returns the following to stdout
:
Usage: weblogic.Admin [-urlurl
] [-usernameusername
] [-passwordpassword
] <COMMAND> <ARGUMENTS>
PING <count
> <bytes
>
LICENSES
Lists the licenses for all WebLogic Server instances installed on the specified server.
java weblogic.Admin [Connection and User Credentials Arguments] LICENSES
In the following example, an administrator using the default username (guest
) and default password (guest
) requests the license information for a WebLogic Server running on port 7001 of machine localhost
:
java weblogic.Admin -url localhost:7001 -username guest -password guest LICENSES
LIST
Lists the bindings of a node in the JNDI naming tree.
java weblogic.Admin [Connection and User Credentials Arguments]LIST
context
Argument |
Definition |
---|---|
|
Required. The JNDI context for lookup, for example, |
In this example, user adminuser
, who has a password of gumby1234
, requests a list of the node bindings in weblogic.ejb
:
java weblogic.Admin -usernameadminuser
-passwordgumby1234
LIST
weblogic.ejb
LOCK
Locks a WebLogic Server against non-privileged logins. Any subsequent login attempt initiates a security exception which may contain an optional string message.
Note: This command is privileged. It requires the password for the WebLogic Server administrative user.
java weblogic.Admin [Connection and User Credentials Arguments]LOCK
"string_message
"
In the following example, a WebLogic Server is locked.
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234LOCK
"Sorry, WebLogic Server is temporarily out of service."
Any application that subsequently tries to log into the locked server with a non-privileged username and password receives the specified message: Sorry, WebLogic Server is temporarily out of service
.
PING
Sends a message to verify that a WebLogic Server is listening on a port, and is ready to accept WebLogic client requests.
java weblogic.Admin [Connection and User Credentials Arguments] PING [round_trips] [message_length]
Argument |
Definition |
---|---|
|
Optional. Number of pings. |
|
Optional. Size of the packet to be sent in each ping. Requests for pings with packets larger than 10 MB throw exceptions. |
In the following example, the command checks a WebLogic Server running on port 7001 of machine localhost
ten (10) times.
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 PING 10
Displays the log file generated on a specific server.
starttime
and endtime
arguments, a running display of the entire server log is started.
java.weblogic.Admin
[Connection and User Credentials Arguments]
SERVERLOG
[[
starttime
]|[
endtime
]]
In the following example, a request is made for a running display of the log for the server listening on port 7001 on machine localhost
.
java weblogic.Admin -urllocalhost:7001
SERVERLOG "2001/12/01 14:00" "2001/12/01 16:00"
The request specifies that the running display should begin at 2:00 p.m. on December 1, 2001, and end at 4:00 p.m. on December 1, 2001.
SHUTDOWN
Shuts down the WebLogic Server that is specified in the URL.
java weblogic.Admin [Connection and User Credentials Arguments]
SHUTDOWN[
seconds
] ["
lockMessage
"]
In the following example, a user with the adminuser
username and an administrative password of gumby1234
shuts down a WebLogic Server that is listening on port 7001 of machine localhost
:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 SHUTDOWN300 "Server localhost is shutting down."
After the command is issued, an interval of five minutes (300 seconds) elapses. Then the command shuts down the specified server and sends the following message to stdout
:
Server localhost is shutting down.
STOREUSERCONFIG
Creates a user-configuration file and an associated key file. The user-configuration file contains an encrypted username and password. The key file contains a secret key that is used to encrypt and decrypt the username and password.
When you use other weblogic.Admin
or weblogic.Deployer
commands, you can specify the user-configuration file and key file instead of entering an unencrypted username and password on the command line or including unencrypted credentials in scripts. See Summary of User Credentials Arguments.
Only the key file that originally encrypted the username and password can decyrpt the values. If you lose the key file, you must create a new user-configuration and key file pair.
Caution: You must ensure that only authorized users can access the key file. Any user who accesses a valid user-configuration and key file pair gains the privileges of the encrypted username. To secure access to the key file, you can store the key file in a directory that provides read and write access only to authorized users, such as WebLogic Server administrators. Alternatively, you can write the key file to a removable medium, such as a floppy or CD, and lock the medium in a drawer when it is not being used.
Unlike other weblogic.Admin
commands, the STOREUSERCONFIG
command does not connect to a WebLogic Server instance. The data encryption and file creation are accomplished by the JVM in which the STOREUSERCONFIG
command runs. Because it does not connect to a WebLogic Server instance, the command cannot verify that the username and password are valid WebLogic Server credentials.
java weblogic.Admin-username
username
[-password
password
] [ -userconfigfile
config-file
] [ -userkeyfile
keyfile
] STOREUSERCONFIG
Argument |
Definition |
---|---|
|
Specifies a file pathname at which the If a file already exists at the specified pathname, the command overwrites the file with a new file that contains the newly encrypted username and password. If you do not specify this option,
|
|
Specifies a file pathname at which the If a file already exists at the specified pathname, If you do not specify this option,
|
|
Specifies the username and password to encrypt. The If you omit the |
Configuring the Default Path Name
If you do not specify the location in which to create and use a user-configuration file and key file, the weblogic.Admin
and weblogic.Deployer
utilities supply the following default values:
user-home-directory
\
username
-WebLogicConfig.properties
user-home-directory
\
username
-WebLogicKey.properties
Where user-home-directory
is the home directory of the operating-system user account as determined by the JVM, and username
is your operating-system username.
The value of the home directory varies depending on the SDK and type of operating system. For example, on UNIX, the home directory is usually "~username
." On Windows, the home directory is usually "C:\Documents and Settings\
username
".
You can use the following Java options to specify values for user-home-directory
and username
:
-Duser.home=
pathname
specifies the value of user-home-directory
-Duser.name=
usernanme
specifies the value of username
.
For example, the following command configures the user-home directory to be c:\myHome
and the user name to be wlAdmin
. The command will search for the following user-configuration file and user key file:c:\myHome\wlAdmin-WebLogicConfig.properties
c:\myHome\wlAdmin-WebLogicKey.properties
java -Duser.home=c:\myHome -Duser.name=wlAdmin
weblogic.Admin
COMMAND
Creating User-Configuration and Key Files
To create user-configuration and key files:
-username
username
and -password
password
arguments to specify the username and password to be encrypted.
-userconfigfile
config-file
and -userkeyfile
key-file
arguments:java weblogic.Admin -username
username
-password
password
-userconfigfile
config-file
-userkeyfile
key-file
STOREUSERCONFIG
user-home-directory
\
username
-WebLogicConfig.properties
and user-home-directory
\
username
-WebLogicKey.properties:
java weblogic.Admin -username
username
-password
password
STOREUSERCONFIG
-Duser.home=
directory
and -Duser.name=
username
Java options to create files nameddirectory
\
username
-WebLogicConfig.properties
and directory
\
username
-WebLogicKey.properties:
java -Duser.home=
directory
-Duser.name=
username
weblogic.Admin -username
username
-password
password
STOREUSERCONFIG
You can change the name and location of a user-configuration file or a key file after you create them, as long as you use the two files as a pair.
Using a Single Key File for Multiple User-Configuration Files
To use one key file to encrypt multiple user-configuration files:
For example, enter the following command:
java weblogic.Admin -username
username
-password
password
-userconfigfile c:\AdminConfig -userkeyfile e:\myKeyFile
STOREUSERCONFIG
For example, enter the following command:
java weblogic.Admin -username
username
-password
password
-userconfigfile c:\anotherConfigFile -userkeyfile e:\myKeyFile
STOREUSERCONFIG
In the following example, a user who is logged in to a UNIX operating system as joe
encrypts the username wlAdmin
and password wlPass
:
java weblogic.Admin -username wlAdmin -password wlPass
STOREUSERCONFIG
The command determines whether a key file named ~joe/joe-WebLogicKey.properties
exists. If such a file does not exist, it prompts the user to select y
to confirm creating a key file. If the command succeeds, it creates two files:~joe\joe-WebLogicConfig.properties
~joe\joe-WebLogicKey.properties
The file joe-WebLogicConfig.properties
contains an encrypted version of the strings wlAdmin
and wlPass
. Any command that uses the ~joe\joe-WebLogicConfig.properties
file must specify the ~joe\joe-WebLogicKey.properties
key file.
In the following example, the user joe
is a System Administrator who wants to create a user-configuration file for an operating-system account named pat
. For the sake of convenience, joe
wants to create the user-configuration file in pat
's home directory, which will simplify the syntax of the weblogic.Admin
commands that pat
invokes. For added security, only one key file exists at joe
's organization, and it is located on a removable hard drive.
To create a user configuration file in pat
's home directory that is encrypted and decrypted by a key file name e:\myKeyFile
:
java -Duser.name=pat -Duser.home="C:\Documents and Settings\pat" weblogic.Admin -username wlOperatorPat -password wlOperator1 -userkeyfile e:\myKeyFile
STOREUSERCONFIG
A user who logs in to pat
's account can use the following syntax to invoke weblogic.Admin
commands:java weblogic.Admin -userkeyfile e:\myKeyFile
COMMAND
For information on using user-configuration and key files, see Summary of User Credentials Arguments.
Provides a real-time snapshot of the WebLogic Server threads that are currently running.
Syntax
java weblogic.Admin [Connection and User Credentials Arguments]
THREAD_DUMP
UNLOCK
Unlocks the specified WebLogic Server after a LOCK operation.
java weblogic.Admin [Connection and User Credentials Arguments]
UNLOCK
Argument |
Definition |
---|---|
|
Required. A valid administrative username must be supplied to use this command. |
|
Required. A valid administrative password must be supplied to use this command. |
In the following example, an administrator named adminuser
with a password of gumby1234
requests the unlocking of the WebLogic Server listening on port 7001 on machine localhost
:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 UNLOCK
VERSION
Displays the version of the WebLogic Server software that is running on the machine specified by the value of URL
.
java weblogic.Admin [Connection and User Credentials Arguments] VERSION
In the following example, a user requests the version of the WebLogic Server running on port 7001 on machine localhost
:
java weblogic.Admin -url localhost:7001 -usernameguest
-passwordguest
VERSION
Note: In this example, the default value of both the username
and password
arguments, guest
, is used.
WebLogic Server Connection Pools Administration Command Reference
Table B-2 presents an overview of WebLogic Server administration commands for connection pools. The following sections describe command syntax and arguments, and provide an example for each command.
For additional information about connection pools see Programming WebLogic JDBC and Managing JDBC Connectivity in the Administration Guide.
Allows creation of connection pool while WebLogic Server is running. For more information, see "Creating a Connection Pool Dynamically in Programming WebLogic JDBC.
java weblogic.Admin [Connection and User Credentials Arguments]
CREATE_POOL poolName aclName=aclX, props=myProps,initialCapacity=1,maxCapacity=1, capacityIncrement=1,allowShrinking=true,shrinkPeriodMins=15, driver=myDriver,url=myURL
In the following example, a user with the name adminuser
and the password gumby1234
runs the CREATE_POOL
command to create a dynamic connection pool:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 CREATE_POOL myPool
java weblogic.Admin -url t3://forest:7901 -username system -password gumby1234 CREATE_POOL dynapool6 "aclName=someAcl, allowShrinking=true,shrinkPeriodMins=10, url=jdbc:weblogic:oracle,driver=weblogic.jdbc.oci.Driver, initialCapacity=2,maxCapacity=8, props=user=SCOTT;password=tiger;server=bay816"
Connections are closed and removed from the pool and the pool dies when it has no remaining connections. Only the "system" user or users granted "admin" permission by an ACL associated with a connection pool can destroy the pool.
java weblogic.Admin [Connection and User Credentials Arguments]
DESTROY_POOL poolName [true|false]
In the following example, a user with the name adminuser
and the password gumby1234
runs the DESTROY_POOL
command temporarily freeze the active pool connections:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 DESTROY_POOL myPool false
You can temporarily disable a connection pool, preventing any clients from obtaining a connection from the pool. Only the "system" user or users granted "admin" permission by an ACL associated with a connection pool can disable or enable the pool.
You have to options for disabling a pool. 1) Freezing the connections in a pool that you later plan to enable, and 2) destroy the connections.
java weblogic.Admin [Connection and User Credentials Arguments]
DISABLE_POOL poolName [true|false]
In the following example, a user with the name adminuser
and the password gumby1234
runs the DISABLE_POOL
command to freeze a connection that is to be enabled later:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 DISABLE_POOL myPool false
When a pool is enabled, the JDBC connection states for each in-use connection are exactly as they were when the connection pool was disabled; clients can continue JDBC operations exactly where they left off.
java weblogic.Admin [Connection and User Credentials Arguments]
ENABLE_POOL poolName
Argument |
Definition |
---|---|
|
Name of the connection pool. |
In the following example, a user with the name adminuser
and the password gumby1234
runs the ENABLE_POOL
command to reestablish connections that have been disabled (frozen):
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 ENABLE_POOL myPool
Tests whether a connection pool with a specified name exists in the WebLogic Server. You can use this method to determine whether a dynamic connection pool has already been created or to ensure that you select a unique name for a dynamic connection pool you want to create.
java weblogic.Admin [Connection and User Credentials Arguments]
EXISTS_POOL poolName
Argument |
Definition |
---|---|
|
Name of connection pool. |
In the following example, a user with the name adminuser
and the password gumby1234
runs the EXISTS_POOL
command to determine wether or not a pool with a specific name exists:
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 EXISTS_POOL myPool
This command resets the connections in a registered connection pool.
This is a privileged command. You must supply the password for the WebLogic Server administrative user to use this command. You must know the name of the connection pool, which is an entry in the config.xml
file.
Syntax
java weblogic.Admin URL RESET_POOL poolName system password
Example
This command refreshes the connection pool registered as "eng" for the WebLogic Server listening on port 7001 of the host xyz.com.
java weblogic.Admin t3://xyz.com:7001 RESET_POOL eng system gumby
Mbean Management Command Reference
Table B-3 presents an overview of the Mbean management commands. The following sections describe command syntax and arguments, and provide an example for each command.
CREATE
Creates an instance of a configuration Mbean. Returns OK
to stdout
when successful. This command cannot be used for run-time Mbeans. The Mbean instance is saved in the config.xml
file or the security realm, depending on where the changes have been made.
Note: When you create Mbeans, configuration objects are also created.
For more information about creating Mbeans, see Developing WebLogic Server Applications.
java weblogic.Admin [Connection and User Credentials Arguments] CREATE -name name -type mbean_type [-domain domain_name]
java weblogic.Admin [Connection and User Credentials Arguments] CREATE -mbean mbean_name
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 CREATE -mbean "mydomain:Type=Server,Name=acctServer"
DELETE
Deletes a configuration Mbean. Returns OK
in stdout
when successful. This command cannot be used for run-time Mbeans.
Note: When you delete Mbeans, configuration objects are also deleted.
For more information about deleting Mbeans, see Developing WebLogic Server Applications.
java weblogic.Admin [Connection and User Credentials Arguments] DELETE {-type mbean_type|-mbean mbean_name}
java weblogic.Admin -url localhost:7001 -username adminuser -password gumby1234 DELETE -mbean "mydomain:Type=Server,Name=AcctServer"
Displays run-time Mbean attributes. You can request a list of attributes for multiple objects of the same type by requesting attributes for the following:
GET
{-pretty} -typembean_type
GET
{-pretty} -mbeanmbean_name
The name of each of the specified Mbeans is included in the output. If -pretty
is specified, each attribute name-value pair is displayed on a new line.
The GET command can only call run-time Mbeans.
The name-value pair for each attribute is specified within curly brackets. This format facilitates scripting by simplifying the parsing of the output.
The name of the Mbean is included in the output as follows:
{mbeanname
mbean_name
{property1
value
} {property2
value
}. . .} {mbeanname
mbean_name
{property1
value
} {property2
value
} . . .} . . .
If -pretty
is specified, each attribute name-value pair is displayed on a new line. The name of each of the specified Mbeans is also included in the output, which is displayed as follows:
mbeanname
:
mbean_name property1
:
value property2
:
value
. . .
mbeanname
:
mbean_name property1
:
value property2
:
value
java weblogic.Admin [Connection and User Credentials Arguments] GET {-pretty} {-type mbean_type|-mbean mbean_name} [-property property1] [-property property2]...
In the following example, a user requests a display of the Mbean attributes for a server named localhost
, which is listening on port 7001:
java weblogic.Admin -url localhost:7001 GET -pretty -type Server
INVOKE
Invokes the specified method (including arguments) on the specified Mbean. This command can call only run-time Mbeans. Use this command to invoke methods that do not get or set Mbean attributes.
java weblogic.Admin [Connection and User Credentials Arguments] INVOKE {-type mbean_type|-mbean mbean_name} -methodmethodname
[argument
. . .]
Example
The following example invokes an administration Mbean named admin_one
using the method getAttributeStringValue
:
java weblogic.Admin -username system -password gumby1234 INVOKE -mbean mydomain:Name=admin_one,Type=Administrator -method getAttributeStringValue PhoneNumber
Sets the specified attribute values for the named configuration Mbean. Returns OK
on stdout
when successful. This command cannot be used for run-time Mbeans.
New values are saved to the config.xml
file or the security realm, depending on where the new values have been defined.
java weblogic.Admin [Connection and User Credentials Arguments] SET {-type mbean_type|-mbean mbean_name} -property property1 property1_value [-property property2 property2_value] . . .
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|