|Oracle® Communications Marketing and Advertising System Administrator's Guide
Part Number E20558-01
This chapter explains how to start and stop Oracle Communications Marketing and Advertising servers.
Marketing and Advertising runs in the context of Oracle WebLogic server, so its startup and shutdown procedures are similar to those of other WebLogic servers.
This chapter describes two simple methods for starting Marketing and Advertising servers:
It also describes:
Always start Core Servers (the Network Cluster) before Web Servers (the Web Cluster) to prevent a database error.
For more complete information on the various ways to start and stop WebLogic Servers generally, see "Starting and Stopping Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server at:
You can start a Marketing and Advertising Administration server using the startWebLogic script that was installed domain_home/bin in your Marketing and Advertising installation.
You can start a Marketing and Advertising Managed server using the startManagedWebLogic script located in domain_home/bin of the machine on which that server runs. You must be logged into that machine. You specify the name of the server to start and the location of the Administration server.
The following example starts up the server named "managedserver1":
startManagedWebLogic.sh managedserver1 http://adminhost:8001
By default, the Marketing and Advertising server starts in production mode, so you will need to provide credentials. For information about how to do this, see the "Provide User Credentials to Start and Stop Server" section of at:
If you are starting servers in an HP-UX installation, you must add the -Djava.security.egd=/dev/random flag to the startWebLogic.sh script before running it.
Using a text editor, scroll down in the script until you come to the following section:
echo starting weblogic with Java version: %JAVA_HOME%\bin\java %JAVA_VM% -version if "%WLS_REDIRECT_LOG%"=="" ( echo Starting WLS with line:
Insert the flag in the next line, which starts:
echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy
at that point in the text.
When you are finished, the entire line should read:
echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Djava.security.egd=/dev/random %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS%
Node Manager is a WebLogic Server utility that enables you to start, stop, and restart administration servers and managed server instances from a remote location. Node Manager relies on a small demon process that must be running on each machine.
Using NodeManager, you can start Marketing and Advertising Managed servers from the Administration console. The console contacts the demon process, which starts the server.
For a complete description of the ways to use Node Manager, see Oracle Fusion Middleware Node Manager Administrator's Guide for WebLogic Server at:
The following instructions offer a simple Java-based method for starting production servers running on Linux or UNIX. Equivalent Microsoft Windows versions exist but are not described here because Windows is not supported for production servers.
To set up the Node Manager.
Start the Node Manager.
The best practice is to do this as part of the normal machine boot up sequence. To start it manually, log in into the server and change to the Middleware_Home/wlserver_10.3/server/bin directory.
Run the startNodeManager.sh script.
Edit the Middleware_Home/wlserver_10.3/common/nodemanager/nodemanager.domains file.
This file specifies the domains that a Node Manager instance controls.
See Oracle Fusion Middleware Node Manager Administrator's Guide for WebLogic Server at:
for a description of nodemanager.domains.
A sample entry is:
Edit the Middleware_Home/wlserver_10.3/common/nodemanager/nodemanager.properties file.
This file is created the first time you start the Node Manager.
Make sure that StartScriptEnabled is set to
Restart the Node Manager, as described in Step 1 above.
Create a startup script.
In the domain_home directory, create a file called startWeblogic.sh. Add a line to it specifying the start command, the server and the port:
./bin/startManagedWebLogic.sh [SERVER_NAME] [ADMIN_HOST_PORT]
./bin/startManagedWebLogic.sh OCM2 http://192.168.1.42:7001
Make sure that Listen Address is configured in the Administration console.
In Domain Structure, select Environment -> Machines -> machine_name->Node Manager. You must use Activate Changes to persist any changes.
At this point the Node Manager is set up. You can use the Node Manager to start Marketing and Advertising Managed servers from the domain's administration console.
To start Marketing and Advertising Managed servers from the domain's administration console:
Select Environment -> Servers.
On the Summary of Servers page, select the Control tab.
Select the checkbox(es) for the Marketing and Advertising server(s) that you want to start.
You can stop an Marketing and Advertising server from the Administration console following these steps:
From the Administration console, click Environment -> Servers.
On the Summary of Servers page, select the Control tab.
Select the checkbox(es) for the Marketing and Advertising server(s) that you want to shut down.
Select Shutdown from the menu.
Select from the menu's alternatives: to stop the server when its work completes or to stop it immediately.
You can stop Marketing and Advertising Managed servers using the stopManagedWeblogic script and the Administration server using the stopWeblogic script. These scripts were installed when you installed Marketing and Advertising.
To use the scripts, set SERVER_NAME, ADMIN_URL, USERID, and PASSWORD as environment variables or specify them on the command line. Run these scripts from domain_home/bin in your the Marketing and Advertising installation.
The following example stops the Marketing and Advertising server named "om3", assuming that the ADMIN_URL, USERID, and PASSWORD are set in the environment:
If you specify the parameters on the command line, they must be in order shown below:
stopManagedWeblogic.sh managed_server_name admin_url username password
The next example stops the administration server, using the same assumptions that ADMIN_URL, USERID, and PASSWORD are set in the environment. If no server is specified, the administration server is stopped by default.
For more information about stopping WebLogic servers, see Shutting Down Instances of WebLogic Server at: