Home > AdminServer, Weblogic, WLST > WebLogic AdminServer startup and shutdown scripts

WebLogic AdminServer startup and shutdown scripts

January 15, 2012 Leave a comment Go to comments

Right after creating a WebLogic domain, you can navigate to the domain directory and start the administration server using the startWebLogic.sh script. However, for easier control over the administration server of your domain, you can create some WLST startup and shutdown scripts that manage your admin server via the Node Manager.

The solution below describes two WLST scripts (startAdmin.jy and stopAdmin.jy ) and two platform dependent scripts that you use to call the Jython ones. (startAdmin.sh and stopAdmin.sh for Unix or startAdmin.bat and stopAdmin.bat for Windows)

In order to use these scripts, you must be able to connect to the Node Manager via WLST, so if you are hitting the “Access to domain <domain> for user ‘weblogic’ denied” error, please see this post first. Once you can connect, create the following files, usually under WL_HOME/wlserver_12.1/server/bin:

——–stopAdmin.jy——–
nmConnect(‘NM_user’,’NM_pass’,’NM_host’,’NM_port’,’Domain_Name,’Domain_Directory’,’Connection_type’);
nmKill(‘Administration Server Name’);
nmDisconnect();
exit();

Of course, the correct parameters need to be set accordingly, for example:

nmConnect(‘weblogic’,’welcome1′,’localhost’,’5556′,’FMW_XPS’,’/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS’,’plain’);
nmKill(‘AdminServer’);
nmDisconnect();
exit();

The same for start:

——–startAdmin.jy——–
nmConnect(‘weblogic’,’welcome1′,’localhost’,’5556′,’FMW_XPS’,’/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS’,’plain’);
nmStart(‘AdminServer’);
nmDisconnect();
exit();

Once the Jython scripts are working, you can create scripts to call them. These can be found under an easily accessible location such as /home/oracle/bin in UNIX, or the Desktop on Windows, or can even be called automatically at boot if you want your admin server started automatically:

For UNIX:

——stopAdmin.sh——
export WL_HOME=/shared/oracle/FMW_Home/wlserver_12.1/server/bin
echo Stopping Weblogic 12c – FMW_XPS Domain
. $WL_HOME/setWLSEnv.sh > /dev/null 2>&1
java weblogic.WLST $WL_HOME/wlserver_12.1/server/bin/stop_FMWAdmin.jy

——startAdmin.sh——
export WL_HOME=/shared/oracle/FMW_Home/wlserver_12.1/server/bin
echo Starting Weblogic 12c – FMW_XPS Domain
. $WL_HOME/setWLSEnv.sh > /dev/null 2>&1
java weblogic.WLST $WL_HOME/wlserver_12.1/server/bin/start_FMWAdmin.jy

For Windows:

——stopAdmin.bat——
call C:\oracle\Middleware\wlserver_10.3\server\bin\setWLSEnv.cmd
java weblogic.WLST C:\oracle\Middleware\user_projects\domains\Allianz\stop_FMWAdmin.jy

——startAdmin.bat——
call C:\oracle\Middleware\wlserver_10.3\server\bin\setWLSEnv.cmd
java weblogic.WLST C:\oracle\Middleware\user_projects\domains\Allianz\start_FMWAdmin.jy

The output should look like:

Please leave a comment below if you’ve come across any issues setting the above scripts.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: