OpenText™ Extended ECM for SAP®

Solutions Cloud

Installation Guide

This guide describes how to plan the installation, how to install

the SAP components of OpenText Extended ECM for SAP
SolutionsCloud, and how to set up the communication between
SAP and Content Server. It also contains information on how to
remove the SAP components and how to undo customizing.

EESPCD230200-IGD-EN-01
OpenText™ Extended ECM for SAP® Solutions Cloud
Installation Guide
EESPCD230200-IGD-EN-01
Rev.: 2023-Apr-12
This documentation has been created for OpenText™ Extended ECM for SAP® Solutions Cloud CE 23.2.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

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 © 2023 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.

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
Cloud .......................................................................................... 9
1.1 Related documentation ...................................................................... 9

Part 1 Installing Extended ECM for SAP Solutions Cloud 11

2 Overall architecture ................................................................. 13

2.1 Component diagram ........................................................................ 14

3 Prerequisites for Extended ECM ............................................ 15

3.1 Required knowledge ........................................................................ 15
3.2 SAP system requirements ............................................................... 15
3.3 SAP Add-On Installation Tool (SAINT) .............................................. 18
3.4 Finding version information for relevant system components of
Extended ECM for SAP Solutions Cloud ........................................... 19

4 Installing Extended ECM for SAP Solutions Cloud .............. 21

5 Installing the SAP package ..................................................... 23

5.1 Optional: Installing Fiori Business Object Browser ............................. 26

6 Generating roles ...................................................................... 29

7 Installing language packages in the SAP system ................ 31

8 Customizing the integration into Generic Object Services

(optional) .................................................................................. 33
8.1 Customizing the Generic Object Services (SAP GUI) ......................... 33
8.2 Selecting items to be displayed in Business Content window ............. 36
8.3 Customizing the context menu of the Business Content window ......... 36
8.3.1 Customizing the Business Content window context menu with
Content Server menu entries ........................................................... 37
8.3.2 Adding custom functionality to the Business Content window
context menu .................................................................................. 38
8.4 Providing Drag-and-drop functionality for the Business Content
window ........................................................................................... 39
8.5 Enabling the integration widget in the Business Content window ........ 39
8.6 Providing access to local folders for the Business Content window ..... 40
8.7 Integrating Viewers in the Business Content window ......................... 41
8.8 Customizing MIME types for preview ................................................ 42
8.9 Customizing the GOS Attachment list for Records Management ........ 43

Part 2 Configuring the systems after the installation 47

EESPCD230200-IGD-EN-01 Installation Guide iii

Table of Contents

9 Network overview .................................................................... 49

9.1 S/4HANA on-prem or S/4HANA Cloud, private edition ....................... 49
9.2 S/4HANA Cloud .............................................................................. 50

10 Connecting the SAP system ................................................... 53

10.1 Connecting the SAP system with Content Server .............................. 53
10.2 Connecting the SAP system with OpenText™ Core Archive .............. 53
10.2.1 Creating an archive on the OpenText Archive Center ........................ 56

11 Performing system administration tasks in Content

Server ....................................................................................... 57
11.1 Connecting SAP as the business application ..................................... 57
11.2 Setting permissions for root folders in Content Server ........................ 60
11.3 Managing users and permissions ..................................................... 61
11.3.1 Setting up the authorization for records ............................................. 61
11.4 Configuring document template settings ........................................... 63
11.5 Preparing the Content Server search for users .................................. 64
11.5.1 Creating a search slice for business workspaces ............................... 64
11.5.2 Indexing documents and other items with business workspace
attributes ........................................................................................ 65
11.6 Configuring Smart View for Business Workspaces ............................ 68
11.6.1 Creating a Perspective using the Perspective Manager tool ............... 69
11.6.1.1 To create a workspace-type Perspective .......................................... 70
11.6.2 Configuring widgets for a Business Workspace ................................. 71
11.6.3 Adding your own logo to Content Server Smart View ......................... 72
11.7 Configuring the display of documents in the side-panel ...................... 73
11.8 Configure how document viewing behaves with Web Viewer .............. 74
11.9 Providing the online help ................................................................. 74
11.9.1 Providing the online help on a local help server (Private Help
Server) ........................................................................................... 75
11.10 Preparing document declaration ....................................................... 76
11.10.1 Creating a Records Management classification (optional) .................. 76
11.11 Enabling OpenText Recycle Bin for business workspaces ................. 76
11.12 Checking the appearance of the SAP integration ............................... 77
11.13 Allowing users to save Outlook emails to business workspaces ......... 80
11.13.1 Installing and upgrading the Business Workspaces Outlook add-in ..... 80
11.13.1.1 Preparing to install or upgrade the Business Workspaces Outlook
add-in ............................................................................................. 81
11.13.1.2 Downloading the latest Outlook add-in manifest file ........................... 81
11.13.1.3 Migrating custom settings to the new Outlook add-in manifest file ....... 82
11.13.1.4 Uploading the Outlook add-in manifest file ........................................ 82
11.13.2 Preparing your environment ............................................................. 83
11.13.2.1 Creating Content Server folders for the add-in ................................... 83

iv OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Table of Contents

11.13.2.2 Creating search forms for the add-in ................................................. 85

11.13.3 Configuring add-in settings .............................................................. 86
11.13.3.1 Examples: Configuring email saving options ..................................... 88
11.13.4 Configuring rules and email search settings to display suggested
workspaces .................................................................................... 91
11.13.4.1 Understanding how rules and email search settings are applied ......... 91
11.13.4.2 Understanding how rules are applied to emails sent from Extended
ECM mobile clients ......................................................................... 93
11.13.4.3 Testing your rules and email search settings ..................................... 94
11.13.4.4 Configuring Rules and Email Search Settings ................................... 94
11.13.4.5 Testing Rules and Email Search Settings ......................................... 98
11.13.4.6 Examples: Workspace rules ............................................................. 98
11.14 For SAP CRM and SRM: Configuring security settings .................... 100
11.15 Repairing a group replacement migration ........................................ 100
11.16 Considering virus-scanning ............................................................ 100

12 Performing system administration tasks in the Archive

Center ..................................................................................... 103
12.1 Customizing processing of Extended ECM Records ........................ 103

13 Reporting incidents to SAP Solution Manager ................... 105

14 Performing general post-installation tasks in SAP ............ 107

14.1 Performing general post-installation tasks in SAP ............................ 107
14.1.1 Using the IMG function .................................................................. 107
14.1.2 Assigning SAP roles ...................................................................... 110
14.1.3 Adjusting authorization default values ............................................. 111
14.2 Performing post-installation tasks ................................................... 113
14.2.1 Verifying that SNI is enabled .......................................................... 113
14.2.2 Exporting the SAP PSE certificate for the SAP authentication
handler ......................................................................................... 113
14.2.3 Activating the SSO HTTP service ................................................... 116
14.2.4 Creating logical ports in the SAP system ........................................ 118
14.2.4.1 Creating logical ports for SAP Basis 7.0 .......................................... 118
14.2.4.2 Creating logical ports for SAP Basis 7.01 ........................................ 123
14.2.4.3 Creating logical ports for SAP Basis 7.31 ........................................ 125
14.2.4.4 Creating logical ports for SAP Basis 7.51 ........................................ 128
14.2.4.5 Using the assertion-based authentication mechanism ...................... 130
14.2.5 Configuring the Service Provider Interface service ........................... 132
14.2.6 Creating logical destinations .......................................................... 134
14.2.7 Maintaining Extended ECM connections ......................................... 135
14.2.8 Importing the Content Server SSL certificate ................................... 138

EESPCD230200-IGD-EN-01 Installation Guide v

Table of Contents

15 Mapping SAP roles to OTDS groups or Content Server

groups .................................................................................... 141
15.1 Defining the user partition for group mapping .................................. 141

16 Performing license measurement ........................................ 143

16.1 Extended ECM License Control ..................................................... 144
16.2 Extended ECM License measurement ............................................ 144
16.2.1 Technical overview ........................................................................ 145
16.2.2 Prerequisites ................................................................................ 147
16.2.3 Preparing license measurement on the SAP system ........................ 147
16.2.3.1 Setting up users for measurement .................................................. 147
16.2.3.2 Maintaining measurement tables .................................................... 149
16.2.4 Extended ECM License Metering (old licensing): preparing license
measurement on Content Server .................................................... 152
16.2.5 Running license measurement ....................................................... 153
16.2.5.1 Running in standard mode ............................................................. 154
16.2.5.2 Running in expert mode ................................................................. 155
16.2.6 Creating an export file with license data .......................................... 160
16.2.7 Understanding the consolidated measurement results ..................... 161
16.2.8 Understanding and resolving licensing issues ................................. 162
16.2.8.1 Validation issues after consolidation ............................................... 162
16.2.8.2 Validation issues types on the SAP system ..................................... 164
16.2.8.3 Extended ECM License Metering: Validation issue types on
Content Server .............................................................................. 166

17 Verifying and analyzing the installation .............................. 169

17.1 Analyzing the SAP system ............................................................. 169
17.1.1 Understanding the SAP Diagnostic Program ................................... 169
17.1.2 Understanding the details of the Diagnostic Program ....................... 170
17.1.3 Understanding the Configuration Report ......................................... 175

Part 3 Uninstalling Extended ECM for SAP Solutions Cloud 177

18 General process .................................................................... 179

18.1 Prerequisites for removal ............................................................... 180

19 Performing manual steps before removal ........................... 181

19.1 Extended ECM component OTEXRL .............................................. 181
19.1.1 Performing mandatory manual steps before uninstalling OTEXRL .... 181
19.1.2 Performing optional manual steps before uninstalling OTEXRL ........ 183
19.2 Extended ECM for SAP ERP, S/4HANA component OTEXRLE ....... 183
19.2.1 Performing mandatory manual steps before uninstalling OTEXRLE .. 184
19.2.2 Performing optional manual steps before uninstalling OTEXRLE ...... 185
19.3 Extended ECM CRM component OTEXRLC ................................... 185

vi OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Table of Contents

19.3.1 Performing mandatory manual steps before uninstalling OTEXRLC .. 185

19.4 Extended ECM SRM component OTEXRLS ................................... 190
19.5 Extended ECM OData Services component OTEXRLO ................... 190
19.5.1 Performing mandatory manual steps before uninstalling OTEXRLO . 190
19.6 Extended ECM Fiori Apps component OTEXRLF ............................ 191
19.6.1 Performing mandatory manual steps before uninstalling OTEXRLF .. 191
19.7 Extended ECM Business Scenarios component OTEXRLSA ........... 192
19.7.1 Performing mandatory manual steps before uninstalling OTEXRLSA 192
19.8 Archiving and Document Access component OTEXBAS .................. 193
19.8.1 Performing mandatory manual steps before uninstalling OTEXBAS .. 193
19.8.2 Performing optional manual steps before uninstalling OTEXBAS ...... 194
19.9 Archiving and Document Access ERP package component
OTEXERP .................................................................................... 195
19.9.1 Performing mandatory manual steps before uninstalling OTEXERP . 195
19.10 Archiving and Document Access CRM package component
OTEXCRM ................................................................................... 195
19.10.1 Performing mandatory steps before uninstalling OTEXCRM ............ 195
19.11 Archiving and Document Access OData Services component
OTEXBASO .................................................................................. 196
19.11.1 Performing mandatory steps before uninstalling OTEXBASO ........... 196
19.12 Archiving and Document Access Fiori Apps component OTEXBASF 197
19.12.1 Performing mandatory steps before uninstalling OTEXBASF ........... 197

20 Removing with the SAINT transaction ................................ 199

GLS Glossary 201

EESPCD230200-IGD-EN-01 Installation Guide vii

Chapter 1
What is OpenText Extended ECM for SAP Solutions
Cloud

OpenText Extended ECM for SAP SolutionsCloud is a provider service that extends
SAP business applications such as ERP, CRM and SRM, S/4HANA, or Hybris Cloud
with comprehensive ECM capabilities, including document management, records
management and content-centered collaboration.

OpenText Extended ECM for SAP SolutionsCloud consists of

• OpenText™ Content Server, which provides the core functionality enterprise

content management as a service offering
• Web clients, installable clients and other services components
• Integration components to be installed and configured as add-ons to the SAP
system

While Content Server is installed and maintained in the OpenText Cloud and
offered to you as a service, you maintain your SAP system and its integration
yourself.

1.1 Related documentation

The following documentation is available for Extended ECM for SAP Solutions on
OpenText My Support (https://webapp.opentext.com/piroot/_doclists/suxecmau-
basic.220200.xml):

OpenText Extended ECM for SAP Solutions Cloud CE 22.2 – Installation Guide
see OpenText Extended ECM for SAP SolutionsCloud - Installation Guide (EESPCD-
IGD).
OpenText Extended ECM for SAP Solutions Cloud CE 22.2 – User Guide
see OpenText Extended ECM for SAP SolutionsCloud - User Guide (EESPCD-UGD).
OpenText™ System Center Manager CE 22.2 - Installation and Configuration
Guide
see OpenText System Center Manager - Installation and Configuration Guide
(SYSCM-IGD).
OpenText Extended ECM for SAP Solutions eBook
The eBook describes the key concepts and capabilities of Extended ECM for SAP
Solutions.
The OpenText Extended ECM for SAP Solutions eBook is available on OpenText My
Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/
78814030).

EESPCD230200-IGD-EN-01 Installation Guide 9

Chapter 1 What is OpenText Extended ECM for SAP Solutions Cloud

Extended ECM Solution Accelerators

The purpose of a solution accelerator is to provide a sample implementation of a
specific business scenario or technical solution, often related to an SAP module
or application. A solution accelerator consists in most cases of scenario and
configuration documentation, transport packages, and configuration files.
Solution accelerators are provided to customers and partners at no additional
cost. They are not part of any product and are excluded from product
maintenance and support. Solution Accelerators are available on OpenText My
Support (https://knowledge.opentext.com/go/37710088).
Business Scenarios
Starting with version 21.4, Extended ECM provides Business Scenarios,
which are fully configured and supported scenarios.
SDK & API Documentation in OpenText Developer Network
The SDK & API documentation describes the Extended ECM for SAP Solutions
API and how to integrate it into your own scenario. The SDK & API
documentation is available on OpenText My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=63007681).
Release Notes
see OpenText My Support.

10 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Part 1
Installing Extended ECM for SAP Solutions
Cloud
Part 1 Installing Extended ECM for SAP Solutions Cloud

This part covers the installation of the Extended ECM for SAP SolutionsCloud SAP
Add-on.

• “Overall architecture“ on page 13

• “Prerequisites for Extended ECM“ on page 15
• “Installing Extended ECM for SAP Solutions Cloud“ on page 21
• “Installing the SAP package“ on page 23
• “Generating roles“ on page 29
• “Installing language packages in the SAP system“ on page 31
• “Customizing the integration into Generic Object Services (optional)
“ on page 33

12 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 2
Overall architecture

EESPCD230200-IGD-EN-01 Installation Guide 13

Chapter 2 Overall architecture

2.1 Component diagram

Figure 2-1: Component diagram of Extended ECM for SAP SolutionsCloud

14 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 3
Prerequisites for Extended ECM

Extended ECM for SAP SolutionsCloud supports the following SAP products:

• SAP S/4HANA
• SAP ERP 6.0
• SAP CRM 7.0

– Content Server integration widget is only supported for Business Workspace

UI Integration in SAP CRM.
– CRM requirement: CRM 7.0 EHP 1
• SAP SRM 7.0

3.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 OpenText Content Server, OpenText Archive Center,
Records Management, User Management, and OpenText Directory Services.

3.2 SAP system requirements

Check the following prerequisites for SAP prior to installation:

Basis package
On most SAP systems, you require:

• The SAP Add-On OTEXBAS of Archiving and Document Access for SAP
Solutions. This component is provided on the Extended ECM for SAP
SolutionsCloud installation medium. For details about required versions and
dependencies, read the Required SAP support packages section below.
• The SAP Add-On OTEXRL. For details about required versions and
dependencies read the Required SAP support packages section below. Most
of the other SAP Add-Ons require the Add-Ons OTEXBAS and OTEXRL at
installation time or at least at runtime.

Transport system
The SAP application transport system is installed, this means the jobs RDDPUTPP
and RDDIMPDP are set up in the correct clients and scheduled to run periodically
or event-triggered.

EESPCD230200-IGD-EN-01 Installation Guide 15

Chapter 3 Prerequisites for Extended ECM

Required SAP support packages

Proceed as follows:

• In the Release notes, look up the following sections:

– SAP Server Support – gives you an overview of which SAP Business

Suite, SAP S/4HANA, or SAP CX releases are supported.
– Supported SAP GUIs – lists the supported SAP GUIs.
• Read the document OpenText™ Extended ECM for SAP Solutions CE
<version>– SAP Add-on Packages – Additional Release Information.

– to get a detailed list of extended attributes and import conditions of the

SAP Add-On packages related to this release.
– to learn whether Attribute Change Packages are available and how to get
them.
– to read details about support of Fiori UI Web User Interface.

You can find this document in the same documentation folder as the Release
notes.
Short overview of required patch levels or versions:

• Patch level for SAP ERP 6.0 – The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 700, patch level 22. 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 – For component BBPCRM, the minimum is
release 700, patch level 02.
For component WEBCUIF, the minimum is release 700, patch level 02.
• Patch level for SAP SRM 7.0 – For component SRM_SERVER, the minimum
requirement is release 700, patch level 08.
• Patch level for optional Fiori UI package – At installation time, the
minimum requirement for software component SAP_UI is release 754.
Add-On package OTEXRLF requires the corresponding Add-On OTEXBASF.
Though not required for installation, the Fiori app calls the OData services of
Extended ECM for SAP Solutions at runtime. At runtime, the Fiori apps
require a minimum of SAPUI5 1.71.
For optimal accessibility, use the highest SAPUI5 version with long-term
maintenance. For more information, see SAP Note 2564165 (https://
launchpad.support.sap.com/#/notes/2564165).
For the SAPUI5 version maintenance status, see https://ui5.sap.com/
versionoverview.html.
• 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).

16 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 3.2. SAP system requirements

Though not required for installation, the OData services of Extended ECM
for SAP Solutions call RFC functions of the basis add-on of Extended ECM
for SAP Solutions OTEXRL at runtime.

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.
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.
2238264 (SAP S/4HANA) Several outbound web service proxies
should be triggered. In that process a
program termination of type
STYLESHEET_GENERATION_FAILURE is
raised.
1713851 (For SAP_BASIS 700 and higher) This note prevents a dump screen in the
Business Content Window when you try to
open a record and then in an SAP Security
dialog press the Deny button.
822380 Required to avoid known problems with
(SAP 7.00) the SAP Add-On Installation Tool
212876 (SAINT).
(SAPCAR tool)
1382711 Required when using SAP CRM
1379958 Investigative Case Management.
1613012
1160362 Required for licensing, thumbnails, and
group mapping.
The profile parameters of your SAP system
ict/disable_cookie_urlencoding = 1 must
be configured.
1451769 Required for additional ArchiveLink
2515351 (SAP_BASIS 740 and later) attributes Description, Filename,
Creator, and CREATIME.

EESPCD230200-IGD-EN-01 Installation Guide 17

Chapter 3 Prerequisites for Extended ECM

SAP Note Required for

2293517 Required for update in document
declarations.
1582867 Starting with version 16.2, Archiving and
Document Access for SAP Solutions and
Extended ECM for SAP Solutions use a
new URL escaping, which is based on
SAP's escape_xss_url as implemented
in SAP note 1582870.
For SAP BASIS 731 and higher, method
cl_abap_dyn_prf=>escape_xss_url
is called directly. For older releases, a
Kernel function is used if an SAP Kernel as
of note 1582867 is at place or a fallback
code is used as derived from SAP's
original implementation of SAP note
1582870.
In the case of non-Unicode systems, the
related notes referenced in SAP Note
1582867 should be applied.
3126094 This note describes the solution in case the
upgrade or the installation stops at the
SKWF_TP_NMSPC_CHECK_AFTER_IMP
post-import method.

Note: The documentation and the Release Notes are updated regularly. Check
for the latest version and the additional release information for integrations to
SAP Solutions at OpenText My Support (https://knowledge.opentext.com/
knowledge/llisapi.dll/open/16514655).

3.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. SAINT uses single PAT files (extension *.PAT) which
integrate several transport files. These collections are also called packages.

On the installation medium, the PAT file is in an SAPCAR file (extension *.SAR),
which can be extracted using the SAPCAR command line tool.
The SAPCAR file is in a DATA folder below the package folder named as the package
and SAP release, for example: Archiving and Document Access for SAP Solutions
\SAP\INST_BAS_700\DATA\OTEXBAS_INST_2240_700.SAR

Note: The handling of the installation procedure within SAINT depends on the
SAP system. For details, see the SAP documentation.

18 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 3.4. Finding version information for relevant system components of Extended ECM for SAP Solutions Cloud

3.4 Finding version information for relevant system

components of Extended ECM for SAP Solutions
Cloud
This chapter explains how you can find out which versions of the different
components are used in your system.

Version information is also included in the system reports of Content Server and the
configuration report in the SAP system.

Tip: You find additional information about your systems in the following
reports:

• Section 27.1.1 “Understanding the SAP Diagnostic Program” in OpenText

Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD)
• Section 27.1.3 “Understanding the Configuration Report” in OpenText
Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD)

• 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 27.1.3
“Understanding the Configuration Report” in OpenText Extended ECM for SAP
SolutionsCloud - Customizing Guide (EESPCD-CGD).
• Support Package of installed SAP System
In the SAP GUI application, on the menu, select System > Status. 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 can use this instead of the
configuration report.
• SAP Fiori apps
For each application, there is a static version.html file, which 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

EESPCD230200-IGD-EN-01 Installation Guide 19

Chapter 4
Installing Extended ECM for SAP Solutions Cloud

This chapter describes the installation of Extended ECM for SAP SolutionsCloud
SAP Add-on package.

Installation sequence
1. On the SAP system, install the SAP packages:

• Archiving and Document Access (SAP Add-On) (OTEXBAS)

• Extended ECM for SAP SolutionsCloud (SAP Add-On) (OTEXRL)
2. Configure Extended ECM for SAP SolutionsCloud:

• Set up security.
• Configure Records Management (declaration, document types, jobs).
• Configure Extended ECM for SAP SolutionsCloud business functionality:
business workspaces, business attachments, business relations. For more
information, see OpenText Extended ECM for SAP SolutionsCloud - Customizing
Guide (EESPCD-CGD).

EESPCD230200-IGD-EN-01 Installation Guide 21

Chapter 5

Installing the SAP package

This chapter describes how to install the following components of Extended ECM
for SAP Solutions on an SAP application server.

Extended ECM for SAP Solutions uses the SAP Add-On Installation Tool (SAINT)
for installation of the SAP part. SAINT uses single PAT files (extension *.PAT) which
integrate several transport files. These collections are also called packages.

On the installation medium, the PAT file is located in an SAPCAR file (extension
*.SAR), which 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, for example: Archiving and Document Access for SAP Solutions/
SAP/INST_BAS_700/DATA/OTEXBAS_INST_2240_700.SAR

Note: The handling of the installation procedure within SAINT depends on the
SAP system. For more information, see the SAP documentation.

• OTEXRL: Mandatory main package for Extended ECM for SAP Solutions
• OTEXRLC: Extended ECM for SAP Solutions for SAP CRM Add-On
• OTEXRLS: Extended ECM for SAP Solutions for SAP SRM Add-On
• OTEXRLO: Extended ECM for SAP Solutions SAP OData Services Add-on
• OTEXRLF: Extended ECM for SAP Solutions SAP Fiori Apps Add-On
• OTEXRLE: Extended ECM for SAP Solutions for SAP ERP, S/4HANA
• OTEXRLSA: Extended ECM for SAP Solutions Business Scenarios
• OTEXRLS4: Extended ECM for SAP Solutions S/4HANA

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 system requirements” on page 15 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.

If you are performing a new installation, you need the installation packages and
their passwords.

EESPCD230200-IGD-EN-01 Installation Guide 23

Chapter 5 Installing the SAP package

Package name OTEXRL OTEXRLO OTEXRLF

Purpose Extended ECM for Extended ECM for Extended ECM for
SAP Solutions SAP Solutions OData SAP Solutions Fiori
Services UI
SAP release SAP BASIS 700 and SAP Basis 7.00, SAP_UI is 752 and
later SAPKB70018, later
IW_BEP 200
OCS Package Name SAPK-311COINOTE SAPK-311COINOTE SAPK-011COINOTE
XRL XRLO XRLF
Password 9387CE26B8 9387CE49B8 9087CE40B8
File OTEXRL_INST_2240 OTEXRLO_INST_224 OTEXRLF_INST_224
_700.SAR 0_700.SAR 0_740.SAR
Source path /INST_BAS_700/ /INST_ODATA_700/ /INST_FIORI_740/
DATA DATA DATA

Package name OTEXRLC OTEXRLS OTEXRLE

Purpose Extended ECM for Extended ECM for Extended ECM for
SAP Solutions for SAP Solutions for SAP Solutions for
SAP CRM SAP SRM SAP ERP, S/4HANA
SAP release SAP CRM 7.0 and SAP SRM 7.0 and SAP ERP 6.0, S/
later later 4HANA
SAP S/4HANA for
Customer
Management 1.0 and
later
OCS Package Name SAPK-511COINOTE SAPK-311COINOTE SAPK-311COINOTE
XRLC XRLS XRLE
Password 9587CE45B8 9387CE55B8 9387CE43B8
File OTEXRLC_INST_224 OTEXRLS_INST_224 OTEXRLE_INST_224
0_700.SAR 0_700.SAR 0_700.SAR
Source path /INST_CRM_700/ /INST_SRM_700/ /INST_ERP_700/
DATA DATA DATA

Package name OTEXRLSA OTEXRLSA OTEXRLS4

Purpose Extended ECM for SAP Extended ECM for SAP Extended ECM for SAP
Solutions for Business Solutions for Business Solutions for S/4HANA
Scenarios Scenarios
SAP release SAP ERP 6.0 SAP S/4HANA 1909 SAP S/4HANA 2022
and later and later
OCS Package SAPK-011COINOTEXR SAPK-311COINOTEXR SAPK-011COINOTEXR
Name LSA LSA LS4
Password 9087CE55D9 9387CE55D9 9087CE55AC

24 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Package name OTEXRLSA OTEXRLSA OTEXRLS4
File OTEXRLSA_INST_224 OTEXRLSA_INST_224 OTEXRLS4_INST_2240
0_700.SAR 0_754.SAR _754.SAR
Source path /INST_BUSSCE_700/ /INST_BUSSCE_754/ /INST_S4HANA_754/
DATA DATA DATA

OTEXRLS4 package
Although this package was created on S/4HANA 1909, only an installation
on S/4HANA 2022 makes sense. This package only contains code relevant
for the UI integration of SAP Harmonized Document Management
(HDM).

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

following command:
SAPCAR -xvf <name of SAPCAR file>
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 later, you can use the SAINT and SPAM
transactions to upload and extract the SAR files from the frontend system.

3. Import the package as described in the respective SAP documentation. You will
need the password for the package.

After the installation, activate a Business Configuration (BC) set for every client.

To avoid issues with the activation of Business Configuration (BC) sets, apply the
SAP notes listed in Section 6.2 “SAP system requirements” in OpenText Extended
ECM for SAP Solutions - Installation and Upgrade Guide (ERLK-IGD).

To activate the BC set:

1. Start the SCPR20 transaction.

The Business Configuration Set screen appears.

2. Activate the following BC Set: /OTEXRL/RM_SEA

For more information, see the SAP documentation.

EESPCD230200-IGD-EN-01 Installation Guide 25

Chapter 5 Installing the SAP package

5.1 Optional: Installing Fiori Business Object

Browser
OpenText™ Fiori Business Object Browser for Extended ECM for SAP Solutions is a
collective term, which includes compatible versions of:

• OpenText™ Extended ECM for SAP Solutions

• OpenText™ Fiori Business Object Browser Enabler for SAP Solutions containing
2 ABAP add-ons of OpenText™ Vendor Invoice Management for SAP®
Solutions.
These add-ons are required to build custom Fiori apps to browse for business
objects.

Notes

• Usage restrictions are detailed in the Release notes section Usage of

OpenText™ Fiori Business Object Browser for SAP Solutions.
• Check the compatibilities depending on the Process Base Fiori Task App
version.
• For details of installation, configuration and required tasks after upgrading
from older versions, read the Release notes and documentation of
OpenText™ Vendor Invoice Management for SAP® Solutions.

List of ABAP add-ons of Vendor Invoice Management – required for a business

object browser scenario:

Target System ABAP Add-on

SAP Backend OTBCBAS
SAP Gateway (Hub / Frontend) OTBCWUI
Optional: OTBCBAS

See also Section 18.2.1.2 “Packages for business object browsers” in OpenText
Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD).

Required Vendor Invoice Management versions for business object browser

scenario – Extended ECM for SAP Solutions 22.4 supports the business object
browser scenario with the following versions of Vendor Invoice Management:

Vendor Invoice Management Component/Package Version Support

for SAP Solutions package[a]
20.4 OTBCBAS 0700_006
OTBCWUI 0740_006
20.4 SPS1 OTBCBAS 0700_006 1
OTBCWUI 0740_006 1

26 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 5.1. Optional: Installing Fiori Business Object Browser

Vendor Invoice Management Component/Package Version Support

for SAP Solutions package[a]
20.4 SPS2 OTBCBAS 0700_006 2
OTBCWUI 0740_006 2
20.4 SPS3 OTBCBAS 0700_006 3
OTBCWUI 0740_006 3
20.4 SPS4 OTBCBAS 0700_006 4
OTBCWUI 0740_006 5
[a] Support Packages are not cumulative. The respective previous package is required.

EESPCD230200-IGD-EN-01 Installation Guide 27

Chapter 6
Generating roles

The following roles are delivered with the application:

• /OTX/RM_ADMIN
• /OTX/RM_ADMIN_S4 (on S/4HANA 2021 onwards)
• /OTX/RM_CS_SAP_USER
• /OTX/RM_CS_SAP_USER_S4 (on S/4HANA 2022 onwards)
• /OTX/RM_USER
• /OTX/RM_IMPERSONATED_USER_ROLE
• If Extended ECM for SAP Solutions for SAP ERP, S/4HANA (component
OTEXRLE) is installed: /OTX/RMERP_DMS_TECH_USER_ROLE

To generate the roles:

1. Start the PFCG transaction.

2. On the Utilities menu, click Mass Generation.

3. Select Roles with Non-Current Profiles, and in the Role field, enter /OTX/RM*.

4. Follow the steps to generate the profiles.

5. Start transaction PFCG and check the following roles one by one:

• /OTX/RM_ADMIN
• /OTX/RM_ADMIN_S4
• /OTX/RM_CS_SAP_USER
• /OTX/RM_CS_SAP_USER_S4
• /OTX/RM_USER
• /OTX/RM_IMPERSONATED_USER_ROLE
• If Extended ECM for SAP Solutions for SAP ERP, S/4HANA (component
OTEXRLE) is installed: /OTX/RMERP_DMS_TECH_USER_ROLE.

6. Ensure that the Authorizations tab has a green icon. If it is yellow, you must
regenerate the authorizations: Click Display Authorization Data, and then
click Generate.

EESPCD230200-IGD-EN-01 Installation Guide 29

Chapter 7
Installing language packages in the SAP system

This chapter describes how to install language packages in an SAP system.

The Add-On installation packages include the default language English. You must
use the optional language packages to install other languages. For more information
about available languages, see Extended ECM for SAP SolutionsCloud 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/Open/8521552).

To install a language package:

1. On OpenText My Support, go to Extended ECM for SAP Solutions, Cloud

Edition (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
70787484), 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.
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, which 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.

Notes

• Extract the SAPCAR file (.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.
• Starting with SAP_BASIS 7.00, you can import and extract the file
directly in transaction SMLT.
3. Use transaction SMLT to import your language package.

Important
Before starting to import language packages, OpenText recommends to
red 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:

EESPCD230200-IGD-EN-01 Installation Guide 31

Chapter 7 Installing language packages in the SAP system

• 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

5. Optional Only for 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 are available. The procedure of installation is the same as
described above.

32 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 8
Customizing the integration into Generic Object
Services (optional)

8.1 Customizing the Generic Object Services (SAP

GUI)
Note: You can open business attachments that are compound documents and
display any document they contain.

You can make business workspaces and business attachments available for users in
SAP GUI via Generic Object Services (GOS). The user can then create workspaces,
display existing ones and display, create and delete business attachments in SAP
GUI. For this, you customize the GOS table.

The Business Content window displays business workspaces, business attachments

like pictures or compound documents for example, business documents, local
TempoBox folders, other local files, and notes in one dialog.

Important
If you are upgrading from 10.0.0, the existing GOS customizing will not be
changed. You can choose if you want to keep several GOS entries or if you
want to use Content Server Business Content.

Tip: For a detailed description of the Business Content window, see Section 8
“Working with the Business Content window” in OpenText Archiving and
Document Access for SAP Solutions - User Guide (ER-UGD).

EESPCD230200-IGD-EN-01 Installation Guide 33

Chapter 8 Customizing the integration into Generic Object Services (optional)

To customize General Object Services:

1. Start the SM30 transaction, and then enter SGOSATTR in the Table/View field.
Click Maintain.

2. Click New Entries.

3. Customize the new entry according to the following list. The OTX_ATTACH
service displays the Business Content window: business workspaces, business
attachments and business documents (ArchiveLink documents). From the
Business Content window, users can access the complete functionality.

Name of service
Enter OTX_ATTACH.
Description
Provide a description, for example, Business Content. This description is
displayed in the GOS menu.
Quick Info
Provide a quick info, for example, Business Content. This information is
displayed for the icon.

34 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.1. Customizing the Generic Object Services (SAP GUI)

Class for Generic Service

Enter /OTX/RM_GOS_SRV_ATTACH_LIST.
Service Type
Select Single Service.
Icon
ICON_BUSINAV_DATAMODEL

Note: Control and Commit required must remain unselected.

4. You must define the position of the new service in the General Object Services.
In the Next service field, enter the name of the service that should follow after
this service. If the service is the last, leave the field empty.

Important
If you do not define the position correctly, it might not be displayed at all.

• You want to add the new service at the beginning of the existing services:
Enter the name of the first existing service in the Next service field of the
new service.
• You want to add the new service at the end of the existing services: Enter the
name of the new service in the Next service field of the last existing service.
Leave the Next service field of the new service empty.
• You want to add the new service in between the existing services: Enter the
name of the new service in the Next service field of the predecessor of
existing services. Enter the name of the successor existing service in the Next
service field of the new services.

5. Click Save.

Note: For more information about maintaining the SGOSATTR table, see the SAP
documentation (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/
a0139058-ef9d-2b10-598c-9e23dc6f44fc).

For problems when displaying services in GOS, see SAP Note 961713 -
Structure of table SGOSATTR.

EESPCD230200-IGD-EN-01 Installation Guide 35

Chapter 8 Customizing the integration into Generic Object Services (optional)

8.2 Selecting items to be displayed in Business

Content window
For each business object type, you can select, which items you want to be displayed
in the Business Content window.

To customize the displayed items in a Business Content window:

1. In the IMG, navigate to the Extended ECM > Business Content Window >
Maintain Business Content Window Display Options, and then click
Execute.
2. Click New Entries.
3. Select a business object type and then select the options that you want to be
displayed:

• Full page: Uses the whole Business Content window to display the business
workspace in Smart View
• Bus. Wrks: Display a node for the business workspace
• Wrks thumbs: Business workspace thumbnails
• Drag Drop: Enable Drag and Drop in business workspaces
• Attachment: Display the business attachments of a node
• Documents: Display a node for business documents
• Doc. thumb: Display thumbnails for business documents
• Notes: Display a node for notes
• Files: Display a node for local files

Tip: For general settings of the Business Content window, which are also
placed in this dialog, see “Enabling the integration widget in the Business
Content window” on page 39.

8.3 Customizing the context menu of the Business

Content window
The context menu of the Business Content window in the SAP system displays a
selection of Content Server menu entries that are available for the specific item. You
can customize the context menu as follows:

• Remove Content Server menu entries that are not relevant and add specific menu
items that are available on Content Server, for example when a new module was
installed. The added menu items are displayed in the context menu only if they
are available for the item type. For more information, see “Customizing the
Business Content window context menu with Content Server menu entries”
on page 37.
• In addition to the available Content Server menu entries, you can add new
entries and implement custom functionality. For more information, see “Adding
custom functionality to the Business Content window context menu”
on page 38.

36 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.3. Customizing the context menu of the Business Content window

8.3.1 Customizing the Business Content window context

menu with Content Server menu entries
You can remove irrelevant entries from the context menu or add specific menu
items, which are also available in Content Server, for example when a new module
was installed. The context menu items are displayed in the context menu only if they
are available for the item type.

To customize the context menu with Content Server menu entries:

1. In the IMG, navigate to the Extended ECM > Business Content Window >
Maintain Business Content Window Menu, and then click Execute.

2. Click New Entries.

3. Enter the following:

Code ID
Enter the code ID. Use the F4 help to retrieve the code ID.

Note: If the code ID is not listed in the F4 help, retrieve it from

Content Server: In the Content Server IDE plug-in for Eclipse, go to
the WebNodeCmd object in the WEBNODE OSpace. From the context
menu of the WebNodeCmd, select Open Inheritance View. A list
with all possible context menu objects is displayed. Find the respective
object and note the name.

BROWSE Open
COPY Copy
DELETE Delete
DOWNLOAD Download
FETCH Open
MAKEFAVORI Add to Favorites
TE
MOVE Move
PRINT Print
TEXTEDIT Edit
VIEWDOC View with Content Suite Viewer

Note: Alternatively, you can integrate Content Suite

Viewer using the SM30 transaction. This is the
recommended integration. For more information, see
“Integrating Viewers in the Business Content window”
on page 41.

EESPCD230200-IGD-EN-01 Installation Guide 37

Chapter 8 Customizing the integration into Generic Object Services (optional)

Add/Remove
Click Add or Remove. When you add an entry, it is added according to the
sequence in the Content Server menu. You cannot add already existing
entries.
Description
Enter a description. This description is displayed in the context menu. You
can use && to display the & character.
If you want to add the entry in other languages, use the standard SAP
mechanism clicking Goto > Translation.

Example: In the following example, the new menu item Zip & Download is added to
the menu.

8.3.2 Adding custom functionality to the Business Content

window context menu
In addition to the available Content Server menu entries, you can add new entries to
the context menu and implement custom-made functionality using BAdI
technology. For detailed information, see the SDK guide on OpenText My Support.

Adding custom functionality:

1. In the IMG, navigate to the Extended ECM > Business Content Window >
Implement Business Content Window Menu BAdI, and then click Execute.

2. Implement your code. For detailed information, see the sample code provided
with the BAdI definition (menu Goto > Sample Code > Display).

• The method PROCESS_CTX_MENU_CONSTRUCTION is used to create an

additional context menu entry.
• In the method PROCESS_WKSP_FCODE you can react on the function codes
you assigned to your context menu entry.

38 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.4. Providing Drag-and-drop functionality for the Business Content window

8.4 Providing Drag-and-drop functionality for the

Business Content window
To upload documents, users can drag files from the local file system into a business
workspace. The local files system can either be the local file explorer or the Local
Files node in the Business Content window.

To copy files, users can drag between different nodes in the Business Content
window. To download files, they drag a file to the Local Files node.

For this functionality, users must have the S_GUI authorization object with the
ACTVT=60 parameter. This authorization object is part of the /OTX/RM_USER role.

8.5 Enabling the integration widget in the Business

Content window
In the Business Content window, users can work with business workspaces. You can
define separately for each business object type that users see the Create and
Complete integration widget (Content Server Smart View) instead of the default
view.

Important
If you use SAP GUI for Windows, the integration widget does not support
office editors in Microsoft Edge. As an alternative, you can use office online
editors.

To enable the integration widget (Content Server Smart View):

1. In the IMG, navigate to the Extended ECM > Maintain Business Object
Declarations activity, and then select Use Widgets for UI for the business
objects for which you want to enable the integration widget in Business Content
window, Web Dynpro or CRM UI.
For more information about the activity, see Section 3.3 “Creating a business
object declaration in SAP” in OpenText Extended ECM for SAP SolutionsCloud -
Customizing Guide (EESPCD-CGD).

2. Through authorization object J_6NRL_WSC, if users may view the Business

Content window in full page view. You may want to disable this option to
avoid that users forget to log out properly.

a. Run transaction pfcg to edit the authorization role.

b. In the J_6NRL_WSC authorization object, set the /OTX/RMWAC field Business
workspace activity to value 02 Open Business Workspace in Fullpage..

Tip: For more customizing options for the Business Content window, see
“Selecting items to be displayed in Business Content window” on page 36.

EESPCD230200-IGD-EN-01 Installation Guide 39

Chapter 8 Customizing the integration into Generic Object Services (optional)

8.6 Providing access to local folders for the

Business Content window
The Business Content window automatically displays the local Tempo Box folder if
Tempo Box client is installed. In addition, users can add other local folders to the
Local files node in the Business Content window. For this functionality, users must
have the J_6NRL_LFS authorization object. This authorization object is part of the /
OTX/RM_USER role.

To assign the authorization object to a group:

1. Start the PFCG transaction.

2. Find the relevant role and add the J_6NRL_LFS authorization object.

Security settings – When a user accesses a local folder from the Business Content
window, an SAP security alert informs the user about the risk. Users can confirm the
message per access attempt, or they can set the security options for their client.

To set the security options on SAP GUI:

1. From the SAP GUI menu, select Options.

2. Select Security > Security Settings.

3. Set Status and Default Action as required.

40 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.7. Integrating Viewers in the Business Content window

8.7 Integrating Viewers in the Business Content

window
Viewers are used to display documents in Business Content window, DocuLink and
Content Server. The following viewers can be integrated and used to display
documents:

OpenText™ Imaging Web Viewer and OpenText™ Imaging Windows Viewer

Can be used as viewers for files that are stored in Archive Center. They must be
of a MIME type that is supported by Web Viewer.
OpenText™ Content Suite Viewer
Can be enabled in Content Server. It uses an OpenText Brava! Server installation
specifically prepared for this use case. For more information about installation
and configuration, see the respective documentation.
OpenText Intelligent Viewing (licensed version)
Is supported in the Business Content window if you use Microsoft Edge and
SAP GUI for HTML 7.70.

Note: OpenText Intelligent Viewing is currently not supported for mobile

devices like Apple® iPad®.

Configuring the Business Content window viewer

The Business Content window displays Content Server content. To use Content
Suite Viewer as viewer within the Business Content window, you enable a menu
entry for the viewer and define that the document opens in the Content Suite Viewer
when the user double-clicks it.

• Enable Content Suite Viewer as Content Server viewer.

– Content Suite Viewer Administration on Content Server Administration page.

For more information, see OpenText Content Server Admin Online Help -
Content Suite Viewer Administration (LLESDV-H-AGD).
• On Content Server, disable that the document opens for editing when the user
double-clicks it.
• Maintain mime types and define that Microsoft Office document are opened with
the viewer. For more information, see “Customizing MIME types for preview”
on page 42.
• Configure the Business Content window so that there is a new menu entry and
the document opens in Content Suite Viewer when the user double-clicks it.

To disable editing in Content Server:

1. On the Content Server administration page, click Core System - Server

Configuration > Security Parameters.

EESPCD230200-IGD-EN-01 Installation Guide 41

Chapter 8 Customizing the integration into Generic Object Services (optional)

2. In the Document Function section, for the Open function, select Disabled.

To add a Content Suite Viewer action to Business Content window menu:

1. Start the SM30 transaction and enter /OTX/RM_WSC_FCOD in the Table/View

field. Click Maintain.

2. Click New Entries.

3. Customize the new entries according to the following lists.

Add an entry for Business Content window:

• Menu ID: ALPLUS

• Code ID: VIEWDOC
• Description: For example, View or Display with Content Suite Viewer.
• Activation: Select it.
• Function Code: PICK

Add an entry for DocuLink:

• Menu ID: DOCULINK

• Code ID: VIEWDOC
• Description: For example, View or Display with Content Suite Viewer.
• Activation: Select it.
• Function Code: PICK

Note: If you do not want to disable the Open document function on Content
Server, the FETCH function will be used instead of the defined VIEWDOC function
when users double-click a document in Business Content window. You can
circumvent this by defining a description that is alphabetically before the
description of the FETCH action, for example FETCH with description Open and
VIEWDOC with description Display.

8.8 Customizing MIME types for preview

The Business Content window is based on a hidden Windows Internet Explorer (IE)
to render documents for the preview. Internet Explorer takes care of calling the
respective rendering application. However, some Internet Explorer add-ons, for
example Web Viewer, handle specific MIME types by enabling an in-place rendition.
As a consequence, the Business Content window must use a visible Internet Explorer
to render the corresponding documents.

The /OTX/RM_GOS_DD table keeps a default list of MIME types for which Internet
Explorer add-ons enable an in-place rendition. If this list is not sufficient, you can
maintain a custom list in the /OTX/RM_GOS_DD_C table.

42 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.9. Customizing the GOS Attachment list for Records Management

Note: The Business Content window ignores the /OTX/RM_GOS_DD table as

soon as the /OTX/RM_GOS_DD_C table has at least one entry.

Recommended setting for Web Viewer

If Web Viewer is enabled on Content Server, add MIME types of documents to the /
OTX/RM_GOS_DD_C table. If you did not maintain the MIME types in the /OTX/RM_
GOS_DD_C table, it can happen that an archived document that you want to open in
Business Content window causes an infinite loop.

Important
Also add the MIME types from /OTX/RM_GOS_DD if you want to keep the
behavior of these MIME types as well.

Restrictions Web Viewer can only render documents that are archived to an OpenText archive.
For example, if you want to display a Microsoft Word document, Internet Explorer
starts Microsoft Word, but leaves an empty browser window open.

Recommended setting for OpenText Content Suite Viewer

If Content Suite Viewer is enabled on Content Server, add MIME types of
documents to the /OTX/RM_GOS_DD_C table. If you did not maintain the MIME types
in the /OTX/RM_GOS_DD_C table, it can happen that an archived document that you
want to open in Business Content window causes an infinite loop.

Important
Also add the MIME types from /OTX/RM_GOS_DD if you want to keep the
behavior of these MIME types as well.

8.9 Customizing the GOS Attachment list for

Records Management
If you want to use business attachments and Records Management functionality in
the GOS Attachment list, you must activate business functions.

Note: This customizing step is not necessary if you are using Business Content
window. For more information, see “Customizing the Generic Object Services
(SAP GUI)” on page 33.

EESPCD230200-IGD-EN-01 Installation Guide 43

Chapter 8 Customizing the integration into Generic Object Services (optional)

With business functions, you integrate the following into the GOS Attachment list:

Button Declare as record

Button View record details

Records Management Status symbol Is record

Business functions

• /OTX/RM_BF_GOS_ATTACHMENT
Integrates Records Management functions into the GOS Attachment list.
• /OTX/RM_DOL_BF_GOS_ATT_LIST
Integrates business attachments into the GOS Attachment list.
• /OTX/RM_BF_DISP_PRINTLIST
Integrates Records Management functionality into the OADR and OADD
transactions.

To activate business functions:

1. In the IMG, navigate to the Extended ECM > Activate Business Functions
activity and click Execute.

2. Open the ENTERPRISE_EXTENSIONS folder and activate the following

options by selecting the checkbox in the Planned Status column:

44 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 8.9. Customizing the GOS Attachment list for Records Management

• /OTX/RM_BF_DISP_PRINTLIST: Records Management for Display

Printlists
• /OTX/RM_BF_GOS_ATTACHMENT: Business Function GOS Attachment

Note: /OTX/RM_DOL_BF_GOS_ATT_LIST is displayed but is no longer

relevant.

3. Click Activate Changes.

EESPCD230200-IGD-EN-01 Installation Guide 45

 Part 2
Configuring the systems after the
installation
Part 2 Configuring the systems after the installation

This part explains the tasks that you perform after the installation. You need system
administrators access to Content Server.

Please contact OpenText Professional Services for assistance.

• “Network overview“ on page 49

• “Connecting the SAP system“ on page 53
• “Performing system administration tasks in Content Server“ on page 57
• “Performing system administration tasks in the Archive Center“ on page 103
• “Reporting incidents to SAP Solution Manager“ on page 105
• “Performing general post-installation tasks in SAP“ on page 107
• “Mapping SAP roles to OTDS groups or Content Server groups“ on page 141
• “Performing license measurement“ on page 143
• “Verifying and analyzing the installation“ on page 169

48 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 9
Network overview

This chapter gives you an overview of the network architecture in the cloud.

9.1 S/4HANA on-prem or S/4HANA Cloud, private

edition

hierweiter

1. Connection to OTDS WebService:

https://otds.example.com/ot-authws/services/Authentication RestAPI:
https://otds.example.com/otdsws/rest

2. SPI Connection, for example:

https://sap-s4hana.example.com:44300/sap/bc/srt/xip/otx/
ecmlinkservice/800/ecmlinkspiservice/basicauthbinding

EESPCD230200-IGD-EN-01 Installation Guide 49

Chapter 9 Network overview

3. Connection to Extended ECM ECMLink WebService:

https://otcs.example.com/services/ECMLink Web:
https://otcs.example.com/cs/cs
4. Connection to archive ArchiveLink:
https://otcs.example.com/alfilter/archive
5. Connection for ILM:
https://otacc.example.com/as_cmis/ilm or, depending on installation type,
https://otac.example.com/as_cmis/ilm
6. Pipeline connection to archive:
https://otacc.example.com/archive or, depending on installation type,
https://otac.example.com/archive

9.2 S/4HANA Cloud

1. SPI Connection, for example:

https://sap-s4hana.example.com:44300/sap/bc/srt/xip/otx/
ecmlinkservice/800/ecmlinkspiservice/basicauthbinding
2. Connection to Extended ECM Integration Handler:
https://otcs.example.com/cs/cs?func=xecmpf.
GetWspIntegration&extsysid=XX&botype=EQUI&bokey=TRUCK05&mode=
fullPage

50 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 9.2. S/4HANA Cloud

3. Connection to CMIS:
https://otcs.example.com/xecm-cmis/browser

4. Connection for ILM:

https://otacc.example.com/as_cmis/ilm, or depending on installation type,
https://otac.example.com/as_cmis/ilm

5. Pipeline connection to archive:

https://otacc.example.com/archive or, depending on installation type,
https://otac.example.com/archive

EESPCD230200-IGD-EN-01 Installation Guide 51

Chapter 10
Connecting the SAP system

10.1 Connecting the SAP system with Content Server

After you installed and prepared the SAP system, you connect it to your Content
Server instance.

SAP
In your SAP system the HTTPS port must be open. Default port number in SAP
is 44300.

To find out the HTTPS port number on your system:

1. Start the SMICM transaction.

2. From the menu, select Goto > Parameters > Display.

For more information about the connection settings in the SAP system, see
“Performing post-installation tasks” on page 113.

10.2 Connecting the SAP system with OpenText™

Core Archive
Each archive must be created both in the SAP system and on the OpenText Archive
Center, using the same name.

To configure an HTTP content repository:

1. In IMG, run the OpenText Archiving and Document Access for SAP Solutions
> DesktopLink and Archiving for SAP Solutions > ArchiveLink > Maintain
Content Repositories activity. Alternatively, you can run the OAC0 transaction.
The Content Repositories overview table is displayed.
2. To switch to edit mode, click Display → Change.
3. To create a new content repository, click Create.
To modify an existing storage system, select it in the list and click Detail.
4. Click Full administration.
5. Enter the following parameters:

Content Rep.
Two-character archive name, which may only contain capital letters and
numbers. When you use a two-character name, you have the highest degree

EESPCD230200-IGD-EN-01 Installation Guide 53

Chapter 10 Connecting the SAP system

of compatibility for different archiving scenarios. For example, for KPro and
Data Archiving scenarios, you can use up to 30 characters. For pure
ArchiveLink scenarios, only two characters are allowed.
For the Extended ECM cloud installation, an archive A1 is provided by
default.
For Core Archive deployments, ArchiveLink documents should be stored in
an own collection/logical archive. A collection A2 is provided for this
purpose.
Description
Description of the archive, for example, indication of archive usage and the
Archive Center.
Document Area
For an ArchiveLink archive, enter ArchiveLink. For a KPro archive enter
the corresponding document area.
Storage type
HTTP Content Server

Protocol
Name of the protocol used for communication. For more information, see
Section 6.1.1.4 “Protocol” in OpenText Core Archive for SAP Solutions -
Scenario Guide (ER-CCL).
The OpenText protocols OT_* can be created manually as described in
OpenText Archiving and Document Access for SAP Solutions - Installation and
Upgrade Guide (ER-IGD). They are also available with transports that can be
downloaded from OpenText My Support (https://knowledge.opentext.com/
knowledge/cs.dll?func=ll&objId=15777379&objAction=browse).
Version no.
ArchiveLink interface or SAP Content Server HTTP Interface version 0045
is the minimum required version.
HTTP server
Name of the Server where AL filter is installed. Usually this is the host
where Content Server is installed, for example: otcs.example.com.
From SAP basis 6.20, the port no. is entered in a separate field.
Port Number
For HTTP connections, leave the port number empty for connections to the
cloud archive.
Port Number of ArchiveLink connection.
SSL Port Number
When using the secure transfer protocol SSL (Secure Socket Layer).
For HTTPS connections, enter the SSL port number 443.
Important
If you have an Extended ECM cloud installation, you must use the
secure transfer protocol SSL (Secure Socket Layer).

54 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 10.2. Connecting the SAP system with OpenText™ Core Archive

Program (CRM: HTTP Script)

The URI part of the URL to the AL Filter. Enter alfilter/archive.
Basic Path, Archive Path
Path to the exchange directories. For HTTP communication, the Archive
Center does not require access to this directory.
The SAP system server stores the documents to be archived on the basic
path. The Archive Center makes the documents requested by the SAP
system available on the archive path. For data archiving, the exchange
directory must be entered identically in the FILE or SARA transaction with
particular attention to upper/lower case. For more information, see Section
6.3 “Creating an exchange directory” in OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS)
Notes

• The basic path and the archive path are only displayed in Full
administration mode.
• The path must always be closed using a forward slash (/) on UNIX
platforms and a backslash (\) on Windows platforms:
\\<Host name>\<Share name>\<Exchange directory>\.

OutputDevice
Enter ARCH.
No signature
If you select this option, the URLs for this archive are transmitted without
encryption. When you disable this option, the URL is given a SecKey, in
which important data is encrypted. In the latter case, a certificate must be
sent from the SAP system to the Archive Center and the signature check
must be configured in the OpenText Administration Client (see the Section
8 “Configuring security settings” in OpenText Archive Center - Administration
Guide (AR-ACN)).

6. Click Save.

You can send a certificate from your SAP system directly to the content repository
defined here.

To send the certificate for your content repository:

1. Wait for the confirmation message that the archive is ready.

2. Click Send certificate.

Note: To send certificates centrally, use the oaht transaction.

EESPCD230200-IGD-EN-01 Installation Guide 55

Chapter 10 Connecting the SAP system

10.2.1 Creating an archive on the OpenText Archive Center

In Extended ECM for SAP SolutionsCloud the logical archive A1 is predefined by
default.

If you need more than one logical archive, please create a Service Request for your
OpenText Cloud Service Management.

56 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 11

Performing system administration tasks in Content

Server

After the actual installation of the module, you have to perform post-installation
tasks in Content Server.

11.1 Connecting SAP as the business application

To connect Content Server with an SAP system, you define connection parameters
on Content Server.

To connect a business application:

1. On the global menu, click Enterprise > Extended ECM, and then click
Connections to Business Applications (External Systems).

2. Click Add Item > Business Application.

3. Specify the parameters for your business application according to the list below.

4. Click Add.

Logical System Name

Define the logical name of the business application. The name must be unique. It
cannot be longer than 32 characters. This name is used when you select the
business application in the business object type configuration.
This name can be, for example, a combination of the SAP system and the client
IDs, or the tenant name of the SAP CX Sales Cloud and SAP CX Service Cloud
system. You can also use the SAP logical system name (as configured in
transaction SCC4). The convention for SAP logical system names is <system
ID>CLNT<client>.
Important

• You cannot change the name later.

• If you use S/4HANA Essential, the Logical System Name must be the
same name as the CMIS user. The name will also be used as the
repository name.

• If you use Business Scenarios, a business application with SAP S/4 HANA
as Logical System Name is already created. You can use this name for
the connection to your SAP system.

EESPCD230200-IGD-EN-01 Installation Guide 57

Chapter 11 Performing system administration tasks in Content Server

Connection Type
Select the adapter for your business application. If there is no special adapter for
your specific business application available, select Default WebService
Adapter.
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
Enter the common URL for accessing the business 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.
For example, https://r3d5g.example.com:44300
Application Server Endpoint
Specify the URL that will be called to obtain business object information.

Example 11-1: SAP

The following is an example for an SAP system: https://myhost.
example.com:44300/sap/bc/srt/xip/otx/ecmlinkservice/800/
ecmlinkspiservice/basicauthbinding

• https://myhost.example.com:44300: Common URL.

Port 8000 is the default HTTP port for SAP. For HTTPS the default port
is 44300.
• 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 use SSL at the web server. For information about importing
certificates to the keystore, see Section 23.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 in the
business application.

58 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.1. Connecting SAP as the business application

Important

• If the business application 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.

• If the business application is an SAP system of release S/4HANA 2022

or higher, in the SAP system you must also also assign the /OTX/RM_
CS_SAP_USER_S4 role to this user.

• If the business application is an SAP system and the following use case
applies, the user also needs to be assigned to a Content Server.
In the SAP system, customizing is active for selecting a template,
classification, or category based on business properties. To create or
update a Business Workspace in Content Server, the following
conditions have to be met:

– The connection to the business application is used.

– The unique names are defined in Content Server.

– The Content Server user who is assigned to this user needs reading
permission on the unique names.

– Based on the customizing, the property provider in the SAP system

needs to resolve one or more unique names.

For more information, see Section 3.4 “Selecting a template,

classification or category based on business properties” in OpenText
Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-
CGD).

Password
Specify the password of the defined user.

Test Connection
Click Test to perform a connection check to the specified business application.
After a successful check, the message Connection test was successful is
displayed next to the button. If the Test button is not active, you must first save
the configuration. To save the configuration, click Apply.

Note: You can only test the connection after you have configured the SPI
service in the business application accordingly and have saved the
configuration. For more information, see “Configuring the Service
Provider Interface service” on page 132.

Business Application Name

Enter localized names for the business application if required.

Repository root folder

For a CMIS integration, select the root folder of your CMIS document structure.

EESPCD230200-IGD-EN-01 Installation Guide 59

Chapter 11 Performing system administration tasks in Content Server

Figure 11-1: SAP as the connected business application

11.2 Setting permissions for root folders in Content

Server
If your setup does not include Enterprise Library, the root folder for the SAP system
in Content Server will be created upon first creation of a corresponding record. The
name of the root folder will be the ID of the SAP system. You need to set the
permissions for the folder in Content Server manually, for example, to avoid
unwanted access.

Therefore, OpenText recommends doing the following before any records are
created.

To set permissions for the root folder:

1. On the Content Server Administration page, click Extended Operations Roots.

2. Create a folder with name <SAP system ID>.

3. Click the button of the folder you just created, and then select the
Permissions.

4. Add users and groups that must have access to this volume.

60 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.3. Managing users and permissions

5. Grant full access to those users and groups that have to declare records within
SAP.

Note: If you choose to store records in Enterprise Workspace folders, set

the permissions 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.1.6 “SAP: Creating a document declaration” in
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

11.3 Managing users and permissions

Content Server users are provided by OpenText Directory Services (OTDS). In order
to access Content Server from an 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 SolutionsCloud,
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.

11.3.1 Setting up the authorization for records

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.

EESPCD230200-IGD-EN-01 Installation Guide 61

Chapter 11 Performing system administration tasks in Content Server

• To declare records, users must have at least Add Items permission.

Example 11-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

62 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.4. Configuring document template settings

access rights to the Finance classification and the HR group to the HR

classification.

11.4 Configuring document template settings

You must configure that the Content Server subtype for business workspaces
(subtype 848) can be used as a template.

To configure document template settings:

1. On the Content Server Administration page, click Document Templates

Administration > Configure Content Server Document Templates.

2. In the Managed object types section, click Configure and make sure that at
least the Business Workspace (subtype 848) item is configured.

3. For the Classification tree for document types, select a classification tree for
business workspaces.

4. Set the other options as required. For more information, see the Content Server
online help for that page.

EESPCD230200-IGD-EN-01 Installation Guide 63

Chapter 11 Performing system administration tasks in Content Server

11.5 Preparing the Content Server search for users

11.5.1 Creating a search slice for business workspaces
You can create search slices, which are filters that narrow down a search to criteria
you defined. For example, you can provide search slices for business workspaces or
even a certain workspace type. Users enter their search criteria and apply a search
slice.

To create a search slice for a certain workspace type:

1. Find the ID of the workspace type:

a. On global menu, click Enterprise > Business Workspaces.

b. Click Workspace Types and open one of the workspace types.
c. The URL in the browser’s address field now shows a string that contains
the parameter ID_CFG, for example, ReferenceTypeEdit&ID_CFG=1.
d. Make a note of the value, in this example, 1.

2. From the Content Server menu, select Tools > Search.

3. From the Look For list, select Complex Query. Then create a complex query
and specify as search criterion: XECMWkspLinkRefTypeID:<ID_CFG value>.

64 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.5. Preparing the Content Server search for users

4. Optionally, add more filter criteria.

5. Click Save as Slice and enter a name. The slice is saved to the Slice Folder.

6. Set the permissions for the created slice to make it available for the respective
users.

11.5.2 Indexing documents and other items with business

workspace attributes
Content Server items like documents, folders, or tasks in a business workspace
usually do not have the same categories and attributes as business workspaces. For
each workspace type, you can decide if items within a business workspace will be
indexed with the attributes of the business workspace. With the re-indexing feature
enabled, a search for attributes not only finds business workspaces but also the other
indexed items.

Attributes that were changed in the business workspace are propagated to the sub-
items to ensure clean data. Because of this feature as well as for performance reasons
you should prefer indexing over metadata inheritance in document templates.

You enable indexing for each business workspace type, and you select which items
are to be indexed. After changing the indexing setting, it may be necessary to re-
index documents.

EESPCD230200-IGD-EN-01 Installation Guide 65

Chapter 11 Performing system administration tasks in Content Server

To enable indexing and to select, which items to be indexed:

1. On the global menu, click Enterprise > Business Workspaces.

2. Click Workspace Types and edit a workspace type.

3. In the Indexing Settings section, select Enable the indexing of category

attributes .... Click Apply.

4. Click Configure indexable subtypes.

5. From the list of all available Content Server object types, select the object types
that you want to be indexed with metadata from the business workspace. A
typical list could contain the following:

• Folder
• Shortcut
• Generation
• URL
• Task List
• Task
• Email
• Document
• Business Workspace

To start the indexing process:

1. On the global menu, click Enterprise > Business Workspaces.

2. Click Workspace Types and open a workspace type.

3. Find a workspace type where the Indexing Status is Re-indexing required.

4. From the function menu of the workspace type, select Schedule for Re-
indexing.

5. Select Run in test mode without indexing to see how many documents need re-
indexing.

66 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.5. Preparing the Content Server search for users

Tip: Run the test mode first to estimate the impact of the indexing process
on Content Server performance.

6. To start the re-indexing, clear the Test run option and click Start.

EESPCD230200-IGD-EN-01 Installation Guide 67

Chapter 11 Performing system administration tasks in Content Server

The re-indexing process is scheduled. You can monitor the actual indexing
progress on the Content Server System page.
Click the respective link on the current window to go to Content Server
System, then click Enterprise Data Source Folder > Enterprise Data Flow
Manager. You can monitor the processing in the Interchange Pools section.

11.6 Configuring Smart View for Business

Workspaces
You have several ways to configure how a Business Workspace can appear in Smart
View.

68 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.6. Configuring Smart View for Business Workspaces

11.6.1 Creating a Perspective using the Perspective Manager

tool
Perspectives control how users see the layout of a business workspace in Content
Server Smart View. The Perspective Manager tool walks you through the creation,
design, and configuration of a Perspective.

With Business Workspaces, the Perspective Manager tool offers a reduced set of
options for Perspectives. For Business Workspaces, a new Perspective is tied to the
workspace type and already contains a sample layout:

The Header widget, an Overview tab with a Team widget and a Metadata widget,
and a Documents tab with the Node Browsing Table widget.

This topic only covers creating a Perspective for a business workspace. For more
information about the full functionality of Perspectives and the Perspective Manager
tool, see the help available in Perspective Manager.

Important
Changes in Perspectives take effect immediately. If you are unsure of your
changes, OpenText recommends that you create your Perspective on a test
system before implementing it on a production system.

Notes

• For systems with Extended ECM Documentum for SAP Solutions, OpenText
recommends that you create a new tab in the Perspective for D2 documents.
For example, you can name the tab as “Documents” and place the
Documentum D2 widget on it to show the Documentum view of the
workspace. For more information, see Section 9 “Extended ECM
Documentum for SAP Solutions Widget Group” in OpenText Content Server -
Widget Configuration Online Help (CSAV-H-CWG).
• In each business workspace, you can have only one Node Browsing Table
widget, regardless of how many tabs you have.
• When you transport Perspectives using the Transport Warehouse, you must
follow a certain order to keep dependencies. For more information, see
Section 4.4 “Transporting the configuration” in OpenText Business Workspaces
- Configuration Guide (CSCWS-CGD).

EESPCD230200-IGD-EN-01 Installation Guide 69

Chapter 11 Performing system administration tasks in Content Server

11.6.1.1 To create a workspace-type Perspective

To create a Perspective for a workspace type:

1. On the global menu, click Enterprise > Business Workspaces, click Workspace
Types, and then open a workspace type.

2. On the General tab, in the Perspective Manager section, click Manage

Perspectives for this workspace type.

3. In the Perspective Manager tool, on the General tab, click Create new, and then
enter a title for the Perspective.

4. Optional On the Rules tab, create logical rules to control when the Perspective
takes effect.

5. On the Configure tab, choose and configure the widgets for the workspace-type
Perspective.

• The widget library pane on the left contains widget groups from the installed
modules, such as the Business Workspaces widget group. You can expand a
widget group and then drag a widget to the working area.
• The working area in the middle allows you to place the widgets. When you
click on a widget in the working area, you can configure its features in the
options pane.
• The options pane on the right allows you to configure the options of the
selected widget.
• The tabs are configurable. You can create new tabs or edit them. Double-click
a tab name to rename it. To remove a tab, select another tab, and then drag
the tab, which you wanted to delete, out of the picture.

6. Click Create.

Notes

• Perspectives for Business Workspaces are stored in Perspectives volume

> Business Workspaces > <workspace_type_name_folder> where the folder
name changes to match the workspace type name.
• To edit a Perspective, open it in Perspective Manager, make the required
changes, and click Update.

70 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.6. Configuring Smart View for Business Workspaces

11.6.2 Configuring widgets for a Business Workspace

You can select widgets from the specified widget groups to add to a workspace-type
Perspective. Your system configuration determines which widgets are appropriate.

Note: Some widget parameters support multilingual text and are indicated
with a globe icon . When you click, a dialog opens with a text box for each
installed language.

Business The Business Workspaces widget group includes several widgets that you
Workspaces can use in a Business Workspace. For information about how to configure
widget group these Business Workspaces widgets, see Section 2 “Business Workspaces
Widget Group” in OpenText Content Server - Widget Configuration Online
Help (CSAV-H-CWG).
• Header widget
• Related Workspaces widget
• Team widget
• Metadata widget
• Workspaces widget
• Configuration Volume widget

Communities The Communities widget group includes the Discussion widget that you
widget group can use in a Business Workspace. For information about how to configure
the Discussion widget, see Section 5 “Communities Widget Group” in
OpenText Content Server - Widget Configuration Online Help (CSAV-H-
CWG).
Extended ECM The Extended ECM Platform widget group includes several widgets that
Platform you can use in a Business Workspace. For information about how to
widget group configure the File upload widget, see Section 13 “Extended ECM Platform
Widget Group” in OpenText Content Server - Widget Configuration Online
Help (CSAV-H-CWG).
• Business Attachments widget
• Dossier widget
• File upload widget
• Scan barcode widget

Extended ECM The Extended ECM Documentum for SAP Solutions widget group
Documentum includes two widgets that you can use in a Business Workspace.
for SAP
• Documentum D2 widget
Solutions
widget group • Permissions in D2 widget

For more information on the these widgets, see Section 9 “Extended ECM
Documentum for SAP Solutions Widget Group” in OpenText Content
Server - Widget Configuration Online Help (CSAV-H-CWG).

EESPCD230200-IGD-EN-01 Installation Guide 71

Chapter 11 Performing system administration tasks in Content Server

11.6.3 Adding your own logo to Content Server Smart View

In Smart View, a logo is displayed after installation. By default, this is the Content
Server logo. You can also choose to display the OpenText Extended ECM logo, or
you show your own logo. A small CSS file is delivered with Extended ECM, which
contains the instruction to display a logo. The CSS file must be propagated in the
Content Server administration. For best results, the graphic file should be in SVG
format.

You need administrator’s access to Content Server.

To change the Extended ECM logo:

With the installation of Extended ECM, a logo and the overrides.css are already
on your system. The override.css file is located in the <Content Server home/
support/xecmpf> folder. You need to change the filename, edit the CSS file and
propagate it.

1. Copy the overrides.css file and name it, for example, my-overrides.css.

2. Open the my-overrides.css file in an editor. Change the graphic file name in
the background-image parameter:
.binf-navbar .binf-navbar-brand > .csui-logo > .csui-logo-image {
background-image: url(header_extended_ecm-inv.svg);
background-repeat: no-repeat;
background-size: 266px, 86px;
height: 43px;
width: 266px;
}

/* Move company logo to the left */

.binf-navbar .binf-navbar-brand .csui-logo {
position: fixed;
left: 40%;
}

You have the following options:

• Select from the standard Extended ECM logos:

– header_extended_ecm.svg

72 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.7. Configuring the display of documents in the side-panel

– header_extended_ecm_inv.svg
• Use your own graphic file. If you use your own graphic file, you copy it to
the support directory <Content Server home/support/xecmpf>. If you
store it in a different folder, you must provide the correct path in the CSS
description.

3. Propagate the my-overrides.css in Content Server:

a. On the Content Server Administration page, select Core System – Server

Configuration > Smart View.
b. In the Overriding Default Style section, enter the path to your overrides.
css.
If you are using IIS as web server, the support folder on Content Server is
mapped to the img folder.

• Storage location: C:\OPENTEXT\support\overrides.css

• URL path: /img/overrides.css

11.7 Configuring the display of documents in the

side-panel
With OpenText Viewing, users can view documents within the business workspace
in a side panel. You can configure, with which function the viewing is invoked.
Either when clicking the document name or the View icon in the functions list.

To configure the viewing behavior:

1. On the Content Server Administration page, select Core System - Server

Configuration > Presentation > Configure Document Functions.

2. Do one of the following:

• Click Enable Document Overview Pages to open the document viewer

when clicking the View icon.
• Leave the Enable Document Overview Pages option clear to open the
viewer by clicking the document link.

EESPCD230200-IGD-EN-01 Installation Guide 73

Chapter 11 Performing system administration tasks in Content Server

11.8 Configure how document viewing behaves with

Web Viewer
Users of classic view can add notes and annotations to business workspace
documents using Web Viewer. The Open link option, from the document context
menu will allow users to invoke the Imaging Web Viewer. Any note and annotation
that is created from here will be stored in Archive Center.

Note: Business workspace documents will not receive the View Document
option, even if the Review and Notes module is installed.

You can configure the Open Link option to be the default viewing method. For
more information, see Section 6.3 “Integrating in Content Server” in OpenText
Imaging Web Viewer - Installation and Configuration Guide (CLWEBV-IGD).

Users of smart view can work with ArchiveLink documents using Web Viewer and
can access notes and annotations for these documents. For non-ArchiveLink
documents, in business workspaces, users can use Content Suite Viewer, OpenText
Viewing or OpenText Intelligent Viewing (licensed version), whichever is
configured and available.

11.9 Providing the online help

Content Server Help is delivered in two forms:

Online help
Some of the help in Content Server is built-in: It is delivered as online help that
is included in the Content Server application directory. Content Server online
help is updated when you apply a Content Server Update, or when you upgrade
Content Server.
OpenText Global Help Server help
Help for the Content Server Smart View, and for certain products such as
Perspective Manager and Business Workspaces is delivered as OpenText Global
Help Server help, which is available over the Internet. Global Help Server help is
updated by OpenText. Updates can occur at any time without requiring any
action on your part. However, if your organization restricts access to the public
Internet, you may need to implement the OpenText Private Help Server: a local
installation of the Global Help Server. For more information, see “Providing the
online help on a local help server (Private Help Server)” on page 75.

74 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.9. Providing the online help

11.9.1 Providing the online help on a local help server (Private

Help Server)
The online help for this module is delivered using the OpenText Global Help Server
(GHS) system, which provides your users with live access to the latest version of the
help. If you cannot use the GHS system, for example, if your site does not have
Internet access, you can install the OpenText Private Help Server (PHS), a local
version of the help system that can host your OpenText online help on your
organization’s network. After the PHS is installed, you can then configure your
OpenText module(s) to forward all online help requests to your PHS. For detailed
information about installing the PHS, see OpenText Help System - Private Help Server
Administration Guide (OTHS-AGD).

Notes

• The Private Help Server can support multiple OpenText modules. If the
Private Help Server has already been installed within your organization to
support another OpenText module, you can add additional OpenText
module online helps to that installation.

• If you are replacing a previous PHS installation, see Section 2.5 “Updating a
Private Help Server installation” in OpenText Help System - Private Help Server
Administration Guide (OTHS-AGD).

• If the server you want to use for the PHS installation cannot connect to the
Internet, see Section 1.1 “Deploying online help files in a secure environment
(no Internet)” in OpenText Help System - Private Help Server Administration
Guide (OTHS-AGD).

Once the PHS is installed or upgraded, you can use its Online Help Deployer to
download online helps from the GHS system by entering the help deployment codes
listed below. For more information about using the codes, see Section 3 “Adding
product online help to the Private Help Server” in OpenText Help System - Private
Help Server Administration Guide (OTHS-AGD).

Table 11-1: Help deployment codes

Code Product
EESPCD230200-IGD OpenText™ Extended ECM for SAP®
Solutions Cloud CE 23.2

Note: This section applies only to the OpenText Global Help Server help,
which is available over the Internet.

For information about the built-in online help that is included in the Content
Server application directory, see Section 7.5 “Set Up the Help Environment” in
OpenText Extended ECM - Installation Guide (LLESCOR-IGD).

EESPCD230200-IGD-EN-01 Installation Guide 75

Chapter 11 Performing system administration tasks in Content Server

To have your Content Server installation call the help topics on your Private Help
Server, set the URL Root of your Private Help Server on the Configure Smart View
administration page.

To configure Content Server to use the Private Help Server:

1. On the Content Server Administration page, in the Server Configuration

section, click Configure Smart View.

2. On the Configure Smart View page, enter the base URL of your Private Help
Server in the URL Root box:
http://<Private_Help_Server>:<port>/OTHelpServer/mapperpi

Example: http://tomcat.example.com:8080/OTHelpServer/mapperpi

3. In the Type box, enter ofh1.

4. In the Tenant box, enter a custom help tenant value.

5. Click Save Changes.

11.10 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.

11.10.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
SolutionsCloud. For more information, see OpenText Classifications - Resource Guide
(LLESCLS-GGD).

11.11 Enabling OpenText Recycle Bin for business

workspaces
You can make use of the Content Server Recycle Bin module for business
workspaces. When users delete a business workspace, the workspace reference is
removed, and the business workspace is moved to the Recycle Bin. The business
workspace is no longer connected to a business object, and the original business
object can be used for another business workspace. In addition, all relationships
from or to this business workspace are removed.

When the business workspace is restored from the Recycle Bin, it is not re-connected
to the original business object. Users must manually assign a business object as
workspace reference again.

76 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.12. Checking the appearance of the SAP integration

The object types Business Workspaces (848) and Related Business Workspace (854)
are mandatory restorable object. This means, that they are always restorable and
cannot configured otherwise.

Prerequisite OpenText Recycle Bin must be installed on Content Server.

To enable the Recycle Bin:

1. On the Content Server Administration page, click Core System – Feature

Configuration > Recycle Bin.

2. Select Enable Recycle Bin and click Save Changes.

11.12 Checking the appearance of the SAP integration

If you want to integrate the Extended ECM for SAP SolutionsCloud functionality in
SAP CRM or SAP SRM, you can adjust the Content Server appearance and use an
SAP based skin. As a standard, these settings are made automatically during the
installation of Business Workspaces

After installation, unique names for standard SAP themes already exist. You can edit
these unique names and their assignment. Changes take effect immediately. The
following SAP themes are already configured: content_server, default, sap_
tradeshow, sap_tradeshow_plus. Unique names for appearances must use the
prefix theme_ and they are always expected in lower-case, even if SAP sends the
parameter in upper-case. For more information, see Section 3.15 “Creating unique
names for Content Server items” in OpenText Extended ECM for SAP Solutions -
Customizing Guide (ERLK-CGD).

To check the appearance integration:

1. On the Content Server Administration page, click Appearances

Administration > Open the Appearances Volume.

2. Select the recommended appearance:

For SAP CRM: EXTENDED_ECM_CRM_DEFAULT
For SAP SRM: EXTENDED_ECM_SRM_SAP_TRADESHOW

3. Check if the following settings are present according to Figure 11-2 or

Figure 11-3.

EESPCD230200-IGD-EN-01 Installation Guide 77

Chapter 11 Performing system administration tasks in Content Server

• Current Status: Enabled

• Header section
• Content Server Components section
• Workspace section

Figure 11-2: Appearance settings for SAP CRM

Header script for EXTENDED_ECM_CRM_DEFAULT –

<SCRIPT ID="crm_default" TYPE="text/javascript"></SCRIPT>
<LINK ID="crm_default_css" REL="stylesheet" TYPE="text/css"/></LINK>
<SCRIPT TYPE="text/javascript">
document.getElementById("crm_default").src = supportPath + 'xecmpf/crm_default/
crm_default.js';
document.getElementById("crm_default_css").href = supportPath + 'xecmpf/
crm_default/crm_default_style.css';
document.getElementsByTagName('body').className+=' preventFlicker';
var trunc_type = '_848';
</SCRIPT>
<STYLE>
#pw_SideBarWrapper {display: none;}
</STYLE>

78 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.12. Checking the appearance of the SAP integration

Figure 11-3: Appearance settings for SAP SRM

Header script for EXTENDED_ECM_SRM_SAP_TRADESHOW –

<SCRIPT ID="srm_sap_tradeshow" TYPE="text/javascript"></SCRIPT>
<LINK ID="srm_sap_tradeshow_css" REL="stylesheet" TYPE="text/css"/></LINK>
<SCRIPT TYPE="text/javascript">
document.getElementById("srm_sap_tradeshow").src = supportPath + 'xecmpf/
srm_sap_tradeshow/srm_sap_tradeshow.js';
document.getElementById("srm_sap_tradeshow_css").href = supportPath + 'xecmpf/
srm_sap_tradeshow/srm_sap_tradeshow_style.css';
document.getElementsByTagName('body').className+=' preventFlicker';
var trunc_type = '_848';
</SCRIPT>

These settings will turn off certain standard Content Server UI components such
as header and footer; an additional JavaScript will be added to the appearance
to manipulate the breadcrumb navigation.

EESPCD230200-IGD-EN-01 Installation Guide 79

Chapter 11 Performing system administration tasks in Content Server

11.13 Allowing users to save Outlook emails to

business workspaces
You can install the Business Workspaces Outlook add-in in Microsoft Exchange or
Microsoft Exchange Online if you want to allow users to save emails from Microsoft
Outlook to business workspaces.

By default, the add-in allows users to browse to and search for business workspaces
and select a folder in which to save an email. If needed, you can also force users to
save emails to a specific regular folder or Email folder in a business workspace.

Tip: For more information about Outlook add-ins, see Add-ins for Outlook
(https://technet.microsoft.com/EN-US/library/jj943753(v=exchg.150).aspx).

Note: You need system administrator rights in Content Server and access to
the file system to configure this feature. Please ask OpenText Professional
Services for assistance.

11.13.1 Installing and upgrading the Business Workspaces

Outlook add-in
You must use an Outlook add-in manifest file to install or upgrade the Business
Workspaces Outlook add-in in Microsoft Exchange or Microsoft Exchange Online.

You must download the latest manifest file for the Business Workspaces Outlook
add-in from the Content Server system you want to use to store emails. During the
download process, information about that Content Server system is saved to the
manifest file. You can then use the downloaded manifest file to install or upgrade
the add-in in Microsoft Exchange or Microsoft Exchange Online.

When users subsequently open the add-in in Outlook, the add-in automatically
connects to the Content Server system you used to download the manifest file.

If you upgrade the Business Workspaces Outlook add-in, downloading the manifest
file, as documented in “To download the latest Outlook add-in manifest file:
“ on page 81, allows you to see all functionality of the upgraded module.

Tips

• If you previously installed the Business Workspaces Outlook add-in, you

can optionally upgrade the add-in whenever a new version of the Business
Workspaces Outlook add-in manifest file is available. For more
information, see the Release Notes.
As stated above, if you upgrade the add-in, and you fail to download the
most recent manifest file, you may not see the new functionality in your
upgraded add-in.

80 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

• For more information about Outlook add-in manifest files, see Outlook
add-in manifests (https://dev.office.com/docs/add-ins/outlook/manifests/
manifests?product=outlook).

Note: You must use the manifest file you downloaded to install the Business
Workspaces Outlook add-in in Microsoft Exchange or Microsoft Exchange
Online. During the installation process, when you are prompted to select the
location from which to install the add-in, select Add from file and then select
the manifest file you downloaded.

For more information, see Install or remove add-ins for Outlook for your
organization (https://technet.microsoft.com/en-us/library/
jj943752(v=exchg.150).aspx).

11.13.1.1 Preparing to install or upgrade the Business Workspaces

Outlook add-in
Before installing or upgrading the Business Workspaces Outlook add-in, confirm
that Content Server is mapped to a web server that has HTTPS enabled.

For more information about configuring a web server for Content Server, see
OpenText Extended ECM - Installation Guide (LLESCOR-IGD).

11.13.1.2 Downloading the latest Outlook add-in manifest file

To download the latest Outlook add-in manifest file:

1. On the Content Server system you want to use to store emails, browse to the
Content Server Administration page, and click Business Workspaces > Set up
Outlook Add-in.

2. On the Set up Outlook Add-in page, in the Outlook Add-in Manifest File area,
do the following:

a. The File name field cannot be edited. This field contains the filename of the
manifest file, BusinessWorkspace.Manifest.xml.

b. The File version field cannot be edited. It displays the Outlook add-in
manifest file version that is available to be downloaded.

c. In the Content Server URL field, confirm that the value in this field
displays the URL for the Content Server system you want to use. The URL
must start with https.
By default, the URL of your current Content Server system is pre-populated
in this field. In most cases, you can keep the default URL. However, you
can edit the URL if, for example, the pre-populated URL does not contain
the correct protocol value or if your Content Server system requires a
different URL for external access.

EESPCD230200-IGD-EN-01 Installation Guide 81

Chapter 11 Performing system administration tasks in Content Server

Notes

• If the pre-populated URL starts with http, you must map Content
Server to a web server that has HTTPS enabled. You must then
confirm that the new URL, that starts with https, appears in the
Outlook Add-in Manifest File area.
• If you edit the URL, and you are using a port other than 443 for
HTTPS connections, you must add your server port number to the
URL. For example, if you are using port 4430 for HTTPS
connections, the URL must have the following form:
https://MyHost.example.com:4430

3. Click Download.

4. When prompted, save the BusinessWorkspace.Manifest.xml file to your local

computer.

11.13.1.3 Migrating custom settings to the new Outlook add-in manifest file
If you are upgrading the Business Workspaces Outlook add-in, you must migrate
settings from your old manifest file to the new manifest file you downloaded if you
previously edited your old manifest file to add custom settings, for example, image
URLs.

Note: If you did not add custom settings to your old manifest file, you can skip
this task.

To migrate custom add-in settings to the new Outlook add-in manifest file:

1. In a text editor, open the new BusinessWorkspace.Manifest.xml manifest file

you downloaded.

2. From your old manifest file, copy the custom settings you want to migrate and
paste them to the corresponding locations in the new manifest file.

3. Save your changes in the new manifest file.

11.13.1.4 Uploading the Outlook add-in manifest file

To install or upgrade the Business Workspaces Outlook add-in, you must upload the
Outlook add-in manifest file you downloaded in Microsoft 365 admin center.

Tip: For more information about installing Outlook add-ins, see Install or
remove add-ins for Outlook for your organization (https://
technet.microsoft.com/en-us/library/jj943752(v=exchg.150).aspx).

To upload the Outlook add-in manifest file:

1. In Microsoft 365 admin center, open the Services & add-ins page.

2. Click Deploy Add-in and click Next.

82 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

3. Click Upload custom apps.

4. Select I have a manifest file (.xml) on this device and click Choose File to select
the BusinessWorkspace.Manifest.xml file you downloaded.

11.13.2 Preparing your environment

Before configuring the add-in, complete the following tasks:

1. Create and configure the business workspaces and folders in which you want
users to save emails. For more information about the types of folders you can
create and the guidelines for creating the folders, see “Creating Content Server
folders for the add-in” on page 83.

2. Grant users the Add Items permission, or higher, on the business workspaces to
which they will save emails.

3. Optionally, if you want users to specify metadata values when saving emails to
folders, assign any of the following categories to those folders:

• Categories with required attributes.

• Categories with required security clearance levels.

• Categories with required supplemental markings.

a. Security clearance levels and supplemental markings apply only if you

are using the OpenText Security Clearance module in Content Server.
For more information, see OpenText Content Server - Security Clearance
(LLESRCS-H-UGD).

b. Do not assign categories that contain attribute sets with multiple rows
to folders. If you assign this type of category to a folder, users will not
be able to specify metadata values in all of the fields within the
attribute set.

4. Optionally, add one or more search forms to the Search Forms folder in the
Business Workspaces volume. For more information, see “Creating search forms
for the add-in” on page 85.

11.13.2.1 Creating Content Server folders for the add-in

When you configure the add-in, you can choose to allow users to browse to, and
then select, folders in which to save emails, or you can force users to save emails to a
specific folder. For more information, see “Configuring add-in settings” on page 86.

You must create one or more regular or Email folders in each business workspace
based on the functionality you plan to configure.

EESPCD230200-IGD-EN-01 Installation Guide 83

Chapter 11 Performing system administration tasks in Content Server

Guidelines for creating regular folders

• If you plan to allow users to browse to, and then select, folders in which to
save emails, you can create as many regular folders as you want in each
business workspace.
• If you plan to force users to save emails to a specific, regular folder, you must
create an instance of the same folder in each business workspace. The
spelling and capitalization of each folder instance must match in all of the
business workspaces.

Example: If you want to allow users to save emails to a business workspace called
BW1, and also save emails to a second business workspace called BW2, create a regular
folder called Email communication in BW1, and a separate folder with the same name
in BW2.

Guidelines for creating Email folders

• If you plan to allow users to browse to, and then select, folders in which to
save emails, you can create as many Email folders as you want in each
business workspace.
• If you plan to force users to save emails to a specific Email folder, you must
create an Email folder in each business workspace. You can choose to create
an Email folder with a different name in each business workspace or create
an instance of the same Email folder in each business workspace.
If you create an Email folder with a different name in each business
workspace, each folder that you create must be the first Email folder that
appears alphabetically in each business workspace. When a business
workspace has multiple Email folders, emails are saved only to the first
Email folder that appears alphabetically in that business workspace.
If you create an instance of the same Email folder in each business
workspace, the spelling and capitalization of each folder instance must
match in all of the business workspaces.

Tip: Regular folders and Email folders are specific types of folders that you can
create in Content Server. For more information about each folder type, see
Section 4.7 “Adding and Configuring Folders” in OpenText Content Server - Get
Started (LLESRT-H-UGD).

84 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

11.13.2.2 Creating search forms for the add-in

The Business Workspaces Outlook add-in provides custom search functionality,
which allows users to search for business workspaces based on search forms you
create in Content Server. By default, the search forms in the Saved Queries volume
are displayed in the Select a search form list in the add-in. Users can select a search
form from this list, and then use the fields within that form to search for a business
workspace in which to save an email.

If you want to display a different set of search forms in the Select a search form list,
you can add search forms, or shortcuts that point to search forms, to the Search
Forms folder in the Business Workspaces volume. You must also configure each
search form as a custom view search.

1. For more information about creating search forms and configuring them as
custom view searches, see Section 3.13.4 “Classic View: Configuring a
simple search” in OpenText Business Workspaces - Configuration Guide
(CSCWS-CGD).
2. If you do not want to make search forms available to users, you can hide
the Custom search button from the add-in. For more information, see
“Configuring add-in settings” on page 86.

To access the Search Forms folder:

1. On the global menu, click Enterprise > Business Workspaces.

2. Click Outlook Add-in Configuration, and then click Search Forms.

To add a search form to the Select a search form list:

1. Do one of the following:

• Create a search form in the Search Forms folder. Browse to the Search
Forms folder, click Search on the Tools menu, and then configure the search
fields for the form.
• Create a search form in any other Content Server location, and then add a
shortcut that points to that search form in the Search Forms folder.

Tip: When you create a search form, consider setting its Content Type
system attribute to Business Workspace. When this attribute is set, only
business workspaces are returned in the search results.

2. Configure the search form as a custom view search. On the Make Custom View
Search page of the search form, select the Show check box for one or more
search fields, and then click Save.

To remove a search form from the Select a search form list:

1. Browse to the Search Forms folder.

EESPCD230200-IGD-EN-01 Installation Guide 85

Chapter 11 Performing system administration tasks in Content Server

2. Remove a search form or shortcut from the folder, for example, delete the item
from the folder or move it to a different location outside of the folder. The
corresponding search form is removed from the Select a search form list in the
add-in.

11.13.3 Configuring add-in settings

On the Configure Outlook Add-in administration page in Content Server, you must
specify the name of each Microsoft Exchange Server system that will be used to save
emails in the Trusted Exchange Servers area. You can also use this page to configure
add-in settings in Content Server, for example, in the Email Saving Options area.

Before Outlook Add-in version 20.3, single sign-on (SSO) was disabled by default.
Beginning with version 20.3, for new installations, SSO is enabled by default. You
can change this setting in Step 6. Single sign-on requires configuration, the
instructions can be found in Section 3.15.5 “Configuring your environment for SSO
authentication” in OpenText Business Workspaces - Configuration Guide (CSCWS-CGD).

To configure add-in settings:

1. On the global menu, click Enterprise > Business Workspaces, and then click
Outlook Add-in Configuration.
2. On the Outlook Add-in Configuration page, click General Configuration. On
the Configure Outlook Add-in page, do the following:
3. In the Email Saving Options area, if you want to specify the folders and folder
types to which users can save emails, do the following options:

a. Optional If you want to allow users to expand business workspaces in the

add-in, select Allow users to expand workspaces and browse workspace
folders. You must select this box if you want to allow users to browse the
folder structure and select a folder in which to save an email. This box is
selected by default.
Clear this box if you want to prevent users from expanding business
workspaces. If you clear this box, you must select and configure the Save
emails to a pre-configured folder option in Step 3.b instead.
If you select this box, you can also choose the following:

• In addition, if you want to restrict users, so that they can only save
emails to Email folders, select Save emails only to email folders. Clear
this box if you want to allow users to save emails to any type of folder.
This box is cleared by default.
When this box is selected, the Save icon appears only when users place
their pointer on Email folders in the add-in. When this box is cleared,
the Save icon appears when users place their pointer on any type of
folder in the add-in.
b. Optional If you want users to save emails to a specific folder in a business
workspace, select Save emails to a pre-configured folder. This box is
cleared by default.

86 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

Clear this box if you want to allow users to save emails to any folder in a
business workspace. If you clear this box, you must select and configure the
Allow users to expand workspaces and browse workspace folders option
in Step 3.a instead.
If you select this box, you must choose one of the following options:

• If you want users to save emails to the first Email folder that appears
alphabetically in a business workspace, select Save emails to the first
email folder in the workspace.
You can use this option if, for example, you want to allow users to save
emails to Email folders with different names in each business
workspace (for example, an Email folder called MyFolder in one
business workspace and an Email folder called Communication in
another business workspace).
If you select this option, you must create an Email folder in each
business workspace that users can access in Content Server. Each folder
you create must be the first Email folder that appears alphabetically in
each business workspace.
• If you want users to save emails to the workspace root folder, select
Save emails to the workspace root folder. For information about the
workspace root folder, see Section 1.11 “Creating a root folder for the
business workspaces” in OpenText Content Server User Online Help -
Business Workspaces (LLESCWS-H-UGD).
• If you want users to save emails to a specific regular folder or Email
folder, select Save emails to the following workspace folder. You can
use this option if, for example, you want users to save emails to a
specific folder that has the same name in each business workspace.
If you select this option, in the associated box, you must specify the
name of the folder to which users will save the emails. You must also
create an instance of the folder in each business workspace that users
can access in Content Server.

1. You cannot specify a subfolder name. You must specify the

name of a folder that has been created directly in a business
workspace.
2. The specified folder name applies to all business workspaces
that users can access in Content Server.
For example, if you specify the folder name Folder1, users can
save emails only to a folder called Folder1 in each business
workspace. In this scenario, if you want to allow users to save
emails to multiple business workspaces, you must create a
folder called Folder1 in each business workspace.

Tip: For examples of how to configure email saving options, see

“Examples: Configuring email saving options” on page 88.

EESPCD230200-IGD-EN-01 Installation Guide 87

Chapter 11 Performing system administration tasks in Content Server

4. In the Page Size area, specify the number of items that are displayed from
business workspaces and folders at a time. By default, this value is 10.

5. Optional In the Search Forms area, select Show custom search section if you
want to make search forms available to users in the add-in.
By default, this option is selected, and users can use search forms to search for
business workspaces. You can specify which search forms are available in the
add-in. For more information, see “Creating search forms for the add-in”
on page 85.
When this option is cleared, the Custom search button is hidden from the add-
in and users can search for business workspaces only by name and type.

6. Optional In the Single Sign-on area, clear Enable if you do not want the add-in to
use single sign-on (SSO) authentication to access Content Server. By default, this
option is selected and SSO authentication is used.
You must configure your environment for SSO authentication. For more
information, see Section 3.15.5 “Configuring your environment for SSO
authentication” in OpenText Business Workspaces - Configuration Guide (CSCWS-
CGD). If your environment is not configured for SSO authentication, users will
still be able to sign in, although the sign-in time will be delayed.

7. In the Trusted Exchange Servers area, specify the name of each Exchange
Server system that will be used to save emails. Users will be permitted to save
emails only from the Exchange Server systems you add to this list.
You must specify each Exchange Server name on a separate line. By default, the
Office 365 Exchange Server name, outlook.office365.com, appears in the list.

8. Click Save Changes.

11.13.3.1 Examples: Configuring email saving options

The following examples list the folders and settings needed to configure email
saving options in different scenarios. For more information about configuring email
saving options, see “Configuring add-in settings” on page 86.

Example 11-3: Allowing users to select folders to save emails

In this example, users can browse to and select any folder in which to save
emails. The Save icon appears whenever users place their pointer on any folder
in any business workspace.

Folders to create
Any number of regular folders or Email folders in each business
workspace.

Email saving options to configure

1. Select Allow users to expand workspaces and browse workspace
folders.

88 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

2. Clear all other email saving options.

Example 11-4: Requiring users to save emails to a specific Email folder

In this example, users are not permitted to expand business workspaces to

browse the folder structure. The Save icon appears whenever users place their
pointer on a business workspace. Clicking this icon saves an email to the first
Email folder that appears alphabetically in the business workspace.

Folders to create
An Email folder in each business workspace. Each folder can have a
different name in each business workspace. Make sure that each folder you
create is the first Email folder that appears alphabetically in each business
workspace.
Email saving options to configure
1. Clear Allow users to expand workspaces and browse workspace
folders.
2. Select Save emails to a pre-configured folder.
3. Select Save emails to the first email folder in the workspace.

Example 11-5: Allowing users to choose an Email folder to save emails

In this example, users can expand business workspaces to browse the folder
structure; however, they are permitted to save emails only to Email folders. The
Save icon appears whenever users place their pointer on an Email folder. The
Save icon does not appear when users place their pointer on regular folders.

Folders to create
Any number of Email folders in each business workspace.
Email saving options to configure
1. Select Allow users to expand workspaces and browse workspace
folders.
2. Select Save emails only to email folders.
3. Clear Save emails to a pre-configured folder.

Example 11-6: Requiring users to save emails to a specific regular folder

In this example, users are not permitted to expand business workspaces to

browse the folder structure. The Save icon appears whenever users place their

EESPCD230200-IGD-EN-01 Installation Guide 89

Chapter 11 Performing system administration tasks in Content Server

pointer on a business workspace. Clicking this icon saves an email to a regular

folder called Folder1.

Folders to create
An instance of a regular folder called Folder1 in each business workspace.
Email saving options to configure
1. Clear the Allow users to expand workspaces and browse workspace
folders option.
2. Select Save emails to a pre-configured folder.
3. Select Save emails to the following workspace folder, and then specify
Folder1 as the name of the folder to which users can save emails.

Example 11-7: Requiring users to save emails to the workspace root

folder

In this example, users are not permitted to expand business workspaces to

browse the folder structure. The Save icon appears whenever users place their
pointer on the workspace root folder. Clicking this icon saves email to the
workspace root folder.

Folders to create
You do not need to create any folders. You need to designate the
workspace root folder. For more information, see Section 1.11 “Creating a
root folder for the business workspaces” in OpenText Content Server User
Online Help - Business Workspaces (LLESCWS-H-UGD).
Email saving options to configure
1. Clear the Allow users to expand workspaces and browse workspace
folders option.
2. Select Save emails to a pre-configured folder.
3. Select Save emails to the workspace root folder.

90 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

11.13.4 Configuring rules and email search settings to display

suggested workspaces
You can configure rules and email search settings to control which business
workspaces are more likely to appear in the Suggested workspaces list in the
Business Workspaces Outlook add-in.

Whenever a user opens the add-in to save an email, the add-in performs the
following steps to determine which business workspaces to display in the Suggested
workspaces list:

1. The add-in uses the rules you configured to search for business workspaces
based on whether the email that is open contains a specific term or pattern in one
of its properties, for example, its subject line.
2. The add-in uses the email search settings you configured to search for business
workspaces containing emails that have the same sender and similar recipients
as the email that is open.
3. After performing both search processes, the add-in assigns the numeric weight
values that are specified within the rules and email search settings to each
business workspace. An overall weight value is calculated for each business
workspace based on the combined results of both search processes.

The business workspaces that have the highest overall weight values are then
displayed in the Suggested workspaces list. By default, up to five business
workspaces can appear in the list.

For more information about how the add-in performs each of these steps, see
“Understanding how rules and email search settings are applied” on page 91.

11.13.4.1 Understanding how rules and email search settings are applied
You can configure rules and email search settings on the Suggested Workspaces
Configuration page in the Business Workspaces volume. For more information, see
“Configuring Rules and Email Search Settings” on page 94.

Whenever a user opens the add-in to save an email, the following actions take place:

1. The add-in uses each rule that you configured to search for business workspaces.
When a rule is applied, the following actions take place:
a. The add-in uses the Matching Condition pattern and email property
specified within the rule to determine whether to apply the rule to the email
that is open. Specifically, the add-in checks whether the email property in the
opened email contains the pattern.

Example: If you specify the regular expression order[\s]\d+ as the Matching

Condition pattern, and then you select Subject as the email property to search, the
add-in searches for the term order followed by a space and any combination of
numbers in the subject line of the opened email.

EESPCD230200-IGD-EN-01 Installation Guide 91

Chapter 11 Performing system administration tasks in Content Server

b. If the email that is open contains that pattern, the add-in searches for
business workspaces based on the Workspace Type value and Extraction
Term pattern specified within the rule.
The add-in uses the Extraction Term pattern to extract a value from the
email property you specified within the rule, and then uses the extracted
value to search for business workspaces by name.

Example: If you specify the regular expression order[\s](\d+) as the Extraction

Term pattern, and then you select Subject as the email property to search, the add-in
extracts the number that appears after the word order from the subject line of the
opened email.
For example, if the subject line of the email is order 1234, the add-in extracts the
value 1234. The add-in then searches for business workspace names that contain
1234.

c. The add-in retrieves business workspaces based on the Workspace Type

value specified within the rule and whether the business workspace names
contain the value that was extracted from the email property.

Example: If you select Order as the Workspace Type value, and if the Extraction
Term pattern extracts 1234 from the email property, the add-in retrieves all business
workspaces that have the type Order, and have names that contain 1234.

d. The add-in assigns a numeric weight value to each business workspace that
is retrieved. These weight values are added to the overall weight value of
each business workspace.
By default, the Default Weight value specified on the Workspace Rules tab
is assigned to each business workspace that is retrieved.

Example: If the Default Weight value is set to 20, a value of 20 is assigned to the
overall weight value of each business workspace that is retrieved.

However, if a Weight value is specified within the rule itself, the Weight
value overrides the Default Weight value.

Example: If you set the Weight value to 100, but set the Default Weight value to 20,
a weight value of 100 is assigned to each business workspace that is retrieved by that
rule specifically.

2. The add-in then uses email search settings you configured to search for relevant
emails. The following actions take place:
a. The add-in searches within all business workspaces to find previously stored
emails that contain the same sender or similar recipients as the email that is
open. In the email search settings, you can specify whether the add-in
performs searches based on the sender, recipients, or both.

Example: If you configured the add-in to perform searches based on both the sender
and recipients, and if the email that is open lists [email protected] as the sender
and [email protected] as a recipient, all previously stored emails that list
[email protected] as the sender or [email protected] as a recipient are
returned in the search results.

92 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

b. When such emails are found, the emails are sorted based on the Sort Emails
by option specified in the email search settings. For example, you can sort
the emails based on their last modified dates.
c. The add-in retrieves emails from the top of the sorted set. The add-in
retrieves a maximum of 50 emails and any emails that appear after the first
50 emails are excluded from the set of retrieved emails.
d. The add-in assigns a numeric weight value to each business workspace that
contains emails that were retrieved in the previous step. The weight values
are assigned based on the number of retrieved emails that each business
workspace contains.
These weight values are added to the overall weight value of each business
workspace and are calculated using the Weight of each Email value
specified in the email search settings.

Example: If the Weight of each Email value is set to 5, and a business workspace
contains 3 of the retrieved emails, a value of 15 is added to that business workspace’s
overall weight value.
3. To calculate an overall weight value for each business workspace, the add-in
uses the weight values that are assigned as a result of applying the rules and
searching for emails.

Example: If a business workspace is assigned a value of 20 after the rules are applied and
a value of 15 after the email search takes place, that business workspace’s overall weight
value is 35.
4. The business workspaces that have the highest overall weight values are then
displayed in the Suggested workspaces list.

Tips

• For more information about rules and email search settings, see “Testing
your rules and email search settings” on page 94.
• For more information about creating regular expressions, see https://
regex101.com/.

11.13.4.2 Understanding how rules are applied to emails sent from

Extended ECM mobile clients
Emails that are sent from Extended ECM mobile clients have pre-defined subject
lines that appear in the following format:

[<Workspace Type Name>] <Workspace Name>:

Example: RE:[Customer] Equipment: Comments

If a user opens an email that has this type of subject line in Outlook, the Business
Workspaces Outlook add-in automatically applies a default rule to determine which
business workspaces to display in the Suggested workspaces list. Specifically, the
add-in uses both the workspace type name and workspace name from the subject

EESPCD230200-IGD-EN-01 Installation Guide 93

Chapter 11 Performing system administration tasks in Content Server

line to search for relevant business workspaces to display in the Suggested

workspaces list.

Example: If the subject of an email is RE:[Customer] Equipment: Comments, the add-in

searches for business workspaces that include Customer in the name of their workspace type
and Equipment in their workspace name.

The add-in assigns a numeric value of 30 to each business workspace that is found,
and then displays the relevant business workspaces in the Suggested workspaces
list.

If you configure rules and email search settings, the default rule is applied in
conjunction with the configured rules and email search settings.

11.13.4.3 Testing your rules and email search settings

You can optionally use the Test tab on the Suggested Workspaces Configuration
page to test the rules and email search settings you configure. You can test rules and
email search settings if, for example, you want to check the validity of the regular
expressions that you configure.

You must first configure and save the rules and email search settings you want to
test on the Workspace Rules and Email Search tabs on the Suggested Workspaces
Configuration page. On the Test tab, you can then specify the properties to include
in a simulated email you want to test.

When you run the test, the add-in applies the rules and email search settings you
configured to the simulated email and displays the actions that would occur if a user
were to open an email containing the properties you specified. For example, the test
results show which values would be extracted from email properties and which
values would be used to search for emails and business workspaces when specific
rules are used.

If the test does not produce the intended results, you can edit the rules and email
search settings and run the test again. You can also run the test with different
simulated email properties.

11.13.4.4 Configuring Rules and Email Search Settings

To configure rules and email search settings:

1. On the global menu, click Enterprise > Business Workspaces, and then click
Outlook Add-in Configuration.
2. Click Suggested Workspaces Configuration.
3. On the General tab, configure the following options, as needed:

a. Optional Select the Show Suggested Workspaces Section option if you want
to display the Suggested workspaces list in the Business Workspaces
Outlook add-in. Clear this option to hide the list from the add-in. By
default, this option is selected.

94 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

b. In the Number of Suggested Workspaces field, select the maximum

number of business workspaces to display in the Suggested workspaces
list. By default, up to five business workspaces appear in the list.

4. On the Workspace Rules tab, do the following:

a. Select the Default Weight value you want to assign to each business
workspace that is found by any of the rules you configure. By default, this
value is added to the overall weight value of each business workspace that
is found by a rule.
b. Optional If you want to configure a rule, in the Rules area, click Add a Rule,
and then configure the following settings.

i. In the Name field, specify a name for the rule.

ii. Select Enabled to allow the rule to find business workspaces. When
this option is cleared, the rule is not used to find business workspaces.
iii. In the Email Property area, select the email property that you want use
to find business workspaces. When a user opens an email, the add-in
checks whether this property contains the pattern specified in the
Matching Condition field. If that pattern is found in the opened email,
the rule uses the regular expression specified in the Extraction Term
field to retrieve business workspaces.
Select one of the following properties:

• Subject: allows the add-in to search for patterns within the subject
line of the opened email.
• Sender: allows the add-in to search for patterns within the Sender
field of the opened email.
• To: allows the add-in to search for patterns within the To field of
the opened email.
• Cc: allows the add-in to search for patterns within the Cc field of
the opened email.

A. In the Apply this rule if property area, specify the matching

method to be used. This is the pattern you want to search for
within the email property you selected in Step 4.b.iii. This pattern
determines whether the rule is used to retrieve business
workspaces. For example, if you selected Subject as the email
property in Step 4.b.iii, the rule searches for the pattern in the
Subject field of the opened email. If the specified pattern is found
in the opened email, the rule retrieves business workspaces.
Select one of the following matching methods:

• Contains: select this option if you want to search for a specific

keyword or phrase within the email property.

EESPCD230200-IGD-EN-01 Installation Guide 95

Chapter 11 Performing system administration tasks in Content Server

• Regular Expression: select this option if you want to use a

regular expression to search for a pattern within the email
property.

Note: Both matching methods are case-insensitive.

B. In the Matching Condition field, specify the keyword, phrase, or

regular expression based on the matching method you selected in
Step 4.b.iii.A. For examples, see “Examples: Workspace rules”
on page 98.
iv. You need to specify the search criteria used to retrieve business
workspaces if the opened email contains a property that matches the
Matching Condition pattern you specified in Step 4.b.iii.B.
Specify the following:

A. In the Workspace Type field, select the business workspace type

you want to retrieve. When the rule is applied, only business
workspaces of that type are retrieved. You can select any
workspace type that is currently configured in Business
Workspaces.
B. In the Extraction Term field, specify a regular expression to
extract a value from the email property you selected. The
extracted value is then used to retrieve business workspaces by
name. For examples, see “Examples: Workspace rules”
on page 98.

Note: You can specify only one capturing group within the
regular expression. If you specify multiple capturing groups,
only the first capturing group is used to extract the value
from the email property.
v. In the Weight field, if needed, select the weight value you want to
assign when business workspaces are retrieved by this rule
specifically. This value is added to the overall weight value of each
business workspace that is found by this rule.
By default, this value is set to Default, meaning that the value that is
selected in the Default Weight list in Step 4.a is assigned to business
workspaces that are found by this rule. If you select a value other than
Default, the Weight value overrides the Default Weight value.
c. Click OK.

Note: Clicking OK adds the rule to the rules list; however, the rule is
not saved until you click Save Changes or Apply.
d. You can now configure additional rules, as needed, by following the steps
in Step 4.b.
Once you are finished configuring your rules, you will see the rules list.
The rules are sorted by weight and then by name. Rules are applied in the
order they are listed.

96 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

Tip: In the rules list, you can click the Edit button to edit a rule, or
the Delete button to delete a rule. You can also enable or disable a
rule by selecting or clearing its check box in the Enabled column.

5. On the Email Search tab, configure the following settings:

a. In the Sort Emails by field, select one of the following options to specify
how to sort the emails that are returned in the search results:

• Last modified date: sorts the emails by the last modified date in
descending order.
• Relevance: sorts the emails according to the relevance rules that are
defined in Content Server. For more information about relevance rules,
see OpenText Content Server - Content Server Administration (LLESWBA-
H-AGD).

The Sort Emails by option specifies which emails are retrieved if more than
50 emails are returned in the search results. The add-in retrieves only the
first 50 emails from the search results and excludes all emails that appear
after the first 50 emails. If more than 50 emails are returned in the search,
the sort order specifies which emails are included in the set of retrieved
emails and which emails are excluded from that set.
b. In the Weight of Each Email field, if needed, specify a numeric value that is
added to the overall weight value of a business workspace whenever an
email is found by the search. By default, the weight value is set to 1;
however, you can specify any positive integer.
For example, if the Weight of Each Email value is set to 5, and if 3 emails
are found in a business workspace, a value of 15 is added to that business
workspace’s overall weight value.
c. Optional Select Search Email Sender if you want to allow the add-in to find
previously saved emails that have the same sender as the email that is
open.
d. Optional Select Search Email Recipients if you want to allow the add-in to
find previously saved emails that include similar recipients as the email
that is open.

6. Click Save Changes to save the rules and search settings and return to the
Outlook Add-in Configuration folder.

Tip: You can also click Apply to save the rules and search settings without
leaving the page.

EESPCD230200-IGD-EN-01 Installation Guide 97

Chapter 11 Performing system administration tasks in Content Server

11.13.4.5 Testing Rules and Email Search Settings

To test rules and email search settings:

1. On the Test tab, in the Outlook User area, specify an Outlook email address to
represent the user who saves emails in Outlook.

2. In the Email Properties area, specify one or more email property values to
include in the simulated email you want to test.

• Sender: specify the email address of the sender to include in the simulated
email.
• To: specify one or more email addresses to include as the recipient in the
simulated email.
• Cc: specify one or more email addresses to include as additional recipients in
the simulated email.
• Subject: specify a phrase or term to include in the subject line of the
simulated email.

Note: If you specify multiple email addresses in the To or Cc fields, each

address must be separated by a semicolon (;).

3. Click Test.

11.13.4.6 Examples: Workspace rules

This section provides examples of workspace rules that are used to find business
workspaces.

Example 11-8: Using the “Contains” matching method to find business

workspaces based on an email’s subject line

In this example, a rule is configured with the following parameters:

• Email Property: Subject

• Matching Method: Contains
• Matching Condition: customer
• Workspace Type: Customer
• Extraction Term: customer[\s]+(.+)

When the rule is applied, the add-in searches the subject line of the opened
email for the term customer. If the subject line contains that term, the add-in
uses the extraction term pattern to extract the characters that appear after
customer in the subject line.

For example, if the subject line is customer ABCD, the add-in extracts the value
ABCD. The add-in then retrieves all business workspaces that have the type
Customer and whose names include ABCD.

98 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.13. Allowing users to save Outlook emails to business workspaces

Example 11-9: Using the “Regular Expression” matching method to find

business workspaces based on an email’s subject line

In this example, a rule is configured with the following parameters:

• Email Property: Subject

• Matching Method: Regular Expression
• Matching Condition: order[\s|-]+\d+
• Workspace Type: Order
• Extraction Term: order[\s|-]+(\d+)

When the rule is applied, the add-in searches the subject line of the opened
email for the pattern order[\s|-]+\d+, that is, the term order, followed by
one or more spaces or hyphens, followed by one or more numbers. If the
subject line contains this pattern, the add-in uses the extraction term pattern to
extract the numbers that appear after order in the subject line.

For example, if the subject line is order - 1234, the add-in extracts the value
1234. The add-in then retrieves all business workspaces that have the type
Order and whose names include 1234.

Example 11-10: Using the “Regular Expression” matching method to find

business workspaces based on an email address

In this example, a rule is configured with the following parameters:

• Email Property: Sender

• Matching Method: Regular Expression
• Matching Condition: equipment_[\d][email protected]
• Workspace Type: Equipment
• Extraction Term: equipment_([\d]+)@server.com

When the rule is applied, the add-in searches the Sender field of the opened
email for the pattern equipment_[\d][email protected], that is, the term
equipment, followed by an underscore, followed by any combination of
numbers, followed by @server.com. If the Sender field contains this pattern,
the add-in uses the extraction term pattern to extract the numbers that appear
between equipment_ and @server.com.

For example, if the Sender address in the opened email is equipment_

[email protected], the add-in extracts the value 1234. The add-in then retrieves
all business workspaces that have the type Equipment and whose names
include 1234.

EESPCD230200-IGD-EN-01 Installation Guide 99

Chapter 11 Performing system administration tasks in Content Server

11.14 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 Core System – Server

Configuration > 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.

11.15 Repairing a group replacement migration

With version 20.2, the group replacement mechanism has been changed internally.
During upgrade a job migrates the previous group replacement settings to the
improved setting. This should happen without any attention from your side.
However, if the group replacement job for data migration failed, you can run the job
again from the Content Server Administrator page.

To re-run the job for group replacement migration:

• In the Content Server Administration, click Core System – Database

Configuration > Maintain Current Database > Test or Repair Known Database
Issues > Repair Business Workspace Group Replacement Data.

11.16 Considering virus-scanning

As an administrator you must ensure that Content Server deployments and related
server systems are scanned for viruses on a regular basis. You should also make
every effort to ensure that desktops, workstations, and even portable systems like
notebooks have real-time virus protection, and that virus definitions are regularly
updated. This could easily be the first line of defense to counter virus threats in your
corporate or organizational environments. Administrators should consult their
antivirus software vendor’s website for up-to-date information, critical updates, and
patches to ensure their corporate or personal virus scanners have the latest fixes to
deal with any reported issues. Antivirus applications can have negative effects on
application deployments if not configured correctly.

100 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 11.16. Considering virus-scanning

• An antivirus application must be able to read files from the file system.
Sometimes, the process of reading the file will “lock” it and prevent other
applications from reading from or writing to the file.
Therefore configure your antivirus software to exclude the <Content_Server_
home> folder and subfolders and the folders that contain the Content Server
search index files.
• When an antivirus application has detected what it believes to be an infected file,
the antivirus application might “quarantine”, which means move and restrict
access, the file or delete the file entirely. However, antivirus applications
sometimes identify non-malicious files as a virus. As a result, these files can be
inadvertently deleted or quarantined. When this happens, important files can be
made inaccessible, which can prevent services from running correctly or from
running at all.

Administrators should be aware that Content Server can be deployed in a variety of

configurations. It can be deployed across multiple servers and use a number of
operating systems. Administrators can enhance the default services with add-ons
and customizations. OpenText Customer Support can assist customers to determine
the appropriate antivirus application configuration for their deployment. OpenText
recommends that administrators test changes to configuration of antivirus
applications prior to deploying them in production.

OpenText partners have also created modules that can integrate directly with
Content Server and an organization’s existing antivirus solutions to block malware
and viruses from being uploaded to Content Server. To inquire about these
solutions, contact your Customer Support channel.

For more information, see the “Best Practices: Content Server Application Security
Hardening Guide” in OpenText My Support (https://knowledge.opentext.com/
knowledge/llisapi.dll/Overview/65175979).

EESPCD230200-IGD-EN-01 Installation Guide 101

Chapter 12
Performing system administration tasks in the
Archive Center

12.1 Customizing processing of Extended ECM

Records
After installation you must change the variable Allow how to process the XECM
records (RECSVC_XECMREC) to value XECMRECDENY ("XECMRECDENY").

EESPCD230200-IGD-EN-01 Installation Guide 103

Chapter 13
Reporting incidents to SAP Solution Manager

You can allow users to report incidents directly from Smart View to your local SAP
Solution Manager. For more information about SAP Solution Manager, see https://
help.sap.com/viewer/p/SAP_Solution_Manager.

To enable SAP incident reporting:

1. On the Content Server Administration page, click Extended ECM for SAP >
Configure SAP support integration.

2. Click Enable and provide the connection parameters to the server, which hosts
the SAP Solution Manager: Server, Port Number and Protocol. Make sure, that
you have no spaces at the end of the server name or the port number. The URL
to the SAP support portal is https://support.sap.com/en/index.html.

3. Click Save Changes.

To report an incident as a user:

1. In Smart View, click the Profile Menu.

2. Click Report incident to SAP.

3. Fill in the required information in the incident report and save your data.

EESPCD230200-IGD-EN-01 Installation Guide 105

Chapter 14
Performing general post-installation tasks in SAP

Before using the Extended ECM for SAP SolutionsCloud functions, you must
perform a series of post-installation and customizing tasks in SAP. For more
information, see “Performing post-installation tasks” on page 113.

For information about the scenario-specific post-installation tasks, see OpenText

Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

Note: The Extended ECM configuration entries are only available in English.
Using other languages result in technical identifiers to be shown instead of
texts.

14.1 Performing general post-installation tasks in

SAP
14.1.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. Start the SPRO transaction.

2. Click SAP Reference IMG.

3. Navigate to the OpenText Extended ECM for SAP Solutions structure and
open it.

EESPCD230200-IGD-EN-01 Installation Guide 107

Chapter 14 Performing general post-installation tasks in SAP

4. Select the required activity, and then 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. Start 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 then click to access the IMG
structure.

108 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.1. Performing general post-installation tasks in SAP

To add the IMG structure to SPRO transaction:

1. Create an enhancement ID:

a. Start 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 SolutionsCloud.
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

EESPCD230200-IGD-EN-01 Installation Guide 109

Chapter 14 Performing general post-installation tasks in SAP

14.1.2 Assigning SAP roles

To use the Extended ECM for SAP Solutions functions in SAP, you must assign
specific SAP roles in transaction SU01. 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. You can also perform transaction
assignments in the SU24 transaction and use them later in the profile
generation tool PFCG.

• 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.

110 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.1. Performing general post-installation tasks in SAP

/OTX/RM_ADMIN
Role for SAP administrator; this role allows for the post-installation and
customizing steps as well as administrative tasks like monitoring or running
batch jobs.
This role contains the following authorizations objects:

Authorization object Description

/OTX/RM Records management authorizations in
GOS
J_6NRL_DOL Business attachments authorizations
J_6NRL_WSC Business workspace authorizations

/OTX/RM_ADMIN_S4
Role for SAP administrator. This role provides additional authorizations or
menu items on S/4HANA systems. For example, it allows access to transaction /
OTX/RM_SBO_CONVERT.

/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 SAP as
the business application” on page 57.
/OTX/RM_CS_SAP_USER_S4
Role for the SAP system connection between Content Server and the SAP
system. This role is needed in S/4HANA systems to provide additional access to
the OData service /OTX/RM_SBO_ODATA_SRV. This role is needed for the SAP
user which is configured in Content Server for the connection to SAP. For more
information, see “Connecting SAP as the business application” on page 57.
/OTX/RM_IMPERSONATED_USER_ROLE
Role for the SAP user which is used in the RFC destination. For more
information, see Section 5.7.1 “Enabling user-specific impersonation (SAP
BAdI)” in OpenText Extended ECM for SAP Solutions - User Management and
Access Control Scenarios (ERLK-CUM).

14.1.3 Adjusting authorization default values

OpenText provides standard authorization assignments for Extended ECM for SAP
SolutionsCloud transactions as part of the installation packages. You can set default
values for the assignment of an authorization to a transaction, which means a
simplification compared to using the SU24 transaction.

The installation packages provide only the standard entries for SAP assignments,
which means those visible in the SU22 transaction. Copy the standard Extended
ECM assignments into the “customer” tables (SU24) through the standard SAP
download/upload programs RSU22DOWN and RSU22UPLD in the following way.

EESPCD230200-IGD-EN-01 Installation Guide 111

Chapter 14 Performing general post-installation tasks in SAP

To copy standard Extended ECM assignments into customer tables:

1. Import the Extended ECM for SAP SolutionsCloud installation and support
packages.

2. Download the authorization-to-transaction-assignment data into a file:

a. Use the SE38 transaction to run the RSU22DOWN program, which downloads
the transaction assignments.
b. Select the SAP Data options and select Display All.
c. Click Execute.
d. Enter a name for the data file.

3. Repeat this for the following transactions:

• /OTX/RMMIG
• /OTX/RMMIGPRINTL
• /OTX/RMMON
• /OTX/RMPEQ
• /OTX/RMPEQPRINTL
• /OTX/RM_DIAGNOSTIC
• /OTX/RM_DIAG_INFRA
• /OTX/RM_CFGREP
• /OTX/RM_WSC_PEQ
• /OTX/RM_WSC_Q
• /OTX/RM_WSC_Q_NR
• /OTX/SEA_UI

If Extended ECM ERP component OTEXRLE is installed, repeat this for the
following two transactions too:

• /OTX/RMERP_DMS_PEQ
• /OTX/RMERP_DMS_MIG

If Extended ECM S/4HANA component OTEXRLS4 is installed, repeat this for

the following transaction too:

• /OTX/RM_SBO_CONVERT

4. Upload the files with the transaction assignments:

a. Use the SE38 transaction to run the RSU22UPLD program, which upload the
transaction assignments to your customer’s table.
b. Enter the same list of transactions, for which you downloaded the data
files.
c. Select the following options. Clear all other.

• SAP Data
• Copy SAP Data to Customer Table

112 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

Optionally, you can perform a test run first and also use the option to create
a transport file if needed.
d. Select the same file that you created with the download program.

5. After you have successfully completed the upload steps for all transaction, you
can adjust the transaction assignments in the SU24 transaction.

6. Use the transaction assignments in the profile generation tool PFCG.

Note: For authorization checks that will be added or changed in future support
packages, OpenText will deliver a list of transactions whose assignments can
be copied into the “customer” list of the SU24 transaction. However, you must
verify existing transaction assignments in the SU25 transaction using step
Postprocess the Settings > 2B Compare Affected Transactions.

14.2 Performing post-installation tasks

14.2.1 Verifying that SNI is enabled
For the cloud connection to work successfully, SNI must be enabled. Run transaction
rz11 and verify that either icm/HTTPS/client_sni_enabled or, on older kernel
versions, ssl/client_sni_enabled is available and enabled. If neither parameter is
present, your kernel release is too low, and you must update your SAP system. For
more details on SNI, see SAP Note 2124480.

14.2.2 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.

Note: If your system uses a different PSE file for SAP Logon Ticket signing (for
example, if you have implemented SAP Note 2420548), then you need to export
that file without the system PSE. The procedure is similar as described for the
system PSE.

To export the SAP PSE certificate:

1. In the IMG, navigate to the Export System PSE Certificate to File System
activity, and then click Execute.

EESPCD230200-IGD-EN-01 Installation Guide 113

Chapter 14 Performing general post-installation tasks in SAP

2. Open the System PSE section, and then check whether there is a certificate in
this folder.
If this is not the case, create a new one. For more information, 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 then copy the PSE file to an appropriate location on the Directory
Services server.

114 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

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, click System Configuration > Keystore
Administration.
3. From the list, select SAPLogonTicketKeypair-cert.
4. Click Download verify.pse File, and then save the file to your desktop.
5. Extract 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 4.2

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

To create an SAP authentication handler:

1. Start Directory Services Administration in a web browser. Open

<protocol>://<server>:<port>/otds-admin/, and then sign in as
[email protected].

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

EESPCD230200-IGD-EN-01 Installation Guide 115

Chapter 14 Performing general post-installation tasks in SAP

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 3.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.

14.2.3 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

• login/create_sso2_ticket = 3 to increase the security for the Web Service

communication between SAP and Content Server to the highest level. This
needs special settings in configuration. For more information, see “Using the
assertion-based authentication mechanism” on page 130.

For a temporary setting, start the RZ11 transaction, enter the parameter name,
and then click Display. For a permanent setting, use the RZ10 transaction, and
restart the system after setting the parameter.

116 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

To activate the HTTP service:

1. In IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Activate HTTP Service activity, and then click Execute.

2. In the Hierarchy Type field, select SERVICE, and then click Execute.

3. In the Maintain service dialog, open the following node default_host > sap >
public.

4. From the context menu of the myssocntl item, select Activate Service.

To activate the redirect service:

Note: The redirect service xecm_redirect, delivered by OpenText, has to be

activated for services that use value 2 and 3 for the login/create_sso2_
ticket system parameter.

1. Enter the SICF transaction.

2. In the Define Services window in the Filter for Calling ICF Hierarchy section,
select the Hierarchy Type SERVICES and click Execute.

EESPCD230200-IGD-EN-01 Installation Guide 117

Chapter 14 Performing general post-installation tasks in SAP

3. In the Virtual Host / Services, open the default_host list.

4. Open the new node otexrl with the xecm_redirect redirect service.

5. Right-click on otexrl and in the menu select Activate Service.

6. In the Activation of ICF Services, click Yes.

14.2.4 Creating logical ports in the SAP system

Extended ECM for SAP SolutionsCloud connects to OpenText web services using
logical ports. The creation of logical ports differs depending on the SAP Basis
version that your system uses.

Note: The ping button in the SOA Manager is not supported by Extended ECM
webservices. It will always return an error. Use the diagnostic report to verify
the webservices configuration.

14.2.4.1 Creating logical ports for SAP Basis 7.0

Extended ECM for SAP SolutionsCloud connects to OpenText components using
HTTP connections and logical ports.

Create the following HTTP connections to the required web services:

• Extended ECM
• OpenText Directory Services
• Content Server Member Services

To create the HTTP connections:

1. In IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Create HTTP Connections activity, and then click Execute.

118 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

2. Click Create.

3. Enterprise Library Services

Optional 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 Content Server installation
Service No.: Content Server 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 Assertion Ticket must be enabled.
See also SAP_BASIS component with a version later than 16 on page 120.

EESPCD230200-IGD-EN-01 Installation Guide 119

Chapter 14 Performing general post-installation tasks in SAP

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:

Extended ECM OpenText Content Server

Directory Services Member Service
RFC Destination Enter a name, for Enter a name, for Enter a name, for
example EXTECM_ example OTDS_ example
DEST. DEST. CSMEMBER_DEST.
Connections Type G (HTTP G (HTTP G (HTTP
Connection to Connection to Connection to
External Server) External Server) External Server)
Technical Settings tab
Target host otcs.example.com otds.example.com[a] otcs.example.com
Path Prefix /otsapxecm/ /ot-authws/ /cws/services/
services/ services/ MemberService
ECMLink Authentication
[a]
If you are using user-specific mapping with impersonation (SAP BAdI), and if OTDS and Content
Server are installed on different servers, enter the host name of the Content Server installation.

The following settings are the same for all ports:

• On the Logon & Security tab, select No Logon, and Send Assertion Ticket.
• On the Messaging tab, in the Message ID Protocol field, select the Suppress
ID Transfer value.

SAP_BASIS component with a version later than 16

If you are using an SAP_BASIS component with a version later than 16, you
might experience the following changes:

The Send SAP Logon Ticket is now called Send SAP Assertion Ticket and
you must provide as destination system the system ID and the client of the
current SAP system.

If this is the case, you must also do the following:

• Ensure that the latest sapssoext.dll file is in the <Tomcat home>\bin

directory.
• Set the following system wide environment variables with the same values
that you specified in SAP:

120 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

– SAPSYSTEMNAME
– SAPSYSTEMCLIENT

After creating the HTTP connection, you must create a corresponding logical port
for each connection:

• Extended ECM logical port

• OpenText Directory Services logical port
• Content Server Member Services

To create a logical port for SAP Basis 7.0:

1. In IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Create New Logical Ports activity, and then click Execute.

2. Extended ECM
Optional In the Proxy Class field, enter /OTX/CO_RM_WSW_ECMLINK.

3. Enter a new name in the Logical Port field, for example ECMLINK_LOGICAL_
PORT.

4. Select the Default Port check box. Select it for your main Content Server if you
have more than one.

5. Click Create.

EESPCD230200-IGD-EN-01 Installation Guide 121

Chapter 14 Performing general post-installation tasks in SAP

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 Content Server in the HTTP Destination field, for example ECMLINK_DEST.

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. 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

122 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

• HTTP Destination
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.

10. 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.

• HTTP Destination
Enter the HTTP destination created before, for example CSMEMBER_DEST.

• State Management
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.

14.2.4.2 Creating logical ports for SAP Basis 7.01

Extended ECM for SAP SolutionsCloud connects to OpenText components using
logical ports.

Create a corresponding logical port for each connection:

• Extended ECM logical port

• OpenText Directory Services logical port

• Content Server Member Services

• Enterprise Library logical port (if required)

• Enterprise Library Content Services logical port (if required)

To create a logical port for SAP Basis 7.01 and later:

1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Create New Logical Ports activity, and then click Execute.

EESPCD230200-IGD-EN-01 Installation Guide 123

Chapter 14 Performing general post-installation tasks in SAP

2. In the SOA Management dialog, 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 then click Go.

4. In the Search Results pane, select the entry for Extended ECM (/OTX/CO_RM_
WSW_ECMLINK), and then click Apply Selection.

5. On the Configurations tab, click Create Logical Port.

6. Enter a new name in the Logical Port Name field and add a description.
Select Logical Port is Default if you have only one logical port for the Extended
ECM. If you have multiple logical ports for Extended ECM, 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 then select SAP Authentication
Assertion Ticket.

9. Open the Messaging tab.

In the Message ID Protocol field, select the Suppress ID Transfer value.

124 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

10. Open the Transport settings tab, and then enter the following parameters:

• URL Access Path:

/otsapxecm/services/ECMLink

• Computer Name of Access URL:

Extended ECM installation host name
• Port Number of Access URL: port. For cloud installations, enter 443.

Click Save.
A message at the top of the screen indicates that the binding has been created.

11. Create the other logical ports according to the following table.

Extended ECM Authentication Content Server

Member Service
Internal name /OTX/CO_RM_WSW_ /OTX/CO_ /OTX/CO_
ECMLINK OTDSAUTHENTICAT MBLLMEMBER_
ION SERVICE
URL Access Path /otsapxecm/ /ot-authws/ /cws/services/
services/ services/ MemberService
ECMLink Authentication
Computer Name otcs.example.com otds.example.com[a] otcs.example.com
Access URL
[a]
If you are using user-specific mapping with impersonation (SAP BAdI), and if OTDS and Content
Server are installed on different servers, enter the host name of the Content Server installation.

The following settings are the same for all ports:

• 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.

14.2.4.3 Creating logical ports for SAP Basis 7.31

Extended ECM for SAP SolutionsCloud connects to OpenText components using
logical ports.

Create a corresponding logical port for each connection:

• Extended ECM logical port

• OpenText Directory Services logical port
• Content Server Member Services
• Enterprise Library logical port (if required)
• Enterprise Library Content Services logical port (if required)

EESPCD230200-IGD-EN-01 Installation Guide 125

Chapter 14 Performing general post-installation tasks in SAP

To create a logical port for SAP Basis 7.31:

1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Create New Logical Ports activity, and then click Execute.

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 then search for Consumer Proxy.

4. In the Search Results list, select the entry for Extended ECM (/OTX/CO_RM_
WSW_ECMLINK).

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 then 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.

126 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

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

• URL Access Path:

/otsapxecm/services/ECMLink
• Computer Name of Access URL:
Content Server installation host name
• Port Number of Access URL: port. For cloud installations, enter 443.
• 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.

Click Finish.
The new logical port is saved and activated.

EESPCD230200-IGD-EN-01 Installation Guide 127

Chapter 14 Performing general post-installation tasks in SAP

11. Repeat Step 4 to Step 10 to create a logical ports according the following table:

Extended ECM Authentication Content Server

Member Service
(MemberService)
Internal name /OTX/CO_RM_WSW_ /OTX/CO_ /OTX/CO_
ECMLINK OTDSAUTHENTICAT MBLLMEMBER_
ION SERVICE
URL Access Path /otsapxecm/ /ot-authws/ /cws/services/
services/ services/ MemberService
ECMLink Authentication
Computer Name of otcs.example.com otds.example.com[a] otcs.example.com
Access URL
Port Number of 443 443 443
Access URL
[a]
If you are using user-specific mapping with impersonation (SAP BAdI), and if OTDS and Content
Server are installed on different servers, enter the host name of the Content Server installation.

The following settings are the same for all ports:

• Consumer Security: SAP Authentication Assertion Ticket

• Transport Binding Type: SOAP1.1
• Message ID Protocol: Suppress ID Transfer

14.2.4.4 Creating logical ports for SAP Basis 7.51

Extended ECM for SAP SolutionsCloud connects to OpenText components using
logical ports.

Create a corresponding logical port for each connection:

• Extended ECM

• OpenText Directory Services

• Content Server Member Services

• Enterprise Library (if required)

• Enterprise Library Content Services (if required)

To create a logical port for SAP Basis 7.51:

1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Create New Logical Ports activity, and then click Execute.

128 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

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 then search for Consumer Proxy.

4. In the Search Results list, select the entry for Extended ECM (/OTX/CO_RM_
WSW_ECMLINK).

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 then 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:

• URL Access Path:

/otsapxecm/services/ECMLink
• Computer Name of Access URL:
otcs.example.com
• Port Number of Access URL: Web Services port ( 443 for cloud
deployments)

EESPCD230200-IGD-EN-01 Installation Guide 129

Chapter 14 Performing general post-installation tasks in SAP

• 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. 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 Content Server

Member Service
(MemberService)
Internal name /OTX/CO_RM_WSW_ /OTX/CO_ /OTX/CO_
ECMLINK OTDSAUTHENTICATI MBLLMEMBER_
ON SERVICE
URL Access Path /otsapxecm/ /ot-authws/ /cws/services/
services/ECMLink services/ MemberService
Authentication
Computer Name of otcs.example.com otds.example.com[a] otcs.example.com
Access URL
Port Number of 443 443 443
Access URL
[a]
If you are using user-specific mapping with impersonation (SAP BAdI), and if OTDS and Content
Server are installed on different servers, enter the host name of the Content Server installation.

The following settings are the same for all ports:

• Consumer Security: SAP Authentication Assertion Ticket

• Transport Binding Type: SOAP1.1
• Message ID Protocol: Suppress ID Transfer

14.2.4.5 Using the assertion-based authentication mechanism

SAP recommend that you use value 3 for the login/create_sso2_ticket system
parameter. With this value, Extended ECM for SAP SolutionsCloud needs some
special configuration steps.

Notes

• To use the assertion-based authentication, Extended ECM for SAP Solutions

must use RFC destinations managed by SM59 transaction. In these RFC
destinations you can maintain the assertion ticket parameters.
• The assertion-based authentication mechanism does not work in the Internet
Explorer compatibility mode.

130 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

For implementing the assertion-based authentication mechanism you must modify

the configuration as follows:

• Download and install the predefined WSDL/OTDS web service, delivered in

wsdl_for_assertion_tickets_level_3.zip.
• Configure additional security settings for RFC destinations.

To install the predefined WSDLs for the ECM Link and OTDS web service:

1. In OpenText My Support Portal, navigate to Knowledge Base article KB0779691:

WSDL for using SAP assertion-based authentication mechanism ( https://
support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0779691).
Download the file. The attached ZIP file contains the required WSDL files.
2. To install the predefined WSDLs for the ECMLink, OTDS and authentication
web services, unpack the ZIP file and click on wsdl_for_assertion_tickets_
level_3.

3. In the SOAMANAGER, create a logical port based on this definitions by using

file based WSDL access. Set the parameters as follows:

• Authentication section

– Authentication method: sapsp:HTTPSSO2

– System ID: <your system ID>
– SAP Client: <your SAP Client number>
• Transport Security section

– Secure Communications: SSL

– Signature Expected: False
– Encryption Expected: False
– Sign Message: False
– Add Encryption: False
• Transport Settings section

– URL Access Path: Complete URL, for example, https://

<server>:<port>/otsapxecm/services/ECMLink
– Proxy: Leave blank
– Transport Binding:
Make Local Call: No Call in Local System
Transport Binding Type: SOAP 1.1
Maximum Wait for WS Consumer: 0
Optimized XML Transfer: None
Compress HTTP Message: Inactive

EESPCD230200-IGD-EN-01 Installation Guide 131

Chapter 14 Performing general post-installation tasks in SAP

Compress Response: True

• Messaging section

– Message ID Protocol: Supress ID Transfer

– Data transfer scope: Enhance Data Transfer
– Transfer protocol: Transfer via SOAP header
• Message Attachments section

– Process Attachments: No

4. Repeat the above steps for each Extended ECM web service in use.

5. Maintain the environment parameters for OTDS:

• SAPSYSTEMCLIENT: 001
• SAPSYSTEMNAME: OTX

To configure additional security settings for RFC destinations

1. Enter the SM59 transaction.

2. In the RFC Connections list, open the HTTP Connections to External Server
section and find the destination configuration which is referred to in the
Extended ECM communication configuration.

3. In the Logon & Security tab in section Logon with Ticket, select Send
Assertion Ticket for Dedicated Target System.

4. In the System ID field enter OTX, and in the Client field enter 001.

14.2.5 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 business

application in Content Server. For more information, see “Connecting SAP as
the business application” on page 57.

1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
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.

132 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

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:
https://mucr3d6v.example.com:44300/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 then 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 23.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.

EESPCD230200-IGD-EN-01 Installation Guide 133

Chapter 14 Performing general post-installation tasks in SAP

– 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.

14.2.6 Creating logical destinations

The SAP system uses the Internet Communication Framework (ICF) to connect
through REST calls to OTDS and the Content Server.

For this, you define a logical destinations for each of the following systems:

• OpenText Directory Services (OTDS)

• Content Server

You will need these logical destinations when you set up the connection to the
Extended ECM system. For more information, see “Maintaining Extended ECM
connections” on page 135.

To create logical destinations:

1. Run transaction SM59 to open the Configuration of RFC Connections screen.

2. Create a new connection of type with the following parameters:

• RFC destination: Enter a name for the connection.

• Connection Type: Select G HTTP COnnection to External Server.
• Technical Settings tab

– Target Host: Enter the fully qualified hostname of the server.

– Service No.: Enter the port of the server. If you want to use SSL (HTTPS),
you also must activate SSL usage on the Logon & Security tab.
– Path Prefix: Leave empty.
– HTTP Proxy Options: You can define proxy settings specific to this
logical destination or a global configuration for all logical destinations
The proxy settings are only active for direct connections from the SAP
server to external server. They are not relevant to frontend UI or Web UI
connections.
• Logon & Security tab:

134 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

– Logon procedure: Select No Logon.

– Send Assertion Ticket: Select the option if it is a checkbox under the
area Logon Procedure. The option must be set at least for the OTDS
destination in order to allow single sign-on (SSO).

Note: In newer SAP releases you have 3 options under the Logon
with Ticket area. The right option depends on the single sign-on
(SSO) settings, see “Activating the SSO HTTP service” on page 116.
If login/accept_sso2_ticket value 2 is used, select the Send
ticket without reference to target system option.
If login/accept_sso2_ticket value 3 is used, select the Send
assertion ticket for dedicated target system option. Then you must
provide the system ID and client, see “Using the assertion-based
authentication mechanism” on page 130.
– SSL: Select Active. If you connect through HTTPS, use the correct port in
the Property Service No. field on the Technical Settings tab.
– SSL Client Certificate: Select ANONYM if SSL is active.
– Authorization for Destination: Leave empty.
– User/Password Status: Leave empty.
• Special Options tab:

– Timeout: Select ICM Default Timeout.

– HTTP Setting Version: Select HTTP 1.1. If you experienced unexpected
issues, you may switch back to 1.0.
– Compression: Select Inactive.

Note: Compression of request bodies is not supported by Content

Server. Leave compression status Inactive.
– Compressed Response: Select Yes.
– HTTP Cookies: Select No.

14.2.7 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 then click Execute.

2. Click New Entries.

EESPCD230200-IGD-EN-01 Installation Guide 135

Chapter 14 Performing general post-installation tasks in SAP

3. Enter the following parameters:

Connection ID
Enter a connection ID.

Extended ECM Connections

• Description: Enter a description for the connection.

Logical Ports for Web Services

Enter the names of the logical ports for Extended ECM, OpenText Directory,
and for the Content Server Member Service. For more information about
logical ports, see Section 22.2.4 “Creating logical ports in the SAP system” in
OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide
(ERLK-IGD).

136 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

OpenText Directory

• Logical Destination: Enter the logical destination as defined for it. For
more information, see “Creating logical destinations” on page 134.
• 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 must 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 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 5.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

• Logical Destination: Enter the logical destination as defined for it. For
more information, see “Creating logical destinations” on page 134.
• Path: cs/cs
• Support Directory defines the directory on Content Server where the
files for the Content Server widgets are stored, for cloud installations the
directory is cssupport. For more information, see Section 11 “Using the
Content Server Integration Widget” in OpenText Extended ECM for SAP
Solutions - Customizing Guide (ERLK-CGD).
• External System ID: Enter the SAP System ID.
• 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. Go to
Directory Services > Resources > <Content Server entry> > Edit and copy
the Resource identifier, for example, d7c6b26b-
af12-4d87-87cd-050de0768f4a.

EESPCD230200-IGD-EN-01 Installation Guide 137

Chapter 14 Performing general post-installation tasks in SAP

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.
Suppress Sending SAP Logon Ticket
Select this option if you do not want to send the SAP Logon Ticket.
Search UI
Enter the logical destination, you created for it.

4. Click Save.

14.2.8 Importing the Content Server SSL certificate

If you get an error about untrusted root in connection tests in the OpenText Cloud
environment, you must import the Content Server SSL certificate into the SAP
system.

Note: For the general setup of SSL in your SAP system, follow the procedure
outlined in http://help.sap.com/saphelp_nw70ehp2/helpdata/en/49/
23501ebf5a1902e10000000a42189c/frameset.htm.

Prerequisites

• You have configured the web servers for HTTPS.

To export certificate from Content Server:

1. Call an URL from the environment in a browser. For example, https://otacc.

example.com/archive.

2. Click the lock symbol to access the certificate. In MS Edge, you must click
Connection is secure and then click the certificate symbol in the top right
corner.

3. In the certificate dialog, click the Certification Path tab and then click the top
most certificate. Click the View Certificate button.

4. Switch to the Details tab of the certificate and click the Copy to File… button.
Follow the assistant to save the certificate.

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 then select Base64.

5. Click the Add to Certificate List button and save your settings.

138 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 14.2. Performing post-installation tasks

6. Repeat the steps for the SSL client SSL Client (Standard) node.

EESPCD230200-IGD-EN-01 Installation Guide 139

Chapter 15

Mapping SAP roles to OTDS groups or Content

Server groups

In Content Server, permissions define who can access a business workspace.

Typically, this is handled with groups to which the users are assigned. Content
Server users and groups are managed in Directory Services (OTDS).

You can fill OTDS groups with users from the SAP system depending on their role
assignment. The OTDS users and groups are synchronized to the Content Server
groups.

For the mapping, you create the OTDS groups in a separate non-synchronized
partition. You configure the Content Server resource in OTDS, define the partition
and a mapping in the SAP system, run it and configure events. Permissions for
groups in Content Server must be defined separately by the Content Server
administrators. For information about all relevant settings, see Section 8 “Mapping
SAP roles to groups” in OpenText Extended ECM for SAP Solutions - User Management
and Access Control Scenarios (ERLK-CUM).

Note: For earlier versions, a Solution Accelerator was available for the
mapping of SAP roles to Directory Services groups. If you have been using this
Solution Accelerator, you can either stay with your former implementation or
switch to the new implementation. If you want to switch to the new
implementation, copy the mapping from the Solution Accelerator table to the
product table.

15.1 Defining the user partition for group mapping

OTDS groups All users that you want to add to an OTDS group must be in one single partition.
When adding a user to an OTDS group, the defined partition is appended to the SAP
user name. This requires that there is a one-to-one relationship of users in SAP with
users in OTDS.

For more information about setting up user mapping, see Section 3.2.3.1 “One-to-one
user mapping without impersonation” in OpenText Extended ECM for SAP Solutions -
User Management and Access Control Scenarios (ERLK-CUM).

Note: The OTDS group can be in a different partition which must be non-
synchronized.

Content Server For Content Server groups, the partition is only appended if OTExternalID2,
groups OTExternalID3, or OTExternalID4 is defined as _NAME_ attribute. In this case,
define the partition.

EESPCD230200-IGD-EN-01 Installation Guide 141

Chapter 15 Mapping SAP roles to OTDS groups or Content Server groups

To define the partition:

1. In the IMG, navigate to the OpenText Extended ECM for SAP Solutions >
Infrastructure > Maintain Extended ECM Connections activity, and then click
Execute.

2. Select the connection in the list, and then click Change.

3. In the OpenText Directory section, in the Partition field, enter information

according to your scenario:

• When synchronizing SAP roles to OTDS groups, enter the partition name.
• When synchronizing SAP roles to Content Server groups or business
policies, do the following:

– With a non-synchronized partition, enter the partition name in the

partition field.
– With a synchronized partition, fill the partition field as follows:

_NAME_ Resource Mapping Partition_ field_

oTExternalID1 Leave empty
oTExternalID2 Domain name
oTExternalID3 Partition name
oTExternalID4 NetBIOS domain name

Tip: To find the OTDS attribute value for the _NAME_ resource
attribute, go to Directory Services Integration Administration >
Configure Directory Services > Resources > Properties (for
Content Server) > User Attributes Mappings.

142 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 16
Performing license measurement

With the license measurement, you assess the number and types of users who are
working with an SAP system. License measurement for Archiving and Document
Access and Extended ECM for SAP Solutions can be integrated in the SAP license
measurement Global License Audit System (GLAS). With this information, you can
align your contract with SAP or OpenText to meet your requirements more
accurately.

Extended ECM License Control

From version 23.1, Extended ECM changed its licensing method

fundamentally. The new license method is called Extended ECM License
Control.New customers use the new method. Existing customers can choose
their licensing method, they can either stay with the Extended ECM License
Metering or they can ask for a new license key and switch the method. Please
contact OpenText for your options.

For more information on installations with the new Extended ECM License
Control, see Section 6.10 “License Extended ECM” in OpenText Extended ECM -
Installation Guide (LLESCOR-IGD).

Currently, there are the following licensing methods:

Extended ECM License Control – Privileges are deprecated as users are blocked
from access. The usage days are still counted but the user is blocked if the access
days are exceeded, or the user has no appropriate license. There is no license report
available. For the available license types, see “Extended ECM License Control”
on page 144.

Extended ECM License Metering (old licensing) – A privilege is used to count on

how many days a user accesses business workspaces. A user is not locked, if the
actual days of usage exceed the number of days that are covered by the assigned
license type. This mismatch is noted in the license report.

EESPCD230200-IGD-EN-01 Installation Guide 143

Chapter 16 Performing license measurement

16.1 Extended ECM License Control

For more information on installations with Extended ECM License Control, see
Section 6.10.1.1 “Extended ECM Licenses” in OpenText Extended ECM - Installation
Guide (LLESCOR-IGD) and
Section 6.10.3.1 “Apply and Allocate an Extended ECM License” in OpenText
Extended ECM - Installation Guide (LLESCOR-IGD).

Note the following:

• The usage days are still counted but the user is blocked if the access days are
exceeded. There is no license report available.
• Privileges are not used.
• Assigning license types to a user or group is performed in OTDS.

The following license types are available:

Table 16-1: Extended ECM License Control license types

License New license

Product Old license name
type name
OpenText Extended ECM for OpenText Extended ECM for X2-Full, X3-
OpenText
SAP SAP – Professional User Full
X2–
OpenText Extended ECM for OpenText Extended ECM for
OpenText Occasional,
SAP SAP – Occasional User
X3–Occasional

16.2 Extended ECM License measurement

144 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

16.2.1 Technical overview

Figure 16-1: License Measurement Overview

Extended ECM for SAP Solutions licensing measurement consists of the following
parts:

Measurement on the SAP system

Measurement on the SAP System is based on a business role with the J_6NLC_
TYP authorization object and an appropriate license type. Business roles with
this authorization object are then evaluated based on their license type related to
the product and depending on the degree of usage.
Important
The authorization object J_6NLC_TYP is not used to grant access
permissions.
Measurement on Content Server
Users and groups are assigned a license type that reflects their quantity of usage.
The license type along with the number of days on which this user accessed a
business workspace in Content Server are passed to the SAP system where the
data is consolidated and presented.
Extended ECM License Control – Privileges are deprecated as users are blocked
from access. The usage days are still counted but the user is blocked if the access
days are exceeded, or the user has no appropriate license. There is no license
report available. For the available license types, see “Extended ECM License
Control” on page 144.
Extended ECM License Metering – A privilege is used to count on how many
days a user accesses business workspaces. A user is not locked, if the actual days
of usage exceed the number of days that are covered by the assigned license
type. This mismatch is noted in the license report.

EESPCD230200-IGD-EN-01 Installation Guide 145

Chapter 16 Performing license measurement

Table 16-2: Extended ECM License Metering license types

Type Description
Licenses sold by OpenText
OXECMF OpenText Extended ECM for SAP – Professional User
OXECMO OpenText Extended ECM for SAP – Occasional User
OXECMB OpenText Extended ECM for SAP – External B2B User
OXECMC OpenText Extended ECM for SAP – External B2C User
OXECMN OpenText Extended ECM for SAP – Non-SAP User
ODOCF OpenText Document Access – Full Named User
ODOCW OpenText Document Access – Web Named User
ODOCO OpenText Document Access – Occasional User
OARCF OpenText Archiving – Full Named User
OARCW OpenText Archiving – Web Named User
OARCO OpenText Archiving – Occasional User
Licenses sold by SAP
SXECMF SAP Extended ECM by OpenText – Named User
SXECMO SAP Extended ECM by OpenText limited access option
SAP Document Access by OpenText – User: Business Expert, Ltd.
SDOCF
Professional
SAP Document Access by OpenText – User: Employee, Employee Self
SDOCW
Service (ESS) User
SARCF SAP Archiving by OpenText – User: Business Expert, Ltd. Professional
SAP Archiving by OpenText – User: Employee, Employee Self Service (ESS)
SARCW
User
SARCF2 SAP Archiving by OpenText
SARCO SAP Archiving by OpenText limited access option
SDOCF2 SAP Document Access by OpenText
SDOCO SAP Document Access by OpenText limited access option

146 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

16.2.2 Prerequisites
To use the Extended ECM for SAP Solutions license measurement, you must do the
following:

1. On the SAP system, create roles for each license type that you need with the
authorization object and appropriate license type, and assign them to the users.
2. • Extended ECM License Metering – in Content Server, assign the appropriate
license type to the users of Extended ECM for SAP Solutions. For example, a
user who rarely needs to work with business workspaces needs a different
license than users that daily work with business workspaces.
• Extended ECM License Control – assign the license types in OTDS.

16.2.3 Preparing license measurement on the SAP system

To prepare your SAP system for license measurement of OpenText products and
integrate into SAP System Measurement (transaction USMM), you must maintain
system measurement tables. You must also create special business roles that contain
an authorization object for measurement.

16.2.3.1 Setting up users for measurement

You need the following users for license measurement with the respective
authorizations objects.

EESPCD230200-IGD-EN-01 Installation Guide 147

Chapter 16 Performing license measurement

User type Authorization objects

User who runs license measurement on and • S_TCODE
for the local system TCD = /OTX/LICENSE, SLG1, SM36,
SM37
• S_BTCH_JOB
JOBACTION, JOBGROUP
enabled to your requirement
• S_GUI
ACTVT = 61
to enable generic ALV functions for /
otx/license
• S_USER_GRP
ACTVT = 03
CLASS = *
to fully use transaction /otx/license
and its function (see also documentation
for transaction USMM)
• S_APPL_LOG
ACTVT = 03, 06
ALG_OBJECT = /OTX/CL
ALG_SUBOBJ = /OTX/CL, /OTX/CL_
RM
to enable the user to read the application
log
• S_BDS_DS
ACTVT = 03
CLASSNAME = DEVC_STXD_BITMAP
CLASSTYPE = OT
to allow access to images inside the PDF
output of the license report
Communication user who is called via RFC • S_RFC
from a central license measurement system ACTVT = 16
RFC_NAME = CL_TRANS, RM_LIC_RFC
RFC_TYPE = FUGR
to allow this user to call the RFC enabled
functions of these function groups

148 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

User type Authorization objects

User who runs license measurement on the All of the above and the following:
central license measurement system which
• S_ICF
calls remote SAP systems
ICF_FIELD = DEST
ICF_VALUE = <value of field
Authorization for Destination in
the RFC destination>
• S_RFC_ADM
ACTVT = 03
The other fields may differ depending on
how restricted your setup your
environment.

user who runs a license measurement needs a business role with the following
authorization objects:

To set up a user for measurement:

1. Start transaction pfcg to assign the authorization role.

2. Create a role for a user who runs license measurement according to the
information given in the table above.

3. On the systems which are called via RFC, create a role for communication users
who are called via RFC from a central license measurement system.

16.2.3.2 Maintaining measurement tables

OpenText provides three function modules for the integration into SAP System
Measurement:

• /OTX/CL_GLAS_DOCUMENT_ACCESS – integration function for Document

Access
• /OTX/CL_GLAS_ARCHIVING – integration function for Archiving
• /OTX/RM_LIC_GLAS_XECM – integration function for Extended ECM

The function modules provide the following:

• Writing status, warning and error messages to application log object SLG1.
If validation issues have been found, this shows as a warning message in the log
of each function. You then must check the more detailed license report in
transaction /otx/license.
• Each function module contains an external ID referring to the related application/
product.
• The function modules call a central method of the OpenText license evaluation to
calculate the license counts.

EESPCD230200-IGD-EN-01 Installation Guide 149

Chapter 16 Performing license measurement

To maintain SAP System Measurement tables:

• Start transaction SM30 to add the following tables:

TUAPP (Applications for System Measurement)

Add entries for OpenText applications to the TUAPP table.

Important
Add the following entries only if you purchased your licenses from
SAP. If you purchased your licenses directly from OpenText, set Call?
= false for all these entries.

App. Version Name of Function PeriodType Call?

Application module
name
1140 0 SAP /OTX/ No period true
Archiving CL_GLAS_ assigned
by ARCHIVIN
OpenText G
1144 0 SAP /OTX/ No period true
Document CL_GLAS_ assigned
Access by DOCUMEN
OpenText T_ACCESS
1154 0 SAP Ext. /OTX/ No period true
Enterprise RM_LIC_G assigned
Content LAS_XECM
Mgmt by
OT

150 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

TUUNT (Units for System Measurement Objects)

Add the following units for the measurement of OpenText applications to
the TUUNT table.

Unit Measurement
1140 OT: Licensed User: Buss. Expert, Ltd Pro
1141 OT: Licensed User: Employee, ESS User
1144 OT: Licensed User: Buss. Expert, Ltd Pro
1145 OT: Licensed User: Employee, ESS User
1152 OT: User limited access option
1154 OT: User

EESPCD230200-IGD-EN-01 Installation Guide 151

Chapter 16 Performing license measurement

16.2.4 Extended ECM License Metering (old licensing):

preparing license measurement on Content Server
For Extended ECM License Metering on Content Server, you must do the following
to enable license measurement:

• Assign a license type to a user or a group. For Extended ECM License Control,
perform this in OTDS. A license can be assigned to a user, group or partition
level.
• Grant the permission to access business workspaces. For Extended ECM License
Control, this is not required anymore.
• For the authentication of this connection, OTDS is required.

To assign a license type to a user or group in Content Server:

1. In Content Server Administration page, click Enterprise > Users & Groups to
open the Content Server user management.

2. Find the user or group that you want to edit.

152 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

3. From the Extended ECM License list, select a license type.

Note: If there are conflicting license assignments for users because one of
their groups has a different type, the most comprehensive license type is
counted.

To grant usage privileges for licensing:

Only users with the Access Business Workspaces privilege can access business
workspaces. Each time a user with this privilege accesses business workspace is
counted for the license measurement.

1. On the Content Server Administration page, click Core System – Feature

Configuration > Usage and Transaction Privileges.
2. Edit the restrictions for the usage privilege Extended ECM Operation > Access
Business Workspaces (Mandatory for Licensing) according to your license
model. Mismatches between granted privileges and license type assignment are
displayed in the report.

16.2.5 Running license measurement

OpenText License Management provides different modes in SAP in which you can
configure and run the measurement. If necessary, you can switch between these
modes during configuration.

Extended ECM License Metering

The SAP administrator who runs the license measurement must have the
following business administrator’s usage privileges in Content Server.

1. Business Administration Extended ECM to set up the licensing scenarios.

2. License Metering to view the Content Server license report.

Standard Mode
Use the standard mode for a simple scenario:

• The SAP client on which you run the license dashboard is the only system
that is being measured.
• The Content Server instance that is being measured is customized in the IMG
activity OpenText Extended ECM for SAP Solutions > Infrastructure >
Maintain Extended ECM Connections. You can select a Content Server if
more than one is configured.

Expert Mode
Use the expert mode for a system measurement of more than one SAP client and
possibly more Content Server installations.
You can use expert mode to include all Content Server instances that are
connected to a remote SAP system.

EESPCD230200-IGD-EN-01 Installation Guide 153

Chapter 16 Performing license measurement

16.2.5.1 Running in standard mode

Standard mode only uses the SAP system on which you started the license
measurement. All other SAP servers that you might have configured in expert mode
will be deactivated.

To run license measurement in standard mode:

1. Start transaction /OTX/LICENSE.

OpenText License Measurement Cockpit starts in standard mode.

2. Maintain OpenText Archives on this SAP Server

In the list of content repositories on this SAP server, you can select which
repository is used as an OpenText Archive. Access permissions for the
OpenText archives are used to validate license types. This setting is valid for all
clients on this server.

154 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

Note: OpenText Archives must be maintained on each remote SAP system

that you include in your measurement.

This section is only visible if Extended ECM is installed and Connection IDs are
maintained in the IMG activity.
Save your settings.

3. OpenText Products Sold by SAP That Have Been Licensed: Select if you
licensed OpenText Employee File Management (EFM) or OpenText Travel
Receipts Management for SAP Solutions (TRM). When you selected an option,
DocuLink projects that are recognized as EFM or TRM projects are ignored
when validating access permissions to DocuLink. In any case, TRM or EFM
DocuLink projects are listed in the license report.

Note: These licensed OpenText products must be maintained on each

remote SAP system that you include in your measurement.

Save your settings.

4. Click Start License Measurement and confirm the creation of the background
job.
The Status section informs you about the status of the measurement. Click
Refresh to update the status. If the measurement was performed without errors,
click Display Latest License Report to view the report.
For more information, see “Understanding the consolidated measurement
results” on page 161.

16.2.5.2 Running in expert mode

You can use expert mode if you want to include other clients on the same SAP
system or remote SAP systems into the measurement. These SAP systems are
connected via RFC. Content Servers that are connected to these SAP systems can
also be included in the measurement.

In expert mode, you have the following options how license data is retrieved for
consolidation:

• Direct transfer through RFC connection. The remote system must be available
during the measurement.
• Export an XML file from the remote SAP system and import it to the license
measurement cockpit inbox. Use this option if the remote system is not available
during measurement. You can either create and export file manually on the
remote system, save it to a disc, and then upload it to the measuring system, or
you can retrieve the export file through the RFC connection. In both cases, you
must make sure that the age of the retrieved license data does not exceed the
maximum age that you set for license data.
• Content Server connected to an SAP system.

EESPCD230200-IGD-EN-01 Installation Guide 155

Chapter 16 Performing license measurement

To run license measurement in expert mode:

1. Start License Measurement Cockpit with transaction /OTX/LICENSE.

OpenText License Measurement Cockpit starts in standard mode.

2. Click Change to Expert Mode.

Click Always Start in Expert Mode if you want this option.

3. Maintain OpenText archives and product exclusions.

On the Preparation of SAP System tab, you can identify OpenText archives and
define which products you want to exclude from measurement.

a. Maintain OpenText Archives on this SAP Server

In the list of content repositories on this SAP server, you can select which
repository is used as an OpenText Archive. Access permissions for the
OpenText archives are used to validate license types. This setting is valid
for all clients on this server.

Note: OpenText Archives must be maintained on each remote SAP

system that you include in your measurement.

This section is only visible if Extended ECM is installed and Connection IDs
are maintained in the IMG activity.
Save your settings.

b. OpenText Products Sold by SAP That Have Been Licensed: Select if you
licensed OpenText Employee File Management (EFM) or OpenText Travel
Receipts Management for SAP Solutions (TRM). When you selected an
option, DocuLink projects that are recognized as EFM or TRM projects are
ignored when validating access permissions to DocuLink. In any case, TRM
or EFM DocuLink projects are listed in the license report.

Note: These licensed OpenText products must be maintained on each

remote SAP system that you include in your measurement.

Save your settings.

4. Define systems that you want to measure

On the Server and Inbox Measurement tab, you maintain all SAP systems and
Content Servers that are part of your system landscape and that you want to
measure. For each measurement, you can decide which systems you want to
include in that run. You can activate systems that are currently used and
deactivate systems that you currently do not need.

Note: If there are no active or inactive SAP systems maintained, at least

the SAP system from which you are running the license measurement will
be entered after a refresh.

156 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

Server is an SAP system

Server is a Content Server connected to the SAP system

View active / inactive systems

Toggle between active and inactive SAP clients and Content Severs

Activate / deactivate
Activate or deactivate an SAP client or a Content Server. Inactive systems
are only visible in the list of inactive systems. They are not deleted,
though. Measurement data that has been uploaded to the inbox for that
system, is invisible when the system is inactive. It is available again once
you activate the system.

New system
Create a system connection manually. Alternatively, create a destination
through an RFC destination.
For this, you need the following information. Most of the SAP related
information are available in transaction SLICENSE. Content Server related
information are taken from the Maintain Extended ECM Connections
IMG activity.

• SAP system number, installation number, hardware key, and client

• Server type C for Content Server or S for SAP system
• If the system type is C, provide the Connection ID as configured in the
IMG of that system as well a connection information and the RFC
destination.

New system with RFC connection

Add an SAP server or Content Server through an RFC destination.
You can use transaction SM59 to define a new RFC connection with
connection type 3.
If you entered an empty RFC destination, it will be replaced by RFC
destination NONE, which connects to the current SAP client.

Edit entry
Edit an entry.

EESPCD230200-IGD-EN-01 Installation Guide 157

Chapter 16 Performing license measurement

Set maximum age

Set the tolerable age in days of the uploaded measurement data. Data that
is older than this age, is not included in the measurement. This also
applies to manually uploaded data.

Change RFC destination

Change the RFC connection for one or more active systems

Delete selected entries

Delete a system entry. You can only delete inactive systems. Deleting an
inactive system also deletes corresponding data from the inbox.

5. Provide measurement data.

You can define how the measurement data is provided by the active systems:

• Automatic file transfer: An export file must be prepared on the remote

system. It must not be older than the maximum age you defined. The remote
system must be available and connected. The export file will then be
transferred to the inbox.
• Manual file transfer: The remote system must be in the list of active systems.
An export file must be prepared on the remote system. It must be exported
and it must be available on a disk or file system.

Enable or disable RFC connection

Enable or disable automatic import of measurement data during the
license measurement. You can disable an RFC connection for a
measurement and use manually imported license data from an exported
XML file instead. Nevertheless, the system must remain active in License
Measurement Cockpit. Only active systems are included in a license
measurement, regardless of the status of the RFC connection.

Upload from file system

Select an active system and upload a file with measurement data to the
inbox of the License Measurement Cockpit. The remote system needs not
be connected through RFC connection. You must have exported the
measurement data first on the remote system. For more information, see
“Creating an export file with license data” on page 160.

If the uploaded measurement data origins from a Content Server,

you must upload two files in a specific order. The file type is part of
the file name, if you did not change the name during export.

158 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

1. File of file type CL

2. File of file type CU

Upload via RFC

Select an active system and import measurement data to the inbox of the
License Measurement Cockpit. The remote system must be connected
through RFC. This action is implicitly carried out when you start a license
measurement run. You can use this manual step for a better monitoring.

Export to file system

Create an export file with license measurement data. For more
information, see “Creating an export file with license data” on page 160.

6. Start License Measurement

a. Click Start License Measurement.

b. Confirm that you want to start a background job for this. While the
background job is running, License Measurement Cockpit is locked for
other activities.
You can use transaction SM37 to monitor the background job. The status of
the background job is also displayed in the title bar of the inbox.
c. Click Refresh to refresh the status.

7. View measurement results.

After the measurement run is finished, you can view the result.

a. Click Display Latest License Report to open the latest report in PDF
format.

Note: This is not necessarily a report of the most recent measurement

if this ended with errors. It is the report of the last measurement that
ended without errors.
b. Open the Status and Results tab to view a consolidated measurement
grouped by license type. For more information, see “Extended ECM
License Control license types” on page 144. You can print the table, save,
export or send it .
c. Open the Consolidated Users tab to view a consolidated list of users from
all systems. For more information, see “Understanding the consolidated
measurement results” on page 161.

EESPCD230200-IGD-EN-01 Installation Guide 159

Chapter 16 Performing license measurement

16.2.6 Creating an export file with license data

If you want to measure a system that will not be available through an RFC
connection during the actual measurement, you can export the measurement data
from that system to a file and then import this file to the measuring system.

When you create the export file, the remote system must be available through an
RFC connection. The export file will first be uploaded to the inbox and then can be
saved to the local file system.

File types – Measurement data for an SAP system consists of one XML file of file
type SA. Measurement data of a Content Server consists of two files: Content Server
license info of file type CL and Content Server users list of file type CU.

Tip: If the measured system has no connection to the system where you are
going to do the actual measurement, and you cannot create the export file from
remote, you can do the following: In the License Measurement Cockpit of the
measured system, create an entry for an active SAP Client, and then create the
export file and save it to the file system or portable disk. Then import it to the
inbox of the measuring system.

To export a license measurement file:

1. Start License Measurement Cockpit with transaction /OTX/LICENSE.

License Measurement Cockpit starts in standard mode.

2. Click Change to Expert Mode.

3. Select the system, for which you want to create the export file.

4. Click Start License Measurement. License measurement must end without

errors before you can export the file.

5. On the Servers and Inbox for Measurement tab, click Export to File
System.

6. Click Yes to confirm the export.

The export file is created and uploaded to the inbox of the License Measurement
Cockpit. A message box informs you about it.

7. After the import, select a directory to save the export file to.
If you exported measurement data from a Content Server, two files are saved:
First a file of file type CL with the Content Server license, and immediately after
that a file of file type CU with user information.

160 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

16.2.7 Understanding the consolidated measurement results

You can view the results of the license measurement on different levels:

Overview list
On the Status and Result tab, you see the results of the consolidated measurement.
Total number or users, grouped by license type.

Compressed list
On the Consolidated Users tab, you see the Compressed User List of
Consolidation. Users from the measured systems are grouped to unique ID's and
properties. Duplicate users were identified by matching login names. Partition
suffixes of Content Server logins are ignored so that they match the SAP user IDs.

Example: User login on the SAP system is PETER, and user login on Content Server is
peter@partition. Both logins are consolidated into one count.

The yellow status icon indicates inconsistencies or mismatches in license type

assignment. For more information, see “Understanding and resolving licensing
issues” on page 162.

EESPCD230200-IGD-EN-01 Installation Guide 161

Chapter 16 Performing license measurement

Column Count of grouped user IDs contains the number of different logins from
the measured systems that were mapped to one entry in the compressed user list.

Complete list
Click Change view and select Grouped users to view the Complete User List of all
Measured Systems.

Important
If the source system is an SAP Client users with classification types T for
technical users and X for specifically excluded users were not transferred. Also
not transferred are users with invalid Valid from or Valid To dates in the user
management.

Aside from detailed information about the measured system and the user, this list
also contains license type information and the number of days in which the user has
used functions of Archiving, Document Access or Extended ECM. This information
is relevant for users with a license type for occasional users. If this number exceeds
52, an issue is displayed.

16.2.8 Understanding and resolving licensing issues

The license evaluation focusses on issues where a license type assignment is
technically inconsistent or insufficient.

16.2.8.1 Validation issues after consolidation

Validation issues types CA_ARCH, CA_DACC, CA_XECM

This is the same as types CA (Table 16-4) and XEXM_NO_LICENSE (Section 16.2.8.3).

User has permissions to access features of Archiving, Document Access or Extended

ECM but has not sufficient license types.

In single source systems, a license type of Extended ECM is sufficient for usage of
Archiving, Document Access or Extended ECM; a license type for Document Access
is also sufficient for usage of Archiving.

162 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

Validation issues type CO_TRUE

See types CO (Table 16-5) and XECM_MAX_ACCESS_EXCEEDED (Section 16.2.8.3).

At least in one of the measured systems, the user has accessed Archiving, Document
Access or Extended ECM functions on more than 52 days in the past year but none
of his license types is sufficient.

Validation issue type CL

License types sold by OpenText (type O) are mixed with license types of SAP
reselling (type S).

The license type is assigned to SAP logins by roles. Due to the role assignment, it can
occur that a role related to more than one license type is assigned to a user login.
Validation issue type CL occurs if licenses sold by OpenText and SAP are maintained
at the same time for the same user login and client.

In this case, the license type of the highest priority is preferred:

• Extended ECM > Document Access > Archiving

• Full > Occasional > Web

• Professional > ESS, Employee

• License sold by SAP > sold by OpenText

Table 16-3: Users with an OpenText license and an SAP license

ID Description
CL Users with an OpenText license and an SAP
license

Important
As the consolidation merges data of duplicate users, it may be that in some
cases issues that were seen in the single source systems disappear. In other
cases, it may be that new issues are raised.

Example: Content Server user hmueller@ECM has no license type assigned and issue XECM_
NO_LICENSE was indicated.

SAP user hmueller has license type SXECMF Extended ECM Full User sold by SAP and issue
CL was found.

After consolidation, both user entries were identified to belong to the same person. The
resulting license type of this unique user is SXECMF. Therefore the issue XECM_NO_LICENSE
is no longer valid, which means that issue CA_XECM will not be raised for that unique ID. But
issue CL persists and is indicated as the inconsistency between seller models could still be a
source of error.

EESPCD230200-IGD-EN-01 Installation Guide 163

Chapter 16 Performing license measurement

16.2.8.2 Validation issues types on the SAP system

OpenText license measurement checks if the maintained data is consistent. The
system gathers this information for each user in each client and collects counts. If
inconsistent data occur, a validation issue is counted. The validation issue counts are
listed in the OpenText license report. The report lists different types of validation
issues. Details on user level are shown in the list of evaluated users.
Only validation issues of valid dialog users are counted.

Validation issue type CA

User has access permissions to Archiving, Document Access or Extended ECM but
either no or a an insufficient license type was assigned to this user.

For each user, the license type of the highest priority is obtained from the values of
authorization object J_6NLC_TYP authorization object assigned to this user:

• Extended ECM > Document Access > Archiving

• Full > Occasional > Web

In addition, the program checks for access permissions of the user based on other
authorization objects:

• Archiving – S_WFAR_OBJ, S_WFAR_PRI

• Document Access – J_6NG_DATA (EFM, TRM projects excluded if licensing flags
for EFM and TRM are set), J_6NRL_SEA
• Extended ECM – J_6NRL_DOL, J_6NRL_WSC

The following results cause a validation issue:

• if the user is allowed to access a product but the maintained license type is not
sufficient.
• if no license type was maintained for a user.
• if only the wildcard value * is assigned as a license type to a user.

Table 16-4: CA: Maintained OpenText license is not sufficient compared to

license required by access permissions

ID Maintained license type Required product license

ARCH No OpenText license type OpenText Archiving or
maintained SAP Archiving by OpenText
DACC No OpenText license type OpenText Document Access
maintained or
SAP Document Access by
OpenText

164 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

ID Maintained license type Required product license

XECM No OpenText license type OpenText Extended ECM or
maintained SAP Extended ECM by
OpenText
XECMALL Only wildcard values are OpenText Extended ECM or
maintained for OpenText SAP Extended ECM by
license type OpenText
XECMOARCF OpenText Archiving – Full OpenText Extended ECM or
Named User SAP Extended ECM by
OpenText
XECMOARCW OpenText Archiving – Web OpenText Extended ECM or
Named User SAP Extended ECM by
OpenText

Validation issue type CO

User has an “occasional” license type but has accessed Archiving, Document Access
or Extended ECM functions on the SAP system on more than 52 days in the past
year.

License types for occasional usage are maintained when a user is accessing OpenText
applications only occasionally. This concerns, for example, ESS usage, usage as
Employee, or Web usage.

For license measurement, the maintained license type set in authorization object J_
6NLC_TYP is counted. At the same time, the access log entries not older than the
current date -1 year are cross checked in table /OTX/CL_T_ACCESS.

If the count of entries for a user login in a client is greater than 52, and the license
type is classified as a type for occasional usage, this causes a validation issue of type
CO.

Table 16-5: CO: Users with occasional license used the product on more than
52 days per year

ID Description
OARCO OpenText Archiving – Occasional User
OARCW OpenText Archiving – Web Named User
SARCW SAP Archiving by OpenText – User:
Employee, ESS User

Validation issue type CL

License types sold by OpenText (type O) are mixed with license types of SAP
reselling (type S).

The license type is assigned to SAP logins by roles. Due to the role assignment, it can
occur that a role related to more than one license type is assigned to a user login.

EESPCD230200-IGD-EN-01 Installation Guide 165

Chapter 16 Performing license measurement

Validation issue type CL occurs if licenses sold by OpenText and SAP are maintained
at the same time for the same user login and client.

In this case, the license type of the highest priority is preferred:

• Extended ECM > Document Access > Archiving

• Full > Occasional > Web

• Professional > ESS, Employee

• License sold by SAP > sold by OpenText

Table 16-6: Users with an OpenText license and an SAP license

ID Description
CL Users with an OpenText license and an SAP
license

Log table /OTX/CL_T_ACCESS

The log table /OTX/CL_T_ACCESS stores information on daily access to

OpenText ABAP applications per client and user. This data is used in the
license validation. The entries of the table are written by applications
DocuLink, Business Content, Imaging Integration, FullText search, Forms
Management and DesktopLink. Occasional users are entitled to use OpenText
applications up to 52 days/year.

Data older than one year is not required and can be regularly deleted.

To delete log entries older than one year, run transaction se38 to start the
program /OTX/CL_MAINTAIN_ACCESS_LOG. It checks for ACTVT = 03 of
authorization object S_USER_GRP.

The data of this log table has no further relevance beyond license validation.

16.2.8.3 Extended ECM License Metering: Validation issue types on

Content Server

Note: For Extended ECM License Control, no license report is available.

If on Content Server license types are assigned by group assignment, users can have
more than one license type assignment. If multiple license types are assigned to on
user, the most comprehensive license type is used.

XECM_NO_LICENSE
User has access permissions to use Extended ECM features on Content Server but
has no sufficient license type.

166 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 16.2. Extended ECM License measurement

Similar issue on SAP side is CA (Table 16-4) with ACCESS_TYPE = XECM.

XECM_MAX_ACCESS_EXCEEDED
User has an “occasional” license type but has accessed Extended ECM functions on
Content Server on more than 52 days in the past year.

Similar issue on SAP side is CO (Table 16-5).

XECM_MULTIPLE_SELLERS
License types sold by OpenText (type O) are mixed with license types of SAP
reselling (type S).

Similar issue on SAP side is CL (Table 16-6).

EESPCD230200-IGD-EN-01 Installation Guide 167

Chapter 17

Verifying and analyzing the installation

17.1 Analyzing the SAP system

17.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 170.

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 then 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.

EESPCD230200-IGD-EN-01 Installation Guide 169

Chapter 17 Verifying and analyzing the installation

3. Click Execute.

17.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.

If both Content Server and the SAP system are upgraded to 16.2.10, Enterprise
Library is not used anymore and therefore not mentioned in the Diagnostic
Program. This is also indicated by a positive test “Does the REST API replace the
Enterprise Library web service?” in the Service Communication section. For test
entries regarding the Enterprise Library, see a previous version of this guide, for
example Section 23.1.2 “Understanding the details of the Diagnostic Program” in
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK160209-CGD).

Test IMG Activity More Information

Content Server

170 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 17.1. Analyzing the SAP system

Test IMG Activity More Information

Does the connection ID exist? Infrastructure > Maintain Section 22.2.7 “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?
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
For SAP Basis > 7.0: Section 22.2.4.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
For SAP Basis > 7.0: Section 22.2.4.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
Did you provide a logical Infrastructure > Create New Section 22.2.4 “Creating
port for the Content Server Logical Ports logical ports in the SAP
Member Service? system” in OpenText Extended
ECM for SAP Solutions -
Installation and Upgrade Guide
(ERLK-IGD)
Can the Content Server
Member Service be
instantiated?
Did you provide an HTTP Infrastructure > Create New
destination for the Content Logical Ports
Server Member logical port?

EESPCD230200-IGD-EN-01 Installation Guide 171

Chapter 17 Verifying and analyzing the installation

Test IMG Activity More Information

Check the following for the For SAP Basis 7.0: Section 22.2.4 “Creating
Content Server Member Infrastructure > Create logical ports in the SAP
HTTP connection: “No HTTP Connections > HTTP system” in OpenText Extended
Logon” and “Send SAP Connections to External ECM for SAP Solutions -
Logon Ticket” is enabled; Server; double-click one Installation and Upgrade Guide
“HTTP compression” is connection; Logon & (ERLK-IGD)
disabled. Security tab and Special
Options tab.
For SAP Basis > 7.0: Section 22.2.4.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
Can the Content Server Directory Services Section 5.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)
Did you provide a logical Infrastructure > Create New Section 22.2.4 “Creating
port for the Extended ECM Logical Ports logical ports in the SAP
Service? system” in OpenText Extended
ECM for SAP Solutions -
Installation and Upgrade Guide
(ERLK-IGD)
Did you provide an HTTP Infrastructure > Create New
destination for the Extended Logical Ports
ECM logical port?
Check the following for the For SAP Basis 7.0: Section 22.2.4 “Creating
Extended ECM HTTP Infrastructure > Create logical ports in the SAP
connection: “No Logon” and HTTP Connections > HTTP system” in OpenText Extended
“Send SAP Logon Ticket” is Connections to External ECM for SAP Solutions -
enabled; “HTTP Server; double-click one Installation and Upgrade Guide
compression” is disabled. connection; Logon & (ERLK-IGD)
Security tab and Special
Options tab.
For SAP Basis > 7.0: Section 22.2.4.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
Can the Extended ECM
Service be executed?

172 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 17.1. Analyzing the SAP system

Test IMG Activity More Information

Did you provide a logical Infrastructure > Create New Section 22.2.4 “Creating
port for the OTDS Service? Logical Ports logical ports in the SAP
system” in OpenText Extended
ECM for SAP Solutions -
Installation and Upgrade Guide
(ERLK-IGD)
Did you provide an HTTP Infrastructure > Create New
destination for the OTDS Logical Ports
services?
Check the following for the For SAP Basis 7.0: Section 22.2.4 “Creating
OTDS HTTP connection: “No Infrastructure > Create logical ports in the SAP
Logon” and “Send SAP HTTP Connections > HTTP system” in OpenText Extended
Logon Ticket” is enabled; Connections to External ECM for SAP Solutions -
“HTTP compression” is Server; double-click one Installation and Upgrade Guide
disabled. connection; Logon & (ERLK-IGD)
Security tab and Special
Options tab.
For SAP Basis > 7.0: Section 22.2.4.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
Can the OTDS Service be
started?
If impersonation RFC is
provided, can the
impersonation RFC be
executed?
Did you provide a service for Infrastructure > Configure “Configuring the Service
the SPI service SPI Service or Provider Interface service”
configuration? SOAMANAGER transaction on page 132
Check the following for the Infrastructure > Configure “Configuring the Service
SPI service configuration: SPI Service or Provider Interface service”
“Transport Guarantee Type = SOAMANAGER transaction on page 132
HTTPS”; “Authentication:
User ID/Password” is
enabled.
Check that the SPI service is SICF transaction Section 18.4.2 “Frontend:
active in SICF. Activating the ICF services”
in OpenText Extended ECM for
SAP Solutions - Customizing
Guide (ERLK-CGD)

EESPCD230200-IGD-EN-01 Installation Guide 173

Chapter 17 Verifying and analyzing the installation

Test IMG Activity More Information

Is the ict profile parameter The following profile Section 6.2 “SAP system
set properly for the REST parameter must be set: requirements” in OpenText
API? ict/disable_cookie_ Extended ECM for SAP
urlencoding = 1 Solutions - Installation and
Upgrade Guide (ERLK-IGD)
Can the OTDS REST API be Check the OTDS REST API
executed? configuration.
Can the Content Server REST Check the Content Server
API be executed? REST API configuration.
Does the REST API replace Content Server and SAP
the Enterprise Library web system are upgraded to at
service? least 16.2.10 and Enterprise
Library is not used anymore.
HTML Controls
Can an HTML control be
instantiated?
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?
Are the SAP HTTP server
and the OTDS server in the
same domain or is the OTDS
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 parameters Section 22.2.3 “Activating the
parameters set properly? must be set: login/ SSO HTTP service” in
accept_sso2_ticket = 1 OpenText Extended ECM for
and login/create_sso2_ SAP Solutions - Installation
ticket = 2 and Upgrade Guide (ERLK-
IGD)

174 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 17.1. Analyzing the SAP system

17.1.3 Understanding the Configuration Report

You can use the SAP Configuration Report to summarize your Extended ECM for
SAP SolutionsCloud configuration. The report displays system and configuration
parameters coming from customizing transactions and tables. You can use this
information for reference and for debugging. You can export the list to a file.

To run the SAP Configuration Report:

1. In the IMG, navigate to the Extended ECM > Configuration Report activity,
and then click Execute .
The report opens. You can use standard SAP functions to view details, browse
the report, or filter separate lists in the report.

2. To save the report to a local file in, for example in HTML format or as a
spreadsheet, click Local file ..., and select the format that you want.

EESPCD230200-IGD-EN-01 Installation Guide 175

 Part 3
Uninstalling Extended ECM for SAP
Solutions Cloud
Part 3 Uninstalling Extended ECM for SAP Solutions Cloud

This part explains how you can uninstall Extended ECM for SAP SolutionsCloud
and undo related customizing.

178 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 18
General process

You remove Extended ECM for SAP Solutions with the same tool that you use to
install, the SAP Add-On Installation Tool (SAINT).

SAINT shows a new tab for uninstallable components. Before the actual removal,
you must perform mandatory steps. This varies according to your system. There
may also be optional steps, which you can perform to completely clean your system
from Extended ECM remnants.

EESPCD230200-IGD-EN-01 Installation Guide 179

Chapter 18 General process

18.1 Prerequisites for removal

• The SAP system meets the minimum technical requirements for Add-On
removal. For more information, see “Add-On Uninstallation” in the
documentation of SAP Add-on Assembly Kit 5.0 or later (https://help.sap.com/
viewer/p/SAP_ADD-ON_ASSEMBLY_KIT).
• Update SAINT/SPAM to at least version 0066
• Solutions Accelerators must be uninstalled first. Ask OpenText for assistance.
• Components that are built on other components must be uninstalled before the
other.
• There may be manual steps necessary before you can actually remove. For more
information, see the following chapter.

180 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 19
Performing manual steps before removal

Before uninstalling a component, you must perform manual steps to undo

customizing or remove custom code.

You need not undo customizing in the Extended ECM for SAP Solutions component
itself, for example, deleting . These will be deleted with the component’s removal.

Customizing for Extended ECM for SAP Solutionsdone in the SAP system outside
the component itself, need to be undone manually, for example, service entries in
table SGOSATTR related to Extended ECM for SAP Solutions only.

19.1 Extended ECM component OTEXRL

19.1.1 Performing mandatory manual steps before uninstalling
OTEXRL
Important
Import SAP Note 0001476315 Error in activation protocol for switch
framework. If the described error already exists, apply the note manually.

You must apply this note BEFORE you start uninstalling OTEXRL.

Perform the following steps before you uninstall. Otherwise, the uninstallation will
not run or the SAP system will have issues after you removed the component.

Remove Extended ECM Solutions Accelerators

If you installed Solutions Accelerators, you must remove them first. check
OpenText My Support if uninstallation transports are available or contact
OpenText Support.
Remove all Extended ECM Roles and Authorizations from users
Use transaction PFCG to do the following:

• Remove the following roles from all users: /OTX/RM_USER, /OTX/RM_ADMIN, /

OTX/RM_CS_SAP_USER, and /OTX/RM_IMPERSONATED_USER_ROLE.

• Remove the following authorization objects from custom created profiles: /

OTX/RM, J_6NRL_DOL, J_6NRL_LFS, J_6NRL_SEA, J_6NRL_WSC

For more information, see “Assigning SAP roles” on page 110 and “Providing
access to local folders for the Business Content window” on page 40.
Remove custom code depending on Extended ECM code
Custom code includes the following:

EESPCD230200-IGD-EN-01 Installation Guide 181

Chapter 19 Performing manual steps before removal

• Property Providers derived from Extended ECM Property Provider classes.

For more information, see Section 3.2 “Implementing a property provider in
SAP” in OpenText Extended ECM for SAP SolutionsCloud - Customizing Guide
(EESPCD-CGD).

• Generated Mass creation reports. For more information, see Section 25.1
“SAP: Creating or updating business workspaces using batch operations” in
OpenText Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-
CGD).

• Implementations of Extended ECM BAdIs, for example the Business Content

Window menu BAdI. For more information, see .

• All other custom code using Extended ECM code.

Remove customizing of Generic Object Services (Table SGOSATTR)

Start the SM30 transaction and enter SGOSATTR in the Table/View field. Click
Maintain.
Remove all entries for the Extended ECM Business Content Window. Adapt the
Next service field of predecessor entry of the removed Extended ECM entry to
point to the following entry if there are any. For more information, see Section
14.1 “Customizing the Generic Object Services (SAP GUI)” in OpenText Extended
ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD).

Delete jobs for Extended ECM

• Business Workspace Mass creation jobs. For more information, see Section
25.1 “SAP: Creating or updating business workspaces using batch
operations” in OpenText Extended ECM for SAP SolutionsCloud - Customizing
Guide (EESPCD-CGD).

• Document Declaration creation jobs. For more information, see Section 25.2
“SAP: Declaring ArchiveLink documents using batch operations” in
OpenText Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-
CGD).

• Remove Deleted Records job. For more information, see Section 25.6 “SAP:
Scheduling jobs for removing deleted records” in OpenText Extended ECM for
SAP SolutionsCloud - Customizing Guide (EESPCD-CGD).

• Delete the asynchronous queue job. For more information, see Section 3.18.2
“Setting queue properties” in OpenText Extended ECM for SAP SolutionsCloud
- Customizing Guide (EESPCD-CGD).

• Any other job using Extended ECM Reports.

Remove Logical Ports created for Extended ECM

Depending on your SAP version, use the LPCONFIG transaction or SOAMANAGER.
For more information, see “Creating logical ports in the SAP system”
on page 118.

182 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.2. Extended ECM for SAP ERP, S/4HANA component OTEXRLE

Remove the SPI service

For more information, see “Configuring the Service Provider Interface service”
on page 132.
Remove Event Type Linkages, which are using Extended ECM function modules
Use the SWETYPV transaction. For more information, see the following:
Section 7.2 “SAP: Linking events to receiver type function modules” in OpenText
Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD)
Section 5.1.10 “Configuring automatic document declaration” in OpenText
Extended ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD)
Change Document events for automatic policy assignment
For more information, see Section 7.4 “SAP: Maintaining change document
events” in OpenText Extended ECM for SAP SolutionsCloud - Customizing Guide
(EESPCD-CGD).

19.1.2 Performing optional manual steps before uninstalling

OTEXRL
The following steps are optional but recommended to achieve a clean SAP system.
Uninstalling the component will work even if you do not perform these steps.

• Remove HTTP/RFC Connections created in the SM59 transaction for Extended

ECM. For more information, see Section 22.2.4 “Creating logical ports in the SAP
system” in OpenText Extended ECM for SAP Solutions - Installation and Upgrade
Guide (ERLK-IGD)“Creating logical ports in the SAP system” on page 118.
• Change Document Events set up for Extended ECM. For more information, see
Section 7.4 “SAP: Maintaining change document events” in OpenText Extended
ECM for SAP SolutionsCloud - Customizing Guide (EESPCD-CGD).

Note: Before you delete an event, make sure that it is not used for any other
purpose than Extended ECM.

19.2 Extended ECM for SAP ERP, S/4HANA

component OTEXRLE

EESPCD230200-IGD-EN-01 Installation Guide 183

Chapter 19 Performing manual steps before removal

19.2.1 Performing mandatory manual steps before uninstalling

OTEXRLE
The following steps need to be performed before uninstalling Extended ECM for
SAP Solutions for SAP ERP, S/4HANA (component OTEXRLE).

You must perform these mandatory steps before the uninstalling the OTEXRLE
component. Otherwise uninstalling process will not run or the SAP system will have
issues after you removed the component.

Delete jobs for Extended ECM ERP

• DMS Document Declaration creation job. For more information, see Section
28.5 “SAP: Declaring SAP DMS documents using batch operations” in
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
• Any other job using Extended ECM ERP Reports.

Remove Event Type Linkages using Extended ECM ERP function modules
Use the SWETYPV transaction. For more information, see Section 6.2.2.6 “SAP:
Linking events to a receiver function module” in OpenText Extended ECM for
SAP Solutions - Customizing Guide (ERLK-CGD).
Remove Extended ECM ERP Roles
Use PFCG transaction to remove the /OTX/RMERP_DMS_TECH_USER_ROLE from all
users. For more information, see Section 6.2.3.2 “SAP: Creating a technical user
and a technical user role” in OpenText Extended ECM for SAP Solutions -
Customizing Guide (ERLK-CGD).
Remove custom code depending on Extended ECM code
Custom code includes the following:

• Property Providers derived from the DMS Workspace Property Provider

class /OTX/RMERP_CL_WSPP_DMS_DOC. For more information, see Section
6.2.2.1 “SAP: Creating business object declarations” in OpenText Extended
ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
• All other custom code using Extended ECM ERP code.

184 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.3. Extended ECM CRM component OTEXRLC

19.2.2 Performing optional manual steps before uninstalling

OTEXRLE
The following steps are optional but recommended to achieve a clean SAP system.
Uninstalling the component will work even if you do not perform these steps.

• Remove SAP role Z_DMS_RM_IMPERSONATION from users and delete role.

• Delete RFC destination OTX_DMS_RM_TECH_USER.
• Delete techical user DMS_RM_TECH.

For more information, see Section 6.2.3 “Creating a technical user” in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

19.3 Extended ECM CRM component OTEXRLC

19.3.1 Performing mandatory manual steps before uninstalling
OTEXRLC
These steps need to be performed before uninstalling Extended ECM for CRM
(component OTEXRLC).

Important
You must perform these mandatory steps before uninstalling the OTEXRLC
component, otherwise the CRM Web UI will not work correctly anymore.

Deleting the integration into CRM Web Client UI

You must remove all enhancements that you implemented for CRM objects for the
integration into CRM Web Client UI.

The following uses the CRM object Business Partner BP_HEAD to explain how you
remove enhancements.

Important
You must repeat this procedure for all other enhancements that you created.
For more information, see Section 19.1 “Customizing the integration into SAP
CRM Web Client UI or S/4CRM” in OpenText Extended ECM for SAP
SolutionsCloud - Customizing Guide (EESPCD-CGD).

To remove the integration into CRM Web Client UI:

1. Start the BSP_WD_CMPWB transaction, and then open the BP_HEAD component
with the enhancement set.

2. Delete the component controller enhancement:

a. In the Component Structure Browser, right-click Component >

Component Controller and select Delete Enhancement.

EESPCD230200-IGD-EN-01 Installation Guide 185

Chapter 19 Performing manual steps before removal

b. In the following pop-up window, select all rows and delete them, for
example Custom Controller, Controller Implementation, and Context.

3. Remove Workspace and Business Reference Assignment Blocks from the View
Set Configuration.

a. In the Runtime Repository Editor, click View Sets > ViewSet BP_HEAD,
for example.
b. Open the Configuration tab, and then double-click Edit.
c. Move the following Extended ECM Assignment Blocks to the left list of
Available Assignment Blocks:

• /OTX/RMCRM_GS_ECMLK/WrkSpceWindow
• /OTX/RMCRM_GS_ECMLK/BusRefWindow

186 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.3. Extended ECM CRM component OTEXRLC

4. Delete the component enhancement: Click Delete Component Enhancement

and confirm that you want to delete the runtime repository and the BSP
application.

Deleting the integration into SAP CRM Interaction Center Web

Client UI
You must remove all enhancements that you implemented for CRM objects for the
integration into CRM Web Interaction Center Client UI.

The following uses the CRM component IUICOVW to explain how you remove
enhancements.

EESPCD230200-IGD-EN-01 Installation Guide 187

Chapter 19 Performing manual steps before removal

Important
You must repeat this procedure for all other enhancements that you created.
For more information, see Section 19.2 “Customizing the integration into SAP
CRM Interaction Center Web Client UI” in OpenText Extended ECM for SAP
SolutionsCloud - Customizing Guide (EESPCD-CGD).

To remove the integration into SAP CRM Interaction Center:

1. Start the BSP_WD_CMPWB transaction, and then open the IUICOVW component
with the enhancement set.

2. Delete the component controller enhancement:

a. In the Component Structure Browser, right-click Component >

Component Controller, and then select Delete Enhancement.

b. In the following pop-up window, select all rows and delete them, for
example Custom Controller, Controller Implementation, and Context.

3. Delete the view controller enhancement:

a. In the Component Structure Browser, right-click View > IUICOV/

AccOvwNac, and then select Delete Enhancement.

b. In the following pop-up window, select all rows and delete them, for
example Controller, View, View Controller Implementation, and Context.

188 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.3. Extended ECM CRM component OTEXRLC

4. Delete the component enhancement: Click Delete Component Enhancement,

and then confirm that you want to delete the runtime repository and the BSP
application.

Deleting the integration into SAP CRM Web Client email screen
You must remove all enhancements that you implemented for the integration into
CRM Web Client email screen.

To delete the integration into SAP CRM Web Client email screen:

1. Start the BSP_WD_CMPWB transaction and open the BT126H_MAIL component with
the enhancement set.

2. Delete the view controller enhancement:

a. In the Component Structure Browser, right-click View > IBT126H_MAIL/

send_screen, and then select Delete Enhancement.

b. In the following pop-up window, select all rows and delete them, for
example Controller, View, View Controller Implementation, and Context.

3. Delete the component enhancement: Click Delete Component Enhancement,

and then confirm that you want to delete the runtime repository and the BSP
application.

Deleting the integration into SAP CRM Interaction Center email

screen
You must remove all enhancements that you implemented for the integration into
CRM Interaction Center email screen.

To delete the integration into SAP CRM Web Client email screen:

1. Start the BSP_WD_CMPWB transaction and open the CRMCMP_CSS_EML component

with the enhancement set.

2. Delete the view controller enhancement:

a. In the Component Structure Browser, right-click View >

CRMCMP_CSS_EML/MailAttachments, and then select Delete
Enhancement.

b. In the following pop-up window, select all rows and delete them, for
example Controller, View, View Controller Implementation, and Context.

3. Delete the component enhancement: Click Delete Component Enhancement,

and then confirm that you want to delete the runtime repository and the BSP
application.

EESPCD230200-IGD-EN-01 Installation Guide 189

Chapter 19 Performing manual steps before removal

19.4 Extended ECM SRM component OTEXRLS

Can be uninstalled without additional tasks.

19.5 Extended ECM OData Services component

OTEXRLO
19.5.1 Performing mandatory manual steps before uninstalling
OTEXRLO
To clean up the Fiori backend and frontend systems, you reverse the customizing
you did before. This is described in:

• Clean-up roles on frontend and backend systems.

• Remove alias assignments, services and nodes of the OData service /OTX/RM_
WSC_ODATA_SRV on the frontend system.

• Optional: Delete the ICF node <default_host>/sap/opu/odata/otx/rm_wsc_

odata_srv on the frontend system.

• If the backend on which you plan to do the uninstallation of OTEXRLO is the last
backend providing data for /OTX/RM_WSC_ODATA_SRV to your Fiori frontend
system, then please make sure to also remove all Extended ECM applications on
the frontend system. See next section about OTEXRLF for details.

To clean-up role assignments and delete roles:

1. Run the PFCG transaction.

2. Find all roles that you created for Extended ECM.

3. Remove the user assignments, and, optionally, delete the roles.

Remove alias assignments, services and ICF nodes on the frontend system:

1. On an active frontend system, do the following:

a. Run the /IWFND/MAINT_SERVICE transaction.

b. Find the /OTX/RM_WSC_ODATA_SRV service: Namespace = /OTX/, External
Service Name = RM_WSC_ODATA_SRV.
c. If the service is available, check if the list of system aliases for that service
contains an alias, which refers to the SAP server on which you are going to
remove the OTEXRLO component.
d. Delete the system alias from that list.
e. Optional If there is no further alias assigned to service /OTX/RM_WSC_ODATA_
SRV, you can do the following:

190 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.6. Extended ECM Fiori Apps component OTEXRLF

i. Delete or deactivate its ICF node. There is a manage ICF Node menu
for the service. Or you may search in transaction SICF for <default_
host>/sap/opu/odata/otx/rm_wsc_odata_srv
ii. Delete the service from the list.
f. Optional If you do not have another need for the system alias, you can
remove it in transaction /UI2/GW_SYS_ALIAS.
2. If service /OTX/RM_WSC_ODATA_SRV has no aliases assigned or has been deleted
completely, make sure that there is no active Fiori app running on the frontend
system, which uses the Fiori app of OTEXRLF.

19.6 Extended ECM Fiori Apps component OTEXRLF

19.6.1 Performing mandatory manual steps before uninstalling
OTEXRLF
To clean up the Fiori frontend system, you reverse the customizing you did before.
This is described in Section 18 “Integrating Extended ECM for SAP SolutionsCloud
into SAP Fiori apps” in OpenText Extended ECM for SAP SolutionsCloud - Customizing
Guide (EESPCD-CGD).

• Identify and delete Extended ECM related applications both cross-client and
client-specific on the frontend system.
• Clean-up roles on the frontend.
• Remove alias assignments, services and nodes of the OData service /OTX/
RM_WSC_ODATA_SRV. For more information, see “Remove alias assignments,
services and ICF nodes on the frontend system:“ on page 190.

To identify Extended ECM related applications:

1. Find a Business Object Browsing Fiori app based on OpenText Business Center.
On the SAP backend system on which the Business Center configuration is
maintained, search for entries of database table /OTX/PF62_T_PERV with
column BSP_APPL containing a pattern *OTX/RMF*. This leads you to the
Perspective IDs, which are integrating Extended ECM apps. You have the
following options.
Use the Perspective maintenance of Business Center to remove the usage of
Extended ECM Perspective views.
If specific target mappings exist on the frontend system, deleted the mappings
with the Fiori Launchpad Designer.
2. Find an Extended ECM app. On the frontend system, run transaction /UI2/
FLIA to open the Fiori Launchpad Intent Analysis. Find intents, which use
pattern */otx/rmf* in column Launchpad Application.
3. Find custom apps, which are extended with Extended ECM app. Run
transaction /UI2/FLIA to open the Fiori Launchpad Intent Analysis. Identify
custom Fiori apps, which integrated Extended ECM controls by code extension.

EESPCD230200-IGD-EN-01 Installation Guide 191

Chapter 19 Performing manual steps before removal

To delete Extended ECM related applications:

Make sure that you are deleting only apps, which you do not need anymore.

1. Run the /ui2/flpd_conf transaction and logon to the Fiori Launchpad

Designer cross-client.
2. Find the Extended ECM application, and drag it to the recycle bin icon, which
occurs once you start dragging.
3. Repeat with all Extended ECM applications.
4. Run the /ui2/flpd_cust transaction and delete all client-specific Extended
ECM applications.

To clean-up role assignments and delete roles:

1. Run the PFCG transaction.

2. Find all roles that you created for Extended ECM.
3. Remove the user assignments, and, optionally, delete the roles.

19.7 Extended ECM Business Scenarios component

OTEXRLSA
19.7.1 Performing mandatory manual steps before uninstalling
OTEXRLSA
The following steps need to be performed before uninstalling Extended ECM
Business Scenarios (component).

You must perform these mandatory steps before the uninstalling the OTEXRLSA
component. Otherwise uninstalling process will not run or the SAP system will have
issues after you removed the component.

Remove event type linkages using Extended ECM Business Scenarios function
modules
Use the SWETYPV transaction. For more information, see:

• Section 6.2.2.6 “SAP: Linking events to a receiver function module” in

OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
• Section 5.4 “SAP: Maintaining change document events” in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
• Section 6.1.10 “Configuring automatic document declaration” in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
• Section 7.5 “Enabling automatic policy assignment for changed role
assignments” in OpenText Extended ECM for SAP Solutions - User Management
and Access Control Scenarios (ERLK-CUM)

192 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.8. Archiving and Document Access component OTEXBAS

Remove custom code depending on Business Scenario code

Custom code includes the following:

• Property providers derived from the property provider classes

• All other custom code using artifacts of development class /OTX/RLSA and its
subordinates

19.8 Archiving and Document Access component

OTEXBAS
19.8.1 Performing mandatory manual steps before uninstalling
OTEXBAS
You must perform these steps before you start the uninstallation. Otherwise, the
uninstallation will fail or the system may be corrupt afterwards.

• Run the su02 transaction to remove the following profiles:

J_6NG_ALL J_6NG_CREA J_6NG_C_DISP

J_6NG_C_EDIT J_6NG_DELE J_6NG_DISP
J_6NG_MIN J_6NG_STDALL J_6NG_STFALL
J_8AFM_ADM J_8AFM_ALL J_8AFM_DISP

• Use the PFCG to remove the following authorization objects from custom created
roles/profiles for DocuLink, Archiving, and Licensing:

J_6NG_PROJ J_6NG_DATA J_6NG_DATA

J_6NB_CUST J_6NB_CLAS J_6NB_PROD
J_6NG_STDO J_6NG_STFL J_6NB_PRCU
J_6NLC_TYP J_6NX_SWF J_6NV_WEBV

• Delete all custom implementations and objects, which refer to data dictionary
objects delivered by Add-On OTEXBAS.

– Remove the function modules for custom or user exits:

○ Section 22.3.6.3.1.6 “User exits tab” in OpenText Archiving and Document

Access for SAP Solutions - Scenario Guide (ER-CCS)
○ Section 22.3.6.4.1 “User exits” in OpenText Archiving and Document Access
for SAP Solutions - Scenario Guide (ER-CCS)
○ Section 22.4.4.4 “Defining Rendition Server task profiles” in OpenText
Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS)
○ Section 11.1.5.5 “Maintaining customer exits” in OpenText Archiving and
Document Access for SAP Solutions - Scenario Guide (ER-CCS)

EESPCD230200-IGD-EN-01 Installation Guide 193

Chapter 19 Performing manual steps before removal

– Remove the storage tables for the ArchiveLink attributes, which make use of
data elements, domains or structures of OTEXBAS.

○ If no data records in those tables are required anymore, you can delete the
tables.

○ If you still require the data, please replace any references to OpenText
data dictionary objects with other objects accordingly.

○ Section 21.2 “Customizing additional ArchiveLink attributes” in OpenText

Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS)

• Remove the customizing of the Generic Object Services in the table SGOSATTR .
You must remove entries for DocuLink or DesktopLink. Adapt the Next service
field of predecessor entry of removed entry to point to the following entry if any.

– Section 12 “Archiving using generic object services (GOS)” in OpenText

Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS)

– Section 21.1 “Customizing the Business Content window in the GOS menu”
in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide
(ER-CCS)

19.8.2 Performing optional manual steps before uninstalling

OTEXBAS
These steps will not prevent uninstalling component and cause no issues on SAP
system if not executed, but are recommended to clean up the SAP system.

• DocuLink – Delete all generated programs. For more information, see Section
25.1 “Administrating (deleting) generated programs” in OpenText DocuLink for
SAP Solutions - Customizing and Administration Guide (DC-CGD).

• If you do not have any movable data of SAP Records Management, you can
remove some predefined element types. For more information, see Section 13.3.1
“Providing element types in the SAP NetWeaver Folders Management system”
in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-
CCS).
Run the SRMREGEDIT transaction. Delete the following nodes:
S_AREA_RMS > /IXOS/RM_SP620_DC > /IXOS/SRM_SPS_CUSTOMER

S_AREA_RMS > /IXOS/RM_SP620_DC

S_AREA_RMS > SRM_SP_AL_DOCUMENT > /IXOS/RM_SPS_AL_DOC_INVOICES

S_AREA_RMS > SRM_SP_MODEL > /IXOS/RM_SPS_MODEL_INVOICES.

S_AREA_RMS > SRM_SP_RECORD > /IXOS/RM_SPS_RECORD_INVOICES

S_AREA_RMS > RMS_ID > /IXOS/RM_COLD_PROJECT

194 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.9. Archiving and Document Access ERP package component OTEXERP

19.9 Archiving and Document Access ERP package

component OTEXERP
19.9.1 Performing mandatory manual steps before uninstalling
OTEXERP
You must perform these steps before you start the uninstallation. Otherwise, the
uninstallation will fail or the system may be corrupt afterwards.

Similar to OTEXBAS, remove custom implementations of DocuLink, DesktopLink or

ArchiveLink PLUS referring to data dictionary objects of OTEXERP. Replace such
references with other object references or remove the using objects, if they are not
required any more. For more information, see “Archiving and Document Access
component OTEXBAS” on page 193.

19.10 Archiving and Document Access CRM package

component OTEXCRM
19.10.1 Performing mandatory steps before uninstalling
OTEXCRM
You must perform these steps before you start the uninstallation. Otherwise, the
uninstallation will fail or the system may be corrupt afterwards.

Similar to OTEXTBAS, remove custom implementations of DocuLink, DesktopLink

or ArchiveLink PLUS referring to data dictionary objects of OTEXERP. Replace such
references with other object references or remove the using objects, if they are not
required any more. For more information, see “Archiving and Document Access
component OTEXBAS” on page 193.

If you integrated DocuLink views into the IC Web client, undo the customizing in
reverse order to delete any customizing from the IC WebClient:

• Section 18.3.1.3 “Adapting the navigation bar profile” in OpenText DocuLink for
SAP Solutions - Customizing and Administration Guide (DC-CGD)
• Section 18.3.1.2 “Configuring the transaction launcher” in OpenText DocuLink for
SAP Solutions - Customizing and Administration Guide (DC-CGD)
• Section 18.3.1.1 “Creating a transaction launcher URL” in OpenText DocuLink for
SAP Solutions - Customizing and Administration Guide (DC-CGD)

If the SAP CRM system has an upgrade history starting from old CRM 5.0 and using
OTEXBAS 10.0 or lower in its past, there may still be residuals of old customizing of
the IC Win Client integration. Undo the customizing of the 10.0 version in reverse
order:

EESPCD230200-IGD-EN-01 Installation Guide 195

Chapter 19 Performing manual steps before removal

Note: The following links point to the 10.0 version of OpenText DocuLink for
SAP Solutions - Customizing and Administration Guide (DC100000-CGD).

• Section 19.3.1.4 “Adapting the CIC profile” in OpenText DocuLink for SAP
Solutions - Customizing and Administration Guide (DC100000-CGD)
• Section 19.3.1.3 “Defining a component profile for the workspace” in OpenText
DocuLink for SAP Solutions - Customizing and Administration Guide (DC100000-
CGD)
• Section 19.3.1.2 “Creating a new workspace” in OpenText DocuLink for SAP
Solutions - Customizing and Administration Guide (DC100000-CGD)
• Section 19.3.1.1 “Creating a new workspace class” in OpenText DocuLink for SAP
Solutions - Customizing and Administration Guide (DC100000-CGD)

19.11 Archiving and Document Access OData Services

component OTEXBASO
19.11.1 Performing mandatory steps before uninstalling
OTEXBASO
You must perform these steps before you start the uninstallation. Otherwise, the
uninstallation will fail or the system may be corrupt afterwards.

To clean up the Fiori backend and frontend systems, you reverse the customizing
you did before. For more information, see Section 18 “Integrating Extended ECM for
SAP SolutionsCloud into SAP Fiori apps” in OpenText Extended ECM for SAP
SolutionsCloud - Customizing Guide (EESPCD-CGD).

• Clean up roles on frontend and backend system.

• Remove alias assignments, services and nodes of the OData service /OTX/ALDS_
ODATA_SRV on the frontend system.

• Optionally, delete the ICF node <default_host>/sap/opu/odata/otx/alds_

odata_srv on the frontend system.

• If the backend, on which you plan to remove OTEXBASO, is the last backend
providing data for /OTX/ALDS_ODATA_SRV to your Fiori frontend system, remove
all Extended ECM for SAP Solutions applications on the frontend system. For
more information, see “Archiving and Document Access Fiori Apps component
OTEXBASF” on page 197.

To clean-up role assignments and delete roles:

1. Run the PFCG transaction.

2. Find all roles that you created for Extended ECM.

3. Remove the user assignments, and, optionally, delete the roles.

196 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 19.12. Archiving and Document Access Fiori Apps component OTEXBASF

Remove alias assignments, services and ICF nodes on the frontend system:

1. On an active frontend system, do the following:

a. Run the /IWFND/MAINT_SERVICE transaction.

b. Find the /OTX/RM_WSC_ODATA_SRV service: Namespace = /OTX/, External
Service Name = RM_WSC_ODATA_SRV.
c. If the service is available, check if the list of system aliases for that service
contains an alias, which refers to the SAP server on which you are going to
remove the OTEXRLO component.
d. Delete the system alias from that list.
e. Optional If there is no further alias assigned to service /OTX/RM_WSC_ODATA_
SRV, you can do the following:

i. Delete or deactivate its ICF node. There is a manage ICF Node menu
for the service. Or you may search in transaction SICF for <default_
host>/sap/opu/odata/otx/rm_wsc_odata_srv
ii. Delete the service from the list.
f. Optional If you do not have another need for the system alias, you can
remove it in transaction /UI2/GW_SYS_ALIAS.

2. If service /OTX/RM_WSC_ODATA_SRV has no aliases assigned or has been deleted

completely, make sure that there is no active Fiori app running on the frontend
system, which uses the Fiori app of OTEXRLF.

19.12 Archiving and Document Access Fiori Apps

component OTEXBASF
19.12.1 Performing mandatory steps before uninstalling
OTEXBASF
You must perform these steps before you start the uninstallation. Otherwise, the
uninstallation will fail or the system may be corrupt afterwards.

To clean up the Fiori backend and frontend systems, you reverse the customizing
you did before. For more information, see Section 18 “Integrating Extended ECM for
SAP SolutionsCloud into SAP Fiori apps” in OpenText Extended ECM for SAP
SolutionsCloud - Customizing Guide (EESPCD-CGD).

• Identify and delete applications related to Extended ECM for SAP Solutions both
cross-client and client-specific on the frontend system.
• Clean-up roles on the frontend system.
• See in previous section, the manual steps before uninstalling of component
OTEXBASO, how to remove alias assignments, services and nodes of the OData
service /OTX/ALDS_ODATA_SRV.

EESPCD230200-IGD-EN-01 Installation Guide 197

Chapter 19 Performing manual steps before removal

To identify applications related to Archiving and Document Access:

1. Find a Business Object Browsing Fiori app based on OpenText Business Center.
On the SAP backend on which the Business Center configuration is maintained,
search for entries of database table /OTX/PF62_T_PERV with column BSP_APPL
containing a pattern *OTX/ALF*. This leads to the Perspective ID’s integrating
Archiving and Document Access apps. You have the following options:
Use the Perspective maintenance of Business Center to remove the usage of
Archiving and Document Access Perspective views.
If specific target mappings exist on the frontend, delete the mappings with the
Fiori Launchpad Designer.
2. Find a Archiving and Document Access app. On the frontend system,
run /UI2/FLIA to open the Fiori Launchpad Intent Analysis. Find intents,
which use pattern */otx/alf*, or have the value for test launcher = /sap/bc/
ui5_ui5/otx/rmf_launch in column Launchpad Application.

3. Find custom apps, which are extended with Archiving and Document Access
app. Run transaction /UI2/FLIA to open the Fiori Launchpad Intent Analysis.
Identify custom Fiori apps, which integrated Archiving and document Access
controls by code extension.

To delete applications related to Archiving and Document Access:

Make sure that you are deleting only apps, which you do not need anymore.

1. Run the /ui2/flpd_conf transaction and logon to the Fiori Launchpad

Designer cross-client.

2. Find the Archiving and Document Access application, and drag it to the recycle
bin icon, which occurs once you start dragging.

3. Repeat with all Archiving and Document Access applications.

4. Run the /ui2/flpd_cust transaction and delete all client-specific Archiving

and Document Access applications.

To clean-up role assignments and delete roles:

1. Run the PFCG transaction.

2. Find all roles that you created for Archiving and Document Access.

3. Remove the user assignments, and, optionally, delete the roles.

198 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

Chapter 20
Removing with the SAINT transaction

You use the SAINT transaction for the removal. You can first use it in test mode to
simulate an uninstallation process before you actually run it.

To use SAINT in test mode:

1. From the menu, select Extras > Settings.

2. On the Import Queue tab, select the Test option.

3. Click Confirm.

4. Perform the uninstallation. If it reports errors, you can view error logs, continue
or roll back.

5. Clear the Test option if the test mode did not report errors.

To remove a component with SAINT:

1. In the SAINT transaction, open the Uninstallable components tab.

2. Select what you want to remove.

3. Click Start.

EESPCD230200-IGD-EN-01 Installation Guide 199

Glossary
ArchiveLink
An interface between the SAP system and an archiving system. Using
ArchiveLink, mostly static and finished documents are stored. ArchiveLink
documents can be declared in Extended ECM.

attribute
Content Server concept to store metadata. Attributes are organized in categories.
Business properties of a business object are mapped to attributes.

BAdI

See: Business Add-In (BAdI)

Business Add-In (BAdI)

SAP method to enhance standard SAP functions with custom functionality.

Business Content window

Window in SAP ERP that contains content, which is related to the business object.
The Business Content window can be opened in an SAP ERP system from the
Generic object services (GOS) menu of a business object. The Business Content
window displays the business workspace and its content, business attachments,
business documents (ArchiveLink), notes and local files.

business object
Representation of a “real-life” object in the business application. This can be, for
example, a business partner, a service process, or a product. Business objects are
the center point of Extended ECM.

Business Workspaces
Content Server core module that enables the use of business workspaces with or
without a connection to a business application.

business attachment
Content Server item, for example a document or a folder, that is added as a link to
the business workspace of a business object. The item, which is used as business
attachment elsewhere, is indicated by an icon and has a link to the respective
business object. The other way around, you can configure a business object type,
so that it can be added to a Content Server item.

business object type

Configuration item for business objects in Content Server. The business object
type describes the structure of the data. A business object type in Content Server
has its counterpart in the business application.

EESPCD230200-IGD-EN-01 Installation Guide 201

Glossary

business workspace
Content Server item that contains documents and other items which are related to
a business object.

cases and binders

See: business workspace

category
Content Server concept to store metadata. A category contains attributes or
attribute sets. A category can be mapped to store metadata delivered from the
business application.

Classic UI

See: Classic View

Classic View
Content Server user interface with folders, function menus and sidebars. As
opposed to Content Server Smart View. Not used in Business Workspaces.
See also: Smart UI

classification
Classifications are used to categorize Content Server items, for example,
documents, compound documents, and folders into a taxonomy of Classifications
called Classification Trees. For business workspaces, classifications control what
kind of business workspace can be created in a certain folder.

declaration

See: document declaration

document declaration
Definition of how a document is to be stored in Archive Center via ArchiveLink.

document metadata
Describes the document and its business context. Different types of documents
may have different metadata assigned. Metadata can be used to search for a
document.

document properties
Set of attributes that all documents share; for example, the owner of a document
or the creation date.

202 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Glossary

document templates
Templates for documents with default content and attributes.
See also: workspace templates

Generic Object Services (GOS)

SAP: Functions that are not application-specific and can generally be used for any
business object, e.g. creating or displaying the business workspace.

GOS

See: Generic Object Services (GOS)

group replacement
Method to dynamically assign access rights for a Content Server item such as a
business workspace or a document to a group of users. The group replacement is
typically based on attributes of the Content Server item.

impersonation
Method in which users of the business application utilize other users to gain
access to Content Server. Impersonation must be implemented according to the
requirements of the business application.

indexing
Process of collecting data about Content Server items so that they can be searched
with Content Server search functionality.

integration widget
Enables an integration method to display Content Server content in HTML-based
application. Content is displayed with JavaScript and HTML5 technology rather
than embedding the classical Content Server user interface.

OpenText Directory Services (OTDS)

A repository of user information and a collection of services to manage this user
information. OTDS is used by Content Server for user authentication.

OpenText Records Management

Content Server module that controls documents and other objects based on rules
and classifications. Compliance and other legal regulations require that
documents have a controlled life cycle, that they are archived, that they can be
frozen, or that they are deleted after a certain time. Records Management also
controls access to the documents. To set a document under the regulations of
Records Management, it is declared as record.

OSS notes

See: SAP Notes

EESPCD230200-IGD-EN-01 Installation Guide 203

Glossary

OTDS

See: OpenText Directory Services (OTDS)

perspective
Controls how users see the layout of a business workspace in Content Server
Smart View. Perspectives consider rules, for example, the workspace type,
template, or the user group. You design and configure a perspective in
Perspective Manager, a tool that walks you through the creation of a perspective
and translates it into ActiveView coding.

Perspective Manager

See: perspective

policies
Method to transfer and apply SAP authorization objects in Content Server.

print lists
Documents that are created by the SAP system and, if necessary, can be processed
automatically. They represent extracts from the SAP data base, compiled
according to specific criteria, and created by reports.

property provider
Program or web service that delivers properties of a business object from the
business application to Content Server.

record

See: OpenText Records Management

Records Management

See: OpenText Records Management

relationship
Hierarchical relationship between business objects that are visualized as
relationships between business workspaces. A sidebar widget and Related
Workspaces Folders make related business workspaces visible in Classic View. In
Smart View, a Related Workspaces widget makes related business workspaces
visible. Automatic relationships are defined in the property provider. Users can
establish manual relationships.

204 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01

 Glossary

RFC service
A program used for communication between the SAP application and the archive
system via RFC (Remote Function Calls).

SAP Notes
Notes provided by SAP that contain post-release changes or corrections for
already released versions of SAP products. When you encounter SAP-specific
problems or false behavior in SAP programs, especially after or during a new
installation of product components, check the SAP Support Portal for necessary
SAP notes.

SAP Reference IMG (SPRO)

A tool for customizing in the SAP system, opened with the SPRO transaction.

SAP Business Add-In

See: Business Add-In (BAdI)

sidebar widget
Element of a business workspace in Classic View that displays various types of
business workspace metadata and information to the end user.

simple search
Saved query and customized search form that can be used to find business
workspaces, cases and binders, and to create shortcuts. Also known as Custom
View Search in Content Server.

Smart UI

See: Smart View

Smart View
Content Server user interface with a landing page and container pages. The
content is presented in tiles that contain widgets. The pages are highly
configurable using the Perspective Manager.

SPRO

See: SAP Reference IMG (SPRO)

system attributes
Metadata that all content items have in common, for example item names, creator
of an item, or the modification date.

widget
Element of the user interface that displays information for the user.

EESPCD230200-IGD-EN-01 Installation Guide 205

Glossary

workspace reference
Business object that is linked to a business workspace. If the business workspace
already exists, users add the business object as business reference to it.

workspace templates
Templates for new business workspaces with default configuration, folder
structure, and optionally default content. Templates are offered to the user based
on the classification and the storage location of the new document.

workspace type
Content Server object that controls the location where a business workspace is
stored, some of the GUI components such as sidebar widgets, and the name
pattern of the business workspace.

206 OpenText™ Extended ECM for SAP® Solutions Cloud EESPCD230200-IGD-EN-01