C H A P T E R 5 - Operating the Content Delivery Server

C H A P T E R 5

Operating the Content Delivery Server

The Sun Java System Content Delivery Server provides continuous service with minimal operator attention. After you deploy and configure the Content Delivery Server, use the Content Delivery Server execute (cdse) command to start and stop the components as described in this chapter.

This section presents the following topics:

Starting the Content Delivery Server

Stopping the Content Delivery Server

5.1 Starting the Content Delivery Server

You must manually start the components of the Content Delivery Server. If you are using Sun Java System Application Server, you must first start the Sun Java System Message Queue broker using the following command:

$CDS_HOME/deployment/deployment-name/sun/applications/broker.sh start

The cdse startserver command starts all components in a deployment. If you do not want to start a service that is included in the deployment, use the administration console of your application server to disable the service before you start the Content Delivery Server. The following services need to be started only if you want to use the feature that they support:

The Notify Service needs to be started only if you want to send notifications about promotional offers to subscribers.

The Postpaid Service needs to be started only if your billing system uses the Call Data Records (CDRs) generated by Content Delivery Server or you want transactions stored in the reports database.

The Monitoring Service needs to be started only if you are connecting an SNMP Network Management station to the Content Delivery Server.

Note - If you are running on the HP-UX platform, set the maximum number of open files to 512 or greater before you start the Content Delivery Server components. To find out what the current limit is, enter the following command:
ulimit -a
To set the limit, enter the following command:
ulimit -n nn
nn is a number greater than or equal to 512.

Use the following command to start all of the components of the Content Delivery Server that are deployed on the host:

cdse startserver [-depl deployment-name] [-dbconf database-configuration-file] [-log log-file] [-spawn]

All parameters are optional. If the deployment parameter -depl is omitted, the value specified for DEFAULT_DEPL in the init_env.sh script is used. If the database configuration file parameter -dbconf is omitted, the value specified for DEFAULT_DB in the init_env.sh script is used. If the logging parameter -log is omitted, $CDS_HOME/cfg/logging.properties is used. If the spawn parameter -spawn is specified, the process is spawned and detached from the shell.

After the components start, you receive one of the following responses, depending on the application server that you are using:

Sun Java System Application Server reports Instance server-name started and returns the command line prompt.

WebLogic Server reports Listening to port nn (where nn is the port number). You are not returned to a command line prompt.

Tip - The default user name for the Catalog Manager and Vending Manager administration consoles is admin. The default password is admin. You must change the password the first time that you log in. There is no default account for either the Subscriber Portal or the Developer Portal.

5.2 Stopping the Content Delivery Server

Use the following command to stop all the components in a deployment:

cdse stopserver [-depl deployment-name] [-force]

All parameters are optional. If the deployment parameter -depl is omitted, the value specified for DEFAULT_DEPL in the init_env.sh script is used. If the force parameter -force is specified, the process is forced to stop regardless of what state the process is in.

If you are using a Sun Java System Application Server that is dedicated to the Content Delivery Server, stop the Sun Java System Message Queue after you stop the Content Delivery Server. Use the following command to stop the Message Queue:

$CDS_HOME/deployment/deployment-name/sun/applications/broker.sh stop