IBM ACEL 1.2
Manuals and User Guides for IBM ACEL 1.2. We found 1 manuals for free downloads User's Guide
Below you will find brief information for ACEL 1.2, PMAC 1.2. The Autonomic Computing Expression Language (ACEL) is a strongly typed, XML-based declarative language designed for expressing complex calculations, particularly in system management. This guide details its semantics, including a rich set of datatypes and functions, and how ACEL expressions are represented in XML. It also covers the Policy Management for Autonomic Computing V1.2 (PMAC 1.2) implementation, which provides parsing and evaluation capabilities for ACEL expressions, making it suitable for rapid authoring and validation.
Key Features
Rich set of nine primitive and two composite datatypes
Strongly typed expression language with XML schema enforcement
Extensible by deployers while retaining strong typing
Comprehensive timezone specification with date and time values
Intuitive XML representation for expressions
Support for PropertySensor and OperationSensor for dynamic values
Parser and evaluator provided by PMAC 1.2 implementation
Wide array of numeric, boolean, string, and calendar functions
Frequently Answers and Questions
What is Autonomic Computing Expression Language (ACEL)?
ACEL is an XML-based declarative expression language, initially developed as part of the Autonomic Computing Policy Language, designed to express calculations of new values from existing ones, especially suited for system management contexts.
What are some distinguishing features of ACEL?
ACEL provides a rich set of datatypes and functions, is strongly typed with XML schema enforcement, is extensible by deployers while preserving type constraints, and includes a comprehensive timezone specification for unambiguous time instances.
What datatypes does ACEL provide?
ACEL offers nine primitive datatypes (Boolean, Short, Integer, Long, Float, Double, String, Calendar, URI) and two composite datatypes (CompositeData and Collection).
How are variables represented in ACEL expressions?
Variables in ACEL can be represented by the PropertySensor element, which has an associated type, or by the OperationSensor element, which is specified by a 'portType', 'operationName', and arguments, allowing для invoking callout functions.
What are the main interfaces provided by PMAC 1.2 implementation of ACEL?
The PMAC 1.2 implementation of ACEL provides three main interfaces: Expression (representing an ACEL expression in Java), SensorLookup (for looking up PropertySensor and OperationSensor values), and ExpressionFactory (to create ACEL expressions).
How does ACEL handle type conversions for numeric operations?
For numeric operations, ACEL follows specific conversion rules: if no operand is Float/Double and at least one is Long, the result is Long; otherwise, if no Float/Double, the result is Integer. If at least one operand is Double, the result is Double, and if at least one is Float (and no Double), the result is Float.
advertisement