Problem: 

Currently the Run-Time Knowledge Base needs to be created within the  source data store(s). This database drives the operation and performance of Data Express' masking and subsetting processes. The Run-Time Knowledge Base consists of tables and indexes, and needs to be created using the schema name DEKB. As the creation requires this new schema to be in the source data store, sometimes that causes problems in the production’s integrity. 

Resolution: 

The solution  is applicable only for ODBC Extension.   

To define a connection to a centralized knowledge base  the hdblayer approach is implemented.  Data Express has to be configured so that it can access the data store housing the metadata by editing a new configuration file similar to hdblayer.ini and named hkblayer.ini, which will be located within the executables directory of the ODBC Extension installation. Edit the information in the file as follows:

RDBMS = ConnectionType

DBNAME = ConnectionAlias

DBOWNER = TableOwner

USER = UserID

PSWD = Password

where: 

• ConnectionType: Set to ODBC for the ODBC Extension. 

• ConnectionAlias: Set to the data store containing the knowledge base tables. For the ODBC Extension, this is the data source name (DSN).

• TableOwner – The table qualifier for the knowledge base tables.

• UserID & Password – The connection criteria for the data store containing the knowledge base tables.

For example:

RDBMS = ODBC

DBNAME = MYDSN

DBOWNER = MYOWNER

USER = MYUSER

PSWD = MYPASSWORD

After configuring the hkblayer.ini file perform the command below from within the executables directory of the ODBC Extension installation:

dxeencrypt  hkblayer   

It will generate the HKBLAYER.rc file.    

Note that in case the new configuration file does not exist (or it  contains  a specified content, like *DEFAULT: still to be decided) the behavior will be the current one.