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. 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. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Starting Standalone JBoss Instances

Starting Standalone JBoss Instances

If you use standalone JBoss instances, start each instance on which you want to install the MDM Hub components.
  1. Navigate to the following directory:
    <
    JBoss installation directory
    >/bin
  2. To start a JBoss instance, run the following command:
    On UNIX.
    standalone.sh -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=5000
    On Windows.
    standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=5000
    JBoss starts on the available network interfaces and listens for the current host that is defined in the hosts file in the
    /etc/hosts
    directory. Adjust the timeout interval based on your environment.
  3. If you have multiple JBoss instances on the same machine, to start the second and any subsequent JBoss instances, add the following argument to the startup command:
    -Djboss.socket.binding.port-offset=<port offset range such as, 0,100,200,...n>

0 COMMENTS

We’d like to hear from you!