· Title: IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide Author: IBM Created Date: 2/7/2014 1:43:01 AM

IBM Security Identity ManagerVersion 6.0

Remedy AR System AdapterInstallation and Configuration Guide

SC27-4412-00

��

IBM Security Identity ManagerVersion 6.0

Remedy AR System AdapterInstallation and Configuration Guide

SC27-4412-00

��

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

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, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

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

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

Preface . . . . . . . . . . . . . . . ixPreface . . . . . . . . . . . . . . . . ix

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

Chapter 1. Remedy AR System AdapterInstallation and Configuration Guide . . 1Overview of the adapter . . . . . . . . . . 1

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

Chapter 2. Adapter installation planning 5Preinstallation roadmap . . . . . . . . . . 5Installation roadmap. . . . . . . . . . . . 5Prerequisites . . . . . . . . . . . . . . 5Installation worksheet for the adapter . . . . . . 6Software download . . . . . . . . . . . . 7

Chapter 3. Adapter installation andconfiguration . . . . . . . . . . . . 9Copies of the Remedy AR System files. . . . . . 9

Placement of the Remedy AR System 7.5 libraryfiles . . . . . . . . . . . . . . . . 9Placement of the Remedy AR System 7.6.04library files . . . . . . . . . . . . . 11

Dispatcher installation verification . . . . . . . 13Installing the adapter . . . . . . . . . . . 14Starting, stopping, and restarting the Dispatcherservice . . . . . . . . . . . . . . . . 14Verifying the adapter installation . . . . . . . 15Start, stop, and restart of the adapter service . . . 15Importing the adapter profile into the IBM SecurityIdentity Manager server . . . . . . . . . . 16Adapter profile installation verification . . . . . 17Adapter user account creation . . . . . . . . 17Creating a service . . . . . . . . . . . . 17

Chapter 4. First steps after installation 21Adapter configuration . . . . . . . . . . . 21

Customizing the adapter profile . . . . . . 21Editing adapter profiles on the UNIX or LINUXoperating system . . . . . . . . . . . 22

Password management for account restoration . . 23Language pack installation . . . . . . . . . 23Verifying that the adapter is working correctly . . 23

Chapter 5. Troubleshooting the adaptererrors . . . . . . . . . . . . . . . 25Techniques for troubleshooting problems . . . . 25Warning and error messages. . . . . . . . . 27

Chapter 6. Adapter upgrade. . . . . . 31Connector upgrade . . . . . . . . . . . . 31Existing adapter profile upgrade . . . . . . . 31

Chapter 7. Adapter uninstallation . . . 33Uninstalling the adapter from the Tivoli DirectoryIntegrator server. . . . . . . . . . . . . 33Adapter profile removal from the IBM SecurityIdentity Manager server . . . . . . . . . . 33

Chapter 8. Adapter reinstallation . . . 35

Appendix A. Adapter attributes . . . . 37

Appendix B. Installing the adapter on az/OS operating system . . . . . . . . 39Installing the Tivoli Directory Integrator RTCconnector . . . . . . . . . . . . . . . 39

Appendix C. Definitions for ITDI_HOMEand ISIM_HOME directories . . . . . . 41

Appendix D. Support information . . . 43Searching knowledge bases . . . . . . . . . 43Obtaining a product fix . . . . . . . . . . 44Contacting IBM Support . . . . . . . . . . 44

Appendix E. Accessibility features forIBM Security Identity Manager . . . . 47

Notices . . . . . . . . . . . . . . 49

Index . . . . . . . . . . . . . . . 53

© Copyright IBM Corp. 2012, 2013 iii

iv IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide

Figures

1. The architecture of the Remedy AR SystemAdapter . . . . . . . . . . . . . . 2

2. Example of a single server configuration . . . 23. Example of multiple server configuration 3

© Copyright IBM Corp. 2012, 2013 v

vi IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide

Tables

1. Preinstallation road map . . . . . . . . 52. Installation roadmap . . . . . . . . . . 53. Prerequisites to install the adapter . . . . . 64. Required information to install the adapter 65. Files needed for Windows operating systems 106. Files needed for AIX operating systems 107. Files needed for HPUX operating systems 118. Files needed for Linux or Solaris operating

systems . . . . . . . . . . . . . . 11

9. Files needed for Windows operating systems 1210. Files needed for AIX operating systems 1211. Files needed for HPUX operating systems 1312. Files needed for Linux or Solaris operating

systems . . . . . . . . . . . . . . 1313. Adapter components . . . . . . . . . 1514. Warnings, error messages, and corrective

action . . . . . . . . . . . . . . 2715. Account form attributes and their details 37

© Copyright IBM Corp. 2012, 2013 vii

viii IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide

Preface

Preface

About this publication

The Remedy AR System Adapter Installation and Configuration Guide provides thebasic information that you can use to install and configure the IBM Remedy ARSystem Adapter. The adapter enables connectivity between the IBM® SecurityIdentity Manager server and the Remedy AR System server.

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://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.isim.doc_6.0/ic-homepage.htm).

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://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.isim.doc_6.0/ic-homepage.htm) displays the welcome page and navigation 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, 2013 ix

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.isim.doc_6.0/ic-homepage.htm





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 D, “Support information,” on page 43 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: Remedy AR System Adapter Installation and Configuration Guide

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

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

Chapter 1. Remedy AR System Adapter Installation andConfiguration Guide

This installation guide provides the basic information that you use to install andconfigure the Remedy AR System Adapter. The adapter enables connectivitybetween the IBM Security Identity Manager server and the managed resource.

Overview of the adapterThe Remedy AR System Adapter enables communication between the IBM SecurityIdentity Manager server and the Remedy AR System 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 various user account administrative tasks.

The adapter automates the following tasks:v Reconciling user accounts and other support datav Adding user accountsv Modifying user account attributesv Modifying user account passwordsv Deleting user accounts

Note: The Remedy AR System server does not support the Suspend and Restoretasks, therefore, the adapter does not automate these tasks.

Architecture of the adapterYou must install the several components for the adapter to work correctly.

You must install the following components for the adapter:v The Dispatcherv The RemedyARSConnector connectorv The IBM Security Identity Manager adapter profile

You need to 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, 2013 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 Tivoli Directory Integrator serverv The managed resourcev The adapter

The adapter must reside directly on the server that runs 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 Remedy AR System Adapter on oneserver to establish communication with the Remedy AR System server.

The Remedy AR System 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, the Remedy AR System Adapter, and the Remedy ARSystem server are installed on different servers.

Install the Tivoli Directory Integrator server, and the Remedy AR System Adapteron the same server as described in Figure 3 on page 3.

RMI callsIBM SecurityIdentityManagerServer

DispatcherService(an instanceof the IBMTivoliDirectoryIntegrator)

Adapterresource

Figure 1. The architecture of the Remedy AR System Adapter

IBM SecurityIdentity Manager Server

Tivoli DirectoryIntegrator Server

Adapter

Managed

resource

Figure 2. Example of a single server configuration

2 IBM Security Identity Manager: Remedy AR System 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 multiple server configuration

Chapter 1. Remedy AR System Adapter Installation and Configuration Guide 3


Chapter 2. Adapter installation planning

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 by doing thetasks that are listed in the preinstallation roadmap.

Table 1. Preinstallation road map

Task For more information

Obtain the installation software. Download the software from PassportAdvantage® website. See “Softwaredownload” on page 7.

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

See “Prerequisites.”

Obtain the necessary information for theinstallation and configuration.

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

Installation roadmapTo install the adapter, complete the tasks that are listed in the installation roadmap.

Table 2. Installation roadmap

Task For more information

Verify the Dispatcher installation. See “Dispatcher installation verification” onpage 13.

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

Verify the installation. See “Verifying the adapter installation” onpage 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 creation” on page17.

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

Configure the adapter. See “Adapter configuration” on page 21.

PrerequisitesVerify that your environment meets all the prerequisites before you install 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 Tivoli DirectoryIntegrator 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

Remedy AR System server Version 7.5

Version 7.6.04

System Administrator AuthorityTo complete the adapter installation procedure,you must have system administrator authority.

Tivoli Directory Integrator adapterssolution directory

A Tivoli Directory Integrator adapters solutiondirectory is a Tivoli Directory Integrator workdirectory for IBM Security Identity Manageradapters. See the Dispatcher Installation andConfiguration Guide.

Remedy AR System Jar files See “Copies of the Remedy AR System files” onpage 9.

For information about the prerequisites and supported operating systems for TivoliDirectory Integrator, see the IBM Tivoli Directory Integrator Administrator Guide.

Installation worksheet for the adapterTake note of the required directories before you install the adapter.

Table 4. Required information to install the adapter

Required information Description Value

Tivoli DirectoryIntegrator HomeDirectory

The ITDI_HOME directory containsthe jars/connectors subdirectory.This subdirectory contains adapterJAR files.

If Tivoli DirectoryIntegrator is automaticallyinstalled with your IBMSecurity Identity Managerproduct, the defaultdirectory path for TivoliDirectory Integrator is asfollows:

Windows:

v for version 7.1:

drive\ProgramFiles\IBM\TDI\V7.1

UNIX:

v for version 7.1:

/opt/IBM/TDI/V7.10


Table 4. Required information to install the adapter (continued)

Required information Description Value

Adapters solutiondirectory

This directory is the defaultdirectory. When you install thedispatcher, the dispatcher promptsyou to specify a file path for theadapter solution directory. For moreinformation about the adaptersolution directory, see the DispatcherInstallation and Configuration 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 downloadDownload 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. Adapter installation planning 7

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


Chapter 3. Adapter installation and configuration

All the adapters that are based on Tivoli Directory Integrator require theDispatcher for the adapters to function correctly.

If the Dispatcher is installed from a previous installation, do not reinstall it unlessthere is an upgrade to the Dispatcher. See “Dispatcher installation verification” onpage 13.

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.

Copies of the Remedy AR System filesBefore you can install the adapter, you must copy the Remedy AR System JAR andC API files to the specified directories.

The following tables list the Remedy AR System JAR files that are required for theinstallation of the adapter. The tables also provide the location of the JAR files inthe Remedy AR System server installation directory. You must copy the JAR filesfrom the workstation where the Remedy AR System server is installed to theITDI_HOME\jvm\jre\lib\ext directory.

Select the files based on your operating system and your version of the RemedyAR System server.

Note: You must install the API package during the Remedy AR System serverinstallation. This installation creates the JAR files and C API library files that youmust copy from Remedy AR System server workstation to the Tivoli DirectoryIntegrator directories. If the API package is not installed, you must upgrade theRemedy AR System server to install only the API package. For more informationabout API package installation, see the Remedy AR System guide Installing.

Placement of the Remedy AR System 7.5 library filesIf you are managing a Remedy 7.5 server, you must copy the following files fromthe Remedy 7.5 server installation directory. You must place these files in the TivoliDirectory Integrator setup before you install the adapter. After you copy the files,the dispatcher must be restarted.

The following tables list the files you need to copy for your operating system.


Table 5. Files needed for Windows operating systems.

Location on the RemedyARS server File name

Target location in the TivoliDirectory Integratorenvironment

C:\Program Files\BMCSoftware\ARSystem\Arserver\api\lib

arapi75.jararapiext75.jararapi75.dllarjni75.dllarrpc75.dllarutl75.dllarxmlutil75.dll

ITDI_HOME\jvm\jre\lib\ext

ITDI_HOME\jars\3rdparty\others

log4j-1.2.15.jar

C:\Program Files\BMCSoftware\ARSystem\midtier\WEB-INF\lib

arutil75.jararutiljni75.dll

C:\Program Files\BMCSoftware\ARSystem

icudt32.dllicuinbmc32.dllicuucbmc32.dllXalan-Cbmc_1_10.dllXalanMessagesbmc_1_10.dllxerces-cbmc_2_8.dllxerces-depdombmc_2_8.dll

ITDI_HOME\libs

Note: You must add the TDI_HOME\libs folder to the library path for the UNIXplatforms. In these example paths, /opt/IBM/TDI/V7.1 represents the TivoliDirectory Integrator 7.1 installation directory. Perform the action for your operatingsystem.

AIX platformsSet the environment variable LIBPATH to /opt/IBM/TDI/V7.1/libs.

HPUX platformsSet the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.1/libs.

Linux or Solaris platformsSet the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.1/libs.

Table 6. Files needed for AIX operating systems.




arapi75.jararapiext75.jarlibar.alibarjni75.a



log4j-1.2.15.jar


arutil75.jararutiljni75.a

C:\Program Files\BMCSoftware\ARSystem\Arserver\bin

libicudatabmc32.alibicui18nbmc32.alibicuiobmc32.alibicuucbmc32.alibxalan-cbmc.alibxalanMsg.alibxerces-cbmc.a

ITDI_HOME\libs


Table 7. Files needed for HPUX operating systems.




arapi75.jararapiext75.jarlibar.sllibarjni75.sl



log4j-1.2.15.jar


arutil75.jararutiljni75.sl


libicudatabmc.sl.32libicui18nbmc.sl.32libicuiobmc.sl.32libicuucbmc.sl.32libxalan-cbmc.sllibxalanMsgbmc.sllibxerces-cbmc.sl

ITDI_HOME\libs

Table 8. Files needed for Linux or Solaris operating systems.




arapi75.jararapiext75.jarlibar.solibarjni75.so



log4j-1.2.15.jar


arutil75.jararutiljni75.so


libicudatabmc.so.32libicui18nbmc.so.32libicuiobmc.so.32libicuucbmc.so.32libxalan-cbmc.solibxalanMsgbmc.solibxerces-cbmc.so

ITDI_HOME\libs

Placement of the Remedy AR System 7.6.04 library filesIf you are managing a Remedy 7.6.04 server, you must copy the following filesfrom the Remedy 7.6.04 server installation directory. You must place these files inthe Tivoli Directory Integrator setup before you install the adapter. After you copythe files, the dispatcher must be restarted.

The following tables list the files you need to copy for your operating system.

Chapter 3. Adapter installation and configuration 11

Table 9. Files needed for Windows operating systems.




arapi7604_build002.jararapiext7604_build002.jararapi7604_build002.dllarjni7604_build002.dllarrpc7604_build002.dllarutl7604_build002.dllarxmlutil7604_build002.dll



log4j-1.2.15.jar


arutil7604_build002.jar

C:\Program Files\BMCSoftware\ARSystem

icudt32.dllicuinbmc32.dllicuucbmc32.dllXalan-Cbmc_1_10.dllXalanMessagesbmc_1_10.dllxerces-cbmc_2_8.dllxerces-depdombmc_2_8.dll

ITDI_HOME\libs

Note: You must add the TDI_HOME\libs folder to the library path for the UNIXplatforms. In these example paths, /opt/IBM/TDI/V7.1 represents the TivoliDirectory Integrator 7.1 installation directory. Perform the action for your operatingsystem.

AIX platformsSet the environment variable LIBPATH to /opt/IBM/TDI/V7.1/libs.

HPUX platformsSet the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.1/libs.

Linux or Solaris platformsSet the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.1/libs.

Table 10. Files needed for AIX operating systems.




arapi7604_build002.jararapiext7604_build002.jarlibar.alibarjni7604_build002.a



log4j-1.2.15.jar




libicudatabmc32.alibicui18nbmc32.alibicuiobmc32.alibicuucbmc32.alibxalan-cbmc.alibxalanMsgbmc.alibxerces-cbmc.a

ITDI_HOME\libs


Table 11. Files needed for HPUX operating systems.




arapi7604_build002.jararapiext7604_build002.jarlibar.sllibarjni7604_build002.sl



log4j-1.2.15.jar




libicudatabmc.sl.32libicui18nbmc.sl.32libicuiobmc.sl.32libicuucbmc.sl.32libxalan-cbmc.sllibxalanMsgbmc.sllibxerces-cbmc.sl

ITDI_HOME\libs

Table 12. Files needed for Linux or Solaris operating systems.




arapi7604_build002.jararapiext7604_build002.jarlibar.solibarjni7604_build002.so



log4j-1.2.15.jar




libicudatabmc.so.32libicui18nbmc.so.32libicuiobmc.so.32libicuucbmc.so.32libxalan-cbmc.solibxalanMsgbmc.solibxerces-cbmc.so

ITDI_HOME\libs

Dispatcher installation verificationIf this installation is for the first adapter that is based on Tivoli DirectoryIntegrator, 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.


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

Installing the adapterUse this task to install the adapter software.

Before you begin

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

on page 5.v Obtain a copy of the installation software. See “Software download” on page 7.v Obtain system administrator authority. See “Prerequisites” on page 5.

About this task

The adapter uses the Tivoli Directory Integrator RemedyARSConnector. Thisconnector is not available with the base Tivoli Directory Integrator product. Theadapter installation involves the Tivoli Directory Integrator Remedy ARS Systemconnector installation. After installing the Dispatcher, you must install theconnector for the adapter. The connector is included in a separate installerprovided with the adapter package. Before you install the adapter, make sure thatthe Dispatcher is already installed. See “Dispatcher installation verification” onpage 13.

Note: If you are running on a 64-bit operating system, you must use the TivoliDirectory Integrator-supplied JVM. The JVM is in ITDI_HOME/jvm/jre/bin/, whereITDI_HOME is the directory where Tivoli Directory Integrator 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 RemedyARSConnector.jar file to the ITDI_HOME/jars/connectors

directory.4. Restart the IBM Security Identity Manager adapter (Dispatcher) service.

What to do next

After you finish the adapter installation, do the following tasks:v Verify that the installation completed successfully. See “Verifying the adapter

installation” on page 15.v Import the adapter profile. See “Importing the adapter profile into the IBM

Security Identity Manager server” on page 16.v Create a user account for the adapter on IBM Security Identity Manager. See

“Adapter user account creation” on page 17.

Starting, stopping, and restarting the Dispatcher serviceThis section provides you the detail information to start, stop, and restart theDispatcher service using the command-line option.


About this task

If the dispatcher service is running before the adapter installation or uninstallationprocess begins, then the adapter installation or uninstallation process stops thedispatcher service. The process restarts the dispatcher service after the completionof the adapter installation or uninstallation. However, the process does not restartthe dispatcher service after the completion of the adapter installation oruninstallation if the service is not running before the process begins.

If you want to start the dispatcher service after the adapter installation oruninstallation, you must:v Use the following command-line option when you run the adapter installer:

FORCE_DISPATCHER_SERVICE_START_ONINSTALL=yes

For example:RTCAdapterInstall_70.exe -DFORCE_DISPATCHER_SERVICE_START_ONINSTALL=yes

v Use the following command-line option when you run the adapter uninstaller:FORCE_DISPATCHER_SERVICE_START_ONUNINSTALL=yes

For example:RTCAdapterUninstall.exe -DFORCE_DISPATCHER_SERVICE_START_ONUNINSTALL=yes

Verifying the adapter installationAfter you install the adapter, the RemedyARSConnector.jar file is created in theITDI_HOME\jars\connectors directory.

About this task

The following table lists the adapter components that are created on the TivoliDirectory Integrator server after you install the adapter.

Table 13. Adapter components

Directory Adapter component

ITDI_Home\jars\connectors RemedyARSConnector.jar

adapter solution directory arsys_api.xml

Review the installer log file, RemedyARS70Adapter_Installer.log that is located inthe adapter installer directory for any errors.

If this installation is to upgrade a connector, send a request from IBM SecurityIdentity Manager and verify that the version number in the ibmdi.log. Thatnumber must match the version of the connector that you installed. The ibmdi.logfile is at ITDI_Home\adapter solution directory\logs.

Start, stop, and restart of the 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

Use this task to create a service on the IBM Security Identity Manager server andestablish communication with the adapter

Before you begin

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 JAR file includes all the files that are required to define the adapter schema,account form, service form, and profile properties. You can extract the files fromthe JAR file to modify the necessary files and package the JAR file with theupdated files.

Before you begin to import the adapter profile, verify that the following conditionsare 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

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 IBMSecurity Identity Manager server and establish communication with the adapter.

To import the adapter profile, perform the following steps:

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 JAR file in the Service Definition File field by

performing one of the following tasks:v Type the complete location of where the file is stored.v Use Browse to navigate to the file.

5. Click OK.

Note: When you import the adapter profile and if you receive an error relatedto the schema, see the trace.log file for information about the error. Thetrace.log file location is specified by using the handler.file.fileDir propertydefined in the IBM Security Identity Manager enRoleLogging.properties file.The enRoleLogging.properties file is installed in the ITIM_HOME\data directory.


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

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

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 account creationYou must create a user account for the adapter on the managed resource. Providethe account information when you create a service for the adapter on IBM SecurityIdentity Manager.

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 Manager Adapter service on the Tivoli DirectoryIntegrator server must be restarted.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 Remedy AR System 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.

Tivoli Directory Integrator URLOptional: 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 theRMI Dispatcher. The default URL isrmi://localhost:1099/ITDIDispatcher

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

Host NameSpecify the IP address or the host name of the managedresource.

Note: Enclose the IPv6 address in brackets. An example of avalid IPv6 address format is:http://[fedc:ba98:7654:3210:fedc:ba98:7654:3210]

TCP PortSpecify the TCP port number of the managed resource.

User NameSpecify a Login ID of the Remedy AR System server that hasadministrator permissions.

PasswordSpecify a password for the Remedy AR System server user thathas administrator permissions.

Allow Unqualified SearchesSelect Yes for the adapter to perform an Unqualified Search onthe Remedy AR System server.

Recon In BatchClick the check box to reconcile the entries in batches.

On the Dispatcher Attributes tab:

Disable AL CachingClick the check box to disable the assembly line (test, add,modify, delete) caching in the dispatcher for the service.

AL FileSystem PathSpecify the file path from where the dispatcher loads theassembly 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: drive:\Program


Files\IBM\TDI\V7.0\profiles or you can specify the followingfile path to load the assembly lines from the profiles directoryof the UNIX and Linux operating:/opt/IBM/TDI/V7.0/profiles

Max Connection CountSpecify the maximum number of assembly lines that thedispatcher can run simultaneously for the service. For example,enter 10 when you want the dispatcher to run maximum 10assembly lines simultaneously for the service. If you enter 0 inthe Max Connection Count field, the dispatcher does not limitthe number of assembly lines that run simultaneously for theservice.

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 do several other tasks. The tasks includeconfiguring the adapter, setting up SSL, installing the language pack, and verifyingthe adapter works correctly.

Adapter configurationYou can use these configuration options for the Remedy AR System Adapter.v “Customizing the adapter profile”v “Editing adapter profiles on the UNIX or LINUX operating system” on page 22

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 Remedy AR SystemAdapter JAR file. You might customize the adapter profile to change the accountform or the service form. You can also change the labels on the forms by using theForm Designer or CustomLabels.properties. Each adapter has aCustomLabels.properties file for that adapter.

About this task

Each adapter has a CustomLabels.properties file for that adapter.

The JAR file is included in the Remedy AR System Adapter compressed file thatyou downloaded from the IBM website.

Note: You cannot modify the schema for this adapter. Attributes cannot be addedto or deleted from the schema.

RemedyARSProfile.jarThe following files are included in the JAR file:v CustomLabels.propertiesv schema.dsmlv service.defv erRmdArsAccount.xmlv erRmdArsRMIService.xmlv RmdArsSearch.xmlv RmdArsAdd.xmlv RmdArsModify.xmlv RmdArsTest.xml


v RmdArsAdapter.xmlv RmdArsDelete.xml

To edit the JAR file, log on to the workstation where the Remedy AR SystemAdapter is installed:

Procedure1. On the Start menu, click Programs > Accessories > Command Prompt.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 Remedy AR SystemAdapter profile. Type the name of the JAR file for your operating system.cd c:\temp#jar -xvf RemedyARSProfile.jar

The jar command extracts the files into the 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 \temp directory byrunning the following commands:cd c:\temp#jar -cvf RemedyARSProfile.jar RTCProfile

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 Remedy AR System Adapter service. See “Start, stop, and

restart of the adapter service” on page 15 for information about stopping andstarting the Remedy AR System 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 for account restorationHow 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 Remedy AR System Adapter to require a new password when theaccount is restored, if your company has a business process in place that dictatesthat the account restoration process must be accompanied by resetting thepassword.

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 installationThe adapters use the same language package as IBM Security Identity Manager.

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

Verifying that the 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 23

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 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 D, “Support information,”on page 43.

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.

The following table contains warnings or errors that might be displayed on theuser interface if the adapter is installed on your workstation.

Table 14. Warnings, error messages, and corrective action

Warning or error message Corrective action

ERROR (307): Required field (without a default)not specified; 101. ERROR (307): Required field(without a default) not specified; 8.

Specify the following required attributes on the account form:

v Login Name

v Full Name

ERROR (382): The values for this entry violate aunique index that is defined for this form.

Provide a unique login name for the Login Name attribute onthe account form when you perform a user add operation.

(52) The field is a core system field and cannot bechanged.

An attempt was made to modify the contents of one of thefollowing core system fields:

v Request ID

v Create Date

v Last Modified By

v Last Modified Date

Do not modify these fields because the Remedy AR Systemserver sets values for these fields.

ERROR (326): Required field cannot be reset to aNULL value; 2.

An attempt was made to delete the value specified in theCreator field.

The Remedy AR Systemserver sets the default for this field;however, if you specify a different value, ensure that you:

v Do not set the value of the field to NULL.

v Specify a string value (for example, Demo) or analphanumeric character (for example, av234.)

ERROR (417): Cannot translate a group name ineither the Group List or Assignee Group field; 104.

This error occurs when an incorrect value is specified for theGroup List attribute during the user add operation.

Perform the following steps to set the Group List attribute:

1. Ensure that the group exists on the Remedy AR Systemserver by performing a support data reconciliationoperation.

2. Select the group from the updated list available for theGroup List attribute.

Chapter 5. Troubleshooting the adapter errors 27

Table 14. Warnings, error messages, and corrective action (continued)


ERROR (30): You are already at the limit of thenumber of fixed user licenses of the following type;Full Text : (0).

An attempt was made to create a user and assign a fixedlicense to the user. You reached the limit of the number offixed user licenses. Add the user with a read, none, or floatinglicense, however, not a fixed license.

The License Type attribute is replaced by write, full text, orflashboards to indicate the type of fixed license.

If you do not have anymore fixed licenses, ensure that thesample users are deleted. Contact the Remedy AR Systemserver distributor for information about obtaining additionallicenses.

ERROR (9860): The application license format isnot valid.

This error occurs either when the application license format isnot correct or the license information is specified incorrectly.

Ensure that the license names end with User Fixed or UserFloating and each license for a user is separated by asemicolon (;).

ERROR (8932): You do not have write license. An attempt was made to add or modify the contents of a field,however, you do not have write access.

Ensure that you provide the Resource Administrator namewho has read and write permissions on the Remedy ARSystem server, for example, Demo on the adapter service formon IBM Security Identity Manager.

ERROR (333): You have no access to field; 101. An attempt was made to add or modify the contents of a field,however, you do not have read or write access.

Ensure that you provide the Resource Administrator namewho has read and write permissions on the Remedy ARSystemserver, for example, Demo on the adapter service formon IBM Security Identity Manager.

ERROR (302): Entry does not exist in database. An attempt was made to modify a user that does not exist inthe Remedy AR System database. Ensure that the user exists inthe database by performing a reconciliation operation and thenperform the modify operation.

ERROR (90): Message not in catalog; Messagenumber = 90;ONC/RPC program not registered IPAddress of Resource.

This error occurs when an attempt to connect to the RemedyAR System server fails. Perform one of the following steps:

v Check whether you can ping the workstation on which theRemedy AR System server is installed. If you cannot pingthe workstation, ensure that the Remedy Action RequestSystem server service is running on the workstation onwhich the Remedy AR System server is installed. If theservice is not running, restart it.

v Check whether there is successful LAN connection betweenthe Tivoli Directory Integrator and the workstation on whichRemedy AR System server is installed.

ERROR (304): Must have Administrativepermissions to perform this operation.

An attempt was made to add, modify, or delete a user withoutthe Administrator permissions and Fixed License of theRemedy AR System server. Ensure that you haveAdministrator permissions and a Fixed License of the RemedyAR System server to perform the operation.


Table 14. Warnings, error messages, and corrective action (continued)


WARNING (77): No free floating full text licensetokens are available. Currently accessing the systemwithout full text search capability. License willupgrade when one is available; Hostname ofRemedy AR System server

You are assigned a floating, Full Text Search Option license,however, there are no floating, Full Text Search Option tokensavailable at this time. You can access the database withoutaccess to the full text search (FTS) engine. The system tries toupgrade your license type when a token is available. Thesystem uses the default database search capability on all fields,including the fields that are FTS indexed.

ERROR[com.remedy.arsys.api.NativeLibraryLoader] -Could not load native libraryjava.lang.UnsatisfiedLinkError: arjni70 (Not foundin java.library.path)

Perform the following steps:

1. Copy the C API files for AIX operating system to theITDI_HOME/jvm/jre/bin/classic directory. See “Copies ofthe Remedy AR System files” on page 9.

2. Navigate to the ITDI_HOME/jvm/jre/bin/classic directory.

3. Run the following commands:

ln -s libicui18nbmc32.0.a libicui18nbmc32.aln -s libicudatabmc32.0.a libicudatabmc32.aln -s libicuucbmc32.0.a libicuucbmc32.a

4. Restart the Dispatcher service.

ERROR[com.remedy.arsys.api.NativeLibraryLoader] -Could not load native libraryjava.lang.UnsatisfiedLinkError: arjni70 (Not foundin java.library.path)

Perform the following steps:

1. Copy the C API files for HP-UX operating system to theITDI_HOME/jvm/jre/lib/PA_RISC2.0/server directory. SeeRemedy AR System.

2. Navigate to the ITDI_HOME/jvm/jre/lib/PA_RISC2.0/serverdirectory.

3. Run the following commands:

ln -s libicui18nbmc.sl.32.0 libicui18nbmc.sl.32ln -s libicudatabmc.sl.32.0 libicudatabmc.sl.32ln -s libicuucbmc.sl.32.0 libicuucbmc.sl.32

4. Restart the Dispatcher service.

Chapter 5. Troubleshooting the adapter errors 29


Chapter 6. Adapter upgrade

You can upgrade the adapter is upgraded by installing the new version of theadapter.

Upgrading the adapter involves tasks such as upgrading the connector, dispatcher,and the existing adapter profile To verify the required version of these adaptercomponents, see the adapter release notes.

Connector upgradeBefore 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.

Existing adapter profile upgradeRead the adapter release notes for any specific instructions before you import anew adapter 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. Adapter uninstallation

Before you uninstall the adapter, inform your users that the adapter is unavailable.

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

To uninstall the Remedy AR System Adapter completely, you must perform thefollowing tasks:1. “Uninstalling the adapter from the Tivoli Directory Integrator server”2. “Adapter profile removal from the IBM Security Identity Manager server”

Uninstalling the adapter from the Tivoli Directory Integrator serverUse this task to remove the connector file for the Remedy AR System Adapter.

About this task

Note: The Dispatcher is required for all Tivoli Directory Integrator adapters. If youuninstall the Dispatcher, none of the other installed adapters work. To uninstall theDispatcher, see the Dispatcher Installation and Configuration Guide

To remove the Tivoli Directory Integrator connector, complete these steps:

Procedure1. Stop the adapter service. For information about stopping the service, see “Start,

stop, and restart of the adapter service” on page 15.2. Delete the ITDI_HOME/jars/connectors/RemedyARSConnector.jar file.3. Start the adapter service.

Adapter profile removal from the IBM Security Identity Manager serverBefore you remove the adapter profile, ensure that objects that reference theadapter profile do not exist on your IBM Security Identity Manager server.v Adapter service instancesv Policies referencing an adapter instance or the profilev Accounts

For specific information about removing the adapter profile, see the IBM SecurityIdentity Manager product documentation.



Chapter 8. Adapter reinstallation

There are no special considerations for reinstalling the adapter. You are notrequired to remove the adapter before reinstalling. See Chapter 6, “Adapterupgrade,” on page 31.



Appendix A. Adapter attributes

The IBM Security Identity Manager server communicates with the adapter withattributes in transmission packets that are sent over a network.

The combination of attributes depends on the type of action that the IBM SecurityIdentity Manager server requests from the adapter.

The following table lists the account form attributes that the adapter uses.

Table 15. Account form attributes and their details

Attribute name on the RemedyAR System 7.0 Adapter accountform

Attribute name on the TivoliDirectory server Data type

Singlevalued

Read orwrite Required

Login Name eruid String True RW True

Full Name erRmdArsFullName String True RW True

License Type erRmdArsLcnsType Integer True RW True

Full Text License Type erRmdArsFullTxtLcnsType Integer True RW True

Creator erRmdArsCreator String True RW True

Request ID erRmdArsReqID String True R False

Password erPassword String True RW False

Group List erRmdArsGrpList String False RW False

Computed Group List erRmdArsCmptGrpList String False R False

Application License erRmdArsAppLcns String True RW False

Default Notify Mechanism erRmdArsDefaultNotifyMech Integer True RW False

Email Address erRmdArsEmailAddr String True RW False

Unique Identifier erRmdArsUID String True RW False

Create Date erRmdArsCreateDate Date True R False

Last Modified By erRmdArsLastModBy String True R False

Modified Date erRmdArsModDate Date True R False

Note:

v The maximum character limit for the Login Name (eruid) attribute is 243characters because of the Remedy AR System API limitation.

v The adapter does not support the Application License attribute. It is hiddenattribute, however, you can customize the attribute on the adapter account formby using Form Customization.



Appendix B. Installing the adapter on a z/OS operating system

To install the adapters on the z/OS® UNIX file system, you must install the RMIDispatcher first, then the Tivoli Directory Integrator RTC connector.

About this task

For instructions about installing the dispatcher, see the Directory Integrator RMIDispatcher Adapter Installation and Configuration Guide.

Installing the Tivoli Directory Integrator RTC connectorUse these detailed steps to install the Tivoli Directory Integrator RTC connector.

Procedure1. Locate the delivered adapter compressed file.2. Extract the contents of the compressed file into a temporary directory and

navigate to that directory.3. From the temporary directory, locate and navigate to the zSystem directory.4. Under the zSystem directory, locate the following two files:

v RTCAdapter.tar

v instRTC_zOS.sh

Note: The RTCAdapter.tar file is a binary UNIX tar file and the instRTC_zOS.shfile is a UNIX shell script.

5. Copy the two files to the same directory on a z/OS workstation where youwant to install the adapter.

6. Run the following command to set the executable permissions for theinstRTC_zOS.sh file:chmod +x instRTC_zOS.sh

7. Run the following command to begin the connection installation:./ instRTC_zOS.sh

The following dialog is displayed.************************************************

TDI RTC connector Installation Program************************************************

You will prompted to enter the following information:

Your TDI solution directory.

Make sure you have the above information available andand the PosixAdapter.jar is located in the current directorybefore you continue

1. Install2. Quit

Please enter choice: 1

Enter the solution directory name (full path): /u/user2/rmi/soldir


Verifying the solution directory /u/user2/rmi/soldir...Extracting content of RTCAdapter.jar...Getting connector files from /u/user2/rmi/RTCAdapter...

Installation complete, press any key to continue..

Note: The path given in the example might be different on your workstation.


Appendix C. 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 D. Support information

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

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 D. Support information 45

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

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


Appendix E. 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 51

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, 47account

password requirements 23restoration 23

adapterattributes

account form 37combination by action type 37description 37

components requiredconnector 1dispatcher 1profile 1

configuration 21features 1installation

C API files 9Dispatcher requirement 9errors 25JAR files 9planning 5roadmaps 5steps 14task sequence 5Tivoli Directory Integrator RTC

connector 39troubleshooting 25verifying 15, 23warnings 25worksheet 6z/OS UNIX file system 39

overview 1post-installation tasks

configuration 21language pack 21SSL setup 21verification 21

profilecreating service 17customizing 21dispatcher restart required 31importing 16objects that reference 33removal 33service creation 17upgrade 31upgrading 16verifying 17

service 17supported configurations

multiple servers 2single server 2

task automation 1uninstallation 33upgrading 31user account 17

attributes, description 37

CC API files 9, 11configuring, adapter 21connector

files, removing 33RemedyARSConnector 1upgrading 31

customizing, adapter profiles 21

Ddispatcher

installation requirement 1installation, verifying 13

download, software 7

Eeducation xerror messages 27

IIBM

Software Support xSupport Assistant x

IBM Support Assistant 44installation

adapterDispatcher requirement 9errors 25overview 1profile 16steps 14troubleshooting 25verifying 15warnings 25

dispatcher, verifying 13language pack 23roadmap 5verification

adapter 23worksheet 6

ISA 44ISIM_HOME definition 41ITDI_HOME definition 41

JJAR files 9, 11

Kknowledge bases 43

Llanguage pack

installation 23same for adapters and server 23

logs, trace.log file 16

Mmessages

error 27warning 27

MS-DOS ASCII characters 22

Nnotices 49

Oonline

publications ixterminology ix

overview, adapter 1

Ppassword

accountrequirements 23restoration 23

requirements 23preinstallation, roadmap 5problem-determination xprofile

architecture 1editing on UNIX or Linux 22importing 16installation 16

publicationsaccessing online ixlist of ix

Rremoving connector files 33roadmap

installation 5preinstallation 5

Sservice

restart 15start 15stop 15

service, creating 17software

download 7


software (continued)prerequisites 6requirements 6website 7

support contact information 44supported configurations

adapter 2multiple servers 2overview 2single server 2

system filesC API files 9, 11JAR files 9, 11

Tterminology ixtivoli directory integrator 1trace.log file 16training xtroubleshooting

contacting support 44error messages 27getting fixes 44identifying problems 25searching knowledge bases 43support website xtechniques 25warning messages 27

Uuninstalling

adapter 33from the directory integrator 33

upgradeadapter 31connector 31

Vverification

installation 23operating system

prerequisites 6requirements 6

softwareprerequisites 6requirements 6

vi command 22

Wwarning messages 27

Zz/OS UNIX file system, adapter

installation 39


��

Printed in USA

SC27-4412-00

Documents

· Title: IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide Author: IBM Created Date: 2/7/2014 1:43:01 AM