RRF Rule definitions can be executed through the following command line utilities:
· Command Line Utility for Rule Execution
· Command Line Utility for Run Execution
You can execute RRF Rule definitions through command line utility.
To execute Rule definitions, do the following:
1. Navigate to $FIC_HOME/utility/RuleExecution/bin of OFSAAI APP tier.
2. Execute RuleExecution.sh (UNIX) along with the required arguments such as <BatchRunExeID> <ComponentID> <TaskID> <MisDate> <DataStoreType> <INFODOM> <IPaddress> <RuleID> <BuildFlag> <OptionalParameters> in the same order.
Arguments |
Description |
BatchRunExeID |
Refers to the Execution ID of the Batch being executed. |
ComponentID |
Refers to The Type of component to be executed. |
TaskID |
Refers to the Task ID. |
MisDate |
Refers to the date with which the data for the execution would be filtered. |
DataStoreType |
Refers to the type of data store such as Enterprise Data Warehouse (EDW) which refers to the Multi-dimensional Database/Cubes. |
INFODOM |
Refers to the Information Domain mapped. |
IPaddress |
Refers to the IP Address of the machine on which Infrastructure Database Components have been installed. |
RuleID |
Refers to the Rule definition to be executed. |
BuildFlag |
Build Flag refers to the pre-compiled rules, which are executed with the query stored in database. Built Flag status set to "No" indicates that the query statement is formed dynamically retrieving the technical metadata details. If the Build Flag status is set to "Yes" then the relevant metadata details required to form the rule query is re-compiled in database. |
OptionalParameters |
Refers to the set of parameters which would behave as filter criteria for the merge query. |
For example,
ksh RuleExecution.sh RRFATOM_exec_rule_20120904_1 RULE_EXECUTION Task1 20120906 EDW RRFATOM A.B.C.D 1344397138549 N '$RUNID=,$PHID=,$EXEID=,$RUNSK='
3. You can access the location $FIC_HOME/utility/RuleExecution/logs to view the related log files. Also the component specific logs can be accessed in the location fic_home/ftpshare/logs.
Manage Run Execution utility can be used to execute Run definitions through RESTful Web Services call. To achieve this, RESTful Service, Client and Shell script are available.
NOTE |
The REST authentication is done against the Service Account user mentioned under OFSAA_SRVC_ACC parameter in the CONFIGURATION table. This user should be created with "SMS Auth Only" attribute from the User Maintenance window. By default, OFSAA_SRVC_ACC parameter is set as SYSADMN. |
Following are the pre-requisites before executing this utility:
1. Ensure that JAVA_HOME is pointing to JAVA bin installation directory.
2. Ensure FIC_HOME is pointing to application installation directory.
3. Set the PATH variable as $ICC_HOME/bin.
To execute this utility, do the following:
1. Navigate to $FIC_HOME/ficapp/icc/bin of OFSAAI APP tier.
2. Provide the following parameters in the command line.
Arguments |
Description |
RUNCODE |
Refers to Run Code to be executed. |
INFODOM |
Refers to the mapped Information Domain. |
SEGMENT/FOLDER |
Refers to the Folder / Segment name to which run is getting executed. |
Run Execution Description |
Refers to the batch description. Note: In case the Run Execution description has space, the same can be passed using double quotes. |
USERNAME |
Refers to the user name who is executing. Note: The User ID or Service accounts are “SMS Auth Only” in case of SSO and LDAP configured setups. |
MISDATE |
Refers to the date with which the data for the execution would be filtered. |
3. Execute WSMRERequest.sh <Run Code> <Infodom> <Segment/Folder Code> <Run Execution Description> <Username> <MIS Date <yyyyMMdd>>.
For example,
./WSMRERequest.sh "1305855689766" "APP" "APPSEG" "App approach" "APPUSER" "20001231”
4. You can access the location $FIC_HOME/ficapp/icc/log/WSMRERequest.log to view the related log files. Also the component specific logs can be accessed in the location <OFSAAI deployed path>/logs.
Every execution of Fire Run Service creates a text file in the location ficapp/icc/mre which contains the Batch ID created for that particular Run. The text file has the following format:
INFODOM_RUNID_MISDATE.mre