IBM InfoSphere Master Data Management, Version 11.3

Deploying the InfoSphere MDM pattern for DB2 pureScale or IBM PureData System for Transactions

You can deploy the InfoSphere® MDM pattern for IBM® DB2® pureScale® or IBM PureData™ System for Transactions with the IBM PureApplication® System workload console or IBM Workload Deployer.

Before you begin

Note: This pattern can be modified to allow you to deploy InfoSphere MDM on remote DB2 for Linux, UNIX, and Windows. To enable this deployment type, you must modify the supplied pattern to remove the MDM Fixup for pureScale script.

Before you can deploy this InfoSphere MDM pattern, you must have already completed the steps that are described in Preparing to deploy InfoSphere MDM patterns.

Remember: If your deployment uses LDAP authentication, your WebSphere® Application Server administrative user name must be authenticated by the LDAP server before you deploy the pattern.

Procedure

Log in to the IBM PureApplication System workload console or IBM Workload Deployer.
Click Patterns > Virtual Systems.
In the Virtual System Patterns list in the left pane, type MDM in the Search field to filter the list to show only InfoSphere MDM patterns.
Select the MDM for DB2 on LUWPure_<version> pattern.
If you have not yet accepted the license terms for this pattern, scroll down to the License status in this pattern section below the deployment diagram. Review the relevant license agreements and click Accept to accept the terms.
Click Deploy. A dialog opens for you to provide the details of the InfoSphere MDM instance that you are deploying.
In the Virtual system name field, provide a unique system name for your InfoSphere MDM instance.
Click Choose environment.
Choose the IP version that your instance uses: IPv4 or IPv6.
Choose whether you want to deploy InfoSphere MDM in either a cloud group or a previously defined environment profile.
If you want to schedule specific start or end times for this instance deployment, click Schedule deployment, then define the start and end times.
Note: By default, the pattern will deploy immediately after you complete the setup, and then run indefinitely.
If you want to configure default passwords to use for all root and virtuser user IDs, click Default password for all virtual parts (optional), then provide default password values.
Click Configure virtual parts > Deployment manager to configure the deployment manager.
Define the parameters of the deployment manager:
Name

A unique name that is assigned to the deployment manager. This value cannot be changed.

Virtual CPUs

The number of virtual processors that the ESX server allocates for the virtual machine.

Memory size (MB)

The amount of RAM that the ESX server allocates for the virtual machine. Define a size that works best for your deployment environment. For many InfoSphere MDM deployments, the optimal size is 8000 MB (8 GB).

Reserve physical CPUs

The physical processor capacity that the ESX server reserves for the virtual machine.

Reserve physical memory

The amount of physical memory that the ESX server reserves for the virtual machine.

Cell name

The name of the cell that the Workload Deployer creates. A cell is a logical group of nodes on the same network.

Node name

The name of the node. A node is a logical group of application servers that are configured on the same machine.

Features

A feature pack is used to deliver new capabilities before the next major release of a product. Choose either none or xc10. The xc10 option enables your application to connect and use shared caching service capabilities.

WebSphere Repository Location

The location of the WebSphere Application Server Installation Manager repository.
Note: This is an optional parameter.

WebSphere Repository User

The user of the WebSphere Application Server Installation Manager repository.
Note: This is an optional parameter.

WebSphere Repository Password

The password for the WebSphere Application Server Installation Manager repository user.
Note: This is an optional parameter.

Verify Password

Verification of the password for the WebSphere Application Server Installation Manager repository user.
Note: This is an optional parameter.

Password (root)

The root password for the virtual machine.

Verify password

Verification of the root password for the virtual machine.

WebSphere administrative user name

The user for the WebSphere Application Server administrative console.
Note: If your deployment uses LDAP, the WebSphere Application Server administrative user name must be authenticated by the LDAP server before you deploy the pattern.

WebSphere administrative password

The password for the WebSphere Application Server administrative console user.

Verify password

Verification of the password for the WebSphere Application Server administrative console user.

CLUSTER_NAME

The name of the InfoSphere MDM cluster.

SERVER_NAME

The name of the InfoSphere MDM instance.

RemoteDatabase_HostIP

The host name or IP address of the machine that hosts the remote DB2 database for this InfoSphere MDM instance.

RemoteDatabase_Port

The service port of the remote DB2 database for this InfoSphere MDM instance.

RemoteDatabase_Name

The name of the remote DB2 database for this InfoSphere MDM instance.

DB2SchemaName

The DB2 schema name.

SIBSchemaName

The schema name for the Service Integration Bus (SIB) messaging tables to use to access the DB2 tables.

databaseUser

The user that InfoSphere MDM uses to connect to the database when creating tables, triggers, indexes, and other database objects.

databasePassword

The password for the user that is defined in databaseUser.

Verify password

Verification of the password for the user that is defined in databaseUser.

MESSAGING_HOST

The host name of the remote WebSphere Message Queue.

MESSAGING_HOME

The home directory for the remote WebSphere Message Queue.

MESSAGING_QMANAGER

The manager of the remote WebSphere Message Queue.

MESSAGING_PORT

The port that is used by the remote WebSphere Message Queue.

MESSAGING_CHANNEL

The channel of the remote WebSphere Message Queue.

MESSAGING_USER

The remote WebSphere Message Queue user.

MESSAGING_PASSWORD

The password that is used by the remote WebSphere Message Queue user.

Verify password

Verification of the password value that is defined in MESSAGING_PASSWORD.

WAS_APPLICATION

The application name of the WebSphere Application Server instance.

ENGINE_TYPE
The matching engine that is used by InfoSphere MDM physical MDM features such as suspected duplicate processing. Type one of the following values:
- DME - use the deterministic matching engine (known as the MDM Classic Matching Engine).
- PME - use the MDM Probabilistic Matching Engine.
MTZ_FLAG

Determine whether this InfoSphere MDM instance uses the physical MDM Multi Time Zone feature (true or false).

MDM_INSENSITIVE_SEARCH
Determines whether physical MDM features can perform non-case-sensitive searches. Type one of the following codes:
- false - use only case-sensitive searches
- true - enable non-case-sensitive searches
MDM_TRIGGER_TYPE
The style of history triggers for this InfoSphere MDM instance. Type one of the following values:
- None
- Simple
- Compound
MDM_CUSTOMER_LANG
The language code that defines the default language for this InfoSphere MDM instance. Type one of the following allowed codes:
- de for German
- el for Greek
- en for English
- es for Spanish
- fr for French
- it for Italian
- ja for Japanese
- ko for Korean
- pl for Polish
- pt_BR for Brazilian Portuguese
- ru for Russian
- tr for Turkish
- zh_CN for Simplified Chinese
- zh_TW for Traditional Chinese
MDM_TRIGGER_DELETE_TYPE
The style of delete triggers for this InfoSphere MDM instance. Type one of the following values:
- None
- Simple
- Compound
MDM_CODE_LANG_LIST
The comma-separated list of languages that are supported by the physical MDM code tables in this InfoSphere MDM instance:
- de for German
- el for Greek
- en for English
- es for Spanish
- fr for French
- it for Italian
- ja for Japanese
- ko for Korean
- pl for Polish
- pt_BR for Brazilian Portuguese
- ru for Russian
- tr for Turkish
- zh_CN for Simplified Chinese
- zh_TW for Traditional Chinese
MDM_DATA_TYPE
The type of industry data that this InfoSphere MDM instance is used for. Type one of the following values:
- Insurance
- Banking
- Telecommunication
- Manufacturing
MDM_USER

The MDM user for administering the InfoSphere MDM application through the WebSphere Application Server admin console. The default value is mdmadmin.

MDM_PASSWORD

The password for the MDM user that is defined in MDM_USER.

Verify password

Verification of the password for the MDM user that is defined in MDM_USER.

MTZ_TIMEZONE

The time zone for this InfoSphere MDM instance. When the Multi Time Zone feature is enabled, this value should match the time zone identifier for the MDM Database. The default value is EST5EDT (Eastern Standard Time).

LDAPHost

The LDAP server host name.

LDAPPort

The LDAP server port number.

LDAPId

The LDAP ID.

serverType

The type of LDAP server, such as IBM Tivoli® Directory Server or Microsoft Active Directory.

baseDN

The Base Distinguished Name.

bindDN

The Bind Distinguished Name.

bindPassword

The password of the Bind Distinguished Name.

Verify password

Verification of the Bind Distinguished Name password.

pureScaleDatabasePassword

The password for the database on DB2 pureScale or PureData™ Systems for Transactions. This parameter is part of the MDM Fixup for pureScale script package, and is only necessary when you are using DB2 pureScale or PureDataSystems for Transactions.

Verify password

Verification of the password value that is defined in pureScaleDatabasePassword.

USERNAME

The username that is used by the DB2 remote client installation. The default value is db2inst1.

PASSWORD

The password that is associated with the user for the DB2 remote client installation.

Verify password

Verification of the password for defined by the PASSWORD value.
Click OK to accept this deployment manager configuration.
Click Configure virtual parts > Custom nodes to configure custom nodes, if necessary for this deployment.
Define the parameters of the custom nodes:
Name

A unique name that is assigned to the custom node. This value cannot be changed.

Virtual CPUs

The number of virtual processors that the ESX server allocates for the virtual machine.

Memory size (MB)

The amount of RAM that the ESX server allocates for the virtual machine.

Reserve physical CPUs

The physical processor capacity that the ESX server reserves for the virtual machine.

Reserve physical memory

The amount of physical memory that the ESX server reserves for the virtual machine.

Node name

The name of the node. A node is a logical group of application servers that are configured on the same machine.

WebSphere Repository Location

The location of the WebSphere Application Server Installation Manager repository.
Note: This is an optional parameter.

WebSphere Repository User

The user of the WebSphere Application Server Installation Manager repository.
Note: This is an optional parameter.

WebSphere Repository Password

The password for the WebSphere Application Server Installation Manager repository user.
Note: This is an optional parameter.

Verify Password

Verification of the password for the WebSphere Application Server Installation Manager repository user.
Note: This is an optional parameter.

Password (root)

The root password for the virtual machine.

Verify password

Verification of the root password for the virtual machine.

WebSphere administrative user name

The user for the WebSphere Application Server administrative console.

WebSphere administrative password

The password for the WebSphere Application Server administrative console user.

Verify password

Verification of the password for the WebSphere Application Server administrative console user.

RemoteDatabase_HostIP

The host name or IP address of the machine that hosts the remote DB2 database for this InfoSphere MDM instance.

RemoteDatabase_Port

The service port of the remote DB2 database for this InfoSphere MDM instance.

RemoteDatabase_Name

The name of the remote DB2 database for this InfoSphere MDM instance.

DB2SchemaName

The DB2 schema name.

SIBSchemaName

The schema name for the Service Integration Bus (SIB) messaging tables to use to access the DB2 tables.

databaseUser

The user that InfoSphere MDM uses to connect to the database when creating tables, triggers, indexes, and other database objects.

databasePassword

The password for the user that is defined in databaseUser.

Verify password

Verification of the password for defined by the databasePassword value.

USERNAME

The username that is used by the DB2 remote client installation. The default value is db2inst1.

PASSWORD

The password that is associated with the user for the DB2 remote client installation.

Verify password

Verification of the password for defined by the PASSWORD value.
Click OK to accept this custom node configuration.
Click OK to deploy this pattern as a new InfoSphere MDM instance.
After the pattern deploys, you must enable the InfoSphere MDM Management Console and Management Agent for IBM PureData deployments:
1. Open the deployed Management Agent policy file, <MDM_INSTALL_HOME>/ManagementAgent/config/mgmt_agent.policy.
  Note: The InfoSphere MDM Management Agent is located on a WebSphere Application Server deployment manager (DMGR) virtual machine. The default location is /opt/IBM/MDM/server/ManagementAgent/config/mgmt_agent.policy.
2. Edit the mgmt_agent.policy file so that it includes references to all hosts that are part of this IBM PureData deployment.
  For example, if PureData is installed on three virtual machines with the host names host01.example.com, host02.example.com, and host03.example.com, then the mgmt_agent.policy file should include the following entries:
```
permission java.net.SocketPermission "host01.example.com", "accept, connect"; 
permission java.net.SocketPermission "host02.example.com", "accept, connect"; 
permission java.net.SocketPermission "host03.example.com", "accept, connect";
```
3. Save your changes.

What to do next

By default, the user name and password values that you define during deployment for the WebSphere administrative user name field is also used for several other user IDs:

InfoSphere MDM application security user
InfoSphere MDM application security client
Administration application client user
Data Stewardship client user credentials
Product User Interface client user

After InfoSphere MDM is installed, you can set up different users for these different applications. For more information, see the WebSphere Application Server documentation.

Tip: The parameters that you define during pattern deployment are used to generate an InfoSphere MDM silent installation response file. If necessary, you can edit the response file that is generated during the pattern deployment and then rerun the silent installation.

Last updated: 27 June 2014