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

Perform Post-Upgrade Tasks for In-place Upgrade

Perform Post-Upgrade Tasks for In-place Upgrade

After an in-place upgrade, you must perform some post-upgrade tasks.
The following table provides details of the post-upgrade tasks:
Upgrade Task
Details
Clear the Java cache
  1. Clear the Java cache. For instructions, see the Java documentation.
  2. Launch the Hub Console.
Configure logging
To optimize the performance of Data Director, configure logging by editing the
log4j.xml
file.
  1. Open
    log4j.xml
    in the following directory:
    <
    MDM Hub installation directory
    >/hub/server/conf
  2. Add the following logging configuration:
    <category name="org.eclipse.persistence.sdo"> <priority value="WARN"/> </category> <category name="org.eclipse.persistence.default"> <priority value="WARN"/> </category>
  3. Save and close the
    log4j.xml
    file.

0 COMMENTS

We’d like to hear from you!