Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Store Post-Installation Tasks
  6. Hub Server Installation
  7. Hub Server Post-Installation Tasks
  8. Process Server Installation
  9. Process Server Post-Installation Tasks
  10. ActiveVOS Post-Installation Tasks for the Application Server
  11. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  12. Customize ActiveVOS
  13. Resource Kit Installation
  14. Troubleshooting the MDM Hub
  15. Uninstallation

Installation Guide for Oracle Database with WebLogic

Installation Guide for Oracle Database with WebLogic

Use a Script to Deploy the Hub Server Applications (Conditional)

Use a Script to Deploy 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.
  1. 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.
    ave_weblogic.ear
    Required. The ActiveVOS Server application.
    activevos-central.war
    Required. The ActiveVOS Central application.
    The deployment files are in the following directory:
    <
    MDM Hub installation directory
    >/hub/server
  2. Open a command prompt, and change to the following directory:
    <
    MDM Hub installation directory
    >/hub/server
  3. 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.
  4. If you deploy in an environment with Managed Servers, ensure that you specify the targets for deployments in the WebLogic Server Administration Console.
    1. 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.
      ave_weblogic.ear
      Required. The ActiveVOS Server application.
      activevos-central.war
      Required. The ActiveVOS Central application.
    2. Specify all the Managed Servers as targets for the JMS module
      SiperianModule
      .
    3. Specify all the Managed Servers as targets for the following data sources:
      • MDM Hub Master Database data source
      • Operational Reference Store datasource
    4. Specify all the Managed Servers as targets for the startup and shutdown classes.
For more information, see the WebLogic documentation.

0 COMMENTS

We’d like to hear from you!