Index Changes

Sierra Initiatives Overview

Application Configuration

JBI Runtime:

  • Facade layer for component runtime configuration (config stored in DAS)
  • Support synchronization of component runtime configuration
  • Use static component configuration declaration

Component Runtime:

  • Static declaration of configuration set for off-line support
  • Support for management (add/list/delete) of named configurations

Admin Clients:

  • Application configuration editor for deployment
  • Application configuration management
  • Deploy-time verification
    • All configuration references can be resolved
    • Supplied configuration is valid

Tooling:

  • Fancy UI for all of the items listed under 'Admin Clients'

Component Upgrade

JBI Runtime:

  • Create component SPI contract for upgrade
  • Invoke upgrade contract during component update
  • Allow jbi.xml modifications on component update

Component Runtime:

  • Implement upgrade SPI
  • Internal support for application artifact versioning
    • Component can decide which artifacts need to be upgraded as part of a component update.

Admin Clients:

  • Add update interface to admin gui
  • Add update command to admin CLI

Tooling:

  • Add update interface to JBI Manager

Logging

JBI Runtime:

  • Contribute to logging guidelines specification
    • Make sure guidelines are consistent w/ runtime view
    • Coordinate component and core runtime messages
    • Modify runtime as necessary to match guidelines
  • Tasks not part of initiative but need to be done
    • Change to single logger MBean per JBI component
    • Persist names of all component loggers so that console can list all of them, not just the ones that have been initialized

Component Runtime:

  • Modify component runtime as necessary to match guidelines

Admin Clients:

  • Enhanced support for JBI runtime logger configuration

Password Handling

JBI Runtime:

  • Determine strategy for keystore synchronization

Component Runtime:

  • Common library to provide access to protected store (Alex Fung)
  • Proposal to use PlatformContext for platform-specific keystore access
  • Components needs to use library to store sensitive config data (e.g. passwords) in protected store

Admin Clients:

  • Obfuscate password values in gui

Tooling:

  • Obfuscate password values in gui

Tooling:

  • N/A

Recovery

JBI Runtime:

  • Move to declarative model for XA recovery participation in lieu of private framework interfaces.

Component Runtime:

  • Support recovery (see wiki page)

Admin Clients:

  • N/A

Tooling:

  • N/A

Runtime Monitoring

JBI Runtime:

  • Instrumentation of NMR to determine ME throughput
  • NMR activity monitoring e.g. # of in-process MEs

Component Runtime:

  • External connection status information for binding components
  • Last error/fault for all components

Admin Clients:

  • Monitoring interface for components
  • Monitoring interface for JBI runtime

Tooling:

  • N/A

Security & Transaction Propagation

JBI Runtime:

  • Parent/Child exchange support could become part of spec (NMR) but not in Sierra timeframe

Component Runtime:

  • Create library to manage exchange creation for parent/child exchanges
  • Establish processing conventions related to security and transaction processing in child & parent exchanges
  • Store parent security and transaction context in standard properties

Admin Clients:

  • N/A

Tooling:

  • N/A

Wire Qualities

JBI Runtime:

  • Support for JBI 2.0 interceptors
  • Support for NMR-based throttling of message exchange activity (?)
  • NMR accept() filter (?)

Component Runtime:

  • Inbound request throttling in BCs
  • MEP processing optimizations (e.g. accept status MEs first)

Admin Clients:

  • Configure throttling parameters for JBI runtime and components

Tooling:

  • Editor support for creating JBI 2.0 interceptors

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-1) was last changed on 17-Jul-07 15:51 PM, -0700 by MarkWhite