Usage Notes

Choosing Business Objects and Components

By default, the Siebel CRM adapter uses the Employee Siebel business component of the Employee Siebel business object for account provisioning. However, you can configure the adapter to use any Siebel business component of any Siebel business object for account provisioning.

• To use a different business object, set the Account Business Object resource parameter appropriately.

• To use a different business component, set the Account Business Component resource parameter to the name of the preferred business component.

You must specify the business component within the specified business object.

You can use the Siebel Tools Client to inspect your business component and to verify which attributes are available for provisioning. The default schema map has some common attributes that are useful for the default Employee business component.

You may have to add, remove, or change attributes to manage your Siebel environment– especially if you have configured the adapter to use a business object or business component other than the default.

The following steps are a basic guide to discovering which attributes Identity Manager can provision to your Siebel environment using the Siebel Tools client:

Identifying Attributes for Provisioning to a Siebel Environment

1. Open the Siebel Tools’ Object Explorer.

2. Click the Business Component icon.

3. Scroll down or create a query to select the desired business component.

4. Select Fields within the Object Explorer.

   A list of fields available to the bus-iness component should display.

   The field Name column values shown in the Object Explorer are typically used for the right-hand side (or the Resource User Attribute), within the schema map of your configured Siebel CRM resource.

   In general, you can manage any of these fields to some degree. However, if you want to manage a multi-valued field or a pick-list field, you must specify a different format for the right-hand side of the schema map, as follows:

   • For a multi-valued field: The right-hand side must use the field@@keyAttr format, where:

     • field represents the name of the multi-valued field

     • keyAttr represents the name of a field within the associated multi-valued business component used to uniquely identify each member of the multi-valued list.

       For example: Position@@Name

     For a pick list field: The right-hand side must use the field!!keyAttr format, where:

     • field represents the name of the pick list field

     • keyAttr represents the name of a field within the associated pick-list business component used to uniquely identify a member of the pick list.

       For example: Employee Organization!!Name

Managing Primary Values in Multi-Value Groups

The adapter performs the following actions when a multi-value group (MVG) already contains a single member that is designated as primary:

• If the incoming MVG contains a single value that is different than the value currently defined in Identity Manager, then the new value will be inserted and marked as the primary. The previous value is then removed from Identity Manager.

• If other non-primary values have been added, by default, the primary value will remain unchanged.

If there are currently multiple values in an MVG with one of the values marked as the primary:

• If any non-primary values are deleted from the set, the current primary will remain as the primary.

• If the MVG value set is replaced with a new single value, then the new single value will be inserted and marked as the primary. All previous values are then removed.

• If other non-primary values have been added, by default, the primary value will remain unchanged.

To move a primary marker from an existing value to a new value when multiple values exist, you must add an account attribute to the schema map. The name of this attribute must be in the form “Primary MVG_Name”, where MVG_Name is a value such as Employee Organization Id or Position. Therefore, the attribute will have a name such as Primary Employee Organization Id or Primary Position. Then, in the user form, set the Primary attribute to the desired value.

Advanced Navigation

The advanced navigation feature of the Siebel CRM adapter allows you to create and update child business components. This is an advanced feature that is not typically implemented in Identity Manager.

The advanced navigation feature allows you to optionally specify the following information needed to create and update child business components:

• business object name

• parent business component name

• parent search attribute

• target business component

• target search attribute

• in scope attributes (which attributes of the business component should be set/updated)

• optional co-action

An advanced navigation rule can be used during create and update actions. It cannot be used for other types of actions.

To implement the advanced navigation feature of the Siebel CRM adapter, you must perform the following tasks:

• Add an attribute to the schema map in which the Resource User Attribute (right hand side) is named PARENT_COMP_ID.

• Use the debug page to manually add the following ResourceAttribute to your resource’s XML

  <ResourceAttribute name=’AdvancedNavRule’
      displayName=’Advanced Nav Rule’
      value=’MY_SIEBEL_NAV_RULE’>
  </ResourceAttribute>

  Replace MY_SIEBEL_NAV_RULE with a valid rule name.

• Write the advanced navigation rule. The rule should expect two variables to be present:

  resource.action. The value must be either create or update.

  resource.objectType. For normal account maintenance, this value will be account.

  The rule must return a map with one or more of the following name/value pairs:

An example navigation rule is provided in $WSHOME/sample/rules/SiebelNavigationRule.xml.