Configure JBoss servers

After creating a middleware server representation of a JBoss server, you must update a few configuration settings so that they are defined specifically for the JBoss installation.

Federate the node running the JBoss server and create a representation of the server.

If we installed JBoss in a location other than the default directory, update the WebSphere variables so that the installation directory is correct. To perform server operations on the server, configure the server operations for the JBoss middleware server representation.

  • Intelligent Management support for using JBoss servers is stabilized. We can use the administrative console or wsadmin scripting to manage these servers.

    1. Update the WebSphere variables so that they match the settings on the node running the JBoss server.

      • Follow the directions in the topic on modifying variables to edit the variables.

      • In the administrative console, click Environment > WebSphere Variables to edit the variables.

      Edit the JBOSS_DIST variable, which specifies the home directory of the JBoss installation. Usually, the default installation location includes the JBoss version, so it is likely that we need to update the default values. Default values are set at the cell scope level:

      • C:\jboss

      • /usr/local/jboss

      Edit the JBOSS_PROFILE variable, which specifies the configuration set in use for the server representation, and defaults to the name of the server itself. The default value is set at the server scope level: ${WAS_SERVER_NAME}. If these settings are different on different nodes in the configuration, create the variables for a specific node.

      Create a new variable and name it JBOSS_HOST. Set the value to the host that the JBoss server will run on. Set the scope to the JBoss server.

    2. Update server operations for the JBoss server to include the user name and password.

      • Launch wsadmin scripting with a username and password so that we can start and stop server operations.

        Follow the directions in the topic on starting the wsadmin scripting client to enable security. The startMiddlewareServer command and the stopMiddlewareServer command require a user name and password to run.

      • In the administrative console, click Servers > Other middleware servers > JBoss servers > jboss_server > Server operations. Edit the start and stop server operations to include the user name and password required to run these commands.

    3. Optional: Update the HTTP and HTTPS ports for your servers. The default port is 8080. If we use a value other than the default, you must change the port.

      • Use the modifyForeignServerProperty command in the middleware server management administrative tasks to change the ports.

      • In the administrative console, click Servers > Other middleware servers > JBoss servers > jboss_server. Edit HTTP connector or HTTPS connector. Click OK, and save and synchronize the changes.


    What to do next

    • To use this configuration when we are configuring the other JBoss servers, create a server template of the current JBoss server.

    • View the log files for the JBoss server on the machine that hosts it. To view the log files for the JBoss server in the administrative console, use the external log viewing service. This service is enabled by default. The following directories are configured by default:

      • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/logs

      • ${AGENT.HOME}/logs/${WAS_SERVER_NAME}

    • Edit configuration files for the JBoss server on the machine that hosts it.

    • After creating representations of all the JBoss servers, we can add the representations to a dynamic cluster.


    Related concepts

  • Middleware nodes and servers
  • Supported middleware server types


    Related tasks

  • Add, managing, and removing nodes
  • Configure middleware server operations
  • Modify variables
  • Start the wsadmin scripting client
  • Add middleware servers to configurations
  • Create middleware server templates
  • Configure the external log viewing service
  • Create dynamic clusters
  • Intelligent Management: middleware server management administrative tasks

  • addNode command
  • Intelligent Management: middleware server creation administrative tasks