Index Changes
View Info
This is version 7. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Common Client Tasks

This document will summarize the changes needed to the common client, for each of the initiatives in the Sierra Update.

Application Configuration

This is the most complicated area, and Yunpeng, Nikita, and I are still making sense of this one... all that I can say right now is that this will be the busiest initiative (as far as changes to the common client).

Additional commands will be needed for the following tasks (at a minimum):

  • Create new application configuration
  • Delete application configuration
  • edit application configuration
  • list application configurations

Until this is fully fleshed out, the time estimate of 3 weeks (to write interfaces and code, followed by additional time for testing) is very rough.

M2 Plan

  • Static configurations (not including environment variables)

M3 Plan

  • environment variables
  • named configurations

Component Upgrade

It is unclear if the "component update" is simply being deprecated or replaced with the new "component upgrade", but either scenario is simple for the common client.

One new command (component upgrade) is to be added. In addition, the existing command (component update) will be removed.

Time estimate: Annies already changed the "updateComponent" method to call the "upgradeComponent" method on the components. All that is left is renaming the common client method to "upgradeComponent." This should take 1 day.

M2 Plan

  • full implementation

Logging

Runtime Logging:

New commands will be added:
  • to get a list of all runtime loggers and their levels,
  • to get one runtime logger and its level,
  • to set one runtime logger's level.

Time estimate: 3 days. Integrated on Friday, Sepember 7th (IN 109677 ).

M2 Plan

  • full implementation

Component Logging:

The Common Client currently uses a JMX query to get a list of all of the LoggerMBeans for a component in order to provide a list of logger names to the administrative clients. That needs to be changed to make a single call to the LoggerMBean to get the list of logger names.

This should take 1-2 days.

M2 Plan

  • full implementation

Password handling

This has no changes on the Common Client.

Recovery

This has no changes on the Common Client.

Runtime Monitoring

A few new commands will be added to obtain/present all the monitoring data, as well as some subsets.

Time estimate: One week.

M3 Plan

  • full implementation

Security and Transaction Propagation

This has no changes on the Common Client.

Wire Qualities

This has no changes on the Common Client.

Use Cases

Design Details

Application Configuration

This area still (actively) being worked on. It is still not clear which part of the existing API is working. The current API is as follows: 

Map<String /* targetInstanceName */, Properties /* configProps */> getComponentConfigurationProperties(
            String componentName, String targetName);

Properties /* targetInstanceName, success/failure */ setComponentConfigurationProperties(String componentName,
            Properties /* configProps */configurationValues, String targetName)
            throws JBIRemoteException;

Proposed new API:

CRUD Commands to manipulate a static configuration for the runtime

CRUD Commands to manipulate a static configuration for a component

CRUD Commands to manipulate a named configuration for a component

Component Upgrade

The following new method will augment (not replace!) the existing similar updateComponent command: 

public String upgradeComponent(String componentName, String zipFilePath)

Logging

Runtime Logging:

The following three new methods will be added: 
public Map<String /* runtimeLoggerName */, Level /* logLevel */> getRuntimeLoggerLevels(
            String targetName, String targetInstanceName)
            throws JBIRemoteException;

public Level getRuntimeLoggerLevel(
            String runtimeLoggerName,
            String targetName, String targetInstanceName)
            throws JBIRemoteException;

public void setRuntimeLoggerLevel(String runtimeLoggerName,
            Level logLevel, String targetName, String targetInstanceName)
            throws JBIRemoteException;

Component Logging:

No changes to the API (just to the implementation) planned.

Password handling

This has no changes on the Common Client.

Recovery

This has no changes on the Common Client.

Runtime Monitoring


Properties getJbiStatistics(String targetName); // get all statistics;

Properties getJbiFrameworkStatistics(String targetName); // get just Framework statistics;

Properties getJbiNmrStatistics(String targetName); // get just NMR statistics;

Properties getJbiComponentStatistics(String targetName);  // get all component statistics;
Properties getJbiComponentStatistics(String componentName, String targetName);  // get component statistics for the given component;

Properties getJbiEndpointStatistics(String targetName); // get all endpoint statistics;
Properties getJbiEndpointStatistics(String endpointName, String targetName); // get endpoint statistics for the given endpoint;

Security and Transaction Propagation

This has no changes on the Common Client.

Wire Qualities

This has no changes on the Common Client.

G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This particular version was published on 07-Sep-07 16:33 PM, -0700 by Marc_Kriguer