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