Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Run the PostInstall Script for Deploying the Hub Server (Conditional)

Run the PostInstall Script for Deploying the Hub Server (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 a WebLogic Server environment with Managed Servers where the Administration Server and the Managed Servers are on different machines, copy all the deployment files to the MDM Hub installation directory of the Administration Server. For more information, see the
Multidomain MDM Installation Guide
.
  1. Open a command prompt and run the
    postInstallSetup
    script the following directory:
    <
    MDM Hub installation directory
    >/hub/server
    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. On UNIX, 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\!\!
    For WebSphere with security disabled:
    ./postInstallSetup.sh -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>
    For WebSphere with security-enabled:
    ./postInstallSetup.sh -Dwebsphere.password=<WebSphere 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>
    For JBoss:
    ./postInstallSetup.sh -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>
    For WebLogic:
    ./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>
    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, add the options that match your decisions:
    • ActiveVOS installed.
      -Dinstall.avos.patch=true
    • T3S protocol used.
      -Dweblogic.naming.protocol=t3s
    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 a WebLogic environment with Managed Servers, ensure that you specify all the Managed Servers as the targets for deployments in the WebLogic Server Administration Console.
For more information, see the
Multidomain MDM Installation Guide
and the WebLogic documentation.

0 COMMENTS

We’d like to hear from you!