This Schema is used to provide common framework components for the OSS/J XML Interfaces. This Schema was generated by the OSS Through Java XML Toolkit Doclet 1-26-2004 7:3

Returns the supported granularity periods for the provided ActivityValue
 or, if the value is null, return the summary of all supported granularity
 periods.
 This operation returns a list of granularity periods that can be used
 when a measurement job shall be created, with the specified definition
 of the measurement job.
 If no granularity period is supported for the specified instances and
 attributes, an empty array shall be returned.
 The returned granularity periods shall be a factor or a multiple of a
 hour.

Interface for the Activity Creation event
 Raised by an OSS/J application, when an activity has been created.

Defines enumeration values for report mode.
 The report mode for the measurement results can be done in different
 ways. The following report modes exists:
 <ul>
 <li> event per measurement job.
 <li> event for multiple measurement jobs.
 <li> report file per measurement job.
 <li> report file for multiple measurement jobs.
 <li> proprietary mechanism per measurement job.
 <li> proprietary mechanism for multiple measurement jobs.
 <li> iterator per measurement job.
 <li> iterator for multiple measurement jobs.
 </ul>
  <p>
 If the reporting mode is set to event the system will emit an event
 that carries the measurement result report. If the reporting mode is set to
 file, the measurement job will capture the measurement result reports into
 a data storage and then emit an event to the client about the availability
 of the data. If the reporting mode is set to proprietary then the proprietary
 of the data. If the reporting mode is set to iterator, then the system will
 emit an event that includes the iterator.  The frequency of this event is
 det ermined by the data storage creation frequency. When a client receives
 an event of data availability, the client can retrieve the data, by using
 appropriate mechanism.
 <p>
 Also, the support for stream oriented protocol makes it
 real-time report forwarding feasible with no inherent delays
 introduced by Activity Scheduling mechanism.
 <p>
 Example stream oriented protocols supported could include
 FTP, HTTP/HTTPS or low-level RAW SOCKET (or SSL socket) based transfers.
 The details of the actual transfer primitives are currently out of
 scope of
 this API specification and are left to individual implementaion.
 <p>

This interface is an enumeration of the
 valid values for the Control State of an ActivityValue

Interface for the Activity Removal event
 Raised by an OSS/J application, when an activity has been removed
 by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the removal of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity Reporting Results Availability
 notification.
 Raised by an OSS/J implementation, when an Activity has
 report results ready, to be sent to the client.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Suspend event
 Raised by an OSS/J application, when an activity has been temporarily
 suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the suspension of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the sending Activity Report Data in a
 notification to the client.
 <p>
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Resume event
 Raised by an OSS/J application, when an activity is resumed,
 after it has been temporarily suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the resumption of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity events.
 Raised by an OSS/J application, when individual Activities are
 created or removed or when there is a change an activity's
 Control Status.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.

This interface is an enumeration of the
 valid values for the Execution State of an ActivityValue

Stylus Studio XML Schema Library Home

Site Map | Privacy Policy | Terms of Use | Trademarks

Stylus Scoop XML Newsletter:

Stylus Studio®, a product from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2006 All Rights Reserved.