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 9.7.1

Upgrading from Version 9.7.1

Starting JBoss Cluster Nodes

Starting JBoss Cluster Nodes

If you use a JBoss cluster environment, start the cluster nodes 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 cluster node, run the following command on machines that have cluster nodes:
    On UNIX.
    standalone.sh -c standalone-full.xml -b 0.0.0.0 -Djboss.node.name=<Name of the cluster node> -Djboss.server.base.dir=../<node path> -Djboss.as.management.blocking.timeout=5000 -u <multicast address> -Djgroups.bind_addr=<bind address> -Djboss.socket.binding.port-offset=<port offset value> -Djboss.partition.name=<Partition name>
    On Windows.
    standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.node.name=<Name of the cluster node> -Djboss.server.base.dir=../<node path> -Djboss.as.management.blocking.timeout=5000 -u <multicast address> -Djgroups.bind_addr=<bind address> -Djboss.socket.binding.port-offset=<port offset value> -Djboss.partition.name=<Partition name>
    Set the port offset value if multiple cluster nodes run on the same machine. Use the default partition name or ensure that the partition name is the same for all nodes that belong to a cluster. Adjust the timeout interval based on your environment.

0 COMMENTS

We’d like to hear from you!