Configuring JBoss servers

After you create a middleware server representation of a JBoss server, you must 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.

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, you must configure the server operations for the JBoss middleware server representation.

Deprecated feature Deprecated feature: Intelligent Management support for using JBoss servers is deprecated. Support for using the administrative console to configure these servers is removed. Use wsadmin scripting to manage these servers.depfeat

Procedure

  1. Update the WebSphere variables so that they match the settings on the node that is running the JBoss server. Follow the directions in the topic on modifying variables using wsadmin scripting to edit the following 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 you need to update the default values. Default values are set at the cell scope level:
    • [Windows] C:\Program Files\jboss
    • [AIX HP-UX Solaris] /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, create the variables for a specific node.

  2. Launch wsadmin scripting with a username and password so that you 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.

  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, you must change the port. Use the modifyForeignServerProperty command in the middleware server management administrative tasks to change the ports.

What to do next

Task topic    

Terms and conditions for information centers | Feedback

Last updated: March 19, 2013 10:03 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twve_mwsjboss
File name: twve_mwsjboss.html