# System Administrator’s Guide

# Starting and Stopping Servers

The following sections describe how to start and stop servers in an Oracle Communications Services Gatekeeper domain:

Note: | Oracle Communications Services Gatekeeper start scripts use default values for many 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 and Network Tier servers, with dependencies among the different server types, you should generally follow this sequence when starting up a domain:

1. Start the Administration Server for the domain.

Start the Administration Server in order to provide the initial configuration to Access 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.

2. Start Network Tier servers in each partition.

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

Note: | When OCSG is first used, the database is initialized. If two NT servers are started up at the same time, they may both try to initialize the database, causing a Service Deployment Exception and one server failing to start up. Make sure the servers are started one at a time. If this occurs, restart the failed server.

1. 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 and Access Tier servers by using the `startManagedWebLogic` script installed with the Configuration Wizard or a custom startup script.

To use the `startManagedWebLogic` script, you must specify the name of the server to startup, as well as the URL of the Administration Server for the domain, as in:

    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. There are several ways to do this. See section Provide User Credentials to Start and Stop Server in http://download.oracle.com/docs/cd/E12840_01/wls/docs103/server_start/overview.html for more information.

#### Using Node Manager

You can also start Network and Access Tier servers by using the Management 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 Server Node Manager Administrator’s Guide at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/index.html) but the easiest is to use the Java-based version, as follows:

Note: | These instructions assume UNIX or Linux. Equivalent Windows versions exist, but Windows is not supported for production servers. These steps must be followed on each of the managed servers.

1. Start the node manager. Best practice is to have this as part of the normal machine boot up sequence. To do it manually, login into the server and change to the `<bea_home>/ocsg_4.1/wlserver_10.3/server/bin` directory. Run the `./startNodeManager.sh` script.
2. Edit the `<bea_home>/wlserver_10.3/common/nodemanager/nodemanager.domains` file. This file specifies the domains that a Node Manager instance controls. See Oracle Weblogic Server Node Manager Administrator’s Guide at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/index.html for a description of `nodemanager.domains`. A sample entry:
   `ocsg-domain=/bea/user_projects/domains/ocsg-domain`
3. Edit the `<bea_home>/wlserver_10.3/common/nodemanager/nodemanager.properties` file. Make sure that `StartScriptEnabled=true` is set.
4. Restart the node manager, using Step 1 above.
5. 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`

6. 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 any make any changes.
7. Once 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.

There are other numerous ways of starting and stopping servers. For a quick reference on how to start and stop servers, see Oracle Weblogic Server Managing Server Startup and Shutdown at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/server_start/index.html.

Note: | 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

Note: | 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.