Installation Guide for IBM DB2 with Red Hat JBoss

10.3 HotFix 1
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3

Back Next

Installing the Hub Server in Console Mode

You can install the

Hub Server

in console mode on UNIX.

Start the application server.

Open a command prompt, and navigate to the following directory in the MDM Hub distribution:

MDM Hub distribution directory

>/<

operating system name

>/mrmserver

Run the following command:

./hub_install.bin -i console

Enter the number of the locale you want to choose for the installation, and then press

Enter

The introduction information about the installation appears.

Press

Enter

The license agreement appears.

Read the License Agreement. Type

to accept the terms of the license agreement, or type

if you do not want to accept the license agreement and want to exit the installation program.

Press

Enter

If you entered

in the preceding step, information about the installation folder appears.

Choose a folder for the

Hub Server

installation.

To choose the default folder, press

Enter

To change the path, type the absolute path of the installation folder, and press

Enter

Confirm the location of the installation folder. Type

to confirm the installation folder, or type

to change the installation folder.

Press

Enter

A list of link location options appears.

Enter the number of a link location option.

The prompt for the license file location appears.

Enter the absolute path of the license file, and press

Enter

A list of advanced security options appears.

Choose a security configuration for the MDM Hub.

To choose the default configuration, press

Enter

To choose a custom security configuration for the MDM Hub, type

Custom

, and press

Enter

When prompted for a customer hash key, you can enter a value up to 128 bits.

If you typed Custom in the preceding step, choose one of the following options:

To accept the default hashing algorithm for password hashing in the MDM Hub, press

Enter

To choose a custom hashing algorithm, type

Other

, and press

Enter

If you typed Other in the preceding step, provide the following information for the custom hashing algorithm:

Hashing algorithm name

Location of the hashing algorithm archive.

The hashing algorithm archive must be a ZIP file. If the archive contains multiple JAR files and other supporting files, ensure they are all in the ZIP file.

Canonical class name of the hashing algorithm implementation.

For example, enter

$HASHING_CLASS_NAME$

A list of certificate provider options appears.

To select the certificate provider for the MDM Hub to authenticate trusted applications, choose one of the following options:

To choose the default certificate provider, press

Enter

To choose a custom certificate provider, type

Custom

and press

Enter

If you typed Custom in the preceding step, provide the following information for the custom certificate provider:

Enter the location of the certificate provider archive.

The certificate provider archive must be a ZIP file. If you use a custom certificate provider, ensure the

MDM Hub installation directory

>/server/resources/certificates

directory is empty. In a WebSphere environment, the MDM Hub user must also have access and write permissions for the certificates directory.

Enter the class name of the certificate provider, and then press

Enter

A list of application server options appears.

Enter the number for the application server that you want to select, and press

Enter

The application server information appears.

Configure the JBoss settings.

Specify the application server installation directory, and press

Enter

The JBoss application server configuration name information appears.

Specify the configuration name. The default value is

standalone

Press

Enter

Specify the remote port.

If the JBoss port conflicts with the default database port, then change one of the ports to resolve the conflict.

Specify the native management port, and press

Enter

Default is

9990

. If port offset is configured for the application server, add the offset value to the default value.

For example, if the port offset is

100

, the native management port value is

10090

, which is (9990 + 100).

Press

Enter

The database selection prompt appears.

Select IBM DB2 UDB, and press

Enter

Specify the settings for the DB2 database to which you want to connect.

Press

Enter

to accept the default values, or replace the defaults with the correct values.

The following table describes the prompts:

Prompt	Description
Server	Host name of the MDM Hub Master Database server.
Port	Port number of the MDM Hub Master Database.
Database Name	Name of the database that you created.
System Schema	Name of the MDM Hub Master Database.
System Schema User Name	User belonging to the DB2ADMNS user group that you use to access the system schema. Use the same user that you used to import seed into the MDM Hub Master Database.
System Schema Password	Password of the user used to connect to the system schema.

Press

Enter

If you want to install the bundled, licensed version of the ActiveVOS Server, press

Enter

for Yes. Otherwise, type

for No and press

Enter

If you selected Yes, the installer prompts you to provide information about your ActiveVOS installation.

Specify the location where you want to install the ActiveVOS Server.

Specify the URL that you want to use to call MDM and ActiveVOS web services.

Enter information about the ActiveVOS database that you specified when you created the ActiveVOS schema.

Specify the location of the ActiveVOS Server installation file.

Enter a user name and password to create an administrative user for the ActiveVOS Server Administration Console.

The user name and password must be the same as the ActiveVOS Console user name and password that was created in the application server.

Press

Enter

The Informatica platform installation prompt appears.

If you want to install the Informatica platform, press

Enter

for Yes. Otherwise, type

for No and press

Enter

The prompts for the Informatica platform installation response file and archive file locations appear.

Enter the locations of the Informatica platform installation response file and archive file, and press

Enter

Specify the Product Usage Toolkit options.

Enter the industry to which the organization belongs , and then press

Enter

Enter the environment type. Type

for Production, type

for Test/QA, or type

for Development, and then press

Enter

Select whether you have a proxy server. Press

Enter

for Yes. Otherwise, type

for No and then press

Enter

You can enter the following proxy server details:

Proxy server name/IP

Proxy server port

Proxy server domain name. Leave blank if not applicable.

Proxy server user name. Leave blank if not applicable.

Proxy server password. Leave blank if not applicable.

The summary of the installation choices appears.

Choose whether you want to run the

postInstallSetup

script as part of the installation, or run it manually later.

In a WebLogic 12.2.1.3 or later environment, if you decided to install ActiveVOS or if you decided to use the WebLogic T3S protocol, select

No, I will run it later

Verify the information in the pre-installation summary. If the information is correct, press

Enter

to start the installation.

The Hub Server is installed according to the configuration information you provide. When the process is complete, the installation complete message appears.

Press

Enter

to exit the installer.

Hub Server Installation

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal