Installation and Upgrade Guide 10.0 - OpenText Archiving and Document Access For SAP Solutions

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.
ER100000-IGD-EN
Installation and Upgrade Guide
OpenText Archiving and Document Access for SAP Solutions
ER100000-IGD-EN
Rev.: 28. Sept. 2011
This documentation has been created for software version 10.0.
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, OpenText, The Content Experts, OpenText ECM Suite,
OpenText eDOCS, eDOCS, OpenText FirstClass, FirstClass, OpenText Exceed, OpenText HostExplorer, OpenText Exceed
OnDemand, OpenText Exceed 3D, OpenText Exceed Freedom, OpenText Exceed PowerSuite, OpenText Exceed XDK,
OpenText NFS Solo, OpenText NFS Client, OpenText NFS Server, OpenText NFS Gateway, OpenText Everywhere, OpenText
Real Time, OpenText Eloquent Media Server, OpenText Integrated Document Management, OpenText IDM, OpenText
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 ....................................................................... 9
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.2 Authorizations ........................................................................................ 26
3.6 Imaging Integration ................................................................................ 26
3.6.2 Checking Java version on clients........................................................... 26
3.7 DocuLink ................................................................................................ 27
3.7.2 Authorizations ........................................................................................ 27
3.7.3 Testing the DocuLink installation ........................................................... 28
ER100000-IGD-EN Installation and Upgrade Guide iii

Table of Contents
4 Installing ERP option package................................................29

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

6 Upgrading.................................................................................33
6.1 Upgrading to OpenText Archiving and Document Access for SAP
Solutions 10.0.0 ..................................................................................... 33
6.1.1 Delta upgrade from version 9.8.0 to 10.0.0 ........................................... 33
6.1.2 Upgrade from versions prior to 9.8.0 ..................................................... 35
6.1.3 OpenText Employee File Management 2.5 ........................................... 35
6.2 Upgrading the SAP system.................................................................... 36
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 ER100000-IGD-EN

Chapter 1
Introduction
OpenText 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 OpenText Knowledge Center):
• 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)
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
OpenText Knowledge Center.
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 OpenText SAP Basis add-on package, the
OpenText SAP ERP add-on package, and the OpenText 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 OpenText
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
OpenText Knowledge Center. Look there for the most up-to-date version.
ER100000-IGD-EN Installation and Upgrade Guide 5

Chapter 1 Introduction
1.2 Contact information

OpenText Online (http://online.opentext.com/) is a single point of access for the
product information provided by OpenText. You can access the following support
sources through OpenText Online:
• Communities
• Knowledge Center
OpenText Online Communities
(http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnli
neCommunity) provide the following resources:
• Usage tips, help files, and best practices for customers and partners.
• Information on product releases.
• User groups and forums where you can ask questions of OpenText experts.
The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText's
corporate extranet and primary site for technical support. The Knowledge Center is
the official source for the following:
• Product downloads, patches, and documentation including Release Notes.
• Discussion forums, Online Communities, and the Knowledge Base.
• OpenText Developer Network (OTDN), which includes developer
documentation and programming samples for OpenText products.
If you need additional assistance, you can find OpenText Corporate Support
Contacts at http://support.opentext.com/.
6 Installation and Upgrade Guide ER100000-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 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.3 SAP prerequisites

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

Chapter 2 Checking prerequisites
• 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
OpenText 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 36.
Note: The documentation is updated regularly; therefore, check for the latest
version in the OpenText Knowledge Center.
2.4 Installation tool

OpenText 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_1000_620.SAR contains the archived PAT file
to install the package for SAP basis release 6.20).
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
2.5 Password control

Every single installation package for OpenText 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 1000_620 OpenText Archiving and Document Access AE80C0145D
for SAP Solutions Basic Component 10.0.0
1000_640 OpenText Archiving and Document Access AD80C0145D
1000_700 OpenText Archiving and Document Access AC80C0145D
OTEXERP 1000_470 OpenText Archiving and Document Access AE87D3175D
for SAP Solutions ERP Component 10.0.0
1000_500 OpenText Archiving and Document Access AD87D3175D
1000_600 OpenText Archiving and Document Access AC87D3175D
OTEXCRM 1000_500 OpenText Archiving and Document Access AC81D30A5D
for SAP Solutions CRM Component 10.0.0
A possible delta upgrade (i.e. an upgrade from version 9.8.0 to version 10.0.0 while
keeping the same SAP release) is also performed with SAINT. For version 10.0 this
upgrade is also performed with the help of the respective installation package in
transaction SAINT.
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
To configure the Web Dynpro UI for the ArchiveLink Full Text Search, see section
28.1.1.1 "Technical prerequisites" in OpenText Archiving and Document Access for
SAP Solutions - Scenario Guide (ER-CCS) and section 28.1.4.2 "Configuring Web
ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 9

Chapter 2 Checking prerequisites
Dynpro search application" in OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS).

Chapter 3
Installing Basis package
This chapter describes the installation of the Basis package of the OpenText
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 OpenText 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 30 "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 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
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

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

Chapter 3 Installing Basis package
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_ALL1000
• /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.
Note: This DocuLink project $GARMISCH may not be modified manually. It

must either be created with the initial report or imported by a transport.

3.2 Configuring components
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 OpenText
DocuLink for SAP Solutions - Customizing and Administration Guide (DC-CGD) and
section 9.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.

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

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
EXIT_ID = OA_OBJECTDISPJAVA_01
ACTIVE = X
Entry for SAP BASIS 700
EXIT_ID = OA_DISPLAYJAVA_01
ACTIVE = X
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.

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.

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. The following step describes the former customizing procedure with the
/ixos/oa_cust table.
Note: Note that the above procedure substitutes the use of the
/ixos/oa_cust table.

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.

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.

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.

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.

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 OpenText Archiving and
Document Access for SAP Solutions:
• Forms Management
see “Authorizations” on page 25 for details
DesktopLink
DocuLink
Tip: For an overview of authorization maintenance, see section 10.3
"Authorizations in SAP applications" in OpenText 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 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 -

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 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
the OpenText Knowledge Center.
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 Open Text 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 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 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 11).
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 located on
the OpenText Archiving and Document Access for SAP Solutions CD:

3.5 DesktopLink
Livelink SAP Common Package\Forms Management\DocModeler\-

sap_OverlayForm.ixbxml
4. Perform the required customizing steps described in section 21 "OpenText

Forms Management" in OpenText 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 21.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.

Authorization profiles have to be assigned to users who are working with
DesktopLink (see section 17.1.6.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 the OpenText Knowledge Center 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 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>

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

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 OpenText Archiving
and Document Access for SAP Solutions.

To install ERP package:
OTEXERP_*_*_*.SAR INST_ERP_<Release>\DATA\ /usr/sap/trans

following command:
of the SAPCAR file.
Note: The optional ERP package does not contain any Business Customizing
Sets (BC Sets).

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 OpenText DocuLink for SAP Solutions - Customizing and Administration Guide (DC-
CGD).

To install CRM package:
OTEXCRM_*_*_*.SAR INST_CRM_<Release>\DATA\ /usr/sap/trans

following command:
of the SAPCAR file.
Note: The optional ERP package does not contain any Business Customizing
Sets (BC Sets).

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

Access for SAP Solutions 10.0.0
Upgrading to OpenText Archiving and Document Access for SAP Solutions 10.0.0 is
only tested as upgrade from version 9.8.0; for details see “Delta upgrade from
version 9.8.0 to 10.0.0” on page 33.
The direct upgrade from versions prior to 9.8.0 requires special care; for details see
“Upgrade from versions prior to 9.8.0” on page 35.
6.1.1 Delta upgrade from version 9.8.0 to 10.0.0

The upgrade from OpenText Archiving and Document Access for SAP Solutions
9.8.0 to OpenText Archiving and Document Access for SAP Solutions 10.0.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.0.0 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:

Chapter 6 Upgrading
Table 6-1: Delta upgrades
Previous add-on release Installation package required

OTEXBAS 0980_620 OTEXBAS_INST_1000_620.SAR
OTEXERP 0980_470 OTEXERP_INST_1000_470.SAR
OTEXCRM 0980_500 OTEXCRM_INST_1000_500.SAR
Important
For CRM 5.0 and higher, only the installation package
OTEXCRM_INST_1000_500 is available. As the CRM functionality contained
in OTEXCRM runs under CRM 5.0 and higher, no other separate OTEXCRM
package is released.
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
OTEX*_DELT_*_*.SAR DELT_*_<Release>\DATA\ /usr/sap/trans

following command:
of the SAPCAR file.
After the upgrade, most of the customizing and configuration will not change.

6.1 Upgrading to OpenText Archiving and Document Access for SAP Solutions 10.0.0
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_ALL1000
This BC set also contains customizing of table /IXOS/RSA_T_TAFO, see
“Configuring rendition management” on page 13. All other content is
identical to the BC sets with similar name of previous versions 9.6.2 and
9.8.0.
• /OTEXBAS/VIEWER_CUSTOMIZING
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 10.0.0 (i.e.
features not used in version 9.8.0), refer to “Configuring components” on
page 13 for details.
6.1.2 Upgrade from versions prior to 9.8.0

OpenText does not recommend direct upgrades from older SAP Solution versions
than 9.8.0. The direct upgrade paths from OpenText Add-Ons of version 9.8.0 to
version 10.0.0 are the only ones which are fully verified by OpenText and are also
verified during an additional validation by SAP.
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.8.0 before further upgrade to 10.0.0.
Depending from which original version you start, there may be SAP system
upgrades required.
Note: Contact your OpenText consultant for planning your individual upgrade
strategy.
6.1.3 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 OpenText
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 OpenText
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 OpenText Archiving and Document Access for SAP
Solutions 10.0.0. Please read the installation and upgrade guides and Release Notes
of OpenText Employee File Management for more details.

Chapter 6 Upgrading
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
OpenText Archiving and Document Access for SAP Solutions add-ons to the
relevant version.
Caution
If you import an upgrade into an SAP system with OpenText Archiving and
Document Access for SAP Solutions and the data of the respective upgrade
packages is not read (upgrade phase IS_SELECT), the OpenText 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 only in the cases listed in Table 6-2 on page 37, 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 OpenText Archiving and
Document Access for SAP Solutions (ADA) 10.0.0 is already installed, you must use
the specific OpenText Archiving and Document Access for SAP Solutions exchange
upgrade packages during the upgrade of the SAP system.
Note: Contact your OpenText consultant for planning your individual upgrade
strategy.
The following exchange upgrades are supported:

6.2 Upgrading the SAP system
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_1000_700.SAR
SAP ERP 6.0 OTEXERP_UPGR_1000_600.SAR
SAP ERP 6.0 EhP x
SAP ECC 5.0 SAP ECC 6.0 OTEXBAS_UPGR_1000_700.SAR
SAP ERP 2004 SAP ERP 6.0 OTEXERP_UPGR_1000_600.SAR
SAP ERP 6.0 EhP x
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 and
OTEXERP
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 and
SAP CRM 5.0 SAP CRM 7.0 OTEXCRM
SAP CRM 2007 SAP CRM 7.0 Vendor keys are required.
SAP CRM 6.0
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 10.0.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 10.0.0 were already installed before upgrading, then
choose to “KEEP” these packages during upgrade phase IS_SELECT.
• For vendor keys please refer to the latest Release Notes of OpenText
Archiving and Document Access for SAP Solutions in the OpenText
Knowledge Center. Please read them also for further information regarding
upgrades. In case you cannot find a suitable vendor key, contact OpenText
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 37.
2. Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP

Chapter 6 Upgrading

OTEX*_UPGR_*_*.SAR UPGR_*_<Release>\DATA\ /usr/sap/trans

following command:
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.

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

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

7.2 Maintaining SAP ArchiveLink application
7. Click .
The ClassId (CLSID) is registered for the OpenText Imaging Enterprise Scan
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.

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.

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


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

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
File


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
File
G @EID=R3ReturnCode
Frontend
G @DID=DocID
G @EID=ErrorID
Frontend
G @EID=R3ReturnCode

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

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.

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.

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.

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.

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

Index
patch levels 8 SE16 14, 18, 18

prerequisites 7 SE80 28
projects SICF 9
RS_TRFC_ST 23 SM30 15, 14
RSUMONITOR 23 SOLE 39
protocols SU02 27
IX_HTTP2 48, 48 transport system 7
IX_OLEU1 48, 48 troubleshooting 51
settings 46
U
R upgrade
rendition management 23 disclaimer 36
rendition server API 23 packages 33
RS_TRFC_ST project 23 SAP system 36
RSUMONITOR project 23 version 9.6.2 to 9.8.0 33
version prior to 9.6.2 35
S upgrade packages 34
SAINT 7 SAP system 37
files 8
password 9 V
sample projects 22 vendor keys 37
SAP Add-On Installation Tool viewer components 46
See “SAINT” viewer languages 19
SAP partner name spaces 24, 25, 27
SAP system upgrading 33 W
SAPCAR files 8 Web Dynpro
configuration 9
T Web Viewer
tables configuration 14
/ixos/oa_cust 18, 18 settings 14
/ixos/oa_cust3 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
J6NA 11
J6NP 11
J6NY 28
OAA3 46
OAA4 41
OAC0 48
PFCG 27
SCPR20 11
SCU3 11

Installation and Upgrade Guide 10.0 - OpenText Archiving and Document Access For SAP Solutions

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Installation and Upgrade Guide 10.0 - OpenText Archiving and Document Access For SAP Solutions

Încărcat de

Drepturi de autor:

Formate disponibile

Installation and Upgrade Guide

OpenText Archiving and Document

The OpenText Archiving and Document Access for SAP

Copyright © by Open Text Corporation, Open Text Inc.

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

ER100000-IGD-EN Installation and Upgrade Guide iii

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

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

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

iv Installation and Upgrade Guide ER100000-IGD-EN

1.1 Product documentation

ER100000-IGD-EN Installation and Upgrade Guide 5

1.2 Contact information

6 Installation and Upgrade Guide ER100000-IGD-EN

2.1 Required knowledge

2.2 Terms and definitions

DPA Name of the system used by OpenText

2.3 SAP prerequisites

ER100000-IGD-EN Installation and Upgrade Guide 7

• SAP 6.40 - OSS note 672652

2.4 Installation tool

8 Installation and Upgrade Guide ER100000-IGD-EN

2.5 Password control

Table 2-1: Installation packages and passwords

Package Release Designation Password

2.6 Web Dynpro configuration

• <Path of Web Dynpro services>/ixos/dcview

ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 9

10 Installation and Upgrade Guide ER100000-IGD-EN

3.1 Installing package

To install Basis package:

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

ER100000-IGD-EN Installation and Upgrade Guide 11

Note: For more details, see the SAP documentation.

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

To create the DocuLink project $GARMISCH initially:

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

12 Installation and Upgrade Guide ER100000-IGD-EN

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

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

3.2 Configuring components

To configure Rendition Server API:

ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 13

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

The following value pairs are valid:

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

3.2.2 Configuration for Java Viewer/Web Viewer

To maintain the imaging integration:

14 Installation and Upgrade Guide ER100000-IGD-EN

To configure the external viewer:

ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 15

2. Define the following settings:

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

16 Installation and Upgrade Guide ER100000-IGD-EN

ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 17

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

To configure the document classes:

18 Installation and Upgrade Guide ER100000-IGD-EN

To configure the viewer languages:

ER100000-IGD-EN OpenText Archiving and Document Access for SAP Solutions 19

2. Select the required language for the viewer.

To assign IP address ranges:

20 Installation and Upgrade Guide ER100000-IGD-EN