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

Configuring the Hub Server for Hierarchies

Configuring the Hub Server for Hierarchies

Use the Hub Server tool in the Hub Console and the
cmxserver.properties
file to configure the Hub Server properties to support hierarchy REST APIs.
You can use hierarchy REST APIs to interact with your hierarchies. For more information about hierarchy REST APIs, see the
Multidomain MDM Business Entity Services Guide
.
  1. Use a text editor to open the
    cmxserver.properties
    file in the following location:
    <MDM Hub Installation Directory>\hub\server\resources\cmxserver.properties
    .
  2. Manually add and configure the following properties:
    cmx.server.hierarchy.max-search-depth
    Maximum depth searched when you use hierarchy REST APIs to find a hierarchy path. Default value is
    100
    .
    cmx.server.hierarchy.max-search-width
    Maximum width of the searched hierarchy to include when you use the hierarchy REST APIs to export. Default value is
    1000000
    .

0 COMMENTS

We’d like to hear from you!