PeopleToolsAdapter Installation and Configuration Guide · 2016-03-10 · PeopleToolsAdapter Installation and Configuration Guide SC27-4405-02. Note Before using this information

IBM Security Identity ManagerVersion 6.0

PeopleTools Adapter Installation andConfiguration Guide

SC27-4405-02

��

IBM Security Identity ManagerVersion 6.0

PeopleTools Adapter Installation andConfiguration Guide

SC27-4405-02

��

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

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

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Preface . . . . . . . . . . . . . . . ixAbout this publication . . . . . . . . . . . ixAccess to publications and terminology . . . . . ixAccessibility . . . . . . . . . . . . . . xTechnical training. . . . . . . . . . . . . xSupport information . . . . . . . . . . . . xStatement of Good Security Practices . . . . . . x

Chapter 1. Overview of the adapter . . . 1Features of the adapter . . . . . . . . . . . 1Architecture of the adapter . . . . . . . . . 1Supported configurations . . . . . . . . . . 2

Chapter 2. Preparation for installing theadapter . . . . . . . . . . . . . . . 5Preinstallation roadmap . . . . . . . . . . 5Installation roadmap. . . . . . . . . . . . 5Prerequisites . . . . . . . . . . . . . . 6Installation worksheet for the adapter . . . . . . 7Software downloads for the PeopleTools adapter . . 7

Chapter 3. Adapter installation . . . . . 9Verification of the Dispatcher installation . . . . . 9Installing the adapter . . . . . . . . . . . 9Modifying the PRG_USR_PROFILE record . . . . 10Loading the PeopleTools Project for IBM SecurityIdentity Manager . . . . . . . . . . . . 10

Loading the component interfaces . . . . . . 11Setting the component interface security . . . . 11

PeopleSoft resource-specific JAR files . . . . . . 12Generating the CompIntfc.jar file . . . . . . 13psjoa.jar file . . . . . . . . . . . . . 14JDBC type 4 driver JAR file . . . . . . . . 14

Installation verification . . . . . . . . . . 15Start, stop, and restart of the PeopleTools adapterservice . . . . . . . . . . . . . . . . 15Importing the adapter profile into the IBM SecurityIdentity Manager server . . . . . . . . . . 16Deploying the ID type subform. . . . . . . . 17Adapter profile installation verification . . . . . 17Adapter user account . . . . . . . . . . . 17Creating a service . . . . . . . . . . . . 18

Chapter 4. First steps after installation 23Adapter configuration options . . . . . . . . 23

Customizing the adapter profile . . . . . . 23Editing adapter profiles on the UNIX or Linuxoperating system . . . . . . . . . . . 24

Password management when restoring accounts . . 25Language pack installation for the PeopleToolsadapter . . . . . . . . . . . . . . . . 25Verifying that the PeopleTools adapter is workingcorrectly . . . . . . . . . . . . . . . 25

Chapter 5. Troubleshooting of theadapter errors . . . . . . . . . . . 27Techniques for troubleshooting problems . . . . 27Warning and error messages. . . . . . . . . 29

Chapter 6. Adapter upgrade. . . . . . 33Connector upgrade . . . . . . . . . . . . 33Dispatcher upgrade. . . . . . . . . . . . 33Upgrade of the existing adapter profile . . . . . 33

Chapter 7. Uninstallation of thePeopleTools adapter . . . . . . . . . 35Uninstalling the adapter from the IBM TivoliDirectory Integrator server . . . . . . . . . 35Removal of the adapter profile from the IBMSecurity Identity Manager server . . . . . . . 35

Chapter 8. Adapter reinstallation . . . 37

Appendix A. Adapter attributes . . . . 39Attributes by adapter actions . . . . . . . . 40

System Login Add . . . . . . . . . . . 40System Login Change . . . . . . . . . . 40System Login Delete . . . . . . . . . . 40System Login Suspend . . . . . . . . . 40System Login Restore . . . . . . . . . . 41System Change Password . . . . . . . . 41Test . . . . . . . . . . . . . . . . 41Reconciliation . . . . . . . . . . . . 41

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

Appendix C. Support information . . . 45Searching knowledge bases . . . . . . . . . 45Obtaining a product fix . . . . . . . . . . 46Contacting IBM Support . . . . . . . . . . 46

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

Notices . . . . . . . . . . . . . . 51

Index . . . . . . . . . . . . . . . 55

© Copyright IBM Corp. 2012, 2014 iii

iv IBM Security Identity Manager: PeopleTools Adapter Installation and Configuration Guide

Figures

1. The architecture of the PeopleTools Adapter 22. Example of a single server configuration . . . 2

3. Example of a multiple server configuration 3

© Copyright IBM Corp. 2012, 2014 v

vi IBM Security Identity Manager: PeopleTools Adapter Installation and Configuration Guide

Tables

1. Preinstallation roadmap . . . . . . . . . 52. Installation roadmap . . . . . . . . . . 53. Prerequisites to install the adapter . . . . . 64. Required information to install the adapter 75. Specific warning and error messages and

actions . . . . . . . . . . . . . . 296. General warning and error messages and

actions . . . . . . . . . . . . . . 307. Attributes, OIDs, descriptions and

corresponding PeopleTools attributes . . . . 39

8. Add request attributes for AIX, HPUX, Linux,and Solaris . . . . . . . . . . . . . 40

9. Change request attributes . . . . . . . . 4010. Delete request attributes . . . . . . . . 4011. Suspend request attributes . . . . . . . 4112. Restore request attributes . . . . . . . . 4113. System change password request attributes 4114. Test attributes . . . . . . . . . . . . 4115. Reconciliation request attributes. . . . . . 41

© Copyright IBM Corp. 2012, 2014 vii

viii IBM Security Identity Manager: PeopleTools Adapter Installation and Configuration Guide

Preface

About this publication

The PeopleTools Adapter Installation and Configuration Guide provides the basicinformation that you can use to install and configure the IBM® Security IdentityManager PeopleTools Adapter. The adapter enables connectivity between the IBMSecurity Identity Manager server and the managed resource.

IBM Security Identity Manager was previously known 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 ix

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 45 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.

x IBM Security Identity Manager: PeopleTools Adapter Installation and Configuration Guide

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

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

Chapter 1. Overview of the adapter

The PeopleTools Adapter enables communication between the IBM SecurityIdentity Manager server and the PeopleSoft server.

An adapter provides an interface between a managed resource and the IBMSecurity Identity Manager server. Adapters might reside on the managed resource.The IBM Security Identity Manager server manages access to the resource by usingyour security system. Adapters function as trusted virtual administrators on thetarget platform. They perform tasks, such as creating, suspending, and restoringuser accounts, and other administrative functions that are performed manually. Theadapter runs as a service, independently of whether you are logged on to the IBMSecurity Identity Manager server.

Features of the adapterThe adapter automates user account management tasks.

The adapter automates the following tasks:v Reconciling user accounts and support data, such as languages, currency code,

roles, and permission lists.v Adding, modifying, and deleting user accountsv Modifying user account attributesv Modifying user account passwordv Checking the connection between the PeopleSoft Application Server and IBM

Security Identity Manager

Architecture of the adapterYou must install the following components for the adapter to function correctly.

The adapter requires the following components:v The Dispatcherv The IBM Tivoli Directory Integrator connectorv The IBM Security Identity Manager adapter profile

You must install the Dispatcher and the adapter profile; however, the TivoliDirectory Integrator connector might already be installed with the base TivoliDirectory Integrator product.

Figure 1 on page 2 describes the components that work together to complete theuser account management tasks in a Tivoli Directory Integrator environment.

© Copyright IBM Corp. 2012, 2014 1

For more information about Tivoli Directory Integrator, see the Quick Start Guide atIBM Security Identity Manager product documentation.

Supported configurationsThe adapter supports both single server and multiple server configurations.

The fundamental components in each environment are:v The IBM Security Identity Manager serverv The IBM Tivoli Directory Integrator serverv The managed resourcev The adapter

The adapter must reside directly on the server running the Tivoli DirectoryIntegrator server.

Single server configuration

In a single server configuration, install the IBM Security Identity Manager server,the Tivoli Directory Integrator server, and the PeopleTools Adapter on one serverto establish communication with the PeopleSoft Application Server.

The PeopleSoft Application Server is installed on a different server as described inFigure 2.

Multiple server configuration

In a multiple server configuration, the IBM Security Identity Manager server, theTivoli Directory Integrator server, the PeopleTools Adapter, and the PeopleSoftApplication Server are installed on different servers.

Install theTivoli Directory Integrator server and the PeopleTools Adapter on thesame server as described in Figure 3 on page 3.

RMI callsIBM SecurityIdentityManagerServer

DispatcherService(an instanceof the IBMTivoliDirectoryIntegrator)

Adapterresource

Figure 1. The architecture of the PeopleTools Adapter

IBM SecurityIdentity Manager Server

Tivoli DirectoryIntegrator Server

Adapter

Managed

resource

Figure 2. Example of a single server configuration

2 IBM Security Identity Manager: PeopleTools Adapter Installation and Configuration Guide

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itim.doc/welcome.htm

IBM SecurityIdentity Managerserver

Tivoli DirectoryIntegrator server Managed

resource

Adapter

Figure 3. Example of a multiple server configuration

Chapter 1. Overview of the adapter 3


Chapter 2. Preparation for installing the adapter

Installing and configuring the adapter involves several steps that you mustcomplete in an appropriate sequence. Review the roadmaps before you begin theinstallation process.

Preinstallation roadmapBefore you install the adapter, you must prepare the environment.

Before you install the adapter, you must prepare the environment by performingthe tasks that are listed in Table 1.

Table 1. Preinstallation roadmap

Task For more information

Obtain the installation software. Download the software from PassportAdvantage® website. See “Softwaredownloads for the PeopleTools adapter” onpage 7.

Verify that your environment meets thesoftware and hardware requirements for theadapter.

See “Prerequisites” on page 6.

Obtain the necessary information for theinstallation and configuration.

See “Installation worksheet for the adapter”on page 7.

Installation roadmapTo install the adapter, complete the various sequential tasks.

Complete the task listed in the following table.

Table 2. Installation roadmap

Task For more information

Verify the Dispatcher installation. See “Verification of the Dispatcherinstallation” on page 9.

Install the adapter. See “Installing the adapter” on page 9.

Verify the installation. See “Installation verification” on page 15.

Import the adapter profile. See “Importing the adapter profile into theIBM Security Identity Manager server” onpage 16.

Verify the profile installation. See “Adapter profile installationverification” on page 17.

Create an adapter user account. See “Adapter user account” on page 17.

Create a service. See “Creating a service” on page 18.

Configure the adapter. See “Adapter configuration options” onpage 23.


PrerequisitesVerify that your environment meets all the prerequisites before installing theadapter.

Table 3 identifies the software and operating system prerequisites for the adapterinstallation.

Ensure that you install the adapter on the same workstation as the IBM TivoliDirectory Integrator server.

Table 3. Prerequisites to install the adapter

Prerequisite Description

Tivoli Directory Integrator server Version 7.1 fix pack 5 or later

Version 7.1.1

IBM Security Identity Manager server Version 6.0

PeopleSoft Enterprise Version 9.0

Version 9.1

PeopleTools Software Versions 8.50

Version 8.51

Version 8.52

System Administrator AuthorityTo complete the adapter installationprocedure, you must have systemadministrator authority.

Tivoli Directory Integrator adapters solutiondirectory

A Tivoli Directory Integrator adapterssolution directory is a Tivoli DirectoryIntegrator work directory for IBM SecurityIdentity Manager adapters. For moreinformation, see, the Dispatcher Installationand Configuration Guide.

You can install the adapter on all platforms that are supported by IBM TivoliDirectory Integrator 7.1. For information about the prerequisites and supportedoperating systems for Tivoli Directory Integrator, see the IBM Tivoli DirectoryIntegrator 7.1: Administrator Guide.


Installation worksheet for the adapterYou must understand the use and location of several directories before you installthe adapter.

Table 4. Required information to install the adapter

Required information Description Value

Tivoli DirectoryIntegrator HomeDirectory

The ITDI_HOME directory containsthe jars/connectors subdirectory thatcontains files for the adapters. Forexample, the jars/connectorssubdirectory contains the files for theUNIX adapter.

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 See the Dispatcher Installation andConfiguration Guide. 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

Software downloads for the PeopleTools adapterDownload the software through your account at the IBM Passport Advantagewebsite.

Go to IBM Passport Advantage.

See the IBM Security Identity Manager Download Document for instructions.

Note:

You can also obtain additional adapter information from IBM Support.

Chapter 2. Preparation for installing the adapter 7

http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm


Chapter 3. Adapter installation

All the Tivoli Directory Integrator-based adapters require the Dispatcher for theadapters to function correctly.

If the Dispatcher is installed from a previous installation, do not reinstall it unlessthere is an upgrade to the Dispatcher. See “Verification of the Dispatcherinstallation.”

After verifying the Dispatcher installation, you might need to install the TivoliDirectory Integrator connector. Depending on your adapter, the connector mightalready be installed as part of the Tivoli Directory Integrator product and nofurther action is required.

Verification of the Dispatcher installationIf this installation is the first adapter that is based on Tivoli Directory Integrator,you must install the Dispatcher before you install the adapter.

You must install the dispatcher on the same Tivoli Directory Integrator serverwhere you want to install the adapter.

Obtain the dispatcher installer from the IBM Passport Advantage website,http://ww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm.For information about Dispatcher installation, see the Dispatcher Installation andConfiguration Guide.

Installing the adapterBefore you install the adapter, you must install the connector to establishcommunication between the adapter and the Dispatcher.

Before you begin

The adapter uses the IBM Tivoli Directory Integrator PeopleSoft connector. Thisconnector is not available with the base Tivoli Directory Integrator product.

Make sure that you do the following tasks:v Verify that your site meets all the prerequisite requirements. See “Prerequisites”

on page 6.v Obtain a copy of the installation software. See “Software downloads for the

PeopleTools adapter” on page 7.v Obtain system administrator authority. See “Prerequisites” on page 6.v Verify that the Dispatcher is installed.

Procedure1. Create a temporary directory on the workstation where you want to install the

adapter.2. Extract the contents of the compressed file in the temporary directory.3. Copy the PeopleSoftConnector.jar file from the adapter package to the

ITDI_HOME/jars/connectors directory.


http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

4. Restart the Dispatcher service.

What to do next

After you finish the installing the adapter software, modify the PRG_USR_Profilerecord.

Modifying the PRG_USR_PROFILE recordUse the PeopleSoft Application Designer to modify PRG_USER_PROFILE record.

Procedure1. Log in to the PeopleTools Application Designer by using the PeopleTools

account of the adapter.2. From the File menu, click Open. The Open Definition dialog window is

displayed.3. Select Record from the Definition drop-down listbox.4. Type PRG in the Name field and click Open. A list of matching records is

displayed in the Definitions matching selection criteria pane.5. Select PRG_USR_PROFILE and click the Open. The record is opened in the

Application Designer.6. From within the Record Fields tabbed pane, right-click the OPRID table entry

and click View PeopleCode from the right-click menu. The PeopleCodewindow opens.

7. Select SaveEdit from the PeopleCode Event drop-down listbox. The followingPeopleCode is displayed in the PeopleCode edit pane.If %OperatorId <> PRG_USR_PROFILE.OPRID Then

If %Panel = Panel.PURGE_USR_PROFILE ThenWarning MsgGet(48, 122, "Select OK to confirm deletion of User Profile or

select Cancel.")End-If;

ElseError MsgGet(48, 109, "Message not found.");

End-If;

8. Replace the existing PeopleCode with the following code.If %OperatorId <> PRG_USR_PROFILE.OPRID Then

If %CompIntfcName <> "ENROLE_DELETE" ThenIf %Panel = Panel.PURGE_USR_PROFILE Then

Warning MsgGet(48, 122, "Select OK to confirm deletion of User Profile orselect Cancel.")End-If;

End-IfElse

Error MsgGet(48, 109, "Message not found.");End-If;

9. From the File menu, click Save to save the record.

What to do next

Load the PeopleTools Project for IBM Security Identity Manager.

Loading the PeopleTools Project for IBM Security Identity ManagerThe adapter software provides a compressed file that contains the PeopleToolsproject file. This file provides component interfaces that must be imported into thePeopleTools Application Designer.


About this task

The Project file PT850_COMPONENT.zip for PeopleTools 8.50, PeopleTools 8.51, andPeopleTools 8.52 is provided with the IBM Security Identity Manager PeopleToolsAdapter software that contains component interfaces. These interfaces are in theENROLE_AGENT subdirectory. This subdirectory is imported into the PeopleToolsApplication Designer as a PeopleTools Project.

Loading the IBM Security Identity Manager-specific PeopleTools project is atwo-part procedure.1. The project must be copied into the PeopleTools system. See “Loading the

component interfaces.”2. The project security must be set. The following two sections provide detailed

procedures on how to load the PeopleTools project for IBM Security IdentityManager. See “Setting the component interface security.”

Loading the component interfacesYou must import the ENROLE_AGENT directory into the PeopleTools ApplicationDesigner as a PeopleTools Project.

Procedure1. From the PT850_COMPONENT.zip file, extract ENROLE_AGENT and its contents

into a temporary directory on your file system.2. Log in to the PeopleTools Application Designer in two-tier mode by using the

PeopleTools account of the adapter.a. Click Start > Programs > Peopletools8.5x > Configuration Manager

b. Select the appropriate database type (for example, if the PeopleSoft isconfigured with oracle, select ORACLE).

c. Specify the server name, database name, and other details for the databasetype, if not already specified.

d. Click OK.3. Copy the ENROLE_AGENT project.

a. Log on to the PeopleTools Application Designer.b. From the Tools menu, select Copy Project and then select From File from

the submenu. The Copy Project from File dialog window is displayed.c. Browse to the directory where you extracted ENROLE_AGENT.

ENROLE_AGENT is displayed in the Projects: list area.d. Ensure that ENROLE_AGENT is highlighted and click Select. The

ENROLE_AGENT project is loaded. A second dialog window is displayed.e. Ensure that Component Interfaces is highlighted and click Copy. The

component interfaces are loaded into PeopleTools.4. Exit the PeopleTools Application Designer.

Setting the component interface securityYou must add components to the permissions list to set security for thePeopleTools project.

Procedure1. Log in to the PeopleSoft web interface by using the PeopleTools account of the

adapter.

Chapter 3. Adapter installation 11

|

2. From the PeopleSoft menu tree, navigate to PeopleTools > Security >Permissions & Roles > Permission Lists.

3. Search for the ALLPAGES permission list link. The Permission List componentis displayed.

4. Click the Component Interface tab and add the following ComponentInterfaces to the list:ENROLE_CCODEENROLE_DELETEENROLE_LANGSENROLE_PERMENROLE_ROLESENROLE_USERSENROLE_OPRALIAS

5. Set Full Access for each method of the component interfaces added in theprevious step.

6. Save your changes.

What to do next

Obtain and generate the PeopleSoft resource-specific JAR files.

PeopleSoft resource-specific JAR filesThe PeopleTools Adapter uses Java™ APIs to communicate and perform operationssuch as add, delete, modify, and search on the PeopleSoft resource.

To use these functions, the PeopleTools Adapter requires following jars:

CompIntfc.jarThe Java API JAR file for the ENROLE_AGENT Component Interfaceproject.

psjoa.jarThis file is created during the PeopleTools installation. The path to thepsjoa.jar file must be set to the ITDI CLASSPATH variable.

psft.jarTo create a psft.jar file:1. Go to the workstation where PeopleTools is installed.2. Locate the PSKeyStore.class file which is present in the pshttp folder of

PeopleTools. It is located in the web server installation directory. On aWindows installation it is in PeopleSoft_Home\webserv\PIA_DOMAIN\applications\peoplesoft\PORTAL\WEB-INF\classes\psft\pt8\pshttpdirectory. For example:E:\PS\PT845\webserv\peoplesoft_84512\applications\peoplesoft\PORTAL\

WEB-INF\classes\psft\pt8\pshttp.

3. Copy pshttp folder to a temporary folder containing folder structure aspsft\pt8. For example,C:\Temp\psft\pt8\pshttp

4. Go to command prompt and locate the temp folder containingpsft/pt8/pshttp folder structure. For example,C:\Temp

5. Create psft.jar by using the following command on command prompt.jar -cvf psft.jar psft


||

After the command is successfully completed, a JAR file psft.jar iscreated in the temp folder.

6. On the workstation where IBM Tivoli Directory Integrator is installed,copy psft.jar to the folder ITDI_HOME\jars\3rdParty\others.

JDBC type 4 driver JAR fileThis JAR file is required to establish the connection with the database.

Generating the CompIntfc.jar fileYou must create the CompIntfc.jar file from the Component interface JAVA files.The CompIntfc.jar file is the PeopleSoft Component Interface JAR file.

About this task

This file must be generated from the respective PeopleSoft resource and thencopied in the ITDI_HOME\jars\3rdParty\others directory on the workstation wherethe adapter is installed.

Procedure1. Log on to PeopleSoft Application Designer in two-tier mode.2. Open the ENROLE_AGENT Component Interface project and open all the

component interfaces by double-clicking each component interface.3. From the menu select Build > PeopleSoft APIs.4. From the Build PeopleSoft API Bindings window, select the Java classes Build

check box and clear the COM Type Library and C Header Files Build checkboxes.

5. In the Java Classes frame, select the Build check box and select the appropriateComponent Interfaces from the drop-down menu. You must select thefollowing options from the drop-down menu and then click OK:v CompIntfc.CompIntfcPropertyInfov CompIntfc.CompIntfcPropertyInfoCollectionv PeopleSoft.* (Select all the Component Interfaces that begin with the prefix

PeopleSoft)v CompIntfc.ENROLE_USERS* (Select all the Component Interfaces that begin

with the prefix CompIntfc.ENROLE_USERS)v CompIntfc.ENROLE_ROLES* (Select all the Component Interfaces that begin

with the prefix CompIntfc.ENROLE_ROLES)v CompIntfc.ENROLE_PERM* (Select all the Component Interfaces that begin

with the prefix CompIntfc.ENROLE_PERM)v CompIntfc.ENROLE_LANGS* (Select all the Component Interfaces that begin

with the prefix CompIntfc.ENROLE_LANGS)v CompIntfc.ENROLE_DELETE* (Select all the Component Interfaces that

begin with the prefix CompIntfc.ENROLE_DELETE)v CompIntfc.ENROLE_CCODE* (Select all the Component Interfaces that begin

with the prefix CompIntfc.ENROLE_CCODE)v CompIntfc.ENROLE_OPRALIAS* (Select all the Component Interfaces that

begin with the prefix CompIntfc.ENROLE_OPRALIAS)

Note: If you need to generate Component Interface Java files for the entiregroup of Component Interfaces click ALL.Specify the appropriate file path for the Java files; otherwise the Java files aregenerated in the default location, PEOPLESOFT_HOME\web\psjoa. The Component


|

Interface Java files are generated in the PeopleSoft\Generated\CompIntfcdirectory that is created in the specified location. For example, if you specifye:\enrole as the file path, then the Component Interface Java files aregenerated in the e:\enrole\PeopleSoft\Generated\CompIntfc directory.

6. Compile the Java files.a. Open the Command prompt and change directories to the folder where the

generated Java files are located. For example,cd e:\enrole

b. Navigate to the PeopleSoft\Generated\CompIntfc\ directory.c. Run the following command.

javac -classpath d:\temp\psjoa.jar *.java

where, d:\temp is a path to psjoa.jar file.d. Optional: You can delete all the generated Java files from the existing

directory, however, do not delete the .class files.7. Package the compiled files as the CompIntfc.jar file.

a. Open the Command prompt and change directories to the folder where thegenerated JAVA files are located. For example,cd e:\enrole

b. Run the command:jar –cvf CompIntfc.jar *

Note: Ensure that the Java compiler used for compiling the generated Java filesis compatible with bothv The Java provided with the PeopleSoft managed resourcev The Java provided with Tivoli Directory Integrator

8. Copy the generated CompIntfc.jar files to the ITDI_HOME\jars\3rdParty\othersdirectory.

psjoa.jar fileThis file is created in the PEOPLESOFT_HOME\web\psjoa directory during thePeopleTools installation.

You must copy the psjoa.jar file from PEOPLESOFT_HOME\web\psjoa to theITDI_HOME\jars\3rdParty\others directory on the workstation where the adapter isinstalled.

JDBC type 4 driver JAR fileBy default, the find method of a PeopleSoft Component Interface is limited to amaximum of 300 entries from PeopleSoft. If more than 300 entries need to beretrieved, the PeopleSoft Connector needs to invoke JDBC queries on thePeopleSoft database tables.

The path to the JDBC_driver.jar file for the database that is used by PeopleSoft,must be copied to the ITDI_HOME\jars\3rdParty\others directory.

The PeopleTools Adapter establishes the connection directly with the database if itfinds more than 300 records to be retrieved. The PeopleTools Adapter uses theJDBC Type 4 drivers to retrieve more than 300 records. To establish the connectionto the database you need to specify the appropriate driver class and a URL of thecorrect format.


For example:

PeopleSoft configured with the DB2®:

JDBC Drivers:db2jcc.jardb2jcc_javax.jardb2jcc_license_cu.jar

Driver Classcom.ibm.db2.jcc.DB2Driver

URL jdbc:db2://workstation:50000/database

PeopleSoft configured with the Microsoft SQL Server 2005:

JDBC Drivers:sqljdbc4.jar

Driver Classcom.microsoft.sqlserver.jdbc.SQLServerDriver

URLjdbc:sqlserver://workstation_name:port;instanceName=instance;SelectMethod=curson;DatabaseName=database

What to do next

After you finish the adapter installation, do the following tasks:v Verify that the installation completed successfully. See “Installation verification.”v Import the adapter profile. See “Importing the adapter profile into the IBM

Security Identity Manager server” on page 16.v Deploy the ID Type subform. See “Deploying the ID type subform” on page 17.v Create a user account for the adapter on IBM Security Identity Manager. See

“Adapter user account” on page 17.

Installation verificationIf the adapter is installed correctly, the PeopleSoftConnector.jar file exists in thespecified directory.

Windows operating systemdrive:\Program Files\IBM\TDI\V7.1\jars\connectors\

UNIX operating system/opt/IBM/TDI/V7.1/jars/connectors/

If this installation is to upgrade a connector, then send a request from IBM SecurityIdentity Manager. Verify that the version number in the ibmdi.log matches theversion of the connector that you installed. The ibmdi.log file is atITDI_Home\adapter solution directory\logs.

Start, stop, and restart of the PeopleTools adapter serviceTo start, stop, or restart the adapter, you must start, stop, or restart the Dispatcher.

The adapter does not exist as an independent service or a process. The adapter isadded to the Dispatcher instance, which runs all the adapters that are installed onthe same Tivoli Directory Integrator instance.


See the topic about starting stopping, and restarting the dispatcher service in theDispatcher Installation and Configuration Guide.

Importing the adapter profile into the IBM Security Identity Managerserver

An adapter profile defines the types of resources that the IBM Security IdentityManager server can manage. Use the profile to create an adapter service on IBMTivoli Directory Integrator server and establish communication with the adapter.

Before you begin

Verify that the following conditions are met:v The IBM Security Identity Manager server is installed and running.v You have root or administrator authority on IBM Security Identity Manager.

About this task

Before you can create an adapter service, the IBM Security Identity Manager servermust have an adapter profile to recognize the adapter. The files that are packagedwith the adapter include the adapter profile JAR file. You can import the adapterprofile as a service profile on the server with the Import feature of IBM SecurityIdentity Manager.

The PeopleToolsProfile.jar file includes all the files that are required to definethe adapter schema, account form, service form, and profile properties. You canextract the files from the JAR file to modify the necessary files and package theJAR file with the updated files.

Procedure1. Log on to the IBM Security Identity Manager server by using an account that

has the authority to perform administrative tasks.2. In the My Work pane, expand Configure System and click Manage Service

Types.3. On the Manage Service Types page, click Import to display the Import Service

Types page.4. Specify the location of the PeopleToolsProfile.jar file in the Service Definition

File field Take one of the following actions:a. Type the complete location of where the file is stored.b. Use Browse to navigate to the file.

5. Click OK.

Note:

v When you import the adapter profile and if you receive an error related tothe schema, see the trace.log file for information about the error. Thetrace.log file location is specified by using the handler.file.fileDirproperty defined in the IBM Security Identity ManagerenRoleLogging.properties file. The enRoleLogging.properties file isinstalled in the ITIM_HOME\data directory.

v Restart IBM Security Identity Manager for the change to take effect.


Deploying the ID type subformYou can use subforms to display additional information on the service form. Usethis procedure to enable the use of subforms.

About this task

You must perform this procedure on both WebSphere® and IBM Security IdentityManager. In a clustered environment the subform must be deployed on eachWebSphere application server.

Procedure1. Extract the opraliastype.zip file into a temporary folder For example, C:\temp.2. Copy the following files from the temporary folder to the subforms directory in

the IBM Security Identity Manager WebSphere deployment directory. Thedirectory locations are:

For a self service console installationWAS_PROFILE_HOME/installedApps/server/ITIM.ear/itim_self_service.war/subforms

For an administrative console installationWAS_PROFILE_HOME/installedApps/server/ITIM.ear/itim_console.war/subforms

For Identity Service Center installationWAS_PROFILE_HOME/installedApps/nodeName/ITIM.ear/isim_isc_subform.war

Note: WAS_PROFILE_HOME is typically C:\Program Files\IBM\WebSphere\AppServer\profiles or opt/IBM/WebSphere/AppServer/profiles.v opraliastype\opraliastype.jsp

v opraliastype\storeValues.jsp

v opraliastype\opraliasstyle.css

Adapter profile installation verificationAfter you install the adapter profile, verify that the installation was successful.

An unsuccessful installation:v Might cause the adapter to function incorrectly.v Prevents you from creating a service with the adapter profile.

To verify that the adapter profile is successfully installed, create a service with theadapter profile. For more information about creating a service, see “Creating aservice” on page 18.

If you are unable to create a service using the adapter profile or open an accounton the service, the adapter profile is not installed correctly. You must import theadapter profile again.

Adapter user accountYou must create a user account for the adapter on the managed resource. You mustprovide the account information when you create a service.


Ensure that the account has sufficient privileges to administer the PeoplesoftApplication server users.

For more information about creating a service, see “Creating a service.”

Creating a serviceAfter the adapter profile is imported on IBM Security Identity Manager, you mustcreate a service so that IBM Security Identity Manager can communicate with theadapter.

About this task

To create or change a service, you must use the service form to provideinformation for the service. Service forms might vary depending on the adapter.

Note: If the following fields on the service form are changed for an existingservice, the IBM Security Identity ManagerAdapter service on the Tivoli DirectoryIntegrator server needs to be restarted.v JDBC driver

v JDBC URL

v Database user name

v Database user password

v AL FileSystem Path

v Max Connection Count

Procedure1. Log on to the IBM Security Identity Manager server with an account that has

the authority to perform administrative tasks.2. In the My Work pane, click Manage Services and click Create.3. On the Select the Type of Service page, select PeopleTools Profile.4. Click Next to display the adapter service form.5. Complete the following fields on the service form:

On the General Information tab:

Service NameSpecify a name that defines the adapter service on the IBMSecurity Identity Manager server.

Note: Do not use forward (/) or backward slashes (\) in theservice name.

DescriptionOptional: Specify a description that identifies the service foryour environment.

IBM Tivoli Directory Integrator locationOptional: Specify the URL for the Tivoli Directory Integratorinstance. The valid syntax for the URL is rmi://ip-address:port/ITDIDispatcher, where ip-address is the TivoliDirectory Integrator host and port is the port number for theDispatcher. The default URL isrmi://localhost:1099/ITDIDispatcher


For information about changing the port number, see IBMSecurity Dispatcher Installation and Configuration Guide.

OwnerOptional: Specify a IBM Security Identity Manager user as aservice owner.

Service prerequisiteOptional: Specify a IBM Security Identity Manager service thatis a prerequisite to this service.

On the PS Connection tab:

APP Server nameSpecify the name or IP address of the PeopleTools ApplicationServer to be managed.

APP Server portSpecify the port number used to connect to the PeopleToolsApplication Server. This number is the IP port number onwhich the PeopleTools Application Server listens for JOLTconnections. This value is typically port 9000.

PS APP IDSpecify the name of the PeopleTools account created for theadapter.

APP ID passwordSpecify a password of the PeopleTools account created for theadapter.

JDBC driverSpecify the database type 4 JDBC driver.

For example, the JDBC driver for IBM DB2 databaseconnectivity is: com.ibm.db2.jcc.DB2Driver. See “JDBC type 4driver JAR file” on page 14 for more information.

JDBC URLSpecify the Web address that is used to connect to thePeopleSoft tables.

For example, the connectivity JDBC URL for IBM DB2 databaseis:jdbc:db2://10.77.68.37:50000/PTDBjdbc:db2://ip address:port/database name

See “JDBC type 4 driver JAR file” on page 14 for moreinformation.

Database user nameSpecify the administrator user name that is used to connect tothe database.

Database user passwordSpecify the password for the database user.

Database table ownerSpecify the name of the PeopleTools database table owner.

On the Dispatcher Attributes tab:

AL FileSystem PathSpecify the file path from where the dispatcher loads the


assembly lines. If you do not specify a file path, the dispatcherloads the assembly lines received from IBM Security IdentityManager. For example, you can specify the following file pathto load the assembly lines from the profiles directory of theWindows operating system: c:\Program Files\IBM\TDI\V7.1\profiles or you can specify the following file path to load theassembly lines from the profiles directory of the UNIX andLinux operating systems: /opt/IBM/TDI/V7.1/profiles.

Disable AL CachingSelect the check box to disable the assembly line caching in thedispatcher for the service. The assembly lines for the add,modify, delete, and test operations are not cached.

Max Connection CountSpecify the maximum number of assembly lines that thedispatcher can execute simultaneously for the service. If youenter 0 in the Max Connection Count field, the dispatcher doesnot limit the number of assembly lines that are executedsimultaneously for the service.

On the Status and information tabThis page contains read only information about the adapter andmanaged resource. These fields are examples. The actual fields varydepending on the type of adapter and how the service form isconfigured. The adapter must be running to obtain the information.Click Test Connection to populate the fields.

Last status update: DateSpecifies the most recent date when the Status and informationtab was updated.

Last status update: TimeSpecifies the most recent time of the date when the Status andinformation tab was updated.

Managed resource statusSpecifies the status of the managed resource that the adapter isconnected to.

Adapter versionSpecifies the version of the adapter that the IBM SecurityIdentity Manager service uses to provision request to themanaged resource.

Profile versionSpecifies the version of the profile that is installed in the IBMSecurity Identity Manager server.

TDI versionSpecifies the version of the Tivoli Directory Integrator on whichthe adapter is deployed.

Dispatcher versionSpecifies the version of the Dispatcher.

Installation platformSpecifies summary information about the operating systemwhere the adapter is installed.

Adapter accountSpecifies the account that running the adapter binary file.


Adapter up time: DateSpecifies the date when the adapter started.

Adapter up time: TimeSpecifies the time of the date when the adapter started.

Adapter memory usageSpecifies the memory usage for running the adapter.

If the connection fails, follow the instructions in the error message. Alsov Verify the adapter log to ensure that the IBM Security Identity

Manager test request was successfully sent to the adapter.v Verify the adapter configuration information.v Verify IBM Security Identity Manager service parameters for the

adapter profile. For example, verify the work station name or the IPaddress of the managed resource and the port.

6. Click Finish.



Chapter 4. First steps after installation

After you install the adapter, you must perform several other tasks. The tasksinclude configuring the adapter, setting up SSL, installing the language pack, andverifying the adapter works correctly.

Adapter configuration optionsThese sections describe the configuration options for the PeopleTools Adapter.v “Customizing the adapter profile”v “Editing adapter profiles on the UNIX or Linux operating system” on page 24

See the IBM Security Dispatcher Installation and Configuration Guide for additionalconfiguration options such as:v JVM propertiesv Dispatcher filteringv Dispatcher propertiesv Dispatcher port numberv Logging configurationsv Secure Sockets Layer (SSL) communication

Customizing the adapter profileTo customize the adapter profile, you must modify the PeopleTools Adapter JARfile. You might customize the adapter profile to change the account form or theservice form.

About this task

Use the Form Designer or CustomLabels.properties file to change the labels on theforms. Each adapter has a CustomLabels.properties file for that adapter. The JARfile is included in the PeopleTools Adapter compressed file that you downloadedfrom the IBM website.

Note: To modify the adapter schema, see the Directory Integrator-Based PeopleToolsAdapter User Guide.

The following files are included in the PeopleTools JAR file:v CustomLabels.propertiesv erpt84xrmiservice.xmlv erpt84xuseraccount.xmlv PeopleToolsAdapterALs.xmlv PeopleToolsAddAL.xmlv PeopleToolsDeleteAL.xmlv PeopleToolsModifyAL.xmlv PeopleToolsSearchAL.xmlv PeopleToolsTestAL.xmlv schema.dsmlv service.def


Procedure1. To edit the JAR file, log on to the workstation where the PeopleTools Adapter is

installed.2. Copy the JAR file into a temporary directory.3. Extract the contents of the JAR file into the temporary directory by running the

following command. The following example applies to the PeopleTools Adapterprofile. Type the name of the JAR file for your operating system.#cd /tmp#jar -xvf PeopleToolsProfile.jar

The jar command extracts the files into the PeopleToolsProfile directory.4. Edit the file that you want to change. After you edit the file, you must import

the file into the IBM Security Identity Manager server for the changes to takeeffect.

5. To import the file, create a JAR file by using the files in the /tmp directory byrunning the following commands:#cd /tmp#jar -cvf PeopleToolsProfile.jar PeopleToolsProfile

6. Import the JAR file into the IBM Security Identity Manager application server.For more information about importing the JAR file, see “Importing the adapterprofile into the IBM Security Identity Manager server” on page 16.

7. Stop and start the IBM Security Identity Manager server.8. Stop and start the PeopleTools Adapter service. See “Start, stop, and restart of

the PeopleTools adapter service” on page 15 for information about stoppingand starting the PeopleTools Adapter service.

Editing adapter profiles on the UNIX or Linux operatingsystem

The adapter profile .jar file might contain ASCII files that are created by using theMS-DOS ASCII format.

About this task

If you edit an MS-DOS ASCII file on the UNIX operating system, you might see acharacter ^M at the end of each line. These characters indicate new lines of text inMS-DOS. The characters can interfere with the running of the file on UNIX orLinux systems. You can use tools, such as dos2unix, to remove the ^M characters.You can also use text editors, such as the vi editor, to remove the charactersmanually.

Example

You can use the vi editor to remove the ^M characters. From the vi commandmode, run the following command and press Enter::%s/^M//g

When you use this command, enter ^M or Ctrl-M by pressing ^v^M or Ctrl V CtrlM sequentially. The ^v instructs the vi editor to use the next keystroke instead ofissuing it as command.


Password management when restoring accountsWhen an account is restored from being previously suspended, you are promptedto supply a new password for the reinstated account. However, in some cases youmight not want to be prompted for a password.

How each restore action interacts with its corresponding managed resourcedepends on either the managed resource, or the business processes that youimplement. Certain resources reject a password when a request is made to restorean account. In this case, you can configure IBM Security Identity Manager toforego the new password requirement. You can set the PeopleTools Adapter torequire a new password when the account is restored, if your company has abusiness process in place that dictates that the account restoration process must beaccompanied by resetting the password.

In the service.def file, you can define whether a password is required as a newprotocol option. When you import the adapter profile, if an option is not specified,the adapter profile importer determines the correct restoration password behaviorfrom the schema.dsml file. Adapter profile components also enable remote servicesto find out if you discard a password that is entered by the user in a situationwhere multiple accounts on disparate resources are being restored. In thissituation, only some of the accounts being restored might require a password.Remote services discard the password from the restore action for those managedresources that do not require them.

Edit the service.def file to add the new protocol options, for example:<Property Name = "com.ibm.itim.remoteservices.ResourceProperties.

PASSWORD_NOT_REQUIRED_ON_RESTORE"<value>true</value></property><Property Name = "com.ibm.itim.remoteservices.ResourceProperties.

PASSWORD_NOT_ALLOWED_ON_RESTORE"<value>false</value></property>

By adding the two options in the preceding example, you ensure that you are notprompted for a password when an account is restored.

Language pack installation for the PeopleTools adapterThe adapters use a separate language package from the IBM Security IdentityManager.

See the IBM Security Identity Manager library and search for information aboutinstalling the adapter language pack.

Verifying that the PeopleTools adapter is working correctlyAfter you install and configure the adapter, take steps to verify that the installationand configuration are correct.

Procedure1. Test the connection for the service that you created on IBM Security Identity

Manager.2. Run a full reconciliation from IBM Security Identity Manager.3. Run all supported operations such as add, modify, and delete on one user

account.

Chapter 4. First steps after installation 25

4. Verify the ibmdi.log file after each operation to ensure that no errors arereported.

5. Verify the IBM Security Identity Manager log file trace.log to ensure that noerrors are reported when you run an adapter operation.


Chapter 5. Troubleshooting of the adapter errors

Troubleshooting can help you determine why a product does not function properly.

These topics provide information and techniques for identifying and resolvingproblems with the adapter. It also provides information about troubleshootingerrors that might occur during the adapter installation.

Techniques for troubleshooting problemsTroubleshooting is a systematic approach to solving a problem. The goal oftroubleshooting is to determine why something does not work as expected andhow to resolve the problem. Certain common techniques can help with the task oftroubleshooting.

The first step in the troubleshooting process is to describe the problem completely.Problem descriptions help you and the IBM technical-support representative knowwhere to start to find the cause of the problem. This step includes asking yourselfbasic questions:v What are the symptoms of the problem?v Where does the problem occur?v When does the problem occur?v Under which conditions does the problem occur?v Can the problem be reproduced?

The answers to these questions typically lead to a good description of the problem,which can then lead you to a problem resolution.

What are the symptoms of the problem?

When starting to describe a problem, the most obvious question is “What is theproblem?” This question might seem straightforward; however, you can break itdown into several more-focused questions that create a more descriptive picture ofthe problem. These questions can include:v Who, or what, is reporting the problem?v What are the error codes and messages?v How does the system fail? For example, is it a loop, hang, crash, performance

degradation, or incorrect result?

Where does the problem occur?

Determining where the problem originates is not always easy, but it is one of themost important steps in resolving a problem. Many layers of technology can existbetween the reporting and failing components. Networks, disks, and drivers areonly a few of the components to consider when you are investigating problems.

The following questions help you to focus on where the problem occurs to isolatethe problem layer:v Is the problem specific to one platform or operating system, or is it common

across multiple platforms or operating systems?v Is the current environment and configuration supported?


v Do all users have the problem?v (For multi-site installations.) Do all sites have the problem?

If one layer reports the problem, the problem does not necessarily originate in thatlayer. Part of identifying where a problem originates is understanding theenvironment in which it exists. Take some time to completely describe the problemenvironment, including the operating system and version, all correspondingsoftware and versions, and hardware information. Confirm that you are runningwithin an environment that is a supported configuration; many problems can betraced back to incompatible levels of software that are not intended to run togetheror have not been fully tested together.

When does the problem occur?

Develop a detailed timeline of events leading up to a failure, especially for thosecases that are one-time occurrences. You can most easily develop a timeline byworking backward: Start at the time an error was reported (as precisely as possible,even down to the millisecond), and work backward through the available logs andinformation. Typically, you need to look only as far as the first suspicious eventthat you find in a diagnostic log.

To develop a detailed timeline of events, answer these questions:v Does the problem happen only at a certain time of day or night?v How often does the problem happen?v What sequence of events leads up to the time that the problem is reported?v Does the problem happen after an environment change, such as upgrading or

installing software or hardware?

Responding to these types of questions can give you a frame of reference in whichto investigate the problem.

Under which conditions does the problem occur?

Knowing which systems and applications are running at the time that a problemoccurs is an important part of troubleshooting. These questions about yourenvironment can help you to identify the root cause of the problem:v Does the problem always occur when the same task is being performed?v Does a certain sequence of events need to happen for the problem to occur?v Do any other applications fail at the same time?

Answering these types of questions can help you explain the environment inwhich the problem occurs and correlate any dependencies. Remember that justbecause multiple problems might have occurred around the same time, theproblems are not necessarily related.

Can the problem be reproduced?

From a troubleshooting standpoint, the ideal problem is one that can bereproduced. Typically, when a problem can be reproduced you have a larger set oftools or procedures at your disposal to help you investigate. Consequently,problems that you can reproduce are often easier to debug and solve.

However, problems that you can reproduce can have a disadvantage: If theproblem is of significant business impact, you do not want it to recur. If possible,


re-create the problem in a test or development environment, which typically offersyou more flexibility and control during your investigation.v Can the problem be re-created on a test system?v Are multiple users or applications encountering the same type of problem?v Can the problem be re-created by running a single command, a set of

commands, or a particular application?

For information about obtaining support, see Appendix C, “Support information,”on page 45.

Warning and error messagesA warning or error message might be displayed in the user interface to provideinformation about the adapter or when an error occurs.

Table 5 and Table 6 on page 30 contain warnings or errors which might bedisplayed in the user interface when the PeopleTools Adapter is installed on yoursystem.

Table 5. Specific warning and error messages and actions

Messagenumber Message Action

CTGIMT600E An error occurred whileestablishing communicationwith the IBM TivoliDirectory Integrator server.

v Verify that the IBM Tivoli DirectoryIntegrator-Based Adapter Service isrunning.

v Verify that the URL specified on theservice form for Tivoli DirectoryIntegrator is correct.

CTGIMT001E The following erroroccurred.

Error: Unable to connect toPeopleSoft Applicationserver.

v Verify that the PeopleSoft ApplicationServer is running.

v Verify that the credentials specified onthe service form of the PeopleSoftApplication Server are correct.

v Verify that the PeopleSoft administratoruser name and password specified on theservice form of the PeopleSoftApplication Server are correct.

CTGIMT003E The account already exists. The user has already been added to theresource. This error might occur if you areattempting to add a user to the managedresource and Tivoli Identity Manager is notsynchronized with the resource. To fix thisproblem, schedule a reconciliation betweenTivoli Identity Manager and the resource.See the online help for information aboutscheduling a reconciliation.

Chapter 5. Troubleshooting of the adapter errors 29

Table 5. Specific warning and error messages and actions (continued)

Messagenumber Message Action

CTGIMT015E An error occurred whiledeleting the usernameaccount because the accountdoes not exist.

This error might occur when you attempt todelete a user. This error might also occur ifyou attempt to change the password for auser. To fix the problem, ensure that:

v The user was created on the resource.

v The user was not deleted from theresource.

v If the user does not exist on the resource,create the user on the resource and thenschedule a reconciliation. See the onlinehelp for information about scheduling areconciliation.

CTGIMT009E The account usernamecannot be modified becauseit does not exist.

This error might occur when you attempt tomodify a user. This error might also occur ifyou attempt to change the password for auser. To fix the problem, ensure that:



v If the user does not exist on the resource,create the user on the resource and thenschedule a reconciliation. See the onlinehelp for information about scheduling areconciliation.

Table 6. General warning and error messages and actions

Message Action

LoadConnectors:

java.lang.NoClassDefFoundError:psft/pt8/joa/JOAException

The psjoa.jar file is missing. Verify that thefile exists in the ITDI_HOME/jars/3rdParty/IBM directory.

InitConnectors:

java.lang.Exception: Unable toGetComponent Interface ABC_XYZ

The PeopleSoft Component Interface classesare unavailable. Perform the following steps:

v Verify that the CompIntfc.jar file (whichcontains the ENROLE_AGENTComponent Interface project classes) ispresent in the jars subdirectory of theITDI_HOME directory.

v Verify that the CompIntfc.jar file containsclasses for the required ENROLE_AGENTComponent Interface project.

v If necessary, add the path of the jarssubdirectory to the ITDI CLASSPATHvariable.


Table 6. General warning and error messages and actions (continued)

Message Action

v A system error occurred while adding anaccount. The account was not added.

v A system error occurred while modifyingan account. The account was not changed.

v A system error occurred while deleting anaccount. The account was not deleted.

v The search failed due to a system error.

To fix this problem, ensure that:

v The CompIntfc.jar and psjoa.jar arepresent appropriate locations of the TivoliDirectory Integrator.

v The ENROLE_AGENT ComponentInterface project is deployed on thePeopleSoft resource.

v The network connection is not slowbetween the IBM Security IdentityManager and the Tivoli DirectoryIntegrator or the Tivoli DirectoryIntegrator and the managed resource.

v The account was added but someattributes failed.

v The account was modified but someattributes failed.

v The account was deleted successfully, butadditional steps failed.

The account was created, modified, ordeleted, but some of the specified attributesin the request were not set. See the list ofattributes that failed and the error messagethat explains why the attribute failed.Correct the errors associated with eachattribute and perform the action againNote: You might want to review thedocumentation for the operating system ofthe managed resource to determine thecorrect values for some attributes..

v The user cannot be modified because itdoes not exist.

v An error occurred while deleting theaccount because the account does notexist.

This error might occur when you attempt tomodify or delete a user. This error mightalso occur if you attempt to change thepassword for a user. To fix the problem,ensure that:

v The location specified for the managedresource is correct.



If the user does not exist on the resource,create the user on the resource and thenschedule reconciliation. See the online helpfor information about schedulingreconciliation.

v Search filter error

v Invalid search filter

The filter specified in the search request isnot correct. Specify the correct filter andperform the search action again.

The application could not establish aconnection to hostname.

Ensure that SSH is enabled on the managedresource.

Adapter profile is not displayed in the userinterface after installing the profile.

You must stop and restart the TivoliDirectory Integrator server, or wait until thecache times out (up to 10 minutes) for IBMSecurity Identity Manager to refresh the listof attribute names.

Chapter 5. Troubleshooting of the adapter errors 31


Chapter 6. Adapter upgrade

Upgrading the adapter involves tasks, such as upgrading the connector, dispatcherand the existing adapter profile.

To verify the required version of these adapter components, see the adapter releasenotes.

Connector upgradeThe new adapter package might require you to upgrade the connector.

Before you upgrade the connector, verify the version of the connector.v If the connector version mentioned in the release notes is later than the existing

version on your workstation, install the connector.v If the connector version mentioned in the release notes is the same or earlier

than the existing version, do not install the connector.

Note: Stop the dispatcher service before the upgrading the connector and start itagain after the upgrade is complete.

Dispatcher upgradeThe new adapter package might require you to upgrade the Dispatcher.

Before you upgrade the dispatcher, verify the version of the dispatcher.v If the dispatcher version mentioned in the release notes is later than the existing

version on your workstation, install the dispatcher.v If the dispatcher version mentioned in the release notes is the same or earlier

than the existing version, do not install the dispatcher.

Note: The dispatcher installer stops the dispatcher service before the upgrade andrestarts it after the upgrade is complete.

Upgrade of the existing adapter profileRead the adapter release notes for any specific instructions before importing a newadapter profile on IBM Security Identity Manager.

See “Importing the adapter profile into the IBM Security Identity Manager server”on page 16.

Note: Restart the dispatcher service after importing the profile. Restarting thedispatcher clears the assembly lines cache and ensures that the dispatcher runs theassembly lines from the updated adapter profile.



Chapter 7. Uninstallation of the PeopleTools adapter

Before you uninstall the adapter, inform your users in advance that the adapter isunavailable.

If you take the server offline, completed adapter requests might not be recoveredwhen the server is back online.

Uninstalling the adapter from the IBM Tivoli Directory Integrator serverThe adapter installation process also installs the Tivoli Directory IntegratorPeopleSoft connector. Therefore, you must remove the PeopleSoftConnector.jarfile from the IBM Tivoli Directory Integrator.

Procedure1. Stop the Dispatcher service.2. Remove the PeopleSoftConnector.jar file from the ITDI_HOME/jars/connectors

directory.3. Start the Dispatcher service.

Removal of the adapter profile from the IBM Security Identity Managerserver

Before you remove the adapter profile, make sure that no objects exist on yourIBM Security Identity Manager server that reference the adapter profile.

Examples of objects on the IBM Security Identity Manager server that can referencethe adapter profile are:v Adapter service instancesv Policies referencing an adapter instance or the profilev Accounts

For specific information about removing the adapter profile, see the online help orthe IBM Security Identity Manager product documentation.



Chapter 8. Adapter reinstallation

There are no special considerations for reinstalling the adapter. You do not need toremove the adapter before reinstalling.

For more information, see Chapter 6, “Adapter upgrade,” on page 33.



Appendix A. Adapter attributes

The PeopleTools Adapter supports a standard set of attributes for user information.

The mandatory attributes for creating an account are:v User IDv Symbolic ID

Table 7. Attributes, OIDs, descriptions and corresponding PeopleTools attributes

Attribute name Description Required PeopleTools attribute

ErUid User ID Yes User ID

ErPassword Password for the userID

No Password

ErAccountStatus Status of the account(suspended or restored)

No Account Locked Out

ErLastAaccessDate Last Access Date No The attribute is availablein the PeopleSoftdatabase, however, it isnot available in thePeopleSoft Pure InternetArchitecture (PIA) userinterface. For moreinformation, see theLASTSIGNONDTTMcolumn in thePSOPRDEFN table of thePeopleSoft database.

erpt84xsymbid Symbolic ID Yes Symbolic ID

erpt84xdescription Description No Description

erpt84xusersupr User Supervisor No Supervising User ID

erpt84xaltid Alternate User ID No Alternate User ID

erpt84xcurrcode Currency Code No Currency Code

erpt84xemailadd Email Addresses No Edit Email Addresses

erpt84xenddate To Date No To Date

erpt84xlangcode Language Code No Language Code

erpt84xmultilang Multi LanguageEnabled?

No Multiple LanguageNote: The attribute isavailable in thePeopleSoft database,however, it is notavailable in thePeopleSoft Pure InternetArchitecture (PIA) userinterface.

erpt84xhomepagepl Navigator Homepage No Navigator Homepage

erpt84xopraliastype ID Types and Values No ID Type

erpt84xprimarypl Primary No Primary

erpt84xprofilepl Process Profile No Process Profile


Table 7. Attributes, OIDs, descriptions and corresponding PeopleTools attributes (continued)

Attribute name Description Required PeopleTools attribute

erpt84xrole Roles No Roles

erpt84xrowpl Row Security No Row Security

erpt84xstartdate Effective Date No From Date

erpt84xexpertentry Enable Expert Entry? No Enable Expert Entry

erpt84xemailuser Routing- Email User No Email User

erpt84xworklistuser Routing- Worklist User No Worklist user

Attributes by adapter actionsThe following lists are adapter actions by their functional transaction group.

The lists include more information about required and optional attributes sent tothe adapter to complete that action.

System Login AddA System Login Add is a request to create a new user account with the specifiedattributes.

Table 8. Add request attributes for AIX®, HPUX, Linux, and Solaris

Required attribute Optional attribute

erUid

erpt84xsymbid

All other supported attributes

System Login ChangeA System Login Change is a request to change one or more attributes for thespecified users.

Table 9. Change request attributes


erUidAll other supported attributes

System Login DeleteA System Login Delete is a request to remove the specified user from the directory.

Table 10. Delete request attributes


erUid None

System Login SuspendA System Login Suspend is a request to disable a user account. The user is neitherremoved nor are their attributes modified.


Table 11. Suspend request attributes


erUid

erAccountStatus

None

System Login RestoreA System Login Restore is a request to activate a user account that was previouslysuspended. After an account is restored, the user can access the system with thesame attributes as those before the Suspend function was called.

Table 12. Restore request attributes


erUid

erAccountStatus

erPassword

None

System Change PasswordA System Change Password is a request to change the password of a user.

Table 13. System change password request attributes


erUid

erPassword

None

TestThe following table identifies attributes needed to test the connection.

Table 14. Test attributes


None None

ReconciliationThe Reconciliation request synchronizes user account information between IBMSecurity Identity Manager and the adapter.

Table 15. Reconciliation request attributes


None All other supported attributes

Appendix A. Adapter attributes 41


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 46v “Contacting IBM Support” on page 46

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 47

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 53

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 x, 49account

creation 18management automation 1password requirements

schema.dsml file 25service.def file 25

required privileges 18restoration 25service, information required 18

adapteraccount 18account management automation 1actions 40attributes 39configuration 23features 1installation

connector 9dispatcher requirement 9home directory 7overview 1solution directory 7troubleshooting errors 27verifying 25warnings 27worksheet 7

overview 1profile

customizing 23import 16removal 35upgrades 33verifying 17

reinstallation 37supported configurations

multiple server 2single server 2

uninstallation 35upgrade 33

application designerPRG_USR_PROFILE record

modification 10two-tier mode 11

architectureadapter profile 1connector 1dispatcher 1

attributes 40mandatory 39reconciliation 41standard 39system login

add 40change 40change password 41delete 40restore 41suspend 41

testing connection 41

automation, account management 1

Cchanging

system login 40system password 41

CompIntfc.jar file 13component

adapter profile 1connector 1dispatcher 1interfaces 11, 13permissions list 11security 11

configuringadapter 23options 23

connections, testing 41connector upgrades 33customizing adapter profiles 23

Ddeleting system login 40dispatcher

architecture 1installation, verifying 9upgrades 33

download, software 7

Eeducation xerror messages 29

IIBM

Software Support xSupport Assistant x

IBM Support Assistant 46ID type subforms 17installation

adapter 9adapter profile 16dispatcher

requirement 9verification 9

first steps afteradapter configuration 23adapter verification 23language pack installation 23SSL setup 23

language pack 25roadmap 5steps 5verification 15

adapter 25

installation (continued)worksheet

home directory 7solution directory 7

interfaces, component 11ISA 46ISIM_HOME definition 43ITDI_HOME definition 43

JJAR files

CompIntfc.jar 12, 13JDBC type 4 driver 14JDBC type 4 driver JAR file 12psft.jar 12psjoa.jar 12, 14resource-specific 12

JDBC type 4 drivers 14

Kknowledge bases 45

Llanguage pack

installation 25same for adapters and server 25

logs, trace.log file 16

Mmessages

error 29warning 29

MS-DOS ASCII characters 24

Nnotices 51

Oonline

publications ixterminology ix

operating system prerequisites 6overview 1

Ppassword requirements

schema.dsml file 25service.def file 25

PeopleSoftConnector.jar file,removing 35


PeopleToolsadapter 12application designer

PRG_USR_PROFILE recordmodification 10

two-tier mode 11project

8.50 118.51 118.52 11

permissions list, component 11post-installation steps

adapter configuration 23adapter verification 23language pack installation 23SSL setup 23

preinstallation roadmap 5preparation 5PRG_USR_PROFILE record

modification 10problem-determination xprofile

editing on UNIX or Linux 24removal 35upgrades 33verification 17

project security 11projects, PeopleTools 11psjoa.jar 14publication ixpublications

accessing online ixlist of ix

Rreconciling 41records, PRG_USR_PROFILE 10reinstallation, adapter 37required privileges, account 18restoring

accounts, password requirements 25system login 41

roadmapsinstallation 5preinstallation 5

Ssecurity for components 11service

restart 15start 15stop 15

service, creating 18software

download 7requirements 6website 7

subforms 17support contact information 46supported configurations

adaptermultiple server 2single server 2

supported configurations (continued)overview

multiple server 2single server 2

suspending system login 41

Tterminology ixtesting connections 41Tivoli Directory Integrator connector 1trace.log file 16training xtroubleshooting

contacting support 46error messages 29getting fixes 46identifying problems 27searching knowledge bases 45support website xtechniques 27warning messages 29

Uuninstallation

adapter 35advance notice to users 35PeopleSoftConnector.jar file 35

upgradesadapter profile 33connector 33dispatcher 33

user account management tasks 1

Vverification

installation 15, 25software

prerequisites 6requirements 6

system prerequisites 6system requirements 6

vi command 24

Wwarning messages 29


��

Printed in USA

SC27-4405-02

Documents

PeopleToolsAdapter Installation and Configuration Guide · 2016-03-10 · PeopleToolsAdapter Installation and Configuration Guide SC27-4405-02. Note Before using this information