Siebel JDBAdapter User Guide - IBM · PDF fileIBM Security Identity Manager Version 6.0 Siebel...

IBM Security Identity ManagerVersion 6.0

Siebel JDB Adapter User Guide

SC27-4418-02

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 45.

Edition notice

Note: This edition applies to version 6.0 of IBM Security Identity Manager (product number 5724-C34) and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2012, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

Preface . . . . . . . . . . . . . . viiAbout this publication . . . . . . . . . . viiAccess to publications and terminology . . . . . viiAccessibility . . . . . . . . . . . . . . viiiTechnical training . . . . . . . . . . . . viiiSupport information . . . . . . . . . . . viiiStatement of Good Security Practices . . . . . viii

Chapter 1. Introduction to the SiebelJDB Adapter . . . . . . . . . . . . . 1Features of the Siebel JDB Adapter . . . . . . . 1

Chapter 2. Checklist for configuring IBMSecurity Identity Manager to run theadapter . . . . . . . . . . . . . . . 3

Chapter 3. Configuration of view modesof business components . . . . . . . 5View modes in the custom XML files . . . . . . 5Configuration of the MVGBusComponent view mode 7

Reconciling custom values of theMVGBusComponent for support data . . . . . 7Reconciling custom values of theMVGBusComponent for user data . . . . . . 8Adding or modifying User or Employee withcustom values for the MVGBusComponent . . . 8

Chapter 4. Siebel JDB Adapter useraccount management tasks . . . . . . 11Reconciliation of user accounts . . . . . . . . 11

Reconciling supporting data . . . . . . . . 12User accounts . . . . . . . . . . . . . 12

Attributes for adding user accounts . . . . . 13User account modification . . . . . . . . . 14

Password change of user accounts . . . . . . 16User account suspension . . . . . . . . . . 16User account restoration . . . . . . . . . . 16User account deletion . . . . . . . . . . . 16

Chapter 5. Customization of the SiebelJDB account form . . . . . . . . . . 17Types of business component attributes . . . . . 17

Attributes in custom XML files . . . . . . . . 17Adding an attribute to the Siebel JDB account form 18Attribute for the adapter profile . . . . . . . 19Mapping attributes . . . . . . . . . . . . 20

Assembly line icons . . . . . . . . . . 20Mapping attributes to the siebelJDBAddassembly line . . . . . . . . . . . . . 21Mapping attributes to the siebelJDBModifyassembly line . . . . . . . . . . . . . 22Mapping attributes to the siebelJDBSearchassembly line . . . . . . . . . . . . . 23

Chapter 6. Reconciling new supportdata attributes . . . . . . . . . . . 27Custom XML file . . . . . . . . . . . . 28Attributes for the schema.dsml file . . . . . . 28Adding a connector to the siebelJDBSearch assemblyline . . . . . . . . . . . . . . . . . 29Connection parameter mapping details for theservice.def file . . . . . . . . . . . . . 30

Chapter 7. Troubleshooting of theSiebel JDB Adapter . . . . . . . . . 31

Appendix A. Adapter attributes . . . . 33

Appendix B. Definitions for ITDI_HOMEand ISIM_HOME directories . . . . . . 37

Appendix C. Support information . . . 39Searching knowledge bases . . . . . . . . . 39Obtaining a product fix . . . . . . . . . . 40Contacting IBM Support . . . . . . . . . . 40

Appendix D. Accessibility features forIBM Security Identity Manager . . . . 43

Notices . . . . . . . . . . . . . . 45

Index . . . . . . . . . . . . . . . 49

© Copyright IBM Corp. 2012, 2014 iii

iv IBM Security Identity Manager: Siebel JDB Adapter User Guide

Tables

1. Checklist for configuring IBM Security IdentityManager . . . . . . . . . . . . . . 3

2. Installation directories . . . . . . . . . 43. Custom XML files used for user account

management . . . . . . . . . . . . 54. Default values of view modes for different

business components . . . . . . . . . . 65. Default values of view modes for MVG

business components and PickList businesscomponents in the UserList.xml file . . . . 6

6. View mode specification in the custom XMLfiles . . . . . . . . . . . . . . . 7

7. Required attributes for adding user accounts 138. Required attributes for adding user accounts

as Employee . . . . . . . . . . . . 139. Definition of attributes in a custom XML file 17

10. Assembly line icons . . . . . . . . . . 2011. Connectors of the siebelJDBAdd assembly line 2112. Connectors of the siebelJDBModify assembly

line . . . . . . . . . . . . . . . 22

13. Connectors of the siebelJDBSearch assemblyline . . . . . . . . . . . . . . . 24

14. Error messages and suggested actions. . . . 3115. Attributes, descriptions, and corresponding

Siebel attributes for erTDISblJDBAccount . . . 3316. Attributes, descriptions, and corresponding

Siebel attributes for erTDISblResponsibility . 3417. Attributes, descriptions, and corresponding

Siebel attributes for erTDISblPosition. . . . 3418. Attribute, description, and corresponding

Siebel attribute for erTDISblTZones . . . . . 3519. Attribute, description, and corresponding

Siebel attribute for erTDISblTitles . . . . . 3520. Attribute, description, and corresponding

Siebel attribute for erTDISblEmpNotify . . . 3521. Attribute, description, and corresponding

Siebel attribute for erTDISblEmpAvail . . . . 3522. Attributes, descriptions, and corresponding

Siebel attributes for erTDISblBU . . . . . . 35

© Copyright IBM Corp. 2012, 2014 v

vi IBM Security Identity Manager: Siebel JDB Adapter User Guide

Preface

About this publication

The Siebel JDB Adapter User Guide provides the basic information that you can useto complete Siebel administrative tasks with the IBM® Security Identity ManagerSiebel Java™ Data Beans Adapter (Siebel JDB Adapter).

The Siebel JDB Adapter enables connectivity between the IBM Security IdentityManager server and a Siebel Server. IBM Security Identity Manager was previouslyknown as Tivoli® Identity Manager.

Access to publications and terminologyThis section provides:v A list of publications in the “IBM Security Identity Manager library.”v Links to “Online publications.”v A link to the “IBM Terminology website.”

IBM Security Identity Manager library

For a complete listing of the IBM Security Identity Manager and IBM SecurityIdentity Manager Adapter documentation, see the online library(http://www-01.ibm.com/support/knowledgecenter/SSRMWJ/welcome).

Online publications

IBM posts product publications when the product is released and when thepublications are updated at the following locations:

IBM Security Identity Manager libraryThe product documentation site (http://www-01.ibm.com/support/knowledgecenter/SSRMWJ/welcome) displays the welcome page andnavigation for the library.

IBM Security Systems Documentation CentralIBM Security Systems Documentation Central provides an alphabetical listof all IBM Security Systems product libraries and links to the onlinedocumentation for specific versions of each product.

IBM Publications CenterThe IBM Publications Center site ( http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss) offers customized search functionsto help you find all the IBM publications you need.

IBM Terminology website

The IBM Terminology website consolidates terminology for product libraries in onelocation. You can access the Terminology website at http://www.ibm.com/software/globalization/terminology.

© Copyright IBM Corp. 2012, 2014 vii

http://www-01.ibm.com/support/knowledgecenter/SSRMWJ/welcome



https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Security%20Systems%20Documentation%20Central/page/Welcome

http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

http://www.ibm.com/software/globalization/terminology

http://www.ibm.com/software/globalization/terminology

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

Technical trainingFor technical training information, see the following IBM Education website athttp://www.ibm.com/software/tivoli/education.

Support informationIBM Support provides assistance with code-related problems and routine, shortduration installation or usage questions. You can directly access the IBM SoftwareSupport site at http://www.ibm.com/software/support/probsub.html.

Appendix C, “Support information,” on page 39 provides details about:v What information to collect before contacting IBM Support.v The various methods for contacting IBM Support.v How to use IBM Support Assistant.v Instructions and problem-determination resources to isolate and fix the problem

yourself.

Note: The Community and Support tab on the product information center canprovide additional support resources.

Statement of Good Security PracticesIT system security involves protecting systems and information throughprevention, detection and response to improper access from within and outsideyour enterprise. Improper access can result in information being altered, destroyed,misappropriated or misused or can result in damage to or misuse of your systems,including for use in attacks on others. No IT system or product should beconsidered completely secure and no single product, service or security measurecan be completely effective in preventing improper use or access. IBM systems,products and services are designed to be part of a comprehensive securityapproach, which will necessarily involve additional operational procedures, andmay require other systems, products or services to be most effective. IBM DOESNOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES AREIMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THEMALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.

viii IBM Security Identity Manager: Siebel JDB Adapter User Guide

http://www.ibm.com/software/tivoli/education

http://www.ibm.com/software/support/probsub.html

Chapter 1. Introduction to the Siebel JDB Adapter

The Siebel JDB Adapter is an application that provides connectivity between IBMSecurity Identity Manager and the Siebel server.

The adapter runs as a service, independent of whether you are logged on to IBMSecurity Identity Manager.

The adapter runs on a workstation where the IBM Tivoli Directory Integrator isinstalled. The adapter needs the Dispatcher installed on the same workstationwhere the IBM Tivoli Directory Integrator is installed. IBM Security IdentityManager uses Remote Method Invocation (RMI) calls to communicate with thedispatcher. The dispatcher uses the IBM Tivoli Directory Integrator to run theadapter.

You can use the Siebel JDB Adapter and IBM Security Identity Manager toautomate the following user account management tasks:v Adding user accounts to the Siebel serverv Modifying attributes of Siebel user accountsv Changing passwords of Siebel user accountsv Suspending, restoring, and deleting Siebel user accountsv Retrieving user accounts from the Siebel server

Features of the Siebel JDB AdapterThe adapter automates user account management tasks.

The Siebel JDB Adapter supports:v Reconciliation of user accounts and other support data, such as time zones,

employee organizations, positions, responsibilities, personal titles, availabilitystatus, and notification types from the Siebel server to the directory server ofIBM Security Identity Manager.

v User account management tasks, such as add, modify (including passwordchange), suspend, restore, and delete to manage accounts on the Siebel server byusing IBM Security Identity Manager.

v Customization of the Siebel JDB account form.

© Copyright IBM Corp. 2012, 2014 1

2 IBM Security Identity Manager: Siebel JDB Adapter User Guide

Chapter 2. Checklist for configuring IBM Security IdentityManager to run the adapter

You must multiple tasks that install and configure the Siebel JDB Adapter.

Table 1

Table 1. Checklist for configuring IBM Security Identity Manager

TaskFor information, see the section in thefollowing documentation:

Install the Siebel JDB Adapter Installing the Siebel JDB Adapter in the SiebelJDB Adapter Installation and Configurationguide.

Import the adapter profile into IBMSecurity Identity Manager

Importing the adapter profile into the IBMSecurity Identity Manager server in the SiebelJDB Adapter Installation and Configurationguide.

Create a service for the Siebel JDB Adapter Creating the service in the Siebel JDB AdapterInstallation and Configuration guide.Note: After you create a Siebel JDB Adapterservice, the IBM Security Identity Managerserver creates a default provisioning policyfor the adapter service. You can customize aprovisioning policy for the Siebel JDBAdapter service according to yourorganizational requirements. For moreinformation, see the section aboutcustomizing a provisioning policy in the IBMSecurity Identity Manager productdocumentation.

Configure the Siebel JDB Adapter Configuring the Siebel JDB Adapter in theSiebel JDB Adapter Installation andConfiguration guide.

Perform a reconciliation operation toretrieve user accounts and store them in theIBM Security Identity Manager server

Managing reconciliation schedules in the IBMSecurity Identity Manager productdocumentation.

Adopt orphan accounts on IBM SecurityIdentity Manager

Assigning an orphan account to a user in theIBM Security Identity Manager productdocumentation.

Table 2 on page 4 identifies the installation directories that you might need toaccess when using the adapter.


Table 2. Installation directories

Required information Description Value

IBM Tivoli DirectoryIntegrator HomeDirectory(ITDI_HOME)

The ITDI_HOME directory containsthe jars/connectors subdirectorythat contains adapter JAR files.

If IBM Tivoli DirectoryIntegrator is automaticallyinstalled with your IBMSecurity Identity Managerproduct, the defaultdirectory path for IBMTivoli Directory Integratoris as follows:

Windows:

v for version 7.1:

drive\ProgramFiles\IBM\TDI\V7.1

UNIX:

v for version 7.1:

/opt/IBM/TDI/V7.1

Solution Directory(ADAPTER_SOLDIR)

When you install the dispatcher, theadapter prompts you to specify a filepath for the solution directory. Formore information about the solutiondirectory, see the DispatcherInstallation and Configuration Guide.

The default solutiondirectory is:

Windows:

v for version 7.1:

drive\ProgramFiles\IBM\TDI\V7.1\timsol

UNIX:

v for version 7.1:

/opt/IBM/TDI/V7.1/timsol


Chapter 3. Configuration of view modes of businesscomponents

A business component is a logical grouping of data on the Siebel server.

For example, the User business component consists of employee flag, login name,password, family name, first name , middle name, job title, and alias attributes.A view mode determines the access controls that you can apply to a businesscomponent in a view. The visibility component of a business component decidesthe user access control. For information about view modes corresponding todifferent business components, see the Siebel documentation.

You can use custom XML files to configure view modes of different businesscomponents. These custom XML files exist in the ADAPTER_SOLDIR\SiebelCustomXMLs\ directory.

The following table lists the custom XML files that are used for managing useraccounts and for retrieving support data attributes.

Table 3. Custom XML files used for user account management

Used forBusinessobject

Businesscomponent Custom XML file

User account management User List User UserList.xml

User account management Employee Employee Employee.xml

Support data reconciliation- Availability

List Of Values List Of Values AvailStatusTypes.xml

Support data reconciliation- Standard/EmergencyNotification

List Of Values List Of Values NotificationTypes.xml

Support data reconciliation- Organization

Organizations Organization Organization.xml

Support data reconciliation- Personal title (Mr./Mrs.)

List Of Values List Of Values PersonalTitle.xml

Support data reconciliation- Position

Employee Position Positions.xml

Support data reconciliation- Responsibility

Employee Responsibility Responsibility.xml

Support data reconciliation- Time Zone

Time Zone Time Zone TimeZone.xml

View modes in the custom XML filesWhen managing user accounts, you can configure the view mode values specifiedin the custom XML files according to your requirements.

The following table gives the default values of view modes for different businesscomponents.


Table 4. Default values of view modes for different business components

XML file name Business component Default value of view mode

UserList.xml User 5

Employee.xml Employee 5

AvailStatusTypes.xml List Of Values 9

NotificationTypes.xml List Of Values 9

Organization.xml Organization 9

PersonalTitle.xml List Of Values 9

Positions.xml Position 9

Responsibility.xml Responsibility 9

TimeZone.xml Time Zone 9

Note: The adapter ignores the view mode values in the following XML files, whichhave the searchSpecificationAttribute or the searchSpecificationValue specified for abusiness component:v PersonalTitle.xml

v NotificationTypes.xml

v AvailStatusTypes.xml

However, the viewMode attribute is a required attribute in the definition of abusiness component, and cannot be deleted.

The following table gives the default values of view modes for the Multi-ValueGroup (MVG) business component. It also provides the default values for thePickList business component attributes in the UserList.xml file. For informationabout identifying types of attributes, see Identifying types of business componentattributes.

Table 5. Default values of view modes for MVG business components and PickList businesscomponents in the UserList.xml file

Type of attributeName of support dataattribute

Default value of viewmode

PicklistBusComponent Time Zone 9

PicklistBusComponent Personal Title 9

PicklistBusComponent Availability Status 9

PicklistBusComponent Standard Notification 9

PicklistBusComponent Emergency Notification 9

MVGBusComponent Employee Organization 9

MVGBusComponent Responsibility 9

MVGBusComponent Position 9

The following table lists the numeric values that you can specify in the definitionof a business component for a view mode, and their meaning.


Table 6. View mode specification in the custom XML files

Viewmodevalue View name Meaning

0 SalesRepView Users can access records owned by them or canaccess records whose team contains their position.

1 ManagerView Users can access records associated with their ownposition and positions that report directly to them.

2 PersonalView Users can access records with which their personrecords are associated.

3 AllView Users can access all records, except those recordswith a missing or an invalid owner.

5 OrganizationView Users can access records that are associated with asingle organization or with multiple organizations towhich their position is linked.

6 ContactView Users can access records that are associated with asingle organization to which their position is linked.

7 GroupView Users can access categories of master data that areassociated with any of the access groups with whichthey are associated. Users are associated with anaccess group if during the current session, they areassociated with a position, organization, account,household, or a user list that is a member of theaccess group.

8 CatalogView Users can access a flat (uncategorized) list of data inall of the categories across catalogs to which all ofthe user’s access groups have access. Users areassociated with an access group if during thecurrent session, they are associated with a position,organization, account, household, or a user list thatis a member of the access group.

9 SubOrganizationView Users can access records associated with their activeorganization or a descendant organization.

Configuration of the MVGBusComponent view modeThis section provides information about configuring the view mode to reconcile,add, and modify the custom values of the MVGBusComponent.

Reconciling custom values of the MVGBusComponent forsupport data

The Siebel JDB Adapter uses the CustomXML file in the ADAPTER_SOLDIR\SiebelCustomXMLs directory for reconciliation. The view mode property in theCustomXML file of a particular MVGBusComponent determines which values of aparticular support data are reconciled.

About this task

By default, the view mode for MVGBusComponent is 9, SubOrganizationView.This view mode reconciles records associated with active organization anddescendant organizations. However, the view mode does not reconcile the customMVGBusComponents that are available on the managed resource.

Chapter 3. Configuration of view modes of business components 7

To reconcile the custom MVGBusComponent, set the view mode in the CustomXmlsdirectory for support data to 3, ALL view.

Set the view mode property to 3 in the CustomXML file of the MVGBusComponentwhose custom values you want to reconcile.

Procedure1. Open the Position.xml file in the ADAPTER_SOLDIR\SiebelCustomXMLs directory2. Modify the file. From

<BusinessComponent name = "Position" viewMode = "9">

to<BusinessComponent name = "Position" viewMode = "3">

3. Save the Position.xml file.4. Restart the adapter service and run the reconciliation operation from IBM

Security Identity Manager.

Reconciling custom values of the MVGBusComponent foruser data

The Siebel JDB Adapter uses the UserList.xml file for user reconciliation. Bydefault, the view mode property in the UserList.xml file is set to 5, OrganizationalView.

About this task

This mode reconciles the user data except the custom values for theMVGBusComponent associated with a particular user. To reconcile the completeuser data, including the custom values for MVGBusComponent, set the view modeproperty in UserList.xml to 3, ALL View. The adapter uses UserList.xml toreconcile the user accounts and the employee accounts.

Procedure1. Open the UserList.xml file in the ADAPTER_SOLDIR\SiebelCustomXMLs directory2. Modify the file. From

<BusinessComponent name = "User" viewMode = "5">

to<BusinessComponent name = "User" viewMode = "3">

3. Save the UserList.xml file.4. Restart the adapter service and run the reconciliation operation from IBM


Adding or modifying User or Employee with custom values forthe MVGBusComponent

The Siebel JDB Adapter uses the UserList.xml file to create User accounts andEmployee.xml to create Employee accounts on the managed resource.

About this task

These files are in the ADAPTER_SOLDIR\SiebelCustomXMLs directory.


By default, the property view Mode for MVGBusComponent attributes in theUserList.xml file and Employee.xml file is 9.

To associate the custom MVGBusComponent values to account types User andEmployee, you must set the view mode property in the UserList.xml file andEmployee.xml file to 3. For example, to associate Position with a user or employeethe UserList.xml file and Employee.xml file must have viewMode property set to 3for the MVGBusComponent Position. When the view mode is 9, the adaptergenerates the following message for custom MVGBusComponent value:Specified Position not found.

To add user or employee account with the custom values, set the view modeproperty to 3 in the CustomXML file of the MVGBusComponent.

Procedure1. Open the Employee.xml file in the ADAPTER_SOLDIR\SiebelCustomXMLs directory2. Modify the file. From

<MVGBusComponent name="Position" viewMode = "9" isRequired = "true">

to<MVGBusComponent name="Position" viewMode = "3" isRequired = "true">

3. Save the Employee.xml file.4. Restart the adapter service and run the reconciliation operation from IBM


Chapter 3. Configuration of view modes of business components 9

Chapter 4. Siebel JDB Adapter user account managementtasks

IBM Security Identity Manager manages user accounts stored on the Siebel serverby using the Siebel JDB Adapter.

You can complete operations, such as reconciliation, add, modify (includingpassword change), suspend, restore, and delete to manage your accounts. You canmanage:v Accounts for a specific person.v Accounts for a service instance.v Specific accounts by using the search function of IBM Security Identity Manager.

Before you use the adapter to complete an operation,v Ensure that you complete the steps given in Chapter 2, “Checklist for

configuring IBM Security Identity Manager to run the adapter,” on page 3.v Use one of the following methods to run the Dispatcher. The Dispatcher in turn

runs the Siebel JDB Adapter.– Windows services in service mode

1. In the Windows control panel, double-click Administrative Tools.2. Double-click Services.3. Right-click the IBM Security Identity Manager Adapter service, and click

Start.– Windows command prompt in console mode

Go to the ADAPTER_SOLDIR directory and run the following command:ibmdisrv -s ADAPTER_SOLDIR -c ITIM_RMI.xml –d

v Ensure that the view mode values specified in the custom XML files areconfigured correctly for your requirements. For information about configuringview modes in the custom XML files, see Configuring view modes in the customXML files.

Reconciliation of user accountsThe reconciliation operation retrieves the user account information from the Siebelserver and stores it in the directory server of IBM Security Identity Manager.

You can schedule reconciliation to run at specific times and to return specificparameters. Running a reconciliation before its schedule time does not cancel thescheduled reconciliation. For more information about scheduling reconciliation andrunning a scheduled reconciliation, see the IBM Security Identity Manager productdocumentation.

You can also complete the following reconciliation tasks at any time from IBMSecurity Identity Manager:v Reconciling support datav Reconciling a single user account

The reconciliation of the Siebel user accounts and supporting data depends on theview mode values. These values are specified for the different business


components in the Siebel custom XML files. For information about configuringview modes in the custom XML files, see Configuring view modes in the customXML files.

Reconciling supporting dataYou can use IBM Security Identity Manager to reconcile support data at any time.

Before you begin

Ensure that the view mode values specified in the custom XML files are accordingto your requirements.

About this task

Supporting data for a Siebel user account includes the following information:v Time zonev Employee organizationsv Positionsv Responsibilitiesv Personal title (Mr or Mrs)v Availability statusv Notification types

For more information about each of these attributes, see the Siebel documentation.

Procedure1. Log on to IBM Security Identity Manager as an administrator.2. In the My Work pane, click Manage Services. The Manage Services page opens.3. Select the type of service from the Service type list and click Search.4. Select the name of the service that you created for the Siebel JDB Adapter.5. Click the arrow icon to view the View popup menu and select Reconcile Now.

The Reconcile Now page opens.6. Click Define query.7. Select the Reconcile supporting data only check box and click Submit.

User accountsYou can add user accounts at any time for either an existing person or a newperson in the organization. This section describes the adapter attributes that definethe accounts on the account form.

For specific procedures, see the IBM Security Identity Manager productdocumentation.

If you specify Database (DB) Authentication in the service form of the Siebel JDBAdapter, then during the add operation, the adapter:v Adds the user account to the Siebel serverv Adds the login details of the user account to the database

If you specify Lightweight Directory Access Protocol (LDAP) Authentication in theservice form of the Siebel JDB Adapter, then during the add operation:


v The adapter adds the user account to the Siebel server.v The Siebel server in turn adds the user account to the LDAP server.

Attributes for adding user accountsTo add user accounts to the Siebel server, you must specify attributes on the SiebelJDB account form.

Specify the following required attributes on the Siebel JDB account form.

Table 7. Required attributes for adding user accounts

Attribute Description

User ID User ID of the account

Last name Surname of the account holder

First name Given name of the account holder

To add user accounts as an Employee, specify the following required attributes onthe Siebel JDB account form.

Table 8. Required attributes for adding user accounts as Employee

Attribute Description

User ID User ID of the account

Last name Surname of the account holder

First name Given name of the account holder

Positions Position of the employee in an organization. For example, SiebelAdministrator.Note: This attribute is a required attribute only when you want toconsider the user as an Employee.

Note: By default, the account holder is considered as the User. To consider theaccount holder as an Employee, select the Is Employee check box on the accountform.

In addition to the required attributes, you can also specify the other optionalattributes on the Siebel JDB account form.

Specifying the Available until : Date and the Available until : Time attributes

The default value of the Available until : Date and the Available until : Timeattributes on the Siebel JDB account form is Never.

Add a user account with the following attributes specified on the Siebel JDBaccount form:v User IDv First namev Last namev Is Employee?

When you perform an add operation, the adapter adds the user account on theSiebel server. The user record is not displayed on the Employee page of the Siebel

Chapter 4. Siebel JDB Adapter user account management tasks 13

Web client. To display the record of an employee user on the Siebel Web client,clear the Never check box next to the Available until : Time attribute on the SiebelJDB account form.

Available until : DateThe end date up to which an employee user is displayed on the Employeepage of the Siebel Web client. To specify a date:1. Clear the Never check box.2. Click the View Calendar icon and select the month, year, and date.3. Click OK.

Available until : TimeThe time up to which an employee user is displayed on the Employeepage of the Siebel Web client. To specify a time:1. Clear the Never check box.2. Click the View Time icon and select the time.3. Click OK.

User account modificationYou can modify user account attributes at any time in IBM Security IdentityManager. This section describes the adapter attributes that you can use to modifythe user accounts.

For specific procedures, see the IBM Security Identity Manager productdocumentation.

You can modify values of the attributes on the following pages of the Siebel JDBaccount form:v USERv ACCESS CONTROLv USER INFO

Modifiable attributes on the USER page of the Siebel JDB account form

v Last namev First namev Middle namev Job titlev Aliasv Time zone

Note: You cannot delete values of the Last name, First name, and Timezone attributes.

Modifiable attributes on the ACCESS CONTROL page of the Siebel JDBaccount form

v Is Employee?v Employee Organizationsv Primary Employee Organizationv Positionsv Primary positionv Responsibilities in database


v Responsibilities in LDAP

Note:

v You can delete values of the Employee Organization attribute, but youcannot add an organization name to the attribute.

v You must not modify the Employee Organization attribute when you areadding organizations to a User account. Siebel does not supportchanging the Employee Organization that is associated with a Useraccount.

v By default, Siebel assigns Default Organization as the EmployeeOrganization attribute value when you create an account. Do not specifythe value Default Organization when you add a User or Employeeaccount on Siebel. If you do specify this value, the Siebel JDB adapterreturns a warning for the Employee Organization attribute.

v You cannot delete the employee organization name from the EmployeeOrganizations field that is specified as the primary employeeorganization in the Primary Employee Organization field. Siebel doesnot support deletion of the primary organization.

v You cannot delete the position from the Positions field that is specifiedas the primary position in the Primary position field. Siebel does notsupport deletion of the primary position.

v After you create a User account or an Employee account by using IBMSecurity Identity Manager, you cannot convert a User account to anEmployee account or vice versa.

v Siebel assigns a default Responsibility value when you create an account.You can configure the default value that Siebel uses. For example, youcan configure Siebel to assign a Responsibility value of SiebelAdministrator to new User or Employee accounts by default. Do notspecify a value for the Responsibility attribute when you add a User orEmployee account on Siebel. If you do specify a value, the Siebel JDBadapter returns a warning for this attribute.

Modifiable attributes on the USER INFO page of the Siebel JDB account form

v Employee numberv Mr/Mrsv Short namev Availabilityv Available until: Datev Available until: Timev Standard notificationv Emergency notificationv Emailv Fax numberv Home phonev Work phonev Cell phonev Pager numberv Pager pin

Note: You cannot delete values of the Mr/Mrs, Availability, Standardnotification, and Emergency notification attributes.

Chapter 4. Siebel JDB Adapter user account management tasks 15

Password change of user accountsYou can change the password of any of the Siebel accounts that exist on IBMSecurity Identity Manager.

For information about changing passwords, see the IBM Security Identity Managerproduct documentation.

User account suspensionWhen you suspend a user account, the status of the user account on IBM SecurityIdentity Manager becomes inactive, and the user account becomes unavailable foruse.

Suspending a user account does not remove the user account from IBM SecurityIdentity Manager. For more information about suspending user accounts, see theIBM Security Identity Manager product documentation.

When you suspend a user account from IBM Security Identity Manager, thesuspended user cannot access the Siebel server.

User account restorationThe restore operation reinstates the suspended user accounts to IBM SecurityIdentity Manager.

After restoring a user account, the status of the user account on IBM SecurityIdentity Manager becomes active. For more information about restoring useraccounts, see the IBM Security Identity Manager product documentation.

When you restore a user account from IBM Security Identity Manager, thereinstated user can access the Siebel server.

User account deletionUse the deprovision feature of IBM Security Identity Manager to delete useraccounts.

For more information about deleting user accounts, see the IBM Security IdentityManager product documentation.

If you specify DB Authentication in the service form of the Siebel JDB Adapter,then during the delete operation, the adapter:v Deletes the user account from the Siebel serverv Deletes the login details of the user account from the database

If you select the following options in the service form of the Siebel JDB Adapter:v LDAP Authentication as the authentication typev The Remove LDAP user on Delete? check box

Then, during the delete operation, the adapter deletes the user account from theLDAP server.


Chapter 5. Customization of the Siebel JDB account form

The Siebel JDB Adapter supports a standard set of attributes. You can customizethe adapter to support additional attributes on the Siebel server.

Types of business component attributesThe Siebel JDB Adapter categorizes attributes of different business components intovarious types.

The Siebel JDB Adapter categorizes the attributes into the following types:v Simple attributes - single-valued attributesv PicklistBusComponent attributes - single-valued attributesv MVGBusComponent attributes - multivalued attributes

To identify the type of a business component attribute, open the Siebel Toolsapplication and navigate to the required business component in the ObjectExplorer pane.

Identifying a simple attribute

An attribute of a business component that does not have a value in the Picklistcolumn of the Single Value Fields pane is a simple attribute. For example, EmployeeId is a simple attribute that belongs to the User business component.

Identifying a PicklistBusComponent attribute

An attribute of a business component that has a value in the Picklist column of theSingle Value Fields pane is a PicklistBusComponent attribute. For example,Availability Status is a PicklistBusComponent attribute that belongs to the Userbusiness component.

Identifying a MVGBusComponent attribute

An attribute that has a value in the Multivalue Link column of the MultivalueFields pane is an MVGBusComponent attribute. For example, Responsibility is anMVGBusComponent attribute that belongs to the User business component.

Attributes in custom XML filesBefore adding an attribute to the Siebel JDB account form, you must define theattribute in the custom XML files.

The following table gives the definitions of different types of attributes in a customXML file.

Table 9. Definition of attributes in a custom XML file

Type of attribute Example Definition in a custom XML file

Simple Employee Id <Attribute name = "Employee Id"></Attribute>


Table 9. Definition of attributes in a custom XML file (continued)

Type of attribute Example Definition in a custom XML file

PicklistBusComponent Availability Status <PicklistBusComponent name = "Availability Status"viewMode = "9"><Attribute name = "Name"isUnique = "true" isRequired = "true"></Attribute></PicklistBusComponent>

MVGBusComponent Responsibility <MVGBusComponent name = "Responsibility"viewMode = "9"><Attribute name = "Name"isUnique = "true" isRequired = "true"></Attribute><Attribute name = "PrimaryOrganization Id" isUnique = "true"isRequired = "true"> </Attribute></MVGBusComponent>

Adding an attribute to the Siebel JDB account formYou can customize account forms for Siebel JDB business components by addingattributes to the Siebel JDB Adapter profile.

Procedure1. Log on to the workstation where the Siebel JDB Adapter is installed.2. Copy the SiebelJDBProfile.jar file to the \temp directory.3. Extract the contents of the SiebelJDBProfile.jar file to the \temp directory Run

the command:cd c:\tempjar -xvf SiebelJDBProfile.jar

This command creates the c:\temp\SiebelJDBProfile directory.4. Add the attribute to the Siebel JDB Adapter profile. For more information about

adding an attribute to the adapter profile, see “Attribute for the adapterprofile” on page 19.

5. Map the attribute to the assembly lines. For more information about mappingan attribute to the assembly line, see “Mapping attributes” on page 20.

6. Go to the IBM Tivoli Directory Integrator installation directory, and run thefollowing command to break the assembly lines.java –classpath jars\ITLMToolkit.jar;jars\miconfig.jar;jars\miserver.jar;jars\mmconfig.jar;jars\diserverapi.jar;jars\log4j-1.2.8.jar;jars\itdiAgents-common.jar com.ibm.di.utils.IDIConfigHelper"c:\\temp\\SiebelJDBProfile\\SiebelJDBAdapter.xml" "c:\\temp\\SiebelJDBProfile"

In this command, c:\temp\SiebelJDBAdapter.xml is the path of theSiebelJDBAdapter.xml file.

7. Use the files in the \temp directory to create a JAR file. Run the command:cd c:\tempjar -cvf SiebelJDBProfile.jar SiebelJDBProfile

8. Import the SiebelJDBProfile.jar file to the IBM Security Identity Managerserver. For more information about importing the SiebelJDBProfile.jar file,see the Siebel JDB Adapter Installation and Configuration guide. Under "Installingthe Siebel JDB Adapter," search for the section "Importing the adapter profileinto the IBM Security Identity Manager server."

9. Stop and start the IBM Security Identity Manager server.


Attribute for the adapter profileTo add attributes to the adapter profile, you must modify theCustomLabels.properties and schema.dsml files.

You must update profiles or specifications of the new attributes in the followingfiles:

CustomLabels.propertiesThe CustomLabels.properties file contains a list of attributes that aresupported by IBM Security Identity Manager and their correspondinglabels.

For example, you want to add an attribute erTDISblMaidenName to theUSER page of the Siebel JDB account form. Specify the attribute inthe CustomLables.properties file as follows:### ertdisblusertab

erTDISblMaidenName=Maiden Name

In this example:

ertdisblusertabDefines the tab on which the erTDISblMaidenName attribute isdisplayed.

erTDISblMaidenName=Maiden NameDefines the label, Maiden Name, for the erTDISblMaidenNameattribute. IBM Tivoli Directory Integrator recognizes the newattribute by the name erTDISblMaidenName.

schema.dsmlDefines an attribute. It contains the schema for attributes and object classesin the profile. For example, the following section of the schema.dsml filedefines the erTDISblMaidenName attribute and adds the erTDISblMaidenNameattribute to the erTDISblJDBAccount class:

<attribute-type single-value = "true">

<name>erTDISblMaidenName</name><description>Maiden Name</description><object-identifier>1.3.6.1.4.1.6054.3.137.2.65</object-identifier><syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>

</attribute-type><class superior="top">

<name>erTDISblJDBAccount</name><description>Siebel JDB Account</description><object-identifier>1.3.6.1.4.1.6054.3.137.1.14</object-identifier>

<attribute ref = "erTDISblMaidenName" required = "false"/></class>

In this example:

<attribute-type single-value = "true">Specifies the value of the attribute type as single.

<name>erTDISblMaidenName</name>Defines the name of the erTDISblMaidenName attribute.

<description>Maiden Name</description>Provides the description for the Maiden Name attribute.

<object-identifier>1.3.6.1.4.1.6054.3.137.2.65</object-identifier>Specifies the unique identifier for the erTDISblMaidenName attribute.

Chapter 5. Customization of the Siebel JDB account form 19

<syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>Refers to the syntax of the erTDISblMaidenName attribute type.

<class superior="top"><name>erTDISblJDBAccount</name><description>Siebel JDB Account</description><object-identifier>1.3.6.1.4.1.6054.3.137.1.14</object-identifier>

<attribute ref = "erTDISblMaidenName" required = "false"/></class>

Adds the erTDISblMaidenName attribute to the erTDISblJDBAccount class.

Note: Each attribute must have a unique identifier. In addition, the identifier mustbe unique in the directory server where the attribute is stored.

Mapping attributesUse this procedure to map the newly added attributes of Component Interfacessupported by IBM Security Identity Manager to the assembly lines.

Procedure1. Run the IBM Tivoli Directory Integrator.2. Click File > Open.3. Select the SiebelJDBAdapter.xml file from the temporary folder where the

Siebel JDB Adapter profile was extracted, and click Open.4. In the navigation pane, expand the AssemblyLines tree.

a. Select the siebelJDBAdd assembly line and map the attributes to thesiebelJDBAdd assembly line. For more information about mappingattributes to the siebelJDBAdd assembly line, see “Mapping attributes to thesiebelJDBAdd assembly line” on page 21.

b. Select the siebelJDBModify assembly line and map the attributes to thesiebelJDBModify assembly line. For more information about mappingattributes to the siebelJDBModify assembly line, see “Mapping attributes tothe siebelJDBModify assembly line” on page 22.

c. Select the siebelJDBSearch assembly line and map the attributes to thesiebelJDBSearch assembly line. For more information about mappingattributes to the siebelJDBSearch assembly line, see “Mapping attributes tothe siebelJDBSearch assembly line” on page 23.

5. Save changes to the assembly lines.

Assembly line iconsYou can use Tivoli Directory Integrator assembly line icons to map attributes.

The following table lists the Tivoli Directory Integrator assembly line icons thatyou can use to map attributes.

Table 10. Assembly line icons

Icon Name

Add an Attribute to the Attribute map

Switch between List, Detail, and Schema view


Table 10. Assembly line icons (continued)

Icon Name

Connect to the data source

Read the next entry

Add new Link Criteria

Mapping attributes to the siebelJDBAdd assembly lineYou can add a value to an attribute by mapping the attribute to the siebelJDBAddassembly line.

About this task

The following table lists the connectors of the siebelJDBAdd assembly line, thecorresponding business components, and support data attributes.

Table 11. Connectors of the siebelJDBAdd assembly line

Connector Business componentName of support dataattribute

siebelJDBConn User Users

siebelJDBConnEmp Employee Employee

To view the assembly line icons used while mapping attributes see Table 10 onpage 20.

As an example, this procedure maps the erTDISblMaidenName attribute to thesiebelJDBAdd assembly line.

Procedure1. Select the siebelJDBAdd assembly line. The siebelJDBAdd page opens.2. Click Call/Return to open the Initial Work Entry page.

a. Click Switch between List, Detail and Schema view in the toolbar untilyou see the Schema pane.

b. Click Add a new attribute to the Attribute Map in the toolbar.c. Type the name of the new attribute as erTDISblMaidenName, and click OK.

The erTDISblMaidenName attribute is displayed in the Work Attribute list.d. Click Add an attribute to the schema in the toolbar.e. Type the name of the new attribute as erTDISblMaidenName, and click OK.

The erTDISblMaidenName attribute is displayed in the Schema pane.f. Click Switch between List, Detail and Schema view in the toolbar until you

see the Attribute Map details pane.g. Select the erTDISblMaidenName attribute in the Work Attribute list.h. Select the erTDISblMaidenName check box in the Schema pane to map the

attribute to the erTDISblMaidenName attribute in the Work Attribute list.3. Click Data Flow to open the Data Flow page.


a. In the left pane, expand the Flow folder and select the siebelJDBConn orthe siebelJDBConnEmp connector. The Config page opens in the rightpane.

b. Click the Output Map tab. The Output Map page opens.c. Click Switch between List, Detail and Schema view in the toolbar until

you see the Schema pane.d. Click Add an attribute to the schema in the toolbar.e. Type the name of the new attribute as Maiden Name, and click OK. The

Maiden Name attribute is displayed in the Schema pane.

Note: The name of the attribute must match with attribute defined in thecustom XML file.

f. Drag the Maiden Name attribute to the Connector Attribute list. The MaidenName attribute is displayed in the Connector Attribute list.

g. Click Switch between List, Detail and Schema view in the toolbar untilyou see the Attribute Map details pane.

h. Select the Maiden Name attribute from the Connector Attribute list.i. Select the erTDISblMaidenName check box from the Schema pane to map

the erTDISblMaidenName attribute to the siebelJDBConn connector.

Note: Complete this step if the attribute is a simple attribute orPicklistBusComponent attribute. To map a MVGBusComponent attribute,you must select the Advance Mapping Settings check box on the AttributeMap details pane. Then write scripts for mapping the MVGBusComponentattribute to the siebelJDBConn connector.

4. Save changes to the siebelJDBAdd assembly line.

Mapping attributes to the siebelJDBModify assembly lineYou can make an attribute modifiable by mapping the attribute to thesiebelJDBModify assembly line.

About this task

The following table lists the connectors of the siebelJDBModify assembly line, thecorresponding business components, and support data attributes.

Table 12. Connectors of the siebelJDBModify assembly line


siebelJDBConn User Users

siebelJDBConnEmp Employee Employee

To view the assembly line icons used while mapping attributes, see Table 10 onpage 20.

As an example, this procedure maps the erTDISblMaidenName attribute to thesiebelJDBModify assembly line.

Procedure1. Select the siebelJDBModify assembly line. The siebelJDBModify page opens.2. Click Call/Return to open the Initial Work Entry page.



b. Click Add a new attribute to the Attribute Map in the toolbar.c. Type the name of the new attribute as erTDISblMaidenName, and click OK.

The erTDISblMaidenName attribute is displayed in the Work Attribute list.d. Click Add an attribute to the schema in the toolbar.e. Type the name of the new attribute as erTDISblMaidenName, and click OK.

The erTDISblMaidenName attribute is displayed in the Schema pane.f. Click Switch between List, Detail and Schema view in the toolbar until you

see the Attribute Map details pane.g. Select the erTDISblMaidenName attribute in the Work Attribute list.h. Select the erTDISblMaidenName check box in the Schema pane to map the

attribute to the erTDISblMaidenName attribute in the Work Attribute list.3. Click the Data Flow tab to open the Data Flow page.

a. In the left pane, expand the Flow folder and select the siebelJDBConn orthe siebelJDBConnEmp connector. The Config page opens in the rightpane.

b. Click the Output Map tab. The Output Map page opens.c. Click Switch between List, Detail and Schema view in the toolbar until

you see the Schema pane.d. Click Add an attribute to the schema in the toolbar.e. Type the name of the new attribute as Maiden Name, and click OK. The

Maiden Name attribute is displayed in the Schema pane.

Note: The name of the attribute must match with attribute defined in thecustom XML file.

f. Drag the Maiden Name attribute to the Connector Attribute list. The MaidenName attribute is displayed in the Connector Attribute list.

g. Click Switch between List, Detail and Schema view in the toolbar untilyou see the Attribute Map details pane.

h. Select the Maiden Name attribute from the Connector Attribute list.i. Select the erTDISblMaidenName check box from the Schema pane to map

the erTDISblMaidenName attribute to the siebelJDBConn connector.

Note: Complete this step if the attribute is a simple attribute orPicklistBusComponent attribute. To map a MVGBusComponent attribute,you must select the Advance Mapping Settings check box on the AttributeMap details pane. Then write scripts for mapping the MVGBusComponentattribute to the siebelJDBConn connector.

4. Save the changes to the siebelJDBModify assembly line.

Mapping attributes to the siebelJDBSearch assembly lineThe siebelJDBSearch assembly line contains connectors corresponding to differentbusiness components and these business components contain different attributes.You can make the value of an attribute reconcilable by mapping the attribute(belonging to a business component) to the corresponding siebelJDBSearchassembly line connector.


About this task

The following table lists the connectors of the siebelJDBSearch assembly line, thecorresponding business components and support data attributes.

Table 13. Connectors of the siebelJDBSearch assembly line


siebelJDBConnUsers User Users

siebelJDBConnAvail List Of Values Availability Status

siebelJDBConnNotfy List Of Values Standard Notification

Emergency Notification

siebelJDBConnBU Organization Employee Organization

siebelJDBConnPerTitl List Of Values Personal Title

siebelJDBConnPostn Position Position

siebelJDBConnResp Responsibility Responsibility

siebelJDBConnTZone Time Zone Time Zone

To view the assembly line icons used while mapping attributes, see Table 10 onpage 20.

For As an example, this procedure reconciles the erTDISblMaidenName attributethat belongs to the User business component.

Procedure1. Select the siebelJDBSearch assembly line. The siebelJDBSearch page opens.2. Click the Data Flow tab to open the Data Flow page.3. In the left pane, expand the Feeds folder and select the siebelJDBConnUsers

connector. The Config page opens in the right pane.4. Click the Input Map tab to open the Input Map page.


b. Click Add an attribute to the schema in the toolbar.c. Type the name of the new attribute as Maiden Name and click OK. The

Maiden Name attribute is displayed in the Schema pane.d. Click Add a new attribute to the Attribute Map in the toolbar.e. Type the name of the new attribute as erTDISblMaidenName, and click OK

The erTDISblMaidenName attribute is displayed in the Work Attribute list.f. Click Switch between List, Detail and Schema view in the toolbar until you

see the Attribute Map details pane.g. Select the Maiden Name attribute from the Connector Attribute list.h. Select the erTDISblMaidenName check box from the Schema pane to map

the erTDISblMaidenName attribute to the siebelJDBConnUsers connector.

Note: Perform this step if the attribute is a simple attribute orPicklistBusComponent attribute. To map a MVGBusComponent attribute,you must select the Advance Mapping Settings check box on the AttributeMap details pane. Then write scripts for mapping the MVGBusComponentattribute to the corresponding connector. For example,


erTDISblRelResponsibility is a MVGBusComponent attribute on the SiebelJDB account form and belongs to the User business component. The SiebelJDB Adapter sends data to IBM Security Identity Manager in the format<Responsibility Name>Siebel Administrator</ResponsibilityName><Primary Organization Id>0-R9NH</Primary Organization Id>. Thefollowing script maps the erTDISblRelResponsibility attribute to thesiebelJDBConnUsers connector:var attr = conn.getAttribute("Responsibility");

if(attr != null){

var v = new Packages.java.util.Vector();var entry1 = attr.getValue(0);var mvAttr = entry1.getAttribute("Responsibility");

if(mvAttr != null){for(var i = 0; i < mvAttr.size(); i=i+1){var e = mvAttr.getValue(i);v.addElement("<Responsibility Name>" + e.getString("Name") +"</Responsibility Name>" + "<Primary Organization Id>" +e.getString("Primary Organization Id")+ "</Primary Organization Id>");}

}//var attrNew = work.newAttribute("erTDISblRelResponsibility");//attrNew.setValues(v);ret.value = v;}

5. Save the changes to the siebelJDBSearch assembly line.


Chapter 6. Reconciling new support data attributes

The Siebel JDB Adapter supports business components that are specified in thecustom XML files. You can customize the adapter to support new businesscomponents for new support data attributes.

Before you begin

You must define the new support data attributes in a custom XML file. Beforeadding an attribute to a custom XML file:v Identify the business object and the business component for which you want to

create and reconcile new support data attributes.v Identify types of attributes that you want to reconcile.

You can use the Siebel Tools application to identify the business object, thebusiness component, and types of attributes. For more information aboutidentifying types of attributes, see Identifying types of business componentattributes.

About this task

You can add and reconcile the following attributes in the Account businesscomponent:v Namev Typev Organization

Procedure1. Create a custom XML file. For more information, see Creating a custom XML

file.2. Log on to the workstation where the Siebel JDB Adapter is installed.3. Copy the SiebelJDBProfile.jar file to the \temp directory.4. Extract the contents of the SiebelJDBProfile.jar file to the \temp directory.

Run the command:cd c:\tempjar -xvf SiebelJDBProfile.jar

This command creates the c:\temp\SiebelJDBProfile directory.5. Add the attributes that are specified in the newly created custom XML file to

the schema.dsml file. For more information, see Adding attributes to theschema.dsml file.

6. Add a connector to the siebelJDBSearch assembly line. For more information,see Adding new connector to the siebelJDBSearch assembly line.

7. Go to the IBM Tivoli Directory Integrator installation directory, and run thefollowing command to break the assembly lines.java –classpath jars\ITLMToolkit.jar;jars\miconfig.jar;jars\miserver.jar;jars\mmconfig.jar;jars\diserverapi.jar;jars\log4j-1.2.8.jar;jars\itdiAgents-common.jar com.ibm.di.utils.IDIConfigHelper "c:\\temp\\SiebelJDBProfile\\SiebelJDBAdapter.xml" "c:\\temp\\SiebelJDBProfile"


In this command, c:\temp\SiebelJDBAdapter.xml is the path of theSiebelJDBAdapter.xml file.

8. Add the connection parameter mapping details for the newly added connectorto the service.def file. For more information, see Adding connectionparameter mapping details to the service.def file.

9. Use the files in the \temp directory to create a JAR file. Run the command:cd c:\tempjar -cvf SiebelJDBProfile.jar SiebelJDBProfile

10. Import the SiebelJDBProfile.jar file to the IBM Security Identity Managerserver. For more information about importing the SiebelJDBProfile.jar file,see the Siebel JDB Adapter Installation and Configuration guide. Under "Installingthe Siebel JDB Adapter," search for the section "Importing the adapter profileinto the IBM Security Identity Manager server."

11. Stop and start the IBM Security Identity Manager server.

Custom XML fileIn a custom XML file, you can define the business object, the business component,and the attributes of the business component that you want to reconcile.

Create the custom XML file in the ADAPTER_SOLDIR\SiebelCustomXMLs\ directory.

For example, to create a custom XML file Account.xml, with the followingattributes that belongs to the Account business component:v Name (Simple attribute)v Organization (MVGBusComponent attribute)v Type (PicklistBusComponent attribute)

Create the Account.xml file, and copy the following information to the file:<?xml version = "1.0" encoding = "UTF-8"?><!DOCTYPE BusinessObject SYSTEM "Validator.dtd">

<BusinessObject name = "Account"><BusinessComponent name = "Account" viewMode = "5">

<Attribute name = "Name" isUnique = "true" isRequired = "true"> </Attribute><PicklistBusComponent name="Type" viewMode = "5">

<Attribute name = "Name" isUnique = "true" isRequired = "true"></Attribute></PicklistBusComponent>

<MVGBusComponent name="Organization" viewMode = "9"><Attribute name = "Name" isUnique = "true" isRequired = "true"></Attribute>

</MVGBusComponent>

</BusinessComponent></BusinessObject>

Note: When creating a custom xml, strictly follow the rules that are defined invalidator.dtd.

Attributes for the schema.dsml fileIn the schema.dsml file, you can define the IBM Tivoli Directory Integrator namesof the attributes that you want to reconcile and the object class for new supportdata.


For example, the IBM Tivoli Directory Integrator names of the Name, the Type, andthe Organization attributes are erTDISblAccountName, erTDISblAcctType, anderTDISblAcctOrgName respectively. The IBM Tivoli Directory Integrator name of theAccount object class is erTDISblAccount. Define these attributes in the schema.dsmlfile as follows:



<attribute-type single-value = "true" ><name>erTDISblAccountName </name><description>Account Name</description><object-identifier>1.3.6.1.4.1.6054.3.137.2.66</object-identifier><syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>

</attribute-type>



<attribute-type single-value = "false" ><name> erTDISblAcctOrgName </name><description>Account Organization Name</description><object-identifier>1.3.6.1.4.1.6054.3.137.2.67</object-identifier><syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>

</attribute-type>



<attribute-type single-value = "true" ><name> erTDISblAcctType </name><description>Account <Type/description><object-identifier>1.3.6.1.4.1.6054.3.137.2.68</object-identifier><syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>

</attribute-type>

<class superior="top">

<name> erTDISblAccount </name><description>Account class</description><object-identifier>1.3.6.1.4.1.6054.3.137.1.105/object-identifier><attribute ref = "erTDISblAccountName" required = "true" />

<attribute ref = "erTDISblAcctOrgName" required = "false" /><attribute ref = "erTDISblAcctType" required = "false" />

</class>

Adding a connector to the siebelJDBSearch assembly lineTo reconcile the record of a new business component that is specified in the newcustom XML file Account.xml, you must add a connector to the siebelJDBSearchassembly line.

Procedure1. Run the IBM Tivoli Directory Integrator.2. Click File > Open.3. Select the SiebelJDBAdapter.xml file from the temporary folder where the

Siebel JDB Adapter profile was extracted, and click Open.4. In the navigation pane, expand the AssemblyLines tree, and select the

siebelJDBSearch assembly line.

Chapter 6. Reconciling new support data attributes 29

5. Right-click the Feeds folder, and select Add connector component to open theSelect Connector window.a. From the connector list, select ibmdi.SiebelJDBConnector.b. In the Name field, type a name for the connector, for example,

siebelJDBConnAcct.c. From the Mode list, select Iterator.d. Click OK. The Config page opens in the right pane.

6. In the Custom XML File Path field, type the relative path of the Account.xmlfile. For example, .\SiebelCustomXMLs\Account.xml.

7. Click the Hooks tab.a. Enable the following hooks from the Prolog folder, and copy the script from

the corresponding hook of an existing connector:v Before Selectionv On Error

b. Enable the following hooks from the DataFlow (Iterator) folder, and copythe script from the corresponding hook of an existing connector:v GetNext Successfulv Iterator Error

8. Map the newly added attributes to the siebelJDBSearch assembly line. For moreinformation, see “Mapping attributes to the siebelJDBSearch assembly line” onpage 23.

9. Save the changes to the siebelJDBSearch assembly line.

Connection parameter mapping details for the service.def fileThe service.def file is available in the \temp directory where the adapter profile isextracted.

In the service.def file, add the following connector parameter mapping details tothe definition of the siebelJDBSearch operation:<connector name="siebelJDBConnAcct"><parameter name="connectString" source="ertdisblconnectstr"></parameter><parameter name="userName" source="erserviceuid"></parameter><parameter name="userPwd" source="erpassword"></parameter><parameter name="language" source="ertdisbllang"></parameter></connector>


Chapter 7. Troubleshooting of the Siebel JDB Adapter

You can identify and resolve error messages that occur while running the SiebelJDB Adapter by using the ibmdi.log file.

Whenever an operation fails, the corresponding error messages are logged in theibmdi.log file. This file is in the ADAPTER_SOLDIR\logs directory. You candisplay the logs in the user interface by running the Remote Method Invocation(RMI) Dispatcher from the command prompt. You can configure logginginformation for the adapter. For more information, see the Siebel JDB AdapterInstallation and Configuration guide. Search for the sections "Displaying logs in theuser interface" and "Configuring logging for the adapter."

The following tables list the error messages and warnings that might occur duringthe Siebel JDB Adapter user tasks and the suggested actions to resolve them.

Note: The error code CTGIMT001E shown in the following table can be issued formultiple reasons.

Table 14. Error messages and suggested actions

Error code Error message Suggested action

CTGIMT001E The following error occurred.

Error: Error communicating withSiebel Server using Java™ DataBeans. Could not open a session in 4attempts. {1} (SBL-JCA-200) ORCode Page "UTF-8" is not supported.Use "-encoding" option to changethe file encoding. (SBL-JCA-328)

v Verify that the Siebel server is running.

v Verify that the port specified in connect string can bereached from the IBM Tivoli Directory Integratorworkstation and that no firewall or other securityproduct prevents communication between them.

v Verify that the dispatcher JVM is not using the UTF-8code page (which is by default on Linux). The codepage for JVM can be changed by using the-Dfile.encoding option.


Error: NoClassDefFoundError forclass:com.siebel.data.SiebelException

Ensure that Siebel.jar and SiebelJI_lang.jar files areplaced in the ITDI_HOME/jars/3rdparty/others directory.


Error: [JavaPackage com.ibm.di.utils. SiebelJDBAdapterUtils.Get[LDAP/JDBC]Connector] is not afunction.

Ensure that the correct dispatcher is installed.


Error: SBL-SVR-00040: Internal:Informational, encrypted parameter.OR The following error occurred.Error: Siebel authentication error.

Verify that the Siebel Administrator name and passwordare correct.


Error: null

Verify that the port number is specified in connect string.


Error: [error message]

Verify that the required parameter specified in the errormessage is given correctly.


Table 14. Error messages and suggested actions (continued)

Error code Error message Suggested action

CTGIMT003E The account already exists. The user exists on the resource. This error might occur ifyou are attempting to add a user to the managedresource and IBM Security Identity Manager is notsynchronized with the resource. To fix this problem,schedule a reconciliation between IBM Security IdentityManager and the resource. See the online help forinformation about scheduling a reconciliation.

For a Siebel server that uses LDAP authentication thiserror might occur if the Siebel user is not present, butthe corresponding LDAP user exists.

CTGIMT009E The account username cannot bemodified because it does not exist.

This error might occur when you attempt to modify auser. This error might also occur if you attempt tochange the password for a user. To fix the problem,ensure that:

v The location specified for the managed resource iscorrect.

v The user was created on the resource.

v The user was not deleted from the resource.

v If the user does not exist on the resource, create theuser on the resource and then schedule areconciliation. See the online help for informationabout scheduling a reconciliation.

CTGIMT015E An error occurred while deleting theusername account because theaccount does not exist.

This error might occur when you attempt to delete auser. This error might also occur if you attempt tochange the password for a user. To fix the problem,ensure that:

v The location specified for the managed resource iscorrect.

v The user was created on the resource.

v The user was not deleted from the resource.

v If the user does not exist on the resource, create theuser on the resource and then schedule areconciliation. See the online help for informationabout scheduling a reconciliation.

CTGIMT211E The account was notadded/modified/deleted due to asystem error: An end of file errorhas occurred. Please continue or askyour systems administrator to checkyour application configuration if theproblem persists.(SBL-DAT-00393).

Verify that the Siebel.jar and SiebelJI_enu.jar files inITDI_HOME/jars/3rdparty/others directory are copiedfrom the same Siebel server that is used to manage theusers.

CTGIMT222W The account is already suspended. This error might occur if you attempt to suspend anaccount that was already suspended.

CTGIMT224W The account is already restored. This error might occur if you attempt to restore anaccount that was already restored.

CTGIMT600E An error occurred while establishingcommunication with the IBM TivoliDirectory Integrator server.

v Verify that the adapter service is running.

v Verify that the URL specified on the service form forIBM Tivoli Directory Integrator is correct.


Appendix A. Adapter attributes

The IBM Security Identity Manager server communicates with the Siebel JDBAdapter by using attributes that are included in transmission packets that are sentover a network.

The following table lists the attributes that are used by the Siebel JDB Adapteraccount object class erTDISblJDBAccount and the corresponding counterparts in theUser business component on the Siebel server.

Table 15. Attributes, descriptions, and corresponding Siebel attributes forerTDISblJDBAccount

Attribute name Description Required Siebel attribute

erUid User ID Yes Login Name

erPassword Password for theuser ID

No LDAP auth.: Passwordand Verify Password DBauth.:<In database>

erAccountStatus Status of theaccount(suspended/restored)

No LDAP auth.: <InLDAP> DB auth.: <Indatabase>

erTDISblIsEmployee Type of account(Employee/Contactuser)

No Employee Flag

erTDISblFirstName Given name Yes First Name

erTDISblLastName Surname Yes Last Name

erTDISblMiddleName Middle initial No Middle Name

erTDISblJobTitle Job title No Job Title

erTDISblAlias Alias No Alias

erTDISblTZone Time zone No Time Zone

erTDISblWorkPhone Work telephonenumber

No Phone #

erTDISblHomePhone Home telephonenumber

No Home Phone #

erTDISblFaxNo Fax number No Fax #

erTDISblEmail Email address No Email Addr

erTDISblEmpNo Employee number No EMP #

erTDISblCellPhone Cell telephonenumber

No Cell Phone #

erTDISblShortName Short name No Nick Name

erTDISblPagerNo Pager number No Pager Phone #

erTDISblPagerPin Pager PIN No Pager PIN

erTDISblEmergencyNtfy Emergencynotification

No Emergency Notification

erTDISblStndNotify Standardnotification

No Standard Notification


Table 15. Attributes, descriptions, and corresponding Siebel attributes forerTDISblJDBAccount (continued)

Attribute name Description Required Siebel attribute

erTDISblAvail Availability No Availability Status

erTDISblAvailUntil Overtimeavailability

No Availability Status Until

erTDISblRelPositions Positions No Position

erTDISblRelResponsibility Responsibilities No Responsibility

erTDISblPersonalTitle Name title(Mr./Mrs.)

No Personal Title

erTDISblBUnits Employeeorganizations

No Employee Organization

erTDISblPrimBUnit Primary employeeorganization

No Primary EmployeeOrganization

erTDISblPrimPosition Primary positionID

No Primary Position

erTDISblLDAPRelResponsibility Responsibilities inLDAP

No Responsibility in LDAP(Available for onlyLDAP authentication.)

erLastAccessDate Last access date No erLastAccessDate

The following table lists the attributes that are used by the Siebel JDB Adapterresponsibility support DataObject class erTDISblResponsibility and thecorresponding counterparts in the Responsibility business component on the Siebelserver.

Table 16. Attributes, descriptions, and corresponding Siebel attributes forerTDISblResponsibility

Object class attribute Description Required Siebel attribute

erTDISblRespName Name of theresponsibility

Yes Name

erTDISblRespDisplayName Display name on theIBM Security IdentityManager user interface

Yes Name + PrimaryOrganization ID +Description

erTDISblRespOrgName Responsibility nameand the primaryorganization ID itbelongs to

Yes Name + PrimaryOrganization ID

The following table lists the attributes that are used by the Siebel JDB Adapterposition support DataObject class erTDISblPosition and the correspondingcounterparts in the Position business component on the Siebel server.

Table 17. Attributes, descriptions, and corresponding Siebel attributes for erTDISblPosition


erTDISblPostnId ID of position onresource

Yes Position ID

erTDISblPostnName Name of the position Yes Name + Division +Position ID +Description


The following table lists the attributes that are used by the Siebel JDB Adapter timezone support DataObject class erTDISblTZones and the corresponding counterpartin the Time Zone business component on the Siebel server.

Table 18. Attribute, description, and corresponding Siebel attribute for erTDISblTZones


erTDISblTZName Name of time zone Yes Name

The following table lists the attributes that are used by the Siebel JDB Adapterpersonal title support DataObject class erTDISblTitles and the correspondingcounterpart in the List of Values business component on the Siebel server.

Table 19. Attribute, description, and corresponding Siebel attribute for erTDISblTitles


erTDISblTitle Name of title onresource

Yes Value

The following table lists the attributes that are used by the Siebel JDB Adapternotification type support DataObject class erTDISblEmpNotify and thecorresponding counterpart in the List of Values business component on the Siebelserver.

Table 20. Attribute, description, and corresponding Siebel attribute for erTDISblEmpNotify


erTDISblNotifyType Type of employeenotification

Yes Value

The following table lists the attributes that are used by the Siebel JDB Adapteravailability type support DataObject class erTDISblEmpAvail and the correspondingcounterpart in the List of Values business component on the Siebel server.

Table 21. Attribute, description, and corresponding Siebel attribute for erTDISblEmpAvail


erTDISblAvailType Type of employeeavailability

Yes Value

The following table lists the attributes that are used by the Siebel JDB Adapteremployee organization support DataObject class erTDISblBU and the correspondingcounterparts in the Organization business component on the Siebel server.

Table 22. Attributes, descriptions, and corresponding Siebel attributes for erTDISblBU


erTDISblBUnitName Name of organization Yes Name

erTDISblBUnitId ID of organization Yes Organization ID

Appendix A. Adapter attributes 35

Appendix B. Definitions for ITDI_HOME and ISIM_HOMEdirectories

ITDI_HOME is the directory where Tivoli Directory Integrator is installed.ISIM_HOME is the directory where IBM Security Identity Manager is installed.

ITDI_HOMEThis directory contains the jars/connectors subdirectory that contains filesfor the adapters.

Windowsdrive\Program Files\IBM\TDI\ITDI_VERSION

For example the path for version 7.1:C:\Program Files\IBM\TDI\V7.1

UNIX/opt/IBM/TDI/ITDI_VERSION

For example the path for version 7.1:/opt/IBM/TDI/V7.1

ISIM_HOMEThis directory is the base directory that contains the IBM Security IdentityManager code, configuration, and documentation.

Windowspath\IBM\isim

UNIXpath/IBM/isim


Appendix C. Support information

You have several options to obtain support for IBM products.v “Searching knowledge bases”v “Obtaining a product fix” on page 40v “Contacting IBM Support” on page 40

Searching knowledge basesYou can often find solutions to problems by searching IBM knowledge bases. Youcan optimize your results by using available resources, support tools, and searchmethods.

About this task

You can find useful information by searching the product documentation for IBMSecurity Identity Manager. However, sometimes you must look beyond the productdocumentation to answer your questions or resolve problems.

Procedure

To search knowledge bases for information that you need, use one or more of thefollowing approaches:1. Search for content by using the IBM Support Assistant (ISA).

ISA is a no-charge software serviceability workbench that helps you answerquestions and resolve problems with IBM software products. You can findinstructions for downloading and installing ISA on the ISA website.

2. Find the content that you need by using the IBM Support Portal.The IBM Support Portal is a unified, centralized view of all technical supporttools and information for all IBM systems, software, and services. The IBMSupport Portal lets you access the IBM electronic support portfolio from oneplace. You can tailor the pages to focus on the information and resources thatyou need for problem prevention and faster problem resolution. Familiarizeyourself with the IBM Support Portal by viewing the demo videos(https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos)about this tool. These videos introduce you to the IBM Support Portal, exploretroubleshooting and other resources, and demonstrate how you can tailor thepage by moving, adding, and deleting portlets.

3. Search for content about IBM Security Identity Manager by using one of thefollowing additional technical resources:v IBM Security Identity Manager version 6.0 technotes and APARs (problem

reports).v IBM Security Identity Manager Support website.v IBM Redbooks®.v IBM support communities (forums and newsgroups).

4. Search for content by using the IBM masthead search. You can use the IBMmasthead search by typing your search string into the Search field at the top ofany ibm.com® page.

5. Search for content by using any external search engine, such as Google, Yahoo,or Bing. If you use an external search engine, your results are more likely to


http://www.ibm.com/software/support/isa/

http://www.ibm.com/support/entry/portal/overview/software/tivoli/tivoli_identity_manager

https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos

http://www.ibm.com/support/search.wss?rs=644&apar=include&tc=SSTFWV&dc=DB520+D800+D900+DA900+DA800+DB550+D100&dtm&atrn=SWVersion&atrv=5.1

http://www.ibm.com/support/search.wss?rs=644&apar=include&tc=SSTFWV&dc=DB520+D800+D900+DA900+DA800+DB550+D100&dtm&atrn=SWVersion&atrv=5.1

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliIdentityManager.html

http://publib-b.boulder.ibm.com/Redbooks.nsf/portals/Tivoli

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Communities.html

include information that is outside the ibm.com domain. However, sometimesyou can find useful problem-solving information about IBM products innewsgroups, forums, and blogs that are not on ibm.com.

Tip: Include “IBM” and the name of the product in your search if you arelooking for information about an IBM product.

Obtaining a product fixA product fix might be available to resolve your problem.

About this task

You can get fixes by following these steps:

Procedure1. Obtain the tools that are required to get the fix. You can obtain product fixes

from the Fix Central Site. See http://www.ibm.com/support/fixcentral/.2. Determine which fix you need.3. Download the fix. Open the download document and follow the link in the

“Download package” section.4. Apply the fix. Follow the instructions in the “Installation Instructions” section

of the download document.

Contacting IBM SupportIBM Support assists you with product defects, answers FAQs, and helps usersresolve problems with the product.

Before you begin

After trying to find your answer or solution by using other self-help options suchas technotes, you can contact IBM Support. Before contacting IBM Support, yourcompany or organization must have an active IBM software subscription andsupport contract, and you must be authorized to submit problems to IBM. Forinformation about the types of available support, see the Support portfolio topic inthe “Software Support Handbook”.

Procedure

To contact IBM Support about a problem:1. Define the problem, gather background information, and determine the severity

of the problem. For more information, see the Getting IBM support topic in theSoftware Support Handbook.

2. Gather diagnostic information.3. Submit the problem to IBM Support in one of the following ways:

v Using IBM Support Assistant (ISA):Any data that has been collected can be attached to the service request.Using ISA in this way can expedite the analysis and reduce the time toresolution.a. Download and install the ISA tool from the ISA website. See

http://www.ibm.com/software/support/isa/.b. Open ISA.


http://www.ibm.com/support/fixcentral/

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/offerings.html

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/getsupport.html

http://www.ibm.com/software/support/isa/

c. Click Collection and Send Data.d. Click the Service Requests tab.e. Click Open a New Service Request.

v Online through the IBM Support Portal: You can open, update, and view allof your service requests from the Service Request portlet on the ServiceRequest page.

v By telephone for critical, system down, or severity 1 issues: For the telephonenumber to call in your region, see the Directory of worldwide contacts webpage.

Results

If the problem that you submit is for a software defect or for missing or inaccuratedocumentation, IBM Support creates an Authorized Program Analysis Report(APAR). The APAR describes the problem in detail. Whenever possible, IBMSupport provides a workaround that you can implement until the APAR isresolved and a fix is delivered. IBM publishes resolved APARs on the IBM Supportwebsite daily, so that other users who experience the same problem can benefitfrom the same resolution.

Appendix C. Support information 41

http://www.ibm.com/software/support/

http://www.ibm.com/planetwide/

Appendix D. Accessibility features for IBM Security IdentityManager

Accessibility features help users who have a disability, such as restricted mobilityor limited vision, to use information technology products successfully.

Accessibility features

The following list includes the major accessibility features in IBM Security IdentityManager.v Support for the Freedom Scientific JAWS screen reader applicationv Keyboard-only operationv Interfaces that are commonly used by screen readersv Keys that are discernible by touch but do not activate just by touching themv Industry-standard devices for ports and connectorsv The attachment of alternative input and output devices

The IBM Security Identity Manager library, and its related publications, areaccessible.

Keyboard navigation

This product uses standard Microsoft Windows navigation keys.

Related accessibility information

The following keyboard navigation and accessibility features are available in theform designer:v You can use the tab keys and arrow keys to move between the user interface

controls.v You can use the Home, End, Page Up, and Page Down keys for more

navigation.v You can launch any applet, such as the form designer applet, in a separate

window to enable the Alt+Tab keystroke to toggle between that applet and theweb interface, and also to use more screen workspace. To launch the window,click Launch as a separate window.

v You can change the appearance of applets such as the form designer by usingthemes, which provide high contrast color schemes that help users with visionimpairments to differentiate between controls.

IBM and accessibility

See the IBM Human Ability and Accessibility Center For more information aboutthe commitment that IBM has to accessibility.


http://www.ibm.com/able

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law :

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to


IBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

If you are viewing this information softcopy, the photographs and colorillustrations might not appear.

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at http://www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

Notices 47

http://www.ibm.com/legal/copytrade.shtml

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Privacy Policy Considerations

IBM Software products, including software as a service solutions, ("SoftwareOfferings") may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, and to tailor interactionswith the end user or for other purposes. In many cases, no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM's Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details/us/ensections entitled "Cookies, Web Beacons and Other Technologies and SoftwareProducts and Software-as-a Service".


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details/us/en

Index

Aaccessibility viii, 43account form

attribute addition 18customization 17

adapterattributes 33features 1overview 1troubleshooting errors 31user account management tasks 11

ADAPTER_SOLDIR 3add user accounts 12adding attributes to the account form 18assembly line

icons 20mapping 20siebelJDBAdd assembly line 21siebelJDBModify assembly line 22siebelJDBSearch assembly line

add connectors 29mapping attributes 24

attributeadding user accounts 13map 20reconciling 12schema.dsml file 29

Bbusiness component attribute types

identification 17

Cconfiguration

IBM Security Identity Manager 3MVGBusComponent 7view mode 7view modes 5

connection parameter mapping 30creating custom XML files 28custom XML files

attribute definitions 17create 28specifying view mode values 5

customization, account form 17CustomLabels.properties file 19

Ddeleting user accounts 16

Eeducation viiierrors, troubleshooting 31

Ffiles

custom XML files 5CustomLabels.properties file 19schema.dsml file 19

IIBM

Software Support viiiSupport Assistant viii

IBM Support Assistant 40ISA 40ISIM_HOME definition 37ITDI_HOME 3ITDI_HOME definition 37

Kknowledge bases 39

Mmapping attributes 20modification

MVGBusComponent custom value 8user or employee data 8

MVGBusComponent custom valuesmodification of user or employee

data 8reconciliation for support data 7reconciliation for user data 8

Nnotices 45

Oonline

publications viiterminology vii

operationsadd 12change passwords 16deletion 16modification 14reconciliation 11restoration 16suspension 16

Ppassword change of user accounts 16problem-determination viiipublications

accessing online viilist of vii

Rreconciliation

MVGBusComponent custom value 7,8

new support data 27supporting data 12user accounts 11

Sschema.dsml file 19service.def file 30Siebel JDB Adapter 1siebelJDBAdd assembly line 21siebelJDBModify assembly line 22siebelJDBSearch assembly line 24support contact information 40support data reconciliation 12

Tterminology viitraining viiitroubleshooting

adapter errors 31contacting support 40getting fixes 40searching knowledge bases 39support website viii

Uuser accounts

add 12changing passwords 16deletion 16modification 14reconciliation 11restoration 16restoriation 16suspension 16

Vview modes

configuring 5default values 5definition 5


��

Printed in USA

SC27-4418-02

Siebel JDBAdapter User Guide - IBM · PDF fileIBM Security Identity Manager Version 6.0 Siebel...

Documents

Transcript of Siebel JDBAdapter User Guide - IBM · PDF fileIBM Security Identity Manager Version 6.0 Siebel...