Configuring the MDM Connector's Security Collection
The MDM Standard Edition Security collection crawls the groups and associated ACLs in IBM Master Data Management Standard Edition. Configurable options for this collection are the following:
- Database Host - The host name or IP address of the MDM (database) server
- Database JDBC Port - The port number to use when connecting to the MDM server's database using JDBC
- JDBC Username - The user that will be used when openiong the KDBC connection and crawling the groups and ACLs on the MDM server. This user must have read access to data in MPI_GRPHEAD, MPI_GRPXSEG, MPI_SRCHEAD, MPI_SEGATTR, MPI_MEMTYPE, MPI_GRPXCVW, and MPI_CVWHEAD.
- JDBC Password - The password to use when opening the JDBC connection to the MDM server
- Database Name - The name of the database containing the MDM data
- Database Type - The type of database the MDM server uses. This is either db2 or oracle.
Advanced JDBC Options
- JDBC Connection String - Specifying a value in this field enables you to override the
default (generated) JDBC connection string, providing a new JDBC connection URL for the MDM server's
database. The database must be accessible from the Watson™ Explorer Engine server. Any value that you
specify in this field will be similar to:
- JDBC Class - Specifying a value in this field enables you to override the default JDBC Driver class. The jar files associated with any class that you specify must be located in the lib/java directory (or otherwise added to the classpath).
- Composite Views SQL Query - Specifying a value in this field enables you to override the default SQL query used to create groups' composite view ACLs. (The default query can be found within this seed's XML.)
- Attributes SQL Query - Specifying a value in this field enables you to override the default SQL query used to create groups' attribute ACLs. (The default query can be found within the seed XML.)
- Maximum java heap size - The maximum size of the Java heap. Specify the heap size using the same format when using the -Xmx argument to the java command (512m for 512 megabytes, 2g for two gigabytes, etc). Values less than 160m are ignored.