Nodes (host controllers)
Add an admin user for JON to login
./add-user.sh
Add an http interface for JON to interact with the node (https://access.redhat.com/solutions/147513)
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.native.port:9999}"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
Setup server up/down alerts
EAP Host Controller -> Managed servers -> EAP h1-server1
Alerts
Definitions -> New
name: server up
priority: medium
Conditions -> Add
Condition Type: Availability Change
Availability: Goes Up
Recovery
Disable When Fired: Yes
Back to List (Definitions) -> New
name: server down
priority: high
Conditions -> Add
Condition Type: Availability Change
Availability: Goes Down
Recovery
Recover Alert: server up
Check for alerts: Alerts -> History
example Test
EAP Management -> Domain -> Overview
h1-server1 -> Stop Server
Check for Alert
EAP Management -> Domain -> Overview
h1-server1 -> Start Server
Check for Alert
Checking Web Server http/ajp traffic
EAP Host Controller -> Managed servers -> EAP h1-server1 -> Subsystems -> Web -> web -> Connector
Monitoring, check http and ajp traffic
Compatible Groups
Inventory -> Compatible Groups -> New
Name: domain eap servers
Next
Select EAP Host/Domain Controller
Working with Compatible Groups
Inventory -> Compatible Groups -> eap servers
Operations -> New
Restart this host controller
Now
in the order below (ripple)
Schedule
History
Restart this host controller
Drift detection
Note:
- Rolling drift, up to 4 snapshots of changes for comparison
- Pinned, based on initial snapshot 0, any changes from that point will be considered out of compliance, return to original in order to return to compliance
- What if I do not want initial snapshot 0, create a new drift config based on new current config
New -> Template-Configuration Files
Drift Definition Name: config drift
Pinned: Yes (declare current config as master)
Interval: 60 (default agent is 60, so can’t go any lower unless agent is changed as well)
Save
Verify JON config drift in compliance
Make changes to config accordingly, for instance:
EAP Management -> Configuration -> full-ha -> Connector -> JCA -> Archive Validation
Is Enabled: false
Verify JON config drift out of compliance
EAP Management -> Configuration -> full-ha -> Connector -> JCA -> Archive Validation
Is Enabled: true
Verify JON config drift in compliance
Patching EAP
Bundles -> Create Bundle
Upload: jboss-eap-6.4.3-patch.zip
Next
Leave bundle unassigned (or assign to bundle group if one is available)