EM12: JBoss Application Server Plug-in Discovery and Troubleshooting
(Doc ID 1495021.1)
Last updated on MARCH 12, 2021
Applies to:Enterprise Manager for Fusion Middleware - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
This article demonstrates how to discover the JBoss Application Server target type in Enterprise Manager (EM) 12c Cloud Control.
JBoss Target Model
1. JBoss is an Open Source Application Server
2. JBoss can be a Standalone Server or organized in Partitions and Clusters
JBoss Application Server (jboss_j2eeserver) or JBoss Partition (jboss_partition)
depends on how the JBoss environment was setup.
Enterprise Manager 12c supports the following JBoss Application Server versions:
5.1.0 - Library Path to be provided during Local Discovery
Include the Library Path during at the time of the Add JBoss Application Server
6.0.0 - Standalone Not Supported.
Fixed in the future 22.214.171.124 release
Note that, as of version 6, this plug-in does not certify against JBOSS Enterprise Application Platform. Instead the plug-in is certified agains the JBOSS Appication Server which is a part of the JBOSS EAP.
The versions of JBOSS EAP and JBOSS AS are not in sync.
To find out what AS version is shipped with EAP please visit the following link on the RedHat website:
Steps to install, initial setup and starting JBoss
1. Download and extract the jboss installation zip file
2. Set the following environment variables
3. Copy MEJB to the appropriate deploy folder
This exposes management APIs to the agent
copy .../docs/examples/jmx/ejb-management.jar to server/default/deploy
4. Run the following command to start the server (from bin folder)
./run.sh -c <Deployment Profile> -b <Binding Address> [-Djboss.partition.name=<Partition Name>]
Deployment Profile = default, all, etc
Binding Address = hostname/IP address running jboss
Partition Name = By dfault, the servers start as part of DefaultPartition.
In case you want to change that, you can specify the partition name here.
./run.sh -c all -b myhostname.domain.com -Djboss.partition.name=MyJBossCluster
5. Start the standalone JBoss Server Instance
By starting the server in 'default' deployment profile, the server gets started as a standalone server instance
./run.sh -c default -b <Binding Address>
6. Start a JBoss Partition
JBoss Clustering service has to be enabled in order to start a JBoss Partition.
By default, starting in 'all' deployment profile starts the server as part of a JBoss partition.
./run.sh -c all -b <Binding Address>
7. Starting multiple server instances on the same host
A. Create multiple deployment profiles as per requirements
B. Use a different port-set to start the individual servers
ports-01, ports-02, ports-03 and ports-04 are predefined port-sets
./run.sh -c node1 -Djobss.service.binding.set=ports-01 -b <Binding Address>
Identifying JBoss target discovery parameters
Finding the JBoss Application Server Host
1. Login to the JBoss server host machine commandline. Search for the existing "run.sh" process using the ps command.
Starting Jboss version 5, jboss provides a port by default which should be used during discovery. Hence no additional configuration is needed at the server.
Please see section "Finding the JMX Port" section in this note.
3. Verify that the Enterprise Manager Agent can communicate with the JBoss binding IP address or Hostname and JMX port.
- Login to the EM12C Agent machine command line.
ping <JBoss Binding IP address or Hostname>
- If this fails the agent machine has no network connectivity to the JBoss Binding IP address or the hostname could not be resolved. Review the section "Identifying JBoss target discovery parameters".
- Troubleshoot any network connectivity issue with the network/system administrators.
telnet <JBoss Binding IP address or Hostname> <JMX Port>
- If connection is refused, the port is either blocked by a firewall, incorrectly identified or JBoss application server is not running. Review the section "Identifying JBoss target discovery parameters"
Discovery - Step 1
Discovery - Step 2
Discovery - Step 3
Discovery - Step 4
Discovery - Step 5
Discovery - Step 6
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|JBoss Target Model|
|Steps to install, initial setup and starting JBoss|
|Identifying JBoss target discovery parameters|
|Finding the JBoss Application Server Host|
|Finding the JBoss Application server Install home|
|Finding the JNDI Port ( EM 126.96.36.199.0 - Fusion Middleware Plugin 188.8.131.52.0 and lower )|
|Finding the JMX Port ( EM 184.108.40.206.0 - Fusion Middleware Plugin 220.127.116.11.0 and higher )|
|EM 18.104.22.168.0 - Fusion Middleware Plugin 22.214.171.124.0 and lower|
|Remote and Local Monitoring Prerequisites|
|Local Monitoring Prerequisite|
|Remote Monitoring Prerequisite|
|EM 126.96.36.199.0 - Fusion Middleware Plugin 188.8.131.52.0 and higher|
|Remote and Local Monitoring Prerequisites|
|Known JBoss Discovery Issue|
|Upload the following information for Oracle Supports' assistance|