OpenText Extended ECM For SAP Solutions. Installation Guide For Microsoft Windows With Microsoft SQL Server PDF

OpenText™ Extended ECM for SAP®
Solutions
Installation Guide for Microsoft

Windows with Microsoft SQL Server
This guide describes the installation and basic configuration of

one of the most common deployment scenarios of Extended
ECM for SAP Solutions. The OpenText™ Enterprise Library is
installed on two physical servers, one for OpenText™ Content
Server, the other one for the Extended OpenText™ Archive
Server.
ERX100500-01-IWS-EN-3
OpenText™ Extended ECM for SAP® Solutions
Installation Guide for Microsoft Windows with Microsoft SQL Server
ERX100500-01-IWS-EN-3
Rev.: 2015-Sept-14
This documentation has been created for software version 10.5 SP1.
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 SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
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
Support: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2015 Open Text SA and/or Open Text ULC (in Canada). All Rights Reserved.
Trademarks owned by Open Text SA or Open Text ULC (in Canada). All rights reserved.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
1 What is OpenText Extended ECM for SAP Solutions ............ 9
1.1 What is new? .................................................................................... 9
1.2 Related documentation ...................................................................... 9
2 Overview ................................................................................... 13
Part 1 Setting up Archive Server 15
3 Prerequisites ............................................................................ 17
4 Installing JRE, Tomcat and SQL Server ................................ 19

4.1 Installing Java Runtime Environment (JRE7) ..................................... 19
4.2 Installing and configuring Apache Tomcat 7 ...................................... 19
4.3 Installing SQL Server 2012 .............................................................. 23
4.4 Configuring SQL Server network connectivity .................................... 38
4.5 Creating the login and the database for Archive Server ...................... 42
5 Installing Archive Server ........................................................ 49

5.1 Using Extended ECM for SAP Solutions Master Setup ...................... 49
5.2 Installing Directory Services ............................................................. 51
5.3 Installing Archive Server .................................................................. 59
5.4 Installing Archive Monitoring Server .................................................. 68
5.5 Installing ECMLink Web Services ..................................................... 71
5.5.1 Deploying Content Web Services ..................................................... 72
5.5.2 Configuring host and port for Content Server in Tomcat ..................... 72
5.6 Installing Enterprise Library Services ................................................ 73
5.7 Installing Administration Client ......................................................... 74
5.8 Installing Solution Registry Agent ..................................................... 75
5.9 Install Document Pipeline components ............................................. 76
5.10 Installing the Archive Server Update ................................................. 77
5.11 Enable the proper usage of sequences in SQL Server 2012 .............. 78
5.12 Test: Archive Spawner Service created ............................................ 79
Part 2 Setting up Content Server 81
6 Setting up IIS 7.5 ...................................................................... 83
7 OpenText Extended ECM for SAP Solutions Master

Setup ......................................................................................... 97
8 Installing Content Server on Windows ................................ 101
9 Installing Content Server modules ...................................... 109
OpenText Extended ECM for SAP Solutions – Installation Guide for Microsoft Windows with
Microsoft SQL Server iii
ERX100500-01-IWS-EN-3
Table of Contents
10 Configuring Content Server ................................................. 111
11 Uninstalling the Document Undelete module ..................... 121
12 Deploying the Web Content Services to Tomcat ................ 123
13 Installing the Content Server modules ................................ 125
14 Testing Content Server search ............................................ 127
Part 3 Installing patches 129
15 Installing Enterprise Library patches .................................. 131
16 Installing Content Server patches using the cluster

management tool ................................................................... 133
Part 4 Configuring Enterprise Library Services 135
17 Starting the Administration Client on Archive Server ....... 137
18 Configuring OpenText Directory Services .......................... 143

18.1 Creating a resource ID .................................................................. 143
18.2 Setting the resource ID at Content Server ....................................... 147
18.3 Setting up a synchronized OTDS user partition from Active Directory ...
149
18.4 Editing memberships to OTDS roles ............................................... 151
19 Configuring Archive Server .................................................. 153

19.1 Creating the connection from Archive Server to Content Server ....... 153
19.2 Creating disk volumes for storage and for disk buffer ....................... 155
19.3 Creating a buffer ........................................................................... 157
19.4 Creating a logical archive ............................................................... 158
19.5 Creating a pool ............................................................................. 159
19.6 Attaching a volume to a pool .......................................................... 162
20 Configuring the storage provider ........................................ 163
21 Creating a storage provider and a storage rule .................. 165
22 Enabling certificates ............................................................. 169
23 Creating an application ......................................................... 171
24 Removing the UndeleteWS from the Enterprise Library

configuration .......................................................................... 175
25 Testing Enterprise Library .................................................... 177

25.1 Starting the test application ............................................................ 177
iv Microsoft SQL Server
ERX100500-01-IWS-EN-3
Table of Contents
25.2 Creating an item ........................................................................... 178
Part 5 Installing Archiving and Document Access for SAP

Solutions 183
26 Introduction ............................................................................ 185
27 Checking prerequisites ......................................................... 187

27.1 Required knowledge ...................................................................... 187
27.2 Software packages ........................................................................ 187
27.3 Terms and definitions .................................................................... 187
27.4 SAP prerequisites ......................................................................... 188
27.5 Installation tool .............................................................................. 189
27.6 Password control .......................................................................... 189
27.7 Web Dynpro configuration ............................................................. 190
28 Installing Basis package ....................................................... 191

28.1 Installing package ......................................................................... 191
28.2 Configuring components ................................................................ 194
28.2.1 Setting number ranges .................................................................. 194
28.2.2 Defining authorizations .................................................................. 194
28.2.3 Defining settings for logging ........................................................... 195
28.2.4 Defining settings for optional sample projects .................................. 195
28.3 Authorizations ............................................................................... 196
28.4 DocuLink ...................................................................................... 196
28.4.1 General information ....................................................................... 196
28.4.2 Authorizations ............................................................................... 196
28.4.3 Testing the DocuLink installation .................................................... 197
29 Installing ERP option package ............................................. 199

29.1 Installing the ERP package ............................................................ 199
30 Installing CRM option package ............................................ 201

30.1 Installing the package .................................................................... 201
31 Installing language packages ............................................... 203
32 Handling communication protocols .................................... 205

32.1 Maintaining OLE application .......................................................... 205
32.2 Maintaining SAP ArchiveLink application ........................................ 207
32.3 Assigning protocols to logical archives (content repositories) ........... 212
Part 6 Setting up ECMLink for SAP Solutions 213
33 Checking the prerequisites .................................................. 215
Microsoft SQL Server v
ERX100500-01-IWS-EN-3
Table of Contents
33.1 Required knowledge ...................................................................... 215

33.2 Prerequisites ................................................................................ 215
33.2.1 SAP prerequisites ......................................................................... 215
33.2.2 Enterprise Library prerequisites ...................................................... 218
33.2.2.1 Enterprise Library prerequisites for ECMLink 10.5.1 ........................ 218
33.2.2.2 Enterprise Library prerequisites for ECMLink 10.0.5 Content Server
module ......................................................................................... 219
33.3 SAP Add-On Installation Tool (SAINT) ............................................ 220
33.4 Finding version information for ECMLink relevant system
components .................................................................................. 221
34 Installing the SAP package ................................................... 223
35 Installing language packages in the SAP system .............. 225
36 Performing general post-installation tasks in SAP ............ 227

36.1 Using the IMG function .................................................................. 227
36.2 Assigning SAP roles ...................................................................... 230
37 Performing post-installation tasks for SAP ERP 6.0, SAP

CRM 7.0, and SAP SRM 7.0 ................................................... 233
37.1 Exporting the SAP PSE certificate for the SAP authentication
handler ......................................................................................... 233
37.2 Activating the ECMLink SSO HTTP service .................................... 236
37.3 Creating logical ports in the SAP system ........................................ 237
37.3.1 Creating logical ports for SAP Basis 7.0 .......................................... 237
37.3.2 Creating logical ports for SAP Basis 7.01 ........................................ 244
37.3.3 Creating logical ports for SAP Basis 7.31 ........................................ 248
37.4 Configuring the Service Provider Interface service ........................... 251
37.5 Maintaining Enterprise Library server settings ................................. 253
38 Performing post-installation or post-upgrade tasks in

Enterprise Library .................................................................. 257
38.1 Importing root certificates for Secure Sockets Layer (SSL)
connections .................................................................................. 257
38.2 Connecting external systems ......................................................... 258
38.3 Managing users ............................................................................ 260
38.4 Preparing document declaration ..................................................... 261
38.4.1 Creating a Records Management classification (optional) ................ 261
38.4.2 Importing folder and item type ........................................................ 261
38.4.3 Setting up the authorization for records in Enterprise Library ............ 263
38.4.4 Creating system categories in Content Server ................................. 264
38.5 For SAP CRM and SRM: Configuring security settings .................... 265
39 Verifying the installation ....................................................... 267
vi Microsoft SQL Server
ERX100500-01-IWS-EN-3
Table of Contents
39.1 Analyzing the SAP system ............................................................. 267

39.1.1 Understanding the SAP Diagnostic Program ................................... 267
39.1.2 Understanding the details of the Diagnostic Program ....................... 268
40 Preparing a checklist for the customizing team ................. 273
Microsoft SQL Server vii
ERX100500-01-IWS-EN-3
Chapter 1
What is OpenText Extended ECM for SAP Solutions
OpenText Extended ECM for SAP Solutions (Extended ECM for SAP Solutions) is a
combination of a Content Server module and an SAP package, with which you can
integrate Content Server functionality into SAP business processes. This includes
functionality for document and records management, archiving, workflow and
collaboration.
Business A business workspace in Content Server contains content that is relevant for an SAP
workspaces, business object. From Content Server side, users can easily view the data of this SAP
cases and
binders
business object. From the SAP system side, users can access Content Server items in
the business workspace without leaving the SAP system. To make full use of the
Content Server functionality, not only business workspaces but also cases and
binders can be configured for ECMLink.
Business In addition to the content that is stored in a business workspace for an SAP business
attachments object, users can connect additional documents as business attachments to an SAP
business object.
Business rela- Extended ECM for SAP Solutions provides tools to illustrate a relationship between
tionships business workspaces. For example, a hierarchical relationship between business
workspaces can be displayed in a sidebar widget of a business workspace.
1.1 What is new?

“Creating the connection from Archive Server to Content Server ”, page 153
Since Update 2014.1, you can connect multiple instances of Enterprise Library or
Content Server to a single Archive Server. Hence, the configuration of the
Content Server connection in Archive Server has changed.
1.2 Related documentation

Important
OpenText strongly recommends that you read OpenText Extended ECM for
SAP Solutions - Overview Guide (ERX-GGD) unless you are familiar with
architectural aspects and business scenarios of Extended ECM for SAP
Solutions.
Product docu- The following documentation is available for ECMLink and Extended ECM for SAP
mentation Solutions in the OpenText Knowledge Center (https://knowledge.opentext.com/
knowledge/cs.dll/Open/10194282):
OpenText Extended ECM for SAP Solutions - Overview Guide (ERX-GGD)

The Overview Guide contains a short overview over the functions and
possibilities of Extended ECM for SAP Solutions. It also explains the architecture
Microsoft SQL Server 9
ERX100500-01-IWS-EN-3
Chapter 1 What is OpenText Extended ECM for SAP Solutions
and shows different business scenarios of Extended ECM for SAP Solutions and
ECMLink.
OpenText ECMLink for SAP Solutions - Installation and Upgrade Guide (ERLK-IGD)
The Installation Guide describes the installation and upgrade of ECMLink up to
the point where the connection between SAP and Content Server is established.
OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD)

The Customizing Guide describes how to customize SAP and configure Content
Server for ECMLink functionality.
OpenText ECMLink for SAP Solutions - Administration Guide (ERLK-AGD)

The Administration Guide describes ongoing maintenance tasks.
OpenText Extended ECM for SAP Solutions - User Management and Access Control
Scenarios (ERX-CUM)
This guide discusses user management and access control scenarios.
OpenText ECMLink for SAP Solutions - User Guide (ERLK-UGD)

The User Guide describes how to use ECMLink functionality in both SAP and
Content Server. This guide is also available as online help.
OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Microsoft SQL Server (ERX-IWS) (this guide)
This specific Installation Guides describe the setup of one architecture scenario
for Extended ECM for SAP Solutions with Microsoft SQL Server as database.
OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Oracle (ERX-IWO)
This specific Installation Guides describe the setup of one architecture scenario
for Extended ECM for SAP Solutions with Oracle as database.
OpenText Extended ECM for SAP Solutions 10.5 - eBook

The eBook describes the key concepts and capabilities of Extended ECM for SAP
Solutions. It also gives an insight to the configuration of version 10.5 of
Extended ECM for SAP Solutions and describes example scenarios.
The OpenText Extended ECM for SAP Solutions 10.5 - eBook is available in the
Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/
ExtendedECMeBook).
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product
• Requirements
• Restrictions
• Important dependencies
• Last-minute changes regarding the documentation
• Manual IDs of the current documentation
The Release Notes are continually updated. The latest versions of the ECMLink and
Extended ECM for SAP Solutions Release Notes is available in the OpenText
Knowledge Center: ECMLink (https://knowledge.opentext.com/knowledge/cs.dll/
10 Microsoft SQL Server
ERX100500-01-IWS-EN-3
1.2. Related documentation
Overview/46226701) and Extended ECM for SAP Solutions (https://

knowledge.opentext.com/knowledge/cs.dll/Overview/46226570).
ERX100500-01-IWS-EN-3
Chapter 2
Overview
This system overview explains how the system will look like after installation.
Figure 2-1: System overview
Important
The documentation assumes that the only installation media is the Extended
ECM for SAP Solutions 10.5 SP1 installation media. It includes OpenText
Enterprise Library 10.5 SP1.
The document describes the following scenario:

• One Archive Server including OTDS, Enterprise Library Services, ECMLink
Services and Archive Services
• One server for the Content Server 10.5 at least SP1
These servers can be physical or virtual.
This guide describes the setup of a system environment containing these

components:
• Windows 2012
• Web application server is Apache Tomcat for Archive Server
ERX100500-01-IWS-EN-3
Chapter 2 Overview
• Database platform is MS SQL Server 2012

• SAP ERP 6.x
• Single-File-Storage on Archive Server on local hard-disk
The installation and configuration of the following components is NOT described in

this guide:
• Oracle Database platform (see separate guide OpenText Extended ECM for SAP
Solutions - Installation Guide for Microsoft Windows with Oracle (ERX-IWO))
• Unix platforms (Oracle Solaris, Linux, HP-UX)
• Windows- or Web-Viewer installation and configuration
• SAP CRM, SRM integration
• Rendition services
• View Services
• Configuration of Enterprise Connect
• eLink Server
For these components the detailed installation and configuration documentation is

to be checked separately.
Important
In this guide the proposed default file system paths are described as a C
drive exists on all Windows systems. But in general it is strongly
recommended to install software on a different drives and to separate data
from the binaries. Therefore you should prepare a partition and file system
concept.
ERX100500-01-IWS-EN-3
Part 1
Setting up Archive Server
Chapter 3
Prerequisites
Following software components must be installed:

• Microsoft Visual C++ 2008 SP1 Redistributable Package (x64). You can download
it from the Microsoft Web site (https://www.microsoft.com/downloads/en/
details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E).
• .NET Framework 3.5.1 SP1 or a newer version is installed and activated.
Following settings are required:

• DHCP is deactivated.
A user with all administrative rights is available. For this example, we use the user
administrator.
ERX100500-01-IWS-EN-3
Chapter 4
Installing JRE, Tomcat and SQL Server
This chapter describes the installation of the basic non-OpenText components

required for Extended ECM for SAP Solutions.
4.1 Installing Java Runtime Environment (JRE7)

Perform the following steps to install JRE:
1. Download Java Runtime Environment 64 bit from the Extended ECM for SAP
Solutions installation media.
2. Run the JRE setup file jre-7-windows-x64.exe.
3. Click Install to start installation.
4. After JRE has been successfully installed, click Close to resume.
4.2 Installing and configuring Apache Tomcat 7

To install Apache Tomcat 7:
1. Download Apache Tomcat 7.0.50 64 bit as installation binary (apache-

tomcat-7.0.50.exe) from the Extended ECM for SAP Solutions installation
media or download it from http://tomcat.apache.org or one of the mirrors.
2. Run the setup file apache-tomcat-7.0.50.exe.
3. Click Next in the startup window and click I Agree to confirm the license
agreement in the next window.
4. In the Choose Components window, keep the default settings.
ERX100500-01-IWS-EN-3
Chapter 4 Installing JRE, Tomcat and SQL Server
Click Next.
5. Keep 8080 as HTTP/1.1 Connector Port and do not enter a User Name and
Password.
ERX100500-01-IWS-EN-3
4.2. Installing and configuring Apache Tomcat 7
Click Next.
6. Choose the installation path for the Java Runtime Environment and click Next
to start the installation.
7. Keep the Destination Folder in the Choose Install Location window and click
Install.
8. Select Run Apache Tomcat in the final window and click Finish to complete
installation.
9. Select Start > Administration Tools > Services and check whether the service
Apache Tomcat 7.0 Tomcat7 is started. Right-click the service and ensure that
the Startup Type is set to Automatic.
In this window, the service can also be restarted if necessary.
ERX100500-01-IWS-EN-3
Note: It can take up to 15 minutes until the system has started.
10. Configure Java for Tomcat:
a. Start the Tomcat configuration program with administrator rights: Click

Start > All Programs > Apache Tomcat 7.0 Tomcat 7, then right-click
Configure Tomcat and select Run as administrator.
On the Java tab, in the Java Options box, append the following lines. Do
not copy them from the PDF file but type them directly into the box.
-XX:MaxPermSize=256m
-XX:+CMSClassUnloadingEnabled
-XX:+CMSIncrementalPacing
-XX:+UseConcMarkSweepGC
b. In the Initial memory pool box, enter 512 MB.
In the Maximum memory pool box, enter 1024 MB.
ERX100500-01-IWS-EN-3
4.3. Installing SQL Server 2012
c. Click OK.
d. Open the >Tomcat home>\conf\logging.properties file in an editor.
e. In the line starting with .handlers = ..., remove the entry
java.util.logging.ConsoleHandler and save the file.
f. Restart the Apache Tomcat service.
g. Test Tomcat: Call the URL http://localhost:8080. The Tomcat default page
opens.
h. Stop the Apache Tomcat service to avoid undesired deployments.
4.3 Installing SQL Server 2012

To install SQL Server 2012:
1. Insert the Microsoft SQL Server DVD.

If the installation does not start automatically, run <DVD drive>:\setup.exe.
2. The User Account Control asks for permission. Click Continue.

The SQL Server Installation Center window opens.
3. In the Planning area, click System Configuration Checker.

If all test passed, click OK. You return to the SQL Server Installation Center.
ERX100500-01-IWS-EN-3
4. In the Installation area, click New SQL-Server stand-alone installation or add

features to an existing installation.
The Setup Support Rules page opens.
5. On the Setup Support Files page, click OK.
ERX100500-01-IWS-EN-3
6. On the Product Key page, select Enter the product key and enter or verify the
product key.
ERX100500-01-IWS-EN-3
Click Next.
7. On theLicense Terms page, select I accept the license terms.
Click Next.
8. Select Include SQL Server product updates and click Next.
ERX100500-01-IWS-EN-3
9. Click Install to install the setup files.
10. On the Setup Support Files page, click Next.
ERX100500-01-IWS-EN-3
If the Windows Firewall is activated, a warning opens. See http://

go.microsoft.com/fwlink/?LinkId=94001 for details on how to configure the
firewall to allow SQL Server access.
Note: The warning opens if the firewall is active, regardless whether it is

configured correctly or not.
11. In the Setup Support Rules window, click Next.
ERX100500-01-IWS-EN-3
12. Specify SQL Server Feature Installation as setup role.
13. On the Feature Selection page, select at least the following:
ERX100500-01-IWS-EN-3
a. From Instance Features: Database Engine Services.

b. From Shared Features: Client Tools Connectivity, Client Tools
Backwards Compatibility, Documentation Components, Management
Tools - Basic, Management Tools - Complete.
c. Do not change the default values for Shared feature directory and Shared
feature directory (x86).
Click Next,
14. On the Installation Rules page, click Next.
ERX100500-01-IWS-EN-3
15. On the Instance Configuration page, keep the default setting and click Next.
ERX100500-01-IWS-EN-3
16. On the Disk Space Requirements page, keep the default settings and click
Next.
17. On the Server Configuration page, select the Service Accounts tab and specify
the following:
Service Account Name Password Startup Type

SQL Server Agent NT AUTHORITY Manual
\SYSTEM
SQL Server NT AUTHORITY Automatic
Database Engine \SYSTEM
SQL Server Browser NT AUTHORITY Disabled
\LOCAL...
Alternatively, you can use the default settings.
ERX100500-01-IWS-EN-3
18. Select the Collation tab. Select the Database Engine and click Customize.
Select SQL collation, used for backwards compatibility and select
SQL_Latin1_General_CP1_CS_AS from the list.
Caution
This is very important: Do not use the default value (case insensitive)!
If you select the wrong setting, you have to reinstall your database
system.
ERX100500-01-IWS-EN-3
19. On the Database Engine Configuration page, select Mixed Mode, do the
following:
ERX100500-01-IWS-EN-3
a. On the Server Configuration tab, select Mixed Mode (SQL Server

Authentication and Windows Authentication) as Authentication Mode.
Enter and confirm the password for the sa (System Administrator) logon.
b. Specify an SQL Server Administrator: To add the user as who you are
currently logged on (Administrator), click Add Current User.
c. Click Next.
20. On the Error Reporting page, do not select anything. Click Next.
ERX100500-01-IWS-EN-3
21. On the Installation Rules page, verify that no errors exist and then click Next.
ERX100500-01-IWS-EN-3
22. On the Ready to Install page, check the summary for the specified parameters
and click Install.
The database software installation will take some time.
Note: If the installation does not proceed when showing Installing local
groups, unplug the network cable of the database server during
installation.
23. When all products have reached the status Succeeded, click Close.
ERX100500-01-IWS-EN-3
4.4 Configuring SQL Server network connectivity

To configure network connectivity:
1. Select Start > Programs > Microsoft SQL Server 200x > SQL Server
Management Studio.
2. To connect to the database server, specify the following:
• Server type: Database Engine

• Server name: localhost
• Authentication: SQL Server Authentication
• Login: sa
• Password: Enter the password.
ERX100500-01-IWS-EN-3
4.4. Configuring SQL Server network connectivity
3. Click Connect.
4. Right-click on localhost (SQL Server 10.0.xxxx - sa), and then click Properties.
5. In the Server Properties window, click Connections. Select the Allow remote
connections to this server option if not already selected and click OK to save
your changes.
ERX100500-01-IWS-EN-3
6. Click Start > Programs > Microsoft SQL Server 2012 > Configuration Tools >
SQL Server Configuration Manager.
7. Expand SQL Server Configuration Manager (Local) > SQL Server Network
Configuration > Protocols for MSSQLSERVER.
8. If TCP/IP is not enabled yet, right-click TCP/IP, and then click Enable.
ERX100500-01-IWS-EN-3
4.4. Configuring SQL Server network connectivity
9. If Shared Memory is enabled, disable the Shared Memory protocol.
10. Repeat the two last steps for the client protocols of SQL Native Client 11.0
Configuration (32 bit) and SQL Native Client 11.0 Configuration.
11. Expand SQL Server Configuration Manager (Local) > SQL Server Services,
right-click SQL Server (MSSQLSERVER), and then click Restart.
SQL Server is now ready to be connected via TCP/IP.
ERX100500-01-IWS-EN-3
4.5 Creating the login and the database for Archive

Server
To create a database for Archive Server:
1. Start SQL Server Management Studio.
2. Connect to the database engine as sa.
3. Expand <host name> (SQL Server 10.0.xxxx - sa) > Security > Logins, right-click
Login, and select New Login.
4. In the Login - New window, set the following:
a. Enter the login name ecr.

b. Select the SQL Server authentication option. Enter and confirm a
password.
c. Do not select Enforce password expiration.
ERX100500-01-IWS-EN-3
4.5. Creating the login and the database for Archive Server
5. Click OK to create the database login.
6. Expand <host name> (SQL Server 10.0.xxxx - sa) > Databases, right-click
Databases, and then select New Database.
ERX100500-01-IWS-EN-3
7. Select General and do the following:
a. Enter the database name ECR.

b. Enter the owner of the database ecr.
ERX100500-01-IWS-EN-3
8. Select Filegroups.
9. Click Add twice, and create one filegroup for data and one for index (e.g.
ECR_DATA and ECR_INDEX).
ERX100500-01-IWS-EN-3
10. Select General again.
11. Create the database files for the data and the index filegroups:
a. Add two files for the data and index filegroups created above: Choose a
logical name for the files (e.g. ECR_DATA_1 and ECR_INDEX_1,
respectively).
Choose the respective filegroup (in the example, select the ECR_DATA
filegroup for the ECR_DATA_1 file and the ECR_INDEX filegroup for the
ECR_INDEX_1 file).
Choose a path where the files are to be located. The files will be created in
the folder you enter. The folder must exist.
b. Choose a path for the primary filegroup and the transaction log (named
<database name> and <database name>_log, respectively.
c. Specify a suitable initial size and enable unrestricted autogrowth for each of
the files:
ERX100500-01-IWS-EN-3
Logical name File type Filegroup Minimum Autogrowth

Initial size
(MB)
ECR Rows Data primary 50 By 1 MB
ECR_log Log Not 100 By 10 %
Applicable
ECR_DATA_1 Rows Data ECR_DATA 100 By 100 MB
ECR_INDEX_1 Rows Data ECR_INDEX 100 By 100 MB
d. Click Options and set the following:
• Select SQL_Latin1_General_CP1_CS_AS as the collation. You may

need to scroll down to find the entry in the list.
• Select Full as the recovery model.
• Compatibility Level: Select SQL Server 2012 (110).
• Set the following options to True:

Auto Create Statistics, Auto Update Statistics, ANSI NULL Default,
ANSI NULLS Enabled, ANSI Padding Enabled, ANSI Warnings
Enabled, Arithmetic Abort Enabled, Concatenate Null Yields Null,
Quoted Identifiers Enabled
• Set the following options to False:

Auto Close, Auto Shrink, Close Cursor On Commit Enabled, Numeric
Round-Abort
• Set Page Verify to TORN_PAGE_DETECTION.
e. Click OK to create the database.
ERX100500-01-IWS-EN-3
12. Expand <host name> (SQL Server 10.0.xxxx - sa) > Security > Logins, right-click
ecr, and then click Properties.
13. In the Login Properties window, select General. Select ECR as the default
database and click OK.
Optional: Test To make sure the Archive Server database has all the required features, process the
the Archive StPreSchemaCreateMSSQL.sql check script that can be found in the Knowledge
Server
Database
Center: https://knowledge.opentext.com/knowledge/cs.dll/open/17997622
Process the script as follows:
sqlcmd -U <user> -P <passwd> -d <database> -S <database server> -i

<path>StPreSchemaCreateMSSQL.sql -v fgd='<data file group>'
fgi='<index file group>'
Example: It is assumed that you process this script on the database server:
sqlcmd -U ecr -P ecr -d ECR -S localhost -i

<path>StPreSchemaCreateMSSQL.sql -v fgd='ECR_DATA' fgi='ECR_INDEX'
If you do not get any FATAL messages, the configuration of connection and user is
correct.
ERX100500-01-IWS-EN-3
Chapter 5
Installing Archive Server
This chapter describes the installation of Directory Services, Archive Server,

Enterprise Library Services, and further components. Content Server will be
installed on a different machine later on.
Note: This chapter describes a basic installation. For more information, see the
OpenText Content Suite Platform document selection (https://
knowledge.opentext.com/knowledge/piroot/_doclists/sucsp-basic.100500.xml)
in the OpenText Knowledge Center.
5.1 Using Extended ECM for SAP Solutions Master

Setup
To install Archive Server:
1. Download the OpenText Extended ECM for SAP Solutions 10.5 ISO-9660 image
from the OpenText Knowledge Center (https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/8521552) and burn a DVD from it.
Alternatively, use a third-party tool to mount the ISO image as a virtual drive.
Using this method, you can directly start ECM Suite Installer in the image file.
For details, see the Knowledge Center (http://mimage.opentext.com/support/
ecm/secure/software/checksuminstructions.html).
2. Log on as user Administrator (local machine administrator).
3. Insert or mount the OpenText Extended ECM for SAP Solutions product DVD.
If the installation does not start automatically, run <DVD drive>:
\Mastersetup.exe. The ECM Suite Installer starts.
4. In the ECM Suite Installer window, click Next to continue.
5. Read the License Agreement. To accept it, select I accept the terms in the
License Agreement and click Agree.
6. In the Deployment Scenarios window, select Extended Archive Server

Deployment and click Next.
ERX100500-01-IWS-EN-3
Chapter 5 Installing Archive Server
A summary displays all components selected for installation.
7. Deselect Document Pipelines if not required and click Next. If you want to
install Document Pipelines, open the section and check the selection. If needed,
select additional components, for example Document Pipeline for Content
Server which is needed for Enterprise Scan.
8. Confirm the Summary with Install.
ERX100500-01-IWS-EN-3
5.2. Installing Directory Services
9. Click Next to start the installation.

The components are installed one after the other. Refer to the instructions for
each installation in the following chapters.
5.2 Installing Directory Services

To install Directory Services
1. After clicking Next in the ECM Suite Installer window, the Directory Services
installer opens. Click Next.
ERX100500-01-IWS-EN-3
2. Select the check box if you want to setup the server as a replication server.
ERX100500-01-IWS-EN-3
3. In the Destination Folders window, enter the paths to the folders for the
Directory Services installation or browse the file system by clicking the Browse
buttons.
ERX100500-01-IWS-EN-3
4. Enter the path to the Java SE 7.0 installation directory.
ERX100500-01-IWS-EN-3
5. In the Apache Tomcat Directory window, enter the service name tomcat7 or the
installation directory.
ERX100500-01-IWS-EN-3
6. In the Directory Services Parameters window, apply the default settings and
click Next.
ERX100500-01-IWS-EN-3
• LDAP Administration Port: The port that will be used for administration
traffic (default: 4440).
• LDAP Communication Port: The port number that Directory Services uses
for communication with your LDAP directory server. Also known as the
LDAP Listener Port (default: 389 for Windows; 1389 for UNIX).
7. In the OTDS Administrator window, enter a password for the global OTDS
Administrator user name (otadmin@otds.admin) and click Next.
The default user (otadmin@otds.admin) is created by the installation.
The following users and groups are added to the role during the installation
when OpenText Directory Services authentication is selected:
otadmin@otds.admin The default OTDS administrator.

otadmins@otds.admin The default group containing all OpenText
administrators including
otadmin@otds.admin. This group is
intended to be used for administrators
who can administer all OpenText
products.
ERX100500-01-IWS-EN-3
8. In the OpenText Directory Services 10.2.1 Data Import window, click Next.
ERX100500-01-IWS-EN-3
5.3. Installing Archive Server
9. In the Ready to Install window, click Install.
Note: If there is an alert from Windows Firewall concerning Java’s access

to the network, allow Java to access the network. Otherwise the
installation will not continue.
5.3 Installing Archive Server

To install Archive Server:
1. After clicking Next in the Archive Server installer window, specify the
application server to be used.
ERX100500-01-IWS-EN-3
2. In the Apache Tomcat Parameters window, select the service name you entered
before during the Directory Services installation.
ERX100500-01-IWS-EN-3
3. Enter the ports.
ERX100500-01-IWS-EN-3
4. In the Destination Folders window, enter the paths to the folders for the
Archive Server installation and configuration data or browse the file system by
clicking the Browse buttons.
Click Next.
5. Specify the service user settings for the Archive Spawner service.
Select Run the service as local system to use the system account for running the
service.
ERX100500-01-IWS-EN-3
Click Next.
6. Enter the paths to the folder for the logging information and the folder for
runtime files (var) or browse the file system by clicking the Browse buttons.
Note: You can only change these settings if they were not specified before.
ERX100500-01-IWS-EN-3
Click Next.
7. Select the database system to be used, here MS SQL Server.

Select the Create schema check box.
ERX100500-01-IWS-EN-3
Click Next.
8. Enter the parameters for the archive database. If possible, use the default
settings.
Database server: Name of the computer the database resides on, the host name,
for example xecmdbv8els2.eng-muc-test.opentext.net.
Database port: Port used for connections to the database; default: 1433
Database name: Name of the database (case sensitive); default: ECR
Database user: Name of the ECR database user; default: ecr
Database password: Password of the ECR database user
Important
Do not use empty passwords!
Data filegroup: Name of the filegroup for data; default: ECR_DATA

Index filegroup: Name of the filegroup for index; default: ECR_INDEX
ERX100500-01-IWS-EN-3
9. Check the settings carefully.
Important
On the remote database server, the firewall has to be turned off before
proceeding.
10. Click Next. The setup tests the connection to the database. In case of an error,
check %TEMP%\opentext\MakeSchema.log.
In our example the database server is the ELS server.
11. Enter the folders for the building of the ISO trees and images or browse the file
system by clicking the Browse buttons.
Important
The ISODIR and IMGDIR folders must be different.
Note: Regardless of planning to use ISO images or not, you have to

specify these settings.
ERX100500-01-IWS-EN-3
Click Next.
12. In the Directory Services Parameters screen, select Run Archive Server with
built-in User Management (dsadmin).
Note: The dsadmin user is used during installation of Archive Server

when the option Built-in User Management is used. This option is
necessary because there is no OTDS at this point. You will need this user
also when you add Archive Server to Administration Client. You can
change the logon user later. You can configure OTDS later in the
Administration Client (Archive Server > OTDS Connection). For more
information, see OpenText Archive Server - Administration Guide (AR-ACN).
13. Click Install. The installation process takes place. This may take some minutes.
14. When the installation procedure has finished, click Finish.
Note: You can find logging information in %TEMP%\opentext.
ERX100500-01-IWS-EN-3
5.4 Installing Archive Monitoring Server

Archive Monitoring Server obtains status information about archives, pools, hard
disk and database space on Archive Server.
To install Archive Monitoring Server:
1. In the Archive Monitoring Server installer window, click Next. The

Destination Folders window opens
2. As application server, select Apache Tomcat.
3. Select the service name and click Next.
ERX100500-01-IWS-EN-3
5.4. Installing Archive Monitoring Server
4. Enter the paths to the folders (here, use the default as displayed in the
screenshot) for the Archive Monitoring Server installation and configuration
data or browse the file system by clicking the Browse buttons.
ERX100500-01-IWS-EN-3
Click Next.
5. Specify the service user settings.
Note: You can only change these settings if they were not specified before.
Select either:
• Run the Archive Spawner service as local system to use the system account
for running the service.
• Run the Archive Spawner service as user to assign a dedicated user to the
server. Enter the user name including the domain (if not specified before),
the password, and confirm the password. You must always specify the
password.
6. Enter the path to the folder for the logging information or browse for it by
clicking the Browse button. Click Next.
Note: You can only change this folder if it was not specified before.
Click Next.
7. Click Install. The installation process takes place.
ERX100500-01-IWS-EN-3
5.5. Installing ECMLink Web Services
5.5 Installing ECMLink Web Services

To install ECMLink Web Services:
1. In the Application Server window, select Apache Tomcat 7.0.
Click Next
3. In the Ready to Install window, click Install. The installation process takes
place.
ERX100500-01-IWS-EN-3
5.5.1 Deploying Content Web Services

Extended ECM for SAP Solutions 10.5.1 requires OpenText Content Web Services.
During the setup of Content Server, the Content Web Services WAR file is placed in
the <Content Server home/webservices/java directory.
To deploy Content Web Services:
1. Copy the cws.war file into your <Tomcat home>/webapps directory.
Note: This is only necessary if you do not deploy Content Web Services
using the Content Server setup, because the Content Web Services do not
run on the same machine as Content Server. If you use the setup, keep the
default value cws.
2. Only Unix systems: After deploying the services, change the directory of the
log files.
a. Open the [tomcat]/webapps/cws/WEB-INF/classes/log4j.xml file

b. Change the line <param name="File" value="logs/cws.log" />
to <param name="File" value="../logs/cws.log" />
5.5.2 Configuring host and port for Content Server in Tomcat

After installation of the Apache Tomcat web server, and deployment of the
ECMLink 10.5.1. Web service, the server name is localhost with port 2099. You can
change these settings, for example if you need to address more than one Content
Server.
To change host name and port of Content Server:
1. Open the <Tomcat home>\webapps\otsapxecm\WEB-INF\web.xml file in an

editor.
2. Find the following elements and change the values according to your needs:
<context-param>
<param-name>LivelinkServer</param-name>
<param-value>localhost</param-value>
</context-param>
<context-param>
<param-name>LivelinkServerPort</param-name>
<param-value>2099</param-value>
</context-param>
<context-param>
<param-name>LivelinkEncoding</param-name>
<param-value>UTF8</param-value>
</context-param>
3. Restart the application for the changes to take effect.
ERX100500-01-IWS-EN-3
5.6. Installing Enterprise Library Services
5.6 Installing Enterprise Library Services

Enterprise Library Services provide the services for connections to Content Server.
To install Enterprise Library Services:
1. In the Application Server window, select Apache Tomcat 7.0.
Click Next.
3. Specify the configuration parameters. You can also specify them later in the
Administration Client.
• Content Server URL: Hostname of the Content Server (fully qualified with
domain).
• Content Server LAPI Port: For the port to be used, accept the default
(default: 2099).
ERX100500-01-IWS-EN-3
Click Next
place.
5.7 Installing Administration Client

Administration Client can only be installed on Windows systems.
To install Administration Client:
1. After clicking Next, the Destination Folder window opens.

Specify the installation folder of Administration Client.
ERX100500-01-IWS-EN-3
5.8. Installing Solution Registry Agent
Click Next.
2. In theReady to Install window, click Install. The installation process takes

place.
5.8 Installing Solution Registry Agent

Solution Registry Agent delivers information about installed OpenText software
components (including product name, product version and installation directory) to
OpenText Solution Registry. For details see OpenText Solution Registry - Configuration
and Administration Guide (LDS-AGD).
To install Solution Registry Agent:
1. After clicking Next, the Destination Folder window opens.
ERX100500-01-IWS-EN-3
Specify the installation folder of Solution Registry Agent.

2. Click Next.
place.
5.9 Install Document Pipeline components

With selecting Archive Server installation these components are selected as well:
• Document Pipeline Perl 10.5
• Document Pipeline Base 10.5
• Document Pipeline for SAP Solutions 10.5
• Document Pipeline for DocuLink 10.5
• Document Pipeline Remote Interface 10.5
• Document Pipeline Info 10.5
In addition, you can select the following components if needed:

• Document Pipeline for Enterprise Library 10.5
• Document Pipeline for Content Server 10.5
ERX100500-01-IWS-EN-3
5.10. Installing the Archive Server Update
As these components are not very common for Extended ECM for SAP Solutions
this document does not describe the detailed configuration. If required install the
files by selecting the desired file system paths and leave all other values empty or
keep the default values.
5.10 Installing the Archive Server Update

After all other components are installed, the current update of Archive Server is
installed.
To install the Archive Server update:
1. Check the list of patches and click Next.
2. After all patches are installed, you see if the installation was successful. You can
also display a logfile for every patch by clicking on a list item.
ERX100500-01-IWS-EN-3
5.11 Enable the proper usage of sequences in SQL

Server 2012
If Microsoft SQL Server 2012 is used as database system, you must execute an SQL
script manually to enble the proper use of sequences. Do the following after the
installation of Update 2013.2 but before starting Spawner and Tomcat.
To enable the proper usage of sequences in SQL Server 2012:
1. Download the MSSQL2012_Correction_SP_AddsSequence.sql file from the

Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/
42301798).
2. In a command window, run
sqlcmd -U <AS DB user> -P <password of AS DB user> -d <DB name> -

S >DB Server name>[\DB instance name>] -i
MSSQL2012_Correction_SP_AddsSequence.sql
ERX100500-01-IWS-EN-3
5.12. Test: Archive Spawner Service created
5.12 Test: Archive Spawner Service created

Check if the Archive Spawner Service in Windows has been created successfully.
Important
Do NOT yet start the Spawner- or Apache Tomcat Service in Windows.
ERX100500-01-IWS-EN-3
Part 2
Setting up Content Server
Chapter 6
Setting up IIS 7.5
You must add the Web Server Role to Windows Server and enable content
expiration.
Important
This chapter does not describe how to configuring IIS in general. It only
describes features that are required for Content Server.
To add the Web Server role:
1. In the Windows Start Menu, click Start > Administrative Tools > Server
Manager.
2. In the Server Manager dialog box, click Add roles and features.
3. In the Add Roles and Features Wizard click Next.
ERX100500-01-IWS-EN-3
Chapter 6 Setting up IIS 7.5
4. Select Role-based or feature-based installation and click Next.
5. Select the server.
ERX100500-01-IWS-EN-3
6. Select Web Server (IIS), and click Next.
7. Click Add features.
ERX100500-01-IWS-EN-3
8. Select the features you want to install.

Select HTTP Activation and add the required roles. Follow the steps of the
wizard and check that the correct roles are created. Click Next.
ERX100500-01-IWS-EN-3
9. The Web Server Role (IIS) displays information. Click Next.
10. Click Role Services and select the following:
ERX100500-01-IWS-EN-3
• Common HTTP Features section: Static Content, Default Document, HTTP

Errors, and WebDAV Publishing.
• Application Development section: CGI, ISAPI Extensions, and ISAPI
Filters.
• Health and Diagnostics section: HTTP Logging and Request Monitor.
• Performance section: Static Content Compression.
• Management Tools section: IIS Management Console, IIS 6 Metabase
Compatibility, IIS 6 WMI Compatibility, and IIS 6 Scripting Tools to
install all backwards compatibility components.
Click Next.
11. Review the list of role services or features, and then click Install.
ERX100500-01-IWS-EN-3
ERX100500-01-IWS-EN-3
12. When the installation is completed, click Close.
To configure the Web Server (IIS) using the IIS Manager:
1. To start the IIS Manager, click Start > Administrative Tools > Internet
Information Services (IIS) Manager.
ERX100500-01-IWS-EN-3
2. Expand the server name folder, expand the Sites folder, and click Default Web
Site. In the IIS section of the Default Web Site Home pane, double-click MIME
Types.
3. Click Add.
ERX100500-01-IWS-EN-3
4. In the File name extension box, enter .properties, and in the MIME type box
enter application/octet-stream.
Click OK.
5. In IIS Manager, in the Connections pane, expand Sites, and click Default Web
Site. In the IIS section of the Default Web Site Home pane, open WebDAV
Authoring Rules.
6. Click Add Authoring Rule in the Actions dialog.
ERX100500-01-IWS-EN-3
7. In the Add Authoring Rule dialog, in the Allow access to section, click
Specified content and enter / (forward slash) for the specified content. In the
Allow access to this content to section, click All users. In the Permissions
section, click Read and Source.
Click OK.
8. In the Actions dialog, click WebDAV Settings.
ERX100500-01-IWS-EN-3
9. In the WebDAV Settings dialog, in the Property Behavior section, set the
Allow Anonymous Property Queries and the Allow Property Queries with
Infinite Depth options to True.
In the Actions dialog, click Apply.
10. In the Actions dialog, click WebDAV Authoring Rules.
ERX100500-01-IWS-EN-3
11. In the Actions dialog, click Enable WebDAV.
12. In the IIS Manager in the Connections tree, click Default Web Site.
13. In the Default Web Site Home dialog, double-click HTTP Response Headers.
ERX100500-01-IWS-EN-3
14. In the Actions dialog, click Set Common Headers… or, alternatively, right-click
the HTTP Response Headers Feature Page and click Set Common Headers….
15. In the dialog box, select the Expire Web content box to enable content
expiration. Set it to 1 day.
Click OK. The initial setup of IIS 7.5 is now complete.
16. Test the configuration: On the server on which you install Content Server, in the
Internet Explorer call this URL: http://localhost. The standard IIS welcome page
should appear.
ERX100500-01-IWS-EN-3
Chapter 7
OpenText Extended ECM for SAP Solutions Master
Setup
Following the two-server approach for Extended ECM for SAP Solutions, Content
Server is installed separately on the second server.
To start the Master Setup for Content Server on the second server:
1. Download the OpenText Extended ECM for SAP Solutions 10.5 ISO-9660 image
from the OpenText Knowledge Center (https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/8521552) and burn a DVD from it.
Alternatively, use a third-party tool to mount the ISO image as a virtual drive.
Using this method, you can directly start ECM Suite Installer in the image file.
For details, see the Knowledge Center (http://mimage.opentext.com/support/
ecm/secure/software/checksuminstructions.html).
2. Log on as a user with administrator rights.
3. To run the master setup of the Extended ECM for SAP Solutions installation:
Mount the product DVD. If the installation does not start automatically, run
<DVD drive>:\Mastersetup.exe. The Extended ECM for SAP Solutions Suite
Installer starts.
4. In the ECM Suite Installer window, click Next to continue.
5. Read the license agreement. To accept it, select I accept the terms in the License
Agreement. Click Agree to continue.
6. In the Deployment Scenarios window, select the Content Server scenario.
ERX100500-01-IWS-EN-3
Chapter 7 OpenText Extended ECM for SAP Solutions Master Setup
7. Click Next.
8. In the Product Groups window, the components to be installed are displayed. If

you want to install additional modules, for example Recycle Bin, expand the list
and select them.
ERX100500-01-IWS-EN-3
9. In the Summary window, check that all required modules are listed.
ERX100500-01-IWS-EN-3
Chapter 7 OpenText Extended ECM for SAP Solutions Master Setup
10. Click Install.
ERX100500-01-IWS-EN-3
Chapter 8
Installing Content Server on Windows
Note: This chapter describes a basic installation. For more information, see the
OpenText Content Suite Platform document selection (https://
knowledge.opentext.com/knowledge/piroot/_doclists/sucsp-basic.100500.xml)
in the OpenText Knowledge Center.
After clicking Install in the Master Setup, the Install Location window opens.
1. In the Install Location window, enter the path as displayed or accept the
default.
2. Click Next.
3. In the Content Server Configuration window, enter the following parameter
values:
• Service Name: Accept the default value OTCS.

DNS Name: Specify fully qualified server name, for example
xecmcs.prod.mydomain.net.
HTTP Server Name: Keep localhost.
ERX100500-01-IWS-EN-3
Chapter 8 Installing Content Server on Windows
HTTP Port Number: Keep 80.
Click Next.
4. Select Internet Information Services (IIS) and click Next.
ERX100500-01-IWS-EN-3
5. In the IIS Web Server Mapping window, accept the default URL prefix for
the /img/ support directory or enter a new prefix.
ERX100500-01-IWS-EN-3
Click Next.
6. In the Port Configuration for Content Server window, accept the default values
for Service Port, Admin Port, and RMI Port.
ERX100500-01-IWS-EN-3
Click Next.
7. As Web Server type for Content Web Services, select Apache Tomcat and click
Next.
ERX100500-01-IWS-EN-3
8. Enter the path.
ERX100500-01-IWS-EN-3
9. Enter the web server settings.
ERX100500-01-IWS-EN-3
11. In the Start Services for Content Server window, select View Mapping File
and the other options.
The mappings.tbl file is a text file that contains the URL prefix (virtual
directory alias) path names that you need to map when you configure your Web
server or application server.
Note: The mappings.tbl file is available to view at any time in your

<OT_HOME> directory.
12. The mappings.tbl file is opened in a separate window. Check it and close the
window.
ERX100500-01-IWS-EN-3
Chapter 9
Installing Content Server modules
Content Server modules are installed using the same steps. The setups of Content
Server modules are initiated from the ECM Suite Installer, one after the other. The
first module automatically starts after Content Server installation has finished. After
the installation of the module is finished, the installation of the next module starts
automatically.
To install a Content Server module:
1. In the first window , click Next.
2. The respective module window for selecting the install location opens. Select
the instance of Content Server on which you want to install the module, and
click Next.
4. Click Finish.
5. The next module installation window opens. Continue with the installation as
described above for every module.
ERX100500-01-IWS-EN-3
Chapter 9 Installing Content Server modules
6. Only for the Classifications Professional module - Perform the following

steps:
a. Make sure the Content Server services are not running and confirm the
dialog with Yes.
b. Confirm the dialog with Yes to restart the Content Server services.
7. Click Finish to end the OpenText ECM Suite Installer.
8. Now the binaries are installed and the modules are prepared for a later
installation in Content Server.
9. To test the installation, check whether the installed modules are located in the
Content Server staging directory C:\opentext\staging.
ERX100500-01-IWS-EN-3
Chapter 10
Configuring Content Server
To configure Content Server:
1. Start Content Server Administration:

From the Start menu, click Open Text Content Server 10 (OTCS), and then
click Content Server Administration.
Alternatively, call this URL: http://localhost/OTCS/livelink.exe?
func=admin.index
Important
Installing the modules requires JavaScript. Ensure that JavaScript is
enabled in your browser.
The settings in the Configure Server Parameters window apply to the first
login after installation only.
2. In the Configure Server Parameters window, keep the default values. You have
to scroll to check all parameters.
3. Specify a Content Server Administrator password. This will be required to open
the administration page in the future.
Tip: The Administrator password is one that you use to access the
Administration pages. Do not confuse this password with the password
for the internal Admin user, which is livelink by default. The internal
Admin user is another security step to access certain Administration
pages. After the initial Content Server installation, you should change the
default Admin password on Content Server > Enterprise > Users &
Groups.
4. To enable Content Server logging select Detailed Thread Logging. Logging is

recommended in the configuration phase.
ERX100500-01-IWS-EN-3
Chapter 10 Configuring Content Server
5. Create a folder with the name C:\csupload. Make sure there is sufficient disk
space available.
6. As Upload Directory, enter C:\csupload. Here, documents will be stored

temporarily.
7. Click Save changes to save your changes.
8. On the Default Metadata Language page, select English - en.
Click Continue.
9. On the Database Administration page, click Create New Database.
ERX100500-01-IWS-EN-3
10. On the Select RDBMS Type page, select Microsoft SQL Server.
11. Click Continue.
12. On the Microsoft SQL Server Administrator Log-in page, enter the fully
qualified hostname of Archive Server (on which you installed the software) and
the sa password specified when the database server was installed.
ERX100500-01-IWS-EN-3
13. Click Log-in.
14. On Archive Server: Create the C:\csstore folder.

15. Click MS SQLServer Maintenance.
16. In the Create A new Microsoft SQL Server Database area, enter the parameter
values as displayed in the following screenshot.
Note: If this is NOT a test system, you must adjust the file size errors.
ERX100500-01-IWS-EN-3
17. Click Create Database.
18. In the Create A New User area, enter the parameter values as displayed in the
following screen shot.
19. Click Create User.
ERX100500-01-IWS-EN-3
20. Click Return to the previous page and set the parameter values as displayed in
the following screenshot.
Ensure that csadmin is selected as Microsoft SQL User Name.
21. Click Create Tables.
22. In the Username box, enter Admin and in the Password box, enter the default
value livelink.
23. Click Log-in.
24. On the Install Modules page, the modules currently installed are displayed. Do
not install any modules now.
Before you continue, restart the Content Server Service OTCS service in the
Windows Services Panel (for example Control Panel > System and Security >
Administrative Tools > Services).
Click Continue.
25. On the Install Modules page, click Continue.
ERX100500-01-IWS-EN-3
26. Start Content Server Administration:
From the Start menu, click Open Text Content Server 10 (OTCS), and then
click Content Server Administration.
Alternatively, call this URL: http://localhost/OTCS/livelink.exe?
func=admin.index
27. The Create New Enterprise Data Source page opens. Set the parameter values
as displayed in the following screenshot.
Note: The amount of partitions depends on the amount of data. One

partition is okay for now and for small installations.
It is strongly recommended to use a more meaningful path outside the
application directory.
Click Create Processes.
28. A status window opens, displaying success or failure of the process creation.
Click Continue to complete the setup.
ERX100500-01-IWS-EN-3
29. A license page is displayed. Click Continue In Administrative Mode
Note: If you have a valid license at hand, you can also upload it. The
result is displayed on the page.
ERX100500-01-IWS-EN-3
This is the last Content Server configuration step. Click Go to Content Server
home page to access the Enterprise Workspace. It is now recommended to
change the Admin password.
ERX100500-01-IWS-EN-3
Chapter 11
Uninstalling the Document Undelete module
If Recycle Bin is installed, uninstall the Document Undelete module.
1. Go to the Content Server Administration Page (../OTCS/livelink.exe?

func=admin.index)
2. Go to Uninstall Modules in the Module Administration section.
3. Click Uninstall next to the Content Server Document Undelete module.
4. Restart the Content Server (OTCS) service when requested and click Continue.
ERX100500-01-IWS-EN-3
Chapter 12
Deploying the Web Content Services to Tomcat
Copy the cws.war file (C:\OPENTEXT\webservices\java\webapps) to Tomcat (C:

\Program Files\Apache Software Foundation\Tomcat 7.0\webapps).
ERX100500-01-IWS-EN-3
Chapter 13
Installing the Content Server modules
1. Go to the Content Server Administration Page (../OTCS/livelink.exe?

func=admin.index).
2. Go to Install Modules in the Module Administration section.
3. From the Installable Modules list, install the modules in accordance to the
dependencies between the modules.
Start with installing required modules that do not have any dependencies listed
in the Dependencies column.
4. After the installation of the selected modules is completed, Content Server

displays the Restart Content Server page. Restart the server instance of Content
Server.
Recommended order of installation
Note: Always restart the server instance of Content Server between the
steps.
1. Required modules with no dependencies.

For example Classifications, Customizations Run Time Environment,
Content Move, Content Server Generic Wizard, Archive Storage Provider,
Email Services, Calendar Attribute, Content Server SAP Base
2. Modules that depend on modules installed in the first step.

For example OpenText Enterprise Connect, Follow Up Management,
Records Management
3. Modules that depend on modules installed in the second step.

For example Extensions for Enterprise Library, Content Server Document
Templates
4. Modules that depend on modules installed in the third step.

For example Content Server - Case Management Base Modules
5. Modules that depend on modules installed in the forth step.

For example Case Management Base Roles Wizard
6. Modules that depend on modules installed in the fifth step.

For example Case Management
7. ECMLink
ERX100500-01-IWS-EN-3
Chapter 14
Testing Content Server search
To test Content Server search:
1. Login to Content Server with user Admin.
2. In your Personal Workspace, create the test folder My first test.
3. Wait about 5 minutes to get the folder full-text-indexed and search for the folder
name in the search box.
ERX100500-01-IWS-EN-3
Part 3
Installing patches
Chapter 15
Installing Enterprise Library patches
Mandatory Enterprise Library patches are installed by the master setup. However,
when a new patch collection is available after the release, you have to install it
manually.
At the Content Stop Content Server service and Content Server Admin service.
Server server:
To install the patches on Archive Server:
1. Download the current patch collection from: https://knowledge.opentext.com/

knowledge/cs.dll/Open/21827049
2. Follow the patch installation instructions for the patch collection.
3. Check the Spawner status with spawncmd status.
ERX100500-01-IWS-EN-3
Chapter 16
Installing Content Server patches using the cluster
management tool
Update Content Server to the current patch level. You can do this using the new
Content Server cluster management tool which allows for easy patch discovery and
deployment. Patch dependencies are enforced along with the removal of superseded
patches. All patches are deployed on a master instance. Once installed the
Administrator can validate the patches before pushing the changes to all other
instances in the cluster.
Tip: For more information, see Cluster Management Patch Deployment System
(https://knowledge.opentext.com/knowledge/cs.dll/Open/41561891) in the
OpenText Knowledge Center.
1. Go to the Content Server Administration Page ( ../OTCS/livelink.exe?

func=admin.index).
2. Go to Cluster Management in the Server Configuration section.
ERX100500-01-IWS-EN-3
Part 4
Configuring Enterprise Library Services
Chapter 17
Starting the Administration Client on Archive Server
To check successful installation, start Administration Client and add your server.
You have to add three server nodes:
• A server node for Archive Server
• A server node for Directory Services
• A server node for Enterprise Library Services
To add your servers:
1. In the Start menu, click OpenText > Administration Client.
2. In the Actions pane, click Add Server.
3. Enter the ELS server name.

4. Change the port to 8080 and choose the protocol (for example http). For the
Archive Server node, select Archive Server 10.5.0.
ERX100500-01-IWS-EN-3
Chapter 17 Starting the Administration Client on Archive Server
Click OK.
5. To create the server node for Directory Services, in the Actions pane, click Add
Server.
Directory Services node, select Directory Services 10.5.0.
ERX100500-01-IWS-EN-3
Click OK.
8. To create the server node for Enterprise Library, in the Actions pane, click Add
Server.
Directory Services node, select Enterprise Library 10.5.0.
ERX100500-01-IWS-EN-3
Chapter 17 Starting the Administration Client on Archive Server
Click OK.
11. Select one of the new servers. In the right pane, click Sign in. Sign in as the
default administration user otadmin@otds.admin. The password was defined
in “Installing Directory Services” on page 51.
ERX100500-01-IWS-EN-3
Repeat this step for all newly created servers.
If you can access the server, the installation so far has been successful.
ERX100500-01-IWS-EN-3
Chapter 18
Configuring OpenText Directory Services
Content Server must be registered as a resource with OpenText Directory Services

(OTDS). During the process, a unique ID, the resource ID, is generated. The user
(administrator) must record the ID and enter it on the OTDS Integration
Administration page. The resource ID and the (OTDS) server URL are required
values, and must be entered to set up (OTDS) authentication in Content Server.
18.1 Creating a resource ID

To create a resource ID:
1. To start Administration Client, click Start > All Programs > OpenText >
Administration Client.
2. Open Shared Services and select the respective server, <host name> (here:
vmeldev2:8080).
3. Sign in as otadmin@otds.admin.
4. Expand Directory Services and select Resources.

In the Actions pane, click New Resource.
5. In the New Resource wizard, click Next.

Enter the resource name for example OTCS or Content Server Resource.
ERX100500-01-IWS-EN-3
Chapter 18 Configuring OpenText Directory Services
Click Next.
6. Select User and group synchronization and as Synchronization connector,

select Content Server.
Keep the Create users and groups and Modify users and groups rights selected
and the Delete users and groups right unselected.
ERX100500-01-IWS-EN-3
18.1. Creating a resource ID
Click Next.
7. Select Advanced Configuration.
Click Next.
ERX100500-01-IWS-EN-3
8. Content Web Services were deployed during the installation of Content Server.
Click Next.
9. In the Connection Information screen, enter the respective user and password.
Change the connection settings for the Member Services and for the
Authentication Services from les-services to cws. Do not use localhost but a
fully qualified host name, for example vmmucels08.eng-muc-
test.opentext.net. For all other values, apply the default settings. Also keep
Admin as the user name.
To verify your settings, click Test Connection. If the result is successful, click
Next.
10. In the User Attribute Mapping screen, click Next.
11. In the Group Attribute Mapping screen, click Next.
12. Check the summary and click Finish.
ERX100500-01-IWS-EN-3
18.2. Setting the resource ID at Content Server
A resource ID is created.
13. In the Resource Identifier dialog, click Copy to Clipboard and continue with
OK.
Thereby, the resource ID is ready to be pasted in a following step.
Tip: Paste the copied resource ID in a temporary text file for future
reference.
14. Click OK.
18.2 Setting the resource ID at Content Server

To set the resource ID:
1. Switch to the Content Server Administration in a browser: http://<host

name>:8080/OTCS/livelink.exe?func=admin.index.
If asked, log in as Administrator.
2. In the Directory Services Integration Administration section, click Configure
Integration Settings.
3. Log in by entering Admin as Username. The default password is livelink.
ERX100500-01-IWS-EN-3
4. Select OTDS Authentication.

Paste the resource ID (should be still in the clipboard) in the Resource Identifier
field.
In the OTDS Server URL field, enter the OTDS server’s fully qualified host
name <HOSTNAME>.<DOMAIN NAME> (e.g. vmmucels08.eng-muc-
test.opentext.net)
Click Run Test. If (and only if) the test is successful, click Save.
5. Restart the Content Server service in the Server Manager or from the Content
Server Administration.
6. Restart the Apache Tomcat service in the Server Manager.
7. In the browser window, click Continue.
8. Optional If the Administration Client's Resource Activation window is still open,

click Verify Activation.
ERX100500-01-IWS-EN-3
18.3. Setting up a synchronized OTDS user partition from Active Directory
9. Select Server Configuration and click Configure Security Parameters.
10. In the Trusted Referring Websites box, check that the full qualified ELS server
name was added correctly.
18.3 Setting up a synchronized OTDS user partition

from Active Directory
For most of the customer installations these descriptions should fit. In case of issues
or major deviations please compare with a LDAP browser tool (eg Softerra LDAP
browser) or consult the local AD experts.
To create a user partition:
1. Start Administration Client (Start > All Programs > OpenText > Administration
Client).
3. Open Directory Services and select User Partitions.
4. In the Actions pane, click New Synchronized User Partition.

Specify the hostname of the directory server (eg.
Mydomaincontroller.opentext.com).
Leave the other port and encryption method as it is for now (Non-SSL).
5. Click Test Connection.

Confirmation for successful connection test should appear.
6. Click Next to configure Authentication.

Select Simple and specify a user including domain (eg. Eng-muc-test
\qmadmin) and the password. The user needs to have read permissions in the
Active Directory.
7. Click Test to test authentication.
8. Click Next to configure the Name and Description.

In our case we call the partition ECM. Uncheck the Use default …
configurationsetting.
ERX100500-01-IWS-EN-3
9. Click Next to specify Server Settings.

Use default setting AD (Active Directory) and ensure that the proposed Base
DN is correct.
10. Click Next to configure Group Locations.

Usually the proposed parameters can be accepted but ensure that the group
location setting the filter is suitable for your customer.
11. Click Next to configure User Locations.

Usually the proposed parameters can be accepted but ensure that the user
location setting and the filter is suitable for your customer.
12. Click Next to configure User Attribute Mappings.

In general the default OTDS attribute login name attribute sAMAccountName is
suitable.
Verify the user attribute mappings.
13. Click Next to configure Group Attribute Mappings.

In general the default OTDS attribute login name attribute sAMAccountName is
suitable.
Verify the group attribute mappings.
14. Click Next to configure Monitoring.

Here you configure how the synchronization should take place in the future.
The default settings can be accepted for now.
15. Click Next to configure Notifications and Search.

For most of the installations the default setting should be suitable.
16. Click Next to configure Extended Functionality.

For most of the installations the default setting should be suitable.
17. Click Next to get the summary.

Leave the setting Start importing users and groups automatically selected.
18. Click Finish.

Wait till users and groups are synchronized from AD to OTDS and to Content
Server before you continue.
ERX100500-01-IWS-EN-3
18.4. Editing memberships to OTDS roles
18.4 Editing memberships to OTDS roles

To edit memberships:
1. Start Administration Client (Start > All Programs > OpenText > Administration
Client).
3. Open Directory Services and select Access Roles.
4. Select Access to OTCS and click on Edit Members in the Actions bar.
In the User Partitions tab, select both partitions and click OK.
ERX100500-01-IWS-EN-3
Chapter 19
Configuring Archive Server
The following procedures are required to configure Archive Server for Extended
ECM for SAP Solutions to get a simple archive set up.
This setup will guide you through creating a disk volume of type HDSK. However
for production deployments, OpenText recommends that you consult Professional
Services to design an Archive Server implementation that properly utilizes the
storage devices listed in the Archive Server Storage Platforms Release Notes – for
implementations with a large volume of documents, using a disk volume of type
HDSK (many discrete files) can significantly increase operational backup and restore
times.
19.1 Creating the connection from Archive Server to

Content Server
To secure integrated archiving and records management scenarios, you must
configure the connection to Content Server inside Archive Server.
New: Since Update 2014.1, you can connect multiple instances of Enterprise
Library or Content Server to a single Archive Server. Hence, the configuration
of the Content Server connection in Archive Server has changed.
Update 2014.1 If you cannot find the configuration variable in the procedure below, install Update
2014.1 for OpenText Archive Server and OpenText Enterprise Library (or later) first.
For more information, see OpenText Archive Server and OpenText Enterprise Library -
Update Installation Guide (Windows) (AR-DWG) or OpenText Archive Server and
OpenText Enterprise Library - Update Installation Guide (UNIX/Linux) (AR-DUG).
Prerequisite Archive Server must be configured to use Directory Services as user management
system. For more information, see OpenText Archive Server - Administration Guide
(AR-ACN).
To configure the Content Server connection:
1. Change the values of several configuration variables in Archive Server:
a. Start Administration Client and sign in to Archive Server.

b. In the console tree, navigate to <server name> > Archive Server >
Configuration.
c. Search for the List of Record Access Information configuration variable
(internal name: RECORDACCESSINFO).
d. In the variable’s Properties, enter a list containing the access information
for documents that are elevated to records.
ERX100500-01-IWS-EN-3
Chapter 19 Configuring Archive Server
Insert the information in the following format:

<Content Server GUID>=<Content Server OTDS resource ID>:<Content
Server host name>:<Content Server port>@<Content Server OTDS
user>
Example:
4F61B240-3F36-445F-7AB3-4702EE063DB3=d5299cd0-166b-4bf4-80b8-
d58745097a06:vmelharv-prod:2099@otadmin@otds.admin
Note: To find out the value of <Content Server GUID>, enter the
following URL in a browser:
http://<Content Server>?func=ll.identify
To be sure, verify the value in the ot-elib.log file, for example:
<date> INFO [...]
com.opentext.ecm.services.entlib.impl.ELContentService --
initService(): Content Server system
GUID='4F61B240-3F36-445F-7AB3-4702EE063DB3'
You can find the value of <Content Server OTDS resource ID> in the
Administration Client: Directory Services > Resources > <resource> >
Edit.
2. Allow the Archive Server resource to impersonate users of the Content Server
resource anonymously:
a. Sign in to Directory Services.

b. In the console tree, expand Directory Services > Resources and select the
resource for Archive Server.
c. In the action pane, click Impersonation settings > Add Resource.
d. Select the Content Server resource and click OK.
e. Select the Anonymous check box for the Content Server resource.
Clear Allow this resource to impersonate its own users, as this is not
necessary, and click OK.
ERX100500-01-IWS-EN-3
19.2. Creating disk volumes for storage and for disk buffer
19.2 Creating disk volumes for storage and for disk

buffer
To create a disk volume for the pool of the logical archive:
1. On your hard disk, create the folders C:\A1Volume and C:\A1Buffer1.
2. Start Administration Client, select the corresponding server, and sign in as

otadmin@otds.admin.
3. Select Archive Server > Infrastructure > Disk Volume and in the Actions pane,
click New Disk Volume.
ERX100500-01-IWS-EN-3
4. As Volume name, enter A1Volume1, and as Mount path, browse for the folder
created in step 1 (C:\A1Volume).
5. As Volume class, select Hard Disk, and then click OK.
6. Create another volume with Volume name A1Buffer1 and as Mount path
browse for the folder created in step 1 (C:\A1Buffer1).
ERX100500-01-IWS-EN-3
19.3. Creating a buffer
7. As Volume class, select Hard Disk, and then click OK.
19.3 Creating a buffer

To create a buffer:
1. In the Administration Client select Archive Server > Infrastructure > Buffers
and in the Actions pane, click New Original Disk Buffer.
2. After clicking Next, click Finish to complete.
3. As next step attach the A1Buffer1 volume to the new buffer:
a. Right-click on the new buffer and select Attach Volume.

b. Select the prepared volume A1Buffer1 and click OK.
ERX100500-01-IWS-EN-3
19.4 Creating a logical archive

First, a logical archive must be created. After this, you can configure the different
settings of the archive.
To create a logical archive:
1. In the Console tree, select Archives > Original Archives and in the Actions
pane, click New Archive. The window to create a new logical archive opens.
2. In the Archive name box, enter A1.
Caution
SAP accepts archive names with maximum two characters only.
ERX100500-01-IWS-EN-3
19.5. Creating a pool
3. Click Next. A summary dialog shows your entries.
4. Click Finish. The original archive is created.
19.5 Creating a pool

To create a pool for archiving:
1. Select the A1 archive and in the Actions pane, click New Pool.
2. As Pool name, enter A1_POOL and as Pool type, select Single File.
ERX100500-01-IWS-EN-3
3. Click Next.
4. Apply the default settings and click Finish.
ERX100500-01-IWS-EN-3
19.5. Creating a pool
ERX100500-01-IWS-EN-3
19.6 Attaching a volume to a pool

To attach the prepared volume to the pool:
1. In the Console tree, select the A1 archive and in the Result pane, select
A1_POOL. In the Actions pane, click Attach Volume.
2. Select A1Volume1 and apply the default value for Priority of first attached
volume. -1 means no priority is set, i.e. the pool decides the priority. If several
volumes are assigned to a pool, the volume with the highest priority is used.
3. Click OK to resume.
ERX100500-01-IWS-EN-3
Chapter 20
Configuring the storage provider
The storage provider configuration connects the logical archives of Archive Server
with the Enterprise Library. Create a storage provider configuration for each logical
archive you plan to use in ECMLink.
To configure the storage provider:
1. On the Admin page , in the Archive Storage Provider Administration section,

click Configure Archive Storage Provider.
2. In the Archive Server field, enter the name of the Archive Server host.
3. Click Save Changes. Archive Storage Provider uploads its certificate to Archive
Server automatically.
4. Click OK.
ERX100500-01-IWS-EN-3
Chapter 21
Creating a storage provider and a storage rule
After the archive is ready to be used, you can configure Content Server to use it as
its storage.
To create a storage provider and a storage rule:
1. Switch to the Content Server Administration in a browser: http://<host

name>:8080/OTCS/livelink.exe?func=admin.index
2. In the Storage Provider Settings section, click Configure Storage Providers.
3. On the Add Item menu, select Enterprise Archive.
4. Enter a Name for the new storage provider, for example, OTDemo.
As Logical Archive, enter the name of the previously created archive (OTDemo).
As Storage Tier, you can only keep the default (none).
Select Delete Documents from Archive and Allow Content Move Operation.
ERX100500-01-IWS-EN-3
Chapter 21 Creating a storage provider and a storage rule
Click Submit.
5. The new storage provider is shown in the table.
Click the Admin Home link to get back to the Admin page.
6. In the Storage Provider Settings section, click Configure Storage Rules.
7. Click the “plus” icon to create a rule.
ERX100500-01-IWS-EN-3
8. As Rule, select Is an Enterprise Library object (value is ignored).
This means that all Enterprise Library documents created within Content Server
will be stored in the archive.
As Logical Storage Provider, select the storage provider created before
(OTDemo).
Click Submit.
ERX100500-01-IWS-EN-3
Chapter 22
Enabling certificates
Two certificates are required for Archive Storage Provider and for the ArchiveLink
interface. Usually, the certificates are uploaded automatically.
In any case, you must enable the certificates before they can be used.
To upload certificates:
1. Start Administration Client, select the appropriate server, and sign in as

administrator.
2. In the Console tree, select <server name> > Enterprise Library Services >
Configuration.
3. In the Actions pane, click Upload certificate and confirm the message with OK.
To enable certificates:
1. Select the archive in the console tree (Archive Server > Original Archives >
OTDemo).
2. In the result pane, select the Certificates tab and select a certificate.
3. In the action pane, click Enable. Enable both certificates.
Tip: You can also enable certificates in Archive Server > System > Key Store >
Certificates in the console tree.
ERX100500-01-IWS-EN-3
Chapter 22 Enabling certificates
This node additionally offers many more options to work with certificates, like
viewing them or changing their privileges, or importing certificates.
ERX100500-01-IWS-EN-3
Chapter 23
Creating an application
To create an Enterprise Library application:
1. Start Administration Client, select the appropriate server and sign in as

administrator.
2. Select Enterprise Library Services > Applications and in the Actions pane, click
New Application.
Important
As Application name, enter the system ID of the SAP system to be
attached later on.
3. In the Password and Confirm password boxes, enter a password.

Select Active and click Next.
Important
You will need this password later on for testing the application and for
accessing the application from the SAP system.
4. Do not select any Audit Interests and click Finish.
ERX100500-01-IWS-EN-3
Chapter 23 Creating an application
To set permissions for application:
1. Go to the Content Server 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.
ERX100500-01-IWS-EN-3
3. 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 (otadmin@otds.admin).
Only See and See Contents access rights for the groups DefaultGroup and
Public Access.
4. Add users and groups that must have access to this volume.
Grant full access to those users and groups that have to declare records within
the SAP system.
Note: If you choose to store records in Enterprise Workspace folders, set

the permissions for these folders accordingly. Users and groups that have
to declare records within SAP require full access to these folders. For more
information, see OpenText ECMLink for SAP Solutions - Customizing Guide
(ERLK-CGD).
ERX100500-01-IWS-EN-3
Chapter 24
Removing the UndeleteWS from the Enterprise
Library configuration
This step is only necessary if you uninstalled the Document Undelete module as
described in “Uninstalling the Document Undelete module“ on page 121.
To remove the workspace:
1. Start Administration Client, select the appropriate server and sign in as

administrator.
2. Open Enterprise Library Service > Configuration.
3. Edit the key elservice.livelinkRoots.roots.
4. Remove UndeleteWS, and click OK.
ERX100500-01-IWS-EN-3
Chapter 24 Removing the UndeleteWS from the Enterprise Library configuration
ERX100500-01-IWS-EN-3
Chapter 25
Testing Enterprise Library
This chapter describes how to test whether your installation was successful and
works as expected.
25.1 Starting the test application

This section describes how to get a sample client running for testing.
To set up the sample client:
1. Download the elclient_10.5.0.war file from https://

knowledge.opentext.com/knowledge/cs.dll/open/43574123 to the webapps
folder of your Apache Tomcat installation on the server hosting the Content
Server (here: C:/Program Files/Apache Software Foundation /Tomcat 7.0/
webapps).
2. Open your browser and enter http://localhost:

8080/elclient_10.5.0/elclient.jnlp
The client-specific login dialog for Enterprise Library opens.
Note: If you have a java permission problem, define alowser security level
at All Programs > Java > Configure Java > Security.
3. Log in as administrator (otadmin@otds.admin). As Server, specify Archive

Server.
4. Log in using user and password created for the application in the
Administration Client (QM8); see 5“Creating an application“ on page 171.
ERX100500-01-IWS-EN-3
Chapter 25 Testing Enterprise Library
25.2 Creating an item

To create an item using the sample client:
1. Select for example Admin Home and from the context menu, select Create
Item.
2. In the Select Type window, select dm.document, and then click Next.
ERX100500-01-IWS-EN-3
25.2. Creating an item
3. As no classification is defined, in the Select Classifications window, click Next.
ERX100500-01-IWS-EN-3
4. In the Edit Properties window, as Display Name enter a name, here: My New
Document from ELS and click Finish.
ERX100500-01-IWS-EN-3
25.2. Creating an item
5. The new item is displayed in the right pane of the test client:
ERX100500-01-IWS-EN-3
ERX100500-01-IWS-EN-3
Part 5
Installing Archiving and Document Access
for SAP Solutions
Chapter 26
Introduction
Archiving and Document Access for SAP Solutions consists of the following
software packages (for the current version numbers, check the latest Release Notes
in the OpenText Knowledge Center):
• OpenText SAP Basis package
• OpenText SAP ERP package (optional)
• OpenText SAP CRM package (optional)
• Enterprise Library package
• OpenText Imaging Clients package
• OpenText Imaging ExchangeLink (optional)
• OpenText Imaging NotesLink (optional)
ERX100500-01-IWS-EN-3
Chapter 27
Checking prerequisites
27.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).
• Basic knowledge of the employed operating system.
• Basic knowledge of the Enterprise Library.
27.2 Software packages

Archiving and Document Access for SAP Solutions consists of the following
software packages (for the current version numbers, check the latest Release Notes
in the OpenText Knowledge Center):
• OpenText SAP Basis package

• OpenText SAP ERP package (optional)
• OpenText SAP CRM package (optional)
• Enterprise Library package
• OpenText Imaging Clients package
• OpenText Imaging ExchangeLink (optional)
• OpenText Imaging NotesLink (optional)
27.3 Terms and definitions

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

OTEXxxx Package with the ID xxx
<SID> System ID of the 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 system
ERX100500-01-IWS-EN-3
Chapter 27 Checking prerequisites
27.4 SAP prerequisites

Check the following prerequisites prior to installation:
SAP support packages

Check the latest version of the Release Notes in the OpenText Knowledge Center
for required support packages for the employed SAP system prior to
installation!
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 following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
• SAP 7.00
• 822380 – Problems w/ add-on inst/upgrade to SAP NW 7.0 AS ABAP

• 822379 – Known problems with Support Packages in SAP NW 7.0 AS
ABAP
• 1597766 – Problems for add-on install./upgrade in SAP NW 7.31 AS
ABAP
ABAP
• 1843158 – Problems with add-on installation/upgrade to SAP NW 7.40 AS
ABAP
ABAP
• Installation information
1611525 – Archiving and Document Access 10.0 by OpenText
• SAPCAR tool
212876 – The new archiving tool SAPCAR
• Activation of the Business Configuration sets (BC sets)
1274142 – SCPR116: Activation links error in BC Set activation
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 16. This patch level is required for enhanced
functionality (e.g. additional icons in the GOS attachment list) based on the SAP
enhancement technology.
ERX100500-01-IWS-EN-3
27.5. Installation tool
Note: The documentation is updated regularly; therefore, check for the latest
version in the OpenText Knowledge Center.
27.5 Installation tool

Archiving and Document Access for SAP Solutions 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 single PAT files are archived in SAPCAR files (extension
*.SAR) that can be extracted using the SAPCAR command line tool. The different
SAPCAR files are located in a DATA folder below the respective package folder
named as the package and SAP release (e.g.
INST_BAS_700/DATA/OTEXBAS_INST_1050_700.SAR contains the archived PAT file
to install the package for SAP basis release 7.00 or higher).
Notes
• The handling of the installation procedure within SAINT differs depending

on the SAP system used. For more details, see the respective SAP
documentation.
• The SAP OSS Note 1353451 Use enhanced SAINT functions in CRM ADDON
MANAGER (http://service.sap.com/sap/support/notes/1353451) describes
how to use enhanced SAINT functions on CRM systems, for example
selecting target Support Packages.
27.6 Password control

Every single installation package for Archiving and Document Access for SAP
Solutions is protected with a specific password. During the installation, this
password is requested by SAINT.
For more details, see the following table:
Table 27-1: Installation packages and passwords
Package Release Designation Password

OTEXBAS 1050_700 Archiving and 9DCA66CC0F
Document Access for
SAP Solutions Basic
Component 10.5.0
OTEXERP 1050_600 Archiving and 9DCD75CF0F
Document Access for
SAP Solutions ERP
Component 10.5.0
ERX100500-01-IWS-EN-3
Chapter 27 Checking prerequisites

OTEXCRM 1050_700 Archiving and 9BCB75D20F
Document Access for
SAP Solutions CRM
Component 10.5.0
A possible delta upgrade, for example an upgrade from version 10.0.0 to version
10.5.0 while keeping the same SAP release, is also performed with SAINT. For
version 10.5.0, this upgrade is also performed with the help of the respective
installation package in transaction SAINT.
27.7 Web Dynpro configuration

Configuring Web Dynpro comprises the following stages:
• General Web Dynpro configuration of the web application server(s) which
provide the Web Dynpro UI (such as configuration of the ICM, activating
services, etc.). For details see the SAP documentation.
• Check the activation of the following services by executing the SICF transaction:
• <Path of Web Dynpro services>/ixos/dc
• <Path of Web Dynpro services>/ixos/dcview
To configure the Web Dynpro UI for the ArchiveLink Full Text Search, see OpenText
Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS) and
OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
ERX100500-01-IWS-EN-3
Chapter 28
Installing Basis package
This chapter describes the installation of the Basis package of the Archiving and
Document Access for SAP Solutions on an SAP application server. Read also the
chapter “Checking prerequisites“ on page 187 with general information on
installation in an SAP environment.
The Basis package contains several basic functions that are required by other
components of the Archiving and Document Access for SAP Solutions:
• Basic components
• Rendition management
• Forms management
• DesktopLink
• Imaging integration
• Migration management
• DocuLink
• DocuLink Web UI (based on Web Dynpro framework)
Tip: The Basis package also includes the OpenText License Report function
that is described in more detail in the OpenText Archiving and Document Access
for SAP Solutions - Scenario Guide (ER-CCS).
28.1 Installing package

The basic components are installed with the Basis package.
To install Basis package:
1. Copy the respective SAPCAR files (*.SAR) located on the installation medium in
Archiving and Document Access for SAP Solutions\SAP to the target SAP
application server in the /usr/sap/trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.
File Source Path Target path

OTEXBAS_INST_1050_700. INST_BAS_700\DATA\ /usr/sap/trans /usr/sap/
SAR trans
SP_BAS_700\DATA\
OTEXBAS_SP_1050_700_01 /usr/sap/trans /usr/sap/
.SAR trans
ERX100500-01-IWS-EN-3
Chapter 28 Installing Basis package
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.
Note: With Basis 7.00 or higher, you can use the SAINT and SPAM
transactions to upload and extract the SAR files from the frontend.
3. Carry out import of packages as described in the respective SAP

documentation. For this, you will need the password for the installation
package. For more information, see“Password control” on page 189.
4. After import has been finished, continue with the activation of the BC sets.
For every client, the Business Configuration Sets (BC Sets) must be activated after
installation.
To activate BC sets:
1. Execute the SCPR20 transaction.

The Business Customizing Set screen appears
2. Activate the BC Sets in the following sequence:
• /OTEXBAS/BASIS_ARCHIVING_1
• /OTEXBAS/DOCULINK_ALL1050
• /OTEXBAS/VIEWER_CUSTOMIZING
Note: For more details, see the SAP documentation.
3. If you experience errors during BC Set activation, repeat the respective

activation procedure up to three times.
Tip: Transaction SCPR20 offers a menu option Utilities > Compare >
Compare BC Set with Tables. This allows you to compare the differences
between the contents of the Business Configuration Set and the
customizing tables of the SAP system. Furthermore, another option of this
feature allows you to display all contents of the BC set.
For every client, the default project $GARMISCH is required by DocuLink.
To create the DocuLink project $GARMISCH initially:
1. Execute the J6NA transaction.
2. Execute the item Initial creation of project $GARMISCH.

The start screen of the /IXOS/DC_A_CREATE_GARMISCH report is displayed.
ERX100500-01-IWS-EN-3
28.1. Installing package
3. To actually create the DocuLink project $GARMISCH on your client, select the
checkbox Create $GARMISCH. Execute the report by pressing the F8 function
key.
The program confirms the execution with a message Project $GARMISCH
created.
4. Exit the report and the J6NA transaction and execute the J6NP transaction.
In the list of the existing DocuLink projects, the project $GARMISCH is listed.
Note: This DocuLink project $GARMISCH may not be modified manually. It

must either be created with the initial report or imported by a transport.
To export the DocuLink project $GARMISCH from your customizing client:
1. Execute the J6NP transaction.

The DocuLink: Customizing: Project Overview dialog is displayed.
2. Click on the $GARMISCH item to position the cursor on this DocuLink project.
3. Click the icon or press SHIFT-F6.

The Transport version(s) dialog is displayed.
4. Keep the settings as they are and click the Continue button or press ENTER.
You are prompted to select a transport request.
5. Create a customizing request and click the Continue button or press ENTER.
6. After the transport request was created, you may leave the J6NP transaction and
follow the standard procedure as described by SAP to release a customizing
transport request.
Regarding the export of DocuLink projects as customizing transport requests, refer

also to the chapters OpenText DocuLink for SAP Solutions - Customizing and
Administration Guide (DC-CGD) and OpenText DocuLink for SAP Solutions -
Customizing and Administration Guide (DC-CGD).
Important
The customizing tables which contain the content of the DocuLink project
customizing are flagged with Log data changes, i.e. you may use the SCU3
(table history) transaction to track any changes in the DocuLink project
customizing.
ERX100500-01-IWS-EN-3
28.2 Configuring components

28.2.1 Setting number ranges
For the number range objects /IXOS/DCLO and /IXOS/DC_K, the number range
interval 01 must be set by an authorized user.
To set /IXOS/DC_K:
Note: A number range for this object is only necessary if archiving is

performed to tables which contain the document ID in the key.
1. Execute the SNRO transaction.
2. Enter /IXOS/DC_K as object.
3. Click the Number ranges button.
4. Click the Change intervals button.
5. Click the Insert interval button.
6. Modify the interval 01:

From number = 1, To number = 9999999999.
7. Save your changes.
To set /IXOS/DCLO:
Note: The number range for the /IXOS/DCLO object is only necessary if the
protocol feature is activated for the attribute objects.
• Repeat the procedure as described for the /IXOS/DC_K object, using the interval
01:
From number = 1, To number = 9999999999.
28.2.2 Defining authorizations

You must set up authorizations and assign them to users. Some authorization
profiles are also supplied by the following components of Archiving and Document
Access for SAP Solutions:
• Forms Management
see OpenText Archiving and Document Access for SAP Solutions - Installation and
Upgrade Guide (ER-IGD) for details
• DesktopLink
see OpenText Archiving and Document Access for SAP Solutions - Installation and
Upgrade Guide (ER-IGD) for details
• DocuLink
ERX100500-01-IWS-EN-3
28.2. Configuring components
see “Authorizations” on page 196 for details
Tip: For an overview of authorization maintenance, see OpenText Archiving and

Document Access for SAP Solutions - Scenario Guide (ER-CCS).
28.2.3 Defining settings for logging

To use the user action log, you must set the number range /IXOS/DCLO as described
in “Setting number ranges” on page 194.
For details on the user action log see OpenText DocuLink for SAP Solutions -
Customizing and Administration Guide (DC-CGD).
28.2.4 Defining settings for optional sample projects

Optional DocuLink sample projects are available as downloads; for more details, see
OpenText DocuLink for SAP Solutions - Customizing and Administration Guide (DC-
CGD). If you want to use these projects, you must define a number of additional
settings in the SAP application.
• If you want to test the authorization check on data selection in the sample project
Linked objects then you must also assign the users the profile J_6NB_PROF
supplied with the sample project.
• In order to archive documents for customers within the document flow SD, the
archive must be set correctly in OAC3 transaction for the link J_6NGDKOR (object
type)/J_6NGDKORR (document type).
Note: Each customer has its own logical archive. Since we are not familiar
with these archives, we supply our own archive name DU set as the default.
• In order to archive documents for customers in the sample project Linked
objects, the archive must be set correctly in OAC3 transaction for the link
J_6NG_CUST/J_6NG_CUST.
Note: Each customer has its own logical archive. Since we are not familiar
with these archives, we supply our own archive name DU set as the default.
• Some number range intervals are required for the sample projects; use the SNRO
transaction to maintain them:
• For $EX_LINK (Linked objects) and $EX_FOLDER (Folder demo (recurrent

structure)) maintain interval 01 for the number range J_6NG_DIV. Enter
1000 as the starting number.
• For $EX_CMDEMO (Demo CM document model) maintain the same number
range J_6NG_DIV, but with a different interval and distinct values, e.g.
interval 02 from 1000000001 - 2000000000 if the interval 01 from 1000 -
1000000000 was used for $EX_LINK.
ERX100500-01-IWS-EN-3
28.3 Authorizations
Authorization profiles have to be assigned to users who are working with Forms
Management (see OpenText Archiving and Document Access for SAP Solutions -
Scenario Guide (ER-CCS) for details).
Example:
• Profile J_8AFM_ALL: Possesses all authorizations.

28.4 DocuLink
As part of the Basis package installation, the component OpenText DocuLink for
SAP Solutions (short: DocuLink) is installed as well. Read also the chapter
“Checking prerequisites“ on page 187 with general information on installation in an
SAP environment.
28.4.1 General information

The following SAP partner name spaces are used:
• /IXOS/
• J6N*
28.4.2 Authorizations
Some authorization profiles are also supplied by DocuLink which you can use as a
basis to set up profiles (see OpenText DocuLink for SAP Solutions - Customizing and
Administration Guide (DC-CGD) for details).
Examples:
• Profile J_6NG_MIN: Minimum profile for entry to DocuLink (without projects).

• Profile J_6NG_CREA: Display and create authorization for all projects.
• Profile J_6NG_ALL: Possesses all authorizations; suitable for testing DocuLink.
To modify authorizations:
1. Execute either the SU02 or PFCG (Profile Generator) transaction to modify the
authorizations.
2. Each user must be assigned the minimum profile J_6NG_MIN as otherwise

nothing will be visible when the user attempts to call DocuLink!
ERX100500-01-IWS-EN-3
28.4. DocuLink
3. Enter a user to test the general authorization J_6NG_ALL. This user can then test
all functions to ensure that they work and thus ensure that installation has been
completed successfully.
4. After assigning authorizations, do not forget to log on to the SAP application

system again.

28.4.3 Testing the DocuLink installation

After the DocuLink installation has been completed, you can test the installation
with the J6NY or the J6NP transaction in a SAP GUI in the client <MDT>.
If it is not possible to execute the transaction, reset all buffers using the /$SYNC or /
$TAB transaction .
Note: This action is not recommended during live operation of the system.
Then repeat the installation.
To check the installation:
1. Execute the J6NY transaction in a SAP GUI in the client <MDT>.
2. Double-click a project in the J6NY transaction; the appropriate view(s) should

appear.
Note: This is only possible if you have imported the supplied DocuLink
sample projects. We recommend that you complete this optional import of
the sample projects for testing purposes.
If no error message appears, the installation was successful.
However, if you receive the error message (OL 808)
The object with the runtime number '0' is not defined
the supplied object types could not be generated. In this case, perform the following
procedure.
To generate object types:
1. Execute the SE80 transaction.
2. Enter J6NG as the development class.
3. Click the Display button.
4. Open the Business Engineering folder.
ERX100500-01-IWS-EN-3
5. Open the Business object types folder.

6. For each of the listed object types:
a. Double-click the object type.

b. Click Generate.
No success message appears.
ERX100500-01-IWS-EN-3
Chapter 29
Installing ERP option package
In addition to the Basis package, you may install the optional ERP package on ERP
systems. The ERP package contains ERP-specific coding of the Archiving and
Document Access for SAP Solutions.
29.1 Installing the ERP package

To install ERP package:
1. Copy the respective SAPCAR file (*.SAR) located on the installation medium in
File Source path Target path

OTEXERP_INST_1050_600. INST_ERP_600\DATA\ /usr/sap/trans
SAR

following command:
of the SAPCAR file.
3. Carry out import of package as described in the respective SAP documentation.
Note: The optional ERP package does not contain any Business Customizing
Sets (BC Sets).
ERX100500-01-IWS-EN-3
Chapter 30
Installing CRM option package
In addition to the Basis package, you may install the optional CRM package on CRM
systems. The CRM package contains coding to support the CM hierarchy link range
CRM in DocuLink and CRM-specific coding for the CIC integration as described in
the OpenText DocuLink for SAP Solutions - Customizing and Administration Guide (DC-
CGD).
30.1 Installing the package

To install CRM package:
1. Copy the respective SAPCAR file (*.SAR) located on the installation medium in
File Source path Target path

OTEXERP_INST_1050_600. INST_ERP_600\DATA\ /usr/sap/trans
SAR

following command:
of the SAPCAR file.
Note: The optional CRM package does not contain any Business Customizing
Sets (BC Sets).
ERX100500-01-IWS-EN-3
Chapter 31
Installing language packages
This chapter describes how to install language packages on an SAP system.
Note: Depending on the delivery bundle, you may also have an ISO image file
containing installation files for components that must not be installed on an
SAP system, for example, language installations of Imaging clients. For more
information, see the installation guides and release notes for these components.
The Add-On installation packages and Add-On support packages include the
default language, which is English. You must use the language packages to install
other languages. For more information about available languages, see the current
Archiving and Document Access for SAP Solutions Release Notes. You can find the
language packages related to the SAP Add-Ons of OpenText Archiving and
Document Access for SAP Solutions in the OpenText Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/14162727).
Language packages for support packages
If not stated otherwise, the language packages of OTEXBAS related to support

packages are cumulative. They include merged language texts of the main
version and of previous and current support packages.
To install a language package:
1. In the OpenText Knowledge Center, go to Archiving and Document Access for

SAP Solutions (https://knowledge.opentext.com/knowledge/cs.dll/open/
16514323) and then go to the Downloads area. Note that you can also obtain the
language packages for support packages and other patches navigating through
the Patches area. Do one of the following:
• If you have installed the installation Add-Ons, select and open the folder for
your version. Open the Language Packs folder, select and open your
language folder, and then download the ADA_<version>_<language
abbreviation>.zip file that contains the language packages as *.SAR files.
• If you have also installed the support packages (recommended), select and
open the folder for your support package version. Open Software >
Languages folders, select and open your language folder, and then
download the ADA_<version>_<language abbreviation>.iso file. On the
ISO image, you will find all available language package files for the selected
language in the OpenText SAP Language Packages folder.
For more details, see the text file stored with the corresponding language
package file in the language folder.
ERX100500-01-IWS-EN-3
Chapter 31 Installing language packages
2. Upload your language file to your SAP system. Each ABAP Add-On has a
specific language package.
Example: DE_OTEXBAS_1050_700_20140514.SAR contains the German package for

the OTEXBAS 10.5 Add-On on SAP_BASIS 7.00.
Note: Note the following options:
• If you use a system with SAP_BASIS 7.00, you can import and extract
the file directly in transaction SMLT.
• If you use any other system, extract the SAPCAR file with the .SAR
extension to the SMLT path folder of your SAP system. Usually the path
is set to the EPS\in system folder. Use the SAPCAR tool to extract the
file.
3. Use transaction SMLT to import your language package.
Important
Before starting to import language packages, OpenText recommends
reading the SAP help (http://help.sap.com/) about importing a language.
In the SAP help, navigate to the application help for the appropriate SAP
release and read the following chapters:
• Preparing to Import a Language

• Importing a Language
• Language Import with Transaction SMLT
• Post-Import Actions
4. After installing the language package, perform the necessary post-installation

steps, for example, such as those described in sections Language Supplementation/
Client Maintenance in the SAP help (http://help.sap.com/). Note that the
language package of OTEXBAS contains client dependent data which requires
specific action Client maintenance in transaction SMLT.
Note: After importing language packages to the SAP system, it can

become necessary to reset certain buffers. For example, you can use the
following transactions:
• /$SYNC - reset all buffers

• /$OTR - reset OTR text buffers (HTTP texts)
• /$CUA - reset SAP GUI object buffers
• /$DYNP - reset SAP GUI dynpro buffers
ERX100500-01-IWS-EN-3
Chapter 32
Handling communication protocols
Communication protocols define the way a document class is handled in SAP

applications. A protocol is assigned to an archive (content repository, storage
system). This ensures that all documents of a document class held in the same
archive (content repository) are handled in the same way.
Tip: For more information on protocols, see OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).
This chapter describes the handling of the ArchiveLink communication protocols on

an SAP application server. You have to perform a manual configuration of the two
main protocols OT_OLEU1 and OT_HTTP2.
32.1 Maintaining OLE application

The OLE applications for Livelink Archive Windows Viewer (ALVIEWER.APP) and
Livelink Imaging: Enterprise Scan (IXOS.IXSCAN.SC2SAP) have to be modified or
created if they do not exist yet.
To modify or create OLE applications:
1. Execute the SOLE transaction and go to change mode.
2. Check if OLE applications ALVIEWER.APP and IXOS.IXSCAN.SC2SAP exist.
3. Create or check the Livelink Archive Windows Viewer application using the
following values:
OLE application
ALVIEWER.APP
CLSID
{30446849-11E3-11D0-9D4E-0020AFC0E4C0}
Type Info key

NO_TYPELIB
ERX100500-01-IWS-EN-3
Chapter 32 Handling communication protocols
4. Click .
The ClassId (CLSID) is registered for the OpenText Imaging Windows Viewer
application.
5. Execute the SOLE transaction and go to change mode.
6. Create or check the OpenText Imaging Enterprise Scan application using the
following values:
OLE application
IXOS.IXSCAN.SC2SAP
Version number
3.5
CLSID
{51F3EF73-DB09-11CF-8B31-0020AFF270C3}
Type Info key

NO_TYPELIB
ERX100500-01-IWS-EN-3
32.2. Maintaining SAP ArchiveLink application
7. Click .
The ClassId (CLSID) is registered for the OpenText Imaging Enterprise Scan
application.
32.2 Maintaining SAP ArchiveLink application

If the ArchiveLink applications do not already exist, you have to create them
manually.
The following ArchiveLink applications must be present:
• IXSCAN
• IXSCAN_HTTP
• IXVIEWER
• IXVIEWERURL
• IXVIEWERURLOA
To modify or create ArchiveLink application:
1. Execute the OAA4 transaction (ArchiveLink Application Maintenance).

If not already listed, create the ArchiveLink applications listed above
(IXSCAN_HTTP, IXVIEWER, IXVIEWERURL, IXVIEWERURLOA).
2. Double-click the specific ArchiveLink application entry for additional

configuration.
All functions for the selected ArchiveLink application are listed.
ERX100500-01-IWS-EN-3
3. Double-click a specific function to maintain or modify its settings.

The following shows the maintaining screen of function Archive from frontend
for the ArchiveLink application IXSCAN as an example.
ERX100500-01-IWS-EN-3
4. Enter the application name, specify events (M - Method, S - Set, G- Get) and the
corresponding commands according to the following tables.
Note: In the following tables, only maintained functions are explicitly

listed; all other functions should not be changed!
IXSCAN
Function Application Event Command

Archive from IXOS.IXSCAN.SC M SendDoc2DP @AID,
Frontend 2SAP
G @DID=DocID
G @EID=ErrorID
Store File on IXOS.IXSCAN.SC M SaveActiveDocMultipage 0
Frontend 2SAP
G @DPA=DocPathName
G @EID=ErrorID
ERX100500-01-IWS-EN-3
IXSCAN_HTTP

Archive from IXOS.IXSCAN.SC M SendDoc2Archive @AID, @DID, @URL
Frontend 2SAP
G @DID=DocID
G @EID=ErrorID
Store File on IXOS.IXSCAN.SC M SaveActiveDocMultipage 0
Frontend 2SAP
G @DPA=DocPathName
G @EID=ErrorID
IXVIEWER

Display Stored ALVIEWER.APP S Language=@LAN
Document
M ShowAppWindow
M OpenDocumentSimple
@WID,@AID,@DID,@WIT,@UID
G @EID=R3ReturnCode
Retrieval on ALVIEWER.APP M GetDocument @AID,@DID,@DPA, ,
Frontend
G @EID=R3ReturnCode
Display Local File ALVIEWER.APP M ShowAppWindow
M OpenDocumentFromFiles
@WID,@DPA,@DTI,@WIT,@UID
G @EID=R3ReturnCode
Archive from ALVIEWER.APP M ArchiveDoc @AID,
Frontend
G @DID=DocID
G @EID=ErrorID
Store File on ALVIEWER.APP M GetDocument @AID,@DID,@DPA,,
Frontend
G @EID=R3ReturnCode
Close Window ALVIEWER.APP M CloseStack @WID
IXVIEWERURL
ERX100500-01-IWS-EN-3

Document
M ShowAppWindow
M OpenDocumentSimpleUrl
@WID,@URL,@WIT,@UID
G @EID=R3ReturnCode
Retrieval on ALVIEWER.APP M GetDocument @AID,@DID,@DPA, ,
Frontend
G @EID=R3ReturnCode
G @EID=R3ReturnCode
Frontend
G @DID=DocID
G @EID=ErrorID
Frontend
G @EID=R3ReturnCode
IXVIEWERURLOA

Document
M OpenDocumentSimpleUrl
@WID,@URL,@WIT,@UID
G @EID=R3ReturnCode
G @EID=R3ReturnCode
Frontend
G @DID=DocID
G @EID=ErrorID
ERX100500-01-IWS-EN-3

Frontend
G @EID=R3ReturnCode
32.3 Assigning protocols to logical archives (content

repositories)
These protocol settings define the protocol to be used for all documents in a specific
logical archive.
To assign a protocol to a logical archive:
1. Execute the OAC0 transaction.
2. Select an already created logical archive and click the Full Administration
button.
3. Enter either OT_HTTP2 or OT_OLEU1 in the Protocol field.
4. Click to store the settings.
ERX100500-01-IWS-EN-3
Part 6
Setting up ECMLink for SAP Solutions
Chapter 33
Checking the prerequisites
33.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 OpenText Enterprise Library, in particular its Records
Management, User Management and Directory Service components.
• Basic knowledge of the employed operating system.
33.2 Prerequisites
33.2.1 SAP prerequisites
ECMLink supports the following SAP products:
• SAP ERP 6.0

• SAP CRM 7.0
Note: Content Server UI Widget Integration is only supported for Business

Workspace UI Integration in SAP CRM.
CRM Requirement: CRM 7.0 Ehp 1.
OTDS Requirement: 10.5 or higher
• SAP SRM 7.0
Check the following prerequisites for SAP prior to installation:
Archiving and Document Access for SAP Solutions

The component OTEXBAS of Archiving and Document Access for SAP Solutions
must be installed on your SAP system. Check the Release Notes for required
versions and dependencies. This component is provided on the ECMLink
installation medium. For more information, see OpenText Archiving and
Document Access for SAP Solutions - Installation and Upgrade Guide (ER-IGD)
SAP support packages

Check the latest version of the Release Notes in the OpenText Knowledge Center
for required support packages for the employed SAP system prior to
installation!
ERX100500-01-IWS-EN-3
Chapter 33 Checking the 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).
SAP notes
Check the respective SAP notes and make sure they are applied:
SAP Note Required for

110910 Some language-dependent texts may not be displayed
correctly in the GUI.
207196 Some sample project data may not be displayed despite a
correct transport of the sample data and correct
authorizations.
884077 Log-on error from external systems to WAS 7.00 systems:
The external candidate's password contains at least one
lower case letter. In accordance with the rules, which were
valid up to and including WAS 6.40, the registration
application changes the passwords to capital letters.
However, as of WAS 7.00 (see SAP Note 862989), the
system can be set in a way that it distinguishes between
upper case and lower case letters in a password. In this
case, the log-on fails if the original password contains at
least one lower case letter.
1128338 CALL_BROWSER does not launch a new window to open
the URL, even when the NEW_WINDOW parameter is
passed to the function module. Instead, an existing window
is used to open the URL.
However, as of SAP Note 1177636, the behavior of
CALL_BROWSER is changed to allow also opening URLs
on other platforms than Microsoft Windows. In this case,
the settings of the MS Internet Explorer govern the URL
handling, i.e. whether a new window is opened.
1117696 Required for the declare functionality in the attachment list
of the generic object service (GOS).
1255948 Required for the declare functionality of the print lists.
1227752 Required to avoid known problems with the web services.
1122938
(SAP ERP 6.0 and
SAP_BASIS 14 or higher)
1424747 Enables the transmission of SOAP error codes to identify
problems.
1267258 Unexpected error message No vendor specified when log-
on language is English.
ERX100500-01-IWS-EN-3
33.2. Prerequisites
SAP Note Required for

822380 Required to avoid known problems with the SAP Add-On
(SAP 7.00) Installation Tool (SAINT).
212876
(SAPCAR tool)
1382711 Required when using SAP CRM Investigative Case
1379958 Management.
1613012
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 16. This patch level is required for
enhanced functionality, for example, additional icons in the GOS attachment
list, based on the SAP enhancement technology.
• Patch level for SAP CRM 7.0
SAP_ABA is release 701, patch level 03
BBPCRM release 700, patch level 02
WEBCUIF release 700, patch level 02.
Content Server UI Widget Integration is only supported for CRM 7.0 Ehp 1.
• Patch level for SAP SRM 7.0
SAP_ABA is release 701, patch level 07; for component SRM_SERVER the
minimum requirement is release 700, patch level 08.
Note: The documentation and the release notes are updated regularly;
therefore, check for the latest version in OpenText Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/16514655).
Basis package of Archiving and Document Access for SAP Solutions
Prior to the SAP Add-on package OTEXRL of ECMLink you must install the
SAP Add-On OTEXBAS of Archiving and Document Access for SAP Solutions
10.5 SP1. For more information, see OpenText Archiving and Document Access
for SAP Solutions - Installation and Upgrade Guide (ER-IGD).
ERX100500-01-IWS-EN-3
33.2.2 Enterprise Library prerequisites

Important
See the Release Notes for a comprehensive and most current list of
prerequisites.
Note: ECMLink provides two different versions of the module for Content
Server and the web services: Version 10.0.5 for Content Server 10.0, and version
10.5.1 for Content Server 10.5. Both run with the same ECMLink SAP Add-on
which has version 10.5.1.
The Enterprise Library prerequisites differ for the two versions.
33.2.2.1 Enterprise Library prerequisites for ECMLink 10.5.1

Check the following prerequisites for Enterprise Library prior to the installation of
SAP Add-On package OTEXRL:
Installation of Enterprise Library and Archive and Storage Services

Both services must be installed. Archive and Storage Services is part of Archive
Server. Install Enterprise Library 10.5 and Archive Server 10.5. Additionally,
install the patches provided on the ECMLink installation medium.
Important
ECMLink is not compatible with the Enterprise Library Interview
module which is an optional Case Management module. Do not install
this module in combination with ECMLink.
ArchiveLink customizing
Customizing of the SAP system and the Archive and Storage Services must be
completed according to OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS).
Host/port for the logical archive
Check that store and retrieval of ArchiveLink documents functions properly
with the server.
Important
With the Archive Server 10.5 version, the logical archive (OAC0
transaction) must use the Archive and Storage Services host/port.
For older Archive Server versions, it must use the Enterprise Library
host/port and not the Archive and Storage Services host/port. In this
case, restrict access to the Archive and Storage Services host/port
exclusively to the Enterprise Library via a firewall configuration.
If you are using a firewall between SAP and Content Server and Enterprise
Library the following ports must be enabled:
• 8080 HTTP or 8090 HTTPS on Apache Webserver: used for the Web service
communication from SAP to the Enterprise Library server.
ERX100500-01-IWS-EN-3
33.2. Prerequisites
• 8000: used for the communication between SAP Base and the SAP Client.
• 80 (HTTP) or 443 (HTTP): only required for connection tests from SAP to
Content Server.
Required patches for the installed Content Server version

Content Server 10.5 SP1 - The security fixes for Content Server are vital for
proper installation; if you already have a Content Server installation, make sure
you have installed Content Server 10.5 SP1. Additionally, install the additional
patches provided in the Patches folder on the Extended ECM for SAP Solutions
installation medium and the current Enterprise Library patch collection at
https://knowledge.opentext.com/knowledge/cs.dll/Open/21827049.
You can also use the cluster management tool to install patches. For more
information, see “Installing Content Server patches using the cluster
management tool“ on page 133.
Note: If you create a completely new system, Content Server 10.5 SP1 will
be installed by the master setup.
Important
Prior to installation, make sure that you have read the information in
OpenText Content Suite Platform - Installation and Upgrade Guide (EL-IGD) and
OpenText Enterprise Library - Scenario and Configuration Guide (EL-GGD) for
the relevant version.
33.2.2.2 Enterprise Library prerequisites for ECMLink 10.0.5 Content

Server module
This section is only relevant if you want to install ECMLink 10.0.5 on an existing
installation of Content Server 10.
Check the following prerequisites for Enterprise Library prior to the installation of
SAP Add-On package OTEXRL:
Installation of Enterprise Library and Archive and Storage Services

Both services must be installed. Install the Enterprise Library 10.2.1 Update 10.
Additionally, install the patches provided on the ECMLink installation medium.
Important
ECMLink is not compatible with the Enterprise Library Interview
module which is an optional Case Management module. Do not install
this module in combination with ECMLink.
ArchiveLink customizing
Customizing of the SAP system and the Archive and Storage Services must be
completed according to OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS).
Host/port for the logical archive
Check that store and retrieval of ArchiveLink documents functions properly
with the server.
ERX100500-01-IWS-EN-3
Important
The logical archive (OAC0 transaction) must use the Enterprise Library
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 via a firewall configuration.
If you are using the Archive Server 10.5 version, the logical archive (OAC0
transaction) must use the Archive and Storage Services host/port.
If you are using a firewall between SAP and Content Server and Enterprise
Library the following ports must be enabled:
• 8080 (HTTP) or 8090 (HTTPS) on Apache Webserver: used for the Web
service communication from SAP to the Enterprise Library server.
• 8000: used for the communication between SAP Base and the SAP Client.
• 80 (HTTP) or 443 (HTTP): only required for connection tests from SAP to
Content Server.
Required patches for the installed Content Server version

Content Server 10.0.0 - The security fixes for Content Server are vital for proper
installation; if you already have a Content Server installation, make sure you
have installed Content Server 10.0.0 including the Content Server Update 2014.9.
Additionally, install the additional patches provided in the Patches folder on the
Extended ECM for SAP Solutions installation medium.
Important
Prior to installation, make sure that you have read the information in
OpenText Content Suite Platform - Installation and Upgrade Guide (EL-IGD) and
OpenText Enterprise Library - Scenario and Configuration Guide (EL-GGD) for
the relevant version.
33.3 SAP Add-On Installation Tool (SAINT)

ECMLink uses the SAP Add-On Installation Tool (SAINT) for installation of the SAP
part of ECMLink. 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 details see the SAP documentation.
Installation packages and passwords

The SAP package for ECMLink is protected with a specific password. During
installation, this password is requested by SAINT.
For details, see the following table:
ERX100500-01-IWS-EN-3
33.4. Finding version information for ECMLink relevant system components
Table 33-1: Installation packages and passwords

OTEXRL 1050_700 OpenText ECMLink for SAP B0D8629A1F
Solutions
OTEXRLC 1050_700 OpenText ECMLink for SAP B6D862F91F
Solutions SAP CRM Add-On
OTEXRLS 1050_700 OpenText ECMLink for SAP B0D862E91F
Solutions SAP SRM Add-On
Note: You only need these passwords and packages if they are not already
installed in your system.
33.4 Finding version information for ECMLink

relevant system components
This chapter explains how you can find out which version of the different
components is used in your system.
Version information is also included in the system reports of Content Server and the
configuration report SAP System.
• Content Server
From the Content Server menu, select Help > About Content Server. The
version is displayed, for example Content Server 10.5 SP1. You find detailed
information also in the Content Server system report. For more information, see
OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD).
• ECMLink module on Content Server
On the Content Server Administration page, click Module Administration >
Install Modules. You see the version of the module next to its name, for example
10.5.1 .
• Web Services and other OpenText components
On the server where Runtime and Core Services (with Content Server 10.0) or
Enterprise Library Services (with Content Server 10.5 SP1) is installed, go to
Control Panel > Add/Remove Programs or Programs and Features. In the list of
programs, you see which version is installed.
• SAP System, Database information and OpenText Components
In the SAP IMG (transaction SPRO, OpenText ECMLink for SAP Solutions >
ECMLink > Configuration Report), run the Configuration Report to get
information about the SAP server. In this report, you find information like the
versions of OTEXBAS, OTEXERP, OTEXRL, OTEXRLC, and OTEXRLS. For more
information, see OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-
CGD).
ERX100500-01-IWS-EN-3
• Support Package of installed SAP System

In the SAP GUI application, from the menu, select System > Status. Then click
Component information to see the installed SAP components with release

number and highest support package. If you only want to know the version
numbers of OTEXBAS, OTEXERP, OTEXRL, OTEXRLC, and OTEXRLS you
could use this instead of the configuration report.
ERX100500-01-IWS-EN-3
Chapter 34
Installing the SAP package
The following describes the installation of the OTEXRL component and, optional, the
OTEXRLC component or the OTEXTRLS of ECMLink on an SAP application server.
Prerequisites The component OTEXBAS of Archiving and Document Access for SAP Solutions must
be installed on your SAP system. Check the Release Notes for required versions.
See also “SAP prerequisites” on page 215 with general information on the
installation in an SAP environment.
To install the package:
1. Copy the respective SAPCAR files (*.SAR) located on the installation medium in
OpenText ECMLink for SAP Solutions\SAP to the target SAP application
server in the /usr/sap/trans folder, which is the parent folder of the
If you are performing a new installation, you need both the SP packages and the
installation packages. You can install the installation package and the SP
package together.
SAP Release File Source path Target path

SAP BASIS 700 OTEXRL_SP_1050_70 SP_BAS_700\DATA /usr/sap/trans
0_01.SAR \
SAP BASIS 700 OTEXRL_INST_1050_ INST_BAS_700\DAT /usr/sap/trans
700.SAR A\
SAP CRM 7.0 OTEXRLC_SP_1050_7 SP_CRM_700\DATA /usr/sap/trans
00_01.SAR \
SAP CRM 7.0 OTEXRLC_INST_105 INST_CRM_700\DA /usr/sap/trans
0_700.SAR TA\
SAP SRM 7.0 OTEXRLS_SP_1050_7 SP_SRM_700\DATA /usr/sap/trans
00_01.SAR \
SAP SRM 7.0 OTEXRLS_INST_1050 INST_SRM_700\DA /usr/sap/trans
_700.SAR TA\
2. Extract the SAPCAR files to the /usr/sap/trans/EPS/in folder with the

following command:
The resulting PAT files will be extracted to the EPS/in folder relative to the path
of the SAPCAR files.
Note: With Basis 7.00 or higher, you can use the SAINT and SPAM
transactions to upload and extract the SAR files from the frontend.
ERX100500-01-IWS-EN-3
Chapter 34 Installing the SAP package

For this, you will need the password for the package. For more information, see
“Installation packages and passwords” on page 220.
After the installation, you must activate Business Configuration Sets (BC sets) for
every client.
To activate the BC set:
1. Start the SCPR20 transaction.

The Business Configuration Set screen appears.
2. Activate the following BC Sets:
• /OTEXRL/RM_LINK_02
• /OTEXRL/RM_SEA
Note: For details, see the SAP documentation.
3. If you experience errors during BC set activation, repeat the respective

activation procedure up to 3 times.
4. After you activated the BC set, check the authorizations for the roles:
a. Use transaction PFCG to open the Role Maintenance.

b. Check the following roles:
• /OTX/RM_ADMIN
• /OTX/RM_CS_SAP_USER
• /OTX/RM_RFCSERVICE. This role is still available but not needed
anymore.
• /OTX/RM_USER
• /OTX/RM_IMPERSONATED_USER_ROLE
5. Ensure that the Authorizations tab has a green icon. If it is yellow, you must
regenerate the authorizations: Click Display Authorization Data, and then
Generate.
ERX100500-01-IWS-EN-3
Chapter 35
Installing language packages in the SAP system
This chapter describes how to install language packages in an SAP system.
Note: Depending on the delivery bundle, you may also have an ISO image file
containing installation files for components that must not be installed on an
SAP system.
The Add-On installation packages include the default language, which is English.
You must use the language packages to install other languages. For more
information about available languages, see OpenText ECMLink for SAP Solutions
Release Notes. You can find the language packages related to the SAP Add-Ons of
OpenText ECMLink for SAP Solutions in the OpenText Knowledge Center (https://
knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=8521552&
objAction=browse).
To install a language package:
1. In the OpenText Knowledge Center, go to OpenText Extended ECM for SAP

Solutions (https://knowledge.opentext.com/knowledge/cs.dll?func=ll&
objId=8521552&objAction=browse) and then go to the <Version> > Downloads
area. Note that you can also obtain the language packages for support packages
and other patches navigating through the Patches area. Do one of the following:
• If you have installed the installation Add-Ons, select and open the folder for
your version. Open the Language Packs folder, select and open your
language folder, and then download the
Extended_ECM_<version>_<language abbreviation>.zip file that
contains the language packages as *.SAR files.
For more details, see the text file stored with the corresponding language
package file in the language folder.
2. Upload your language file to your SAP system. Each ABAP Add-On has a
specific language package.
Example: OTEXRLDE30502_0000001 contains the German package for the OTEXRL

1002_700 Add-On on SAP_BASIS 7.00.
Note: Note the following options:
• If you use a system with SAP_BASIS 7.00, you can import and extract
the file directly in transaction SMLT.
ERX100500-01-IWS-EN-3
Chapter 35 Installing language packages in the SAP system
• If you use any other system or prefer the manual handling, extract the
SAPCAR file with the .SAR extension to the SMLT path folder of your
SAP system. Usually the path is set to the EPS\in system folder. Use the
SAPCAR tool to extract the file.
3. Use transaction SMLT to import your language package.
Important
Before starting to import language packages, OpenText recommends
reading the SAP help (http://help.sap.com/) about importing a language.
In the SAP help, navigate to the application help for the appropriate SAP
release and read the following chapters:
• Preparing to Import a Language
• Importing a Language
• Language Import with Transaction SMLT
• Post-Import Actions
4. After installing the language package, perform the necessary post-installation

steps, for example, such as those described in sections Language Supplementation/
Client Maintenance in the SAP help (http://help.sap.com/). Note that the
language package contains client dependent data which requires specific action
Client maintenance in transaction SMLT.
Note: After importing language packages to the SAP system, it can

become necessary to reset certain buffers. For example, you can use the
following transactions:
• /$SYNC - Reset all buffers
• /$OTR - Reset OTR text buffers (HTTP texts)
• /$CUA - Reset SAP GUI object buffers
• /$DYNP - Reset SAP GUI dynpro buffers
ERX100500-01-IWS-EN-3
Chapter 36
Performing general post-installation tasks in SAP
Before using the ECMLink functions, you have to perform a series of post-
installation and customizing tasks in SAP:
• “Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM
7.0“ on page 233
Apart from the general guide to the IMG function, the following generic task is
covered in the following:
• “Assigning SAP roles”
Note: For information on the scenario-specific post-installation tasks, see

OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD).
36.1 Using the IMG function

ECMLink provides a central customizing menu in SAP in the OpenText ECMLink
for SAP Solutions structure of SAP’s Customizing Implementation Guide (IMG)
function.
To call the IMG:
1. Run the SPRO transaction.
2. Click SAP Reference IMG.
3. Navigate to the OpenText ECMLink for SAP Solutions structure and open it.
ERX100500-01-IWS-EN-3
Chapter 36 Performing general post-installation tasks in SAP
4. Select the required activity and click Execute.
If an SAP system displays a different IMG structure rather than standard Reference
IMG, the Extended ECM Customizing is not visible. You have the following options
to access the Extended ECM Customizing structure:
• Use transaction SIMGH, save the Extended ECM IMG structure as a favorite and
call it from there.
• Add the Extended ECM Customizing to the existing customizing structure of
transaction SPRO.
To use transaction SIMGH to access Extended ECM Customizing:
1. Run the SIMGH transaction.
ERX100500-01-IWS-EN-3
36.1. Using the IMG function
2. In the IMG structure field, open the search help and search for the search term
OpenText*. With this search term, you also find IMG structures for other
OpenText products.
3. Double-click on entry.
4. Click Add to Favorites.
5. In the Favorites list, select one entry and click to access the IMG structure.
To add the IMG structure to SPRO transaction:
1. Create an Enhancement ID:
a. Run the S_IMG_EXTENSION transaction.

b. Open the search help of field Enhancement ID.
c. Click Create Enhancement ID (F5).
d. Enter an Enhancement ID, for example Z_OTX_EXTECM, and an
explanatory text, for example OpenText Extended ECM.
e. Click Save.
f. Click Continue.
g. Double-click the newly created Enhancement ID in the Enhancement ID:
Original list to select it for the Enhancement ID field.
2. Enhance the SAP IMG structure for ECMLink:
a. In the IMG structure field, select the IMG structure that is currently
displayed in the SPRO transaction and which you want to enhance.
For example, in SAP Extended Warehouse Management, select the IMG
structure SAP - Implementation Guide.
b. Click Favorite to add the IMG structure to your favorites.
c. Select the IMG structure in the Favorites list by double clicking.
d. If not already done, in field Enhancement ID, select the Enhancement ID
created in Step 1.
e. Click Enhance Structure.
f. Select the root node of the IMG structure.
g. From the menu, select Edit > Nodes > Insert IMG Structure > As Subnode.
h. Enter the node name for the ECMLink customizing, for example OpenText
ECMLink for SAP Solutions.
i. Click Find structure to search for the ECMLink customizing IMG
structure. Search for OpenText - Extended ECM for SAP Solutions.
j. Click Copy.
k. Click Save.
3. Enhance the SAP IMG structure for Archiving and Document Access:
ERX100500-01-IWS-EN-3
Chapter 36 Performing general post-installation tasks in SAP
Repeat the steps described in Step 2 for the OpenText Archiving and Document
Access customizing with the corresponding data:
• Name of the node: OpenText Archiving and Document Access for SAP
Solutions
• Name of the IMG structure: OpenText Archiving and Document Access for
SAP Solutions
36.2 Assigning SAP roles

In order to use the ECMLink functions in SAP, you must assign specific roles in SAP.
The following roles are required:
Note: If you do not want to use these roles, you must assign the respective
authorization objects to your own roles.
/OTX/RM_USER
Role for ECMLink application users. This role allows an SAP user declare
ArchiveLink documents as records, search Content Server, display a business
workspace in the Business Content window, and show record details.
This role contains the following authorizations objects:
Authorization object Description

/OTX/RM Records management authorizations in
GOS
Set field /OTX/RMACT to value 00 or * for
granting access to functionality related to
Records Management.
J_6NRL_DOL Business attachments authorizations
Set field /OTX/RMDAC to value 00 for
granting access to business-attachments-
related functionality.
J_6NRL_WSC Business workspace authorizations
Set field /OTX/RMWAC to value 00 for
granting access to business-workspace-
related functionality.
J_6NRL_LFS Access to local Tempo Box folder and
other local folders
Set field /OTX/RMLAC to value 00 for
granting access to local files
S_GUI Access to Drag & Drop functionality in
Business Content window.
Set field ACTVT to value 60 for granting
access to drag drop.
ERX100500-01-IWS-EN-3
36.2. Assigning SAP roles
/OTX/RM_ADMIN
Role for SAP administrator; this role allows for the post-installation and
customizing steps as well as administrative tasks like monitoring or running
batch jobs.
This role contains the following authorizations objects:
Authorization object Description

/OTX/RM Records management authorizations in
GOS
J_6NRL_DOL Business attachments authorizations
J_6NRL_WSC Business workspace authorizations
/OTX/RM_CS_SAP_USER
Role for the SAP system connection between Content Server and the SAP
system. This role is needed for the SAP user which is configured in Content
Server for the connection to SAP. For more information, see “Connecting
external systems” on page 258.
/OTX/RM_IMPERSONATED_USER_ROLE
Role for the SAP user which is used in the RFC destination. For more
information, see OpenText Extended ECM for SAP Solutions - User Management and
Access Control Scenarios (ERX-CUM).
ERX100500-01-IWS-EN-3
Chapter 37
Performing post-installation tasks for SAP ERP 6.0,
SAP CRM 7.0, and SAP SRM 7.0
37.1 Exporting the SAP PSE certificate for the SAP

authentication handler
You need the SAP PSE certificate to create the SAP authentication handler in
OpenText Directory Services. The SAP authentication handler validates SAP tickets
sent from the SAP system against the exported certificate. You export the certificate
in a PSE file from SAP using the Export System PSE Certificate to File System
activity in the SAP IMG.
To export the SAP PSE certificate:
1. In the IMG, navigate to the Export System PSE Certificate to File System
activity and click Execute.
ERX100500-01-IWS-EN-3
Chapter 37 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP
SRM 7.0
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; for details, see SAP Help Portal (http://
help.sap.com/saphelp_nw70/helpdata/de/0e/fb993af7700577e10000000a11402f/
frameset.htm).
3. Make sure the certificate's CN value in the Owner field equals to the system ID;
in this case, the value is D67.
If this is not the case, delete the current one and create a new one.
4. Click Veri. PSE. If there are more certificates available, click Yes in the message
window to add only your own certificate to the verification PSE.
5. Click Yes and copy the PSE file to an appropriate location on the Enterprise
Library server.
ERX100500-01-IWS-EN-3
37.1. Exporting the SAP PSE certificate for the SAP authentication handler
Only if you want to use SAP SRM you must export the SAP certificate from an SAP
SRM portal.
To export the SAP PSE certificate from an SAP SRM Portal:
In addition to the SAP server certificate, you must export a certificate for the portal.
1. Log in to the SAP SRM Portal as Portal Administrator.
2. On the System Administration tab, go to System Configuration > Keystore

Administration.
3. From the list, select SAPLogonTicketKeypair-cert.
4. Click Download verify.pse File and save the file to your desktop.
5. Unzip the downloaded file. Optionally, you can rename it to your system name,
for example <systemname>.pse.
Creating an SAP authentication handler in the OpenText

Administration Client
The SAP authentication handler validates the user against the SAP PSE certificate
and extracts user information from the SAP logon ticket. This is relevant for
synchronized and non-synchronized partitions. You create the respective
authentication handler in the OpenText Administration Client.
Note: For a detailed description of authentication handlers, see section 7.2

“Creating an Authentication Handler” in OpenText Directory Services -
Administration Guide (OTDS-AGD).
To create an SAP authentication handler:
1. Open the OpenText Administration Client and navigate within your Enterprise
Library to Directory Services > Authentication Handlers.
2. In the Actions pane, click New Authentication Handler.
3. Define the following settings:
• On the General page, set the Authentication handler type to SAPSSOEXT

Authentication Handler and enter a name. Click Next.
• On the User Partition page, set the scope to Global only if the user name
exists only once across all partitions. If the user exists in more than one
partition, specify the partition in the User Partition field. Click Next.
• On the Parameters page, set the following parameters:
• In the SAP Certificate (PSE) 1 field, add the certificate you exported
from SAP, and, optionally, provide a password. You can add additional
certificates if necessary. The Description field is automatically filled with
the path to the certificate; you can change the text.
ERX100500-01-IWS-EN-3
SRM 7.0
• Only if you want to map all SAP users to one user in Content Server
according to the scenario described in section 4.2.3.4 “Mapping all SAP
users to one OTDS user in OTDS SAPSSOEXT authentication handler” in
OpenText Extended ECM for SAP Solutions - User Management and Access
Control Scenarios (ERX-CUM), in the Map all authenticated users to field,
enter the name of the OTDS user name to which all authenticated SAP
users will be mapped once their logon ticket is verified. Use the same
format that you define in the Authentication principal attribute field.
• On the Configuration page, set the following parameters:
• From the Authentication principal attribute list, select an attribute that

will uniquely find a given user in Directory Services. Enter the attribute
that complies to the SAP user ID which is sent with the SAP logon ticket,
for example oTExternalID or oTExtraAttr1. Typically, this is
oTExternalID1.
• Set Authentication handler Priority to 1. This setting defines that this

authentication handler is used first before the other authentication
handlers.
• Select Enable authentication handler.
4. Click Finish.
37.2 Activating the ECMLink SSO HTTP service

You must activate the ECMLink HTTP service to use the Single sign-on (SSO)
service.
Note: Make sure that the SSO profile parameters of your SAP system are set to
the following values:
login/accept_sso2_ticket = 1 for the Web Service communication between
SAP and Enterprise Library.
login/create_sso2_ticket = 2 for the display of Content Server HTML
dialogs in SAP GUI.
For a temporary setting, start the RZ11 transaction, enter the parameter name
and click Display. For a permanent setting, use the RZ10 transaction, and
restart the system after setting the parameter. The user used for the setting
must be a dialog user.
To activate the HTTP service:
1. In IMG, navigate to the OpenText ECMLink ... > Infrastructure > Activate
HTTP Service activity and click Execute.
2. In the Hierarchy Type field, select SERVICE and click Execute.
3. In the Maintain service dialog, open the following node default_host > sap >
public.
ERX100500-01-IWS-EN-3
37.3. Creating logical ports in the SAP system
4. From the context menu of the myssocntl item, select Activate Service.
37.3 Creating logical ports in the SAP system

ECMLink connects to OpenText web services using logical ports. The creation of
logical ports differs depending on the SAP Basis version that your system uses.
37.3.1 Creating logical ports for SAP Basis 7.0

ECMLink connects to OpenText components using HTTP connections and logical
ports.
You must create the following HTTP connections to the required web services:
• Enterprise Library
• ECMLink
• OpenText Directory Services
• Enterprise Library Content Services
• Content Server Member Services
ERX100500-01-IWS-EN-3
SRM 7.0
To create the HTTP connections:
1. In IMG, navigate to the OpenText ECMLink for SAP Solutions >

Infrastructure > Create HTTP Connections activity and click Execute.
2. Click Create.
3. Enterprise Library Services

Create the HTTP connection for Enterprise Library Services with the following
settings:
• RFC Destination
Enter a name for this connection, for example ELS_DEST_CORE.
• Connection Type
G (HTTP Connection to External Server)
• Description
Enter a descriptive text.
4. Click Save.
5. Customize the connection:
• Technical Settings tab

Target host: Fully qualified host name of your Enterprise Library installation
Service No.: Enterprise Library Web Services port; port 8080 is typically
used for Apache Tomcat.
ERX100500-01-IWS-EN-3
Path Prefix: /ot-elib/services/EnterpriseLibrary

• Logon & Security tab
The options No Logon and Send SAP Logon Ticket must be enabled.
See also SAP_BASIS component with a version higher than 16 on page 241.
6. Click Connection Test.
7. Check that the value in the Status HTTP Response field is 200 which indicates
that the request was successful.
8. Save your settings.
9. ECMLink
Repeat steps 2 to 7 and create the HTTP connection for ECMLink with the
following settings:
• RFC Destination
Enter a name, for example ECMLINK_DEST.
• Connection Type
• Description
Target host: Host name of your ECMLink installation
Service No.: ECMLink Web Services port
Path Prefix: /otsapxecm/services/ECMLink
10. OpenText Directory Services

Repeat steps 2 to 7 and create the HTTP connection for OpenText Directory
Services with the following settings:
• RFC Destination
Enter a name, for example OTDS_DEST.
• Connection Type
• Description
ERX100500-01-IWS-EN-3
SRM 7.0
Target host: Host name of your Directory Services (OTDS) installation.

If you are using user-specific mapping with impersonation (SAP BAdI) and
OpenText Directory Services and Enterprise Library and Content Server are
installed on different servers, enter the host name of the Enterprise Library
installation.
Service No.: Directory Services Web Services port
Path Prefix: /ot-authws/services/Authentication
11. Enterprise Library Content Services

Repeat steps 2 to 7 and create the HTTP connection for Enterprise Library
Content Services with the following settings:
• RFC Destination
Enter a name, for example ELCONTENT_DEST.
• Connection Type
• Description
Target host: Host name of the Enterprise Library installation.
Service No.: Enterprise Library Content Services port
Path Prefix: /ot-elib/services/Content
12. Content Server Member Services

Repeat steps 2 to 7 and create the HTTP connection for Content Server Member
Services with the following settings:
• RFC Destination
Enter a name, for example CSMEMBER_DEST.
• Connection Type
• Description
ERX100500-01-IWS-EN-3

Target host: Host name of the Content Server installation.
Service No.: Content Server Member Services port
Path Prefix: With ECMLink module version 10.5.0 /
cws/services/MemberService, with ECMLink module version 10.0.5 /
les-services/services/MemberService

SAP_BASIS component with a version higher than 16
If you are using a SAP_BASIS component with a version higher than 16, you
might experience the following changes:
The Send SAP Logon Ticket is now called Send SAP Assertion Ticket and
you must provide as destination system the system ID and the client of the
current SAP system.
If this is the case, you must also do the following:
• Ensure that the latest sapssoext.dll file is in the Tomcat\bin directory.

• Set the following system wide environment variables with the same
values that you specified in SAP:
• SAPSYSTEMNAME
• SAPSYSTEMCLIENT
After creating the HTTP connection, you must create a corresponding logical port
for each connection:
• Enterprise Library logical port

• ECMLink logical port
• OpenText Directory Services logical port
• Enterprise Library Content Services logical port
To create a logical port for SAP Basis 7.0:
1. In IMG, navigate to the Infrastructure > Create New Logical Ports activity and
click Execute.
ERX100500-01-IWS-EN-3
SRM 7.0
2. Enterprise Library
In the Proxy Class field, enter /OTX/CO_RMELENTERPRISE_LIBRARY.
3. Enter a new name in the Logical Port field, for example ELS_LOGICAL_PORT.
4. Select the Default Port check box. Select it for your main Content Server if you
have more than one.
5. Click Create.
ERX100500-01-IWS-EN-3
6. Enter a description for the logical port in the Description field.

On the Call Parameters tab, enter your new HTTP destination created before for
the Enterprise Library in the HTTP Destination field, for example
ELS_DEST_CORE.
7. Click Check to check the new logical port.

Check that the message in the status bar reads No errors found in
configuration.
8. Click Save and Activate (Ctrl + F3) to activate the logical port.
9. ECMLink
Repeat steps 2 to 8 to create a logical port for ECMLink using the following
values:
• Proxy Class
Enter /OTX/CO_RM_WSW_ECMLINK.
• Logical Port
Enter the name of the logical port, for example ECMLINK_LOGICAL_PORT.
• HTTP Destination
Enter the HTTP destination created before, for example ECMLINK_DEST.
10. OpenText Directory Services

Repeat steps 2 to 8 to create a logical port for OpenText Directory Services using
the following values:
• Proxy Class
Enter /OTX/CO_OTDSAUTHENTICATION.
• Logical Port
Enter the name of the logical port, for example OTDS_LOGICAL_PORT
Enter the HTTP destination created before, for example OTDS_DEST.
• State Management
Select this option for the OpenText Directory Services web service. If you did
not select this option, you will get an according message during the
connection check.
11. Enterprise Library Content Services

Repeat steps 2 to 8 to create a logical port for Enterprise Library Content
Services using the following values:
• Proxy Class
Enter /OTX/CO_RMELCONTENT.
ERX100500-01-IWS-EN-3
SRM 7.0
• Logical Port
Enter the name of the logical port, for example ELCONTENT_LOGICAL_PORT
Enter the HTTP destination created before, for example ELCONTENT_DEST.
Select this option for the Enterprise Library Content Services web service. If
you did not select this option, you will get an according message during the
connection check.
12. Content Server Member Services

Optional Repeat steps 2 to 8 to create a logical port for Content Server Member
Services using the following values:
• Proxy Class
Enter /OTX/CO_MBLLMEMBER_SERVICE.
• Logical Port
Enter the name of the logical port, for example CSMEMBER_LOGICAL_PORT
Enter the HTTP destination created before, for example CSMEMBER_DEST.
Select this option for the Content Server Member Services web service.
If you did not select this option, you will get an according message during
the connection check.

ECMLink connects to OpenText components using logical ports.
You must create a corresponding logical port for each connection:

• ECMLink
To create a logical port for SAP Basis 7.01 and higher:
1. In the IMG, navigate to the OpenText ECMLink for SAP Solutions >
Infrastructure > Create New Logical Ports activity and click Execute.
The SOA Management dialog opens.
ERX100500-01-IWS-EN-3
2. On the Application and Scenario Communication tab, click Single Service

Administration.
3. On the Search tab, change the Search by value to Consumer Proxy, enter a * in
the Search Pattern field, and click Go.
4. In the Search Results pane, select the entry for EnterpriseLibrary (/

OTX/CO_RMELENTERPRISE_LIBRARY) and click Apply Selection.
5. On the Configurations tab, click Create Logical Port.
6. Enter a new name in the Logical Port Name field and add a description.
Select Logical Port is Default if you have only one logical port for the Enterprise
Library. If you have multiple logical ports for Enterprise Library, select this
option only for one of the logical ports.
For the Configuration Type, select Manual Configuration.
7. Click Apply Settings. The Web Service Configuration of Proxy Definition

section is displayed.
8. Open the Consumer Security tab and select SAP Authentication Assertion
Ticket.
9. Open the Messaging tab.

In the Message ID Protocol field, select the Suppress ID Transfer value.
ERX100500-01-IWS-EN-3
SRM 7.0
10. Open the Transport settings tab and enter the following parameters:
• URL Access Path:

/ot-elib/services/EnterpriseLibrary
• Computer Name of Access URL:
Enterprise Library installation host name
• Port Number of Access URL: Enterprise Library Web Services port (usually
8080 for Tomcat)
Click Save.
A message at the top of the screen indicates that the binding has been created.
11. Logical port for ECMLink
Repeat Step 4 to Step 10 to create a logical port for ECMLink:
Select the entry for ECMLink (/OTX/CO_RM_WSW_ECMLINK).
• URL Access Path on the Transport settings tab:

/otsapxecm/services/ECMLink
• Computer Name of Access URL on the Transport settings tab:
Host name of your ECMLink installation.
• Port Number of Access URL on the Transport settings tab:
ECMLink Web Services port (usually 8080 for Tomcat)
Leave all other settings as described for the Enterprise Library port.
12. Logical port for authentication
Repeat Step 4 to Step 10 to create a logical port for authentication:
Select the entry for Authentication (/OTX/CO_OTDSAUTHENTICATION).
• SAP Authentication Assertion Ticket on the Consumer settings tab, select

SAP Authentication Assertion Ticket.
/ot-authws/services/Authentication
ERX100500-01-IWS-EN-3
Host name of your Directory Services installation.

If you are using user-specific mapping with impersonation (SAP BAdI) and
OpenText Directory Services and Enterprise Library and Content Server are
installed on different servers, enter the host name of the Enterprise Library
installation.
Directory Services Web Services port (usually 8080 for Tomcat)
13. Logical port for Enterprise Library Content Services

Repeat Step 4 to Step 10 to create a logical port for Enterprise Library Content
Service:
Select the entry for Content (/OTX/CO_RMELCONTENT).

/ot-elib/services/Content

Host name of your Enterprise Library Content Services installation.
Enterprise Library Content Services port (usually 8080 for Tomcat)
14. Logical port for Content Server Member Service

Repeat Step 4 to Step 10 to create a logical port for Content Server Member
Service:
Select the entry for MemberService (/OTX/CO_MBLLMEMBER_SERVICE).

With ECMLink module version 10.5.0 /cws/services/MemberService,
with ECMLink module version 10.0.5 /les-
services/services/MemberService

Host name of your Content Server Member Service installation.
Content Server Member Service port (usually 8080 for Tomcat)
ERX100500-01-IWS-EN-3
SRM 7.0

ECMLink connects to OpenText components using logical ports.
You must create a corresponding logical port for each connection:
• ECMLink
To create a logical port for SAP Basis 7.31:
Infrastructure > Create New Logical Ports activity and click Execute.
The SOA Management dialog opens.
2. On the Service Administration tab, click Web Service Configuration.
3. On the Design Time Object Search tab, select the search criteria Object Type
and search for Consumer Proxy.
4. In the Search Results list, select the entry for EnterpriseLibrary (/

OTX/CO_RMELENTERPRISE_LIBRARY).
5. On the Configurations tab, click Create > Manual Configuration.
6. In the Logical Port Name step, enter a new name in the Logical Port Name field
and add a description.
Select Logical Port is Default if you have only one logical port for the Enterprise
Library. If you have multiple logical ports for Enterprise Library, select this
option only for one of the logical ports. Click Next.
ERX100500-01-IWS-EN-3
7. In the Consumer Security step, select SAP Authentication Assertion Ticket.

Click Next.
8. In the HTTP Settings step, configure at least the following:
• URL Access Path:

/ot-elib/services/EnterpriseLibrary
• Computer Name of Access URL:
Enterprise Library installation host name
• Port Number of Access URL: Enterprise Library Web Services port (usually
8080 for Tomcat)
• Transport Binding Type: SOAP1.1
Click Next.
9. In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID
Transfer
Click Next.
10. In the Operation specific step, select the GetObjects operation.
ERX100500-01-IWS-EN-3
SRM 7.0
Click Finish.
The new logical port is saved and activated.
11. Create Logical ports for the other web services according the following table.
Repeat Step 4 to Step 10 to create a logical ports for the following:
• ECMLink
Internal name: /OTX/CO_RM_WSW_ECMLINK
URL Access Path: /otsapxecm/services/ECMLink
Computer Name of Access URL: Host name of your ECMLink installation
Port Number of Access URL: ECMLink Web Services port (usually 8080 for
Tomcat)
• Authentication
Internal name: /OTX/CO_OTDSAUTHENTICATION
URL Access Path: /ot-authws/services/Authentication
Computer Name of Access URL: Host name of your Directory Services
installation. If you are using user-specific mapping with impersonation (SAP
BAdI) and OpenText Directory Services and Enterprise Library and Content
Server are installed on different servers, enter the host name of the
Enterprise Library installation.
Port Number of Access URL: Directory Services Web Services port (usually
8080 for Tomcat)
• Enterprise Library Content Services (Content)
Internal name: /OTX/CO_RMELCONTENT
URL Access Path: /ot-elib/services/Content
Computer Name of Access URL: Host name of your Enterprise Library
Content Services installation
Port Number of Access URL: Enterprise Library Content Services port
(usually 8080 for Tomcat)
ERX100500-01-IWS-EN-3
37.4. Configuring the Service Provider Interface service
• Content Server Member Service (MemberService)

Internal name: /OTX/CO_MBLLMEMBER_SERVICE
URL Access Path: With ECMLink module version 10.5.0 /
cws/services/MemberService, with ECMLink module version 10.0.5 /
les-services/services/MemberService
Computer Name of Access URL: Host name of your Content Server
Member Service installation
Port Number of Access URL: Content Server Member Service port (usually
8080 for Tomcat)
37.4 Configuring the Service Provider Interface

service
For communication from Content Server to the SAP system a web service is used.
You configure the web service on SAP side. Content Server uses this web service to
connect to the SAP system.
Note: This activity is required to connect the SAP system as external system in
Content Server. For more information, see “Connecting external systems”
on page 258.
Infrastructure structure and open it.
2. For the Configure SPI Service activity, click Execute.

The SOA Manager opens in a web browser.
Note: In the SOA Manager, the option names differ from release to
release. The following steps cover some of the possible option names. For
detailed information, see the SAP documentation.
3. Click the Business Administration, Business Administrator or Service
Administration tab.
4. Click the Web Service Administration or Single Service Configuration link to
manage the web service.
5. Search for the /OTX/ECMLINKSERVICE web service to display details.
6. Select the web service and click Apply Selection.
7. Click the Configurations tab.
8. To create a service and an end point, click Create Service.
9. Enter the following:
• New Service Name or Web Service Name: Enter a name of your web
service, for example ECMLinkSPIService.
ERX100500-01-IWS-EN-3
SRM 7.0
• Description: Enter a description for your web service.

• New Binding Name: Enter a binding of your web service, for example
BasicAuthBinding.
Note: The information you enter here will be part of the address used to
access the SAP system from Content Server:
https://<common url:port/sap/bc/srt/xip/otx/ecmlinkservice/
<Client>/<WebServiceName>/<BindingName>
Example:
https://mucr3d6v.opentext.net:8443/sap/bc/srt/xip/otx/
ecmlinkservice/800/ecmlinkspiservice/basicauthbinding
10. Click Apply Settings to save.
11. To configure your web service and binding, select your web service and end
point in the table and click Edit.
12. Define the security and authentication settings. The following authentication
scenario is supported:
• HTTPS and HTTP basic authentication with user and password

On the Provider security tab, enter the following:
• Transport Guarantee Type: Select HTTPS.
Note: For HTTPS, the SSL certificate must be imported to the

keystore. For more information, see section 22.1 “Importing root
certificates for Secure Sockets Layer (SSL) connections” in OpenText
ECMLink for SAP Solutions - Installation and Upgrade Guide (ERLK-
IGD).
• Transport Protocol or Communication Security: Select HTTP Using
Secure SSL Connection.
• HTTP Authentication or Transport Channel Authentication: Select

User ID/Password.
13. Click Save.
14. Go back to SAP GUI and start the SICF transaction.
15. In the Maintain Service dialog open the

sap/bc/srt/xip/otx/ecmlinkservice/<Client>/<WebServiceName>, for
example sap/bc/srt/xip/otx/ecmlinkservice/800/ecmlinkspiservice
node and check if the <BindingName> (for example basicauthbinding) service
is activated. If not, activate it.
ERX100500-01-IWS-EN-3
37.5. Maintaining Enterprise Library server settings
37.5 Maintaining Enterprise Library server settings

All parameters for a connection to an Enterprise Library server are collected with an
Enterprise Library ID. For an installation, you have to create a new Enterprise Library
ID along with the connections to an Enterprise Library Server, Content Server, and
OTDS.
To maintain Enterprise Library Server settings in:
1. Navigate to the Infrastructure > Maintain Enterprise Library Servers Settings

activity and click Execute.
2. Click New Entries.
ERX100500-01-IWS-EN-3
SRM 7.0
3. Enter the following parameters:
EL ID
Enter an Enterprise Library ID.
Enterprise Library Server Settings
• Description: Enter a description for the Enterprise Library server.

• EL Application Pwd: Enter the Enterprise Library application password;
this application password has been defined in section 22.6.1 “Creating
an Enterprise Library application” in OpenText ECMLink for SAP
Solutions - Installation and Upgrade Guide (ERLK-IGD).
ERX100500-01-IWS-EN-3
37.5. Maintaining Enterprise Library server settings
Logical Ports for Web Services

Enter the names of the logical ports for the Enterprise Library, the OpenText
Directory, ECMLink, Enterprise Library Content Services, and for the
Content Server Member Service. For more information about logical ports,
see “Creating logical ports in the SAP system” on page 237.
OpenText Directory
• Partition: Enter the OTDS partition that is used to authenticate SAP

users in Content Server, only if you are using policies and only if you
have consolidated those users in OTDS in the format user@partition.
Do not enter @ together with the partition, only the partition name.
Leave the field empty, if you do not use partitions at all.
Example: Users in your system are created using the following scheme
USER@PARTITION, for example nick@SAP_USER. In this case, here, you enter
SAP_USER.
• Impersonation RFC: If you are using impersonation, enter the RFC
destination used for impersonation. In addition, you have to implement
and activate the /OTX/RM_IMPERSONATE BAdI and perform additional
configuration tasks. You also must provide the CS Resource ID.
• For more information about implementation, see the ECMLink SDK in
the OpenText Knowledge Center.
For more information about the impersonation scenario and relevant
configuration, see section 6.7.1 “Enabling user-specific impersonation
(SAP BAdI)” in OpenText Extended ECM for SAP Solutions - User
Management and Access Control Scenarios (ERX-CUM).
OpenText Content Server
• Protocol, Hostname, Port, and Path: These URL parameters define how
to display the Content Server Web UI.
Important
You must enter the full Content Server path including the
domain name.
Example: Example:
• Protocol: http
• Hostname: ecmlink15.opentext.net
• Port: 2099
• Path: OTCS/cs.exe
• Support Directory defines the directory on Content Server where the
files for the Content Server widgets are stored, for example img. This is
only relevant if you want to use widgets and meet all prerequisites. For
more information, see section 9 “Using Content Server UI Widgets for
the integration” in OpenText ECMLink for SAP Solutions - Customizing
Guide (ERLK-CGD).
ERX100500-01-IWS-EN-3
SRM 7.0
• External System ID: Enter the name defined when configuring the
external connection on Content Server for this SAP system.
• Logical Destination: Select an existing logical destination defined in the
SM59 transaction. This entry is used for enabling the Content Server full
text search in the SAP system. For more information, see section 24.1.2
“Customizing search templates” in OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).
• CS Resource ID: Content Server Resource ID as defined for Directory
Services. This option is necessary if you want to use impersonation with
web-based SSO. To retrieve the ID, open Administration Client; then go
to Directory Services > Resources > [Content Server entry] > Edit and
copy the Resource identifier, for example d7c6b26b-
af12-4d87-87cd-050de0768f4a.
Suppress Sending SAP Logon Ticket

Select this option if you do not want to send the SAP Logon Ticket. For
example, you use this option for security reasons if you use the Integrated
Windows Authentication, also called NTLM authentication.
For more information about this scenario, see section 4.3.3 “Integrated
Windows Authentication” in OpenText Extended ECM for SAP Solutions -
User Management and Access Control Scenarios (ERX-CUM).
4. Click Save.
ERX100500-01-IWS-EN-3
Chapter 38
Performing post-installation or post-upgrade tasks
in Enterprise Library
After the actual installation of the module, you have to perform post-installation
tasks in Enterprise Library
38.1 Importing root certificates for Secure Sockets

Layer (SSL) connections
To secure communication between Content Server and the external system
connected in “Connecting external systems” on page 258, OpenText strongly
recommends to use the Secure Sockets Layer (SSL) protocol. The keystore for
ECMLink is ecmlink-spi.cacerts in the config directory of Content Server. It
contains the common root certificates known from Java runtime. If you want to use
certificates from a different certificate authority (CA), for example a self-signed
certificate, you can import them using the standard java keytool commands.
Note: The certificate should be in Base64 format.
To import a certificate:
1. Open a command prompt window.

2. To list the certificates, run the following command:
keytool -list -keystore c:\opentext\config\ecmlink-spi.cacerts -

storepass changeit
3. The key store password is changeit. To change the password, enter:
keytool -storepasswd changeit -new <KeystorePassphrase> -

keystore c:\opentext\config\ecmlink-spi.cacerts
4. To add an certificate run the following command:
<JavaHome>\bin\keytool -import
-alias <CertificateAlias>
-file <CertificateFile>
-keystore <Keystore>
-storepass <KeystorePassphrase>
Example:
C:\OPENTEXT\jre\bin\keytool
-import
-alias mycertificate
-file c:\temp\mycertificate.cer
ERX100500-01-IWS-EN-3
Chapter 38 Performing post-installation or post-upgrade tasks in Enterprise Library
-keystore c:\opentext\config\ecmlink-
spi.cacerts
-storepass mypassword
38.2 Connecting external systems

To connect the Content Server with an external system, you define connection
parameters on Content Server.
To connect an external system:
1. On the Content Server Administration page, click ECM Link Administration >
Configure Connections to External Systems.
The page displays all connections to external systems, both HTTP connections
and deprecated RFC connections.
2. Click Add External System.
3. For the external system, you specify the following parameters:
Logical External System Name

Define the logical name of the external system. The name must be unique
and have a maximum of 32 characters. This name can be, for example, the
name of the SAP system such as D6V.
This name is for example used when you select the external system in the
business object type configuration on Content Server.
Caution
Do not change the name later as the value is used as a foreign key.
Connection Type
Displays the connection type.
Enabled
Select this option to enable the configuration.
ERX100500-01-IWS-EN-3
38.2. Connecting external systems
Tip: You can use this option when you create a configuration only for
testing and want to disable it in case the external system goes
productive; the disabled configuration can then be enabled again if
required.
Comment
Enter a comment to give further information.
Base URL
Common URL for accessing applications via a Web browser. You can use
this base URL when configuring business object types on Content Server.
The base URL is represented by the $BaseURL$ variable for new business
object types.
Application Server Web Service Endpoint

Specifies the URL that will be called to obtain business object information.
Example 38-1: SAP

The following is an example for an SAP system: https://
myhost.opentext.net:8443/
sap/bc/srt/xip/otx/ecmlinkservice/800/
ecmlinkspiservice/basicauthbinding
• https://myhost.opentext.net:8443: Common URL.

Port 8000 is the default HTTP port for SAP, for HTTPS the
default port is 8443.
• 800 is the client number. Replace this number with your own
client number.
• basicauthbinding is currently the only supported
authentication.
Note: With using basic authentication, OpenText strongly

recommends that you to use SSL at the web server. For information
about importing certificates to the keystore, see section 22.1
“Importing root certificates for Secure Sockets Layer (SSL)
connections” in OpenText ECMLink for SAP Solutions - Installation and
Upgrade Guide (ERLK-IGD).
Schema Version
Select the interface version.
User Name
Enter the user that is used to access business object type information from
the external system.
Password
Specify the password of the defined user.
ERX100500-01-IWS-EN-3
Note: If you are upgrading from 10.5 to 10.5 SP1, re-enter the
password and save the configuration.
Test Connection
Note: You can only test the connection after you have configured the
SPI service in the external system accordingly. For more information,
see section 21.3 “Configuring the Service Provider Interface service” in
OpenText ECMLink for SAP Solutions - Installation and Upgrade Guide
(ERLK-IGD).
Click Test to perform a connection check to the specified external system.

After a successful check, the message Connection test to <Logical External
System Name> was successful is displayed next to the button. The system
ID will also be retrieved and displayed.
You can save a configuration without performing the test only if the
configuration is not enabled.
Tip: If the test was not successful, check the connection manually by
opening a browser and entering the URL directly. This will give you
more detailed error messages. Also check the Content Server thread
logs and the ecmlink-spi.log file in the logs directory.
• SAP system - https://<common url of the sap
system>:port/sap/bc/srt/xip/otx/ecmlinkservice/
<client>/ecmlinkspiservice, for example https://
sap123.opentext.net:
8443/sap/bc/srt/xip/otx/ecmlinkservice/800/ecmlinkspise
rvice
• Oracle E-Business Suite - http://<common url of the EBS
system>:port/xxxecm4o/xxxecm4o, for example
ebs01.opentext.net
4. Click Add.
38.3 Managing users

Content Server users are provided by OpenText Directory Services (OTDS). In order
to access Content Server from a SAP system, user accounts of the SAP system and
Content Server user accounts have to be mapped to each other. There are a number
of different scenarios, which are described in detail in OpenText Extended ECM for
SAP Solutions - User Management and Access Control Scenarios (ERX-CUM).
Create the Content Server users according to your authentication scenario. For
example, for each SAP user working with ECMLink, you can create a Content Server
user with the same user name as in SAP. Alternatively, you can have one Content
Server user for many SAP users.
For test purposes or a small number of users, this can be done manually in OpenText
Directory Services. For a large number of SAP users this can achieved using an
ERX100500-01-IWS-EN-3
38.4. Preparing document declaration
Active Directory server that provides users for both the SAP system and for Content
Server via Directory Services.
In your SAP system, the users are either provided and maintained in your SAP
system or in an external identity provider. Directory Services can synchronize with
your identity provider to pull user and group information from your identity
provider automatically.
38.4 Preparing document declaration

The following steps are only necessary if you want to store SAP ArchiveLink
documents and print lists as documents in a defined location in Content Server.
38.4.1 Creating a Records Management classification

(optional)
If you want to use Records Management, you must create at least one Records
Management classification that can be used in ECMLink.
For more information, see OpenText Classifications - Resource Guide (LLESCLS-GGD).
38.4.2 Importing folder and item type

ECMLink stores metadata for the declared ArchiveLink documents in the Enterprise
Library volume. On the installation CD in the folder
ECMLink for SAP Solutions\Enterprise Library\Document Model, 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 OpenText Administration Client.
To import the folder type:
1. Invoke the OpenText Administration Client and navigate within your

Enterprise Library 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.
ERX100500-01-IWS-EN-3
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
ERX100500-01-IWS-EN-3
38.4. Preparing document declaration
38.4.3 Setting up the authorization for records in Enterprise

Library
The access rights to the records created by ECMLink correspond to the access rights
used by the Enterprise Library application. For more information, see “Creating an
application“ on page 171. In order to restrict the access in accordance with your
company policy, you have to create Content Server 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.
ERX100500-01-IWS-EN-3
Example 38-2: Authorization for records in Content Server
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 Content Server 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.
38.4.4 Creating system categories in Content Server

ECMLink stores all metadata in Content Server categories rather than 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.
You can also create system categories manually, but copying the imported item
types ensures that no mandatory category attributes are missing.
To create system categories:
1. Go to the Content Server Administration page and select the Enterprise

Library Administration > Open the Enterprise Library Types Volumes entry.
2. Browse to the folder named otx.sap.rm.SystemArchiveLink and open it.
3. Copy the category file otx.sap.rm.SystemArchiveLink.v to a different location

within the Categories volume. If required, you can change the category name.
ERX100500-01-IWS-EN-3
38.5. For SAP CRM and SRM: Configuring security settings
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.
5. Create unique names for the system categories. You will need the unique name
for the document declaration configuration in the SAP IMG. For more
information, see section 6.8 “Configuring unique names for Content Server
items” in OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD).
38.5 For SAP CRM and SRM: Configuring security

settings
To display business workspaces in web applications of SAP CRM and SAP SRM,
you must adapt the security parameters in Content Server.
To enable display of business workspaces in web applications of SAP:
1. On the Content Server Administration page, click Server Configuration >

Configure Security Parameters.
2. Specify the following parameters:
Frame Embedding
Must be unchecked. You do not want to prevent request handlers from
being embedded in external frames.
Trusted Referring Websites

Enter the URL of the SAP application website with port, for example
http://mycrmsystem.mycompany.com:8000.
ERX100500-01-IWS-EN-3
Chapter 39
Verifying the installation
39.1 Analyzing the SAP system

39.1.1 Understanding the SAP Diagnostic Program
You can use the Diagnostic Program to analyze your installation.
Important
You can run the infrastructure diagnostic program after specifying at least
the connection to the Enterprise Library in the Infrastructure section of the
IMG.
The diagnostic program is aimed at two different target groups:

• The Infrastructure part is for technical consultants who set up the connection
between the SAP system, Enterprise Library and Content Server. The report
contains the following types of information: the connection to Content Server,
Web service communication such as logical ports, the OTDS service or HTML
controls.
• The ECMLink part contains the infrastructure information in addition to
information about the customizing, like business object declarations, Document
Declarations, or Item types.
A green light icon indicates that everything is in order. For checks with a red light
icon, a recommendation is displayed. For more information about each check, see
“Understanding the details of the Diagnostic Program” on page 268.
To run the Diagnostic Program:
1. In the IMG, navigate to the Infrastructure > Diagnostic Program or the

ECMLink > Diagnostic Program activity and click Execute.
If there is only one Content Server configuration, the diagnosis is started
immediately. If there are more Content Server configurations, perform the
following steps:
2. Enter the Enterprise Library ID of the respective Content Server system.
3. Click Execute.
ERX100500-01-IWS-EN-3
Chapter 39 Verifying the installation
39.1.2 Understanding the details of the Diagnostic Program

This section lists the various tests of the Diagnostic Program and refers to sections in
this guide which contain helpful information.
Test IMG Activity More Information

Content Server
Does the Enterprise Library Infrastructure > Maintain Section 21.4 “Maintaining
ID exist? Enterprise Library Server Enterprise Library server
Settings; double-click one settings” in OpenText
Did you provide the Content entry. ECMLink for SAP Solutions -
Server host name? Installation and Upgrade Guide
Is the Content Server host (ERLK-IGD)
name fully qualified?
Did you provide the Content
Server port?
ERX100500-01-IWS-EN-3
39.1. Analyzing the SAP system

Did you provide the path to
Content Server?
Is the Content Server URL
valid?
Service Communication
Did you provide a port for Infrastructure > Create New Section 21.2 “Creating logical
the Enterprise Library Logical Ports ports in the SAP system” in
Service? OpenText ECMLink for SAP
Solutions - Installation and
Upgrade Guide (ERLK-IGD)
Can the Enterprise Library
Service be instantiated?
Did you provide an HTTP Infrastructure > Create New Section 21.2 “Creating logical
destination for the Enterprise Logical Ports ports in the SAP system” in
Library logical port? OpenText ECMLink for SAP
Check the following for the For SAP Basis 7.0: Section 21.2 “Creating logical
Enterprise Library HTTP Infrastructure > Create ports in the SAP system” in
connection: “No Logon” and HTTP Connections > HTTP OpenText ECMLink for SAP
“Send SAP Logon Ticket” is Connections to External Solutions - Installation and
enabled; “HTTP Server; double-click one Upgrade Guide (ERLK-IGD)
compression” is disabled. connection; Logon &
Security tab and Special
Options tab.
For SAP Basis > 7.0: Section 21.2.2 “Creating
Infrastructure > Create New logical ports for SAP Basis
Logical Ports > SOA 7.01 and higher” in OpenText
Management > Application ECMLink for SAP Solutions -
and Scenario Installation and Upgrade Guide
Communication > Single (ERLK-IGD)
Service Administration
Service be executed?
the Enterprise Library Logical Ports ports in the SAP system” in
Content Service? OpenText ECMLink for SAP
Content Service be
instantiated?
Did you provide an HTTP Infrastructure > Create New
destination for the Enterprise Logical Ports
Library Content logical port?
ERX100500-01-IWS-EN-3

Enterprise Library Content Infrastructure > Create ports in the SAP system” in
connection: “No Logon” and HTTP Connections > HTTP OpenText ECMLink for SAP
“Send SAP Logon Ticket” is Connections to External Solutions - Installation and
enabled; “HTTP Server; double-click one Upgrade Guide (ERLK-IGD)
compression” is disabled. connection; Logon &
Options tab.
Can Enterprise Library
Content Service be executed?
Did you provide a logical Infrastructure > Create New Section 21.2 “Creating logical
port for the Content Server Logical Ports ports in the SAP system” in
Member Service? OpenText ECMLink for SAP
Can the Content Server
Member Service be
instantiated?
destination for the Content Logical Ports
Server Member logical port?
Content Server Member Infrastructure > Create ports in the SAP system” in
HTTP connection: “No HTTP Connections > HTTP OpenText ECMLink for SAP
Logon” and “Send SAP Connections to External Solutions - Installation and
Logon Ticket” is enabled; Server; double-click one Upgrade Guide (ERLK-IGD)
“HTTP compression” is connection; Logon &
disabled. Security tab and Special
Options tab.
ERX100500-01-IWS-EN-3
39.1. Analyzing the SAP system

Can the Content Server OpenText Administration Section 6.5 “Configuring
Member Service be executed? Client > Directory Services > access roles” in OpenText
Access Roles Extended ECM for SAP
Solutions - User Management
and Access Control Scenarios
(ERX-CUM)
the ECMLink Service? Logical Ports ports in the SAP system” in
OpenText ECMLink for SAP
destination for the ECMLink Logical Ports
logical port?
ECMLink HTTP connection: Infrastructure > Create ports in the SAP system” in
“No Logon” is enabled; HTTP Connections > HTTP OpenText ECMLink for SAP
“HTTP compression” is Connections to External Solutions - Installation and
disabled. Server; double-click one Upgrade Guide (ERLK-IGD)
connection; Logon &
Options tab.
Can the ECMLink Service be
executed?
Did you provide a logical Infrastructure > Create New Section 21.2 “Creating logical
port for the OTDS Service? Logical Ports ports in the SAP system” in
OpenText ECMLink for SAP
destination for the OTDS Logical Ports
services?
“Authentication” HTTP Infrastructure > Create ports in the SAP system” in
connection: “No Logon” is HTTP Connections > HTTP OpenText ECMLink for SAP
enabled; “HTTP Connections to External Solutions - Installation and
compression” is disabled. Server; double-click one Upgrade Guide (ERLK-IGD)
connection; Logon &
Options tab.
ERX100500-01-IWS-EN-3

Can the OTDS Service be
executed?
If impersonation RFC is
provided, can the
impersonation RFC be
executed?
Did you provide a service for Infrastructure > Configure Section 21.3 “Configuring the
the SPI service SPI Service or Service Provider Interface
configuration? SOAMANAGER transaction service” in OpenText
ECMLink for SAP Solutions -
Installation and Upgrade Guide
(ERLK-IGD)
Check the following for the Infrastructure > Configure Section 21.3 “Configuring the
SPI service configuration: SPI Service or Service Provider Interface
“Transport Guarantee Type = SOAMANAGER transaction service” in OpenText
HTTPS”; “Authentication: ECMLink for SAP Solutions -
User ID/Password is Installation and Upgrade Guide
enabled”. (ERLK-IGD)
HTML Controls
Can an HTML control be
instantiated?
Can an HTML control be
initialized?
Can the HTML control
enable SSO?
Do the SAP HTTP server and
the Content Server server
share both the second-level
and the top-level domain
name?
>>> Double-click here to test Tests the above items and
an HTML control. <<< opens a window with
Content Server categories. It
also gives solutions for
possible problems.
ERX100500-01-IWS-EN-3
Chapter 40
Preparing a checklist for the customizing team
After you have installed the infrastructure for Extended ECM for SAP Solutions, you
can hand-over the work to those who are responsible for the customizing of the
system as it is described in OpenText ECMLink for SAP Solutions - Customizing Guide
(ERLK-CGD).
The following tools provide both necessary and useful information:
SAP system
• Diagnostic Program: “Understanding the SAP Diagnostic Program”
on page 267
Tests the customizing and provides solutions for errors.
• Configuration Report: Section 17.1.3 “Understanding the Configuration
Report” in OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-
CGD)
Provides information about ECMLink related customizing in the SAP
system.
Content Server
System Report: Section 17.2.1 “Understanding the Content Server System
Report” in OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD)
Contains the complete configuration information of the Content Server system.
Look for the “Extended ECM Information” section.
OpenText Administration Client

• OpenText™ Directory Services: System report provides information about
user management related configurations.
• OpenText Archive Server: Provides information for the ArchiveLink setup
in SAP (OAC0 transaction).
To generate the system configuration reports:
1. In OpenText Administration Client, log on to the Enterprise Library Server.
2. OpenText™ Directory Services
a. Go to Directory Services > Configuration Manager.

b. In the Actions pane, click View system configuration report.
3. OpenText Archive Server
a. Go to Archive Server > System > Reports.
ERX100500-01-IWS-EN-3
Chapter 40 Preparing a checklist for the customizing team
b. In the Reports pane, open the Scenarios tab.

c. In the Actions pane, click Generate Report. A new window opens, which
you can close.
d. Switch to the Reports tab in the Reports pane.
e. Click one the of the generated reports to view it.
ERX100500-01-IWS-EN-3

OpenText Extended ECM For SAP Solutions. Installation Guide For Microsoft Windows With Microsoft SQL Server PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OpenText Extended ECM For SAP Solutions. Installation Guide For Microsoft Windows With Microsoft SQL Server PDF

Caricato da

Copyright:

Formati disponibili

OpenText™ Extended ECM for SAP®

Installation Guide for Microsoft

This guide describes the installation and basic configuration of

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

No Warranties and Limitation of Liability

Part 1 Setting up Archive Server 15

4 Installing JRE, Tomcat and SQL Server ................................ 19

5 Installing Archive Server ........................................................ 49

Part 2 Setting up Content Server 81

6 Setting up IIS 7.5 ...................................................................... 83

7 OpenText Extended ECM for SAP Solutions Master

8 Installing Content Server on Windows ................................ 101

9 Installing Content Server modules ...................................... 109

10 Configuring Content Server ................................................. 111

11 Uninstalling the Document Undelete module ..................... 121

12 Deploying the Web Content Services to Tomcat ................ 123

13 Installing the Content Server modules ................................ 125

14 Testing Content Server search ............................................ 127

Part 3 Installing patches 129

15 Installing Enterprise Library patches .................................. 131

16 Installing Content Server patches using the cluster

Part 4 Configuring Enterprise Library Services 135

17 Starting the Administration Client on Archive Server ....... 137

18 Configuring OpenText Directory Services .......................... 143

19 Configuring Archive Server .................................................. 153

20 Configuring the storage provider ........................................ 163

21 Creating a storage provider and a storage rule .................. 165

22 Enabling certificates ............................................................. 169

23 Creating an application ......................................................... 171

24 Removing the UndeleteWS from the Enterprise Library

25 Testing Enterprise Library .................................................... 177

25.2 Creating an item ........................................................................... 178

Part 5 Installing Archiving and Document Access for SAP

26 Introduction ............................................................................ 185

27 Checking prerequisites ......................................................... 187

28 Installing Basis package ....................................................... 191

29 Installing ERP option package ............................................. 199

30 Installing CRM option package ............................................ 201

31 Installing language packages ............................................... 203

32 Handling communication protocols .................................... 205

Part 6 Setting up ECMLink for SAP Solutions 213

33 Checking the prerequisites .................................................. 215

33.1 Required knowledge ...................................................................... 215

34 Installing the SAP package ................................................... 223

35 Installing language packages in the SAP system .............. 225

36 Performing general post-installation tasks in SAP ............ 227

37 Performing post-installation tasks for SAP ERP 6.0, SAP

38 Performing post-installation or post-upgrade tasks in

39 Verifying the installation ....................................................... 267

39.1 Analyzing the SAP system ............................................................. 267

40 Preparing a checklist for the customizing team ................. 273

1.1 What is new?

1.2 Related documentation

OpenText Extended ECM for SAP Solutions - Overview Guide (ERX-GGD)

OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD)

OpenText ECMLink for SAP Solutions - Administration Guide (ERLK-AGD)

OpenText ECMLink for SAP Solutions - User Guide (ERLK-UGD)

OpenText Extended ECM for SAP Solutions 10.5 - eBook

Overview/46226701) and Extended ECM for SAP Solutions (https://

Figure 2-1: System overview

The document describes the following scenario: