OpenText Archiving and Document Access For SAP Solutions 16.2 - Installation and Upgrade Guide English (ER160200-00-IGD-EN-1)

Installation and Upgrade Guide
OpenText™ Archiving and Document

Access for SAP Solutions
The OpenText Archiving and Document Access for SAP

Solutions installation guide describes the installation of the
basic components including DocuLink, DesktopLink, Forms
Management, and Java Viewer/Web Viewer integration.
ER160200-00-IGD-EN-1
Installation and Upgrade Guide
OpenText™ Archiving and Document Access for SAP Solutions
ER160200-00-IGD-EN-1
Rev.: 24. 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 Archiving and Document Access for
SAP Solutions? .......................................................................... 5
2 Checking prerequisites ............................................................. 7

2.1 Required knowledge .......................................................................... 7
2.2 Software packages ............................................................................ 7
2.3 Terms and definitions ........................................................................ 8
2.4 SAP prerequisites ............................................................................. 8
2.5 Installation tool ................................................................................ 10
2.6 Installation packages and passwords ............................................... 10
2.7 Web Dynpro configuration ............................................................... 11
3 Installing Basis package ......................................................... 13

3.1 Installing package ........................................................................... 13
3.2 Configuring components .................................................................. 16
3.2.1 Configuring rendition management ................................................... 16
3.2.2 Configuration for Java Viewer/Web Viewer/Brava! View ..................... 16
3.2.3 Setting number ranges .................................................................... 23
3.2.4 Defining authorizations .................................................................... 23
3.2.5 Defining settings for logging ............................................................. 24
3.2.6 Defining settings for optional sample projects .................................... 24
3.3 Rendition management ................................................................... 25
3.4 Forms Management ........................................................................ 25
3.4.1 General information ......................................................................... 25
3.4.2 Installing Forms Management .......................................................... 26
3.4.3 Authorizations ................................................................................. 27
3.5 DesktopLink .................................................................................... 27
3.5.2 Authorizations ................................................................................. 28
3.6 Imaging Integration ......................................................................... 28
3.6.2 Installing Java Viewer on a Web Server as a CGI Script .................... 28
3.7 DocuLink ........................................................................................ 30
3.7.2 Authorizations ................................................................................. 30
3.7.3 Testing the DocuLink installation ...................................................... 31
4 Installing ERP option package ............................................... 33

4.1 Installing the ERP package .............................................................. 33
5 Installing CRM option package .............................................. 35

5.1 Installing the package ...................................................................... 35
OpenText Archiving and Document Access for SAP Solutions – Installation and Upgrade
Guide iii
ER160200-00-IGD-EN-1
Table of Contents
6 Installing the SAP Fiori OData Services packages .............. 37

7 Installing the SAP Fiori UI package ....................................... 39

8 Installing language packages ................................................. 41
9 Upgrading to version 16.2 ...................................................... 45

9.1 Upgrading to Archiving and Document Access for SAP Solutions
16.2 ............................................................................................... 45
9.1.1 Delta upgrade from version 16 to 16.2 .............................................. 45
9.1.2 Intermediate step: delta upgrade from version 10.5.0 to 16 ................ 47
9.1.3 Intermediate step: delta upgrade from version 10.0.0 to 10.5.0 ........... 49
9.1.4 Upgrading from versions prior to SAP 6.0 ......................................... 50
9.1.5 Upgrading from SAP 6.0 and Livelink ECM-Suite for SAP Solution
9.5.1 or 9.5.2 .................................................................................. 51
9.1.6 Upgrading from Livelink ECM-Suite for SAP Solution 9.5.0 ................ 53
9.1.7 Upgrading from Archiving and Document Access for SAP Solutions
9.6.0 - 10.0.0 .................................................................................. 53
9.1.8 OpenText Employee File Management 2.5 ....................................... 56
9.1.9 Equivalencies of OTEXBAS, OTEXERP and OTEXCRM packages .... 57
9.2 Upgrading the SAP system .............................................................. 59
9.2.1 Exchange upgrades keeping 16.2 .................................................... 59
10 Uninstalling Add-Ons .............................................................. 63
11 Handling communication protocols ...................................... 65

11.1 Maintaining OLE application ............................................................ 65
11.2 Maintaining SAP ArchiveLink application .......................................... 67
11.3 Maintaining viewer components ....................................................... 72
11.4 Assigning protocols to logical archives (content repositories) ............. 76
12 Troubleshooting ...................................................................... 77
iv Guide
ER160200-00-IGD-EN-1
Chapter 1
What is OpenText Archiving and Document Access
for SAP Solutions?
With Archiving and Document Access for SAP Solutions, you can automatically
store SAP and non-SAP data and documents on a secure archive server (OpenText™
Archive Center). This increases operational efficiency by freeing IT from the time-
consuming chore of manual backups and recovery. It also offloads data from
production systems, for improved system performance and faster upgrades.
Archiving and Document Access for SAP Solutions offers a range of options for
integrating SAP documents and other documents in the different SAP applications,
including emails, faxes, images and informal correspondence, etc. Besides archiving
documents, it allows you to manage, search, display and edit them.
Archiving and Document Access for SAP Solutions software

packages
Archiving and Document Access for SAP Solutions consists of the following SAP
packages:
• SAP basis package OTEXBAS
Provides all base applications: DocuLink, DesktopLink, Forms Management,
Imaging Integration, ArchiveLink attributes, License Measurement
• SAP ERP package OTEXERP (optional)
Optional package with ERP specific functionality
• Allows use of DVS/PLM nodetypes in DocuLink
• Transaction /ixos/plm to have an uploader transaction for DVS/PLM
documents
• Client independent objects and code for sample DocuLink projects, which are
not only SAP ERP specific but can also be used for base examples
• SAP CRM package OTEXCRM (optional)
Optional package with CRM specific functionality.
• Allows use of SAP CRM link range in Content Management node type in
DocuLink
• Client independent objects and code for a sample DocuLink project in SAP
CRM
• SAP Fiori package OTEXBASO (optional)
Optional package with OData services for SAP Fiori
Guide 5
ER160200-00-IGD-EN-1
Chapter 1 What is OpenText Archiving and Document Access for SAP Solutions?
• SAP Fiori UI package OTEXBASF (optional)

Optional package with SAP Fiori specific user interface functionality for
ArchiveLink Plus and test application
6 Guide
ER160200-00-IGD-EN-1
Chapter 2
Checking 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).
• Basic knowledge of the employed operating system.
• Basic knowledge of the Enterprise Library.
2.2 Software packages

Archiving and Document Access for SAP Solutions consists of the following
software packages (for the current version numbers, check the latest Release Notes
in OpenText My Support):
• OpenText SAP Basis package
• OpenText SAP ERP package (optional)
• OpenText SAP CRM package (optional)
• Enterprise Library package
• OpenText Imaging Clients package
• OpenText Imaging ExchangeLink (optional)
• OpenText Imaging NotesLink (optional)
• OpenText SAP OData Services package (optional)
• OpenText SAP Fiori UI package (optional)
Guide 7
ER160200-00-IGD-EN-1
Chapter 2 Checking prerequisites
2.3 Terms and definitions

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

OTEXxxx Package with the ID xxx
<SID> System ID of the system used by the user
<MDT> Client into which the import will take place
/usr/sap/trans/EPS/in Package directory in the user's system
2.4 SAP prerequisites

Check the following prerequisites prior to installation:
SAP support packages

Check the latest version of the Release Notes in OpenText My Support for
required support packages for the employed SAP system prior to installation!
Transport system
The SAP application transport system is installed, or in other words, the jobs
RDDPUTPP and RDDIMPDP are set up in the correct clients (scheduled to run
periodically or event-triggered).
OSS notes
Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
• SAP 7.00
• 822380 – Problems w/ add-on inst/upgrade to SAP NW 7.0 AS ABAP
• 822379 – Known problems with Support Packages in SAP NW 7.0 AS
ABAP
• 1597766 – Problems for add-on install./upgrade in SAP NW 7.31 AS
ABAP
ABAP
• 1843158 – Problems with add-on installation/upgrade to SAP NW 7.40 AS
ABAP
ABAP
• Installation information
1611525 – Archiving and Document Access 10.0 by OpenText
• SAPCAR tool
212876 – The new archiving tool SAPCAR
8 Guide
ER160200-00-IGD-EN-1
2.4. SAP prerequisites
• Activation of the Business Configuration sets (BC sets)

1274142 – SCPR116: Activation links error in BC Set activation
Patch levels
• Patch level for SAP ERP 6.0 - The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 700, patch level 16. This
patch level is required for enhanced functionality, for example, additional
icons in the GOS attachment list based on the SAP enhancement technology.
• Patch level for SAP CRM 7.0 - The minimum requirement for software
components SAP_BASIS and SAP_ABA is release 701 BBPCRM minimum
release 700.
• Patch level to install optional OData package - This package can be
installed on SAP backend systems either with Backend Event Provider
(IW_BEP release 200, patch level 10) or with SAP Gateway Foundation
(SAP_GWFND, at least release 740, patch level 09). On systems with
SAP_GWFND release 750, like S/4 HANA, use SPAM/SAINT level 0059 or
newer for installation. Though not required for installation, at runtime the
OData services of Archiving and Document Access for SAP Solutions call
RFC functions of the basis add-on (OTEXBAS) of Archiving and Document
Access for SAP Solutions 16.
• Patch level to install optional Fiori UI package - This package can be
installed on SAP frontend systems with User Interface Technology (SAP_UI
release 740, patch level 13. On systems with SAP_UI release 750, like S/4
HANA, use SPAM/SAINT level 0059 or newer for installation). Though not
required for installation, at runtime the Fiori app calls the OData services of
Archiving and Document Access for SAP Solutions.
System upgrade
When you have to upgrade your SAP system and you already installed
Archiving and Document Access for SAP Solutions using packages, you have to
use vendor keys or attribute change packages (ACP).
For more details, see “Upgrading the SAP system” on page 59.
Note: The documentation is updated regularly; therefore, check for the latest
version in OpenText My Support.
Guide 9
ER160200-00-IGD-EN-1
Chapter 2 Checking prerequisites
2.5 Installation tool

Archiving and Document Access for SAP Solutions uses the SAP Add-On
Installation Tool (SAINT) for installation. SAINT uses single PAT files (extension
*.PAT) which integrate several transport files; these collections are also called
packages.
On the product ISO image or ZIP archive, the single PAT files are archived in
SAPCAR files (extension *.SAR) that can be extracted using the SAPCAR command
line tool. The different SAPCAR files are located in a DATA folder below the
respective package folder named as the package and SAP release. For example,
INST_BAS_700/DATA/OTEXBAS_INST_1620_700.SAR contains the archived PAT file
to install the package for SAP basis release 7.00 or higher.
Notes
• The handling of the installation procedure within SAINT differs depending

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

Every single installation package for Archiving and Document Access for SAP
Solutions is protected with a specific password. During the installation, this
password is requested by SAINT.
Installation packages and the corresponding passwords are listed in “Installation
packages and passwords” on page 10.
Table 2-1: Installation packages and passwords
Package Designation Release Password

OTEXBAS Archiving and 1620_700 9396C555B8
Document Access for
SAP Solutions for
Basis Component
16.2
OTEXBASO Archiving and 1620_700 9396C555D7
Document Access for
SAP Solutions OData
Services Component
16.2
10 Guide
ER160200-00-IGD-EN-1
2.7. Web Dynpro configuration
Package Designation Release Password

OTEXBASF Archiving and 1620_740 9096C555DE
Document Access for
SAP Solutions Fiori
UI Component 16.2
OTEXERP Archiving and 1620_600 9391D656B8
Document Access for
SAP Solutions ERP
Component 16.2
OTEXCRM Archiving and 1620_700 9597D64BB8
Document Access for
SAP Solutions CRM
Component 16.2
SAP Note 567695
SAP requires having a SAP Note number that contains information regarding
the installation and upgrade of OpenText software. Depending on the number
is an installation password which is needed for installation and delta upgrades.
Refer to SAP Note 567695, which is the general note related to Add-ons for
Software Partners.
2.7 Web Dynpro configuration

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

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

OTEXBAS_INST_1620_700. INST_BAS_700\DATA\ /usr/sap/trans
SAR
Guide 13
ER160200-00-IGD-EN-1
Chapter 3 Installing Basis package
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command:
SAPCAR -xvf <name of SAPCAR file>
The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
Note: With Basis 7.00 or higher, you can use the SAINT and SPAM
transactions to upload and extract the SAR files from the frontend.
3. Carry out import of packages as described in the respective SAP
documentation. For this, you will need the password for the installation
package. For more information, see“Installation packages and passwords”
on page 10.
4. After import has been finished, continue with the activation of the BC sets.
For every client, the Business Configuration Sets (BC Sets) must be activated after
installation.
To activate BC sets:
1. Execute the SCPR20 transaction.

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

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

Document Access for SAP Solutions > DocuLink Administration >
Customizing Maintenance and Upgrade > Create DocuLink Project
$GARMISCH.
14 Guide
ER160200-00-IGD-EN-1
3.1. Installing package
2. The start screen of the /IXOS/DC_A_CREATE_GARMISCH report is displayed.

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

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

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

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

also to the chapters section 7.3.1 “Standard functions in the tab view” in OpenText
DocuLink for SAP Solutions - Customizing and Administration Guide (DC-CGD) and
section 8.2 “The versions” in OpenText DocuLink for SAP Solutions - Customizing and
Administration Guide (DC-CGD).
Important
The customizing tables which contain the content of the DocuLink project
customizing are flagged with Log data changes, i.e. you may use the SCU3
(table history) transaction to track any changes in the DocuLink project
customizing.
Guide 15
ER160200-00-IGD-EN-1
3.2 Configuring components

3.2.1 Configuring rendition management
After successful installation of the Basis package, you may configure the Rendition
Server API.
To configure Rendition Server API:
1. Execute the SM30 transaction to maintain the tables /IXOS/RSA_T_CONF and /

IXOS/RSA_T_RENS (see OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS)).
Note: The following steps are only required when rendition management
shall be used within DocuLink.
2. Execute the SM30 transaction to maintain the table /IXOS/RSA_T_TAFO

containing the target formats used in the Rendition Task Profiles (table IXOS/
RSA_T_CONF).
The following value pairs are valid:
Document class MIME type of a Web object

PDF application/pdf
TIF image/tiff
TXT text/plain
ORIGINAL original
This standard setting of table /IXOS/RSA_T_TAFO is also delivered by

activating the BC set /OTEXBAS/DOCULINK_ALL1600. The MIME type =
original has to be in lower case letters. In the DocuLink Rendition Server task
profile, this special type can be used to download the files without converting
them.
3. Execute the DocuLink administration transaction J6NA to maintain the tables /

IXOS/RSA_T_CONF and /IXOS/RSA_T_RENS.
3.2.2 Configuration for Java Viewer/Web Viewer/Brava! View

Note: The customizing procedure with the /ixos/oa_cust table has been
superseded by the parameters defined in the new /ixos/oa_cust_a table.
By default, documents that are opened from within the SAP GUI are displayed in
the SAP viewer, or, if it is installed, in Windows Viewer. Compared to the SAP
viewer, Windows Viewer offers additional functionality to edit documents,
however, it requires an additional client installation. If you would like to take
advantage of additional viewer functionality without an additional installation
process, you can use the Java Viewer, Web Viewer or Brava! View for SAP Solutions.
16 Guide
ER160200-00-IGD-EN-1
3.2. Configuring components
To do so, you may configure the viewer integration on the SAP server in a way that
the required viewer will be used.
Note: An instance of Brava! View for SAP Solutions is customized nearly like
a Web Viewer but behaves differently. About the restrictions of Brava! View
for SAP Solutions, see also the release notes of OpenText Archiving and
Document Access for SAP Solutions.
To maintain the imaging integration:
• Activate the user exit to use a different viewer other than the standard SAP
viewer:
a. Run the SE16 transaction and open the TOAEX table.

b. Create a new entry with these values:
EXIT_ID = OA_OBJECTDISPLAY_01
ACTIVE = X
EXIT_FUB = /IXOS/OA_X_OA_OBJECTDISPLAY_01
c. To use a different viewer also for SAPGUI for JAVA create the following
entries with these values:
EXIT_ID = OA_DISPLAYJAVA_01
ACTIVE = X
EXIT_FUB = /IXOS/OA_X_OA_OBJECTDISPLAY_01
After installation, the viewer components must be configured and customized using
the following tables:
• /ixos/oa_cust_a
Legacy table - it is still evaluated, but do not use it anymore. A description can be
found in guides of version 10.5 SP1 or older.
• /ixos/oa_doctype
Document classes and their viewer types (if not defined, the default viewer for
ArchiveLink documents will be used)
• /ixos/oa_locales
Languages used (optional, for Web Viewer only)
• /ixos/oa_iprange
IP settings used to optimize network performance (optional, for Web Viewer
only)
• /ixos/oa_cust3
Force MimeType settings to display documents
To configure the external viewer:
1. In the IMG, navigate to OpenText Archiving and Document Access for SAP
Solutions > Imaging (Viewer) Integration > Standard Customizing and run
the Maintain Viewer Usage and Settings activity. Alternatively, you can run
the SM30 transaction and open the /ixos/oa_cust_a table.
Guide 17
ER160200-00-IGD-EN-1
2. Define the following settings:
Path and Script/appl

Path name and script/application name to call either Web Viewer or Java
Viewer:
• Web Viewer — the source code of the Web Viewer must be located
directly below the application directory of the web server. Therefore, the
application name is WebViewer.
• Java Viewer — the Java Viewer is called by a perl script that is located in
a subdirectory of the Content Server cgi-bin directory. Therefore, by
default the application name is /cgi-bin/JAVAVW/ixosjv.pl. If you
host the Java Viewer as Web Application, enter /JAVAVW/JavaViewer.
• Brava! View — after installation of Brava! View on a Windows host, the
application layer responding to the imaging integration resides in
location BravaView. Therefore, the application name is BravaView. In all
other settings of /IXOS/OA_CUST_A (or /IXOS/OA_CUST_B), IXOS/
18 Guide
ER160200-00-IGD-EN-1
OA_DOCTYPE, /IXOS/OA_IPRANGE maintain the settings of Brava! View as

if it were a WebViewer.
Viewer Usage
Possible values:
No
No external viewer is used.
Yes, if winviewer is not installed locally
The external viewer specified in the Viewer Type field is used if the
Windows Viewer is not installed locally.
Yes, if SET/GET parameter /IXOS/OA_JV = X
User-specific configuration; if the SET/GET parameter /IXOS/OA_JV = X
(defined in the user profile), the external viewer specified in the Viewer
Type field is used.
Yes
The external viewer specified in the Viewer Type field is always used.
Viewer Type
Possible values:
Java Viewer
Java Viewer
Web Viewer
Web Viewer and Brava! View.
Disable Caching
Specifies whether the information on the cache server stored in ArchiveLink
Cache customizing is used when generating the URL.
Disable Applet Inpl.
For the Java Viewer only: Specifies whether the Java Viewer is started in its
own browser window.
The height and width of this window can be defined using the subsequent
Viewer Window Width and Viewer Window Height parameters.
Use Cached Build
For the Java Viewer only: Deprecated parameter that does not work with Java
Viewer 9.5.x or later. If you use Java Viewer 9.5.x or later, ignore this
parameter.
Use HTTPS Protocol
If activated, the secure HTTPS protocol is used when the script is run.
3. If you selected the Web Viewer option above in the Viewer Type field, you can
specify the following additional parameters for default settings in the Web
Viewer Settings area:
Do not show Thumbs

Deactivates the default display of thumbnails.
Guide 19
ER160200-00-IGD-EN-1
Do not show Header

Deactivates the default display of the header line.
Show Notes
Activates the default display of document notes.
Open in curr. Window

Stops Web Viewer from opening a new browser window; viewer uses
current window instead.
Authority Check
Activates evaluation of authorization object J_6NV_WEBV which defines
rules for accessing and processing documents.
Use Signature
Restricts the usage and acceptance of URLs to signed Web Viewer URLs
only.
To configure the document classes:
the Maintain Document Classes for Viewer activity. Alternatively, you can run
the SM30 transaction and open the /ixos/oa_doctype table.
2. Define the following settings:
Document Type
Enter the document extension without leading dot, for example, JPG for
JPEG image documents.
Viewer Type
Enter the viewer type which will be used to display a specific type of
document. The available values are Java Viewer or Web Viewer. The
settings for Web Viewer are also used for Brava! View for SAP Solutions.
Important
Only document types maintained in the table /IXOS/OA_DOCTYPE
are opened with the JavaViewer or the Web Viewer; for all other
documents, the default viewer for ArchiveLink documents will be
used.
Document
After activation of BC set /OTEXBAS/VIEWER_CUSTOMIZING, the following
document and viewer type combinations are maintained by default:
Document Java Viewer Web Viewer

ALF x x
ASCII x x
FAX x x
20 Guide
ER160200-00-IGD-EN-1
Document Java Viewer Web Viewer

GIF x x
JPEG x x
JPG x x
OTF x x
PDF x
TIF x x
TIFF x x
To configure the viewer languages:
the Maintain Languages for Viewer activity. Alternatively, you can run the
SM30 transaction and open the /ixos/oa_locales table.
2. Select the required languages for the viewer.
Note: This setting does only apply to the Web Viewer or Brava! View and
does not influence the standard locale set for SAP.
3. To create an entry, click New Entries and specify the parameters for the new
element.
In order to optimize the network performance, you can assign specific IP address
ranges of a repository to a specific server. If the IP address of a client is within this
Guide 21
ER160200-00-IGD-EN-1
specific range, then the Web viewer or Brava! View from the local server specified in
the fields Servername:Port and Path and Script/appl is used to view documents.
To assign IP address ranges:
the Maintain IP Ranges for Viewer activity. Alternatively, you can run the
SM30 transaction and open the /ixos/oa_iprange table.
2. Specify the content repository and the range of the IP addresses.
3. Specify the server and the required script in the Servername:Port field and the
Path and Script/appl field respectively.
To configure the Force MimeType settings to display documents:
1. Run the SE16 transaction and open the /ixos/oa_cust3 table.
2. Define the following parameters:
AR_OBJECT
Document type for which the settings are defined.
FORCEMIMETYPE
MIME type which should be used on a client to display documents for the
corresponding document type. The MIME type settings (for example, app/
LLVIEW ) have to be specified in the client registry.
An example for the client registry setting could be:
[HKEY_CLASSES_ROOT\MIME\Database\Content Type\app/LLVIEW]
''extension''=''.fax''
22 Guide
ER160200-00-IGD-EN-1
3.2.3 Setting number ranges

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

performed to tables which contain the document ID in the key.
1. Execute the SNRO transaction.

2. Enter /IXOS/DC_K as object.
3. Click the Number ranges button.
4. Click the Change intervals button.
5. Click the Insert interval button.
6. Modify the interval 01:
From number = 1, To number = 9999999999.
7. Save your changes.
To set /IXOS/DCLO:
Note: The number range for the /IXOS/DCLO object is only necessary if the
protocol feature is activated for the attribute objects.
• Repeat the procedure as described for the /IXOS/DC_K object, using the interval
01:
From number = 1, To number = 9999999999.
3.2.4 Defining authorizations

You must set up authorizations and assign them to users. Some authorization
profiles are also supplied by the following components of Archiving and Document
Access for SAP Solutions:
• Forms Management
see “Authorizations” on page 27 for details
• DesktopLink
• DocuLink
Tip: For an overview of authorization maintenance, see section 6.3

“Authorizations in SAP applications” in OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).
Guide 23
ER160200-00-IGD-EN-1
3.2.5 Defining settings for logging

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

Optional DocuLink sample projects are available as downloads; for more details, see
section 2.6 “Sample projects overview” in OpenText DocuLink for SAP Solutions -
Customizing and Administration Guide (DC-CGD). If you want to use these projects,
you must define a number of additional settings in the SAP application.
• If you want to test the authorization check on data selection in the sample project
Linked objects then you must also assign the users the profile J_6NB_PROF
supplied with the sample project.
• In order to archive documents for customers within the document flow SD, the
archive must be set correctly in OAC3 transaction for the link J_6NGDKOR (object
type)/J_6NGDKORR (document type).
Note: Each customer has its own logical archive. Since we are not familiar
with these archives, we supply our own archive name DU set as the default.
• In order to archive documents for customers in the sample project Linked
objects, the archive must be set correctly in OAC3 transaction for the link
J_6NG_CUST/J_6NG_CUST.
Note: Each customer has its own logical archive. Since we are not familiar
with these archives, we supply our own archive name DU set as the default.
• Some number range intervals are required for the sample projects; use the SNRO
transaction to maintain them:
• For $EX_LINK (Linked objects) and $EX_FOLDER (Folder demo
(recurrent structure)) maintain interval 01 for the number range
J_6NG_DIV. Enter 1000 as the starting number.
• For $EX_CMDEMO (Demo CM document model) maintain the same number
range J_6NG_DIV, but with a different interval and distinct values, e.g.
interval 02 from 1000000001 - 2000000000 if the interval 01 from 1000 -
1000000000 was used for $EX_LINK.
24 Guide
ER160200-00-IGD-EN-1
3.3. Rendition management
3.3 Rendition management

The rendition management consists of the OpenText Rendition Server API (also
referred to as Rendition Server API) and two DocuLink monitoring projects called
RSUMONITOR and RS_TRFC_ST. Both monitoring projects may be downloaded from
OpenText My Support.
The Rendition Server API is a prerequisite for OpenText DesktopLink and is also
required when document processing/output utilizing the OpenText Rendition
Server shall be used in DocuLink.
The optional DocuLink monitoring projects called RSUMONITOR and RS_TRFC_ST are
utilities to review the logs of document renditions processed by the Rendition Server
API. RS_TRFC_ST is used for the display of the My job overview feature within
DocuLink.
Notes
• Rendition management also requires the installation of OpenText Rendition
Server as described in the OpenText Rendition Server - Installation and
Administration Guide (RS-IGD).
Installation of the monitoring project is not mandatory for rendition
management. It is intended as a help for the rendition log administration.
• After installation, you have to configure the rendition management. For
details, see “Configuring rendition management” on page 16.
3.4 Forms Management

3.4.1 General information
The following SAP partner name spaces are used:
• J8AF*
• J_8AF*
• J_8AS*
• /IXOS/FM
Message class is 81.
Guide 25
ER160200-00-IGD-EN-1
3.4.2 Installing Forms Management

Forms for forms overlay can also be maintained in a OpenText TCP Context Server.
This requires additional preparation.
To install Forms Management:
1. Perform the basis package installation with the SAINT tool (see “Installing
package” on page 13).
2. Install the Business Application Integration (BAI) on the server for OpenText
TCP Context Server.
3. Import the mapping configuration for Forms Management for OpenText TCP
Context Server in OpenText TCP Modeler.
a. Start OpenText TCP Modeler.

b. Activate the BAI plug-in:
i. Go to the menu, select Tools - Options and click the Plug-Ins tab.
Mark the TCP Mapping Tool check box in the list of available plug-
ins.
ii. Restart OpenText TCP Modeler. Now, the Mapping Configuration
node appears in the navigation area.
c. Right-click the Mapping Configuration node in the navigation area.
d. Select the Import Configuration command from the context menu.
e. Enter the path and file name of the mapping configuration file
sap_OverlayForm.ixbxml. This file is contained in a ZIP archive file
located in the patches area of OpenText My Support:
Forms Management (All Versions) - mapping configuration file
sap_OverlayForm.ixbxml (https://knowledge.opentext.com/knowledge/
llisapi.dll?func=ll&objId=62311236&objAction=browse&viewType=1)
Note that though located in a folder for ADA version 10.5.1, the file is valid
for all versions.
4. Perform the required customizing steps described in section 18 “OpenText

Forms Management” in OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS).
26 Guide
ER160200-00-IGD-EN-1
3.5. DesktopLink
3.4.3 Authorizations
Authorization profiles have to be assigned to users who are working with Forms
Management (see section 18.2 “Rights for OpenText Forms Management” in
OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS)
for details).
Example:
• Profile J_8AFM_ALL: Possesses all authorizations.

3.5 DesktopLink
In addition to the installation, you must perform the OpenText Imaging Clients
installation on a client in order to work with OpenText DesktopLink.

Used SAP partner name spaces
• J8AM*
• J_8AM*
• J_8AS*
• J8A3*
• J_8A3*
• /IXOS/DL*
• /IXOS/RS*
Message class is 81.
Special authorizations
If you are using an SAP GUI 6.20 or higher, you require an additional
authorization for the J8A8 transaction for DesktopLink 9.6.0. This is due to the
new SAP shortcut technique implemented in these versions to support the new
SAP GUI versions.
Guide 27
ER160200-00-IGD-EN-1
Authorization profiles have to be assigned to users who are working with
DesktopLink (see section 14.1.8.2 “Authorizations” in OpenText Archiving and
Document Access for SAP Solutions - Scenario Guide (ER-CCS) for details).
Examples:
• Profile J_8AM_ALL: Authorizes the user to archive all object types.

• Profile J_8AM_ADM: Authorizes all utilization and customizing rights, including
converting document formats and assigning target document classes.

3.6 Imaging Integration

The Livelink Imaging Integration with SAP contains the integration of OpenText
Imaging Java Viewer and OpenText Imaging Web Viewer with and RFC functions
that allow generic calls of functions from Preindexing in OpenText Imaging
Enterprise Scan.
Notes
• See the compatibility matrix in OpenText My Support to find out which

versions of OpenText Imaging Enterprise Scan allow calls of functions.
• Implementation of calls of SAP functions during Preindexing in OpenText
Imaging Enterprise Scan requires support from your OpenText consultant.
3.6.2 Installing Java Viewer on a Web Server as a CGI Script

Installation Java Viewer is an applet. The installation package contains a perl CGI script that can
help to generate the HTML markup including the APPLET tag and its configuration.
You can install Java Viewer on Archive Center where the web server is installed. The
installation package is provided as a zip file.
Language support
If you want to add languages to an existing installation, save the changed

viewer.cfg configuration file(s) from their locations. Repeat the Java Viewer
installation steps and copy the configuration file(s) back. For details, see
OpenText Imaging Viewers and DesktopLink - Installation and Administration Guide
(CL-IGD).
28 Guide
ER160200-00-IGD-EN-1
3.6. Imaging Integration
To install Java Viewer:
1. Make sure that the file system where the Java Viewer package will be copied is
writeable.
2. On the OpenText Imaging Viewers and DesktopLink installation media,
navigate to the \JavaViewer directory.
For support of other languages than English, see the language packs in My
Support at https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
16930708.
3. Unzip the JAVAVW.zip file to a temporary directory called <TMP>.
4. Copy the <TMP>\JAVAVW\w3\htdocs\ directory to target directory on the web
server. Under Windows, this is typically the <IXOS_ROOT>\w3\htdocs\
directory.
5. Optional steps for customers using the cgi script:
a. Copy the <TMP>\JAVAVW\w3\cgi-bin directory to the cgi-bin enabled

directory. Under Windows, this is typically the <IXOS_ROOT>\w3\cgi-bin\
directory.
b. Edit the first line in the ixosjv.pl Perl script, you have copied in the
previous step. It is originally placed in the <TMP>\JAVAVW\w3\cgi-bin\
JAVAVW\ directory. The first line has following structure: #!
<PATH_TO_PERL> -w. The <PATH_TO_PERL> must be a valid path to perl, for
example C:\Perl\perl.
6. Install JVM on the client computers, if not already done.
Installation on If you install Java Viewer on an HTTP server, for example an Internet Information
an HTTP server Server (IIS), you must extract w3vw.jar on the server side to get the Java Viewer
running.
SAP integration In order to use Java Viewer in SAP scenarios with Archiving and Document Access
for SAP Solutions (formerly known as Livelink ECM – Suite for SAP Solutions),
further installation and configuration is required. For more information, see
“Imaging Integration” on page 28 and section 20.2 “Configuration for Java Viewer/
Web Viewer/Brava! View” in OpenText Archiving and Document Access for SAP
Upgrade Old Java Viewer installations will be overwritten, no upgrade procedure is available.
OpenText recommends saving the viewer.cfg configuration file before the
installation. After installation, set the values in the new viewer.cfg file accordingly.
Checking Java In a heterogeneous environment with different older JVM versions on client
version on the computers, you may check whether the correct Java version is installed on the
clients
individual clients. For this, a small applet is available that checks the Java version on
the client and displays an error message if the supported version is not found. The
applet may impair performance and is thus not activated by default. To enable
checking, you need to include the following lines into the script or html page
invoking Java Viewer.
Guide 29
ER160200-00-IGD-EN-1
<BODY>
<APPLET
CODEBASE = "/JAVAVW"
CODE = "ixos.viewer.jvmchecker.JVMCheckerApplet"
WIDTH = 1
HEIGHT = 1
HSPACE = 0
VSPACE = 0
ALIGN = Middle
>
<param name="vu_StartupWindowHeight" value="100">
<param name="vu_StartupWindowWidth" value="500">
</APPLET>
If the installed version is not correct the applet provides a link to the Java download
page. By default, this is www.java.com/en/download/manual.jsp. If you want to
change this link, for example to change the language, open the file
<IXOS_ROOT>\w3\htdocs\JAVAVW\ixos\viewer\jvmchecker\messages.
properties and change the JVMTester.jvmLink key.
Note: If no Java version is available on the client, the applet will not work.
3.7 DocuLink
As part of the Basis package installation, the component OpenText DocuLink for
SAP Solutions (short: DocuLink) is installed as well. Read also the chapter
“Checking prerequisites“ on page 7 with general information on installation in an
SAP environment.

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

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

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

system again.

3.7.3 Testing the DocuLink installation

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

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

b. Click Generate.
No success message appears.
32 Guide
ER160200-00-IGD-EN-1
Chapter 4
Installing ERP option package
In addition to the Basis package, you may install the optional ERP package on ERP
systems. The ERP package contains specific code and objects, such as:
• DVS/PLM document nodetype in DocuLink – SAP GUI and SAP GUI for HTML
• Code to support optional DocuLink example projects – provided as download in
My Support
• DesktopLink support of PLM/DVS – transactions /IXOS/PLM, /IXOS/PLM_DL, /
IXOS/PLM_IMPORT, IXOS/PLM_SCAN
• ERP-specific example BOR objects
4.1 Installing the ERP package

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

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

following command:
of the SAPCAR file.
3. Carry out import of package as described in the respective SAP documentation.
Note: The optional ERP package does not contain any Business Customizing
Sets (BC Sets).
Guide 33
ER160200-00-IGD-EN-1
Chapter 5
Installing CRM option package
In addition to the Basis package, you may install the optional CRM package on CRM
systems. The CRM package contains coding to support the CM hierarchy link range
CRM in DocuLink and CRM-specific coding to enable the DocuLink CRM example
project, which can be downloaded from My Support. The CIC integration is
described in the OpenText DocuLink for SAP Solutions - Customizing and
Administration Guide (DC-CGD).
5.1 Installing the package

To install CRM package:

OTEXERP_CRM_1620_700. INST_CRM_700\DATA\ /usr/sap/trans
SAR

following command:
of the SAPCAR file.
Note: The optional CRM package does not contain any Business Customizing
Sets (BC Sets).
Guide 35
ER160200-00-IGD-EN-1
Chapter 6
Installing the SAP Fiori OData Services packages
Install this optional package, if you want to use the Fiori UI control for an
attachment list using ArchiveLink PLUS. You can install this package on an SAP
backend system with Backend Event Provider or SAP Gateway Foundation (read
release notes for specific requirements). The package contains the OData services
(model, service, model provider class, data provider class) for an attachment list
using ArchiveLink PLUS. For information about integration the functionaliy into
SAP Fiori apps see section 10 “Integrating Archiving and Document Access for SAP
Solutions into SAP Fiori apps” in OpenText Archiving and Document Access for SAP

To install the SAP OData Services package:

OTEXBASO_INST_1620_70 INST_ODATA_700\DATA /usr/sap/trans
0.SAR \

following command:
of the SAPCAR file.
Note: The optional SAP OData Services package does not contain any Business
Customizing Sets (BC Sets).
Guide 37
ER160200-00-IGD-EN-1
Chapter 7
Installing the SAP Fiori UI package
Install this optional package if you want to use the Fiori UI control for an attachment
list using ArchiveLink Plus. You may install this package on an SAP frontend
system with User Interface Technology (see release notes for specific requirements).
The package contains the Fiori UI apps (BSP applications) for an attachment list
using ArchiveLink PLUS (/OTX/ALF_DOC_UI), a test launcher app (/OTX/
RMF_LAUNCH) and a Fiori UI view (/OTX/ALF_DOCS4BC) for the integration into
the Fiori app of the OpenText Business Center. For information about integration the
functionality into SAP Fiori apps see section 10 “Integrating Archiving and
Document Access for SAP Solutions into SAP Fiori apps” in OpenText Archiving and
Document Access for SAP Solutions - Scenario Guide (ER-CCS).

To install SAP Fiori UI package:

OTEXBASF_INST_1620_74 INST_FIORI_740\DATA\ /usr/sap/trans
0.SAR

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

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

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

the OTEXBAS 10.5 Add-On on SAP_BASIS 7.00.
Note: Note the following options:

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

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

become necessary to reset certain buffers. For example, you can use the
following transactions:
• /$SYNC - reset all buffers
• /$OTR - reset OTR text buffers (HTTP texts)
• /$CUA - reset SAP GUI object buffers
• /$DYNP - reset SAP GUI dynpro buffers
Localization of Fiori apps

Starting with version 16.2, the Fiori apps contained in the Fiori UI Add-on package
OTEXBASF deliver i18n properties files, which are mapped to text tables on the
42 Guide
ER160200-00-IGD-EN-1
SAP system. Therefore specific language packages for Add-On package OTEXBASF
will be made available in OpenText My Support. The installation procedure is the
same as already described above.
Guide 43
ER160200-00-IGD-EN-1
Chapter 9
Upgrading to version 16.2
Depending on your current system configuration, you may perform one of the
following:
• “Upgrading to Archiving and Document Access for SAP Solutions 16.2”

on page 45
• “Upgrading the SAP system” on page 59
In both cases, OpenText provides special upgrade packages.
9.1 Upgrading to Archiving and Document Access

for SAP Solutions 16.2
Upgrading to Archiving and Document Access for SAP Solutions 16.2 is only tested
as upgrade from version 16; for details see “Delta upgrade from version 16 to 16.2”
on page 45.
Note the following:
• upgrade from version 10.5.0 - In the case of an upgrade from version 10.5.0,
install version 16 as an intermediate step; for details see “Intermediate step: delta
upgrade from version 10.5.0 to 16” on page 47.
• upgrade from version 10.0.0 - In the case of an upgrade from version 10.0.0,
install version 10.5.0 as an intermediate step; for details see “Intermediate step:
delta upgrade from version 10.0.0 to 10.5.0” on page 49. Then install version 16
as an intermediate step.
• direct upgrade from versions prior to 10.0.0 - The direct upgrade from versions
prior to 10.0.0 requires special care; for details see “Upgrading from versions
prior to SAP 6.0” on page 50.
9.1.1 Delta upgrade from version 16 to 16.2

The upgrade from OpenText Archiving and Document Access for SAP Solutions 16
to version 16.2 is called a delta upgrade, because the version of OpenText's Add-On
package changes while the SAP release remains unchanged. With version 16.2 no
specific delta upgrade packages are delivered. Instead, the upgrade is done by
installing the respective installation package in transaction SAINT.
The following delta upgrades are supported:
Guide 45
ER160200-00-IGD-EN-1
Chapter 9 Upgrading to version 16.2
Previous add-on Installation packages required

release
OTEXBAS 1600_700 OTEXBAS_INST_1620_700.SAR
OTEXERP 1600_600 OTEXERP_INST_1620_600.SAR
OTEXCRM 1600_700 OTEXCRM_INST_1620_700.SAR
OTEXBASO 1600_700 OTEXBASO_INST_1620_700.SAR
OTEXBASF 1600_740 OTEXBASF_INST_1620_740.SAR
Tip: Use the SAINT transaction to get an overview of the add-ons installed on
your SAP system.
To perform a delta upgrade procedure:
1. Copy the required SAPCAR files (*.SAR) located on the installation medium in
DIR_EPS_ROOT folder. The SAP Basis/SAP NetWeaver related package OTEXBAS
is always required, whereas the ERP and CRM specific packages are optional.
SAP Release Files Source Path Target Path

All supported SAP OTEXBAS_INST_16 INST_BAS_700\DA /usr/sap/trans
Releases SAP NW 20_700.SAR TA
7.0 AS upwards
All supported ERP OTEXERP_INST_16 INST_ERP_600\DA /usr/sap/trans
Releases SAP ERP 20_600.SAR TA
6.0 upwards
All supported CRM OTEXCRM_INST_1 INST_CRM_700\D /usr/sap/trans
Releases SAP CRM 620_700.SAR ATA
7.0 upwards
All supported SAP OTEXBASO_INST_ INST_ODATA_700\ /usr/sap/trans
Releases NW 700 AS 1620_700.SAR DATA
upwards with
Backend Event
Provider or SAP
Gateway
Foundation
All supported SAP OTEXBASF_INST_1 INST_FIORI_700\D /usr/sap/trans
Releases with User 620_740.SAR ATA
Interface
Technology
(SAP_UI)
46 Guide
ER160200-00-IGD-EN-1
9.1. Upgrading to Archiving and Document Access for SAP Solutions 16.2
2. Extract the SAPCAR files to the /usr/sap/trans/EPS/in folder with the

following command:
The resulting PAT files will be extracted to the EPS/in folder relative to the path
of the SAPCAR files.

After the upgrade, most of the customizing and configuration will not change.
4. For activation of BC sets of OTEXBAS, check the following:
Needs not to be activated if the BC set with the same name has already been
activated for version 9.6.2 or higher.
Needs not to be activated if the BC set with the same name has already been
activated for version 16.
Needs not to be activated if you already have done viewer customizing for
the previous version.
Tip: If you want to use additional features after upgrading to 16.2, for
example features not used in version 16, refer to “Configuring
components” on page 16 for details.
9.1.2 Intermediate step: delta upgrade from version 10.5.0 to

16
This section describes an intermediate step before finally upgrading to version 16.2.
The upgrade from OpenText Archiving and Document Access for SAP Solutions
10.5.0 (SP1) to version 16 is called a delta upgrade, because the version of OpenText's
Add-On package changes while the SAP release remains unchanged. With version
16 no specific delta upgrade packages are delivered. Instead the upgrade is done by
installing the respective installation package in transaction SAINT.
Table 9-1: Delta upgrades
Previous add-on release Installation packages required

Guide 47
ER160200-00-IGD-EN-1
Previous add-on release Installation packages required

your SAP system.
is always required, whereas the ERP and CRM specific packages are optional.

7.0 AS upwards
6.0 upwards
7.0 upwards

following command:

4. As this is only meant as an intermediate step, no BC sets of OTEXBAS need to

be activated. Continue with the steps described in “Delta upgrade from version
16 to 16.2” on page 45.
48 Guide
ER160200-00-IGD-EN-1
9.1.3 Intermediate step: delta upgrade from version 10.0.0 to

10.5.0
This section describes an intermediate step before the next intermediate step for
upgrading to version 16. The installation of support package 1 of Add-On OTEXBAS
10.5.0 is not necessary. The upgrade from Archiving and Document Access for SAP
Solutions 10.0.0 to version 10.5.0 is called a delta upgrade, because the version of
OpenText’s Add-On package changes while the SAP release remains unchanged.
With version 10.5.0, no specific delta upgrade packages are delivered. Instead, the
upgrade is done by installing the respective installation package in the SAINT
transaction.
Table 9-2: Delta upgrades
Previous add-on release Installation and support packages

required
Important
For CRM 7.0 and higher, the installation package OTEXCRM_INST_1050_700 is
available. In version 10.0, an installation package OTEXCRM_INST_1000_500
was available that could be installed on CRM 5.0 and higher.
your SAP system.
and their support packages are always required, whereas the ERP and CRM
specific packages are optional.

7.0 AS upwards
6.0 upwards
Guide 49
ER160200-00-IGD-EN-1

7.0 upwards

following command:

4. As this is only meant as an intermediate step, no BC sets of OTEXBAS need to be

activated. Continue with the steps described in .
9.1.4 Upgrading from versions prior to SAP 6.0

Depending on the exact SAP Release and Archiving and Document Access for SAP
Solutions version you are currently using, you may need further consulting. In the
following, you find examples from where you may be starting from.
Example: You have DocuLink 2.x on an R/3 4.6C system - upgrade to SAP 6.0 and follow the
instructions to upgrade from DocuLink 2.x to DocuLink 6.0. Continue with the path described
in “Upgrading from SAP 6.0 and Livelink ECM-Suite for SAP Solution 9.5.1 or 9.5.2”
on page 51.
Example: You have DocuLink 3.x on an R/3 4.6C system - upgrade to SAP 6.0 and continue
with the path described in “Upgrading from SAP 6.0 and Livelink ECM-Suite for SAP
Solution 9.5.1 or 9.5.2” on page 51.
Example: You have DocuLink 2.x on an R/3 4.7 system - You have the following options:
• install the transports of DocuLink version 9.6.0 and apply the upgrade description for
DocuLink 2.x to 9.6.0. Do the upgrade to SAP ERP 6.0 and then continue to upgrade the
OpenText Add-Ons as described in “Upgrading from Archiving and Document Access for
SAP Solutions 9.6.0 - 10.0.0” on page 53.
• upgrade to OTEXBAS and OTEXERP 10.0.0 as described in “Upgrading from Archiving and
Document Access for SAP Solutions 9.6.0 - 10.0.0” on page 53 and then do the upgrade
from R/3 4.7 to SAP ERP 6.0. After that perform a delta upgrade from 10.0.0 to 10.5.0 as
described in “Intermediate step: delta upgrade from version 10.0.0 to 10.5.0” on page 49
followed by a delta upgrade from 10.5.0 to 16 as described in “Intermediate step: delta
upgrade from version 10.5.0 to 16” on page 47 and then and then followed by a delta
upgrade from 16 to 16.2 as described in “Delta upgrade from version 16 to 16.2”
on page 45.
50 Guide
ER160200-00-IGD-EN-1
Caution
Do not forget to select the exchange packages of OTEXBAS and OTEXERP 10.0
during IS_SELECT phase. Read the disclaimer about SAP system upgrades
in the OpenText Archiving and Document Access Installation and Upgrade
Guide 10.0.0 (https://knowledge.opentext.com/knowledge/piroot/er/
v100000/er-igd/docovw.xml).
Example: You have DocuLink 3.x on an R/3 4.7 system - you have the following options:
• install the transports of DocuLink version 9.6.0 and follow the upgrade description for
DocuLink 3.x to 9.6.0. Do the upgrade to SAP ERP 6.0 and continue to upgrade the
OpenText Add-Ons as described in “Upgrading from Archiving and Document Access for
SAP Solutions 9.6.0 - 10.0.0” on page 53.
• upgrade to OTEXBAS and OTEXERP 10.0.0 as described in “Upgrading from Archiving
and Document Access for SAP Solutions 9.6.0 - 10.0.0” on page 53 and then do the
upgrade from R/3 4.7 to SAP ERP 6.0. After that, do a delta upgrade from 10.0.0 to 10.5.0 as
described in “Intermediate step: delta upgrade from version 10.0.0 to 10.5.0” on page 49.
After that, perform the delta upgrade from 10.5.0 to 16 as described in “Intermediate step:
delta upgrade from version 10.5.0 to 16” on page 47 and then followed by a delta upgrade
from 16 to 16.2 as described in “Delta upgrade from version 16 to 16.2” on page 45.
Caution
Do not forget to select the exchange packages of OTEXBAS and OTEXERP 10.0
during IS_SELECT phase. Read the disclaimer about SAP system upgrades
in the OpenText Archiving and Document Access Installation and Upgrade
Guide 10.0.0 (https://knowledge.opentext.com/knowledge/piroot/er/
v100000/er-igd/docovw.xml).
Note: Contact your OpenText consultant for planning your individual upgrade
strategy. Furthermore, the Knowledge Base of OpenText My Support provides
additional articles about upgrade paths.
9.1.5 Upgrading from SAP 6.0 and Livelink ECM-Suite for SAP
Solution 9.5.1 or 9.5.2
Livelink ECM-Suite for SAP Solution 9.5 also delivered a branch for 6.0 including
transports for R/3 4.6C. After that, two special add-on package versions 9.5.1 and
9.5.2 were available for use in R/3 4.6C for both reselling and direct OpenText
customers. In these cases you need to upgrade your R/3 4.6C to a SAP ERP 6.0
system. To do this, the following upgrade path is recommended:
1. After performing transports of version 6.0 on R/3 4.6C, use transaction SAINT to
install Add-ons of OTEXBAS and OTEXERP of version 9.5.1 on client 000.
2. Use transaction SAINT to install Add-Ons of OTEXBAS and OTEXERP of version

9.5.2 on client 000.
Guide 51
ER160200-00-IGD-EN-1
3. Upgrade your SAP system to SAP ERP 6.0. During this system upgrade, select
the Exchange upgrade packages of OTEXBAS 0962_700 and OTEXERP 0962_600
to execute an upgrade to version 9.6.2 on ERP 6.0.
Caution
Caution: Read the disclaimer about SAP system upgrades in the
OpenText Archiving and Document Access Installation and Upgrade
Guide 9.6.2 (https://knowledge.opentext.com/knowledge/cs.dll?
func=ll&objaction=overview&objid=16364631).
Important
There is a significant change in the interfaces of DocuLink User-Exits
when changing from version 9.5.1, 9.5.2 or SAP 6.0 to 9.6.2. If you had
DocuLink projects with User-Exits, contact your OpenText consultant to
re-implement the User-Exits based on the interfaces as introduced with
9.5.0 or 9.6.x.
4. Continue with the upgrade path of version 9.6.2 as described in “Upgrading

from Archiving and Document Access for SAP Solutions 9.6.0 - 10.0.0”
on page 53.
If you have the non-unicode DocuLink 6.0 branch installed on an R/3 4.7 or newer
system, and you want upgrading to DocuLink 10.5, you also must upgrade to SAP
ERP 6.0 or an EhP of SAP ERP 6.0.
In this case, we recommend the following upgrade path:
1. Install the Archiving and Document Access for SAP Solutions 9.6.0 transports.
Important
Between 6.0 and 9.5, there is a significant change in the interfaces of
DocuLink User-Exits. If you have DocuLink projects with User-Exits,
contact your OpenText consultant to re-implement the User-Exits based
on the interfaces as introduced with 9.5.0 or higher. Consider to do this
step at the end of your full upgrade path before going live with the
updated version.
2. Upgrade your SAP system.
3. Continue with the upgrade path from version 9.6.0 to 16.2 as described in
“Upgrading from Archiving and Document Access for SAP Solutions 9.6.0 -
10.0.0” on page 53.
52 Guide
ER160200-00-IGD-EN-1
9.1.6 Upgrading from Livelink ECM-Suite for SAP Solution

9.5.0
This section treats the transports of this release for SAP Basis 6.x and higher. Install
the transports of version 9.6.0 and follow the path as described in “Upgrading from
Archiving and Document Access for SAP Solutions 9.6.0 - 10.0.0” on page 53.
9.1.7 Upgrading from Archiving and Document Access for

SAP Solutions 9.6.0 - 10.0.0
To start from transport version 9.6.0 or higher, OpenText recommends the following
upgrade path:
9.6.0 < 9.6.1+SP1 < 9.6.2 < 9.8.0 < 10.0.0 < 10.5.0 SP1 < 16 < 16.2.
This upgrade path can be followed directly on ERP 6.0, CRM 7.0, SRM 7.0 systems or
their respective EHP-releases. If your SAP System is an older release, e.g. R/3 4.7,
SAP ECC 5.0, SAP CRM 5.0, or SAP CRM 2006, the last supported ADA version is
10.0.0 including SP1 + SP2. To upgrade to version 16.2, you must upgrade your SAP
release first and then upgrade to 16.2. See “Upgrading the SAP system”
on page 59.
On ERP-Systems - if you also want to update the optional OTEXERP package, note
that the OTEXERP package 9.6.1 only supports ERP 6.0. Using an Attribute Change
Package, it supports also EHP2, EHP3 or EHP4 for ERP 6.0. If you have already
installed a higher EHP x for SAP ERP 6.0, install OTEXERP 9.6.2 with its installation
package.
To follow the upgrade path, note the following:
1. Download all installation and upgrade resources from the SAP Service
Marketplace and/or OpenText My Support. Customers who bought from SAP
are entitled to get access to OpenText My Support and its Patch areas.
2. To obtain the Add-On’s installation passwords, see the installation guides of

Archiving and Document Access for SAP Solutions versions 9.6.1 - 16.2.
3. Check the latest Release Notes of Archiving and Document Access and the
Patches area in OpenText My Support (https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/14162727) for language packages. All languages
supported for version 16 will also be supported for 16.2. If the required
language is not yet available in 16.2, consider to install the language packages of
16 before updating to 16.2.
4. When upgrading from 9.6.0, for example as customer who bought the license
from OpenText, install all client independent transports delivered for Livelink
ECM Suite for SAP Solutions 9.6.0 from the installation CD. Do not apply any
patches.
5. When upgrading from 9.6.0 with patches of 9.6.0, there can already exist some
erroneous entries of Add-On packages OTEXBAS and OTEXERP. This is a known
Guide 53
ER160200-00-IGD-EN-1
issue. Contact OpenText Customer Support to be provided with a special

correction program and guidance how to use it.
6. Upload all Add-On packages of OTEXBAS (and optionally OTEXERP) to the EPS\
in folder of your SAP system:
• Installation packages of OTEXBAS and OTEXERP 9.6.1

• Support package 1 of OTEXBAS 9.6.1
• Delta upgrade packages of OTEXBAS 9.6.2 and OTEXERP 9.6.2
• Delta upgrade packages of OTEXBAS 9.8.0 and OTEXERP 9.8.0
• Installation packages of OTEXBAS 10.0.0 and OTEXERP 10.0.0
• Installation packages of OTEXBAS 10.5.0 and OTEXERP 10.5.0
Support Package 1 of OTEXBAS 10.5.0
• Installation packages of OTEXBAS 16 and OTEXERP 16
• Installation packages of OTEXBAS 16.2 and OTEXERP 16.2.
7. Check if you already have configured DesktopLink and DocuLink as GOS
services. Execute transaction SM30 and check table SGOSATTR. Note down the
entries, for example entries like IXOS_DC or IXOS_DL.
8. After installing the packages in steps 9- 17, do not apply any BC set activation
yet. Instead, check and apply the BC sets of version 16.2 in a later step.
9. Execute transaction SAINT on client 000 to install package OTEXBAS 9.6.1. In the
same installation queue, select support package 1 as target patch level.
10. Install OTEXERP 9.6.1 or skip, if you have issues with the EHP level of the SAP
ERP 6.0 Release.
11. Execute transaction SAINT on client 000 to install delta upgrade package of
OTEXBAS 9.6.2.
12. Install delta upgrade package of OTEXERP 9.6.2. If you had to skip the
installation of 9.6.1, use the installation package of OTEXERP 9.6.1 instead.
13. Execute transaction SAINT on client 000 to install delta upgrade package of
OTEXBAS 9.8.0..
14. Install delta upgrade package of OTEXERP 9.8.0.

15. Execute transaction SAINT on client 000 to install installation package of OTEXBAS
10.0.0. Then install installation package of OTEXERP 10.0.0.
16. Execute transaction SAINT on client 000 to install installation package of

OTEXBAS 10.5.0. Afterwards, install installation package of OTEXERP 10.5.0.
16.0.0. Afterwards, install installation package of OTEXERP 16.0.0.
• If no language packages for 16.2 are available yet, execute transaction SAINT
in client 000 to install installation package of OTEXBAS 16. Then install
54 Guide
ER160200-00-IGD-EN-1
installation package OTEXERP 16. Afterwards, install the language packages

for OTEXBAS 16 and OTEXERP 16.
16.2. Then install installation package of OTEXERP 16.2.
19. Execute transaction SM30 and check table SGOSATTR. Look for entries from
DocuLink and/or DesktopLink using names IXOS_DC or IXOS_DL. Check if the
entries are consistent with the settings of the other services. Replace the entries
with the ones you noted down before in step 7. This is necessary because in
versions 9.6.1 to 9.8, entries were erroneously included. This can cause errors
when calling GOS. See also section 15 “Archiving using generic object services
(GOS) (for SAP ERP only) ” in OpenText Archiving and Document Access for SAP
20. Execute transaction SCPR20 to perform the following BC Set activation for
OTEXBAS 16.2 on your test client:
Note: You cannot apply Business Configuration Sets (BC Sets) on systems
with a productive client. Apply the BC Sets on a development or test client
to create customizing transports for the production system. You can
execute transaction SCPR20 using the menu option Utilities > Compare >
Compare BC Sets with Tables. This allows you to check the content of the
BC set compared to the current content of the systems customizing tables.
21. If you have used DocuLink before, execute transaction J6NA to delete generated
reports.
22. You may need language packages of version 16.2 for other languages than
English. Please note, that language packages of version 16 can be used
preliminary. Check the latest Release Notes and the Patches area of OpenText
My Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
14162727) for the respective packages. See chapters about language import and
installation in this guide for further details and import the language packages
for OTEXBAS and OTEXERP in transaction SMLT accordingly.
On CRM-Systems - instead of the optional OTEXERP package for each version you
can install the respective OTEXCRM package right after the related OTEXBAS package.
Per version, the following packages are available:

• For 9.6.1 – OTEXCRM packages for CRM 4.0 and CRM 5.0
• For 9.6.2 – OTEXCRM packages for CRM 4.0, CRM 5.0, CRM 6.0, and higher
• For 9.8.0 – OTEXCRM package for CRM 5.0 and higher
• For 10.0.0 – OTEXCRM package for CRM 5.0 and higher
Guide 55
ER160200-00-IGD-EN-1
• For 10.5.0 and 10.5.0 SP1 – OTEXCRM package for CRM 7.0 and higher
• For 16 – OTEXCRM package for CRM 7.0 and higher
• For 16.2 – OTEXCRM package for CRM 7.0 and higher
Example 9-1:
You are starting on a CRM 7.0 system and you have installed 9.6.2 with
optional OTEXCRM package. Use the following for upgrading:
1. delta upgrade package for OTEXCRM 9.8

2. installation packages of OTEXCRM 10.0
If you are starting on lower releases, check “Upgrading the SAP system”
on page 59.
On SRM-Systems - there is no optional SRM-Package for Archiving and Document

Access for SAP Solutions. Just follow the upgrade path of package OTEXBAS.
strategy. Furthermore, the Knowledge Base of OpenText My Support provides
additional articles about upgrade paths.
9.1.8 OpenText Employee File Management 2.5

The OTEXEIM 0250_... add-on packages of OpenText Employee File Management 2.5
works together with the respective OTEXBAS 0962_... add-ons of Archiving and
Document Access for SAP Solutions 9.6.2. They contain some objects which were
migrated to the OTEXBAS 0980_... add-on packages of Archiving and Document
Access for SAP Solutions 9.8.0. Therefore customers with an installation of OTEXEIM
0250_... should always do the combined upgrade with the upgrade packages
OTEXEIM 0300_... and OTEXBAS 0980_... before upgrading to version OTEXBAS
1000_... of Archiving and Document Access for SAP Solutions 10.0.0. Read the
installation and upgrade guides and Release Notes of OpenText Employee File
Management for more details.
56 Guide
ER160200-00-IGD-EN-1
9.1.9 Equivalencies of OTEXBAS, OTEXERP and OTEXCRM

packages
This chapter lists how releases and support package levels of Add-On packages are
superseded by releases or support package levels of the directly following release
version. The list refers to support packages and versions released until Archiving
and Document Access for SAP Solutions 16.0
Release/Support Package level Superseded by

OTEXBAS
Livelink for SAP Solutions 9.6.0 and Patches OTEXBAS 9.6.1 SP1
transports
OTEXBAS 9.6.1 OTEXBAS 9.6.2
OTEXBAS 9.6.1 SP1 OTEXBAS 9.6.2
OTEXBAS 9.6.2 SP3 OTEXBAS 9.8.0 SP2
OTEXBAS 9.8.0 SP2 OTEXBAS 10.0.0 SP2
OTEXBAS 10.5.0 OTEXBAS 16
OTEXBAS 10.5.0 SP1 OTEXBAS 16
also see Release Notes
OTEXBAS 16 OTEXBAS 16.2
OTEXERP
Livelink for SAP Solutions 9.6.0 and Patches OTEXERP 9.6.1
transports
OTEXERP 9.6.1 OTEXERP 9.6.2
OTEXERP 10.5.0 OTEXERP 16
Guide 57
ER160200-00-IGD-EN-1
Release/Support Package level Superseded by

OTEXERP 16 OTEXERP 16.2
OTEXCRM
Livelink for SAP Solutions 9.6.0 and Patches OTEXCRM 9.6.1
transports
OTEXCRM 9.6.1 OTEXCRM 9.6.2
OTEXCRM 10.5.0 OTEXCRM 16
OTEXCRM 16 OTEXCRM 16.2
OTEXBASO
OTEXBASO 16 OTEXBASO 16.2
OTEXBASF
OTEXBASF 16 OTEXBASF 16.2
OTEXBASF 16 SP1 OTEXBASF 16.2
Use this table to continue the step-by-step upgrades in transaction SAINT as

described starting with section “Upgrading from Livelink ECM-Suite for SAP
Solution 9.5.0” on page 53.
Example 9-2:
You have a source SAP ERP system with OTEXBAS 9.6.0 SP3 and OTEXERP
9.6.2 installed. To upgrade to 16.2, proceed as follows: the table shows
OTEXBAS 9.6.0 SP3 > superseded by OTEXBAS 9.8.0 SP2 > superseded by
OTEXBAS 10.0.0 SP2 > superseded by OTEXBAS 10.5.0 > superseded by
OTEXBAS 16 superseded by OTEXBAS 16.2.
Do the following:
1. Upload OTEXBAS 9.8.0 including SP1 + SP2 and OTEXERP 9.8.0. Install
OTEXBAS 9.8.0 in transaction SAINT. Select SP2 as the target support
package level.
Install OTEXERP 9.8.0.
2. Upload OTEXBAS 10.0.0 including SP1 + SP2 and OTEXERP 10.0.0.
Install OTEXBAS 10.0.0 in transaction SAINT. Select SP2 as the target
support package level.
Install OTEXERP 10.0.0.
3. Continue with OTEXBAS 10.5.0 and OTEXERP 10.5.0.
4. Continue with OTEXBAS 16 and OTEXERP 16.
5. Finally install OTEXBAS 16.2 and OTEXERP 16.2.
58 Guide
ER160200-00-IGD-EN-1
9.2. Upgrading the SAP system
9.2 Upgrading the SAP system

Disclaimer
When you upgrade an SAP release (R/3, ERP, CRM) to a higher release, the system
automatically recognizes that an SAP add-on is installed and requests the respective
upgrade package. This way the standard SAP upgrade procedure also updates the
Archiving and Document Access for SAP Solutions add-ons to the relevant version.
Caution
If you import an upgrade into an SAP system with Archiving and
Document Access for SAP Solutions and the data of the respective upgrade
packages is not read (upgrade phase IS_SELECT), the Archiving and
Document Access for SAP Solutions add-on (i.e. OTEXBAS, OTEXERP,
OTEXCRM) will no longer work after the upgrade procedure. Since the status
of the system is then inconsistent, OpenText can no longer accept any
liability.
Note that there are no exchange upgrade packages for OpenText Archiving
and Document Access 16.2. Keep the existing packages (Select KEEP in
upgrade phase IS_SELECT). To allow a keep you may need a vendor key or
an Attribute Change Package. For target SAP Releases with SAP Netweaver
7.02 and higher, SAP enforces to use Attribute Change Packages (ACP’s)
instead of vendor keys to match the versions of the target release. See the
Release Notes of OpenText Archiving and Document Access 16.2 to get
information about ACP’s and vendor keys.
9.2.1 Exchange upgrades keeping 16.2

Archiving and Document Access for SAP Solutions 16.2 is delivered with packages
that are installable on several ERP, CRM and SRM Systems based on SAP
NetWeaver 7.0 or compatible. See the latest Release Notes of Archiving and
Document Access for SAP Solutions for an updated list. Therefore, no Exchange
Upgrade packages were created for this version. Instead, keep the already installed
Add-On packages of Archiving and Document Access for SAP Solutions as
suggested in the table below. To do this, select KEEP to keep the packages during
upgrade phase IS_SELECT and use the vendor keys as listed in the Release Notes of
OpenText Archiving and Document Access for SAP Solutions 16.2.
strategy.
The following exchange upgrades are supported:
Guide 59
ER160200-00-IGD-EN-1
Table 9-3: EHP Upgrades for SAP system
Upgrade from ADA 16 on Upgrade to ADA 16.2 on Upgrade

SAP ERP 6.0 EHP x for SAP ERP 6.0 Select KEEP in the upgrade
EHP x for SAP ERP 6.0 phase IS_SELECT of
OTEXBAS and OTEXERP.
Vendor keys are required.
SAP CRM 7.0 EHP x for SAP CRM 7.0 Select KEEP in the upgrade
EHP x for SAP CRM 7.0 phase IS_SELECT of
OTEXBAS and OTEXCRM.
SAP SRM 7.0 EHP x for SAP SRM 7.0 Select KEEP in the upgrade
EHPx for SAP SRM 7.0 phase IS_SELECT of
OTEXBAS.
Note: See the latest Release Notes of Archiving and Document Access for SAP
Solutions to get the required vendor keys. Check also for additional notes on
installation and updates.
To perform an exchange upgrade procedure:
1. Follow the standard SAP system upgrade instructions. During upgrade phase
IS_SELECT, select KEEP for the installed add-ons Upgrade with SAINT Package
(applies to OTEXBAS, OTEXERP, packages).
Note: Apply the vendor keys from the Release Notes for the KEEP
operations, if necessary.
2. After the upgrade, no activation of BC sets is necessary.
Note: Archiving and Document Access for SAP Solutions 16.2 is not delivered
anymore for older releases like SAP R/3 4.7, SAP ECC 5.0 , SAP CRM 5.0 or
SAP CRM 2007. If you have an older version of Archiving and Document
Access for SAP Solutions installed on SAP R/3 4.7 or SAP ECC 5.0, you can
upgrade first to version 10.0, do the system upgrade and use the exchange
upgrade packages of 10.0 as described in the OpenText Archiving and
Document Access for SAP Solutions 10.0.0 installation guide (https://
knowledge.opentext.com/knowledge/piroot/er/v100000/er-igd/docovw.xml).
Another valid path option would be to do Exchange upgrades with Archiving
and Document Access for SAP Solutions 9.6.2 or 9.8 at place and then on the
target SAP release to continue an update path as described in “Upgrading from
Archiving and Document Access for SAP Solutions 9.6.0 - 10.0.0” on page 53.
From SAP CRM 5.0 or SAP CRM 2007, you can upgrade OTEXBAS and OTEXCRM
to version 10.0 and then do an exchange upgrade to the SAP target release, for
example SAP CRM 7.0. On the target release, continue a delta upgrade by
installing OTEXBAS and OTEXCRM version 16.2 as described in “Upgrading from
60 Guide
ER160200-00-IGD-EN-1
9.2. Upgrading the SAP system
Archiving and Document Access for SAP Solutions 9.6.0 - 10.0.0” on page 53
for step 16.
Guide 61
ER160200-00-IGD-EN-1
Chapter 10
Uninstalling Add-Ons
Starting with Version 5.0 of the Add-On Assembly Kit, SAP makes it possible to
create add-ons that can be uninstalled. At present, OpenText Archiving and
Document Access for SAP Solutions 16.2 does not deliver any Add-On that can be
uninstalled. For updates on this topic, refer to the latest release notes of OpenText
Archiving and Document Access for SAP Solutions 16.2, which can be downloaded
from OpenText My Support (https://knowledge.opentext.com).
Guide 63
ER160200-00-IGD-EN-1
Chapter 11
Handling communication protocols
Communication protocols define the way a document class is handled in SAP

applications. A protocol is assigned to an archive (content repository, storage
system). This ensures that all documents of a document class held in the same
archive (content repository) are handled in the same way.
Tip: For more information on protocols, see section 20.1.1.1 “Communication

protocols in SAP applications” in OpenText Archiving and Document Access for
SAP Solutions - Scenario Guide (ER-CCS).
This chapter describes the handling of the ArchiveLink communication protocols on

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

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

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

NO_TYPELIB
66 Guide
ER160200-00-IGD-EN-1
11.2. Maintaining SAP ArchiveLink application
7. Click .
The ClassId (CLSID) is registered for the OpenText Imaging Enterprise Scan
application.
11.2 Maintaining SAP ArchiveLink application

If the ArchiveLink applications do not already exist, you have to create them
manually.
The following ArchiveLink applications must be present:

• IXSCAN
• IXSCAN_HTTP
• IXVIEWER
• IXVIEWERURL
• IXVIEWERURLOA
To modify or create ArchiveLink application:
1. In the IMG, run the OpenText Archiving and Document Access for SAP
Solutions > DesktopLink and Archiving for SAP Solutions > ArchiveLink >
Front End Communication Customizing > Maintain Applications activity.
Alternatively, you can run the OAA4 transaction (ArchiveLink Application
Maintenance).
If not already listed, create the ArchiveLink applications listed above
(IXSCAN_HTTP, IXVIEWER, IXVIEWERURL, IXVIEWERURLOA).
2. Double-click the specific ArchiveLink application entry for additional
configuration.
Guide 67
ER160200-00-IGD-EN-1
All functions for the selected ArchiveLink application are listed.
3. Double-click a specific function to maintain or modify its settings.

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

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

Archive from IXOS.IXSCAN.SC M SendDoc2DP @AID,
Frontend 2SAP
G @DID=DocID
G @EID=ErrorID
Store File on IXOS.IXSCAN.SC M SaveActiveDocMultipage 0
Frontend 2SAP
G @DPA=DocPathName
G @EID=ErrorID
Guide 69
ER160200-00-IGD-EN-1
IXSCAN_HTTP

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

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

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

Document
M OpenDocumentSimpleUrl
@WID,@URL,@WIT,@UID
G @EID=R3ReturnCode
G @EID=R3ReturnCode
Frontend
G @DID=DocID
G @EID=ErrorID
Guide 71
ER160200-00-IGD-EN-1

Frontend
G @EID=R3ReturnCode
11.3 Maintaining viewer components

These protocol settings determine which viewer component will be used for
document display:
• OT_HTTP2
For document display, the Web browser is invoked.
• OT_HTTP3
For document display, the Web browser is invoked. For scanning using the
archive ID and the document ID, an URL is created that can be signed. This URL
is passed on to the scan client.
• OT_OLEU1
For document display, the OpenText Imaging Windows Viewer will be invoked
via OLE.
• OT_OLEU2
For document display, the OpenText Imaging Windows Viewer will be invoked
via OLE. For scanning using the archive ID and the document ID, an URL is
created which can be signed. This URL is passed on to the scan client.
The protocols have to be modified or created if they do not exist yet.
To modify or create protocols:
1. Execute the OAA3 transaction (Protocol settings Maintenance).

If not already listed, create the protocols listed above (OT_HTTP2, OT_HTTP3,
OT_OLEU1, OT_OLEU2).
2. Double-click on the specific protocol entry.
72 Guide
ER160200-00-IGD-EN-1
11.3. Maintaining viewer components
The Overview of Protocol screen appears; a tree view shows the details of the
respective ArchiveLink protocol.
3. Double-click on a specific function.

A list of related document classes is displayed.
Guide 73
ER160200-00-IGD-EN-1
4. For explicit maintenance, select the combo box item of the required document
class and then double-click on the document class entry.
The following shows the settings screen for the document class ALF.
74 Guide
ER160200-00-IGD-EN-1
11.3. Maintaining viewer components
5. Modify the settings according to the following tables.

OT_HTTP2 protocol
Function Doc.class Communication Application

Type
Display Stored Document ALF OPEN_V_URL IXVIEWERU
RL
Display Stored Document MSG ARCHIVELNK
Archive from frontend FAX , JPG OPEN IXSCAN
Close Window * OPEN DUMMY
OT_HTTP3 protocol

Type
Display Stored Document ALF OPEN_V_URL IXVIEWERU
RL
Display Stored Document MSG ARCHIVELNK
Archive from frontend FAX , JPG OPEN IXSCAN_HT
TP
OT_OLEU1 protocol

Type
Display Stored Document * , ALF , FAX , JPG , OPEN_V_URL IXVIEWERU
OTF , PDF , TIF RLOA
Retrieval Frontend * OPEN IXVIEWER
Display Local File * ARCHIVELINK
Archive from frontend FAX , JPG OPEN IXSCAN
Close Window ALF , FAX , JPG , OPEN IXVIEWER
OTF , PDF , TIF
Guide 75
ER160200-00-IGD-EN-1
OT_OLEU2 protocol

Type
Display Stored Document * , ALF , FAX , JPG , OPEN_V_URL IXVIEWERU
OTF , PDF , TIF RLOA
Retrieval Frontend * OPEN IXVIEWER
Display Local File * ARCHIVELINK
Archive from frontend FAX , JPG OPEN IXSCAN_HT
TP
Close Window ALF , FAX , JPG , OPEN IXVIEWER
OTF , PDF , TIF
6. Click to store the settings.
11.4 Assigning protocols to logical archives (content

repositories)
These protocol settings define the protocol to be used for all documents in a specific
logical archive.
To assign a protocol to a logical archive:
1. Execute the OAC0 transaction.
2. Select an already created logical archive and click the Full Administration
button.
3. Enter either OT_HTTP2 or OT_OLEU1 in the Protocol field.
4. Click to store the settings.
76 Guide
ER160200-00-IGD-EN-1
Chapter 12
Troubleshooting
When general problems occur during installation, check the following points, or
carry out the tasks described:
1. Check if the SAP basis version on your system is supported by the component
you would like to install (see the latest Release Notes in My Support).
2. For Oracle database only: Check whether the OracleTCPListener has been started
on the SAP database server.
3. Check the transport directory in the /usr/sap/trans/bin/TPPARAM file; it
should be specified as the global parameter transdir. Copy the data and the co-
file into this directory. Repeat the addtobuffer and import commands.
4. Modify the TPPARAM file so that the comments are on a separate line like in the
following example:
# SID
<SID>/dbname = <SID>
# TCP/IP name of transport host
<SID>/dbhost = <TRNASHOST>
# <DBTYPE>: ora sqd mss
<SID>/dbtype = <DBTYPE>
# normally PATH linked to \\<TRANSHOST>\sapmnt\<SID>\SYS\exe\run
<SID>/r3transpath = R3trans.exe
# normally PATH linked to \\<TRANSHOST>\sapmnt\<SID>\SYS\exe\run
<SID>/sapevtpath = sapevt.exe
5. Check if the correct authorizations and number ranges were defined.
6. If issues occur when calculating Archive URL’s, check SAP support note 1833702
(http://service.sap.com/sap/support/notes/1833702). The note fixes issues of
function SCMS_LOCATION_GET, which is used in function SCMS_URL_GENERATE.
Guide 77
ER160200-00-IGD-EN-1

OpenText Archiving and Document Access For SAP Solutions 16.2 - Installation and Upgrade Guide English (ER160200-00-IGD-EN-1)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Archiving and Document Access For SAP Solutions 16.2 - Installation and Upgrade Guide English (ER160200-00-IGD-EN-1)

Uploaded by

Copyright:

Available Formats

Installation and Upgrade Guide

OpenText™ Archiving and Document

The OpenText Archiving and Document Access for SAP

Open Text Corporation

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

Copyright © 2017 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

2 Checking prerequisites ............................................................. 7

3 Installing Basis package ......................................................... 13

4 Installing ERP option package ............................................... 33

5 Installing CRM option package .............................................. 35

6 Installing the SAP Fiori OData Services packages .............. 37

7 Installing the SAP Fiori UI package ....................................... 39

8 Installing language packages ................................................. 41

9 Upgrading to version 16.2 ...................................................... 45

10 Uninstalling Add-Ons .............................................................. 63

11 Handling communication protocols ...................................... 65

Archiving and Document Access for SAP Solutions software

• SAP Fiori UI package OTEXBASF (optional)

2.1 Required knowledge

2.2 Software packages

2.3 Terms and definitions

DPA Name of the system used by OpenText

2.4 SAP prerequisites

SAP support packages

• Activation of the Business Configuration sets (BC sets)

2.5 Installation tool

• The handling of the installation procedure within SAINT differs depending

2.6 Installation packages and passwords

Table 2-1: Installation packages and passwords

Package Designation Release Password

Package Designation Release Password

SAP Note 567695

2.7 Web Dynpro configuration

Installing Basis package

3.1 Installing package

To install Basis package:

File Source Path Target path

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

SAPCAR -xvf <name of SAPCAR file>

1. Execute the SCPR20 transaction.

Note: For more details, see the SAP documentation.

3. If you experience errors during BC Set activation, repeat the respective

For every client, the default project $GARMISCH is required by DocuLink.

To create the DocuLink project $GARMISCH initially:

1. Execute the SPRO transaction. In IMG, go to OpenText Archiving and

2. The start screen of the /IXOS/DC_A_CREATE_GARMISCH report is displayed.

Note: This DocuLink project $GARMISCH may not be modified manually. It

To export the DocuLink project $GARMISCH from your customizing client:

1. Execute the J6NP transaction.

3. Click the icon or press SHIFT-F6.

Regarding the export of DocuLink projects as customizing transport requests, refer

3.2 Configuring components

To configure Rendition Server API:

1. Execute the SM30 transaction to maintain the tables /IXOS/RSA_T_CONF and /

2. Execute the SM30 transaction to maintain the table /IXOS/RSA_T_TAFO

Document class MIME type of a Web object

This standard setting of table /IXOS/RSA_T_TAFO is also delivered by

3. Execute the DocuLink administration transaction J6NA to maintain the tables /

3.2.2 Configuration for Java Viewer/Web Viewer/Brava! View

To maintain the imaging integration:

a. Run the SE16 transaction and open the TOAEX table.

To configure the external viewer: