Red Hat Training

A Red Hat training course is available for Red Hat JBoss Operations Network

3.5. Additional Post-Setup Checklist

Once the JBoss ON server is configured, there are a number of different areas that administrators can configure to set up and manage resource in JBoss ON and to configure JBoss ON itself.
Most of the initial setup — building out the JBoss ON inventory with managed resources, setting up roles and access control, and creating resource groups — is covered in Initial Setup: the Resource Inventory, Groups, and Users. JBoss ON has a number of other features like drift monitoring, alerting, application and content deployment, server high availability, and configuration management. The way that these are configured depends on the demands of your infrastructure. Table 3.2, “Configuration and Features to Set Up” has links to procedures for features which are commonly set up soon after JBoss ON is set up; browse the JBoss ON GUI and documentation for a more comprehensive view of JBoss ON's capabilities.

Table 3.2. Configuration and Features to Set Up

Feature Description Doc Link
Creating resource groups For simplicity and effectiveness with managing resources, JBoss ON has resource groups. There are a number of different types of groups, including compatible groups (groups of the same type of resource) and dynamically-created groups. This makes it possible to apply configuration changes, alert definitions, drift definitions, and other settings all at once and to create useful groups for better monitoring and inventory tracking. "Managing Groups"
Configuring roles and access control JBoss ON defines access to resources based on roles. Both users and resources are assigned to roles, and then access control rights are assigned to the roles. "About Security in JBoss ON: Roles and Access Control"
LDAP user authentication By default, users are created in JBoss ON and then stored in the JBoss ON database. However, JBoss ON can be configured to check an LDAP server first for user accounts, so existing LDAP users can be authenticated in JBoss ON — without having to create users in JBoss ON first. "How JBoss ON Uses LDAP for Authentication"
LDAP group authorization LDAP groups can be associated with JBoss ON roles. This means that the members in the LDAP group are automatically granted the rights and can manage the resources defined in the JBoss ON role. "How JBoss ON Roles Work with LDAP User Groups"
Creating alerts An alert is a way of informing administrators that some event or condition has occurred on a resource. JBoss ON provides a number of different ways to set and respond to alerts, both by sending notifications and by taking a specified action. "Brief Introduction to Alerts and Notifications"
Configuring drift monitoring When configuration settings change, the configuration drifts from its designated state. Drift monitoring provides a mechanism for administrators to define and manage that designated configuration state, to apply it to multiple resources, and to be informed if any resource drifts from that state. "Understanding Drift"
Setting up bundles for provisioning Provisioning is a way of deploying content through JBoss ON. Provisioning takes a bundle, an archive file, and deploys it on a platform or a JBoss resource. This bundle can be a configuration file, a set of EARs or WARs, or even a full application server. JBoss ON supports multiple versions of the same bundle and can deploy these bundles to different resources, all managed through a single point in JBoss ON. "Creating Bundles"
Setting affinity and high availability When multiple JBoss ON servers are added, they naturally establish a high availability and failover topology. Agents can be managed by any server in the cloud, but it is possible to set a preference, or affinity, for agents to be managed by selected servers. This can improve performance or be used to reflect the infrastructure topology. "Configuring High Availability"