...
All information that is required to be shown to user and that is needed for proper removing file from the processing queue is available on different steps of file routing. ORCH tables in PACE_MASTERDBO schema can be used to store this information in one place, which makes it easy to handle and update. The CorrelationID for stored information about a file is the same as used for trigger file name that ndfa sends to ndfa_exec, GUID with DATA suffix, i.e. B812JJ64DU6DEVPSDATA.
When the user queries data about all incoming files provided on the region (from EJM MT External Data tab) EJM MT shows data from ORCH_REQUEST_DEF and ORCH_QUEUE tables where ORCH_QUEUE.CREATE_DATE is within queried time interval and ORCH_REQUEST_DEF.CORRELATION_ID has ‘DATA’ as four last characters.
Data stored is:
- File correlation id – to correlate incoming file and all information about this file, same as signal correlation id.
- Remote file name – original file name of file.
- Added timestamp – timestamp of file acceptance on region. Combined with remote file name will allow user to understand what is this file, if it should or not be processed.
- Status – to store information about status of file processing, if file was acknowledged as file for some of workflows and pending for processing, if file was already processed, if file is not acknowledged as data for any workflow on region and if file processing was canceled before actual file load. Needed for user to be able to understand what happened with the file.
- Source signal correlation id – only for files that were created from incoming file as result of profile_executor processing.
- Process wrf + wrf + event names and process wrf + wrf + event corrIds for already processed files – information about procWrf/wrf/event that will process/already processed file. Needed for user to understand what will happen/what happened with file.
- Sent by – must store information about user who sent this file (if file was sent through MCC/MCE) or owner of the file (for instance sitesee adds itself as owner of the file to file properties) or profile under which this file was sent to processing
- Source file name – name of source file from which this file was generated – only for files that are created from external data as part of profile_executor processing.
- Consumed/cancelation timestamps – timestamps when file was processed or file record was deleted from queue for processing
- Cancelation correlation id – correlation id for RTR for removing file from queue for processing
- Canceled as child flag – if file was canceled as child of incoming file. For instance, if user sends incorrect SRM file that is processed in profile_executor workflow and creates GenericSMF and Rating files for profiled generic load user must be able to cancel all files that were created from source SRM file.
- isBundleTrigger flag – if file is bundle trigger and instantiated workflow
- triggeredWrofklowCorrId – correltation id of workflow that is triggered by this file if file is bundle trigger
- genericloadprofile – name of profile if file belongs to specific generic load profile
- ErrorDescr – detailted reason of failed/NACK status
- Queue instance – specifies to what queue file belongs to.
PossibleScenarios
...
In this section:
| Child pages (Children Display) | ||
|---|---|---|
|