Working with Packages and Configurations


One of the important BizDataX features is the ability to allow central management of many different BizDataX Packages. One reason for that is the fact that systems implemented to support many day-to-day processes differ significantly. Some require nothing but the real data while others are able to function with heavily distorted and randomized data. Different transformations could be used to produce anonymized/masked data for different usage scenarios. Also, data is typically stored in many different data stores and sometimes it is practical to be able to transform data step by step or system by system, using the “divide and conquer” approach. I.e. it may be easier to subset, transfer, clean and standardize as the first step and then do the core masking after that.

BizDataX Package represents an implementation of data transformation logic. BizDataX Configuration is the term we use when talking about metadata such as connection strings and other configuration parameters needed to execute the logic, information about schedules or history of executions, notification settings, monitoring options etc. Initial configuration is created when a package is registered with a central management service (Alternatively, package is registered when it is published from BizDataX Designer, see Publishing Workflow to Runtime). Details are then set via BizDataX Management Console. BizDataX Runtime transforms data by using the logic defined in a package and according to settings defined in a configuration. The package can access certain information from the configuration during execution, e.g. connection strings.




Figure 50: Managing multiple package configurations with BizDataX Runtime

Each configuration refers to a single package and provides information about configurable options for the package. One can define multiple configurations for a package (same package can be registered multiple times) to use the same data transformation logic with different configuration options. E.g. one can easily use the same package to execute a data masking of data stored in different databases by just using different connection string settings in configurations.

package groups


Figure 51: Package configurations organized in groups into a hierarchical structure

The BizDataX MC displays details about package structure under the Process structure node. Process structure is inferred from the package during the registration process. The level of details displayed depends upon how package structure was defined during the design phase. E.g. if data masking steps were used extensively, more details about the structure would be displayed.


package structure

Figure 52: Inspecting package structure

Arguments can be defined in a scope of a package or in scopes of individual steps. Configuration table displays only package-scoped arguments when a package node is selected and only step-scoped arguments when a step node is selected in console tree.

configuration parameters

Figure 53: Using BizDataX Management Console to manage package configuration parameters