Professional Documents
Culture Documents
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
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
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
8 Troubleshooting ......................................................................51
IDX Index .........................................................................................53
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.
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.
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
Dynpro search application" in OpenText Archiving and Document Access for SAP
Solutions - Scenario Guide (ER-CCS).
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
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.
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
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
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.
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.
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
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 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.
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:
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.
• J_8AF*
• J_8AS*
• /IXOS/FM
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.
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.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.
• J_8AM*
• J_8AS*
• J8A3*
• J_8A3*
• /IXOS/DL*
• /IXOS/RS*
3.5.2 Authorizations
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.
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).
<BODY>
<!--
<APPLET
CODEBASE = "/JAVAVW"
CODE = "ixos.viewer.jvmchecker.JVMCheckerApplet"
WIDTH = 1
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 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.
• 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 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.
Note: This action is not recommended during live operation of the system.
Then repeat the installation.
the supplied object types could not be generated. In this case, perform the following
procedure.
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).
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).
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.
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.
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).
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.
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).
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. Click .
The ClassId (CLSID) is registered for the OpenText Imaging Enterprise Scan
application.
• IXVIEWER
• IXVIEWERURL
• IXVIEWERURLOA
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
IXVIEWER
IXVIEWERURL
IXVIEWERURLOA
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.
IX_OLEU1 protocol
$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