Вы находитесь на странице: 1из 54

Installation and Upgrade Guide

Open Text Archiving and Document


Access for SAP Solutions

The Open Text 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.

ER090800-IGD-EN
Installation and Upgrade Guide
Open Text Archiving and Document Access for SAP Solutions
ER090800-IGD-EN
Rev.: 05. Aug. 2010
This documentation has been created for software version 9.8.
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
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com

Copyright © by Open Text Corporation, Open Text Inc.


Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, Open Text ECM Suite, Open Text
eDOCS, eDOCS, Open Text FirstClass, FirstClass, Open Text Exceed, Open Text HostExplorer, Open Text Exceed OnDemand,
Open Text Exceed 3D, Open Text Exceed Freedom, Open Text Exceed PowerSuite, Open Text Exceed XDK, Open Text NFS
Solo, Open Text NFS Client, Open Text NFS Server, Open Text NFS Gateway, Open Text Everywhere, Open Text Real Time,
Open Text Eloquent Media Server, Open Text Integrated Document Management, Open Text IDM, Open Text DocuLink,
Livelink, Livelink ECM, Artesia, RedDot, RightFax, RKYV, DOMEA, Alchemy, Vignette, Vizible, Nstein, LegalKEY, Picdar,
Hummingbird, IXOS, Alis Gist-in-Time, Eurocortex, Gauss, Captaris, Spicer, Genio, Vista Plus, Burntsand, New Generation
Consulting, Momentum Systems, DOKuStar, and RecoStar among others. This list is not exhaustive.
All other products or company names are used for identification purposes only, and are trademarks of their respective own-
ers. All rights reserved.
Table of Contents

1 Introduction ............................................................................... 5
1.1 Product documentation ............................................................................ 5
1.2 Contact information .................................................................................. 6

2 Checking prerequisites............................................................. 7
2.1 Required knowledge ................................................................................ 7
2.2 Terms and definitions............................................................................... 7
2.3 SAP prerequisites .................................................................................... 7
2.4 Installation tool ......................................................................................... 8
2.5 Password control...................................................................................... 9
2.6 Web Dynpro configuration ..................................................................... 10

3 Installing Basis package......................................................... 11


3.1 Installing package .................................................................................. 11
3.2 Configuring components ........................................................................ 13
3.2.1 Configuring rendition management........................................................ 13
3.2.2 Configuration for Java Viewer/Web Viewer ........................................... 14
3.2.3 Setting number ranges........................................................................... 21
3.2.4 Defining authorizations .......................................................................... 22
3.2.5 Defining settings for logging................................................................... 22
3.2.6 Defining settings for optional sample projects ....................................... 22
3.3 Rendition management .......................................................................... 23
3.4 Forms Management ............................................................................... 24
3.4.1 General information................................................................................ 24
3.4.2 Installing Forms Management................................................................ 24
3.4.3 Authorizations ........................................................................................ 25
3.5 DesktopLink ........................................................................................... 25
3.5.1 General information................................................................................ 25
3.5.2 Authorizations ........................................................................................ 26
3.6 Imaging Integration ................................................................................ 26
3.6.1 General information................................................................................ 26
3.6.2 Checking Java version on clients........................................................... 26
3.7 DocuLink ................................................................................................ 27
3.7.1 General information................................................................................ 27
3.7.2 Authorizations ........................................................................................ 27
3.7.3 Testing the DocuLink installation ........................................................... 28

ER090800-IGD-EN Installation and Upgrade Guide iii


Table of Contents

4 Installing ERP option package................................................29


4.1 Installing package .................................................................................. 29

5 Installing CRM option package ...............................................31


5.1 Installing package .................................................................................. 31

6 Upgrading.................................................................................33
6.1 Upgrading to Open Text Archiving and Document Access for SAP
Solutions 9.8.0 ....................................................................................... 33
6.1.1 Delta upgrade from version 9.6.2 to 9.8.0 ............................................. 33
6.1.2 Upgrade from versions prior to 9.6.2 ..................................................... 35
6.2 Upgrading the SAP system.................................................................... 35
6.2.1 Exchange upgrades ............................................................................... 36

7 Handling communication protocols .......................................39


7.1 Maintaining OLE application .................................................................. 39
7.2 Maintaining SAP ArchiveLink application .............................................. 41
7.3 Maintaining viewer components............................................................. 46
7.4 Assigning protocols to logical archives (content repositories) ............... 48

8 Troubleshooting ......................................................................51
IDX Index .........................................................................................53

iv Installation and Upgrade Guide ER090800-IGD-EN


Chapter 1
Introduction
Open Text Archiving and Document Access for SAP Solutions consists of the
following software packages (for the current version numbers, check the latest
Release Notes in the Open Text Knowledge Center):
• Open Text SAP Basis package
• Open Text SAP ERP package (optional)
• Open Text SAP CRM package (optional)
• Enterprise Library package
• Open Text Imaging Clients package
• Open Text Imaging ExchangeLink (optional)
• Open Text Imaging NotesLink (optional)

1.1 Product documentation


You can find the product documentation as follows:
• The documentation of all products and all supported versions is available in the
Open Text Knowledge Center (see the Release Notes for details and links). In the
Knowledge Center, select the product below Supported by product, then the
wished document category below <Product name> Documentation.
Note: You can find the latest information on manuals and online help files for
each product in the corresponding Release Notes. This includes the
identification codes of the current documentation.
This document describes the installation and upgrade process in the SAP
environment only, i.e. it includes the Open Text SAP Basis add-on package, the
Open Text SAP ERP add-on package, and the Open Text SAP CRM add-on package.
For information on the other packages, see the individual installation guides. For
information on supported hardware and software platforms, check the Open Text
Archiving and Document Access for SAP Solutions Release Notes.

Important
Note that there may be a more recent version of this installation guide in the
Open Text Knowledge Center. Look there for the most up-to-date version.

ER090800-IGD-EN Installation and Upgrade Guide 5


Chapter 1 Introduction

1.2 Contact information


Open Text Online is a single point of access for the product information provided by
Open Text. Depending on your role, you have access to different levels of
information.
You can access Open Text Online via the Internet at http://online.opentext.com/ or
the support sites at http://support.opentext.com/.
The following information and support sources can be accessed through Open Text
Online:
Knowledge Center
Open Text's corporate extranet and primary site for technical support. It is the
official source for:
• Open Text products and modules.
• Documentation for all Open Text products.
• Open Text Developer Network, OTDN: developer documentation and
programming samples for Open Text products.
The following role-specific information is available:
Partners
• Information on the Open Text Partner Program.
• Programs and support for registered partners.
Business Users
• Tips, help files, and further information from Open Text staff and other users
in one of the Open Text Online communities
Administrators/developers
• Documentation
• Product information
• Discussions
• Product previews
Feedback on If you have any comments, questions, or suggestions to improve our
documentation documentation, contact us by email at documentation@opentext.com.

6 Installation and Upgrade Guide ER090800-IGD-EN


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 Terms and definitions


When describing the installation, the following terms and definitions are used:

DPA Name of the SAP system used by Open Text/IXOS


OTEXxxx Package with the ID xxx
<SID> System ID of the SAP 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 SAP system

2.3 SAP prerequisites


Check the following prerequisites prior to installation:
SAP support packages
Check the latest version of the Release Notes in the Open Text Knowledge
Center 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).

ER090800-IGD-EN Installation and Upgrade Guide 7


Chapter 2 Checking prerequisites

OSS notes
Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
• SAP 7.00 - OSS note 822380
• SAP 6.40 - OSS note 672652
• SAP 6.20 - OSS note 484219
• Installation information - OSS note 1486406
• SAPCAR tool - OSS note 212876
Check the following OSS notes to avoid known problems related to the
activation of the Business Configuration sets (BC sets):
• OSS note 1015139
• OSS note 1036876
• OSS note 1274142
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 (e.g. additional icons in the GOS attachment list) based on the SAP
enhancement technology.
System upgrade
When you have to upgrade your SAP system and you already installed Open
Text Archiving and Document Access for SAP Solutions using packages, you
have to use the upgrade packages.
For more details, see “Upgrading the SAP system” on page 35.
Note: The documentation is updated regularly; therefore, check for the latest
version in the Open Text Knowledge Center.

2.4 Installation tool


Open Text 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 CD, 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 (e.g.
INST_BAS_620/DATA/OTEXBAS_INST_0980_620.SAR contains the archived PAT file
to install the package for SAP basis release 6.20).

8 Installation and Upgrade Guide ER090800-IGD-EN


2.5 Password control

Note: The handling of the installation procedure within SAINT differs


depending on the SAP system used. For more details, see the respective SAP
documentation.

2.5 Password control


Every single installation package for Open Text Archiving and Document Access for
SAP Solutions is protected with a specific password. During the installation, this
password is requested by SAINT.
For more details, see the following table:

Table 2-1: Installation packages and passwords

Package Release Designation Password


OTEXBAS 0980_620 Open Text Archiving and Document Access 8A804A6A3A
for SAP Solutions Basic Component 9.8.0
0980_640 Open Text Archiving and Document Access 89804A6A3A
for SAP Solutions Basic Component 9.8.0
0980_700 Open Text Archiving and Document Access 88804A6A3A
for SAP Solutions Basic Component 9.8.0
OTEXERP 0980_470 Open Text Archiving and Document Access 8A8759693A
for SAP Solutions ERP Component 9.8.0
0980_500 Open Text Archiving and Document Access 898759693A
for SAP Solutions ERP Component 9.8.0
0980_600 Open Text Archiving and Document Access 888759693A
for SAP Solutions ERP Component 9.8.0
OTEXCRM 0980_500 Open Text Archiving and Document Access 888159743A
for SAP Solutions CRM Component 9.8.0

A possible delta upgrade (i.e. an upgrade from version 9.6.2 to version 9.8.0 while
keeping the same SAP release) is also performed with SAINT. Every single upgrade
package is protected with a specific password. During the upgrade, this password is
requested by SAINT.
For more details, see the following table:

Table 2-2: Upgrade packages and passwords

Package Release Designation Password


OTEXBAS 0980_620 Open Text Livelink for SAP Solution Basic 8A804A6A3D
Component 9.8.0
0980_640 Open Text Livelink for SAP Solution Basic 89804A6A3D
Component 9.8.0
0980_700 Open Text Livelink for SAP Solution Basic 88804A6A3D
Component 9.8.0

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 9
Chapter 2 Checking prerequisites

Package Release Designation Password


OTEXERP 0980_470 Open Text Livelink for SAP Solution ERP 8A8759693D
Component 9.8.0
0980_500 Open Text Livelink for SAP Solution ERP 898759693D
Component 9.8.0
0980_600 Open Text Livelink for SAP Solution ERP 888759693D
Component 9.8.0
OTEXCRM 0980_500 Open Text Livelink for SAP Solution CRM 888159743D
Component 9.8.0

2.6 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

10 Installation and Upgrade Guide ER090800-IGD-EN


Chapter 3
Installing Basis package
This chapter describes the installation of the Basis package of the Open Text
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 Open Text 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 Open Text Licence Report function
that is described in more detail in the section 28 "Open Text Licence Report" in
Open Text 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 file (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEXBAS_*_*_*.SAR INST_BAS_<Release>\DATA\ /usr/sap/trans

ER090800-IGD-EN Installation and Upgrade Guide 11


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.
3. Carry out import of package as described in the respective SAP documentation.
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_ALL962

• /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 3 times.

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

To create the DocuLink project $GARMISCH initially:


1. Execute the J6NA transaction.
2. Execute the item Initial creation of project $GARMISCH.
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.

12 Installation and Upgrade Guide ER090800-IGD-EN


3.2 Configuring components

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 8.3.1 "Standard functions in the tab view" in Open Text
DocuLinkfor SAP Solutions - Customizing and Administration Guide (DC-CGD) and
section 9.2 "The versions" in Open Text DocuLinkfor 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.

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 Open Text Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS)).

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 13
Chapter 3 Installing Basis package

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

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


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 or the Web Viewer.
To do so, you may configure the viewer integration on the SAP server in a way that
the required viewer will be used.

To maintain the imaging integration:


• Activate the user exit to use a different viewer other than the standard SAP
viewer:
a. Execute 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:
Entry for SAP BASIS 620 or 640

14 Installation and Upgrade Guide ER090800-IGD-EN


3.2 Configuring components

EXIT_ID = OA_OBJECTDISPJAVA_01
ACTIVE = X
EXIT_FUB = /IXOS/OA_X_OA_OBJECTDISPLAY_01
Entry for SAP BASIS 700
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
General settings, default values used
• /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. Execute the SM30 transaction and open the /ixos/oa_cust_a table.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 15
Chapter 3 Installing Basis package

2. Define the following settings:


Path and Script/appl
For the Web Viewer only: Storage location of the viewer script. By default this
is:
/cgi-bin/JAVAVW/ixosjv.pl

For theWeb Viewer 9.6 only: By default the value is:


WebViewer

Use Java-/Webviewer
Possible values:
No
No external viewer is used.
Yes, if winviewer is not installed locally
The external viewer specified in the Type of Viewer 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 Type of
Viewer field is used.

16 Installation and Upgrade Guide ER090800-IGD-EN


3.2 Configuring components

Yes
The external viewer specified in the Type of Viewer field is always used.
Type of Viewer
Possible values:
Java Viewer
Java Viewer
Web Viewer
Web Viewer
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 heigth 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
If activated, the secure HTTPS protocol is used when the script is run.
3. If you selected the Web Viewer option above in the Type of Viewer field, you
can specify the following additional parameters for default settings:
Don't show Thumbs
Deactivates the default display of thumbnails.
Don't 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.
4.
Note: The following step describes the former customizing procedure with the
/ixos/oa_cust table. Note that the above procedure substitutes the use of the
/ixos/oa_cust table.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 17
Chapter 3 Installing Basis package

If documents are stored in a logical archive on an archive server where Java


Viewer or Web Viewer is not installed, you can specify a different server to start
the viewer from in the /ixos/oa_cust table.
a. Execute the SE16 transaction and open the /ixos/oa_cust table.
b. Define the following parameters:
ARCHIV_ID
ID of the logical archive for which the settings are defined
HTTP_SERV
Name of the HTTP server on which the viewer is installed. Use the
syntax:
<server name>:<port>

For the Web Viewer only: Enter the port for Tomcat.
SCRIPT
For the Web Viewer only: Storage location of the viewer script. By default
this is:
<IXOS_ROOT>/w3/cgi-bin/JAVAVW/ixosjv.pl

For the Web Viewer 9.6 only: By default the value is:
WebViewer

c. By default, the current SAP user is inserted in the URL when the viewer is
started. You can deactivate this setting; however, as a result you can not
create notes to a document in the Web Viewer. For the Java Viewer, the
operating system user is inserted in this case, and notes can still be created.
To deactivate the insertion of the user parameter in the URL, select the
DISABLE_USER option in the /ixos/oa_cust table.

To configure the document classes:


1. Execute the SM30 transaction and open the /ixos/oa_doctype table.
2. Define the following settings:
Type
Enter the document extension without leading dot, e.g. JPG for JPEG image
documents.
Viewer Type
Enter the viewer type which will be used to display a specific type of docu-
ment. The available values are Java Viewer or Web Viewer.

18 Installation and Upgrade Guide ER090800-IGD-EN


3.2 Configuring components

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
By default the following document and viewer type combinations are
maintained (after activation of BC set /OTEXBAS/VIEWER_CUSTOMIZING):
Document Java Viewer Web Viewer
ALF x x
ASCII x x
FAX x x
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:


1. Execute the SM30 transaction and open the /ixos/oa_locales table.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 19
Chapter 3 Installing Basis package

2. Select the required language for the viewer.


Note: This setting does only apply to the Web Viewer components and
does not influence the standard locale set for SAP.
3. To create an entry, click the New Entries button 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
specific range, then the Web viewer 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:


1. Execute the SM30 transaction and open the /ixos/oa_iprange table.

20 Installation and Upgrade Guide ER090800-IGD-EN


3.2 Configuring components

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. Execute 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 (e.g. 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''

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.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 21
Chapter 3 Installing Basis package

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

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 Open Text Archiving and
Document Access for SAP Solutions:
• Forms Management
see “Authorizations” on page 25 for details
DesktopLink
see “Authorizations” on page 26 for details
DocuLink
see “Authorizations” on page 27 for details
Tip: For an overview of authorization maintenance, see section 10.3
"Authorizations in SAP applications" in Open Text Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).

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 21.
For details on the user action log see Open Text DocuLinkfor 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 Open Text DocuLinkfor SAP Solutions -

22 Installation and Upgrade Guide ER090800-IGD-EN


3.3 Rendition management

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.

3.3 Rendition management


The rendition management consists of the Open Text 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
the Open Text Knowledge Center.
The Rendition Server API is a prerequisite for Open Text DesktopLink and is also
required when document processing/output utilizing the Open Text 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 Open Text
Rendition Server as described in the Open Text Rendition Server - Installation
and Administration Guide (RS-IGD).

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 23
Chapter 3 Installing Basis package

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

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.

3.4.2 Installing Forms Management


Forms for forms overlay can also be maintained in a Open Text 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 11).
2. Install the Business Application Integration (BAI) on the server for Open Text
TCP Context Server.
3. Import the mapping configuration for Forms Management for Open Text TCP
Context Server in Open Text TCP Modeler.
a. Start Open Text 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 Open Text 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 located on
the Open Text Archiving and Document Access for SAP Solutions CD:

24 Installation and Upgrade Guide ER090800-IGD-EN


3.5 DesktopLink

Livelink SAP Common Package\Forms Management\DocModeler\-


sap_OverlayForm.ixbxml

4. Perform the required customizing steps described in section 20 "Livelink Forms


Management" in Open Text Archiving and Document Access for SAP Solutions -
Scenario Guide (ER-CCS).

3.4.3 Authorizations
Authorization profiles have to be assigned to users who are working with Forms
Management (see section 20.2 "Rights for Livelink Forms Management" in Open
Text Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS) for
details).
Example:
• Profile J_8AFM_ALL: Possesses all authorizations.
Tip: For an overview of authorization maintenance, see section 10.3
"Authorizations in SAP applications" in Open Text Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).

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

3.5.1 General information


Used SAP partner name spaces
The following SAP partner name spaces are used:
• 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.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 25
Chapter 3 Installing Basis package

3.5.2 Authorizations
Authorization profiles have to be assigned to users who are working with
DesktopLink (see see section 16.1.6.2 "Authorizations" in Open Text 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.
Tip: For an overview of authorization maintenance, see section 10.3
"Authorizations in SAP applications" in Open Text Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).

3.6 Imaging Integration


3.6.1 General information
The Livelink Imaging Integration with SAP contains the integration of Open Text
Imaging Java Viewer and Open Text Imaging Web Viewer with SAP and RFC
functions that allow generic calls of SAP functions from Preindexing in Open Text
Imaging Enterprise Scan.
Notes:
• See the compatibility matrix in the Open Text Knowledge Center to find out
which versions of Open Text Imaging Enterprise Scan allow calls of SAP
functions.
• Implementation of calls of SAP functions during Preindexing in Open Text
Imaging Enterprise Scan requires support from your Open Text consultant.

3.6.2 Checking Java version on clients


The Java Viewer requires Java 1.4. In order to check whether this Java version is
installed on the individual clients, you can add a small applet that checks the Java
version on the client and displays an error message if the supported version is not
found. The applet may, however, impair performance and is thus not activated by
default. To enable checking, you need to remove the comment tags for the following
lines in the Java Viewer script file ixosjv.pl:

<BODY>
<!--
<APPLET
CODEBASE = "/JAVAVW"
CODE = "ixos.viewer.jvmchecker.JVMCheckerApplet"
WIDTH = 1

26 Installation and Upgrade Guide ER090800-IGD-EN


3.7 DocuLink

HEIGHT = 1
HSPACE = 0
VSPACE = 0
ALIGN = Middle
></APPLET>
-->

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

3.7.1 General information


The following SAP partner name spaces are used:
• /IXOS/

• J6N*

3.7.2 Authorizations
Some authorization profiles are also supplied by DocuLink which you can use as a
basis to set up profiles (see section 25 "Authorizations" in Open Text DocuLinkfor
SAP Solutions - Customizing and Administration Guide (DC-CGD) for details).
Examples:
• Profile J_6NG_MIN: Minimum profile for entry to DocuLink (without projects).
• Profile J_6NG_CREA: Display and create authorization for all projects.
• Profile J_6NG_ALL: Possesses all authorizations; suitable for testing DocuLink.

To modify authorizations:
1. Execute either the SU02 or PFCG (Profile Generator) transaction to modify the
authorizations.
2. Each user must be assigned the minimum profile J_6NG_MIN as otherwise
nothing will be visible when the user attempts to call DocuLink!
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.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 27
Chapter 3 Installing Basis package

Tip: For an overview of authorization maintenance, see section 10.3


"Authorizations in SAP applications" in Open Text Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).

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.

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.

28 Installation and Upgrade Guide ER090800-IGD-EN


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 ERP-specific coding of the Open Text Archiving
and Document Access for SAP Solutions.

4.1 Installing package


To install ERP package:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEXERP_*_*_*.SAR INST_ERP_<Release>\DATA\ /usr/sap/trans

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

ER090800-IGD-EN Installation and Upgrade Guide 29


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 for the CIC integration as described in
the (DCL-CGD).

5.1 Installing package


To install CRM package:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEXCRM_*_*_*.SAR INST_CRM_<Release>\DATA\ /usr/sap/trans

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

ER090800-IGD-EN Installation and Upgrade Guide 31


Chapter 6
Upgrading
Depending on your current system configuration, you may perform one of the
following:
• “Upgrading to Open Text Archiving and Document Access for SAP Solutions
9.8.0” on page 33
• “Upgrading the SAP system” on page 35
In both cases, Open Text provides special upgrade packages.

6.1 Upgrading to Open Text Archiving and


Document Access for SAP Solutions 9.8.0
Upgrading to Open Text Archiving and Document Access for SAP Solutions 9.8.0 is
only possible as upgrade from version 9.6.2; for details see “Delta upgrade from
version 9.6.2 to 9.8.0” on page 33.
The direct upgrade from versions prior to 9.6.2 is not possible; for details see
“Upgrade from versions prior to 9.6.2” on page 35.

6.1.1 Delta upgrade from version 9.6.2 to 9.8.0


The upgrade from Open Text Archiving and Document Access for SAP Solutions
9.6.2 to Open Text Archiving and Document Access for SAP Solutions 9.8.0 is called
a delta upgrade, because the version of Open Text’s Add-On package changes while
the SAP release remains unchanged. There are specific Open Text Archiving and
Document Access for SAP Solutions delta upgrade packages.
The following delta upgrades are supported:

ER090800-IGD-EN Installation and Upgrade Guide 33


Chapter 6 Upgrading

Table 6-1: Delta upgrades

Previous add-on release Upgrade package required


OTEXBAS 0962_620 OTEXBAS_DELT_0980_620.SAR
OTEXBAS 0962_640 OTEXBAS_DELT_0980_640.SAR
OTEXBAS 0962_700 OTEXBAS_DELT_0980_700.SAR
OTEXERP 0962_470 OTEXERP_DELT_0980_470.SAR
OTEXERP 0962_500 OTEXERP_DELT_0980_500.SAR
OTEXERP 0962_600 OTEXERP_DELT_0980_600.SAR
OTEXCRM 0962_500 OTEXCRM_DELT_0980_500.SAR
OTEXCRM 0962_600 OTEXCRM_DELT_0980_500.SAR

Important
For Open Text Archiving and Document Access for SAP Solutions 9.8.0,
there is no OTEXCRM upgrade package for CRM 4.0 available.
For CRM 5.0 and higher, only the upgrade package
OTEXCRM_DELT_0980_500 is available. As the CRM functionality
contained in OTEXCRM runs under CRM 5.0 and higher, no other separate
OTEXCRM package is released.
Note that an update to Open Text Archiving and Document Access for SAP
Solutions 9.8.0 is still available for OTEXBAS on SAP Basis 620. An already
installed OTEXBAS 0962_400 is expected to still run with OTEXBAS
0980_620.

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. Select the appropriate upgrade package from the table “Delta upgrades” on
page 34.
2. Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEX*_DELT_*_*.SAR DELT_*_<Release>\DATA\ /usr/sap/trans

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


following command:
SAPCAR –xvf <name of SAPCAR file>

34 Installation and Upgrade Guide ER090800-IGD-EN


6.2 Upgrading the SAP system

The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
4. Carry out import of package as described in the respective SAP documentation.
After the upgrade, most of the customizing and configuration will not change.
5. For activation of BC sets of OTEXBAS, check the following:
• /OTEXBAS/BASIS_ARCHIVING_1
Needs not to be activated if the BC set with the same name has already been
activated for version 9.6.2.
• /OTEXBAS/DOCULINK_ALL962
Needs not to be activated if the BC set with the same name has already been
activated for version 9.6.2.
• /OTEXBAS/VIEWER_CUSTOMIZING
Needs not to be activated if you already have done viewer customizing for
the previous version; see for more details.
Tip: If you want to use additional features after upgrading to 9.8.0 (i.e.
features not used in version 9.6.2), refer to “Configuring components” on
page 13 for details.

6.1.2 Upgrade from versions prior to 9.6.2


There is no direct upgrade from older SAP solution versions prior to Open Text
Archiving and Document Access for SAP Solutions 9.6.2.
If an older version of DocuLink, DesktopLink or Livelink ECM – Suite for SAP
Solutions is already installed on your SAP system, you have to follow an upgrade
path which leads you to version 9.6.2 before further upgrade to 9.8.0.
Depending from which original version you start, there may be SAP system
upgrades required.
Note: Contact your Open Text consultant for planning your individual
upgrade strategy.

6.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
Open Text Archiving and Document Access for SAP Solutions add-ons to the
relevant version.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 35
Chapter 6 Upgrading

Caution
If you import an upgrade into an SAP system with Open Text Archiving and
Document Access for SAP Solutions and the data of the respective upgrade
packages is not read (upgrade phase IS_SELECT), the Open Text 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, Open Text can no longer accept any
liability.
Note that only in the cases listed in Table 6-2 on page 36, the existing add-
ons may be kept (KEEP in upgrade phase IS_SELECT).

6.2.1 Exchange upgrades


When you have to upgrade your SAP system where Open Text Archiving and
Document Access for SAP Solutions (ADA) 9.6.2 is already installed, you must use
the specific Open Text Archiving and Document Access for SAP Solutions exchange
upgrade packages during the upgrade of the SAP system.
Note: Contact your Open Text consultant for planning your individual
upgrade strategy.
The following exchange upgrades are supported:

Table 6-2: Exchange upgrades for SAP system

Upgrade from ADA Upgrade to Upgrade package required


9.8.0 on
SAP R/3 Enterprise 4.7 SAP ECC 6.0 OTEXBAS_UPGR_0980_700.SAR
SAP ERP 6.0 OTEXERP_UPGR_0980_600.SAR
SAP ECC 5.0 SAP ECC 6.0 OTEXBAS_UPGR_0980_700.SAR
SAP ERP 2004 SAP ERP 6.0 OTEXERP_UPGR_0980_600.SAR
SAP ERP 6.0 SAP ERP 6.0 EhP x No package; instead choose KEEP in
SAP ERP 6.0 EhP x the upgrade phase IS_SELECT of
OTEXBAS_UPGR_0980_700.SAR
and
OTEXERP_UPGR_0980_600.SAR.
Vendor keys are required.
SAP CRM 5.0 SAP CRM 2007 No package; instead choose KEEP in
SAP CRM 6.0 the upgrade phase IS_SELECT of
OTEXBAS_UPGR_0980_700.SAR
SAP CRM 5.0 SAP CRM 7.0 and
SAP CRM 2007 SAP CRM 7.0 OTEXCRM_UPGR_0980_500.SAR.
SAP CRM 6.0
Vendor keys are required.

36 Installation and Upgrade Guide ER090800-IGD-EN


6.2 Upgrading the SAP system

Notes:
• On ERP 6.0 systems with different enhancement packages, the base
functionality delivered with OTEXBAS and OTEXERP is supported. If add-
on packages OTEXBAS and OTEXERP of version 9.8.0 were already
installed before upgrading the enhancement packages, then choose to
“KEEP” these packages during upgrade phase IS_SELECT.
• On supported CRM releases (5.0 - 7.0), the base functionality delivered with
OTEXBAS and OTEXCRM is supported. If add-on packages OTEXBAS and
OTEXERP of version 9.8.0 were already installed before upgrading, then
choose to “KEEP” these packages during upgrade phase IS_SELECT.
• Vendor keys are available from the SAP Marketplace
(https://services.sap.com/support); search for the most recent vendor keys
of Open Text add-ons. Search for SAP notes with the key words “vendor”
and “keys” and the name of the add-on, e.g. OTEXBAS, OTEXERP,
OTEXCRM.
Refer also to the latest Release Notes of Open Text Archiving and
Document Access for SAP Solutions in the Open Text Knowledge Center
for further information. In case you cannot find a suitable vendor key,
contact Open Text support or SAP support.

To perform an exchange upgrade procedure:


1. Select the appropriate upgrade packages from the table “Exchange upgrades for
SAP system” on page 36.
2. Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (i.e. the parent folder of the
DIR_EPS_ROOT folder).
File Source path Target path
OTEX*_UPGR_*_*.SAR UPGR_*_<Release>\DATA\ /usr/sap/trans

3. 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.
4. Follow the standard SAP system upgrade instructions. During upgrade phase
IS_SELECT, select the upgrade type for the installed add-ons Upgrade with
SAINT Package (applies to OTEXBAS, OTEXERP, packages).

Note: No passwords are required for the upgrade packages.


5. After the upgrade, no activation of BC sets is necessary.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 37
Chapter 7
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 22.1.1.1 "Communication
protocols in SAP applications" in Open Text 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 IX_OLEU1 and IX_HTTP2.

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

ER090800-IGD-EN Installation and Upgrade Guide 39


Chapter 7 Handling communication protocols

4. Click .
The ClassId (CLSID) is registered for the Open Text Imaging Windows Viewer
application.
5. Execute the SOLE transaction and go to change mode.
6. Create or check the Open Text 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

40 Installation and Upgrade Guide ER090800-IGD-EN


7.2 Maintaining SAP ArchiveLink application

7. Click .
The ClassId (CLSID) is registered for the Open Text Imaging Enterprise Scan
application.

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

• IXVIEWER

• IXVIEWERURL

• IXVIEWERURLOA

To modify or create ArchiveLink application:


1. Execute the OAA4 transaction (ArchiveLink Application Maintenance).
If not already listed, create the ArchiveLink applications listed above (IXSCAN,
IXVIEWER, IXVIEWERURL, IXVIEWERURLOA).

2. Double-click the specific ArchiveLink application entry for additional


configuration.
All functions for the selected ArchiveLink application are listed.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 41
Chapter 7 Handling communication protocols

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.

42 Installation and Upgrade Guide ER090800-IGD-EN


7.2 Maintaining SAP ArchiveLink application

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.S M SendDoc2DP @AID,
Frontend C2SAP
G @DID=DocID
G @EID=ErrorID
Store File on IXOS.IXSCAN.S M SaveActiveDocMultipage 0
Frontend C2SAP
G @DPA=DocPathName
G @EID=ErrorID

IXVIEWER

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 43
Chapter 7 Handling communication protocols

Function Application Event Command


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 ALVIEWER.APP M ShowAppWindow
File
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

Function Application Event Command


Display Stored ALVIEWER.APP S Language=@LAN
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
Display Local ALVIEWER.APP M ShowAppWindow
File

44 Installation and Upgrade Guide ER090800-IGD-EN


7.2 Maintaining SAP ArchiveLink application

Function Application Event Command


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

IXVIEWERURLOA

Function Application Event Command


Display Stored ALVIEWER.APP S Language=@LAN
Document
M OpenDocumentSimpleUrl
@WID,@URL,@WIT,@UID
G @EID=R3ReturnCode
Display Local ALVIEWER.APP M ShowAppWindow
File
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

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 45
Chapter 7 Handling communication protocols

7.3 Maintaining viewer components


These protocol settings determine which viewer component will be used for
document display:
• IX_HTTP2
For document display, the Web browser is invoked.
• IX_OLEU1
For document display, the Open Text Imaging Windows Viewer will be invoked
via OLE.
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 (IX_HTTP2, IX_OLEU1).
2. Double-click on the specific protocol entry.

46 Installation and Upgrade Guide ER090800-IGD-EN


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

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.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 47
Chapter 7 Handling communication protocols

5. Modify the settings according to the following tables.


IX_HTTP2 protocol

Function Doc.class Communication Application


Type
Display Stored Docu- ALF OPEN_V_URL IXVIEW-
ment ERURL
Display Stored Docu- MSG ARCHIVELINK
ment
Archive from frontend FAX , JPG OPEN IXSCAN
Close Window * OPEN DUMMY

IX_OLEU1 protocol

Function Doc.class Communication Application


Type
Display Stored Docu- * , ALF , FAX , JPG , OPEN_V_URL IXVIEW-
ment OTF , PDF , TIF ERURLOA
Retrieval Frontend * OPEN IXVIEWER
Display Local File * ARCHIVELINK
Archive from frontend FAX , JPG OPEN IXSCAN
Close Window * OPEN DUMMY
Close Window ALF , FAX , JPG , OPEN IXVIEWER
OTF , PDF , TIF

6. Click to store the settings.

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

48 Installation and Upgrade Guide ER090800-IGD-EN


7.4 Assigning protocols to logical archives (content repositories)

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 IX_HTTP2 or IX_OLEU1 in the Protocol field.
4. Click to store the settings.

ER090800-IGD-EN Open Text Archiving and Document Access for SAP Solutions 49
Chapter 8
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 the Knowledge Center).
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.

ER090800-IGD-EN Installation and Upgrade Guide 51


Index
F
Feedback 6
$GARMISCH 12
Forms Management 24
forms management installation 24
A forms overlay 24
ArchiveLink
applications 41
I
communication protocols 39
imaging integration 14, 26
assigning protocols 48
installation packages
authorization profiles 22, 25, 27
passwords 9
IP address ranges 14
B IX_HTTP2 protocol 46, 48
BAI plug-in 24 IX_OLEU1 protocol 46, 48
Basis package 11
BC Sets 7, 11
J
Java version on clients 26
C Java Viewer
communication protocols 39 configuration 14
CRM option 31
CRM package 31
L
Livelink Archive Windows Viewer 39
D Livelink Imaging Enterprise Scan 39
default project logical archives 48
$GARMISCH 12
delta upgrade 33
M
DesktopLink 25
MIME type settings 14
displaying documents
Java Viewer 14
Web Viewer 14 O
DocuLink 22, 27 OLE application 39
examples 29 Open Text Online 6
testing 28 Open TextImagingJava Viewer 26, 26
document classes 18 Open TextImagingWeb Viewer 26
OracleTCPListener 51
OSS notes 8
E
ERP option 29
ERP package 29 P
exchange upgrade 36 packages
Basis 11

ER090800-IGD-EN Installation and Upgrade Guide 53


Index

CRM 31 J6NA 11
delta upgrades 34 J6NP 11
ERP 29 J6NY 28
exchange upgrades 36 OAA3 46
password OAA4 41
installation packages 9 OAC0 48
upgrade packages 9 PFCG 27
PAT files 8 SCPR20 11
patch levels 8 SCU3 11
prerequisites 7 SE16 18, 14
projects SE80 28
RS_TRFC_ST 23 SICF 10
RSUMONITOR 23 SM30 15, 18, 19, 14
protocols SOLE 39
IX_HTTP2 46, 48, 48 SU02 27
IX_OLEU1 48, 48 transport system 7
settings 46 troubleshooting 51

R U
rendition management 23 upgrade
rendition server API 23 disclaimer 35
RS_TRFC_ST project 23 packages 33
RSUMONITOR project 23 SAP system 35
version 9.6.2 to 9.8.0 33
S version prior to 9.6.2 35
SAINT 8 upgrade packages 34
files 8 passwords 9
password 9 SAP system 36
sample projects 22
SAP Add-On Installation Tool V
See “SAINT” vendor keys 37
SAP Marketplace 37 viewer components 46
SAP partner name spaces 24, 25, 27 viewer languages 19
SAP system upgrading 33
SAPCAR files 8 W
Web Dynpro
T configuration 10
tables Web Viewer
/ixos/oa_cust 18, 18 configuration 14
/ixos/oa_cust3 14 settings 14
/ixos/oa_cust_a 15
/ixos/oa_doctype 18
/ixos/oa_iprange 14
/ixos/oa_locales 19
TOAEX 14
transactions
/$SYNC 28
/$TAB 28

54 Installation and Upgrade Guide ER090800-IGD-EN