8.4.1. JBoss Setup

Engineering Knowledge Manager

Installation Guide | Chapter 8: Installing a Front-End Web Server | 8.4. Configuring the Application Server |

8.4. Configuring the Application Server |  | 8.5. Configuring EKM to Communicate with the Web Server
Prev |  | Next

### 8.4.1. JBoss Setup

The JBoss application server may need to be configured to match the settings of the Apache web server and mod_proxy load balancer, depending on the settings you chose in those components. To configure JBoss, follow these steps:

- Configure JBoss
- Configure JBoss Web Services
- Configure JBoss Undertow (Optional)

#### 8.4.1.1. Configure JBoss

JBoss can be configured to communicate with the front-end web server via the mod_proxy load balancer using HTTP or HTTPS protocols. This section provides instructions for configuring JBoss to communicate via mod_proxy using HTTP; for instructions on how to configure JBoss to communicate via mod_proxy using HTTPS, please consult the JBoss and mod_proxy documentation.

To configure JBoss to communicate via mod_proxy using HTTP, follow these steps:

1. Edit the JBoss configuration (see JBoss Domain Mode and Configuration).

2. Find the undertow element, and find its server child element. Under the server element, you will see two elements defining "listeners". Edit the http-listener and set proxy-address-forwarding to true:

       <subsystem xmlns="urn:jboss:domain:undertow:1.2" instance-id="${jboss.server.name}">
           <buffer-cache name="default"/>
           <server name="default-server">
               <http-listener name="default" socket-binding="http"
                max-post-size="0" max-parameters="5000" proxy-address-forwarding="true"/>

#### 8.4.1.2. Configure JBoss Web Services

JBoss web services must be configured to match the configuration of the front-end web server. To configure JBoss web services, follow these steps:

1. Edit the JBoss configuration (see JBoss Domain Mode and Configuration).

2. Find the `webservices` subsystem element:

       <subsystem xmlns="urn:jboss:domain:webservices:1.2">

3. Configure the following elements: `wsdl-host`, `wsdl-port`, and `wsdl-secure-port`. The values of these elements must be configured to match the hostname and HTTP and/or HTTPS port of the front-end web server. These values control how URLs are written in the WSDL contracts of web services that are provided by EKM.

            <wsdl-host>jbossws.undefined.host</wsdl-host>
            <wsdl-port>80</wsdl-port>
       <wsdl-secure-port>443</wsdl-secure-port>

   `wsdl-host:`

     Set the value of this element to the hostname or IP address of the front-end web server. The special value `jbossws.undefined.host` is set by default, which substitutes the hostname from the request when a web service WSDL is accessed. It is usually not necessary to change this value. Alternatively, you may specify the hostname or IP address of the front-end web server here.

     Examples: `jbossws.undefined.host, `ekm.yourdomain.com`, 192.168.1.2`

   `wsdl-port:`

     Set the value of this element to the HTTP port of the front-end web server. Examples: `80`, `8080`

   `wsdl-secure-port:`

     Set the value of this element to the HTTPS port of the front-end web server. Examples: `443`, `8443`

#### 8.4.1.3. Configure JBoss Undertow (Optional)

Undertow is the name of the web server subsystem within JBoss. This subsystem listens for incoming connections on both AJP and HTTP protocols by default. Depending on your desired configuration, you may want to disable one of these listeners if you are not using it. For example, if mod_proxy will be using AJP, you may want to disable the HTTP listener, or vice-versa.

To disable a listener, follow these steps:

1. Edit the JBoss configuration (see JBoss Domain Mode and Configuration).

2. Find the `undertow` element, and find its `server` child element. Under the `server` element, you will see two elements defining “listeners”: `http-listener` and `ajp-listener`:

       <subsystem xmlns="urn:jboss:domain:undertow:1.2" instance-id="${jboss.server.name}">
           <buffer-cache name="default"/>
           <server name="default-server">
               <http-listener name="default" socket-binding="http" max-post-size="0" max-parameters="5000"/>
               <ajp-listener name="ajp" socket-binding="ajp" max-post-size="0" max-parameters="5000"/>

3. To disable a listener, set the `enabled` attribute on the listener element to `false`. For example, to disable the AJP listener:

       <subsystem xmlns="urn:jboss:domain:undertow:1.2" instance-id="${jboss.server.name}">
           <buffer-cache name="default"/>
           <server name="default-server">
               <http-listener name="default" socket-binding="http" max-post-size="0" max-parameters="5000"/>
               <ajp-listener name="ajp" socket-binding="ajp" max-post-size="0" max-parameters="5000"
       enabled="false"/>

To enable a listener, reverse these steps.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.