Open Text RMLink For SAP Solutions 9 7 1 Installation Guide

Installation Guide
Open Text RMLink for SAP Solutions

9.7.1
The Open Text RMLink for SAP Solutions installation guide

describes the installation of the Open Text RMLink for SAP
Solutions components.
RMSAP090701-IGD-EN
Installation Guide
Open Text RMLink for SAP Solutions 9.7.1
RMSAP090701-IGD-EN
Rev.: 07. May 2009
This documentation has been created for software version 9.7.1.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
E-mail: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
Copyright © by Open Text Corporation, Open Text Inc.

Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, Great Minds Working Together,
Livelink, Livelink ECM, Livelink ECM-eDOCS, Livelink MeetingZone, MeetingZone, B2BScene, B2BScene.com, Client/Surfer,
Collaboration, Creative Desktop, Further Faster, Hyperinnovation, Internet Anywhere ,Livelink IRIMS, IRIMS, IXOS, Livelink
OnTime, OnTime, Livelink Remote Cache, Microstar, MyLivelink, O & Design, Odesta, Odesta Helix, Odesta Livelink, Open
Text Intranet, Open Text Web Index, Personality +, Putting Knowledge To Work, Techlib, The Hyperlinked Organization, The
Source For Business Knowledge, Worksmart, and World Of E among others. This list is not exhaustive.
ACKNOWLEDGEMENTS
SAP®, R/3® and SAP ArchiveLink® are registered trademarks of SAP AG.
Adobe® is a trademark of Adobe Systems Incorporated.
Lotus® and Lotus Notes® are registered trademarks of Lotus Development Corporation. Domino is a trademark of Lotus
Development Corporation.
Microsoft®, Microsoft SQL®, and Microsoft SharePoint® are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Oracle® is a registered trademark of Oracle Corporation.
Netscape and the Netscape N and Ship's Wheel logos are registered trademarks of Netscape Communications Corporation in
the U.S. and other countries.
Firefox® is a registered trademark of the Mozilla Foundation.
Sentry Spelling-Checker Engine Copyright © 2000 Wintertree Software Inc.
WordNet 2.0 Copyright © 2003 by Princeton University. All rights reserved.
Outside In® Viewing Technology © 1992-2002 Stellent Chicago, Inc. All rights reserved. Outside In® HTML Export © 2002
Stellent Chicago, Inc. All rights reserved.
Portions of eDOCS DM are copyrighted by DataDirect Technologies, 1991-2002.
All other products or company names are used for identification purposes only, and are trademarks of their respective own-
ers. All rights reserved.
Table of Contents
1 Introduction ............................................................................... 5
1.1 Product documentation ............................................................................ 6
1.2 Contact information .................................................................................. 7
2 Checking prerequisites............................................................. 9
2.1 Required knowledge ................................................................................ 9
2.2 Terms and definitions............................................................................... 9
2.3 SAP prerequisites .................................................................................... 9
2.4 Enterprise Library Services prerequisites .............................................. 10
2.5 Installation tool ....................................................................................... 11
2.6 Password control.................................................................................... 11
3 Installing package ................................................................... 13

4 Upgrading ................................................................................ 15
4.1 Upgrading to Open Text RMLink for SAP Solutions 9.7.1 ..................... 15
4.2 Upgrading the SAP system .................................................................... 15
4.2.1 Exchange upgrades ............................................................................... 15
5 Performing post-installation tasks in Enterprise Library

Services ................................................................................... 17
5.1 Configuring storage provider.................................................................. 17
5.2 Installing SAP SSO libraries .................................................................. 19
5.3 Creating Livelink users for SAP users ................................................... 20
5.4 Creating Enterprise Library Services application................................... 22
5.5 Creating RM classification (optional) ..................................................... 24
5.6 Importing folder and item type ............................................................... 25
5.7 Setting up authorization for records in Livelink ...................................... 27
5.8 Creating system categories in Livelink................................................... 28
5.9 Installing Open Text Advanced Item Management (optional)................ 29
5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise
4.70 only) ............................................................................................... 29
5.10.1 Installing SAP Java Connector module.................................................. 29
5.10.2 Installing RMLink RFC Service .............................................................. 30
5.10.3 Configuring RMLink RFC Service .......................................................... 31
5.10.4 Troubleshooting RMLink RFC Service................................................... 33
RMSAP090701-IGD-EN Installation Guide iii

Table of Contents
6 Performing post-installation tasks in SAP .............................35

6.1 Defining SAP roles ................................................................................. 35
6.2 Using the IMG function .......................................................................... 36
6.3 Setting up SAP authentication (SAP ERP 6.0 only) .............................. 37
6.4 Creating HTTP connection and logical port for Enterprise Library
Services (SAP ERP 6.0 only)................................................................. 40
6.5 Creating TCP/IP connection for RMLink RFC Service (SAP R/3
Enterprise 4.70 only) .............................................................................. 44
6.6 Maintaining Enterprise Library server settings....................................... 47
6.7 Activating the RMLink SSO HTTP service............................................. 49
6.8 Activating business functions (SAP ERP 6.0 only) ................................ 50
6.9 Scheduling job for removing deleted records ........................................ 51
6.10 Maintaining receiver modules for automatic declaration (optional,
SAP R/3 Enterprise 4.70 only) ............................................................... 52
6.11 Maintaining receiver modules for changed/created events (optional) ... 55
6.12 Maintaining receiver modules for automatic declaration of print lists
(optional, SAP ERP 6.0 only)................................................................. 56
6.13 Creating additional Livelink categories (optional) .................................. 59
6.14 Implementing business property provider (optional).............................. 60
7 Appendix ..................................................................................61
7.1 Single sign-on process for using Livelink............................................... 61
7.1.1 Configuring CAP Connector module...................................................... 62
7.2 Example for user synchronization.......................................................... 64
7.2.1 Exporting SAP users .............................................................................. 64
7.2.2 Using LDAP user management ............................................................. 67
7.2.3 Importing users in Livelink ..................................................................... 68
IDX Index .........................................................................................71
iv Installation Guide RMSAP090701-IGD-EN

Chapter 1
Introduction
Open Text RMLink for SAP Solutions (RMLink) allows you to declare SAP
ArchiveLink documents and print lists as records that are under control of Livelink
ECM – Records Management. The declaration can be performed automatically
during document archiving or interactively by an application user. In addition, the
declaration procedure can be performed in batch mode by an administrator.
Configurable declaration rules allow SAP-module-specific records declaration. Each
rule defines the classification, metadata, supplemental markings, etc. related to a
declaration context.
The Livelink disposition process eliminates expired records. Then RMLink reads the
corresponding notification messages and deletes all affected documents links in
SAP.
Note: RMLink also supports SAP R/3 Enterprise 4.70; however, the
functionality is limited due to platform restrictions. For 4.70, the
communication layer RFC is used instead of web service. The corresponding
restrictions and changes for RFC are listed in this document.
The following architecture diagram shows all components and gives an overview of
the RMLink functionality.
RMSAP090701-IGD-EN Installation Guide 5

Chapter 1 Introduction
RMLink resides in the SAP Business Suite ABAP Stack. It communicates via web
services with the Open Text Enterprise Library Services. The web services run on
Livelink with the same user as the one using RMLink. Therefore synchronization
between SAP and Livelink users via LDAP is required.
Figure 1-1: RMLink scheme
Note: RMLink 9.7.1 does not support an upgrade from any of the following
previous versions:
• Livelink ECM - Records Management for SAP Solutions 9.6.0
• Open Text Extended ECM for SAP Solutions 9.6.1
• Open Text - RMLink for SAP Solutions 9.7.0
1.1 Product documentation

This document describes the installation and upgrade process in the SAP
environment only.
For information on the other packages, see the individual installation guides. For
information on supported hardware and software platforms, check the Open Text
RMLink for SAP Solutions Release Notes.
Important
Note that there may be a more recent version of this installation guide in the
Open Text Knowledge Center. Look there for the most up-to-date version.
6 Installation Guide RMSAP090701-IGD-EN

1.2 Contact information
1.2 Contact information

Open Text Online is a single point of access for the product information provided by
Open Text. Depending on your role, you have access to different scopes of
information (see below for details).
You can access Open Text Online via the Internet at http://online.opentext.com/ or
the support sites at http://support.opentext.com/.
The following information and support sources can be accessed through Open Text
Online:
Knowledge Center
Open Text's corporate extranet and primary site for technical support. It is the
official source for:
• Open Text products and modules.
• Documentation for all Open Text products.
• Open Text Developer Network (OTDN): developer documentation and
programming samples for Open Text products.
• Patches for Open Text products.
The following role-specific information is available:
Partners
• Information on the Open Text Partner Program.
• Programs and support for registered partners.
Business Users
• Tips, help files, and further information from Open Text staff and other users
in one of the Open Text online communities
Administrators/developers
• Downloads and patches
• Documentation
• Product information
• Discussions
• Product previews
Feedback on If you have any comments, questions, or suggestions to improve our
documentation documentation, contact us by e-mail at documentation@opentext.com.
RMSAP090701-IGD-EN Open Text RMLink for SAP Solutions 9.7.1 7

Chapter 2
Checking prerequisites
2.1 Required knowledge

The following knowledge is required from the person dealing with the installation
as described in this document:
• In-depth knowledge of SAP administration tasks, in particular the SAP Add-On
Installation Tool (SAINT).
• In-depth knowledge of Open Text Enterprise Library Services, in particular its
Records Management, User Management and Directory Service components.
• Basic knowledge of the employed operating system.
2.2 Terms and definitions

When describing the installation, the following terms and definitions are used:
DPA Name of the SAP system used by Open Text

OTEXxxx Package with the ID xxx
<SID> System ID of the SAP system used by the user
<MDT> Client into which the import will take place
/usr/sap/trans/EPS/in Package directory in the user's SAP system
2.3 SAP prerequisites

RMLink supports the following SAP products:
• SAP ERP 6.0
• SAP R/3 Enterprise 4.70
Check the following prerequisites prior to installation:
SAP support packages
Check the latest version of the Release Notes in the Open Text Knowledge
Center for required support packages for the employed SAP system prior to
installation!

Chapter 2 Checking prerequisites
Transport system
The SAP application transport system is installed, or in other words, the jobs
RDDPUTPP and RDDIMPDP are set up in the correct clients (scheduled to run
periodically or event-triggered).
OSS notes
Check the OSS note 1117696 and make sure it is applied. This note is required
for the declare functionality in the attachment list of the generic object service
(GOS).
Check the OSS note 1255948 and make sure it is applied. This note is required
for the declare functionality of the print lists.
Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
• SAP 7.00 - OSS note 822380
• SAP 6.20 - OSS note 484219
• Installation information - OSS note 1040369
• SAPCAR tool - OSS note 212876
Patch levels
• Patch level for SAP ERP 6.0
The minimum requirement for software components SAP_BASIS and
SAP_ABA is release 700, patch level 15. This patch level is required for
enhanced functionality (e.g. additional icons in the GOS attachment list)
based on the SAP enhancement technology.
• Patch level for SAP R/3 Enterprise 4.70
The minimum requirement for software components SAP_BASIS and
SAP_ABA is release 620, patch level 63.
Note: The documentation is updated regularly; therefore, check for the latest
version in the Open Text Knowledge Center.
2.4 Enterprise Library Services prerequisites

Check the following prerequisites for Enterprise Library Services prior to
installation:
Installation of Enterprise Library Services and Archive and Storage Services
Both services must be installed.
ArchiveLink customizing
Customizing of the SAP system and the Archive and Storage Services must be
completed according to Part 3 "SAP basis customizing" in Open Text Archiving
and Document Access for SAP Solutions - Scenario Guide (ER-CCS).

2.5 Installation tool
Host/port for logical archive

Check that store and retrieval of ArchiveLink documents functions properly
with the server.
Important
The logical archive (OAC0 transaction) must use the Enterprise Library
Services host/port and not the Archive and Storage Services host/port.
Restrict access to the Archive and Storage Services host/port exclusively
to the Enterprise Library Services via a firewall configuration.
Important
Prior to installation, make sure that you have read the information in Open
Text Enterprise Library Services - Installation and Upgrade Guide (EL-IGD) and
Open Text Enterprise Library Services - Configuration and Scenario Guide (EL-
GGD) for the version 10.1.0.
2.5 Installation tool

RMLink uses the SAP Add-On Installation Tool (SAINT) for installation. SAINT
uses single PAT files (extension *.PAT) which integrate several transport files; these
collections are also called packages.
On the product CD, the PAT file is archived in a SAPCAR file (extension *.SAR) that
can be extracted using the SAPCAR command line tool. The SAPCAR file is located
in a DATA folder below the package folder named as the package and SAP release.
Note: The handling of the installation procedure within SAINT differs
depending on the SAP system used. For more details, see the respective SAP
documentation.
2.6 Password control

The package for RMLink is protected with a specific password. During installation,
this password is requested by SAINT.
For more details, see the following table:
Table 2-1: Installation packages and passwords
Package Release SAP Re- Designation Password

lease
OTEXRL 0971_700 SAP ERP Open Text RMLink for 4DBAF1FEF3
6.0 SAP Solutions
OTEXRL 0971_620 SAP R/3 Open Text RMLink for 4FBAF1FEF3
Enterprise SAP Solutions
4.70

Chapter 3
Installing package
This chapter describes the installation of the OTEXRL component of RMLink on an
SAP application server. Read also the chapter “Checking prerequisites” on page 9
with general information on installation in an SAP environment.
To install package:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
SAP Re- File Source path Target path
lease
SAP ERP 6.0 OTEXRL_INST_0971_70 INST_BAS_700\DATA\ /usr/sap/trans
0.SAR
SAP R/3 En- OTEXRL_INST_0971_62 INST_BAS_620\DATA\ /usr/sap/trans
terprise 4.70 0.SAR
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command:
SAPCAR –xvf <name of SAPCAR file>
The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
3. Carry out import of package as described in the respective SAP documentation.
4. After import has been finished, continue with the activation of the BC sets.
For every client, the Business Customizing Set (BC set) must be activated after
installation.
To activate BC set:
1. Execute the SCPR20 transaction.
The Business Customizing Set screen appears
2. Activate the /OTEXRL/RM_LINK_01 BC set.
Note: For more details, see the SAP documentation.

Chapter 3 Installing package
3. If you experience errors during BC set activation, repeat the respective

activation procedure up to 3 times.

Chapter 4
Upgrading
4.1 Upgrading to Open Text RMLink for SAP

Solutions 9.7.1
RMLink 9.7.1 does not support an upgrade with add-on delta upgrade packages
from any of the following previous OTEXRL add-on versions:
• Livelink ECM - Records Management for SAP Solutions 9.6.0
• Open Text Extended ECM for SAP Solutions 9.6.1
• Open Text - RMLink for SAP Solutions 9.7.0
4.2 Upgrading the SAP system

Disclaimer
When you upgrade your SAP R/3 Enterprise 4.70 to SAP ERP 6.0, the system
automatically recognizes that an SAP add-on is installed and requests the respective
upgrade package. This way the standard SAP upgrade procedure also updates the
Open Text RMLink for SAP Solutions add-ons to the relevant version.
Caution
If you import an upgrade into an SAP system with RMLink and the data of
the respective upgrade packages is not read (upgrade phase IS_SELECT), the
Open Text RMLink for SAP Solutions add-on (OTEXRL) will no longer work
after the upgrade procedure. Since the status of the system is then
inconsistent, Open Text can no longer accept any liability.
4.2.1 Exchange upgrades

When you have to upgrade your SAP system where Open Text RMLink for SAP
Solutions 9.7.1 is already installed, you must use the specific Open Text RMLink for
SAP Solutions exchange upgrade packages during the upgrade of the SAP system.
Note: Contact your Open Text consultant for planning your individual
upgrade strategy.

Chapter 4 Upgrading
The following exchange upgrades are supported:
Table 4-1: Exchange upgrades for SAP system
Upgrade from RMLink Upgrade to Upgrade package required

9.7.1 on
SAP R/3 Enterprise 4.70 SAP ERP 6.0 OTEXRL_UPGR_0971_700.SAR
To perform an exchange upgrade procedure:

1. Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEXRL_UPGR_0971_70 UPGR_BAS_700\DATA\ /usr/sap/trans
0.SAR
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command:
The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
3. Follow the standard SAP system upgrade instructions. During upgrade phase
IS_SELECT, select the upgrade type for the installed add-ons Upgrade with
SAINT Package (applies to OTEXRL package).
Note: No passwords are required for the upgrade packages.

4. After the upgrade, no activation of BC sets is necessary.

Chapter 5
Performing post-installation tasks in Enterprise
Library Services
After the actual installation of the package, you have to perform the following post-
installation tasks in Enterprise Library Services:
• Configuring storage provider
• Installing SAP SSO libraries
• Creating Livelink users for SAP users
• Creating Enterprise Library Services application
• Creating RM classification (optional)
• Importing folder and item types
• Setting up authorization for records in Livelink
5.1 Configuring storage provider

The storage provider configuration connects the logical archives of the Archive and
Storage Services with the Enterprise Library Services. Create a storage provider
configuration for each logical archive you plan to use in RMLink.
To configure the storage provider:

1. Invoke the Open Text Administration client and navigate within your
Enterprise Library Services to the Storage Providers entry.
2. In the Actions pane, select the New Provider entry.

Chapter 5 Performing post-installation tasks in Enterprise Library Services
The New Provider wizard displays.
3. Enter a name in the Name field and select the Enterprise Archive entry as type.
Click the Next button.

5.2 Installing SAP SSO libraries
Select an entry from the Logical Archive drop-down and select the default value
none from the Storage Tier drop-down.
Select the Delete Documents from Archive option.
4. Click the Next button and then the Finish button.
5.2 Installing SAP SSO libraries

RMLink requires the following SAP products for its Single Sign On functionality:
• SAP Security Library for Digital Signatures (SAPSECULIB)
• SAP SSO EXT lib for SAP logon ticket verification (SAPSSOEXT)
These products must be downloaded from SAP Software Distribution Center
(https://service.sap.com/swdc) and installed for your operating system.

To install libraries:
1. Download the SAPSECULIB and SAPSSOEXT SAR files for the operating system
that your Enterprise Library Services installation is using.
Tip: Use the Search for all Categories option with SAPSECULIB or
SAPSSOEXT to find the download area for these products.
2. Extract the SAPCAR files with the following command:

3. Copy the extracted files to the appropriate location:

• For Windows:
Copy the extracted files sapsecu.dll and sapssoext.dll to the %PATH%
folder.
• For Unix-like operating system:
Copy the extracted files libsapsecu.so and libsapssoext.so to the
$LD_LIBRARY_PATH directory.
The environment variable %PATH% or $LD_LIBRARY_PATH must be the one of the

user under which Tomcat or SAP NetWeaver runs.
5.3 Creating Livelink users for SAP users

For each SAP user working with RMLink, you must create a Livelink user with the
same user name as in SAP.
For test purposes or a small number of users, this can be done manually. For a large
number of SAP users this can achieved using a LDAP or Active Directory server
which synchronizes users between SAP and Livelink.
The following scheme shows the different software components involved in
exporting SAP users to Livelink. The SAP LDAP Connector exports users to a user
directory (LDAP or Active Directory). The user directory has a user-defined schema
specially customized for SAP users. The Livelink Directory Services Module imports
users from a user directory into Livelink.

5.3 Creating Livelink users for SAP users
Figure 5-1: Directory synchronization architecture
Use the SAP Directory Services (BC-SEC-DIR) to synchronize SAP user with an
LDAP/AD system; for details see
http://help.sap.com/saphelp_nw04/helpdata/en/e6/0bfa3823e5d841e10000000a1
1402f/content.htm .
Use the Livelink ECM – Directory Services module to synchronize Livelink users
with an LDAP/AD system.
Note: For more details see the respective SAP and Livelink documentation.
Tip: The “Example for user synchronization” on page 64 shows how to set up a
scenario with a Sun ONE Directory Server.

5.4 Creating Enterprise Library Services application

RMLink connects from the SAP system to the Enterprise Library Services using an
Enterprise Library Services application. ArchiveLink documents and print lists
declared as records by the SAP system can either be stored in the Enterprise
Workspace or in this application area. To restrict access to these documents, you
must set additional permissions on the application level.
To create an application:
Enterprise Library Services to the Applications entry.
2. In the Actions pane, select the New Application entry.

The New Application wizard displays.

5.4 Creating Enterprise Library Services application
3. Enter the required parameters.

Note: The value in the ID field must be the respective SAP system ID;
otherwise no connection between the SAP system and the Enterprise
Library Services will be established.
4. Select the required audit interests and click the Finish button to complete the
wizard.
The new application is now displayed in the list of applications.
To set permissions for application:

1. Go to the Livelink Administration page and select the Enterprise Library
Administration | Open the Enterprise Library Volumes entry.
2. Click the button of the application folder with the application ID you just
created and select the Permissions entry from the context menu.

The Permissions page displays.
The following permissions are set as a default:

• Full access rights to the volume for the user who created the application (in
our case the user is Admin)
• Only See and See Contents access rights for the group DefaultGroup and
Public Access
3. Add users and groups that must have access to this volume.
4. Grant full access to those users and groups that have to declare records within
SAP.
Note: If you choose to store records in Enterprise Workspace folders, set
the permissions accordingly. Users and groups that have to declare records
within SAP require full access to these folders.
5.5 Creating RM classification (optional)

If you do not have set up a classification tree in Livelink, you must create at least
one RM classification that can be used in RMLink.
For more details see the Livelink ECM - Classifications Resource Guide in the Open
Text Knowledge Center
(https://knowledge.opentext.com/knowledge/llisapi.dll/properties/13587516).

5.6 Importing folder and item type
5.6 Importing folder and item type

RMLink stores metadata for the declared ArchiveLink documents in the Enterprise
Library Services volume. On the installation CD in the folder ELS_TYPES you find
the following items:
• Folder type otx.sap.rm.Folder.xml
• Item type otx.sap.rm.Document.xml
• Item type otx.sap.rm.SystemArchiveLink.xml
• Item type otx.sap.rm.SystemPrintlist.xml
These files must be imported with the Administration client.
To import the folder type:

Enterprise Library Services to the Document Model entry and click the Folder
Types tab.
2. In the Actions pane, select the Import Types entry and navigate to the
otx.sap.rm.Folder.xml file provided in the folder ELS_TYPES on your
installation CD. Click the Open button to import the file.
The list of folder types displays the new folder type.

3. Select the new folder type, invoke the Properties dialog and click the
Classification tab.
4. Click the Set default classification option and click the Browse button to select
a classification.
To import the item type:

• In the Document Model entry, click the Item Types tab.
Repeat the above procedure for the following files:
• otx.sap.rm.Document.xml
• otx.sap.rm.SystemArchiveLink.xml
• otx.sap.rm.SystemPrintlist.xml
Note: A default classification must not be set.

5.7 Setting up authorization for records in Livelink
5.7 Setting up authorization for records in Livelink

The access rights to the records created by RMLink correspond to the access rights
used by the Enterprise Library Services application (see “Creating Enterprise
Library Services application” on page 21). In order to restrict the access in
accordance with your company policy, you have to create Livelink groups and set
the respective access rights on the classification level.
The following access rights (either directly, via a group, or via public access) are
required:
• To see records, users must have at least See Contents permission.
• To declare records, users must have at least Add Items permission.

Example 5-1: Authorization for records in Livelink

Records should be created for HR and Finance department; you could now separate
the records either by storing them in different locations or by classifying them
differently. To use the classification approach, create a Finance Livelink group and
add all the users that should have access to the Finance records; then create a similar
HR group. Assign the Finance group access rights to the Finance classification and
the HR group to the HR classification.
5.8 Creating system categories in Livelink

This RMLink version now stores all metadata in Livelink categories instead of using
Enterprise Library item types. The imported item types
otx.sap.rm.SystemArchiveLink and otx.sap.rm.SystemPrintList can be
copied to categories described below.
One can also create system categories manually, but copying the imported item
types ensures that no mandatory category attributes is missing.
To create system categories:

Administration | Open the Enterprise Library Types Volumes entry.
2. Browse to the folder named otx.sap.rm.SystemArchiveLink and open it.

5.9 Installing Open Text Advanced Item Management (optional)
3. Copy the category file otx.sap.rm.SystemArchiveLink.v to a different location

within the Enterprise Workspace. If required, you can change the category
name.
Caution
Do not delete the original category file under Open the Enterprise
Library Types Volumes.
4. Repeat the above procedure with the category file otx.sap.rm.SystemPrintList.v

in the otx.sap.rm.SystemPrintList folder.
Note: Note the location of the copied system category files

otx.sap.rm.SystemArchiveLink.v and otx.sap.rm.SystemPrintList.v. You will
need this information to configure new declarations with the SPRO transaction
in SAP.
5.9 Installing Open Text Advanced Item Management

(optional)
If you require MIME-type-specific metadata during creation, and if disposition
export to the format specified by the US DoD, then you have to download (from the
Knowledge Center) and install the Open Text Advanced Item Management
component.
5.10 Installing RMLink RFC Service on RCS Server

(SAP R/3 Enterprise 4.70 only)
SAP R/3 Enterprise 4.70 does not support web services. Therefore, the RMLink RFC
Service enables RMLink on SAP R/3 Enterprise 4.70 to communicate with the
Enterprise Library Services via RFC. The RMLink RFC Service has to be installed on
the Enterprise Library Services installation.
5.10.1 Installing SAP Java Connector module

Prior to installing the RMLink RFC Service, you must install the SAP Java Connector
(JCo) version 2.1.8 on the RCS server.
JCo is a toolkit that allows the RMLink RFC Service to communicate with any SAP
system.
Note: To download JCo, you must be an SAP customer or partner (with a valid
SAPnet (OSS) user ID); go to http://service.sap.com/connectors and follow
the download instructions.

To install the Java Connector module on Windows:

1. Make sure that the DLL files librfc32.dll and sapjcorfc.dll can be found
by Windows (for example by copying them into the <Windows
installation>\System32 folder).
2. Copy the sapjco.jar file to the <Tomcat installation>\common\lib folder

(or a similar path for NetWeaver).
During startup, the application server loads all libraries in this path and makes
them available to its applications, including the RCS server. Therefore, the
RMLink RFC Service, running under the RCS Server, will be able to access JCo
and use it to establish a communication with SAP servers.
3. Restart the application server.
To install the Java Connector Module on UNIX:

1. Make sure that the library files librfccm.so and libsapjcorfc.so can be
found by the operating system.
2. Make sure that the library files librfccm.so and libsapjcorfc.so can be
found by the application server (for example by copying them to the
$LD_LIBRARY_PATH path for the Tomcat application server).
3. Copy the sapjco.jar file to the <Tomcat installation>/common/lib

directory (or a similar path for NetWeaver).
4. Restart the application server.
5.10.2 Installing RMLink RFC Service

To install the RMLink RFC Service, execute the setup file (RMLink RFC Service-9.-
7.1.msi for Windows, setup.sh for UNIX ) provided on your installation CD on
the RCS server. The RCS server must to be running during the installation; once the
installation is finished, restart the RCS server server.
After the installation, verify the RMLink RFC Service is installed. In the Open Text
Administration, navigate toRuntime and Core Service | Configuration | RMLink
RFC Service and check the state of the services.

5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise 4.70 only)
Note: Make sure that your RCS server has a sufficient initial memory pool.
Refer to the Section 3.1.1.3 "Configuring Tomcat pool size" in Open Text
Runtime and Core Services - Installation Guide (ELCS-IGD) for memory pool size
recommendations (available in the Knowledge Center under:
https://knowledge.opentext.com/knowledge/llisapi.dll/open/13609768).
5.10.3 Configuring RMLink RFC Service

The RMLink RFC Service is configured in the Open Text Administration.
Note: The initial configuration supports a single SAP server (parameter
rmlink.maxservers = 1). If you plan to use the RMLink RFC Service with
multiple SAP servers, you must set the value of rmlink.maxservers to the
number of SAP servers and copy the complete server-specific set of parameters
(rmlink.server1.<xxx>) so that each additional SAP server gets its own set of
parameters (rmlink.server2…, rmlink.server3…, etc.).
To configure the RMLink RFC Service

1. In the Open Text Administration, navigate toRuntime and Core Service |
Configuration | RMLink RFC Service.
You see a list of all possible configuration parameters. Some parameters already
have a default value.
2. Set the required parameters.

The following table explains each configuration parameter.

Name Type Description Default
Value
rmlink.maxservers Numeric Number of SAP servers that com- 1
municate with the RFC Service
rmlink.sapusername. Enumera- Upon function calls, the RFC Service false
convert2lowercase tion will either lowercase or uppercase
the user in the SAP token for subse-
quent authentication of this user
with the CAP service. The value (true
or false) depends on whether the
Livelink users are defined in lower or
upper cases.
rmlink.server1.applic String SAP server system ID (example:
ationname DP1)
rmlink.server1.client String SAP server client number 800
rmlink.server1.hostn String SAP server host name
ame
rmlink.server1.poolsi Numeric Thread pool size for this SAP server 5
ze
rmlink.server1.progr String Name of the registered RFC Server RMLinkR
amid Program ID within SAP RFC Desti- FCSer-
nation configuration (SM59 transac- vice
tion)
rmlink.server1.rfctrac Boolean Enable or disable the RFC trace false
e (*.trc files log the entire RFC data
communication)
rmlink.server1.sapgw String SAP gateway host name for this
host server
rmlink.server1.sapgw String SAP gateway service for this server
service (example: sapgw01)
rmlink.server1.sapus String SAP user name to register the RFC
ername Service in the gateway; the user must
have the SAP role
/OTX/RM_RFCSERVICE assigned.
rmlink.server1.sapus Password SAP user password to register the

erpassword RFC Service in the gateway
rmlink.server1.sncna String SNC name for secure connections
me (same as defined in SAP registered
program)
rmlink.server1.sncsec Range SNC security level (value range 1 to 1
uritylevel 9)

5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise 4.70 only)
Name Type Description Default

Value
rmlink.server1.snclib String Path to the SNC library
rary
rmlink.server1.syste String SAP server system number (example:
mnumber 00)
rmlink.server1.unico Boolean SAP server Unicode support true
de
5.10.4 Troubleshooting RMLink RFC Service

The RMLink RFC Service features three log levels: ERROR, DEBUG, and TRACE
with ERROR being the default. The RMLink RFC Service writes its logs in the
rcs.log file located in the logging directory of your application server (e.g. <Tomcat
installation>\logs).
To change the default log level:

1. In the Open Text Administration, navigate toRuntime and Core Service |
Configuration | Logging.
2. Double-click the logger.RMLinkRFCService.loglevel entry or select it and click

Properties in the right Actions pane. Select the required log level.
An additional source of troubleshooting information is the RFC trace. To enable the

RFC trace, set the rmlink.server1.rfctrace configuration parameter to true and
restart the RFC Service. As a result, SAP JCo will begin to log the complete RFC data
communication in *.trc files. With a Tomcat server, these *.trc files are located
directly in the <Tomcat installation> directory.

Chapter 6
Performing post-installation tasks in SAP
Before using the RMLink functions, the following post-installation and customizing
tasks in SAP are required:
• Defining SAP roles
• Using the IMG function
• Setting up SAP authentication
• Creating HTTP connection and logical port for Enterprise Library Services
• Creating HTTP connection and logical port for CAP services
• Creating logical port for Web service proxy class
• Maintaining Enterprise Library server settings
• Scheduling job removing deleted records
• Activating GOS enhancements
The following additional post-installation and customizing tasks in SAP are
optional:
• Maintaining receiver module /OTX/RM_UPD_RECORD_VIA_EVENT for changed
events and receiver module /OTX/RM_CRT_RECORD_PRINTLIST for created events
• Creating additional Livelink categories
• Implementing business property provider
6.1 Defining SAP roles

In order to use the RMLink functions in SAP, you must add and assign specific roles
in SAP. The following roles are required:
/OTX/RM_USER
Role for RMLink application users (e.g. FI clerk); this role allows an SAP user to
declare ArchiveLink documents as records, search Livelink and show record
details.
/OTX/RM_ADMIN
Role for SAP administrator; this role allows for the post-installation and
customizing steps.

Chapter 6 Performing post-installation tasks in SAP
/OTX/RM_RMCSERVICE
Role for the technical user of the RMLink RFC Service.
6.2 Using the IMG function

You start all following post-installation tasks from a central menu in SAP's IMG
function.
To invoke the IMG:

1. Execute the SPRO transaction.
2. Click the SAP Reference IMG button.
Navigate to the Open Text RMLink for SAP Solutions section and open it.

6.3 Setting up SAP authentication (SAP ERP 6.0 only)
3. Select the required procedure.

Tip: The column Additional information indicates whether the procedure
is mandatory or optional.
6.3 Setting up SAP authentication (SAP ERP 6.0

only)
The SAP authentication comprises the following steps:
• Exporting the System PSE (Personal Security Environment) in SAP.
• Creating an SAP driver in the Open Text Administration client.
To export a certificate:
1. Click the Export System PSE Certificate to File System entry in the IMG.
The Trust Manager dialog opens.
2. Open the System PSE section and check whether there is a certificate in this
folder.
If this is not the case, create a new one (see SAP Help Portal
(http://help.sap.com/saphelp_nw70/helpdata/de/0e/fb993af7700577e1000000
0a11402f/frameset.htm) for details).
3. Make sure the certificate's CN value in the Owner field equals to the system ID
(in this case, the value is DP1).
If this is not the case, delete the current one and create a new one.

4. Click the Veri. PSE button. If there are more certificates available, the following
popup is displayed:
5. Click the Yes button and copy the PSE file to an appropriate location on the
Enterprise Library Services server.
To create an SAP driver in the Open Text Administration client:

1. Invoke the Open Text Administration client and open your target library.
2. Select Runtime and Core Services | Authentication | Drivers.
3. In the Actions pane, select the New Driver entry.

6.3 Setting up SAP authentication (SAP ERP 6.0 only)
The New Driver wizard displays.
4. Enter a name, a description and select the SAP entry from the Type drop-down.

5. Enter the path of the exported system PSE file on the Enterprise Library Services
server in the pabFile1 field.
6. Click the Next button and then the Finish button.
Note: If Runtime and Core Services run on a Unix-like operating system, you
have to specify the newly created driver in the Properties dialog. Click the
Advanced tab and enter in the ssfLirary field the value libsapsecu.so.
6.4 Creating HTTP connection and logical port for

Enterprise Library Services (SAP ERP 6.0 only)
RMLink connects to Open Text Runtime and Core Services using HTTP connections
and logical ports. You must create an HTTP connection to your Enterprise Library
Services installation. After creation of the HTTP connection, you must create a
corresponding logical port.

6.4 Creating HTTP connection and logical port for Enterprise Library Services (SAP ERP 6.0 only)
To create an HTTP connection:

1. Click the Create Connection for Enterprise Library Services entry in the IMG.
The Configuration of RFC Connections dialog opens.
2. Click the button.
3. Enter a name in the RFC Destination field and select value G in the Connection
Type field.
Enter a description and click the button to save your entries.

4. In the Technical Settings tab, enter the host and port name of your Enterprise
Library Services installation in the fields Target Host and Service No. fields.
Enter the value /ot-elib/services/EnterpriseLibrary in the Path Prefix field.
5. Select the Logon & Security tab.
6. In the Logon Procedure group, select the No Logon option button and select the
Send SAP Logon Ticket check box.
8. Click the Connection Test button.

6.4 Creating HTTP connection and logical port for Enterprise Library Services (SAP ERP 6.0 only)
9. Check that the value in the Status HTTP Response field is 200.
To create a logical port:

1. Click the Create Logical Port for WS Proxy Class entry in the IMG.
The Display/Create Logical Port dialog opens.
2. Click the button in the Proxy Class field and select the
/OTX/CO_RMELENTERPRISE_LIBRARY element from the list.
3. Enter a new value in the Logical Port field and select the Default Port check
box.

5. Enter a description for the logical port in the Description field.

Click the Call Parameters tab and enter your new HTTP destination created for
the Enterprise Library Services in the HTTP Destination field.
6. Click the button to check the new logical port.
Check that the message in the status bar reads No errors found in
configuration.
7. Click the button and click the button to activate the logical port.
6.5 Creating TCP/IP connection for RMLink RFC

Service (SAP R/3 Enterprise 4.70 only)
This step is required if you use the RMLink RFC Service to communicate between
Enterprise Library Services and SAP R/3 Enterprise 4.70, which does not support
web services.
You must first create a TCP/IP connection to your RMLink RFC Service.
To create a TCP/IP connection:

1. Click the Create Connection for Enterprise Library Services entry in the IMG.

6.5 Creating TCP/IP connection for RMLink RFC Service (SAP R/3 Enterprise 4.70 only)
The Display and maintain RFC destinations dialog opens.
2. Click the Create button.
3. Enter a name in the RFC destination field and select value T in the Connection
type field. Enter a description and click the button to save your entries.

4. In the Technical settings tab,

select the Registered Server Program option and enter the program ID of your
RMLink RFC Service installation (see “rmlink.server1.programid” on page 32)
in the Program ID field.
5. Select the Special Options tab.

6.6 Maintaining Enterprise Library server settings
6. In the Character Width in Target System group, select the Unicode option if
your system is set to Unicode.
7. Click the Unicode Test button and check the result of the test.
9. Click the Test Connection button and check the result of the connection test.
6.6 Maintaining Enterprise Library server settings

All parameters for a connection to an Enterprise Library Services server are collected
with an Enterprise Library ID. You have to create a new Enterprise Library ID.
To create an Enterprise Library ID:

1. Click the Maintain Enterprise Library Servers Settings entry in the IMG.
2. Click the New Entries button.

For SAP ERP 6.0:
For SAP R/3 Enterprise 4.70:
3. Enter a new Enterprise Library ID.

4. Enter a description and specify the following parameters:
WS: ELS logical port (SAP ERP 6.0 only)
Enter the name of the ELS logical port you created before.
RFC alt. Comm. (SAP R/3 Enterprise 4.70 only)
RFC destination for alternative communication implementation; enter the
name of the RFC TCP/IP connection to the RMLink RFC Service you created
before (see page 45).

6.7 Activating the RMLink SSO HTTP service
Livelink Protocol, Livelink Hostname, Livelink Port and Livelink Path

These URL parameters define how to display the Enterprise Server Web UI.
Note: Make sure you enter the full Livelink path including the domain
name.
SSO is not supported
The cookie IP comparison setting (see “Single sign-on process for using
Livelink” on page 61) might be insufficient for RMLink's SSO connection to
Livelink dialogs.
In this case, select the checkbox so that RMLink avoids SSO and proposes
log-on dialogs instead, whenever a Livelink dialog is required.
5. Click the (Save) button.
The new entry is displayed in the list of server settings.
6.7 Activating the RMLink SSO HTTP service

To activate RMLink SSO HTTP service:
1. Click the Activate HTTP Service entry in the IMG.
2. Open the default_host host.
3. Open the sap namespace.
4. Open the public group.

5. Select the otx_rmuic_sso item, and select Activate Service command from the
context menu.
6.8 Activating business functions (SAP ERP 6.0

only)
You must activate the business functions to enhance the following functions:
• the GOS attachment list
• the OADR print list transaction
The business functions activate two additional menu buttons (Declare as Record
and Display Record Details) as well as some additional columns like the one with
the status icons.
To activate business functions:

1. Click the Activate Business Functions entry in the IMG.
2. Activate both the /OTX/RM_BF_DISP_PRINTLIST and the
/OTX/RM_BF_GOS_ATTACHMENT option by clicking the On checkbox in
the Planned Status column.
3. Click the Activate Changes button.

6.9 Scheduling job for removing deleted records
6.9 Scheduling job for removing deleted records

The report /OTX/RM_REMOVE_LINKS deletes the ArchiveLink entries for documents
that no longer exist in the Enterprise Library Services. This occurs due to the
disposition policy set up in your Enterprise Library Services.
You can schedule the execution of the /OTX/RM_REMOVE_LINKS report according to
your needs. Depending on the dispositions on your system, a periodical or only
manual execution can be necessary.
To schedule job:
1. Click the Schedule Job Removing Deleted Records entry in the IMG.
The Define Background Job dialog opens.
2. Click the Step button.

3. Enter the value /OTX/RM_REMOVE_LINKS in the Name field of the ABAP

program group.
6.10 Maintaining receiver modules for automatic

declaration (optional, SAP R/3 Enterprise 4.70
only)
This step is required if you want to declare any new ArchiveLink entry
automatically as record.
You must activate the creation of the ASSIGNED event. After activation, a receiver
module must be linked to the ASSIGNED event for every BOR Object Type were
ArchiveLink entries should be declared automatically.
Caution
Do not perform this step in SAP ERP 6.0; this step is only required for SAP
R/3 Enterprise 4.70.

6.10 Maintaining receiver modules for automatic declaration (optional, SAP R/3 Enterprise 4.70 only)
To activate the creation of the ASSIGNED event:

1. Click the Activate Receiver Module Events entry in the IMG.
The ArchiveLink: Basic Settings dialog opens.
2. Click the Generate Event <Object Type>.ASSIGNED option.


To link the receiver module to the ASSIGNED event of the Object Type:
Note: The following procedure must be repeated for every BOR Object Type
were ArchiveLink entries should be declared automatically.
1. Click the Maintain Receiver Module Events entry in the IMG.
2. Specify the following parameters:

Object Category
BOR Object Type
Object Type
Select the object type were ArchiveLink entries should be declared
automatically
Event
ASSIGNED
Receiver Type
Arbitrary
Receiver Call
Function module
Receiver Function Module
/OTX/RM_CRT_RECORD_VIA_EVENT
Destination of Receiver
NONE

6.11 Maintaining receiver modules for changed/created events (optional)
Leave all other settings as in the example above.

Note: For automatic declaration, the check box Automatic in the assignment of
declaration ID to object and document type must also be selected. For details,
see Section 3 "Assigning a declaration ID to object and document type" in Open
Text RMLink for SAP Solutions 9.7.1 - Administration Guide (RMSAP-AGD).
6.11 Maintaining receiver modules for

changed/created events (optional)
This step is required if you want to set up a scenario where a change of the metadata
in a business transaction should automatically update the metadata of the records
linked to this business object.
ArchiveLink documents linked to the finance business object BKPF are declared as
records. Some metadata like the reference number are stored at the record item type
during declaration. At a later stage, the reference number changes; this should
automatically update the reference number in the item type.
Depending on the SAP version used, the following screens might look different on
your system.
Figure 6-1: Example entry Event Type Linkages

Object Category
BOR Object Type
Object Type
Select the type that you want to update.
Event
Changed
Receiver Type
Arbitrary
Receiver Call
Function module
Value may be either
/OTX/RM_UPD_RECORD_VIA_EVENT for a complete update (i.e. title, location,
metadata, classification, and security clearance) or
/OTX/RM_UPDMD_RECORD_VIA_EVENT for an update of the metadata only
Destination of Receiver
Set this field to NONE for SAP R/3 Enterprise 4.70, leave this field empty for
SAP ERP 6.0.
Note: In some application areas, business events can be activated using SAP
Change Documents.
6.12 Maintaining receiver modules for automatic

declaration of print lists (optional, SAP ERP 6.0
only)
This step is required if you want to set up a scenario where print lists that are
archived should be declared automatically as records documents.
You must activate the creation of the PRINTLIST.CREATED event. After activation, a
receiver module must be linked to the CREATED event of the PRINTLIST Object Type.
Caution
RMLink supports print lists only in SAP ERP 6.0.

6.12 Maintaining receiver modules for automatic declaration of print lists (optional, SAP ERP 6.0 only)
To activate the creation of the CREATED event:

1. Click the Activate Events for RMLink Receiver Function Modules entry in the
IMG.
The ArchiveLink: Basic Settings dialog opens.
2. Click the Trigger Event PRINTLIST.CREATED option.


To link the receiver module to the CREATED event:

1. Click the Maintain Receiver Module Events entry in the IMG.
2. Specify the following parameters:

Object Category
BOR Object Type
Object Type
PRINTLIST
Event
CHANGED
Receiver Type
Arbitrary
Receiver Call
Function module
/OTX/RM_CRT_RECORD_PRINTLIST


6.13 Creating additional Livelink categories (optional)
Note: For automatic declaration of printlists, the check box Automatic in the
assignment of declaration ID to object and document type must also be
selected. For details, see Section 3 "Assigning a declaration ID to object and
document type" in Open Text RMLink for SAP Solutions 9.7.1 - Administration
Guide (RMSAP-AGD).
6.13 Creating additional Livelink categories (optional)

This step is required if you want to declare records using your own property
provider (see “Implementing business property provider (optional)” on page 60).
To create a Livelink category:

1. Click the Create Enterprise Library Item Type entry in the IMG.
The Create a new Enterprise Library Services item type dialog opens.
2. Create a new Enterprise Library Services item type for each property provider
that should be used.
Specify the following parameters:
Property Provider
Choose one of the business property providers available in the value list.
Enterprise Library ID
Choose one of the configured IDs.
New Enterprise Lib. Item Type
Enter a name that features at least one dot to define a namespace.
New Item Type Description
Enter a description that states the purpose of the type.
3. Click the button
A success message is displayed.
Note: If an error message “Cannot form valid challenge” is displayed,
check the existence of an authentication driver (PSE file) using the Open
Text Administration client.

To create additional categories from the newly created item type:

Administration | Open the Enterprise Library Types Volumes entry.
2. Browse to the folder named like the item type you just created and open it.
3. Copy the contained category file to a different location within the Enterprise
Workspace. If required, you can change the category name.
Caution
Do not delete the original category file under Open the Enterprise
Library Types Volumes.
Note: Note the location of the copied category file. You will need this
information to configure new declarations with the SPRO transaction in SAP.
6.14 Implementing business property provider

(optional)
This step is required if you want to enhance the basic metadata with more business
properties. RMLink ships with the following default business property provider
classes:
• /OTX/RM_CL_PP_ALINK
This provider class allows to store records with all the ArchiveLink properties
like Document ID, Business Object Type, etc.
• /OTX/RM_CL_PP_PRINTLIST
This provider class allows to store print lists.
To enhance the basic metadata you have to derive a new class from the default
business property provider classes. All the elements needed for this implementation
are collected in the package interface of the package /OTX/RM.
Note: This interface may change with the next version of RMLink. Be aware
that possible upgrade tasks will not be covered by RMLink.

Chapter 7
Appendix
7.1 Single sign-on process for using Livelink

When invoking the Livelink HTML dialogs and the Livelink HTML search page
within the SAP GUI, RMLink uses a single sign-on (SSO) process to avoid manual
authentication. This SSO process has the following restrictions:
• The SAP HTTP server and the Livelink server must share both the second-level
and the top-level domain name (e.g. the SAP HTTP server may be
ottawa.sample.com and the Livelink server may be toronto.sample.com).
The option Never expire must be set for the Livelink security parameter in the
section Cookie Authentication Information.
Note: RMLink generates in the SSO mode a 2-hour persistent CAP cookie.
Make sure that your Web browser settings allow cookies.
If either SSO cannot be achieved in your server and desktop environment or SSO is
turned off in the LES configuration (see “Maintaining Enterprise Library server
settings” on page 47), the RMLink functionality is restricted as follows:
• The interactive declare dialog (see Section 3 "Assigning a declaration ID to object
and document type" in Open Text RMLink for SAP Solutions 9.7.1 - Administration
Guide (RMSAP-AGD)) will not allow to select RSI, categories and cross
references.
• The declaration customizing will not support value help for selecting categories
and root folder. The user will have to enter these values manually.
However, if the LES configuration does turn off SSO, these restrictions do not apply.
Instead, each time RMLink requests a Livelink popup dialog, an intermediate
popup caller dialog appears. Both the popup caller dialog and the target Livelink
dialog may show a log-on screen.
For the caller dialog, the logon screen appears only once, as long as a SAPGUI
session or the SAP Logon application is open. For the Livelink popup dialog, a
logon is always necessary unless an instance of the Web browser has been open
since the latest logon.
Tip: In order to avoid logging in every time a Livelink dialog pops up under
Windows, keep an instance of Microsoft Internet Explorer open.

Chapter 7 Appendix
To configure security parameters:

1. Go to the Livelink Administration page.
2. Select the Configure Security Parameters entry in the Server Configuration
section.
3. In the Cookie Authentication Information group, select the Never Expire

option.
7.1.1 Configuring CAP Connector module

The single sign-on (SSO) process requires the Livelink CAP Connector module 9.7.1.
For details see Application Note - What is the LES 9.7.1 CAP Connector in the Open
Text Knowledge Center
(https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=13585347
&objAction=properties).
To configure the Livelink CAP Connector:

1. Go to the Livelink Administration page.
2. Select the Configure CAP Web Service parameters entry in the CAP Connector
Administration section.
3. Check that the CAP Web Service URL and CAP Web Service Name parameters
are set to the default as seen below.

7.1 Single sign-on process for using Livelink
4. Select the Set CAP ID to Livelink user mapping entry in the CAP Connector
Administration section.
5. Check that the CAP ID to Livelink user mapping is set to the default option
Livelink user name as seen below.

Chapter 7 Appendix
7.2 Example for user synchronization

7.2.1 Exporting SAP users
Figure 7-1, Figure 7-2 and Figure 7-3 show an example of how to use the LDAP
transaction to configure an LDAP server. Figure 7-3 shows the mapping of SAP
attributes to LDAP schema attributes.
Figure 7-1: LDAP server configuration in SAP (1/3)

Figure 7-4 and Figure 7-5 illustrate the use of the RSLDAPSYNC_USER transaction to
export users. It is important to select the desired action to be taken in case some
users exist in both SAP and in the external user directory. Since this transaction can
trigger an export, an import, or a combination of both, it is also important to
properly select the desired actions.

Chapter 7 Appendix
Figure 7-4: Export of SAP users (1/2)
Figure 7-5: Export of SAP users (2/2)

7.2.2 Using LDAP user management

Figure 7-6 shows the Sun ONE Directory Server with a specific user schema for SAP
users. This schema is provided by SAP and must be imported in the directory
server. For Sun ONE Directory Server, it is important to make this schema a child of
the inetorgperson object class.
Figure 7-6: SAP user schema
Figure 7-7 shows some SAP users exported in the Sun ONE Directory Server.

Chapter 7 Appendix
Figure 7-7: SAP user schema
7.2.3 Importing users in Livelink

Figure 7-8 to Figure 7-12 show the import of users from a directory server to
Livelink.
Figure 7-8: Importing users in Livelink (1/5)
Figure 7-9 shows the configuration of a directory server.

Figure 7-10 to Figure 7-12 show the import process.

Chapter 7 Appendix

Index
I
Installation 13
packages 11
A prerequisites 9, 10
Activating business functions 50 Installation packages 11
Automatic declaration
Print list 56
J
Record 52
JCo
Download 29
B
BC set 13
L
Business property provider 60
LDAP user management 67
Livelink categories 28
C Livelink security parameters 61
CAP Web Service 62
Category files 28
M
Classification tree 24
MIME-type-specific metadata 29
Cookies 61
O
D
Open Text Advanced Item Management
Disposition export 29
29
DoD format 29
Open Text Online 7
Domain names 61
Open Text Runtime and Core Services 40
OSS notes 9
E otx_rmuic_sso 49
Enterprise Library Services
post-installation 17
P
Enterprise Library Services application 21
Package
Event
Exchange upgrades 16
Receiver module 52, 55
Packages 11
Exchange upgrade 15
Password control 11, 15
PAT files 11
F Patch levels 9
Feedback 7 post-installation 17, 35
Prerequisites 9
H Print list
HTTP connection 40 Automatic declaration 56

Index
Receiver module 56 Transaction

OAC0 11
R OADR 50
Receiver modules 52, 56 RSLDAPSYNC_USER 65
Record SCPR20 13
Automatic declaration 52 SPRO 36
Removing deleted records 51 Transport system 9
Report
/OTX/RM_BF_DISP_PRINTLIST 50 U
/OTX/RM_BF_GOS_ATTACHMENT 50 Upgrade
/OTX/RM_REMOVE_LINKS 51 disclaimer 15
RFC trace 33 SAP system 15
RM classification 24 Upgrade packages 16
RMLink RFC Service 29 Upgrade path 6, 15
Configuring 31 User management
Installing 30 LDAP 67
Log levels 33
TCP/IP connection 44
Troubleshooting 33
RMLink scheme 6
S
SAINT 9, 11
files 11
password 11
SAP
post-installation 35
SAP Add-On Installation Tool 9, 11
SAP authentication 37
SAP Java Connector module
See “JCo”
SAP R/3 Enterprise 4.70
RMLink RFC Service 29
SAP roles 35
SAPCAR files 11
Single sign-on
See “SSO”
SSO
CAP Web Service 62
cookies 61
process 61
settings 47
SSO HTTP service 49
Sun ONE Directory Server 67
System categories 28
T
Target group 9

Open Text RMLink For SAP Solutions 9 7 1 Installation Guide

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Open Text RMLink For SAP Solutions 9 7 1 Installation Guide

Transféré par

Droits d'auteur :

Formats disponibles

Installation Guide

Open Text RMLink for SAP Solutions

The Open Text RMLink for SAP Solutions installation guide

Copyright © by Open Text Corporation, Open Text Inc.

3 Installing package ................................................................... 13

5 Performing post-installation tasks in Enterprise Library

RMSAP090701-IGD-EN Installation Guide iii

6 Performing post-installation tasks in SAP .............................35

IDX Index .........................................................................................71

iv Installation Guide RMSAP090701-IGD-EN

RMSAP090701-IGD-EN Installation Guide 5

Figure 1-1: RMLink scheme

1.1 Product documentation

6 Installation Guide RMSAP090701-IGD-EN

1.2 Contact information

RMSAP090701-IGD-EN Open Text RMLink for SAP Solutions 9.7.1 7

2.1 Required knowledge

2.2 Terms and definitions

DPA Name of the SAP system used by Open Text

2.3 SAP prerequisites

RMSAP090701-IGD-EN Installation Guide 9

2.4 Enterprise Library Services prerequisites

10 Installation Guide RMSAP090701-IGD-EN

Host/port for logical archive

2.5 Installation tool

2.6 Password control

Table 2-1: Installation packages and passwords

Package Release SAP Re- Designation Password

RMSAP090701-IGD-EN Open Text RMLink for SAP Solutions 9.7.1 11

2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

RMSAP090701-IGD-EN Installation Guide 13

3. If you experience errors during BC set activation, repeat the respective

14 Installation Guide RMSAP090701-IGD-EN

4.1 Upgrading to Open Text RMLink for SAP

4.2 Upgrading the SAP system

4.2.1 Exchange upgrades

RMSAP090701-IGD-EN Installation Guide 15

The following exchange upgrades are supported:

Table 4-1: Exchange upgrades for SAP system

Upgrade from RMLink Upgrade to Upgrade package required

To perform an exchange upgrade procedure:

2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

Note: No passwords are required for the upgrade packages.

16 Installation Guide RMSAP090701-IGD-EN

5.1 Configuring storage provider

To configure the storage provider:

2. In the Actions pane, select the New Provider entry.

RMSAP090701-IGD-EN Installation Guide 17

The New Provider wizard displays.

18 Installation Guide RMSAP090701-IGD-EN

5.2 Installing SAP SSO libraries

RMSAP090701-IGD-EN Open Text RMLink for SAP Solutions 9.7.1 19

2. Extract the SAPCAR files with the following command:

3. Copy the extracted files to the appropriate location:

The environment variable %PATH% or $LD_LIBRARY_PATH must be the one of the

5.3 Creating Livelink users for SAP users

20 Installation Guide RMSAP090701-IGD-EN

Figure 5-1: Directory synchronization architecture

RMSAP090701-IGD-EN Open Text RMLink for SAP Solutions 9.7.1 21

5.4 Creating Enterprise Library Services application

2. In the Actions pane, select the New Application entry.

22 Installation Guide RMSAP090701-IGD-EN