NonStop Server Guide for BEA WebLogic Server 8.1

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
4-13
Step 4. Configure Managed Servers Startup Options
icebat4.txn.cpqcorp.net
4. Start the Node Manager:
$WL_HOME/server/bin/startNodeManager.sh
5. In the output, check that new values for the properties are set.
Step 4. Configure Managed Servers Startup Options
The Node Manager will now start each managed server. Because neither the servers’
usual startup scripts (startManagedWebLogic.sh) or shell env are used, you must
configure the following for the managed servers:
1. $WL_HOME/server/lib/unix/nodemanager.sh starts each managed server
using NonStop platform-specific variables from nm-server.env:
Create $WL_HOME/common/nodemanager/nm-server.env with the minimum
contents shown below (TCP/IP stack identification is mandatory. See CPUselector
for information about CPU selection):
export TCPIP_PROCESS_NAME=\$ZSAMA
export PTCPIP_FILTER_KEY=rlkey
case $WLS_SERVER in
rlserver1)
WLS_CPUS=”0”
;;
rlserver2
WLS_CPUS=”1”
;;
esac
2. Configure startup options for each managed server. The environment values for
each managed server are mirrored from the Node Manager.
For options that must be configured at the managed server level:
a. In the Admin console GUI, select a managed server (for example, rlserver1).
b. Click the Remote Start tab and configure at least:
Root Directory: /home/roland/wls/bea/user_projects/domains/rldomain
User Name: weblogic
Password: ********
Step 5. Start Managed Servers Using the Node Manager
1. From the Admin console GUI:
a. Select a server and click the Control tab.
b. Click Start this server.