Understanding PSOs

As mentioned in the previous section, targets manage Provisioning Service Objects (PSOs). A PSO is somewhat analogous to a view in Waveset, but without behavior. Consequently, you can think of a PSO as the data portion of an Waveset view, a User view in particular.

Waveset only manages Users and requires you to define a user extended attribute called spml2ObjectClass.

For Waveset’s purposes, a PSO is a collection of attributes that are mapped (using a form) to and from a User view. Each object specifies an objectclass attribute that is used to map the object to an objectclass definition in the schema defined for the target.

The objectclass attribute is used to find the following:

• A repoType that is provided to support additional targets later

• A form that maps the attributes to and from the Waveset view