17 Stopping and Starting Services and Queues

For information about the initial installation of Oracle Warehouse Builder or the Distributed Processing Server, see "Installing the Oracle Life Sciences Data Hub" in the Oracle Life Sciences Data Hub Installation Guide.

See Setting Up Services for information about the Distributed Processing (DP) Server.

Note:

During its development, the Oracle Life Sciences Data Hub was known internally as CDR. Therefore many Oracle LSH-related directories, files, scripts, parameters, and so on are named CDR or contain the string cdr. Please think of CDR as a synonym for Oracle LSH.

This section contains the following topics:

• Starting, Stopping, and Checking the Distributed Processing Service
  The Oracle Life Sciences Data Hub Distributed Processing (DP) Server passes jobs—executions of user-defined Programs and Data Marts and internal Oracle LSH jobs requiring XML Publisher—to the external engines that process them.
• Stopping and Starting the Oracle Warehouse Builder Service
  The Oracle Warehouse Builder (OWB) service is required to run any Oracle Life Sciences Data Hub job and to install Work Areas.
• Stopping, Starting, and Enabling the Job Queue
  A job queue is required on the database to pass jobs from Oracle Life Sciences Data Hub to OWB.
• Starting and Stopping Message-Triggered Submission Queues
  You can start and stop message-triggered submission queues.

Starting, Stopping, and Checking the Distributed Processing Service

The Oracle Life Sciences Data Hub Distributed Processing (DP) Server passes jobs—executions of user-defined Programs and Data Marts and internal Oracle LSH jobs requiring XML Publisher—to the external engines that process them.

You must install and start the DP Server on every computer where you have a processing engine installed. See Setting Up Services for further information.

You must then start the service on the computer where it is required. The scripts required for starting, checking, and stopping the DP Server are provided with Oracle LSH. See Setting Up the Distributed Processing Server and the Oracle Life Sciences Data Hub Installation Guide for instructions for copying them to the DP Server home directory in each location.

This section contains the following topics:

• Login Name
  You must log in as cdr_dpserver.
• Starting the Distributed Processing Server Service
  You can start the Distributed Processing Server Service by following the steps in this procedure.
• Checking the Distributed Processing Server Service
  After you have installed and started the service, use the script checkJSapps to check that it is running.
• Stopping the Distributed Processing Server Service
  You can start the Distributed Processing Server Service by following the steps in this procedure.

Login Name

You must log in as cdr_dpserver.

This user is created by the post-installation job. Your company should have changed the default password. See "Run the Post-Installation Programs" in the chapter on installing Oracle Life Sciences Data Hub in the Oracle Life Sciences Data Hub Installation Guide for further information.

Starting the Distributed Processing Server Service

You can start the Distributed Processing Server Service by following the steps in this procedure.

1. If you have not already edited the script cdr_apps_dpserver.sh (or cdr_apps_dpserver.cmd), do so. See "Edit the DP Server Start Script" in the chapter on installing Oracle Life Sciences Data Hub in the Oracle Life Sciences Data Hub Installation Guide.
2. Log on as cdr_dpserver.

   This user is created when you run the post-installation job (see the "Run the Post-Installation Programs" in the chapter on installing Oracle LSH in the Oracle Life Sciences Data Hub Installation Guide).

3. Run the script cdr_apps_dpserver.sh (or cdr_apps_dpserver.bat) by entering the following command:

   ./cdr_apps_dpserver.sh ORACLE_SID DB_HOST DB_PORT RAC_TNS RAC_FLAG

   where:

   • ORACLE_SID is the Oracle SID of the database

     Note:

     The Oracle SID is case-sensitive.
   • DB_HOST is the name of the computer where the Oracle_SID resides
   • DB_PORT is the SQL*Net Listener port for the Oracle_SID
   • RAC_TNS is the JDBC connection string of the database server
   • RAC_FLAG indicates whether you are using an Oracle RAC (Real Application Cluster) database installation. Set to RAC if you have a RAC installation. Set to NO-RAC if you do not.

     The RAC_FLAG setting determines which input parameter values the script uses when starting the DP Server.

     • If RAC_FLAG is set to RAC, the script uses only the value for RAC_TNS.

     • If RAC_FLAG is set to NO-RAC, the script uses the values for ORACLE_SID, DB_HOST, and DB_PORT.

     In either case, it does not matter what value you enter for the unused parameters. See examples below.

   • FW_ENABLED Set to Yes to start the File Watcher Service or No if you are not using Oracle DMW.
   • FW_FREQ (Applies only to Oracle DMW customers.) Refresh frequency in seconds. This value specifies the minimum interval between requests to the database to check if there is a new set of Watcher Configurations. This value cannot be set lower than 60 seconds. A high setting will result in a delay between the user's addition or adjustment of a Watcher Configuration in Oracle DMW and the changes' taking effect in file detection behavior.
   • FW_POLL (Applies only to Oracle DMW customers.) Polling frequency in seconds. The polling frequency represents the minimum interval at which a File Watcher Service may run to detect if there are any files in the watched location that should be loaded into Oracle DMW. The minimum value permitted is 60 seconds.

   NO-RAC Example when RAC_FLAG is set to NO-RAC:

   ./cdr_apps_dpserver.sh abc123 ab123cd.example.com 1234 NA NO-RAC

   where:

   • abc123 is the Oracle SID
   • ab123cd.example.com is the host
   • 1234 is the port
   • You may enter NA (Not Applicable) or any other value for RAC_TNS.
   • NO-RAC is the setting for RAC_FLAG

   RAC Example when RAC_FLAG is set to RAC:

   ./cdr_apps_dpserver.sh NA NA NA 'jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=ab123cd.example.com)(PORT=1234))(ADDRESS=(PROTOCOL=tcp)(HOST=ef456ghRAC.example.com)(PORT=5678)))(CONNECT_DATA=(SERVICE_NAME=CDRXXX)))' RAC

   where:

   • You may enter NA (Not Applicable) or any other value for ORACLE_SID.
   • You may enter NA (Not Applicable) or any other value for DB_PORT.
   • You may enter NA (Not Applicable) or any other value for DB_HOST.
   • jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=ab123cd.example.com)(PORT=1234))(ADDRESS=(PROTOCOL=tcp)(HOST=ef456ghRAC.example.com)(PORT=5678)))(CONNECT_DATA=(SERVICE_NAME=CDRXXX)))is the JDBC connection string of the database server
   • RAC is the setting for RAC_FLAG
4. The script prompts you for a password. Enter the password for the cdr_dpserver user.

Note:

Do not change the value of DB_USER.

Checking the Distributed Processing Server Service

After you have installed and started the service, use the script checkJSapps to check that it is running.

Enter the ORACLE_SID as a parameter value.

1. Log on as cdr_dpserver.
2. Run the script checkJSapps.sh (or cdr_apps_dpserver.bat) by entering the following command:

   checkJSapps Oracle_SID

   For example:

   ./checkJSapps abc123

   where abc123 is the SID.

Note:

The Oracle SID is case-sensitive.

Stopping the Distributed Processing Server Service

You can start the Distributed Processing Server Service by following the steps in this procedure.

1. Log on as cdr_dpserver.
2. Run the script stopJSapps.sh by entering the following command:

   stopJSapps.sh Oracle_SID DPService_Name

   where:

   • Oracle_SID is the Oracle SID of the database

     Note:

     The Oracle SID is case-sensitive.
   • DPService_Name is the Service Location name for the computer where the DP Server is running.

Stopping and Starting the Oracle Warehouse Builder Service

The Oracle Warehouse Builder (OWB) service is required to run any Oracle Life Sciences Data Hub job and to install Work Areas.

The OWB service is started automatically by the Oracle LSH database startup kit during installation.

Note:

The OWB server's log files are located in the directory $OWB_HOME/owb/log. If you have problems with a Work Area installation, the log file may help you diagnose the problem.

• Stopping the OWB Service
  To stop the OWB service do the following:
• Starting the OWB Service
  To start the OWB service do the following:

Stopping the OWB Service

To stop the OWB service do the following:

1. Change directory to $OWB_HOME/owb/rtp/sql
2. Log into SQL using the CDR_RTREPOS username and the password you set up when you installed OWB (see "Installing Oracle Warehouse Builder" in the Oracle Life Sciences Data Hub Installation Guide).

   Note:

   If you have upgraded to OWB 11.2.0.1 you must log in as OWBSYS instead of CDR_RTREPOS.
3. At the SQL prompt, enter:

   @stop_service.sql

When the system displays the words "Not Available" the service is stopped.

Starting the OWB Service

To start the OWB service do the following:

1. Change directory to $OWB_HOME/owb/rtp/sql
2. Log into SQL using the CDR_RTREPOS username and the password you set up when you installed OWB (see "Installing Oracle Warehouse Builder" in the Oracle Life Sciences Data Hub Installation Guide).

   Note:

   If you have upgraded to OWB 11.2.0.1 you must log in as OWBSYS instead of CDR_RTREPOS.
3. At the SQL prompt, enter:

   @start_service.sql

When the system displays the word "Available" the service has been restarted.

Stopping, Starting, and Enabling the Job Queue

A job queue is required on the database to pass jobs from Oracle Life Sciences Data Hub to OWB.

The job queue is enabled by the Oracle LSH post-installation concurrent processing job. You must explicitly start it using the instructions below.

Note:

The scripts are located in $cdr/patch/115/sql/.

This section includes the following topics:

• Starting the Job Queue
  To start the job queue, connect as apps to run the script.
• Stopping the Job Queue
  You can stop and disable the job queue by connecting as apps to run the script.
• Enabling the Job Queue
  After you have started the job queue (or it has been started during installation) you must enable the job queue by connecting as apps and running the script.

Starting the Job Queue

To start the job queue, connect as apps to run the script.

 begin
 cdr_exe_job_queues.start_jobq_process_disabled;
 end;
/
commit;

Stopping the Job Queue

You can stop and disable the job queue by connecting as apps to run the script.

begin
cdr_exe_job_queues.stop_processing_queues;
end;
/
commit;

Enabling the Job Queue

After you have started the job queue (or it has been started during installation) you must enable the job queue by connecting as apps and running the script.

begin
cdr_exe_job_queues.start_jobq_process_enabled;
end;
/
commit;

Starting and Stopping Message-Triggered Submission Queues

You can start and stop message-triggered submission queues.

Note:

If you plan to use message-triggered job submission, you must start a job queue on the database to pass jobs to Oracle Life Sciences Data Hub from XML messages from external systems. See "Using Message-Triggered Submission from External Systems" in the Oracle Life Sciences Data Hub Application Developer's Guide.

This section contains the following topics:

• Starting a Message-Triggered Submission Queue
  Log on as the APPS user and enter the following to start the queue:
• Stopping a Message-Triggered Submission Queue
  Log on as the APPS user and enter the following to stop the queue:

Starting a Message-Triggered Submission Queue

Log on as the APPS user and enter the following to start the queue:

begin
cdr_exe_msg_queues_admin.start_processing_queues;
cdr_exe_msg_queues_admin.enable_job_processing_queue;
end; 

Stopping a Message-Triggered Submission Queue

Log on as the APPS user and enter the following to stop the queue:

begin
cdr_exe_msg_queues_admin.stop_processing_queues;
end;