All previous package executions can be viewed on Package execution history overview list. It contains a table with name of user who made changes, process status and Date and time process started and ended.
|Table of contents|
|Package execution information|
|Package execution process|
|View package execution history|
After package registration on the BizDataX Portal, the registered package can be executed.
Except on the BizDataX Portal, the package can be executed from Visual Studio (Debug -> Start Debugging (or press F5) or from the command line.
After selecting on Package execution button on the View package details screen, a new screen for configuring package execution is displayed. It is necessary to select:
If the package originated from the same Visual Studio project, ie. was published several times, this means that it appears on the BizDataX Portal in as many packages/versions as it is published, otherwise, the package execution will fail is some mode different than
Off is used.
Figure 1: Package execution information
There are no registered iterators in the next step because this package was not previously run through the Portal. Iterators are registered in the BizDataX Portal database when running packages in some of the restartability modes. Each step, partition, and segment defined in BizDataX Designer is registered as an iterator during package execution so the next package execution takes into account only non-finished iterators that the user would specify to execute in this step of the wizard.
Figure 2: Package execution - Iterator control
The last step of the wizard determines the values of the parameters defined in BizDataX Designer.
Figure 3: Package execution parameters
To confirm execution select Confirm button. To cancel execution select Cancel button.
After confirmation, a new page with details about the execution process will be shown. On this page a few blocks appear:
Execution can end as:
After successful package execution, the progress bar will be set on 100%, Logs will be created and Execution steps and Table performance will be filled with values for executed steps and masked tables. Execution errors should be empty if everything finished without errors or filled with message errors which should be checked.
Figure 4: Package execution process - Logs
Figure 5: Package execution process - Execution parameters
Figure 6: Package execution process - Errors
Each step can have multiple iterators where the performance of each of the iterators is monitored by recording the start and end of iterator execution, how many records are processed, how many records are processed per second, and to which engine each iterator belongs.
The step can end as:
truein the BizDataX Designer properties for the belonging masking engine of that step.
falsein the BizDataX Designer properties for that step.
To see Iterators and Engines, on tab Execution summary select Step. To see Details, Errors and Logs select on Execution summary.
Figure 7: Step - iterator performance
The iterator statuses are:
Figure 8: Step - engine performance
By selecting Execution history on the Packages list for the selected package or on the Package details screen, a list of executions for the selected package appears.
Figure 9: Package execution history
With selecting a specific item from the list, Process details for the selected Package execution appear. Process details are the same as details on the package execution process.
On right upper corner there is the Advanced options button, where you can filter view of Execution history overview list.
Figure 10: Advanced options
User can choose options to filter data in the overview:
To clear all inserted filters in Advanced options, choose Clear button.
To apply inserted filter data in Advanced options, choose Commit button. A filtered data view will be displayed in the table.
To cancel changes in Advanced options, choose Cancel button.
When executing Package system opens Package execution details screen where user can track the current execution or view the previous executions history.
Figure 11: Package execution history details