IBM Security Identity Manager: Remedy AR System Adapter

IBM Security Identity Manager
Version 6.0
Remedy AR System Adapter
Installation and Configuration Guide
SC27-4412-00
IBM Security Identity Manager
Version 6.0
Remedy AR System Adapter
Installation and Configuration Guide
SC27-4412-00
Note
Before 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 all
subsequent 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 Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . v
Tables . . . . . . . . . . . . . . . vii
Preface . . . . . . . . . . . . . . . ix
Preface . . . . . . . . . . .
About this publication . . . . .
Access to publications and terminology
Accessibility . . . . . . . . .
Technical training. . . . . . . .
Support information . . . . . . .
Statement of Good Security Practices .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
. ix
. ix
. x
. x
. x
. x
Chapter 1. Remedy AR System Adapter
Installation and Configuration Guide . . 1
Overview of the adapter . .
Features of the adapter . .
Architecture of the adapter
Supported configurations .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 2. Adapter installation planning
Preinstallation roadmap
Installation roadmap. .
Prerequisites . . . .
Installation worksheet for
Software download . .
. . . .
. . . .
. . . .
the adapter
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
1
2
5
.
.
.
.
.
.
.
.
.
.
5
5
5
6
7
Chapter 3. Adapter installation and
configuration . . . . . . . . . . . . 9
Copies of the Remedy AR System files. . . . .
Placement of the Remedy AR System 7.5 library
files . . . . . . . . . . . . . . .
Placement of the Remedy AR System 7.6.04
library files . . . . . . . . . . . .
Dispatcher installation verification . . . . . .
Installing the adapter . . . . . . . . . .
Starting, stopping, and restarting the Dispatcher
service . . . . . . . . . . . . . . .
Verifying the adapter installation . . . . . .
Start, stop, and restart of the adapter service . .
Importing the adapter profile into the IBM Security
Identity Manager server . . . . . . . . .
Adapter profile installation verification . . . .
Adapter user account creation . . . . . . .
Creating a service . . . . . . . . . . .
Chapter 4. First steps after installation
Adapter configuration .
.
.
© Copyright IBM Corp. 2012, 2013
.
.
.
.
.
.
.
. 9
. 9
. 11
. 13
. 14
. 14
. 15
. 15
.
.
.
.
16
17
17
17
21
Customizing the adapter profile . . . . .
Editing adapter profiles on the UNIX or LINUX
operating system . . . . . . . . . .
Password management for account restoration .
Language pack installation . . . . . . . .
Verifying that the adapter is working correctly .
. 21
.
.
.
.
22
23
23
23
Chapter 5. Troubleshooting the adapter
errors . . . . . . . . . . . . . . . 25
Techniques for troubleshooting problems
Warning and error messages. . . . .
.
.
.
.
.
.
. 25
. 27
Chapter 6. Adapter upgrade. . . . . . 31
Connector upgrade . . . . . .
Existing adapter profile upgrade .
.
.
.
.
.
.
.
.
.
.
. 31
. 31
Chapter 7. Adapter uninstallation . . . 33
Uninstalling the adapter from the Tivoli Directory
Integrator server. . . . . . . . . . . .
Adapter profile removal from the IBM Security
Identity Manager server . . . . . . . . .
Chapter 8. Adapter reinstallation
. 33
. 33
. . . 35
Appendix A. Adapter attributes . . . . 37
Appendix B. Installing the adapter on a
z/OS operating system . . . . . . . . 39
Installing the Tivoli Directory Integrator RTC
connector . . . . . . . . . . . . .
.
. 39
Appendix C. Definitions for ITDI_HOME
and ISIM_HOME directories . . . . . . 41
Appendix D. Support information . . . 43
Searching knowledge bases .
Obtaining a product fix . .
Contacting IBM Support . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 43
. 44
. 44
Appendix E. Accessibility features for
IBM Security Identity Manager . . . . 47
Notices . . . . . . . . . . . . . . 49
Index . . . . . . . . . . . . . . . 53
. 21
iii
iv
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Figures
1.
The architecture of the Remedy AR System
Adapter . . . . . . . . . . . . .
© Copyright IBM Corp. 2012, 2013
. 2
2.
3.
Example of a single server configuration .
Example of multiple server configuration
.
. 2
3
v
vi
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Tables
1.
2.
3.
4.
5.
6.
7.
8.
Preinstallation road map . . . . . . . . 5
Installation roadmap . . . . . . . . . . 5
Prerequisites to install the adapter . . . . . 6
Required information to install the adapter
6
Files needed for Windows operating systems
10
Files needed for AIX operating systems
10
Files needed for HPUX operating systems
11
Files needed for Linux or Solaris operating
systems . . . . . . . . . . . . . . 11
© Copyright IBM Corp. 2012, 2013
9.
10.
11.
12.
13.
14.
15.
Files needed for Windows operating systems
12
Files needed for AIX operating systems
12
Files needed for HPUX operating systems
13
Files needed for Linux or Solaris operating
systems . . . . . . . . . . . . . . 13
Adapter components . . . . . . . . . 15
Warnings, error messages, and corrective
action . . . . . . . . . . . . . . 27
Account form attributes and their details
37
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 the
basic information that you can use to install and configure the IBM Remedy AR
System Adapter. The adapter enables connectivity between the IBM® Security
Identity Manager server and the Remedy AR System server.
IBM Security Identity Manager was previously known as Tivoli® Identity Manager.
Access to publications and terminology
This 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 Security
Identity 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 the
publications are updated at the following locations:
IBM Security Identity Manager library
The product documentation site (http://publib.boulder.ibm.com/
infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.isim.doc_6.0/ichomepage.htm) displays the welcome page and navigation for the library.
IBM Security Systems Documentation Central
IBM Security Systems Documentation Central provides an alphabetical list
of all IBM Security Systems product libraries and links to the online
documentation for specific versions of each product.
IBM Publications Center
The IBM Publications Center site ( http://www-05.ibm.com/e-business/
linkweb/publications/servlet/pbi.wss) offers customized search functions
to help you find all the IBM publications you need.
IBM Terminology website
The IBM Terminology website consolidates terminology for product libraries in one
location. You can access the Terminology website at http://www.ibm.com/
software/globalization/terminology.
© Copyright IBM Corp. 2012, 2013
ix
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.
Technical training
For technical training information, see the following IBM Education website at
http://www.ibm.com/software/tivoli/education.
Support information
IBM Support provides assistance with code-related problems and routine, short
duration installation or usage questions. You can directly access the IBM Software
Support 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 can
provide additional support resources.
Statement of Good Security Practices
IT system security involves protecting systems and information through
prevention, detection and response to improper access from within and outside
your 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 be
considered completely secure and no single product, service or security measure
can be completely effective in preventing improper use or access. IBM systems,
products and services are designed to be part of a comprehensive security
approach, which will necessarily involve additional operational procedures, and
may require other systems, products or services to be most effective. IBM DOES
NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES ARE
IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THE
MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.
x
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 1. Remedy AR System Adapter Installation and
Configuration Guide
This installation guide provides the basic information that you use to install and
configure the Remedy AR System Adapter. The adapter enables connectivity
between the IBM Security Identity Manager server and the managed resource.
Overview of the adapter
The Remedy AR System Adapter enables communication between the IBM Security
Identity Manager server and the Remedy AR System server.
An adapter provides an interface between a managed resource and the IBM
Security Identity Manager server. Adapters might reside on the managed resource.
The IBM Security Identity Manager server manages access to the resource by using
your security system. Adapters function as trusted virtual administrators on the
target platform. They perform tasks, such as creating, suspending, and restoring
user accounts, and other administrative functions that are performed manually. The
adapter runs as a service, independently of whether you are logged on to the IBM
Security Identity Manager server.
Features of the adapter
The adapter automates various user account administrative tasks.
The adapter automates the following tasks:
v Reconciling user accounts and other support data
v Adding user accounts
v Modifying user account attributes
v Modifying user account passwords
v Deleting user accounts
Note: The Remedy AR System server does not support the Suspend and Restore
tasks, therefore, the adapter does not automate these tasks.
Architecture of the adapter
You must install the several components for the adapter to work correctly.
You must install the following components for the adapter:
v The Dispatcher
v The RemedyARSConnector connector
v The IBM Security Identity Manager adapter profile
You need to install the Dispatcher and the adapter profile; however, the Tivoli
Directory Integrator connector might already be installed with the base Tivoli
Directory Integrator product.
Figure 1 on page 2 describes the components that work together to complete the
user account management tasks in a Tivoli Directory Integrator environment.
© Copyright IBM Corp. 2012, 2013
1
IBM Security RMI calls
Identity
Manager
Server
Dispatcher
Service
(an instance
of the IBM
Tivoli
Directory
Integrator)
Adapter
resource
Figure 1. The architecture of the Remedy AR System Adapter
For more information about Tivoli Directory Integrator, see the Quick Start Guide at
IBM Security Identity Manager product documentation.
Supported configurations
The adapter supports both single server and multiple server configurations.
The fundamental components in each environment are:
v The IBM Security Identity Manager server
v The Tivoli Directory Integrator server
v The managed resource
v The adapter
The adapter must reside directly on the server that runs the Tivoli Directory
Integrator 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 one
server to establish communication with the Remedy AR System server.
The Remedy AR System server is installed on a different server as described in
Figure 2.
IBM Security
Identity Manager Server
Tivoli Directory
Integrator Server
Managed
resource
Adapter
Figure 2. Example of a single server configuration
Multiple server configuration
In a multiple server configuration, the IBM Security Identity Manager server, the
Tivoli Directory Integrator, the Remedy AR System Adapter, and the Remedy AR
System server are installed on different servers.
Install the Tivoli Directory Integrator server, and the Remedy AR System Adapter
on the same server as described in Figure 3 on page 3.
2
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
IBM Security
Identity Manager
server
Tivoli Directory
Integrator server
Managed
resource
Adapter
Figure 3. Example of multiple server configuration
Chapter 1. Remedy AR System Adapter Installation and Configuration Guide
3
4
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 2. Adapter installation planning
Installing and configuring the adapter involves several steps that you must
complete in an appropriate sequence. Review the roadmaps before you begin the
installation process.
Preinstallation roadmap
Before you install the adapter, you must prepare the environment by doing the
tasks that are listed in the preinstallation roadmap.
Table 1. Preinstallation road map
Task
For more information
Obtain the installation software.
Download the software from Passport
Advantage® website. See “Software
download” on page 7.
Verify that your environment meets the
See “Prerequisites.”
software and hardware requirements for the
adapter.
Obtain the necessary information for the
installation and configuration.
See “Installation worksheet for the adapter”
on page 6.
Installation roadmap
To 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” on
page 13.
Install the adapter.
See “Installing the adapter” on page 14.
Verify the installation.
See “Verifying the adapter installation” on
page 15.
Import the adapter profile.
See “Importing the adapter profile into the
IBM Security Identity Manager server” on
page 16.
Verify the profile installation.
See “Adapter profile installation
verification” on page 17.
Create an adapter user account.
See “Adapter user account creation” on page
17.
Create a service.
See “Creating a service” on page 17.
Configure the adapter.
See “Adapter configuration” on page 21.
Prerequisites
Verify that your environment meets all the prerequisites before you install the
adapter.
© Copyright IBM Corp. 2012, 2013
5
Table 3 identifies the software and operating system prerequisites for the adapter
installation.
Ensure that you install the adapter on the same workstation as the Tivoli Directory
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
Remedy AR System server
Version 7.5
Version 7.6.04
System Administrator Authority
To complete the adapter installation procedure,
you must have system administrator authority.
Tivoli Directory Integrator adapters
solution directory
A Tivoli Directory Integrator adapters solution
directory is a Tivoli Directory Integrator work
directory for IBM Security Identity Manager
adapters. See the Dispatcher Installation and
Configuration Guide.
Remedy AR System Jar files
See “Copies of the Remedy AR System files” on
page 9.
For information about the prerequisites and supported operating systems for Tivoli
Directory Integrator, see the IBM Tivoli Directory Integrator Administrator Guide.
Installation worksheet for the adapter
Take note of the required directories before you install the adapter.
Table 4. Required information to install the adapter
Required information Description
Tivoli Directory
Integrator Home
Directory
The ITDI_HOME directory contains
the jars/connectors subdirectory.
This subdirectory contains adapter
JAR files.
Value
If Tivoli Directory
Integrator is automatically
installed with your IBM
Security Identity Manager
product, the default
directory path for Tivoli
Directory Integrator is as
follows:
Windows:
v for version 7.1:
drive\Program
Files\IBM\TDI\V7.1
UNIX:
v for version 7.1:
/opt/IBM/TDI/V7.10
6
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Table 4. Required information to install the adapter (continued)
Required information Description
Value
Adapters solution
directory
Windows:
This directory is the default
directory. When you install the
dispatcher, the dispatcher prompts
you to specify a file path for the
adapter solution directory. For more
information about the adapter
solution directory, see the Dispatcher
Installation and Configuration Guide.
v for version 7.1:
drive\Program
Files\IBM\TDI\V7.1\
timsol
UNIX:
v for version 7.1:
/opt/IBM/TDI/V7.1/
timsol
Software download
Download the software through your account at the IBM Passport Advantage
website.
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
8
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 3. Adapter installation and configuration
All the adapters that are based on Tivoli Directory Integrator require the
Dispatcher for the adapters to function correctly.
If the Dispatcher is installed from a previous installation, do not reinstall it unless
there is an upgrade to the Dispatcher. See “Dispatcher installation verification” on
page 13.
After verifying the Dispatcher installation, you might need to install the Tivoli
Directory Integrator connector. Depending on your adapter, the connector might
already be installed as part of the Tivoli Directory Integrator product and no
further action is required.
Copies of the Remedy AR System files
Before you can install the adapter, you must copy the Remedy AR System JAR and
C API files to the specified directories.
The following tables list the Remedy AR System JAR files that are required for the
installation of the adapter. The tables also provide the location of the JAR files in
the Remedy AR System server installation directory. You must copy the JAR files
from the workstation where the Remedy AR System server is installed to the
ITDI_HOME\jvm\jre\lib\ext directory.
Select the files based on your operating system and your version of the Remedy
AR System server.
Note: You must install the API package during the Remedy AR System server
installation. This installation creates the JAR files and C API library files that you
must copy from Remedy AR System server workstation to the Tivoli Directory
Integrator directories. If the API package is not installed, you must upgrade the
Remedy AR System server to install only the API package. For more information
about API package installation, see the Remedy AR System guide Installing.
Placement of the Remedy AR System 7.5 library files
If you are managing a Remedy 7.5 server, you must copy the following files from
the Remedy 7.5 server installation directory. You must place these files in the Tivoli
Directory 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.
© Copyright IBM Corp. 2012, 2013
9
Table 5. Files needed for Windows operating systems.
Location on the Remedy
ARS server
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi75.jar
arapiext75.jar
arapi75.dll
arjni75.dll
arrpc75.dll
arutl75.dll
arxmlutil75.dll
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil75.jar
arutiljni75.dll
C:\Program Files\BMC
Software\ARSystem
icudt32.dll
icuinbmc32.dll
icuucbmc32.dll
Xalan-Cbmc_1_10.dll
XalanMessagesbmc_1_10.dll
xerces-cbmc_2_8.dll
xerces-depdombmc_2_8.dll
Target location in the Tivoli
Directory Integrator
environment
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Note: You must add the TDI_HOME\libs folder to the library path for the UNIX
platforms. In these example paths, /opt/IBM/TDI/V7.1 represents the Tivoli
Directory Integrator 7.1 installation directory. Perform the action for your operating
system.
AIX platforms
Set the environment variable LIBPATH to /opt/IBM/TDI/V7.1/libs.
HPUX platforms
Set the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.1/libs.
Linux or Solaris platforms
Set the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.1/libs.
Table 6. Files needed for AIX operating systems.
Location on the Remedy
ARS server
10
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi75.jar
arapiext75.jar
libar.a
libarjni75.a
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil75.jar
arutiljni75.a
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc32.a
libicui18nbmc32.a
libicuiobmc32.a
libicuucbmc32.a
libxalan-cbmc.a
libxalanMsg.a
libxerces-cbmc.a
Target location in the Tivoli
Directory Integrator
environment
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Table 7. Files needed for HPUX operating systems.
Location on the Remedy
ARS server
Target location in the Tivoli
Directory Integrator
environment
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi75.jar
arapiext75.jar
libar.sl
libarjni75.sl
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil75.jar
arutiljni75.sl
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc.sl.32
libicui18nbmc.sl.32
libicuiobmc.sl.32
libicuucbmc.sl.32
libxalan-cbmc.sl
libxalanMsgbmc.sl
libxerces-cbmc.sl
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Table 8. Files needed for Linux or Solaris operating systems.
Location on the Remedy
ARS server
Target location in the Tivoli
Directory Integrator
environment
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi75.jar
arapiext75.jar
libar.so
libarjni75.so
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil75.jar
arutiljni75.so
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc.so.32
libicui18nbmc.so.32
libicuiobmc.so.32
libicuucbmc.so.32
libxalan-cbmc.so
libxalanMsgbmc.so
libxerces-cbmc.so
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Placement of the Remedy AR System 7.6.04 library files
If you are managing a Remedy 7.6.04 server, you must copy the following files
from the Remedy 7.6.04 server installation directory. You must place these files in
the Tivoli Directory 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.
Chapter 3. Adapter installation and configuration
11
Table 9. Files needed for Windows operating systems.
Location on the Remedy
ARS server
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi7604_build002.jar
arapiext7604_build002.jar
arapi7604_build002.dll
arjni7604_build002.dll
arrpc7604_build002.dll
arutl7604_build002.dll
arxmlutil7604_build002.dll
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil7604_build002.jar
C:\Program Files\BMC
Software\ARSystem
icudt32.dll
icuinbmc32.dll
icuucbmc32.dll
Xalan-Cbmc_1_10.dll
XalanMessagesbmc_1_10.dll
xerces-cbmc_2_8.dll
xerces-depdombmc_2_8.dll
Target location in the Tivoli
Directory Integrator
environment
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Note: You must add the TDI_HOME\libs folder to the library path for the UNIX
platforms. In these example paths, /opt/IBM/TDI/V7.1 represents the Tivoli
Directory Integrator 7.1 installation directory. Perform the action for your operating
system.
AIX platforms
Set the environment variable LIBPATH to /opt/IBM/TDI/V7.1/libs.
HPUX platforms
Set the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.1/libs.
Linux or Solaris platforms
Set the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.1/libs.
Table 10. Files needed for AIX operating systems.
Location on the Remedy
ARS server
12
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi7604_build002.jar
arapiext7604_build002.jar
libar.a
libarjni7604_build002.a
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil7604_build002.jar
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc32.a
libicui18nbmc32.a
libicuiobmc32.a
libicuucbmc32.a
libxalan-cbmc.a
libxalanMsgbmc.a
libxerces-cbmc.a
Target location in the Tivoli
Directory Integrator
environment
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Table 11. Files needed for HPUX operating systems.
Location on the Remedy
ARS server
Target location in the Tivoli
Directory Integrator
environment
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi7604_build002.jar
arapiext7604_build002.jar
libar.sl
libarjni7604_build002.sl
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil7604_build002.jar
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc.sl.32
libicui18nbmc.sl.32
libicuiobmc.sl.32
libicuucbmc.sl.32
libxalan-cbmc.sl
libxalanMsgbmc.sl
libxerces-cbmc.sl
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Table 12. Files needed for Linux or Solaris operating systems.
Location on the Remedy
ARS server
Target location in the Tivoli
Directory Integrator
environment
File name
C:\Program Files\BMC
Software\ARSystem\
Arserver\api\lib
arapi7604_build002.jar
arapiext7604_build002.jar
libar.so
libarjni7604_build002.so
ITDI_HOME\jars\3rd
party\others
log4j-1.2.15.jar
C:\Program Files\BMC
Software\ARSystem\midtier\
WEB-INF\lib
arutil7604_build002.jar
C:\Program Files\BMC
Software\ARSystem\
Arserver\bin
libicudatabmc.so.32
libicui18nbmc.so.32
libicuiobmc.so.32
libicuucbmc.so.32
libxalan-cbmc.so
libxalanMsgbmc.so
libxerces-cbmc.so
ITDI_HOME\jvm\jre\lib\ext
ITDI_HOME\libs
Dispatcher installation verification
If this installation is for 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 server
where 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 and
Configuration Guide.
Chapter 3. Adapter installation and configuration
13
Installing the adapter
Use 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. This
connector is not available with the base Tivoli Directory Integrator product. The
adapter installation involves the Tivoli Directory Integrator Remedy ARS System
connector installation. After installing the Dispatcher, you must install the
connector for the adapter. The connector is included in a separate installer
provided with the adapter package. Before you install the adapter, make sure that
the Dispatcher is already installed. See “Dispatcher installation verification” on
page 13.
Note: If you are running on a 64-bit operating system, you must use the Tivoli
Directory Integrator-supplied JVM. The JVM is in ITDI_HOME/jvm/jre/bin/, where
ITDI_HOME is the directory where Tivoli Directory Integrator is installed.
Procedure
1. 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 service
This section provides you the detail information to start, stop, and restart the
Dispatcher service using the command-line option.
14
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
About this task
If the dispatcher service is running before the adapter installation or uninstallation
process begins, then the adapter installation or uninstallation process stops the
dispatcher service. The process restarts the dispatcher service after the completion
of the adapter installation or uninstallation. However, the process does not restart
the dispatcher service after the completion of the adapter installation or
uninstallation if the service is not running before the process begins.
If you want to start the dispatcher service after the adapter installation or
uninstallation, 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 installation
After you install the adapter, the RemedyARSConnector.jar file is created in the
ITDI_HOME\jars\connectors directory.
About this task
The following table lists the adapter components that are created on the Tivoli
Directory 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 in
the adapter installer directory for any errors.
If this installation is to upgrade a connector, send a request from IBM Security
Identity Manager and verify that the version number in the ibmdi.log. That
number must match the version of the connector that you installed. The ibmdi.log
file is at ITDI_Home\adapter solution directory\logs.
Start, stop, and restart of the adapter service
To 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 is
added to the Dispatcher instance, which runs all the adapters that are installed on
the same Tivoli Directory Integrator instance.
Chapter 3. Adapter installation and configuration
15
See the topic about starting stopping, and restarting the dispatcher service in the
Dispatcher Installation and Configuration Guide.
Importing the adapter profile into the IBM Security Identity Manager
server
Use this task to create a service on the IBM Security Identity Manager server and
establish communication with the adapter
Before you begin
Before you can create an adapter service, the IBM Security Identity Manager server
must have an adapter profile to recognize the adapter. The files that are packaged
with the adapter include the adapter profile JAR file. You can import the adapter
profile as a service profile on the server with the Import feature of IBM Security
Identity 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 from
the JAR file to modify the necessary files and package the JAR file with the
updated files.
Before you begin to import the adapter profile, 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
An adapter profile defines the types of resources that the IBM Security Identity
Manager server can manage. Use the profile to create an adapter service on IBM
Security Identity Manager server and establish communication with the adapter.
To import the adapter profile, perform the following steps:
Procedure
1. 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 related
to the schema, see the trace.log file for information about the error. The
trace.log file location is specified by using the handler.file.fileDir property
defined in the IBM Security Identity Manager enRoleLogging.properties file.
The enRoleLogging.properties file is installed in the ITIM_HOME\data directory.
16
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
6. Restart IBM Security Identity Manager for the change to take effect.
Adapter profile installation verification
After 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 the
adapter profile. For more information about creating a service, see “Creating a
service.”
If you are unable to create a service using the adapter profile or open an account
on the service, the adapter profile is not installed correctly. You must import the
adapter profile again.
Adapter user account creation
You must create a user account for the adapter on the managed resource. Provide
the account information when you create a service for the adapter on IBM Security
Identity Manager.
For more information about creating a service, see “Creating a service.”
Creating a service
After the adapter profile is imported on IBM Security Identity Manager, you must
create a service so that IBM Security Identity Manager can communicate with the
adapter.
About this task
To create or change a service, you must use the service form to provide
information for the service. Service forms might vary depending on the adapter.
Note: If the following fields on the service form are changed for an existing
service, the IBM Security Identity Manager Adapter service on the Tivoli Directory
Integrator server must be restarted.
v AL FileSystem Path
v Max Connection Count
Procedure
1. 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:
Chapter 3. Adapter installation and configuration
17
Service Name
Specify a name that defines the adapter service on the IBM
Security Identity Manager server.
Note: Do not use forward (/) or backward slashes (\) in the
service name.
Description
Optional: Specify a description that identifies the service for
your environment.
Tivoli Directory Integrator URL
Optional: Specify the URL for the Tivoli Directory Integrator
instance. The valid syntax for the URL is rmi://ipaddress:port/ITDIDispatcher, where ip-address is the Tivoli
Directory Integrator host and port is the port number for the
RMI Dispatcher. The default URL is
rmi://localhost:1099/ITDIDispatcher
For information about changing the port number, see IBM
Security Dispatcher Installation and Configuration Guide.
Host Name
Specify the IP address or the host name of the managed
resource.
Note: Enclose the IPv6 address in brackets. An example of a
valid IPv6 address format is:
http://[fedc:ba98:7654:3210:fedc:ba98:7654:3210]
TCP Port
Specify the TCP port number of the managed resource.
User Name
Specify a Login ID of the Remedy AR System server that has
administrator permissions.
Password
Specify a password for the Remedy AR System server user that
has administrator permissions.
Allow Unqualified Searches
Select Yes for the adapter to perform an Unqualified Search on
the Remedy AR System server.
Recon In Batch
Click the check box to reconcile the entries in batches.
On the Dispatcher Attributes tab:
Disable AL Caching
Click the check box to disable the assembly line (test, add,
modify, delete) caching in the dispatcher for the service.
AL FileSystem Path
Specify the file path from where the dispatcher loads the
assembly lines. If you do not specify a file path, the dispatcher
loads the assembly lines received from IBM Security Identity
Manager. For example, you can specify the following file path
to load the assembly lines from the profiles directory of the
Windows operating system: drive:\Program
18
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Files\IBM\TDI\V7.0\profiles or you can specify the following
file path to load the assembly lines from the profiles directory
of the UNIX and Linux operating:/opt/IBM/TDI/V7.0/profiles
Max Connection Count
Specify the maximum number of assembly lines that the
dispatcher can run simultaneously for the service. For example,
enter 10 when you want the dispatcher to run maximum 10
assembly lines simultaneously for the service. If you enter 0 in
the Max Connection Count field, the dispatcher does not limit
the number of assembly lines that run simultaneously for the
service.
On the Status and information tab
This page contains read only information about the adapter and
managed resource. These fields are examples. The actual fields vary
depending on the type of adapter and how the service form is
configured. The adapter must be running to obtain the information.
Click Test Connection to populate the fields.
Last status update: Date
Specifies the most recent date when the Status and information
tab was updated.
Last status update: Time
Specifies the most recent time of the date when the Status and
information tab was updated.
Managed resource status
Specifies the status of the managed resource that the adapter is
connected to.
Adapter version
Specifies the version of the adapter that the IBM Security
Identity Manager service uses to provision request to the
managed resource.
Profile version
Specifies the version of the profile that is installed in the IBM
Security Identity Manager server.
TDI version
Specifies the version of the Tivoli Directory Integrator on which
the adapter is deployed.
Dispatcher version
Specifies the version of the Dispatcher.
Installation platform
Specifies summary information about the operating system
where the adapter is installed.
Adapter account
Specifies the account that running the adapter binary file.
Adapter up time: Date
Specifies the date when the adapter started.
Adapter up time: Time
Specifies the time of the date when the adapter started.
Adapter memory usage
Specifies the memory usage for running the adapter.
Chapter 3. Adapter installation and configuration
19
If the connection fails, follow the instructions in the error message. Also
v 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 IP
address of the managed resource and the port.
6. Click Finish.
20
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 4. First steps after installation
After you install the adapter, you must do several other tasks. The tasks include
configuring the adapter, setting up SSL, installing the language pack, and verifying
the adapter works correctly.
Adapter configuration
You 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 additional
configuration options such as:
v JVM properties
v
v
v
v
v
Dispatcher filtering
Dispatcher properties
Dispatcher port number
Logging configurations
Secure Sockets Layer (SSL) communication
Customizing the adapter profile
To customize the adapter profile, you must modify the Remedy AR System
Adapter JAR file. You might customize the adapter profile to change the account
form or the service form. You can also change the labels on the forms by using the
Form Designer or CustomLabels.properties. Each adapter has a
CustomLabels.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 that
you downloaded from the IBM website.
Note: You cannot modify the schema for this adapter. Attributes cannot be added
to or deleted from the schema.
RemedyARSProfile.jar
The following files are included in the JAR file:
v CustomLabels.properties
v schema.dsml
v service.def
v erRmdArsAccount.xml
v erRmdArsRMIService.xml
v
v
v
v
© Copyright IBM Corp. 2012, 2013
RmdArsSearch.xml
RmdArsAdd.xml
RmdArsModify.xml
RmdArsTest.xml
21
v RmdArsAdapter.xml
v RmdArsDelete.xml
To edit the JAR file, log on to the workstation where the Remedy AR System
Adapter is installed:
Procedure
1. 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 System
Adapter 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 take
effect.
5. To import the file, create a JAR file by using the files in the \temp directory by
running 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 adapter
profile 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 and
starting the Remedy AR System Adapter service.
Editing adapter profiles on the UNIX or LINUX operating
system
The adapter profile .jar file might contain ASCII files that are created by using the
MS-DOS ASCII format.
About this task
If you edit an MS-DOS ASCII file on the UNIX operating system, you might see a
character ^M at the end of each line. These characters indicate new lines of text in
MS-DOS. The characters can interfere with the running of the file on UNIX or
Linux 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 characters
manually.
Example
You can use the vi editor to remove the ^M characters. From the vi command
mode, run the following command and press Enter:
:%s/^M//g
22
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
When you use this command, enter ^M or Ctrl-M by pressing ^v^M or Ctrl V Ctrl
M sequentially. The ^v instructs the vi editor to use the next keystroke instead of
issuing it as command.
Password management for account restoration
How each restore action interacts with its corresponding managed resource
depends on either the managed resource, or the business processes that you
implement. Certain resources reject a password when a request is made to restore
an account. In this case, you can configure IBM Security Identity Manager to
forego the new password requirement.
You can set the Remedy AR System Adapter to require a new password when the
account is restored, if your company has a business process in place that dictates
that the account restoration process must be accompanied by resetting the
password.
In the service.def file, you can define whether a password is required as a new
protocol option. When you import the adapter profile, if an option is not specified,
the adapter profile importer determines the correct restoration password behavior
from the schema.dsml file. Adapter profile components also enable remote services
to find out if you discard a password that is entered by the user in a situation
where multiple accounts on disparate resources are being restored. In this
situation, only some of the accounts being restored might require a password.
Remote services discard the password from the restore action for those managed
resources that do not require them.
Edit the service.def file to add the new protocol options, for example:
<Property Name
</property>
<Property Name
= "com.ibm.itim.remoteservices.ResourceProperties.
PASSWORD_NOT_REQUIRED_ON_RESTORE"<value>true</value>
= "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 not
prompted for a password when an account is restored.
Language pack installation
The adapters use the same language package as IBM Security Identity Manager.
See the IBM Security Identity Manager library and search for information about
installing language packs.
Verifying that the adapter is working correctly
After you install and configure the adapter, take steps to verify that the installation
and configuration are correct.
Procedure
1. 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 are
reported.
5. Verify the IBM Security Identity Manager log file trace.log to ensure that no
errors are reported when you run an adapter operation.
24
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 resolving
problems with the adapter. It also provides information about troubleshooting
errors that might occur during the adapter installation.
Techniques for troubleshooting problems
Troubleshooting is a systematic approach to solving a problem. The goal of
troubleshooting is to determine why something does not work as expected and
how to resolve the problem. Certain common techniques can help with the task of
troubleshooting.
The first step in the troubleshooting process is to describe the problem completely.
Problem descriptions help you and the IBM technical-support representative know
where to start to find the cause of the problem. This step includes asking yourself
basic questions:
v
v
v
v
What are the symptoms of the problem?
Where does the problem occur?
When does the problem occur?
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 the
problem?” This question might seem straightforward; however, you can break it
down into several more-focused questions that create a more descriptive picture of
the 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 the
most important steps in resolving a problem. Many layers of technology can exist
between the reporting and failing components. Networks, disks, and drivers are
only 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 isolate
the 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?
© Copyright IBM Corp. 2012, 2013
25
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 that
layer. Part of identifying where a problem originates is understanding the
environment in which it exists. Take some time to completely describe the problem
environment, including the operating system and version, all corresponding
software and versions, and hardware information. Confirm that you are running
within an environment that is a supported configuration; many problems can be
traced back to incompatible levels of software that are not intended to run together
or have not been fully tested together.
When does the problem occur?
Develop a detailed timeline of events leading up to a failure, especially for those
cases that are one-time occurrences. You can most easily develop a timeline by
working 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 and
information. Typically, you need to look only as far as the first suspicious event
that 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 which
to investigate the problem.
Under which conditions does the problem occur?
Knowing which systems and applications are running at the time that a problem
occurs is an important part of troubleshooting. These questions about your
environment 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 in
which the problem occurs and correlate any dependencies. Remember that just
because multiple problems might have occurred around the same time, the
problems are not necessarily related.
Can the problem be reproduced?
From a troubleshooting standpoint, the ideal problem is one that can be
reproduced. Typically, when a problem can be reproduced you have a larger set of
tools 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 the
problem is of significant business impact, you do not want it to recur. If possible,
26
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
re-create the problem in a test or development environment, which typically offers
you 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 messages
A warning or error message might be displayed in the user interface to provide
information about the adapter or when an error occurs.
The following table contains warnings or errors that might be displayed on the
user 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:
ERROR (382): The values for this entry violate a
unique index that is defined for this form.
Provide a unique login name for the Login Name attribute on
the account form when you perform a user add operation.
(52) The field is a core system field and cannot be
changed.
An attempt was made to modify the contents of one of the
following core system fields:
v Login Name
v Full Name
v Request ID
v Create Date
v Last Modified By
v Last Modified Date
Do not modify these fields because the Remedy AR System
server sets values for these fields.
ERROR (326): Required field cannot be reset to a
NULL value; 2.
An attempt was made to delete the value specified in the
Creator 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 an
alphanumeric character (for example, av234.)
ERROR (417): Cannot translate a group name in
either the Group List or Assignee Group field; 104.
This error occurs when an incorrect value is specified for the
Group 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 System
server by performing a support data reconciliation
operation.
2. Select the group from the updated list available for the
Group List attribute.
Chapter 5. Troubleshooting the adapter errors
27
Table 14. Warnings, error messages, and corrective action (continued)
Warning or error message
Corrective action
ERROR (30): You are already at the limit of the
An attempt was made to create a user and assign a fixed
number of fixed user licenses of the following type; license to the user. You reached the limit of the number of
Full Text : (0).
fixed user licenses. Add the user with a read, none, or floating
license, however, not a fixed license.
The License Type attribute is replaced by write, full text, or
flashboards to indicate the type of fixed license.
If you do not have anymore fixed licenses, ensure that the
sample users are deleted. Contact the Remedy AR System
server distributor for information about obtaining additional
licenses.
ERROR (9860): The application license format is
not valid.
This error occurs either when the application license format is
not correct or the license information is specified incorrectly.
Ensure that the license names end with User Fixed or User
Floating and each license for a user is separated by a
semicolon (;).
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 name
who has read and write permissions on the Remedy AR
System server, for example, Demo on the adapter service form
on 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 name
who has read and write permissions on the Remedy AR
Systemserver, for example, Demo on the adapter service form
on IBM Security Identity Manager.
ERROR (302): Entry does not exist in database.
An attempt was made to modify a user that does not exist in
the Remedy AR System database. Ensure that the user exists in
the database by performing a reconciliation operation and then
perform the modify operation.
ERROR (90): Message not in catalog; Message
number = 90;ONC/RPC program not registered IP
Address of Resource.
This error occurs when an attempt to connect to the Remedy
AR System server fails. Perform one of the following steps:
v Check whether you can ping the workstation on which the
Remedy AR System server is installed. If you cannot ping
the workstation, ensure that the Remedy Action Request
System server service is running on the workstation on
which the Remedy AR System server is installed. If the
service is not running, restart it.
v Check whether there is successful LAN connection between
the Tivoli Directory Integrator and the workstation on which
Remedy AR System server is installed.
ERROR (304): Must have Administrative
permissions to perform this operation.
28
An attempt was made to add, modify, or delete a user without
the Administrator permissions and Fixed License of the
Remedy AR System server. Ensure that you have
Administrator permissions and a Fixed License of the Remedy
AR System server to perform the operation.
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Table 14. Warnings, error messages, and corrective action (continued)
Warning or error message
Corrective action
WARNING (77): No free floating full text license
tokens are available. Currently accessing the system
without full text search capability. License will
upgrade when one is available; Hostname of
Remedy AR System server
You are assigned a floating, Full Text Search Option license,
however, there are no floating, Full Text Search Option tokens
available at this time. You can access the database without
access to the full text search (FTS) engine. The system tries to
upgrade your license type when a token is available. The
system 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 library
java.lang.UnsatisfiedLinkError: arjni70 (Not found
in java.library.path)
Perform the following steps:
1. Copy the C API files for AIX operating system to the
ITDI_HOME/jvm/jre/bin/classic directory. See “Copies of
the 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.a
ln -s libicudatabmc32.0.a libicudatabmc32.a
ln -s libicuucbmc32.0.a libicuucbmc32.a
4. Restart the Dispatcher service.
ERROR
[com.remedy.arsys.api.NativeLibraryLoader] Could not load native library
java.lang.UnsatisfiedLinkError: arjni70 (Not found
in java.library.path)
Perform the following steps:
1. Copy the C API files for HP-UX operating system to the
ITDI_HOME/jvm/jre/lib/PA_RISC2.0/server directory. See
Remedy AR System.
2. Navigate to the ITDI_HOME/jvm/jre/lib/PA_RISC2.0/server
directory.
3. Run the following commands:
ln -s libicui18nbmc.sl.32.0 libicui18nbmc.sl.32
ln -s libicudatabmc.sl.32.0 libicudatabmc.sl.32
ln -s libicuucbmc.sl.32.0 libicuucbmc.sl.32
4. Restart the Dispatcher service.
Chapter 5. Troubleshooting the adapter errors
29
30
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 6. Adapter upgrade
You can upgrade the adapter is upgraded by installing the new version of the
adapter.
Upgrading the adapter involves tasks such as upgrading the connector, dispatcher,
and the existing adapter profile To verify the required version of these adapter
components, see the adapter release notes.
Connector upgrade
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 it
again after the upgrade is complete.
Existing adapter profile upgrade
Read the adapter release notes for any specific instructions before you import a
new 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 the
dispatcher clears the assembly lines cache and ensures that the dispatcher runs the
assembly lines from the updated adapter profile.
© Copyright IBM Corp. 2012, 2013
31
32
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 recovered
when the server is back online.
To uninstall the Remedy AR System Adapter completely, you must perform the
following 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 server
Use 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 you
uninstall the Dispatcher, none of the other installed adapters work. To uninstall the
Dispatcher, see the Dispatcher Installation and Configuration Guide
To remove the Tivoli Directory Integrator connector, complete these steps:
Procedure
1. 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 server
Before you remove the adapter profile, ensure that objects that reference the
adapter profile do not exist on your IBM Security Identity Manager server.
v Adapter service instances
v Policies referencing an adapter instance or the profile
v Accounts
For specific information about removing the adapter profile, see the IBM Security
Identity Manager product documentation.
© Copyright IBM Corp. 2012, 2013
33
34
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Chapter 8. Adapter reinstallation
There are no special considerations for reinstalling the adapter. You are not
required to remove the adapter before reinstalling. See Chapter 6, “Adapter
upgrade,” on page 31.
© Copyright IBM Corp. 2012, 2013
35
36
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Appendix A. Adapter attributes
The IBM Security Identity Manager server communicates with the adapter with
attributes in transmission packets that are sent over a network.
The combination of attributes depends on the type of action that the IBM Security
Identity 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 Remedy
AR System 7.0 Adapter account Attribute name on the Tivoli
form
Directory server
Data type
Single
valued
Read or
write
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 243
characters because of the Remedy AR System API limitation.
v The adapter does not support the Application License attribute. It is hidden
attribute, however, you can customize the attribute on the adapter account form
by using Form Customization.
© Copyright IBM Corp. 2012, 2013
37
38
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 RMI
Dispatcher first, then the Tivoli Directory Integrator RTC connector.
About this task
For instructions about installing the dispatcher, see the Directory Integrator RMI
Dispatcher Adapter Installation and Configuration Guide.
Installing the Tivoli Directory Integrator RTC connector
Use these detailed steps to install the Tivoli Directory Integrator RTC connector.
Procedure
1. 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.sh
file is a UNIX shell script.
5. Copy the two files to the same directory on a z/OS workstation where you
want to install the adapter.
6. Run the following command to set the executable permissions for the
instRTC_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 and
and the PosixAdapter.jar is located in the current directory
before you continue
1. Install
2. Quit
Please enter choice: 1
Enter the solution directory name (full path): /u/user2/rmi/soldir
© Copyright IBM Corp. 2012, 2013
39
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.
40
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Appendix C. Definitions for ITDI_HOME and ISIM_HOME
directories
ITDI_HOME is the directory where Tivoli Directory Integrator is installed.
ISIM_HOME is the directory where IBM Security Identity Manager is installed.
ITDI_HOME
This directory contains the jars/connectors subdirectory that contains files
for the adapters.
Windows
drive\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_HOME
This directory is the base directory that contains the IBM Security Identity
Manager code, configuration, and documentation.
Windows
path\IBM\isim
UNIX
path/IBM/isim
© Copyright IBM Corp. 2012, 2013
41
42
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 44
v “Contacting IBM Support” on page 44
Searching knowledge bases
You can often find solutions to problems by searching IBM knowledge bases. You
can optimize your results by using available resources, support tools, and search
methods.
About this task
You can find useful information by searching the product documentation for IBM
Security Identity Manager. However, sometimes you must look beyond the product
documentation to answer your questions or resolve problems.
Procedure
To search knowledge bases for information that you need, use one or more of the
following approaches:
1. Search for content by using the IBM Support Assistant (ISA).
ISA is a no-charge software serviceability workbench that helps you answer
questions and resolve problems with IBM software products. You can find
instructions 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 support
tools and information for all IBM systems, software, and services. The IBM
Support Portal lets you access the IBM electronic support portfolio from one
place. You can tailor the pages to focus on the information and resources that
you need for problem prevention and faster problem resolution. Familiarize
yourself 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, explore
troubleshooting and other resources, and demonstrate how you can tailor the
page by moving, adding, and deleting portlets.
3. Search for content about IBM Security Identity Manager by using one of the
following 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 IBM
masthead search by typing your search string into the Search field at the top of
any 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
© Copyright IBM Corp. 2012, 2013
43
include information that is outside the ibm.com domain. However, sometimes
you can find useful problem-solving information about IBM products in
newsgroups, forums, and blogs that are not on ibm.com.
Tip: Include “IBM” and the name of the product in your search if you are
looking for information about an IBM product.
Obtaining a product fix
A product fix might be available to resolve your problem.
About this task
You can get fixes by following these steps:
Procedure
1. 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 Support
IBM Support assists you with product defects, answers FAQs, and helps users
resolve problems with the product.
Before you begin
After trying to find your answer or solution by using other self-help options such
as technotes, you can contact IBM Support. Before contacting IBM Support, your
company or organization must have an active IBM software subscription and
support contract, and you must be authorized to submit problems to IBM. For
information about the types of available support, see the Support portfolio topic in
the “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 the
Software 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 to
resolution.
a. Download and install the ISA tool from the ISA website. See
http://www.ibm.com/software/support/isa/.
b. Open ISA.
44
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 all
of your service requests from the Service Request portlet on the Service
Request page.
v By telephone for critical, system down, or severity 1 issues: For the telephone
number to call in your region, see the Directory of worldwide contacts web
page.
Results
If the problem that you submit is for a software defect or for missing or inaccurate
documentation, IBM Support creates an Authorized Program Analysis Report
(APAR). The APAR describes the problem in detail. Whenever possible, IBM
Support provides a workaround that you can implement until the APAR is
resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support
website daily, so that other users who experience the same problem can benefit
from the same resolution.
Appendix D. Support information
45
46
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Appendix E. Accessibility features for IBM Security Identity
Manager
Accessibility features help users who have a disability, such as restricted mobility
or limited vision, to use information technology products successfully.
Accessibility features
The following list includes the major accessibility features in IBM Security Identity
Manager.
v Support for the Freedom Scientific JAWS screen reader application
v Keyboard-only operation
v Interfaces that are commonly used by screen readers
v Keys that are discernible by touch but do not activate just by touching them
v Industry-standard devices for ports and connectors
v The attachment of alternative input and output devices
The IBM Security Identity Manager library, and its related publications, are
accessible.
Keyboard navigation
This product uses standard Microsoft Windows navigation keys.
Related accessibility information
The following keyboard navigation and accessibility features are available in the
form 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 the
web 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 using
themes, which provide high contrast color schemes that help users with vision
impairments to differentiate between controls.
IBM and accessibility
See the IBM Human Ability and Accessibility Center For more information about
the commitment that IBM has to accessibility.
© Copyright IBM Corp. 2012, 2013
47
48
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
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 in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law :
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, 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 be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
© Copyright IBM Corp. 2012, 2013
49
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, 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 material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. 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 application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
50
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM's application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
If you are viewing this information softcopy, the photographs and color
illustrations 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 rights
reserved.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not be displayed.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International 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 and
trademark information" at http://www.ibm.com/legal/copytrade.shtml.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered
trademarks 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 and
Telecommunications Agency which is now part of the Office of Government
Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office
of Government Commerce, and is registered in the U.S. Patent and Trademark
Office.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer
Entertainment, Inc., in the United States, other countries, or both and is used under
license therefrom.
Notices
51
Java™ and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Privacy Policy Considerations
IBM Software products, including software as a service solutions, ("Software
Offerings") may use cookies or other technologies to collect product usage
information, to help improve the end user experience, and to tailor interactions
with the end user or for other purposes. In many cases, no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect
personally identifiable information.
If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.
For more information about the use of various technologies, including cookies, for
these purposes, see IBM's Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details/us/en
sections entitled "Cookies, Web Beacons and Other Technologies and Software
Products and Software-as-a Service".
52
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Index
A
C
L
accessibility x, 47
account
password requirements 23
restoration 23
adapter
attributes
account form 37
combination by action type 37
description 37
components required
connector 1
dispatcher 1
profile 1
configuration 21
features 1
installation
C API files 9
Dispatcher requirement 9
errors 25
JAR files 9
planning 5
roadmaps 5
steps 14
task sequence 5
Tivoli Directory Integrator RTC
connector 39
troubleshooting 25
verifying 15, 23
warnings 25
worksheet 6
z/OS UNIX file system 39
overview 1
post-installation tasks
configuration 21
language pack 21
SSL setup 21
verification 21
profile
creating service 17
customizing 21
dispatcher restart required 31
importing 16
objects that reference 33
removal 33
service creation 17
upgrade 31
upgrading 16
verifying 17
service 17
supported configurations
multiple servers 2
single server 2
task automation 1
uninstallation 33
upgrading 31
user account 17
attributes, description 37
C API files 9, 11
configuring, adapter 21
connector
files, removing 33
RemedyARSConnector 1
upgrading 31
customizing, adapter profiles 21
language pack
installation 23
same for adapters and server
logs, trace.log file 16
© Copyright IBM Corp. 2012, 2013
M
messages
error 27
warning 27
MS-DOS ASCII characters
D
dispatcher
installation requirement 1
installation, verifying 13
download, software 7
23
22
N
notices
49
E
education x
error messages
O
27
online
publications ix
terminology ix
overview, adapter 1
I
IBM
Software Support x
Support Assistant x
IBM Support Assistant 44
installation
adapter
Dispatcher requirement
errors 25
overview 1
profile 16
steps 14
troubleshooting 25
verifying 15
warnings 25
dispatcher, verifying 13
language pack 23
roadmap 5
verification
adapter 23
worksheet 6
ISA 44
ISIM_HOME definition 41
ITDI_HOME definition 41
J
JAR files
P
9
password
account
requirements 23
restoration 23
requirements 23
preinstallation, roadmap 5
problem-determination x
profile
architecture 1
editing on UNIX or Linux
importing 16
installation 16
publications
accessing online ix
list of ix
22
R
removing connector files
roadmap
installation 5
preinstallation 5
33
9, 11
S
K
knowledge bases
43
service
restart 15
start 15
stop 15
service, creating 17
software
download 7
53
software (continued)
prerequisites 6
requirements 6
website 7
support contact information
supported configurations
adapter 2
multiple servers 2
overview 2
single server 2
system files
C API files 9, 11
JAR files 9, 11
44
T
terminology ix
tivoli directory integrator 1
trace.log file 16
training x
troubleshooting
contacting support 44
error messages 27
getting fixes 44
identifying problems 25
searching knowledge bases
support website x
techniques 25
warning messages 27
43
U
uninstalling
adapter 33
from the directory integrator
upgrade
adapter 31
connector 31
33
V
verification
installation 23
operating system
prerequisites
requirements
software
prerequisites
requirements
vi command 22
6
6
6
6
W
warning messages
27
Z
z/OS UNIX file system, adapter
installation 39
54
IBM Security Identity Manager: Remedy AR System Adapter Installation and Configuration Guide
Printed in USA
SC27-4412-00