Scheduling and Run time parameters
Hi,
We have installed Data3Sixty Analyze and trying to import legacy LAE graphs into it.
While I am trying that, I see there are options to provide "Run Properties" and to "Schedule" it in Data3SixtyAnalyze.
Currently in LAE, we have jobs scheduled through crontab and the run properties are provided as part of the configuration file. And Many file operations are performed through shell script and some values are exported from shell script before we actually run the "BRX" .
How can this be accomplished in Data3SixtyAnalyze ? i.e. if we want to run the process only after certain file operations or exporting values from shell script..?
Kindly advise
-
Data3Sixty Analyze does not support the execution of a BRX from a script.
When using the Data3Sixty Analyse Server editions you can leverage the Analyze REST API e.g. using the API to run a simple scheduled task
See the System administration > API developer documentation section of the Server editions' Help for details of how to authenticate and create a scheduled task with specified run properties, manage and run simple scheduled tasks using the Analyze REST API.
-
Hi Adrian,
Thank you for your time and reply. I think I didn't put my question right.
Currently in LAE, before we kick off BRX -we do several file operations or checks using shell script etc...then we run the brx.
Now in Data3SixtyAnalyze, since the schedule is completely on the Web Client, how can we do those file operations/checks before we run a "Data Flow" ?
Also, we currently export several runtime parameters(like previous month, year, or different DB credentials etc ) to the brx, but in Data3SixtyAnalyze - I see we can provide run time parameters but I don't see where we can calculate parameters for running the Data Flow according to the varying inputs.
Thank you,
Nithya
-
There are no pre-compiled version of a graph (a BRX) in Data3Sixty Analyze.
Today you would need to use a driver data flow to calculate the values and then call the REST API from within the driver data flow and pass in the run property values in the API call.
Alternatively, you could re-work the data flow to build the checks in and calculate the values in-line within the data flow. However, in this case the values would not be available within the data flow as run properties (i.e. they would not be 'broadcast'/ available to any node via textual substitution.
We are considering a future enhancement to provide functionality equivalent to that delivered by the Execute BRX node - which would enable you to more easily chain data flow execution and support parameterization of the child data flow.
Please sign in to leave a comment.
Comments
4 comments