Chapter 2. New Features

2.1. Features - Technical Preview 2

Monitor EAP in OpenShift

You can now use the Middleware Manager and CloudForms to monitor Red Hat JBoss Enterprise Application Platform servers running in containers on Red Hat OpenShift Container Platform. Red Hat is now shipping EAP 6 and EAP 7 containers through the Red Hat Container Catalog that includes an agent that allows for monitoring with the Middleware Manager and CloudForms. The CloudForms user interface has been enhanced to display the relationships between containers and the EAP servers running in those containers. The CloudForms interface has also been modified to disable operations on EAP servers when those servers are running in containers on OpenShift.

Run the Middleware Manager in OpenShift

An OpenShift Template is available for running the Middleware Manager and the Storage Node in OpenShift. This Template is intended to be used on conjunction with the CloudForms OpenShift template for running CloudForms in OpenShift.

Secure Communications with CloudForms

The Middleware Manager can now be configured for secure SSL communication with CloudForms.

Note

The only supported security protocols for the current release are SSL without validation and Non-SSL.

RPM distributions of EAP agents

The EAP agents are now distributed in the EAP 6 and EAP 7 RPM Package Manager channels for users who are provisioning their Red Hat JBoss Enterprise Application Platform servers via RPMs. 

2.2. Features - Technical Preview 1

The middleware provider provides several dedicated views of important middleware server groupings. You can view Enterprise Application Platform (EAP 6 and 7) domains and server groups, and drill down to view the availability and state of your middleware servers.

Figure 2.1. Provider Summary Screen

Provider Summary

Middleware Provider Inventory

When viewing the discovered inventory, Red Hat JBoss Enterprise Application Platform (EAP 6 and 7) Servers can have parent relations to the following entities:

  • Middleware Provider
  • Virtual Machines
  • EAP Server Group

EAP Servers can have child relations to the following entities:

  • Deployments
  • DataSources
  • Message Brokers

Middleware Provider Power Operations

Using the middleware provider you can perform the following power operations on EAP 6 and 7 servers:

  • Gracefully Shutdown Server - rejects new sessions and allows sessions to complete
  • Restart Server - restarts the Java Virtual Machine (JVM)
  • Stop Server - stop the session and shutdown the JVM.
  • Suspend and Resume - stop sessions but do not shutdown
  • Reload Server - restarts the server but not the JVM
Note

The technical preview does not yet support the "start" operation.

Middleware Provider Datasources

For standalone EAP servers you can create datasources. You can also create datasource drivers for all supported EAP databases and add user provided drivers.

Middleware Provider Application Deployment

For standalone EAP servers you can add application deployments.

Middleware Provider Monitoring

The middleware monitor provides a timeline view where you can see:

  • Alerts triggered by

    • Heap Used
    • Non Heap Used
    • Garbage Collection

  • Events tracked

    • Application Deployement
    • Application Undeployment
    • Datasource Deployment
    • Datasource Undeployment

The middleware provider monitors local capacity and utilization, including the utilization of the following resources:

  • Datasource availability

    • Available
    • In Use
    • Timed Out

  • Datasource responsiveness

    • Creation Time
    • Get Time
    • Wait Time
  • Garbage Collection Duration

  • JVM Heap Memory

    • Committed
    • Max
    • Used

  • JVM Non-Heap Memory

    • Used Committed

  • Messaging

    • Delivering Message Count
    • Durable Message Count
    • Non-durable Message Count
    • Messages Added
    • Messages Count

  • Messaging Subscribers

    • Durable Subscribers
    • Non-durable Subscribers
    • Subscriptions

  • Transactions

    • Aborted
    • Application Failure
    • Committed
    • Heuristic
    • Resource Failure
    • Timed-Out

  • Web Sessions

    • Active
    • Expired
    • Rejected

Middleware Provider Reports

The middleware provider comes with the following pre-configured reports:

  • JVM Heap and Non-heap consumption
  • JVM Garbage Collection
  • EAP JTA Transactions

Middleware Provider Topology

The middleware provider includes an interactive user interface that allows you to view the network topology of managed entities, including the following:

  • Datasources
  • Deployments
  • EAP Domains
  • Messaging (Queues/Topics)
  • EAP Servers
  • EAP Server groups
  • Virtual Machines

Figure 2.2. Topology View

Topology View"