Skip to content

Application Servers Pre-Installation Tasks

JBoss

JBoss Cluster - Domain Mode

For information about setting up JBoss Cluster in domain mode, refer to JBoss EAP 7.2 Domain Mode Setup.

Configure Load Balancer as Proxy in JBoss Multinode Setup (Optional if SSL Offloading at Load Balancer)

  1. Navigate to your Volt MX Foundry install directory and open the domain.xml file.

  2. In the domain.xml, update all the http connector tags to include the scheme and proxy-port details.

    For example,`<connector name="http" protocol="HTTP/1.1" scheme="https" socket-binding="http" proxy-name="loadbalancer hostname" proxy-port="443" secure="true"/>`

Update Listen Interfaces in host.xml for JBoss Cluster

For JBoss domain mode installation, configure the following interface address.

  1. Go to <JBOSS EAP dir>/domain/configuration/host.xml
  2. In place of existing  interfaces xml tag, replace the default content with below details:
<interfaces>
        <interface name="management">
            <any-ipv4-address/>
        </interface>
        <interface name="public">
           <any-ipv4-address/\>
        </interface>
        <interface name="unsecure">
            <!-- Used for IIOP sockets in the standard configuration.
                 To secure JacORB you need to setup SSL -->
            <any-ipv4-address/>
        </interface>
        <interface name="any">  
            <any-ipv4-address/>  
        </interface> 
    </interfaces>

Comment the javax-persistence-module for Volt MX Engagement Services on JBoss Cluster

If you are installing Volt MX Engagement Services on JBoss domain mode installation, comment the below persistence module in the domain.xml file.

  1. Go to <JBOSS EAP dir>/domain/configuration/domain.xml
  2. Comment the below xml tag. Comment the persistence module at four places in the domain.xml file.
            <!-- <subsystem xmlns="urn:jboss:domain:jpa:1.1">
                <jpa default-datasource="" default-extended-persistence-inheritance="DEEP"/>
            </subsystem> \-->

How to Configure Connector - JBoss Standalone

For importing an app to Volt MX Foundry Console properly, you must have set the enough value for the max-post-size in the standalone.xml file. For more details, refer to Configure Connectors - JBoss

How to Increase Timeout and Maximum Heap Size Settings - JBoss Standalone

Restarting JBoss can cause deployment failures. To avoid these failures, you must increase the JBoss timeout and maximum heap size settings for cluster.

To increase memory and timeout settings in JBoss (pre-configured JBoss), follow these steps:

  1. In the standalone.bat or .sh file, add the following properties to Java_opts: 
    -Djboss.as.management.blocking.timeout=8400  
-Xms2048m  
-Xmx4096m
  2. In the <JBoss_Home>/standalone/configuration/standalone.xml file, add config deployment-timeout=”8400” in the deployment-scanner subsystem, shown below:
    3. <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">  
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout=”8400” runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}"/>  
</subsystem>

To increase memory and timeout settings in JBoss Multinode, follow these steps:

  1. In the domain.bat or .sh file, add the following properties to Java_opts:
    -Djboss.as.management.blocking.timeout=8400
  2. Set the heap size for the selected server groups as below in the <JBoss_Home>/domain/configuration/domain.xml.
  3. Search for <server-groups> tag in the domain.xml and set the heap size in the JVM settings.
    4. <heap size="2048m" max-size="4096m"/>

How to Configure Engagement Services - JBoss

When Engagement is selected as Foundry Component, based on the selected JBoss mode, you must add the following parameter in the JVM arguments present in standalone.bat/domain.bat (for Windows) or standalone.sh/domain.sh (for Unix):

-DVMS_CORE_VERSION=2