Oracle Waveset 8.1.1 Deployment Guide

Map the Attributes

Generally, you set options for the adapter type by mapping the incoming resource attributes to the standard Waveset account attributes or by creating your own custom attributes (called extended schema attributes).

Your resource must define resource attributes and set default values for resource attributes for which it makes sense to have default. The resource does not have to present the prototypeXML object.


Note –

The attributes in SkeletonActiveSyncResourceAdapter are mandatory. Do not delete these attribute definitions when customizing the file.


Mapping Resource Attributes to Standard Account Attributes

To map incoming resource attributes to one of the standard Waveset account attributes, use the syntax shown in the following example.


Example 10–3 Mapping a Resource Attribute


"<AccountAttributeTypes>\n"+ <AccountAttributeType name=’accountId’ mapName=’change-value-here’
mapType=’string’ required=’true’>\n"+ "<AttributeDefinitionRef>\nt"+  <ObjectRef type=’AttributeDefinition’
name=’accountId’/>\n"+ "</AttributeDefinitionRef>\n"+ "</AccountAttributeType>\n"+
 "</AccountAttributeTypes>\n"+

Where:

Table 10–13 <AttributeDefinitionRef> Element Fields

Element Field  

Description  

name

Identifies the Waveset account attribute to which the resource attribute is being mapped. (The left column on the resource schema page in the Waveset User Interface.) 

mapName

Identifies the name of the incoming resource attribute. When editing the skeleton file, replace change-value-here with the resource attribute name.

mapType

Identifies the incoming attribute type, which can be string, int, or encrypted. 

For more information on mapping resource attributes to account attributes, see Map the Attributes.

Mapping Resource Attributes to Extended Schema Attributes

To map incoming resource attributes to attributes other than a standard Waveset attribute, you must create an extended schema attribute. The following example illustrates how to map a resource attribute to an extended schema attribute.


Example 10–4 Mapping a Resource Attribute to an Extended Schema Attribute


<AccountAttributeType name=’HomeDirectory’ type=’string’ mapName=’HomeDirectory’
mapType=’string’>\n"+ </AccountAttributeType>\n"+

You do not have to declare an ObjectRef type. The mapName field identifies the custom account attribute HomeDirectory. You define the mapType field the same as you would when mapping an attribute to a standard account attribute.