HPOS 3.5 Using -extended-features

HP Output Server 3.5 5

Using -extended-features

About mapper.xml file

HP Output Server utilizes attributes and values to express intent while the destination capabilities are expressed

through features and values. Mapping helps to translate the attributes into their corresponding features so that the

DSM server can properly process the constraints and the invocation strings. Mapping is performed by the DSM

server which uses a file named mapper.xml that exists in the /etc subdirectory of the HP Output Server

installation. This text file enumerates the mappings between the attributes and the features. It contains one-to-one

mappings or multiple-to-one mappings in both directions.

The use of mapping helps to simplify the use of advanced features by allowing you to specify options through

standard HP Output Server attributes and values.Otherwise, you would have to constantly specify the XML

fragments by using the –extended-features attribute.The use of attributes, however, requires an update to both

mapper.xml file and DPAOIDs. So an advanced feature support through attributes is not always immediately

available. The –extended-features attribute needs to be utilized until the next update to these files is available.

Mapping of attributes to the features

Mapping expresses the relationship between attributes and features. Mappings are bi-directional. There are different

ways of expressing mappings between the features and attributes.

The following examples illustrate the different ways to express mapping:

1. Simple feature <--> attribute mapping

In this style of mapping, one HP Output Server attribute is mapped to exactly one feature in the cap ticket.

Examples

• <class name=”copycount">

<attributename="copies"type="cardinal"/>

<!--

The equivalence element under mapping indicates that the attribute and

the feature have the same meaning in the different models. In order to

set one from the other, you just use the value without modification.

-->

<attribute-ref name="copies"/>

<feature-ref name="Copies"/>

</equivalence>

</mapping>

</class>

• <class>

<!--

Note that in this class the feature and attribute both have units. Since

the units are not the same, there is an implied conversion. If a

conversion element is found whose units match the units of the attributes

and features, it will be used. If a conversion is not found,a straight

assignment will be done.