Staging Database
You can perform data subset operations in a Data Masking task. H2 is a database that you use to stage subsets of data.
The Data Masking task uses the H2 database to stage record IDs, data subset for simple entities, entities with junction objects, multipath relationships, and lookup based relationships, and masking fields.
The H2 staging database installer is packaged with the Secure Agent. You can run the H2 package installer to install the staging connection. You can either start the staging database connection automatically from the Schedule page, or manually run the H2 startup script.
You can view the subset record count in the logs. The task reads the record IDs that are selected for subset from the staging database and uses standard API to read those records from the source. The task uses standard or bulk API to load data into the target.
Configure Staging Connection
You can start the staging database connection from the Schedule page before you run a Data Masking task.
Select a Secure Agent and start the staging database service. The task uses the staging database to store the data during the subset operations.
The following image shows the staging connection details:
You can view the JVM type and configure the JVM heap size for a staging connection. The JVM type specifies the type of JVM that the staging database uses. The JVM heap size specifies the heap memory for the staging database. Configure the JVM heap size to process large amount of data in the staging database in a short time. JVM type can be of 32-bit or 64-bit. When the JVM type is 32-bit, the default maximum heap size is 512 MB. When the JVM type is 64-bit, the default maximum heap size is 4096 MB. You can increase or decrease the heap size based on the amount of memory that the system can support.
You can select a Secure Agent and stop the staging database service.
H2 Database Requirements
You must consider the maximum file size of the file system, cache size, and heap size when you configure the H2 database.
The H2 staging database has the following requirements:
Installing and Configuring H2 Database Manually on Windows
After you install the Secure Agent, you must run the H2 staging database installer that is packaged with the Secure Agent. In Informatica Cloud, you must create a connection to connect to the H2 database.
1. Browse to the following location:
<Secure Agent installation directory>\apps\Data_Integration_Server\$version\ICS\main\tomcat\cmask
2. Run the h2_start.bat startup script.
The database starts up and the Command Prompt displays the parameters that you need to configure the connection in Informatica Cloud. Keep the Command Prompt open.
3. Log in to Informatica Cloud.
4. Click Configure > Connections.
The Connections page appears.
5. Click New.
The New Connection page appears.
6. Enter the connection name for the H2 database.
Connection names are not case sensitive. Connection names can contain alphanumeric characters, spaces, and the following special characters:
_ . + -
7. Optionally, enter a description for the connection. Maximum length is 255 characters.
8. Select the JDBC_IC (Informatica Cloud) connection type.
The JDBC_IC connection properties appears.
9. Enter the Secure Agent group that runs the Data Masking task.
10. Enter the JDBC Connection URL that appears in the Command Prompt.
11. Enter the path to the JDBC jar directory that appears in the Command Prompt.
12. Enter the database schema.
13. Enter the user name and password that appears in the Command Prompt to connect to the H2 database.
14. To test the connection, click Test.
15. To create the connection, click OK.
The H2 database connection appears on the Connections page.
Installing H2 Database Manually on Linux
You can install H2 database on Linux and configure the connection in Informatica Cloud.
Provide read, write, and execute access to the following directory:
<Secure Agent installation directory>\apps\Data_Integration_Server\$version\ICS\main\tomcat\cmask
1. Browse to the following location:
<Secure Agent installation directory>\apps\Data_Integration_Server\$version\ICS\main\tomcat\cmask
2. To run the H2 startup script, enter the following command:
nohup sh h2_start.sh &
The H2 database starts up and lists all the parameter values that you need to configure the connection in Informatica Cloud.
Note: To stop the database, identify the process ID and enter the following command:
ps -ef | grep "h2", kill -9 processid
3. To view the parameter values, open nohup.out file in a text editor or run the following command:
vi nohup.out
4. Log in to Informatica Cloud.
5. Click Configure > Connections.
The Connections page appears.
6. Click New.
The New Connection page appears.
7. Enter the connection name for the H2 database.
Connection names are not case sensitive. Connection names can contain alphanumeric characters, spaces, and the following special characters:
_ . + -
8. Optionally, enter a description for the connection. Maximum length is 255 characters.
9. Select the JDBC_IC (Informatica Cloud) connection type.
The JDBC_IC connection properties appears.
10. Enter the Secure Agent group that runs the Data Masking task.
11. Enter the JDBC Connection URL that appears in the nohup.out file.
12. Enter the path to the JDBC jar directory that appears in the nohup.out file.
13. Enter the database schema.
14. Enter the user name and password that appears in the nohup.out file to connect to the H2 database.
15. To test the connection, click Test.
16. To create the connection, click OK.
The H2 database connection appears on the Connections page.
