Virtual MDM configuration
Configuration of the virtual MDM is managed using a set of configuration files within the MDM_INSTALL_HOME/conf directory.
- Operational server configuration files
The operational server employs a Java-based service platform that allows for remote management. Operational server configuration variables are set within a set of configuration files maintained within the operational server instance WAS_PROFILE_HOME/conf directory in the application server. - Entity managers
You can configure your operational server to use an asynchronous entity management process or to use synchronous entity management. Before starting your installation, you might find it helpful to understand the difference between these two types of entity management. - Diagnostic logging
To provide diagnostic information for the operational server, you can use command-line utilities or take advantage of the native logging mechanism available with the application server. - Using the operational server utilities
There are a number of command-line utilities that are used with the operational server. These utilities are primarily used by the implementation and IBM® Software Support teams. Some of these utilities are also available as jobs in InfoSphere MDM Workbench. - Configuring SSL
By default, MDM operational server instances are not configured to use SSL communication. To configure SSL communication, you must complete this procedure. - Changing row-level locking isolation for a virtual MDM database on IBM DB2
The IBM InfoSphere Master Data Management operational server, implemented as either a virtual or hybrid configuration with a DB2® database, uses repeatable read isolation (RR) locks for all member updates. The RR setting can be changed to RS. - Setting a block value for sequence number generation
As part of a comprehensive performance tuning project, experienced MDM implementers can set a block value for sequence number generation. Each database access operation impacts system performance, and sequence number generation is one of the most common operations. To enhance performance by decreasing the number of database access operations, you can configure the operational server to cache block values for entrecno, memrecno, rellinkno, and tskrecno. Rather than accessing the database for each new record number, the next sequence number is retrieved from the cached values. The database is accessed only when all of the cached values are used. - Thread count settings
Service thread count settings are tuned during the implementation process to allow for determination of the best use of available resources. - MDM Standard Edition Memory Usage
Reading the details of memory usage for the MDM Standard Edition can help with performance improvements and with debugging. - Configuration for remote deployments
You can deploy the operational server to multiple hosts that are maintained by a single instance of the IBM WebSphere Application Server. If you do, ensure that virtual MDM configuration for all deployments remains in sync.
Last updated: 2 Nov 2018