Using WLST with Oracle Fusion Middleware Products

WebLogic Scripting Tool (WLST) is the standard command-line and scritping solution for administering WebLogic Server. Now with WebLogic Server (WLS) being the core application server for the Oracle Fusion Middleware (OFMW) components, WLST is also being extended for configuring and monitoring OFMW coponents. For example now you can use WLST for configuring Oracle SOA Suite, Oracle Web Center etc. WLST can be started by invoking the corresponding Java class or using wlst.cmd/sh script under the WL_HOME/common/bin folder for WLS environments. But when WLST is being used with other OFMW components it requires additional libraries and modules.

So instead of starting WLST from the WLS folders, it should be started from the respective component folders (E.g ORACLE_HOME_for_SOA/common/bin/wlst.sh). That way all the required additional libraries and modules are loaded and you can use the extended command to configure OFMW components like Oracle SOA suite, Oracle Web Center etc. If in case you started WLST from WLS folders or by directly invoking the Java command then you might see an error similar to the following:

wls:/wl_S3001/serverConfig> deleteConnection(appName, conn-name)
Traceback (innermost last):
File "", line 1, in ?
NameError: deleteConnection


The above is an example of a general Oracle WebCenter custom WLST command deleteConnection. If the command is not recognized by WLST then you would receive a NameError. This is the indication that WLST did not understood that command. As the OFMW component specific command are exention to the basic WLST they work only when the proper libraries and modules are loaded. You can find more information about this here - http://download.oracle.com/docs/cd/E12839_01/core.1111/e10105/getstart.htm#ASADM10692