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. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Reapplying the Process Server Upgrade (Optional)

Reapplying the Process Server Upgrade (Optional)

If you complete the Process Server upgrade, the upgrade process does not allow you to reapply the Process Server upgrade. For example, you might want to reapply the Process Server upgrade if hardware fails during the upgrade process. You can also perform this procedure if you test an upgrade and then want to revert to an earlier version of the software.
  1. Back up the
    siperian-mrm.ear
    file in the following directory:
    • On UNIX.
      <
      MDM Hub installation directory
      >/hub/cleanse
    • On Windows.
      <
      MDM Hub installation directory
      >\hub\cleanse
  2. Repeat the upgrade steps. Add the parameter
    -DSIPERIAN_FORCED_PATCH_INSTALL=true
    to the install command.
    For example, if you reapply the upgrade in graphical mode in UNIX, run the following command:
    hub_cleanse_install.bin -DSIPERIAN_FORCED_PATCH_INSTALL=true

0 COMMENTS

We’d like to hear from you!