Installing the Hub Server in Graphical Mode

Start the application server.

Open a command prompt, and navigate to the

Hub Server

installer in the distribution directory.

By default, the installer is in the following directory:

<

MDM Hub distribution directory

>/<

operating system name

>/mrmserver

Run the following command:

On UNIX.

./hub_install.bin

On Windows.

hub_install.exe

Select the language for the installation, and then click

OK

.

The

Introduction

window appears.

Click

The

License Agreement

window appears.

Select the

I accept the terms of the License Agreement

option, and then click

The

Choose an Install Folder

window appears.

Select the location of the

Hub Server

installation.

To choose the default location, click

To enter a path, type the path to the installation folder, and click

The installation fails if you specify a path that has spaces in the directory or folder names.

To choose another location, click

Choose

, and then click

On UNIX, choose a link folder or select the option to not create links and click

On Windows, select the location to create a product icon or select the option not to create a product icon.

Click

The

Enter the location of the license file

window appears.

Click

Choose

to select a license file, and click

The

Advanced Security

window appears.

Select the security configuration for the MDM Hub.

Optionally, in the

Customer hash key

field, enter a hashing key up to 128 bits.

To choose the default configuration, click

Hub Certificate Provider

window appears.

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

Custom

and click

If you selected Custom in the preceding step, the

Hashing Algorithm

page appears.

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

Hub Certificate Provider

window appears.

To choose a custom hashing algorithm, select

Other

, and then click

If you selected Other in the preceding step, provide the following information for the custom hashing algorithm, and then click

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$

.

The

Hub Certificate Provider

window 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, click

Application Server

window appears.

To choose a custom certificate provider, select

Custom

.

If you selected 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.

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

The

Application Server

window appears.

Select

JBoss

, and then click

The

JBoss Application Server Home

window appears.

Configure the following JBoss settings:

Specify the application server installation directory, and then click

The

JBoss Application Server Configuration Name

window appears.

Specify the Configuration Name, and then click

The default value is

standalone

.

The

JBoss Application Server Port

window appears.

Specify the remote port.

The JBoss port can conflict with the default database server port. If ports conflict, change one of the ports to resolve the conflict. For more information on changing ports, see the JBoss documentation.

Specify the native management port.

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).

Click

The

Database Selection

window appears.

Select IBM DB2 UDB, and click

The

DB2 Database Information

window appears.

Enter the following settings for the IBM DB2 database to which you want to connect, and click

Field Name	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	The IBM DB2 database user 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.

The

Install ActiveVOS

window appears.

If you want to install the bundled, licensed version of

Informatica ActiveVOS

, select

Yes

and perform the following substeps. Otherwise, select

No

, and click

On the

Choose ActiveVOS Installation Folder

page, accept the default installation path or specify a preferred location. Click

On the

Database Information

page, enter the database details that you specified when you created the ActiveVOS database schema, and click

On the

Application Server Web URL

page, accept the default URL or specify the URL that you want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server. Click

The post installation setup script uses the URL to call ActiveVOS web services, deploy the predefined MDM workflows to ActiveVOS, and create the URN mapping.

On the

ActiveVOS Installer

page, click

Choose

and browse to the ActiveVOS_Server installation file in the distribution package. Click

Enter the administrative user name and password to create an administrative user for the ActiveVOS 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.

Click

Select one of the following Informatica platform installation options:

Yes

. Install Informatica platform.

No

. Does not install Informatica platform.

If you select

Yes

in the preceding step, click

Choose

and browse to the following Informatica platform file locations:

Installation response file

Platform installation file

On the Product Usage Toolkit page, select the industry to which the organization belongs and the environment type.

If you want to use a proxy server, select

Yes

, and enter the proxy server details. Otherwise, select

No

.

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.

Click

The Deploy page appears.

Select one of the following

postInstallSetup

script options:

Yes, run the script during this installation

. Runs the

postInstallSetup

script during the installation.

No, I will run it later

. Does not run the

postInstallSetup

script during the installation. After the installation, you must run the

postInstallSetup

script or manually deploy the Hub Server applications.

The

postInstallSetup

script repackages and deploys the Hub Server applications. Also, the script creates data sources and configures JMS message queues.

Click

The

Pre-Installation Summary

window appears.

After the Pre-Installation Summary window displays the options you want, click

Install

to start the installation process.

When the installation completes, the

Install Complete

window appears.

Click

Done

to exit the Hub Server installer.

Table of Contents

Installation Guide for IBM DB2 with Red Hat JBoss

Installation Guide for IBM DB2 with Red Hat JBoss