2 Starting and Stopping Servers

This chapter describes how to start and stop servers in an Oracle Communications Services Gatekeeper domain.

Note that the Oracle Communications Services Gatekeeper start scripts use default values for many Java Virtual machine (JVM) parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance.

Because a typical Oracle Communications Services Gatekeeper domain contains multiple Access Tier and Network Tier servers, with dependencies among the different server types, you should generally adhere to the following sequence when starting up a domain:

Start the Administration Server for the domain.

The Administration Server provides the initial configuration to Access Tier and Network Tier servers in the domain. The Administration Server can also be used to monitor the startup/shutdown status of each Managed Server. You generally start the Administration Server by using either the startAdminServer script installed with the Configuration wizard or a custom startup script.
Start Network Tier servers in each partition.

The Access Tier cannot function until servers in the Network Tier are available.
Start Access Tier servers in each partition.

Caution:

All servers should be started and available before opening the system to production network traffic.

Using Scripts

You can start Network Tier and Access Tier servers by using either the startManagedWebLogic script installed with the Configuration wizard or a custom startup script.

To use the startManagedWebLogic script, specify the name of the server to start and the URL of the Administration Server for the domain using the syntax:

startManagedWebLogic.sh managed_server_name admin_url

For example:

startManagedWebLogic.sh networknode0-0 t3://adminhost:7001

Note:

By default, the servers are started in production mode. This means that user credentials must be provided. For more information, see "Provide User Credentials to Start and Stop Server" in Oracle® Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server at

http://download.oracle.com/docs/cd/E15523_01/web.1111/e13708/overview.htm

Using Node Manager

You can also start Network Tier and Access Tier servers by using the Administration Console in conjunction with an instance of Node Manager running on each machine. There are many different ways to use Node Manager. See Oracle Weblogic Middleware Node Manager Administrator's Guide for Oracle WebLogic Server at

http://download.oracle.com/docs/cd/E15523_01/web.1111/e13740/toc.htm

but the easiest is to use the Java-based version, as follows:

Note:

The following instructions assume UNIX or Linux. Equivalent Windows versions exist, but Windows is not supported for production servers. The following instructions must be followed on managed server.

Start the node manager.

The best practice is to have this as part of the normal machine startup sequence. To do it manually:
1. Log in into the server.
2. Change to the Middleware_Home/wlserver_10.3/server/bin directory.
3. Run the ./startNodeManager.sh script.
Add the domains that the Node Manager instance controls to the Middleware_Home/wlserver_10.3/common/nodemanager/nodemanager.domains file. See “General Node Manager Configuration” in Oracle® Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server at

http://download.oracle.com/docs/cd/E15523_01/web.1111/e13740/nodemgr_config.htm#BHCJHHDC

for a description of nodemanager.domains. A sample entry for a domain in this file is:
```
ocsg-domain=/bea/user_projects/domains/ocsg-domain
```
Edit the Middleware_Home/wlserver_10.3/common/nodemanager/nodemanager.properties file. Make sure that StartScriptEnabled=true is set.
Restart the node manager, using Step 1 above.
Create a startup script. In the Domain_home directory, create a file called startWeblogic.sh and add this line:
```
./bin/startManagedWebLogic.sh SERVER_NAME ADMIN_HOST_PORT
```
For example: ./bin/startManagedWebLogic.sh NT1 192.168.1.42:7001
Make sure that Listen Address is configured in the Console. In Domain Structure, click Environment > Machines > machine_name > Node Manager. You must use Lock & Edit to make any changes.
After everything is set up, to use the Node Manager to start Oracle Communications Services Gatekeeper servers, go to the domain's Administration Console. Under Environment, select the managed servers you want to start.

For other ways of starting and stopping servers, see “Starting and Stopping Servers” in Oracle® Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server at:

http://download.oracle.com/docs/cd/E15523_01/web.1111/e13708/toc.htm

HP-UX

If you are using HP-UX in your installation, you must make a small edit to whichever of the startup scripts you are using. You must add the -Djava.security.egd flag to the invocation, in the locations shown below in bold.

if [ '${WLS_REDIRECT_LOG}' = '' ] ; then
        echo 'Starting WLS with line:'
        echo '${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}-Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy  ${PROXY_SETTINGS}
${SERVER_CLASS}' ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Djava.security.egd=/dev/random -Dweblogic.Name
=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy
${PROXY_SETTINGS} ${SERVER_CLASS}
else
        echo 'Redirecting output from WLS window to ${WLS_REDIRECT_LOG}' 
        ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
-Djava.security.egd=/dev/random -Dweblogic.Name
=${SERVER_NAME} -Djava.security.policy=${
WL_HOME}/server/lib/weblogic.policy${PROXY_SETTINGS} ${SERVER_CLASS}  >'${WLS_REDIRECT_LOG}' 2>&1

Solaris 64-bit

If your installation is for Solaris 64-bit, and you are using Sun's JVM, you must add the -d64 flag to whichever startup script you are using. If you do not use this flag, the JVM will default to 32-bit.