Professional Documents
Culture Documents
x using WLST
The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system
administrators and operators use to monitor and manage WebLogic Server instances and
domains. The WLST scripting environment is based on the Java scripting interpreter, Jython. You
can use the scripting tool online (connected to a running Administration Server or Managed
Server instance) and offline (not connected to a running server).Commands for
deployment/undeployment can only be executed on online mode.
Below are the steps to deploy/redeploy/undeploy applications in weblogic server using WLST.
You need to run weblogic environment set up script, setWLSEnv.sh, If you see the below error
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/WLST
2) Execute the below command for connecting to weblogic admin server and to make WLST
online.
connect ('<AdminServerUserName>','<AdminServerPassword>','<URL>');
Replace <AdminServerUserName> / <AdminServerPassword> with the weblogic admin user
name/password in the above command. <URL> consists the listen address and listen port of the
admin server instance, specified using the following format: [protocol://]listen-address:listen-port
For example, below is the command for connecting to weblogic server in test environment.
connect('pricetst','pricetst','t3://hvdnt44a.dev.qintra.com:20010')
Note: Make sure that the server is up and running before trying to connect. The above two steps
are to be executed before running any of the below deploy/redeploy/undeploy commands.
For example, below is the command for deploying ‘ips0’ application in the test environment.
If the deployment is not successful, execute dumpStack() function to know the root cause.
dumpStack() displays stack trace from the last exception that occurred while performing a WLST
action, and reset the stack trace.
4) Use the below command for redeploying an already running application.
The same set of arguments (mentioned in the 4th step) are to be provided here as well.
disconnect()
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.
exit()
Note:
The deployment/redeployment steps mentioned above would also make the applications in active
state. So a different activation process is not required. You may log into admin console- (for test
environment-http://hvdnt44a.dev.qintra.com:20010/console) and verify the deployment status if
required.
Links: