IBM Db2 data source worksheet
Use this data source worksheet to identify parameters for the IBM® DB2® data source to which your Product Master is connecting.
When you define the names for your databases and user accounts,
consider giving the associated database instance, user account, and
data source configuration the same name. You might also want to include
the Product Master version
in your name. Using this naming convention can help other members
of your organization and IBM Software
Support understand the mapping between instances, accounts, and databases.
The parameters that are listed in the following table equate to user prompts or fields that
you see in IBM Installation Manager.
| Parameter | Description | Your value |
|---|---|---|
| Database type | Product Master supports Db2. | |
| Database host name | Identify the fully qualified address of the host on which the database is
installed. The default is localhost. |
|
| Database port | Identify the database port or use the default port number provided. The Db2 default is 50000. |
|
| Database user name | The database user name must have DBA privileges. Restrictions on length and supported characters for user names and passwords are dependent upon any restrictions that might be imposed by your operating system. |
|
| Database password | Provide a password for the database user name. | |
| Local database name | Provide a name that identifies the MDM database. The default is
MDMDB. The name must consist of 12 or fewer alphanumeric characters. Underscore (_) characters can be used in the name. Other characters are not supported. A physical MDM implementation uses the Db2 local client to run database scripts and requires a local database name. |
|
| Remote database name | Provide a name that identifies the remote MDM database. The default is
MDMDB. |
|
| Database home | Provide the parent directory of SQLLIB. For example, IBM AIX®, Linux® or Solaris: /home/db2inst1/sqllib | |
| Database schema | Specify the database schema name. By default the schema name is the same as the database application user. |