Installation Guide: Open Text Archiving and Document Access for SAP Solutions (DocuLink Component)

Transcription

1 Installation Guide: Open Text Archiving and Document Access for SAP Solutions (DocuLink Component) Applies to: Open Text Archiving and Document Access for SAP Solutions For more information visit: Summary 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). This article describes the procedure followed for the installation of DocuLink component of Open Text Archiving and Document Access for SAP Solutions Author: Harish Kumar D Company: Applexus Technologies (P) Ltd. Created on: 06 May 2011 Author Bio Harish Kumar D is working as an SAP Technology Consultant with Applexus Technologies (P) Ltd. He has working experience in SAP ABAP and SAP Data Archiving SAP AG 1

2 Table of Contents Introduction... 3 Checking Pre-requisites... 3 Terms and Definitions... 3 SAP Prerequisites... 3 Installation tool... 4 Password Control... 4 Package... 4 Installing Basis Package... 5 Checking ZAUTHCUST structure... 5 Installing package... 5 Related Content... 7 Disclaimer and Liability Notice SAP AG 2

3 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). Checking Pre-requisites Terms and Definitions When describing the installation, the following terms and definitions are used: DPA OTEXxxx <SID> <MDT> Name of the SAP system used by Open Text/IXOS Package with the ID xxx System ID of the SAP system used by the user Client into which the import will take place /usr/sap/trans/eps/in Package directory in the user's SAP system SAP Prerequisites Check the following prerequisites prior to installation: 1. SAP support packages Check the latest version of the Release Notes in the Open Text Knowledge Center for required support packages for the employed SAP system prior to installation! 2. 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). 3. OSS notes Check the following OSS notes to avoid known problems with the SAP Add-On Installation Tool (SAINT): SAP OSS note SAP OSS note SAP OSS note Installation information - OSS note SAPCAR tool - OSS note SAP AG 3

4 Check the following OSS notes to avoid known problems related to the activation of the Business Configuration sets (BC sets): OSS note OSS note OSS note Installation tool Open Text Archiving and Document Access for SAP Solutions uses the SAP Add-On Installation Tool (SAINT) for installation. SAINT uses single PAT files (extension *.PAT) which integrate several transport files; these collections are also called packages. On the product CD, the single PAT files are archived in SAPCAR files (extension *.SAR) that can be extracted using the SAPCAR command line tool. The different SAPCAR files are located in a DATA folder below the respective package folder named as the package and SAP release (e.g. INST_BAS_620/DATA/OTEXBAS_INST_0961_620.SAR contains the archived PAT file to install the package for SAP basis release 6.20). Password Control Every single installation package for Open Text Archiving and Document Access for SAP Solutions is protected with a specific password. During the installation, SAINT requests this password. For more details, see the following table: Table 1-1: Installation packages and passwords Package Release Designation Password OTEXBAS 0962_620 Open Text Archiving and Document Access for SAP Solutions Basic 0962_640 Open Text Archiving and Document Access for SAP Solutions Basic 0962_700 Open Text Archiving and Document Access for SAP Solutions Basic OTEXERP 0962_470 Open Text Archiving and Document Access for SAP Solutions ERP 0962_500 Open Text Archiving and Document Access for SAP Solutions ERP 0962_600 Open Text Archiving and Document Access for SAP Solutions ERP 2011 SAP AG 4

5 Installing Basis Package The Basis package contains several basic functions that are required by other components of the Open Text Archiving and Document Access for SAP Solutions: Basic components Rendition management Forms management DesktopLink Imaging integration Migration management DocuLink Checking ZAUTHCUST structure An existing ZAUTHCUST structure is an important prerequisite for a proper installation. Important: Carry out the following check to avoid subsequent errors during installation. To check the ZAUTHCUST structure: 1. Log on to your SAP system (possibly test system) as a user with administrator rights. 2. Execute the SE11 transaction. 3. Click Data type and enter the data type ZAUTHCUST. 4. Click Display. 5. 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. Re-enter the data type ZAUTHCUST in the same transaction and click the Create button. b. Choose Structure in the dialog box and click the Next button. c. Enter the following short text: Authorization fields for Customers d. Select the Components folder. e. Enter DUMMYF as the component and DUMMY as the component type. f. Save this as a local object or add it to an existing development class. g. Activate the structure. 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> The resulting PAT file will be extracted to the EPS/in folder relative to the path of the SAPCAR file SAP AG 5

6 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 Customizing Sets (BC Sets) must be activated after installation. To activate BC sets: 1. Execute the SCPR20 transaction. The Business Customizing Set screen appears 2. Activate the BC Sets in the following sequence: /OTEXBAS/BASIS_ARCHIVING_1 /OTEXBAS/DOCULINK_ALL962 /OTEXBAS/VIEWER_CUSTOMIZING Note: For more details, see the SAP documentation. 3. If you experience errors during BC Set activation, repeat the respective activation procedure up to 3 times. For every client, the default project $GARMISCH is required by DocuLink. To create the DocuLink project $GARMISCH initially: 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. 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 2011 SAP AG 6

7 Related Content For more information, visit SAP AG 7

8 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 8