OpenText Extended ECM For SAP Solutions CE 21.4 - Installation and Upgrade Guide English (ERLK210400-IGD-En-03)

OpenText™ Extended ECM for SAP®
Solutions
Installation and Upgrade Guide
This guide describes how to plan the installation, how to install

the SAP® and the OpenText™ Content Server components of
OpenText Extended ECM for SAP Solutions, and how to set up
the communication between SAP and Content Server. It also
contains upgrade information.
ERLK210400-IGD-EN-03
OpenText™ Extended ECM for SAP® Solutions
Installation and Upgrade Guide
ERLK210400-IGD-EN-03
Rev.: 2021-Dec-13
This documentation has been created for OpenText™ Extended ECM for SAP® Solutions CE 21.4.
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 © 2021 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 .......... 11
1.1 Related documentation .................................................................... 11
Part 1 Planning the installation of Extended ECM for SAP

Solutions 13
2 Overall architecture ................................................................. 15

2.1 Persistence layer ............................................................................ 16
2.2 Network and communication layer .................................................... 16
2.3 Business logic layer ........................................................................ 17
2.4 Presentation layer ........................................................................... 17
3 Data characteristics of an Extended ECM system ............... 19
4 Best practices for the network and communication layer ... 21

4.1 Business Content window without Smart UI integration ...................... 21
4.2 Business Content window with Smart UI integration .......................... 22
4.3 Deployment options ........................................................................ 23
4.3.1 Deployment option 1: One Content Server, one SAP system ............. 23
4.3.2 Deployment option 2: One Content Server, multiple SAP systems ...... 25
4.3.3 Deployment option 3: Multiple Content Server instances, multiple
SAP systems .................................................................................. 26
Part 2 Installing Extended ECM for SAP Solutions 27
5 Obtaining the installation software ........................................ 29

5.1 Installing with OpenText System Center Manager ............................. 29
5.1.1 Scenarios and their components ...................................................... 31
5.1.2 List of all components by scenario .................................................... 35
5.1.3 Prerequisites for running the execution plan for an all-in-one
scenario ......................................................................................... 46
5.1.4 Running installation with the execution plan for an all-in-one
scenario ......................................................................................... 48
5.2 Installing using the master setup ...................................................... 49
6 Prerequisites for Extended ECM ............................................ 51

6.1 Required knowledge ........................................................................ 51
6.2 SAP system requirements ............................................................... 51
6.3 Content Server system requirements ................................................ 54
6.4 SAP Add-On Installation Tool (SAINT) .............................................. 55
6.5 AppWorks Gateway system requirements ......................................... 56
6.6 Finding version information for relevant system components of
Extended ECM for SAP Solutions .................................................... 56
ERLK210400-IGD-EN-03 Installation and Upgrade Guide iii

Table of Contents
7 Installing Extended ECM for SAP Solutions ......................... 59
8 Installing the SAP package ..................................................... 61
9 Generating roles ...................................................................... 65
10 Installing language packages in the SAP system ................ 67
11 Installing the Content Server modules .................................. 69

11.1 Installation procedure on Content Server .......................................... 69
11.2 Installing Content Server and modules files ....................................... 69
11.3 Installing the Content Server modules .............................................. 72
11.4 Installing the Enterprise Asset Management Business Scenario on
Content Server ................................................................................ 72
11.4.1 Installing OpenText Business Scenario EAM Setup ........................... 74
11.4.2 Installing OpenText Business Scenario Enterprise Asset
Management – 01 ........................................................................... 75
Management – 02 ........................................................................... 76
Management – 03 ........................................................................... 78
11.4.5 Configuring settings for the OpenText Business Scenario
Enterprise Asset Management ......................................................... 79
12 Installing language packs on Content Server ....................... 81
13 Deploying Extended ECM Web Services ............................... 83

13.1 Deploying Extended ECM Web Services into the application server ... 83
13.2 Deploying Content Web Services ..................................................... 84
13.3 Configuring host and port for Content Server in Tomcat ..................... 84
14 Installing OpenText ArchiveLink Filter .................................. 87
15 Installing AppWorks Gateway (optional) ............................... 89
Part 3 Upgrading Extended ECM for SAP Solutions 91
16 Upgrade scenarios .................................................................. 93

16.1 Supported combinations .................................................................. 93
16.2 Phasing out Enterprise Library ......................................................... 94
16.2.1 Upgrading with Enterprise Library installed ....................................... 95
16.2.2 Migrating Enterprise Library records and other items ......................... 95
17 General recommendations for the upgrade .......................... 99
18 Upgrading to Extended ECM for SAP Solutions 21.4 ........ 101

18.1 Checklist for the upgrade ............................................................... 101
iv OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

Table of Contents
18.2 Upgrading the database schema .................................................... 104

18.3 Upgrading Extended ECM for SAP Solutions in the SAP system ...... 104
19 Upgrading from Extended ECM for SAP Solutions 20.2 to

21.4 .......................................................................................... 105
19.1 Checklist for the upgrade ............................................................... 105
19.2 Upgrading the database schema .................................................... 108
19.3 Upgrading to Extended ECM for SAP Solutions in the SAP system .. 109
20 Upgrading Business Scenarios on the SAP system .......... 111
Part 4 Configuring the system after the installation 113
21 Connecting the SAP system ................................................. 115

21.1 Connecting the SAP system with Content Server ............................ 115
21.2 Connecting the SAP system with OpenText Archive Center ............. 116
21.2.1 Creating an archive on the OpenText Archive Center ...................... 118
22 Performing general post-installation tasks in SAP ............ 119

22.1 Performing general post-installation tasks in SAP ............................ 119
22.1.1 Using the IMG function .................................................................. 119
22.1.2 Assigning SAP roles ...................................................................... 122
22.1.3 Adjusting authorization default values ............................................. 123
22.2 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0,
and SAP SRM 7.0 ......................................................................... 125
22.2.1 Exporting the SAP PSE certificate for the SAP authentication
handler ......................................................................................... 125
22.2.2 Activating the SSO HTTP service ................................................... 128
22.2.3 Creating logical ports in the SAP system ........................................ 130
22.2.3.1 Creating logical ports for SAP Basis 7.0 .......................................... 130
22.2.3.2 Creating logical ports for SAP Basis 7.01 ........................................ 136
22.2.3.5 Using the assertion based authentication mechanism ...................... 144
22.2.4 Configuring the Service Provider Interface service ........................... 149
22.2.5 Creating logical destinations .......................................................... 150
22.2.6 Maintaining Extended ECM connections ......................................... 152
22.2.7 Improving data security for impersonation connections .................... 155
22.2.8 Importing the Content Server SSL certificate ................................... 155
23 Performing system administration tasks in Content

Server ..................................................................................... 157
23.1 Enabling Business Workspaces ..................................................... 157
23.2 Importing root certificates for Secure Sockets Layer (SSL)
connections .................................................................................. 157
ERLK210400-IGD-EN-03 Installation and Upgrade Guide v

Table of Contents
23.3 Connecting SAP as the business application ................................... 159

23.4 Configuring the storage provider .................................................... 161
23.5 Creating an Enterprise Library application ....................................... 162
23.6 Setting permissions for root folders in Content Server ...................... 165
23.7 Managing users and permissions ................................................... 165
23.7.1 Setting up the authorization for records ........................................... 166
23.8 Granting object and usage privileges .............................................. 167
23.8.1 Granting permissions and privileges for business administrators ...... 167
23.8.2 Granting usage privileges for business workspaces ......................... 169
23.8.3 Granting object and usage privileges for business attachments ........ 170
23.9 Configuring how users can copy or move business workspaces ....... 170
23.10 Configuring multilingual metadata languages .................................. 171
23.11 Configuring document template settings ......................................... 172
23.12 Preparing the Content Server search for users ................................ 173
23.12.1 Creating a search slice for business workspaces ............................. 173
23.12.2 Indexing documents and other items with business workspace
attributes ...................................................................................... 174
23.13 Smart View: Creating a perspective with Perspective Manager ........ 176
23.13.1 Migrating perspectives ................................................................... 178
23.13.2 Header widget .............................................................................. 179
23.13.3 Related Workspaces widget ........................................................... 181
23.13.4 Team widget ................................................................................. 184
23.13.5 Metadata widget ........................................................................... 184
23.13.6 Workspaces widget ....................................................................... 185
23.13.7 Configuration Volume widget ......................................................... 186
23.13.8 Discussion widget ......................................................................... 187
23.13.9 Business Attachments widget ........................................................ 188
23.13.10 Dossier widget .............................................................................. 191
23.13.11 Header widget with business object information .............................. 191
23.13.12 Scan barcode widget ..................................................................... 194
23.14 Adding your own logo to Content Server Smart View ....................... 194
23.15 Configuring the display of documents in the side-panel .................... 195
23.16 Configure how document viewing behaves with Web Viewer ............ 196
23.17 Providing the online help ............................................................... 196
23.17.1 Providing the online help on a local help server (Private Help
Server) ......................................................................................... 197
23.18 Preparing document declaration ..................................................... 198
23.18.1 Creating a Records Management classification (optional) ................ 198
23.18.2 Importing SAP system categories ................................................... 198
23.19 Enabling OpenText Recycle Bin for business workspaces ............... 199
23.20 Checking the appearance of the SAP integration ............................. 199
23.21 Allowing users to save Outlook emails to business workspaces ....... 203
vi OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

Table of Contents
23.21.1 Installing and upgrading the Business Workspaces Outlook add-in ... 203
23.21.1.1 Preparing to install or upgrade the Business Workspaces Outlook
add-in ........................................................................................... 204
23.21.1.2 Downloading the latest Outlook add-in manifest file ......................... 204
23.21.1.3 Migrating custom settings to the new Outlook add-in manifest file ..... 205
23.21.1.4 Uploading the Outlook add-in manifest file ...................................... 205
23.21.2 Preparing your environment ........................................................... 206
23.21.2.1 Creating Content Server folders for the add-in ................................. 206
23.21.2.2 Creating search forms for the add-in ............................................... 207
23.21.3 Configuring add-in settings ............................................................ 209
23.21.3.1 Examples: Configuring email saving options ................................... 211
23.21.4 Configuring rules and email search settings to display suggested
workspaces .................................................................................. 214
23.21.4.1 Understanding how rules and email search settings are applied ....... 214
23.21.4.2 Understanding how rules are applied to emails sent from Extended
ECM mobile clients ....................................................................... 216
23.21.4.3 Testing your rules and email search settings ................................... 217
23.21.4.4 Configuring Rules and Email Search Settings ................................. 217
23.21.4.5 Testing Rules and Email Search Settings ....................................... 221
23.21.4.6 Examples: Workspace rules ........................................................... 221
23.21.4.7 Allowing email fields to be extracted for indexing ............................. 223
23.21.5 Configuring your environment for SSO authentication ...................... 223
23.21.5.1 Configuring security settings for SSO authentication ........................ 224
23.21.6 Adding URLs to the list of trusted sites in Internet Explorer .............. 224
23.22 For SAP CRM and SRM: Configuring security settings .................... 225
23.23 Repairing a group replacement migration ........................................ 225
23.24 Considering virus-scanning ............................................................ 225
24 Performing additional optional tasks in the SAP system .. 227

24.1 Customizing the integration into SAP GUI via Generic Object
Services ....................................................................................... 227
24.1.1 Customizing the Generic Object Services (SAP GUI) ....................... 227
24.1.2 Selecting items to be displayed in Business Content window ........... 230
24.1.3 Customizing the context menu of the Business Content window ....... 230
24.1.3.1 Customizing the Business Content window context menu with
Content Server menu entries ......................................................... 231
24.1.3.2 Adding custom functionality to the Business Content window
context menu ................................................................................ 232
24.1.3.3 Opening a document from the Business Content window context
menu ............................................................................................ 233
24.1.4 Providing Drag-and-drop functionality for the Business Content
window ......................................................................................... 233
24.1.5 Enabling the integration widget in the Business Content window ...... 233
ERLK210400-IGD-EN-03 Installation and Upgrade Guide vii

Table of Contents
24.1.5.1 Configuring Microsoft IIS to return meaningful REST API error

messages ..................................................................................... 234
24.1.6 Maintaining Content Server subtypes as copy/move target in the
Business Content window .............................................................. 235
24.1.7 Providing access to local folders for the Business Content window ... 236
24.1.8 Integrating Viewers in the Business Content window ....................... 237
24.1.9 Customizing MIME types for preview .............................................. 240
24.1.10 Customizing the GOS Attachment list for Records Management ...... 241
24.2 Viewing the old configuration in SAP .............................................. 242
24.3 Configuring Single Sign-on for Content Server ................................ 243
24.4 Configuring Imaging viewers .......................................................... 244
25 Verifying the installation ....................................................... 245

25.1 Analyzing the SAP system ............................................................. 245
25.1.1 Understanding the SAP Diagnostic Program ................................... 245
25.1.2 Understanding the details of the Diagnostic Program ....................... 246
25.1.3 Understanding the Configuration Report ......................................... 247
25.1.4 Using the Error Queues ................................................................. 247
25.1.5 Analyzing the application log .......................................................... 252
Part 5 Handing over and transporting the system 257
26 Preparing a checklist for business administrators ............ 259
27 Transporting Extended ECM for SAP Solutions Content

Server configuration and templates .................................... 261
27.1 Transporting the Business Workspaces configuration from versions
10.5.1 and later ............................................................................. 261
27.1.1 Importing the configuration from a Content Server version before
16.2.6 ........................................................................................... 263
Part 6 Removing Extended ECM for SAP Solutions 265
28 General process .................................................................... 267

28.1 Prerequisites for removal ............................................................... 268
29 Performing manual steps before removal ........................... 269

29.1 Extended ECM component OTEXRL .............................................. 269
29.1.1 Performing mandatory manual steps before uninstalling OTEXRL .... 269
29.1.2 Performing optional manual steps before uninstalling OTEXRL ........ 271
29.2 Extended ECM for SAP ERP, S/4HANA component OTEXRLE ....... 272
29.2.1 Performing mandatory manual steps before uninstalling OTEXRLE .. 272
29.2.2 Performing optional manual steps before uninstalling OTEXRLE ...... 273
29.3 Extended ECM CRM component OTEXRLC ................................... 273
29.3.1 Performing mandatory manual steps before uninstalling OTEXRLC .. 273
viii OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

Table of Contents
29.4 Extended ECM SRM component OTEXRLS ................................... 278

29.5 Extended ECM OData Services component OTEXRLO ................... 278
29.5.1 Performing mandatory manual steps before uninstalling OTEXRLO . 278
29.6 Extended ECM Fiori Apps component OTEXRLF ............................ 279
29.6.1 Performing mandatory manual steps before uninstalling OTEXRLF .. 279
29.7 Extended ECM Business Scenarios component OTEXRLSA ........... 280
29.7.1 Performing mandatory manual steps before uninstalling OTEXRLSA 280
29.8 Archiving and Document Access component OTEXBAS .................. 281
29.8.1 Performing mandatory manual steps before uninstalling OTEXBAS .. 281
29.8.2 Performing optional manual steps before uninstalling OTEXBAS ...... 282
29.9 Archiving and Document Access ERP package component
OTEXERP .................................................................................... 283
29.9.1 Performing mandatory manual steps before uninstalling OTEXERP . 283
29.10 Archiving and Document Access CRM package component
OTEXCRM ................................................................................... 283
29.10.1 Performing mandatory steps before uninstalling OTEXCRM ............ 283
29.11 Archiving and Document Access OData Services component
OTEXBASO .................................................................................. 284
29.11.1 Performing mandatory steps before uninstalling OTEXBASO ........... 284
29.12 Archiving and Document Access Fiori Apps component OTEXBASF 285
29.12.1 Performing mandatory steps before uninstalling OTEXBASF ........... 285
30 Removing with the SAINT transaction ................................ 287
Part 7 Appendix: Architecture and system recommendations 289
31 Components of Extended ECM for SAP Solutions ............ 291
32 Deployment scenarios .......................................................... 293
33 Communication protocols .................................................... 295
GLS Glossary 297
ERLK210400-IGD-EN-03 Installation and Upgrade Guide ix

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

modules, web services and an SAP package, with which you can integrate Content
Server functionality into SAP business processes. This includes functionality for
document and records management, archiving, workflow, and collaboration.
Business A business workspace in Content Server contains content that is relevant for a business
workspaces, object. From Content Server side, users can easily view the data of this business
cases and
binders
object. From the business application, users can access Content Server items in the
business workspace without leaving their system. To make full use of the Content
Server functionality, not only business workspaces but also cases and binders can be
configured for Extended ECM for SAP Solutions.
Business In addition to the content that is stored in a business workspace for a business object,
attachments users can connect additional documents as business attachments to a business object.
Business rela- Extended ECM for SAP Solutions provides tools to illustrate a relationship between
tionships business workspaces. For example, a hierarchical relationship between business
workspaces can be displayed in a sidebar widget of a business workspace.
1.1 Related documentation

The following documentation is available for Extended ECM for SAP Solutions on
OpenText My Support (https://knowledge.opentext.com/knowledge/llisapi.dll/
Open/10194282):
OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide (ERLK-IGD)
The Installation Guide describes the installation and upgrade of Extended ECM
for SAP Solutions up to the point where the connection between SAP and
Content Server is established.
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
The Customizing Guide describes how to customize SAP and configure Content
Server for Extended ECM for SAP Solutions functionality.
OpenText Extended ECM for SAP Solutions - User Management and Access Control
Scenarios (ERLK-CUM)(this guide)
This guide discusses user management and access control scenarios.
OpenText Directory Services - Installation and Administration Guide (OTDS-IWC)
This guide describes the configuration of OpenText Directory Services.
OpenText Extended ECM for SAP Solutions - User Guide (ERLK-UGD)
The User Guide describes how to use Extended ECM for SAP Solutions
functionality in both SAP and Content Server. This guide is also available as
online help.
ERLK210400-IGD-EN-03 Installation and Upgrade Guide 11

Chapter 1 What is OpenText Extended ECM for SAP Solutions
OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Microsoft SQL Server (ERLK-IWS)
This specific Installation Guide describes the setup of one architecture scenario
for Extended ECM for SAP Solutions with Microsoft SQL Server as database.
OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Oracle Database (ERLK-IWO)
for Extended ECM for SAP Solutions with Oracle as database.
OpenText Extended ECM for SAP Solutions - Installation Guide for SAP HANA (ERLK-
IWH)
for Extended ECM for SAP Solutions with SAP HANA as database.
OpenText System Center Manager - Installation and Configuration Guide (SYSCM-IGD)
OpenText™ System Center simplifies the installation, configuration, patching,
and updating of supported OpenText software applications.
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/
Open/18208703).
Content Server Champion Toolkit
A variety of documents deals with deployment scenarios of Content Server as
well as Best Practices examples.
The Content Server Champion Toolkit documents are available on OpenText My
Support (https://knowledge.opentext.com/knowledge/llisapi.dll/open/19905386).
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product

• Requirements
• Restrictions
• Important dependencies
• Last-minute changes regarding the documentation
• Manual IDs of the current documentation
The Release Notes are continually updated. The latest versions of the Extended ECM
for SAP Solutions Release Notes is available on OpenText My Support: Extended
ECM for SAP Solutions (https://knowledge.opentext.com/knowledge/llisapi.dll/
Open/67811874).
12 OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

Part 1
Planning the installation of Extended ECM
for SAP Solutions
Part 1 Planning the installation of Extended ECM for SAP Solutions
This part describes the overall architecture of Extended ECM for SAP Solutions and
provides best practices regarding deployment options.
• “Overall architecture“ on page 15

• “Data characteristics of an Extended ECM system“ on page 19
• “Best practices for the network and communication layer“ on page 21

Chapter 2
Overall architecture
The following sections of this chapter describe the architecture of an Extended ECM
system by breaking down the system into multiple layers:
• Persistence and storage layer

• Network and communication layer
• Business logic layer
• Presentation layer
For an overview, see Figure 2-1. For detailed information, see “Components of
Extended ECM for SAP Solutions“ on page 291.
Presentation
Smart UI
integration Search form Mobile app
widget
Business logic
SAP SAP
Content Suite Extended SAP ECMLink
Document Document
Platform ECM platform package
Access Archiving
Network / communication
Directory Web service AppWorks
Services components Gateway
Persistence / storage
Database Archive Center
Figure 2-1: Layered view of Extended ECM

Chapter 2 Overall architecture
2.1 Persistence layer

This layer takes care of persistent data storage. The content is stored in OpenText™
Archive Center.
Components in this layer
• Database stores metadata and application data

• Archive Center stores document content
Most database tuning tips are documented thoroughly in the database optimization
paper of Content Server, which is also valid for Extended ECM in general. For more
information, see Best Practices SQL Server for OpenText Content Server (https://
knowledge.opentext.com/knowledge/cs.dll/Overview/61019094) or Best Practices
Oracle for OpenText Content Server (http://knowledge.opentext.com/knowledge/
cs.dll/Overview/64127492).
2.2 Network and communication layer

This layer contains the components dealing with the communication between
different software systems in a customer’s software landscape.
• Extended ECM web service components

• SPI interface
• OpenText™ Directory Services
OpenText Directory Services (OTDS) is a communication layer component.
OTDS is responsible for authentication across the various components in an
Extended ECM system landscape. It enables user synchronization between
identity providers (like Microsoft Active Directory) and Content Server. OTDS
also provides Single Sign-On (SSO) capabilities with business applications, for
example using SAML, integrated Windows authentication, or the MYSAPSSO
cookie.
• OpenText™ AppWorks™ Gateway (optional)
AppWorks Gateway is an Enterprise Application Development and Management
platform. The AppWorks Gateway engine component is the single point of
contact between all mobile clients and your production Content Server. It
forwards all incoming operation requests, queues data requests to reduce server
load, and handles notifications to all registered client applications.
Questions to be addressed for this layer
• How do Extended ECM components communicate with each other?

• What are the deployment options?

2.3. Business logic layer
• How to configure OTDS authentication in Extended ECM for SAP Solutions?

• Do I have to support the mobile app?
See also “Best practices for the network and communication layer“ on page 21.
2.3 Business logic layer

This layer contains the most complex components in the Extended ECM Solution
package. For more information, see section 2 “Concepts, scenarios and best
practices” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-
CGD).
2.4 Presentation layer

This layer presents Extended ECM to the user. One major benefit of Extended ECM
is that it expands the ways of accessing unstructured content produced by the
business processes. Users are not only able to access content in a structured way in
the business application but are also able to access it without the context of the
business application, for example, from a web interface. You need to consider
carefully how to expose the content to different interfaces.
• Business application: integration widgets or perspectives for UI integration

• Web interface: perspective for business workspaces in Content Server Smart UI
• Client interface: Windows® Explorer/Microsoft® Outlook®, OpenText™
Enterprise Connect
• Content Server mobile app (optional)
Question to be addressed for this layer
• How can a user access the workspace most efficiently?

Chapter 3
Data characteristics of an Extended ECM system
An Extended ECM system differs from standard OpenText™ Content Suite Platform
in several characteristics. In general, during the initial phase of an Extended ECM
system, storing one document implies on average 1.7 times the amount of business
workspaces and 5.5 times the number of folders stored in the same system (see
Figure 3-1).
Figure 3-1: Number of business workspaces and folders compared to number

of documents
Noticing these differences can help you creating a sizing concept, index and search
configurations.
Metadata Further, business workspaces are linked with business objects from the business
application, which contributes metadata about the business object. The majority of
business properties are stored with the business workspace and not necessarily with
documents. Therefore, when calculating required search partitions, not only
consider the number of documents but also the amount of metadata. For more
information about search and index settings, see the Content Server Champion
Toolkit on My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/
19905386).

Chapter 4
Best practices for the network and communication
layer
From Extended ECM version 16 on, business administrators can enable the Smart UI
widgets in the SAP Business Content window. This changes the communication
flow between Extended ECM components to a certain extent.
4.1 Business Content window without Smart UI

integration
The Business Content window is an integration component from Extended ECM for
SAP Solutions in SAP ERP. It can be opened in a business object transaction from the
Generic Object Services (GOS) menu. The Business Content window displays the
business workspace and its content, business attachments, business documents
(ArchiveLink), notes and local files.
Figure 4-1: Business Content window classic view integration

Chapter 4 Best practices for the network and communication layer
Communication The communication channels can be grouped into two major categories: SOAP (web
channels service) communication or HTTP/HTTPS communication.
SOAP communication
• Workspace creation and update uses ECMLink web services.
HTTP/HTTPS communication
• Displaying the workspace folder structure in a tree view uses the Content Server
REST API.
• SAP Business Content window Drag & Drop operations use the Content Server
REST API.
• Search within the Business Content window through the Content Server Search
API.
• Document-related activities like editing, versioning, etc.
4.2 Business Content window with Smart UI

integration
Business administrator can enable the Smart UI integration widget in the Business
Content window. The underlying communication is then simplified as shown in
Figure 4-2.
Figure 4-2: Business Content window with Smart UI integration
The configuration for establishing the communication however stays unchanged

and can be configured using SAP Customizing (IMG): OpenText Extended ECM for
SAP Solutions > Maintain Extended ECM Connections.

4.3. Deployment options
4.3 Deployment options

If your company has multiple business application systems, for example, multiple
SAP systems, the following deployment options are possible:
1. One Content Server connected to one SAP system

2. One Content Server connected to several SAP systems
3. Several Content Servers connected to one SAP system (with limitations)
For more information, see also “Deployment scenarios“ on page 293.
4.3.1 Deployment option 1: One Content Server, one SAP

system
Option 1 is the most common deployment option and is strongly recommended for
an Extended ECM setup. A typical SAP system setup may use a three-tier system
landscape (DEV-QA-PROD). Correspondingly, you may want to consider a three-
tier Content Server landscape connect to each of the SAP tiers. The benefits are as
follows:
• With the three-tier system landscape, you make all changes to your system (to
include customizing) in a separate development system.
• Changes can then be imported into a quality assurance system where
stakeholders can thoroughly test them.
• Once you can confirm the changes are safe, they can be transported into the
production system.
• All Content Server installations in this three-tier system landscape are clearly
separated from each other, the communication flow between the leading
application system and the Content Server system is easy to understand and to
manage.
From the infrastructure perspective, Figure 4-3 shows an example of deployment

option 1. In a real-world scenario, the components can be scaled according to the
actual demand.
For considering a Content Server cluster deployment, see the “Content Server
Architecture Overview” on My Support (https://knowledge.opentext.com/
knowledge/cs.dll/Overview/RKA500025).
• Frontend servers are those instances accessed by end-users.

• The index server manages the full-text index process.
• When the Extended ECM system is heavily using agent processes, like the
notification agent, workflow agent, or automatic web reports, you may want to
configure a separate agent server to have most of the agents running on this
separate machine.

• The communication between the business application and Content Server relies
on web services. If you are planning bulk operation from the SAP system to
Content Server, you can setup a separate server, and use it only to interact with
web service requests. Alternatively, load balance the web service requests.
Consider using a non-sticky load balancer setup for consuming the requests from
SAP system.
Note: From version 20.2, Extended ECM for SAP Solutions fully supports
active-active clustering in a scenario without Enterprise Library Server.
SAP
ECMLink ArchiveLink
Load balancer
OTDS Content Server cluster Archive

Center
Content Server frontend
Frontend Frontend Frontend

server 1 + server 2 + server 3 +
Extended Extended Extended
ECM Web ECM Web ECM Web
Services Services Services
Content Server backend
Content Index server Agent server

Archive
Server (optional)
Center
database database
Figure 4-3: Deployment option 1 – infrastructure example

4.3. Deployment options
4.3.2 Deployment option 2: One Content Server, multiple SAP

systems
Deployment option 2 allows system administrator to configure one Content Server
instance and connect it to several SAP systems. These SAP systems can either be
connected to each other like in a three-tier system landscape, you can configure DEV
and QA system sharing one Content Server, or they can be separated from each
other (for example, two different SAP ERP systems).
If you decide for this deployment option, ensure that the configuration entities, like
workspace types, business object types, categories, templates, and root locations, are
well structured. Since they will be created in a single Content Server system, you can
best distinguish them by adding the external systems ID to the name. For example, if
you are using the same Content Server for your SAP DEV and QA systems, you can
consider using the following naming schema:
Property Naming schema

External System ID <System ID>_<Client>
Category <System ID>_<Client>_<Business Object Name>_Data
Classification <System ID>_<Client>_<Business Object
Name>_Classification
Storage Location <System ID>_<Client>_<Business Object Name>_Storage
Storage Location is the root folder where workspaces are created.
Workspace Type <System ID>_<Client>_<Business Object
Name>_Workspace_Type
Business Object Type <System ID>_<Client>_<Business Object Name>
Business Workspace <System ID>_<Client>_<Business Object
Template Name>_Template
The disadvantage of sharing Extended ECM is the blur edge of different SAP
systems. Also, in situations where SAP DEV and QA systems are sharing one
Extended ECM, you may lose the opportunity to test your customization transport
packages, which consequentially adds risk of transporting customizations into the
production system.
Also keep in mind that sharing a Content Server system with different SAP systems
may change the hardware demand of the underlying Content Server.

4.3.3 Deployment option 3: Multiple Content Server

instances, multiple SAP systems
This option has its constraints as follows:
• By default, you cannot create business workspaces for the same business objects
in different Content Server installations. For example, with standard
configuration, you cannot create equipment workspaces from the SAP system
into different Content Server systems.
• Business relationships between business objects need to be carefully considered.
When the multiple SAP systems are not connected to each other, workspace
relationships might not be updated automatically by the SAP property provider.
A business user must maintain the business relationships manually in Content
Server.

Part 2
Installing Extended ECM for SAP Solutions
Part 2 Installing Extended ECM for SAP Solutions
This part covers the details of the Extended ECM for SAP Solutions installation and
the SAP Add-on.
For information about installing the other products or components of OpenText

Extended ECM for SAP Solutions, see the individual installation guides. For
information about supported hardware and software platforms, check the OpenText
Extended ECM for SAP Solutions Release Notes.
OpenText also recommends that you read one of the following comprehensive
installation instructions for certain scenarios, which are available on OpenText My
Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/10194282):
• OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Microsoft SQL Server (ERLK-IWS)
• OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows
with Oracle Database (ERLK-IWO)
• OpenText Extended ECM for SAP Solutions - Installation Guide for SAP HANA
(ERLK-IWH)
• “Obtaining the installation software“ on page 29

• “Prerequisites for Extended ECM“ on page 51
• “Installing Extended ECM for SAP Solutions“ on page 59
• “Installing the SAP package“ on page 61
• “Generating roles“ on page 65
• “Installing language packages in the SAP system“ on page 67
• “Installing the Content Server modules“ on page 69
• “Installing language packs on Content Server“ on page 81
• “Deploying Extended ECM Web Services“ on page 83
• “Installing OpenText ArchiveLink Filter“ on page 87
• “Installing AppWorks Gateway (optional)“ on page 89

Chapter 5
Obtaining the installation software
Deployment Extended ECM for SAP Solution is available for different deployment methods.
method Depending on your requirements you may chose one of the following:
• On premises and purchased from OpenText: Use the OpenText System Center
Manager. For more information, see “Installing with OpenText System Center
Manager” on page 29.
• On premises and purchased from SAP SE: Download an ISO image from the SAP
Store
• In a Kubernetes cluster on a cloud platform, such as Microsoft Azure, Amazon
Web Services, and Google Cloud Platform: Download Docker images. For more
information, see OpenText Content Suite Platform and Extended ECM - Cloud
Deployment Guide (SULCCD-IGD).
Extended ECM for SAP Solutions consists of a number of components and parts, all
of which are available for download from OpenText System Center. Depending on
your scenario, you may need not all of them. This chapter gives an overview, which
installable parts you may need for the most common scenarios. You will also find a
comprehensive list of all components with description.
Important
If you purchased your license from SAP SE directly, you may download the
ISO images from SAP Store.
5.1 Installing with OpenText System Center Manager

New: In OpenText System Center Manager you can now use a predefined
execution plan for the all-in-one installation of OpenText Directory Services,
OpenText Content Server, OpenText Extended ECM modules, and OpenText
Archive Center and related modules.
OpenText System Center Manager helps you download the respective software. As a
direct customer of OpenText, you find OpenText System Center Manager on
OpenText My Support. Customers of SAP find it in SAP Store.
Prerequisites You need a user login to OpenText My Support.
To download installation software with OpenText System Center:
1. Login in to OpenText My Support and download the OpenText System Center

Manager for SAP installable OpenText_SystemCenter_Manager_S.msi. As an
SAP customer, download the file from SAP Software Download Center.

Chapter 5 Obtaining the installation software
2. Install the OpenText System Center Manager for SAP on your computer or
server. Follow the install instructions.
You can install certain scenarios. For more information, see “Scenarios and their
components” on page 31 and “List of all components by scenario” on page 35.
After you installed OpenText System Center Manager for SAP, you can use the
predefined execution plan (extended_ecm_plan.pln) to install an all-in-one
scenario for OpenText Extended ECM for SAP Solutions including all basic software
and modules. The execution plan conducts the following installations in 19 steps:
• Installing and setting up OpenText Directory Services:
– Installing OpenText Directory Services

– Setting up OpenText Directory Services
• Installing and configuring OpenText Content Server
– Installing OpenText Content Server

– Configuring OpenText Content Server
• Installing and setting up OpenText Extended ECM modules
– Installing OpenText Extended ECM Platform

– Installing OpenText Extended ECM for SAP Solutions
– Installing OpenText Activator for SAP Solutions
• Installing OpenText Archive Center and related modules
– Installing Monitoring Agent

– Installing OpenText Archive Center
– Installing OpenText Administration Client
– Installing Archive Monitoring Server
– Installing OpenText Document Pipelines Base
– Installing OpenText Document Pipelines CMIS
– Installing OpenText Document Pipeline DocuLink
– Installing OpenText Document Pipelines File Archiving
– Installing OpenText Document Pipelines Info
– Installing OpenText Document Pipeline Perl
– Installing OpenText Document Pipeline Remote Interface
– Installing Document Pipeline for SAP products
The installations require certain prerequisites. For more information, see

“Prerequisites for running the execution plan for an all-in-one scenario” on page 46.

5.1. Installing with OpenText System Center Manager
Note: You can also create an execution plan on your own. If you do, take care
that the execution plan still has to follow the above mentioned order.
5.1.1 Scenarios and their components
OpenText Directory Services (OTDS) deployment

Installation information – OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC)
Component Order Windows Linux

Directory Services 1 OTDS-<version>-
WIN.msi
Archive Center deployment

Installation information
• OpenText Archive Center - Amazon S3 Installation and Configuration Guide (AR-

IAM)
• OpenText Archive Center - Installation Guide for Windows (Extended Component

Installer) (AR-IASW)
• OpenText Archive Center - Microsoft Azure Installation and Configuration Guide

(AR-IAZ)
• OpenText Archive Center - EMC Centera Installation and Configuration Guide

(AR-ICE)
• OpenText Archive Center - Compliant File System Installation and Configuration

Guide (AR-ICF)
• OpenText Archive Center - Cluster Installation Guide (AR-ICLU)
• OpenText Archive Center - IBM TSM SSAM Installation and Configuration Guide
(AR-IDR)
• OpenText Archive Center - Dell EMC Elastic Cloud Storage Installation and
Configuration Guide (AR-IECS)
• OpenText Archive Center - Google Cloud Storage Installation and Configuration

Guide (AR-IGCS)
• OpenText Archive Center - Installation Guide for UNIX/Linux (AR-IGU)
• OpenText Archive Center - Installation Guide for Windows (Integrated Archive

Installer) (AR-IGW)
• OpenText Archive Center - HDS HCP Installation and Configuration Guide (AR-
IHC)


Archive Center 1 archive_server- archive_server_<vers
<version>.msi ion>.tar.gz
Archive Monitoring 2 archive_monitoring archive_monitoring
Server _server- _server_<version>.tar
<version>.msi .gz
Solution Registry 3 solution_registry_ag solution_registry_ag
Agent ent-<version>.msi ent_<version>.tar.gz
Archive Cache optional archive_cache_serve archive_cache_serve
Server r-<version>.msi r_<version>.tar.gz
Archive Cache Server deployment

• Section 5.2 “Installing Archive Cache Server” in OpenText Archive Center -

Installation Guide for Windows (Extended Component Installer) (AR-IASW)
• Section 5.2 “Running the setup” in OpenText Archive Center - Installation Guide
for UNIX/Linux (AR-IGU)

Archive Cache 1 archive_cache_serve archive_cache_serve
Server r-<version>.msi r_<version>.tar.gz
Solution Registry 2 solution_registry_ag solution_registry_ag
Archive Center optional archive_server- archive_server_<vers
<version>.msi ion>.tar.gz
Archive Monitoring optional archive_monitoring archive_monitoring
Server _server- _server_<version>.tar
<version>.msi .gz
Content Server deployment

• OpenText Content Server - Installation Guide (LLESCOR-IGD)

• OpenText Content Server - Module Installation and Upgrade Guide (LLESCOR-
IMO)

Content Server 1 <version>_CS64_WI <version>_CS64_LN
N.exe X6.tar.gz
Extended ECM 2 <version>_XECMPF6 <version>_XECMPF6
Platform 4_WIN.exe 4_LNX.tar


Extended ECM for 3 <version>_XECMSA <version>_XECMSA
SAP Solutions P64_WIN.exe P64_LNX.tar
ArchiveLink Filter 4 OpenText
ArchiveLink Filter
<version>.msi
Extended ECM Web 5 Extended ECM Web
Services Services-20.4.0.msi
Extended ECM 6 xecm_cmis-20.4.0.m xecm-cmis.war
CMIS Service si
Activator for SAP optional <version>_OTSAPA <version>_OTSAPA
Solutions CT64_WIN.exe CT64_LNX.tar
Imaging Enterprise optional SCAN_MODULE_< SCAN_MODULE_<
Scan – Web version>.iso version>.iso
Interface (<version>_escanweb (<version>_escanweb
interface64_WIN.ex interface64_LNX.tar
e) )
Imaging Reviews optional <version>_llimaging6 <version>_llimaging6
and Notes 4_WIN.exe 4_LNX.tar
Monitoring Agent optional monitoring_agent_< monitoring_agent_<
version>_win.msi version>_LNX.tar.gz
Content Server optional
Mobile
Imaging Web optional OT_DOCVW_20.3.is OT_DOCVW_20.3.is
Viewer Service o (WebViewer-20.3- o (WebViewer-20.3-
Win64.msi) Linux64.sh)
SAP packages deployment

• “SAP Add-On Installation Tool (SAINT)” on page 55

• “Installing the SAP package“ on page 61
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRL <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLC <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLE <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLF <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLO <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLS <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLSA <version>
Vendor Invoice Management Foundation - SAP Add-on Packages - OTBCBAS <version>

Vendor Invoice Management Foundation - SAP Add-on Packages - OTBCWUI <version>
Document Pipelines deployment

Installation information – OpenText Document Pipelines - Installation and Upgrade
Guide (AR-IDPDP)

Document Pipeline 1 dp_base-
Base <version>.msi
Document Pipeline 2 DPCS_<version>_PL
for Content Server AIN.iso
(dp_content_server-
<version>.msi)
Document Pipeline 3 dp_doculink-
for DocuLink <version>.msi
Document Pipeline 4 dp_sap-
for SAP Solutions <version>.msi
Document Pipeline 5 dp_info-
Info <version>.msi
Document Pipeline 6 dp_perl-
Perl <version>.msi
Document Pipeline 7 dp_remote_interface
Remote Interface -<version>.msi
Solution Registry optional solution_registry_ag solution_registry_ag
Remote Cache Module with Smart Cache Services deployment

Installation information – OpenText Remote Cache - Installation, Configuration, and
Administration Guide (LLESRCA-IGD)

Remote Cache <version>_RCACHE
Module MODULE64_WIN.e
xe
Remote Cache <version>_RCACHE
Server SERVER64_WIN.exe
Smart Cache <version>_SMARTC
Services for Primary ACHESERVICES_P
Server RIMARY_WIN64.ex
e
Smart Cache <version>_SMARTC
Services for Remote ACHESERVICES_R
Server EMOTE_WIN64.exe

5.1.2 List of all components by scenario

Installation Name Description Windows Linux Binaries
Scenario Binaries
Archiving Archive Cache Provide the archive_cache_se archive_cache_se
Server ability to rver-20.2.msi rver_20_2.tar.gz
support remote
Archive Center
(not installable
for local Archive
Center).
Archiving Archive Center Provide archive_server-2 archive_server_2
compliant long- 0.2.msi 0_2.tar.gz
term archiving
for documents
incorporating:
the ability to
store and
retrieve content,
storage
virtualization,
caching and
cache servers,
long-term
preservation and
more.
Archiving Archive Provide the archive_monitori archive_monitori
Monitoring ability to ng_server-20.2.m ng_server_20_2.t
Server monitor Archive si ar.gz
Center locally or
remotely.
Archiving Core Archive Provide access to CoreArchiveCon
Connector the archiving nector-20.3.2.msi
services of
Archive Center
in the OpenText
Cloud.
Archiving Solution Deliver solution_registry solution_registry
Registry Agent information to _agent-20.2.msi _agent_20_2.tar.
Solution gz
Registry Server
regarding
installed
OpenText
software.


Scenario Binaries
Clients Administration Allow administration_c
Client configuration lient-20.2.msi
and
administration
of OpenText
Services
installed on
different
operating
systems. It is
based on
Microsoft
Management
Console (MMC)
and can be
installed only on
Windows
systems. Include
patch
ADC-1050-011.
Clients AppWorks Provide a opentextappwor
Desktop Client seamless, ksdesktop-16.7.0.
interactive view 11-x64.msi
of content and
functionality
from the
AppWorks
server.
Clients Content Server Provide back-
Mobile end AppWorks
application that
brings Content
Server
functionality to
mobile clients.
Clients Enterprise Provide a EnterpriseConne
Connect seamless, ct_Framework_2
Framework (32- interactive view 0.4.msi
bit version) of content and
functionality
from many
Enterprise
systems.


Scenario Binaries
Clients Enterprise Provide a EnterpriseConne
Connect seamless, ct_Framework_2
Framework (64- interactive view 0.4_x64.msi
bit version) of content and
functionality
from many
Enterprise
systems.
Clients Imaging Quickly and OT_IMG_WIV_2
Desktop Link easily archive 0.3.iso (Desktop
and retrieve files Link 20.3 - 64
from your bit.msi)
workstation.
Clients Imaging Bring scanning OT_SCAN_1640.
Enterprise Scan capacity to the iso (Enterprise
Content Server Scan 16.4.0.msi)
user interface.
The indexing
feature is also
available. Users
can scan an
image and run
an indexing
session in the
same user
interface.
Clients Imaging Quickly and ExchangeLink
ExchangeLink easily archive 20.3.msi
(32-bit version) and retrieve files
from your
workstation.
Clients Imaging Enable linking ExchangeLink
ExchangeLink and archiving 20.3 - 64 bit.msi
(64-bit version) Exchange
documents into
other
applications by
selecting them
and using the
respective menu
option.
Clients Imaging Archive Lotus NotesLink -
NotesLink 16 Notes mails and 16.0.0.msi
link them to SAP
R/3 objects.


Scenario Binaries
Clients Imaging Archive OutlookLink
OutlookLink Microsoft 20.3.msi
20.3 Outlook objects,
such as emails,
attachments, and
calendar events
and link them to
other
applications by
selecting them
and using the
task pane
against each
email to archive
email and
attachments.
Clients Imaging PDF OpenText OpenText
Extensions 20.3 Imaging PDF Imaging PDF
Extensions Extensions
brings in 20.3.msi
support for
viewing and
annotating PDF
documents.
Clients Imaging OpenText OT_IMG_WIV_2
Windows Imaging 0.3.iso
Viewer Windows (Windows
Viewer is the Viewer 20.3.msi)
basic package
for Viewer.
Clients Mobile Scan Scan documents Scan_Mobile_16
Client using mobile 40.iso
devices, like
iPads or
iPhones, and
upload the
outcome to
Content Server.
Clients Office Editor Offer users a OFFICEEDITOR
Client (32-bit seamless instant _CLIENT_20.4.m
version) editing si
experience,
providing the
performance of
editing files on a
local hard drive
without
installing any


Scenario Binaries
Clients Office Editor special add-ons OFFICEEDITOR
Client (64-bit to applications. _CLIENT_20.4_x
version) 64.msi
Clients Searchable PDF Allow rendering DPOCR_1620.iso
DocTool of scanned (dt_ocr_16.2.0.m
documents to si)
searchable PDF
documents.
Content Server Activator for Allow Content 16.2.8_OTSAPA 16.2.8_OTSAPA
SAP Solutions Server to CT64_WIN.exe CT64_LNX.tar
16.2.8 communicate
with the SAP
Server via RFC
requests.
Content Server Archive Link Dispatch OpenText
Filter Archive Link ArchiveLink
requests, Filter 20.4.1.msi
ensuring records
management
rules are
enforced.
Content Server Content Server Forms the 20.4.0_CS64_WI 20.4.0_CS64_LN
document N.exe X6.tar.gz
management
cornerstone of
the OpenText
Content Suite
and provide
secure,
enterprise-wide
control over any
type of content -
from contracts to
engineering
drawings,
system reports,
email messages,
images rich
media and much
more.
Content Server Extended ECM Provide a CMIS xecm_cmis-20.4. xecm-cmis.war
CMIS API for external 0.msi
enterprise
systems.


Scenario Binaries
Content Server Extended ECM Extend the 20.4.0_XECMSA 20.4.0_XECMSA
for SAP transactional P64_WIN.exe P64_LNX.tar
Solutions 20.4 process
management
capabilities of
SAP Business
Suite with
comprehensive
Enterprise
Content
Management
(ECM)
capabilities,
including
document
management,
records
management,
and
collaboration.
Content Server Extended ECM Extend the 20.4.0_XECMPF6 20.4.0_XECMPF6
Platform transactional 4_WIN.exe 4_LNX.tar
process
management
capabilities of
leading business
applications
with
comprehensive
Enterprise
Content
Management
(ECM)
capabilities,
including
document
management,
records
management,
and
collaboration.
Content Server Extended ECM Provide a Web Extended ECM otsapxecm.war
Web Services Services API for Web
integrating Services-20.4.0.m
external si
applications to
Extended ECM.


Scenario Binaries
Content Server Imaging Bring scanning SCAN_MODUL SCAN_MODUL
Enterprise Scan - capacity to the E_1640.iso E_1640.iso
Web Interface Content Server (16.4.0_escanwe (16.4.0_escanwe
16.4 user interface. binterface64_WI binterface64_LN
The indexing N.exe) X.tar)
feature is also
available. Users
can scan an
image and run
an indexing
session in the
same user
interface
Content Server Imaging Enable markup 16.2.0_llimaging 16.2.0_llimaging
Reviews and and notes 64_WIN.exe 64_LNX.tar
Notes functionality for
supported
document types.
Necessary for
integration with
Imaging
Windows
Viewer and
Imaging
WebViewer.
Content Server Monitoring Provide real- monitoring_agen monitoring_agen
Agent time information t_20.2.0_win.msi t_20.2.0_LNX.tar
about multiple .gz
Content Servers.
Content Server SAP System Provide
Categories mandatory
Content Server
categories for
declaring SAP
documents in
Content Server.
Document Document Provide the basic dp_base-20.2.msi
Pipelines Pipeline Base package for
Document
Pipelines.
Document Document Provide the DPCS_1621_PLA
Pipelines Pipeline for Document IN.iso
Content Server Pipeline for (dp_content_ser
16.2.1 archiving ver-16.2.1.msi)
documents to
Content Server.


Scenario Binaries
Document Document Provide the dp_doculink-20.
Pipelines Pipeline for Document 2.msi
DocuLink Pipeline for
DocuLink.
Document Document Provide the dp_sap-20.2.msi
Pipelines Pipeline for SAP Document
Solutions Pipeline for SAP
document
archiving. May
require
additional
licenses.
Document Document Provide a tool dp_info-20.2.msi
Pipelines Pipeline Info for monitoring
Document
Pipelines.
Document Document Provide a Perl dp_perl-20.2.msi
Pipelines Pipeline Perl package for
Document
Pipelines.
Document Document Document dp_remote_inter
Pipelines Pipeline Remote Pipeline Remote face-20.2.msi
Interface Interface 20.2
Remote Cache Remote Cache Remote Cache 16.2.10_RCACH
Module Module EMODULE64_W
IN.exe
Remote Cache Remote Cache Remote Cache 16.2.10_RCACH
Server Server 16.2.10 ESERVER64_WI
N.exe
Remote Cache Smart Cache Smart Cache 16.2.10_SMART
Services for Services for CACHESERVIC
Primary Server Primary Server ES_PRIMARY_
16.2.10 - WIN64.exe
Requires JCE!
Remote Cache Smart Cache Smart Cache 16.2.10_SMART
Services for Services for CACHESERVIC
Remote Server Remote Server ES_REMOTE_W
16.2.10 - IN64.exe
Requires JCE!
SAP Add-on OTEXBAS Archiving and
Packages Document
Access for SAP
Solutions base
package


Scenario Binaries
SAP Add-on OTEXBASB Archiving and
Packages Document
Access for SAP
Solutions base
package
SAP Add-on OTEXBASF Archiving and
Packages Document
Access for SAP
Solutions
package for SAP
Fiori
SAP Add-on OTEXBASO Archiving and
Packages Document
Access for SAP
Solutions
package for
OData Services
SAP Add-on OTEXCRM Archiving and
Packages Document
Access for SAP
Solutions
package for SAP
CRM
SAP Add-on OTEXERP Archiving and
Packages Document
Access for SAP
Solutions
package for SAP
ERP
SAP Add-on OTEXRL Extended ECM
Packages for SAP
Solutions base
package
SAP Add-on OTEXRLC Extended ECM
Packages for SAP
Solutions
package for SAP
CRM
SAP Add-on OTEXRLE Extended ECM
Packages for SAP
Solutions
package for SAP
ERP, S/4HANA


Scenario Binaries
SAP Add-on OTEXRLF Extended ECM
Packages for SAP
Solutions
package for SAP
Fiori
SAP Add-on OTEXRLO Extended ECM
Packages for SAP
Solutions
package for
OData Services
SAP Add-on OTEXRLS Extended ECM
Packages for SAP
Solutions
package for SAP
SRM
SAP Add-on OTEXRLSA Extended ECM
Packages for SAP
Solutions
Business
Scenarios
SAP Add-on OTBCBAS Vendor Invoice
Packages Management
Foundation base
package
SAP Add-on OTBCWUI Vendor Invoice
Packages Management
Foundation User
Interface
package
Server AppWorks Allows quickly otag-
Gateway 16.7.0 and easily gateway-16.7.0.z
building ip
purpose-specific
apps for the
Enterprise using
well-established
Web
technologies like
HTML5, CSS,
and JavaScript.


Scenario Binaries
Server Directory Integrate OTDS-2023- OTDS-2031-
Services 20.3.1 OpenText WIN.msi LNX.tar
products with an
enterprise
directory
infrastructure
(based on
Microsoft AD
and/or LDAPv3)
to enable Single
Sign On (SSO)
across all
components.
Viewing Services Brava! Server Offers a BravaEnterprise BravaEnterprise
Components 16 customized _ServerCompon _ServerCompon
EP7 Update 1 component ents_16.6.1.38.ex ents_16.6.1.38.tg
delivery system e z
intended for
select
integrators.
Administrators
of Content
Server
(deploying
Content Suite
Viewer) and
Brava! for
Content Suite
are primary
consumers of
this product.
Viewing Services Imaging Web Provides a web OT_DOCVW_20 OT_DOCVW_20
Viewer 20.3 application for .3.iso .3.iso
displaying and (WebViewer-20. (WebViewer-20.
printing 3-Win64.msi) 3-Linux64.sh)
documents in
web-based
scenarios and for
appending
comments to
these
documents.
Viewing Services Intelligent Provide a cloud intelligent-
Viewing 20.4 first product viewing-
built for file packaging-
viewing and windows-20.4.0.
transformation 64.zip
at scale.

Note: When you install Extended ECM Platform or Extended ECM for SAP
Solutions, OpenText System Center offers Extended ECM Web Services and
Extended ECM CMIS for download. Still, you have to deploy these
components manually.
For more information, see “Deploying Extended ECM Web

Services“ on page 83.
5.1.3 Prerequisites for running the execution plan for an all-

in-one scenario
Before you can start running the extended_ecm_plan.pln execution plan for the all-
in-one scenario to completely install OpenText Extended ECM for SAP Solutions
including all basic software and modules, all of the following prerequisites have to
be fulfilled.
General prerequisites
• System Center Manager for SAP needs to be configured with System Center
Agent.
• Java has to exist on the system or needs to be installed. To be able to install it
with the execution plan, upload the Java installer to System Center Manager for
SAP under Settings > External Vendor Files. It is then available for the execution
plan.
• Apache Tomcat has to exist on the system or needs to be installed. To be able to
install it with the execution plan, upload the Tomcat installer to System Center
Manager under Settings > External Vendor Files. It is then available for the
execution plan. For more information, see Section 1.3 “Setting up Tomcat” in
OpenText Archive Center - Installation Guide for Windows (Integrated Archive
Installer) (AR-IGW).
Prerequisites for installing and setting up OpenText Directory Services
The extended_ecm_plan.pln execution plan will install OpenText Directory

Services (OTDS) on a specific agent first. For installing and setting up OTDS the
following prerequisites apply:
• OTDS product has to be downloaded from the Catalog tab in System Center
Manager.
• Since System Center Manager does not install OTDS on Windows, the agent
should have Windows Server OS as a base.
• Details on OTDS have to be defined. For example, it has to be defined whether to
use an internal or an external OTDS.
Note: An external OTDS can be configured in the following ways:
– Using ResourceId by selecting the External option

– Using Resource name by selecting External Lookup option
For configuring an OTDS migration, keep all values as 0. Otherwise the

plan might fail with errors. For more information, see Section 1.2
“Importing data from previous versions of Directory Services” in OpenText
Directory Services - Installation and Administration Guide (OTDS-IWC).
Prerequisites for installing and configuring OpenText Content Server
The extended_ecm_plan.pln execution plan will continue with installing and

configuring Content Server on a specific agent. The following prerequisites apply:
• Content Server product has to be downloaded from the Catalog tab in System
Center Manager.
• Details on the database on which Content Server will be deployed must be
defined.
Note: You can optionally add a Content Server license by uploading it

to System Center Manager under Settings > External Vendor Files. The license
is needed in order to allow users to sign-in to Content Server.
Prerequisites for installing and setting up OpenText Extended ECM modules
In this part, the extended_ecm_plan.pln execution plan will install the relevant
OpenText Extended ECM modules on the specific agent. The following prerequisites
apply:
• OpenText Extended ECM Platform, OpenText Extended ECM for SAP Solutions,
and OpenText Activator for SAP Solutions products have to be downloaded
from the Catalog tab in System Center Manager.
• OpenText Content Server has to be installed and configured on the agent.
Prerequisites for installing OpenText Archive Center and related modules
In the last step, the extended_ecm_plan.pln execution plan will install OpenText
Archive Center and related modules on the specific agent. The following
prerequisites apply:
• OpenText Archive Center, OpenText Administration Client, and Archive

Monitoring Server have to be downloaded from the Catalog tab in System Center
Manager.
• OpenText Document Pipelines Base, OpenText Document Pipelines CMIS,
OpenText Document Pipeline DocuLink, OpenText Document Pipelines File
Archiving, OpenText Document Pipelines File Archiving, OpenText Document
Pipelines Info, OpenText Document Pipeline Perl, OpenText Document Pipeline
Remote Interface, and Document Pipeline for SAP products have to be
downloaded from the Catalog tab in System Center Manager.
• A database for Archive Center is already installed and configured. For more
information about the necessary steps, see Section 2 “Setting up the database” in

OpenText Archive Center - Installation Guide for Windows (Integrated Archive

Installer) (AR-IGW).
5.1.4 Running installation with the execution plan for an all-

in-one scenario
To run the installation for an all-in-one Scenario of OpenText Extended ECM for
SAP Solutions including all basic software and modules with the extended_ecm_
plan.pln execution plan, certain prerequisites apply. For more information, see
“Prerequisites for running the execution plan for an all-in-one scenario” on page 46.
As soon as these prerequisites are fulfilled, you can start the execution plan.
Note: Running the installation with the extended_ecm_plan.pln System

Center execution plan takes about half an hour time. It cannot be rolled back.
To run the installation with the predefined execution plan
1. In OpenText My Support navigate to DOWNLOADS > Ecosystems > SAP >

Extended ECM for SAP Solutions > Extended ECM for SAP Solutions 21.4 >
System Center Installation Plan. Download the extended_ecm_plan.pln
execution plan.
2. Import the downloaded plan into System Center. To do so, in System Center
navigate to the Plans tab, In Plans Overview page, click on the Import plan.
Then select the downloaded plan.
3. To open the plan, in the Plan Overview select extended_ecm_plan, and click
Edit. You can see the details of the execution plan with the separate steps of the
complete installation.
4. Optional: If Java and Apache Tomcat do not yet exist on the system yet, you can
define to install them in the first step Install Directory Services for Windows of
the plan. For this, open the Step. In the Apache Tomcat tab rsp. the Java tab in
Installation Type, select New Install.
5. Click Execute to start installing.
6. If passwords are required, a dialog opens. Enter the necessary passwords and
click Yes.
7. After you started the execution plan, the Execution Plans view in the Activities
tab opens. Here, you can monitor the progress of the execution plan.

5.2. Installing using the master setup
5.2 Installing using the master setup

To install Extended ECM with the master setup:
1. Download the ISO file from the SAP Store.
2. Mount the ISO image.
3. Run the Mastersetup.exe file located on the installation medium and accept
the license agreement.
4. Select a scenario and click Next.
5. Click Install and follow the instructions.

Chapter 6
Prerequisites for Extended ECM
Extended ECM for SAP Solutions 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
– OTDS requirement: 10.5 or later

• SAP SRM 7.0
6.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.
6.2 SAP system requirements

Check the following prerequisites for SAP prior to installation:
Basis package
The SAP Add-On OTEXBAS of Archiving and Document Access for SAP
Solutions must be installed on your SAP system. Check the Release Notes for
required versions and dependencies. This component is provided on the
Extended ECM for SAP Solutions installation medium. For more information
about the installation of Archiving and Document Access for SAP Solutions, see
OpenText Archiving and Document Access for SAP Solutions - Installation and
Upgrade Guide (ER-IGD).
SAP support packages

Check the latest version of the Release Notes on OpenText My Support for
required support packages for the SAP system.

Chapter 6 Prerequisites for Extended ECM
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.
SAP notes
The following SAP notes must be applied:
SAP Note Required for

110910 Some language-dependent texts may not
be displayed correctly in the GUI.
884077 Log-on error from external systems to
WAS 7.00 systems:
The external candidate's password
contains at least one lower-case letter. In
accordance with the rules, which were
valid up to and including WAS 6.40, the
registration application changes the
passwords to capital letters. However, as
of WAS 7.00 (see SAP Note 862989), the
system can be set in a way that it
distinguishes between upper-case and
lower-case letters in a password. In this
case, the log-on fails if the original
password contains at least one lower-case
letter.
1128338 CALL_BROWSER does not launch a new
window to open the URL, even when the
NEW_WINDOW parameter is passed to
the function module. Instead, an existing
window is used to open the URL.
However, as of SAP Note 1177636, the
behavior of CALL_BROWSER is changed
to allow also opening URLs on other
platforms than Microsoft Windows. In this
case, the settings of the MS Internet
Explorer govern the URL handling, i.e.
whether a new window is opened.
1255948 Required for the declare functionality of
the print lists.
1227752 Required to avoid known problems with
1122938 the web services.
(SAP ERP 6.0 and SAP_BASIS 14 or later)
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.

6.2. SAP system requirements
SAP Note Required for

1424747 Enables the transmission of SOAP error
codes to identify problems.
1267258 Unexpected error message No vendor
specified when log-on language is English.
822380 Required to avoid known problems with
(SAP 7.00) the SAP Add-On Installation Tool
Installation information - OSS note (SAINT).
212876
(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.
2293517 Required for update in document
declarations.
Patch levels
• Patch level for SAP ERP 6.0 – The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 700, patch level 16. This
patch level is required for enhanced functionality, for example, additional
icons in the GOS attachment list, based on the SAP enhancement technology.
• Patch level for SAP CRM 7.0 – The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 701, patch level 03
BBPCRM release 700, patch level 02
WEBCUIF release 700, patch level 02.
Content Server integration widget is only supported for CRM 7.0 Ehp 1.
• Patch level for SAP SRM 7.0 – The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 701, patch level 07; for
component SRM_SERVER, the minimum requirement is release 700, patch
level 08.
• Patch level for optional Fiori UI package – At runtime, the Fiori apps
require SAPUI5 1.52, which is based on User Interface Technology SAP_UI
release 750. At installation time, this package can be installed on SAP
frontend systems with User Interface Technology (SAP_UI release 740, patch
level 13 or later). The Fiori Add-On package of OpenText Archiving and
Document Access for SAP Solutions, OTEXBASF 2040_740 is required.

Though not required for installation, the Fiori app calls the OData services of
Extended ECM for SAP Solutions at runtime. For optimal accessibility, use
the highest SAPUI5 version with long-term maintenance. For more
information, see SAP Note 2564165.
For more information, 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). On systems with SAP_GWFND release 750, like
SAP S/4HANA, use SPAM/ level 0059 or later for installation. 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.
Note: The documentation and the Release Notes are updated regularly. Check
for the latest version on OpenText My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/16514655).
6.3 Content Server system requirements

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

Content Server – The security fixes for Content Server are vital for proper
installation. If you already have a Content Server installation, make sure you
have installed Content Server. Additionally, install the patches provided in the
Patches folder on the installation medium.
You can also use OpenText™ System Center to install patches. For more
information, see OpenText System Center Manager - Installation and Configuration
Guide (SYSCM-IGD).
Note: If you create a completely new system, Content Server is installed

with the master setup.
Installation of Archive Center Services
Archive Center Services is part of Archive Center. Install Archive Center 16.2
and Update 16.2.2. Additionally, install the patches provided on the Extended
ECM for SAP Solutions installation medium.
Important
Extended ECM for SAP Solutions is not compatible with the Content
Server Interview module which is an optional Case Management module.

6.4. SAP Add-On Installation Tool (SAINT)
Do not install this module in combination with Extended ECM for SAP
Solutions.
ArchiveLink customizing
Customizing of the SAP system and Archive Center must be completed
according to Part II “SAP basis customizing” in OpenText Archiving and
Document Access for SAP Solutions - Scenario Guide (ER-CCS).
Host and port for the logical archive
Check that store and retrieval of ArchiveLink documents functions properly
with the server.
Important
If AL filter is in use, the logical archive (OAC0 transaction) must use the
host and port of the server, where the AL filter process is installed. Usually
this is the Content Server system. Link to OAC0 transaction.
With the newest Archive Center version, the logical archive (OAC0
transaction) must use the host and port of Archive Server.
For older versions, it must use the host and port of Enterprise Library
Services. In this case, restrict access to the Archive Server host and port
exclusively to Enterprise Library using a firewall configuration.
If you are using a firewall between SAP and Content Server, enable
communication for the following ports:
• 8080 (HTTP) or 8090 (HTTPS) on Apache HTTP Server™: used for the Web
service communication from SAP to Content Server
• 8000: used for the communication between Content Server and the SAP
Client.
• 80 (HTTP) or 443 (HTTP): only required for connection tests from SAP to
Content Server
6.4 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 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_2040_700.SAR
Note: The handling of the installation procedure within SAINT depends on the
SAP system. For details, see the SAP documentation.

6.5 AppWorks Gateway system requirements

Installing AppWorks Gateway to support the Content Server mobile app requires
the following:
• Dedicated server with Apache Tomcat

• Database (Microsoft® SQL Server®, MySQL™, Oracle® Database, PostgreSQL, or
SAP® HANA)
• Connection to Directory Services (OTDS)
For more information, see the AppWorks Gateway Release Notes on the AppWorks
Developer website (https://developer.opentext.com/webaccess/#url=%2Fawd
%2Fintro).
6.6 Finding version information for relevant system

components of Extended ECM for SAP Solutions
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.
• Content Server
On the Content Server menu, select Help > About Content Server. The
version is displayed, for example, Content Server 16.2. You also find detailed
information in the Content Server system report. For more information, see
Section 25.2 “Understanding the Content Server System Report” in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
• Web Services and other OpenText components
Go to Control Panel > Add/Remove Programs or Programs and Features. In the
list of programs, you see which version is installed.
• SAP System, Database information and OpenText Components
In the SAP IMG (transaction SPRO, OpenText Extended ECM for SAP Solutions
> Extended ECM > Configuration Report), run the Configuration Report to get
information about the SAP server. In this report, you find information like the
versions of OTEXBAS, OTEXERP, OTEXRL, OTEXRLC, OTEXRLS, OTEXBASO,
OTEXBASF, OTEXRLO, and OTEXRLF. For more information, see Section 25.1.3
“Understanding the Configuration Report” in OpenText Extended ECM for SAP
Solutions - Customizing Guide (ERLK-CGD).
• Support Package of installed SAP System
In the SAP GUI application, 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

6.6. Finding version information for relevant system components of Extended ECM for SAP Solutions
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

Chapter 7
Installing Extended ECM for SAP Solutions
This chapter describes the installation sequence for Extended ECM for SAP
Solutions.
Tip: The installation of a complete OpenText Extended ECM for SAP Solutions
environment is described in the following comprehensive installation
instructions:
• OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft
Windows with Microsoft SQL Server (ERLK-IWS)
• OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft
Windows with Oracle Database (ERLK-IWO)
Important
Always check for the most recent version of an installation guide on OpenText
My Support.
Installation sequence for Extended ECM for SAP Solutions

1. In the SAP system, install the SAP packages:
a. Archiving and Document Access (SAP Add-On) (OTEXBAS)

b. Extended ECM for SAP Solutions (SAP Add-On) (OTEXRL)
2. On the server, install OpenText Extended ECM for SAP Solutions using the
master setup. During installation, select the following:
a. Select the deployment scenario. For a typical all-in-one installation for one
instance of Content Server, select All-in-one Deployment (Archive Center,
Directory Services, Content Server, etc.).
For a two-server landscape, select Content Server Deployment on one
server and Extended Archive Center Deployment (Archive Center,
Directory Services, etc.) on the other server.
b. Windows only: In the Services section, keep the selections and select
Extended ECM Web Services in addition.
UNIX/Linux only: Deploy the WAR file for Extended ECM Web Services
(otsapxecm.war) in Apache Tomcat manually.
c. Install the ArchiveLink Filter into the Apache Tomcat instance, that you
used for Archive Center.
3. Install the required patches; see the respective installation guides. Also check
the installation medium for relevant patches.

Chapter 7 Installing Extended ECM for SAP Solutions
4. Configure the following components:
a. Configure Archive Center.

b. Configure Content Server.
c. Configure OpenText Directory Services (OTDS).
d. Configure modules.
5. Configure Extended ECM for SAP Solutions:
a. Set up security.
b. Set up communication with OTDS.
c. Configure Records Management (declaration, doctypes, jobs).
d. Configure Extended ECM for SAP Solutions business functionality:
business workspaces, business attachments, business relations. For more
information, see OpenText Extended ECM for SAP Solutions - Customizing
Guide (ERLK-CGD).
6. Install the clients:
a. Install Imaging (Web Viewer, Windows Viewer, Enterprise Scan,

DesktopLink, ExchangeLink, NotesLink), OpenText™ Brava!™ Server
Components.
b. Install Enterprise Connect Client (Windows® Explorer/Microsoft®
Outlook®).
c. Install OpenText Administration Client.

Chapter 8
Installing the SAP package
New: The installation of Extended ECM for SAP Solutions Business Scenarios
on the SAP system is now supported.
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_2040_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
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 51 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.

Chapter 8 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-310COINOTE SAPK-310COINOTE SAPK-010COINOTE
XRL XRLO XRLF
Password 9387CF26B8 9387CF49B8 9087CF40B8
File OTEXRL_INST_2140 OTEXRLO_INST_214 OTEXRLF_INST_214
_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-510COINOTE SAPK-310COINOTE SAPK-310COINOTE
XRLC XRLS XRLE
Password 9587CF45B8 9387CF55B8 9387CF43B8
File OTEXRLC_INST_214 OTEXRLS_INST_214 OTEXRLE_INST_214
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

Purpose Extended ECM for SAP Extended ECM for SAP
Solutions for Business Solutions for Business
Scenarios Scenarios
SAP release SAP ERP 6.0 SAP S/4HANA 1909 and later
OCS Package Name SAPK-010COINOTEXRLSA SAPK-310COINOTEXRLSA
Password 9087CF55D9 9387CF55D9
File OTEXRLSA_INST_2140_700. OTEXRLSA_INST_2140_754.
SAR SAR

Package name OTEXRLSA OTEXRLSA
Source path /INST_BUSSCE_700/DATA /INST_BUSSCE_754/DATA
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 Set (BC set) for every client.
To activate the BC set:
1. Start the SCPR20 transaction.

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

activation procedure up to three times.

Chapter 9
Generating roles
The following roles are delivered with the application:
• /OTX/RM_ADMIN
• /OTX/RM_CS_SAP_USER
• /OTX/RM_USER
• /OTX/RM_IMPERSONATED_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*.
After an upgrade, select Roles with Current Profiles for New Generation, and
in the Role field, enter /OTX/RM* to generate updated profiles.
4. Follow the steps to generate the profiles.
5. After an upgrade, perform a mass comparison:
a. On the Utilities menu, click Mass Comparison.

b. As role, enter /OTX/RM*, and then select Cleanups.
c. Follow the steps to do a mass comparison.
6. Start transaction PFCG and check the following roles one by one:
• /OTX/RM_ADMIN
• /OTX/RM_CS_SAP_USER
• /OTX/RM_USER
• /OTX/RM_IMPERSONATED_USER_ROLE
7. 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.

Chapter 10
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 Solutions Release Notes. You
can find the language packages related to the SAP Add-Ons of Extended ECM for
SAP Solutions on OpenText My Support (https://knowledge.opentext.com/
knowledge/cs.dll/Open/8521552).
To install a language package:
1. On OpenText My Support, go to OpenText Extended ECM for SAP Solutions

(https://knowledge.opentext.com/knowledge/llisapi.dll/open/16514655), 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:

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

Chapter 11
Installing the Content Server modules
The installation procedure closely resembles the procedure for any other Content
Server optional module.
11.1 Installation procedure on Content Server

The installation procedure consists of two stages, which are both part of the
automated installation procedure:
1. Copying the module files to the <Content Server home>\staging directory

using the master setup.
2. Installing the modules into Content Server using the Install Modules page of
Content Server's administration interface.
11.2 Installing Content Server and modules files

Important
If you install on a UNIX/Linux system, make sure that you are performing the
setup actions with the user who installed Content Server and runs the Content
Server service.
To install the module files:
1. Run the Mastersetup.exe program (Mastersetup for UNIX/Linux) located on

the installation medium and accept the license agreement.
Tip: The installation procedure for UNIX/Linux systems is similar to the

Windows based installation as described here.

Chapter 11 Installing the Content Server modules
2. Select your deployment scenario. The module installation is included in the

Content Server Deployment scenario and in the All-in-one Deployment
scenario. Click Next.

11.2. Installing Content Server and modules files
3. Under Content Server and Modules, verify that the Extended ECM for SAP
Solutions and the Extended ECM Platform entries are selected.
As the Enforce selection dependencies checkbox is selected by default, all the
dependent modules will be selected as well.
4. Click Next.
If more than one Content Server instance is installed, select the one to which
you want to add the module.
5. Check your entries in the Summary pane, and the click Install.
6. Content Server modules are installed using the same steps. The setups of
Content Server modules are initiated from the installer, one after the other. If
more than one Content Server instance is installed, select the one to which you
want to add the module. After the installation of the module is finished, the
installation of the next module starts automatically.
The files are copied to the staging directory of the server instance of Content
Server that you specified.
Tip: If you want to install the module to several Content Server instances,
you can start the Mastersetup.exe program again selecting another
Content Server instance.

11.3 Installing the Content Server modules

You must install the required Content Server modules in a certain sequence to avoid
error messages during installation.
You must restart the server instance of Content Server between each step. For
information about starting and stopping Content Server servers, see the following
topic of the Content Server administration online help: Server Configuration >
Managing the Servers in Content Server > Stopping and Starting the Servers.
Important
The installation fails if you check all listed modules simultaneously for
installation.
To install Content Server modules:
1. Open the Content Server Administration page in a Web browser.

2. If prompted, enter the Content Server Administrator password, and then click
Log-in.
3. Select Core System – Module Configuration > Install Modules.
4. From the Installable Modules list, install the modules in accordance to the
dependencies between the modules.
Start with installing required modules that do not have any dependencies listed
in the Dependencies column.
5. After the installation of the selected modules is completed, restart Content
Server.
6. Proceed with the next set of modules, which do not have any dependencies.
Restart Content Server.
7. Repeat this step until all modules are installed.
11.4 Installing the Enterprise Asset Management

Business Scenario on Content Server
New: The installation of Extended ECM for SAP Solutions Business Scenarios
on Content Server is now supported.
In the Enterprise Asset Management Business Scenario an Enterprise Asset

Management sample application can be used.
This chapter describes how to install the Extended ECM for SAP Solutions
Enterprise Asset Management Business Scenario on the Content Server. The
configuration is provided in four transport packages:
• OpenText Business Scenario EAM Setup

The package contains web reports for creating users and groups:

11.4. Installing the Enterprise Asset Management Business Scenario on Content Server
– Basic setup
– Enterprise Asset Management setup
• OpenText Business Scenario Enterprise Asset Management – 01
The package contains:
– Categories
– Classifications
The package contains:
– Workspace types
– Unique names
– Business workspace templates
– Business object types
– Enterprise structure (workspace folders)
– Custom columns
– Facets
– Webreports for folders
– Search forms and search queries

– Departmental page
– Workspace perspectives
– Web reports used in perspectives
Prerequisites Download the transport packages (zip files) from the support directory of the
Extended ECM for SAP Solutions module on OpenText My Support and execute the
steps mentioned below for the following transport packages:
• OpenText Business Scenario EAM Setup.zip

• OpenText Business Scenario Enterprise Asset Management – 01.zip
To install the Enterprise Asset Management Business Scenario on Content Server,

install the four packages and configure settings, as follows:
1. Install OpenText Business Scenario EAM Setup

For more information, see “Installing OpenText Business Scenario EAM Setup”
on page 74
2. Install OpenText Business Scenario Enterprise Asset Management – 01
For more information, see “Installing OpenText Business Scenario Enterprise
Asset Management – 01” on page 75


5. Configure settings for the OpenText Business Scenario Enterprise Asset
Management
For more information, see “Configuring settings for the OpenText Business
Scenario Enterprise Asset Management” on page 79
11.4.1 Installing OpenText Business Scenario EAM Setup

With the transport package OpenText Business Scenario EAM Setup.zip proceed
as follows.
To import the package:
1. Navigate to Enterprise > Transport Warehouse.
2. Click on Add Item and select Workbench.
3. Enter a <name> and click on Add.
4. Click on the Transport Packages folder.
5. Click on Add Item and select Transport Package.
6. Click on Choose File, select OpenText Business Scenario EAM Setup.zip that
you downloaded before. Then click Ok.
To deploy each package:
1. On the Transport packages screen, click on OpenText Business Scenario EAM

Setup.zip.
2. Click on Unpack to workbench.
3. In the next screen, click on Browse Content Server and select the workbench
created before.
4. Click on Unpack and, in the next screen, click Ok.
5. In the next screen, click on Deploy workbench to deploy all objects.
6. In the next screen, click Deploy and, in the confirmation popup, click Ok.
Note: The transport warehouse selects the possible matches automatically.

Therefore, you can ignore the message Item has some non-exact matches.
Please review..
7. In the next screen, click Ok to finish deploying.
Note: After deploying, a dialogue shows the status of deployment. For all
objects, the status Ok should be displayed now.

Execute WebReport for Business Scenario Setup:
The WebReport creates the required users and groups:
• Scenario Owner user as the owner of the Business Scenario object

• Scenario Owner Group
• EAM specific groups Maintenance Planner and Maintenance Technician
If needed, also the Enterprise Asset Management sample application is created.
1. Navigate to Enterprise > OpenText Business Scenario EAM Setup.

2. Click on EAM Setup.
3. Click Provide password for Scenario Owner and enter a password. Enter a
name for the Enterprise Asset Management sample application and click on
Run Report.
Note: If you do not want to use the Enterprise Asset Management sample
application, create a business application for your planned external system.
Then enter its ID in the Sample App ID field and no sample app will be
created.

Management – 01
With the transport package OpenText Business Scenario Enterprise Asset
Management – 01.zip proceed as follows.

6. Click on Choose File, select OpenText Business Scenario Enterprise Asset
Management – 01.zip that you downloaded before. Then click Ok.
To deploy the package:
1. On the Transport packages screen, click on OpenText Business Scenario

Enterprise Asset Management – 01.zip.

created before.

4. Click on Unpack and, on the next screen, click Ok.
5. On the next screen, click on Deploy workbench to deploy all objects.
6. In the next screen, click Deploy and, in the confirmation popup, click Ok.

Please review..

Management – 02

To prepare deploying:
Before deploying OpenText Business Scenario Enterprise Asset Management –

02.zip, proceed as follows.
1. To enable browse list column customization, navigate to Enterprise > Content

Server Administration > Features > Configure Container Options.
2. In the Columns section, select the checkbox Enable browse list column
customization and click Save changes.
3. To enable the WR trigger for folder and workspace types, navigate to Enterprise
> Content Server Administration > WebReports Administration > Manage WR
Triggers.
4. In the Node Types section, select the Folder and the Business Workspace
checkboxes, and click Add.

5. Click Save changes.
Note: Before you continue deploying, make sure that a business application is
configured to connect to the business objects deployed in the next step. For an
easy start, OpenText delivers the Enterprise Asset Management sample
application. As well, you can configure a new business application.
For more information, see Section 2.2.1 “Enterprise Asset Management

Business Scenario” in OpenText Extended ECM for SAP Solutions - Customizing
Guide (ERLK-CGD) and “Connecting SAP as the business application”
on page 159.
To deploy the package:


created before.
To connect to a business application:
1. Pause deploying to manually connect to the Enterprise Asset Management

sample application. On the Deployment screen, click on any business object
type, for example, OT Equipment (x).
2. Click Edit in the Business Application row. Then click Browse Content Server.
3. Navigate to Content Server > Extended ECM > Connections to Business
Applications (External Systems), and select the Enterprise Asset Management
sample application or the business application, you created before.
4. Click Save and then click Close.
Note: You can also connect a business application like SAP. For more
information, see “Connecting SAP as the business application” on page 159.
To continue deploying:
1. Return to the Deployment screen,

2. Click Deploy and, in the confirmation popup, click Ok.

Please review.. Still, you have to fix issues for items showing the message
Cannot deploy item.


Management – 03

To prepare deploying:
1. Login as Admin to Content Server.

2. Navigate to Enterprise > Personal > Search Templates.
3. Make sure, you are in the Admin folder, navigate back to Transport Warehouse
and proceed with deploying.
To start deploying the package:


created before.
To integrate perspectives:
1. Pause deploying to manually integrate the perspectives of the Business Scenario

Enterprise Asset Management. On the Deployment screen, open OT
Equipment (x) and select OT Equipment Perspective.

2. Click Edit, then click Browse Content Server.
3. Navigate to Content Server > Perspectives > Business Workspaces and select
OT Equipment(x). Click Save and then click Close.
4. Repeat the steps for the following perspectives of the Business Scenario
Enterprise Asset Management:
• OT Equipment Perspective
• OT Functional Location Perspective
• OT Maintenance Order Perspective
• OT Maintenance Order Operation Perspective
• OT Material Perspective
• OT Notification Perspective
• OT Task List Perspective
• OT Task List Operation Perspective
To finish deploying of the package
1. To proceed deploying you automatically return to the deployment process.

Click Deploy and, in the confirmation popup, click Ok.

Please review..
11.4.5 Configuring settings for the OpenText Business

Scenario Enterprise Asset Management
Finally, you have to change some settings for the OpenText Business Scenario
Enterprise Asset Management. For this, proceed as follows.
To configure Content Server document templates
1. Navigate to Enterprise > Content Server Administration > Configure Content

Server Document Templates.
2. From Classification tree for object types, select

Classifications;Types;Workspace Types.
To configure GoogleMapsApiKey variable to use maps
1. Navigate to Enterprise > Business Workspaces.

2. In the Business Workspaces, select Variables for Replacement Tags.

3. Enter variable name GoogleMapsApiKey in the Name field and the
corresponding key in the Value field.

Chapter 12
Installing language packs on Content Server
This chapter describes how to install language packs on Content Server. The module
installation packages and module support packages include the default language,
which is English. Use the language packs to install other languages. For more
information about available languages, see the Release Notes.
Language packages for support packages
If not stated otherwise, the language packs related to support packages are
cumulative. They include merged language texts of the main version and of
previous and current support packages.
The language packs are available on OpenText My Support at the following location:
OpenText My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/
63201449)
Note: Depending on the delivery bundle, you may also have System Center
access to installation files for components that must not be installed on Content
Server, for example, language installations of Imaging clients and the SAP
language package. For more information, see the installation guides and
release notes for these components.
To install a language pack:
1. Download the language packs from OpenText My Support. You can also obtain
the language packs for support packages and other patches navigating through
the Patches area.
2. Extract the files for the relevant modules in the Content Server root installation
directory.
3. On the Content Server Administration page, go to Core System - Language

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

Language Packs section, select Install for each language that you want to
install, and then click Install.
For more information about language packs, see Help for this page in the
Content Server help.
5. Restart your servers when prompted.
6. Click Continue.

Chapter 13
Deploying Extended ECM Web Services
13.1 Deploying Extended ECM Web Services into the

application server
Install the Extended ECM Web Services on your Apache® Tomcat™ server.
Notes
• Make sure that Tomcat has enough initial memory pool. See Section 2.2.2
“Configuring Tomcat options” in OpenText Enterprise Library - Installation and
Upgrade Guide (EL-IGD) for memory pool size recommendations.
• The Tomcat service must be running during the installation.
• Use the default service name for Tomcat. Otherwise, the installer may be
unable to find the service.
• Restart Tomcat manually after the installation.
To deploy Extended ECM Web Services on Windows:
1. Download the extended ecm web services-21.4.msi file from OpenText My

Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
62453665).
2. Run the MSI file.
3. In the setup wizard, accept the license agreement.
4. Select the Tomcat service to be used.
5. After the installation, Tomcat is started automatically.
To deploy Extended ECM Web Services on UNIX/Linux:
1. Download the otsapxecm.war file from OpenText My Support (https://

knowledge.opentext.com/knowledge/llisapi.dll/Open/76755705).
2. Stop the Tomcat service.
3. Copy the otsapxecm.war file into the <Tomcat home>/webapps/ directory.
4. Start the Tomcat service.
5. After deploying the services, change the directory of the log files.
a. Open the <Tomcat home>/webapps/otsapxecm/WEB-INF/classes/log4j.

xml file in an editor.

Chapter 13 Deploying Extended ECM Web Services
b. Change the line

<param name="File" value="logs/ecmlink.log" />
to
<param name="File" value="../logs/ecmlink.log" />
13.2 Deploying Content Web Services

Extended ECM for SAP Solutions requires OpenText Content Web Services. During
the installation of Content Server, the Content Web Services WAR file is placed in
the <Content Server home>/webservices/java/webapps directory.
Deploy the web service cws to the Tomcat installation on the server where you also
installed Archive Center.
To deploy Content Web Services:
1. Copy the cws.war file from <Content Server home>/webservices/java/

webapps to your <Tomcat home>/webapps directory.
2. UNIX/Linux systems only: After deploying the services, change the directory of
the log files.
a. Open the <Tomcat home>/webapps/cws/WEB-INF/classes/log4j.xml file

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

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

editor.
2. Find the following elements and change the values according to your needs:
<context-param>
<param-name>LivelinkServer</param-name>
<param-value>cs.example.com</param-value>
</context-param>
<context-param>
<param-name>LivelinkServerPort</param-name>
<param-value>2099</param-value>
</context-param>
<context-param>
<param-name>LivelinkEncoding</param-name>

13.3. Configuring host and port for Content Server in Tomcat
<param-value>UTF8</param-value>
</context-param>
3. Restart the Tomcat service for the changes to take effect.

Chapter 14
Installing OpenText ArchiveLink Filter
OpenText ArchiveLink Filter allows you to delete ArchiveLink documents on the

SAP system.
Prerequisites Content Server and the Tomcat server in which you want to install OpenText
ArchiveLink Filter must be running.
Restrictions See the Content Server release notes for supported OpenJDK versions.
To install OpenText ArchiveLink Filter:
1. Obtain the OpenText ArchiveLink Filter 21.4.msi file from OpenText

Software Center.
2. Double-click the file and follow the instructions of the installer.
a. Accept the license agreement, then click Next.
b. Enter or select the following information, then click Next.
• Java Home directory: You must use an OpenJDK version supported by

Content Server.
• Tomcat Home Directory: Enter a Apache Tomcat instance. The version
must be version 9 or newer.
• Host: Fully qualified name of the machine, the OpenText ArchiveLink
Filter is going to be installed on, for example mycontentserver.
example.com.
• Port: Port of the Apache Tomcat server that hosts the OpenText
ArchiveLink Filter webapp.
• Protocol: Select the protocol that you want the ArchiveLink Filter to use.
c. Enter the connection information to Content Server, then click Next.
• Content Server URL: Enter the Content Server URL with protocol, port
and path to the cs.exe, for example https://mycontentserver.
example.com:9090/OTCS/cs.exe.
• Username and Password: Credentials of the Content Server

Administrative user.
Tip: You can later change your settings in the properties file <TOMCAT_
HOME>/lib/alfilter_resources/application.properties.

Chapter 14 Installing OpenText ArchiveLink Filter
3. Optional If you are running Content Server and the ArchiveLink Filter in the same
Tomcat instance, check if the following tags are present in the Server/
Service/Engine/Host section of the TOMCAT_HOME/conf/server.xml file.
<Context path="/OTCS" reloadable="true"/>
<Context path="/alfilter" reloadable="true"/>
If not, add them accordingly.

Chapter 15
Installing AppWorks Gateway (optional)
AppWorks Gateway acts as a proxy server and allows the Content Server Mobile
app to communicate securely with Content Server. It is deployed in Apache®
Tomcat™.
You configure AppWorks Gateway to connect to Directory Services (OTDS) and a

production database such as Oracle Database or SQL Server.
Using the Content Server Mobile app, your users can access and share Content
Server content, manage documents and files, complete Workflow assignments that
are designed for Smart View, and view documents that users have marked for
offline viewing. Offline viewing allows a user to view and edit Content Server files
on their mobile device when the device is not connected to Content Server or
AppWorks Gateway.
For more information, see OpenText AppWorks Gateway - Installation and

Administration Guide (OTAG-IGD) and OpenText Content Server Mobile - Configuration
Guide (CSMOB-CGD).

Part 3
Upgrading Extended ECM for SAP
Solutions
Part 3 Upgrading Extended ECM for SAP Solutions
This part outlines the different upgrade scenarios.
• “Upgrade scenarios“ on page 93

• “General recommendations for the upgrade“ on page 99
• “Upgrading to Extended ECM for SAP Solutions 21.4“ on page 101
• “Upgrading from Extended ECM for SAP Solutions 20.2 to 21.4“ on page 105
• “Upgrading Business Scenarios on the SAP system“ on page 111

Chapter 16
Upgrade scenarios
There are different upgrade scenarios depending on the Content Server version from
which version you upgrade.
16.1 Supported combinations

You can split up the upgrade into two maintenance windows; however, you must
keep this order.
1. Upgrade the Content Server system. The new Content Server system will be
working with an SAP system that is not updated yet.
2. Upgrade the SAP system. “” on page 93 lists possible working combinations of
old and new versions of the Content Server module and the SAP Add-on.
Important
You can run Content Server on a higher version than the SAP system, but you
must first upgrade Content Server to 20.4 before you update the SAP ABAP
Add-On OTEXRL (and depending Add-Ons) to 20.4. This order is mandatory if
you use Records Management. If you do not use Records Management, still
OpenText recommends that you keep this order.
For information about known issues, see the Release Notes.
You can use the following upgrade combinations:
Table 16-1:
Content Server and module version SAP Add-on version OTEXRL

16.2.0 – 16.2.3 16.2
16.2.4 – 16.2.9 16.2

16.2.4 – 16.2.9 16.2 SP1 (16.2.4)
16.2.10 16.2
16.2.10 16.2 SP1 (16.2.4)
16.2.10 16.2 SP2 (16.2.10)
20.2 16.2 SP2 (16.2.10)

Chapter 16 Upgrade scenarios
Content Server and module version SAP Add-on version OTEXRL

20.2 16.2 SP3 (20.2)
20.3 16.2 SP2 (16.2.10)

20.3 16.2 SP3 (20.2)
20.4 16.2 SP2 (16.2.10)

20.4 16.2 SP3 (20.2)
20.4 20.4
21.1 16.2 SP2 (16.2.10)

21.1 16.2 SP3 (20.2)
21.1 20.4
21.2 16.2 SP2 (16.2.10)

21.2 16.2 SP3 (20.2)
21.2 20.4
21.3 16.2 SP2 (16.2.10)

21.3 16.2 SP3 (20.2)
21.3 20.4
21.4 16.2 SP3 20.2

21.4 20.4
21.4 21.4
16.2 Phasing out Enterprise Library

Enterprise Library was a framework to apply records management to SAP
documents. With version 20.2, Enterprise Library is not used anymore – with a one
exception: If you require SAP ILM, you still need Enterprise Library.
The Enterprise Library record functionality is now taken over by alternative

methods native to Extended ECM and using a RESTful API. To make your existing
Enterprise Library records accessible without having Enterprise Library installed,
you must migrate them.

16.2. Phasing out Enterprise Library
16.2.1 Upgrading with Enterprise Library installed

Upgrade sequence with Enterprise Library
1. Upgrade your Extended ECM system to 20.2 or later, both SAP and Content
Server.
2. Upgrade Enterprise Library to 16.2.11
3. Migrate your documents from Enterprise Library to Extended ECM. For more
information, see “Migrating Enterprise Library records and other items”
on page 95.
4. In Content Server Administration, under Search Administration, select Open
the System Object Volume. Then delete all Enterprise Library Data Source folders.
Tip: After deleting the Enterprise Library Data Source folder(s) go back to
System Object Volume. Under Slices recheck that all Enterprise Library
slices are deleted too.
Important
Any slices related to the Enterprise Data Source in Content Server
Administration under Slices must not be deleted.
5. Uninstall the Enterprise Library module and web service, that is unless you are
using SAP ILM. If you are using SAP ILM, you must keep Enterprise Library.
16.2.2 Migrating Enterprise Library records and other items

Migration order
OpenText recommends the following order for your migration process. However,
you can switch step 1. and 2., but the third conversion step must remain the last one.
1. Enterprise Library records. This operation is a database operation, which adds

additional information to the record.
2. Objects in Enterprise Library volumes. This operation moves items from the
Enterprise Library volumes to the Legacy Record Folders. You can access this
folder from the Content Server Administration > Extended ECM > Root
Folders. If there are migrated objects, a root folder contains a Legacy Record
folder.
3. Enterprise Library system categories. Moves category definitions that are
associated with an Enterprise Library type to category folder System Record
Type Categories in the categories volume and deletes the related Enterprise
Library type. Therefore, you must complete this step only after you migrated
documents and volumes.
Migration is done by scheduled processing tasks. You can schedule the tasks or run
them immediately. For more information about scheduled processing, see Section 8
“Using Scheduled processing” in OpenText Extended ECM for SAP Solutions -
Customizing Guide (ERLK-CGD).

Chapter 16 Upgrade scenarios
To migrate Enterprise Library items:
1. Migrate Enterprise Library documents:
a. Create a scheduled processing job with the job type Migrate Enterprise
Library Records.
Leave Business Application and Business Object Type blank.
b. Review the settings for Records per Task and Records Fetch Size.
OpenText recommends that you leave the default values.
c. Run this job either scheduled or start it immediately.
2. Migrate the Enterprise Library volumes:
Library Volume.
b. Edit the processing job and enter a volume name. You find the Enterprise
Library volumes in the Content Server Administration > Enterprise
Library Administration > Open the Enterprise Library Volumes.
c. Review the settings for Child Objects per Task and Child Objects per
Fetch. OpenText recommends that you leave the default values.
If the volume contains child folders with an extremely huge number of
objects, for example hundreds of thousands or millions, and especially
when it contains deeply nested folder hierarchies, OpenText recommends
that you use a low value for the Child Objects per Task. In extreme cases it
might be necessary to increase the database transaction log size.
d. Run this job either scheduled or start it immediately.
e. Check if the Enterprise Library volumes are empty.
3. Migrate the Enterprise Library types.
Library Types.
b. Edit the processing job and enter the following:
• Type Names: Enter the name of the types. Separate multiple names
with a comma. Leave this field empty to select all types. You find the
Enterprise Library types in the Content Server Administration >
Enterprise Library Administration > Open the Enterprise Library
Type Volumes.
Important
If you have custom applications, you must keep all types for these
applications as long as you want to run the applications. You must
thoroughly check, which types are used with objects for the
custom application.

16.2. Phasing out Enterprise Library
If you use backslash “\” or commas “,” in your type names, you must
escape them with a backslash resulting in “\\” and “\,”.
c. Review the settings for Types per Task and Types per Fetch. OpenText
recommends that you leave the default values.
d. Run this job either scheduled or start it immediately.
e. Check in the Content Server Administration if the Enterprise Library Type
volumes are empty and the Extended ECM System Record Type Categories
are filled.

Chapter 17
General recommendations for the upgrade
When you perform an upgrade, you must upgrade the various components of
Extended ECM for SAP Solutions.
Note: Always use the latest patches for upgrade. Particularly, always install
the latest patch for Business Workspaces before you upgrade the database
schema.
To perform an upgrade:
1. Refer to the Release Notes of Extended ECM for SAP Solutions to determine
which versions of the different components are required. On System Center,
you have access to all supported components.
2. Plan your upgrade procedure. OpenText recommends the following:
a. Retrieve all related documentation. Since many different components are

involved you will need to go through many different guides.
Refer to Section 5 “Upgrading Enterprise Library” in OpenText Enterprise
Library - Installation and Upgrade Guide (EL-IGD). This guide describes the
different stages of the upgrade and refers to other relevant guides.
b. Perform the upgrade on your development systems. One option is to split
up the upgrade procedure: In a first maintenance window, upgrade
Content Server and all related components. Test if the new version is
running with the old components in the SAP system. Later, in a second
maintenance window, upgrade the relevant components on the SAP
system. The other way is supported, too. For more information, see
“Supported combinations” on page 93.
Note the exact procedure with all necessary steps.
c. Perform the upgrade on the test system. Follow exactly the steps you noted
to verify the procedure. If necessary, adapt the list.
d. Perform the upgrade on the production system. OpenText recommends
that you have two maintenance windows: The first for the upgrade of
Content Server and all related components, the second for the components
on the SAP system. The other way is supported, too. For more information,
see “Supported combinations” on page 93.

Chapter 18
Upgrading to Extended ECM for SAP Solutions 21.4
“” on page 93 lists possible working combinations of old and new versions of the
Content Server module and the SAP Add-on. For information about the necessary
steps see the checklists for the different upgrade paths.
18.1 Checklist for the upgrade

Table 18-1: Update checklist for upgrade to Extended ECM for SAP Solutions
21.4
Step System and Information

tools
Upgrading Content Server, Content Server modules, Directory Services, Archive Center
Prepare your Content Server All OpenText For more information, see the following
system for the upgrade systems guides and linked information:
OpenText Content Server - Upgrade Guide
(LLESCOR-IUP)
OpenText Content Server - Module Installation
and Upgrade Guide (LLESCOR-IMO)
Migrate OpenText Directory Server on For more information, see Section 1.2
Services to newest version which “Importing data from previous versions of
Directory Directory Services” in OpenText Directory
Services is Services - Installation and Administration Guide
installed (OTDS-IWC).
Upgrade and configure Archive For more information, see the following and
Archive Center Center linked guides.
OpenText Document Pipelines - Installation and
Upgrade Guide (AR-IDPDP) and the Archive
Center Upgrade Guides.
• Use Directory Services authentication.
• Use the new resource ID that was created
for Archive Center during Directory
Services migration.
Upgrade Document Pipelines For more information, see OpenText
(only relevant if you are Document Pipelines - Installation and Upgrade
using Document Pipelines) Guide (AR-IDPDP).
Update Content Server Content Use System Center to retrieve and install the
Server latest patches.

Chapter 18 Upgrading to Extended ECM for SAP Solutions 21.4

tools
Install the Updates for Always use the latest patches from
Content Server, Archive OpenText My Support.
Center, and finish the
Archive Center
configuration.
If you are working with With the upgrade, the appearances are
appearances, update the automatically renamed from SAPBASE_* to
relevant path EXTENDED_ECM_*. In the content of all
relevant appearances, in the header, replace
sapbase with otsapxecm.
If you are performing an in-parallel upgrade

of Content Server, run the following tool to
ensure that the configuration is updated
correctly:
http://server/otcs/cs.exe?func=otsapxecm.Configure&module=otsapxecm
Deploy Extended ECM Web To upgrade Extended ECM Web Services,

Services you need to perform these steps manually:
Download the new version from My
Support, remove the old version, and deploy
the new version. For more information, see
“Deploying Extended ECM Web Services
into the application server” on page 83.
Deploy CMIS Web Services For more information about this optional
(optional) feature, see the “CMIS Cookbook” on My
Support (https://knowledge.opentext.com/
knowledge/llisapi.dll/Overview/68247627).
Perform post-upgrade steps SAP system • Change the logical port for Content
in the SAP system Server Member Services from les-
services to cws.
• Update the connection settings to point
to the new systems. For more
information, see “Maintaining Extended
ECM connections” on page 152.
Perform post-upgrade steps Directory • Update the Content Server resource
in Directory Services Services settings to point to the new systems.
• Update the Content Server resource
settings to point to Content Web Services
cws instead of les-services.
For more information, see Section 5.3
“Creating and configuring resources for
Directory Services” in OpenText Extended
ECM for SAP Solutions - User Management
and Access Control Scenarios (ERLK-CUM).
If you encounter problems, re-create the
Content Server resource.

18.1. Checklist for the upgrade

tools
Perform post-upgrade steps Content If there is a change in the Archive Center
in Content Server Server port or system, update the setting on
Content Server in the Archive Storage
Provider settings.
Perform post-upgrade steps Archive Upload the relevant certificates and enable
in Archive Center Center them for Archive Center and for the logical
archives: SP_<hostname>: Archive Storage
Provider certificate.
Upgrade clients Clients Upgrade the Enterprise Connect client after
the Enterprise Connect module and the
Office Editor module are updated.
After this maintenance window and all relevant steps, the new systems are working with
the old SAP system. All scenarios work without changing the configuration.
Upgrading the SAP Add-ons
Upgrade Extended ECM for SAP system, “Upgrading Extended ECM for SAP
SAP Solutions Add-ons from SAINT Solutions in the SAP system” on page 104
20.4 to 21.4 transaction
If the connection test on SAP system Do one of the following:
Content Server does not
• Create a new web service binding in the
work, configure the Service SOAMANAGER and switch all the
Provider Interface again. connections on Content Server side to
use the new binding.
• Delete the old web service binding and
create a new web service binding in the
SOAMANAGER with the same settings
as before. Changes on Content Server are
not necessary.
For more information, see “Configuring the
Service Provider Interface service”
on page 149.
Also recreate the logical ports and activate

them. For more information, see “Creating
logical ports in the SAP system”
on page 130.
Perform post-installation Content Perform post-installation steps. For more
steps Server and information, see “Configuring the system
SAP system after the installation” on page 113.
Verify the installation SAP system Run the Diagnostics Program. For more
information, see “Understanding the SAP
Diagnostic Program” on page 245.

Chapter 18 Upgrading to Extended ECM for SAP Solutions 21.4
18.2 Upgrading the database schema

The current version of the Business Workspaces module changes database tables.
The database schema is upgraded with the standard Content Server mechanism.
When an upgrade is necessary, you are prompted accordingly and can upgrade the
database.
Note: You can monitor the database schema upgrade in a separate log file. This
log file is created in the logs directory of Content Server during the upgrade:
ECMLinkDBSchemaUpgrade_<threadID>.log. It logs all SQL statements of the
upgrade.
Important
Make sure that you installed the latest patch of Business Workspaces before
you upgrade the database schema.
18.3 Upgrading Extended ECM for SAP Solutions in

the SAP system
Note: After you updated Content Server you can still work with the older
version in the SAP system. Hence, you can delay the upgrade of Extended
ECM for SAP Solutions in the SAP system to a later maintenance window.
• If you want to migrate toSAP S/4HANA, which is supported since OpenText

Extended ECM for SAP Solutions 16, see the respective SAP documentation for
information about all relevant prerequisites and steps.
• Install the installation packages of Archiving and Document Access for SAP
Solutions 21.4 and OpenText Extended ECM for SAP Solutions 21.4 with the
SAINT tool. Dependencies between packages are resolved this way. For more
information, see Installing the SAP package. For more information, see
“Installing the SAP package“ on page 61.
• Ensure that for the HTTP connection to OTDS, the option Send SAP Logon
Ticket is selected. For more information, see “Creating logical ports for SAP
Basis 7.0” on page 130.

Chapter 19
Upgrading from Extended ECM for SAP Solutions
20.2 to 21.4
“” on page 93 lists possible working combinations of old and new versions of the
Content Server module and the SAP Add-on. For information about the necessary
steps see the checklists for the different upgrade paths.
19.1 Checklist for the upgrade

Table 19-1: Upgrade checklist for upgrade from Extended ECM for SAP
Solutions 20.2 to 21.4

tools
Upgrading Content Server, Content Server modules, Directory Services, Archive Center
Prepare your system for the All OpenText For more information, see Section 5
upgrade systems “Upgrading Enterprise Library” in OpenText
Enterprise Library - Installation and Upgrade
Guide (EL-IGD) and the linked guides.
Migrate OpenText Directory Server on For more information, see Section 1.2
Services to newest version which “Importing data from previous versions of
Directory Directory Services” in OpenText Directory
Services is Services - Installation and Administration Guide
installed (OTDS-IWC).
Upgrade and configure Archive For more information, see Section 5.1
Archive Center Center “Upgrade roadmap” in OpenText Enterprise
Library - Installation and Upgrade Guide (EL-
IGD) and the linked guides.
• Use Directory Services authentication.
• Use the new resource ID that was created
for Archive Center during Directory
Services migration.
Upgrade Document Pipelines For more information, see OpenText
(only relevant if you are Document Pipelines - Installation and Upgrade
using Document Pipelines) Guide (AR-IDPDP).

Chapter 19 Upgrading from Extended ECM for SAP Solutions 20.2 to 21.4

tools
Upgrade Content Server Content To upgrade Content Server, you perform a
Server parallel upgrade installation: Make copies of
your database, External File Store, and
search index. You install a new instance of
Content Server and set up your new instance
to match your existing deployment. You
then connect that instance to a copy of your
production database. The database directs
you as you install required modules, set up
your Admin servers, connect to your Storage
Providers, and finally upgrade the database
itself.
After that, you connect to Directory Services

(OTDS).
If necessary, you make adjustments to your

search and indexing environment, and apply
a new license to Content Server.
Install the Updates for Always use the latest patches from
Content Server and Archive OpenText My Support.
Center, and finish the
Archive Center
configuration.
If you are working with With the upgrade, the appearances are
appearances, update the automatically renamed from SAPBASE_* to
relevant path EXTENDED_ECM_*. In the content of all
relevant appearances, in the header, replace
sapbase with otsapxecm.
If you are performing an in-parallel upgrade

of Content Server, run the following tool to
ensure that the configuration is updated
correctly:
http://server/otcs/cs.exe?func=otsapxecm.Configure&module=otsapxecm

19.1. Checklist for the upgrade

tools
For the Template Content This step is required if your previous version
Workspaces module, Server was Template Workspaces 10.1, Contract
perform the configuration Management 10.1, Case Management
upgrade and the data Framework 1.1.0, 10.0.0 or Contract
upgrade Management 2.1.1. Additionally, in the
Template Workspace Administration
section, you need to do the upgrade step.
Make sure the
LivelinkDocumentTemplates setting is
moved from the opentext.ini of the old
Content Server system to the new one. After
that, perform the configuration and data
upgrade. For more information, see
OpenText Content Server - Upgrade Guide
(LLESCOR-IUP).
Perform post-upgrade steps SAP system • Change the logical port for Content
in the SAP system Server Member Services from les-
services to cws.
• Update the connection settings to point
to the new systems.
Perform post-upgrade steps Directory • Update the Content Server resource
in Directory Services Services settings to point to the new systems.
• Update the Content Server resource
settings to point to Content Web Services
cws instead of les-services.
“Creating and configuring resources for
Directory Services” in OpenText Extended
ECM for SAP Solutions - User Management
and Access Control Scenarios (ERLK-CUM)
If you encounter problems, re-create the
Content Server resource.
Perform post-upgrade steps Content If there is a change in the Archive Center
in Content Server Server port or system, update the setting in Content
Server in the Archive Storage Provider
settings.
Perform post-upgrade steps Archive Upload the relevant certificates and enable
in Archive Center Center them for Archive Center and for the logical
archives:
SP_<hostname>: Archive Storage Provider

certificate
Upgrade clients Clients Upgrade the Enterprise Connect client after
the Enterprise Connect module and the
Office Editor module are updated.

Chapter 19 Upgrading from Extended ECM for SAP Solutions 20.2 to 21.4

tools
After this maintenance window and all relevant steps, the new systems are working with
the old SAP system. All scenarios work without changing the configuration.
Upgrading the SAP Add-ons
Upgrade Extended ECM for SAP system, “Upgrading to Extended ECM for SAP
SAP Solutions Add-ons from SAINT Solutions in the SAP system” on page 109
20.2 to 21.4 transaction
If the connection test on SAP system Do one of the following:
Content Server does not
• Create a new web service binding in the
work, configure the Service SOAMANAGER and switch all the
Provider Interface again. connections on Content Server side to
use the new binding.
• Delete the old web service binding and
create a new web service binding in the
SOAMANAGER with the same settings
as before. Changes on Content Server are
not necessary.
Also recreate the logical ports and activate

them.
Perform post-installation Content Perform post-installation steps. For more
steps Server and information, see “Configuring the system
SAP system after the installation” on page 113.
Verify the installation SAP system Run the Diagnostics Program.
19.2 Upgrading the database schema

The current version of the Business Workspaces module changes database tables.
The database schema is upgraded with the standard Content Server mechanism.
When an upgrade is necessary, you are prompted accordingly and can upgrade the
database.
Note: You can monitor the database schema upgrade in a separate log file. This
log file is created in the logs directory of Content Server during the upgrade:
ECMLinkDBSchemaUpgrade_<threadID>.log. It logs all SQL statements of the
upgrade.
Important
Make sure that you installed the latest patch of Business Workspaces before
you upgrade the database schema.

19.3. Upgrading to Extended ECM for SAP Solutions in the SAP system
19.3 Upgrading to Extended ECM for SAP Solutions in

the SAP system
Note: After the previous steps, you can still work with the old version in the
SAP system. Therefore, you can move the upgrade of Extended ECM for SAP
Solutions in the SAP system to a later maintenance window.
• If you want to migrate to SAP S/4HANA, which is supported since by OpenText

Extended ECM for SAP Solutions 16, see the respective SAP documentation for
information about all relevant prerequisites and steps.
• Install all required SAP Notes. For more information, see “SAP system
requirements” on page 51.
• Install the relevant packages for Archiving and Document Access for SAP
Solutions 21.4 with the SAINT tool.
• Install the relevant packages for OpenText Extended ECM for SAP Solutions 21.4
with the SAINT tool and activate the BC sets. For more information, see
“Installing the SAP package“ on page 61.
• In the IMG, go to the Maintain Extended ECM Connections activity and change
the External System ID from the old connection to the new connection. For more
information, see “Maintaining Extended ECM connections” on page 152.
Ensure that for the HTTP connection to OTDS, the option Send SAP Logon
Ticket is selected. For more information, see “Creating logical ports for SAP
Basis 7.0” on page 130.

Chapter 20
Upgrading Business Scenarios on the SAP system
The Extended ECM for SAP Solutions Business Scenarios Add-on for SAP ERP
(component OTEXRLSA), release 2140_700 has import conditions which allow to
install it or keep it from SAP ERP 6.0 up to SAP S/4HANA 2120.
To have the full Business Scenarios functionality forSAP S/4HANA 1909 and later,
OTEXRLSA release 2140_754 must be installed instead.
If you upgrade an older SAP ERP release to SAP S/4HANA 1909 or later, and
previously installed OTEXRLSA 2140_700, you have to install OTEXRLSA 2140_754.

Part 4
Configuring the system after the
installation
Part 4 Configuring the system after the installation
This part explains the tasks that you perform after the installation. You need system
administrators access to Content Server.
• “Connecting the SAP system“ on page 115

• “Performing general post-installation tasks in SAP“ on page 119
• “Performing system administration tasks in Content Server“ on page 157
• “Performing additional optional tasks in the SAP system“ on page 227
• “Verifying the installation“ on page 245

Chapter 21
Connecting the SAP system
21.1 Connecting the SAP system with Content Server

After you installed and prepared the SAP system, you connect it to your Content
Server instance.
Content Server
The Content Server instance has been prepared for the connection: ports and
firewall are configured accordingly. Content Server uses the following default
ports:
443 – Content Server HTTPS default port
8442 – Tomcat HTTPS default port for Web services and OTDS
For more information about the connection settings in Content Server, see
“Importing root certificates for Secure Sockets Layer (SSL) connections”
on page 157 and “Connecting SAP as the business application” on page 159.
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 for SAP ERP 6.0, SAP CRM 7.0, and SAP
SRM 7.0” on page 125.

Chapter 21 Connecting the SAP system
21.2 Connecting the SAP system with OpenText

Archive Center
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
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.
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).

21.2. Connecting the SAP system with OpenText Archive Center
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. In addition, the port should be shown, for
example: monopoly:8080.
From SAP basis 6.20, the port no. is entered in a separate field.
Port Number
For HTTP connections, enter the port number 8080.
Port Number of ArchiveLink connection.
SSL Port Number
For HTTPS connections, enter the SSL port number 8090.
When using the secure transfer protocol SSL (Secure Socket Layer).
Program (CRM: HTTP Script)
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)).

Chapter 21 Connecting the SAP system
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.
21.2.1 Creating an archive on the OpenText Archive Center

On the OpenText Archive Center you must create an archive with the same name as
in the SAP system. When you configure the archive, specify the media type on
which the documents are to be archived (for example, CD, DVD, WORM, hard disk),
and indicate the exchange directory.
For more, information, see OpenText Archive Center - Administration Guide (AR-ACN).

Chapter 22
Performing general post-installation tasks in SAP
Before using the Extended ECM for SAP Solutions functions, you must perform a
series of post-installation and customizing tasks in SAP. For more information,
see“Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM
7.0” on page 125.
For information about the scenario-specific post-installation tasks, see OpenText

22.1 Performing general post-installation tasks in

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

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

22.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 Solutions.
i. Click Find structure to search for the Extended ECM for SAP Solutions
customizing IMG structure. Search for OpenText - Extended ECM for SAP
Solutions.
j. Click Copy.
k. Click Save.
3. Enhance the SAP IMG structure for Archiving and Document Access:
Repeat the steps described in Step 2 for the OpenText Archiving and Document
Access customizing with the corresponding data:
• Name of the node: OpenText Archiving and Document Access for SAP
Solutions
• Name of the IMG structure: OpenText Archiving and Document Access for
SAP Solutions

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

22.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_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 159.
/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).
22.1.3 Adjusting authorization default values

OpenText provides standard authorization assignments for Extended ECM for SAP
Solutions transactions as part of the installation packages. You can set default values
for the assignment of an authorization to a transactions, 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.
To copy standard Extended ECM assignments into customer tables:
1. Import the Extended ECM for SAP Solutions 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. Activate 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 transaction:
• /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
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.

22.2. Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0
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
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.
22.2 Performing post-installation tasks for SAP ERP

6.0, SAP CRM 7.0, and SAP SRM 7.0
22.2.1 Exporting the SAP PSE certificate for the SAP
authentication handler
You need the SAP PSE certificate to create the SAP authentication handler in
OpenText Directory Services. The SAP authentication handler validates SAP tickets
sent from the SAP system against the exported certificate. You export the certificate
in a PSE file from SAP using the Export System PSE Certificate to File System
activity in the SAP IMG.
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.

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.

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
otadmin@otds.admin.
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

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.
22.2.2 Activating the SSO HTTP service

You must activate the HTTP service to use the Single sign-on (SSO) service.
Note: Make sure that the SSO profile parameters of your SAP system are set to
the following values:
• login/accept_sso2_ticket = 1 for the Web Service communication

between SAP and Content Server
• login/create_sso2_ticket = 2 for the display of Content Server HTML

dialogs in SAP GUI
• 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 144.
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.

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.

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.
22.2.3 Creating logical ports in the SAP system

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

Extended ECM for SAP Solutions connects to OpenText components using HTTP
connections and logical ports.
Create the following HTTP connections to the required web services:
• Extended ECM
• OpenText Directory Services
• Content Server Member Services
• Enterprise Library (only if still required due to Content Server version older than
16.2.10)
• Enterprise Library Content Services (only if still required due to Content Server
version older than 16.2.10)
To create the HTTP connections:
Infrastructure > Create HTTP Connections activity, and then click Execute.

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 SAP Logon Ticket must be enabled.
See also SAP_BASIS component with a version later than 16 on page 133.

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 OpenText Content Enterprise Enterprise

ECM Directory Server Library Library
Services Member Services Content
Service (if required) Services
(if required)
RFC Enter a Enter a Enter a Enter a name Enter a
Destination name, for name, for name, for for this name, for
example example example connection, example
EXTECM_ OTDS_DEST. CSMEMBER_ for example ELCONTENT
DEST. DEST. ELS_DEST_ _DEST.
CORE.
Connections G (HTTP G (HTTP G (HTTP G (HTTP G (HTTP
Type Connection Connection Connection Connection Connection
to External to External to External to External to External
Server) Server) Server) Server) Server)
Technical Settings tab
Target host Host name Host name Host name Fully Host name
of Extended of OTDS of the qualified of the
ECM installation[a] Content host name of Enterprise
installation Server your Library
installation Enterprise Services
Library installation
Services
installation
Service No. Extended Directory Content Enterprise Enterprise
ECM Web Services Server Library Web Library
Services port Web Member Services Content
Services port Services port port; port Services port
8080 is
typically
used for
Apache
Tomcat.
Path Prefix / /ot- /cws/ /ot-elib/ /ot-elib/
otsapxecm authws/ services/ services/ services/
/ services/ MemberSer Enterpris Content
services/ Authentic vice eLibrary
ECMLink ation
[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 SAP Logon
Ticket.
• On the Messaging tab, in the Message ID Protocol field, select the Suppress
ID Transfer value.
SAP_BASIS component with a version 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:
– 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
• Enterprise Library logical port (if required)
• Enterprise Library Content Services logical port (if required)
To create a logical port for SAP Basis 7.0:
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.

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

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

Extended ECM for SAP Solutions connects to OpenText components using logical
ports.
Create a corresponding logical port for each connection:
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 >

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.

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 (usually 8080 for Tomcat)
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. If not indicated
otherwise, use the settings as described for the Enterprise Library port.
Extended Authenticati Content Enterprise Enterprise

ECM on Server Library Library
Member (if required) Content
Service Services
(if required)
Internal /OTX/CO_ /OTX/CO_ /OTX/CO_ /OTX/CO_ /OTX/CO_
name RM_WSW_ OTDSAUTHE MBLLMEMBE RMELENTER RMELCONTE
ECMLINK NTICATION R_SERVICE PRISE_ NT
LIBRARY
URL Access / /ot- /cws/ /ot-elib/ /ot-elib/
Path otsapxecm authws/ services/ services/ services/
/ services/ MemberSer Enterpris Content
services/ Authentic vice eLibrary
ECMLink ation
Computer Host name Host name Host name Enterprise Host name
Name of Extended of OTDS of Content Library of Enterprise
Access URL ECM installation[a] Server Services Library
installation Member installation Content
Service host name Services
installation installation
[a]
If you are using user-specific mapping with impersonation (SAP BAdI), and if OTDS, Enterprise
Library Services, and Content Server are installed on different servers, enter the host name of the
Enterprise Library installation.
• On the Consumer Security tab, select SAP Authentication Assertion Ticket.

• On the Messaging tab, in the Message ID Protocol field, select the Suppress
ID Transfer value.


ports.

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:

Content Server installation host name
• Port Number of Access URL: usually 8080 for Tomcat
• Transport Binding Type: SOAP1.1
Click Next.
9. In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID
Transfer.
Click Next.
10. In the Operation specific step, select the GetObjects operation.

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 Enterprise

Member Library
Service Content
(MemberServic Services
e) (Content)
(if required)
Internal name /OTX/CO_RM_ /OTX/CO_ /OTX/CO_ /OTX/CO_
WSW_ECMLINK OTDSAUTHENT MBLLMEMBER_ RMELCONTENT
ICATION SERVICE
URL Access /otsapxecm/ /ot-authws/ /cws/ /ot-elib/
Path services/ services/ services/ services/
ECMLink Authenticat MemberServi Content
ion ce
Computer Host name of Host name of Host name of Host name of
Name of Extended ECM OTDS Content Server Enterprise
Access URL installation installation[a] Member Service Library Content
installation Services
installation
Port Number of Extended ECM Directory Content Server Enterprise
Access URL Web Services Services Web Member Service Library Content
port, usually Services port , port, usually Services port,
8080 for Tomcat usually 8080 8080 for Tomcat usually 8080 for
for Tomcat Tomcat
[a]

• Consumer Security: SAP Authentication Assertion Ticket

• Message ID Protocol: Suppress ID Transfer

ports.
• Extended ECM
• OpenText Directory Services
• Enterprise Library (if required)
• Enterprise Library Content Services (if required)
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:

Enterprise Library Services installation host name
• Port Number of Access URL: Web Services port (usually 8080 for Tomcat)
Click Next.
9. In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID
Transfer.
Click Next.
10. Click Finish.

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

Member Library
Service Content
e) (Content)
(if required)
Internal name /OTX/CO_RM_ /OTX/CO_ /OTX/CO_ /OTX/CO_
WSW_ECMLINK OTDSAUTHENT MBLLMEMBER_ RMELCONTENT
ICATION SERVICE
URL Access /otsapxecm/ /ot-authws/ /cws/ /ot-elib/
Path services/ services/ services/ services/
ECMLink Authenticat MemberServi Content
ion ce


Member Library
Service Content
e) (Content)
(if required)
Computer Host name of Host name of Host name of Host name of
Name of Extended ECM OTDS Content Server Enterprise
Access URL installation installation[a] Member Service Library Content
installation Services
installation
Port Number of Extended ECM Directory Content Server Enterprise
Access URL Web Services Services Web Member Service Library Content
port, usually Services port , port, usually Services port,
8080 for Tomcat usually 8080 8080 for Tomcat usually 8080 for
for Tomcat Tomcat
[a]
• Consumer Security: SAP Authentication Assertion Ticket

• Message ID Protocol: Suppress ID Transfer
22.2.3.5 Using the assertion based authentication mechanism

SAP recommend that you use value 3 for the login/create_sso2_ticket system
parameter. However, with this value, Extended ECM for SAP Solutions needs some
special configuration steps.
Notes
• To use the assertion based authentication, Extended ECM for SAP Solutions
has to use RFC destinations managed by SM59 transaction. In these RFC
destinations you can maintain the assertion ticket parameters.
• The assertion based authentification mechanism does not work in the

Internet Explorer compatibility mode.
For using the assertion based authentication mechanism you have to modify
configuration by:
• Download and nstall the predefined WSDL/OTDS web service, delivered in

wsdl_for_assertion_tickets_level_3.zip
• Configuring additional security settings for RFC destinations

To install the predefined WSDL/OTDS web service
1. In OpenText My Support navigate to DOWNLOADS > Ecosystems > SAP >

Extended ECM for SAP Solutions > Extended ECM for SAP Solutions 21.4 >
WSDL for assertion tickets level 3.
2. Download wsdl_for_assertion_tickets_level_3.zip.
3. To install the predefined WSDL/OTDS web service, unpack the Zip file and
click on wsdl_for_assertion_tickets_level_3.
To create and configure the WSDL/OTDS web service for using the assertion
based authentication mechanism:
1. Download the web service WSDL from your installation, for example, from
http[s]://[host]:[port]/otsapxecm/services/ECMLink?wsdl.
2. Open this WSDL file in an editor and add the following policy definition to the
definition section:
In the above picture, the highlighted section <wsp1_2> is collapsed.

Add your custom value for SAPClient and SID. Check what kind of prefix is
assigned in the WSDL to the highlighted namespace. Use the same namespace
for your policy definition.
For the OTDS web service, change the WSDL to use http[s]://[host]:
[port]/ot-authws/services/Authentication as service location.
<wsp1_2:UsingPolicy required="true"/>
<wsp1_2:Policy wsu:Id="BN__PLCY_ECMLink">
<wsp1_2:ExactlyOne>
<wsp1_2:All>
<sapattahnd:Enabled xmlns:sapattahnd="http://www.sap.com/710/
features/attachment/">false</sapattahnd:Enabled>
<saptrnbnd:OptimizedMimeSerialization xmlns:saptrnbnd="http://
schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"
wsp1_2:Optional="true"/>
<wsaw:UsingAddressing xmlns:wsaw="http://www.w3.org/2006/05/
addressing/wsdl" wsp1_2:Optional="true"/>
<wsp1_2:All xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/
policy">
<sp:TransportBinding xmlns:sp="http://docs.oasis-open.org/ws-
sx/ws-securitypolicy/200702" xmlns:sapsp="http://www.sap.com/webas/630/soap/
features/security/policy" xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-trust/200512" xmlns:wsu="http://
schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsx="http://schemas.xmlsoap.org/ws/
2004/09/mex">
<wsp1_2:Policy>
<sp:TransportToken>
<wsp1_2:Policy>
<sp:HttpsToken>
<wsp1_2:Policy>

<sapsp:HTTPSSO2 SAPClient="999"
SID="ABC"/>
</wsp1_2:Policy>
</sp:HttpsToken>
</wsp1_2:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp1_2:Policy>
<sp:Basic128Rsa15/>
</wsp1_2:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp1_2:Policy>
<sp:Strict/>
</wsp1_2:Policy>
</sp:Layout>
</wsp1_2:Policy>
</sp:TransportBinding>
</wsp1_2:All>
</wsp1_2:All>
<wsp1_2:All>
<sapattahnd:Enabled xmlns:sapattahnd="http://www.sap.com/710/
features/attachment/">false</sapattahnd:Enabled>
<saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/
2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/
features/transportbinding/" wsp1_2:Optional="true"/>
<wsaw:UsingAddressing xmlns:wsaw="http://www.w3.org/2006/05/
addressing/wsdl" wsp1_2:Optional="true"/>
<wsp1_2:All xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/
policy">
<sp:TransportBinding xmlns:sp="http://docs.oasis-open.org/ws-
sx/ws-securitypolicy/200702" xmlns:sapsp="http://www.sap.com/webas/630/soap/
features/security/policy" xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-trust/200512" xmlns:wsu="http://
schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsx="http://schemas.xmlsoap.org/ws/
2004/09/mex">
<wsp1_2:Policy>
<sp:TransportToken>
<wsp1_2:Policy>
<sp:HttpsToken>
<wsp1_2:Policy>
<sapsp:HTTPSSO2 SAPClient="999"
SID="ABC"/>
</wsp1_2:Policy>
</sp:HttpsToken>
</wsp1_2:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp1_2:Policy>
<sp:Basic128Rsa15/>
</wsp1_2:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp1_2:Policy>
<sp:Strict/>
</wsp1_2:Policy>
</sp:Layout>
</wsp1_2:Policy>
</sp:TransportBinding>
</wsp1_2:All>
</wsp1_2:All>
</wsp1_2:ExactlyOne>
</wsp1_2:Policy>



<wsp1_2:Policy>
<wsp1_2:PolicyReference URI="#BN__PLCY_ECMLink"/>
</wsp1_2:Policy>


3. Link the binding with the policy definition and save the file.
4. Upload the modified WSDL definition and create a logical port based on this
definition. 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
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
5. Repeat the above steps for each Extended ECM web service in use.
6. Maintain the environment parameters for OTDS:

• SAPSYSTEMCLIENT: <your SAP Client ID>

• SAPSYSTEMNAME: <your SAP system name>
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 <your SAP Client ID>, and in the Client field enter
<your SAP Client ID>.
Work-around for complex web service definitions

If the WSDL contains XSD imports, which cascade to multiple levels, you might not
be able to import them using the SOAMANAGER. The WSDL either needs to be
flattened or, as a work-around, the web service must be configured with an old
approach. However, this is obsolete but still possible in the SAP system.
Note: If you chose this configuration path, the diagnostic report might display
a warning for the particular web service. You can ignore that.
To use the work-around method for complex web service definitions:
1. Use the SM59 transaction and create a custom destination of type G HTTP
Connection to External Server.
2. Select the Send assertion ticket for dedicated target system.

Set the client name and the system ID. Use the same as for the OTDS
configuration.
3. Use the (obsolete) Lpconfig transaction to create logical ports.
4. Define the logical port.
5. Maintain the HTTP destination.
6. Activate the configuration.
7. Maintain the logical port name in the Extended ECM connection definition. For
more information, see “Maintaining Extended ECM connections” on page 152.

22.2.4 Configuring the Service Provider Interface service

For communication from Content Server to the SAP system a web service is used.
You configure the web service on SAP side. Content Server uses this web service to
connect to the SAP system.
Note: This activity is required to connect the SAP system as business

application in Content Server. For more information, see “Connecting SAP as
the business application” on page 159.
Infrastructure structure and open it.
2. For the Configure SPI Service activity, click Execute.

The SOA Manager opens in a web browser.
Note: In the SOA Manager, the option names differ from release to
release. The following steps cover some of the possible option names. For
detailed information, see the SAP documentation.
3. Click the Business Administration, Business Administrator or Service

Administration tab.
4. Click the Web Service Administration or Single Service Configuration link to

manage the web service.
5. Search for the /OTX/ECMLINKSERVICE web service to display details.
6. Select the web service and click Apply Selection.
7. Click the Configurations tab.
8. To create a service and an end point, click Create Service.
9. Enter the following:
• New Service Name or Web Service Name: Enter a name of your web
service, for example ECMLinkSPIService.
• Description: Enter a description for your web service.
• New Binding Name: Enter a binding of your web service, for example
BasicAuthBinding.
Note: The information you enter here will be part of the address used to
access the SAP system from Content Server:
https://<common url:port/sap/bc/srt/xip/otx/ecmlinkservice/<Client>/
<WebServiceName>/<BindingName>
Example:
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 “Importing root certificates for
Secure Sockets Layer (SSL) connections” on page 157.
– Transport Protocol or Communication Security: Select HTTP Using
Secure SSL Connection.
– HTTP Authentication or Transport Channel Authentication: Select
User ID/Password.
13. Click Save.
14. Go back to SAP GUI and start the SICF transaction.
15. In the Maintain Service dialog open the sap/bc/srt/xip/otx/

ecmlinkservice/<Client>/<WebServiceName>, for example sap/bc/srt/
xip/otx/ecmlinkservice/800/ecmlinkspiservice node and check if the
<BindingName> (for example basicauthbinding) service is activated. If not,
activate it.
22.2.5 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 152.
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:
– Logon procedure: Select No Logon.

– Send SAP Logon Ticket: Need not to be set here. If it is needed with SSO
it is set automatically.
– 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.
– Compressed Response: Select Yes.
– HTTP Cookies: Select No.

22.2.6 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.
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 “Creating logical ports in the SAP system” on page 130.
OpenText Directory
• Logical Destination: Enter the logical destination as defined for it. For
more information, see “Creating logical destinations” on page 150.
• 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, see “Improving data security for
impersonation connections” on page 155.
• 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 150.
• Path: OTCS/cs.exe
Note: If this path has Integrated Windows Authentication (IWA)

enabled, there are limitations for the following features: thumbnail
view in the Business Content window, license measurement,
Content Server search from SAP, UI Widget integration. These

functions ask for authentication if Integrated Windows

Authentication is exclusively enabled as authentication method.
Workarounds are:
– Thumbnail preview: Disable the preview in IMG at Extended

ECM > Business Content Window > Business Content Window
Settings. Create a new entry with WSP_THUMBNAIL_OFF as setting
name and TRUE as value.
– License Report and search: Use a new RFC destination with a
mapping to Content Server without IWA.
– UI Widget integration: Use the native Business Content window
UI.
Alternative authentication configurations are:
– Enable the OTDS SSO authentication and disable the IIS IWA
configuration. (recommended)
– If you need IIS IWA for all others users except SAP users, and
there is no way to use OTDS SSO, you can create a second
mapping in IIS that does not have IIS IWA, and configure that in
the Extended ECM connection settings.
• Support Directory defines the directory on Content Server where the
files for the Content Server widgets are stored, for example img. This is
only relevant if you want to use widgets and meet all prerequisites. For
more information, see Section 9 “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.
RFC Impersonation uses a web service for SSO: if you want to restrict this
web service to redirect to a certain Content Server, you can maintain a
whitelist. For more information, see “Improving data security for
impersonation connections” on page 155.
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.
22.2.7 Improving data security for impersonation connections

If you are using impersonation with web-based SSO to call embedded Content
Server windows in SAP GUI, you can explicitly create a list of Content Servers that
are allowed for this kind of connection. This follows the SAP whitelist concept. For
more information, see the SAP Help Portal (http://help.sap.com/saphelp_nw73ehp1/
helpdata/en/ee/984daaa3834eeaa77d5edb822570f6/frameset.htm).
To create a whitelist for allowed impersonation connections:
1. Use transaction SM30 to open table /OTX/RM_THTWHITE.
2. Create an entry for each Content Server that is allowed to connect to your SAP
system:
Use Redirect URL /sap/public/otx_rmuic_sso as Whitelist Entry Type.
Provide the protocol, host name, port and an URL template.
Notes
• You can use the * wildcard in these fields.

• You must add the wildcard at the end of the URL Template to cover all
URLs based on that template.
Example:
• Protocol of URL: HTTP

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

To use SSL for the communication between Content Server and the SAP system, you
must import the Content Server SSL certificate into the SAP system.
Prerequisite
• You have configured the web servers for HTTPS.

• You have exported the certificate from Content Server in the Base64 format.
To import the certificate:
1. In the SAP system, start the TRUST transaction.
2. Open the SSL client SSL Client (Anonymous) node.
3. On the Certificate menu, click Import.

4. Enter the file path, and then select Base64.

5. Click the Add to Certificate List button and save your settings.
6. Repeat the steps for the SSL client SSL Client (Standard) node.

Chapter 23
Performing system administration tasks in Content
Server
After the actual installation of the module, you have to perform post-installation
tasks in Content Server.
23.1 Enabling Business Workspaces

Business Workspaces and its underlying module Template Workspaces have been
installed with the Content Server package. However, you must enable it before you
can configure and use it. Before you enable Business Workspaces and Template
Workspaces, make sure your license plan includes both modules. Once you enabled
it, you cannot disable it anymore.
Note: You must restart Content Server after your enabled Business
Workspaces and Template Workspaces.
To enable the modules:
1. On the Content Server Administration page, click Business Workspaces >

Enable Business Workspaces.
2. Click Enable Template Workspaces and Business Workspaces features.
3. Enter your name as a signature and to confirm thereby that you’ve read the
terms of usage and have proper licensing in place.
4. Click Save Changes.
5. Restart Content Server.
23.2 Importing root certificates for Secure Sockets

Layer (SSL) connections
To secure communication between Content Server and the business application,
OpenText strongly recommends that you use the Secure Sockets Layer (SSL)
protocol. Install the certificates on the business application, the Tomcat server
running the Extended ECM Web Services, and in the Extended ECM for SAP
Solutions keystore. The Extended ECM for SAP Solutions keystore is located in
<Opentext home>/config/ecmlink-spi.cacerts. It contains the common root
certificates known from Java runtime.
Notes
• If you want to use self-signed certificates, you must import them into the
following keystores:

Chapter 23 Performing system administration tasks in Content Server
– Extended ECM keystore (<Opentext home>\config\ecmlink-spi.

cacerts)
– Content Server keystore (<Opentext home>\jre\lib\security\cacerts)

– JRE keystore for the Tomcat server running the Extended ECM Web
Services
For more information about keystores in Tomcat, see the Tomcat

documentation (http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html).
• The certificate should be in Base64 format.
The following procedure describes how to import a certificate to the Extended ECM
keystore ecmlink-spi.cacerts.
To import a certificate:
1. Open a command prompt window.
2. To list the certificates, run the following command:

keytool ‑list ‑keystore <Opentext home>\config\ecmlink-spi.cacerts ‑storepass
changeit
3. The key store password is changeit. To change the password, enter:

keytool ‑storepasswd changeit ‑new <KeystorePassphrase> ‑keystore <Opentext home>
\config\ecmlink-spi.cacerts
4. To add a certificate, run the following command:

<Java home>\bin\keytool ‑import
‑alias <CertificateAlias>
‑file <CertificateFile>
‑keystore <Keystore>
‑storepass <KeystorePassphrase>
Example:
C:\OPENTEXT\jre\bin\keytool
‑import
‑alias mycertificate
‑file c:\temp\mycertificate.cer
‑keystore c:\opentext\config\ecmlink-spi.cacerts
‑storepass mypassword

23.3. Connecting SAP as the business application
23.3 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 C/4HANA Sales Cloud and SAP C/4HANA
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>.
Note: You cannot change the name later.
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 23-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 “Importing root certificates for Secure
Sockets Layer (SSL) connections” on page 157.
Schema Version
Select the interface version.
User Name
Enter the user that is used to access business object type information in the
business application.
Notes
• 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 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.

23.4. Configuring the storage provider
For more information, see Section 3.5 “Selecting a template, classification

or category based on business properties” in OpenText Extended ECM for
SAP Solutions - Customizing Guide (ERLK-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 149.
System Name
Enter localized names for the business application if required.
23.4 Configuring the storage provider

The storage provider configuration connects the logical archives of Archive Center
with Content Server. Create a storage provider configuration for each logical
archive.
To configure the storage provider:
1. Switch to the Content Server Administration in a browser: ../OTCS/cs.exe?

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

Archive Storage Provider.
3. In the Archive Server field, enter the name of the Archive Center host.
5. Click Upload Certificate to Archive Server. Archive Storage Provider uploads

its certificate to Archive Center automatically.
6. Click OK.

23.5 Creating an Enterprise Library application

Important
From version 16.2.10 on, Extended ECM for SAP Solutions does not require
Enterprise Library anymore for new installations. In this case, see “Setting
permissions for root folders in Content Server” on page 165.
To declare records, Extended ECM for SAP Solutions needs an Enterprise Library
application. ArchiveLink documents and print lists declared as records by the SAP
system can either be stored in the Enterprise Workspace or in this application area.
To restrict access to these documents, you must set additional permissions on the
application level.
To create an application:
1. In the OpenText Administration Client, navigate within the Enterprise Library
Services to the Applications entry.
2. In the Actions pane, select the New Application entry.
3. Enter the required parameters for the application.
a. Select Delete notifications.

This is required for the /OTX/RM_REMOVE_LINKS report which deletes
orphaned links on Content Server. For more information about the report,

23.5. Creating an Enterprise Library application
see Section 24.8 “SAP: Scheduling jobs for removing deleted records” in
OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
b. In the Password field, you define an application password that is used for
“Maintaining Extended ECM connections” on page 152.
Note: OpenText recommends that the application name is identical to

the respective SAP system ID.
c. Click Next.
4. Select the required audit interests that correspond to your audit scheme, and
then click Finish to complete the assistant.
The new application is now displayed in the list of applications.
To set permissions for an application:
1. On the Content Server Administration page, click Enterprise Library

Administration > Open the Enterprise Library Volumes.
2. Click the button of the application folder with the application ID you just
created, and then select the Permissions.

In the Permissions page, the following permissions are set as a default:
• Full access rights to the volume for the user who created the application (in
our case the user is otadmin@otds.admin).
• Only See and See Contents access rights for the groups DefaultGroup and
Public Access.
3. Add users and groups that must have access to this volume.
4. Grant full access to those users and groups that have to declare records within
SAP.
Note: If you choose to store records in Enterprise Workspace folders, set

the permissions 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

23.6. Setting permissions for root folders in Content Server
23.6 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.
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
23.7 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 Solutions, you can
create a Content Server user with the same user name as in SAP. Alternatively, you
can have one Content Server user for many SAP users.
For test purposes or a small number of users, this can be done manually in OpenText
Directory Services. For a large number of SAP users this can achieved using an
Active Directory server that provides users for both the SAP system and for Content
Server via Directory Services.

In your SAP system, the users are either provided and maintained in your SAP
system or in an external identity provider. Directory Services can synchronize with
your identity provider to pull user and group information from your identity
provider automatically.
23.7.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.
• To declare records, users must have at least Add Items permission.

23.8. Granting object and usage privileges
Example 23-2: Authorization for records in Content Server
Records should be created for HR and Finance department; you could now
separate the records either by storing them in different locations or by
classifying them differently. To use the classification approach, create a Finance
Content Server group and add all the users that should have access to the
Finance records; then create a similar HR group. Assign the Finance group
access rights to the Finance classification and the HR group to the HR
classification.
23.8 Granting object and usage privileges

23.8.1 Granting permissions and privileges for business
administrators
The installation created the Business Administrators user group, which has all
necessary usage privileges for business administrators and access to the Business
Workspaces volume. You must now also grant permissions for some of the
configuration volumes, object privileges, and the Warehouse usage privilege.
Note: Business administrators now have default access to the Business

Workspaces volume and the Extended ECM volume without manual
configuration.
To grant permissions to configuration nodes:
1. Log on as system administrator.

2. From the function menu of a configuration volume, select Permissions.
3. In the Assigned Access area, click Grant Access.
4. Add the Business Administrators group and grant the required permissions up
to and including the Delete permission. Make sure the Delete permission is
only for sub-items not for the root folder, for example for the categories but nor
for the Categories volume.
5. Select Apply to this Item & Sub-Items and click Update.
6. Apply this to the following configuration nodes:
• Enterprise workspace to create the root folder for business workspaces

• Categories volume
• Classifications volume
• Facets volume
• Outlook Add-in Configurations
• Saved Queries Volume
• Document Templates volume
• LiveReports volume
To grant object privileges:
1. On the Content Server Administration page, click Core System - Feature

Configuration > Object Privileges.
2. Add the Business Administrators group to the following object privileges:
• ActiveView
• Appearance
• Category
• Category Folder
• Classification
• Custom View
• LiveReports if you want to configure widgets, which use LiveReports
• WebReports if you want to configure widgets, which use WebReports
• License metering if you want to run the License report.
To grant the transport warehouse usage privilege:
1. On the Content Server Administration page, click Core System - Feature

Configuration > Usage Privileges.
2. Add the Business Administrators group to the Warehouse Administration -

Warehouse Manager usage privilege. This usage privilege is optional.

23.8. Granting object and usage privileges
23.8.2 Granting usage privileges for business workspaces

The following Content Server privileges are related to Business Workspaces and
Extended ECM:
• Business Administration:
Content Server Document Templates
Business Workspaces
Extended ECM
Extended ECM for SAP
• Move Business Workspaces: Only users with this privilege can move a business
workspace to a different folder.
• Edit attributes relevant for group mapping: This privilege is relevant if you use
group replacement in the template. It restricts the editing of attributes that are
used to define the groups that have access to a business workspace. For more
information, see Section 3.16.1.8 “Defining group replacement settings” in
• Regenerate Reference Attribute: This privilege allows to generate a new
reference number. This may be necessary if the reference number contains
attributes and these attributes have changed. For more information, see Section
3.11.7 “Using the Reference attribute” in OpenText Extended ECM for SAP
• Change/Remove Workspace Reference: This privilege allows users to change
the business object of a business workspace, or remove the business object from
the workspace.
• Access Business Workspaces (<Product Name>): This privilege is provided by
each installed Extended ECM product. It necessary to access a business
workspace. It is also the basis for license measurement. .
• Display Business Objects: This privilege allows users to display the data of a
business object in the business application.
• Add/Edit/Remove Business Objects: This privilege allows users to add business
objects to Content Server items.
To administer the privileges:
1. On the Content Server Administration page, click Core System – Feature

Configuration > Usage Privileges.
2. Find the Business Workspaces and Extended ECM usage types and configure
them according to your requirements.
For more information about permissions and privileges in Content Server, see
Section 4.3 “Permissions on Content Server” in OpenText Extended ECM for SAP
Solutions - User Management and Access Control Scenarios (ERLK-CUM).

23.8.3 Granting object and usage privileges for business

attachments
The following Content Server privileges are related to business attachments:
• Add/Edit/Remove Business Objects

Only users with this privilege can add business objects as a link to a Content
Server item, edit the link or remove it.
• Display Business Objects
This restriction applies only to SAP business objects that are linked by adding
them to a Content Server item. It does not restrict the access to an SAP business
object from the corresponding business workspace.
To administer the privileges:

Configuration > Usage and Transaction Privileges.
2. Set the object and usage privileges as required.
For more information about permissions and privileges on Content Server, see
Section 4.3 “Permissions on Content Server” in OpenText Extended ECM for SAP
Solutions - User Management and Access Control Scenarios (ERLK-CUM).
23.9 Configuring how users can copy or move

business workspaces
You can configure if and how users can copy or move business workspaces.
Per workspace You can inhibit copying for each workspace type.
type
Usage You can grant the Move Business Workspaces usage privilege to a group of users.
Privileges You need administrator permissions for this.
Classification As default, users can copy or move business workspaces only to folders, which have
independent the same classification as their original folder. However, you can disable this check
and allow users to copy or move business workspaces wherever they want to. This
is a system-wide setting and you need administrator permissions for it.
To allow to copy or move a business workspace anywhere:

Configure Business Workspaces.
2. Select Allow Move and Copy.

23.10. Configuring multilingual metadata languages
23.10 Configuring multilingual metadata languages

For each language that you configured in the business application, you must
configure a language in Content Server.
Note: System administrator rights are required for this task. Please ask
OpenText Professional Services for assistance.
To configure multilingual metadata languages:

Configuration > Multilingual Metadata.
2. Add an entry for each language that you want to support, and enable it.
Important
Select languages whose Language Code matches the value of the Lng ISO
field in the SAP system, for example en.
You can have more languages in Content Server than you have
customized in the business application, but you must not have less.
Figure 23-1: Configuring multilingual metadata languages

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

23.12. Preparing the Content Server search for users
23.12 Preparing the Content Server search for users

23.12.1 Creating a search slice for business workspaces
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>.
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.

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

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.

23.12. Preparing the Content Server search for users
5. Select Run in test mode without indexing to see how many documents need re-
indexing.
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.

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.
23.13 Smart View: Creating a perspective with

Perspective Manager
Perspectives control how users see the layout of a business workspace in Content
Server Smart View. You design and configure a perspective in Perspective Manager,
a tool that walks you through the creation of a perspective and translates it into
appropriate coding.
With Business Workspaces, Perspective Manager uses a reduced set of options,

focusing on 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 Team and Metadata widget, and a Documents tab with the
Node Browsing Table widget.
Important
• This chapter only covers perspectives for business workspaces. For more
information about the full functionality of Perspective Manager and
perspectives, see the online help of Perspective Manager.

23.13. Smart View: Creating a perspective with Perspective Manager
• Changes in perspectives take effect immediately. If you need testing, create

the perspective on a test system first.
Some widget parameters support multilingual text. You recognize them by the globe
icon . When you click into one such box, a pop-up opens with text boxes for each
installed language.
Note: In each business workspace, you can have only one Node Browsing
Table widget, regardless of how many tabs you have.
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, on the General tab, click Create new, and then
enter a title for the perspective.
4. On the Rules tab, you create logical rules, which control when the perspective is
used.
5. On the Configure tab, you design the perspective of the workspace type.
• The widget library pane on the left contains widgets from installed modules,
one of which being Business Workspaces.
• The working area in the middle is where you place the widgets.
• The options pane on the right shows configuration 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. When you are done, click Create.
7. To edit a perspective, open it in Perspective Manager and make the required

changes. Perspectives for Business Workspaces are stored in the following
location: Perspectives volume > Business Workspaces > <Folder named after the
workspace type with workspace type ID> . The folder name changes when you
change the workspace type name, the ID remains the same.
Note: When you transport perspectives using the Transport Warehouse, you
must follow a certain order to keep dependencies. For more information, see
Section 6.4 “Transporting the configuration” in OpenText Business Workspaces -
Configuration Guide (CSCWS-CGD).

23.13.1 Migrating perspectives

Perspectives for business workspaces, which were created with versions 16.2.9 or
earlier, are “Container” perspectives and they determine their respective workspace
type with a rule. Starting with version 16.2.10, this behavior has changed:
Perspectives can now be “Workspace” perspectives. The workspace type is set
automatically when you start Perspective Manager from the Workspace Type
configuration page.
With version 20.2, all ActiveView perspectives use a new “Perspectives” node type
and must be converted, therefore all rule-based workspace perspectives must be
manually migrated to type-based perspectives.
Important
If you have more than one perspective for the same workspace type, you must
follow a certain order for the conversion of these perspectives.
To convert rule-based perspectives to type-based perspectives:
1. Check for multiple perspectives for the same workspace type:
a. On the global menu, click Business Workspaces > Perspectives.

b. Sort the list of Business Workspaces perspective by size to see all
workspace type folders with multiple perspectives in it.
2. Note the order of these perspectives:
a. On the Content Server Administration page, select ActiveView

Administration > Manage Global Perspectives.
b. In the Container Perspectives section, search for those perspective with the
same workspace type ID.
c. Take a note of the order in which these perspectives are listed on the Global
Perspectives page. You must follow this order when you convert these
perspectives.
3. On the Content Server Administration page, select ActiveView Administration

> Open the Perspective Manager.
4. Open the workspace perspective that you want to convert, click Edit
Perspective and convert it. Stick to the order that you noted in Step 2.c.
a. On the General tab, click Edit existing and select the perspective you want
to migrate.
b. As Type, select Workspace.
c. Select the corresponding workspace type. If you are unsure, which
workspace was associated to this perspective, check the rule in the Rules
tab.
d. On the Rules tab, delete the rule with the workspace type.
e. Click Update.

For more information, see the online help for Perspective Manager.
23.13.2 Header widget

The Header widget displays metadata like the name of the business workspace and
important attributes. Metadata is taken dynamically from category attributes, node
properties, and business properties. You can also add static text, line breaks, tabs,
and spaces.
You can also embed another widget in the Header widget, currently only the
Activity Feed widget.
Workspace Properties
Workspace properties are displayed in the left part of the Header widget in the
following top-down order, with the font becoming smaller. You can use the
suggested properties, add others, and combine attributes and properties with
text.
Property Description
Title Name of the business workspace, prefilled
with the {name} node property.
Type Name of the workspace type, prefilled
with the {business_properties.
workspace_type_name} business
property.
Description Description of the business workspace,
prefilled with the {description} node
property.
• Business properties must be configured with the business_properties

prefix, for example {business_properties.workspace_type_name}.
– {business_properties.workspace_type_name}: Name of workspace

type.
– {business_properties.workspace_type_id}: ID of the workspace
type, useful for testing and preparing perspectives.
• Node properties require no prefix, for example {name}.
– {name}: Workspace name.

– {description}: The workspace node description.
– {type_name}: Name of the Content Server item type: Business
Workspace.
– {create_date}: Date when business workspace was created, formatted
according to the current formatting rules.
– {create_user_id}: Name of the user who created the business
workspace, formatted to the user's readable display name.

– {modify_date}: Date when the business workspace was modified.

– {modify_user_id}: Name of the user who modified the business
workspace, formatted to the user's readable display name.
– {owner_group_id}: Name of the group the workspace owner belongs to.
– {owner_user_id}: Name of the workspace owner, formatted to the user's
readable display name.
• Category attributes
Click Add Attribute to Field and select attributes from the categories that
contain information for this business workspace. You cannot use attribute
sets for this. Only text attributes are allowed.
Widget
You can embed another widget in the header widget. It depends on your
system, which widgets are available.
Embed Widget Select one of the available widgets to
embed it into the header widget. It is
displayed in the right half of the header
widget. Currently available is the Activity
Feed widget, which displays all activities
in relation to this business workspace and
its related child workspaces. You see
comments or recently added documents.
If you want to use the Activity Feed
widget, you must enable Content Server
Pulse and, optionally, create activity
manager objects. For more information, see
Section 5.7 “Creating an activity manager
object for the Activity Feed” in OpenText
Business Workspaces - Configuration Guide
(CSCWS-CGD).
Note: The Extended ECM Platform

Header Widget does not support
non-text attributes like, for example,
Booleans, sets, or users.

23.13.3 Related Workspaces widget

The Related Workspaces widget displays business workspaces that are related to the
currently opened business workspace. You must configure the widget in both
collapsed and expanded view. You can display business workspaces that are in a
parent relationship or in a child relationship, and you can have more than one
Related Workspaces widget in a perspective. Relations must be configured in
Content Server.
General
Title Title of the widget, typically the
workspace type name in plain text.
Workspace type Workspace type of the related workspaces.
Relation type Child or Parent.
Collapsed view
Message for empty result Custom message if no business
workspaces of this type are available.
Preview pane The preview pane is a window that opens
when you hover with the mouse over a
related workspace in the widget. The
preview pane contains additional
information as well as team members of
this business workspace.
• Preview title – Title of the preview
pane, for example the workspace type.
The title is displayed in small font
above the display name of the related
workspace.
• Message for empty metadata – Custom
message if there is no metadata to
display.
• Name of role – Name of the role whose
members are displayed in the preview.
• Message for empty role – Custom
message if there are no roles or team
members to display.
Message that is displayed if the
specified role has no members. The
default text is No role members
assigned.

Metadata in preview pane The preview pane uses data from category
attributes. You select a category or single
attributes. To group attributes, enter a
group name and then select the categories
and attributes. Leave the group name
empty to add a category or attribute
without a group. Drag attributes or groups
to change the order.
• Group name – Name of a group of
attributes or categories
• Category or attribute – Category or
single attributes. You can use the
following data sources: A single
attribute or a complete category with
all its attributes.
Order by Orders the list of related workspaces by a
custom column and defines the sort
direction. The default sorting is ascending
by the name of the business workspace.
If you have not selected a custom column
in the Order by option, the workspaces are
ordered by the custom column configured
in Related workspace title. And in this
case, you can only use custom columns
that are configured for ordering. If you
selected a custom column that is not
configured for ordering, an error message
is displayed when the widget is loaded.
For more information about configuration
of custom columns, see Section 5.6
“Creating custom columns for Content
Server Smart View search and widgets” in
OpenText Business Workspaces -
If you want to have the workspaces sorted
by another order than by name, you must
explicitly define the column and the sort
order in the order by section.
• Default is an order ascending by name.
• Sort ascending by the column that you
want to display as Title: Select that
column as Title, do not specify
anything in the Order by field.
• Sort descending by the column that
you want to display as widget title:
select that column as Title, additionally
select this column in the Order by field,
and select the sort order Desc.

Related workspace title Name of the related workspace. You can
use the following:
Variables: {name}. It uses the name of the
business workspace, which may already be
assembled from several attributes.
{modify_date}. For this, the custom
column for Workspace Modify Date
must be configured and have the Used for
Sorting and Filtering option enabled.
Custom columns if they have the Used for
Related workspaces description Description of the related workspace. You
can use the following:
Variables: {name}, {description},
{type_name}, {modify_date},
{create_date}
System Default Columns: {id}, {size},
or {type}
Custom columns if they have the Used for
Metadata fields Additional fields to display metadata in
the widget. Enter a label and the value,
which can be a custom column or one of
the following variables: {name},
{description}, {type_name},
{modify_date}, {create_date}. The
{name} variable uses the name of the
To format a custom column to be
displayed in currency format,
add :currency within in the brackets, for
example: {wnf_att_fl14_
5:currency}. With this format, zeros are
displayed and thousands separators are
added.
Expanded view
Order by Orders the list of workspaces by a custom
column and defines the sort direction.

Custom columns Custom columns to be displayed in the
expanded view. Select a custom column,
and then click Add to array. You can drag
the columns to change the order.
You can enable sorting by date in the
Related Workspaces widget. For this, you
create a custom column for the Workspace
Modify Date data source and configure it
to be sortable and used for sorting and
filtering. No further configuration is
required in the widget. For more
information, see Section 5.6 “Creating
custom columns for Content Server Smart
View search and widgets” in OpenText
Business Workspaces - Configuration Guide
(CSCWS-CGD).
23.13.4 Team widget

The Team widget displays team members as well as roles that have no members.
Title Title of the Team widget. Default is Team.
Title Title of the Team widget. Default is Team.
23.13.5 Metadata widget

The Metadata widget displays attributes of the business workspace.
Title Title of the Metadata widget. Default is
Metadata.
Hide empty fields Hide metadata fields that have no value.
Default is False.

Metadata The Metadata widget uses data from
category attributes. You select a category or
single attributes. To group attributes, enter a
group name and then select the categories
and attributes. Leave the group name empty
to add a category or attribute without a
group. Drag attributes or groups to change
the order.
attributes or categories. You can use this
option to visually group attributes.
single attributes. To add an attribute,
select the category and then select the
attributes that you want to display.
Note: Metadata groups in the

Related Workspaces widget must
not contain complete attribute sets.
However, you can select single
attributes from an attribute set.
Attribute sets with multiple rows
are displayed as a table in the
Metadata widget. Make sure that
the table width does not exceed the
width of the widget.
23.13.6 Workspaces widget

The Workspaces widget displays workspaces of a certain type. Workspaces widgets
are typically used on a Home page. You can have more than one Workspaces
widget.
General
Title Title of the Workspaces widget, typically
the type of business workspaces listed
here. Default is My workspaces.
Workspace type Type of business workspaces that you
want to display.

Collapsed view
Message for empty result Custom message if no business
workspaces of this type are available.
Expanded view
Order by Orders the list of workspaces by a custom
Custom columns Custom columns to be displayed in the
expanded view. Select a custom column,
and then click Add to array. You can drag
the columns to change the order.
You can enable sorting by date in the
Workspaces widget. For this, you create a
custom column for the Workspace Modify
Date data source and configure it to be
sortable and used for sorting and filtering.
No further configuration is required in the
widget. For more information, see Section
5.6 “Creating custom columns for Content
Server Smart View search and widgets” in
OpenText Business Workspaces -
23.13.7 Configuration Volume widget

The Configuration Volume widget provides access to configuration volumes in
Smart View, for example the Document templates volume. The user needs sufficient
access rights to see the widget and make use of it.

23.13.8 Discussion widget

In Perspective Manager, the Discussion widget is displayed as a Communities
widget. The Smart View Discussion widget is intended for a business workspace,
allowing users to ask questions, provide answers to those questions, and search
through previously asked questions and their related answers. This widget stores
data in a Forum object. To include a Discussion widget in a business workspace, the
associated workspace template must include the associated Forum object.
Notes
• The Discussion widget is intended for use in a business workspace.

• Although both Perspective Manager and the Smart View Edit Page tool
allow you to configure the Discussion widget outside of the context of a
business workspace, such use is not supported.
• Keep in mind that this Smart View Discussion widget is associated with a
Classic View forum object, not a Classic View discussion object.
Discussion widget prerequisites
Set notifications
To support the Follow feature in the Discussion widget, you must configure
notifications just as you would for a Forum in Classic View. For information
about how to configure the frequency of notifications if a user chooses to follow
a topic, see Section 1.2 “Configure Notifications” in OpenText Content Server -
Notifications Administration (LLESWBN-H-AGD).
Set eLink
To support the Follow feature in the Discussion widget, you must configure
eLink just as you would for a Forum in Classic View. For information about how
to configure eLink, see Section 1.2 “eLink Settings” in OpenText Content Server -
eLink Administration (LLESELK-H-AGD).
Discussion widget configuration parameters
Parameter Description
Width Choose the size that you want for the Discussion widget.
For the Overview tab of a business workspace, the recommended size is
single width.

Forum object To associate the widget with the Forum object in the business workspace,
leave this parameter empty and the widget will automatically link to the
forum. Typically, the administrator creates a new Forum object in the
business workspace or in the business workspace template.
Notes
• The Forum objects must be available in the root folder of the
business workspace. If the root folder does not include a Forum
object, the Discussion widget will display a message that no
discussion is configured. If you later add a Forum to the root
folder, the Discussion widget will automatically link to it.
• If there is more than one Forum object in the root folder of the
business workspace, the Discussion widget automatically links to
the oldest Forum.
To associate the widget with a Forum object outside of the business

workspace, browse Classic View Content Server to find the appropriate
Forum object.
For information about how to create a Forum, see Section 1.1 “Creating
and Configuring Forums” in OpenText Content Server - Forums (LLESFOR-
H-UGD).
23.13.9 Business Attachments widget

The Business Attachments widget displays documents and other Content Server
items that are attached to a business object. Business attachments usually are not
stored in a business workspace. If not configured otherwise and if the widget is used
in a workspace perspective, the widget displays business attachments for the
business object of the business workspace. You can also display business objects for
other business object.
Users can create a snapshot for all business attachments displayed in the widget.
Snapshots are folders in Content Server, which contain a Generation of the latest
version of each business attachment that is a document. A Generation is a copy of a
document, which is separated from the original document, unlike a version. For
more information, see the Content Server help. The snapshot contains a shortcut to
objects other than documents. The name of the folder starts with a prefix, which you
configure for the widget.
In the expanded view, you see additional information for each business attachment
such as description, location and version.
General
Title Title of the Business Attachments widget.
Default is Business attachments.

Snapshot folder name prefix Prefix that is added to the snapshot folder
when you create a snapshot from this
widget. A snapshot freezes the current
version of all business attachments of the
business object and stores them in a folder.
Business attachment
Business object ID Category attribute that contains the ID of the
business objects for which you want to
display business attachments.
Business object type Category attribute that contains the business
object type.
Business application ID Category attribute that contains the ID of the
business application where the business
object type resides.
If you want to use attribute sets in these fields, you must use the following format:
{categories.<category ID>_<set number>_<attribute ID>}, for example,
{categories.37275_33_1_34}. If the attribute picker does not provide this format,
you must enter it manually.
• Category ID: 37275

• Set: 33
• Line of set: 1
• Attribute ID number: 34
To retrieve the attribute ID, run the following report: <URL of content server>?
func=attributes.dump.
Collapsed view
Message for empty result Custom message if no business attachments
are available.

Order by Orders the list of business attachments by a
column. The default sorting is ascending by
the name of the business attachment.
If you have not selected a column in the

Order by option, the attachments are
ordered by the name. If you selected a
custom column that is not configured for
ordering, an error message is displayed
when the widget is loaded.
Business attachment title Name of the business attachment in the
collapsed view. You can use one of the
following variables: {name},
Business attachment description Description of the business attachment. You
can use one of the following variables:
{name}, {description}, {type_name},
Metadata fields Additional fields to display metadata in the
widget. Enter a label and the value. You can
use one of the following variables: {name},
Expanded view
Order by Orders the list of business attachments by a
Snapshot
Parent folder name Folder in business workspace, where
Snapshots are created.
Snapshot name prefix The name of a snapshot consists of the prefix
and a timestamp.

23.13.10 Dossier widget

The Dossier widget displays all documents in the business workspaces.
Default group by criterion Groups the documents by their creation date
or a classification.
Hide group by criterion dropbox Provides an option for users to hide certain
groups of documents. The default settings
display the dropbox.
Hide metadata Provides an option for users to hide
metadata of documents. The default settings
display the metadata.
Hide empty fields Hide metadata fields that contain no data.
The default settings display empty metadata
fields.
23.13.11 Header widget with business object information

The Header widget of the Extended ECM Platform module contains information
about the business objects and connections to the respective business application.
Note: Do not use multivalue attributes and multi-row set attributes in the
header widget. You can only use text attributes.
Workspace Properties
Title Name of the business workspace, prefilled
with the {name} node property.
Type Name of the workspace type, prefilled with
the {business_properties.
workspace_type_name} business
property.
Description Description of the business workspace,
prefilled with the {description} node
property.
Workspace properties are displayed in the left part of the Header widget in the
following top-down order, with the font becoming smaller. You can use the
suggested properties, add others, and combine attributes and properties with text.
• Business properties must be configured with the business_properties prefix,

for example {business_properties.workspace_type_name}.
– {business_properties.workspace_type_name}: Name of workspace type.

– {business_properties.workspace_type_id}: ID of the workspace type,

useful for testing and preparing perspectives.
• Node properties require no prefix, for example {name}.
– {name}: Workspace name.

– {description}: The workspace node description.
– {type_name}: Name of the Content Server item type: Business Workspace.
– {create_date}: Date when business workspace was created, formatted
according to the current formatting rules.
– {create_user_id}: Name of the user who created the business workspace,
formatted to the user's readable display name.
– {modify_date}: Date when the business workspace was modified.
– {modify_user_id}: Name of the user who modified the business workspace,
formatted to the user's readable display name.
– {owner_group_id}: Name of the group the workspace owner belongs to.
– {owner_user_id}: Name of the workspace owner, formatted to the user's

readable display name.
• Category attributes
Click Add Attribute to Field and select attributes from the categories that
contain information for this business workspace. You cannot use attribute sets for
this. Only text attributes are allowed.
Completeness check settings

You can configure rules that define which document a business workspace must be
contain. The completeness check displays the number of missing documents.
Widget
You can embed another widget in the header widget. It depends on your system,
which widgets are available.

Embed Widget Select one of the available widgets to embed
it into the header widget. It is displayed in
the right half of the header widget. Currently
available is the Activity Feed widget, which
displays all activities in relation to this
business workspace and its related child
workspaces. You see comments or recently
added documents.
If you want to use the Activity Feed widget,

you must enable Content Server Pulse and,
optionally, create activity manager objects.
“Creating an activity manager object for the
Activity Feed” in OpenText Business
Workspaces - Configuration Guide (CSCWS-
CGD).
Metadata settings
Hide metadata Provides an option for users to hide
metadata of documents. The default settings
display the metadata.
Hide empty fields Hide metadata fields that contain no data.
The default settings display empty metadata
fields.
Metadata The Header widget uses data from category
attributes. You select a category or single
attributes. To group attributes, enter a group
name and then select the categories and
attributes. Leave the group name empty to
add a category or attribute without a group.
Drag attributes or groups to change the
order.
You cannot use Boolean attributes in the

Header widget. Use the metadata widget to
display this type of data.
attributes or categories
single attributes. You can use the
following data sources: A single attribute
or a complete category with all its
attributes.
Favorite
You can hide the Favorite button in the Header widget.

23.13.12 Scan barcode widget

Scan the QR code of an object and open the business workspace of that object.
In the configuration of this widget, select one or more business object types. The
business object type must have a configuration for the category attribute, which
contains the barcode value.
For more information, see the following:
• “Scan barcode widget” on page 194

• OpenText Content Server Mobile - Configuration Guide (CSMOB-CGD)
23.14 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:

23.15. Configuring the display of documents in the side-panel
.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
– 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
23.15 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.
23.16 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 Server.
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.
23.17 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 197.

23.17. Providing the online help
23.17.1 Providing the online help on a local help server (Private

Help Server)
The online help for this product 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 product online help on your
organization’s network. After the PHS is installed, you can then configure your
OpenText products 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 products. If the
Private Help Server has already been installed within your organization to
support another OpenText product, you can add additional OpenText
product 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.2 “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 23-1: Help deployment codes
Code Product
ERLK210400-IGD OpenText™ Extended ECM for SAP®
Solutions CE 21.4
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.4 “Set Up the Help Environment” in
OpenText Content Server - Installation Guide (LLESCOR-IGD).

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.
23.18 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.
23.18.1 Creating a Records Management classification

(optional)
If you want to use Records Management, you must create at least one Records
Management classification that can be used in Extended ECM for SAP Solutions. For
more information, see OpenText Classifications - Resource Guide (LLESCLS-GGD).
23.18.2 Importing SAP system categories

Extended ECM for SAP Solutions stores metadata for the declared ArchiveLink
documents in the Categories volume. To import the types, you use a Content Server
transport file, which contains the required SAP system categories.
You find the transport file in the staging directory of the Extended ECM for SAP
Solutions module at the following location: support/transport/System
Categories.zip. The ZIP file contains the transports for the otx.sap.rm.
SystemArchiveLink and the otx.sap.rm.SystemPrintList categories.

23.19. Enabling OpenText Recycle Bin for business workspaces
23.19 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.
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:

Configuration > Recycle Bin.
2. Select Enable Recycle Bin and click Save Changes.
23.20 Checking the appearance of the SAP integration

If you want to integrate the Extended ECM for SAP Solutions 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.18 “Creating unique
names for Content Server items” in OpenText Extended ECM for SAP Solutions -
Note: System administrator rights are required for this task. Contact OpenText
Professional Services for assistance.
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 23-2 or

Figure 23-3.
• Current Status: Enabled

• Header section
• Content Server Components section
• Workspace section

23.20. Checking the appearance of the SAP integration
Figure 23-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>

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

23.21. Allowing users to save Outlook emails to business workspaces
23.21 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).
23.21.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 204, 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.
• 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).
23.21.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 Content Server - Installation Guide (LLESCOR-IGD).
23.21.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.
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.
23.21.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.
23.21.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.
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.

23.21.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 206.
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 207.
23.21.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 209.
You must create one or more regular or Email folders in each business workspace
based on the functionality you plan to configure.
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).
23.21.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 5.15.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 209.
To access the Search Forms folder:
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.
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.

23.21.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 5.17.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. 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, configure 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.
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 211.
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 207.
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 5.17.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.
23.21.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 209.
Example 23-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.
2. Clear all other email saving options.

Example 23-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.
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 23-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.
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 23-6: Requiring users to save emails to a specific regular folder

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.
1. Clear the Allow users to expand workspaces and browse workspace
folders option.
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 23-7: Requiring users to save emails to the workspace root

folder

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).
1. Clear the Allow users to expand workspaces and browse workspace
folders option.
3. Select Save emails to the workspace root folder.

23.21.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 214.
23.21.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 217.
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.

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 jdoe@domain.com as the sender
and jsmith@domain.com as a recipient, all previously stored emails that list
jdoe@domain.com as the sender or jsmith@domain.com as a recipient are
returned in the search results.

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 217.
• For more information about creating regular expressions, see https://
regex101.com/.
23.21.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

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

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.

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

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 the Content Server Administration Online Help.
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.

23.21.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.
23.21.4.6 Examples: Workspace rules

This section provides examples of workspace rules that are used to find business
workspaces.
Example 23-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.

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

business workspaces based on an email’s subject line
• 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 23-10: Using the “Regular Expression” matching method to find

business workspaces based on an email address
• Email Property: Sender

• Matching Method: Regular Expression
• Matching Condition: equipment_[\d]+@server.com
• 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]+@server.com, 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_

1234@server.com, 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.

23.21.4.7 Allowing email fields to be extracted for indexing

To allow the add-in to search for emails based on email properties, you must allow
the OTEmailSenderAddress and OTEmailRecipientAddress email fields to be
extracted for indexing in Content Server.
Note: System administrator rights are required for this task.
To allow email fields to be extracted for indexing:
1. On the Content Server Administration page, click Email Services

Administration > Configure Email Services.
2. In the Extractable Email Fields area, confirm that the following email fields are
selected:
• OTEmailSenderAddress
• OTEmailRecipientAddress
By default, these fields are permitted to be extracted for indexing.
23.21.5 Configuring your environment for SSO authentication

By default, users are prompted to type their Content Server credentials whenever
they browse to the Business Workspaces Outlook add-in. You can optionally set up
single sign-on (SSO) authentication so that users do not need to enter credentials
each time they browse to the add-in.
To set up SSO authentication, you can do either of the following:
• Configure Content Server to use either Microsoft Active Directory Federation

Services (ADFS) authentication through OpenText Directory Services, or
authentication through the local Active Directory domain. For more information,
see OpenText My Support (https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/14273139).
You must then configure security settings in Content Server and add URLs to the
list of trusted sites in Internet Explorer. For more information, see “Configuring
security settings for SSO authentication” on page 224 and “Adding URLs to the
list of trusted sites in Internet Explorer” on page 224.
• Enable SSO authentication in Content Server itself. For more information, see
Section 1.3 “Configuring Integration Settings” in OpenText Content Server -
OpenText Directory Services Integration Administration (LLESDSI-AGD).

23.21.5.1 Configuring security settings for SSO authentication

If you enable single sign-on (SSO) authentication for the add-in, you must also
configure Content Server to allow request handlers to be embedded in external
frames. By default, Content Server prevents request handlers from being embedded
in external frames.
To configure security settings for SSO authentication:
1. On the Content Server Administration page, click Core System – Server

Configuration > Security Parameters.
2. In the Frame Embedding area, clear the Prevent request check box.
For more information about configuring security parameters, see the OpenText
Content Server Administration Online Help.
23.21.6 Adding URLs to the list of trusted sites in Internet

Explorer
In Microsoft Outlook, the Business Workspaces Outlook add-in is displayed in an
embedded Internet Explorer browser. On each client computer that is used to access
the add-in, you must add the URL of your Content Server system to the list of
trusted web sites in Internet Explorer.
If you are configuring SSO authentication in your environment, you must also add
the URLs of all servers that provide access to Content Server (for example, the
OpenText Directory Services server, ADFS server, and any proxy servers).
To add URLs to the list of trusted sites in Internet Explorer:
1. In Internet Explorer, open the Internet Options dialog box.
2. On the Security tab, select the Trusted site zone.
3. Click Sites, add the required URLs to the list of trusted web sites, and then close
the Trusted sites dialog box.
4. Click OK.

23.22. For SAP CRM and SRM: Configuring security settings
23.22 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

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

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

Chapter 24
Performing additional optional tasks in the SAP
system
24.1 Customizing the integration into SAP GUI via

Generic Object Services
24.1.1 Customizing the Generic Object Services (SAP GUI)
New: You can now 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.
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).

Chapter 24 Performing additional optional tasks in the SAP system
To customize General Object Services:
1. Start the SM30 transaction, and then enter SGOSATTR in the Table/View field.
Click Maintain.
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.

24.1. Customizing the integration into SAP GUI via Generic Object Services
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.

24.1.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.
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 a node business attachments
• 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 233.
24.1.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 231.
• 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 232.

Note: The customizing applies only to Content Server Classic View. It does not
apply if the integration widget is used as described in “Enabling the
integration widget in the Business Content window” on page 233.
24.1.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:
Maintain Business Content Window Menu, and then click Execute.
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 237.
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.
24.1.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 on OpenText My Support (https://
knowledge.opentext.com/knowledge/cs.dll/Open/63007681).
Adding custom functionality:
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.
24.1.3.3 Opening a document from the Business Content window context

menu
If you want to have the Open command for documents in the context menu of the
Business Content window in Classic View, you must configure it:
To enable the Open command for documents:
1. On the Content Server Administration page, select Core System - Server

Configuration > Presentation > Configure Document Functions.
2. In the Open section, enable Enabled.
24.1.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.
24.1.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. Optionally, you can also define which theme to use.
Important
If you want to use the integration widget and if you use Content Server on
Microsoft IIS, you must configure detailed errors messages on local and remote
requests. For more information, see “Configuring Microsoft IIS to return
meaningful REST API error messages” on page 234.

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.4 “Creating a business
object declaration in SAP” in OpenText Extended ECM for SAP Solutions -
2. Optional To define the theme, in the IMG, navigate to the Extended ECM >
Business Content Window > Maintain Business Content Window Display
Options, and then click Execute.
a. In the General Settings section, click New Entries.

b. As Setting Name enter WSP_WIDGET_CSS_THEME and as Setting Value enter
the name of the theme, for example belize.
Note: You can now use the new belize theme for the integration
widget integration. However it is currently not recommended for
page view.
3. 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 230.
24.1.5.1 Configuring Microsoft IIS to return meaningful REST API error

messages
Using the default configuration, Microsoft IIS returns a generic error message when
interfaces that are based on the Content Server REST API, such as the Content Server
Smart View, encounter errors. Presenting a more informative error message to users
can aid in troubleshooting any difficulties that they encounter.
Example: With Detailed errors enabled, IIS returns a message similar to An item with the
name <filename.txt> already exists, but if Detailed errors is not enabled, IIS returns
only Error: Bad Request (400).
To enable Content Server to display informative error messages when problems

occur with Content Server REST API interfaces enabled using Microsoft IIS,
OpenText recommends that you enable Detailed Errors in Microsoft IIS.

To enable Detailed Errors in Microsoft IIS:
1. Open Internet Information Services (IIS) Manager.
2. On the left, expand the Content Server website, and click the Content Server
Application.
3. The default Application name is OTCS.
4. In the middle pane, double-click Error Pages.
5. On the right, under Actions, click Edit Feature Settings On the Edit Error
Pages Settings, enable Detailed errors in the Error Responses section, and then
click OK.
24.1.6 Maintaining Content Server subtypes as copy/move

target in the Business Content window
In the Business Content window, users can copy or move documents or other items
from one location to another location in Content Server. However, if you are using
custom Case subtypes and you want to copy or move documents to these custom
Case subtypes you must do the following SAP customizing.
All Content Server items that can be targets for a copy/move operation are
maintained in the /OTX/RM_STWL table. This table is part of Extended ECM for SAP
Solutions and it is filled with a predefined set of subtypes. The new table /OTX/RM_
STWL_C is available to maintain new entries.
Important
As soon as /OTX/RM_STWL_C has one entry, the /OTX/RM_STWL is not used
anymore. If you intend to use /OTX/RM_STWL_C, you must copy the entries of /
OTX/RM_STWL into the custom table.
To maintain custom Case subtypes for copy/move operations:
1. Copy all entries from the /OTX/RM_STWL table to the Subtype column of the /
OTX/RM_STWL_C table.
a. Start transaction SE16, and then open /OTX/RM_STWL.

b. Start transaction SM30, and then open the maintenance view of the /OTX/
RM_STWL_C table.
c. Copy all entries from /OTX/RM_STWL into the clipboard. You can use CTRL
+ Y to copy several rows.
d. Copy the rows into the Subtype column of the /OTX/RM_STWL_C table.
e. Add the connection ID for which the subtype is valid.
2. Add a new entry for your new Case subtype:
• Conn. ID: Connection ID. You find this information in the IMG > OpenText
Extended ECM for SAP Solutions > Infrastructure > Maintain Extended

ECM Connections. For more information, see “Maintaining Extended ECM

connections” on page 152.
• Subtype: ID of the Case subtype. You find this information in the Content
Server Administration page > Template Workspaces Administration >
Administer Case Types. The subtype ID of a Case is a positive integer
between 31350 and 31399. For more information, see the Content Server
online help for this administration page.
24.1.7 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.
24.1.8 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 Content Server viewer

Configuring OpenText Viewing or OpenText Intelligent Viewing (licensed
version) as Content Server viewer:
• If you want to use OpenText Viewing or Intelligent Viewing, enable this viewer
in Content Server Administration. For more information, see Section 2
“Configuring OpenText Viewing” in OpenText Content Server Admin Online Help -
Viewing and Transformation Administration (LLESVWX-H-AGD).
Configuring Web Viewer and OpenText Imaging Windows Viewer as Content

Server viewer:
• If you want to use one of these viewers, define the relevant settings in Content
Server Administration.
• Configure the mime types. For more information, see Section 12.9 “Customizing
MIME types for preview” in OpenText Extended ECM for SAP Solutions -
• Configure the viewer settings in the SAP system. For more information, see
Section 17.2 “Configuration for Web Viewer” in OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).
Configuring Content Suite Viewer as Content Server viewer:
• Content Suite Viewer Administration on the Content Server Administration

page. For more information, see OpenText Content Server Admin Online Help -
Content Suite Viewer Administration (LLESDV-H-AGD).
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 240.
• 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

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.

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.

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

24.1.10 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 227.
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:
• /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.
24.2 Viewing the old configuration in SAP

After the update, the old configuration is still available in the SAP system, but is no
longer evaluated. You can display the information.
To display the old business object type configuration from the SAP system:
1. Start the SM34 transaction.
2. Open the /OTX/RM_WSC_VCZ view cluster.

The screen shows the new reduced configuration.
3. In the command field, enter &show_legacy_on.
4. Navigate to the configuration that you want to retrieve.

24.3. Configuring Single Sign-on for Content Server
For information about the new business object type configuration, see Section
3.17 “Configuring business object types” in OpenText Extended ECM for SAP
5. To display the old field mapping for authorization based on category IDs,
navigate to Workspace Authorization > Field Mapping and enter &show_
legacy_on.
24.3 Configuring Single Sign-on for Content Server

When invoking the Content Server HTML dialogs or the Content Server HTML
search page within the SAP GUI, Extended ECM for SAP Solutions uses a single
sign-on (SSO) process to avoid manual authentication. The following prerequisites
apply for this:
• The redirect service is activated in ABAP.

• No HTTPONLY cookie is used in Content Server.
• Content Server needs to be trusted. For example, in the Security settings of
Microsoft Internet Explorer mark Content Server as trusted site. For this, use the
path http://*.eng-muc-test.otxlab.net/.
Restriction If either SSO cannot be achieved in your server and desktop environment or the
when SSO is option Suppress Sending SAP Logon Ticket is turned on in the connection ID
not enabled
configuration (see “Maintaining Extended ECM connections” on page 152), the
Extended ECM for SAP Solutions functionality is restricted as follows:
• The interactive declare dialog will not allow selecting RSI, categories and cross
references. See Section 6.1.8 “SAP: Assigning a document declaration to a
business object and a document type” in OpenText Extended ECM for SAP
• In some cases the user gets a logon screen when accessing Content Server
functionality.
For the caller dialog, the logon screen appears only once, as long as an SAP GUI
session or the SAP Logon application is open. For the Content Server popup
dialog, a logon is always necessary unless an instance of the Web browser has
been open since the latest logon.
Tip: In order to avoid that the user must log in every time a Content Server
dialog pops up under Microsoft Windows, keep an instance of Microsoft
Internet Explorer open.
In order to avoid that the cookie expires and a logon screen is displayed, you can
switch off cookie expiration in the Content Server security settings.

24.4 Configuring Imaging viewers

Content Suite provides several means to load and view documents in Content
Server:
• OpenText™ Content Suite Viewer

• OpenText Imaging Web Viewer
• OpenText Imaging Windows Viewer
To configure the Content Suite Viewer:
Note: This viewer is not enabled by default. Before you can enable this viewer,
download and install the Brava! Server Components package, which can be
found on My Support. For more information, see OpenText Brava! - Server
Components for Content Suite Viewer Admin Guide (CLBRVW-ICS).
1. On the Content Server Administration page, click Content Suite Viewer

Administration > Configure Content Suite Viewer Settings.
2. Select the Enable Content Suite Viewer option.
3. In the Viewer Server URL section, type the URL to the Brava! Server in the
following format:
http://<computer_name>:<port number>, where <computer_name> is the
name of the computer where the Brava! Server Components package is
installed, and <port number> is the port number specified for the Brava! Server
Components.
To configure Windows Viewer and Web Viewer:
• On the Content Server Administration page, click Editor Administration and

the configuration options of this section.
For more information about the configuration of the viewers, see the respective
online help pages.

Chapter 25
Verifying the installation
25.1 Analyzing the SAP system

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

Chapter 25 Verifying the installation
3. Click Execute.
25.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).

25.1. Analyzing the SAP system
25.1.3 Understanding the Configuration Report

You can use the SAP Configuration Report to summarize your Extended ECM for
SAP Solutions 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.
25.1.4 Using the Error Queues

Errors occurring during the declaration either of ArchiveLink entries, print lists, SAP
DMS documents, or business workspaces are tracked in an error queue. This queue
can be accessed with the following transactions:
/OTX/RMPEQ ArchiveLink entries

/OTX/ Print lists
RMPEQPRINTL
/OTX/RM_WSC_ Business workspaces and business attachments. Errors of creating
PEQ business workspaces in the course of creating a document are written
to /OTX/RMPEQ. This is not relevant for OpenText Extended ECM for SAP
Solutions.
/OTX/RMERP_ SAP DMS documents. Errors of declaring SAP DMS documents, creating a
DMS_PEQ business workspace for the SAP DMS, or making them visible in a related
business workspace. If there is a problem with updating a business
workspace, you may also want to check the error queue for business
workspaces /OTX/RM_WSC_PEQ.
All errors that occur during document declaration in batch mode are stored. Also
update declaration errors are tracked. The error queue then allows reprocessing the
entries that failed. Errors that occur during the processing of the asynchronous
queue can be monitored there. They are not logged in an error queue. For more
information about the asynchronous queue, see Section 3.24 “Creating business
workspaces and declaring document asynchronously” in OpenText Extended ECM for
To open the ArchiveLink records error queue:
1. Start the /OTX/RMPEQ transaction.

2. Restrict the entries to be listed by specifying the required parameters.

In addition to the standard ArchiveLink values you can also enter the user who
failed in the declaration process (Error created by field) and the date of the error
entry (Error created at field).
You may process the records either in the manual or in the automatic mode. For
more information, see Step 4:
3. Processing records in manual mode
a. If you want to first have a look at the error entries and afterwards re-
process these entries, select the Process records in manual mode check box
and specify the maximum number of entries in the Hit restriction field.
b. Click Execute.
The Error Queue Management dialog displays the selected entries. In this
manual mode, the number of hits is restricted to the value specified before.

c. Select the entries you want to reprocess and click Re-process.
d. Click Yes.
A result list of the re-processed ArchiveLink entries is displayed.
e. To view the SAP log of the error that caused the entry in the error queue,
click the number in the Log number column.
4. Processing records in automatic mode

Deselect the Process records in manual mode check box and run the report
either in the background or directly.
The result list is the same as in the manual re-processing, with all entries of the
error queue filtered according to your selection mask entries.
To open the print list record error queue (SAP ERP 6.0 only):
1. Start the /OTX/RMPEQPRINTL transaction.


In addition to the standard print list values you can also enter the user who
failed in the declaration process (Error created by field) and the date of the error
entry (Error created at field).
3. You may process the records either in the manual or in the automatic mode:
Proceed as described under Step 3 on page 248 or Step 4 on page 249,
respectively.
To open the business workspaces error queue:
1. Start the /OTX/RM_WSC_PEQ transaction.


In addition to the standard values you can also enter the user who failed in the
declaration process (Error created by field) and the date of the error entry (Error
created at field).
respectively.
4. To view the SAP log of the error that caused the entry in the error queue, click
the number in the Log number column.
To open the SAP DMS documents error queue:
1. Start the /OTX/RMERP_DMS_PEQ transaction.
respectively.
4. To view the SAP log of the error that caused the entry in the error queue, click
the number in the Log number column.

25.1.5 Analyzing the application log

Extended ECM for SAP Solutions tracks errors and warning situations in the SAP
standard application log.
The application object for Extended ECM for SAP Solutions is /OTX/RM.
Depending on the scenario, the following subobjects are available:
/OTX/AUTH Authorization check

/OTX/BRUPD Business attachment update
/OTX/CONFIG Configuration
/OTX/DECUI Record declaration UI
/OTX/DISP Disposition report
/OTX/ERRQ Error queue failure
/OTX/GOS GOS attachment list
/OTX/GOSENH Modify GOS items via enhancement
/OTX/GOSMENU GOS menu
/OTX/HTTPSRV HTTP server failure
/OTX/LINKE Link entry changed
/OTX/MIGR Migrate report
/OTX/MIG_IDS Migrate Content Server IDs report
/OTX/RMDOL Content Server Business Attachments
/OTX/RMWSA Workspace Policies
/OTX/RMWSS Business Object Search
/OTX/SEAB Full-text Search Base
/OTX/SEAPI Full-text search API
/OTX/SEARCH Search report
/OTX/SEAX Full-text search connector
/OTX/TEST Test
/OTX/UPD Update events
/OTX/WSSET Read, create, or update business workspace
/OTX/CRM SAP CRM related issues
Note: There are no additional objects or subobjects for an SAP SRM system.

To view the SAP application log:
1. Start the SLG1 transaction.
2. Enter the application object /OTX/RM in the Object field and specify additional
parameters as required. Use a subobject to filter the log.
3. Click Execute.

4. Select a log entry, and then click Technical Information to display the
entry's technical context information.

In an error situation with a specific ArchiveLink entry, you can view the
property values Client, Object Type, and SAP object ID.
5. Click Detailed Information to show the calls stack where the error or
warning occurred. Expand the selected log entry to get more detailed
information.

6. Double-click on the subentry to show a detailed error message. If available, click

Detailed Information to display the details of the error message.

Part 5
Handing over and transporting the system
Part 5 Handing over and transporting the system
This part contains optional configuration tasks.
• “Preparing a checklist for business administrators“ on page 259

• “Transporting Extended ECM for SAP Solutions Content Server configuration
and templates“ on page 261

Chapter 26
Preparing a checklist for business administrators
The following tools provide both necessary and useful information:
SAP system
• Diagnostic Program: “Understanding the SAP Diagnostic Program”

on page 245
Tests the customizing and provides solutions for errors.
• Configuration Report: Section 25.1.3 “Understanding the Configuration
Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-CGD)
Provides information about Extended ECM for SAP Solutions related
customizing in the SAP system.
Content Server
System Report: Section 25.2 “Understanding the Content Server System Report”
in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
Contains the complete configuration information of the Content Server system.
Look for the “Extended ECM Information” section.
OpenText Administration Client
You can generate a report for OpenText Archive Center, which provides
information for the ArchiveLink setup in SAP (OAC0 transaction).
To generate the system configuration reports:
1. In OpenText Administration Client, log on to the Archive Center server.
2. Go to Archive Server > System > Reports.
3. In the Reports pane, open the Scenarios tab and select the scenario.
4. In the Actions pane, click Generate Report. A new window opens, which
you can close.
5. Switch to the Reports tab in the Reports pane.
6. Click Refresh to list the newly generated reports.
7. Double-click one of the generated reports to view it.
OpenText Directory Services Web Client

The System Status page lets you view a System Configuration Report, version
information for the product, and highlights Potential Configuration Issues.

Chapter 26 Preparing a checklist for business administrators
To generate the system configuration reports:
1. From the web administration menu, under the Info heading, click System
Status.
2. On the System Status page, click Download System Configuration Report.
3. The system configuration report downloads to your machine. An

information box displays, depending on your browser settings, that you can
click to display the report.

Chapter 27
Transporting Extended ECM for SAP Solutions

Content Server configuration and templates
You can export and import a OpenText Extended ECM for SAP Solutions
configuration with the standard functions of Content Server Transport Warehouse.
This helps you moving an existing configuration from one Content Server
installation to another, for example if you are using development, test and
production systems.
Extensive plausibility checks help you import a working configuration. To reduce

the number of warnings and unresolved dependencies, OpenText recommends that
you use the following order for transport.
Between versions 10.5.1 and 16.2.6, OpenText Extended ECM for SAP Solutions used
a custom transport mechanism, which was gradually replaced by Content Server
Transport Warehouse. You can still import transport files from versions prior to
16.2.6 but you cannot export configurations anymore. In addition, you could migrate
the business object type configuration from a 10.5 SAP system to a 10.5.1 Content
Server.
Table 27-1: Recommended transport order
Item type Transport method

1 Categories, classifications, and folder Content Server Transport Warehouse
structure, workspace types, unique names
2 Variable definitions, Workspace templates Content Server Transport Warehouse
(document templates)
3 Business object types Content Server Transport Warehouse
27.1 Transporting the Business Workspaces

configuration from versions 10.5.1 and later
What does the configuration import do?
• The import evaluates Content Server nodes like folders, classifications and
categories as they are used in the configuration of business object type,
workspace type and unique names by the name they had in the source system. If
a node with the same name exists in the target system, it is used, otherwise a
warning is issued. If more than one node with the same path is found, the first
one is used and a warning is issued. You can change the node on the preview
page.

Chapter 27 Transporting Extended ECM for SAP Solutions Content Server configuration and templates
• The import checks the usage of categories with attributes and attribute sets for
location and sub location path in workspace type and external document storage,
RM Classification, classification and multilingual names. If it is not correct a
warning is issued. Additionally, if the category does not contain the used
attributes or attribute sets a warning is issued.
• To transport the configuration from the Extended ECM SAP side version 10.5
to Content Server 10.5.1 – When a transport file from the SAP Configuration
Export Report /OTX/RM_EXPORT_BUS_O is imported, the property usages
including the property modifier in location, sub location path of workspace type
and multilingual names are substituted by their corresponding category attribute
according to the property mappings in the transport file. If there is no mapping
or if there are multiple mappings, a warning is issued.
• If the transport file contains names for multilingual names in languages that are
not enabled in the target system, a warning is issued. The name is imported, but
it cannot be seen in the workspace type configuration as long as the language is
not enabled. If you change the workspace type before the language has been
enabled, this name is removed from the configuration.
• To find out whether a workspace type in the transport file must be created or
updated, workspace types are searched by their name given in the transport file.
If no business object type can be found, a new type is created. If there is no name
for a workspace type in the transport file, which is the case for an export from an
SAP system, but the workspace type is associated to a business object type in the
target system, this workspace type is used.
• To find out whether a business object type in the transport file must be created or
updated, business object types are searched by their name, and also by the
combination of business object type/business application. If no business object
type can be found that way, a new type is created. If different types are found,
the import is rejected with the message Different Object Types found ….
• If workspace types are used in the Related Items sidebar widget and they are not
exported to the same file, these workspace types are also searched by their
names. You can change the found type on the preview page. This is also done if
only business object types are exported and imported but not their associated
workspace types.

27.1. Transporting the Business Workspaces configuration from versions 10.5.1 and later
27.1.1 Importing the configuration from a Content Server

version before 16.2.6
To import the Business Workspaces configuration on Content Server:

Import/Export Configuration.
2. On the following page, click Import Configuration.
3. Select the transport file from your local file system. If you want to use the
transport file that is stored in your personal workspace, you must first
download it.
4. Click Preview. The transport file is checked and you can preview everything
that is going to be imported and where. Errors and warnings are also displayed.
ID Mapping
Contains all node IDs that have been found in the transport file, for example
for classifications, or for categories that are used for the location or the
workspace name. If the target system contains nodes with the same name as
the source system, they prefilled with that suggestion. You can change the
node.
Workspace Types, Business Object Types, Unique Names, Variable
Definitions
If workspace types, business object types, unique names and variable
definitions are part of the export, they are listed in these sections. You can
see what data is being imported, if workspace types or business object types
are created or updated.
5. Resolve the inconsistencies in the mapping:
a. Click Select to map another node. These settings are buffered and used
when you refresh the preview or start the import. Alternatively, edit the
transport file and save it.
b. Click Preview to read the new changes into the preview.

Chapter 27 Transporting Extended ECM for SAP Solutions Content Server configuration and templates
6. When you are satisfied with the import preview, click Import.
A result page informs you in detail about what has been imported.

Part 6
Removing Extended ECM for SAP Solutions
Part 6 Removing Extended ECM for SAP Solutions
This part explains how you can remove Extended ECM for SAP Solutions and undo
related customizing.
• “General process“ on page 267

• “Performing manual steps before removal“ on page 269
• “Removing with the SAINT transaction“ on page 287

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

Chapter 28 General process
28.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.
For example, first remove Extended ECM CRM (OTEXRLC), then Extended ECM
base (OTEXRL).
• There may be manual steps necessary before you can actually remove. For more
information, see the following chapter.

Chapter 29
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 business object types. 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.
29.1 Extended ECM component OTEXRL

29.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 122 and “Providing
access to local folders for the Business Content window” on page 236.
Remove custom code depending on Extended ECM code
Custom code includes the following:

Chapter 29 Performing manual steps before removal
• Property Providers derived from Extended ECM Property Provider classes.

For more information, see Section 3.3 “Implementing a property provider in
SAP” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-
CGD).
• Generated Mass creation reports. For more information, see Section 24.2
“SAP: Creating or updating business workspaces using batch operations” in
• Implementations of Extended ECM BAdIs, for example the Business Content

Window menu BAdI. For more information, see Section 12.3.2 “Adding
custom functionality to the Business Content window context menu” in
• 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
12.1 “Customizing the Generic Object Services (SAP GUI)” in OpenText Extended
ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
Delete jobs for Extended ECM
• Business Workspace Mass creation jobs. For more information, see Section
24.2 “SAP: Creating or updating business workspaces using batch
operations” in OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-CGD).
• Document Declaration creation jobs. For more information, see Section 24.4
“SAP: Declaring ArchiveLink documents using batch operations” in
• Remove Deleted Records job. For more information, see Section 24.8 “SAP:
Scheduling jobs for removing deleted records” in OpenText Extended ECM for
• Delete the asynchronous queue job. For more information, see Section 3.24.2
“Setting queue properties” in OpenText Extended ECM for SAP Solutions -
• 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 130.

29.1. Extended ECM component OTEXRL
Remove the SPI service

For more information, see “Configuring the Service Provider Interface service”
on page 149.
Remove Event Type Linkages, which are using Extended ECM function modules
Use the SWETYPV transaction. For more information, see the following:
Section 5.2 “SAP: Linking events to receiver type function modules” in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)
Section 6.1.10 “Configuring automatic document declaration” in OpenText
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)
Change Document events for automatic policy assignment
For more information, see Section 5.4 “SAP: Maintaining change document
events” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-
CGD).
29.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 “Creating logical ports in the SAP system”
on page 130.
• Change Document Events set up for Extended ECM. For more information, see
Section 5.4 “SAP: Maintaining change document events” in OpenText Extended
Note: Before you delete an event, make sure that it is not used for any other
purpose than Extended ECM.

29.2 Extended ECM for SAP ERP, S/4HANA

component OTEXRLE
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
24.5 “SAP: Declaring SAP DMS documents using batch operations” in
• 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
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 -
Remove custom code depending on Extended ECM code
• 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
• All other custom code using Extended ECM ERP code.

29.3. Extended ECM CRM component OTEXRLC

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
29.3 Extended ECM CRM component OTEXRLC

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 15.1 “Customizing the integration into SAP
CRM Web Client UI or S/4CRM” in OpenText Extended ECM for SAP Solutions -
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.

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

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.

Important
You must repeat this procedure for all other enhancements that you created.
For more information, see Section 15.2 “Customizing the integration into SAP
CRM Interaction Center Web Client UI” in OpenText Extended ECM for SAP
To remove the integration into SAP CRM Interaction Center:
1. Start the BSP_WD_CMPWB transaction, and then open the IUICOVW component
2. Delete the component controller enhancement:
a. In the Component Structure Browser, right-click Component >

Component Controller, and then select Delete Enhancement.
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.
example Controller, View, View Controller Implementation, and Context.

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.
a. In the Component Structure Browser, right-click View > IBT126H_MAIL/

send_screen, and then select Delete Enhancement.

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

a. In the Component Structure Browser, right-click View >

CRMCMP_CSS_EML/MailAttachments, and then select Delete
Enhancement.

application.

29.4 Extended ECM SRM component OTEXRLS

Can be uninstalled without additional tasks.
29.5 Extended ECM OData Services component

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

29.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.
29.6 Extended ECM Fiori Apps component OTEXRLF

OTEXRLF
To clean up the Fiori frontend system, you reverse the customizing you did before.
This is described in Section 14 “Integrating Extended ECM for SAP Solutions into
SAP Fiori apps” in OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-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 278.
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.

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.

29.7 Extended ECM Business Scenarios component

OTEXRLSA
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
• Section 6.1.10 “Configuring automatic document declaration” in OpenText
• 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)

29.8. Archiving and Document Access component OTEXBAS
Remove custom code depending on Business Scenario code

• Property providers derived from the property provider classes

• All other custom code using artifacts of development class /OTX/RLSA and its
subordinates
29.8 Archiving and Document Access component

OTEXBAS
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 21.3.6.3.1.6 “User exits tab” in OpenText Archiving and Document

Access for SAP Solutions - Scenario Guide (ER-CCS)
○ Section 21.3.6.4.1 “User exits” in OpenText Archiving and Document Access
for SAP Solutions - Scenario Guide (ER-CCS)
○ Section 21.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)

– 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 20.3 “Customizing additional ArchiveLink attributes” in OpenText

• 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

– Section 20.2 “Customizing the Business Content window in the GOS menu”
in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide
(ER-CCS)

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

29.9. Archiving and Document Access ERP package component OTEXERP
29.9 Archiving and Document Access ERP package

component OTEXERP
OTEXERP
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 281.
29.10 Archiving and Document Access CRM package

component OTEXCRM
29.10.1 Performing mandatory steps before uninstalling
OTEXCRM
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 281.
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
• Section 18.3.1.1 “Creating a transaction launcher URL” in OpenText DocuLink for
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:

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

• Section 19.3.1.1 “Creating a new workspace class” in OpenText DocuLink for SAP
29.11 Archiving and Document Access OData Services

component OTEXBASO
OTEXBASO
you did before. For more information, see .
• 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 285.

29.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.
29.12 Archiving and Document Access Fiori Apps

component OTEXBASF
OTEXBASF
you did before. For more information, see Section 14 “Integrating Extended ECM for
SAP Solutions into SAP Fiori apps” in OpenText Extended ECM for SAP Solutions -
• 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.

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.
2. Find all roles that you created for Archiving and Document Access.

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

Part 7
Appendix: Architecture and system
recommendations
Part 7 Appendix: Architecture and system recommendations
This part provides additional information about the components and architecture of
Extended ECM for SAP Solutions.
• “Components of Extended ECM for SAP Solutions“ on page 291

• “Deployment scenarios“ on page 293
• “Communication protocols“ on page 295

Chapter 31
Components of Extended ECM for SAP Solutions
Extended ECM for SAP Solutions consists of components providing capabilities

inside the SAP business applications but can also be deployed for an enterprise-wide
content management including non-SAP users and non-SAP applications.
The core of Extended ECM for SAP Solutions is the combination of the two major
components OpenText Content Server (Content Server) and OpenText Archive
Center (Archive Center).
Content Server is tightly integrated with Archive Center. All content managed by
Content Server can be stored in Archive Center, which is mainly an abstraction layer
to the underlying storage hardware.
This provides the foundation for the following capabilities:
• Document Management
• Records Management
• Content-centric Workflow
• Collaboration
The components of Extended ECM for SAP Solutions are deployed in three ways:
• Client components running on user's desktop, for example the following:
– Open Text Web GUI

This component provides a web-based interface to the majority of the
Extended ECM for SAP Solutions functions and to SAP and non-SAP content.
– Enterprise Connect
This component provides the integration in the desktop applications like
Microsoft Windows Explorer, Microsoft Office and Acrobat. It is also
responsible for the offline access to content.
– Open Text Imaging Enterprise Scan
Imaging Enterprise Scan provides an application to scan paper-based content
directly to SAP or into Extended ECM.
• Server components, for example the following:
– Content Server
Content Server provides the core document management, search, records
management, collaboration, and workflow capabilities of Extended ECM for
SAP Solutions.

Chapter 31 Components of Extended ECM for SAP Solutions
– Archive Center
Interface and abstraction layer for the storage layer. It is responsible for the
long-term preservation of content.
• Components running in SAP Business Suite, for example the following:
– DocuLink for SAP Solutions

The DocuLink for SAP Solutions component of Extended ECM for SAP
Solutions adds a process-oriented view to all business documents and data
from different SAP applications.
– Extended ECM for SAP Solutions
Extended ECM for SAP Solutions allows putting SAP documents under the
control of Records Management policies and retention schedules. It enables
the manual and automatic creation of business workspaces from SAP
business objects and of business attachments.
Note: This overview does not cover the optional components AppWorks
Gateway and Content Server mobile app.
Figure 31-1: Deployment of components on clients, in SAP Business Suite,

and on server components

Chapter 32
Deployment scenarios
This chapter shows some typical deployment scenarios. For detailed information
and other possible deployment scenarios with Content Server, see Section 1.2
“Common deployments” in OpenText Enterprise Library - Installation and Upgrade
Guide (EL-IGD) or Section 2 “Design Your Content Server System” in OpenText
Content Server - Installation Guide (LLESCOR-IGD).
Tip: For deployment scenarios of Content Server as well as best practices

examples, see the Content Server Champion Toolkit on OpenText My Support
(https://knowledge.opentext.com/knowledge/llisapi.dll/open/19905386).
All-in-one scenario
In an all-in-one scenario, all components are deployed on one server. This scenario is
primarily intended for demonstration and testing.
All-in-one server
SAP ERP Archive Center
Development system Directory Services
Content Server
OpenText ABAP Add-ons Database
Document Pipelines
Figure 32-1: All-in-one scenario
Distributed scenario
In a distributed scenario, Archive Center and all web services are installed on one
computer and are connected to one or more Content Server installations.
Each Content Server computer can host one or more Content Server instances.
Multiple frontend servers are deployed with a load-balancer to provide highly
available end-user services.

Chapter 32 Deployment scenarios
Extended Content Server Content Server

SAP ERP Archive Center Content Server Content Server
Development system as frontend server as frontend server
as frontend server as backend server
Archive Center
OpenText ABAP Add-ons Directory Services Content Service is running Admin Service is running
Document Pipelines
Database server Load balancer

Storage device
Databases for
hardware and software
(third-party product) o Archive Center
(third-party products)
o Content Server
Figure 32-2: Distributed scenario

Chapter 33
Communication protocols
The Service Provider Interface (SPI) is required to access business information that is
available in the leading application, for example, SAP ERP or SAP CRM, from
Content Server. To access Content Server from the external system, you use the
Extended ECM web services. A detailed description of SPI and the API is available
on OpenText My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/
44140285).
Legend:
Extended ECM for SAP Solutions OpenText component
SAP component
Desktop Other component

R R
R
Exchange/ SAPGUI, Enterprise Enterprise
DesktopLink NWBC Scan Connect
NotesLink OLE
R
(Archive)
R R
Windows Administration Mobile Apps
Browser Viewer Client
R R
R
R
RFC HTTP R
HTTP (Content Server UI)
R
R R
R
R HTTP (SAP UI) Document HTTP
HTTP
Pipeline
RFC R
HTTP AppWorks
HTTP
SAP R/3 (ERP, CRM, SRM)
R Gateway
R
Event Tomcat
Workflow ArchiveLink
Archive Center
Remote Cache
BAdI Imaging Web Server
R Document Storage
Fiori Business R R R
Object SAP Module ILM R

OTDS
Browsing R Content Server
Event SOAP/HTTP
Enabler
R R
R
WebDav WebDav Core Rec. Management Other Modules
R (ILM)
R
Enterprise R R R
Extended ECM for SAP SOAP
Library xECM Platform Connected Workspaces
Services HTTP Configuration
UI integration Property Configuration
Provider R xECM Web UI components R
UI components
R
R Services / API/SPI Workspaces
R SOAP / HTTP CMIS
Integration Communication Bus. Attachment Templating
services services
Archiving and HTTP(Search, UI, Rest) Completness Check
Document R R R R R
Access for Configuration R
SAP Extended ECM for SAP
SOAP(SPI)
Figure 33-1: Extended Enterprise Content Management
The following communication protocols are used between the systems and
components:
• SOAP Web Services over HTTP(S)
– between the SAP add-on Extended ECM for SAP Solutions and the Business
Workspaces module on Content Server via the Extended ECM Web service
(API)
– between the Business Workspaces module and the SAP add-on Extended
ECM for SAP Solutions (SPI)

Chapter 33 Communication protocols
– between the SAP add-on Extended ECM for SAP Solutions and Directory
Services (API)
– only for versions 16.2.10 or earlier: between the SAP add-on Extended ECM
for SAP Solutions and Enterprise Library Services (API)
• OLE for communication between SAP GUI
– between SAP GUI and Enterprise Scan

– between SAP GUI and Imaging Viewers
• WebDAV over HTTP(S)
– between SAP system using SAP ILM and Extended ECM (WebDAV)
• HTTP(S)
– between SAP ArchiveLink and Archive Center

– between SAP add-on Extended ECM for SAP Solutions and Content Server
(XML Search)
– between Imaging Viewers/DesktopLink and Archive Center
– between Enterprise Scan and Archive Center
– between Content Server Web UI and Content Server
Using asynchronous methods

With the asynchronous methods, you can detach the workspace creation or update
process from the caller process. The requests are placed in a queue and are
processed separately by another process in the background while the control
immediately gets back to the caller process.
The methods simulate a transactional behavior. The API supports placing more than
one workspace creation/update request at the same time. In that case the request are
bundled and handled in a transactional manner, meaning if one creation fails in a
bundle, the other eventually created workspaces are also not visible until the failure
is corrected. Note that this behavior is only valid if you use the corresponding
asynchronous read method to get information about a workspace. For more
information, see the SDK Guide on OpenText My Support (https://
knowledge.opentext.com/knowledge/cs.dll/Open/63007681).

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.

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

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

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.

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.

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.

OpenText Extended ECM For SAP Solutions CE 21.4 - Installation and Upgrade Guide English (ERLK210400-IGD-En-03)

Uploaded by

Copyright:

Available Formats

OpenText Extended ECM For SAP Solutions CE 21.4 - Installation and Upgrade Guide English (ERLK210400-IGD-En-03)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Extended ECM For SAP Solutions CE 21.4 - Installation and Upgrade Guide English (ERLK210400-IGD-En-03)

Uploaded by

Copyright:

Available Formats

OpenText™ Extended ECM for SAP®

Installation and Upgrade Guide

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

Open Text Corporation

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

Copyright © 2021 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

Part 1 Planning the installation of Extended ECM for SAP

2 Overall architecture ................................................................. 15

3 Data characteristics of an Extended ECM system ............... 19

4 Best practices for the network and communication layer ... 21

Part 2 Installing Extended ECM for SAP Solutions 27

5 Obtaining the installation software ........................................ 29

6 Prerequisites for Extended ECM ............................................ 51

ERLK210400-IGD-EN-03 Installation and Upgrade Guide iii

7 Installing Extended ECM for SAP Solutions ......................... 59

8 Installing the SAP package ..................................................... 61

9 Generating roles ...................................................................... 65

10 Installing language packages in the SAP system ................ 67

11 Installing the Content Server modules .................................. 69

12 Installing language packs on Content Server ....................... 81

13 Deploying Extended ECM Web Services ............................... 83

14 Installing OpenText ArchiveLink Filter .................................. 87

15 Installing AppWorks Gateway (optional) ............................... 89

Part 3 Upgrading Extended ECM for SAP Solutions 91

16 Upgrade scenarios .................................................................. 93

17 General recommendations for the upgrade .......................... 99

18 Upgrading to Extended ECM for SAP Solutions 21.4 ........ 101

iv OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

18.2 Upgrading the database schema .................................................... 104

19 Upgrading from Extended ECM for SAP Solutions 20.2 to

20 Upgrading Business Scenarios on the SAP system .......... 111

Part 4 Configuring the system after the installation 113

21 Connecting the SAP system ................................................. 115

22 Performing general post-installation tasks in SAP ............ 119

23 Performing system administration tasks in Content

ERLK210400-IGD-EN-03 Installation and Upgrade Guide v

23.3 Connecting SAP as the business application ................................... 159

vi OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

24 Performing additional optional tasks in the SAP system .. 227

ERLK210400-IGD-EN-03 Installation and Upgrade Guide vii

24.1.5.1 Configuring Microsoft IIS to return meaningful REST API error

25 Verifying the installation ....................................................... 245

Part 5 Handing over and transporting the system 257

26 Preparing a checklist for business administrators ............ 259

27 Transporting Extended ECM for SAP Solutions Content

Part 6 Removing Extended ECM for SAP Solutions 265

28 General process .................................................................... 267

29 Performing manual steps before removal ........................... 269

viii OpenText™ Extended ECM for SAP® Solutions ERLK210400-IGD-EN-03

29.4 Extended ECM SRM component OTEXRLS ................................... 278

30 Removing with the SAINT transaction ................................ 287

Part 7 Appendix: Architecture and system recommendations 289

31 Components of Extended ECM for SAP Solutions ............ 291

32 Deployment scenarios .......................................................... 293

33 Communication protocols .................................................... 295

GLS Glossary 297

ERLK210400-IGD-EN-03 Installation and Upgrade Guide ix

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