IBM InfoSphere Master Data Management, Version 11.3

Deploying the basic InfoSphere MDM pattern for DB2 for Linux, UNIX, and Windows

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

Before you begin

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.

Procedure

Log in to the IBM PureApplication System workload console or IBM Workload Deployer.
From the menu bar, 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 Basic Pattern_<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 so that you can 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 will use: IPv4 or IPv6.
Choose whether you want to deploy InfoSphere MDM using 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 > DB2 Enterprise to configure the DB2 instance for this deployment.
Define the parameters of the DB2 instance:
Name

The name of this DB2 instance. This name is predefined and cannot be changed.

Virtual CPUs

The number of virtual processors that the ESX server allocates for this DB2 instance.

Memory size (MB)

The maximum memory size that is allotted to this DB2 instance.

Instance owner group

The name of the group for the instance owner user ID for this DB2 instance.

Instance owner

The user ID of the instance owner for this DB2 instance. This user ID controls all DB2 processes and owns all file systems and devices that are used by the databases that are contained within the instance.

Password (Instance owner)

The password of the instance owner user ID.

Verify password

Verification for the password that is defined by Password (Instance owner).

Fenced user group

The name of the group for the fenced user ID for this DB2 instance.

Fenced user

The user ID of the fenced user for this DB2 instance. The fenced user is used to run user-defined functions (UDFs) and stored procedures outside of the address space that is used by the DB2 database.

Password (Fenced user)

The password of the fenced user ID.

Verify password

Verification for the password that is defined by Password (Fenced user).

DAS user group

The name of the group for the DB2 administration server (DAS) user ID for this DB2 instance.

DAS user

The user ID of the DB2 administration server (DAS) user for this DB2 instance. This user is used to run the DB2 administration server on your system.

Password (DAS user)

The password of the DB2 administration server user ID.

Verify password

Verification for the password that is defined by Password (DAS user).

DB2 service port

The service port for this DB2 instance.

Database creation

From the list, choose whether you want to create a new database, a sample database, or neither (do nothing).

Name for the new database

The name of the new database that is associated with this DB2 instance.

Codeset for the new database

The code set that this DB2 instance supports.
Note: Refer to the DB2 documentation for a list of supported code sets.

Territory for the new database

The two- or three-letter territory code for this DB2 instance. Territory codes are used by the database manager internally to provide region-specific support.
Note: Refer to the DB2 documentation for a list of supported territory codes.

Collation for the new database

From the list, choose the collation style to use for this DB2 instance.

Custom collation for the new database

If you chose Other from the Collation list, provide the collation details.
Note: This is an optional parameter.

Pagesize for the new database

Specify the page size for the new database.

DB2 compatibility mode

From the list, choose the DB2 compatibility mode style to use for this DB2 instance.

Configure all raw disks for use by DB2

Specify whether all raw disks are configured for DB2.

Password (root)

The password of the root user of this DB2 instance.

Verify password

Verification of the password value that is defined by Password (root).

Virtuser username

The virtuser user ID for this DB2 instance.

Password (virtuser)

Specify the password of the virtuser ID of this DB2 instance.

Verify password

Verification of the password value that is defined by Password (virtuser).

DBNAME

The name of the MDM Database instance.

TERRITORY

The two- or three-letter territory code for the MDM Database instance. Territory codes are used by the database manager internally to provide region-specific support.
Note: Refer to the DB2 documentation for a list of supported territory codes.
Click OK.
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 for is 8000 MB (8 GB).

Reserve physical CPUs

The physical CPU 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.

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.

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

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

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 UTC (Universal Time Code).

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.
Click OK to accept this deployment manager configuration.
Click Configure virtual parts > Custom nodes to configure custom nodes, if required 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 CPUs 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 CPU 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.
Click OK to accept this custom node configuration.
Click OK to deploy this pattern as a new InfoSphere MDM instance.

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