OpenText Extended ECM For SAP Solutions 16.2 - Installation and Upgrade Guide English (ERLK160200-00-IGD-En-01)

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

ERLK160200-00-IGD-EN-01

OpenText™ Extended ECM for SAP® Solutions Installation and Upgrade Guide ERLK160200-00-IGD-EN-01 Rev.: 23. Mar. 2017 This documentation has been created for software version 16.2. It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published at https://knowledge.opentext.com. Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677 Support: https://support.opentext.com For more information, visit https://www.opentext.com

Copyright © 2017 Open Text. All Rights Reserved. Trademarks owned by Open Text. Disclaimer No Warranties and Limitation of Liability Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

Table of Contents 1

What is OpenText Extended ECM for SAP Solutions ............ 7

1.1 1.2

What is new? .................................................................................... 7 Related documentation ...................................................................... 8

Part 1

Installing Extended ECM for SAP Solutions

Checking the prerequisites .................................................... 13

2.1 2.2 2.2.1 2.2.2 2.3 2.4

Required knowledge ........................................................................ Prerequisites .................................................................................. SAP prerequisites ........................................................................... Content Server prerequisites ............................................................ SAP Add-On Installation Tool (SAINT) .............................................. Finding version information for Extended ECM for SAP Solutions relevant system components ............................................................

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

3.1

Installation sequence for Extended ECM for SAP Solutions ............... 21

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

Generating roles ...................................................................... 25

Installing language packages in the SAP system ................ 27

13 13 13 16 17 18

Installing the Content Server modules .................................. 29

7.1 7.2 7.3

Installation procedure on Content Server .......................................... 29 Installing Content Server and modules files ....................................... 29 Installing the Content Server modules .............................................. 32

Installing language packs on Content Server ....................... 35

Deploying Extended ECM Web Services ............................... 37

9.1 9.2 9.3

Deploying Extended ECM Web Services into the application server ... 37 Deploying Content Web Services ..................................................... 39 Configuring host and port for Content Server in Tomcat ..................... 40

Part 2

Upgrading Extended ECM for SAP Solutions

Upgrade scenarios .................................................................. 43

10.1

Supported combinations .................................................................. 44

General recommendations for the upgrade .......................... 47

Upgrading from Extended ECM for SAP Solutions 16 to 16.2 ............................................................................................ 49

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

iii

Table of Contents

12.1 12.2 12.3

Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2 ............................. 65

13.1 13.2 13.3

Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2 ................ 65 Upgrading the database schema ...................................................... 78 Upgrading to Extended ECM for SAP Solutions in the SAP system .... 79

Upgrading from ECMLink 10.0.3, 10.0.4, or 10.5.0 ................ 81

Upgrading from ECMLink 9.8.x, 10.0, or 10.0 SP1 or SP2 ... 83

Upgrading from versions prior to 9.8 .................................... 85

Part 3

Post-installation and post-upgrade tasks

Performing general post-installation tasks in SAP .............. 89

17.1 17.2

Using the IMG function .................................................................... 89 Assigning SAP roles ........................................................................ 92

Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0 ..................................................... 95

18.1

Exporting the SAP PSE certificate for the SAP authentication handler ........................................................................................... 95 Activating the SSO HTTP service ..................................................... 98 Creating logical ports in the SAP system .......................................... 99 Creating logical ports for SAP Basis 7.0 ............................................ 99 Creating logical ports for SAP Basis 7.01 ........................................ 106 Creating logical ports for SAP Basis 7.31 ........................................ 109 Creating logical ports for SAP Basis 7.51 ........................................ 113 Configuring the Service Provider Interface service ........................... 116 Maintaining Extended ECM connections ......................................... 117 Improving data security for impersonation connections .................... 121 Importing the Content Server SSL certificate ................................... 122

18.2 18.3 18.3.1 18.3.2 18.3.3 18.3.4 18.4 18.5 18.6 18.7

Performing post-installation or post-upgrade tasks in Content Server ....................................................................... 123

19.1

Importing root certificates for Secure Sockets Layer (SSL) connections .................................................................................. Connecting an external system ...................................................... Configuring the storage provider .................................................... Managing users ............................................................................

19.2 19.3 19.4

Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2 ............................................................................................... 49 Upgrading the database schema ...................................................... 62 Upgrading to Extended ECM for SAP Solutions in the SAP system .... 63

123 124 126 127

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Table of Contents

19.5 19.5.1 19.5.2 19.5.3 19.5.4 19.5.5 19.6

Preparing document declaration ..................................................... Creating an Enterprise Library application ....................................... Creating a Records Management classification (optional) ................ Importing folder and item type ........................................................ Setting up the authorization for records ........................................... Creating system categories in Content Server ................................. For SAP CRM and SRM: Configuring security settings ....................

Verifying the installation ....................................................... 137

20.1 20.1.1 20.1.2 20.1.3

Analyzing the SAP system ............................................................. Understanding the SAP Diagnostic Program ................................... Understanding the details of the Diagnostic Program ....................... Understanding the Configuration Report .........................................

137 137 138 143

Part 4

Miscellaneous

145

Installing Content Server patches using the cluster management tool ................................................................... 147

Performing additional optional tasks .................................. 149

22.1 22.2

Checking the appearance of the SAP integration ............................. Customizing the integration into SAP GUI via Generic Object Services ....................................................................................... Customizing the Generic Object Services (SAP GUI) ....................... Select items to be displayed in Business Content window ................ Customizing the context menu of the Business Content window ....... Customizing the Business Content window context menu with Content Server menu entries ......................................................... Adding custom functionality to the Business Content window context menu ................................................................................ Providing Drag-and-drop functionality for the Business Content window ......................................................................................... Enabling the integration widget in the Business Content window ...... Maintaining Content Server subtypes as copy/move target in the Business Content window .............................................................. Providing access to local folders for the Business Content window ... Providing thumbnails for business workspace documents in the Business Content window .............................................................. Integrating Viewers ....................................................................... Customizing MIME types for preview .............................................. Customizing the GOS Attachment list for Records Management ...... Viewing the old configuration in SAP .............................................. Configuring Single Sign-on for Content Server ................................ Configuring external viewers for Content Server ..............................

22.2.1 22.2.2 22.2.3 22.2.3.1 22.2.3.2 22.2.4 22.2.5 22.2.6 22.2.7 22.2.8 22.2.9 22.2.10 22.2.11 22.3 22.4 22.5

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

127 127 131 131 133 134 135

149 152 152 154 155 155 157 157 157 158 159 160 161 163 164 165 166 168

Table of Contents

Preparing a checklist for the customizing team ................. 171

Transporting Extended ECM for SAP Solutions Content Server configuration and templates .................................... 173

24.1 24.1.1 24.2

Transporting the Connected Workspaces configuration ................... 173 Importing the configuration ............................................................ 174 Transporting categories, classifications and workspace templates .... 176

GLS

Glossary

179

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 1

What is OpenText Extended ECM for SAP Solutions OpenText Extended ECM for SAP Solutions is a combination of Content Server modules, web services and an SAP package, with which you can integrate Content Server functionality into SAP business processes. This includes functionality for document and records management, archiving, workflow, and collaboration. Business workspaces, cases and binders

A business workspace in Content Server contains content that is relevant for a business object. From Content Server side, users can easily view the data of this business 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 attachments

In addition to the content that is stored in a business workspace for a business object, users can connect additional documents as business attachments to a business object.

Business relationships

Extended ECM for SAP Solutions provides tools to illustrate a relationship between business workspaces. For example, a hierarchical relationship between business workspaces can be displayed in a sidebar widget of a business workspace.

1.1 What is new? “Generating roles“, page 25 The client-dependent data for the roles are no longer delivered with BC set /

OTEXRL/RM_LINK_02.

“General recommendations for the upgrade“, page 47 The product, components, and administration activities have been renamed as follows: •

The product ECMLink is now Extended ECM for SAP Solutions.

•

The Content Server module ECMLink is now Connected Workspaces. In addition, there are the modules Extended ECM Platform and Extended ECM for SAP Solutions.

•

ECMLink Web Services are now Extended ECM Web Services.

•

Content Server administration: There are now two relevant sections on the Administration Page: Connected Workspaces for general configuration and Extended ECM for configuration related to external systems such as SAP.

•

SAP administration: In the IMG, all activities are collected in the OpenText Extended ECM for SAP Solutions section. In addition to the Infrastructure section, there is a Extended ECM section. The Maintain Enterprise Library Settings activity has been renamed to Maintain Extended ECM Connections.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 1 What is OpenText Extended ECM for SAP Solutions

In general to refer to connections to OpenText components, Connection ID is used instead of Enterprise Library ID. “Upgrading the database schema”, page 62 The database schema is now upgraded with the standard Content Server mechanism. “Upgrading the database schema”, page 78 The database schema is now upgraded with the standard Content Server mechanism. “Improving data security for impersonation connections”, page 121 For an improved data security, you can now create a whitelist that contains all Content Server URLs which are allowed to connect to the SAP system. “Checking the appearance of the SAP integration”, page 149 You can now define a unique name for a Content Server appearance, to make the theme mapping transportable. “Select items to be displayed in Business Content window ”, page 154 You can now customize, which items are displayed in the Business Content window of a certain business object type.

1.2 Related documentation Important OpenText strongly recommends that you read OpenText Extended ECM for SAP Solutions - Overview Guide (ERLK-GGD) to make you familiar with architectural aspects and business scenarios of Extended ECM for SAP Solutions. Product documentation

The following documentation is available for Extended ECM for SAP Solutions respectively on OpenText My Support (https://knowledge.opentext.com/knowledge/ cs.dll/Open/https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10194282): OpenText Extended ECM for SAP Solutions - Overview Guide (ERLK-GGD) The Overview Guide contains a short overview over the functions and features of Extended ECM for SAP Solutions. It also explains the architecture and shows different business scenarios of Extended ECM for SAP Solutions. OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide (ERLK-IGD) (this guide) 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 – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

1.2. Related documentation

OpenText Extended ECM for SAP Solutions - Administration Guide (ERLK-AGD) The Administration Guide describes ongoing maintenance tasks. OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLK-CUM) This guide discusses user management and access control scenarios. OpenText Extended ECM for SAP Solutions - User Guide (ERLK-UGD) The User Guide describes how to use Extended ECM for SAP Solutions functionality in both SAP and Content Server. This guide is also available as online help. OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows with Microsoft SQL Server (ERLK-IWS) This specific Installation Guide describes the setup of one architecture scenario for Extended ECM for SAP Solutions with Microsoft SQL Server as database. OpenText Extended ECM for SAP Solutions - Installation Guide for Microsoft Windows with Oracle Database (ERLK-IWO) This specific Installation Guide describes the setup of one architecture scenario for Extended ECM for SAP Solutions with Oracle as database. Release Notes

The Release Notes describe the following aspects in detail: • • • • • •

The software supported by the product Requirements Restrictions Important dependencies Last-minute changes regarding the documentation Manual IDs of the current documentation

The Release Notes are continually updated. The latest versions of the Extended ECM for SAP Solutions Release Notes is available on OpenText My Support: Extended ECM for SAP Solutions (https://knowledge.opentext.com/knowledge/cs.dll/Open/ https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10194282).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Part 1 Installing Extended ECM for SAP Solutions

This guide covers the details of Extended ECM for SAP Solutions installation, the Content Server module Connected Workspaces and the SAP Add-on. For information on installing the other products or components, which are part of OpenText Extended ECM for SAP Solutions, see the individual installation guides. For information on 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)

•

“Checking the prerequisites“ on page 13

•

“Installing Extended ECM for SAP Solutions“ on page 21

•

“Installing the SAP package“ on page 23

•

“Generating roles“ on page 25

•

“Installing language packages in the SAP system“ on page 27

•

“Installing the Content Server modules“ on page 29

•

“Installing language packs on Content Server“ on page 35

•

“Deploying Extended ECM Web Services“ on page 37

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 2

Checking the prerequisites 2.1 Required knowledge The following knowledge is required from the person dealing with the installation as described in this document: •

In-depth knowledge of SAP administration tasks, in particular the SAP Add-On Installation Tool (SAINT).

•

In-depth knowledge of OpenText™ Content Server, OpenText™ Archive Center, Records Management, User Management, and OpenText™ Directory Services.

•

Basic knowledge of the employed operating system.

2.2 Prerequisites 2.2.1

SAP prerequisites Extended ECM for SAP Solutions supports the following SAP products: •

SAP S/4 HANA

•

SAP ERP 6.0

•

SAP CRM 7.0 Note: Content Server integration widget is only supported for Business Workspace UI Integration in SAP CRM. CRM Requirement: CRM 7.0 Ehp 1. OTDS Requirement: 10.5 or higher

•

SAP SRM 7.0

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 2 Checking the prerequisites

Transport system The SAP application transport system is installed, or in other words, the jobs RDDPUTPP and RDDIMPDP are set up in the correct clients (scheduled to run periodically or event-triggered). SAP notes The following SAP notes must be applied:

SAP Note

Required for

110910

Some language-dependent texts may not be displayed correctly in the GUI.

884077

Log-on error from external systems to WAS 7.00 systems: The external candidate's password contains at least one lower case letter. In accordance with the rules, which were valid up to and including WAS 6.40, the registration application changes the passwords to capital letters. However, as of WAS 7.00 (see SAP Note 862989), the system can be set in a way that it distinguishes between upper case and lower case letters in a password. In this case, the log-on fails if the original password contains at least one lower case letter.

1128338

CALL_BROWSER does not launch a new window to open the URL, even when the NEW_WINDOW parameter is passed to the function module. Instead, an existing window is used to open the URL. However, as of SAP Note 1177636, the behavior of CALL_BROWSER is changed to allow also opening URLs on other platforms than Microsoft Windows. In this case, the settings of the MS Internet Explorer govern the URL handling, i.e. whether a new window is opened.

1255948

Required for the declare functionality of the print lists.

1227752 1122938 (SAP ERP 6.0 and SAP_BASIS 14 or higher)

Required to avoid known problems with the web services.

2238264 (SAP S/4 HANA)

Several outbound web service proxies should be triggered. In that process a program termination of type STYLESHEET_GENERATION_FAILURE is raised.

1424747

Enables the transmission of SOAP error codes to identify problems.

1267258

Unexpected error message No vendor specified when logon language is English.

822380 (SAP 7.00) Installation information OSS note 1040369 212876 (SAPCAR tool)

Required to avoid known problems with the SAP Add-On Installation Tool (SAINT).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

2.2. Prerequisites

SAP Note

Required for

1382711 1379958 1613012

Required when using SAP CRM Investigative Case Management.

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.38.9, which is based on User Interface Technology SAP_UI release 750. At installation time this package can be installed on SAP frontend systems with User Interface Technology (SAP_UI release 740, patch level 13 or higher). The Fiori Add-On package of OpenText Archiving and Document Access for SAP Solutions, OTEXBASF 1620_740 is required. Though not required for installation, at runtime the Fiori app calls the OData services of Extended ECM for SAP Solutions.

•

Patch level for optional OData package: This package can be installed on SAP backend systems either with Backend Event Provider (IW_BEP release 200, patch level 10) or with SAP Gateway Foundation (SAP_GWFND, at least release 740, patch level 09). On systems with SAP_GWFND release 750, like S/4 HANA, use SPAM/SAINT level 0059 or newer for installation. Though not required for installation, at runtime the OData services of Extended ECM for SAP Solutions call RFC functions of the basis add-on of Extended ECM for SAP Solutions (OTEXRL) 16.2. Note: The documentation and the release notes are updated regularly; therefore, check for the latest version on OpenText My Support (https:// knowledge.opentext.com/knowledge/llisapi.dll/open/16514655). Basis package of Archiving and Document Access for SAP Solutions Prior to the SAP Add-on package OTEXRL of Extended ECM for SAP Solutions you must install the SAP Add-On OTEXBAS of Archiving and

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 2 Checking the prerequisites

Document Access for SAP Solutions 16. For more information, see Section 3 “Installing Basis package” in OpenText Archiving and Document Access for SAP Solutions - Installation and Upgrade Guide (ER-IGD).

2.2.2

Content Server prerequisites Check the following prerequisites prior to the installation of SAP Add-On package OTEXRL: Important See the Release Notes for a comprehensive and most current list of prerequisites. Required patches for the installed Content Server version Content Server 16.2 - The security fixes for Content Server are vital for proper installation; if you already have a Content Server installation, make sure you have installed Content Server 16.2. Additionally, install the additional patches provided in the Patches folder on the Extended ECM for SAP Solutions installation medium and the current Enterprise Library patch collection at https://knowledge.opentext.com/knowledge/cs.dll/Open/21827049. You can also use the cluster management tool to install patches. For more information, see “Installing Content Server patches using the cluster management tool“ on page 147. Note: If you create a completely new system, Content Server 16.2 is installed by the master setup. Important Prior to installation, make sure that you have read the information in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and OpenText Enterprise Library - Scenario and Configuration Guide (EL-GGD) for the relevant version. Installation of Enterprise Library Services and Archive Center Services Both services must be installed. Archive Center Services is part of Archive Center. Install Enterprise Library Services 16.2 and Archive Center 16.2. Additionally, install the patches provided on the Extended ECM for SAP Solutions installation medium. Important Extended ECM for SAP Solutions is not compatible with the Enterprise Library Interview module which is an optional Case Management module. Do not install this module in combination with Extended ECM for SAP Solutions. ArchiveLink customizing Customizing of the SAP system and the Archive and Storage Services must be completed according to Part II “SAP basis customizing” in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

2.3. SAP Add-On Installation Tool (SAINT)

Host/port for the logical archive Check that store and retrieval of ArchiveLink documents functions properly with the server. Important With the newest Archive Center version, the logical archive (OAC0 transaction) must use the Archive and Storage Services host/port. For older versions, it must use the Enterprise Library Services host/port and not the Archive and Storage Services host/port. In this case, restrict access to the Archive and Storage Services host/port exclusively to the Enterprise Library via a firewall configuration. If you are using a firewall between SAP and Content Server the following ports must be enabled: •

8080 HTTP or 8090 HTTPS on Apache Webserver: used for the Web service communication from SAP to Content Server.

•

8000: Used for the communication between Content Server and the SAP Client.

•

80 (HTTP) or 443 (HTTP): Only required for connection tests from SAP to Content Server.

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

Installation packages and passwords The SAP package for Extended ECM for SAP Solutions is protected with a specific password. During installation, this password is requested by SAINT. For details, see the following table: Table 2-1: Installation packages and passwords Package

Release

Designation

Password

OTEXRL

1620_700

Extended ECM for SAP Solutions

9386C726B8

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 2 Checking the prerequisites

Package

Release

Designation

Password

OTEXRLC

1620_700

Extended ECM for SAP Solutions SAP CRM Add-On

9586C745B8

OTEXRLS

1620_700

Extended ECM for SAP Solutions SAP SRM Add-On

9386C755B8

OTEXRLO

1620_700

Extended ECM for SAP Solutions SAP OData Services Add-on

9386C749B8

OTEXRLF

1620_740

Extended ECM for SAP Solutions SAP Fiori Apps AddOn

9086C740B8

Note: You only need these passwords and packages if they are not already installed in your system.

2.4 Finding version information for Extended ECM for SAP Solutions relevant system components This chapter explains how you can find out which version of the different components is used in your system. Version information is also included in the system reports of Content Server and the configuration report SAP System. Tip: You find additional information about your systems in the following reports:

•

Section 20.1.1 “Understanding the SAP Diagnostic Program” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)

•

Section 20.1.3 “Understanding the Configuration Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)

•

Section 20.2 “Understanding the Content Server System Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD)

Content Server From the Content Server menu, select Help > About Content Server. The version is displayed, for example Content Server 16. You find detailed information also in the Content Server system report. For more information, see Section 20.2 “Understanding the Content Server System Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

•

Connected Workspaces module on Content Server On the Content Server Administration page, click Module Administration > Install Modules. You see the version of the module next to its name, for example 16.0.0 .

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

2.4. Finding version information for Extended ECM for SAP Solutions relevant system components

•

Web Services and other OpenText components Go to Control Panel > Add/Remove Programs or Programs and Features. In the list of programs, you see which version is installed.

•

SAP System, Database information and OpenText Components In the SAP IMG (transaction SPRO, OpenText Extended ECM for SAP Solutions > Extended ECM > Configuration Report), run the Configuration Report to get information about the SAP server. In this report, you find information like the versions of OTEXBAS, OTEXERP, OTEXRL, OTEXRLC, OTEXRLS, OTEXBASO, OTEXBASF, OTEXRLO, and OTEXRLF. For more information, see Section 20.1.3 “Understanding the Configuration Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

•

Support Package of installed SAP System In the SAP GUI application, from the menu, select System > Status. Then click Component information to see the installed SAP components with release number and highest support package. If you only want to know the version numbers of OTEXBAS, OTEXERP, OTEXRL, OTEXRLC, OTEXRLS, OTEXBASO, OTEXBASF, OTEXRLO, and OTEXRLF you could use this instead of the configuration report.

•

SAP Fiori apps For each application, there is a static version.html that includes the version number. To retrieve the file, enter the following in a browser: http(s)://:/sap/bc/ui5_ui5/otx//version.html

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 3

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.

3.1 Installation sequence for Extended ECM for SAP Solutions 1. In the SAP system, install the SAP packages: •

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

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

•

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.

In the Services section, keep the selections and select Extended ECM Web Services in addition. 3. Install the required patches, see the respective installation guides. Also check the installation medium for relevant patches. 4. Configure the following components : •

•

Configure Archive Center

•

Configure Content Server

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 3 Installing Extended ECM for SAP Solutions

•

Configure OpenText Directory Services (OTDS)

Configure modules 5. Configure Extended ECM for SAP Solutions: •

•

Set up security

•

Set up communication with Enterprise Library Services and OTDS

•

Configure Records Management (declaration, doctypes, jobs)

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 (ERLKCGD). 6. Install the clients: •

•

Install Imaging (Web Viewer, Windows Viewer, Enterprise Scan, DesktopLink, ExchangeLink, NotesLink), Brava! View for SAP Solutions, Brava! Server Components

•

Install Enterprise Connect Client (MS Windows Explorer/MS Outlook)

•

Install OpenText Administration Client

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 4

Installing the SAP package The following describes the installation of the OTEXRL component of Extended ECM for SAP Solutions and the optional components OTEXRLC, OTEXTRLS, OTEXRLO, and OTEXRLF on an SAP application server. Prerequisites

The component OTEXBAS of Archiving and Document Access for SAP Solutions must be installed on your SAP system. If you want to integrate into SAP Fiori, also the component OTEXBASF of Archiving and Document Access for SAP Solutions must be installed on your SAP system. Check the Release Notes for required versions of these components. See also “SAP prerequisites” on page 13 with general information on the installation in an SAP environment. To install the package: 1.

Copy the respective SAPCAR files (*.SAR) located on the installation medium in Extended ECM\SAP to the target SAP application server in the /usr/sap/trans folder, which is the parent folder of the DIR_EPS_ROOT folder. SAP Release

File

Source path

Target path

SAP BASIS 700

OTEXRL_INST_1620_ INST_BAS_700\DAT /usr/sap/trans 700.SAR A\

SAP CRM 7.0

OTEXRLC_INST_162 0_700.SAR

INST_CRM_700\DA TA\

/usr/sap/trans

SAP SRM 7.0

OTEXRLS_INST_1620 INST_SRM_700\DA _700.SAR TA\

/usr/sap/trans

IW_BEP release 200 or SAP_GWFND 740/750

OTEXRLO_INST_162 0_700.SAR

INST_ODATA_700\ DATA

/usr/sap/trans

SAP_UI 740/750

OTEXRLF_INST_1620 INST_FIORI_740\D _740.SAR ATA

/usr/sap/trans

Extract the SAPCAR files to the /usr/sap/trans/EPS/in folder with the following command:

SAPCAR -xvf

The resulting PAT files will be extracted to the EPS/in folder relative to the path of the SAPCAR files. Note: With Basis 7.00 or higher, you can use the SAINT and SPAM transactions to upload and extract the SAR files from the frontend.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 4 Installing the SAP package

Carry out import of package as described in the respective SAP documentation. For this, you will need the password for the package. For more information, see “Installation packages and passwords” on page 17.

After the installation, you must activate a Business Configuration Set (BC set) for every client. To activate the BC set: 1.

Start the SCPR20 transaction. The Business Configuration Set screen appears.

Activate the following BC Set: •

/OTEXRL/RM_SEA

Note: For details, see the SAP documentation. 3.

If you experience errors during BC set activation, repeat the respective activation procedure up to 3 times.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 5

Generating roles New: The client-dependent data for the roles are no longer delivered with BC set /OTEXRL/RM_LINK_02. The following relevant 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 transaction PFCG.

On the Utilities menu, click Mass Generation.

Select Roles with Non-Current Profiles and in the Role field, enter /OTX/RM*. After an upgrade, Roles with Current Profiles for New Generation and in the Role field, enter /OTX/RM* to generate updated profiles.

Follow the steps to generate the profiles.

After an upgrade, perform a mass comparison: a. b. c.

Start transaction PFCG and check the following roles one by one: • • • •

On the Utilities menu, click Mass Comparison. As role, enter /OTX/RM* and select Cleanups. Follow the steps to do a mass comparison.

/OTX/RM_ADMIN /OTX/RM_CS_SAP_USER /OTX/RM_USER /OTX/RM_IMPERSONATED_USER_ROLE

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 6

Installing language packages in the SAP system This chapter describes how to install language packages in an SAP system. Note: Depending on the delivery bundle, you may also have an ISO image file containing installation files for components that must not be installed on an SAP system. The Add-On installation packages include the default language, which is English. You must use the language packages to install other languages. For more information about available languages, see Extended ECM for SAP Solutions Release Notes. You can find the language packages related to the SAP Add-Ons of Extended ECM for SAP Solutions on OpenText My Support (https://knowledge.opentext.com/ knowledge/cs.dll?func=ll&objId=8521552&objAction=browse). To install a language package: 1.

On OpenText My Support, go to OpenText Extended ECM for SAP Solutions (https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=8521552& objAction=browse) and then go to the > Downloads area. Note that you can also obtain the language packages for support packages and other patches navigating through the Patches area. Do one of the following: •

If you have installed the installation Add-Ons, select and open the folder for your version. Open the Language Packs folder, select and open your language folder, and then download the Extended_ECM__.zip file that contains the language packages as *.SAR files.

For more details, see the text file stored with the corresponding language package file in the language folder. 2.

Upload your language file to your SAP system. Each ABAP Add-On has a specific language package. Example: OTEXRLDE30502_0000001 contains the German package for the OTEXRL 1002_700 Add-On on SAP_BASIS 7.00.

Note: Note the following options: •

If you use a system with SAP_BASIS 7.00, you can import and extract the file directly in transaction SMLT.

•

If you use any other system or prefer the manual handling, extract the SAPCAR file with the .SAR extension to the SMLT path folder of your SAP system. Usually the path is set to the EPS\in system folder. Use the SAPCAR tool to extract the file.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 6 Installing language packages in the SAP system

Use transaction SMLT to import your language package. Important Before starting to import language packages, OpenText recommends reading the SAP help (http://help.sap.com/) about importing a language. In the SAP help, navigate to the application help for the appropriate SAP release and read the following chapters:

•

Preparing to Import a Language

•

Importing a Language

•

Language Import with Transaction SMLT

•

Post-Import Actions

After installing the language package, perform the necessary post-installation steps, for example, such as those described in sections Language Supplementation/ Client Maintenance in the SAP help (http://help.sap.com/). Note that the language package contains client dependent data which requires specific action Client maintenance in transaction SMLT. Note: After importing language packages to the SAP system, it can become necessary to reset certain buffers. For example, you can use the following transactions: •

/$SYNC - Reset all buffers

•

/$OTR - Reset OTR text buffers (HTTP texts)

•

/$CUA - Reset SAP GUI object buffers

•

/$DYNP - Reset SAP GUI dynpro buffers

Note: Localization of Fiori apps Starting with version 16.2 the Fiori apps contained in the Fiori UI Add-on packages OTEXBASF and OTEXRLF deliver i18n properties files, which are mapped to text tables on the SAP system. Therefore specific language packages for Add-On packages OTEXBASF and OTEXRLF will be available in OpenText My Support. The procedure of installation is the same as described above.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 7

Installing the Content Server modules The installation procedure closely resembles the procedure for any other Content Server optional module.

7.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 \staging directory using the master setup. 2. Installing the modules into Content Server using the Install Modules page of Content Server's administration interface.

7.2 Installing Content Server and modules files Important If you install on a Unix 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 file (Mastersetup for Unix) located on the installation medium and accept the license agreement. Tip: The installation procedure for Unix systems is similar to the Windows based installation as described here.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 7 Installing the Content Server modules

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

7.2. Installing Content Server and modules files

Under Content Server and Modules, verify that the Connected Workspaces, Extended ECM for SAP Solutions, and the Extended ECM Platform entries are selected. As the Enforce selection dependencies checkbox is selected as default, all the dependent modules will be selected as well.

Click Next. If more than one Content Server instance is installed, select the one to which you want to add the Connected Workspaces module.

Check your entries in the Summary pane and click Install.

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 file again selecting another Content Server instance.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 7 Installing the Content Server modules

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

Caution The installation fails if you check all listed modules simultaneously for installation. Notes •

Before you install the modules, check that the following modules are already installed correctly: • • •

•

Case Management Content Server Document Templates Initiate Workflow from Item

The rest of the listed modules do not need to be installed for getting started if there is no specific requirement that needs the modules.

To install Content Server modules: 1.

Open the Content Server Administration page in a Web browser.

If prompted, enter the Content Server Administrator password in the Administrator password field and click Log-in.

Select Module Administration > Install Modules.

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.

After the installation of the selected modules is completed, Content Server displays the Restart Content Server page. Restart the server instance of Content Server. Recommended order of installation Note: Always restart the server instance of Content Server between the steps. 1. Required modules with no dependencies. For example, Customizations Run Time Environment, Content Server Generic Wizard, Calendar Attribute

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

7.3. Installing the Content Server modules

2. Modules that depend on modules installed in the first step. For example, Follow Up Management, Records Management 3. Modules that depend on modules installed in the second step. For example, Extensions for Enterprise Library, Content Server Document Templates 4. Modules that depend on modules installed in the third step. For example, Content Server - Case Management Base Modules 5. Modules that depend on modules installed in the fourth step. For example, Case Management Base Roles Wizard 6. Modules that depend on modules installed in the fifth step. For example, Case Management 7. Connected Workspaces 8. Extended ECM Platform 9. Extended ECM for SAP Solutions

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 8

Installing language packs on Content Server This chapter describes how to install language packs on Content Server. The module installation packages and module support packages include the default language, which is English. You must use the language packs to install other languages. For more information about available languages, see the Release Notes. Language packages for support packages If not stated otherwise, the language packs related to support packages are cumulative. They include merged language texts of the main version and of previous and current support packages. The language packs are available on OpenText My Support at the following location: OpenText My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/ 63201449) Note: Depending on the delivery bundle, you may also have an ISO image file containing installation files for components that must not be installed on Content Server, for example, language installations of Imaging clients and the SAP language package. For more information, see the installation guides and release notes for these components. To install a language pack: 1.

Download the language packs from OpenText My Support. You can also obtain the language packs for support packages and other patches navigating through the Patches area. On the ISO image, the relevant files for the language packs are available in the

OpenText Content Server and Modules folder.

Unzip the files for the relevant modules in the root Content Server installation directory.

On the Content Server Administration page, go to Languages > Install Language Packs.

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.

Restart your servers when prompted.

Click Continue.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 9

Deploying Extended ECM Web Services 9.1 Deploying Extended ECM Web Services into the application server Install the Extended ECM Web Services on your Tomcat server. Note: Make sure that your server has a sufficient initial memory pool. Refer to Section 2.2.2 “Configuring Java options” in OpenText Enterprise Library Installation and Upgrade Guide (EL-IGD) for memory pool size recommendations. The server must be running during the installation. To deploy Extended ECM Web Services: 1.

Run the Mastersetup.exe file (Mastersetup for Unix) located on the installation medium and accept the license agreement.

Select Advanced Deployment (Custom Selection) and click Next.

Under Services, select the Extended ECM Web Services entry. As the Enforce selection dependencies checkbox is selected as default, all the dependent services will be selected as well.

Click Next and click Install.

Restart Tomcat manually once after the installation.

Only Unix systems: After deploying the services, change the directory of the log files. a. b.

Open the /webapps/otsapxecm/WEB-INF/classes/log4j.xml file. Change the line to

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 9 Deploying Extended ECM Web Services

Figure 9-1: Deployment Scenario

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

9.2. Deploying Content Web Services

Figure 9-2: Services

9.2 Deploying Content Web Services Extended ECM for SAP Solutions requires OpenText Content Web Services. During the setup of Content Server, the Content Web Services WAR file is placed in the /webservices/java directory. You can deploy Content Web Services in IIS or in Tomcat automatically using the Content Server installer. If you use the setup, keep the default value cws. If you do not use the installer, deploy Content Web Services as follows. To deploy Content Web Services: 1.

Copy the cws.war file into your /webapps directory.

Only Unix systems: After deploying the services, change the directory of the log files. a.

Open the [tomcat]/webapps/cws/WEB-INF/classes/log4j.xml file

Change the line to .

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 9 Deploying Extended ECM Web Services

9.3 Configuring host and port for Content Server in Tomcat After installation of the Apache Tomcat web server, and deployment of the Extended ECM Web service, the server name is localhost with port 2099. You can change these settings, for example if you need to address more than one Content Server instance. To change host name and port of Content Server: 1.

Open the \webapps\otsapxecm\WEB-INF\web.xml file in an editor.

Find the following elements and change the values according to your needs:

LivelinkServer localhost

LivelinkServerPort 2099

LivelinkEncoding UTF8

Restart the application for the changes to take effect.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Part 2 Upgrading Extended ECM for SAP Solutions

This part outlines the different upgrade scenarios.

•

“Upgrade scenarios“ on page 43

•

“General recommendations for the upgrade“ on page 47

•

“Upgrading from Extended ECM for SAP Solutions 16 to 16.2“ on page 49

•

“Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2“ on page 65

•

“Upgrading from ECMLink 10.0.3, 10.0.4, or 10.5.0“ on page 81

•

“Upgrading from ECMLink 9.8.x, 10.0, or 10.0 SP1 or SP2“ on page 83

•

“Upgrading from versions prior to 9.8“ on page 85

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 10

Upgrade scenarios There are different upgrade scenarios depending on the Content Server version from which you upgrade. Table 10-1: Upgrade from ECMLink 10.5.1 or Extended ECM for SAP Solutions 16 to Extended ECM for SAP Solutions 16.2 Old Content Server version

Old module version

New Content Server version

New Connected New Extended Workspaces ECM for SAP module version Solutions SAP Add-on version

Content Server 10.5 SP1

ECMLink 10.5.1

Content Server 16.2

Connected Extended ECM Workspaces 16.2 for SAP Solutions 16.2 Extended ECM Platform 16.2 Extended ECM for SAP 16.2

Content Server 16

Connected Workspaces 16

Content Server 16.2

Connected Extended ECM Workspaces 16.2 for SAP Solutions 16.2 Extended ECM Platform 16.2 Extended ECM for SAP 16.2

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 10 Upgrade scenarios

Figure 10-1: Upgrade from ECMLink 10.5.1 or Extended ECM for SAP Solutions 16 or to Extended ECM for SAP Solutions 16.2

10.1 Supported combinations You can split up the upgrade to two maintenance windows. You can either update the Content Server system first or the SAP system first. The new Content Server system will also be working with an SAP system that is not updated yet and vice versa. . “Supported combinations” on page 44 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. For the different combinations, there may be limitations. For information about all known issues, see the Release Notes. Table 10-2: Supported combinations

Content Server version

Content Server module version

SAP Add-on version Limitations for different SAP Systems

10.5

10.5.1

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

10.1. Supported combinations

Content Server version

Content Server module version

SAP Add-on version Limitations for different SAP Systems

10.5

10.5.1

16.2

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 11

General recommendations for the upgrade When you perform an upgrade, you have to upgrade the various components of Extended ECM for SAP Solutions. New The product, components, and administration activities have been renamed as follows: •

The product ECMLink is now Extended ECM for SAP Solutions.

•

The Content Server module ECMLink is now Connected Workspaces. In addition, there are the modules Extended ECM Platform and Extended ECM for SAP Solutions.

•

ECMLink Web Services are now Extended ECM Web Services.

•

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. The ISO image contains all supported components. The master setup does not show all of them.

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.

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 in the SAP system.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 11 General recommendations for the upgrade

The other way is supported, too. For more information, see “Supported combinations” on page 44. c. d.

Note the exact procedure with all necessary steps. Perform the upgrade on the test system. Follow exactly the steps you noted to verify the procedure. If necessary, adapt the list. Perform the upgrade on the productive system. OpenText recommends to have two maintenance windows: The first for the upgrade of Content Server and all related components, the second for the components in the SAP system. The other way is supported, too. For more information, see “Supported combinations” on page 44.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 12

Upgrading from Extended ECM for SAP Solutions 16 to 16.2 “Supported combinations” on page 44 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.

12.1 Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2 Table 12-1: Upgrade checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2 (Content Server and modules first) Step

System and Tools

Information

Upgrading to Content Server 16.2 and Content Server module Prepare your system for the upgrade

All OpenText systems

For more information, see Section 5 “Upgrading Enterprise Library” in OpenText Enterprise Library Installation and Upgrade Guide (EL-IGD) and the linked guides.

Migrate OpenText Directory Services to version 16.2

Server on which Directory Services is installed, using Administration Client, and Content Server

For more information, see Section 1.3 “Importing data from previous versions of OpenText Directory Services to 16” in OpenText Directory Services - Installation and Administration Guide (OTDSIWC).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Upgrade and configure Archive Center

Archive Center

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

(only relevant if you are using Document Pipelines): Upgrade Document Pipelines.

•

Use Directory Services authentication.

•

Use the new resource ID that was created for Archive Center during Directory Services migration.

For more information, see OpenText Document Pipeline Installation and Upgrade Guide (AR-IDPDP)

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Upgrade Content Server and Enterprise Library Services

Content Server

Make a copy of the Content Server installation directory first. For more information, see Section 1.3 “Preparing Content Server in your Source Environment” in OpenText Content Server Upgrade Guide (LLESCORIUP). Uninstall the old Content Server version and delete the installation directory. Install the new version in a directory with the same name. To upload the certificate, open the Administration Client and connect with the server and navigate to Enterprise Library Services > Configuration. For information about Enterprise Library Services, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD), and the linked guides. To view the certificates, open the Administration Client, connect with Archive Center, and navigate to System > Key Store > Certificates. The CS_ELIB_ certificates displays on the Global tab.

Install the Updates for Content Server and Archive Center, and finish the Archive Center configuration

Install the new Connected Workspaces module and all other modules that were installed before.

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides. Content Server

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

For more information, see “Installation procedure on Content Server” on page 29.

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

If you are working with appearances, update the relevant path

Information With the upgrade, the appearances are automatically renamed from SAPBASE_* to EXTENDED_ECM_*. In the content of all relevant appearances, in the header, replace sapbase with otsapxecm. If you are performing an inparallel upgrade of Content Server, run the following tool to ensure that the configuration is updated correctly: http://server/otcs/ cs.exe? func=otsapxecm.Config ure&module=otsapxecm

Deploy the Extended ECM Web Services

For more information, see “Deploying Extended ECM Web Services into the application server” on page 37.

Connect the new Content Server with the old database and upgrade the database.

Content Server

Connect the old database and upgrade it. For more information, see Section 1.5.1 “Upgrading your Content Server Database” in OpenText Content Server - Upgrade Guide (LLESCOR-IUP).

Upgrade the database schema

Content Server

“Upgrading the database schema” on page 62

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

For the Template Workspaces Content Server module, perform the configuration upgrade and the data upgrade

This step is required if your previous version was Template Workspaces 10.1, Contract Management 10.1, Case Management Framework 1.1.0, 10.0.0 or Contract Management 2.1.1. Additionally, in the Template Workspace Administration section, you need to do the upgrade step. Make sure the LivelinkDocumentTempl ates 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 Section 3 “Upgrading Template Workspaces from the Admin page” in OpenText Template Workspaces - Installation and Administration Guide (LLESCSB-IGD)

Perform post-upgrade steps in the SAP system

•

SAP system

•

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Change the logical port for Content 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 117.

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Directory Services

Directory Services

•

Update the Content Server resource 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 6.3 “Creating and configuring resources for Directory Services” in OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLKCUM)

If you encounter problems, re-create the Content Server resource. Perform post-upgrade steps in Content Server

Content Server

If there is a change in the Archive Center port or system, update the setting in Content Server in the Archive Storage Provider settings.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Archive Center

Archive Center

Upload the relevant certificates and enable them for Archive Center and for the logical archives. The following certificates are relevant: •

•

CS_ELIB_: Enterprise Enterprise Library Services certificate SP_: Archive Storage Services certificate

For more information, see Section 4.8 “Configuring security settings and connection details” in OpenText Enterprise Library Installation and Upgrade Guide (EL-IGD) and Section 5.2 “Starting services and concluding upgrade” in OpenText Enterprise Library Installation and Upgrade Guide (EL-IGD) 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 further. Upgrading the SAP Add-on Upgrade Extended ECM for SAP Solutions Add-on from 16 to 16.2

SAP system

“Upgrading to Extended ECM for SAP Solutions in the SAP system” on page 63

Upgrade the Fiori Add-On from 16 to 16.2

SAP system

Do the upgrade in the same maintenance window or before if you already have an SAP Fiori Gateway with Business Workspace app 16 running against an SAP Backend which is updated from 16 to 16.2.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

If the connection test on Content Server does not work, configure the Service Provider Interface again.

SAP system

Information Do one of the following: •

Create a new web service binding in the SOAMANAGER and switch all the 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 116. Also recreate the logical ports and activate them. For more information, see “Creating logical ports in the SAP system” on page 99 Perform post-installation steps

Content Server and SAP system

Perform post-installation steps. For more information, see “Post-installation and post-upgrade tasks” on page 87.

Verify the installation

SAP system

Run the Diagnostics Program. For more information, see “Understanding the SAP Diagnostic Program” on page 137.

Table 12-2: Upgrade checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2 (SAP system first) Step

System and Tools

Information

SAP system

“Upgrading to Extended ECM for SAP Solutions in the SAP system” on page 63

Upgrading the SAP Add-on Upgrade Extended ECM for SAP Solutions Add-on from 16 to 16.2

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Upgrade the Fiori Add-On from 16 to 16.2

SAP system

Do the upgrade in the same maintenance window or before if you already have an SAP Fiori Gateway with Business Workspace app 16 running against an SAP Backend which is updated from 16 to 16.2.

Install the newest cumulative Content Server patch for Extended ECM for SAP Solutions and other relevant patches.

Refer to the Release Notes for 16 for information about the current cumulative patch. Download the patch from OpenText My Support (https:// knowledge.opentext.com/ knowledge/llisapi.dll/open/ 16514655).

After this maintenance window and all relevant steps, the SAP system works with the old Content Server module. Upgrading to Content Server 16.2 and newest Content Server module Prepare your system for the upgrade

All OpenText systems

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

Migrate OpenText Directory Services to version 16

Server on which Directory Services is installed and Content Server

Upgrade and configure Archive Center

Archive Center

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides. • •

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Use Directory Services authentication. Use the new resource ID that was created for Archive Center during Directory Services migration.

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

(only relevant if you are using Document Pipelines): Upgrade Document Pipelines. Upgrade Content Server and Enterprise Library Services

Information For more information, see OpenText Document Pipeline Installation and Upgrade Guide (AR-IDPDP).

Content Server

Install the Updates for Content Server and Archive Center, and finish the Archive Center configuration

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

If you are working with appearances, update the relevant path

Deploy the Extended ECM Web Services

For more information, see “Deploying Extended ECM Web Services into the application server” on page 37

Connect the new Content Server with the old database and upgrade the database.

Content Server

Connect the old database and upgrade it. For more information, see Section 1.5.1 “Upgrading your Content Server Database” in OpenText Content Server - Upgrade Guide (LLESCOR-IUP).

Upgrade the database schema

Content Server

“Upgrading the database schema” on page 62

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

For the Template Workspaces Content Server module, perform the configuration upgrade and the data upgrade

This step is required if your previous version was Template Workspaces 10.1, Contract Management 10.1, Case Management Framework 1.1.0, 10.0.0 or Contract Management 2.1.1. Additionally, in the Template Workspace Administration section you need to do the upgrade step. Make sure the LivelinkDocumentTempl ates 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 Section 3 “Upgrading Template Workspaces from the Admin page” in OpenText Template Workspaces - Installation and Administration Guide (LLESCSB-IGD)

Perform post-upgrade steps in Directory Services

•

Update the Content Server resource settings to point to the new systems.

•

Update the Content Server resource settings to point to Content Web Services cws instead of les-services.

Directory Services

For more information, see Section 6.3 “Creating and configuring resources for Directory Services” in OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLKCUM) If you encounter problems, re-create the Content Server resource.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

12.1. Checklist for upgrade from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Content Server

Content Server

If there is a change in the Archive Centerport or system, update the setting in Content Server in the Archive Storage Provider settings.

Perform post-upgrade steps in Archive Center

Archive Center

Upload the relevant certificates and enable them for Archive Center and for the logical archives. The following certificates are relevant: •

•

CS_ELIB_: Enterprise Library Services certificate SP_: Archive Storage Services certificate

Clients

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

Perform post-upgrade steps in the SAP system

SAP system

•

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Change the logical port for Content Server Member Services from les-services to cws. Update the Enterprise Library settings to point to the new systems. For more information, see “Maintaining Extended ECM connections” on page 117.

Chapter 12 Upgrading from Extended ECM for SAP Solutions 16 to 16.2

Step

System and Tools

If the connection test on Content Server does not work, configure the Service Provider Interface again.

SAP system

Information Do one of the following: •

Create a new web service binding in the SOAMANAGER and switch all the 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.

SAP system

Perform the remaining postinstallation steps. For more information, see “Postinstallation and post-upgrade tasks” on page 87.

Verify the installation

SAP system

Run the Diagnostics Program. For more information, see “Understanding the SAP Diagnostic Program” on page 137.

12.2 Upgrading the database schema New: The database schema is now upgraded with the standard Content Server mechanism. The current version of the Connected 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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

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

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_.log. It logs all SQL statements of the upgrade.

12.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. So 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 S/4HANA which is supported 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 prerequisites” on page 13.

•

Install the relevant packages for Archiving and Document Access for SAP Solutions 16.2 with the SAINT tool.

•

Install the relevant packages for OpenText Extended ECM for SAP Solutions 16.2 with the SAINT tool. For more information, see “Installation procedure on Content Server” on page 29.

•

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

•

Activate the BC sets. For more information, see “Installing the SAP package“ on page 23.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 13

Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2 “Supported combinations” on page 44 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.

13.1 Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2 Table 13-1: Upgrade checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2 (Content Server and modules first) Step

System and Tools

Information

Upgrading to Content Server 16.2 and Content Server module Prepare your system for the upgrade

All OpenText systems

For more information, see Section 5 “Upgrading Enterprise Library” in OpenText Enterprise Library Installation and Upgrade Guide (EL-IGD) and the linked guides.

Migrate OpenText Directory Services to version 16.2

Server on which Directory Services is installed, using Administration Client, and Content Server

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Upgrade and configure Archive Center

Archive Center

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

(only relevant if you are using Document Pipelines): Upgrade Document Pipelines.

•

Use Directory Services authentication.

•

Use the new resource ID that was created for Archive Center during Directory Services migration.

For more information, see OpenText Document Pipeline Installation and Upgrade Guide (AR-IDPDP)

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Upgrade Content Server and Enterprise Library Services

Content Server

Install the Updates for Content Server and Archive Center, and finish the Archive Center configuration

Install the new Connected Workspaces module and all other modules that were installed before.

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides. Content Server

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

For more information, see “Installation procedure on Content Server” on page 29.

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

If you are working with appearances, update the relevant path

Deploy the Extended ECM Web Services

For more information, see “Deploying Extended ECM Web Services into the application server” on page 37.

Connect the new Content Server with the old database and upgrade the database.

Content Server

Connect the old database and upgrade it. For more information, see Section 1.5.1 “Upgrading your Content Server Database” in OpenText Content Server - Upgrade Guide (LLESCOR-IUP).

Upgrade the database schema

Content Server

“Upgrading the database schema” on page 78

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

For the Template Workspaces Content Server module, perform the configuration upgrade and the data upgrade

Perform post-upgrade steps in the SAP system

•

SAP system

•

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Directory Services

Directory Services

•

If you encounter problems, re-create the Content Server resource. Perform post-upgrade steps in Content Server

Content Server

If there is a change in the Archive Center port or system, update the setting in Content Server in the Archive Storage Provider settings.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Archive Center

Archive Center

Upload the relevant certificates and enable them for Archive Center and for the logical archives. The following certificates are relevant: •

•

CS_ELIB_: Enterprise Enterprise Library Services certificate SP_: Archive Storage Services certificate

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 further. There are some restrictions though: • •

For all SAP systems: No integration widget support. SAP Fiori Extended ECM: No support

Upgrading the SAP Add-on Upgrade Extended ECM for SAP Solutions Add-on from 10.5.1 to 16.2

SAP system

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

“Upgrading to Extended ECM for SAP Solutions in the SAP system” on page 79

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

If the connection test on Content Server does not work, configure the Service Provider Interface again.

SAP system

Information Do one of the following: •

Create a new web service binding in the SOAMANAGER and switch all the 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.

Content Server and SAP system

Perform post-installation steps. For more information, see “Post-installation and post-upgrade tasks” on page 87.

Verify the installation

SAP system

Run the Diagnostics Program. For more information, see “Understanding the SAP Diagnostic Program” on page 137.

Table 13-2: Upgrade checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2 (SAP system first) Step

System and Tools

Information

SAP system

“Upgrading to Extended ECM for SAP Solutions in the SAP system” on page 79

Upgrading the SAP Add-on Upgrade Extended ECM for SAP Solutions Add-on from 10.5.1 to 16.2

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Install the newest cumulative Content Server patch for ECMLink 10.5.1 and other relevant patches.

Information Refer to the Release Notes for 10.5 SP1 for information about the current cumulative patch. Download the patch from OpenText My Support (https:// knowledge.opentext.com/ knowledge/llisapi.dll/open/ 16514655).

After this maintenance window and all relevant steps, the SAP system works with the old Content Server module. There are some restrictions though: •

For all SAP systems: No integration widget support.

Upgrading to Content Server 16.2 and newest Content Server module Prepare your system for the upgrade

All OpenText systems

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

Migrate OpenText Directory Services to version 16.2

Server on which Directory Services is installed and Content Server

Upgrade and configure Archive Center

Archive Center

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides. • •

(only relevant if you are using Document Pipelines): Upgrade Document Pipelines.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Use Directory Services authentication. Use the new resource ID that was created for Archive Center during Directory Services migration.

For more information, see OpenText Document Pipeline Installation and Upgrade Guide (AR-IDPDP).

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Upgrade Content Server and Enterprise Library Services

Content Server

Install the Updates for Content Server and Archive Center, and finish the Archive Center configuration

For more information, see Section 5.1 “Upgrade roadmap” in OpenText Enterprise Library - Installation and Upgrade Guide (EL-IGD) and the linked guides.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

If you are working with appearances, update the relevant path

Deploy the Extended ECM Web Services

For more information, see “Deploying Extended ECM Web Services into the application server” on page 37

Connect the new Content Server with the old database and upgrade the database.

Content Server

Connect the old database and upgrade it. For more information, see Section 1.5.1 “Upgrading your Content Server Database” in OpenText Content Server - Upgrade Guide (LLESCOR-IUP).

Upgrade the database schema

Content Server

“Upgrading the database schema” on page 78

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

For the Template Workspaces Content Server module, perform the configuration upgrade and the data upgrade

This step is required if your previous version was Template Workspaces 10.1, Contract Management 10.1, Case Management Framework 1.1.0, 10.0.0 or Contract Management 2.1.1. Additionally, in the Template Workspace Administration section you need to do the upgrade step. Make sure the LivelinkDocumentTempl ates 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 Section 3 “Upgrading Template Workspaces from the Admin page” in OpenText Template Workspaces - Installation and Administration Guide (LLESCSB-IGD)

Perform post-upgrade steps in Directory Services

•

Update the Content Server resource settings to point to the new systems.

•

Update the Content Server resource settings to point to Content Web Services cws instead of les-services.

Directory Services

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

13.1. Checklist for upgrade from ECMLink 10.5.1 with Content Server 10.5 SP1 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

Information

Perform post-upgrade steps in Content Server

Content Server

If there is a change in the Archive Centerport or system, update the setting in Content Server in the Archive Storage Provider settings.

Perform post-upgrade steps in Archive Center

Archive Center

Upload the relevant certificates and enable them for Archive Center and for the logical archives. The following certificates are relevant: •

•

CS_ELIB_: Enterprise Library Services certificate SP_: Archive Storage Services certificate

Clients

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

Perform post-upgrade steps in the SAP system

SAP system

•

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 13 Upgrading from ECMLink 10.5.1 with Content Server 10.5 to Extended ECM for SAP Solutions 16.2

Step

System and Tools

If the connection test on Content Server does not work, configure the Service Provider Interface again.

SAP system

Information Do one of the following: •

Create a new web service binding in the SOAMANAGER and switch all the 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.

SAP system

Perform the remaining postinstallation steps. For more information, see “Postinstallation and post-upgrade tasks” on page 87.

Verify the installation

SAP system

Run the Diagnostics Program. For more information, see “Understanding the SAP Diagnostic Program” on page 137.

13.2 Upgrading the database schema New: The database schema is now upgraded with the standard Content Server mechanism. The current version of the Connected 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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

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

13.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. So 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 S/4HANA which is supported 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 prerequisites” on page 13.

•

Install the relevant packages for Archiving and Document Access for SAP Solutions 16.2 with the SAINT tool.

•

Install the relevant packages for OpenText Extended ECM for SAP Solutions 16.2 with the SAINT tool. For more information, see “Installation procedure on Content Server” on page 29.

•

Activate the BC sets. For more information, see “Installing the SAP package“ on page 23.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 14

Upgrading from ECMLink 10.0.3, 10.0.4, or 10.5.0 For an upgrade from ECMLink 10.0.3 or 10.0.4 on Content Server 10 first upgrade to ECMLink 10.0.5 and then to Extended ECM for SAP Solutions 16. For an upgrade from ECMLink 10.5.0 on Content Server 10.5, first upgrade to ECMLink 10.5.1 and then to Extended ECM for SAP Solutions 16. To perform the upgrade refer to this guide for version 10.5.1 and the guides for related components. After this, perform the upgrade as described above. Note: Contact your OpenText consultant for planning your individual upgrade strategy.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 15

Upgrading from ECMLink 9.8.x, 10.0, or 10.0 SP1 or SP2 For an upgrade from version of ECMLink 9.8.x, 10.0.0, 10.0.0 SP1, or 10.0.0 SP2 first upgrade to ECMLink 10.0.3, then to ECMLink 10.5.1 and then to Extended ECM for SAP Solutions 16. To perform the upgrade refer to this guide for version 10.0.2 and the guides for related components. After this, perform the upgrade as described above. Note: Contact your OpenText consultant for planning your individual upgrade strategy.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 16

Upgrading from versions prior to 9.8 There is no direct upgrade from any of the following previous OTEXRL add-on versions: •

Livelink ECM - Records Management for SAP Solutions 9.6.0

•

Open Text Extended ECM for SAP Solutions 9.6.1

•

Open Text - RMLink for SAP Solutions 9.7.0

If one of these older versions is already installed on your SAP system, you have to follow an upgrade path which leads you to version 10.0.3 before further upgrade to the newest version. Depending on the original version you start from, there may be SAP system upgrades required. Note: Contact your OpenText consultant for planning your individual upgrade strategy.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Part 3 Post-installation and post-upgrade tasks

This part explains the tasks that you perform after the installation.

•

“Performing general post-installation tasks in SAP“ on page 89

•

“Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0“ on page 95

•

“Performing post-installation or post-upgrade tasks in Content Server“ on page 123

•

“Verifying the installation“ on page 137

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 17

Performing general post-installation tasks in SAP Before using the Extended ECM for SAP Solutions functions, you have to perform a series of post-installation and customizing tasks in SAP: •

“Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0“ on page 95

Apart from the general guide to the IMG function, the following generic task is covered in the following: •

“Assigning SAP roles” Note: For information on the scenario-specific post-installation tasks, see OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

17.1 Using the IMG function Extended ECM for SAP Solutions provides a central customizing menu in SAP in the OpenText Extended ECM for SAP Solutions structure of SAP’s Customizing Implementation Guide (IMG) function. To call the IMG: 1.

Run the SPRO transaction.

Click SAP Reference IMG.

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 17 Performing general post-installation tasks in SAP

Select the required activity and click

Execute.

If an SAP system displays a different IMG structure rather than standard reference IMG, the Extended ECM for SAP Solutions customizing is not visible. You have the following options to access the Extended ECM for SAP Solutions customizing structure: •

Use transaction SIMGH, save the Extended ECM for SAP Solutions IMG structure as a favorite and call it from there.

•

Add the Extended ECM for SAP Solutions customizing to the existing customizing structure of transaction SPRO.

To use transaction SIMGH to access Extended ECM for SAP Solutions customizing:

Run the SIMGH transaction.

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.

Double-click on entry.

Click Add to Favorites.

In the Favorites list, select one entry and click

to access the IMG structure.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

17.1. Using the IMG function

To add the IMG structure to SPRO transaction: 1.

Create an enhancement ID: a.

Run the S_IMG_EXTENSION transaction.

Open the search help of field Enhancement ID.

Click

Enter an Enhancement ID, for example Z_OTX_EXTECM, and an explanatory text, for example OpenText Extended ECM.

Click

Save.

Click

Continue.

Double-click the newly created enhancement ID in the Enhancement ID: Original list to select it for the Enhancement ID field.

Create Enhancement ID (F5).

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.

Click Favorite to add the IMG structure to your favorites.

Select the IMG structure in the Favorites list by double clicking.

If not already done, in field Enhancement ID, select the enhancement ID created in Step 1.

Click Enhance Structure.

Select the root node of the IMG structure.

From the menu, select Edit > Nodes > Insert IMG Structure > As Subnode.

Enter the node name for the customizing, for example OpenText Extended ECM for SAP Solutions.

Find structure to search for the Extended ECM for SAP Solutions Click customizing IMG structure. Search for OpenText - Extended ECM for SAP Solutions.

Click

Copy.

Click

Save.

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 17 Performing general post-installation tasks in SAP

17.2 Assigning SAP roles In order to use the Extended ECM for SAP Solutions functions in SAP, you must assign specific roles in SAP. The following roles are required: Notes •

If you do not want to use these roles, you must assign the respective authorization objects to your own roles.

•

If you want to use field values other than those recommend here, field help provides additional information.

/OTX/RM_USER

Role for Extended ECM for SAP Solutions application users. This role allows an SAP user declare ArchiveLink documents as records, search Content Server, display a business workspace in the Business Content window, and show record details. This role contains the following authorizations objects: Authorization object

Description

/OTX/RM

Records management authorizations in GOS Set field /OTX/RMACT to value 00 or * for granting access to functionality related to Records Management.

J_6NRL_DOL

Business attachments authorizations Set field /OTX/RMDAC to value 00 for granting access to business-attachmentsrelated functionality.

J_6NRL_WSC

Business workspace authorizations Set field /OTX/RMWAC to value 00 for granting access to business-workspacerelated functionality.

J_6NRL_LFS

Access to local Tempo Box folder and other local folders Set field /OTX/RMLAC to value 00 for granting access to local files

S_GUI

Access to Drag & Drop functionality in Business Content window. Set field ACTVT to value 60 for granting access to drag and drop.

/OTX/RM_ADMIN

Role for SAP administrator; this role allows for the post-installation and customizing steps as well as administrative tasks like monitoring or running batch jobs.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

17.2. Assigning SAP roles

This role contains the following authorizations objects: Authorization object

Description

/OTX/RM

Records management authorizations in GOS

J_6NRL_DOL

Business attachments authorizations

J_6NRL_WSC

Business workspace authorizations

/OTX/RM_CS_SAP_USER

Role for the SAP system connection between Content Server and the SAP system. This role is needed for the SAP user which is configured in Content Server for the connection to SAP. For more information, see “Connecting an external system” on page 124.

/OTX/RM_IMPERSONATED_USER_ROLE

Role for the SAP user which is used in the RFC destination. For more information, see Section 6.7.1 “Enabling user-specific impersonation (SAP BAdI)” in OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLK-CUM).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 18

Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0 18.1 Exporting the SAP PSE certificate for the SAP authentication handler You need the SAP PSE certificate to create the SAP authentication handler in OpenText Directory Services. The SAP authentication handler validates SAP tickets sent from the SAP system against the exported certificate. You export the certificate in a PSE file from SAP using the Export System PSE Certificate to File System activity in the SAP IMG. To export the SAP PSE certificate: 1.

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Open the System PSE section and check whether there is a certificate in this folder. If this is not the case, create a new one; for details, see SAP Help Portal (http:// help.sap.com/saphelp_nw70/helpdata/de/0e/fb993af7700577e10000000a11402f/ frameset.htm).

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.

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.

Click Yes and copy the PSE file to an appropriate location on the Directory Services server.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.1. Exporting the SAP PSE certificate for the SAP authentication handler

Only if you want to use SAP SRM you must export the SAP certificate from an SAP SRM portal. To export the SAP PSE certificate from an SAP SRM Portal: In addition to the SAP server certificate, you must export a certificate for the portal. 1.

On the System Administration tab, go to System Configuration > Keystore Administration.

From the list, select SAPLogonTicketKeypair-cert.

Click Download verify.pse File and save the file to your desktop.

Unzip the downloaded file. Optionally, you can rename it to your system name, for example .pse.

Creating an SAP authentication handler in Directory Services The SAP authentication handler validates the user against the SAP PSE certificate and extracts user information from the SAP logon ticket. This is relevant for synchronized and non-synchronized partitions. You create the respective authentication handler using the Directory Services Administration web client. Note: For a detailed description of authentication handlers, see Section 5.2 “Creating an authentication handler” in OpenText Directory Services - Installation and Administration Guide (OTDS-IWC). To create an SAP authentication handler: 1.

Start Directory Services Administration in a web browser. Open http://

: Infrastructure > Activate HTTP Service activity and click Execute.

In the Hierarchy Type field, select SERVICE and click

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

Execute.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

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

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

18.3.1

Creating logical ports for SAP Basis 7.0 Extended ECM for SAP Solutions connects to OpenText components using HTTP connections and logical ports. You must create the following HTTP connections to the required web services: •

Enterprise Library

•

Extended ECM

•

OpenText Directory Services

•

Enterprise Library Content Services

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

•

Content Server Member Services

To create the HTTP connections: 1.

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

Click

Enterprise Library Services

Create.

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

Click

Customize the connection: •

Technical Settings tab Target host: Fully qualified host name of your Enterprise Library Services installation

100

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

Service No.: Enterprise Library Web Services port; port 8080 is typically used for Apache Tomcat. Path Prefix: /ot-elib/services/EnterpriseLibrary •

Logon & Security tab The options No Logon and Send SAP Logon Ticket must be enabled. See also SAP_BASIS component with a version higher than 16 on page 102.

Click Connection Test.

Check that the value in the Status HTTP Response field is 200 which indicates that the request was successful.

Save your settings.

Repeat steps 2 to 7 and create more HTTP connections according to the following table: Enterprise Library Services

Extended ECM OpenText Directory Services

Enterprise Library Content Services

RFC Destination

Enter a name for this connection, for example ELS_DEST_CO RE.

Enter a name, for example EXTECM_DEST.

Enter a name, for example ELCONTENT_D EST.

Connections Type

G (HTTP G (HTTP G (HTTP G (HTTP Connection to Connection to Connection to Connection to External Server) External Server) External Server) External Server)

Enter a name, for example OTDS_DEST.

Technical Settings tab

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

101

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Target host

Enterprise Library Services

Extended ECM OpenText Directory Services

Enterprise Library Content Services

Fully qualified host name of your Enterprise Library Services installation

Host name of your Extended ECM installation

Host name of the Enterprise Library Services installation.

Target host: Host name of your Directory Services (OTDS) installation. If you are using user-specific mapping with impersonation (SAP BAdI) and OpenText Directory Services and Enterprise Library Services and Content Server are installed on different servers, enter the host name of the Enterprise Library Services installation.

Service No.

Enterprise Library Web Services port; port 8080 is typically used for Apache Tomcat.

Extended ECM Web Services port

Directory Services Web Services port

Enterprise Library Content Services port

Path Prefix

/ot-elib/ services/ EnterpriseL ibrary

/otsapxecm/ services/ ECMLink

/ot-authws/ services/ Authenticat ion

/ot-elib/ services/ Content

The following settings are the same for all ports: •

On the Logon & Security tab, select No Logon and Send SAP Logon Ticket.

•

On the Messaging tab, in the Message ID Protocol field, select the Suppress ID Transfer value. SAP_BASIS component with a version higher than 16 If you are using a SAP_BASIS component with a version higher than 16, you might experience the following changes:

102

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

The Send SAP Logon Ticket is now called Send SAP Assertion Ticket and you must provide as destination system the system ID and the client of the current SAP system. If this is the case, you must also do the following: •

Ensure that the latest sapssoext.dll file is in the Tomcat\bin directory.

•

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

SAPSYSTEMNAME SAPSYSTEMCLIENT

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

Enterprise Library logical port

•

Extended ECM logical port

•

OpenText Directory Services logical port

•

Enterprise Library Content Services logical port

•

Content Server Member Services

To create a logical port for SAP Basis 7.0: 1.

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

Enterprise Library In the Proxy Class field, enter /OTX/CO_RMELENTERPRISE_LIBRARY.

Enter a new name in the Logical Port field, for example ELS_LOGICAL_PORT.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

103

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

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

Click

Enter a description for the logical port in the Description field. On the Call Parameters tab, enter your new HTTP destination created before for the Enterprise Library in the HTTP Destination field, for example ELS_DEST_CORE.

Click Check to check the new logical port. Check that the message in the status bar reads No errors found in configuration.

Click

Extended ECM

Create.

Save and

Activate (Ctrl + F3) to activate the logical port.

Repeat steps 2 to 8 to create a logical port for Extended ECM using the following values: •

Proxy Class Enter /OTX/CO_RM_WSW_ECMLINK.

•

Logical Port Enter the name of the logical port, for example ECMLINK_LOGICAL_PORT.

•

HTTP Destination Enter the HTTP destination created before, for example ECMLINK_DEST.

104

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

10. OpenText Directory Services Repeat steps 2 to 8 to create a logical port for OpenText Directory Services using the following values: •

Proxy Class Enter /OTX/CO_OTDSAUTHENTICATION.

•

Logical Port Enter the name of the logical port, for example OTDS_LOGICAL_PORT

•

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.

11. Enterprise Library Content Services Repeat steps 2 to 8 to create a logical port for Enterprise Library Content Services using the following values: •

Proxy Class Enter /OTX/CO_RMELCONTENT.

•

Logical Port Enter the name of the logical port, for example ELCONTENT_LOGICAL_PORT

•

HTTP Destination Enter the HTTP destination created before, for example ELCONTENT_DEST.

•

State Management Select this option for the Enterprise Library Content Services web service. If you did not select this option, you will get an according message during the connection check.

12. Content Server Member Services Optional Repeat steps 2 to 8 to create a logical port for Content Server Member Services using the following values: •

Proxy Class Enter /OTX/CO_MBLLMEMBER_SERVICE.

•

Logical Port Enter the name of the logical port, for example CSMEMBER_LOGICAL_PORT

•

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

105

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

•

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.

18.3.2

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

Enterprise Library

•

Extended ECM

•

OpenText Directory Services

•

Enterprise Library Content Services

•

Content Server Member Services

To create a logical port for SAP Basis 7.01 and higher: 1.

In the IMG, navigate to the OpenText Extended ECM for SAP Solutions > Infrastructure > Create New Logical Ports activity and click Execute. The SOA Management dialog opens.

On the Application and Scenario Communication tab, click Single Service Administration.

On the Search tab, change the Search by value to Consumer Proxy, enter a * in the Search Pattern field, and click Go.

106

In the Search Results pane, select the entry for EnterpriseLibrary (/OTX/

CO_RMELENTERPRISE_LIBRARY) and click Apply Selection.

On the Configurations tab, click Create Logical Port.

Enter a new name in the Logical Port Name field and add a description.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

Select Logical Port is Default if you have only one logical port for the Enterprise Library Services. If you have multiple logical ports for Enterprise Library Services, select this option only for one of the logical ports. For the Configuration Type, select Manual Configuration.

Click Apply Settings. The Web Service Configuration of Proxy Definition section is displayed.

Open the Consumer Security tab and select SAP Authentication Assertion Ticket.

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

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

URL Access Path:

/ot-elib/services/EnterpriseLibrary •

•

Computer Name of Access URL: Enterprise Library Services installation host name Port Number of Access URL: Enterprise Library Web Services port (usually

8080 for Tomcat)

Click Save. A message at the top of the screen indicates that the binding has been created. 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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

107

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Enterprise Library

Extended ECM

Authenticati Enterprise on Library Content Services

Content Server Member Service

Internal name

/OTX/ CO_RMELEN TERPRISE_ LIBRARY

/OTX/ CO_RM_WSW _ECMLINK

/OTX/ CO_OTDSAU THENTICAT ION

/OTX/ CO_RMELCO NTENT

/OTX/ CO_MBLLME MBER_SERV ICE

URL Access Path

/ot-elib/ services/ Enterpris eLibrary

/ otsapxecm / services/ ECMLink

/otauthws/ services/ Authentic ation

/ot-elib/ services/ Content

/cws/ services/ MemberSer vice

Computer Name Access URL

Enterprise Library Services installation host name

Host name of your Extended ECM installation

Computer Name of Access URL on the Transport settings tab: Host name of your Directory Services installation.

Host name of your Enterprise Library Content Services installation.

Host name of your Content Server Member Service installation.

If you are using userspecific mapping with impersonati on (SAP BAdI) and OpenText Directory Services and Enterprise Library Services and Content Server are installed on different servers, enter the host name of the Enterprise Library Services installation.

The following settings are the same for all ports:

108

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

18.3.3

•

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.

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

Enterprise Library

•

Extended ECM

•

OpenText Directory Services

•

Enterprise Library Content Services

•

Content Server Member Services

To create a logical port for SAP Basis 7.31: 1.

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

In SOA Management, on the Service Administration tab, click Web Service Configuration.

On the Design Time Object Search tab, select the search criteria Object Type and search for Consumer Proxy.

In the Search Results list, select the entry for EnterpriseLibrary (/OTX/

CO_RMELENTERPRISE_LIBRARY).

On the Configurations tab, click Create > Manual Configuration.

In the Logical Port Name step, enter a new name in the Logical Port Name field and add a description.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

109

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

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.

In the Consumer Security step, select SAP Authentication Assertion Ticket. Click Next.

In the HTTP Settings step, configure at least the following: •

URL Access Path:

/ot-elib/services/EnterpriseLibrary •

Computer Name of Access URL: Enterprise Library Services installation host name

•

Port Number of Access URL: Enterprise Library Web Services port (usually 8080 for Tomcat)

•

Transport Binding Type: SOAP1.1

Click Next. 9.

110

In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID Transfer

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

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 Enterprise Library Content Services (Content)

Content Server Member Service (MemberServic e)

Internal name

/OTX/ /OTX/ CO_RM_WSW_ CO_OTDSAUT ECMLINK HENTICATIO N

/OTX/ /OTX/ CO_RMELCON CO_MBLLME TENT MBER_SERVIC E

URL Access Path

/otsapxecm/ services/ ECMLink

/ot-elib/ services/ Content

/ot-authws/ services/ Authentication

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

/cws/services/ MemberService

111

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Computer Name of Access URL

Extended ECM Authentication Enterprise Library Content Services (Content)

Content Server Member Service (MemberServic e)

Host name of your Extended ECM installation

Port Number of Extended ECM Access URL Web Services port, usually 8080 for Tomcat

Host name of your Directory Services installation. If you are using user-specific mapping with impersonation (SAP BAdI), and OpenText Directory Services, Enterprise Library Services and Content Server are installed on different servers, enter the host name of the Enterprise Library Services installation.

Host name of your Enterprise Library Content Services installation

Host name of your Content Server Member Service installation

Directory Services Web Services port , usually 8080 for Tomcat

Enterprise Library Content Services port, usually 8080 for Tomcat

Content Server Member Service port, usually 8080 for Tomcat

The following settings are the same for all ports: • • •

112

Consumer Security: SAP Authentication Assertion Ticket Transport Binding Type: SOAP1.1 Message ID Protocol: Suppress ID Transfer

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

18.3.4

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

Enterprise Library

•

Extended ECM

•

OpenText Directory Services

•

Enterprise Library Content Services

•

Content Server Member Services

To create a logical port for SAP Basis 7.51: 1.

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

In SOA Management, on the Service Administration tab, click Web Service Configuration.

On the Design Time Object Search tab, select the search criteria Object Type and search for Consumer Proxy.

In the Search Results list, select the entry for EnterpriseLibrary (/OTX/

CO_RMELENTERPRISE_LIBRARY).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

113

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

On the Configurations tab, click Create > Manual Configuration.

In the Logical Port Name step, enter a new name in the Logical Port Name field and add a description. Select Logical Port is Default if this is the only logical port for Enterprise Library Services or if this is the preferred port of several logical ports for Enterprise Library Services. Click Next.

In the Consumer Security step, select SAP Authentication Assertion Ticket. Click Next.

In the HTTP Settings step, configure at least the following: •

URL Access Path:

/ot-elib/services/EnterpriseLibrary •

•

Computer Name of Access URL: Enterprise Library Services installation host name Port Number of Access URL: Enterprise Library Web Services port (usually 8080 for Tomcat) Transport Binding Type: SOAP1.1

Click Next. 9.

In the SOAP Protocol step, set the Message ID Protocol option to Suppress ID Transfer Click Next.

10. Click Finish. The new logical port is saved and activated. 11. Repeat Step 4 to Step 10 to create a logical ports according the following table: Extended ECM Authentication Enterprise Library Content Services (Content)

114

Content Server Member Service (MemberServic e)

Internal name

/OTX/ /OTX/ CO_RM_WSW_ CO_OTDSAUT ECMLINK HENTICATIO N

/OTX/ /OTX/ CO_RMELCON CO_MBLLME TENT MBER_SERVIC E

URL Access Path

/otsapxecm/ services/ ECMLink

/ot-elib/ services/ Content

/ot-authws/ services/ Authentication

/cws/services/ MemberService

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.3. Creating logical ports in the SAP system

Computer Name of Access URL

Extended ECM Authentication Enterprise Library Content Services (Content)

Content Server Member Service (MemberServic e)

Host name of your Extended ECM installation

Port Number of Extended ECM Access URL Web Services port, usually 8080 for Tomcat

Host name of your Enterprise Library Content Services installation

Host name of your Content Server Member Service installation

Directory Services Web Services port , usually 8080 for Tomcat

Enterprise Library Content Services port, usually 8080 for Tomcat

Content Server Member Service port, usually 8080 for Tomcat

The following settings are the same for all ports: • • •

Consumer Security: SAP Authentication Assertion Ticket Transport Binding Type: SOAP1.1 Message ID Protocol: Suppress ID Transfer

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

115

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

18.4 Configuring the Service Provider Interface service For communication from Content Server to the SAP system a web service is used. You configure the web service on SAP side. Content Server uses this web service to connect to the SAP system. Note: This activity is required to connect the SAP system as external system in Content Server. For more information, see “Connecting an external system” on page 124. 1.

In the IMG, navigate to the OpenText Extended ECM for SAP Solutions > Infrastructure structure and open it.

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.

Click the Web Service Administration or Single Service Configuration link to manage the web service.

Search for the /OTX/ECMLINKSERVICE web service to display details.

Select the web service and click Apply Selection.

Click the Configurations tab.

To create a service and an end point, click Create Service.

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:// Maintain Extended ECM Connections activity and click Execute.

Click New Entries.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

117

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Enter the following parameters: Connection ID Enter a connection ID. Extended ECM Connections •

118

Description: Enter a description for the connection.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.5. Maintaining Extended ECM connections

•

EL Appl. Password: Enter the Enterprise Library application password; this application password has been defined in “Creating an Enterprise Library application” on page 127.

Logical Ports for Web Services Enter the names of the logical ports for the Enterprise Library, the OpenText Directory, Extended ECM, Enterprise Library Content Services, and for the Content Server Member Service. For more information about logical ports, see “Creating logical ports in the SAP system” on page 99. OpenText Directory •

Partition: Enter the OTDS partition that is used to authenticate SAP users in Content Server, only if you are using policies and only if you have consolidated those users in OTDS in the format user@partition. Do not enter @ together with the partition, only the partition name. Leave the field empty, if you do not use partitions at all. Example: Users in your system are created using the following scheme USER@PARTITION, for example nick@SAP_USER. In this case, here, you enter SAP_USER.

•

Impersonation RFC: If you are using impersonation, enter the RFC destination used for impersonation. In addition, you have to implement and activate the /OTX/RM_IMPERSONATE BAdI and perform additional configuration tasks. You also must provide the CS Resource ID. RFC Impersonation uses a web service for SSO: if you want to restrict this web service to redirect to a certain Content Server, you can maintain a whitelist. For more information, see “Improving data security for impersonation connections” on page 121.

•

For more information about implementation, see the Extended ECM for SAP Solutions SDK on OpenText My Support. For more information about the impersonation scenario and relevant configuration, see Section 6.7.1 “Enabling user-specific impersonation (SAP BAdI)” in OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLK-CUM).

OpenText Content Server •

Protocol, Hostname, Port, and Path: These URL parameters define how to display the Content Server Web UI. Enter the parameters for your Content Server. If you are using a Remote Cache Server, enter the hostname of the primary Content Server. For Remote Cache, the IP range must be configured, which will then redirect the HTTP request to the configured Remote Cache Server. Important You must enter the full Content Server path including the domain name.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

119

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Example: •

Protocol: http

•

Hostname: myhost.example.net

•

Port: 2099

•

Path: OTCS/cs.exe Note: If this path has Integrated Windows Authentication (IWA) enabled, there are limitations for the following features: thumbnail view in the Business Content Window, license measurement, Content Server search from SAP, UI Widget integration. These functions ask for authentication if Integrated Windows Authentication is exclusively enabled as authentication method. Workarounds are: •

Thumbnail preview: Disable the preview in IMG at Extended ECM > Business Content Window > Business Content Window Settings. Create a new entry with WSP_THUMBNAIL_OFF as setting name and TRUE as value.

•

License Report and search: Use a new RFC destination with a mapping to Content Server without IWA .

•

UI Widget integration: Use the native Business Content Window UI.

Alternative authentication configurations are:

120

•

Enable the OTDS SSO authentication and disable the IIS IWA configuration. (Recommended)

•

If you need IIS IWA for all others users except SAP users, and there is no way to use OTDS SSO, you can create a second mapping in IIS that does not have IIS IWA, and configure that in the Extended ECM connection settings.

•

Support Directory defines the directory on Content Server where the files for the Content Server widgets are stored, for example img. This is only relevant if you want to use widgets and meet all prerequisites. For more information, see Section 7 “Using the Content Server Integration Widget” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

•

External System ID: Enter the name defined when configuring the external connection on Content Server for this SAP system.

•

Logical Destination: This entry is needed for enabling the Content Server full text search in the SAP system. Enter an existing logical destination defined in the SM59 transaction that contains the connection to the Content Server that is relevant for your search. transaction For more information, see Section 25.1.2 “Customizing search templates” in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).

•

CS Resource ID: Content Server Resource ID as defined for Directory Services. This option is necessary if you want to use impersonation with web-based SSO. To retrieve the ID, open Administration Client; then go

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

18.6. Improving data security for impersonation connections

to Directory Services > Resources > [Content Server entry] > Edit and copy the Resource identifier, for example d7c6b26baf12-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 121. Suppress Sending SAP Logon Ticket Select this option if you do not want to send the SAP Logon Ticket. Proxy Settings for OpenText Content Server The proxy settings define how to display the Content Server Web UI via a proxy, for example Web Dispatcher. •

Proxy Settings Enabled: Select to enable the following proxy settings.

•

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

Example:

•

Proxy Protocol: http

•

Proxy Hostname: myproxy.domain.net

•

Proxy Port: 80

Click

Save.

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

Use transaction SM30 to open table /OTX/RM_THTWHITE.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

121

Chapter 18 Performing post-installation tasks for SAP ERP 6.0, SAP CRM 7.0, and SAP SRM 7.0

Note: You can use the * wildcard in these fields. Important You must add the wildcard at the end of the URL Template to cover all URLs based on that template. Example: • • • •

Protocol of URL: HTTP Host Name: MYHOST.DOMAIN.NET Port: 80*, includes for example, port 8080 URL Template: /OTCS/CS.EXE*

18.7 Importing the Content Server SSL certificate To use SSL for the communication between Content Server and the SAP system, you must import the Content Server SSL certificate into the SAP system. Prerequisite •

You have configured the web servers for HTTPS.

•

You have exported the certificate from Content Server in the Base64 format.

To import the certificate:

122

In the SAP system, start the TRUST transaction.

Open the SSL client SSL Client (Anonymous) node.

On the Certificate menu, click Import.

Enter the file path and select Base64.

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

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 19

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

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

Open a command prompt window.

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

The key store password is changeit. To change the password, enter: keytool -storepasswd changeit -new keystore c:\opentext\config\ecmlink-spi.cacerts

To add an certificate run the following command: \bin\keytool -import -alias -file -keystore -storepass Example: C:\OPENTEXT\jre\bin\keytool -import -alias mycertificate

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

123

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

-file c:\temp\mycertificate.cer -keystore c:\opentext\config\ecmlink-

spi.cacerts

-storepass mypassword

19.2 Connecting an external system To connect Content Server with an SAP system, you define connection parameters on Content Server. To connect an external system: 1.

On the Content Server Administration page, click Extended ECM > Configure Connections to External Systems.

Click Add External System.

Specify the parameters for your external system according to the list below.

Click Add.

Logical External System Name Define the logical name of the external system. The name must be unique . It cannot be longer than 32 characters. This name is used when you select the external system in the business object type configuration. This name can be, for example, the name of the SAP system. Note: You cannot change the name later. Connection Type Displays the connection type. Enabled Select this option to enable the configuration. Tip: You can disable a configuration, for example, if you created it only for testing and you do not want it to be used. Comment Enter a comment to give further information. Base URL Common URL for accessing applications via a Web browser. You can use this base URL when configuring business object types on Content Server. The base URL is represented by the $BaseURL$ variable for new business object types. Application Server Endpoint Specify the URL that will be called to obtain business object information.

124

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.2. Connecting an external system

Example 19-1: SAP The following is an example for an SAP system: https://myhost.

opentext.net:8443/sap/bc/srt/xip/otx/ecmlinkservice/800/ ecmlinkspiservice/basicauthbinding

•

https://myhost.opentext.net:8443: Common URL.

Port 8000 is the default HTTP port for SAP. For HTTPS the default port is 8443. •

800 is the client number. Replace this number with your own client

number.

•

basicauthbinding is currently the only supported authentication.

Note: With using basic authentication, OpenText strongly recommends that you to use SSL at the web server. For information about importing certificates to the keystore, see “Importing root certificates for Secure Sockets Layer (SSL) connections” on page 123. Schema Version Select the interface version. User Name Enter the user that is used to access business object type information from the external system. Note: If the external system is an SAP system, in the SAP system assign the /OTX/RM_CS_SAP_USER role to this user. This user requires permissions for the SAP authorization object S_RFC. Password Specify the password of the defined user. Test Connection Click Test to perform a connection check to the specified external system. After a successful check, the message Connection test to was successful is displayed next to the button. The system ID will also be retrieved and displayed. Note: You can only test the connection after you have configured the SPI service in the external system accordingly. For more information, see “Configuring the Service Provider Interface service” on page 116. External System Names Enter localized names for the external system if required.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

125

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

Figure 19-1: SAP as an external system

19.3 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

In the Archive Storage Provider Administration section, click Configure Archive Storage Provider. Log in as Administrator.

126

In the Archive Server field, enter the name of the Archive Center host.

Click Save Changes. Archive Storage Provider uploads its certificate to Archive Center automatically.

Click OK.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.4. Managing users

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

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

19.5.1

Creating an Enterprise Library application 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.

In the Actions pane, select the New Application entry.

Enter the required parameters for the application.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

127

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

c. 4.

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, see Section 5.5 “SAP: Scheduling jobs for removing deleted records” in OpenText Extended ECM for SAP Solutions - Administration Guide (ERLKAGD). In the Password field, you define an application password that is used for “Maintaining Extended ECM connections” on page 117. Note: OpenText recommends that the application name is identical to the respective SAP system ID. Click Next.

Select the required audit interests that correspond to your audit scheme and click Finish to complete the assistant. The new application is now displayed in the list of applications.

128

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.5. Preparing document declaration

To set permissions for an application: 1.

Go to the Content Server Administration page and select the Enterprise Library Administration > Open the Enterprise Library Volumes entry.

Click the button of the application folder with the application ID you just created and select the Permissions entry from the context menu. The Permissions page displays.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

129

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

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 [emailprotected]).

•

Only See and See Contents access rights for the groups DefaultGroup and Public Access.

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

Grant full access to those users and groups that have to declare records within 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.10 “SAP: Creating an document declaration” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

130

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.5. Preparing document declaration

19.5.2

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

19.5.3

Importing folder and item type Extended ECM for SAP Solutions stores metadata for the declared ArchiveLink documents in the Enterprise Library volume. On the installation CD in the folder Extended ECM for SAP Solutions\Enterprise Library\Document Model, you find the following items: •

Folder type otx.sap.rm.Folder.xml

•

Item type otx.sap.rm.Document.xml

•

Item type otx.sap.rm.SystemArchiveLink.xml

•

Item type otx.sap.rm.SystemPrintlist.xml

These files must be imported with the OpenText Administration Client. To import the folder type: 1.

Invoke the OpenText Administration Client and navigate within your Enterprise Library Services to the Document Model entry and click the Folder Types tab.

In the Actions pane, select the Import Types entry and navigate to the otx. sap.rm.Folder.xml file provided in the folder ELS_TYPES on your installation

CD. Click the Open button to import the file.

The list of folder types displays the new folder type. 3.

Select the new folder type, invoke the Properties dialog and click the Classification tab.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

131

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

Click the Set default classification option and click the Browse button to select a classification.

To import the item type: •

132

In the Document Model entry, click the Item Types tab. Repeat the above procedure for the following files: •

otx.sap.rm.Document.xml

•

otx.sap.rm.SystemArchiveLink.xml

•

otx.sap.rm.SystemPrintlist.xml

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.5. Preparing document declaration

19.5.4

Setting up the authorization for records The access rights to the records created by Extended ECM for SAP Solutions correspond to the access rights used by the Enterprise Library application. For more information, see “Creating an Enterprise Library application” on page 127. In order to restrict the access in accordance with your company policy, you have to create Content Server groups and set the respective access rights on the classification level. The following access rights (either directly, via a group, or via public access) are required: •

To see records, users must have at least See Contents permission.

•

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

133

Chapter 19 Performing post-installation or post-upgrade tasks in Content Server

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

19.5.5

Creating system categories in Content Server Extended ECM for SAP Solutions stores all metadata in Content Server categories rather than using Enterprise Library item types. The imported item types otx. sap.rm.SystemArchiveLink and otx.sap.rm.SystemPrintList can be copied to categories described below. You can also create system categories manually, but copying the imported item types ensures that no mandatory category attributes are missing. To create system categories:

134

Go to the Content Server Administration page and select the Enterprise Library Administration > Open the Enterprise Library Types Volumes entry.

Browse to the folder named otx.sap.rm.SystemArchiveLink and open it.

Copy the category file otx.sap.rm.SystemArchiveLink.v to a different location within the Categories volume. If required, you can change the category name.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

19.6. For SAP CRM and SRM: Configuring security settings

Caution Do not delete the original category file under Open the Enterprise Library Types Volumes. 4.

Repeat the above procedure with the category file otx.sap.rm.SystemPrintList.v in the otx.sap.rm.SystemPrintList folder.

Create unique names for the system categories. You will need the unique name for the document declaration configuration in the SAP IMG. For more information, see Section 6.9 “Configuring unique names for Content Server items” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLKCGD).

19.6 For SAP CRM and SRM: Configuring security settings To display business workspaces in web applications of SAP CRM and SAP SRM, you must adapt the security parameters in Content Server. To enable display of business workspaces in web applications of SAP: 1.

On the Content Server Administration page, click Server Configuration > Configure Security Parameters.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

135

Chapter 20

Verifying the installation 20.1 Analyzing the SAP system 20.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 138. Note: You can also run the Diagnostic Program as a background job. To run the Diagnostic Program manually: 1.

If you are only interested in infrastructure information, in the IMG, navigate to the OpenText Extended ECM for SAP Solutions > Infrastructure > Diagnostic Program and click Execute. If you are also interested in the Extended ECM specific information, in the IMG. navigate to the OpenText Extended ECM for SAP Solutions > Extended ECM > Diagnostic Program activity.

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.

Click

Execute.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

137

Chapter 20 Verifying the installation

20.1.2

Understanding the details of the Diagnostic Program This section lists the various tests of the Diagnostic Program and refers to sections in this guide which contain helpful information. Test

IMG Activity

More Information

Content Server Does the connection ID exist? Infrastructure > Maintain Extended ECM connections; Did you select a proxy for double-click one entry. Content Server?

“Maintaining Extended ECM connections” on page 117

Did you provide the Content Server host name? Is the Content Server host name fully qualified?

138

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

20.1. Analyzing the SAP system

Test

IMG Activity

More Information

Infrastructure > Create New Logical Ports

“Creating logical ports in the SAP system” on page 99

Did you provide an HTTP Infrastructure > Create New destination for the Enterprise Logical Ports Library logical port?

“Creating logical ports in the SAP system” on page 99

Check the following for the Enterprise Library HTTP connection: “No Logon” and “Send SAP Logon Ticket” is enabled; “HTTP compression” is disabled.

For SAP Basis 7.0: Infrastructure > Create HTTP Connections > HTTP Connections to External Server; double-click one connection; Logon & Security tab and Special Options tab.

“Creating logical ports in the SAP system” on page 99

For SAP Basis > 7.0: Infrastructure > Create New Logical Ports > SOA Management > Application and Scenario Communication > Single Service Administration

“Creating logical ports for SAP Basis 7.01” on page 106

Infrastructure > Create New Logical Ports

“Creating logical ports in the SAP system” on page 99

Did you provide the Content Server port? Did you provide the path to Content Server? Can the SAP system connect to Content Server through HTTP? Can the SAP system connect to the proxy through HTTP? Service Communication Did you provide a port for the Enterprise Library Service? Can the Enterprise Library Service be instantiated?

Can the Enterprise Library Service be executed? Did you provide a port for the Enterprise Library Content Service? Can the Enterprise Library Content Service be instantiated? Did you provide an HTTP Infrastructure > Create New destination for the Enterprise Logical Ports Library Content logical port?

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

139

Chapter 20 Verifying the installation

Test

IMG Activity

More Information

Check the following for the Enterprise Library Content connection: “No Logon” and “Send SAP Logon Ticket” is enabled; “HTTP compression” is disabled.

For SAP Basis 7.0: Infrastructure > Create HTTP Connections > HTTP Connections to External Server; double-click one connection; Logon & Security tab and Special Options tab.

“Creating logical ports in the SAP system” on page 99

For SAP Basis > 7.0: Infrastructure > Create New Logical Ports > SOA Management > Application and Scenario Communication > Single Service Administration

“Creating logical ports for SAP Basis 7.01” on page 106

Infrastructure > Create New Logical Ports

“Creating logical ports in the SAP system” on page 99

Can Enterprise Library Content Service be executed? Did you provide a logical port for the Content Server Member Service? Can the Content Server Member Service be instantiated? Did you provide an HTTP destination for the Content Server Member logical port?

Infrastructure > Create New Logical Ports

Check the following for the Content Server Member HTTP connection: “No Logon” and “Send SAP Logon Ticket” is enabled; “HTTP compression” is disabled.

For SAP Basis 7.0: Infrastructure > Create HTTP Connections > HTTP Connections to External Server; double-click one connection; Logon & Security tab and Special Options tab.

“Creating logical ports in the SAP system” on page 99

For SAP Basis > 7.0: Infrastructure > Create New Logical Ports > SOA Management > Application and Scenario Communication > Single Service Administration

“Creating logical ports for SAP Basis 7.01” on page 106

Can the Content Server Directory Services Member Service be executed? Administration > Access Roles

140

Section 6.5 “Configuring access roles” in OpenText Extended ECM for SAP Solutions - User Management and Access Control Scenarios (ERLK-CUM)

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

20.1. Analyzing the SAP system

Test

IMG Activity

More Information

Did you provide a logical port for the Extended ECM Service?

Infrastructure > Create New Logical Ports

“Creating logical ports in the SAP system” on page 99

Did you provide an HTTP destination for the Extended ECM logical port?

Infrastructure > Create New Logical Ports

Check the following for the Extended ECM HTTP connection: “No Logon” and “Send SAP Logon Ticket” is enabled; “HTTP compression” is disabled.

For SAP Basis 7.0: Infrastructure > Create HTTP Connections > HTTP Connections to External Server; double-click one connection; Logon & Security tab and Special Options tab.

“Creating logical ports in the SAP system” on page 99

For SAP Basis > 7.0: Infrastructure > Create New Logical Ports > SOA Management > Application and Scenario Communication > Single Service Administration

“Creating logical ports for SAP Basis 7.01” on page 106

Did you provide a logical port for the OTDS Service?

Infrastructure > Create New Logical Ports

“Creating logical ports in the SAP system” on page 99

Did you provide an HTTP destination for the OTDS services?

Infrastructure > Create New Logical Ports

Check the following for the OTDS HTTP connection: “No Logon” and “Send SAP Logon Ticket” is enabled; “HTTP compression” is disabled.

For SAP Basis 7.0: Infrastructure > Create HTTP Connections > HTTP Connections to External Server; double-click one connection; Logon & Security tab and Special Options tab.

“Creating logical ports in the SAP system” on page 99

For SAP Basis > 7.0: Infrastructure > Create New Logical Ports > SOA Management > Application and Scenario Communication > Single Service Administration

“Creating logical ports for SAP Basis 7.01” on page 106

Can the Extended ECM Service be executed?

Can the OTDS Service be executed?

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

141

Chapter 20 Verifying the installation

Test

IMG Activity

More Information

If impersonation RFC is provided, can the impersonation RFC be executed? Did you provide a service for Infrastructure > Configure the SPI service SPI Service or configuration? SOAMANAGER transaction

“Configuring the Service Provider Interface service” on page 116

Check the following for the Infrastructure > Configure SPI service configuration: SPI Service or “Transport Guarantee Type = SOAMANAGER transaction HTTPS”; “Authentication: User ID/Password” is enabled.

“Configuring the Service Provider Interface service” on page 116

HTML Controls Can an HTML control be instantiated? Can an HTML control be initialized? Can the HTML control enable SSO? Are the SAP HTTP server and the Content Server server in the same domain or is the Content Server server in a subdomain of the SAP HTTP server domain?

142

>>> Double-click here to test an HTML control. Open the Appearances Volume.

Select the recommended appearance: For SAP CRM: EXTENDED_ECM_CRM_DEFAULT For SAP SRM: EXTENDED_ECM_SRM_SAP_TRADESHOW

Check if the following settings are present according to Figure 22-1 or Figure 22-2. •

Current Status: Enabled

•

Header section

•

Content Server Components section

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

149

Chapter 22 Performing additional optional tasks

•

Workspace section

Figure 22-1: Appearance settings for SAP CRM Header script for EXTENDED_ECM_CRM_DEFAULT

Figure 22-2: Appearance settings for SAP SRM Header script for EXTENDED_ECM_SRM_SAP_TRADESHOW

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

151

Chapter 22 Performing additional optional tasks

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.

22.2 Customizing the integration into SAP GUI via Generic Object Services 22.2.1

Customizing the Generic Object Services (SAP GUI) 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, business documents, local TempoBox folders, other local files, and notes in one dialog. Important If you are upgrading from 10.0.0, the existing GOS customizing will not be changed. You can choose if you want to keep several GOS entries or if you want to use OpenText Business Content. Tip: For a detailed description of the Business Content window, see Section 25.2 “OpenText Business Content window” in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).

152

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

To customize General Object Services: 1.

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

Click New Entries.

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

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

153

Chapter 22 Performing additional optional tasks

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.

22.2.2

Select 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. New: You can now customize, which items are displayed in the Business Content window of a certain business object type. 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 click Execute.

Click New Entries.

Select a business object type and then select the options that you want to be displayed: Business workspace thumbnails Drag and Drop in business workspaces Business attachments Business documents Business documents thumbnails Notes 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 157.

154

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

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

•

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 157. Note: The customizing applies only to Content Server Classic View, not if the integration widget is used as described in “Enabling the integration widget in the Business Content window” on page 157.

22.2.3.1

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

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

Click New Entries.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

155

Chapter 22 Performing additional optional tasks

BROWSE

Open

COPY

Copy

DELETE

Delete

DOWNLOAD

Download

FETCH

Open

MAKEFAVORI Add to Favorites TE MOVE

Move

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” on page 161.

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 (Goto > Translation). Example: In the following example, the new menu item Zip & Download is added to the menu.

156

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

22.2.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/44140285). Adding custom functionality:

22.2.4

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

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.

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.

22.2.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 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 Section 4.2.1.2 “Configuring Microsoft IIS to Return Meaningful REST API Error Messages” in OpenText Content Server - Installation Guide (LLESCOR-IGD).

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

157

Chapter 22 Performing additional optional tasks

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

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

Optional To define the theme, in the IMG, navigate to the Extended ECM > Business Content Window > Maintain Business Content Window Display Options and click Execute.

a. b.

In the General Settings section, click New Entries. As Setting Name enter WSP_WIDGET_CSS_THEME and as Setting Value enter the name of the theme, for example sap_bluecrystal.

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

22.2.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. b. c. d. e.

158

Start transaction SE16 and open /OTX/RM_STWL. Start transaction SM30 and open the maintenance view of the /OTX/ RM_STWL_C table. Copy all entries from /OTX/RM_STWL into the clipboard. You can use CTRL + Y to copy several rows. Copy the rows into the Subtype column of the /OTX/RM_STWL_C table. Add the connection ID for which the subtype is valid.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

22.2.7

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

•

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.

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.

Run the PFCG transaction.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

159

Chapter 22 Performing additional optional tasks

22.2.8

Select Security > Security Settings.

Set Status and Default Action as required.

Providing thumbnails for business workspace documents in the Business Content window You can display thumbnail pictures for documents that are stored in a business workspace in the Business Content window. This is a feature of Content Server, which you must configure accordingly. Important Thumbnail pictures for business documents are displayed automatically for all document formats that are supported by the OpenText Imaging Web Viewer. For more information, see Section 25.2.3.2 “Using the Business Documents function” in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS). To provide thumbnails for business workspace documents: 1.

On the Content Server Administration page, select Server Configuration > Configure Presentation > Configure Thumbnails.

Enable thumbnail generation and display. Set the MIME types for those file formats, for which you want to provide thumbnails. For more information, see the Content Server Administration online help.

160

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

22.2.9

Integrating Viewers 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. Note: OpenText Brava! View for SAP Solutions runs against the OpenText Imaging Windows Viewer integration of Archiving and Document Access on an SAP system. Since the Business Content window displays documents via Content Server it cannot call Brava! View for SAP Solutions directly. Instead it uses the viewer enabled for Content Server.

Configuring the Content Server viewer 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. For more information, see “Configuring external viewers for Content Server” on page 168.

•

Configure the mime types. For more information, see Section 8.10 “Customizing MIME types for preview” in OpenText Extended ECM for SAP Solutions Customizing Guide (ERLK-CGD).

•

Configure the viewer settings in the SAP system. For more information, see Section 20.2 “Configuration for Java Viewer/Web Viewer/Brava! View” in OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ERCCS).

Configuring Content Suite Viewer as Content Server viewer: •

Brava! Installation: Brava Server Components for OpenText Content Suite Viewer – Installation and Administration Guide.

•

Content Suite Viewer Administration on Content Server Administration page: Content Suite Viewer Admin Online Help - Content Server Administration (LLESDVH-AGD)

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

161

Chapter 22 Performing additional optional tasks

Configuring the Business Content window viewer Business Content window displays Content Server content. To use Content Suite Viewer as viewer within the Business Content window, you can 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 •

Brava! Installation: Brava Server Components for OpenText Content Suite Viewer – Installation and Administration Guide, available on OpenText My Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/61356446).

•

Content Suite Viewer Administration on Content Server Administration page: Content Suite Viewer Admin Online Help - Content Server 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 163.

•

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 Server Configuration > Configure Security Parameters.

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

Adding Content Suite Viewer action in Business Content window menu: 1.

Start the SM30 transaction and enter /OTX/RM_WSC_FCOD in the Table/View field. Click Maintain.

Click New Entries.

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.

•

Function Code: PICK

Add an entry for DocuLink:

162

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.2. Customizing the integration into SAP GUI via Generic Object Services

•

Menu ID: DOCULINK

•

Code ID: VIEWDOC

•

Description: For example View or Display with Content Suite Viewer

•

Activation: Select.

•

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.

22.2.10

Customizing MIME types for preview The Business Content window relies 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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

163

Chapter 22 Performing additional optional tasks

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.

22.2.11

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

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 •

164

/OTX/RM_BF_GOS_ATTACHMENT

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.3. Viewing the old configuration in SAP

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 Execute. activity and click

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.

Click

Activate Changes.

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

Open the /OTX/RM_WSC_VCZ view cluster. The screen shows the new reduced configuration.

In the command field, enter &show_legacy_on.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

165

Chapter 22 Performing additional optional tasks

Navigate to the configuration that you want to retrieve. For information about the new business object type configuration, see Section 3.13 “Configuring business object types” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

To display the old field mapping for authorization based on category IDs, navigate to Workspace Authorization > Field Mapping and enter & show_legacy_on.

22.4 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 Content Server server and the OTDS server must be in the same domain or in a sub-domain of the SAP HTTP server that issues the cookie. Same domain: CS = cs.example.com OTDS = otds.example.com SAP = sap.example.com

Sub-domain: CS = cs.paris.example.com OTDS = otds.paris.example.com SAP = sap.example.com

Note: This restriction is only valid if you want to use Content Server Classic View. If you want to use Content Server Smart View or integrations of the integration widget also cross-domain requests can be handled. •

Restriction when SSO is not enabled

166

The user must be a dialog user in SAP, otherwise the SSO ticket cannot be created.

If either SSO cannot be achieved in your server and desktop environment or the option Suppress Sending SAP Logon Ticket is turned on in the connection ID configuration (see “Maintaining Extended ECM connections” on page 117), 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.12 “SAP: Assigning a document declaration to a business object and a document type” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).

•

In some cases the user gets a logon screen when accessing Content Server functionality.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.4. Configuring Single Sign-on for Content Server

For the caller dialog, the logon screen appears only once, as long as a 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. To configure security parameters: 1.

Go to the Content Server Administration page and select the Server Configuration > Configure Security Parameters entry.

In the Cookie Authentication Information group, select the Never Expire option.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

167

Chapter 22 Performing additional optional tasks

22.5 Configuring external viewers for Content Server Note: This does not describe the configuration of Content Suite Viewer. The configuration of Content Suite Viewer is available on Content Server Administration page at Content Suite Viewer Administration > Configure Content Suite Viewer Settings. You can configure the OpenText Imaging Windows Viewer and the OpenText Imaging Web Viewer as viewers for files that are stored in Archive Center. They must be of a MIME type that is supported by Web Viewer. Important This setting of Web Viewer or Windows Viewer only applies to archived documents that are stored in a Business Workspace, Binder or Case. For all other documents, the settings of Content Server apply.

Enable OpenText Imaging Windows Viewer Enables the OpenText Imaging Windows Viewer integration. The document is displayed in Windows Viewer installed on the user’s machine unless some other program is configured as default viewer for the MIME type. If both viewers are enabled, the viewer with the higher precedence is used to display the document. Enable OpenText Imaging Web Viewer Enables the OpenText Imaging Web Viewer integration. If both viewers are enabled, the viewer with the higher precedence is used to display the document. Web Viewer URL Defines the OpenText Imaging Web Viewer URL. Important Make sure that the precedence in Content Server (Web Edit Administration > Configure Web Edit Settings) is in line with your selection here. This means, that if you enable a viewer, it must not have a negative precedence. Viewer precedence To set the precedence and the MIME types for each of the viewers, you can configure the default settings on the Web Edit Administration > Configure Web Edit Settings section of the Content Server Administration page. The following settings are relevant:

168

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

22.5. Configuring external viewers for Content Server

•

Precedence settings for OpenText Imaging Web Viewer and OpenText Imaging Windows Viewer in the Content Server configuration. If both viewers are enabled, the viewer with the higher precedence is used to display the document.

•

MIME type settings for OpenText Imaging Web Viewer and OpenText Imaging Windows Viewer. Enter the relevant MIME types in the first field.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

169

Chapter 23

Preparing a checklist for the customizing team After you have installed the infrastructure for Extended ECM for SAP Solutions, you can hand-over the work to those who are responsible for the customizing of the system as it is described in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD). The following tools provide both necessary and useful information: SAP system •

Diagnostic Program: “Understanding the SAP Diagnostic Program” on page 137 Tests the customizing and provides solutions for errors.

•

Configuration Report: Section 20.1.3 “Understanding the Configuration Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD) Provides information about Extended ECM for SAP Solutions related customizing in the SAP system.

Content Server System Report: Section 20.2 “Understanding the Content Server System Report” in OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD) Contains the complete configuration information of the Content Server system. Look for the “Extended ECM Information” section. After installation, the following sections are interesting: Enterprise Library Applications, SAP Systems, OpenText Imaging Viewers. OpenText Administration Client You can generate a report for OpenText Archive Center: Provides information for the ArchiveLink setup in SAP (OAC0 transaction). To generate the system configuration reports: 1.

In OpenText Administration Client, log on to the server.

OpenText Archive Center a. b. c. d. e.

Go to Archive Server > System > Reports. In the Reports pane, open the Scenarios tab and select the scenario. In the Actions pane, click Generate Report. A new window opens, which you can close. Switch to the Reports tab in the Reports pane. Click Refresh to list the newly generated reports.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

171

Chapter 23 Preparing a checklist for the customizing team

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. To generate the system configuration reports:

172

From the web administration menu, under the Info heading, click System Status.

On the System Status page, click Download System Configuration Report.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Chapter 24

Transporting Extended ECM for SAP Solutions Content Server configuration and templates Exporting and importing a Connected Workspaces configuration together with the standard functions of Content Server Transport Warehouse, help you moving an existing configuration from one Content Server installation to another, for example if you are using development, test and productive 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. Table 24-1: Recommended transport order Item type

Transport method

1 Categories, classifications, and folder structure

Content Server Transport Warehouse

2 Workspace types, and unique names and variable definitions

Connected Workspaces export and import

3 Workspace templates (document templates) Content Server Transport Warehouse 4 Business object types

Only for Extended ECM: Connected Workspaces export and import

24.1 Transporting the Connected Workspaces configuration 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.

•

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

173

Chapter 24 Transporting Extended ECM for SAP Solutions Content Server configuration and templates

24.1.1

•

When a transport file from the SAP Configuration Report 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.

Importing the configuration To import the Connected Workspaces configuration on Content Server:

174

On the Content Server Administration page, click Connected Workspaces > Import/Export Configuration.

On the following page, click Import Configuration.

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.

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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

24.1. Transporting the Connected Workspaces configuration

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.

b. 6.

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. Click Preview to read the new changes into the preview.

When you are satisfied with the import preview, click Import. A result page informs you in detail about what has been imported.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

175

Chapter 24 Transporting Extended ECM for SAP Solutions Content Server configuration and templates

24.2 Transporting categories, classifications and workspace templates You can use Content Server Transport to transport categories, classifications and workspace templates from one Content Server to another Content Server. The transport of a workspace template contains all subitems and the Related Workspaces folder with its configuration. Restrictions •

You can only transport workspace templates. Normal business workspaces cannot be transported. You will get an error message when you try to add them to a workbench.

•

Group replacement settings are not part of the transport.

Processing sequence •

On the source system: 1. Create a workbench. 2. Add category, classification or workspace template to the workbench. 3. Create a transport package and add workbench items. 4. Download the transport package.

•

On the target system: 1. Upload the transport package. 2. Unpack the transport package to a workbench. 3. Deploy the workbench.

The following procedure describes the transport of workspace templates. The transport of categories and classifications follows the same schema. Tip: For more information about Content Server Transport, see the Content Server online help on that topic. To transport a template: 1.

Create a new workbench: a. b. c.

Add a workspace template to the workbench: a. b.

176

From the main menu, select Enterprise > Transport Warehouse. Click Add Item > Workbench. Enter a name and click Add.

From the main menu, select Enterprise > Document templates and find the workspace template that you want to transport. From the context menu of the workspace template, select Add to Warehouse.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

24.2. Transporting categories, classifications and workspace templates

Select the workbench that you created for workspace templates.

Select if you want to include the content of the workspace templates. All subitems that can be transported will be transported. This also includes the Related workspaces folder.

Create a transport package: a.

In the workbench, click Add all to Transport Package. To add single items, select Add to Transport Package from the context menu of that item.

Enter the name of the transport package and click Add.

Go to the location of the transport package and download it

On the target system, import the transport package. a.

From the main menu, select Enterprise > Transport Warehouse.

In the Transport Warehouse, click Transport Packages.

Click Add Item > Transport Package.

Enter a name for the new transport package. Select the ZIP file that you downloaded from the source system.

Click Add.

Unpack the transport package. a.

If you do not yet have a workbench for the transport, create it.

From the context menu of the transport package, select Unpack.

Select the workbench to which you want to unpack the transport package.

Click Unpack.

Deploy the workbench items. a.

Click a workbench item to view its details. If there is an Edit button in the Actions column, you can change, for example, the location where the item will be stored. You can view the automatically created team roles and edit the team participants.

To deploy a single item, click Deploy in the details view.

To deploy the whole workbench, click Deploy workbench.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

177

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

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

179

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 Content Server user interface with folders, function menus and sidebars. As opposed to Content Server Smart UI. See Also smart UI. classification Systematic grouping of metadata based on a specific set of criteria. Classifications categorize Content Server items, for example, documents, compound documents, and folders into a taxonomy of Classifications called Classification Trees. For business workspaces, classifications control the layout and other options. It also controls which template can be used for creating a new business workspace of this type. Connected Workspaces Content Server module that enables the use of business workspace with or without a connection to an external system. 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.

180

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Glossary

document templates Basis for new business workspaces that are managed with Extended ECM for SAP Solutions. Templates are offered to the user based on the business object type and the storage location of the new document. 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 time 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.

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

181

Glossary

OTDS See OpenText Directory Services (OTDS). Perspective Manager See perspective. 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. 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. Automatic relationships are defined in the property provider. Users can establish manual relationships. 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

182

OpenText Extended ECM for SAP Solutions – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

Glossary

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 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. See Also classic UI. 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. 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 – Installation and Upgrade Guide ERLK160200-00-IGD-EN-01

183

OpenText Extended ECM For SAP Solutions 16.2 - Installation and Upgrade Guide English (ERLK160200-00-IGD-En-01) - PDFCOFFEE.COM (2024)

References