Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

10.5 HotFix 2

Back Next

Upgrading the Hub Server in Console Mode

You can upgrade the Hub Server in console mode in UNIX.

If you use embedded ActiveVOS for business process management, the upgrade process requires you to install the updated version of ActiveVOS in a new directory. If you prefer to overwrite the existing ActiveVOS installation, before you begin the upgrade, open the

../hub/server/bin/build.properties

file and comment out the following property:

activevos.install.dir = <AVOS installed path>

Start the application server.

Navigate to the following directory in the MDM Hub distribution:

On UNIX.

MDM Hub distribution directory

>/<

operating system name

>/mrmserver

Run the following command from the command prompt:

./hub_install.bin -i console

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

Enter

The introduction information about the upgrade 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.

Specify the directory where you installed the Hub Server.

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.

If you use Customer 360 or Supplier 360, perform the following tasks:

Ensure that all the draft records are submitted in Customer 360 or Supplier 360.

If you do not submit the draft records, you can confirm to delete them and proceed with the upgrade.

Click

Proceed

Enter

to proceed and

to cancel. The default option is

Press

Enter

to confirm that you want to proceed.

Configure the server details for the Hub Console:

IP address or fully qualified host name (FQDN) of the server to which the application server binds.

HTTP port of the server that the Hub Console must use.

If HTTPS is enabled for the application server, after the upgrade, configure the Hub Console client by editing the properties in the

build.properties

file.

In WebLogic environments, enter your WebLogic password, and press

Enter

If you use, or want to use, embedded ActiveVOS for business process management, install the embedded ActiveVOS version that is recommended for this version of

Multidomain MDM

Standalone ActiveVOS is not supported. If you already have a supported version of embedded ActiveVOS installed, you can skip some of the substeps in this step. Perform substep c. to enter database details and substep 12f. to specify the user name and password for the ActiveVOS Server Administration Console.

Press

Enter

for y=Yes.

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

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

If you are moving from standalone ActiveVOS to embedded ActiveVOS, enter the details for the standalone ActiveVOS schema.

Specify the URL that you want to use to call MDM and ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server.

On the ActiveVOS Installer page, select

Choose

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

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.

Choose whether you want to run the

postInstallSetup

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

Option	Conditions
Yes, run the script during this installation	Deploys the Hub Server EAR file automatically after a successful installation. Select this option if you use one of the following application server environments with one of the ActiveVOS scenarios: Application server environments: JBoss standalone environment WebSphere standalone environment ActiveVOS scenarios: You chose to install ActiveVOS and no other version of ActiveVOS is installed in this environment. You chose to install ActiveVOS and the environment includes a supported version of ActiveVOS. Check the product availability matrix (PAM) for supported versions. You chose not to install ActiveVOS. If you chose to install ActiveVOS but you have an unsupported version of ActiveVOS in your environment, select No, I will run it later .
No, I will run it later	You package and deploy the Hub Server EAR file manually. Select this option if you use one of the following application server environments, with or without ActiveVOS: WebLogic standalone environment WebLogic clustered environment JBoss clustered environment WebSphere clustered environment If you are using any application server environment that includes an unsupported version of ActiveVOS, select this option. You must upgrade the ActiveVOS schema to the supported version and then deploy manually.

Option

Conditions

Yes, run the script during this installation

Deploys the

Hub Server

EAR file automatically after a successful installation.

Select this option if you use one of the following application server environments with one of the ActiveVOS scenarios:

Application server environments:

JBoss standalone environment

WebSphere standalone environment

ActiveVOS scenarios:

You chose to install ActiveVOS and no other version of ActiveVOS is installed in this environment.

You chose to install ActiveVOS and the environment includes a supported version of ActiveVOS. Check the product availability matrix (PAM) for supported versions.

You chose not to install ActiveVOS.

If you chose to install ActiveVOS but you have an unsupported version of ActiveVOS in your environment, select

No, I will run it later

You package and deploy the

Hub Server

EAR file manually.

Select this option if you use one of the following application server environments, with or without ActiveVOS:

WebLogic standalone environment

WebLogic clustered environment

JBoss clustered environment

WebSphere clustered environment

If you are using any application server environment that includes an unsupported version of ActiveVOS, select this option. You must upgrade the ActiveVOS schema to the supported version and then deploy manually.

Press

Enter

The summary of the upgrade choices appears.

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

Enter

to start the upgrade. If you need to make changes, type

BACK

to the specific information and make changes.

When the process is complete, the upgrade completion information appears.

Press

Enter

to exit the installer.

Hub Server Upgrade (In-place Upgrade)

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading the Hub Server in Console Mode

Upgrading the Hub Server in Console Mode