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. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies 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. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Update the ActiveVOS URNs

Update the ActiveVOS URNs

To use the HTTP Secure (HTTPS) protocol for secure communication between the MDM Hub and ActiveVOS, change the URLs in the URN paths from http to https.
  1. Launch the
    ActiveVOS Console
    . In a browser, type the following URL, substituting the correct host name and port number:
    JBoss Version 7.2 or 7.1
    URL Path
    Secure connections
    https://<
    host
    >:<
    port
    >/activevos
    Non-secure connections
    http://<
    host
    >:<
    port
    >/activevos
  2. In the
    ActiveVOS Console
    , on the Home page, click
    Administration > Configure Server > URN Mappings
    .
  3. For the following URNs, update the paths to reflect the host name and port number of the ActiveVOS Server:
    URN
    URL Path
    ae:internal-reporting
    Secure connections.
    https://<
    host
    >:<
    port
    >/activevos/internalreports
    Non-secure connections.
    http://<
    host
    >:<
    port
    >/activevos/internalreports
    ae:task-inbox
    Secure connections.
    https://<
    host
    >:<
    port
    >/activevos-central/avc
    Non-secure connections.
    http://<
    host
    >:<
    port
    >/activevos-central/avc
  4. Verify that
    MDMHost:InfaMDM
    is mapped to the host name and port number of the MDM Hub Server:
    Secure connections.
    https://<
    host
    >:<
    port
    >/cmx/services/SifService
    Non-secure connections.
    http://<
    host
    >:<
    port
    >/cmx/services/SifService

0 COMMENTS

We’d like to hear from you!