EMC Documentum Content Services for SAP

Transcription

1 EMC Documentum Content Services for SAP Version 6.0 Installation Guide P/N Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published September 2007 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up to date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.

3 Table of Contents Preface... 7 Chapter 1 Introducing Content Services for SAP Overview Content Services for SAP architecture Supported SAP document formats SAP and Content Services for SAP terms Chapter 2 Installing Content Services for SAP Server Components Overview Installation scenarios Installation prerequisites EI Core docapp file Documentum Content Server (UNIX or Windows) Content Services for SAP WebAdmin server (Windows) SAP R/3 server (UNIX or Windows) Preinstallation tasks Preinstallation checklist dm_doclink_sap user dm_doclink_sap workaround for UNIX dm_doclink_sap workaround for UNIX (for repositories created using pre EMC Documentum Content Server 5.3 versions) dm_doclink_sap workaround for UNIX (for repositories created using EMC Documentum Content Server 5.3 and higher versions) Installing Content Services for SAP server components Installing the EI Core docapp file Copying the software to the Content Services for SAP server Changing registry values for SAP version Creating Content Services for SAP Windows services Configuring IIS for WebAdmin on Windows Configuring WebView Installing the Daeja plug in Installing the image services docapp Removing Content Services for SAP Windows services Chapter 3 Starting services Overview Starting Agent services on Windows Configuring logging WebView logging Log4j EMC Documentum Content Services for SAP Version 6.0 Installation Guide 3

4 Table of Contents WDK Tracing Chapter 4 Installing PrintList Transformation Filters Overview On demand rendering versus stored rendering Configuring EMC Documentum Content Server for on demand rendering Chapter 5 Installing Content Services for SAP Client Components Overview System configuration and dependencies User roles and client components Installation prerequisites Customizing installation Upgrading Content Services for SAP client components Installing Content Services for SAP Client Components Configuring the View component for Webtop or WebView Configuring Japanese Language Pack for WebView Silent Installation Postinstallation tasks Using Doclink Capture Disabling tag pooling for WebView Chapter 6 Upgrading Content Services for SAP Overview Upgrading from Content Services for SAP 5.3 SP Upgrading RFC archiving services Chapter 7 Testing the Installation Overview Testing the installation Prerequisites for testing the installation Connecting to WebAdmin Configuring the SAP server Configuring an SAP user Creating an SAP query Testing an SAP query Chapter 8 Troubleshooting Installation Issues Overview Troubleshooting IIS related issues Correcting SAP queries (BAPI configuration) SAP 4.6b BAPI workaround for German language Chapter 9 Uninstalling Content Services for SAP Overview Uninstalling Content Services for SAP server components Removing the Content Services for SAP software Deleting default SAP configuration information or data Uninstalling Content Services for SAP client components EMC Documentum Content Services for SAP Version 6.0 Installation Guide

5 Table of Contents List of Figures Figure 1. Content Services for SAP and SAP Figure 2. Content Services for SAP installation scenario Figure 3. Windows server configuration Figure 4. Windows Unix Unix server configuration EMC Documentum Content Services for SAP Version 6.0 Installation Guide 5

6 Table of Contents List of Tables Table 1. Terms and definitions Table 2. System configuration and dependencies Table 3. System configuration and dependencies Table 4. Prerequisites for testing the installation EMC Documentum Content Services for SAP Version 6.0 Installation Guide

7 Preface Purpose of this guide This manual explains how to install and configure the components of Content Services for SAP 6.0. It contains information about installation requirements, and provides details of the tasks performed with the software. Intended audience In order to address the manuals to the correct audience, the roles of the users of the manuals have been defined as follows: System Administrator This role covers users who install and configure Content Services for SAP. The Content Services for SAP application integrates EMC Documentum and the SAP R/3 system. Therefore, system administrators must have experience with the software products listed in the EMC Documentum Content Services for SAP Release Notes. Content Services Administrator This role covers users who manage Content Services using WebAdmin. Document Controller This role covers those who release documents to SAP and maintain the links to those documents. Capture Operator This role covers users who scan documents and create links to the appropriate records in SAP. Standard User This role covers users who view documents using SAPGUI and the View component of Content Services. This manual is intended for System Administrators. Revision history This section contains a description of this document s revision history. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 7

8 Preface Revision history Revision date September 2007 Description Initial publication of document for Content Services for SAP 6.0 Typographic conventions This guide uses the following text conventions. Typographic conventions used in this guide Convention Description > Represents a pop up or pull down menu. <Text enclosed within angle brackets> Information in this font Represents a variable name for which you must provide a value, or a defined term. Represents code samples, user input, and computer output. [] square brackets Used in method command syntax specifications, square brackets indicate an optional argument. {} curly brackets Used in method command syntax specifications, curly brackets indicate an optional argument that can be repeated more than once. Related documentation This manual forms part of a documentation suite designed to support those who install, configure, and use Content Services. The product and documentation suite can be found on EMC Powerlink, located at: From Powerlink, you can download the latest version of Content Services and the related documentation suite. To access the contents in Powerlink, you will need to provide the login credentials assigned to you when you first applied for access. Note: Your login ID, by default, is your address. If you cannot locate your password, use the password finder at the bottom of the login page. If you re accessing Powerlink for the first time, you will need to apply for access and obtain a user name and password. 8 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

9 Preface Content Services for SAP Documentation suite Title Description Target role Content Services for SAP Release Notes Content Services for SAP Installation Guide Configuring SAP R/3 for Content Services for SAP Provides an overview of new and amended features, known bugs, limitations, miscellaneous technical notes, and documentation correctness and clarifications. Provides the procedures for installing Content Services. Describes the configuration tasks that need to be performed in SAP so that SAP can communicate with Content Services. Standard User, System Administrator, System Administrator (SAP), and Content Services Administrator System Administrator System Administrator (SAP) Content Services for SAP Administration Guide Content Services for SAP User Guide Describes how to configure Content Services using the WebAdmin tool. Describes how SAP users view documents. Content Services Administrator Standard User EMC Documentum Content Services for SAP Version 6.0 Installation Guide 9

10 Preface 10 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

11 Chapter 1 Introducing Content Services for SAP Overview The EMC Documentum Content Services for SAP application integrates the Documentum content management system with the SAP R/3 system. It is an interface to the SAP R/3 system based on SAP standard Document Management System (DMS) and ArchiveLink interfaces. Content Services for SAP provides the following functionalities: Enables users to easily access and display documents stored in a Documentum repository from a variety of SAP modules. Links documents stored in Documentum to a variety of SAP documents. Archives SAP data, reports, and documents through ArchiveLink certified interfaces in Documentum. Stores and manages reports and outgoing documents in Documentum. This chapter covers the following topics: Content Services for SAP architecture, page 12 Supported SAP document formats, page 14 SAP and Content Services for SAP terms, page 14 EMC Documentum Content Services for SAP Version 6.0 Installation Guide 11

12 Introducing Content Services for SAP Content Services for SAP architecture Figure 1. Content Services for SAP and SAP Content Services for SAP consists of the following components: Agent services A server component that allows you to automate the linking between SAP objects and documents, as well as maintain those links. This substantially improves productivity, information integrity, and information availability. Capture Enables you to scan documents, store the images in a Documentum repository, and create a link to the appropriate transaction documents in SAP. Once this link is created, the document is accessible from SAPGUI, the SAP client interface. The Capture component is part of Documentum integration to ArchiveLink. 12 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

13 Introducing Content Services for SAP Manage Enables you to release Documentum documents to SAP, and to maintain those released documents. View Enables you to view released Documentum documents from inside SAP. The View component supports the following operating systems: Windows 2000 Windows XP Windows 2003 The View component must be installed on every client computer that needs to access reports, drawings, and other documents stored in a Documentum repository. Rendition Services Built in filters that provide the following renditions: PDF rendition ASCII text rendition HTML rendition When one of these built in filters is used, the appropriate document rendition is generated when the Print List is archived in the repository. Note: This component is only relevant when your environment includes parallel installations of Content Services for SAP and Archive Services for SAP. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 13

14 Introducing Content Services for SAP WebAdmin An administrative console that allows you to: Perform archiving services. Note: Your environment should have coexisting installations of Content Services for SAP and Archive Services for SAP in order to leverage these services. Using WebAdmin, you can perform the following archiving services: Create, configure, and manage archives. Manage certificates for the archive. Create repository connections for Content Services. Create workflows and associate the same with archived documents. Configure document archival for Content Services. Perform DMS related services. You can: Configure batch jobs for linking and replication tasks. Schedule and manage the execution of linking and replication jobs. Note: The EMC Documentum Content Services for SAP Release Notes provides detailed information about specific OS versions and supported software environments. Supported SAP document formats Documentum supports the following SAP document classes/formats: Incoming or scanned documents (FAX class, Tiff format) Outgoing documents (OTF class, PDF format) Archived data (REO class, REO format) Reports or print lists (ALF class, ALF format) SAP and Content Services for SAP terms This section presents terms and definitions used in this guide. 14 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

15 Introducing Content Services for SAP Table 1. Terms and definitions Term Content Services for SAP HTTP Archiving Server ArchiveLink WebAdmin Definition Product that connects Documentum to and from SAP. Server component that, using an HTTP connection to SAP, enables you to archive reports, data, incoming and outgoing documents from SAP to the Documentum repository. Archiving Server is a J2EE Web application based on the SAP ArchiveLink interface. The archived reports and documents can later be retrieved and viewed through SAPGUI and Documentum clients. Cross functional interface that is part of the SAP Basis System. ArchiveLink handles storing and retrieving documents and data to and from a repository external to SAP. An administrative console that allows you to: Perform archiving services. Note: Your environment should have coexisting installations of Content Services for SAP and Archive Services for SAP in order to leverage these services. Using WebAdmin, you can perform the following archiving services: Create, configure, and manage archives. Manage certificates for the archive. Create repository connections for Content Services. Create workflows and associate the same with archived documents. Configure document archival for Content Services. Perform DMS related services. You can: EMC Documentum Content Services for SAP Version 6.0 Installation Guide 15

16 Introducing Content Services for SAP Term Capture Capture Import SAP DMS SAP PLM SAP Master Record SAPGUI Definition Configure batch jobs for linking and replication tasks. Schedule and manage the execution of linking and replication jobs. Scanning module for Documentum and SAP that is part of the Content Services for SAP suite. Module that allows you to import scanned documents (or other documents) to SAP using the SAP ArchiveLink front end interface. This module is used with third party scanning applications like EMC Captiva InputAccel. The import module is part of the same application as Content Services Capture. The Content Services Capture can operate in two different modes (scan and import). Document Management System that is part of the SAP Basis System. Presents a logical layer to integrate with external systems like AutoCAD or Documentum. Not directly related to ArchiveLink. Product Life Cycle Management (PLM). SAP PLM provides an integrated environment that ensures all personnel involved in product development, manufacturing, and service have quick and secure access to current information. It provides a set of BAPI calls that can be used by external systems like Documentum. A set of master data, such as customer or vendor data, which is used in the creation of SAP documents. SAP graphical user interface. Graphical menu/screen tool that connects a client to the SAP server. 16 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

17 Introducing Content Services for SAP Term Original document SAP document Definition Paper based version of a document. Example 1 1. An invoice can consist of two sheets of paper received from a supplier. Paper documents are scanned in and stored as electronic documents in EMC Documentum. An electronic transactional record of header data and line items in SAP. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 17

18 Introducing Content Services for SAP 18 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

19 Chapter 2 Installing Content Services for SAP Server Components Overview This chapter describes the procedure for installing Content Services for SAP. The components of Content Services for SAP are configured using WebAdmin, which is installed with the other components. Instructions for using WebAdmin are provided in the EMC Documentum Content Services for SAP Administration Guide. Installing the Content Services for SAP Server consists of the following high level tasks. Each task contains a link to the detailed procedure: Installation scenarios, page 19 Installation prerequisites, page 21 Preinstallation checklist, page 26 Installing Content Services for SAP server components, page 29 Configuring IIS for WebAdmin on Windows 2003, page 34 Removing Content Services for SAP Windows services, page 37 Installation scenarios Content Services for SAP is an integrated suite of products that provide document management, imaging and archiving services. Services can be installed on different physical machines in different locations as long as the required functional components for each specific service are on the same machine. The following table provides an overview of possible system configurations and the functional component dependencies for each service or function. Note: SAP GUI is not required when using only server components and agents. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 19

20 Installing Content Services for SAP Server Components Table 2. System configuration and dependencies System configuration Content Services for SAP Administration including automated linking and data replication. Browser enabled viewing client View documents by selecting a link in SAPGUI. OLE viewing client View documents by selecting a link in SAP GUI or by calling a DRL directly from the repository. OLE viewing client View documents by calling a DRL directly from the repository. Scan and Link to SAP. SAP DMS Linking Links EMC Documentum documents to SAP equipment, material, functional location, customer, vendor, WBS element, or document info record. Functional component dependencies (must be on same physical machine) Windows + IIS + Content Services for SAP + Agent SAPGUI + View component Installed with Webtop integration SAP GUI + View component View component Capture component + SAP GUI + View component or WebView View component + Manage component The following illustration shows a possible scenario for how Content Services for SAP can be installed. 20 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

21 Installing Content Services for SAP Server Components Figure 2. Content Services for SAP installation scenario Installation prerequisites The following servers must be installed and configured as indicated before installing Content Services for SAP. EI Core docapp file The latest EI Core docapp file must be installed for the CS SAP Capture feature to work. More information about the CS SAP Capture feature is in the EMC Documentum Content Services for SAP Scanner Operator User Guide. Note: CS SAP version 5.3 server is incompatible with CS SAP version 6.0 Capture. More information about upgrading is in Upgrading Content Services for SAP. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 21

22 Installing Content Services for SAP Server Components Documentum Content Server (UNIX or Windows) The EMC Documentum Content Services for SAP Release Notes has version information. Documentum Content Server. A fully functional repository and the administrative logon/password used to configure it. Content Services for SAP WebAdmin server (Windows) Your WebAdmin Server must be a Microsoft Windows 2000 or 2003 Server, and must be configured as follows: The server must be able to ping both the Documentum Content Server and the R/3 server you intend to connect to via the TCP/IP network. If DNS is not being used, both of these servers should be identified in the HOSTS file. Your Windows Server machine must be configured with the following options: Microsoft Management Console Launch the MMC and verify that it is functioning properly. Microsoft Internet Information Server (IIS) IIS Manager is not installed with the Windows 2003 Server operating system by default. Furthermore, when you initially install IIS, it is installed in locked mode. If you do not have IIS Manger installed, or if you are running it in its default locked mode, refer to the Windows online help topic titled IIS Manager for detailed instructions. In IIS under the Microsoft Internet Information Server make sure your hostname is correct and that your Web site is running. To test the Web server, enter the following URL in your browser on the server host: A valid Microsoft Welcome to IIS Web page should display from your local drive. Errors or web pages from Internet sites indicate that the software is not installed or configured properly or that the World Wide Web Publishing Service and/or the IIS Service is not running. If these services are stopped you must start them and try the test again. Windows Scripting Host IIS must be completely installed and running with the VB scripting options. If scripting is not installed, the WebAdmin tool will not work. 22 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

23 Installing Content Services for SAP Server Components Access to a Documentum Content Server and an R/3 SAP server. See the Content Services for SAP Release Notes for supported versions. SAPGUI During installation Content Services for SAP installs librfc32.dll derived from the SAP DLL libraries. It is also a prerequisite that the latest version of SAPGUI be installed on the Content Services server. The SAPGUI should be launched from the Content Services server to test the SAP logon and verify the network connection. After Content Services for SAP is installed, the SAPGUI will be needed to get the SAP information required for the WebAdmin configurations. SAP R/3 server (UNIX or Windows) Manual configuration of SAP ArchiveLink and SAP DMS are prerequisites for installation of Content Services for SAP. Please refer to Configuring SAP R/3 for Content Services for SAP. Caution: Documentum is not responsible for problems encountered during installation due to SAP related issues such as empty or wrongly configured tables, or needed support packages, hot fixes, or OSS Notes. Documentum requires that you read and apply all ArchiveLink and DMS related OSS Notes and patches prior to Content Services for SAP installation. Documentum support is not responsible for answering SAP configuration questions/problems. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 23

24 Installing Content Services for SAP Server Components Figure 3. Windows server configuration 24 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

25 Installing Content Services for SAP Server Components Figure 4. Windows Unix Unix server configuration EMC Documentum Content Services for SAP Version 6.0 Installation Guide 25

26 Installing Content Services for SAP Server Components Preinstallation tasks You must follow the information in the pre installation checklist before you install Content Services for SAP. If the pre installation tasks are not done your system will not function properly. Preinstallation checklist You must perform the following steps before you install Content Services for SAP. Before you install Content Services for SAP: 1. Launch SAPGUI from the intended Content Services for SAP server or client and log on to the SAP system you wish to support. If this test fails, you must resolve the connection between Content Services for SAP and the SAP system before proceeding. 2. Be sure all previous versions of DocLink/Content Services are either removed physically or deactivated so that the install program can write over the old files. You will receive errors if DLL files are in use. (You may have to logoff and back on after stopping the services). 3. Test IIS by typing localhost in the browser on the intended Content Services for SAP server. A valid Microsoft Welcome to IIS Web page should display from the local drive. Errors or web pages from Internet sites indicate that IIS is not installed or configured properly. Please refer to Microsoft Internet Information Server (IIS) for important information about IIS. 4. The repository should be up, running and performing before any installation of Content Services occurs. Content Services requires a fully functioning repository and writes configuration objects into the chosen repository during the install. The installation creates an SAP cabinet and writes Content Services admin objects under the System cabinet. 5. Create a repository superuser called dm_doclink_sap to configure the repository for the version of SAP you are accessing. See dm_doclink_sap user, page 27. Continue with the following steps if you plan to archive SAP printlists, outgoing documents or data: 6. Create a directory on the SAP server. This directory will be used by SAP to store files temporarily until they are transported into Documentum. This directory must be configured in SAP for RFC archives. For RFC communication (TCP/IP), you must share and mount (UNIX) or map (Windows) this drive between the SAP server and the server where the Content Services Archive Services are installed (please see the Server Configuration Diagrams). Example: SAP server exports /export/spool, Documentum Content Server mounts /sap/spool. 26 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

27 Installing Content Services for SAP Server Components 7. If you wish to use Content Services for SAP with HTTP archiving services, you must also install Archive Services for SAP. For information on installing Archive Service for SAP, refer to the Archive Services for SAP Installation Guide. 8. If you wish to use Content Services for SAP with RFC archiving services, you must also install the RFC archiving services that is available as a part of Archive Services for SAP. For installation information, refer to the Archive Services for SAP Installation Guide. 9. Create a Content Services SAP user ID. Designate the user as a Dialog User. This user ID will be used by Content Services to connect to SAP to run queries. Give the user account sufficient access to all SAP data that will be queried during Content Services operations. dm_doclink_sap user On the Documentum Content Server create a special user in both the OS and your Documentum repository called dm_doclink_sap. This user is mandatory to run the Agent services. Without this repository user your installation will not operate correctly. If it is not possible to create dm_doclink_sap at the OS level due to operating system limitations or security issues there is a workaround. Please refer to dm_doclink_sap workaround for UNIX, page 28. dm_doclink_sap must be a Superuser to install the Content Services for SAP software and configure the repository. After the installation is completed, these privileges can be reduced. dm_doclink_sap must always have DELETE permissions on the System/DocLink folder and all of it s contents. The default ACL applied to the DocLink folder and contents when they are created during the repository configuration portion of the Content Services Server installation gives Owner DELETE permissions. dm_doclink_sap will have these permission by default if dm_doclink_sap was used to configure the repository. If some other repository user was entered during the repository configuration, that user will be the owner of the Content Services objects in the System/DocLink folder and ʺinsufficient permissionʺ errors may occur during some of the Content Services for SAP activities. To create the dm_doclink_sap user: 1. On the Documentum Content Server machine, create a user ID called dm_doclink_sap. 2. Set the user s permission to system administrator. 3. Set the user s password to never expire and not time out. 4. In Documentum Administrator, create a user ID in your repository called dm_doclink_sap. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 27

28 Installing Content Services for SAP Server Components 5. Set the repository user s permission to superuser. dm_doclink_sap workaround for UNIX If your repository is installed on a UNIX operating system, you may encounter a limitation on the length of user IDs in certain flavors of UNIX; this will prevent designating the user ID as dm_doclink_sap. Use the workaround described in the following sections to add dm_doclink_sap to the user list. This section contains the following topics: dm_doclink_sap workaround for UNIX (for repositories created using pre EMC Documentum Content Server 5.3 versions), page 28 dm_doclink_sap workaround for UNIX (for repositories created using EMC Documentum Content Server 5.3 and higher versions), page 29 dm_doclink_sap workaround for UNIX (for repositories created using pre EMC Documentum Content Server 5.3 versions) To add dm_doclink_sap to user list: 1. Create a UNIX OS user on the repository host server to use for Content Services Administration operations. Any ID will work. For example, tuser1. 2. Using Documentum Administrator create a new user for your UNIX repository called dm_doclink_sap. This user must be a superuser. 3. In the os user field, fill in your custom OS user created in step 1 (ʺtuser1ʺ). 4. On the Content Services for SAP server where WebAdmin and the Agent service are running, create a Windows user which has the same name as the UNIX OS user, in this case ʺtuser1, and the user rights Log on locally and Log on as a service. 5. When you are configuring the repository in, the installer asks for a repository user name. Type the OS user name: tuser1 Do not use the repository user name dm_doclink_sap. tuser1 is the alias for the dm_doclink_sap user name. 6. When you are configuring the Agent Service in Creating Content Services for SAP Windows services, page 33, the installer asks for a repository user name. Type the OS user name: tuser1 Do not use the repository user name dm_doclink_sap. tuser1 is an alias for the dm_doclink_sap user name. 28 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

29 Installing Content Services for SAP Server Components 7. When logging in to the repository, use the OS user name tuser1. The system will automatically translate tuser1 into dm_doclink_sap user internally. dm_doclink_sap workaround for UNIX (for repositories created using EMC Documentum Content Server 5.3 and higher versions) To add dm_doclink_sap to user list: 1. Using Documentum Administrator (DA) 5.3 or higher, create a new user in the repository called dm_doclink_sap. This user must be a superuser. 2. When creating the new user, from the User Source drop down field, select Inline Password. 3. In the Password field, type a password of your choice. 4. In the page, enter other relevant details for the user and click Finish. Selecting the Inline Password option ensures that you do not need to create the dm_doclink_sap user (or a workaround user) in the operating system. The dm_doclink_sap user is not authenticated against the operating system; this is because the login credentials are stored in the repository itself. Installing Content Services for SAP server components There are these parts to setting up the Content Services for SAP server: Installing the EI Core docapp file Copying the software to the Content Services for SAP server, page 30 Creating Content Services for SAP Windows services, page 33 Installing the EI Core docapp file This section provides instructions for installing the Install EI Core docapp file on all operating systems. To continue the installation on all operating systems: EMC Documentum Content Services for SAP Version 6.0 Installation Guide 29

30 Installing Content Services for SAP Server Components 1. Extract the Enterprise_Integration_Core compressed file (Enterprise_Integration_ Core.zip for windows and Enterprise_Integration_Core.tar for UNIX) to a temporary location. 2. Start the EMC Documentum Application Installer and log into a repository as a user with superuser privileges. The Select DocApp Archive dialog box appears. 3. Click Browse and locate the Enterprise_Integration_Core docapp folder. 4. Select the Enterprise_Integration_Core docapp folder and click OK. 5. Click Start Installation. An information message appears indicating that the installation will take a few minutes to complete. 6. Click Yes to continue. The EMC Documentum Application Installer installs the DocApp archive. 7. After the installation completes, check the DocApp s installation log file (<docapp_name>.html) for any docapp installation related errors. The <docapp_name>.html log file is created in the directory where the EMC Documentum Application Installer starts. Note: More information on installing docapps is in the How to Use section of EMC Documentum Application Installer online help. Copying the software to the Content Services for SAP server Use this procedure to download the Content Services for SAP server software. To copy the Content Services for SAP software: 1. Log on to the Content Services for SAP server (Windows machine) as an administrator. You may use the administrator for Content Services for SAP. 2. Download and unzip the current release of Content Services for SAP to a temporary directory on your local machine. This URL will take you to the download center login page where you can download the latest version of Content Services for SAP: Your default login ID is your e mail address. If you cannot locate your password use the password finder at the bottom of the login page. 30 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

31 Installing Content Services for SAP Server Components Note: Make sure the folder in which you unzip the release does not have any of the following special characters:! \ / : *? ʺ < >. For example, if the full path to the installer is C:\Downloads\!Documentum\NewRelease\ Content_Services_sap\server\setup.exe, the installation may fail because of the! in the folder name. 3. Navigate to..\content_services_sap\server\setup.exe in the directory where you unzipped the release. 4. Double click setup.exe. The Welcome dialog box appears. 5. Click Next. The Setup Type dialog appears. 6. Select Copy Software from the list in the Setup Type dialog. This option copies files to your machine. 7. Click Next. The Enter Product License Key dialog appears. 8. Type your product license key exactly as it appears. The license key is included in the product release package. 9. Click Next. The Select Components dialog appears. 10. Ensure that the boxes relating to the components that you want to install are checked. Note: It is recommended that you install everything; so, select all check boxes. 11. The default destination folder where the components are installed is C:\Documentum\DocLink. Documentum recommends you do not change the default destination unless you are completely familiar with the IIS and Content Services and are certain of the required path structure for those products. 12. Click Next. The Enter Web Server Directory for WebAdmin, WebView dialog appears. You must install Content Services for SAP in the same directory as IIS. The default destination folder is \InetPub\wwwroot\econnector. Do not change this default root directory during installation unless you changed the root directory when IIS was installed, and you are completely familiar with the IIS and Content Services. 13. Click Next. The Installer copies the files to the chosen locations and messages appear as required. Respond appropriately to these messages. If the dmcl.ini file already exists, you will be asked if you want to overwrite it. If you select Yes, or if you do not have a dmcl.ini file, you will be prompted to enter the name of the Documentum connection broker you want to use in the Documentum EMC Documentum Content Services for SAP Version 6.0 Installation Guide 31

32 Installing Content Services for SAP Server Components Configuration dialog. If you select No, the Start Copying Files dialog appears; skip to step 16. We recommend that you DO NOT overwrite any existing dmcl.ini file if you have an available repository. If you overwrite the current dmcl.ini, you will be overwriting your current connection broker entries. Note: Sometimes there is a conflict with installed dmcl.ini files. Some applications install the dmcl.ini file in the Windows directory, others in the Documentum directory. Make sure you have only one dmcl.ini file and that it is referencing the correct connection broker. 14. Enter the host name or IP address for the connection broker. 15. Click Next. The Start Copying Files dialog appears. This is a summary screen that lists all the selections you made previously in the installation wizard. 16. Check that the details are correct and click Next. 17. The files are copied and the RegSvr32 dialog appears. During the ʺCopy Softwareʺ portion of the Content Services for SAP server installation, the installer locates the file regsvr32.exe on the host machine using the windows path variable. This file is used to register the Content Services for SAP dynamic link libraries (DLL) and ActiveX Controls (OCX). regsvr32.exe usually exists in the directory C:\WINDOWS\system32. If the installer cannot find regsvr32.exe in the windows path, the following error message will display: Unable to launch regsvr32.exe. Please copy regsvr32.exe in the windows path. For more information please refer to install guide. If you get this message, please copy regsvr32.exe to the directory where you downloaded the installation files,..\content_services_sap\server. 18. Click OK. An Information dialog displays asking you to make changes in the Internet Services Manager after you finish this installation. 19. Click OK. The Setup Complete dialog appears. 20. Click Finish. The Content Services for SAP Server is installed. 32 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

33 Installing Content Services for SAP Server Components Changing registry values for SAP version If you re using SAP R/3 Server version 4.6x and later After repository configuration, the default Content Services for SAP Server registry value must be changed on the Content Services for SAP host server to trigger the server to use the PLM interface. Set the following registry value to True: HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\DocLink Server\Install\UseNewInterface > set to true. Since SAP 4.7 no longer supports the CAD interface, Content Services for SAP 5.3 SP3 will use the PLM interface even if UseNewInterface = false (set to false by default when CSS server is installed). If you re using SAP R/3 Server version prior to 4.7 If the following registry key HKEY_LOCAL_ MACHINE\SOFTWARE\Documentum\DocLink Server\Install\UseNewInterface is set to true, the PLM interface on pre SAP 4.7 versions will be used when running Agent operations. When UseNewInterface = true, all Agent jobs should use PLM objects if there s a PLM alternative available for the specific operation being configured. Link Documentum jobs that are configured to use the CAD interface will fail. If UseNewInterface = false, Link Documentum jobs that are configured to use the PLM interface will fail. Creating Content Services for SAP Windows services Creating Content Services for SAP Windows Services will set up the services for Content Services Archive and Content Services Agent. Once the services are installed they are configured from the WebAdmin tool. When you have created the archive services, you will need to change the start up condition from Control Panel > Services. It is important that you use an administrator or superuser ID like dm_doclink_sap or workaround ID when performing these activities (particularly for the Agent service). You can check for errors using the Event Viewer which is found in Start>Settings>Control Panel >Administrative Tools >Event Viewer. To create Content Services for SAP Windows services: 1. Navigate to the temporary directory where you downloaded the release, and go to..\content_services_sap\server\setup.exe. 2. Double click setup.exe. The Welcome dialog appears 3. Click Next. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 33

34 Installing Content Services for SAP Server Components The Select Type dialog appears. 4. Select Agent Service Create from the list. 5. Click Next. The Content Services for SAP (Agent) Parameters dialog box appears. 6. Type in the fields as described next: a. Repository to be used with Content Services Agent. b. Docbase User Name: must be dm_doclink_sap or workaround ID. c. Password. d. Confirm Password. e. Microsoft Windows Domain Name (if required). 7. Click Next. Consult your network administrator for the correct domain name. The Ready to Create Services dialog box appears. 8. Check the details and click Next. The Services to be created section displays the service you selected in step Click OK. A dialog asks you whether you want to create another service. If you click Yes, you are returned to the Select Components page. If you click No, you are forwarded to the Finish dialog. 10. Click Finish. The Content Services for SAP (Agent) <Repository Name> service is created. Configuring IIS for WebAdmin on Windows 2003 If you re installing Content Services for SAP Server on a Windows 2003 host server, you must configure and complete the post installation tasks for IIS for WebAdmin as described below. Note: IIS Manager is not installed with the Windows 2003 Server operating system by default. Furthermore, when you initially install IIS, it is installed in locked mode. If you do not have IIS Manger installed, or if you are running it in its default locked mode, refer to the Windows online help topic titled IIS Manager for detailed instructions. 34 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

35 Installing Content Services for SAP Server Components To configure IIS for WebAdmin on Windows 2003: 1. Open IIS Manager, expand the master server node (that is, the Servername node), and then select the Web service extensions node. 2. In the right pane of IIS Manager, select Active Server Pages. 3. Click Allow. To complete post installation for WebAdmin on Windows 2003: 1. Ensure all extensions at the following location are set to Allowed: IIS Manager > <domain> > Web Service Extensions Where <domain> is the hostname. 2. Ensure execute permissions at the following location is set to Scripts and Executables: IIS Manager > <domain> > Properties of econnector Where <domain> is the hostname. 3. In the Administrator Properties dialog box, click Remove to clear the existing application name and create a new application name, a shown below. 4. Navigate to the dmcl cache directory. For example: C:\Documentum\dmcl 5. Ensure that Modify Permissions is set for user IIS_WPG. 6. Restart IIS Manager. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 35

36 Installing Content Services for SAP Server Components Configuring WebView To prepare the web application server to support WebView: 1. Shutdown the web application server that will support WebView. 2. Deploy wdk.war to that web application server. The wdk.war file is in the temporary directory where you downloaded and unzipped webview.zip. 3. Located the dfc.properties file in the wdk/web INF/classes folder. 4. Edit the dfc.properties file with your docbase login parameters. For example: dfc.docbroker.host[0]=vmeidevrepos dfc.globalregistry.repository=sap53_dev_sc dfc.globalregistry.username=dmadmin dfc.globalregistry.password=dm_admin_pwd 5. Restart the web application server. Installing the Daeja plug in Daeja is not delivered with WebView, but is compatible with WebView and supports the following formats: PDF Tiff JPEG BMP GIF To use the Daeja plug in, download and install the plug in from the Daeja website at: Follow the website instructions for installing the plug in. To enable WebView to use Daeja: 1. Shutdown the web application server that supports WebView. 2. Locate the dmei_webview unobfs.jar file in the wdk/ WEB INF/lib folder. 3. Open the webview.properties file that is in the dmei_webview unobfs.jar file. 36 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

37 Installing Content Services for SAP Server Components 4. Set the following parameter from false to true: DaejaViewer = true Note: By default, the DaejaViewer parameter is set to false. 5. Restart the web application server. Installing the image services docapp You must install the image services docapp for WebView and the Daeja plug in to work correctly together. To install the image services docapp: 1. Locate ImageServices_XYZ.zip bundled inside webview.zip. 2. Unzip the contents of ImageServices_XYZ.zip to a temporary directory and use the EMC Documentum Application Installer to install the image services docapp into your docbase. More information on using the EMC Documentum Application Installer is in Installing the EI Core docapp file. 3. Open the webview.properties file and set the DaejaViewer property to true. By default the DaejaViewer property is set to false. 4. Reload the WDK application or restart the web application server. The webview.properties file change is enabled and the image services docapp installation is complete. Removing Content Services for SAP Windows services This procedure is used to clean up in case you made a mistake in the repository name or RFC Destination, before changing Agent services or before uninstalling previous versions of Content Services for SAP. Note: You can determine the existing repository name by looking at Windows Services in Administrative Tools. Ensure that you stop the services you want to remove before running the uninstaller. EMC Documentum Content Services for SAP Version 6.0 Installation Guide 37

38 Installing Content Services for SAP Server Components To remove Content Services for SAP Windows services: 1. Navigate to the temporary directory where you downloaded the release, and go to..\content_services_sap\server\setup.exe. 2. Double click setup.exe. The Welcome dialog appears. 3. Click Next. The Setup Type dialog appears. 4. Select Agent Service Remove from the list. 5. Click Next. 6. Type the repository name and click Next. 7. A confirmation dialog appears. 8. Click Next. The service is removed. A dialog appears. If you want to remove another service, click Yes. If you click No, you will be forwarded to the Finish dialog. 9. Click Finish. 38 EMC Documentum Content Services for SAP Version 6.0 Installation Guide

39 Chapter 3 Starting services Overview This chapter discusses how to start the services that run Content Services. These concepts are described in the following sections: Starting Agent services on Windows, page 39 Configuring logging, page 39 Starting Agent services on Windows Use the following procedure to start the Windows services: 1. Launch the Service Control Manager via Start > Settings > Control Panel> Administrative Tools> Services. 2. Select and start the following service: Content Services for SAP (Agent) <repository> Configuring logging If the Agent services encounter any errors during start up or while running, there are two places where errors may be logged: Windows Event Viewer <EMC Documentum Installation Directory>\DocLink\log The Event Viewer can be accessed from Start > Programs > Administrative tools (Common) > Event Viewer. When you start the viewer choose both Application and System logs to see both types of messages. On Windows these are found under the Log menu. Content Services errors may be classified as Source names ʺContent Services for SAPʺ, ʺContent Services Agentʺ, or ʺService Control Manager.ʺ Agent service logs are written to a log file in C:\Documentum\DocLink\log (assuming default installation). These log files use the naming convention dmagent*.log for the Agent service. To change the log locations and debug levels, go to the following registry settings: EMC Documentum Content Services for SAP Version 6.0 Installation Guide 39

40 Starting services HKEY_LOCAL_MACHINE > SOFTWARE > Documentum > Doclink > Agent > Docbase > <repository name> Under these keys you will find a debug_level (3 is recommended for troubleshooting) and a log_dir which is the log path. Setting the debug level allows you to see if there are any problems and to make sure the software runs properly. Once the software runs as expected, be sure to set the debug level back to 0. If debugging is left on, log files fill up quickly even if nothing is archived, and can eventually consume a tremendous amount of disk space. WebView logging This section provides information about WebView logging. Log4j The log4j.properties file is located in the wdk/web INF/classes directory. Change the debug level by updating following line as follows: log4j.logger.com.documentum.ei.webview=debug,eiwebviewlog The default location of the log file is specified at following line: log4j.appender.eiwebviewlog.file=c\:/documentum/logs/webview.log. WDK Tracing WDK tracing flags trace operations and content manipulation, such as: Sessions JSP requests Locales Actions Configuration The full list of tracing flags and their usage is in your WDK documentation. After enabling tracing, tracing statements are written to the wdk.log file in the DOCUMENTUM_HOME/config directory selected during the first installation of a Documentum product. WDK tracing flags are listed in the WDK resource file, TraceProp.properties, located in the /WEB INF/classes/com/documentum/debug 40 EMC Documentum Content Services for SAP Version 6.0 Installation Guide