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, or 10.3

Upgrading from Version 10.1, 10.2, or 10.3

Configure the Hub Console Client

Configure the Hub Console Client

To configure the Hub Console client to connect to the Hub Server machine, edit the
cmxserver.properties
file and repackage the Hub Server application.
You can override the host name and port number when you launch the Hub Console.
  1. Set relevant values for the
    cmx.appserver.console.mode
    property in the
    cmxserver.properties
    file in the following directory:
    <
    MDM Hub installation directory
    >/hub/server/resources
    Set the value to the communication protocol that you use, either HTTP or HTTPS.
  2. Navigate to the following directory:
    <
    MDM Hub installation directory
    >/hub/server/bin
  3. Run the following command:
    On UNIX.
    ./sip_ant.sh repackage -Dconsole.hostname=<host name> -Dconsole.webport=<port>
    On Windows.
    sip_ant.bat repackage -Dconsole.hostname=<host name> -Dconsole.webport=<port>
    Where host name is the IP address or publicly accessible host name of the server that the application server binds to and port is the HTTP or HTTPS port of the current node that the Hub Console must use.

0 COMMENTS

We’d like to hear from you!