Prerequisites¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
Network Configuration¶
Open outbound TCP port 50000 to the DB2 Database(default). (DB2 instances can listen on non-standard ports. Open the appropriate outbound TCP ports from the Alation server.)
Service Account¶
The DB2 service account is a Linux account. When the account is created, grant it the required permissions to access the database and perform MDE, profiling, and QLI.
Example SQL to create an account:
group -g 999 db2iadm1
useradd -u 1004 -g db2iadm1 -m -d /home/alation alation
password alation
Example SQL to grant database access to the account:
Enable a new user to connect to database
GRANT CONNECT ON DATABASE TO alation;
This grants `alation` access to all data
GRANT DATAACCESS ON DATABASE TO alation;
Permissions for Metadata Extraction:
GRANT SELECT ON QSYS2.SYSSCHEMAS TO alation;
GRANT SELECT ON QSYS2.SYSTABLES TO alation;
GRANT SELECT ON QSYS2.SYSCOLUMNS TO alation;
Permissions for Sampling and Profiling:
For profiling, the service account requires the SELECT permission on tables that you want to sample.
Permissions for Query Log Ingestion:
See QLI Configuration on DB2 below
JDBC URI:
Format as400://<hostname_or_ip>:<port>/<service_name>
Example as400:/my_ibm.net:50000/TESTDB
ACS Customers¶
If you are an Alation Cloud Service customer, ensure you have Alation Agent installed and running. The Agent is mandatory for this connector in ACS deployments.
On-premise / Self-managed Alation Customers¶
Check Alation Connector Manager (ACM) is installed and running. ACM is mandatory for OCF connectors.