Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide
7-25
Cisco Customer Response Solutions Administration Guide, Release 6.0(1)
Chapter 7 Managing Prompts, Grammars, Documents, and Custom Files
Managing AAR Files
Main Attributes
Main attributes are the attributes that are present in the main section of the
manifest. They fall into three different groups:
manifest. They fall into three different groups:
•
General main attributes: See the following table.
Attribute
Description
Manifest-Version
The manifest file version. The value is a legitimate version number, as
described in the above spec.
described in the above spec.
Created-By
The version and the vendor of the java implementation on top of which this
manifest file is generated. This attribute is generated by the jar tool.
manifest file is generated. This attribute is generated by the jar tool.
Crs-Version
The minimum CRS version release compatible with the AAR file.
Crs-version is the accumulation of the CRS release, CRS Service Release,
and CRS Engineering Special defined in that order. For example, if the AAR
file is compatible with CRS release 4.1(1)_Build705, SR1_Build001,
ES2_Build002, the Crs-Version would be defined as
4.1(1)SR1ES2_Build002. Only the last build number is taken. So for
instance, if the AAR file is compatible with CRS release 4.1(1)_build705,
SR1_Build001, then the Crs-Version is 4.1(1)SR1_Build001. As a last
example, if AAR file is compatible with CRS release 4.1(1)_Build705 and
above, then Crs-Version would be 4.1(1)_Build705.
Crs-version is the accumulation of the CRS release, CRS Service Release,
and CRS Engineering Special defined in that order. For example, if the AAR
file is compatible with CRS release 4.1(1)_Build705, SR1_Build001,
ES2_Build002, the Crs-Version would be defined as
4.1(1)SR1ES2_Build002. Only the last build number is taken. So for
instance, if the AAR file is compatible with CRS release 4.1(1)_build705,
SR1_Build001, then the Crs-Version is 4.1(1)SR1_Build001. As a last
example, if AAR file is compatible with CRS release 4.1(1)_Build705 and
above, then Crs-Version would be 4.1(1)_Build705.
Class-Path
The directories or JAR files that need to be installed and accessed by scripts
directly. Entries are separated by one or more spaces. The CRS class loader
uses the value of this attribute to construct its internal search path where
each entry is defined relative to the /Documents/default/classpath directory
in this AAR file.
directly. Entries are separated by one or more spaces. The CRS class loader
uses the value of this attribute to construct its internal search path where
each entry is defined relative to the /Documents/default/classpath directory
in this AAR file.
Step-Class-Path
The directories or JAR files that need to be installed and accessed by
customer-defined steps directly. Entries are separated by one or more spaces.
The CRS class loader uses the value of this attribute to construct its internal
search path where each entry is defined relative to the
/Documents/default/classpath directory in this AAR file.
customer-defined steps directly. Entries are separated by one or more spaces.
The CRS class loader uses the value of this attribute to construct its internal
search path where each entry is defined relative to the
/Documents/default/classpath directory in this AAR file.
Subsystem-Class-Path
The directories or JAR files that need to be installed and accessed by
customer-defined subsystems directly. Entries are separated by one or more
spaces. The CRS class loader uses the value of this attribute to construct its
internal search path where each entry is defined relative to the
/Documents/default/classpath directory in this AAR file.
customer-defined subsystems directly. Entries are separated by one or more
spaces. The CRS class loader uses the value of this attribute to construct its
internal search path where each entry is defined relative to the
/Documents/default/classpath directory in this AAR file.