User guide

Chapter 7. Establish monitoring with JBoss Operations
Network (JON)
With your business application deployed to a correctly-configured AMI instance, the next step is to
establish monitoring of the platform with JBoss Operations Network (JON).
The JON server is commonly located inside a corporate network, so it's necessary to establish a secure
connection between the server and each of its agents. Establishing a VPN between the two points is the
most common solution but this complicates the required networking configuration.
This chapter provides network configuration guidelines for enabling communication between the JON
agent and JON server. For more extensive information on JBoss Operations Network's configuration,
management and usage refer to the Red Hat documentation.
Figure 7.1. Network connectivity between JON Server and it s agents
7.1. Connectivity Requirements
Registering a JON agent with its servers requires two- way communication between agent and servers.
The JON Agent needs access to port 7080 (or 74 43 in case SSL is used) on all JON servers, and
each JON server must be able to access each of the connected agents on a unique IP:TCP port pair
(agent port is usually 16163).
If there are multiple, clustered JON servers, make sure each agent can communicate with all servers in
the JON cluster via the IP/hostname pairs as configured through the JON server administration console.
The JON server used by the agent to register may not be the server it tries to use after initialization.
7.2. Network Address Translation (NAT)
A corporate VPN gateway acting in routed mode greatly simplifies network configuration. However, if the
Chapter 7. Establish monitoring with JBoss Operations Network (JON)
25