Copy, Edit, and Grant Permissions to Execution Command Files for Processing Engines

Do the following on each computer where you have installed a processing engine:

1. From $CDR_TOP/admin/template, copy the sample execution command script for each processing engine installed on the computer. You can copy the scripts directly into the DP Server Home directory or create a subdirectory for them.

   Note:

   Keep a record of the absolute location of these scripts. You will need it when you define a service location for the computer. See Define Service Locations and Services for details.

   The scripts include:

   • cdrzip.sh and cdrunzip.shfor Text Data Marts
   • sasNormal.sh for SAS Programs
   • oraexp.sh for Oracle Export Data Marts
   • orareprunner.sh for Oracle Reports Programs
   • txtNormal.sh for Text Load Sets
   • xmlprunner.sh for post-processing Report Sets
   • xmlpreprunner.sh for the Oracle LSH system reports and for cover sheets for outputs
   • obieeinstall.cmd for Oracle Business Intelligence Business Areas—required only on the BI Server
   • obieedeploy.cmd for Oracle Business Intelligence Business Areas— required only on the BI Server
2. Edit each script with information specific to the computer, for example:
   • Oracle SID
   • Location of the technology server
   • Location of Oracle setup script coraenv
   • Paths

   Ensure that environment variables are accessible to the DP server. For example, if the script refers to the variable $ORACLE_HOME, either define the variable or provide the full path in the script.

   Note:

   If you run SAS programs, add instructions to sasNormal.sh to start SAS in UTF8 mode. (See Start SAS in UTF8 Mode for details.) In addition, include the DP Server Home path  in the environment variable as shown:

   PATH=$ORACLE_HOME/bin:$ORACLE_HOME/lib32: DP_Server_Home_Path:$PATH export PATH

3. Make all the scripts executable on the UNIX system with the following command:

   chmod 755 *.sh