Index Changes

Composite Application Manager (CAM)


The Composite Application Manager provides management and monitoring functionalities for composite applications and components (SE and BC) deployed in the JBI container. It provides a runtime view of the composite applications and components and allow you track the health, performance and message recovery of your JBI system.

Overview

Composite Application Manager provides the following high level set of functionalities
  1. Basic core management and monitoring capabilities for multi-layered views that would allow you could drill down into the components for more detailed views. For instance, you could view the overall application/component performance or statistics, then drill down into the BP process artifacts for more in-depth view. The list of managed components includes:
    • composite applications
    • components (SEs and BCs)
  2. Enhanced management services for SOA applications and components. This includes:
    • Alerting SE (includes alert throttling, forking)
    • Logging SE
    • Message Recovery SE
    • Message Tracker SE

Scope

The scope of Composite Application Manager is limited to management and monitoring of composite applications, SEs and BCs in a JBI container. Enterprise-level view is not in-scope.

Functional Specs

Project Plans

Resources

Team Members

  • Yoke Lee (Project Lead)
  • Gopalan Raj (Architect)
  • Reuven Damir
  • Vladimir Raguimov

BP Visualizer is a tool for analyzing and visualizing business data. You can plot different kinds of graphs (pie,line,timeseries,bar,etc), spot trends, and perform analysis on your data.

Quick guide to setup your tooling environment to use the BP Visualizer

  • Setup the BPEL DB connection
  • Enable Persistence in the BPEL SE runtime configuration
  • Create and Map simple variablies in your NetBeans BPEL editor
  • Plot your business data in the BP Visualizer

Detailed instructions

Aspect-Orientation for Mashups can be used by administrators weave non-functional concerns into the Mashup fabric through a facade pattern and change the behavior of the composite application at runtime.

For readers interested in the work that has gone into Aspect-Oientation for Enterprise Mashups, please click here to learn more about it.

The statistics collected by the components are the JBI Message Exchange statistics. For each service invocation, the Message Exchange pattern used determines which statistical parameters are collected. For example, a In-only Message Exchange pattern, only the requests statistical paramaters are collected.

The statistics collections are tabulated at multi-level views - per endpoint, per Service Unit and per Service Enginer/Binding Component.

Note: The statistical data are not persisted to DB. Hence, if you restart the JBI Container, all the statistics are cleared out.

Implementation Details

Sample screen shot

The configuration page allows the configuration of runtime and environment properties of components (BC/SE) and service units.

For a cluster profile, you can select an specific instance configuration and apply the changes to one or more instances in the GlassFish Admin Console.

Schema Data Validation is available if the component supports it.

Implementation Details

Sample screen shot

Component Configuration

  • How do I turn on single-sign-on?
    In the GF Admin Console, check the SSO checkbox and recycle your browser.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-18) was last changed on 01-Oct-07 11:41 AM, -0700 by MarkWhite