Sun Java[TM] System Identity Manager 7.1 Resources Reference |
SiebelThe Siebel resource adapter has been deprecated. Use the Siebel CRM resource adapter (described in the next section) instead.
Siebel CRMThe Siebel CRM resource adapter is defined in the com.waveset.adapter.SiebelCRMResourceAdapter class.
This adapter supports the following Siebel versions:
Identity Manager Installation Notes
The Siebel CRM resource adapter is a custom adapter. You must perform the following steps to complete the installation process:
- To add the Siebel CRM resource to the resources list, you must add the following value in the Custom Resources section of the Configure Managed Resources page.
com.waveset.adapter.SiebelCRMResourceAdapter
- Copy the appropriate JAR files to the InstallDir\idm\WEB-INF\lib directory, as listed in the following table.
The JAR file versions must match the version of the Siebel CRM resource:
Resource Configuration Notes
None
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.
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:
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:
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:
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>
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.
Provisioning Notes
The following table summarizes the provisioning capabilities of this adapter.
Feature
Supported?
Enable/disable account
No
Rename account
Yes
Create account
Yes
Update account
Yes
Delete account
Yes
Pass-through authentication
Yes
Before/after actions
No
Data loading methods
Account Attributes
The default schema map assumes that the Employee business object and Employee business component are configured. You might 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.
Security Notes
This section provides information about supported connections and privilege requirements.
Supported Connections
Identity Manager can use HTTP or RSA to communicate with the Siebel CRM adapter. (See the Siebel user documentation for more information.)
Required Administrative Privileges
Ensure the administrator user name/password configured for the adapter is assigned sufficient privileges within Siebel to create new records and to update existing records for the specified business component.
Resource Object Management
By default, the Siebel CRM adapter supports the following Siebel objects:
If necessary, you can manually configure the adapter to support additional resource object types by editing the resource prototype XML as follows:
- Add a new <ObjectType> element to the XML, following the default Employee:Position object type example.
- Replace Employee with the name of the preferred Siebel business object.
- Replace Position with the name of the preferred Siebel business component.
- Verify that the embedded <ObjectAttributes> element has an idAttr attribute that names which <ObjectAttribute> will be used to uniquely identity each item in the business component.
Identify Template
The default identity template is $accountId$.
Sample Forms
The following sample forms are provided with this resource adapter:
Troubleshooting
Use the Identity Manager debug pages to set trace options on the following class:
com.waveset.adapter.SiebelCRMResourceAdapter
Additionally, you can set the following Identity Manager Active Sync logging parameters for the resource instance: