WebLogic Server (WLS) 7.0

Configuring Persistent WebLogic Server Processes
HP NonStop Server Platform Guide for WebLogic Server—525779-001
3-6
startgp.tacl
startgp.tacl
startgp.tacl is a TACL macro that must be copied to the Guardian namespace and
converted to an EDIT file using CTOEDIT. As with startgp.sh, the macro needs to
be updated to reflect the process to be started and must be run by a member of the
SUPER group.
Scripts to Start the WebLogic Server Process
Regardless of what method is used to add and start the generic process, a sample
script is needed to start the WebLogic Server process. To avoid the character limit of
115 on STARTUPMSG, place the following scripts in a directory near the root directory.
The administration server script and the node manager script use the standard scripts
created by the WebLogic Server. These scripts can be expanded as appropriate.
Administration Server Script
Place the following text into a file, turn the execute bit on, and use its name as the
script name used when adding the generic process:
#!/bin/sh
PATH=/usr/bin:/bin:/usr/local/bin:
cd <application directory>
../setEnv.sh
exec ./startWebLogic.sh
Node Manager Script
Place the following text into a file, turn the execute bit on, and use its name as the
script name used when adding the generic process:
#!/bin/sh
PATH=/usr/bin:/bin:/usr/local/bin:
cd application directory
../setEnv.sh
exec ./startNodeManager.sh
stopgp.sh and stopgp.tacl
The script and macro have one required argument, the generic process name, and an
optional delete argument if the generic process entry should be deleted. The script and
macro attempt to run an ABORT PROCESS command to cause the generic process to
stop. Because the process being stopped is the OSH process, running the ABORT
PROCESS command does not cause the WebLogic Server process to stop. Instead, the
scripts put out a message reminding you that the WebLogic Server process also needs
to be stopped.