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.
|Table of contents|
|Package execution start|
|Package execution process|
|Package execution history|
Registered package contains:
Figure 1: Package details
After click on the red play button on the Package details screen, a pop-up wizard for configuring package execution is displayed. In the first step, it is necessary to select the restartability mode and the package version. The restartablity mode must be configured before the package is published and registered.
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 2: Package execution start - step 1
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 3: Package execution start - step 2
The last step of the wizard determines the values of the parameters defined in BizDataX Designer.
Figure 4: Package execution start - step 3
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 5: Package execution process - details
Figure 6: Package execution process - errors
Figure 7: Package execution process - logs
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.
The iterator statuses are:
Figure 8: Step - iterator performance
Figure 9: Step - engine performance
By selecting Package 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 10: 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.