The following sections describe the WLST commands and variables in detail. Topics include:
Note:
It is recommended that you review "Syntax for WLST Commands" in Oracle WebLogic Scripting Tool for command syntax requirements.
WLST commands are divided into the following categories.
Table 3-1 WLST Command Categories
| Command Category | Description |
|---|---|
|
Navigate the hierarchy of configuration or runtime beans and control the prompt display. |
|
|
|
|
Add the command group help and command help that is displayed by the WLST |
|
|
|
|
Export diagnostic data. |
|
|
Interrogate and edit configuration beans. |
|
|
Interrogate WebLogic domains, servers, and variables, and provide configuration bean, runtime bean, and WLST-related information. |
|
|
Manage the life cycle of a server instance. |
|
|
Start, shut down, restart, and monitor WebLogic Server instances using Node Manager. |
|
|
Navigate among MBean hierarchies. |
Use the WLST browse commands, listed in Table 3-2, to navigate the hierarchy of configuration or runtime beans and control the prompt display.
Table 3-2 Browse Commands for WLST Configuration
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Navigate the hierarchy of configuration or runtime beans. |
Online or Offline |
|
|
Return the current location in the hierarchy. |
Online |
|
|
Toggle the display of path information at the prompt. |
Online or Offline |
|
|
Display the current location in the hierarchy. |
Online or Offline |
Command Category: Browse Commands
Use with WLST: Online or Offline
Navigates the hierarchy of configuration or runtime beans. This command uses a model that is similar to navigating a file system in a Windows or UNIX command shell. For example, to navigate back to a parent configuration or runtime bean, enter cd('..'). The character string .. (dot-dot), refers to the directory immediately above the current directory. To get back to the root bean after navigating to a bean that is deep in the hierarchy, enter cd('/').
You can navigate to beans in the current hierarchy and to any child or instance.
The cd command returns a stub of the configuration or runtime bean instance, if one exists. If you navigate to a type, this command returns a stub of the configuration or runtime bean instance from which you navigated. In the event of an error, the command returns a WLSTException.
Note:
The cmo variable is initialized to the root of all domain configuration beans when you first connect WLST to a server instance. It reflects the parent configuration bean type until you navigate to an instance. For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
The following example navigates the hierarchy of configuration beans. The first command navigates to the Servers configuration bean type, the second, to the myserver configuration bean instance, and the last back up two levels to the original directory location.
wls:/mydomain/serverConfig> cd('Servers') wls:/mydomain/serverConfig/Servers> cd('myserver') wls:/mydomain/serverConfig/Servers/myserver> cd('../..') wls:/mydomain/serverConfig>
Command Category: Browse Commands
Use with WLST: Online
Returns the current location in the hierarchy. This command enables you to store the current location in the hierarchy and easily return to it after browsing. In the event of an error, the command returns a WLSTException.
The following example stores the current location in the hierarchy in myTree and uses it to navigate back to the Edit MBean hierarchy from the runtime MBean hierarchy on an Administration Server instance.
wls:/mydomain/edit> myTree=currentTree() wls:/mydomain/edit> serverRuntime() Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root. For more help, use help('serverRuntime') wls:/mydomain/serverRuntime> myTree() wls:/mydomain/edit>
Command Category: Browse Commands
Use with WLST: Online or Offline
Toggles the display of path information at the prompt, when entered without an argument. This command is useful when the prompt becomes too long due to the length of the path.
You can also explicitly specify on or off as an argument to the command. When you specify off, WLST hides the WLST prompt and defaults to the Jython prompt. By default, the WLST prompt displays the configuration or runtime navigation path information.
When you disable the prompt details, to determine your current location in the hierarchy, you can use the pwd command, as described in pwd.
In the event of an error, the command returns a WLSTException.
prompt(myPrompt)
| Argument | Definition |
|---|---|
myPrompt
|
Optional. Hides or displays WLST prompt. Valid values include
|
The following example hides and then redisplays the path information at the prompt.
wls:/mydomain/serverConfig/Servers/myserver> prompt()
wls:/> prompt()
wls:/mydomain/serverConfig/Servers/myserver>
The following example hides the prompt and defaults to the Jython prompt (since the command is run using WLST online), changes the Jython prompt, and then redisplays the WLST prompt. This example also demonstrates the use of the pwd command.
Note:
For more information about programming using Jython, see http://www.jython.org.
wls:/mydomain/serverConfig/Servers/myserver> prompt('off') >>>sys.ps1="myprompt>" myprompt> prompt() wls:> pwd() 'serverConfig:Servers/myserver' wls:> prompt() wls:/mydomain/serverConfig/Servers/myserver>
Command Category: Browse Commands
Use with WLST: Online or Offline
Displays the current location in the configuration or runtime bean hierarchy.
This command is useful when you have turned off the prompt display of the path information using the prompt command, as described in prompt.
In the event of an error, the command returns a WLSTException.
Use the WLST control commands, listed in Table 3-3, to perform the following tasks:
Connect to or disconnect from a server (connect and disconnect commands)
Create a new WebLogic domain from a domain template, similar to the Configuration Wizard (createDomain, readTemplate, writeDomain, and closeTemplate commands)
Update an existing WebLogic domain, offline (readDomain, addTemplate, updateDomain, and closeDomain commands)
Write a domain template (writeTemplate command)
Exit WLST
Table 3-3 lists the control commands for WLST configuration.
Table 3-3 Control Commands for WLST Configuration
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Connect WLST to a WebLogic Server instance. |
Online or Offline |
|
|
Disconnect WLST from a WebLogic Server instance. |
Online |
|
|
Create a new WebLogic domain using the specified template. |
Offline |
|
|
Open an existing domain template for domain creation. |
Offline |
|
|
Write the domain configuration information to the specified directory. |
Offline |
|
|
Close the current domain template. |
Offline |
|
|
Open an existing WebLogic domain for updating. |
Offline |
|
|
Extend the current WebLogic domain using an application or service extension template. |
Offline |
|
|
Update and save the current domain. |
Offline |
|
|
Close the current domain. |
Offline |
|
|
Writes the configuration information to the specified domain template file. |
Offline |
|
|
Exit WLST from the interactive session and close the scripting shell. |
Online or Offline |
Command Category: Control Commands
Use with WLST: Offline
Extends the current WebLogic domain using an application or service extension template. Use the Template Builder to create an application or service extension template. See Oracle WebLogic Server Creating Templates Using the Domain Template Builder.
In the event of an error, the command returns a WLSTException.
addTemplate(templateFileName)
| Argument | Definition |
|---|---|
templateFileName
|
Name of the application or service extension template. |
The following example opens a WebLogic domain and extends it using the specified extension template, DefaultWebApp.jar.
wls:/offline> readDomain('c:/Oracle/Middleware/user_projects/domains/wlw') wls:/offline/wlw> addTemplate('c:/Oracle/Middleware/wlserver_10.3 /common/templates/applications/DefaultWebApp.jar') wls:/offline/wlw>
Command Category: Control Commands
Use with WLST: Offline
Closes the current domain. The domain is no longer available for editing once it is closed. In the event of an error, the command returns a WLSTException.
Command Category: Control Commands
Use with WLST: Offline
Closes the current domain template. The domain template is no longer available once it is closed. In the event of an error, the command returns a WLSTException.
Command Category: Control Commands
Use with WLST: Online or Offline
Connects WLST to a WebLogic Server instance.
Requires you to provide the credentials (user name and password) of a user who has been defined in the active WebLogic security realm. Once you are connected, a collection of security policies determine which configuration attributes you are permitted to view or modify. (See "Default Security Policies for MBeans" in the WebLogic Server MBean Reference.)
You can supply user credentials by doing any of the following:
Enter the credentials on the command line. This option is recommended only if you are using WLST in interactive mode.
Enter the credentials on the command line, then use the storeUserConfig command to create a user configuration file that contains your credentials in an encrypted form and a key file that WebLogic Server uses to unencrypt the credentials. On subsequent WLST sessions (or in WLST scripts), supply the name of the user configuration file and key file instead of entering the credentials on the command line. This option is recommended if you use WLST in script mode because it prevents you from storing unencrypted user credentials in your scripts.
Use the credentials that are stored in the Administration Server's boot.properties file. By default, when you create an Administration Server in development mode, WebLogic Server encrypts the credentials that were used to create the server and stores them in a boot.properties file. When you create an Administration Server in production mode, no boot.properties file is created. If your production domain does not contain a boot.properties file, you can create one manually; see "Creating a Boot Identify File for an Administration Server" in Managing Server Startup and Shutdown for Oracle WebLogic Server.
When you run the connect command, if there is a boot.properties file containing the encrypted username and password for the domain, you do not have to enter the username and password to connect to the Administration Server. You do, however, have to specify the name of the Administration Server in the connect command.
Please note:
If you run the connect command in a script without specifying the username and password or user configuration file and key file, a WSLTException occurs. In interactive mode, you are prompted for the username and password.
Oracle strongly recommends that you connect WLST to the server through the SSL port or administration port. If you do not, the following warning message is displayed:
Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.
If you are connecting to a WebLogic Server instance through an SSL listen port on a server that is using the demonstration SSL keys and certificates, invoke WLST using the following command:
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
For more information about invoking WLST, see "Main Steps for Using WLST in Interactive or Script Mode" in Oracle WebLogic Scripting Tool.
If you are connecting to a WebLogic Server instance via HTTP, ensure that the TunnelingEnabled attribute is set to true for the WebLogic Server instance. For more information, see "TunnelingEnabled" in Oracle WebLogic Server MBean Reference.
When trying to connect to the WebLogic Server Administration Server from WLST using localhost as the host name, the following message may be displayed if the listen-address attribute of the Administration Server has been restricted to certain IP addresses:
javax.naming.CommunicationException [Root exception is java.net.ConnectException : <t3://HOST:PORT> : Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination
You can use either of the following workarounds for this issue:
Check that the listen-address attribute of the Administration Server has been set correctly. For example, in the domain configuration file:
<server> <name>AdminServer</name> <ssl> . . . </ssl> <machine>your_machine</machine> <!-- listen-address><your_ip_address></listen-address --> </server>
Use the hostname of the Administration Server, instead of localhost, in the WLST connect command.
After successfully connecting to a WebLogic Server instance, all the local variables are initialized.
In the event of an error, the command returns a WLSTException.
connect([username, password], [url], [timeout]) connect([userConfigFile, userKeyFile], [url], [timeout]) connect([url], [adminServerName], [timeout])
| Argument | Definition |
|---|---|
username
|
Optional. Username of the operator who is connecting WLST to the server. If not specified, WLST processes the command as described above. |
password
|
Optional. Password of the operator who is connecting WLST to the server. If not specified, WLST processes the command as described above. |
url
|
Optional. Listen address and listen port of the server instance, specified using the following format: |
timeout
|
Optional. The number of milliseconds that WLST waits for online commands to complete (return). When you invoke a WLST online command, WLST connects to an MBean Server, invokes an MBean server method, and returns the results of the invocation. If the MBean server method does not return within the timeout period, WLST abandons its invocation attempt. Use the following syntax for this argument:
A value of |
userConfigFile
|
Optional. Name and location of a user configuration file which contains an encrypted username and password. Use the following syntax for this argument:
If not specified, WLST processes the command as described above. When you create a user configuration file, the |
userKeyFile
|
Optional. Name and location of the key file that is associated with the specified user configuration file and is used to decrypt it. Use the following syntax for this argument:
If not specified, WLST processes the command as described above. See storeUserConfig. |
adminServerName
|
Optional. Name of the Administration Server for the domain. Causes the connect command to use the credentials that are stored in the Administration Server's
This argument is valid only when you start WLST from a domain directory. If the If not specified, WLST processes the command as described above. |
The following example connects WLST to a WebLogic Server instance. In this example, the Administration Server name defaults to AdminServer. Note that a warning is displayed if the SSL or administration port is not used to connect to the server.
wls:/offline> connect('weblogic','welcome1','t3://localhost:8001')
Connecting to weblogic server instance running at t3://localhost:8001 as
username weblogic...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'mydomain'.
Warning: An insecure protocol was used to connect to the server. To ensure
on-the-wire security, the SSL port or Admin port should be used instead.
wls:/mydomain/serverConfig>
The following example connects WLST to a WebLogic Server instance at the specified URL. In this example, the username and password are passed as variables. This example uses a secure protocol.
wls:/offline> username = 'weblogic' wls:/offline> password = 'welcome1' wls:/offline> connect(username,password,'t3s://myhost:8001') Connecting to weblogic server instance running at t3://myhost:8001 as username weblogic... Successfully connected to Admin Server 'AdminServer' that belongs to domain 'mydomain'. wls:/mydomain/serverConfig>
The following example connects WLST to a WebLogic Server instance using a user configuration and key file to provide user credentials.
wls:/offline> connect(userConfigFile='c:/myfiles/myuserconfigfile.secure', userKeyFile='c:/myfiles/myuserkeyfile.secure') Connecting to t3://localhost:7001 with userid username ... Successfully connected to Admin Server 'AdminServer' that belongs to domain 'mydomain'. wls:/mydomain/serverConfig>
The following example shows the prompts that are displayed in interactive mode if you run the command without parameters:
wls:/offline> connect() Please enter your username :username Please enter your password : Please enter your server URL [t3://localhost:7001] : Connecting to t3//localhost:7001 with userid username
Command Category: Control Commands
Use with WLST: Offline
Creates a WebLogic domain using the specified template.
Note:
If you wish to modify the domain configuration settings when creating a WebLogic domain, see Option 2 in "Editing a Domain (Offline)" in Oracle WebLogic Scripting Tool.
The createDomain command is similar in functionality to the unpack command, as described in Creating Templates and Domains Using the pack and unpack Commands.
In the event of an error, the command returns a WLSTException.
createDomain(domainTemplate, domainDir, user, password)
| Argument | Definition |
|---|---|
domainTemplate
|
Name and location of the domain template from which you want to create a domain. |
domainDir
|
Name of the directory to which you want to write the domain configuration information. Oracle recommends that you create all domains for your environment outside of the Middleware home directory. This makes it easier for you to remove an existing installation or install a new version of WebLogic Server without having to recreate your domains and applications. |
user
|
Name of the default user. |
password
|
Password of the default user. |
The following example creates a new WebLogic domain using the Avitek MedRec template and sets the default username to weblogic and the password to welome1. The domain is saved to the following directory: c:/Oracle/Middleware/wlserver_10.3/user_projects/domains/medrec.
wls:/offline> createDomain('c:/Oracle/Middleware/wlserver_10.3/common /templates/domains/wls_medrec.jar','c:/Oracle/Middleware/user_projects/domains/medrec', 'weblogic', 'welcome1')
Command Category: Control Commands
Use with WLST: Online
Disconnects WLST from a WebLogic Server instance. The disconnect command does not cause WLST to exit the interactive scripting shell; it closes the current WebLogic Server instance connection and resets all the variables while keeping the interactive shell alive.
In the event of an error, the command returns a WLSTException.
You can connect to another WebLogic Server instance using the connect command, as described in connect.
disconnect(force)
| Argument | Definition |
|---|---|
force
|
Optional. Boolean value specifying whether WLST should disconnect without waiting for the active sessions to complete. This argument defaults to |
Command Category: Control Commands
Use with WLST: Online or Offline
Exits WLST from the user session and closes the scripting shell.
If there is an edit session in progress, WLST prompts you for confirmation. To skip the prompt, set the defaultAnswer argument to y.
By default, WLST calls System.exit(0) for the current WLST JVM when exiting WLST. If you would like the JVM to exit with a different exit code, you can specify a value using the exitCode argument.
Note:
When the WLST exit command is issued within an Ant script, it may also exit the execution of the Ant script. It is recommended that when invoking WLST within an Ant script, you fork a new JVM by specifying fork="true".
In the event of an error, the command returns a WLSTException.
exit([defaultAnswer], [exitcode])
| Argument | Definition |
|---|---|
defaultAnswer
|
Optional. Default response, if you would prefer not to be prompted at the command line. Valid values are |
exitcode
|
Optional. Exit code to set when exiting WLST. |
The following example disconnects from the user session and closes the scripting shell.
wls:/mydomain/serverConfig> exit()
Exiting WebLogic Scripting Tool ...
c:\>
The following example disconnects from the user session, closes the scripting shell, and sets the error code to 101.
wls:/mydomain/serverConfig> exit(exitcode=101)
Exiting WebLogic Scripting Tool ...
c:\>
Command Category: Control Commands
Use with WLST: Offline
Opens an existing WebLogic domain for updating.
WLST offline provides read and write access to the configuration data that is persisted in the config directory for the WebLogic domain, or in a domain template JAR created using Template Builder. This data is a collection of XML documents and expresses a hierarchy of management objects.
When you open a template or WebLogic domain, WLST is placed at the root of the configuration hierarchy for that domain, and the prompt is updated to reflect the current location in the configuration hierarchy. For example:
wls:/offline/base_domain>
For more information, see "Navigating and Interrogating MBeans" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
readDomain(domainDirName)
| Argument | Definition |
|---|---|
domainDirName
|
Name of the WebLogic domain directory that you want to open. |
Command Category: Control Commands
Use with WLST: Offline
Opens an existing domain template for domain creation.
When you open a domain template, WLST is placed into the configuration bean hierarchy for that domain template, and the prompt is updated to reflect the current location in the configuration hierarchy. For example:
wls:/offline/base_domain>
WebLogic Server configuration beans exist within a hierarchical structure. In the WLST file system, the hierarchies correspond to drives; types and instances are directories; attributes and operations are files. WLST traverses the hierarchical structure of configuration beans using commands such as cd, ls, and pwd in a similar way that you would navigate a file system in a UNIX or Windows command shell. After navigating to a configuration bean instance, you interact with the bean using WLST commands. For more information, see "Navigating and Interrogating MBeans" in Oracle WebLogic Scripting Tool.
Note:
Using WLST and a domain template, you can only create and access security information when you are creating a new WebLogic domain. When you are updating a WebLogic domain, you cannot access security information through WLST.
In the event of an error, the command returns a WLSTException.
readTemplate(templateFileName)
| Argument | Definition |
|---|---|
templateFileName
|
Name of the JAR file corresponding to the domain template. |
Command Category: Control Commands
Use with WLST: Offline
Updates and saves the current WebLogic domain. The domain continues to be editable after you update and save it.
In the event of an error, the command returns a WLSTException.
Command Category: Control Commands
Use with WLST: Offline
Writes the domain configuration information to the specified directory.
Once you write the WebLogic domain to file system, you can continue to update the domain template object that exists in memory, and reissue the writeDomain command to store the domain configuration to a new or existing file.
By default, when you write a WebLogic domain, the associated applications are written to WL_HOME/user_projects/applications/domainname, where WL_HOME specifies the WebLogic Server home directory and domainname specifies the name of the WebLogic domain. This directory must be empty; otherwise, WLST displays an error.
When you have finished using the domain template object in memory, close it using the closeTemplate command. If you want to edit the WebLogic domain that has been saved to disk, you can open it using the readDomain command.
Note:
The name of the WebLogic domain is derived from the name of the domain directory. For example, for a domain saved to c:/Oracle/Middleware/user_projects/domains/myMedrec, the domain name is myMedrec.
Before writing the domain, you must define a password for the default user, if it is not already defined. For example:
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('welcome1')
In the event of an error, the command returns a WLSTException.
writeDomain(domainDir)
| Argument | Definition |
|---|---|
domainDir
|
Name of the directory to which you want to write the domain configuration information. |
The following example reads the medrec.jar domain templates, performs some operations, and writes the domain configuration information to the c:/Oracle/Middleware/user_projects/domains/medrec directory.
wls:/offline> readTemplate('c:/Oracle/Middleware/wlserver_10.3/common/templates /domains/wls.jar') ... wls:/offline/base_domain> writeDomain('c:/Oracle/Middleware/user_projects/domains/base_domain')
Command Category: Control Commands
Use with WLST: Offline
Writes the domain configuration information to the specified domain template. You can use the domain configuration template to recreate the WebLogic domain.
Once your write the configuration information to the domain configuration template, you can continue to update the WebLogic domain or domain template object that exists in memory, and reissue the writeDomain or writeTemplate command to store the domain configuration to a new or existing WebLogic domain or domain template file. For more information, see writeDomain or writeTemplate, respectively.
In the event of an error, the command returns a WLSTException.
Note:
The writeTemplate command is similar in functionality to the pack command; see "The pack Command" in Creating Templates and Domains Using the pack and unpack Commands. However, writeTemplate does not support creating a Managed Server template.
writeTemplate(templateName)
| Argument | Definition |
|---|---|
templateName
|
Name of the domain template to store the domain configuration information. |
The following example writes the current domain configuration to the domain template named c:/Oracle/Middleware/user_projects/templates/myTemplate.jar.
wls:/offline> readDomain('c:/Oracle/Middleware/user_projects/domains/mydomain') ... wls:/offline/base_domain> writeTemplate('c:/Oracle/Middleware/user_projects /templates/myTemplate.jar')
Use the WLST customization commands, listed in Table 3-4, to add the command group help and command help that is listed by the WLST help() and help('commandGroup') commands. For more information about adding command help to WLST, see "Adding Integrated Help for Custom Commands" in Oracle WebLogic Scripting Tool.
Table 3-4 Customization Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Adds a new help command group to those shown by the WLST |
Online or Offline |
|
|
Adds new command help for a command to an existing command group. Once added to the group, the command (along with a brief description) is displayed in the command list for the group when you enter the |
Online or Offline |
Command Category: Customization Commands
Use with WLST: Online or Offline
Adds a new command help group to those shown by the WLST help() command, and specifies the resource bundle in which the help information is defined for the group.
addHelpCommandGroup(commandGroup, resourceBundleName)
| Argument | Definition |
|---|---|
commandGroup
|
Use a unique name for the command group. Do not use a command group name that is already shown by the WLST |
resourceBundleName
|
Represents either a class name or property resource file name. The resource bundle contains help text for entries for the command group using a standard pattern. The resource bundle name will be passed to The resource bundle must be present in the classpath. See "Adding Integrated Help for Custom Commands" in Oracle WebLogic Scripting Tool for information on how to define the help text for each command group and command. For more information on resourceBundles and localization, refer to |
The following example adds the boot command group to the list of groups shown by the help() command, and specifies that the help text is located in the property resource file 'myhelp':
wls:/offline> addHelpCommandGroup('boot','myhelp')
The following example adds the boot command group to the list of groups shown by the help() command, and specifies that the help text is located in the class foo.bar.MyResourceBundleClass:
wls:/offline> addHelpCommandGroup('boot','foo.bar.MyResourceBundleClass')
Command Category: Customization Commands
Use with WLST: Online or Offline
Adds new command help for a command to an existing command group. Once added to the group, the command (along with a brief description) is displayed in the command list for the group when you enter the help('commandGroup') command. You can also specify whether or not the command is listed by the help('online') and help('offline') commands.
addHelpCommand(commandName,commandGroup,[offline=false, online=false])
| Argument | Definition |
|---|---|
commandName
|
The name of the command as defined in the command group specified by commandGroup. |
commandGroup
|
The commandGroup to which the command belongs. |
online |
Optional. Boolean value that determines whether or not the command shows up in the |
offline |
Optional. Boolean value that determines whether or not the command shows up in the |
Use the WLST deployment commands, listed in Table 3-5, to:
Deploy, undeploy, and redeploy applications and standalone modules to a WebLogic Server instance.
Update an existing deployment plan.
Interrogate the WebLogic Deployment Manager object.
Start and stop a deployed application.
For more information about deploying applications, see Deploying Applications to Oracle WebLogic Server.
Table 3-5 Deployment Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Deploy an application to a WebLogic Server instance. |
Online |
|
|
Copy the deployment bundle to the specified targets. |
Online |
|
|
Return the WebLogic |
Online |
|
|
List all applications that are currently deployed in the WebLogic domain. |
Online |
|
|
Load an application and deployment plan into memory. |
Online and Offline |
|
|
Redeploy a previously deployed application. |
Online |
|
|
Start an application, making it available to users. |
Online |
|
|
Stop an application, making it unavailable to users. |
Online |
|
|
Undeploy an application from the specified servers. |
Online |
|
|
Update an application configuration using a new deployment plan. |
Online |
Command Category: Deployment Commands
Use with WLST: Online
Deploys an application to a WebLogic Server instance.
The deploy command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
Note:
If there is an edit session in progress, the deploy command does not block user interaction.
deploy(appName, path, [targets], [stageMode], [planPath], [options])
| Argument | Definition |
|---|---|
appName
|
Name of the application or standalone Java EE module to be deployed. |
path
|
Name of the application directory, archive file, or root of the exploded archive directory to be deployed. |
targets
|
Optional. Comma-separated list of the targets. Each target may be qualified with a Java EE module name (for example, |
stageMode
|
Optional. Staging mode for the application you are deploying. Valid values are |
planPath
|
Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. Valid options include:
|
options
(Continued) |
|
The following example deploys the businessApp application located at c:/myapps/business, A default deployment plan is created.
The deploy command returns a WLSTProgress object that you can access to check the status of the command. The WLSTProgress object is captured in a user-defined variable, in this case, progress.
wls:/mydomain/serverConfig/Servers> progress= deploy(appName='businessApp', path='c:/myapps/business',createplan='true')
The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to print the status of the deploy command. For example:
wls:/mydomain/serverConfig/Servers> progress.printStatus()
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : completed
Deployment Message : null
wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
The following example deploys the demoApp application in the archive file located at c:/myapps/demos/app/demoApp.ear, targeting the application modules to myserver, and using the deployment plan file located in c:/myapps/demos/app/plan/plan.xml. WLST waits 120,000 ms for the process to complete.
wls:/mydomain/serverConfig/Servers> deploy('demoApp', 'c:/myapps/demos/app/demoApp.ear', targets='myserver', planPath='c:/myapps/demos/app/plan/plan.xml', timeout=120000)
The following example deploys the jmsApp application located at c:/myapps/demos/jmsApp/demo-jms.xml, targeting the application module to a specific target.
wls:/mydomain/serverConfig/Servers> deploy('jmsApp',path= 'c:/myapps/demos/jmsApps/demo-jms.xml', subModuleTargets='jmsApp@managed1')
The following example shows how to set the application version (appVersion) to a unique identifier to support production (side-by-side) redeployment. This example deploys the demoApp application in the archive file located at c:/myapps/demos/app/demoApp.ear, and sets the application and archive version numbers to the specified values.
wls:/mydomain/serverConfig> deploy('demoApp', 'c:/myapps/demos/app/demoApp.ear', archiveVersion='901-101', appVersion='901-102')
For more information about production redeployment strategies, see "Redeploying Applications in a Production Environment" in Deploying Applications to Oracle WebLogic Server.
Command Category: Deployment Commands
Use with WLST: Online
Copies the deployment bundle to the specified targets. The deployment bundle includes module, configuration data, and any additional generated code. The distributeApplication command does not start deployment.
The distributeApplication command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
distributeApplication(appPath, [planPath], [targets], [options])
| Argument | Definition |
|---|---|
appPath
|
Name of the archive file or root of the exploded archive directory to be deployed. |
planPath
|
Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the |
targets
|
Optional. Comma-separated list of targets. Each target may be qualified with a Java EE module name (for example, |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see the |
The following example loads the BigApp application located in the c:/myapps directory, and stores the WLSTProgress object in a user-defined variable, in this case, progress.
The following example distributes the c:/myapps/BigApp application to the myserver, oamserver1, and oamcluster servers, using the deployment plan defined at c:/deployment/BigApp/plan.xml.
wls:/offline> progress=distributeApplication('c:/myapps/BigApp', 'c:/deployment/BigApp/plan.xml', 'myserver,oamserver1,oamcluster') Distributing Application and Plan ... Successfully distributed the application.
The previous example stores the WLSTProgress object in a user-defined variable, in this case, progress. You can then use the progress variable to determine if the distributeApplication command has completed. For example:
wls:/mydomain/serverConfig/Servers> progress.isCompleted()
1
wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
Command Category: Deployment Commands
Use with WLST: Online
Returns the WebLogic DeploymentManager object. You can use the object methods to configure and deploy applications. WLST must be connected to an Administration Server to run this command. In the event of an error, the command returns a WLSTException.
Command Category: Deployment Commands
Use with WLST: Online
Lists all applications that are currently deployed in the WebLogic domain.
In the event of an error, the command returns a WLSTException.
The following example lists all the applications currently deployed in mydomain.
wls:/mydomain/serverConfig> listApplications()
SamplesSearchWebApp
asyncServletEar
jspSimpleTagEar
ejb30
webservicesJwsSimpleEar
ejb20BeanMgedEar
xmlBeanEar
extServletAnnotationsEar
examplesWebApp
apache_xbean.jar
mainWebApp
jdbcRowSetsEar
Command Category: Deployment Commands
Use with WLST: Online and Offline
Loads an application and deployment plan into memory. When used in online mode, you can connect only to the Administration Server; you cannot connect to a Managed Server.
The loadApplication command returns a WLSTPlan object that you can access to make changes to the deployment plan. For more information about the WLSTPlan object, see "WLSTPlan Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
loadApplication(appPath, [planPath], [createPlan])
| Argument | Definition |
|---|---|
appPath
|
Name of the top-level parent application directory, archive file, or root of the exploded archive directory containing the application to be loaded. |
planPath
|
Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the |
createPlan
|
Optional. Boolean value specifying whether WLST should create a plan in the application directory if the specified plan does not exist. This argument defaults to |
The following example loads the c:/myapps/myejb.jar application using the plan file at c:/myplans/myejb/plan.xml.
wls:/offline> myPlan=loadApplication('c:/myapps/myejb.jar', 'c:/myplans/myejb/plan.xml')
Loading application from c:/myapps/myejb.jar and deployment plan from c:/myplans/myejb/plan.xml ...
Successfully loaded the application.
The previous example stores the WLSTPlan object returned in the myPlan variable. You can then use myPlan variable to display information about the plan, such as the variables. For example:
wls:/offline> myPlan.showVariables()
MyEJB jndi.ejb
MyWAR app.foo
For more information about the WLSTPlan object, see "WLSTPlan Object" in Oracle WebLogic Scripting Tool.
Command Category: Deployment Commands
Use with WLST: Online
Reloads classes and redeploys a previously deployed application.
The redeploy command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
For more information about redeploying applications, see "Overview of Common Deployment Scenarios" in Deploying Applications to Oracle WebLogic Server.
redeploy(appName, [planPath], [options])
| Argument | Definition |
|---|---|
appName
|
Name of the application to be redeployed. |
planPath
|
Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see In addition, the following deployment option can be specified for the
|
The following example redeploys myApp application using the plan.xml file located in the c:/myapps directory.
wls:/mydomain/serverConfig> progress=redeploy('myApp' 'c:/myapps/plan.xml')
Redeploying application 'myApp' ...
Redeployment of 'myApp' is successful
wls:/mydomain/serverConfig>
The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to access the state of the redeploy command. For example:
wls:/mydomain/serverConfig/Servers> progress.getState()
'completed'
wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
Command Category: Deployment Commands
Use with WLST: Online
Starts an application, making it available to users. The application must be fully configured and available in the WebLogic domain.
The startApplication command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
startApplication(appName, [options])
| Argument | Definition |
|---|---|
appName
|
Name of the application to start, as specified in the |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see |
The following example starts the BigApp application with the specified deployment options.
wls:/mydomain/serverConfig/Servers> progress=startApplication('BigApp', stageMode='NOSTAGE', testMode='false')
Starting the application...
Successfully started the application.
The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to access the state of the startApplication command. For example:
wls:/mydomain/serverConfig/Servers> progress.getState()
'completed'
wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
Command Category: Deployment Commands
Use with WLST: Online
Stops an application, making it unavailable to users. The application must be fully configured and available in the WebLogic domain.
The stopApplication command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
stopApplication(appName, [options])
| Argument | Definition |
|---|---|
appName
|
Name of the application to stop, as specified in the |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see |
The following example stops the BigApp application.
wls:/offline> progress=stopApplication('BigApp')
Stopping the application...
Successfully stopped the application.
The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to check whether stopApplication command is running. For example:
wls:/mydomain/serverConfig/Servers> progress.isRunning()
0
wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
Command Category: Deployment Commands
Use with WLST: Online
Undeploys an application from the specified servers.
The undeploy command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
For more information about deploying and undeploying applications, see "Overview of Common Deployment Scenarios" in Deploying Applications to Oracle WebLogic Server.
undeploy(appName,[targets],[options])
| Argument | Definition |
|---|---|
appName
|
Deployment name for the deployed application. |
targets
|
Optional. List of the target servers from which the application will be removed. If not specified, defaults to all current targets. |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see |
The following example removes the businessApp application from all target servers. WLST waits 60,000 ms for the process to complete.
wls:/mydomain/serverConfig> undeploy('businessApp', timeout=60000)
Undeploying application businessApp ...
<Jul 20, 2005 9:34:15 AM EDT> <Info> <J2EE Deployment SPI> <BEA-260121>
<Initiating undeploy operation for application, businessApp [archive: null],
to AdminServer .>
Completed the undeployment of Application with status
Current Status of your Deployment:
Deployment command type: undeploy
Deployment State : completed
Deployment Message : no message
wls:/mydomain/serverConfig>
Command Category: Deployment Commands
Use with WLST: Online
Updates an application configuration using a new deployment plan. The application must be fully configured and available in the WebLogic domain.
The updateApplication command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.
updateApplication(appName, [planPath], [options])
| Argument | Definition |
|---|---|
appName
|
Name of the application, as specified in the current |
planPath
|
Optional. Name of the new deployment plan file. The filename can be absolute or relative to the application directory. |
options
|
Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see |
The following example updates the application configuration for BigApp using the plan.xml file located in c:/myapps/BigApp/newPlan.
wls:/offline> progress=updateApplication('BigApp', 'c:/myapps/BigApp/newPlan/plan.xml', stageMode='STAGE', testMode='false') Updating the application... Successfully updated the application.
The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to access the state of the updateApplication command. For example:
wls:/mydomain/serverConfig/Servers> progress.getState() 'completed' wls:/mydomain/serverConfig/Servers>
For more information about the WLSTProgress object, see "WLSTProgress Object" in Oracle WebLogic Scripting Tool.
Use the WLST diagnostics commands, listed in Table 3-6, to retrieve diagnostics data by executing queries against the WebLogic Diagnostics Framework (WLDF) data stores. For more information about WLDF, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
Table 3-6 Diagnostic Command for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Execute a query against the specified log file. |
Offline |
|
|
Executes a query on the server side and retrieves the exported WebLogic Diagnostic Framework (WLDF) data. |
Online |
|
|
Returns a list of the previously captured diagnostic images. |
Online |
|
|
Downloads the specified diagnostic image capture. |
Online |
|
|
Downloads a specific entry from the diagnostic image capture. |
Online |
Command Category: Diagnostics Commands
Use with WLST: Offline
Executes a query against the specified log file. The results are saved to an XML file.
For more information about the WebLogic Server Diagnostic Service, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
exportDiagnosticData([options])
| Argument | Definition |
|---|---|
options
|
Optional. Comma-separated list of export diagnostic options, specified as name-value pairs. Valid options include:
|
The following example executes a query against the ServerLog named myserver.log and stores the results in the file named myExport.xml.
wls:/offline/mydomain>exportDiagnosticData(logicalName='ServerLog', logName='myserver.log', exportFileName='myExport.xml') {'elfFields': '', 'logName': 'myserver.log', 'logRotationDir': '.', 'endTimestamp': 9223372036854775807L, 'exportFileName': 'export.xml', 'storeDir': '../data/store/diagnostics', 'logicalName': 'ServerLog', 'query': '', 'beginTimestamp': 0} Exporting diagnostic data to export.xml <Aug 2, 2005 6:58:21 PM EDT> <Info> <Store> <BEA-280050> <Persistent store "WLS_DIAGNOSTICS" opened: directory="c:\Oracle\Middleware \wlserver_10.3\server\data\store\diagnostics" writePolicy="Disabled" blockSize=512 directIO=false driver="wlfileio2"> wls:/mydomain/serverRuntime>
Command Category: Diagnostics Commands
Use with WLST: Online
Executes a query on the server side and retrieves the exported WebLogic Diagnostic Framework (WLDF) data. The results are saved to an XML file.
For more information about the WebLogic Server Diagnostic Service, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
exportDiagnosticDataFromServer([options])
| Argument | Definition |
|---|---|
options
|
Optional. Comma-separated list of export diagnostic options, specified as name-value pairs. Valid options include:
|
Command Category: Diagnostics Commands
Use with WLST: Online
Returns, as an array of strings, a list of the previously captured diagnostic images that are stored in the image destination directory configured on the server. The default directory is SERVER\logs\diagnostic_images.
This command is useful for identifying a diagnostic image capture that you want to download, or for identifying a diagnostic image capture from which you want to download a specific entry.
For more information about the WebLogic Server Diagnostic Service, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
The following example returns an array of strings named images, which contains a list of the diagnostic image capture files available in the image destination directory, and prints the entries contained in the diagnostic image named diagnostic_image_myserver_2009_06_15_14_58_36.zip.
wls:/mydomain/serverRuntime>images=getAvailableCapturedImages() Connecting to http://localhost:7001 with userid weblogic ... wls:/mydomain/serverRuntime>print images [ 'diagnostic_image_myserver_2009_06_15_14_58_36.zip' ]
Command Category: Diagnostics Commands
Use with WLST: Online
Downloads the specified diagnostic image capture from the server to which WLST is currently connected.
For more information about the WebLogic Server Diagnostic Service, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
saveDiagnosticImageCaptureFile(imageName, [outputFile])
| Argument | Definition |
|---|---|
imageName
|
The name of the diagnostic image capture to download. |
outputFile
|
Optional. Local path and file name in which the retrieved diagnostic image capture is to be stored. If not specified, this argument defaults to the value of |
The following example retrieves the list of the diagnostic image captures that are stored in the image destination directory on the server. It then shows two uses of the saveDiagnosticImageCaptureFile command. In the first use, the first diagnostic image capture in the list is downloaded to the local machine using the default output file name. In the second use, the first diagnostic image capture in the list is downloaded to the local machine in the file mylocalimg.zip.
wls:/mydomain/serverRuntime>images=getAvailableCapturedImages() Connecting to http://localhost:7001 with userid weblogic ... wls:/mydomain/serverConfig> saveDiagnosticImageCaptureFile(images[0]) Retrieving diagnostic_image_myserver_2009_06_25_12_12_50.zip to local path diagnostic_image_myserver_2009_06_25_12_12_50.zip Connecting to http://localhost:7001 with userid weblogic ... wls:/mydomain/serverConfig> saveDiagnosticImageCaptureFile(images[0], 'mylocalimg.zip') Retrieving diagnostic_image_myserver_2009_06_25_12_12_50.zip to local path mylocalimg.zip Connecting to http://localhost:7001 with userid weblogic ...
Command Category: Diagnostics Commands
Use with WLST: Online
Downloads a specific entry from the diagnostic image capture that is located on the server to which WLST is currently connected.
For more information about the WebLogic Server Diagnostic Service, see Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
saveDiagnosticImageCaptureEntryFile(imageName, imageEntryName, [outputFile])
| Argument | Definition |
|---|---|
imageName
|
Name of the diagnostic image capture containing the desired entry. |
imageEntryName
|
Name of the specific entry to be retrieved from the diagnostic image capture. This can be one of the following: image.summary JTA.img JRockitFlightRecorder.jfr FlightRecording.jfr WatchSource.img configuration.img WORK_MANAGER.img JNDI_IMAGE_SOURCE.img APPLICATION.img InstrumentationImageSource.img SAF.img Logging.img PERSISTENT_STORE.img JDBC.img PathService.img JMS.img Deployment.img JVM.img CONNECTOR.img |
outputFile
|
Optional. Local path and file name in which the entry retrieved from the diagnostic image capture is to be stored. If not specified, this argument defaults to the value of |
The following example gets the list of diagnostic image captures, then uses the saveDiagnosticImageCaptureEntryFile twice. In the first use, this example retrieves the image summary to the local machine using the default output file name. In the second use, it retrieves the image summary to the local machine in the file myimage.summary.
wls:/mydomain/serverRuntime>images=getAvailableCapturedImages() Connecting to http://localhost:7001 with userid weblogic ... wls:/mydomain/serverConfig> saveDiagnosticImageCaptureEntryFile(images[0], 'image.summary') Retrieving entry image.summary from diagnostic_image_myserver_2009_06_25_12_12_50.zip to local path image.summary Connecting to http://localhost:7001 with userid weblogic ... wls:/mydomain/serverConfig> saveDiagnosticImageCaptureEntryFile(images[0], 'image.summary', 'myimage.summary') Retrieving entry image.summary from diagnostic_image_myserver_2009_06_25_12_12_50.zip to local path myimage.summary Connecting to http://localhost:7001 with userid weblogic ...
Use the WLST editing commands, listed in Table 3-7, to interrogate and edit configuration beans.
Note:
To edit configuration beans, you must be connected to an Administration Server, and you must navigate to the edit tree and start an edit session, as described in edit and startEdit, respectively.
If you connect to a Managed Server, WLST functionality is limited to browsing the configuration bean hierarchy. While you cannot use WLST to change the values of MBeans on Managed Servers, it is possible to use the Management APIs to do so. Oracle recommends that you change only the values of configuration MBeans on the Administration Server. Changing the values of MBeans on Managed Servers can lead to an inconsistent domain configuration.
For more information about editing configuration beans, see "Using WLST Online to Update an Existing Domain" in Oracle WebLogic Scripting Tool.
Table 3-7 Editing Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Activate changes saved during the current editing session but not yet deployed. |
Online or Offline |
|
|
Assign resources to one or more destinations. |
Offline |
|
|
Cancel an edit session, release the edit lock, and discard all unsaved changes. This operation can be called by any user with administrator privileges, even if the user did not start the edit session. |
Online |
|
|
Create a configuration bean of the specified type for the current bean. |
Online or Offline |
|
|
Delete an instance of a configuration for the current configuration bean. |
Online or Offline |
|
|
Encrypt the specified string. |
Online |
|
|
Return the value of the specified attribute. |
Online or Offline |
|
|
Return the latest |
Online |
|
|
Invokes a management operation on the current configuration bean. |
Online |
|
|
Determine whether a server restart is required. |
Online |
|
|
Load SQL files into a database. |
Offline |
|
|
Load property values from a file. |
Online or Offline |
|
|
Save the edits that have been made but have not yet been saved. |
Online |
|
|
Set the specified attribute value for the current configuration bean. |
Online or Offline |
|
|
Set options related to a WebLogic domain creation or update. |
Offline |
|
|
Show the changes made to the configuration by the current user during the current edit session. |
Online |
|
|
Starts a configuration edit session on behalf of the currently connected user. |
Online |
|
|
Stop the current edit session, release the edit lock, and discard unsaved changes. |
Online |
|
|
Unassign applications or resources from one or more destinations. |
Offline |
|
|
Revert all unsaved or unactivated edits. |
Online |
|
|
Validate the changes that have been made but have not yet been saved. |
Online |
Command Category: Editing Commands
Use with WLST: Online
Activates changes saved during the current editing session but not yet deployed. This command prints a message if a server restart is required for the changes that are being activated.
The activate command returns the latest ActivationTask MBean which reflects the state of changes that a user is currently making or has made recently. You can then invoke methods to get information about the latest Configuration Manager activate task in progress or just completed. In the event of an error, the command returns a WLSTException.
activate([timeout], [block])
| Argument | Definition |
|---|---|
timeout
|
Optional. Time (in milliseconds) that WLST waits for the activation of configuration changes to complete before canceling the operation. A value of -1 indicates that the operation will not time out. This argument defaults to 300,000 ms (or 5 minutes). |
block
|
Optional. Boolean value specifying whether WLST should block user interaction until the command completes. This argument defaults to |
The following example activates the changes made during the current edit session that have been saved to disk, but that have not yet been activated. WLST waits for 100,000 ms for the activation to complete, and 200,000 ms before the activation is stopped.
wls:/mydomain/edit !> activate(200000, block='true')
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Action completed.
wls:/mydomain/edit>
Command Category: Editing Commands
Use with WLST: Offline
Assigns resources to one or more destinations.
In the event of an error, the command returns a WLSTException.
assign(sourceType, sourceName, destinationType, destinationName)
| Argument | Definition |
|---|---|
sourceType
|
Type of configuration bean to be assigned. This value can be set to one of the following values:
Guidelines for setting this value are provided below. |
sourceName
|
Name of the resource to be assigned. Multiple names can be specified, separated by commas, or you can use the wildcard (*) character to specify all resources of the specified type. Specify subdeployments using the following format: Note: A given subdeployment name cannot contain a dot (.), as the |
destinationType
|
Type of destination. Guidelines for setting this value are provided below. |
destinationName
|
Name of the destination. Multiple names can be specified, separated by commas. |
Use the following guidelines for setting the sourceType and destinationType:
When assigning application deployments, set the values as follows:
sourceType: AppDeployment
destinationType: Target
When assigning libraries, set the values as follows:
sourceType: Library
destinationType: Target
When assigning services, set the values as follows:
sourceType: Name of the specific server, such as JDBCSystemResource
destinationType: Target
When assigning servers to clusters, set the values as follows:
sourceType: Server
destinationType: Cluster
When assigning subdeployments, set the values as follows:
sourceType: service.SubDeployment, where service specifies the parent of the SubDeployment, such as JMSSystemResource.SubDeployment; you can also specify nested subdeployments (such as AppDeployment.SubDeployment.SubDeployment)
destinationType: Target
When assigning security types, set the values as follows:
sourceType: Name of the security type, such as User
destinationType: Name of the destination security type, such as Group
The following examples:
Assign the servers myServer and myServer2 to the cluster myCluster.
wls:/offline/mydomain> assign("Server", "myServer,myServer2", "Cluster", "myCluster")
Assign all servers to the cluster myCluster.
wls:/offline/mydomain> assign("Server", "*", "Cluster", "myCluster")
Assign the application deployment myAppDeployment to the target server newServer.
wls:/offline/mydomain> assign("AppDeployment", "myAppDeployment", "Target", "newServer")
Assign the user newUser to the group Monitors.
wls:/offline/mydomain> assign("User", "newUser", "Group", "Monitors")
Assign the SubDeployment myQueueSubDeployment, which is a child of the JMS resource myJMSResource, to the target server newServer.
wls:/offline/mydomain> assign('JMSSystemResource.SubDeployment', 'myJMSResource.myQueueSubDeployment', 'Target', 'newServer')
Assign the nested SubDeployment MedRecAppScopedJMS.MedRecJMSServer, which is a child of the AppDeployment AppDeployment, to the target server AdminServer.
wls:/offline/mydomain>assign('AppDeployment.SubDeployment.SubDeployment ','MedRecEAR.MedRecAppScopedJMS.MedRecJMSServer','Target','AdminServer')
Command Category: Editing Commands
Use with WLST: Online
Cancels an edit session, releases the edit lock, and discards all unsaved changes.
The user issuing this command does not have to be the current editor; this allows an administrator to cancel an edit session, if necessary, to enable other users to start an edit session.
In the event of an error, the command returns a WLSTException.
cancelEdit([defaultAnswer])
| Argument | Definition |
|---|---|
defaultAnswer
|
Optional. Default response, if you would prefer not to be prompted at the command line. Valid values are |
Command Category: Editing Commands
Use with WLST: Online or Offline
Creates a configuration bean of the specified type for the current bean.
The create command returns a stub for the newly created configuration bean. In the event of an error, the command returns a WLSTException.
Note:
Child types must be created under an instance of their parent type. You can only create configuration beans that are children of the current Configuration Management Object (cmo) type. For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
Please note the following when using the create command with WLST online:
You must be connected to an Administration Server. You cannot use the create command for runtime MBeans or when WLST is connected to a Managed Server instance.
You must navigate to the edit configuration MBean hierarchy using the edit command before issuing this command. See edit.
You can use the create command to create a WebLogic Server configuration MBean that is a child of the current MBean type.
Please note the following when using the create command with WLST offline:
When using WLST offline, the following characters are not valid in object names: period (.), forward slash (/), or backward slash (\).
For more information about:
Creating MBeans, see "Understanding WebLogic Server MBeans" in Developing Custom Management Utilities with JMX.
Examples of creating specific types of MBean resources, for example, a JMS or JDBC system resource, refer to the WLST sample scripts installed with your product, as described in "WLST Sample Scripts" in Oracle WebLogic Scripting Tool.
MBeans, their child types, attributes, and operations, see Oracle WebLogic Server MBean Reference.
create(name, childMBeanType, [baseProviderType])
| Argument | Definition |
|---|---|
name
|
Name of the configuration bean that you are creating. |
childMBeanType
|
Type of configuration bean that you are creating. You can create instances of any type defined in the |
baseProviderType
|
When creating a security provider, specifies the base security provider type, for example, |
The following example creates a child configuration bean of type Server named newServer for the current configuration bean, storing the stub as server1:
wls:/mydomain/edit !> server1=create('newServer','Server') Server with name 'newServer' has been created successfully. wls:/mydomain/edit !> server1.getName() 'newServer' wls:/mydomain/edit !>
The following example creates an authentication provider security provider called myProvider:
wls:/mydomain/edit !> cd('SecurityConfiguration/mydomain/Realms/myrealm') wls:/mydomain/edit !> create('myProvider','weblogic.security.providers.authentication.SQLAuthenticator' ,'AuthenticationProvider') wls:/mydomain/edit ! cd('AuthenticationProviders/myProvider') wls:/mydomain/edit ! set('ControlFlag', 'REQUIRED')
The following example creates a machine named highsec_nm and sets attributes for the associated Node Manager.
wls:/mydomain/edit !> create('highsec_nm', 'Machine') wls:/mydomain/edit !> cd('Machine/highsec_nm/NodeManager/highsec_nm') wls:/mydomain/edit !> set('DebugEnabled', 'true') wls:/mydomain/edit !> set('ListenAddress', 'innes') wls:/mydomain/edit !> set('NMType', 'SSL') wls:/mydomain/edit !> set('ShellCommand', '')
Command Category: Editing Commands
Use with WLST: Online or Offline
Deletes an instance of a configuration bean of the specified type for the current configuration bean.
In the event of an error, the command returns a WLSTException.
Note:
You can only delete configuration beans that are children of current Configuration Management Object (cmo) type. For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
delete(name, childMBeanType)
| Argument | Definition |
|---|---|
name
|
Name of the child configuration bean to delete. |
childMBeanType
|
Type of the configuration bean to be deleted. You can delete instances of any type defined in the |
Command Category: Editing Commands
Use with WLST: Online
Encrypts the specified string. You can then use the encrypted string in your configuration file or as an argument to a command.
You must invoke this command once for each WebLogic domain in which you want to use the encrypted string. The string can be used only in the WebLogic domain for which it was originally encrypted.
In the event of an error, the command returns a WLSTException.
encrypt(obj, [domainDir])
| Argument | Definition |
|---|---|
obj
|
String that you want to encrypt. |
domainDir
|
Optional. Absolute path name of a WebLogic domain directory. The encrypted string can be used only by the WebLogic domain that is contained within the specified directory. If you do not specify this argument, the command encrypts the string for use in the WebLogic domain to which WLST is currently connected. |
Command Category: Editing Commands
Use with WLST: Online or Offline
Returns the value of the specified attribute. For more information about the MBean attributes that can be viewed, see Oracle WebLogic Server MBean Reference. In the event of an error, the command returns a WLSTException.
Note:
You can list all attributes and their current values by entering ls('a'). For more information, see ls.
Alternatively, you can use the cmo variable to perform any get method on the current configuration bean. For example:
cmo.getListenPort()
For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
get(attrName)
| Argument | Definition |
|---|---|
attrName
|
Name of the attribute to be displayed. You can specify the full pathname of the attribute. If no pathname is specified, the attribute is displayed for the current configuration object. |
Command Category: Editing Commands
Use with WLST: Online
Return the latest ActivationTask MBean on which a user can get status. The ActivationTask MBean reflects the state of changes that a user has made recently in WLST. You can then invoke methods to get information about the latest Configuration Manager activate task in progress or just completed. In the event of an error, the command returns a WLSTException.
Note:
If you have activated changes outside of WLST, use the ConfigurationManagerMBean getActivationTasks() method to get access to Activation Tasks created in other tools.
Command Category: Editing Commands
Use with WLST: Online
Invokes a management operation on the current configuration bean. Typically, you use this command to invoke operations other than the get and set operations that most WebLogic Server configuration beans provide. The class objects are loaded through the same class loader that is used for loading the configuration bean on which the action is invoked.
You cannot use the invoke command when WLST is connected to a Managed Server instance.
If successful, the invoke command returns the object that is returned by the operation invoked. In the event of an error, the command returns a WLSTException.
invoke(methodName, parameters, signatures)
| Argument | Definition |
|---|---|
methodName
|
Name of the method to be invoked. |
parameters
|
An array of parameters to be passed to the method call. |
signatures
|
An array containing the signature of the action. |
The following example invokes the lookupServer method on the current configuration bean.
wls:/mydomain/config> objs = jarray.array([java.lang.String("oamserver")],java.lang.Object) wls:/mydomain/edit> strs = jarray.array(["java.lang.String"],java.lang.String) wls:/mydomain/edit> invoke('lookupServer',objs,strs) true wls:/mydomain/edit>
Command Category: Editing Commands
Use with WLST: Online
Determines whether a server restart is required.
If you invoke this command while an edit session is in progress, the response is based on the edits that are currently in progress. If you specify the name of an attribute, WLST indicates whether a server restart is required for that attribute only.
In the event of an error, the command returns a WLSTException.
isRestartRequired([attributeName])
| Argument | Definition |
|---|---|
attributeName
|
Optional. Name of a specific attribute for which you want to check if a server restart is required. |
The following example specifies whether a server restart is required for all changes made during the current WLST session.
wls:/mydomain/edit !> isRestartRequired()
Server re-start is REQUIRED for the set of changes in progress.
The following attribute(s) have been changed on MBeans that require server re-start.
MBean Changed : mydomain:Name=mydomain,Type=Domain
Attributes changed : AutoConfigurationSaveEnabled
The following example specifies whether a server restart is required if you edit the ConsoleEnabled attribute.
wls:/mydomain/edit !> isRestartRequired("ConsoleEnabled")
Server re-start is REQUIRED if you change the attribute ConsoleEnabled wls:/mydomain/edit !>
Command Category: Editing Commands
Use with WLST: Offline
Loads SQL files into a database.
The loadDB command loads the SQL files from a template file. This command can only be issued after a domain template or extension template has been loaded into memory (see readDomain and readTemplate).
Before executing this command, ensure that the following conditions are true:
The appropriate database is running.
SQL files exist for the specified database and version.
To verify that the appropriate SQL files exist, open the domain template and locate the relevant SQL file list, jdbc.index, in the _jdbc_ directory. For example, for Oracle 9i, the SQL file list is located at _jdbc_\Oracle\9i\jdbc.index.
The command fails if the above conditions are not met.
In the event of an error, the command returns a WLSTException.
loadDB(dbVersion, datasourceName, dbCategory)
| Argument | Definition |
|---|---|
dbVersion
|
Version of the database for which the SQL files are intended to be used. |
datasourceName
|
Name of the JDBC data source to be used to load SQL files. |
dbCategory
|
Optional. Database category associated with the specified data source. For more information about the |
Command Category: Editing Commands
Use with WLST: Online and Offline
Loads property values from a file and makes them available in the WLST session.
This command cannot be used when you are importing WLST as a Jython module, as described in "Importing WLST as a Jython Module" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
Command Category: Editing Commands
Use with WLST: Online
Saves the edits that have been made but have not yet been saved. This command is only valid when an edit session is in progress. For information about starting an edit session, see startEdit.
In the event of an error, the command returns a WLSTException.
Command Category: Editing Commands
Use with WLST: Online or Offline
Sets the value of a specified attribute in the current management object. When using WLST offline, this command writes the attribute value to the domain configuration files. When using WLST online, this command sets the value of an MBean attribute. Online changes are written to the domain configuration file when you activate your edits.
In the event of an error, the command returns a WLSTException.
For information about setting encrypted attributes (all encrypted attributes have names that end with Encrypted), see "Writing and Reading Encrypted Configuration Values" in Oracle WebLogic Scripting Tool.
Note the following when using WLST online:
You must be in an edit session to use this command. See startEdit.
You cannot use this command when WLST is connected to a Managed Server.
As an alternative to this command, you can use the cmo variable with the following syntax:
cmo.setattrName(value)
For example, instead of using set('ListenPort', 7011), you can use:
cmo.setListenPort(7011)
For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
set(attrName, value)
| Argument | Definition |
|---|---|
attrName
|
Name of the attribute to be set. |
value
|
Value of the attribute to be set. Note: This value should not be enclosed in single or double quotes. See the examples. |
The following example sets the ArchiveConfigurationCount attribute of DomainMBean to 10:
wls:/mydomain/serverConfig> set('ArchiveConfigurationCount', 10)
The following example sets the long value of the T1TimerInterval attribute of a custom Mbean to 123:
wls:/mydomain/serverConfig> set('T1TimerInterval', Long(123))
The following example sets the boolean value of the MyBooleanAttribute attribute of a custom Mbean to true:
wls:/mydomain/serverConfig> set('MyBooleanAttribute', Boolean(true))
Command Category: Editing Commands
Use with WLST: Offline
Sets options related to a WebLogic domain creation or update. In the event of an error, the command returns a WLSTException.
setOption(optionName, optionValue)
| Argument | Definition |
|---|---|
optionName
|
Name of the option to set. Available options for domain creation include:
Available options for domain updates include:
Available options for both domain creation and domain updates include:
|
optionValue
|
Value for the option. Note: Boolean values can be specified as a String ( |
Command Category: Editing Commands
Use with WLST: Online
Shows the changes made to the configuration by the current user during the current edit session. In the event of an error, the command returns a WLSTException.
showChanges([onlyInMemory])
| Argument | Definition |
|---|---|
onlyInMemory
|
Optional. Boolean value specifying whether to display only the changes that have not yet been saved. This argument defaults to |
The following example shows all of the changes made by the current user to the configuration since the start of the current edit session.
wls:/mydomain/edit !> showChanges()
Changes that are in memory and saved to disc but not yet activated are:
MBean Changed : com.bea:Name=basicWLSDomain,Type=Domain
Operation Invoked : add
Attribute Modified : Machines
Attributes Old Value : null
Attributes New Value : Mach1
Server Restart Required : false
MBean Changed : com.bea:Name=basicWLSDomain,Type=Domain
Operation Invoked : add
Attribute Modified : Servers
Attributes Old Value : null
Attributes New Value : myserver
Server Restart Required : false
Command Category: Editing Commands
Use with WLST: Online
Starts a configuration edit session on behalf of the currently connected user. You must navigate to the edit configuration MBean hierarchy using the edit command before issuing this command. For more information, see edit.
This command must be called prior to invoking any command to modify the WebLogic domain configuration.
In the event of an error, the command returns a WLSTException.
Note:
WLST automatically starts an edit session if it detects that there is an edit session that is already in progress by the same user, which may have been started via the Administration Console or another WLST session.
startEdit([waitTimeInMillis], [timeoutInMillis], [exclusive])
| Argument | Definition |
|---|---|
waitTimeInMillis
|
Optional. Time (in milliseconds) that WLST waits until it gets a lock, in the event that another user has a lock. This argument defaults to 0 ms. |
timeOutInMillis
|
Optional. Timeout (in milliseconds) that WLST waits to release the edit lock. This argument defaults to -1 ms, indicating that this edit session never expires. |
exclusive
|
Optional. Specifies whether the edit session should be an exclusive session. If set to |
Command Category: Editing Commands
Use with WLST: Online
Stops the current edit session, releases the edit lock, and discards unsaved changes.
In the event of an error, the command returns a WLSTException.
stopEdit([defaultAnswer])
| Argument | Definition |
|---|---|
defaultAnswer
|
Optional. Default response, if you would prefer not to be prompted at the command line. Valid values are |
Command Category: Editing Commands
Use with WLST: Offline
Unassign applications or resources from one or more destinations.
In the event of an error, the command returns a WLSTException.
unassign(sourceType, sourceName, destinationType, destinationName)
| Argument | Definition |
|---|---|
sourceType
|
Type of configuration bean to be unassigned. This value can be set to one of the following values:
|
sourceName
|
Name of the application or resource to be unassigned. Multiple names can be specified, separated by commas, or you can use the wildcard (*) character to specify all resources of the specified type. Specify subdeployments using the following format: |
destinationType
|
Type of destination. Guidelines for setting this value are provided below. |
destinationName
|
Name of the destination. Multiple names can be specified, separated by commas. |
Use the following guidelines for setting the sourceType and destinationType:
When unassigning application deployments, set the values as follows:
sourceType: AppDeployment
destinationType: Target
When unassigning libraries, set the values as follows:
sourceType: Library
destinationType: Target
When unassigning security types, set the values as follows:
sourceType: Name of the security type, such as User
destinationType: Name of the destination security type, such as Group
When unassigning servers from clusters, set the values as follows:
sourceType: Server
destinationType: Cluster
When unassigning services, set the values as follows:
sourceType: Name of the specific server, such as JDBCSystemResource
destinationType: Target
When unassigning subdeployments, set the values as follows:
sourceType: service.SubDeployment, where service specifies the parent of the SubDeployment, such as JMSSystemResource.SubDeployment; you can also specify nested subdeployments (such as AppDeployment.SubDeployment.SubDeployment)
destinationType: Target
The following examples:
Unassign the servers myServer and myServer2 from the cluster myCluster.
wls:/offline/medrec> unassign("Server", "myServer,myServer2", "Cluster", "myCluster")
Unassign all servers from the cluster myCluster.
wls:/offline/mydomain> unassign("Server", "*", "Cluster", "myCluster")
Unassign the user newUser from the group Monitors.
wls:/offline/medrec> unassign("User", "newUser", "Group", "Monitors")
Unassign the application deployment myAppDeployment from the target server newServer.
wls:/offline/mydomain> unassign("AppDeployment", "myAppDeployment", "Target", "newServer")
Unassign the nested SubDeployment MedRecAppScopedJMS.MedRecJMSServer, which is a child of the AppDeployment AppDeployment, from the target server AdminServer.
wls:/offline/mydomain> assign('AppDeployment.SubDeployment.SubDeployment', 'MedRecEAR.MedRecAppScopedJMS.MedRecJMSServer', 'Target','AdminServer')
Command Category: Editing Commands
Use with WLST: Online
Reverts all unsaved or unactivated edits.
You specify whether to revert all unactivated edits (including those that have been saved to disk), or all edits made since the last save operation. This command does not release the edit session.
In the event of an error, the command returns a WLSTException.
undo([unactivatedChanges], [defaultAnswer])
| Argument | Definition |
|---|---|
unactivatedChanges
|
Optional. Boolean value specifying whether to undo all unactivated changes, including edits that have been saved to disk. This argument defaults to |
defaultAnswer
|
Optional. Default response, if you would prefer not to be prompted at the command line. Valid values are |
The following example reverts all changes since the last save operation. WLST prompts for verification before reverting.
wls:/mydomain/edit !> undo() Sure you would like to undo your changes? (y/n) y Discarded your in-memory changes successfully. wls:/mydomain/edit>
The following example reverts all unactivated changes. WLST prompts for verification before reverting.
wls:/mydomain/edit !> undo('true') Sure you would like to undo your changes? (y/n) y Discarded all your changes successfully. wls:/mydomain/edit>
Use the WLST information commands, listed in Table 3-8, to interrogate domains, servers, and variables, and provide configuration bean, runtime bean, and WLST-related information.
Table 3-8 Information Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Add a JMX listener to the specified MBean. |
Online |
|
|
Convert an existing server configuration ( |
Online or Offline |
|
|
Display stack trace from the last exception that occurred while performing a WLST action, and reset the stack trace. |
Online or Offline |
|
|
Display all variables used by WLST, including their name and value. |
Online or Offline |
|
|
Find MBeans and attributes in the current hierarchy. |
Online |
|
|
Return the latest |
Online |
|
|
Return the MBean by browsing to the specified path. |
Online |
|
|
Return the |
Online |
|
|
Return the MBean path for the specified MBean instance. |
Online |
|
|
List all the children MBeans that can be created or deleted for the cmo type. |
Online |
|
|
Look up the specified MBean. |
Online |
|
|
List all child beans and/or attributes for the current configuration or runtime bean. |
Online or Offline |
|
|
Display help from |
Online |
|
|
Redirect WLST output to the specified filename. |
Online |
|
|
Remove a listener that was previously defined. |
Online |
|
|
Show all listeners that are currently defined. |
Online |
|
|
Record all user interactions with WLST; useful for capturing commands to replay. |
Online or Offline |
|
|
Returns a map of servers or clusters and their state using Node Manager. |
Online |
|
|
Stop recording WLST commands. |
Online or Offline |
|
|
Stop redirection of WLST output to a file. |
Online or Offline |
|
|
Create a user configuration file and an associated key file. |
Online |
|
|
Display a thread dump for the specified server. |
Online or Offline |
|
|
Display information about an MBean, such as the attribute names and values, and operations. |
Online |
|
|
Convert WLST definitions and method declarations to a Python ( |
Online or Offline |
Command Category: Information Commands
Use with WLST: Online
Adds a JMX listener to the specified MBean. Any changes made to the MBean are reported to standard out and/or are saved to the specified configuration file.
In the event of an error, the command returns a WLSTException.
addListener(mbean, [attributeNames], [logFile], [listenerName])
| Argument | Definition |
|---|---|
mbean
|
Name of the MBean or MBean object to listen on. |
attributeNames
|
Optional. Comma-separated list of all attribute names on which you would like to add a JMX listener. This argument defaults to null, and adds a JMX listener for all attributes. |
logFile
|
Optional. Name and location of the log file to which you want to write listener information.This argument defaults to standard out. |
listenerName
|
Optional. Name of the JMX listener. This argument defaults to a WLST-generated name. |
The following example defines a JMX listener on the cmo MBean for the Notes and ArchiveConfigurationCount attributes. The listener is named domain-listener and is stored in ./listeners/domain.log.
wls:/mydomain/serverConfig> addListener(cmo, "Notes,ArchiveConfigurationCount", "./listeners/domain.log","domain-listener")
Command Category: Information Commands
Use with WLST: Online or Offline
Converts an existing server configuration (config directory) to an executable WLST script. You can use the resulting script to re-create the resources on other servers.
The configToScript command creates the following files:
A WLST script that contains the commands needed to recreate the configuration.
A properties file that contains domain-specific values. You can update the values in this file to create new domains that are similar to the original configuration.
A user configuration file and an associated key file to store encrypted attributes. The user configuration file contains the encrypted information. The key file contains a secret key that is used to encrypt and decrypt the encrypted information.
When you run the generated script:
If a server is currently running, WLST will try to connect using the values in the properties file and then run the script commands to create the server resources.
If no server is currently running, WLST will start a server with the values in the properties file, run the script commands to create the server resources, and shutdown the server. This may cause WLST to exit from the command shell.
In the event of an error, the command returns a WLSTException.
configToScript([configPath], [pyPath], [overwrite], [propertiesFile], [createDeploymentScript])
| Argument | Definition |
|---|---|
configPath
|
Optional. Path to the |
pyPath
|
Optional. Path and filename to which you want to write the converted WLST script. This argument defaults to |
overwrite
|
Optional. Boolean value specifying whether the script file should be overwritten if it already exists. This argument defaults to |
propertiesFile
|
Optional. Path to the directory in which you want WLST to write the properties files. This argument defaults to the pathname specified for the |
createDeploymentScript
|
Optional. Boolean value specifying whether WLST creates a script that performs deployments only. This argument defaults to |
The following example converts the configuration to a WLST script config.py. By default, the configuration file is loaded from ./config, the script file is saved to .config/config.py, and the properties files is saved to .config/config.py.properties.
wls:/offline> configToScript()
configToScript is loading configuration from c:\Oracle\Middleware
\user_projects\domains\wls\config\config.xml ...
Completed configuration load, now converting resources to wlst script...
configToScript completed successfully
The WLST script is written to c:\Oracle\Middleware
\user_projects\domains\wls\config\config.py
and the properties file associated with this script is written to c:\Oracle\
Middleware\user_projects\domains\wls\config\config.py.properties
wls:/offline>
The following example converts server resources configured in the file c:\Oracle\Middleware\user_projects\domains\mydomain\config directory to a WLST script c:\Oracle\Middleware\myscripts\config.py.
wls:/offline> configToScript('c:/Oracle/Middleware/user_projects/domains /mydomain','c:/Oracle/Middleware/myscripts') configToScript is loading configuration from c:\Oracle\Middleware \user_projects\domains\mydomain\config\config.xml ... Completed configuration load, now converting resources to wlst script... configToScript completed successfully The WLST script is written to c:\Oracle\Middleware\myscripts\config.py and the properties file associated with this script is written to c:\Oracle\Middlware\mydomain\config.py.properties wls:/offline>
Command Category: Information Commands
Use with WLST: Online or Offline
Displays the stack trace from the last exception that occurred while performing a WLST action, and resets the stack trace.
If successful, the dumpstack command returns the Throwable object. In the event of an error, the command returns a WLSTException.
Command Category: Information Commands
Use with WLST: Online or Offline
Displays all the variables used by WLST, including their name and value. In the event of an error, the command returns a WLSTException.
This example displays all the current variables and their values.
wls:/mydomain/serverConfig> dumpVariables()
adminHome weblogic.rmi.internal.BasicRemoteRef - hostID:
'-1 108080150904263937S:localhost:[7001,8001,-1,-1,-1,-1,-1]:
mydomain:AdminServer', oid: '259', channel: 'null'
cmgr [MBeanServerInvocationHandler]com.bea:Name=ConfigurationManager,
Type=weblogic.management.mbeanservers.edit.ConfigurationManagerMBean
cmo [MBeanServerInvocationHandler]com.bea:Name=mydomain,Type=Domain
connected true
domainName mydomain
...
wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online
Finds MBeans and attributes in the current hierarchy.
WLST returns the pathname to the MBean that stores the attribute and/or attribute type, and its value. If searchInstancesOnly is set to false, this command also searches the MBeanType paths that are not instantiated in the server, but that can be created. In the event of an error, the command returns a WLSTException.
find([name], [type], [searchInstancesOnly])
| Argument | Definition |
|---|---|
name
|
Optional. Name of the attribute to find. |
type
|
Optional. Type of the attribute to find. |
searchInstancesOnly
|
Optional. Boolean value specifying whether to search registered instances only or to also search |
The following example searches for an attribute named javaCompiler in the current configuration hierarchy.
wls:/mydomain/serverConfig> find(name = 'JavaCompiler')
Finding 'JavaCompiler' in all registered MBean instances ...
/Servers/AdminServer JavaCompilerPreClassPath null
/Servers/AdminServer JavaCompiler java
/Servers/AdminServer JavaCompilerPostClassPath null
wls:/mydomain/serverConfig>
The following example searches for an attribute of type JMSRuntime in the current configuration hierarchy.
wls:/mydomain/serverRuntime> find(type='JMSRuntime')
Finding MBean of type 'JMSRuntime' in all the instances ...
/JMSRuntime/AdminServer.jms
wls:/mydomain/serverRuntime>
The following example searches for an attribute named execute in the current configuration hierarchy. The searchInstancesOnly argument is set to false, indicating to also search MBeanTypes that are not instantiated in the server.
wls:/mydomain/serverConfig> find(name='execute', searchInstancesOnly='false')
Finding 'execute' in all registered MBean instances ...
/Servers/AdminServer ExecuteQueues [Ljavax.management.ObjectName;@1aa7dbc
/Servers/AdminSever Use81StyleExecuteQueues false
Now finding 'execute' in all MBean Types that can be instantiated ...
/Servers ExecuteQueues
/Servers Use81StyleExecuteQueues
wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online
Returns the latest ConfigurationManager MBean which manages the change process. You can then invoke methods to manage configuration changes across a WebLogic domain. In the event of an error, the command returns a WLSTException.
Command Category: Information Commands
Use with WLST: Online
Returns the MBean by browsing to the specified path. In the event of an error, the command returns a WLSTException.
Note:
No exception is thrown if the MBean is not found.
getMBean(mbeanPath)
| Argument | Definition |
|---|---|
mbeanPath
|
Path name to the MBean in the current hierarchy. |
Command Category: Information Commands
Use with WLST: Online
Returns the MBeanInfo for the specified MBeanType or the cmo variable. In the event of an error, the command returns a WLSTException.
getMBI([mbeanType])
| Argument | Definition |
|---|---|
mbeanType
|
Optional. |
Command Category: Information Commands
Use with WLST: Online
Returns the MBean path for the specified MBean instance or ObjectName for the MBean in the current tree. In the event of an error, the command returns a WLSTException.
getPath(mbean)
| Argument | Definition |
|---|---|
mbean |
MBean instance or ObjectName for the MBean in the current tree for which you want to return the MBean path. |
Command Category: Information Commands
Use with WLST: Online
Lists all the child MBeans that can be created or deleted for the cmo. The cmo variable specifies the configuration bean instance to which you last navigated using WLST. For more information about the cmo variable, see "Changing the Current Management Object" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
listChildTypes([parent])
| Argument | Definition |
|---|---|
parent
|
Optional. Parent type for which you want the children types listed. |
Command Category: Information Commands
Use with WLST: Online
Looks up the specified MBean. The MBean must be a child of the current MBean. In the event of an error, the command returns a WLSTException.
lookup(name, [childMBeanType])
| Argument | Definition |
|---|---|
name
|
Name of the MBean that you want to lookup. |
childMBeanType
|
Optional. The type of the MBean that you want to lookup. |
Command Category: Information Commands
Use with WLST: Online or Offline
Lists the attributes, operations, and child management objects of the specified management object.
In the event of an error, the command returns a WLSTException.
By default, the output is returned as a string and is arranged in three columns:
The first column displays a set of codes that describe the listed item. See Table 3-9.
The second column displays the item name.
When the item is an attribute, the third column displays the attribute value. If an attribute is encrypted, the third column displays asterisks instead of the value. (See "Writing and Reading Encrypted Configuration Values" in Oracle WebLogic Scripting Tool.)
When the item is an operation, the third column uses the following pattern to display the operation's return type and input parameters: returnType: parameterType(parameterName)
Table 3-9 ls Command Output Information
| Code | Description |
|---|---|
|
|
Indicates that the item is a child management object. Like a directory in a UNIX or Windows file system, you can use the |
|
|
Indicates that the item is a child management object or an attribute that is readable, assuming that current user has been given read permission by the security realm's policies. (See "Default Security Policies for MBeans" in the Oracle WebLogic Server MBean Reference.) |
|
|
Indicates that the item is an attribute that is writable, assuming that current user has been given write permission by the security realm's policies. (See "Default Security Policies for MBeans" in the Oracle WebLogic Server MBean Reference.) |
|
|
Indicates that the item is an operation that can be executed, assuming that current user has been given execute permission by the security realm's policies. (See "Default Security Policies for MBeans" in the Oracle WebLogic Server MBean Reference.) |
By default, the output lists all attributes, operations, and child management objects of the current management object. To filter the output or to see a list for a different management object, you can specify a command argument.
Note:
As a performance optimization, when using WLST offline, WebLogic Server does not store most of its default values in the configuration files for the WebLogic domain. In some cases, this optimization prevents entire management objects from being displayed by WLST offline (because WebLogic Server has never written the corresponding XML elements to the domain configuration files). For example, if you never modify the default logging severity level for a WebLogic domain while the domain is active, WLST offline will not display the Log management object for the domain.
If you want to change the default value of attributes whose management object is not displayed by WLST offline, you must first use the create command to create the management object. Then you can cd to the management object and change the attribute value. See create.
ls( [ a | c | o ] [ moPath ]) ls( [ moPath ] returnMap [ returnType ] )
| Argument | Definition |
|---|---|
a |
Optional. Displays only the attributes of the specified management object (suppresses the display of other items). |
c |
Optional. Displays only the child management objects of the specified management object (suppresses the display of other items). |
o |
Optional. Displays only the operations that can be invoked on the specified management object (suppresses the display of other items). This argument is only applicable for WLST online. |
moPath
|
Optional. Path name to the management object for which you want to list attributes, operations, and child management objects. You can specify a pathname that is relative to your current location in the hierarchy or an absolute pathname. With WLST offline, use the forward-slash character ( With WLST online, you can list the contents of MBeans in any management hierarchy (see Tree Commands). Use the following syntax to specify the root of a hierarchy:
For example, to list the root of the server runtime hierarchy:
If you do not specify this argument, the command lists items for the current management object. |
returnMap
|
Optional. Boolean value that determines whether the command returns values as a map. This argument defaults to |
returnType
|
Optional. Controls the output returned in the map. Specify This argument is valid only if |
The following example displays all the child configuration beans, and attribute names and values for the examples domain, which has been loaded into memory, in WLST offline mode:
wls:/offline/mydomain > ls()
dr-- AppDeployments
dr-- BridgeDestinations
dr-- Clusters
dr-- CustomResources
dr-- DeploymentConfiguration
dr-- Deployments
dr-- EmbeddedLDAP
dr-- ErrorHandlings
dr-- FileStores
dr-- InternalAppDeployments
dr-- InternalLibraries
dr-- JDBCDataSourceFactories
dr-- JDBCStores
dr-- JDBCSystemResources
dr-- JMSBridgeDestinations
dr-- JMSInteropModules
dr-- JMSServers
dr-- JMSSystemResources
dr-- JMX
...
wls:/offline/examples>
The following example displays all the attribute names and values in DomainMBean:
wls:/mydomain/serverConfig> ls('a')
-r-- AdminServerName AdminServer
-r-- AdministrationMBeanAuditingEnabled false
-r-- AdministrationPort 9002
-r-- AdministrationPortEnabled false
-r-- AdministrationProtocol t3s
-r-- ArchiveConfigurationCount 0
-r-- ClusterConstraintsEnabled false
-r-- ConfigBackupEnabled false
-r-- ConfigurationAuditType none
-r-- ConfigurationVersion 9.0.0.0
-r-- ConsoleContextPath console
-r-- ConsoleEnabled true
-r-- ConsoleExtensionDirectory console-ext
-r-- DomainVersion 9.0.0.0
-r-- LastModificationTime 0
-r-- Name basicWLSDomain
-r-- Notes null
-r-- Parent null
-r-- ProductionModeEnabled false
-r-- RootDirectory .
-r-- Type Domain
wls:/mydomain/serverConfig>
The following example displays all the child beans and attribute names and values in Servers MBean:
wls:/mydomain/serverConfig> ls('Servers')
dr-- AdminServer
The following example displays the attribute names and values for the specified MBean path and returns the information in a map:
wls:/mydomain/serverConfig> svrAttrList = ls('edit:/Servers/myserver', 'true', 'a')
-rw- AcceptBacklog 50
-rw- AdminReconnectIntervalSeconds 10
-rw- AdministrationPort 9002
-rw- AdministrationProtocol t3s
-rw- AutoKillIfFailed false
-rw- AutoMigrationEnabled false
-rw- AutoRestart true
-rw- COMEnabled false
-rw- ClasspathServletDisabled false
-rw- ClientCertProxyEnabled false
-rw- Cluster null
-rw- ClusterRuntime null
-rw- ClusterWeight 100
wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online
Displays help from MBeanInfo for the current MBean or its specified attribute. In the event of an error, the command returns a WLSTException.
man([attrName])
| Argument | Definition |
|---|---|
attrName
|
Optional. MBean attribute name for which you would like to display help. If not specified, WLST displays helps for the current MBean. |
The following example displays help from MBeanInfo for the ServerMBean bean.
wls:/mydomain/serverConfig> man('Servers')
dynamic : true
creator : createServer
destroyer : destroyServer
description : <p>Returns the ServerMBeans representing the servers that have been
configured to be part of this domain.</p>
descriptorType : Attribute
Name : Servers
interfaceClassName : [Lweblogic.management.configuration.ServerMBean;
displayName : Servers
relationship : containment
Command Category: Information Commands
Use with WLST: Online
Redirects WLST information, error, and debug messages to the specified filename. Also redirects the output of the dumpStack() and dumpVariables() commands to the specified filename.
In the event of an error, the command returns a WLSTException.
redirect(outputFile, [toStdOut])
| Argument | Definition |
|---|---|
outputFile
|
Name of the file to which you want to record the WLST commands. The filename can be absolute or relative to the directory from which you started WLST. |
toStdOut
|
Optional. Boolean value specifying whether the output should be sent to |
Command Category: Information Commands
Use with WLST: Online
Removes a listener that was previously defined. If you do not specify an argument, WLST removes all listeners defined for all MBeans. For information about setting a listener, see addListener.
In the event of an error, the command returns a WLSTException.
removeListener([mbean], [listenerName])
| Argument | Definition |
|---|---|
mbean
|
Optional. Name of the MBean or MBean object for which you want to remove the previously defined listeners. |
listenerName
|
Optional. Name of the listener to be removed. |
Command Category: Information Commands
Use with WLST: Online
Shows all listeners that are currently defined. For information about setting a listener, see addListener.
In the event of an error, the command returns a WLSTException.
Command Category: Information Commands
Use with WLST: Online or Offline
Records all user interactions with WLST. This command is useful for capturing commands for replay.
In the event of an error, the command returns a WLSTException.
This command cannot be used when you are importing WLST as a Jython module, as described in "Importing WLST as a Jython Module" in Oracle WebLogic Scripting Tool.
startRecording(recordFile, [recordAll])
| Argument | Definition |
|---|---|
recordFile
|
Name of the file to which you want to record the WLST commands. The filename can be absolute or relative to the directory from which you invoked WLST. |
recordAll
|
Optional. Boolean value specifying whether to capture all user interactions in the file. This argument defaults to |
Command Category: Information Commands
Use with WLST: Online
Using Node Manager, returns a map of servers or clusters and their state. Node Manager must be running.
For more information about server states, see "Understanding Server Life Cycle" in Managing Server Startup and Shutdown for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
state(name, [type])
| Argument | Definition |
|---|---|
name
|
Name of the server or cluster for which you want to retrieve the current state. |
type
|
Optional. Type, |
The following example returns the state of the Managed Server, managed1.
wls:/mydomain/serverConfig> state('managed1','Server')
Current state of "managed1": SUSPENDED
wls:/mydomain/serverConfig>
The following example returns the state of the cluster, mycluster.
wls:/mydomain/serverConfig> state('mycluster','Cluster')
There are 3 server(s) in cluster: mycluster
States of the servers are
MServer1---SHUTDOWN
MServer2---SHUTDOWN
MServer3---SHUTDOWN
wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online or Offline
Stops recording WLST commands. For information about starting a recording, see startRecording.
In the event of an error, the command returns a WLSTException.
Command Category: Information Commands
Use with WLST: Online or Offline
Stops the redirection of WLST output to a file, if redirection is in progress.
In the event of an error, the command returns a WLSTException.
Command Category: Information Commands
Use with WLST: Online
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.
Only the key file that originally encrypted the username and password can be used to decrypt the values. If you lose the key file, you must create a new user configuration and key file pair.
In the event of an error, the command returns a WLSTException.
storeUserConfig([userConfigFile], [userKeyFile], [nm])
| Argument | Definition |
|---|---|
userConfigFile
|
Optional. Name of the file to store the user configuration. The pathname can be absolute or relative to the file-system directory from which you started WLST. If you do not specify this argument, the command stores the file in your home directory as determined by your JVM. The location of the home directory depends on the SDK and type of operating system on which WLST is running.The default filename is based on the following pattern:
where The command also prints to standard out the location in which it created the file. |
userKeyFile
|
Optional. Name of the file to store the key information that is associated with the user configuration file that you specify. The pathname can be absolute or relative to the file-system directory from which you started WLST. If you do not specify this argument, the command stores the file in your home directory as determined by your JVM. The location of the home directory depends on the SDK and type of operating system on which WLST is running. The default filename is based on the following pattern:
where The command also prints to standard out the location in which it created the file. |
nm
|
Optional. Boolean value specifying whether to store the username and password for Node Manager or WebLogic Server. If set to true, the Node Manager username and password is stored. This argument default to |
The following example creates and stores a user configuration file and key file in the default location.
wls:/mydomain/serverConfig> storeUserConfig() Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Do you want to create the key file? y or n y The username and password that were used for this current WLS connection are stored in C:\Documents and Settings\pat\pat-WebLogicConfig.properties and C:\Documents and Settings\pat\pat-WebLogicKey.properties.
The following example creates and stores a user configuration file and key file in the specified locations.
wls:/mydomain/serverConfig> storeUserConfig('c:/myFiles/myuserconfigfile.secure', 'c:/myFiles/myuserkeyfile.secure') Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Do you want to create the key file? y or n y The username and password that were used for this current WLS connection are stored in c:/myFiles/mysuserconfigfile.secure and c:/myFiles/myuserkeyfile.secure wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online or Offline
Displays a thread dump for the specified server. In the event of an error, the command returns a WLSTException.
threadDump([writeToFile], [fileName], [serverName])
| Argument | Definition |
|---|---|
writeToFile
|
Optional. Boolean value specifying whether to save the output to a file. This argument defaults to |
fileName
|
Optional. Name of the file to which the output is written. The filename can be absolute or relative to the directory where WLST is running. This argument defaults to |
serverName
|
Optional. Server name for which the thread dump is requested. This argument defaults to the server to which WLST is connected. If you are connected to an Administration Server, you can display a thread dump for the Administration Server and any Managed Server that is running in the WebLogic domain. If you are connected to a Managed Server, you can only display a thread dump for that Managed Server. |
The following example displays the thread dump for the current server and saves the output to the Thread_Dump_serverName file.
wls:/mydomain/serverConfig> threadDump()
The following example displays the thread dump for the server managedServer. The information is not saved to a file.
wls:/mydomain/serverConfig> threadDump(writeToFile='false', serverName='managedServer')
Command Category: Information Commands
Use with WLST: Online
Displays information about an MBean, such as the attribute names and values, and operations. In the event of an error, the command returns a WLSTException.
The following example displays information about the current MBean, cmo.
wls:/mydomain/serverConfig> cmo.getType() 'Domain' wls:/mydomain/serverConfig> viewMBean(cmo) Attribute Names and Values -------------------------- XMLEntityCaches null Targets javax.management.ObjectName[com.bea :Name=MedRecJMSServer,Type=JMSServer, com.bea:Name=WSStoreForwardInternalJMSServerMedRecServer,Type=JMSServer, com.bea:Name=MedRecWseeJMSServer,Type=JMSServer, com.bea:Name=PhysWSEEJMSServer,Type=JMSServer, com.bea:Name=MedRecSAFAgent,Type=SAFAgent, com.bea:Name=AdminServer,Type=Server] RootDirectory . EmbeddedLDAP com.bea:Name=OOTB_medrec,Type=EmbeddedLDAP RemoteSAFContexts null Libraries javax.management.ObjectName[com.bea ... wls:/mydomain/serverConfig>
Command Category: Information Commands
Use with WLST: Online
Converts WLST definitions and method declarations to a Python (.py) file to enable advanced users to import them as a Jython module. After importing, the definitions and method declarations are available to other Jython modules and can be accessed directly using Jython syntax. For more information, see "Importing WLST as a Jython Module" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
writeIniFile(filePath)
| Argument | Definition |
|---|---|
filePath
|
Full pathname to the file that you want to save the converted information. |
Use the WLST life cycle commands, listed in Table 3-10, to manage the life cycle of a server instance.
For more information about the life cycle of a server instance, see "Understanding Server Life Cycle" in Managing Server Startup and Shutdown for Oracle WebLogic Server.
Table 3-10 Life Cycle Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Migrate services to a target server within a cluster. |
Online |
|
|
Resume a server instance that is suspended or in |
Online |
|
|
Gracefully shut down a running server instance or cluster. |
Online |
|
|
Start a Managed Server instance or a cluster using Node Manager. |
Online |
|
|
Start the Administration Server. |
Online or Offline |
|
|
Suspend a running server. |
Online |
Command Category: Life Cycle Commands
Use with WLST: Online
Migrates the specified services (JTA, JMS, or Server) to a targeted server within a cluster. In the event of an error, the command returns a WLSTException.
For information about migrating services, see "Service Migration" in Using Clusters for Oracle WebLogic Server.
migrate(sname, destinationName, [sourceDown], [destinationDown], [migrationType])
| Argument | Definition |
|---|---|
sname
|
Name of the server from which the services should be migrated. |
destinationName
|
Name of the machine or server to which you want to migrate the services. |
sourceDown
|
Optional. Boolean value specifying whether the source server is down. This argument defaults to When migrating JTA services, the |
destinationDown
|
Optional. Boolean value specifying whether the destination server is down. This argument defaults to If the destination is not running, and you do not set this argument to When migrating JMS-related services to a non-running server instance, the server instance will activate the JMS services upon the next startup. When migrating the JTA Transaction Recovery Service to a non-running server instance, the target server instance will assume recovery services when it is started. |
migrationType
|
Optional. Type of service(s) that you want to migrate. Valid values include:
This argument defaults to |
The following example migrates all JMS and JTA services on server1 to the server server2. The boolean arguments specify that the source server is down and the destination server is running.
wls:/mydomain/edit !> migrate('server1','server2', 'true', 'false', 'all')
Migrating all JMS and JTA services from 'server1' to destination 'server2' ...
wls:/mydomain/edit !>
The following example migrates all Server services on server1 to the server server2. The boolean arguments specify that the source server is down and the destination server is running.
wls:/mydomain/edit !> migrate('server1','server2', 'true', 'false', 'Server')
Migrating singleton server services from 'server1' to machine 'server2'...
wls:/mydomain/edit !>
Command Category: Life Cycle Commands
Use with WLST: Online
Resumes a server instance that is suspended or in ADMIN state. This command moves a server to the RUNNING state. For more information about server states, see "Understanding Server Life Cycle" in Managing Server Startup and Shutdown for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
resume([sname], [block])
| Argument | Definition |
|---|---|
sname
|
Name of the server to resume. This argument defaults to the server to which WLST is currently connected. |
block
|
Optional. Boolean value specifying whether WLST should block user interaction until the server is resumed. This argument defaults to |
Command Category: Life Cycle Commands
Use with WLST: Online
Gracefully shuts down a running server instance or a cluster. The shutdown command waits for all the in-process work to be completed before shutting down the server or cluster.
You shut down a server to which WLST is connected by entering the shutdown command without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut down the Managed Server instance to which WLST is connected; you cannot shut down another server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed Server, Node Manager must be running.
In the event of an error, the command returns a WLSTException.
shutdown([name], [entityType], [ignoreSessions], [timeOut], [force], [block])
| Argument | Definition |
|---|---|
name
|
Optional. Name of the server or cluster to shutdown. This argument defaults to the server to which WLST is currently connected. |
entityType
|
Optional. Type, |
ignoreSessions
|
Optional. Boolean value specifying whether WLST should drop all HTTP sessions immediately or wait for HTTP sessions to complete or timeout while shutting down. This argument defaults to |
timeOut
|
Optional. Time (in seconds) that WLST waits for subsystems to complete in-process work and suspend themselves before shutting down the server. This argument defaults to 0 seconds, indicating that there is no timeout. |
force
|
Optional. Boolean value specifying whether WLST should terminate a server instance or a cluster without waiting for the active sessions to complete. This argument defaults to |
block
|
Optional. Boolean value specifying whether WLST should block user interaction until the server is shutdown. This argument defaults to |
The following example instructs WLST to shutdown the server to which you are connected:
wls:/mydomain/serverConfig> shutdown()
Shutting down the admin server that you are currently connected to .......
Disconnected from weblogic server: AdminServer
The following example instructs WLST to wait 1000 seconds for HTTP sessions to complete or timeout (at 1000 seconds) before shutting down myserver:
wls:/mydomain/serverConfig> shutdown('myserver','Server','false',1000, block='false')
The following example instructs WLST to drop all HTTP sessions immediately while connected to a Managed Server instance:
wls:/mydomain/serverConfig> shutdown('MServer1','Server','true',1200)
Shutting down a managed server that you are connected to ...
Disconnected from weblogic server: MServer1
The following example instructs WLST to shutdown the cluster mycluster:
wls:/mydomain/serverConfig> shutdown('mycluster','Cluster') Shutting down the cluster with name mycluster Shutdown of cluster mycluster has been issued, please refer to the logs to check if the cluster shutdown is successful. Use the state(<server-name>) or state(<cluster-name>,"Cluster") to check the status of the server or cluster wls:/mydomain/serverConfig> state('mycluster','Cluster') There are 3 server(s) in cluster: mycluster States of the servers are MServer1---SHUTDOWN MServer2---SHUTDOWN MServer3---SHUTDOWN wls:/mydomain/serverConfig>
Command Category: Life Cycle Commands
Use with WLST: Online
Starts a Managed Server instance or a cluster using Node Manager. WLST must be connected to the Administration Server and Node Manager must be running.
For more information about WLST commands used to connect to and use Node Manager, see Node Manager Commands.
In the event of an error, the command returns a WLSTException.
start(name, [type], [url], [block])
| Argument | Definition |
|---|---|
name
|
Name of the Managed Server or cluster to start. |
type
|
Optional. Type, |
url
|
Optional. Listen address and listen port of the server instance, specified using the following format: |
block
|
Optional. Boolean value specifying whether WLST should block user interaction until the server or cluster is started. This argument defaults to |
The following example instructs Node Manager to start a Managed Server instance; the listen address is localhost and listen port is 8801. WLST returns control to the user after issuing this command, as block is set to false.
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server myserver ...
Server with name myserver started successfully.
wls:/mydomain/serverConfig>
The following example instructs Node Manager to start a cluster. WLST block user interaction until the cluster is started, as block defaults to true.
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
......................................................................
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig>
Command Category: Life Cycle Commands
Use with WLST: Online or Offline
Starts the Administration Server. In the event of an error, the command returns a WLSTException.
Note:
You can use startServer only to start a WebLogic Administration Server, by running WLST from the WL_HOME/common/bin directory. You cannot use startServer to start an integrated WebLogic Administration Server (that is, an Administration Server for a Fusion Middleware Suite product installed in an ORACLE_HOME directory).
To start the Administration server for a Fusion Middleware Suite product other than WebLogic Server, use either of the following methods:
Execute the server startup script for the associated WebLogic domain.
Start the server using Node Manager. If you use this method, make sure that the startScriptEnabled property is set to true in Node Manager.
startServer([adminServerName], [domainName], [url], [username], [password], [domainDir], [block], [timeout], [serverLog], [systemProperties], [jvmArgs] [spaceAsJvmArgsDelimiter])
| Argument | Definition |
|---|---|
adminServerName
|
Optional. Name of the Administration Server to start. This argument defaults to |
domainName
|
Optional. Name of the WebLogic domain to which the Administration Server belongs. This argument defaults to |
url
|
Optional. URL of the Administration Server. The URL supplied with the startServer command will override the listen address and port specified in the |
username
|
Optional. Username use to connect WLST to the server. This argument defaults to |
password
|
Optional. Password used to connect WLST to the server. This argument defaults to |
domainDir
|
Optional. Domain directory in which the Administration Server is being started. This argument defaults to the directory from which you started WLST. |
block
|
Optional. Boolean value specifying whether WLST blocks user interaction until the server is started. When |
timeout
|
Optional. Time (in milliseconds) that WLST waits for the server to start before canceling the operation. The default value is 60000 milliseconds. This argument is only applicable when |
serverLog
|
Optional. Location of the server log file. This argument defaults to |
systemProperties
|
Optional. System properties to pass to the server process. System properties should be specified as comma-separated name-value pairs, and the name-value pairs should be separated by equals sign ( |
jvmArgs
|
Optional. JVM arguments to pass to the server process. Multiple arguments can be specified, separated by commas. |
spaceAsJvmArgsDelimiter
|
Optional. Boolean value specifying whether JVM arguments are space delimited. The default value is false. |
The following example starts the Administration Server named demoServer in the demoDomain.
wls:/offline> startServer('demoServer','demoDomain','t3://localhost:8001', 'myweblogic','wlstdomain','c:/mydomains/wlst','false', 60000, jvmArgs='-XX:MaxPermSize=75m, -Xmx512m, -XX:+UseParallelGC') wls:/offline>
Command Category: Life Cycle Commands
Use with WLST: Online
Suspends a running server. This command moves a server from the RUNNING state to the ADMIN state. For more information about server states, see "Understanding Server Life Cycle" in Managing Server Startup and Shutdown for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
suspend([sname], [ignoreSessions], [timeOut], [force], [block])
| Argument | Definition |
|---|---|
sname
|
Optional. Name of the server to suspend. The argument defaults to the server to which WLST is currently connected. |
ignoreSessions
|
Optional. Boolean value specifying whether WLST should drop all HTTP sessions immediately or wait for HTTP sessions to complete or time out while suspending. This argument defaults to |
timeOut
|
Optional. Time (in seconds) the WLST waits for the server to complete in-process work before suspending the server. This argument defaults to 0 seconds, indicating that there is no timeout. |
force
|
Optional. Boolean value specifying whether WLST should suspend the server without waiting for active sessions to complete. This argument defaults to |
block
|
Optional. Boolean value specifying whether WLST blocks user interaction until the server is started. This argument defaults to |
Use the WLST Node Managers commands, listed in Table 3-11, to start, shut down, restart, and monitor WebLogic Server instances.
Note:
Node Manager must be running before you can execute the commands within this category.
For more information about Node Manager, see "Using Node Manager" in the Node Manager Administrator's Guide for Oracle WebLogic Server.
Table 3-11 Node Manager Commands for WLST Configuration
| This command... | Enables you to... | Use with WLST... |
|---|---|---|
|
Determine whether WLST is connected to Node Manager. |
Online |
|
|
Connect WLST to Node Manager to establish a session. |
Online or Offline |
|
|
Disconnect WLST from a Node Manager session. |
Online or Offline |
|
|
Enables the Node Manager on the current computer to manage servers in a specified WebLogic domain. |
Online |
|
|
Generates the Node Manager property files, |
Online |
|
|
Kill the specified server instance that was started with Node Manager. |
Online or Offline |
|
|
Return the Node Manager log. |
Online or Offline |
|
|
Return the server output log of the server that was started with Node Manager. |
Online or Offline |
|
|
Return the status of the server that was started with Node Manager. |
Online or Offline |
|
|
Start a server in the current WebLogic domain using Node Manager. |
Online or Offline |
|
|
Return the Node Manager version. |
Online or Offline |
|
|
Starts Node Manager on the same computer that is running WLST. |
Online or Offline |
|
|
Stops Node Manager. |
Online or Offline |
Command Category: Node Manager Commands
Use with WLST: Online or Offline
Determines whether WLST is connected to Node Manager. Returns true or false and prints a descriptive message. Node Manager must be running before you can execute this command.
In the event of an error, the command returns a WLSTException.
The following example indicates that WLST is currently connected to Node Manager that is monitoring mydomain.
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig>
The following example indicates that WLST is not currently connected to Node Manager.
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
Command Category: Node Manager Commands
Use with WLST: Online or Offline
Connects WLST to Node Manager to establish a session. After connecting to Node Manager, you can invoke any Node Manager commands via WLST. Node Manager must be running before you can execute this command.
Note:
If you have previously used the connect command in the current WLST session, nmconnect uses the same user credentials as were used for the connect command, unless you specify otherwise.
Once connected, the WLST prompt displays as follows, where domainName indicates the name of the WebLogic domain that is being managed: wls:/nm/domainName>. If you then connect WLST to a WebLogic Server instance, the prompt is changed to reflect the WebLogic Server instance. You can use the nm command to determine whether WLST is connected to Node Manager, as described in nm.
In the event of an error, the command returns a WLSTException.
nmConnect([username, password], [host], [port], [domainName], [domainDir] [nmType], [verbose]) nmConnect([userConfigFile, userKeyFile], [host], [port], [domainName], [domainDir] [nmType], [verbose])
| Argument | Definition |
|---|---|
username
|
Username of the operator who is connecting WLST to Node Manager. The username defaults to Note: When running a server in production mode, you must specify the username and password explicitly on the command line to ensure that the appropriate username and password are used when connecting to Node Manager. |
password
|
Password of the operator who is connecting WLST to Node Manager. The password defaults to Note: When running a server in production mode, you must specify the username and password explicitly on the command line to ensure that the appropriate username and password are used when connecting to Node Manager. |
host
|
Optional. Host name of Node Manager. This argument defaults to |
port
|
Optional. Port number of Node Manager. This argument defaults to a value that is based on the Node Manager type, as follows:
|
domainName
|
Optional. Name of the WebLogic domain that you want to manage. This argument defaults to |
domainDir
|
Optional. Path of the domain directory to which you want to save the Node Manager secret file ( |
nmType
|
The Node Manager type. Valid values are:
This argument defaults to |
verbose
|
Optional. Boolean value specifying whether WLST connects to Node Manager in verbose mode. This argument defaults to |
userConfigFile
|
Optional. Name and location of a user configuration file which contains an encrypted username and password. When you create a user configuration file, the |
userKeyFile
|
Optional. Name and location of the key file that is associated with the specified user configuration file and is used to decrypt it. (See storeUserConfig.) |
The following example connects WLST to Node Manager to monitor the oamdomain domain using the default host and port numbers and plain Node Manager type.
wls:/myserver/serverConfig> nmConnect('weblogic', 'welcome1', 'localhost', '5555', 'oamdomain', 'c:/Oracle/Middleware/user_projects/domains/oamdomain','ssl') Connecting to Node Manager Server ... Successfully connected to Node Manager. wls:/nm/oamdomain>
The following example connects WLST to a Node Manager Server instance using a user configuration and key file to provide user credentials.
wls:/myserver/serverConfig> nmConnect(userConfigFile=' c:/myfiles/myuserconfigfile.secure', userKeyFile='c:/myfiles/myuserkeyfile.secure', host='172.18.137.82', port=26106, domainName='mydomain', domainDir='c:/myfiles/mydomain', mType='ssl') Connecting to Node Manager Server ... Successfully connected to Node Manager. wls:/nm/mydomain>
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Disconnects WLST from a Node Manager session.
In the event of an error, the command returns a WLSTException.
Command Category: Node Manager Commands
Use with WLST: Online
Enrolls the machine on which WLST is currently running. WLST must be connected to an Administration Server to run this command; WLST does not need to be connected to Node Manager.
This command downloads the following files from the Administration Server:
Node Manager secret file (nm_password.properties), which contains the encrypted username and password that is used for server authentication
SerializedSystemIni.dat file
This command also updates the nodemanager.domains file under the WL_HOME/common/nodemanager directory with the domain information, where WL_HOME refers to the top-level installation directory for WebLogic Server.
You must run this command once per WebLogic domain per machine unless that domain shares the root directory of the Administration Server.
If the machine is already enrolled when you run this command, the Node Manager secret file (nm_password.properties) is refreshed with the latest information from the Administration Server.
In the event of an error, the command returns a WLSTException.
nmEnroll([domainDir], [nmHome])
| Argument | Definition |
|---|---|
domainDir
|
Optional. Path of the domain directory to which you want to save the Node Manager secret file ( |
nmHome
|
Optional. Path to the Node Manager home. The |
The following example enrolls the current machine with Node Manager and saves the Node Manager secret file (nm_password properties) and SerializedSystemIni.dat file to c:/Oracle/Middleware/mydomain/common/nodemanager/nm_password.properties. The nodemanager.domains file is written to WL_HOME/common/nodemanager by default.
wls:/mydomain/serverConfig> nmEnroll('c:/Oracle/Middleware/mydomain/common/nodemanager')
Enrolling this machine with the domain directory at c:\Oracle\Middleware\mydomain\common\nodemanager....
Successfully enrolled this machine with the domain directory at C:\Oracle\Middleware\mydomain\common\nodemanager
wls:/mydomain/serverConfig>
Command Category: Node Manager Commands
Use with WLST: Online
Generates the Node Manager property files, boot.properties and startup.properties, for the specified server. The Node Manager property files are stored relative to the root directory of the specified server. The target root directory must be on the same machine on which you are running the command.
You must specify the name of a server; otherwise, the command will fail.
In the event of an error, the command returns a WLSTException.
nmGenBootStartupProps(serverName)
| Argument | Definition |
|---|---|
serverName
|
Name of the server for which Node Manager property files are generated. |
The following example generates boot.properties and startup.properties in the root directory of the specified server, ms1.
wls:/mydomain/serverConfig> nmGenBootStartupProps('ms1')
Successfully generated boot.properties at
c:\Oracle\Middleware\mydomain\servers\ms1\data\nodemanager\boot.properties
Successfully generated startup.properties at
c:\Oracle\Middleware\mydomain\servers\ms1\data\nodemanager\startup.properties
wls:/mydomain/serverConfig>
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Kills the specified server instance that was started with Node Manager.
If you do not specify a server name using the serverName argument, the argument defaults to myServer, which must match your server name or the command will fail.
If you attempt to kill a server instance that was not started using Node Manager, the command displays an error.
In the event of an error, the command returns a WLSTException.
nmKill([serverName], [serverType])
| Argument | Definition |
|---|---|
serverName
|
Optional. Name of the server to be killed. This argument defaults to |
serverType
|
Optional. The type of server to start. This argument defaults to WebLogic. Another valid option is Coherence. |
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Returns the Node Manager log.
In the event of an error, the command returns a WLSTException.
nmLog([writer])
| Argument | Definition |
|---|---|
writer
|
Optional. |
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Returns the server output log of the server that was started with Node Manager.
In the event of an error, the command returns a WLSTException.
nmServerLog([serverName], [writer], [serverType])
| Argument | Definition |
|---|---|
serverName
|
Optional. Name of the server for which you want to display the server output log. This argument defaults to |
writer |
Optional. |
serverType
|
Optional. The type of server to start. This argument defaults to WebLogic. Another valid option is Coherence. |
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Returns the status of the server that was started with Node Manager.
In the event of an error, the command returns a WLSTException.
nmServerStatus([serverName], [serverType])
| Argument | Definition |
|---|---|
serverName
|
Optional. Name of the server for which you want to display the status. This argument defaults to |
serverType
|
Optional. The type of server to start. This argument defaults to WebLogic. Another valid option is Coherence. |
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Starts a server in the current WebLogic domain using Node Manager.
In the event of an error, the command returns a WLSTException.
Note:
boot.properties must exist in order to start a server with nmStart. If this is the first time you are starting a server, you must manually create it in order to use nmStart.
Alternatively, you can use the nmStartprops argument to provide user credentials (after connecting to Node Manager):
prps = makePropertiesObject("username=weblogic, password=welcome1")
nmStart("AdminServer",props=prps)
nmStart([serverName], [domainDir], [props], [writer], [serverType])
| Argument | Definition |
|---|---|
serverName
|
Optional. Name of the server to be started. |
domainDir
|
Optional. Domain directory of the server to be started. This argument defaults to the directory from which you started WLST. |
props
|
Optional. System properties to apply to the new server. |
writer
|
Optional. |
serverType
|
Optional. The type of server to start. This argument defaults to WebLogic. Another valid option is Coherence. |
The following example starts the managed1 server in the current WebLogic domain using Node Manager.
wls:/nm/mydomain> nmStart("managed1")
Starting server managed1 ...
Server managed1 started successfully
wls:/nm/mydomain>
The following example starts the Administration Server in the specified WebLogic domain using Node Manager. In this example, the prps variable stores the system property settings and is passed to the command using the props argument.
wls:/nm/mydomain> prps = makePropertiesObject("weblogic.ListenPort=8001") wls:/nm/mydomain> nmStart("AdminServer",props=prps) Starting server AdminServer... Server AdminServer started successfully wls:/nm/mydomain>
Command Category: Node Manager Commands
Use with WLST: Online or Offline
WLST must be connected to Node Manager to run this command.
Returns the Node Manager version.
In the event of an error, the command returns a WLSTException.
Command Category: Node Manager Commands
Use with WLST: Online or Offline
Starts Node Manager on the same computer that is running WLST.
Notes:
The WebLogic Server custom installation process optionally installs and starts Node Manager as a Windows service on Windows systems. For more information, see "About Installing Node Manager as a Windows Service" in the Installation Guide for Oracle WebLogic Server. In this case, you do not need to start the Node Manager manually.
In production environments, Oracle recommends that you do not use the startNodeManager command to start Node Manager. The recommended approach is to install Node Manager as a service or daemon, or to use the startNodeManager script (startNodeManager.sh or startNodeManger.cmd).
If Node Manager is already running when you invoke the startNodeManager command, the following message is displayed:
A Node Manager has already been started. Cannot start another Node Manager process via WLST
In the event of an error, the command returns a WLSTException.
startNodeManager([verbose], [nmProperties])
| Argument | Definition |
|---|---|
verbose
|
Optional. Boolean value specifying whether WLST starts Node Manager in verbose mode. This argument defaults to |
nmProperties
|
Optional. Comma-separated list of Node Manager properties, specified as name-value pairs. Node Manager properties include, but are not limited to, the following: |
The following example displays the Node Manager server version.
wls:/mydomain/serverConfig> startNodeManager(verbose='true', NodeManagerHome='c:/Oracle/Middleware/wlserver_10.3/common/nodemanager', ListenPort='6666', ListenAddress='myhost')) Launching Node Manager ... Successfully launched the Node Manager. The Node Manager process is running independent of the WLST process Exiting WLST will not stop the Node Manager process. Please refer to the Node Manager logs for more information. The Node Manager logs will be under c:\Oracle\Middleware\wlserver_10.3\common\nodemanager. wls:/mydomain/serverConfig>
Command Category: Node Manager Commands
Use with WLST: Online or Offline
Stops the Node Manager process.
Note:
In order to stop the Node Manager process, you must have either started Node Manager with startNodeManager, or Node Manager must have been started with the property QuitEnabled=true. You can configure this property in $WLS_HOME/common/nodemanager.properties. This allows you to connect to the Node Manager to shut it down.
If the Node Manager is not running when you invoke the stopNodeManager command, the following message is displayed:
Cannot stop the Node Manager unless you are connected to it.
Use the WLST tree commands, listed in Table 3-12, to navigate among MBean hierarchies.
Table 3-12 Tree Commands for WLST Configuration
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Navigate to the root of custom MBeans that are registered in the server. |
Online |
|
|
Navigate to the last MBean to which you navigated in the domain configuration hierarchy or to the root of the hierarchy, |
Online |
|
|
Navigate to the root of custom MBeans that are registered in the Domain Runtime MBean Server |
Online |
|
|
Navigate to the last MBean to which you navigated in the domain runtime hierarchy or to the root of the hierarchy, |
Online |
|
|
Navigate to the last MBean to which you navigated in the edit configuration MBean hierarchy or to the root of the hierarchy, |
Online |
|
|
Navigates to the JNDI tree for the server to which WLST is currently connected. |
Online |
|
|
Navigate to the last MBean to which you navigated in the configuration MBean hierarchy or to the root of the hierarchy, |
Online |
|
|
Navigate to the last MBean to which you navigated in the runtime MBean hierarchy or to the root of the hierarchy, |
Online |
Command Category: Tree Commands
Use with WLST: Online
Navigates to the root of custom MBeans that are registered in the Runtime MBean Server. WLST navigates, interrogates, and edits custom MBeans as it does domain MBeans; however, custom MBeans cannot use the cmo variable because a stub is not available.
Note:
When navigating to the custom tree, WLST queries all MBeans in the compatibility MBean server, the runtime MBean server, and potentially the JVM platform MBean server to locate the custom MBeans. Depending on the number of MBeans in the current WebLogic domain, this process make take a few minutes, and WLST may not return a prompt right away.
The custom command is available when WLST is connected to an Administration Server instance or a Managed Server instance. When connected to a WebLogic Integration or WebLogic Portal server, WLST can interact with all the WebLogic Integration or WebLogic Portal server MBeans.
For more information about custom MBeans, see Developing Custom Management Utilities With JMX for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
Note:
You can also navigate to custom MBeans on the Domain Runtime MBean Server using the domainCustom() command. See domainCustom, for more information.
The following example navigates from the configuration MBean hierarchy to the custom MBean hierarchy on a Administration Server instance.
wls:/mydomain/serverConfig> custom()
Location changed to custom tree. This is a writeable tree with No root. For more help, use help('custom')
wls:/mydomain/custom>
Command Category: Tree Commands
Use with WLST: Online
Navigates to the last MBean to which you navigated in the domain Configuration hierarchy or to the root of the hierarchy, DomainMBean. This read-only hierarchy stores the configuration MBeans that represent your current WebLogic domain.
In the event of an error, the command returns a WLSTException.
The following example navigates from the configuration MBean hierarchy to the WebLogic domain Configuration hierarchy on an Administration Server instance.
wls:/mydomain/serverConfig> domainConfig() Location changed to domainConfig tree. This is a read-only tree with DomainMBean as the root. For more help, use help('domainConfig') wls:/mydomain/domainConfig> ls() dr-- AppDeployments dr-- BridgeDestinations dr-- Clusters dr-- CustomResources dr-- DeploymentConfiguration dr-- Deployments dr-- EmbeddedLDAP dr-- ErrorHandlings dr-- FileStores dr-- InternalAppDeployments dr-- InternalLibraries dr-- JDBCDataSourceFactories dr-- JDBCStores dr-- JDBCSystemResources dr-- JMSBridgeDestinations dr-- JMSInteropModules dr-- JMSServers dr-- JMSSystemResources ... wls:/mydomain/domainConfig>
Command Category: Tree Commands
Use with WLST: Online
Navigates to the domain custom tree of custom MBeans that are registered in the Domain Runtime MBean Server. WLST navigates, interrogates, and edits domain custom MBeans as it does domain MBeans; however, domain custom MBeans cannot use the cmo variable because a stub is not available.
Note:
When navigating to the domainCustom tree, WLST queries all MBeans in the Domain Runtime MBean Server, the Runtime MBean Servers on each server, and potentially the JVM platform MBean server to locate the custom MBeans. Depending on the number of MBeans in the current WebLogic domain, this process make take a few minutes, and WLST may not return a prompt right away. It is recommended that a JMX query Object Name Pattern be specified to limit the amount of searching performed.
The domainCustom command is available only when WLST is connected to an Administration Server instance.
For more information about the Domain Runtime MBean Server, see "Understanding WebLogic Server MBeans" in Developing Custom Management Utilities With JMX for Oracle WebLogic Server.
In the event of an error, the command returns a WLSTException.
domainCustom(ObjectNamePattern)
| Argument | Definition |
|---|---|
ObjectNamePattern
|
A JMX query pattern, such as |
The following example navigates from the configuration MBean hierarchy to the domain custom MBean hierarchy on an Administration Server instance:
wls:/mydomain/serverConfig> domainCustom()
Location changed to domain custom tree. This is a writeable tree with No root. For more help, use help('domainCustom').
wls:/mydomain/domainCustom
Command Category: Tree Commands
Use with WLST: Online
Navigates to the last MBean to which you navigated in the domain Runtime hierarchy or to the root of the hierarchy, DomainRuntimeMBean. This read-only hierarchy stores the runtime MBeans that represent your current WebLogic domain.
In the event of an error, the command returns a WLSTException.
The following example navigates from the configuration MBean hierarchy to the domain Runtime hierarchy on an Administration Server instance.
wls:/mydomain/serverConfig> domainRuntime() wls:/mydomain/domainRuntime> ls() dr-- AppRuntimeStateRuntime dr-- DeployerRuntime dr-- DomainServices dr-- LogRuntime dr-- MessageDrivenControlEJBRuntime dr-- MigratableServiceCoordinatorRuntime dr-- MigrationDataRuntimes dr-- SNMPAgentRuntime dr-- ServerLifeCycleRuntimes dr-- ServerRuntimes dr-- ServerServices -r-- ActivationTime Mon Aug 01 11:41:25 EDT 2005 -r-- Clusters null -r-- MigrationDataRuntimes null -r-- Name sampleMedRecDomain -rw- Parent null -r-- SNMPAgentRuntime null -r-- Type DomainRuntime -r-x restartSystemResource Void : WebLogicMBean(weblogic.management.configuration.SystemResourceMBean) wls:/mydomain/domainRuntime>
Command Category: Tree Commands
Use with WLST: Online
Navigates to the last MBean to which you navigated in the edit configuration MBean hierarchy or to the root of the hierarchy, DomainMBean. This writable hierarchy stores all of the configuration MBeans that represent your current WebLogic domain.
Note:
To edit configuration beans, you must be connected to an Administration Server. If you connect to a Managed Server, WLST functionality is limited to browsing the configuration bean hierarchy. While you cannot use WLST to change the values of MBeans on Managed Servers, it is possible to use the Management APIs to do so. Oracle recommends that you change only the values of configuration MBeans on the Administration Server. Changing the values of MBeans on Managed Servers can lead to an inconsistent domain configuration.
For more information about editing configuration beans, see "Using WLST Online to Update an Existing Domain" in Oracle WebLogic Scripting Tool.
In the event of an error, the command returns a WLSTException.
The following example illustrates how to navigate from the server configuration MBean hierarchy to the editable copy of the domain configuration MBean hierarchy, in an Administration Server instance.
wls:/myserver/serverConfig> edit() Location changed to edit tree. This is a writeable tree with DomainMBean as the root. For more help, use help('edit') wls:/myserver/edit !> ls() dr-- AppDeployments dr-- BridgeDestinations dr-- Clusters dr-- DeploymentConfiguration dr-- Deployments dr-- EmbeddedLDAP ... wls:/myserver/edit !>
Command Category: Tree Commands
Use with WLST: Online
Navigates to the JNDI tree for the server to which WLST is currently connected. This read-only tree holds all the elements that are currently bound in JNDI.
In the event of an error, the command returns a WLSTException.
The following example navigates from the runtime MBean hierarchy to the Domain JNDI tree on an Administration Server instance.
wls:/myserver/runtime> jndi()
Location changed to jndi tree. This is a read-only tree with No root. For more help, use help('jndi')
wls:/myserver/jndi> ls()
dr-- ejb
dr-- javax
dr-- jms
dr-- weblogic
...
Command Category: Tree Commands
Use with WLST: Online
Navigates to the last MBean to which you navigated in the configuration MBean hierarchy or to the root of the hierarchy, DomainMBean.
This read-only hierarchy stores the configuration MBeans that represent the server to which WLST is currently connected. The MBean attribute values include any command-line overrides that a user specified while starting the server.
In the event of an error, the command returns a WLSTException.
For more information, see "Navigating Among MBean Hierarchies" in Oracle WebLogic Scripting Tool.
Command Category: Tree Commands
Use with WLST: Online
Navigates to the last MBean to which you navigated in the runtime MBean hierarchy or to the root of the hierarchy, ServerRuntimeMBean. This read-only hierarchy stores the runtime MBeans that represent the server to which WLST is currently connected.
In the event of an error, the command returns a WLSTException.
The following example navigates from the configuration MBean hierarchy to the runtime MBean hierarchy on an Administration Server instance.
wls:/mydomain/serverConfig> serverRuntime()
Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help('serverRuntime')
wls:/mydomain/serverRuntime>
Table 3-13 describes WLST variables and their common usage. All variables are initialized to default values at the start of a user session and are changed according to the user interaction with WLST.
| Variable | Description | Example |
|---|---|---|
cmgr |
The |
wls:/mydomain/edit> cmgr.getCurrentEditor()
'weblogic'
|
cmo |
Current Management Object. The WLST sets the variable to the current WLST path. For example, when you change to the serverConfig hierarchy, The variable is available in all WLST hierarchies except custom and jndi. |
wls:/mydomain/edit> cmo.setAdministrationPort(9092)
|
connected |
Boolean value specifying whether WLST is connected to a running server. WLST sets this variable to |
wls:/mydomain/serverConfig> print connected
false
|
domainName |
Name of the WebLogic domain to which WLST is connected. |
wls:/mydomain/serverConfig> print domainName
mydomain
|
domainRuntimeService |
|
wls:/mydomain/serverConfig> domainService.getServerName()
'myserver'
|
editService |
|
wls:/mydomain/edit> dc = editService.getDomainConfiguration()
|
exitonerror |
Boolean value specifying whether WLST terminates script execution when it encounters an exception. This variable defaults to |
wls:/mydomain/serverConfig> print exitonerror
true
|
home |
Represents the local MBeanHome. |
wls:/mydomain/serverConfig> print home weblogic.rmi.internal.BasicRemoteRef - hostID: '-hostID:[7001,7001,-1,-1,-1,-1,-1]:mydomain:AdminServer', oid: '260', channel: 'null' |
isAdminServer |
Boolean value specifying whether WLST is connected to a WebLogic Administration Server instance. WLST sets this variable to |
wls:/mydomain/serverConfig> print isAdminServer
true
|
mbs |
|
wls:/mydomain/serverConfig> mbs.isRegistered(ObjectName('mydomain: Name=mydomain,Type=Domain')) |
recording |
Boolean value specifying whether WLST is recording commands. WLST sets this variable to |
wls:/mydomain/serverConfig> print recording
true
|
runtimeService |
|
wls:/mydomain/serverConfig> sr=runtimeService.getServerRuntime()
|
serverName |
Name of the server to which WLST is connected. |
wls:/mydomain/serverConfig> print serverName
myserver
|
typeService |
|
wls:/mydomain/serverConfig> mi=typeService.getMBeanInfo('weblogic. management.configuration.ServerMBean') |
username |
Name of user currently connected to WLST. |
wls:/mydomain/serverConfig> print username
weblogic
|
version |
Current version of the running server to which WLST is connected. |
wls:/mydomain/serverConfig> print version
WebLogic Server 9.0 Thu Aug 31 12:15:50 PST 2005 778899
|