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

Select an Upgrade Process

Select an Upgrade Process

You have the following options for upgrading
Multidomain MDM
:
Clean Upgrade
In a clean upgrade, you prepare a new environment with machines that meet the current MDM system requirements. You clone the MDM Hub Master Database and Operational Reference Stores from the existing environment, copy the cloned databases to the new environment, and run the Hub Store upgrade. You install the Hub Server and Process Servers in the new environment by following the instructions in the
Installation Guide
. For information about planning an infrastructure, see the
Multidomain MDM Infrastructure Planning Guide
.
In-place Upgrade
For an in-place upgrade, you update the machines that run
Multidomain MDM
to be compliant with the current MDM system requirements. Then you upgrade the MDM components.

0 COMMENTS

We’d like to hear from you!