2
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/WebViewer integration.
ER090602-IGD-EN
Installation and Upgrade Guide Open Text Archiving and Document Access for SAP Solutions 9.6.2 ER090602-IGD-EN Rev.: 31. Mar. 2009
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 E-mail: support@opentext.com FTP: ftp://ftp.opentext.com For more information, visit http://www.opentext.com
Table of Contents
1
1.1 1.2
Introduction ............................................................................... 5
Product documentation ............................................................................ 5 Contact information .................................................................................. 6
2
2.1 2.2 2.3 2.4 2.5
Checking prerequisites............................................................. 9
Required knowledge ................................................................................ 9 Terms and definitions............................................................................... 9 SAP prerequisites .................................................................................... 9 Installation tool ....................................................................................... 10 Password control.................................................................................... 11
3
3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.4 3.5 3.5.1 3.5.2 3.5.3 3.6 3.6.1 3.6.2 3.7 3.7.1 3.7.2 3.8 3.8.1 3.8.2 3.8.3
ER090602-IGD-EN
iii
Table of Contents
4
4.1
5
5.1
6
6.1 6.1.1 6.1.2 6.1.3 6.2 6.2.1
Upgrading.................................................................................35
Upgrading to Open Text Archiving and Document Access for SAP Solutions 9.6.2 ....................................................................................... 35 Delta upgrade from version 9.6.1 to 9.6.2 ............................................. 35 Exchange upgrade from version 9.5.2 to 9.6.2...................................... 37 Upgrade from versions prior to 9.6.1 or 9.5.2 ........................................ 38 Upgrading the SAP system.................................................................... 38 Exchange upgrades ............................................................................... 39
7
7.1 7.2 7.3 7.4
8 IDX
iv
ER090602-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 Services package Open Text Imaging Clients package Livelink ECM Imaging: ExchangeLink (optional) Open Text Imaging NotesLink (optional)
The product CD-ROM contains the documentation corresponding to the product and the version. Note: In case that the CD-ROM does not start automatically, please open the file index.htm and follow the navigation offered there.
The documentation of all products and all supported versions is available in the Expert Service Center or the Open Text Knowledge Center (see the Release Notes for details and links). In the ESC, open the product folder and click on Product Documentation. 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.
ER090602-IGD-EN
Chapter 1 Introduction
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.
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. Patches for Open Text products.
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
ER090602-IGD-EN
1.2
Contact information
Feedback on documentation
If you have any comments, questions, or suggestions to improve our documentation, contact us by e-mail at documentation@opentext.com.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
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 Services.
ER090602-IGD-EN
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 1267724 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):
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 38. Note: The documentation is updated regularly; therefore, check for the latest version in the Open Text Knowledge Center.
10
ER090602-IGD-EN
2.5
Password control
A possible delta upgrade (i.e. an upgrade from version 9.6.1 to version 9.6.2 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 OTEXBAS Release 0962_620 0962_640 0962_700 Designation Open Text Livelink for SAP Solution Basic Component 9.6.2 Open Text Livelink for SAP Solution Basic Component 9.6.2 Open Text Livelink for SAP Solution Basic Component 9.6.2 Password 27F58052CB 24F58052CB 25F58052CB
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
11
Package OTEXERP
Designation Open Text Livelink for SAP Solution ERP Component 9.6.2 Open Text Livelink for SAP Solution ERP Component 9.6.2 Open Text Livelink for SAP Solution ERP Component 9.6.2 Open Text Livelink for SAP Solution CRM Component 9.6.2 Open Text Livelink for SAP Solution CRM Component 9.6.2
OTEXCRM
0962_400 0962_500
12
ER090602-IGD-EN
Chapter 3
Basic components Rendition management Forms management DesktopLink Imaging integration Migration management DocuLink Tip: The Basis package also includes the Open Text Licence Report function that is described in more detail in the Open Text DocuLink for SAP Solutions 9.6.2 - Customizing and Administration Guide (DC-CGD).
ER090602-IGD-EN
13
2. 3. 4. 5.
Execute the SE11 transaction. Click Data type and enter the data type ZAUTHCUST. Click Display. If you now see the structure definition, you can continue with the installation. However, if a warning or error message appears in the status line and no table appears, you must first set up the structure as follows: a. b. c. Re-enter the data type ZAUTHCUST in the same transaction and click the Create button. Choose Structure in the dialog box and click the Next button. Enter the following short text:
Authorization fields for Customers
d. Select the Components folder. e. f. g. Enter DUMMYF as the component and DUMMY as the component type. Save this as a local object or add it to an existing development class. Activate the structure.
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. 4. Carry out import of package as described in the respective SAP documentation. After import has been finished, continue with the activation of the BC sets.
For every client, the Business Customizing Sets (BC Sets) must be activated after installation.
14
ER090602-IGD-EN
3.2
Installing package
To activate BC sets: 1. Execute the SCPR20 transaction. The Business Customizing Set screen appears 2. Activate the BC Sets in the following sequence:
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. 2. Execute the J6NA transaction. 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. To export the DocuLink project $GARMISCH from your customizing client: 1. Execute the J6NP transaction. The DocuLink: Customizing: Project Overview dialog is displayed. 2. 3. Click on the $GARMISCH item to position the cursor on this DocuLink project. 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.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
15
You are prompted to select a transport request. 5. 6. Create a customizing request and click the Continue button or press ENTER. 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 DocuLink for SAP Solutions 9.6.2 - Customizing and Administration Guide (DC-CGD) and Section 9.2 "The versions" in Open Text DocuLink for SAP Solutions 9.6.2 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.
16
ER090602-IGD-EN
3.3
Configuring components
3.
Execute the DocuLink administration transaction J6NA to maintain the tables /IXOS/RSA_T_CONF and /IXOS/RSA_T_RENS.
/ixos/oa_cust_a
/ixos/oa_doctype
Document classes and their viewer types (if not defined, the default viewer for ArchiveLink documents will be used)
/ixos/oa_locales
/ixos/oa_iprange
IP settings used to optimize network performance (optional, for Web Viewer only)
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
17
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 the Web 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.
18
ER090602-IGD-EN
3.3
Configuring components
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: Specifies whether the Java Viewer with a specific build number is used. You can find the build number in the w3vw.cab file on the Archive and Storage Services, in the <IXOS_ROOT>\w3\htdocs\JAVAVW directory). Open the IXOS_JavaViewer.osd file which is included in it. The build number is located in the fifth row, within the VERSION tags, e.g. <VERSION>5,2,2003,116</VERSION>. 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.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
19
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. 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. b. Execute the SE16 transaction and open the /ixos/oa_cust table. 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. 2. Execute the SM30 transaction and open the /ixos/oa_doctype table. Define the following settings: Type Enter the document extension without leading dot, e.g. JPG for JPEG image documents.
20
ER090602-IGD-EN
3.3
Configuring components
Viewer Type Enter the viewer type which will be used to display a specific type of document. The available values are Java Viewer or Web Viewer. 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 ALF ASCII FAX GIF JPEG JPG OTF PDF TIF TIFF x x Java Viewer x x x x x x x Web Viewer x x x x x x x x x x
To configure the viewer languages: 1. Execute the SM30 transaction and open the /ixos/oa_locales table.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
21
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 ranges: 1. Execute the SM30 transaction and open the /ixos/oa_iprange table.
22
ER090602-IGD-EN
3.3
Configuring components
2. 3.
Specify the content repository and the range of the IP addresses. 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. 2. Execute the SE16 transaction and open the /ixos/oa_cust3 table. 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.
[HKEY_CLASSES_ROOT\MIME\Database\Content Type\app/LLVIEW] ''extension''=''.fax''
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
23
3. 4. 5. 6.
Click the Number ranges button. Click the Change intervals button. Click the Insert interval button. Modify the interval 01: From number = 1, To number = 9999999999.
7.
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.
01:
Repeat the procedure as described for the /IXOS/DC_K object, using the interval
Forms Management see Authorizations on page 27 for details DesktopLink see Authorizations on page 28 for details DocuLink see Authorizations on page 29 for details Tip: For an overview of authorization maintenance, see Section 9.3 "Authorizations in SAP applications" in Open Text Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
24
ER090602-IGD-EN
3.4
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.
Rendition management also requires the installation of Open Text Rendition Services as described in the Open Text Rendition Services Installation and Administration Guide (RS-IGD).
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
25
Installation of the monitoring project is not mandatory for rendition management. It is intended as a help for the rendition log administration.
After installation, you have to configure the rendition management. For details, see Configuring rendition management on page 16.
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:
26
ER090602-IGD-EN
3.6
DesktopLink
4.
Perform the required customizing steps described in Section 19 "Livelink Forms Management" in Open Text Archiving and Document Access for SAP Solutions Scenario Guide (ER-CCS).
3.5.3 Authorizations
Authorization profiles have to be assigned to users who are working with Forms Management (see Section 19.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 9.3 "Authorizations in SAP applications" in Open Text Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
3.6 DesktopLink
In addition to the installation, you must perform the Open Text Imaging Clients installation on a client in order to work with Livelink ECM Imaging: DesktopLink.
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.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
27
3.6.2 Authorizations
Authorization profiles have to be assigned to users who are working with DesktopLink (see see Section 15.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 9.3 "Authorizations in SAP applications" in Open Text Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
See the compatibility matrix in the ESC 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.
<BODY> <!--
28
ER090602-IGD-EN
3.8
DocuLink
-->
Note: If no Java version is available on the client, the applet will not work.
3.8 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 9 with general information on installation in an SAP environment.
/IXOS/ J6N*
3.8.2 Authorizations
Some authorization profiles are also supplied by DocuLink which you can use as a basis to set up profiles (see Section 24 "Authorizations" in Open Text DocuLink for SAP Solutions 9.6.2 - 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. 2. 3. Execute either the SU02 or PFCG (Profile Generator) transaction to modify the authorizations. Each user must be assigned the minimum profile J_6NG_MIN as otherwise nothing will be visible when the user attempts to call DocuLink! 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. After assigning authorizations, do not forget to log on to the SAP application system again.
4.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
29
Tip: For an overview of authorization maintenance, see Section 9.3 "Authorizations in SAP applications" in Open Text Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).
the supplied object types could not be generated. In this case, perform the following procedure. To generate object types: 1. 2. 3. 4. 5. 6. Execute the SE80 transaction. Enter J6NG as the development class. Click the Display button. Open the Business Engineering folder. Open the Business object types folder. For each of the listed object types: a. b. Double-click the object type. Click Generate. (No success message appears.)
30
ER090602-IGD-EN
Chapter 4
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).
ER090602-IGD-EN
31
Chapter 5
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).
ER090602-IGD-EN
33
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.6.2 on page 35 Upgrading the SAP system on page 38
6.1 Upgrading to Open Text Archiving and Document Access for SAP Solutions 9.6.2
Upgrading to Open Text Archiving and Document Access for SAP Solutions 9.6.2 is only possible on the following paths:
Delta upgrade from version 9.6.1 to 9.6.2 on page 35 Exchange upgrade from version 9.5.2 to 9.6.2 on page 37
The direct upgrade from versions prior to 9.6.1 or 9.5.2 is not possible; for details see Upgrade from versions prior to 9.6.1 or 9.5.2 on page 38.
ER090602-IGD-EN
35
Chapter 6 Upgrading
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. 2. Select the appropriate upgrade package from the table Delta upgrades on page 36. 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 OTEX*_DELT_*_*.SAR Source path DELT_*_<Release>\DATA\ Target path /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. 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.1.
/OTEXBAS/DOCULINK_ALL962
36
ER090602-IGD-EN
6.1
Upgrading to Open Text Archiving and Document Access for SAP Solutions 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.6.2 (i.e. features not used in version 9.6.1), refer to Configuring components on page 16 for details.
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.
Caution
If you import an upgrade into an SAP system with Livelink ECM Suite 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.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
37
Chapter 6 Upgrading
To perform an exchange upgrade procedure: 1. 2. Select the appropriate upgrade package from the table Exchange upgrades on page 37. 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 OTEX*_UPGR_*_*.SAR Source path UPGR_*_<Release>\DATA\ Target path /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, OTEXCRM packages). Note: No passwords are required for the upgrade packages. 5. After the upgrade, no activation of BC sets is necessary.
38
ER090602-IGD-EN
6.2
Caution
If you import an upgrade into an SAP system with Livelink ECM Suite 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.
To perform an exchange upgrade procedure: 1. 2. Select the appropriate upgrade packages from the table Exchange upgrades for SAP system on page 39. 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 OTEX*_UPGR_*_*.SAR Source path UPGR_*_<Release>\DATA\ Target path /usr/sap/trans
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
39
Chapter 6 Upgrading
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, OTEXCRM packages). Note: No passwords are required for the upgrade packages. 5. After the upgrade, no activation of BC sets is necessary.
40
ER090602-IGD-EN
Chapter 7
ER090602-IGD-EN
41
4.
Click
The ClassId (CLSID) is registered for the Livelink ECM Imaging: Windows Viewer application. 5. 6. Execute the SOLE transaction and go to change mode. 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
42
ER090602-IGD-EN
7.2
7.
Click
The ClassId (CLSID) is registered for the Open Text Imaging Enterprise Scan application.
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). Double-click the specific ArchiveLink application entry for additional configuration. All functions for the selected ArchiveLink application are listed.
2.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
43
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.
44
ER090602-IGD-EN
7.2
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 Archive from Frontend Application IXOS.IXSCAN.S C2SAP Event M G G Store File on Frontend IXOS.IXSCAN.S C2SAP M G G IXVIEWER Command SendDoc2DP @AID, @DID=DocID @EID=ErrorID SaveActiveDocMultipage 0 @DPA=DocPathName @EID=ErrorID
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
45
Application ALVIEWER.APP
Event S M M G
Command Language=@LAN ShowAppWindow OpenDocumentSimple @WID,@AID,@DID,@WIT,@UID @EID=R3ReturnCode GetDocument @AID,@DID,@DPA, , @EID=R3ReturnCode ShowAppWindow OpenDocumentFromFiles @WID,@DPA,@DTI,@WIT,@UID @EID=R3ReturnCode ArchiveDoc @AID, @DID=DocID @EID=ErrorID GetDocument @AID,@DID,@DPA,, @EID=R3ReturnCode CloseStack @WID
Retrieval on Frontend
ALVIEWER.APP
M G
ALVIEWER.APP
M M G
ALVIEWER.APP
M G G
ALVIEWER.APP
M G
ALVIEWER.APP
Application ALVIEWER.APP
Event S M M G
Command Language=@LAN ShowAppWindow OpenDocumentSimpleUrl @WID,@URL,@WIT,@UID @EID=R3ReturnCode GetDocument @AID,@DID,@DPA, , @EID=R3ReturnCode ShowAppWindow
Retrieval on Frontend
ALVIEWER.APP
M G
ALVIEWER.APP
46
ER090602-IGD-EN
7.2
Function
Application
Event M G
Command OpenDocumentFromFiles @WID,@DPA,@DTI,@WIT,@UID @EID=R3ReturnCode ArchiveDoc @AID, @DID=DocID @EID=ErrorID GetDocument @AID,@DID,@DPA,, @EID=R3ReturnCode CloseStack @WID
ALVIEWER.APP
M G G
ALVIEWER.APP
M G
ALVIEWER.APP
Application ALVIEWER.APP
Event S M G
Command Language=@LAN OpenDocumentSimpleUrl @WID,@URL,@WIT,@UID @EID=R3ReturnCode ShowAppWindow OpenDocumentFromFiles @WID,@DPA,@DTI,@WIT,@UID @EID=R3ReturnCode ArchiveDoc @AID, @DID=DocID @EID=ErrorID GetDocument @AID,@DID,@DPA,, @EID=R3ReturnCode CloseStack @WID
ALVIEWER.APP
M M G
ALVIEWER.APP
M G G
ALVIEWER.APP
M G
Close Window
ALVIEWER.APP
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
47
IX_HTTP2
IX_OLEU1
For document display, the Livelink ECM 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. 2. Execute the OAA3 transaction (Protocol settings Maintenance). If not already listed, create the protocols listed above (IX_HTTP2, IX_OLEU1). Double-click on the specific protocol entry.
48
ER090602-IGD-EN
7.3
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.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
49
5.
6.
Click
50
ER090602-IGD-EN
7.4
To assign a protocol to a logical archive: 1. 2. 3. 4. Execute the OAC0 transaction. Select an already created logical archive and click the Full Administration button. Enter either IX_HTTP2 or IX_OLEU1 in the Protocol field. Click to store the settings.
ER090602-IGD-EN
Open Text Archiving and Document Access for SAP Solutions 9.6.2
51
Chapter 8
Troubleshooting
When general problems occur during installation, check the following points, or carry out the tasks described: 1. 2. 3. 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 ESC). For Oracle database only: Check whether the OracleTCPListener has been started on the SAP database server. 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. 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
4.
5. 6.
For DocuLink only: Check if the ZAUTHCUST structure exists (see Checking ZAUTHCUST structure on page 13). Check if the correct authorizations and number ranges were defined.
ER090602-IGD-EN
53
Index
$GARMISCH 15 A ArchiveLink application 43 ArchiveLink communication protocols 41 Assigning protocols 50 Authorization profiles 24 B Basis package 13 BC Sets 9, 14 C CD-ROM Product CD-ROM 5 Communication protocols 41 CRM option 33 CRM package 33 D Default project $GARMISCH 15 Delta upgrade 35 DesktopLink 27 Displaying documents Java Viewer 17 Web Viewer 17 DocuLink 24, 29 Testing 30 DocuLink examples 31 E ERP option 31 ERP package 31 Exchange upgrade 37, 39 F Feedback 7 Forms management 26 Installation 26 Forms overlay 26 I Imaging Integration 28 Installation packages 11 IX_HTTP2 protocol 41, 48 IX_OLEU1 protocol 41, 48 J Java version on clients 28 Java Viewer 17 L Livelink Archive Windows Viewer 41 Livelink ECM Imaging: Java Viewer 28 Livelink ECM Imaging: Web Viewer 28 Livelink Imaging Enterprise Scan 41 O OLE application 41 Open Text Online 6 OracleTCPListener 53 OSS notes 9 P Package Basis 13 CRM 33 Delta upgrades 36 ERP 31 Exchange upgrades 37, 39 Password control 37, 39 PAT files 10
ER090602-IGD-EN
55
Index
Project RS_TRFC_ST 25 RSUMONITOR 25 R Rendition management 25 Rendition Server API 25 RS_TRFC_ST project 25 RSUMONITOR project 25 S SAINT 9 Files 10 password 11 Sample projects 24 SAP Add-On Installation Tool See SAINT SAP system Upgrade 35 SAPCAR files 10 T Tables /ixos/oa_cust 20, 20 /ixos/oa_cust3 17 /ixos/oa_cust_a 18 /ixos/oa_doctype 20 /ixos/oa_iprange 17 /ixos/oa_locales 21 TOAEX 17 Transactions J6NA 14 J6NP 14 J6NY 30 OAA3 48 OAA4 43 OAC0 50 SCPR20 14 SCU3 14 SE11 13 SE16 20, 17 SE80 30 SM30 18, 20, 21, 17 SOLE 41 Transport system 9 Troubleshooting 53
U Upgrade disclaimer 37, 38 Packages 35 SAP system 37, 38 Version 9.5.2 to 9.6.2 37 Version 9.6.1 to 9.6.2 35 Version prior to 9.6.1 or 9.5.2 38 Upgrade packages 11, 36, 37, 39 V Viewer components 48 W Web Viewer 17 Settings 17 Z ZAUTHCUST structure 13
56
ER090602-IGD-EN