| Oracle® Life Sciences Data Hub System Administrator's Guide Release 2.2 Part Number E22745-02 |
|
|
View PDF |
| Oracle® Life Sciences Data Hub System Administrator's Guide Release 2.2 Part Number E22745-02 |
|
|
View PDF |
This section contains the following topics:
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 Chapter 1, "Setting Up Services" for information about the Distributed Processing (DP) Server.
Note:
During its development, the Oracle Life Sciences Data Hub (Oracle LSH) 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:
The Oracle LSH 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 Chapter 1, "Setting Up Services" for further information.
The scripts required for starting, checking, and stopping the DP Server are provided with Oracle LSH. See "Setting Up the Distributed Processing Server" for instructions for copying them to the DP Server home directory in each location.
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 LSH in the Oracle Life Sciences Data Hub Installation Guide for further information.
To start the DP Server, do the following:
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 LSH in the Oracle Life Sciences Data Hub Installation Guide.
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).
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.
Example when RAC_FLAG is set to NO-RAC:
./cdr_apps_dpserver.sh CDRD6X10 ad986sdb.us.oracle.com 20502 NA NO-RAC
where:
CDRD6X10 is the Oracle SID
ad986sdb.us.oracle.com is the host
20502 is the port
You may enter NA (Not Applicable) or any other value for RAC_TNS.
NO-RAC is the setting for RAC_FLAG
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=AP6010RAC.us.oracle.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=AP6009RAC.us.oracle.com)(PORT=1521)))(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=AP6010RAC.us.oracle.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=AP6009RAC.us.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=CDRXXX)))is the JDBC connection string of the database server
RAC is the setting for RAC_FLAG
The script prompts you for a password. Enter the password for the cdr_dpserver user.
Note:
Do not change the value of DB_USER.After you have installed and started the DP server, use the script checkJSapps to check that it is running. Enter the ORACLE_SID as a parameter value.
Log on as cdr_dpserver.
Run the script checkJSapps.sh (or cdr_apps_dpserver.bat) by entering the following command:
checkJSapps Oracle_SID
For example:
./checkJSapps CDRD6X10
where CDRD6X10 is the SID.
Note:
The Oracle SID is case-sensitive.To stop the DP Server, do the following:
Log on as cdr_dpserver.
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.
The Oracle Warehouse Builder (OWB) service is required to run any Oracle LSH 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.To stop the OWB service do the following:
Change directory to $OWB_HOME/owb/rtp/sql
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.At the SQL prompt, enter:
@stop_service.sql
When the system displays the words "Not Available" the service is stopped.
To start the OWB service do the following:
Change directory to $OWB_HOME/owb/rtp/sql
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.At the SQL prompt, enter:
@start_service.sql
When the system displays the word "Available" the service has been restarted.
A job queue is required on the database to pass jobs from Oracle LSH to OWB. The job queue is started by the Oracle LSH post-installation concurrent processing job. Afterwards you normally do not need to stop or restart the job queue. However, if the need arises you can use the following scripts.
This section includes the following topics:
You can stop and disable the job queue by connecting as apps and running this script:
begin cdr_exe_job_queues.stop_processing_queues; end; / commit;
To start the job queue, connect as apps and run this script:
Note:
This script starts the job queue but does not enable it. See "Enabling the Job Queue" to enable the queue.begin cdr_exe_job_queues.start_jobq_process_disabled; end; / commit;
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 a script as follows:
begin cdr_exe_job_queues.start_jobq_process_enabled; end; / commit;
This section contains the following topics:
If you plan to use message-triggered job submission, you must start a job queue on the database to pass jobs to Oracle LSH 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.
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;
Log on as the APPS user and enter the following to stop the queue:
begin cdr_exe_msg_queues_admin.stop_processing_queues; end;
|
 Copyright © 2006, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|