Understanding the Architecture

Mon, 01 Jan 0001 00:00:00 +0000

The architecture for the DB2 Database Protector is depicted in the image below.

Component	Description
RPAgent	A daemon running on each node that downloads the package from the ESA over a TLS channel using the installed Certificates.
Log Forwarder	A daemon running on each node that routes the audit logs and application logs to the ESA/Audit Store.
config.ini	A file on each node containing the set of configuration parameters to modify the protector behavior.
DBP Layer	Contains the Database Protector UDFs and APIs.
Core	The set of various libraries that provide the Protegrity Core functionality.

Verifying the System Requirements

Mon, 01 Jan 0001 00:00:00 +0000

Ensure that the following prerequisites are met:

The DB2 Database is installed and configured.
Enterprise Security Administrator (ESA) is installed, configured, and running.
The IP address or host name of the ESA is noted.
The Policy Management (PIM) module is initialized on ESA. The initialization of PIM ensures that cryptographic keys for protecting data and the policy repository are created.
Download and save the DB2 Database Protector, DatabaseProtector_Linux-ALL-64_x86-64_DB2-ALL-64_<DBP_version>.tgz, made available by Protegrity.
Backup the databases where the DB2 Database Protector and UDFs would be installed.
Access to the database server as the sudo access user is available. This permission is required to install all the components.
Access to the DB2 database as the database user is available.
The following permissions are available to the user and group to install and uninstall the UDFs:
- GRANT DBADM ON DATABASE TO USER <user_name>;
- GRANT DBADM ON DATABASE TO GROUP <user_name>;
- GRANT CONNECT ON DATABASE TO USER <user_name>;
- GRANT CREATEIN, ALTERIN, DROPIN ON SCHEMA PTY TO USER <user_name>;
- GRANT ACCESSCTRL ON DATABASE TO USER <user_name>;