Installation Guide for Oracle Database with WebLogic

10.3 HotFix 1

Back Next

Using a Script for Deploying the Hub Server Applications (Conditional)

If you skipped the

postInstallSetup

script during the installation, run the script. The post-installation process deploys the Hub Server applications, creates data sources, and configures JMS message queues.

If you use an environment with Managed Servers where the Administration Server and the Managed Servers are on different machines, copy the following deployment files to the MDM Hub installation directory of the Administration Server:

Deployment File Name	Description
siperian-mrm.ear	Required. The Hub Server application.
provisioning-ear.ear	Required. The Provisioning tool application.
entity360view-ear.ear	Optional. The Entity 360 framework.
informatica-mdm-platform-ear.ear	Optional. The Informatica platform application.
ave_weblogic.ear	Optional. The ActiveVOS server application.
activevos-central.war	Optional. The ActiveVOS Central application.

The deployment files are in the following directory:

MDM Hub installation directory

>/hub/server

Open a command prompt, and change to the following directory:

MDM Hub installation directory

>/hub/server

Run the

postInstallSetup

script.

If you did not install the ActiveVOS version that is bundled with the MDM Hub installer, do not include the ActiveVOS user names and passwords in the command.

For the WebLogic 12.2.1 or later environments, if you installed the ActiveVOS version that is bundled with the MDM Hub installer, run the script by adding the

-Dinstall.avos.patch=true

option.

On UNIX.

./postInstallSetup.sh -Dweblogic.password=<WebLogic password> 
-Ddatabase.password=<MDM Hub Master database password> 
-Davos.username=<ActiveVOS Console username> 
-Davos.password=<ActiveVOS Console password> 
-Davos.jdbc.database.username=<ActiveVOS database username>
-Davos.jdbc.database.password=<ActiveVOS database password>

If you include the exclamation mark (!) in your password, you must include a backslash before the exclamation mark. For example, if your password is !!cmx!!, enter the following password: \!\!cmx\!\!

On Windows.

postInstallSetup.bat 
-Dweblogic.password=<WebLogic password> 
-Ddatabase.password=<MDM Hub Master database password> 
-Davos.username=<ActiveVOS Console username> 
-Davos.password=<ActiveVOS Console password> 
-Davos.jdbc.database.username=<ActiveVOS database username> 
-Davos.jdbc.database.password=<ActiveVOS database password>

The ActiveVOS Console credentials are the same credentials as the administrative user in the application server.

The ActiveVOS database credentials are the same credentials that were used to run the

create_bpm

script.

If you deploy in an environment with Managed Servers, ensure that you specify the targets for deployments in the WebLogic Server Administration Console.

Specify all the Managed Servers as targets for the following Hub Server deployments:

Deployment File Name	Description
siperian-mrm.ear	Required. The Hub Server application.
provisioning-ear.ear	Required. The Provisioning tool application.
entity360view-ear.ear	Optional. The Entity 360 framework.
informatica-mdm-platform-ear.ear	Optional. The Informatica platform application.
ave_weblogic.ear	Optional. The ActiveVOS server application.
activevos-central.war	Optional. The ActiveVOS Central application.

Specify all the Managed Servers as targets for the JMS module

SiperianModule

Specify all the Managed Servers as targets for the following data sources:

MDM Hub Master Database data source

Operational Reference Store datasource

Specify all the Managed Servers as targets for the startup and shutdown classes.

Rename Saved Search

Table of Contents

Installation Guide for Oracle Database with WebLogic

Installation Guide for Oracle Database with WebLogic

Using a Script for Deploying the Hub Server Applications (Conditional)

Using a Script for Deploying the Hub Server Applications (Conditional)