Configuration (.cfg) files are not created under the Native Engine EAR during a Microsoft Windows cluster deployment

Resolving The Problem

For each cluster member that is missing .cfg files, use these steps to manually create the files.

1. Go to the <WAS_HOME>/profiles/<PROFILE_NAME>/installedApp/<CELL_NAME>/MDM-native-<INSTANCE_ID>.ear/native.war/conf directory.

2. Create a file called 'com.ibm.mdm.mds.search.index.cfg' with the following content:
indexDir=<WAS_HOME>/profiles/<PROFILE_NAME>/installedApp/<CELL_NAME>/MDM-native-<INSTANCE_ID>.ear/native.war/index

3. Create a file called 'com.ibm.mdm.mds.entity.manager.cfg' with the following content:
relationshipLinkerEnabled=true
enableGroupProcessing=false

4. Create a file called 'com.ibm.mdm.mds.event.manager.cfg' with the following content:
enableAutoSuspension=false
enableGroupProcessing=false

5. Create a file called 'com.ibm.mdm.mds.jdbc.cfg' with the following content:
user=<DB_USER>
dynamicSections=1000
password=<DB_PASSWORD>
className=com.ibm.mdm.jdbc.DB2DataSource (for DB2 and DB2Z)
className=com.ibm.mdm.jdbc.OracleDataSource (for Oracle)
className=com.ibm.mdm.jdbc.SQLServerDataSource (for SQL Server)
portNumber=<DB_PORT>
databaseName=<DB_NAME>
serverName=<DB_HOST>

6. Create a file called 'com.ibm.mdm.mds.jni.cfg' with the following content:
MAD_DBTYPE=DB2 (for DB2)
MAD_DBTYPE=DB2Z (for DB2Z)
MAD_DBTYPE=ORACLE (for Oracle)
MAD_DBTYPE=MSSQLU (for SQL Server)
MAD_CONNSTR=DSN\=<DB_NAME>_<INSTANCE_ID>;UID\=<DB_USER>;PWD\=<DB_PASSWORD>;
MAD_ROOTDIR=<WAS_HOME>/profiles/<PROFILE_NAME>/installedApp/<CELL_NAME>/MDM-native-<INSTANCE_ID>.ear/native.war
MAD_SMTLIST=<LOCALE_LIST> (use comma as the seperator)

7. Create a file called 'com.ibm.mdm.mds.job.manager.cfg' with the following content:
workDir=<WAS_HOME>/profiles/<PROFILE_NAME>/installedApp/<CELL_NAME>/MDM-native-<INSTANCE_ID>.ear/native.war/work

8. Create a file called 'com.ibm.mdm.mds.messages.cfg' with the following content:
smtCodeList=<LOCALE_LIST> (use comma as the seperator)

9. Create a file called 'com.ibm.mdm.mds.net.logic.cfg' with the following content:
contextPoolSize=10

10. After all .cfg files are created for all cluster members, restart the cluster.