/
/ readMe.txt
/
/ Copyright (c) 2006, Oracle. All Rights Reserved.
/

ReadMe.txt
----------

Perl scripts to automate DP execution
-------------------------------------

File Lists:
-----------
executeDP.pl
generateTemplate.pl
initializeDelNode.pl
initializeExtCluster.pl
initializeRacProv.pl
replaceRuntimeValues.pl
replaceRuntimeValues_patching.pl

Usage:
----------
perl executeDP.pl
         -t <template>  (mandatory)
         -p <properties file name>  (mandatory)
         -g <DP GUID>  (manadatory) 
         [-s <schedule> in the format yyyy/MM/dd HH:mm]  (optional) 
         [-z <time zone id>]
         [-d <emcli directory path>, mandatory if emcli executable is not in current directory]
where,

template - is name of the RuntimeData template for out-of-box procedures or location of the RuntimeData xml file downloaded after the execution of a customized procedure.

properties file name- is the location of the properties file created for executing the procedure.

DP GUID- is the GUID of the procedure that needs to be executed. 

emcli Directory- is the directory, which has the EMCLI executable. In case the current working directory has the EMCLI executable, this parameter is optional.

schedule - The time when the deployment procedure would be scheduled to run, if not specified it defaults to run the deployment procedure immediately. The HH:MM is based on 24 Hrs Clock. E.g.: 22:30

Time Zone Id - The time zone to which the deployment procedure run is scheduled to, if not specified it defaults the schedule to the time zone of the OMS.

It uses the appropriate 'replaceRuntimeValues' perl script to instantiate the runtime xml. The instantiated runtime xml file is written in the current working directory with "instance_data_" prefixed to the name of runtime data template.



Automation Process:
-------------------
1. setup emcli.
   command: emcore/emcli/bin/emcli setup -url=<host>:<port>/em -user <repos user> -pass <repos password>";
   e.g. emcore/emcli/bin/emcli setup -url=http://myoms.example.com:1000/em -user sysman -pass welcome1
   This is a one time activity. This should be done only once before executing the DPs using emcli. Refer to 
   EMCLI documention for more details on setting up the client for EMCLI.

2. Synchronize emcli after setup . 
	command : emcore/emcli/bin/emcli sync
3. run executeDP.pl. with 4 parameters.
4. It submits the DP for execution, waits for its completion and then reports status. It creates the log files in current working directory. 

Example Usage
-------------
 perl executeDP.pl -t crsasmrac_gold_prov_template.xml -p crsasmrac_extend_cluster.txt -g 1F8178444594E67CE040578C8A0309BA 
-d /oracle/orahome/


Sample Output
-------------
Inside execute DP script.
Number of arguments passed : 6
Template Name  : crsasmrac_gold_prov_template.xml
Property File  : crsasmrac_extend_cluster.properties
UseCase Name   : crsasmrac_extend_cluster
DP GUId        : 1F8178444594E67CE040578C8A0309BA 
Repos User     : sysman
Source Path    : /oracle/orahome/
--------------------------------------------------------
Script execution started ...
Going to instantiate runtime data ...
*** Step Name: Instantiate Runtime Data SUCCESSFUL. ***
Going to submit DP using emcli ...
Verifying parameters ...
Parsing schedule "" ...
Schedule not specified, defaults to immediate
Deployment procedure submitted successfully
Instance GUID for DP run is : 229A1CCA02C9E3D9E040449824C55DC9
*** Step Name: Submit Deployment Procedure SUCCESSFUL. ***
Monitoring DP execution and waiting for its completion ...
Current Status is :  Scheduled
Current Status is :  Running 
Current Status is :  Running 
....
......
Current Status is :  Succeeded 
Monitoring DP execution is over.
DP Execution successfully completed.