Deploying the MDM Native Component feature on remote Windows server

The Master Data Management Native Component feature is the ODBC data source that virtual MDM configurations require to operate successfully.

About this task

If you are planning to install the MDM operational server and implement a virtual MDM configuration on a WebSphere® Application Server cluster and a Microsoft Windows operating system, there are steps that you must take after you install your operational server.

The installer automatically runs the madconfig create_datasource target to create an ODBC data source on a remote server by using an ANT agent. However, the ANT agent does not have permission to modify the Windows registry.

If you are running IBM® Installation Manager and WebSphere Application Server deployment manager on machine A and must deploy your operational server and virtual configuration to managed nodes on other machines (for example B, C, and D), use this procedure. This procedure manually creates the ODBC data source on each of the remote Windows servers after you first run IBM Installation Manager to install your operational server.

Procedure

  1. Run IBM Installation Manager on machine A and install the MDM operational server.
  2. On machine B, go to your <WAS_PROFILE_HOME>\installedApps\<YOUR_CELL_NAME>\<MDM-native-IDENTIFIER>.ear\native.war\scripts directory.
  3. Open a command-line prompt.
  4. Type this command: madconfig.bat register_odbc.
  5. Type this command: madconfig.bat create_datasource -Dmad.db.type=DBTYPE -Dmad.db.name=DBNAME -Dmad.db.port=DBPORT -Dmad.db.host=DBHOST -Dmad.db.dsn=DSN
    Where:
    • DBTYPE: is your database type; specify DB2, ORACLE, or MSSQLU on machine B
    • DBHOST: is your database host name or IP address on machine B
    • DBPORT: is your database port on machine B
    • DBNAME: is your database name on machine B, for example mdmins11
    • DSN: the data source name; DSN naming convention is <DB_NAME>_<MDM_INSTANCE_IDENTIFIER>. <MDM_INSTANCE_IDENTIFIER>. must match the MDM application name value that you entered on the Application Configuration panel during installation on machine A.
  6. Repeat steps 2 - 5 for each additional machine in your cluster (for example, C and D).