Jake 11.27 note - info taken from below:
\\thenest\users\jmathews\DOC Team\RDC_PRICING CENTER\JIRAs\DOC-1625_Engine Processing
The ultimate goal of RDC Prices is to produce Gold Copy Price records for a given effective date and a fixed set of securities out of raw prices received from multiple vendors, or by using prior day Gold Copy prices. To achieve this goal, RDC Prices uses Data Strategies, and the concepts of a Main Engine and Rule Engines.
Is it ok to use H2’s and H3’s for the below sections? Or is there a standard for detailing the sections
Data Strategies
Data Strategies are composite data processing rules made up of Processing Rules. Data Strategies are applied at an individual security level, while Processing Rules are defined based on individual data fields. Data Strategies work by processing activity through the below phases:
...
Interpret data strategy security criteria to produce a list of security aliases subject to processing
Determine which Data Strategy phases to be executed. For example, Demand, Validation, or Composite.
Launch Rule engines for each phase, using a predetermined order
Perform necessary rule engine synchronizations
Exception handling and cleanup
A typical set of input parameters includes data strategy identification, effective date, and the list of requested phases.
Main Engine – that Main Engine kicked off and interprets the Data Strategy criteria, produces a list of securities, filters down from holdings, then determines which phase needs to be run – i.e. Demand, Validation, or Composite.
So, for example, if you had 11K securities – recommendation across RDC to process 5K at a time. So if the Main Engine kicked off and goes through to find 11K securities, it would then kick off 3 Rule Engines. Rule Engines are responsible for a specific phase against that subset of security aliases. Maximum number of securities processed by a single rule engine is configured through system configuration. One Rule Engine processes one Validation rule per Data Strategy.
Rule Engine
The Rule engines execute specific phases of a data strategy on a limited set of securities. A typical data strategy can include an unlimited number of securities, but each rule engine only operates on a subset with a size that does not exceed the configured maximum. The number of Rule engines required for each phase is determined by the following factors:
...
A typical set of input parameters includes data strategy identification, effective date, specific phase identification, and a security alias selector. The security alias selector is either a range of security aliases, or a list of values.
Jake note - would it help to have an example here, or reference the system configuration that determines the maximum number of securities processed by a single rule engine?
Add label