OpenText Extended ECM For SAP Solutions 16.2 - Installation Guide For Microsoft Windows With Oracle Database English (ERLK160200-00-IWO-En-01)

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

Windows with Oracle Database
This guide describes the installation and basic configuration of

one of the most common deployment scenarios of Extended
ECM for SAP Solutions. Extended ECM for SAP Solutions is
installed on two physical servers, one for OpenText™ Content
Server together with the Oracle client, the other one for the
Extended OpenText™ Archive Center together with Oracle
Server.
ERLK160200-00-IWO-EN-01
OpenText™ Extended ECM for SAP® Solutions
Installation Guide for Microsoft Windows with Oracle Database
ERLK160200-00-IWO-EN-01
Rev.: 2017-Mar-23
This documentation has been created for software version 16.2.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2017 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
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 .................................................................... 10
2 Overview ................................................................................... 13
Part 1 Setting up the server for Archive Center 15
3 Prerequisites ............................................................................ 17
4 Preparing the server ................................................................ 19

4.1 Configuring Tomcat ......................................................................... 19
4.2 Installing Oracle Database 11g R2 ................................................... 20
4.3 Creating a database user for Archive Center ..................................... 21
5 Installing the server for Archive Center ................................ 23

5.1 Using the Extended ECM for SAP Solutions Master Setup for
Extended Archive Center ................................................................. 23
5.2 Installing Archive Center .................................................................. 25
5.3 Installing Archive Monitoring Server .................................................. 28
5.4 Installing Solution Registry Agent ..................................................... 30
5.5 Installing Administration Client ......................................................... 31
5.6 Installing Directory Services ............................................................. 32
5.7 Install Document Pipeline components ............................................. 38
6 Installing the services ............................................................. 39

6.1 Using the Extended ECM for SAP Solutions Master Setup ................. 39
6.2 Installing Extended ECM Web Services ............................................ 39
6.2.1 Deploying Content Web Services ..................................................... 40
6.2.2 Configuring host and port for Content Server in Tomcat ..................... 41
6.3 Installing Enterprise Library Services ................................................ 41
Part 2 Setting up the server for Content Server 45
7 Prerequisites ............................................................................ 47
8 Setting up IIS 7.5 ...................................................................... 49
9 Installing Oracle Database Client and setting up the

communication between Oracle Database Server and
Client ......................................................................................... 63
9.1 Installing Oracle Database Client 11g R2 .......................................... 63
9.2 Setting up the communication between Oracle Database Server
and Oracle Database Client ............................................................. 67
OpenText Extended ECM for SAP Solutions – Installation Guide for Microsoft Windows with
Oracle Database iii
ERLK160200-00-IWO-EN-01
Table of Contents
10 Using the Extended ECM for SAP Solutions Master Setup

for Content Server ................................................................... 77
11 Installing Content Server on Windows .................................. 81
12 Installing Content Server modules ........................................ 91
13 Configuring Content Server ................................................... 93
14 Configuring OpenText Directory Services for Content

Server ..................................................................................... 105
14.1 Creating a resource ....................................................................... 105
14.2 Setting the resource ID at Content Server ....................................... 106
14.3 Setting up a synchronized OTDS user partition from Active Directory ...
108
14.4 Editing memberships to OTDS roles ............................................... 110
15 Installing the Content Server modules ................................ 111
16 Testing Content Server search ............................................ 113
Part 3 Installing patches 115
17 Installing Enterprise Library patches .................................. 117
18 Installing Content Server patches using the cluster

management tool ................................................................... 119
Part 4 Configuring Enterprise Library Services 121
19 Starting the Administration Client ....................................... 123
20 Configuring OpenText Directory Services for Archive

Center ..................................................................................... 127
21 Configuring Archive Center .................................................. 129

21.1 Creating the connection from Archive Center to Content Server ....... 129
21.2 Creating disk volumes for storage and for disk buffer ....................... 131
21.3 Creating a buffer ........................................................................... 132
21.4 Creating a logical archive ............................................................... 133
21.5 Creating a pool ............................................................................. 135
21.6 Attaching a volume to a pool .......................................................... 138
22 Configuring the storage provider ........................................ 139
23 Creating a storage provider and a storage rule .................. 141
24 Enabling certificates ............................................................. 145
iv Oracle Database
ERLK160200-00-IWO-EN-01
Table of Contents
25 Creating an application ......................................................... 147
Part 5 Installing Archiving and Document Access for SAP

Solutions 151
26 Introduction ............................................................................ 153
27 Checking prerequisites ......................................................... 155

27.1 Required knowledge ...................................................................... 155
27.2 Software packages ........................................................................ 155
27.3 Terms and definitions .................................................................... 156
27.4 SAP prerequisites ......................................................................... 156
27.5 Installation tool .............................................................................. 157
27.6 Installation packages and passwords ............................................. 158
27.7 Web Dynpro configuration ............................................................. 159
28 Installing Basis package ....................................................... 161

28.1 Installing package ......................................................................... 161
28.2 Configuring components ................................................................ 164
28.2.1 Setting number ranges .................................................................. 164
28.2.2 Defining authorizations .................................................................. 164
28.2.3 Defining settings for logging ........................................................... 165
28.2.4 Defining settings for optional sample projects .................................. 165
28.3 Authorizations ............................................................................... 166
28.4 DocuLink ...................................................................................... 166
28.4.1 General information ....................................................................... 166
28.4.2 Authorizations ............................................................................... 166
28.4.3 Testing the DocuLink installation .................................................... 167
29 Installing ERP option package ............................................. 169

29.1 Installing the ERP package ............................................................ 169
30 Installing CRM option package ............................................ 171

30.1 Installing the package .................................................................... 171
31 Installing language packages ............................................... 173
32 Handling communication protocols .................................... 177

32.1 Maintaining OLE application .......................................................... 177
32.2 Maintaining SAP ArchiveLink application ........................................ 179
32.3 Assigning protocols to logical archives (content repositories) ........... 184
Part 6 Setting up Extended ECM for SAP Solutions 185
33 Checking the prerequisites .................................................. 187
Oracle Database v
ERLK160200-00-IWO-EN-01
Table of Contents
33.1 Required knowledge ...................................................................... 187

33.2 Prerequisites ................................................................................ 187
33.2.1 SAP prerequisites ......................................................................... 187
33.2.2 Content Server prerequisites .......................................................... 190
33.3 SAP Add-On Installation Tool (SAINT) ............................................ 191
33.4 Finding version information for Extended ECM for SAP Solutions
relevant system components .......................................................... 192
34 Installing the SAP package ................................................... 195
35 Installing language packages in the SAP system .............. 197
36 Performing general post-installation tasks in SAP ............ 199

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

CRM 7.0, and SAP SRM 7.0 ................................................... 205
37.1 Exporting the SAP PSE certificate for the SAP authentication
handler ......................................................................................... 205
37.2 Activating the SSO HTTP service ................................................... 208
37.3 Creating logical ports in the SAP system ........................................ 209
37.3.1 Creating logical ports for SAP Basis 7.0 .......................................... 209
37.3.2 Creating logical ports for SAP Basis 7.01 ........................................ 216
37.4 Configuring the Service Provider Interface service ........................... 227
37.5 Maintaining Extended ECM connections ......................................... 228
37.6 Improving data security for impersonation connections .................... 232
37.7 Importing the Content Server SSL certificate ................................... 233
38 Performing post-installation or post-upgrade tasks in

Content Server ....................................................................... 235
38.1 Importing root certificates for Secure Sockets Layer (SSL)
connections .................................................................................. 235
38.2 Connecting an external system ...................................................... 236
38.3 Managing users ............................................................................ 238
38.4 Preparing document declaration ..................................................... 239
38.4.1 Creating a Records Management classification (optional) ................ 239
38.4.2 Importing folder and item type ........................................................ 239
38.4.3 Setting up the authorization for records ........................................... 241
38.4.4 Creating system categories in Content Server ................................. 242
38.5 For SAP CRM and SRM: Configuring security settings .................... 243
39 Installing language packs on Content Server ..................... 245
vi Oracle Database
ERLK160200-00-IWO-EN-01
Table of Contents
40 Verifying the installation ....................................................... 247

40.1 Analyzing the SAP system ............................................................. 247
40.1.1 Understanding the SAP Diagnostic Program ................................... 247
40.1.2 Understanding the details of the Diagnostic Program ....................... 248
41 Preparing a checklist for the customizing team ................. 255
Oracle Database vii
ERLK160200-00-IWO-EN-01
Chapter 1
What is OpenText Extended ECM for SAP Solutions
OpenText Extended ECM for SAP Solutions is a combination of Content Server

modules, web services 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 a business
workspaces, object. From Content Server side, users can easily view the data of this business
cases and
binders
object. From the business application, users can access Content Server items in the
business workspace without leaving their system. To make full use of the Content
Server functionality, not only business workspaces but also cases and binders can be
configured for Extended ECM for SAP Solutions.
Business In addition to the content that is stored in a business workspace for a business object,
attachments users can connect additional documents as business attachments to a 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?

“Configuring OpenText Directory Services for Content Server“, page 105
To configure OpenText Directory Services, use the new web administration
client.
“Configuring OpenText Directory Services for Archive Center“, page 127
To configure the resource for Archive Center, you can use the OTDS connection
assistant in the Administration Client.
“Improving data security for impersonation connections”, page 232
For an improved data security, you can now create a whitelist that contains all
Content Server URLs which are allowed to connect to the SAP system.
Oracle Database 9
ERLK160200-00-IWO-EN-01
Chapter 1 What is OpenText Extended ECM for SAP Solutions
1.2 Related documentation

Important
OpenText strongly recommends that you read OpenText Extended ECM for
SAP Solutions - Overview Guide (ERLK-GGD) to make you familiar with
architectural aspects and business scenarios of Extended ECM for SAP
Solutions.
Product docu- The following documentation is available for Extended ECM for SAP Solutions
mentation respectively on OpenText My Support (https://knowledge.opentext.com/knowledge/
cs.dll/Open/https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10194282):
OpenText Extended ECM for SAP Solutions - Overview Guide (ERLK-GGD)

The Overview Guide contains a short overview over the functions and features
of Extended ECM for SAP Solutions. It also explains the architecture and shows
different business scenarios of Extended ECM for SAP Solutions.
OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide (ERLK-IGD)
The Installation Guide describes the installation and upgrade of Extended ECM
for SAP Solutions up to the point where the connection between SAP and
Content Server is established.
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
The Customizing Guide describes how to customize SAP and configure Content
Server for Extended ECM for SAP Solutions functionality.
OpenText Extended ECM 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 (ERLK-CUM)
This guide discusses user management and access control scenarios.
OpenText Extended ECM for SAP Solutions - User Guide (ERLK-UGD)
The User Guide describes how to use Extended ECM for SAP Solutions
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 (ERLK-IWS)
This specific Installation Guide describes 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 Database (ERLK-IWO) (this guide)
This specific Installation Guide describes the setup of one architecture scenario
for Extended ECM for SAP Solutions with Oracle as database.
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product
• Requirements
10 Oracle Database
ERLK160200-00-IWO-EN-01
1.2. Related documentation
• 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 Extended ECM
for SAP Solutions Release Notes is available on OpenText My Support: Extended
ECM for SAP Solutions (https://knowledge.opentext.com/knowledge/cs.dll/Open/
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10194282).
Oracle Database 11
ERLK160200-00-IWO-EN-01
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 installation media. It includes OpenText Enterprise
Library.
The document describes the following scenario:

• One server for Archive Center including OTDS, Enterprise Library Services,
Extended ECM Services
• One server for the Content Server. On this server, you must install the Oracle
client and configure it with Oracle Server before starting the Content Server
installation.
These servers can be physical or virtual.
This guide describes the setup of a system environment containing these

components:
• Microsoft Windows Server 2012
Oracle Database 13
ERLK160200-00-IWO-EN-01
Chapter 2 Overview
• Web application server is Apache Tomcat for Archive Center

• Database platform is Oracle 11g Release2
• SAP ERP 6.x
• Single-File-Storage on the Archive Center on local hard-disk
The installation and configuration of the following components is NOT described in

this guide:
• MS SQL Server platform (see separate guide OpenText Extended ECM for SAP
Solutions - Installation Guide for Microsoft Windows with Microsoft SQL Server
(ERLK-IWS))
• 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.
14 Oracle Database
ERLK160200-00-IWO-EN-01
Part 1
Setting up the server for Archive Center
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.
Oracle Database 17
ERLK160200-00-IWO-EN-01
Chapter 4
Preparing the server
Install the following components on the server that you want to use for the Archive
Center. Refer to the respective product documentation for detailed information. The
following table only lists the most important settings.
Component Link Preferences

Java Runtime Environment 8 http://www.java.com Download the file and install
64 Bit, latest version it.
Apache Tomcat 64 Bit. For http://tomcat.apache.org • HTTP/1.1 Connector
information about the latest Port: 8080 or 8090 for
supported version, see SSL
Release Notes. • Do not enter a user nor
password.
• Select the Run Apache
Tomcat option. Then
check under Start >
Administration Tools >
Services, to see whether
the Apache Tomcat
service has started.
4.1 Configuring Tomcat

To configure Tomcat:
1. Start the Tomcat configuration program with administrator permissions: Click

Start > All Programs > Apache Tomcat <Version> Tomcat <Version>. Right-
click Configure Tomcat and click Start as Administrator.
2. Under the Java tab, in the Initial memory pool field, enter 512 MB.
In the Maximum memory pool field, enter 1024 MB (proposal for demo or test
system).
3. Click OK.
4. Open the <Tomcat home>\conf\logging.properties file in an editor.
5. Remove the line that begins with .handlers = ... in the java.util.logging.
ConsoleHandler entry and save the file.
6. Restart the Apache Tomcat service.
7. Test Tomcat: Go to the URL http://localhost:8080. The Tomcat homepage will be

displayed.
Oracle Database 19
ERLK160200-00-IWO-EN-01
Chapter 4 Preparing the server
8. Stop the Apache Tomcat service in order to prevent unwanted software

deployments. Restart the service once the installation of Open Text components
is complete.
4.2 Installing Oracle Database 11g R2

Install Oracle Database 11g according to the manufacturer instructions. The
following table shows the settings that OpenText recommends for this installation.
Note: If you have the Oracle Database installed on another server, install
Oracle Client here instead, see “Installing Oracle Database Client 11g R2”
on page 63.
Page in the installation program Inputs

Select Installation Option Create and configure a database
System Class Server Class
Grid Installation Options Single Instance Database Installation
Select Install Type Advanced Install, so that you can set the
character set later.
Select Product Languages Select the relevant languages.
Select Database Edition Select Enterprise Edition. OpenText
recommends that you only use this version.
Specifiy Installation Location Software Location
Select Configuration Type General Purpose/Transaction Processing
Specify Database Identifiers Enter a global database name, e.g. orcl.
eng-muc.opentext.net and an Oracle
Service Identifier (SID), e.g. orcl
Configuration Options, Character sets tab Use Unicode (AL32UTF8). Use this character
set only.
Configuration Options, Security tab Assert all new security settings
Configuration Options, Sample Schemas Do not activate: Create database with
tab sample schema
Management Options Use Oracle Enterprise Manager Database
Control for database management
Specify Database Storage Options As required, for example File System
Specify Recovery Options As required
Specify Schema Passwords As required, for example Use same
password for all accounts
20 Oracle Database
ERLK160200-00-IWO-EN-01
4.3. Creating a database user for Archive Center
4.3 Creating a database user for Archive Center

To create a database and user for Archive Center:
1. Start SQL*Plus.
sqlplus [[SDLENTITYREF[lt]]]DBA_User_Name>/
[[SDLENTITYREF[lt]]]DBA_User_Password>@[[SDLENTITYREF[lt]]]SID>
as SYSDBA
Example:
sqlplus sys/Ot$temp1@orcl as SYSDBA
2. Enter the following SQL command to create a tablespace for Archive Center:
Create two tablespaces, one for data and one for the index :
create tablespace [[SDLENTITYREF[lt]]]NAME> datafile

'[[SDLENTITYREF[lt]]]Data File>' size 100M autoextend on;
Example:
create tablespace ASV_DATA datafile 'D:\oradata\asv_data.dbf'

size 100M autoextend on;
create tablespace ASV_INDEX datafile 'D:\oradata
\asv_index.dbf' size 100M autoextend on;
3. Enter the following SQL commands to create a database user and assign the
default tablespace.
create user [[SDLENTITYREF[lt]]]User_Name> identified by

[[SDLENTITYREF[lt]]]Password>;
grant create sequence to [[SDLENTITYREF[lt]]]User_Name>;
grant create table to [[SDLENTITYREF[lt]]]User_Name>;
grant create view to [[SDLENTITYREF[lt]]]User_Name>;
grant create session to [[SDLENTITYREF[lt]]]User_Name>;
grant create procedure to [[SDLENTITYREF[lt]]]User_Name>;
grant alter session to [[SDLENTITYREF[lt]]]User_Name>;
grant query rewrite to [[SDLENTITYREF[lt]]]User_Name>;
grant select on v_$session to [[SDLENTITYREF[lt]]]User_Name>;
grant select on v_$parameter to [[SDLENTITYREF[lt]]]User_Name>;
grant select on v_$parameter2 to [[SDLENTITYREF[lt]]]User_Name>;
grant execute on DBMS_SQL to [[SDLENTITYREF[lt]]]User_Name>;
alter user [[SDLENTITYREF[lt]]]User_Name> default tablespace
[[SDLENTITYREF[lt]]]DATA_TABLESPACE>;
alter user [[SDLENTITYREF[lt]]]User_Name> quota unlimited on
[[SDLENTITYREF[lt]]] DATA_TABLESPACE>;
alter user [[SDLENTITYREF[lt]]]User_Name> quota unlimited on
[[SDLENTITYREF[lt]]]INDEX_ TABLESPACE>;
Example:
create user asv identified by asv;

grant create sequence to asv;
grant create table to asv;
grant create view to asv;
Oracle Database 21
ERLK160200-00-IWO-EN-01
Chapter 4 Preparing the server
grant create session to asv;

grant create procedure to asv;
grant alter session to asv;
grant query rewrite to asv;
grant select on v_$session to asv;
grant select on v_$parameter to asv;
grant select on v_$parameter2 to asv;
grant execute on DBMS_SQL to asv;
alter user asv default tablespace asv_data;
alter user asv quota unlimited on asv_data;
alter user asv quota unlimited on asv_index;
4. Exit SQL*Plus.
22 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 5
Installing the server for Archive Center
This chapter describes the installation of Directory Services, Archive Center,

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 My Support.
5.1 Using the Extended ECM for SAP Solutions

Master Setup for Extended Archive Center
The Extended ECM for SAP Solutions Installer leads through the complete
installation process and start the separate installers for the different components on
after the other.
To start the Master Setup for Extended Archive Center on the first server:
1. Download the OpenText Extended ECM for SAP Solutions ISO-9660 image
from the OpenText My Support and burn a DVD from it.
For some Windows Server versions, for example 2012 R2, you can mount the
DVD in Windows Explorer using the context menu of the ISO or by double-
clicking on the ISO.
Alternatively, use a third-party tool to mount the ISO image as a virtual drive.
Using this method, you can directly start the installer in the image file. For
details, see My Support (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 installer starts.
4. In the OpenText Extended ECM for SAP Solutions 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 Center

Deployment and click Next.
Oracle Database 23
ERLK160200-00-IWO-EN-01
Chapter 5 Installing the server for Archive Center
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.
24 Oracle Database
ERLK160200-00-IWO-EN-01
5.2. Installing Archive Center
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 Archive Center

The installer for Archive Center is started automatically by the master setup. The
installer guides you through the installation. For information about the inputs, see
“Installing Archive Center” on page 25.
Note: The installation log can be found under %TEMP%\opentext.
Table 5-1: Installing Archive Center
Page in the installation wizard Input

Apache Tomcat Parameters Service name, for example Apache
Tomcat85.
Ports Web Application Server Ports, usually 8080 for the HTTP port and
8090 for the SSL port.
Destination Folders Folder for installation and configuration.
Oracle Database 25
ERLK160200-00-IWO-EN-01

Service User Settings Run the Archive Spawner service as user.
Enter the user including domain, password,
and then enter the password again to
confirm. You must enter a password. Tomcat
must be running with the same user.
Log and Var Folders Paths for logs (log) and runtime files (var).
You can only change the paths if they were
not defined beforehand.
Database System Oracle. Select Create Schema.
Oracle Parameters (1/2) Enter the data corresponding to the entries
that you have entered in 4.2 and 4.3.
Database server: Name of the computer on

which the database is located, for example
vmmucels01ora.eng-muc-test.
opentext.net)
Database port: Port for connections to the

database: 1521
Database user: Name of the database user

for Archive Center that was created in 4.3,
for example asv
Database password: Database user

password
Important
Do not use blank passwords!
Oracle service: Name of the Oracle Database

Server Service, for example orcl
Oracle SID: SID of the Oracle Database

Server, for example orcl.
26 Oracle Database
ERLK160200-00-IWO-EN-01
5.2. Installing Archive Center

Oracle Parameters (2/2) Data tablespace: Tablespace for the Archive
Center data, for example ASV_DATA
Index tablespace: Tablespace for the Archive

Center index, for example ASV_INDEX
TNS admin directory: Path to tnsnames.

ora, for example C:\app\Administrator
\product\OraHome_1\network\admin
Oracle home directory: Oracle program

directory, for example C:\app\
Administrator\product\OraHome_1
Check the settings carefully.
Important
If the database server is not installed
on the computer, turn on the
computer firewall off.
The installation file is testing the connection

to the database. If an error occurs, check
%TEMP%\opentext\MakeSchema.log.
ISO Image Configuration Paths and directories for the ISO directory
trees and ISO image files. This information is
not used here, but must be entered.
Important
The directories must be different to
each other, for example ISODIR
and IMGDIR.
Directory Services Parameters Run Archive Server with built-in User
Management (dsadmin)
Note: The user dsadmin is used

throughout the Archive Center
installation, when this option is
activated. This is necessary because
OTDS has not yet been installed. You
can also use this user even by adding
Archive Center in the Administration
Client. You can change the log in data
later.
You can configure OTDS later. For

more information, see “Configuring
OpenText Directory Services for
Archive Center“ on page 127.
Oracle Database 27
ERLK160200-00-IWO-EN-01
Note: You can find logging information in %TEMP%\opentext.
5.3 Installing Archive Monitoring Server

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

2. In the Apache Tomcat Parameters window, select the service name and click
Next.
3. 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.
28 Oracle Database
ERLK160200-00-IWO-EN-01
5.3. Installing Archive Monitoring Server
Click Next.
4. Specify the service user settings.
Note: You can only change these settings if they were not specified before.
Select one of the following:
• 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.
Click Next.
5. 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.
6. Click Install. The installation process takes place.
Oracle Database 29
ERLK160200-00-IWO-EN-01
7. When the installation procedure has finished, click Finish.
5.4 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:
2. In the Destination Folder window opens, specify the installation folder of

Solution Registry Agent.
3. Click Next.
4. In the Ready to Install window, click Install. The installation process takes
place.
30 Oracle Database
ERLK160200-00-IWO-EN-01
5.5. Installing Administration Client
5.5 Installing Administration Client

Administration Client can only be installed on Windows systems.
To install Administration Client:
2. In the Destination Folder window, specify the installation folder of

Administration Client.
3. Click Next.
4. In theReady to Install window, click Install. The installation process takes

place.
Oracle Database 31
ERLK160200-00-IWO-EN-01
5.6 Installing Directory Services

To install Directory Services:
2. 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.
3. Specify the application server to be used.
32 Oracle Database
ERLK160200-00-IWO-EN-01
5.6. Installing Directory Services
4. Select the check box if you want to setup the server as a replication server.
Oracle Database 33
ERLK160200-00-IWO-EN-01
5. Enter the path to the Java SE installation directory.
6. In the Apache Tomcat Directory window, enter the service name tomcat8 or the
installation directory.
34 Oracle Database
ERLK160200-00-IWO-EN-01
7. In the Directory Services Parameters window, apply the default settings and
click Next.
Oracle Database 35
ERLK160200-00-IWO-EN-01
• 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).
8. 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.
36 Oracle Database
ERLK160200-00-IWO-EN-01
9. In the OpenText Directory Services Data Import window, click Next.
Oracle Database 37
ERLK160200-00-IWO-EN-01
10. 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.7 Install Document Pipeline components

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

• Document Pipeline for Enterprise Library 16
• Document Pipeline for Content Server 16
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.
38 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 6
Installing the services
This chapter describes the installation of the Extended ECM web services and the
Enterprise Library services.
6.1 Using the Extended ECM for SAP Solutions

Master Setup
The Extended ECM for SAP Solutions Installer leads through the complete
installation process and start the separate installers for the different components on
after the other.
To deploy Extended ECM Web Services:
1. Run the Mastersetup.exe file (Mastersetup for Unix) located on the

installation medium and accept the license agreement.
2. Select Advanced Deployment (Custom Selection) and click Next.
3. Under Services, select the Extended ECM Web Services entry and the
Enterprise Library Services.
4. Click Next and click Install.
5. Restart Tomcat manually once after the installation.
6.2 Installing Extended ECM Web Services

To install Extended ECM Web Services:
2. In the Apache Tomcat Parameters window, select the service name.
Oracle Database 39
ERLK160200-00-IWO-EN-01
Chapter 6 Installing the services
Click Next
place.
6.2.1 Deploying Content Web Services

Extended ECM for SAP Solutions 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.
You can deploy Content Web Services in IIS or in Tomcat automatically using the
Content Server installer. If you use the setup, keep the default value cws.
If you do not use the installer, deploy Content Web Services as follows.
To deploy Content Web Services:
1. Copy the cws.war file into your <Tomcat home>/webapps directory.

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" />
40 Oracle Database
ERLK160200-00-IWO-EN-01
6.3. Installing Enterprise Library Services
to <param name="File" value="../logs/cws.log" />.
6.2.2 Configuring host and port for Content Server in Tomcat

After installation of the Apache Tomcat web server, and deployment of the
Extended ECM 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 instance.
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.
6.3 Installing Enterprise Library Services

Enterprise Library Services provide the services for connections to Content Server.
To install Enterprise Library Services:
2. In the Apache Tomcat Parameters window, select the service name you entered
before during the Directory Services installation.
Oracle Database 41
ERLK160200-00-IWO-EN-01
Chapter 6 Installing the services
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).
42 Oracle Database
ERLK160200-00-IWO-EN-01
6.3. Installing Enterprise Library Services
Click Next
place.
Oracle Database 43
ERLK160200-00-IWO-EN-01
Part 2
Setting up the server for Content Server
Chapter 7
Prerequisites
Following software components must be installed:

• Microsoft Windows Server 2012 R2.
Following settings are required:

• Content Server has to be in the same domain as the SAP system.
You need a user with all administrative rights is available. For this example, we use
the user administrator.
Oracle Database 47
ERLK160200-00-IWO-EN-01
Chapter 8
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 configure 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.
Oracle Database 49
ERLK160200-00-IWO-EN-01
Chapter 8 Setting up IIS 7.5
4. Select Role-based or feature-based installation and click Next.
5. Select the server.
50 Oracle Database
ERLK160200-00-IWO-EN-01
6. Select Web Server (IIS), and click Next.
7. Click Add features.
Oracle Database 51
ERLK160200-00-IWO-EN-01
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.
52 Oracle Database
ERLK160200-00-IWO-EN-01
9. The Web Server Role (IIS) displays information. Click Next.
10. Click Role Services and select the following:
Oracle Database 53
ERLK160200-00-IWO-EN-01
• 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.
54 Oracle Database
ERLK160200-00-IWO-EN-01
Oracle Database 55
ERLK160200-00-IWO-EN-01
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.
56 Oracle Database
ERLK160200-00-IWO-EN-01
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 Error
Pages.
3. Click Edit Feature Settings. In the Edit Error Pages Settings dialog box, click
Detailed errors for local requests.
4. 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.
5. Click Add.
Oracle Database 57
ERLK160200-00-IWO-EN-01
6. In the File name extension box, enter .properties, and in the MIME type box
enter application/octet-stream.
Click OK.
7. 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.
8. Click Add Authoring Rule in the Actions dialog.
58 Oracle Database
ERLK160200-00-IWO-EN-01
9. 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.
10. In the Actions dialog, click WebDAV Settings.
Oracle Database 59
ERLK160200-00-IWO-EN-01
11. 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.
12. In the Actions dialog, click WebDAV Authoring Rules.
13. In the Actions dialog, click Enable WebDAV.
14. In the IIS Manager in the Connections tree, click Default Web Site.
15. In the Default Web Site Home dialog, double-click HTTP Response Headers.
60 Oracle Database
ERLK160200-00-IWO-EN-01
16. In the Actions dialog, click Set Common Headers… or, alternatively, right-click
the HTTP Response Headers Feature Page and click Set Common Headers….
17. 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.
Oracle Database 61
ERLK160200-00-IWO-EN-01
18. 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.
62 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 9
Installing Oracle Database Client and setting up the
communication between Oracle Database Server
and Client
This chapter describes the installation of the basic non-OpenText components

required for Content Server.
9.1 Installing Oracle Database Client 11g R2

To install Oracle Database Client:
1. Insert the Oracle Database Client DVD.

If the installation does not start automatically, run <DVD drive>:\setup.exe.
2. On the Select Installation Type page, select Administrator.
Note: Administrator - This installation type installs the Oracle Enterprise

Manager Standalone Console, Oracle networking services, and client
software that enables applications or individuals to connect to an Oracle
Database. It also installs development tools that you can use to develop
applications.
Oracle Database 63
ERLK160200-00-IWO-EN-01
Chapter 9 Installing Oracle Database Client and setting up the communication between
Oracle Database Server and Client
Click Next.
3. On the Select Products Languages page, select English.
64 Oracle Database
ERLK160200-00-IWO-EN-01
9.1. Installing Oracle Database Client 11g R2
Click Next.
4. On the Specify Installation Location page, specify the Software Location path.
The Oracle Base path will be adjusted by the system accordingly.
Click Next.
5. On the Perform Prerequisite Checks page, wait until the check is completed
and the Summary page displays.
Oracle Database 65
ERLK160200-00-IWO-EN-01
6. Click Save Response File to save the data base client installation details into a
file.
66 Oracle Database
ERLK160200-00-IWO-EN-01
9.2. Setting up the communication between Oracle Database Server and Oracle Database
Client
7. Click Finish to start the installation.

8. On the Finish page, click Close to complete the Oracle client installation.
9. To test the communication between Oracle Server and client use TNSPING:
On the command line in the system and call tnsping orcl.
The result should be OK.
9.2 Setting up the communication between Oracle

Database Server and Oracle Database Client
To setup the communication between Oracle Database Server and Oracle
Database Client:
1. In the server where Oracle Database Client is installed, from Windows Start
menu, select Oracle > OraClient11g-home1 > Configuration and Migration
Tools > Net Manager.
Oracle Database 67
ERLK160200-00-IWO-EN-01
2. On the Oracle Net Manager page, expand the tree Oracle Net Configuration >
Local > Service Naming.
3. Click + to add a new entry.

4. On the Net Service Name Wizard: Welcome page, enter name for Net Service
Name.
68 Oracle Database
ERLK160200-00-IWO-EN-01
Client
Click Next.
5. On the Net Service Name Wizard, page 2 of 5: Protocol page, select TCP/IP
(Internet Protocol).
Click Next.
6. On the Net Service Name Wizard, page 3 of 5: Protocol Settings page, enter the
Oracle Server host name and the Oracle Server port number.
Note: Default Port of Oracle Server is 1521.
Oracle Database 69
ERLK160200-00-IWO-EN-01
Click Next.
7. On the Net Service Name Wizard, page 5 of 5: Test click Test.
8. On the Connection Test page, click Change Login.
70 Oracle Database
ERLK160200-00-IWO-EN-01
Client
9. On the Change Loginpage, enter the correct user name, for example system,
and the password. Click OK.
Oracle Database 71
ERLK160200-00-IWO-EN-01
10. On the Connection Test page, click Test.
Note: The test result message should be successful to confirm that the
communication between Oracle Client and Server worked.
72 Oracle Database
ERLK160200-00-IWO-EN-01
Client
11. On the Net Service Name Wizard, page 5 of 5: Test page, click Finish.
12. On the Oracle Net Manager page, select File > Save As from the menu.
Oracle Database 73
ERLK160200-00-IWO-EN-01
13. On the Service Network Configuration page, click OK to save the

configuration in file tnsnames.ora in the path <Oracle Client Home>\network
\admin.
74 Oracle Database
ERLK160200-00-IWO-EN-01
Client
Oracle Database 75
ERLK160200-00-IWO-EN-01
Chapter 10
Using the Extended ECM for SAP Solutions Master
Setup for Content Server
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 ISO-9660 image
from the OpenText My Support and burn a DVD from it.
For some Windows Server versions, for example 2012 R2, you can mount the
DVD in Windows Explorer using the context menu of the ISO or by double-
clicking on the ISO.
Alternatively, use a third-party tool to mount the ISO image as a virtual drive.
Using this method, you can directly start the installer in the image file. For
details, see My Support (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
Installer starts.
4. In the OpentText Extended ECM for SAP Solutions 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.
Oracle Database 77
ERLK160200-00-IWO-EN-01
Chapter 10 Using the Extended ECM for SAP Solutions Master Setup for Content Server
7. Click Next.
8. In the Product Groups window, the components to be installed are displayed. If

you want to install additional modules, expand the list and select them.
78 Oracle Database
ERLK160200-00-IWO-EN-01
9. Under Content Server and Modules, verify that the Connected Workspaces
entry is selected.
As the Enforce selection dependencies checkbox is selected as default, all the
dependent modules will be selected as well.
10. In the Summary window, check that all required modules are listed.
Oracle Database 79
ERLK160200-00-IWO-EN-01
Chapter 10 Using the Extended ECM for SAP Solutions Master Setup for Content Server
11. Click Install.
80 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 11
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 My Support.
After clicking Install in the Master Setup, the Install Location window opens.

2. In the Install Location window, enter the path as displayed or accept the
default.
3. Click Next.
4. 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.
Oracle Database 81
ERLK160200-00-IWO-EN-01
Chapter 11 Installing Content Server on Windows
HTTP Server Name: Keep localhost.

HTTP Port Number: Keep 80.
Click Next.
5. Select Internet Information Services (IIS) and click Next.
82 Oracle Database
ERLK160200-00-IWO-EN-01
6. In the IIS Web Server Mapping window, accept the default URL prefix for
the /img/ support directory or enter a new prefix.
Oracle Database 83
ERLK160200-00-IWO-EN-01
Click Next.
7. In the Port Configuration for Content Server window, accept the default values
for Service Port, Admin Port, and RMI Port.
84 Oracle Database
ERLK160200-00-IWO-EN-01
Click Next.
8. As Web Server type for Content Web Services, select Apache Tomcat and click
Next.
Oracle Database 85
ERLK160200-00-IWO-EN-01
9. Enter the path.
86 Oracle Database
ERLK160200-00-IWO-EN-01
10. Enter the web server settings.
Oracle Database 87
ERLK160200-00-IWO-EN-01
88 Oracle Database
ERLK160200-00-IWO-EN-01
12. 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.
13. The mappings.tbl file is opened in a separate window. Check it and close the
window.
Oracle Database 89
ERLK160200-00-IWO-EN-01
Chapter 12
Installing Content Server modules
Content Server modules are installed using the same steps. The setups of Content
Server modules are initiated from the OpenText Extended ECM for SAP Solutions
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.
6. Click Finish to end the OpenText Extended ECM for SAP Solutions Installer.
7. Now the binaries are installed and the modules are prepared for a later
installation in Content Server.
8. To test the installation, check whether the installed modules are located in the
Content Server staging directory C:\opentext\staging.
Oracle Database 91
ERLK160200-00-IWO-EN-01
Chapter 13
Configuring Content Server
This chapter describes the most important steps and parameters. For information
about all parameters, see section 6 “Configuring Content Server” in OpenText
Content Server - Installation Guide (LLESCOR-IGD).
To configure Content Server:
1. Start Content Server Administration:

From the Start menu, click Open Text Content Server 16.2 (OTCS), and then
click Content Server Administration.
Alternatively, call this URL: ../OTCS/cs.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.
Tip: This is the password that you use to access the Content Server
Administration page during the initial setup of Content Server, if Content
Server cannot connect to its database, or if Content Server cannot connect
to OpenText Directory Services.
4. To enable Content Server logging select Detailed Thread Logging. Logging is

recommended in the configuration phase.
Oracle Database 93
ERLK160200-00-IWO-EN-01
Chapter 13 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.
94 Oracle Database
ERLK160200-00-IWO-EN-01
10. On the Select RDBMS Type page, select Oracle Server.
11. Click Continue.
12. On the Oracle Server Administrator Log-in page, enter the Oracle Server
Details.
System User Name: Oracle Database Server DBA User Name (for example
system).
Password: Password for Oracle Database Server DBA User.
Service Name: Oracle Database Server service name (for example orcl)
Oracle Database 95
ERLK160200-00-IWO-EN-01
13. Click Log-in.
14. On the server where Oracle Database is installed: Create the D:\csstore folder.
15. On the Create Content Server tables page, click Oracle Server Maintenance.
16. In the Create New Tablespace area, enter the parameter values as displayed in
the following screenshot.
Note: The file size errors need to be adjusted in case this is NOT a test
system.
96 Oracle Database
ERLK160200-00-IWO-EN-01
17. Click Create Tablespace.
18. In the Create A New User area, enter the parameter values as displayed in the
following screen shot. Ensure that table space (for example cs16) created in
before has been selected as Default Tablespace.
19. Click Create User.
20. Click Return to previous page to go to the previous page and set the parameter
values as displayed in the following screenshot.
21. Ensure that cs16 is selected as Oracle User Name.
22. Click Create Tables.
Oracle Database 97
ERLK160200-00-IWO-EN-01
23. In the Username box, enter Admin and in the Password box, enter the default
value livelink.
Note: You can change the default password later after the basic
configuration is finished. For more information about the different
administrator users, see Content Server Admin Online Help > Changing
the Administrator Password and the the Admin User Password.
24. Click Log-in.
25. 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.
98 Oracle Database
ERLK160200-00-IWO-EN-01
26. On the Configure OTDS Integration Settings page, in the Server Type menu,
select External OTDS Server.
Note: Do not use an internal OTDS server for Extended ECM for SAP
Solutions.
Switch to Directory Services Administration and create a resource now.
a. Start Directory Services Administration in a web browser. Open http://

<fully_qualified_domain_name_of_server>:<port_number/otds-
admin/ and sign in as otadmin@otds.admin.
b. On the Directory Services Administration menu, click Resources and click
Add.
c. On the General page, enter the resource name for example OTCS or Content
Server Resource and click Next.
Oracle Database 99
ERLK160200-00-IWO-EN-01
d. On the Synchronization page, select the User and group synchronization

box. From the Synchronization connector list, select Content Server.
Keep the Create users and groups and Modify users and groups rights
selected and the Delete users and groups right unselected. Click Next.
e. In the Connection Information screen, enter the respective user and

password. Make sure that the connection settings for the Member Services
and for the Authentication Services are set to cws and not to les-services.
Do not use localhost but a fully qualified host name, for example
xecmwinsrv03.eng-muc.text.opentext.net. For all other values, apply
the default settings. Also keep Admin as the user name.
100 Oracle Database
ERLK160200-00-IWO-EN-01
To verify your settings, click Test Connection. If the result is successful,
click Next.
f. In the User Attribute Mapping screen, review the settings and click Next.
Note: For information about special user mapping secenarios and the
required settings, see OpenText Extended ECM for SAP Solutions - User
Management and Access Control Scenarios (ERLK-CUM)
g. In the Group Attribute Mapping screen, review the settings and click Next.
h. Click Save.
i. In the Resource Activation dialog, the resource identifier displays. Copy
the ID to the clipboard, nd continue with OK.
Tip: You can always display the resource identifier later. Only verify
activation after you have set the resource ID in Content Server
Administration.
In the Server URL box, enter the host name (or IP address) and port of your
OTDS server. For example, enter http://xecmwinsrv03.eng-muc-test.
opentext.net:8080/.
In the Resource ID box, enter the resource identifier of the OTDS resource that
has been set up for use with Content Server. For example, enter dba563af-
b01d-4f88-bc42-2493c97dbc87.
Click Continue.
27. On the Users and group migration page, do not select the Migrate Content
Server users and groups to OTDS and click Continue.
Oracle Database 101
ERLK160200-00-IWO-EN-01
28. 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.
29. A status window opens, displaying success or failure of the process creation.
Click Continue to complete the setup.
102 Oracle Database
ERLK160200-00-IWO-EN-01
30. 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.
Oracle Database 103
ERLK160200-00-IWO-EN-01
104 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 14
Configuring OpenText Directory Services for
Content Server
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 Content Server. Typically, this is
done during the initial configuration of Content Server. For more information, see
“Configuring Content Server “ on page 93. The resource ID and the (OTDS) server
URL are required values, and must be entered to set up (OTDS) authentication in
Content Server.
New: To configure OpenText Directory Services, use the new web

administration client.
After creating the resource, the following steps are necessary to configure OTDS:
• Creating a user partition
• Editing memberships to OTDS roles
14.1 Creating a resource

Typically, you create to resource in parallel to the initial configuration of Content
Server. For more information, see “Configuring Content Server “ on page 93. If you
want to check or change the setting later, you can access it in the Directory Services
Integration Administration on Content Server.
To create a resource:
1. Start Directory Services Administration in a web browser. Open http://

<fully_qualified_domain_name_of_server>:<port_number/otds-admin/
and sign in as otadmin@otds.admin.
2. On the Directory Services Administration menu, click Resources and click Add.
3. On the General page, enter the resource name for example OTCS or Content
Server Resource and click Next.
4. On the Synchronization page, select the User and group synchronization box.
From the Synchronization connector list, select Content Server.
Keep the Create users and groups and Modify users and groups rights selected
and the Delete users and groups right unselected. Click Next.
5. In the Connection Information screen, enter the respective user and password.
Make sure that the connection settings for the Member Services and for the
Authentication Services are set to cws and not to les-services. Do not use
Oracle Database 105
ERLK160200-00-IWO-EN-01
Chapter 14 Configuring OpenText Directory Services for Content Server
localhost but a fully qualified host name, for example xecmwinsrv03.eng-muc.

text.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.
6. In the User Attribute Mapping screen, review the settings and click Next.
Note: For information about special user mapping secenarios and the
required settings, see OpenText Extended ECM for SAP Solutions - User
Management and Access Control Scenarios (ERLK-CUM)
7. In the Group Attribute Mapping screen, review the settings and click Next.
8. Click Save.
9. In the Resource Activation dialog, the resource identifier displays. Continue

with OK.
Tip: You can always display the resource identifier later. Only verify
activation after you have set the resource ID in Content Server
Administration.
14.2 Setting the resource ID at Content Server

Typically, you set the resource ID at Content Server during the initial configuration.
For more information, see “Configuring Content Server “ on page 93. If you want to
check or change the setting later, you can access it in the Directory Services
Integration Administration.
To set the resource ID:
1. Switch to the Content Server Administration in a browser: ../OTCS/cs.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 opentext.
106 Oracle Database
ERLK160200-00-IWO-EN-01
14.2. Setting the resource ID at Content Server
4. Select Directory Services 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 Resource Activation window is still open, click Verify Activation.
Oracle Database 107
ERLK160200-00-IWO-EN-01
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.
14.3 Setting up a synchronized OTDS user partition

from Active Directory
For most customer installations these descriptions should fit. In case of issues or
major deviations compare with a LDAP browser tool, for example Softerra LDAP
browser or consult the local Active Directory experts.
To create a user partition:

2. On the Directory Services Administration menu, click Partitions.
3. In the center pane, click Add. Next, from the Add list, select New Synchronized
User Partition.
4. On theConnection Information page, specify the hostname of the directory

server (for example Mydomaincontroller.opentext.com). Leave the other port
and encryption method as it is for now (None).
5. Click Test.
If your test succeeds, a message indicating success appears. If your test fails,
close the information window, and then make any necessary corrections.
Click Next.
108 Oracle Database
ERLK160200-00-IWO-EN-01
14.3. Setting up a synchronized OTDS user partition from Active Directory
6. On the Authentication page, select Simple and specify a user including domain
(for example 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
9. On the General page, configure the Name and Description.

In our case we call the partition ECM. Clear the Use default … configuration
check box.
Click Next.
10. On the Server Settings page, use default setting AD (Active Directory) and
ensure that the proposed Base DN is correct.
Click Next.
11. On the Group Locations page, ensure that the group location setting and the
filter is suitable. Usually you can accept the proposed parameters.
Click Next.
12. On the User Locations page, ensure that the user location setting and the filter
is suitable. Usually you can accept the proposed parameters.
Click Next.
13. On the User Mappings page, verify the user attribute mappings. In general the
default OTDS attribute login name attribute sAMAccountName is suitable.
Click Next.
14. On the Group Mappings page, verify the group attribute mappings. In general
the default OTDS attribute login name attribute sAMAccountName is suitable.
Click Next.
15. On the Monitoring page, you configure how the synchronization should take
place in the future.
The default settings can be accepted for now.
Click Next
16. On the Scheduler page, define the scheduler settings.

Click Next
17. On the Notifications and Search page, for most of the installations the default
setting should be suitable.
Click Next.
18. On the Extended Functionality page, for most of the installations the default
setting should be suitable.
Click Next.
Oracle Database 109
ERLK160200-00-IWO-EN-01
19. In the summary, leave the setting Start importing users and groups
automatically selected.
20. Click Finish.

Wait till users and groups are synchronized from AD to OTDS and to Content
Server before you continue.
14.4 Editing memberships to OTDS roles

To edit memberships:

2. On the Directory Services Administration menu, click Access Roles.
3. On the Action menu for you access role (for example Access to OTCS), click
View Access Role Details.
4. On the User Partitions tab, select all relevant partitions and click OK. This adds
all users in the selected partitions to the access role.
5. Click Save to add the members to your access role.
110 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 15
Installing the Content Server modules
1. Go to the Content Server Administration Page (../OTCS/cs.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, Customizations Run Time Environment, Content Server
Generic Wizard, Calendar Attribute
2. Modules that depend on modules installed in the first step.
For example, 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 fourth step.
For example, Case Management Base Roles Wizard
6. Modules that depend on modules installed in the fifth step.
For example, Case Management
7. Connected Workspaces
8. Extended ECM Platform
9. Extended ECM for SAP Solutions
Oracle Database 111
ERLK160200-00-IWO-EN-01
Chapter 16
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.
Oracle Database 113
ERLK160200-00-IWO-EN-01
Part 3
Installing patches
Chapter 17
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.
Patches for Enterprise Library are included in the Archive Center Patch Collection at
the following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
32919421
Note: Enterprise Library Web Services Patches may be released prior to an

Archive Center Patch collection. The patches are available at the following
location: https://knowledge.opentext.com/knowledge/cs.dll/Open/14498471
To install the patches:
1. Download the current patch or patch collection.
2. Follow the patch installation instructions for the patch or the patch collection.
Oracle Database 117
ERLK160200-00-IWO-EN-01
Chapter 18
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.
In some cases there are dependencies between the patch levels on the Content Server
and Web service side. The cluster management tool only provides the Content
Server side patch.
Tip: For more information, see Cluster Management Patch Deployment System
(https://knowledge.opentext.com/knowledge/cs.dll/Open/41561891) on
OpenText My Support.
1. Go to the Content Server Administration Page ( ../OTCS/cs.exe?func=admin.

index).
2. Go to Cluster Management in the Server Configuration section.
Oracle Database 119
ERLK160200-00-IWO-EN-01
Part 4
Configuring Enterprise Library Services
Chapter 19
Starting the Administration Client
To check successful installation, start Administration Client and add your servers.
You have to add the following server nodes:
• A server node for Archive Center
• A server node for Enterprise Library Services
To add your servers:
1. In the Start menu, click OpenText > Administration Client.
2. To create the server node for Archive Center, in the Actions pane, click Add
Server.
3. Enter the name of the server where Archive Center is installed.
4. Change the port to 8080 and choose the protocol (for example http).
Oracle Database 123
ERLK160200-00-IWO-EN-01
Chapter 19 Starting the Administration Client
Click OK.
5. To create the server node for Enterprise Library Services, in the Actions pane,
click Add Server.
6. Enter the name of the server where Enterprise Library Services is installed.
7. Change the port to 8080 and choose the protocol (for example http).
124 Oracle Database
ERLK160200-00-IWO-EN-01
Click OK.
8. Select the server created for Archive Center.

Sign in as the default Archive Center administration user dsadmin without a
password.
Important
Make sure to change the password later.
9. Select the server created for Enterprise Library Services. 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 32.
If you can access the servers, the installation so far has been successful.
Oracle Database 125
ERLK160200-00-IWO-EN-01
Chapter 20
Configuring OpenText Directory Services for
Archive Center
Archive Center must be registered as a resource with OpenText Directory Services

(OTDS). After this step, you can use the default OTDS administration user
otadmin@otds.admin to sign in to Archive Center.
New: To configure the resource for Archive Center, you can use the OTDS
connection assistant in the Administration Client.
To create the resource for Archive Center
1. Start Administration Client and sign in to Archive Server with dsadmin.
2. In the console tree, navigate to <server name> > Archive Server.
3. In the action pane, click OTDS connection.

4. On the Connection page, enter the following:
OTDS server URL

Enter the server hosting OTDS as URL: <protocol>://<server>:<port> For
example, https://otds_server:8090
OTDS administrator
Enter the name of the OTDS administrator; default: otadmin@otds.admin
OTDS administrator password

Enter the password of the OTDS administrator.
5. On the Resource page, enter a resource name for Archive Center. The resource
name must be unique.
6. On the Summary page, verify your entries and click Finish. The resource is
created.
7. Restart Archive Center to activate the new resource.
For more information, see section 9.9 “Connecting to Directory Services” in OpenText
Archive Center - Administration Guide (AR-ACN).
Oracle Database 127
ERLK160200-00-IWO-EN-01
Chapter 21
Configuring Archive Center
The following procedures are required to configure Archive Center 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, we recommend consulting with Professional Services
to appropriately design an Archive Center implementation that properly utilizes the
storage devices listed in the Archive Center Storage Platforms Release Notes – for
implementations with a large volume of documents, using a disk volume of type
HDSK (lots of discrete files) can significantly increase operational backup and
restore times.
21.1 Creating the connection from Archive Center to

Content Server
To secure integrated archiving and records management scenarios, you must
configure the connection to Content Server inside Archive Center.
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 Center.
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.
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
Oracle Database 129
ERLK160200-00-IWO-EN-01
Chapter 21 Configuring Archive Center
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
Directory Services Administration: Resources > <resource> > Actions >
Activation Status.
Whenever you change the value of the property later you must restart
the Apache Tomcat and services for the change to take effect.
2. Allow the Archive Server resource to impersonate users of the Content Server
resource anonymously:
a. Start Directory Services Administration in a web browser. Open http://

<fully_qualified_domain_name_of_server>:<port_number/otds-
admin/ and sign in as otadmin@otds.admin.
b. On the Directory Services Administration menu, click Resources.
c. For the Archive Center resource, click Actions > Impersonation settings.
d. Select the Content Server resource and select Anonymous.
Clear Allow this resource to impersonate its own users, as this is not
necessary, and click OK.
130 Oracle Database
ERLK160200-00-IWO-EN-01
21.2. Creating disk volumes for storage and for disk buffer
21.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.
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.
Oracle Database 131
ERLK160200-00-IWO-EN-01
6. Create another volume with Volume name A1Buffer1 and as Mount path
browse for the folder created in step 1 (C:\A1Buffer1).
As Volume class, select Hard Disk, and then click OK.
21.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.
132 Oracle Database
ERLK160200-00-IWO-EN-01
21.4. Creating a logical archive
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.
21.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.
Oracle Database 133
ERLK160200-00-IWO-EN-01
2. In the Archive name box, enter A1.
Caution
SAP accepts archive names with maximum two characters only.
3. Click Next. A summary dialog shows your entries.
4. Click Finish. The original archive is created.
134 Oracle Database
ERLK160200-00-IWO-EN-01
21.5. Creating a pool
21.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.
Oracle Database 135
ERLK160200-00-IWO-EN-01
3. Click Next.
4. Apply the default settings and click Finish.
136 Oracle Database
ERLK160200-00-IWO-EN-01
21.5. Creating a pool
Oracle Database 137
ERLK160200-00-IWO-EN-01
21.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.
138 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 22
Configuring the storage provider
The storage provider configuration connects the logical archives of Archive Center
with Content Server. Create a storage provider configuration for each logical
archive.
To configure the storage provider:

func=admin.index
Log in as Administrator.
2. In the Archive Storage Provider Administration section, click Configure

Archive Storage Provider.
Log in as Administrator.
3. In the Archive Server field, enter the name of the Archive Center host.
4. Click Save Changes. Archive Storage Provider uploads its certificate to Archive
Center automatically.
5. Click OK.
Oracle Database 139
ERLK160200-00-IWO-EN-01
Chapter 23
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:

func=admin.index
If asked, log in as Administrator.
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 (A1).
As Storage Tier, you can only keep the default (none).
Select Delete Documents from Archive and Allow Content Move Operation.
Oracle Database 141
ERLK160200-00-IWO-EN-01
Chapter 23 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.
142 Oracle Database
ERLK160200-00-IWO-EN-01
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.
Oracle Database 143
ERLK160200-00-IWO-EN-01
Chapter 24
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.
Oracle Database 145
ERLK160200-00-IWO-EN-01
Chapter 24 Enabling certificates
This node additionally offers many more options to work with certificates, like
viewing them or changing their privileges, or importing certificates.
146 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 25
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.
Note: The application name must be identical to the respective SAP

system ID.
3. In the Password and Confirm password boxes, enter a password.

Select Active and Delete Notifications 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.
Oracle Database 147
ERLK160200-00-IWO-EN-01
Chapter 25 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.
148 Oracle Database
ERLK160200-00-IWO-EN-01
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 section 6.10 “SAP: Creating an document declaration” in
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
Oracle Database 149
ERLK160200-00-IWO-EN-01
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 My Support):
• 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)
Oracle Database 153
ERLK160200-00-IWO-EN-01
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 OpenText My Support):
• 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)
• OpenText SAP OData Services package (optional)
• OpenText SAP Fiori UI package (optional)
Oracle Database 155
ERLK160200-00-IWO-EN-01
Chapter 27 Checking prerequisites
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
27.4 SAP prerequisites

Check the following prerequisites prior to installation:
SAP support packages

Check the latest version of the Release Notes in OpenText My Support 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
156 Oracle Database
ERLK160200-00-IWO-EN-01
27.5. Installation tool
• 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, for example, additional
icons in the GOS attachment list based on the SAP enhancement technology.
• Patch level for SAP CRM 7.0 - The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 701 BBPCRM minimum
release 700.
• Patch level to install optional OData package - This package can be
installed on SAP backend systems either with Backend Event Provider
(IW_BEP release 200, patch level 10) or with SAP Gateway Foundation
(SAP_GWFND, at least release 740, patch level 09). On systems with
SAP_GWFND release 750, like S/4 HANA, use SPAM/SAINT level 0059 or
newer for installation. Though not required for installation, at runtime the
OData services of Archiving and Document Access for SAP Solutions call
RFC functions of the basis add-on (OTEXBAS) of Archiving and Document
Access for SAP Solutions 16.
• Patch level to install optional Fiori UI package - This package can be
installed on SAP frontend systems with User Interface Technology (SAP_UI
release 740, patch level 13. On systems with SAP_UI release 750, like S/4
HANA, use SPAM/SAINT level 0059 or newer for installation). Though not
required for installation, at runtime the Fiori app calls the OData services of
Archiving and Document Access for SAP Solutions.
Note: The documentation is updated regularly; therefore, check for the latest
version in OpenText My Support.
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 ISO image or ZIP archive, 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. For example,
INST_BAS_700/DATA/OTEXBAS_INST_1620_700.SAR contains the archived PAT file
to install the package for SAP basis release 7.00 or higher.
Oracle Database 157
ERLK160200-00-IWO-EN-01
Chapter 27 Checking prerequisites
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 Installation packages and passwords

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.
Installation packages and the corresponding passwords are listed in “Installation
packages and passwords” on page 158.
Table 27-1: Installation packages and passwords
Package Designation Release Password

OTEXBAS Archiving and 1620_700 9396C555B8
Document Access for
SAP Solutions for
Basis Component
16.2
OTEXBASO Archiving and 1620_700 9396C555D7
Document Access for
SAP Solutions OData
Services Component
16.2
OTEXBASF Archiving and 1620_740 9096C555DE
Document Access for
SAP Solutions Fiori
UI Component 16.2
OTEXERP Archiving and 1620_600 9391D656B8
Document Access for
SAP Solutions ERP
Component 16.2
OTEXCRM Archiving and 1620_700 9597D64BB8
Document Access for
SAP Solutions CRM
Component 16.2
158 Oracle Database
ERLK160200-00-IWO-EN-01
27.7. Web Dynpro configuration
SAP Note 567695
SAP requires having a SAP Note number that contains information regarding
the installation and upgrade of OpenText software. Depending on the number
is an installation password which is needed for installation and delta upgrades.
Refer to SAP Note 567695, which is the general note related to Add-ons for
Software Partners.
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 section
25.1.1.1 “Technical prerequisites” in OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS) and section 25.1.4.2 “Configuring Web Dynpro
search application” in OpenText Archiving and Document Access for SAP Solutions -
Scenario Guide (ER-CCS).
Oracle Database 159
ERLK160200-00-IWO-EN-01
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 155 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 section 27 “OpenText License Report” in
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_1620_700. INST_BAS_700\DATA\ /usr/sap/trans
SAR
Oracle Database 161
ERLK160200-00-IWO-EN-01
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“Installation packages and passwords”
on page 158.
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_ALL1600
• /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 SPRO transaction. In IMG, go to OpenText Archiving and

Document Access for SAP Solutions > DocuLink Administration >
Customizing Maintenance and Upgrade > Create DocuLink Project
$GARMISCH.
162 Oracle Database
ERLK160200-00-IWO-EN-01
28.1. Installing package
2. The start screen of the /IXOS/DC_A_CREATE_GARMISCH report is displayed.

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 section 7.3.1 “Standard functions in the tab view” in OpenText
DocuLink for SAP Solutions - Customizing and Administration Guide (DC-CGD) and
section 8.2 “The versions” in 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.
Oracle Database 163
ERLK160200-00-IWO-EN-01
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 section 3.4.3 “Authorizations” in OpenText Archiving and Document Access for
SAP Solutions - Installation and Upgrade Guide (ER-IGD) for details
• DesktopLink
see section 3.5.2 “Authorizations” in OpenText Archiving and Document Access for
SAP Solutions - Installation and Upgrade Guide (ER-IGD) for details
• DocuLink
164 Oracle Database
ERLK160200-00-IWO-EN-01
28.2. Configuring components
see “Authorizations” on page 166 for details
Tip: For an overview of authorization maintenance, see section 6.3

“Authorizations in SAP applications” in 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 164.
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
section 2.6 “Sample projects overview” in 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.
Oracle Database 165
ERLK160200-00-IWO-EN-01
28.3 Authorizations
Authorization profiles have to be assigned to users who are working with Forms
Management (see section 18.2 “Rights for OpenText Forms Management” in
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 155 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 section 24 “Authorizations” in 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!
166 Oracle Database
ERLK160200-00-IWO-EN-01
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.
Oracle Database 167
ERLK160200-00-IWO-EN-01
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.
168 Oracle Database
ERLK160200-00-IWO-EN-01
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 specific code and objects, such as:
• DVS/PLM document nodetype in DocuLink – SAP GUI and SAP GUI for HTML
• Code to support optional DocuLink example projects – provided as download in
My Support
• DesktopLink support of PLM/DVS – transactions /IXOS/PLM, /IXOS/PLM_DL, /
IXOS/PLM_IMPORT, IXOS/PLM_SCAN
• ERP-specific example BOR objects
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_1620_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).
Oracle Database 169
ERLK160200-00-IWO-EN-01
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 to enable the DocuLink CRM example
project, which can be downloaded from My Support. The CIC integration is
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_CRM_1620_700. INST_CRM_700\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).
Oracle Database 171
ERLK160200-00-IWO-EN-01
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 OpenText My Support (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 OpenText My Support, 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.
Oracle Database 173
ERLK160200-00-IWO-EN-01
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
Localization of Fiori apps

Starting with version 16.2, the Fiori apps contained in the Fiori UI Add-on package
OTEXBASF deliver i18n properties files, which are mapped to text tables on the
174 Oracle Database
ERLK160200-00-IWO-EN-01
SAP system. Therefore specific language packages for Add-On package OTEXBASF
will be made available in OpenText My Support. The installation procedure is the
same as already described above.
Oracle Database 175
ERLK160200-00-IWO-EN-01
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 section 20.1.1.1 “Communication

protocols in SAP applications” in 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
Oracle Database 177
ERLK160200-00-IWO-EN-01
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
178 Oracle Database
ERLK160200-00-IWO-EN-01
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. In the IMG, run the OpenText Archiving and Document Access for SAP
Solutions > DesktopLink and Archiving for SAP Solutions > ArchiveLink >
Front End Communication Customizing > Maintain Applications activity.
Alternatively, you can run 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.
Oracle Database 179
ERLK160200-00-IWO-EN-01
All functions for the selected ArchiveLink application are listed.
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.
180 Oracle Database
ERLK160200-00-IWO-EN-01
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
Oracle Database 181
ERLK160200-00-IWO-EN-01
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
182 Oracle Database
ERLK160200-00-IWO-EN-01

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
Oracle Database 183
ERLK160200-00-IWO-EN-01

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.
184 Oracle Database
ERLK160200-00-IWO-EN-01
Part 6
Setting up Extended ECM 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™ Content Server, OpenText™ Archive Center,
Records Management, User Management, and OpenText™ Directory Services.
• Basic knowledge of the employed operating system.
33.2 Prerequisites
33.2.1 SAP prerequisites
Extended ECM for SAP Solutions supports the following SAP products:
• SAP S/4 HANA
• SAP ERP 6.0
• SAP CRM 7.0
Note: Content Server integration widget 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 Extended ECM
for SAP Solutions 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 on OpenText My Support for
required support packages for the employed SAP system prior to installation!
Oracle Database 187
ERLK160200-00-IWO-EN-01
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
The following SAP notes must be applied:
SAP Note Required for

110910 Some language-dependent texts may not be displayed
correctly in the GUI.
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.
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)
2238264 (SAP S/4 HANA) Several outbound web service proxies should be triggered.
In that process a program termination of type
STYLESHEET_GENERATION_FAILURE is raised.
1424747 Enables the transmission of SOAP error codes to identify
problems.
1267258 Unexpected error message No vendor specified when log-
on language is English.
822380 Required to avoid known problems with the SAP Add-On
(SAP 7.00) Installation Tool (SAINT).
Installation information -
OSS note 1040369
212876
(SAPCAR tool)
188 Oracle Database
ERLK160200-00-IWO-EN-01
33.2. Prerequisites
SAP Note Required for

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 integration widget 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.
• Patch level for optional Fiori UI package: At runtime the Fiori apps require
SAPUI5 1.38.9, which is based on User Interface Technology SAP_UI release
750. At installation time this package can be installed on SAP frontend
systems with User Interface Technology (SAP_UI release 740, patch level 13
or higher). The Fiori Add-On package of OpenText Archiving and Document
Access for SAP Solutions, OTEXBASF 1620_740 is required. Though not
required for installation, at runtime the Fiori app calls the OData services of
Extended ECM for SAP Solutions.
• Patch level for optional OData package: This package can be installed on
SAP backend systems either with Backend Event Provider (IW_BEP release
200, patch level 10) or with SAP Gateway Foundation (SAP_GWFND, at least
release 740, patch level 09). On systems with SAP_GWFND release 750, like
S/4 HANA, use SPAM/SAINT level 0059 or newer for installation. Though
not required for installation, at runtime the OData services of Extended ECM
for SAP Solutions call RFC functions of the basis add-on of Extended ECM
for SAP Solutions (OTEXRL) 16.2.
Note: The documentation and the release notes are updated regularly;
therefore, check for the latest version on OpenText My Support (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 Extended ECM for SAP
Solutions you must install the SAP Add-On OTEXBAS of Archiving and
Oracle Database 189
ERLK160200-00-IWO-EN-01
Document Access for SAP Solutions 16. For more information, see section 3
“Installing Basis package” in OpenText Archiving and Document Access for SAP
Solutions - Installation and Upgrade Guide (ER-IGD).
33.2.2 Content Server prerequisites

Check the following prerequisites prior to the installation of SAP Add-On package
OTEXRL:
Important
See the Release Notes for a comprehensive and most current list of
prerequisites.
Required patches for the installed Content Server version

Content Server 16.2 - 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 16.2. 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 119.
Note: If you create a completely new system, Content Server 16.2 is

installed by the master setup.
Important
Prior to installation, make sure that you have read the information in
OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and
OpenText Enterprise Library - Scenario and Configuration Guide (EL-GGD)
for the relevant version.
Installation of Enterprise Library Services and Archive Center Services

Both services must be installed. Archive Center Services is part of Archive
Center. Install Enterprise Library Services 16.2 and Archive Center 16.2.
Additionally, install the patches provided on the Extended ECM for SAP
Solutions installation medium.
Important
Extended ECM for SAP Solutions is not compatible with the Enterprise
Library Interview module which is an optional Case Management
module. Do not install this module in combination with Extended ECM
for SAP Solutions.
ArchiveLink customizing
Customizing of the SAP system and the Archive and Storage Services must be
completed according to part II “SAP basis customizing” in OpenText Archiving
and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
190 Oracle Database
ERLK160200-00-IWO-EN-01
33.3. SAP Add-On Installation Tool (SAINT)
Host/port for the logical archive

Check that store and retrieval of ArchiveLink documents functions properly
with the server.
Important
With the newest Archive Center version, the logical archive (OAC0
transaction) must use the Archive and Storage Services host/port.
For older versions, it must use the Enterprise Library Services 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 the following ports
must be enabled:
• 8080 HTTP or 8090 HTTPS on Apache Webserver: used for the Web service
communication from SAP to Content Server.
• 8000: Used for the communication between Content Server and the SAP
Client.
• 80 (HTTP) or 443 (HTTP): Only required for connection tests from SAP to
Content Server.
33.3 SAP Add-On Installation Tool (SAINT)

Extended ECM for SAP Solutions uses the SAP Add-On Installation Tool (SAINT)
for installation of the SAP part of Extended ECM for SAP Solutions. 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 Extended ECM for SAP Solutions is protected with a specific
password. During installation, this password is requested by SAINT.
For details, see the following table:
Table 33-1: Installation packages and passwords
Package Release Designation Password

OTEXRL 1620_700 Extended ECM for SAP 9386C726B8
Solutions
Oracle Database 191
ERLK160200-00-IWO-EN-01
Package Release Designation Password

OTEXRLC 1620_700 Extended ECM for SAP 9586C745B8
Solutions SAP CRM Add-On
OTEXRLS 1620_700 Extended ECM for SAP 9386C755B8
Solutions SAP SRM Add-On
OTEXRLO 1620_700 Extended ECM for SAP 9386C749B8
Solutions SAP OData Services
Add-on
OTEXRLF 1620_740 Extended ECM for SAP 9086C740B8
Solutions SAP Fiori Apps 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 Extended ECM

for SAP Solutions 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 16. You find detailed information
also in the Content Server system report. For more information, see section 20.2
“Understanding the Content Server System Report” in OpenText Extended ECM
for SAP Solutions - Customizing Guide (ERLK-CGD).
• Connected Workspaces 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
16.0.0 .
• Web Services and other OpenText components
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 Extended ECM for SAP Solutions
> Extended ECM > 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, OTEXRLS, OTEXBASO,
OTEXBASF, OTEXRLO, and OTEXRLF. For more information, see section 20.1.3
192 Oracle Database
ERLK160200-00-IWO-EN-01
33.4. Finding version information for Extended ECM for SAP Solutions relevant system
components
“Understanding the Configuration Report” in OpenText Extended ECM for SAP

Solutions - Customizing Guide (ERLK-CGD).
• 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, OTEXRLS, OTEXBASO,
OTEXBASF, OTEXRLO, and OTEXRLF you could use this instead of the
configuration report.
• SAP Fiori apps
For each application, there is a static version.html that includes the version
number. To retrieve the file, enter the following in a browser:
http(s)://<SAP hostname>:<SAP port>/sap/bc/ui5_ui5/otx/<subpath

of fiori app>/version.html
Oracle Database 193
ERLK160200-00-IWO-EN-01
Chapter 34
Installing the SAP package
The following describes the installation of the OTEXRL component of Extended ECM
for SAP Solutions and the optional components OTEXRLC, OTEXTRLS, OTEXRLO, and
OTEXRLF on an SAP application server.
Prerequisites The component OTEXBAS of Archiving and Document Access for SAP Solutions must
be installed on your SAP system. If you want to integrate into SAP Fiori, also the
component OTEXBASF of Archiving and Document Access for SAP Solutions must be
installed on your SAP system. Check the Release Notes for required versions of
these components.
See also “SAP prerequisites” on page 187 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
Extended ECM\SAP to the target SAP application server in the /usr/sap/trans
folder, which is the parent folder of the DIR_EPS_ROOT folder.
SAP Release File Source path Target path

SAP BASIS 700 OTEXRL_INST_1620_ INST_BAS_700\DAT /usr/sap/trans
700.SAR A\
SAP CRM 7.0 OTEXRLC_INST_162 INST_CRM_700\DA /usr/sap/trans
0_700.SAR TA\
SAP SRM 7.0 OTEXRLS_INST_1620 INST_SRM_700\DA /usr/sap/trans
_700.SAR TA\
IW_BEP release 200 OTEXRLO_INST_162 INST_ODATA_700\ /usr/sap/trans
or SAP_GWFND 0_700.SAR DATA
740/750
SAP_UI 740/750 OTEXRLF_INST_1620 INST_FIORI_740\D /usr/sap/trans
_740.SAR ATA
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.
Oracle Database 195
ERLK160200-00-IWO-EN-01
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 191.
After the installation, you must activate a Business Configuration Set (BC set) for
every client.
To activate the BC set:
1. Start the SCPR20 transaction.

The Business Configuration Set screen appears.
2. Activate the following BC Set:
• /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.
196 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 35
Installing language packages in the SAP system
This chapter describes how to install language packages in an SAP system.
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 Extended ECM for SAP Solutions Release
Notes. You can find the language packages related to the SAP Add-Ons of Extended
ECM for SAP Solutions on OpenText My Support (https://knowledge.opentext.com/
knowledge/cs.dll?func=ll&objId=8521552&objAction=browse).
To install a language package:
1. On OpenText My Support, 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.
• 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.
Oracle Database 197
ERLK160200-00-IWO-EN-01
Chapter 35 Installing language packages in the SAP system
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
Note: Localization of Fiori apps
Starting with version 16.2 the Fiori apps contained in the Fiori UI Add-on
packages OTEXBASF and OTEXRLF deliver i18n properties files, which are
mapped to text tables on the SAP system. Therefore specific language packages
for Add-On packages OTEXBASF and OTEXRLF will be available in OpenText
My Support. The procedure of installation is the same as described above.
198 Oracle Database
ERLK160200-00-IWO-EN-01
Chapter 36
Performing general post-installation tasks in SAP
Before using the Extended ECM for SAP Solutions 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 205
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 Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
36.1 Using the IMG function

Extended ECM for SAP Solutions provides a central customizing menu in SAP in the
OpenText Extended ECM 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 Extended ECM for SAP Solutions structure and
open it.
Oracle Database 199
ERLK160200-00-IWO-EN-01
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 for SAP Solutions customizing is not visible. You have the
following options to access the Extended ECM for SAP Solutions customizing
structure:
• Use transaction SIMGH, save the Extended ECM for SAP Solutions IMG structure
as a favorite and call it from there.
• Add the Extended ECM for SAP Solutions customizing to the existing
customizing structure of transaction SPRO.
To use transaction SIMGH to access Extended ECM for SAP Solutions

customizing:
1. Run the SIMGH transaction.

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.
200 Oracle Database
ERLK160200-00-IWO-EN-01
36.1. Using the IMG function
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 Extended ECM for SAP Solutions:
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 customizing, for example OpenText Extended
ECM for SAP Solutions.
i. Click Find structure to search for the Extended ECM for SAP Solutions
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:
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
Oracle Database 201
ERLK160200-00-IWO-EN-01
Chapter 36 Performing general post-installation tasks in SAP
36.2 Assigning SAP roles

In order to use the Extended ECM for SAP Solutions functions in SAP, you must
assign specific roles in SAP. The following roles are required:
Notes
• If you do not want to use these roles, you must assign the respective
authorization objects to your own roles.
• If you want to use field values other than those recommend here, field help
provides additional information.
/OTX/RM_USER
Role for Extended ECM for SAP Solutions 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 and drop.
/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.
202 Oracle Database
ERLK160200-00-IWO-EN-01
36.2. Assigning SAP roles
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 an
external system” on page 236.
/OTX/RM_IMPERSONATED_USER_ROLE
Role for the SAP user which is used in the RFC destination. For more
information, see section 6.7.1 “Enabling user-specific impersonation (SAP
BAdI)” in OpenText Extended ECM for SAP Solutions - User Management and
Access Control Scenarios (ERLK-CUM).
Oracle Database 203
ERLK160200-00-IWO-EN-01
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.
Oracle Database 205
ERLK160200-00-IWO-EN-01
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 Directory
Services server.
206 Oracle Database
ERLK160200-00-IWO-EN-01
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 Directory Services

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 using the Directory Services Administration web client.
Note: For a detailed description of authentication handlers, see section 5.2

“Creating an authentication handler” in OpenText Directory Services - Installation
and Administration Guide (OTDS-IWC).
To create an SAP authentication handler:

2. On the Directory Services Administration menu, click Authentication
Handlers.
3. Click Add.
4. In the New Authentication Handler assistant, 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
Oracle Database 207
ERLK160200-00-IWO-EN-01
SRM 7.0
certificates if necessary. The Description field is automatically filled with

the path to the certificate; you can change the text.
• 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 (ERLK-CUM), in the Map all SAP 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:
• Select Enable authentication handler.

• Set Priority to 1. This setting defines that this authentication handler is
used first before the other authentication handlers.
• From the list box, 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.
Click Add to add the attribute to the Authentication principal attribute
list.
5. Click Save.
37.2 Activating the SSO HTTP service

You must activate the 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 Content Server.
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.
To activate the HTTP service:
1. In IMG, navigate to the OpenText Extended ECM for SAP Solutions >
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.
208 Oracle Database
ERLK160200-00-IWO-EN-01
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

Extended ECM for SAP Solutions 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

Extended ECM for SAP Solutions connects to OpenText components using HTTP
connections and logical ports.
You must create the following HTTP connections to the required web services:
• Enterprise Library
• Extended ECM
• OpenText Directory Services
• Enterprise Library Content Services
Oracle Database 209
ERLK160200-00-IWO-EN-01
SRM 7.0
• Content Server Member Services
To create the HTTP connections:
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 Services
installation
210 Oracle Database
ERLK160200-00-IWO-EN-01
Service No.: Enterprise Library Web Services port; port 8080 is typically
used for Apache Tomcat.
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 212.
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. Repeat steps 2 to 7 and create more HTTP connections according to the

following table:
Enterprise Extended ECM OpenText Enterprise

Library Directory Library
Services Services Content
Services
RFC Enter a name Enter a name, Enter a name, Enter a name,
Destination for this for example for example for example
connection, for EXTECM_DEST. OTDS_DEST. ELCONTENT_D
example EST.
ELS_DEST_CO
RE.
Connections G (HTTP G (HTTP G (HTTP G (HTTP
Type Connection to Connection to Connection to Connection to
External Server) External Server) External Server) External Server)
Technical Settings tab
Oracle Database 211
ERLK160200-00-IWO-EN-01
SRM 7.0
Enterprise Extended ECM OpenText Enterprise

Library Directory Library
Services Services Content
Services
Target host Fully qualified Host name of Target host: Host name of
host name of your Extended Host name of the Enterprise
your Enterprise ECM your Directory Library Services
Library Services installation Services installation.
installation (OTDS)
installation.
If you are using
user-specific
mapping with
impersonation
(SAP BAdI) and
OpenText
Directory
Services and
Enterprise
Library Services
and Content
Server are
installed on
different
servers, enter
the host name
of the
Enterprise
Library Services
installation.
Service No. Enterprise Extended ECM Directory Enterprise
Library Web Web Services Services Web Library Content
Services port; port Services port Services port
port 8080 is
typically used
for Apache
Tomcat.
Path Prefix /ot-elib/ /otsapxecm/ /ot-authws/ /ot-elib/
services/ services/ services/ services/
EnterpriseL ECMLink Authenticat Content
ibrary ion
The following settings are the same for all ports:
• On the Logon & Security tab, select No Logon and Send SAP Logon Ticket.
• On the Messaging tab, in the Message ID Protocol field, select the Suppress
ID Transfer value.
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:
212 Oracle Database
ERLK160200-00-IWO-EN-01
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
• Extended ECM logical port
• OpenText Directory Services logical port
• Enterprise Library Content Services logical port
To create a logical port for SAP Basis 7.0:
Infrastructure > Create New Logical Ports activity and click Execute.
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.
Oracle Database 213
ERLK160200-00-IWO-EN-01
SRM 7.0
4. Select the Default Port check box. Select it for your main Content Server if you
have more than one.
5. Click Create.
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. Extended ECM
Repeat steps 2 to 8 to create a logical port for Extended ECM 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
214 Oracle Database
ERLK160200-00-IWO-EN-01
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.
• 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
Oracle Database 215
ERLK160200-00-IWO-EN-01
SRM 7.0
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.

Extended ECM for SAP Solutions connects to OpenText components using logical
ports.
You must create a corresponding logical port for each connection:

• Extended ECM
To create a logical port for SAP Basis 7.01 and higher:
1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
The SOA Management dialog opens.
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.
216 Oracle Database
ERLK160200-00-IWO-EN-01
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 Services. If you have multiple logical ports for Enterprise Library
Services, 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.
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 Services 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.
Oracle Database 217
ERLK160200-00-IWO-EN-01
SRM 7.0
11. Create the other logical ports according to the following table. If not indicated
otherwise, use the settings as described for the Enterprise Library port.
Enterprise Extended Authenticati Enterprise Content

Library ECM on Library Server
Content Member
Services Service
Internal /OTX/ /OTX/ /OTX/ /OTX/ /OTX/
name CO_RMELEN CO_RM_WSW CO_OTDSAU CO_RMELCO CO_MBLLME
TERPRISE_ _ECMLINK THENTICAT NTENT MBER_SERV
LIBRARY ION ICE
URL Access /ot-elib/ / /ot- /ot-elib/ /cws/
Path services/ otsapxecm authws/ services/ services/
Enterpris / services/ Content MemberSer
eLibrary services/ Authentic vice
ECMLink ation
218 Oracle Database
ERLK160200-00-IWO-EN-01
Enterprise Extended Authenticati Enterprise Content

Library ECM on Library Server
Content Member
Services Service
Computer Enterprise Host name Computer Host name Host name
Name Library of your Name of of your of your
Access URL Services Extended Access URL Enterprise Content
installation ECM on the Library Server
host name installation Transport Content Member
settings tab: Services Service
Host name installation. installation.
of your
Directory
Services
installation.
If you are
using user-
specific
mapping
with
impersonati
on (SAP
BAdI) and
OpenText
Directory
Services and
Enterprise
Library
Services and
Content
Server are
installed on
different
servers,
enter the
host name of
the
Enterprise
Library
Services
installation.
• On the Consumer Security tab, select SAP Authentication Assertion Ticket.

• On the Messaging tab, in the Message ID Protocol field, select the Suppress
ID Transfer value.
Oracle Database 219
ERLK160200-00-IWO-EN-01
SRM 7.0

ports.
• Extended ECM
2. In SOA Management, 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 this is the only logical port for Enterprise
Library Services or if this is the preferred port of several logical ports for
Enterprise Library Services. Click Next.
220 Oracle Database
ERLK160200-00-IWO-EN-01
7. In the Consumer Security step, select SAP Authentication Assertion Ticket.

Click Next.
8. In the HTTP Settings step, configure at least the following:

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.
Oracle Database 221
ERLK160200-00-IWO-EN-01
SRM 7.0
Click Finish.
The new logical port is saved and activated.
11. Repeat Step 4 to Step 10 to create a logical ports according the following table:
Extended ECM Authentication Enterprise Content Server

Library Member
Content Service
Services (MemberServic
(Content) e)
Internal name /OTX/ /OTX/ /OTX/ /OTX/
CO_RM_WSW_ CO_OTDSAUT CO_RMELCON CO_MBLLME
ECMLINK HENTICATIO TENT MBER_SERVIC
N E
URL Access /otsapxecm/ /ot-authws/ /ot-elib/ /cws/services/
Path services/ services/ services/ MemberService
ECMLink Authentication Content
222 Oracle Database
ERLK160200-00-IWO-EN-01

Library Member
Content Service
(Content) e)
Computer Host name of Host name of Host name of Host name of
Name of your Extended your Directory your Enterprise your Content
Access URL ECM Services Library Content Server Member
installation installation. If Services Service
you are using installation installation
user-specific
mapping with
impersonation
(SAP BAdI),
and OpenText
Directory
Services,
Enterprise
Library Services
and Content
Server are
installed on
different
servers, enter
the host name
of the
Enterprise
Library Services
installation.
Port Number of Extended ECM Directory Enterprise Content Server
Access URL Web Services Services Web Library Content Member Service
port, usually Services port , Services port, port, usually
8080 for Tomcat usually 8080 usually 8080 for 8080 for Tomcat
for Tomcat Tomcat
• Consumer Security: SAP Authentication Assertion Ticket

• Message ID Protocol: Suppress ID Transfer
Oracle Database 223
ERLK160200-00-IWO-EN-01
SRM 7.0

ports.

• Extended ECM
2. In SOA Management, 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).
224 Oracle Database
ERLK160200-00-IWO-EN-01
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 this is the only logical port for Enterprise
Library Services or if this is the preferred port of several logical ports for
Enterprise Library Services. Click Next.
7. In the Consumer Security step, select SAP Authentication Assertion Ticket.

Click Next.
8. In the HTTP Settings step, configure at least the following:

8080 for Tomcat)
Click Next.
9. In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID
Transfer
Click Next.
10. Click Finish.

The new logical port is saved and activated.
11. Repeat Step 4 to Step 10 to create a logical ports according the following table:

Library Member
Content Service
(Content) e)
Internal name /OTX/ /OTX/ /OTX/ /OTX/
CO_RM_WSW_ CO_OTDSAUT CO_RMELCON CO_MBLLME
ECMLINK HENTICATIO TENT MBER_SERVIC
N E
URL Access /otsapxecm/ /ot-authws/ /ot-elib/ /cws/services/
Path services/ services/ services/ MemberService
ECMLink Authentication Content
Oracle Database 225
ERLK160200-00-IWO-EN-01
SRM 7.0

Library Member
Content Service
(Content) e)
Computer Host name of Host name of Host name of Host name of
Name of your Extended your Directory your Enterprise your Content
Access URL ECM Services Library Content Server Member
installation installation. If Services Service
you are using installation installation
user-specific
mapping with
impersonation
(SAP BAdI),
and OpenText
Directory
Services,
Enterprise
Library Services
and Content
Server are
installed on
different
servers, enter
the host name
of the
Enterprise
Library Services
installation.
Port Number of Extended ECM Directory Enterprise Content Server
Access URL Web Services Services Web Library Content Member Service
port, usually Services port , Services port, port, usually
8080 for Tomcat usually 8080 usually 8080 for 8080 for Tomcat
for Tomcat Tomcat
• Consumer Security: SAP Authentication Assertion Ticket

• Message ID Protocol: Suppress ID Transfer
226 Oracle Database
ERLK160200-00-IWO-EN-01
37.4. Configuring the Service Provider Interface service
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 an external system”
on page 236.
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.
• 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:
Oracle Database 227
ERLK160200-00-IWO-EN-01
SRM 7.0
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 19.1 “Importing root
certificates for Secure Sockets Layer (SSL) connections” in OpenText
Extended ECM 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.
37.5 Maintaining Extended ECM connections

All parameters for a connection to OpenText servers are collected with an
connection ID. For an installation, you have to create a new connection ID.
To maintain connection settings in:
1. Navigate to the Infrastructure > Maintain Extended ECM Connections activity

and click Execute.
2. Click New Entries.
228 Oracle Database
ERLK160200-00-IWO-EN-01
37.5. Maintaining Extended ECM connections
3. Enter the following parameters:
Connection ID
Enter a connection ID.
Extended ECM Connections
• Description: Enter a description for the connection.
Oracle Database 229
ERLK160200-00-IWO-EN-01
SRM 7.0
• EL Appl. Password: Enter the Enterprise Library application password;

this application password has been defined in section 19.5.1 “Creating
an Enterprise Library application” in OpenText Extended ECM for SAP
Solutions - Installation and Upgrade Guide (ERLK-IGD).
Logical Ports for Web Services

Enter the names of the logical ports for the Enterprise Library, the OpenText
Directory, Extended ECM, 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 209.
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.
RFC Impersonation uses a web service for SSO: if you want to restrict
this web service to redirect to a certain Content Server, you can maintain
a whitelist. For more information, see “Improving data security for
impersonation connections” on page 232.
• For more information about implementation, see the Extended ECM for
SAP Solutions SDK on OpenText My Support.
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 (ERLK-CUM).
OpenText Content Server
• Protocol, Hostname, Port, and Path: These URL parameters define how
to display the Content Server Web UI. Enter the parameters for your
Content Server.
If you are using a Remote Cache Server, enter the hostname of the
primary Content Server. For Remote Cache, the IP range must be
configured, which will then redirect the HTTP request to the configured
Remote Cache Server.
230 Oracle Database
ERLK160200-00-IWO-EN-01
37.5. Maintaining Extended ECM connections
Important
You must enter the full Content Server path including the
domain name.
Example:
• Protocol: http
• Hostname: myhost.example.net
• Port: 2099
• Path: OTCS/cs.exe
Note: If this path has Integrated Windows Authentication (IWA)

enabled, there are limitations for the following features: thumbnail
view in the Business Content Window, license measurement, Content
Server search from SAP, UI Widget integration. These functions ask for
authentication if Integrated Windows Authentication is exclusively
enabled as authentication method. Workarounds are:
• Thumbnail preview: Disable the preview in IMG at Extended ECM >
Business Content Window > Business Content Window Settings.
Create a new entry with WSP_THUMBNAIL_OFF as setting name and
TRUE as value.
• License Report and search: Use a new RFC destination with a
mapping to Content Server without IWA .
• UI Widget integration: Use the native Business Content Window UI.
Alternative authentication configurations are:

• Enable the OTDS SSO authentication and disable the IIS IWA
configuration. (Recommended)
• If you need IIS IWA for all others users except SAP users, and there
is no way to use OTDS SSO, you can create a second mapping in IIS
that does not have IIS IWA, and configure that in the Extended ECM
connection settings.
• 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 7 “Using the Content Server Integration
Widget” in OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-CGD).
• External System ID: Enter the name defined when configuring the
external connection on Content Server for this SAP system.
• Logical Destination: This entry is needed for enabling the Content
Server full text search in the SAP system. Enter an existing logical
destination defined in the SM59 transaction that contains the connection
to the Content Server that is relevant for your search. transaction For
more information, see section 25.1.2 “Customizing search templates” in
OpenText Archiving and Document Access for SAP Solutions - Scenario Guide
(ER-CCS).
Oracle Database 231
ERLK160200-00-IWO-EN-01
SRM 7.0
• 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.
RFC Impersonation uses a web service for SSO: if you want to restrict this
web service to redirect to a certain Content Server, you can maintain a
whitelist. For more information, see “Improving data security for
impersonation connections” on page 232.
Suppress Sending SAP Logon Ticket
Select this option if you do not want to send the SAP Logon Ticket.
Proxy Settings for OpenText Content Server
The proxy settings define how to display the Content Server Web UI via a
proxy, for example Web Dispatcher.
• Proxy Settings Enabled: Select to enable the following proxy settings.

• Proxy Protocol, Proxy Hostname, Proxy Port: Enter the settings for the
proxy.
Example:
• Proxy Protocol: http

• Proxy Hostname: myproxy.domain.net
• Proxy Port: 80
4. Click Save.
37.6 Improving data security for impersonation

connections
If you are using impersonation with web-based SSO to call embedded Content
Server windows in SAP GUI, you can explicitly create a list of Content Servers that
are allowed for this kind of connection. This follows the SAP whitelist concept. For
more information, see the SAP Help Portal (http://help.sap.com/saphelp_nw73ehp1/
helpdata/en/ee/984daaa3834eeaa77d5edb822570f6/frameset.htm).
New: For an improved data security, you can now create a whitelist that
contains all Content Server URLs which are allowed to connect to the SAP
system.
To create a whitelist for allowed impersonation connections:
1. Use transaction SM30 to open table /OTX/RM_THTWHITE.

2. Create an entry for each Content Server that is allowed to connect to your SAP
system:
232 Oracle Database
ERLK160200-00-IWO-EN-01
37.7. Importing the Content Server SSL certificate
Use Redirect URL /sap/public/otx_rmuic_sso as Whitelist Entry Type.

Provide the protocol, host name, port and an URL template.
Note: You can use the * wildcard in these fields.
Important
You must add the wildcard at the end of the URL Template to cover all
URLs based on that template.
Example:
• Protocol of URL: HTTP

• Host Name: MYHOST.DOMAIN.NET
• Port: 80*, includes for example, port 8080
• URL Template: /OTCS/CS.EXE*
37.7 Importing the Content Server SSL certificate

To use SSL for the communication between Content Server and the SAP system, you
must import the Content Server SSL certificate into the SAP system.
Prerequisite
• You have configured the web servers for HTTPS.
• You have exported the certificate from Content Server in the Base64 format.
To import the certificate:
1. In the SAP system, start the TRUST transaction.
2. Open the SSL client SSL Client (Anonymous) node.
3. On the Certificate menu, click Import.
4. Enter the file path and select Base64.
5. Click the Add to Certificate List button and save your settings.
6. Repeat the steps for the SSL client SSL Client (Standard) node.
Oracle Database 233
ERLK160200-00-IWO-EN-01
Chapter 38
Performing post-installation or post-upgrade tasks
in Content Server
After the actual installation of the module, you have to perform post-installation
tasks in Content Server.
38.1 Importing root certificates for Secure Sockets

Layer (SSL) connections
To secure communication between Content Server and the external system
connected in “Connecting an external system” on page 236, OpenText strongly
recommends to use the Secure Sockets Layer (SSL) protocol. The keystore for
Extended ECM for SAP Solutions 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
Oracle Database 235
ERLK160200-00-IWO-EN-01
Chapter 38 Performing post-installation or post-upgrade tasks in Content Server
-file c:\temp\mycertificate.cer
-keystore c:\opentext\config\ecmlink-
spi.cacerts
-storepass mypassword
38.2 Connecting an external system

To connect Content Server with an SAP system, you define connection parameters
on Content Server.
To connect an external system:
1. On the Content Server Administration page, click Extended ECM > Configure
Connections to External Systems.
2. Click Add External System.
3. Specify the parameters for your external system according to the list below.
4. Click Add.
Logical External System Name

Define the logical name of the external system. The name must be unique . It
cannot be longer than 32 characters. This name is used when you select the
external system in the business object type configuration.
This name can be, for example, the name of the SAP system.
Note: You cannot change the name later.
Connection Type
Displays the connection type.
Enabled
Select this option to enable the configuration.
Tip: You can disable a configuration, for example, if you created it only for
testing and you do not want it to be used.
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 Endpoint

Specify the URL that will be called to obtain business object information.
236 Oracle Database
ERLK160200-00-IWO-EN-01
38.2. Connecting an external system
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 19.1 “Importing root certificates for
Secure Sockets Layer (SSL) connections” in OpenText Extended ECM 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.
Note: If the external system is an SAP system, in the SAP system assign
the /OTX/RM_CS_SAP_USER role to this user. This user requires permissions
for the SAP authorization object S_RFC.
Password
Specify the password of the defined user.
Test Connection
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.
Note: You can only test the connection after you have configured the SPI
service in the external system accordingly. For more information, see
section 18.4 “Configuring the Service Provider Interface service” in
OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide
(ERLK-IGD).
External System Names

Enter localized names for the external system if required.
Oracle Database 237
ERLK160200-00-IWO-EN-01
Figure 38-1: SAP as an external system
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 (ERLK-CUM).
Create the Content Server users according to your authentication scenario. For
example, for each SAP user working with Extended ECM for SAP Solutions, 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
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.
238 Oracle Database
ERLK160200-00-IWO-EN-01
38.4. Preparing document declaration
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 Extended ECM for SAP Solutions.
For more information, see OpenText Classifications - Resource Guide (LLESCLS-GGD).
38.4.2 Importing folder and item type

Extended ECM for SAP Solutions stores metadata for the declared ArchiveLink
documents in the Enterprise Library volume. On the installation CD in the folder
Extended ECM 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 Services to the Document Model entry and click the Folder
Types tab.
2. In the Actions pane, select the Import Types entry and navigate to the otx.
sap.rm.Folder.xml file provided in the folder ELS_TYPES on your installation
CD. Click the Open button to import the file.
The list of folder types displays the new folder type.
3. Select the new folder type, invoke the Properties dialog and click the
Classification tab.
Oracle Database 239
ERLK160200-00-IWO-EN-01
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
240 Oracle Database
ERLK160200-00-IWO-EN-01
38.4. Preparing document declaration
38.4.3 Setting up the authorization for records

The access rights to the records created by Extended ECM for SAP Solutions
correspond to the access rights used by the Enterprise Library application. For more
information, see “Creating an application“ on page 147. 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.
Oracle Database 241
ERLK160200-00-IWO-EN-01
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

Extended ECM for SAP Solutions 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.
242 Oracle Database
ERLK160200-00-IWO-EN-01
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.9 “Configuring unique names for Content Server
items” in OpenText Extended ECM 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.
Oracle Database 243
ERLK160200-00-IWO-EN-01
Chapter 39
Installing language packs on Content Server
This chapter describes how to install language packs on Content Server. The module
installation packages and module support packages include the default language,
which is English. You must use the language packs to install other languages. For
more information about available languages, see the Release Notes.
Language packages for support packages
If not stated otherwise, the language packs related to support packages are
cumulative. They include merged language texts of the main version and of
previous and current support packages.
The language packs are available on OpenText My Support at the following location:
OpenText My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/
63201449)
containing installation files for components that must not be installed on
Content Server, for example, language installations of Imaging clients and the
SAP language package. For more information, see the installation guides and
release notes for these components.
To install a language pack:
1. Download the language packs from OpenText My Support. You can also obtain
the language packs for support packages and other patches navigating through
the Patches area.
On the ISO image, the relevant files for the language packs are available in the
OpenText Content Server and Modules folder.
2. Unzip the files for the relevant modules in the root Content Server installation
directory.
3. On the Content Server Administration page, go to Languages > Install

Language Packs.
4. On the Install Language Packs page, in the Installable Content Server

Language Packs section, select Install for each language that you want to
install, and then click Install.
For more information about language packs, see Help for this page in the
Content Server help.
5. Restart your servers when prompted.
6. Click Continue.
Oracle Database 245
ERLK160200-00-IWO-EN-01
Chapter 40
Verifying the installation
40.1 Analyzing the SAP system

40.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 Extended ECM connection 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 and the OpenText servers. 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 Extended ECM part contains the infrastructure information in addition to
information about the customizing, like business object declarations, document
declarations, or item types.
This information only displays if you start the activity from OpenText Extended
ECM for SAP Solutions > Extended ECM > Diagnostic Program.
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 248.
Note: You can also run the Diagnostic Program as a background job.
To run the Diagnostic Program manually:
1. If you are only interested in infrastructure information, in the IMG, navigate to

the OpenText Extended ECM for SAP Solutions > Infrastructure > Diagnostic
Program and click Execute.
If you are also interested in the Extended ECM specific information, in the IMG.
navigate to the OpenText Extended ECM for SAP Solutions > Extended ECM
> Diagnostic Program activity.
2. If there is only one Extended ECM connection configured, the diagnosis is
started immediately. If there are more connections configured, perform the
following steps, enter the connection ID.
3. Click Execute.
Oracle Database 247
ERLK160200-00-IWO-EN-01
Chapter 40 Verifying the installation
40.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 connection ID exist? Infrastructure > Maintain Section 18.5 “Maintaining
Extended ECM connections; Extended ECM connections”
Did you select a proxy for double-click one entry. in OpenText Extended ECM for
Content Server? SAP Solutions - Installation
Did you provide the Content and Upgrade Guide (ERLK-
Server host name? IGD)
Is the Content Server host

name fully qualified?
248 Oracle Database
ERLK160200-00-IWO-EN-01
40.1. Analyzing the SAP system

Did you provide the Content
Server port?
Did you provide the path to
Content Server?
Can the SAP system connect
to Content Server through
HTTP?
Can the SAP system connect

to the proxy through HTTP?
Service Communication
Did you provide a port for Infrastructure > Create New Section 18.3 “Creating logical
the Enterprise Library Logical Ports ports in the SAP system” in
Service? OpenText Extended ECM 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 18.3 “Creating logical
destination for the Enterprise Logical Ports ports in the SAP system” in
Library logical port? OpenText Extended ECM for
IGD)
Check the following for the For SAP Basis 7.0: Section 18.3 “Creating logical
Enterprise Library HTTP Infrastructure > Create ports in the SAP system” in
connection: “No Logon” and HTTP Connections > HTTP OpenText Extended ECM for
“Send SAP Logon Ticket” is Connections to External SAP Solutions - Installation
enabled; “HTTP Server; double-click one and Upgrade Guide (ERLK-
compression” is disabled. connection; Logon & IGD)
Security tab and Special
Options tab.
For SAP Basis > 7.0: Section 18.3.2 “Creating
Infrastructure > Create New logical ports for SAP Basis
Logical Ports > SOA 7.01” in OpenText Extended
Management > Application ECM for SAP Solutions -
and Scenario Installation and Upgrade Guide
Communication > Single (ERLK-IGD)
Service Administration
Service be executed?
Oracle Database 249
ERLK160200-00-IWO-EN-01

Did you provide a port for Infrastructure > Create New Section 18.3 “Creating logical
the Enterprise Library Logical Ports ports in the SAP system” in
Content Service? OpenText Extended ECM for
IGD)
Content Service be
instantiated?
Did you provide an HTTP Infrastructure > Create New
destination for the Enterprise Logical Ports
Library Content logical port?
Enterprise Library Content Infrastructure > Create ports in the SAP system” in
Options tab.
Can Enterprise Library
Content Service be executed?
Did you provide a logical Infrastructure > Create New Section 18.3 “Creating logical
port for the Content Server Logical Ports ports in the SAP system” in
Member Service? OpenText Extended ECM for
IGD)
Can the Content Server
Member Service be
instantiated?
destination for the Content Logical Ports
Server Member logical port?
250 Oracle Database
ERLK160200-00-IWO-EN-01

Content Server Member Infrastructure > Create ports in the SAP system” in
HTTP connection: “No HTTP Connections > HTTP OpenText Extended ECM for
Logon” and “Send SAP Connections to External SAP Solutions - Installation
Logon Ticket” is enabled; Server; double-click one and Upgrade Guide (ERLK-
“HTTP compression” is connection; Logon & IGD)
disabled. Security tab and Special
Options tab.
Can the Content Server Directory Services Section 6.5 “Configuring
Member Service be executed? Administration > Access access roles” in OpenText
Roles Extended ECM for SAP
Solutions - User Management
and Access Control Scenarios
(ERLK-CUM)
port for the Extended ECM Logical Ports ports in the SAP system” in
Service? OpenText Extended ECM for
IGD)
destination for the Extended Logical Ports
ECM logical port?
Extended ECM HTTP Infrastructure > Create ports in the SAP system” in
Options tab.
Can the Extended ECM
Service be executed?
Oracle Database 251
ERLK160200-00-IWO-EN-01

port for the OTDS Service? Logical Ports ports in the SAP system” in
OpenText Extended ECM for
IGD)
destination for the OTDS Logical Ports
services?
OTDS HTTP connection: “No Infrastructure > Create ports in the SAP system” in
Logon” and “Send SAP HTTP Connections > HTTP OpenText Extended ECM for
Logon Ticket” is enabled; Connections to External SAP Solutions - Installation
“HTTP compression” is Server; double-click one and Upgrade Guide (ERLK-
disabled. connection; Logon & IGD)
Options tab.
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 18.4 “Configuring the
the SPI service SPI Service or Service Provider Interface
configuration? SOAMANAGER transaction service” in OpenText Extended
ECM for SAP Solutions -
Installation and Upgrade Guide
(ERLK-IGD)
Check the following for the Infrastructure > Configure Section 18.4 “Configuring the
SPI service configuration: SPI Service or Service Provider Interface
“Transport Guarantee Type = SOAMANAGER transaction service” in OpenText Extended
HTTPS”; “Authentication: ECM for SAP Solutions -
User ID/Password” is Installation and Upgrade Guide
enabled. (ERLK-IGD)
HTML Controls
Can an HTML control be
instantiated?
252 Oracle Database
ERLK160200-00-IWO-EN-01

Can an HTML control be
initialized?
Can the HTML control
enable SSO?
Are the SAP HTTP server
and the Content Server
server in the same domain or
is the Content Server server
in a subdomain of the SAP
HTTP server domain?
>>> 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.
Are the SAP SSO profile The following parameter Section 18.2 “Activating the
parameters set properly? must be set: login/ SSO HTTP service” in
accept_sso2_ticket = 1 OpenText Extended ECM for
and login/ SAP Solutions - Installation
create_sso2_ticket = 2 and Upgrade Guide (ERLK-
IGD)
Oracle Database 253
ERLK160200-00-IWO-EN-01
Chapter 41
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 Extended ECM 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 247
Tests the customizing and provides solutions for errors.
• Configuration Report: Section 20.1.3 “Understanding the Configuration
Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-CGD)
Provides information about Extended ECM for SAP Solutions related
customizing in the SAP system.
Content Server
System Report: Section 20.2 “Understanding the Content Server System Report”
in OpenText Extended ECM 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

You can generate a report for OpenText Archive Center: 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 server.
2. OpenText Archive Center
a. Go to Archive Server > System > Reports.

b. In the Reports pane, open the Scenarios tab and select the scenario.
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 Refresh to list the newly generated reports.
f. Double-click one of the generated reports to view it.
Oracle Database 255
ERLK160200-00-IWO-EN-01
Chapter 41 Preparing a checklist for the customizing team
OpenText Directory Services Web Client

The System Status page lets you view a System Configuration Report, version
information for the product, and highlights Potential Configuration Issues.
To generate the system configuration reports:
1. From the web administration menu, under the Info heading, click System
Status.
2. On the System Status page, click Download System Configuration Report.
3. The system configuration report downloads to your machine. An

information box displays, depending on your browser settings, that you can
click to display the report.
256 Oracle Database
ERLK160200-00-IWO-EN-01

OpenText Extended ECM For SAP Solutions 16.2 - Installation Guide For Microsoft Windows With Oracle Database English (ERLK160200-00-IWO-En-01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Extended ECM For SAP Solutions 16.2 - Installation Guide For Microsoft Windows With Oracle Database English (ERLK160200-00-IWO-En-01)

Uploaded by

Copyright:

Available Formats

OpenText™ Extended ECM for SAP®

Installation Guide for Microsoft

This guide describes the installation and basic configuration of

Open Text Corporation

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

Copyright © 2017 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

Part 1 Setting up the server for Archive Center 15

4 Preparing the server ................................................................ 19

5 Installing the server for Archive Center ................................ 23

6 Installing the services ............................................................. 39

Part 2 Setting up the server for Content Server 45

8 Setting up IIS 7.5 ...................................................................... 49

9 Installing Oracle Database Client and setting up the

10 Using the Extended ECM for SAP Solutions Master Setup

11 Installing Content Server on Windows .................................. 81

12 Installing Content Server modules ........................................ 91

13 Configuring Content Server ................................................... 93

14 Configuring OpenText Directory Services for Content

15 Installing the Content Server modules ................................ 111

16 Testing Content Server search ............................................ 113

Part 3 Installing patches 115

17 Installing Enterprise Library patches .................................. 117

18 Installing Content Server patches using the cluster

Part 4 Configuring Enterprise Library Services 121

19 Starting the Administration Client ....................................... 123

20 Configuring OpenText Directory Services for Archive

21 Configuring Archive Center .................................................. 129

22 Configuring the storage provider ........................................ 139

23 Creating a storage provider and a storage rule .................. 141

24 Enabling certificates ............................................................. 145

25 Creating an application ......................................................... 147

Part 5 Installing Archiving and Document Access for SAP

26 Introduction ............................................................................ 153

27 Checking prerequisites ......................................................... 155

28 Installing Basis package ....................................................... 161

29 Installing ERP option package ............................................. 169

30 Installing CRM option package ............................................ 171

31 Installing language packages ............................................... 173

32 Handling communication protocols .................................... 177

Part 6 Setting up Extended ECM for SAP Solutions 185

33 Checking the prerequisites .................................................. 187

33.1 Required knowledge ...................................................................... 187

34 Installing the SAP package ................................................... 195

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

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

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

38 Performing post-installation or post-upgrade tasks in

39 Installing language packs on Content Server ..................... 245

40 Verifying the installation ....................................................... 247

41 Preparing a checklist for the customizing team ................. 255

OpenText Extended ECM for SAP Solutions is a combination of Content Server

1.1 What is new?

1.2 Related documentation

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

Figure 2-1: System overview

The document describes the following scenario:

These servers can be physical or virtual.

This guide describes the setup of a system environment containing these

• Web application server is Apache Tomcat for Archive Center

The installation and configuration of the following components is NOT described in

For these components the detailed installation and configuration documentation is

Following software components must be installed: