Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

---

 

Configure JBoss servers

After creating a middleware server representation of a JBoss server in the administrative console, update a few configuration settings so that they are defined specifically for your JBoss installation.

 

Before you begin

Federate the node that is running the JBoss server and create a representation of the server in the administrative console.

 

About this task

If you 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 your server from the administrative console, configure the server operations for the JBoss middleware server representation.

 

Procedure

1. Update the WebSphere variables so that they match the settings on the node that is running the JBoss server. In the administrative console, click Environment > WebSphere Variables. Edit the JBOSS_DIST variable, which specifies the home directory of your JBoss installation. Usually, the default installation location includes the JBoss version, so it is likely that update the default values. Default values are set at the cell scope level:

   • C:\Program Files\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 your configuration, select the node scope and create the variables for the specific node.

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

   1. In the administrative console, click Servers > Other middleware servers > JBoss servers > jboss_server > Server operations.

   2. Edit the start and stop server operations to include the user name and password that is required to run these commands.

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

   1. In the administrative console, click Servers > Other middleware servers > JBoss servers > jboss_server .

   2. Edit HTTP connector or HTTPS connector. Click OK and save and synchronize your changes.

 

What to do next

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

• To view the log files for your 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}

• To edit configuration files for your JBoss server, use the external configuration service. The following files are included by default:

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/jboss-minimal.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/jboss-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/log4j.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/login-config.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/standardjaws.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/standardjboss.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/standardjbosscmp-jdbc.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/jndi.properties

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/conf/server.policy

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/bsh-deployer.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/cache-invalidation-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/client-deployer-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/ear-deployer-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/ejb-deployer-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/hsqldb-ds.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/jbossjca-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/jmx-invoker-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/jsr88-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/mail-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/monitoring-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/properties-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/schedule-manager-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/schedule-service.xml

  • ${JBOSS_DIST}/server/${JBOSS_PROFILE}/deploy/sqlexception-service.xml

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

---

Previous topic
Federating middleware nodes

Next topic

Creating middleware server templates

Next topic

Configure the external log viewing service

Next topic

Creating dynamic clusters

 

Related concepts

Middleware nodes and servers
Supported middleware server types

 

Related tasks

Configure middleware server operations
Configure WebSphere variables Adding middleware servers to configurations

 

Related reference

Middleware server creation administrative tasks