FAQs: WLST

WLST online is supported on WebLogic Server 10.0, 9.x, 8.1, and 7.0. WLST offline is supported on WebLogic Server 10.0, 9.x and 8.1 SP5.

What is the relationship between WLST and the existing WebLogic Server command-line utilities, such as wlconfig and weblogic.Deployer?

WLST functionality includes the capabilities of the following WebLogic Server command-line utilities:

weblogic.Admin utility that you use to interrogate MBeans and configure a WebLogic Server instance (deprecated in this release of WebLogic Server)
wlconfig Ant task tool for making WebLogic Server configuration changes (see “ Using Ant Tasks to Configure and Use a WebLogic Server Domain” in Developing Applications with WebLogic Server)
weblogic.Deployer utility for deploying applications. (see “ Overview of Deployment Tools” in Deploying Applications to WebLogic Server)

When would I choose to use WLST over the other command-line utilities or the Administration Console?

You can create, configure, and manage domains using WLST, command-line utilities, and the Administration Console interchangeably. The method that you choose depends on whether you prefer using a graphical or command-line interface, and whether you can automate your tasks by using a script.

You can use WLST online (connected to a running Administration Server or Managed Server instance) and offline (not connected to a running server).

WLST online is used when you are connected to a running server and provides simplified access to Managed Beans (MBeans), WebLogic Server Java objects that you manage through JMX. Online, WLST provides access to information that is persisted as part of the internal representation of the configuration.

WLST offline enables you to create a new domain or update an existing domain without connecting to a running WebLogic Server—supporting the same functionality as the Configuration Wizard. Offline, WLST only provides access to information that is persisted in the config directory.

The WLST scripting environment is based on the Java scripting interpreter, Jython 2.1.

Yes. WebLogic Server developers and administrators can extend the WebLogic scripting language to suit their environmental needs by following the Jython language syntax. For more information, see


http://www.jython.org

If I have SSL or the administration port enabled for my server, how do I connect using WLST?

If you will be 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

   java weblogic.WLST

Yes, using the exitonerror variable. Set this variable to true to specify that execution should exit when WLST encounters an error, or false to continue execution. This variable defaults to true. For more information, see WLST Variable Reference.

Why do I have to specify (and) after each command, and enclose arguments in single- or double-quotes?

Can I start a server, deploy applications, and then shut down the server using WLST?

Yes. You can connect to a Managed Server using the connect command. While connected to a Managed Server, you can view runtime data for the server and manage the security data that is in your Authentication provider’s data store (for example, you can add and remove users). You cannot modify the domain’s configuration. For more information, see connect.

Yes. You can use the loadProperties command to load your variables and values from a properties file. When you use the variables in your script, during execution, the variables are replaced with the actual values from the properties file. See loadProperties.

Does the configToScript command convert security MBeans in config.xml?

Yes, the security MBeans are converted. However, the information within the Embedded LDAP is not converted.

How can I access custom MBeans that are registered in the WebLogic MBeanServer?

Navigate to the custom tree using the custom command. For more information, see Tree Commands.

As a performance optimization, WebLogic Server does not store most of its default values in the domain’s configuration files. 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’s configuration files). For example, if you never modify the default logging severity level for a domain while the domain is active, WLST offline will not display the domain’s Log management object.

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.

When browsing custom MBeans, why do I get the following error message: No stub Available?

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 WebLogic Server MBean Reference.

Yes, one could fork a new weblogic.WLST process inside an Ant script and pass your script file as an argument.

Yes. You can create an instance of the WLST interpreter in your Java code and use it to run WLST commands and scripts. You can then call the WLST scripts as a startup class or as part of ejbCreate so that they execute on the server side. For more information, see Embedded Mode.

Yes. You can update the WLST home directory to define custom WLST commands, WLST commands within a library, and WLST commands as a Jython module. For more information, see Customizing WLST.

WebLogic Scripting Tool

FAQs: WLST