RDF and Curve provide a number of hooks for running customized computation at certain points of the batch process.
Generate is an RDF utility that runs the RDF batch, such as generating profiles, generating source level forecasts, and approving forecasts. Often, some customized computation is needed during the running of generate. For instance, after the generation of forecast and prior to the forecast approval, you may want to run some rules to compute the value of the approval alerts.
Curvebatch is a Curve utility that runs profile generation batch, such as range data source, generate source level profiles, and merge profiles.
This appendix details these topics:
There are several hooks provided in the RDF Generate and Curvebatch utilities so that custom expressions can be run at various predefined phases of the batch.
The hooks listed in the following tables are defined in the appcust.xml file.
Each phase of the batch cycle begins and ends with a hook that links to the next phase. Table F-1 lists and describes the RDF batch phases along with its hooks. These hooks are provided in the RDF Generate utility and defined in the appcust.xml file as shown in Figure F-1.
Table F-1 RDF Phases and Hooks
Phase | Phase Action | This Hook... | Is Run... |
---|---|---|---|
Initialization |
Prepares initializing environment for forecast generation |
preinit |
before initialization starts |
postinit |
after initialization |
||
Forecast Generation |
Generates forecast |
pregen |
before generate forecast |
postgen |
after generate forecast |
||
Like Functionality Performance |
Runs a like item sister store functionality |
prelikets |
Before likets function |
postlikets |
After likets function |
||
Forecast Adjustment |
Automatic adjustment for forecast |
preadjust |
Before adjust forecast |
postadjust |
After adjust forecast |
||
Alert Execution |
Runs alerts |
prealert |
Before generate alerts |
postalert |
After generate alerts |
||
Forecast Approval |
Automatic approval of forecast |
preapprove |
Before forecast approval |
postapprove |
After forecast approval |
Each phase of the batch cycle begins and ends with a hook that links to the next phase. Table F-2 lists and describes the Curve batch phases along with its hooks. These hooks are provided in the Curvebatch utility and defined in the appcust.xml file as shown in Figure F-2.
Table F-2 Curve Phases and Hooks
Phase | Phase Action | This Hook... | Is Run... |
---|---|---|---|
Ranging |
Ranging the source data based on training window |
prerangesource |
Before rangeDataSource is run |
postrangesource |
After rangeDataSource is run |
||
Profile Generation |
Generate profile at all source levels |
prerunsource |
One time before SourceLevel:run is iteratively performed on all source levels of the profile |
postrunsource |
One time after SourceLevel:run is iteratively performed on all source levels of the profile |
||
Profile Merger |
Merge profiles |
premerge |
Before merge is run |
postmerge |
After merge is run |
||
Profile Reshape |
Reshape profiles |
prereshape |
Before reshape is run |
postreshape |
After reshape is run |
||
Profile Renormalize |
Renormalize profiles |
prerenormalize |
Before renormalize is run |
postrenormalize |
After renormalize is run |
||
Profile Clip |
Clip profiles based on phase start and end dates |
prephaseclip |
Before phaseClip is run |
postphaseclip |
After phaseClip is run |
||
Profile Approval |
Automatic approvals of profiles |
preapprove |
Before approve is run |
postapprove |
After is approve run |
The hooks listed in "Hooks" are defined in the appcust.xml file. For the setup directory of each domain, appcust.xml must be included.
The format of the RDF appcust.xml file is shown in Figure F-1.
The format of the Curve appcust.xml file is shown in Figure F-2.