This edition applies to version 5.1 of Tivoli Identity Manager and to all subsequent releases and modifications until otherwise indicated in new editions.
Copyright International Business Machines Corporation 2003, 2013.
All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Installation and Configuration Notes.
Corrections to Installation Guide.
Default Port Number for Dispatcher
Customizing or Extending Adapter Features.
Support for Customized Adapters.
Welcome to the IBM Tivoli Identity Manager Remedy AR System Adapter.
These Release Notes contain information for the following products that was not available when the IBM Tivoli Identity Manager manuals were printed:
The Remedy AR System Adapter is designed to create and manage accounts on BMC’s Remedy AR System (Remedy). The adapter runs in “agentless” mode installed remotely from your Remedy server. The adapter uses the Remedy Java API to establish communication with the Remedy AR system server. The Remedy API provides a mechanism for adding, retrieving, updating, and removing data from the Remedy AR system server.
IBM recommends the installation of this Adapter (and the prerequisite Tivoli Directory Integrator) on each node of an Identity Manager WebSphere cluster. A single copy of the adapter can handle multiple Identity Manager Services. The deployment configuration is based, in part, on the topology of your network domain, but the primary factor is the planned structure of your Identity Manager Provisioning Policies and Approval Workflow process. Please refer to the Identity Manager Knowledge Center for a discussion of these topics.
The Identity Manager adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions and home directories Operations requested from the Identity Manager server will fail if the adapter is not given sufficient authority to perform the requested task. IBM recommends that this adapter run with administrative (root) permissions.
The ability to manage service groups is a new feature introduced in TIM 5.1. By service groups, TIM is referring to any logical entity that can group accounts together on the managed resource.
Managing service groups implies the following:
Create service groups on the managed resource.
Modify attribute of a service group.
Delete a service group.
Note that service group name change is not supported in TIM 5.1 release.
The Remedy AR System adapter does not support service groups management.
Component |
Version |
Release Date |
2013 June 02 23.24.57 |
Adapter Version |
5.1.3 |
Component Versions |
Adapter Build 5.1.3.15 Profile 5.1.3.15 Connector: 5.1.3.15 Dispatcher: 5.719 or higher |
Documentation |
Remedy AR System Adapter Installation and Configuration Guide Version 5.1 (SC23-9643-00) |
Enhancement # (FITS) |
Description |
Items included in current release |
|
34696 (20030) |
BMC Remedy AR System Server v7.6.04 |
BMC Remedy AR System Server v8.0 |
|
56604 (30576) |
Support for Remedy 8.1 |
Items included in 5.1.2 release |
|
OSDB |
Updated adapter to support Remedy 7.5 |
Items included in 5.1.1 release |
|
Initial release for Tivoli Identity Manager v5.1 |
|
MR090308436 |
ITIM Remedy adapter support for Remedy 7.1.00 |
MR020309436 |
Tivoli Identity Manager - Remedy Adapter Connection Use TCP Protocol |
MR0203095943 |
Tivoli Identity Manager - Remedy Adapter - Client wants to have TCP connection for Remedy Adapter Not RPC. |
MR1109054829 |
Remedy Agent won't reconcile if Remedy is configured to not allow 'unqualified searches' |
MR030308343 |
Remedy: Support for ARS without Help Desk |
MR1102064511 |
Remedy: enhance the adapter to work with custom remedy forms |
CMVC# |
APAR# |
PMR# / Description |
Items closed in current release |
||
None |
CMVC# |
APAR# |
PMR# / Description |
N/A |
N/A |
Limitation on length of Remedy Login Name Login Name (eruid) is supported to maximum of 244 characters because of Remedy AR System API limitation. |
N/A |
N/A |
Error on “Dynamic Group Access” Adapter returns attribute level failure for "Dynamic Group Access" attribute during USER ADD and USER MODIFY operations even though it is set on Remedy AR System server. Work around: If Customer wants to set value for attribute "Dynamic Group Access", then this attribute must be provided a value ends with semicolon. For example, 'User1'; |
N/A |
N/A |
Application License Attribute Application License is not supported attribute. It is hidden attribute, but Customer can bring it to TIM Account Form using Form Customization Feature of TIM and use it. |
N/A |
N/A |
Limitations on removing Remedy attributes Replacing with blank values for following attributes from TIM Account Form will set 0 on Remedy AR System server. (a) Number of Days Before Expiration (b) Number of Warning Days (c) Days After Expiration Until Disablement NOTE: use caution when defining provisioning policy attributes on these fields since the Recon will bring back a “0” value not a blank or Null. |
N/A |
N/A |
AIX Test Connection error: Cannot load native libraries. On AIX platform, following error might occur during Test Connection: “ERROR [com.bmc.arsys.api.NativeLibraryLoader] - Could not load native library java.lang.UnsatisfiedLinkError: arjni71 (Not found in java.library.path)” Solution: Refer to C API files for AIX platform mentioned in Table 6 of Remedy AR System Adapter Install Guide. Copy C API files for AIX platform to ITDI_HOME/jvm/jre/bin/classic folder. Navigate to the ITDI_HOME/jvm/jre/bin/classic directory. 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 Restart the Dispatcher service. |
N/A |
N/A |
HP-UX Test Connection error: Cannot load native libraries. On HP-UX platform, following error might occur during Test Connection: “ERROR [com.bmc.arsys.api.NativeLibraryLoader] - Could not load native library java.lang.UnsatisfiedLinkError: arjni71 (Not found in java.library.path)” Solution: Refer to C API files for HP-UX platform mentioned in Table 6 of Remedy AR System Adapter Install Guide. Copy C API files for HP-UX platform to ITDI_HOME/jvm/jre/lib/PA_RISC2.0/server folder. Navigate to the ITDI_HOME/jvm/jre/lib/PA_RISC2.0/server directory. 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 Restart the Dispatcher service. |
N/A |
N/A |
Upgrading Remedy from 7.x to 7.5 Upgrading between versions of the adapter and versions of Remedy are not supported. The solution is to uninstall and reinstall this version of the adapter. |
N/A |
N/A |
Dynamic and computed groups displayed in group list but cannot be added Dynamic and computed groups show up on the group list in the form for add or modify groups. However, they cannot be added because Remedy only allows adding Regular groups. Trying to add those groups to an account will results in failure or warning depending on the groups being added. |
N/A |
N/A |
Conflict with other adapters that use TDI xml processing Remedy libraries override some functionailities in TDI's xml processing, and will cause other adapters that depends on those features to malfunction. It is recommended that the remedy adapter be installed on a TDI system that is not shared by those adapters. Currently the Sharepoint adapter is confirmed to have this issue. Please refer to this technote for details |
See the IBM Tivoli Identity Manager Adapter Installation Guide” for detailed instructions.
The following corrections to the Installation Guide apply to this release:
New Installation Instructions This release of the adapter does not include an installer. Please follow the instructions below to install the connector:
The following configuration notes apply to this release:
By default the property “api.remote.on“ in TDI 7.0 is true which forces the Dispatcher to start on the default TDI remote port 1099. The Dispatcher default local port property value (16231) is overridden because TDI 7.0 sets the api.remote.on property value to "true". To start the dispatcher on local port 16231, the default remote port value must be set or the api.remote.on property must be set to "false".
See the installation guide and release notes for additional information.
Copying the Remedy AR System 7.5 Library Files
If you are managing a Remedy 7.5 Server, it is required that the following files be copied from the Remedy 7.5 Server installation directory and placed in the TDI setup BEFORE installing the adapter. After copying the files the dispatcher must be restarted.
Following is a list of files for the various platforms.
1) WINDOWS platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem |
ITDI_HOME\libs |
2) AIX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
3) HPUX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
4) SOLARIS platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
5) LINUX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
Note :
Add the TDI_HOME\libs folder to the Library path for the Unix platforms.
(1) For AIX set the environment variable LIBPATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
(2) For HPUX set the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
(3) For Solaris and Linux set the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
Copying the Remedy AR System 7.6.04 Library Files
If you are managing a Remedy 7.6.04 Server, it is required that the following files be copied from the Remedy 7.6.04 Server installation directory and placed in the TDI setup BEFORE installing the adapter. After copying the files the dispatcher must be restarted.
Following is a list of files for the various platforms.
1) WINDOWS platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem |
ITDI_HOME\libs |
2) AIX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
3) HPUX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
4) SOLARIS platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
5) LINUX platform:
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ITDI_HOME\jars\3rd party\others |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
|
C:\ Program Files\BMC Software\ ARSystem\Arserver\bin |
ITDI_HOME\libs |
Note :
Add the TDI_HOME\libs folder to the Library path for the Unix platforms.
(1) For AIX set the environment variable LIBPATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
(2) For HPUX set the environment variable SHLIB_PATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
(3) For Solaris and Linux set the environment LD_LIBRARY_PATH to /opt/IBM/TDI/V7.0/libs path where /opt/IBM/TDI/V7.0 is TDI 7.0 installation directory.
Copying the Remedy AR System 8+ Library Files
If you are managing a Remedy Server, it is required that the following files be copied from the Remedy Server installation directory and placed in the TDI setup BEFORE installing the adapter. After copying the files the dispatcher must be restarted. In the information below, VerNum refers to the version number of the file found in respective Remedy installation.
In addition to the table below, you also need to copy log4jVerNum from ITDI_HOME\jars\3rd party\others to ITDI_Home\jvm\jre\lib\ext
Following is a list of files for all platforms.
File Name |
Location to be taken from the Server |
Location to be placed in TDI setup |
|
ARS_SYSTEM_HOME\Arserver\api\lib |
ITDI_Home\jvm\jre\lib\ext |
|
ARS_SYSTEM_HOME\midtier\WEB-INF\lib |
ITDI_Home\jvm\jre\lib\ext |
Note :
Add the TDI_HOME\libs folder to the Library path for the Unix platforms.
(1) For AIX set the environment variable LIBPATH to /opt/IBM/TDI/<TDI_VERSION>/libs path where /opt/IBM/TDI/<TDI_VERSION> is TDI installation directory.
(2) For HPUX set the environment variable SHLIB_PATH to /opt/IBM/TDI/<TDI_VERSION>/libs path where /opt/IBM/TDI/<TDI_VERSION> is TDI installation directory.
(3) For Solaris and Linux set the environment LD_LIBRARY_PATH to /opt/IBM/TDI/<TDI_VERSION>/libs path where /opt/IBM/TDI/<TDI_VERSION> is TDI installation directory.
The Identity Manager adapters can be customized and/or extended. The type and method of this customization may vary from adapter to adapter.
Customizing and extending adapters requires a number of additional skills. The developer must be familiar with the following concepts and skills prior to beginning the modifications:
Note: If the customization requires a new Tivoli Directory Integrator connector, the developer must also be familiar with Tivoli Directory Integrator connector development and working knowledge of Java programming language.
Tivoli Identity Manager Resources:
Check the “Learn” section of the Tivoli Identity Manager Support web site for links to training, publications, and demos.
Tivoli Directory Integrator Resources:
Check the “Learn” section of the Tivoli Directory Integrator Support web site for links to training, publications, and demos.
Tivoli Identity Manager Adapter Development:
Adapter Development Tool
The Adapter Development Tool, ADT, is a tool used by IBM Tivoli Identity Manager (ITIM) customers and consultants to create custom TIM adapters. It reduces adapter delivery time by about 50% and it helps in the development of custom adapters. The Adapter development tool is available on the IBM Open Process Automation Library (OPAL).
The integration to the Identity Manager server – the adapter framework – is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a PMR is opened.
The IBM Tivoli Identity Manager Adapter was built and tested on the following product versions.
The IBM Tivoli Identity Manager Adapter was built and tested on the following product versions.
This adapter installs into Tivoli Directory Integrator (TDI) and may be installed on any platform supported by the TDI product and supported by the target system libraries or client, where applicable. IBM recommends installing TDI on each node of the ITIM WAS Cluster and then installing this adapter on each instance of TDI. Supported TDI versions include:
Adapter Installation Platform:
Tivoli Directory Integrator v7.0 with Fix Pack 1 or higher
Managed Resource:
BMC Remedy AR System Server v7.5
BMC Remedy AR System Server v7.6.04
BMC Remedy AR System Server v8.0
BMC Remedy AR System Server v8.1
IBM Tivoli Identity Manager:
Identity Manager v5.1
Please note that there are no Remedy ARS DLLs available for 64-bit Windows OS prior to ARS version 7.6.04 SP1. Please refer to http://remedy.ncsu.edu/project/documentation/files/701Matrix.xls for additional information on Remedy ARS compatibility.
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:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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 may 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.
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
2ZA4/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 information 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 measurements 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.
The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM
IBM logo
Tivoli
Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
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.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.
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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the U.S., 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.
IT Infrastructure Library® is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Other company, product, and service names may be trademarks or service marks of others.
End of Release Notes