ContentServices forSAP Installation Guide - Dell EMCSAP), andContentServices Administrator ContentServicesforSAP InstallationGuide Providestheprocedures forinstallingContent Services

Content Services for SAP InstallationGuide

Version 5.3 SP1October 2005

Copyright © 1994-2005 EMC Corporation. All rights reserved.

Table of Contents

Preface ........................................................................................................................... 7

Chapter 1 Introducing Content Services for SAP ................................................... 13Overview ................................................................................................... 13Understanding the Content Services for SAP architecture ............................. 14Supported SAP document formats............................................................... 16Understanding SAP and Content Services for SAP terms .............................. 16

Chapter 2 Installing Content Services for SAP Server Components ...................... 19Overview ................................................................................................... 19Installation scenarios .................................................................................. 19Installation prerequisites ............................................................................. 21Documentum Content Server (UNIX or Windows) ................................... 21Content Services for SAP WebAdmin server (Windows)............................ 22SAP R/3 server (UNIX or Windows)......................................................... 23

Preinstallation tasks ................................................................................... 26Preinstallation checklist .......................................................................... 26dm_doclink_sap user .............................................................................. 27dm_doclink_sap workaround for UNIX ................................................... 28

Upgrading Content Services for SAP ........................................................... 29Preupgrade tasks .................................................................................... 29Upgrading an Existing Content Services Installation ................................. 29

Installing Content Services for SAP Server Components................................ 30Copying the software to the Content Services for SAP server ..................... 31Configuring the repository for Content Services for SAP ........................... 33Changing registry values for SAP version ................................................ 34Creating Content Services for SAP Windows services ............................... 35Changing the RFC start-up condition ................................................... 37

Configuring and starting WebAdmin ........................................................... 38Configuring IIS for WebAdmin on Windows 2003 ........................................ 39Removing Content Services for SAP Windows services ................................. 40Installing Content Services for SAP on UNIX systems ................................... 41Copying the software to the local machine ............................................... 41Installing the archive .............................................................................. 41Configuring the archive .......................................................................... 43Configuring Trusted Login .................................................................. 43Example:........................................................................................ 44

Configuring DMCL.INI....................................................................... 44Example:........................................................................................ 45

Chapter 3 Starting Processes ................................................................................ 47Overview ................................................................................................... 47Starting Agent and RFC processes on Windows ........................................... 47

Content Services for SAP Installation Guide 3

Table of Contents

Configuring logging ............................................................................... 48Starting RFC archive processes on UNIX ...................................................... 48

Chapter 4 Installing Print List Transformation Filters ............................................ 53Overview ................................................................................................... 53On-demand rendering versus stored rendering ............................................ 53Configuring EMC Documentum Content Server for on-demandrendering ................................................................................................... 54

Chapter 5 Installing Content Services for SAP Client Components ....................... 57Overview ................................................................................................... 57System configuration and dependencies....................................................... 57User roles and client components ................................................................ 58Installation prerequisites ............................................................................. 59Customizing installation ............................................................................. 59Upgrading Content Services for SAP ........................................................... 61Installing Content Services for SAP Client Components ................................ 62Configuring the View component for Webtop........................................... 64Silent Installation.................................................................................... 64

Postinstallation tasks.................................................................................. 65

Chapter 6 Testing the Installation .......................................................................... 67Overview ................................................................................................... 67Testing the installation using WebAdmin ..................................................... 67Prerequisites for testing the installation.................................................... 68Connecting to WebAdmin ....................................................................... 68Configuring the SAP server ..................................................................... 69Configuring an SAP user......................................................................... 69Creating an SAP query............................................................................ 70Testing an SAP query.............................................................................. 70

Testing an RFC archive installation .............................................................. 71

Chapter 7 Troubleshooting Installation Issues ...................................................... 73Overview ................................................................................................... 73Troubleshooting IIS-related issues ............................................................... 73Correcting SAP queries (BAPI configuration) ............................................... 74SAP 4.6b BAPI workaround for German language .................................... 75

Chapter 8 Uninstalling Content Services for SAP .................................................. 77Overview ................................................................................................... 77Uninstalling Content Services for SAP server components............................. 77Removing the Content Services for SAP software ..................................... 78Deleting default SAP configuration information or data ............................ 78

Uninstalling Content Services for SAP client components.............................. 79

4 Content Services for SAP Installation Guide

Table of Contents

List of Figures

Figure 1–1. Content Services for SAP and SAP ................................................................... 14Figure 2–1. Content Services for SAP installation scenario .................................................. 21Figure 2–2. Windows server configuration......................................................................... 24Figure 2–3. Windows-Unix-Unix server configuration ........................................................ 25


Table of Contents

List of Tables

Table 1–1. Terms and definitions ..................................................................................... 16Table 2–1. System configuration and dependencies........................................................... 20Table 2–2. Unpacked files................................................................................................ 42Table 5–1. System configuration and dependencies........................................................... 58Table 6–1. Prerequisites for testing the installation............................................................ 68


Preface

Purpose of this guideThis manual explains how to install and configure the components of Content Servicesfor SAP. It contains information about installation requirements, and provides detailsof the tasks performed with the software.

Intended audienceIn order to address the manuals to the correct audience, the roles of the users of themanuals have been defined as follows:

• System Administrator - This role covers users who install and configure ContentServices. The Content Services application integrates Documentum and the SAP R/3system. Therefore, system administrators may require experience with:

— Windows XP, 2000, 2003, or HP-UX 11i

— UNIX (if Documentum Content Server or SAP R/3 are installed on a UNIX-basedplatform).

— Documentum Technologies like Content Server and DFC

— SAP R/3 versions 4.6c or 4.7

— The following databases, depending on your system platform:

— DB2

— Oracle

— SQL Server

— Sybase• 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.


Preface

Revision historyThis section contains a description of this document’s revision history.

Revision history

Revision date Description

January 2004 Initial publication of document forContent Services for SAP 5.2.5.

Changed product name from eConnectorto Content Services for SAP. Changedproduct version to 5.2.5.

March 2004 Removed erroneous information aboutlicensing. There is only one licenserequired to install and use ContentServices for SAP (not two as previouslystated).

January 2005 Revised publication for Content Servicesfor SAP 5.2.5 SP3.

June 2005 Revised publication of document for CSfor SAP - Archiving Server 5.3.

October 2005 Revised publication for Content Servicesfor SAP 5.3 SP1.

Organization of this guideThis guide contains the following chapters. The table below lists the information thatyou can expect to find in each.

Organization of this guide

Chapter Contents

Chapter 1, Introducing Content Servicesfor SAP

Provides an overview of Content Servicesfor SAP.

Chapter 2, Installing Content Services forSAP Server Components

Describes the procedure for installing theserver components of Content Servicesfor SAP.

Chapter 3, Starting Processes Describes how to start the processes thatrun Content Services for SAP.


Preface

Chapter Contents

Chapter 4, Installing Print ListTransformation Filters

Describes how to install the PrintlistFilters.

Chapter 5, Installing Content Services forSAP Client Components

Describes how to install the clientcomponents of Content Services for SAP.

Chapter 6, Testing the Installation Describes how to test the Content Servicesfor SAP connection to SAP and ContentServices Archive.

Chapter 7, Troubleshooting InstallationIssues

Describes how to troubleshoot installationissues.

Chapter 8, Uninstalling Content Servicesfor SAP

Describes how to uninstall ContentServices for SAP.

Typographic conventionsThis 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> Represents a variable name for which youmust provide a value, or a defined term.

Information in this fontRepresents code samples, user input, andcomputer output.

[] square brackets Used in method command syntaxspecifications, square brackets indicate anoptional argument.

{} curly brackets Used in method command syntaxspecifications, curly brackets indicate anoptional argument that can be repeatedmore than once.

Related documentationThis 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 foundon Documentum’s download center: https://documentum.subscribenet.com.


https://documentum.subscribenet.com

Preface

From Subscribenet, you can download the latest version of Content Services and therelated documentation suite. To access the contents in Subscribenet, you will need toprovide the login credentials assigned to you when you first applied for access.

Note: Your login ID, by default, is your email address. If you cannot locate yourpassword, use the password finder at the bottom of the login page.

If you’re accessing Subscribenet for the first time, you will need to apply for access andobtain a user name and password. Refer to Applying for access.

Content Services for SAP — Documentation suite

Title Description Target role

Content Services for SAPRelease Notes

Provides an overviewof new and amendedfeatures, known bugs,limitations, miscellaneoustechnical notes, anddocumentation correctnessand clarifications.

Standard User, SystemAdministrator, SystemAdministrator (SAP),and Content ServicesAdministrator

Content Services for SAPInstallation Guide

Provides the proceduresfor installing ContentServices.

System Administrator

Configuring SAP R/3 forContent Services for SAP

Describes the configurationtasks that need to beperformed in SAP so thatSAP can communicate withContent Services.

System Administrator(SAP)

Content Services for SAPAdministration Guide

Describes how to configureContent Services using theWebAdmin tool.

Content ServicesAdministrator

Content Services for SAPUser Guide

Describes how SAP usersview documents.

Standard User

Applying for access

To apply for access to Support online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Click the Request Access link.

4. Complete the form and send it.Documentum will respond to your request within two business days.


http://www.documentum.com

Preface

Accessing documentation online

Customers with a Software Support Agreement can read our product documentationat the Documentum Web site. You must have a valid user name and password, andAdobe Acrobat Exchange or Acrobat Reader installed on your system in order to viewthe documentation.

To access documents online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Log on to the Support page.

4. Click the Documentation link.

5. Select how you want to display the documentation.

6. Click List.

7. Click the name of the document.

Purchasing bound paper manuals

Our product documentation is available for purchase as bound paper manuals. Toplace an order, call the Documentation Order Line at (925) 600-6666. You can pay witha purchase order, check, or credit card.


http://www.documentum.com

Preface


Chapter 1Introducing Content Services for SAP

OverviewThe Content Services for SAP application integrates the Documentum contentmanagement system with the SAP R/3 system. It is an interface to the SAP R/3 systembased on SAP’s standard DMS and ArchiveLink interfaces.

Content Services for SAP provides the following functionalities:

• Enables users to easily access and display documents stored in a Documentumrepository from a variety of SAP modules.

• Links documents stored in Documentum to a variety of SAP documents.• Archives SAP data, reports, and documents through ArchiveLinkTM certified

interfaces in Documentum.• Stores and manages reports and outgoing documents in DocumentumThis chapter covers the following topics:• Understanding the Content Services for SAP architecture, page 14• Supported SAP document formats, page 16• Understanding SAP and Content Services for SAP terms, page 16


Introducing Content Services for SAP

Understanding the Content Services for SAParchitectureFigure 1-1. Content Services for SAP and SAP

Content Services for SAP consists of the following components:

• RFC Archiving Server

A server component that enables you to archive reports, data, incoming andoutgoing documents from SAP to the Documentum repository. The archivedreports and documents can later be retrieved and viewed through SAPGUI andDocumentum clients. This component uses SAP Remote Function Calls (RFCs) tocommunicate with SAP.

• Agent services



A server component that allows you to automate the linking process between SAPobjects and documents, as well as maintain those links. This substantially improvesproductivity, information integrity, and information availability.

• Capture

Enables you to scan documents, store the images in a Documentum repository, andcreate a link to the appropriate transaction documents in SAP. Once this link iscreated, the document is accessible from SAPGUI, the SAP client interface. TheCapture component is part of Documentum’s integration to ArchiveLink.

• Manage

Enables you to release Documentum documents to SAP, and to maintain thosereleased 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 R/3 client computer that needsto access reports, drawings and other documents stored in a Documentumrepository.

• Rendition Services

Build-in filters that provide the following renditions::

— PDF rendition

— ASCII text rendition

— HTML rendition

When one of these built-in filters are used, the desired document rendition isgenerated when the document is archived in the repository.

• WebAdmin

An administrative console that allows you to:

— Create, configure, and manage archives

— Manage certificates for the archive

— Create repository connections for Content Services

— Configure document archival for Content Services



Note: Please refer to the Content Services for SAP Release Notes for detailed informationabout specific OS versions and supported software environments.

Supported SAP document formatsDocumentum 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)

Understanding SAP and Content Services forSAP terms

This section presents some terms and their definitions, as used in this guide.

Table 1-1. Terms and denitions

Term Definition

Content Services for SAP Product that connects Documentum toSAP and vice versa.

Archiving Server Server component that, using an HTTPconnection to SAP, enables you to archivereports, data, incoming and outgoingdocuments from SAP to the Documentumrepository. Archiving Server is a J2EEWeb application based on the SAPArchiveLink interface. The archivedreports and documents can later beretrieved and viewed through SAPGUIand Documentum clients.

ArchiveLink Cross-functional interface that is partof the SAP Basis System. ArchiveLinkhandles storing and retrieving documentsand data to and from a repository externalto SAP.



Term Definition

WebAdmin An administrative console that allows youto:• Create and manage archives• Manage certificates for the archive• Create repository connections for theContent Services

Capture Scanning module for Documentum andSAP that is part of the Content Servicesfor SAP suite.

Capture Import Module that allows you to import scanneddocuments (or other documents) to SAPusing the SAP ArchiveLink front-endinterface. This module is used with thirdparty scanning applications like InputSoftware. The import module is part ofthe same application as Content ServicesCapture. The Content Services Capturecan operate in two different modes (scanand import).

SAP DMS Document Management System that ispart of the SAP Basis System. Presentsa logical layer to integrate with externalsystems like AutoCAD or Documentum.Not directly related to ArchiveLink.

SAP PLM Product Life-Cycle Management (PLM).SAP PLM provides an integratedenvironment that ensures all peopleinvolved in product development,manufacturing, and service have quickand secure access to current information.It provides a set of BAPI calls thatcan be used by external systems likeDocumentum.

SAP Master Record A set of master data, such as customer orvendor data, which is used in the creationof SAP documents.

SAPGUI SAP Graphical User Interface. Graphicalmenu/screen tool that connects a client tothe SAP server.



Term Definition

Original Document Paper based version of a document.

Example 1-1.An invoice may consist of two sheetsof paper received from a supplier.Paper documents are scanned in andstored as electronic documents in EMCDocumentum.

SAP Document An electronic transactional record ofheader data and line items in SAP.


Chapter 2Installing Content Services for SAPServer Components

OverviewThis chapter describes the procedure for installing Content Services for SAP.

The components of Content Services for SAP are configured using WebAdmin, which isinstalled with the other components. Instructions for using WebAdmin are provided inthe 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.

• Review the installation scenarios. Refer to Installation scenarios, page 19.• Review the installation prerequisites. Refer to Installation prerequisites, page 21.• Review the sample server configuration diagrams. Refer to Figure 2–2, page 24

and Figure 2–3, page 25.• Carry out the Preinstallation checklist, page 26.• Install the Content Services for SAP Server application, repository objects and

types, and Windows services. Refer to Installing Content Services for SAP ServerComponents, page 30.

• Start WebAdmin. Refer to Configuring and starting WebAdmin, page 38.• Configure IIS for WebAdmin on Windows 2003. Refer to Configuring IIS for

WebAdmin on Windows 2003, page 39.• Remove Content Services for SAP Windows services. Refer to Removing Content

Services for SAP Windows services, page 40.• Install the Content Services Archive Services on UNIX (if applicable). Refer to

Installing Content Services for SAP on UNIX systems, page 41.

Installation scenariosContent Services for SAP is an integrated suite of products that provide documentmanagement, imaging and archiving services. Services can be installed on differentphysical machines in different locations as long as the required functional components


Installing Content Services for SAP Server Components

for each specific service are on the same machine. The following table provides anoverview of possible system configurations and the functional component dependenciesfor each service or function:

Table 2-1. System conguration and dependencies

System configuration Functional component dependencies(must be on same physical machine)

Content Services for SAP Administrationincluding automated linking and datareplication

Windows + IIS + Content Services for SAP+ Agent + RFC Archiving Server (RFCArchive service could also be installed onthe Documentum Content Server)

Archiving docs/reports/data Archiving Server + Agent + SAPGUI +View or WebView

(RFC Archive services must be runningon the Documentum Content Server.Content Services Agent service must berunning on the Content Services for SAPserver for some operations.)

Browser enabled viewing client - viewdocuments by selecting a link in SAPGUI

SAPGUI + View component - installedwith Webtop integration

OLE viewing client - view documents byselecting a link in SAP GUI or by calling aDRL directly from the repository

SAP GUI + View component

OLE viewing client - view documents bycalling a DRL directly from the repository

View component

Scan and Link to SAP Capture component + SAP GUI + Viewcomponent or WebView

SAP DMS Linking - Links EMCDocumentum documents to SAPequipment, material, functional location,customer, vendor, WBS element, ordocument info record

View component + Manage component

The following illustration shows a possible scenario for how Content Services for SAPcan be installed.



Figure 2-1. Content Services for SAP installation scenario

Installation prerequisitesThe following servers must be installed and configured as indicated before installingContent Services for SAP.

Documentum Content Server (UNIX or Windows)

See Content Services for SAP Release Notes for 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 mustbe configured as follows:

• The server must be able to ping both the Documentum Content Server and the R/3server 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 bydefault. 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 detailedinstructions.

In IIS under the Microsoft Internet Information Server make sure your hostname iscorrect and that your Web site is running.

To test the Web server, enter the following URL in your browser on the server host:

http://localhost:<port>

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 installedor configured properly — or that the World Wide Web Publishing Service and/orthe IIS Service is not running. If these services are stopped you must start themand try the test again.

• Windows Scripting Host

IIS must be completely installed and running with the VB scripting options. Ifscripting is not installed, the WebAdmin tool will not work.

• Access to a Documentum Content Server and an R/3 SAP server. See the ContentServices for SAP Release Notes for supported versions.

• SAPGUI

During installation Content Services for SAP requires certain DLL libraries fromSAP in order to operate. For this reason it is a prerequisite that the latest versionof SAPGUI be installed on the Content Services server. The SAPGUI should belaunched from the Content Services server to test the SAP logon and verify thenetwork connection. After Content Services for SAP is installed, the SAPGUI will beneeded 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 forinstallation of Content Services for SAP. Please refer to Configuring SAP R/3 for ContentServices for SAP.

Caution: Documentum is not responsible for problems encountered during installationdue to SAP related issues such as empty or wrongly configured tables, or needed supportpackages, hot fixes, or OSS Notes. Documentum requires that you read and apply allArchiveLink and DMS related OSS Notes and patches prior to Content Services for SAPinstallation. Documentum support is not responsible for answering SAP configurationquestions/problems.



Figure 2-2. Windows server conguration



Figure 2-3. Windows-Unix-Unix server conguration



Preinstallation tasksYou must follow the information in the pre-installation checklist before you installContent Services for SAP. If the pre-installation tasks are not done your system will notfunction 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 andlog on to the SAP system you wish to support. If this test fails, you must resolve theconnection before proceeding. Content Services for SAP logs into the SAP systemand requires files from the SAPGUI directory to operate.

2. Be sure all previous versions of DocLink/Content Services are either removedphysically or deactivated so that the install program can write over the old files. Youwill receive errors if DLL files are in use. (You may have to logoff and back on afterstopping the services).

3. Test IIS by typing localhost in the browser on the intended Content Services for SAPserver. A valid Microsoft Welcome to IIS Web page should display from the localdrive. Errors or web pages from Internet sites indicate that IIS is not installed orconfigured properly. Please refer to “Microsoft Internet Information Server (IIS)” forimportant information about IIS.

4. The repository should be up, running and performing before any installation ofContent Services occurs. Content Services requires a fully functioning repositoryand writes configuration objects into the chosen repository during the install. Theinstallation creates an SAP cabinet and writes Content Services admin objects underthe System cabinet.

5. Create a repository superuser called dm_doclink_sap to configure the repository forthe 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, outgoingdocuments or data:

6. Create a directory on the SAP server. This directory will be used by SAP to store filestemporarily until they are transported into Documentum. This directory must beconfigured in SAP for RFC archives. For RFC communication (TCP/IP), you mustshare and mount (UNIX) or map (Windows) this drive between the SAP server andthe 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’.

7. If you wish to use Content Services for SAP with HTTP archive services, you mustfirst install Archive Services for SAP. For information on installing Archive Servicefor SAP, refer to the Archive Services for SAP Installation Guide.

8. If you are using RFC archive services, create an Archive "shared directory" OS userID on the server where the Content Services RFC Archive Services are installed. Givethis user Delete or Full Control privileges on the shared directory. If the ContentServices Archive Services are installed on Windows, map a drive to the shareddirectory and connect with this user ID. After installing the Content Services RFCArchive Services this user ID will also be used as follows:• On a UNIX platform: The RFC Archive Services will be started by the Archive

user.• On a Windows platform: The RFC Archive Services will be configured to "Log

on as" the user to access the shared directory.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 theuser account sufficient access to all SAP data that will be queried during ContentServices operations.

dm_doclink_sap user

On the Documentum Content Server create a special user in both the OS and yourDocumentum repository called dm_doclink_sap. This user is mandatory to run theAgent 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 systemlimitations or security issues there is a workaround. Please refer to dm_doclink_sapworkaround for UNIX, page 28.

dm_doclink_sap must be a Superuser to install the Content Services for SAP softwareand configure the repository. After the installation is completed, these privilegescan be reduced. dm_doclink_sap must always have DELETE permissions on theSystem/DocLink folder and all of it’s contents. The default ACL applied to the DocLinkfolder and contents when they are created during the repository configurationportion of the Content Services Server installation gives Owner DELETE permissions.dm_doclink_sap will have these permission by default if dm_doclink_sap was usedto configure the repository. If some other repository user was entered during therepository configuration, that user will be the owner of the Content Services objects inthe System/DocLink folder and "insufficient permission" errors may occur during someof the Content Services for SAP activities.



To create the dm_doclink_sap user:

1. On the Documentum Content Server machine, create a user ID calleddm_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 calleddm_doclink_sap.

5. Set the repository user’s permission to superuser.

dm_doclink_sap workaround for UNIX

This user must exist at the operating system and repository levels. If your repositoryresides on a UNIX operating system you may encounter a limitation on the length ofuser IDs, which will prevent adding dm_doclink_sap. If so, please use the followingworkaround to add dm_doclink_sap to the user list.

To add dm_doclink_sap to user list:

1. Create a UNIX OS user on the repository host server to use for Content ServicesAdministration operations. Any Id will work. The Following screen shots show anexample using an OS user called "tuser1".

2. Using Documentum Administrator create a new user for your UNIX repositorycalled 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 arerunning, create a Windows user which has the same name as the UNIX OS user, inthis case "tuser1”, and the user rights “Log on locally” and “Log on as a service.”

5. When you are configuring the repository in Configuring the repository for ContentServices for SAP, page 33, the installer asks for a repository user name. Type theOS user name:tuser1

Do not use the repository user name dm_doclink_sap. tuser1 is the alias for thedm_doclink_sap user name.

6. When you are configuring the Agent Service in Creating Content Services for SAPWindows services, page 35, the installer asks for a repository user name. Type theOS user name:tuser1



Do not use the repository user name dm_doclink_sap. tuser1 is an alias for thedm_doclink_sap user name.

7. When logging in to the repository, use the OS user name “tuser1”. The system willautomatically translate “tuser1” into dm_doclink_sap user internally.

Upgrading Content Services for SAPIf you have an earlier version of Content Services for SAP then you need to upgradeusing the following information.

Preupgrade tasks

When upgrading RFC make sure there are no pending requests in the server queue.

It is not necessary to remove an existing RFC. You may want to have it as a backup.

When upgrading the Agent make sure there are no pending jobs. De-activate jobs andre-activate the jobs upon upgrade completion.

Upgrading an Existing Content Services Installation

The following steps are required:

1. Uninstall the existing software using Microsoft ADD/REMOVE programs, as follows:

a. Log out of and close all Content Services applications.

b. Stop Content Services Services (AGENT and RFC).

c. Stop the IIS service to end any Content Services HTTP activity.

d. Open Control Panel > Add/Remove Programs.

e. Remove the Content Services Clients.

f. If you receive messages stating that DLLs are in use, open the Task Managerand end the process indicated in the message. If something is still preventingremoval of the programs, reboot the server and try again.

g. If DmView.exe or DmWebView.exe was manually copied to a directory otherthan the default installation directory after the client installation, make sure



these files are deleted before reinstalling the new clients. Installshield uninstallerwill not remove these files during the uninstall.

h. Remove the Content Services Server.After you have run the uninstaller, you must navigate to the server installationdirectories and manually delete any leftover files.For example, the Doclink folder, which is installed in the Documentum folder inthe server installation directory.

2. Install the server software (copy software). Please refer to Copying the software tothe Content Services for SAP server, page 31 for installation information.

3. This step is required only if you are upgrading from DocLink for SAP 4.0 or 4.01.Configure the repository using the UPGRADE option. Please refer to Configuringthe repository for Content Services for SAP, page 33 for configuration information.The upgrade process copies all dm_relation objects where relation name begins with"sap_" into a new relation object of type "sap_link_relation". The old relation objectsare not removed but the expiry date is set to the current date.

4. For a 4.5 to 4.5.5 upgrade only: Log on to WebAdmin and under Actions>LinkDocumentum, delete the configuration called "Start invoice workflow in SAP".This configuration will be replaced during the 4.5.5 install during repositoryconfiguration.

5. For a 4.5 to 4.5.5.1 upgrade OR 4.5.5 to 4.5.5.1 upgrade: Configure the repository forthe correct SAP version. Do this even if you configured the repository for the correctSAP version during a previous installation of Content Services or DocLink for SAP.

6. Configure the repository for the correct SAP version. Do this even if you configuredthe repository for the correct SAP version during a previous installation of ContentServices or DocLink for SAP.

7. Upgrade all client applications. You must re-install your clients after you upgradethe server. Refer to Preinstallation tasks , page 26 for more information.

Installing Content Services for SAP ServerComponents

There are three parts to setting up the Content Services for SAP server:

• Copying the software to the Content Services for SAP server, page 31• Configuring the repository for Content Services for SAP, page 33• Creating Content Services for SAP Windows services, page 35



Copying the software to the Content Services for SAPserver

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 anadministrator. You may use the administrator for Content Services for SAP.

2. Download and unzip the current release of Content Services for SAP to a temporarydirectory on your local machine.This URL will take you to the download center login page whereyou can download the latest version of Content Services for SAP:https://documentum.subscribenet.comYour default login ID is your e-mail address.If you cannot locate your password use the password finder at the bottom of thelogin page.

Note: Make sure the folder in which you unzip the release does not haveany of the following special characters: ! \ / : * ? " < > |. For example, ifthe 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 youunzipped the release.

4. Double-click setup.exe.TheWelcome dialog 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 includedin 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 isC:\Documentum\DocLink. Documentum recommends you do not change thedefault destination unless you are completely familiar with the IIS and ContentServices 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 defaultdestination folder is \InetPub\wwwroot\econnector. Do not change this defaultroot directory during installation unless you changed the root directory when IISwas 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 youselect Yes, or if you do not have a dmcl.ini file, you will be prompted to enter thename of the Documentum connection broker you want to use in the DocumentumConfiguration 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 anavailable repository. If you overwrite the current dmcl.ini, you will be overwritingyour current connection broker entries.

Note: Sometimes there is a conflict with installed dmcl.ini files. Some applicationsinstall the dmcl.ini file in the Windows directory, others in the Documentumdirectory. Make sure you have only one dmcl.ini file and that it is referencing thecorrect 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 theinstallation 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 serverinstallation, the installer locates the file regsvr32.exe on the host machine usingthe windows path variable. This file is used to register the Content Services forSAP dynamic-link libraries (DLL) and ActiveX Controls (OCX). regsvr32.exeusually exists in the directory C:\WINDOWS\system32. If the installer cannot findregsvr32.exe in the windows path, the following error message will display:



Unable to launch regsvr32.exe. Please copy regsvr32.exe in the windowspath. For more information please refer to install guide.

If you get this message, please copy regsvr32.exe to the directory where youdownloaded the installation files, ..\Content_Services_sap\server.

18. Click OK.An Information dialog displays asking you to make changes in the Internet ServicesManager after you finish this installation. Please refer to Configuring and startingWebAdmin, page 38 for more information.

19. Click OK.The Setup Complete dialog appears.

20. Click Finish.The Content Services for SAP Server is installed.

Conguring the repository for Content Services for SAP

Configuring the repository for Content Services for SAP will set up the required cabinetand folder structure in the repository.

To congure the repository for Content Services for SAP:

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.TheWelcome dialog appears


4. Select Docbase Configuration from the list.


6. Check the radio button appropriate to the SAP version that you are running.If you are upgrading, please refer to Upgrading Content Services for SAP, page29 for more information. The custom.xml option is for writing XML code tochange the configuration objects internal to Content Services. If you are creating acustom.xml install and are not familiar with XML or SAP BAPIs please contact yourDocumentum partner or consultant.

Note: Running multiple SAP versions with one Content Services repository mayresult in configured queries that do not execute.



7. Click Next.The Docbase Login Parameters dialog appears.

8. Fill in the following information:

a. Type the repository name.Make sure your repository is running.

b. Type the repository user name (must be dm_doclink_sap or dm_doclink_sapworkaround user ID).

c. Type the repository user password that you created in the Pre-installation tasks.

d. Type a domain, if required.Consult you network administrator for the correct domain name.

e. Click Next.The Configure Docbase dialog appears.

9. Click Next.The repository structure is created. This may take several minutes.The repository will be configured. An SAP cabinet is created in the repository tohold archived objects. This is a user cabinet for SAP content. A DocLink folder iscreated under the System cabinet in the repository to hold Content Services systemobjects. The DocLink folder is for administrators and contains a Documentum folderand an SAP folder. It is used by WebAdmin for configuration.The BAPI folder in the SAP folder is for internal use only.

10. Click OK.The repository is configured.

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 Serverregistry value must be changed on the Content Services for SAP host serverto trigger the server to use the PLM interface. Set the following registry valueto True: HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\DocLinkServer\Install\UseNewInterface > set to ‘true’.

Since SAP 4.7 no longer supports the CAD interface, Content Services for SAP 5.2.5SP1 will use the PLM interface even if UseNewInterface = false (set to false by defaultwhen 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\DocLinkServer\Install\UseNewInterface is set to ‘true’, the PLM interface on pre-SAP 4.7versions will be used when running Agent operations. When UseNewInterface =true, all Agent jobs should use PLM objects if there’s a PLM alternative available forthe specific operation being configured. Link Documentum jobs that are configuredto use the CAD interface will fail. If UseNewInterface = false, Link Documentumjobs 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 ContentServices Archive and Content Services Agent. Once the services are installed they areconfigured from the WebAdmin tool. When you have created the archive services, youwill need to change the start-up condition from Control Panel>Services. It is importantthat you use an administrator or superuser ID like dm_doclink_sap or workaround IDwhen performing these activities (particularly for the Agent service).

You can check for errors using the Event Viewer which is found in Start>Settings>ControlPanel >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.TheWelcome dialog appears

3. Click Next.The Select Type dialog appears.

4. Select Service Create from the list.


6. Check the radio button for the service that you want to create.

a. Content Services Archive (RFC) to create an RFC archive service.This service communicates with the RFC portion of SAP ArchiveLink. Thisservice must match the RFC destination name configured in SAP andWebAdminand must be started by the user ID which has access to the shared or mounteddrive.

b. Content Services Agent to create an SAP Agent service.



This service is responsible for the replication and linking of SAP objects viaBAPIs. This service uses the dm_doclink_sap inbox and must be started by thedm_doclink_sap or workaround ID.

7. Click Next.The Content Services Agent Service Parameters dialog appears.

8. 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).Consult your network administrator for the correct domain name.

9. Click Next.The Ready to Create Services dialog appears.

10. Check the details and click Next.The Services to be created section displays the service you selected in step 7. In thiscase we selected Content Services Agent.If you selected Archive (RFC) then an Information dialog appears with a warningsince you must make sure that the RFC destination name is identical in SAP,WebAdmin, and Services. You must also use the correct ID for drive sharing beforeyou start the Windows processes after you finish this installation.You must use caution when specifying domain names for the Archive services ifthe share drive is in use, especially if SAP and the Content Services server are indifferent domains. Please refer to Starting Agent and RFC processes on Windows ,page 47 for more information.

11. Click OK.The Windows Services are created.A dialog asks you whether you want to create another service. If you click Yes, youare returned to the Select Components page. If you click No, you are forwarded tothe Finish dialog.

12. Click Finish.The following services will be started.• eConnector Agent• eConnector Archive Handler• eConnector Server Handler



Changing the RFC start-up condition

You may need to modify settings in the Control Panel>Services Installed dialog toensure that a shared directory required by RFC ArchiveLink is mapped or mounted.You may use a batch file or script to map the shared drive prior to starting the Archiveservices.

For the agent process this is not required as long as the Agent service was installedby dm_doclink_sap or its OS ID.

To change the start-up condition:Because the ArchiveLink RFC processes need a shared directory, you must map anetwork drive from the SAP server. In UNIX, use NFS mount or you may need thirdparty software if you are operating in an environment with a “mix” of Windows andUNIX operating systems.

1. Provide a user name and a password to connect to the SAP server to get access tothe shared drive.To read and write to this shared drive, both ArchiveLink services must run underthe same user to which the shared drive is mapped. When using Windows Domainusers, make sure the drive is accessible for the Service user. It is possible to use localusers on each system, in which case the username and password have to be identical.

2. From the Control Panel, choose Administrative Tools > Services.

3. Right-click each archive service (Handler and Server) and then choose Properties.

4. Select Properties, then go to the Log On tab.The Service dialog appears.

5. In the Log On As section:

a. Check the This Account radio button.

b. Set the user name to the shared drive user name.

c. Set the password and confirm it.For example, the shared drive is mapped as user "sapshare". You specify the user"sapshare" with the corresponding password.You must also create an OS User for "sapshare,” and check the User CannotChange Password and Password Never Expires boxes.

6. Click OK.The next stage is to configure and start WebAdmin before testing the installation bytesting an SAP query. See Testing the installation using WebAdmin, page 67.



Conguring and starting WebAdminWebAdmin is configured and started from Windows Internet Service Manager (ISM).

To congure and start Web Admin:

1. Launch ISM via Start > Settings > Control Panel >Administrative Tools >InternetService Manager.

2. In the IIS window that is launched when you start ISM, select the Default WebSite\Content Services\Archive folder.

3. Right-click the Archive folder and choose Properties.The Archive Properties dialog appears.

4. Ensure that the Read, Log Access, and Index This Directory check boxes areselected. Ensure the Execute radio button is selected.

5. Click Configuration.The Application Configuration dialog appears.

6. In the Application Configuration dialog, select the .asp line and click Edit.The Add/Edit Application Extension Mapping dialog appears.

a. Select Limit to: and type GET, POST,PUT.

7. Click OK to close the Add/Edit Application Extension Mapping dialog.The results of the editing appear in the Application Configuration dialog.

8. Click OK in the Archive Properties dialog.

9. Exit IIS.

10. In Windows Explorer, navigate to ...\wwwroot\Content Services\Archive\temp.

11. Right-click on the temp folder and select Properties.The Properties dialog appears.

12. Select the Security tab and click Permissions.The Directory Permissions dialog appears.

13. Select all items in the Group or user names: area.

14. In the Permissions for Administrators area, select Full Control.

15. If you’re running Windows 2003, skip this step and go to Step 16. If you’rerunning Windows 2000, select the Replace Permissions on Existing Files or Allowinheritable permissions from parent... checkbox.

16. Click Advanced.The Advanced Security Settings dialog box displays.



17. Select the following checkboxes.• Allow inheritable permissions from parent to propogate ....• Replace permission entries on all child objects with entries shown here ....

18. Click OK.

19. Click Yes in the Security dialog that appears.During IIS installation, default values are set for the various properties assigned to Websites. Properties can be set at the global level, affecting all Web sites on a server, on theindividual site level, at the directory level, or at the file level. IIS uses an inheritancemodel, which means that settings on higher levels are automatically inherited by lowerlevels. Settings at lower levels can be edited individually to override inherited settingsfrom the next level up.

If you change a setting at a lower level, then later change a setting at a higher level thatconflicts with the lower level setting, you will be prompted to choose whether you wantto change the lower-level setting to match the new higher-level setting.

Conguring IIS for WebAdmin on Windows2003

If you’re installing Content Services for SAP Server on a Windows 2003 host server, youmust configure IIS for WebAdmin as described below.

Note: IIS Manager is not installed with the Windows 2003 Server operating system bydefault. Furthermore, when you initially install IIS, it is installed in “locked” mode. Ifyou 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.

To congure 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. Select the Allow button.



Removing Content Services for SAP Windowsservices

This procedure is used to clean up in case you made a mistake in the repository nameor RFC Destination, before changing Agent services or before uninstalling previousversions of Content Services for SAP.

Note: You can determine the existing repository or RFC Destination Name by looking atWindows Services in Administrative Tools.

Ensure that you stop the services you want to remove before running the uninstaller.

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.



4. Select Service Remove from the list.


6. Select the radio button of the component that you want to remove.

7. Click Next.The Docbase to Remove dialog appears.

8. Type the repository name and click Next.

9. If the service being removed is RFC ArchiveLink, type the SAP RFC destinationand click Next.A confirmation dialog appears.

10. Click Next.The service is removed. A dialog appears.If you want to remove another service, click Yes. If you click No, you will beforwarded to the Finish dialog.

11. Click Finish.



Installing Content Services for SAP on UNIXsystems

At this time, Agent services run on Windows only. The following procedure is onlyfor installation of RFC Archive services.

Complete the following tasks to install Content Services Archive on a UNIX system:

• Copying the software to the local machine, page 41• Installing the archive, page 41• Configuring the archive, page 43

Copying the software to the local machine

The software is distributed in a compressed TAR archive created with the standard UNIXtar and compress utilities. Download the software from the Subscribenet site to yourserver where the Content Services Archive software will be installed.

This URL will take you to the download center login page where you can download thelatest version of Content Services for SAP: https://documentum.subscribenet.com. Yourdefault login ID is your e-mail address. If you cannot locate your password, please usethe password finder at the bottom of the login page.

Note: Make sure the folder in which you unzip the release does not have any of thefollowing special characters: ! \ / : * ? " < > |. For example, if the full path to the installer isC:\Downloads\!Documentum\NewRelease\ Content_Services_sap\server\setup.exe,the installation may fail because of the ! in the folder name.

Installing the archive

We recommend you install the software in the Documentum Content Server installationdirectory tree under the Documentum Administrator UNIX account.

To install the archive:

1. Connect to your UNIX server as the standard Documentum repository administrator(dmadmin).

2. Create a directory under the /home/dmadmin directory, and name it “dmal”(Documentum Content Services Archive).

Note: /home/dmadmin is the root of the Documentum Content Server installation.




3. Copy the installation file from the /Content_Services_sap/Server/UNIX_os folder onthe Subscribenet site to the /home/dmadmin/dmal directory.This file is named:• dmalsunXX.tar.Z for Sun Solaris systems• dmalhpXX.tar.Z for HP-UX systemswhere XX is the version number of the software.For example, the installation file for Content Services Archive for Sun Solaris,version 4.0 is located in:.../Content_Services_sap/Server/Solaris/dmalsun40b.tar.Z

Note: If you use FTP make sure you transfer the files in binary mode.

4. Uncompress the file.• Use the following command for Solaris:

uncompress dmalsunXX.tar

• Use the following command for HP-UX:uncompress dmalhpXX.tar.Z

5. Unpack the installation file.• Use the following command for Solaris:

tar -xvf dmalsunXX.tar

• Use the following command for HP-UX:tar xvf dmalhpXX.tar

The following files are unpacked:

Table 2-2. Unpacked les

File name Description

dmarchivelink ArchiveLink Request Handler program

dmcl.ini Sample dmcl.ini

sapinfo Program to test the SAP RFC connection

dmal.ini Sample Content Services Archiveconfiguration file

alfilter Sample filter that extracts the first text lineof a Print list

alfilter.cpp Source code of sample filter

alf2html PDF/HTML filter



Conguring the archive

You must configure the Content Services Archive software for UNIX systems afteryou have copied the software to the installation directory and unpacked it. You mustconfigure two files in the Content Services Archive installation directory:

• dmal.ini• dmcl.ini

Conguring Trusted Login

The Dmal.ini file is optional on UNIX under certain conditions. If it is not configured, theprocess uses trusted login to connect to the repository. This is the preferred method if youdo not want to store the password in a file in plain text.

Trusted login can be used when the Content Services Archive software runs on thesame server platform as the Documentum Content Server. Use the UNIX account thatcorresponds to a Documentum user configured in the repository.

The UNIX user needs the privileges to read and write to the spool directories configuredfor each Archive. In Documentum, the Content Services Archive user does not needspecial privileges. The user must be able to read the configuration objects in the Systemcabinet and to create documents in the configured folders that correspond to an Archive.

The configuration file dmal.ini may be located in the installation and run-directory ofthe Content Services Archive dmarchivelink program. It may also be located in thedirectory defined by the environment variable $DOCUMENTUM. The dmal.ini filecontains configuration information that allows the Content Services Archive program toconnect to the repository. All other configuration information is stored in the repositoryin special repository objects.

Edit dmal.ini to add the required parameters:

• [Docbase\Docbase name]: Enter repository name here. You may have entries forseveral repositories.

• [Docbase\Docbase name\RFC destination name] The RFC destination name is theRFC destination name configured in WebAdmin. RFC destination name must beidentical in three locations (Windows service, SAP SM59, and WebAdmin) andmust also be unique. It is recommended that you use a naming convention such as<documentum_server_hostname>_<SAP_server_hostname> to meet these requirements.Refer to Configuring SAP R/3 for Content Services for SAP and Content Services for SAPUser Guide for Administrators for more details.

• docbase_user: Enter repository user under which the Content Services Archiveinterface is running. This user will be the owner of the documents created. We



recommend that you create a special repository user under which the ArchiveLinkprocesses will run.

• docbase_password: Password of the repository user. If the program runs under therepository user account on the same UNIX server, the password is not required orcan be anything (see Trusted Login). We recommend running under the repositoryuser account so the password does not have to be written down. If you use thepassword make sure the file is only readable by the user under which the program runs.

Change permissions on the dmal.ini file to make it non-readable for others:chmod 700 dmal.ini

• debug_level: Must be under [Debug]. Debugging is turned off if set to 0 or omitted.If 1 or more, debugging is switched on and debug information is written to the logfile. We recommend you set the debug level to 3 during the installation. If there aredifficulties running the software or for remote-debugging, set the level to 9 whenswitching on tracing. Switch it back to 0 if the problems have been solved, sincedebugging fills up the log files considerably.

Note: ‘#’ starts a comment up to the end of the line. No spaces are allowed in front ofa parameter or between ‘=’ and values.

Example:

# dmarchivelink configuration

[Docbase\db1\Documentum]

docbase_user=fred

docbase_password=foo.bar

[Debug]

debug_level=3

Conguring DMCL.INI

The standard Documentum client configuration file is named dmcl.ini. The minimumconfiguration required is the host name or IP address of the host running the connectionbroker. You can use the host name if it is configured in ‘/etc/hosts’ UNIX configurationfile. The dmcl.ini file may reside in the run-directory and installation directory of the



Content Services Archive software or it may also be located in a directory specified bythe environment variable $DOCUMENTUM.

Edit dmcl.ini in the Documentum Content Services Archive installation directory toconfigure the host name or IP address that runs the connection broker:

Example:

[DOCBROKER_PRIMARY]host=maverick




Chapter 3Starting Processes

OverviewThis chapter discusses how to start the processes that run Content Services.

These concepts are described in the following sections:

• Starting Agent and RFC processes on Windows , page 47• Starting RFC archive processes on UNIX, page 48

Starting Agent and RFC processes on WindowsBefore starting the RFC Archive services on a Windows server, the RFC destination namemust be identical, and unique for each repository-SAP connection, in three locations:

• Windows - RFC Archive service install• SAP RFC configuration (SM59)• Content Services WebAdmin - ArchiveLink RFC configurationIt is recommended that one of the following naming conventions be used, depending onthe intended uses of Content Services for SAP and the number of systems that will beintegrated in the development, testing and production environments:<DOCBASENAME>_<SAPSYSID_CLIENT> (ex: APINVOICE_PRD_100)<DCTMHOSTNAME>_<SAPSYSID_CLIENT> (ex: NTDCTMPRD01_PRD_100)<DCTMHOSTNAME>_<SAPHOSTNAME> (ex: NTDCTMPRD01_SAPPRD01)

Refer to Configuring SAP R/3 for Content Services for SAP to configure the SAP RFCDestination and Content Services for SAP User Guide for Administrators to configure theContent Services RFC Destination using the WebAdmin.

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 each of the services created with the Content Services Setup program.• Content Services Archive Handler <repository>/<RFC>


Starting Processes

• Content Services Archive Server <repository>/<RFC>• Content Services Agent <repository>For example, if you are using a repository named testenv, select ’Content ServicesAgent Testenv’.

Conguring logging

If the RFC Archive or Agent services encounter any errors during start up or whilerunning, there are two places where errors may be logged:

• Windows Event Viewer• <EMC Documentum-Installation-Directory>\DocLink\logThe Event Viewer can be accessed from Start > Programs > Administrative tools(Common) > Event Viewer. When you start the viewer choose both Application andSystem logs to see both types of messages. On Windows these are found under the Logmenu. Content Services errors may be classified as Source names "Content Services forSAP", "Content Services Agent", or "Service Control Manager."

RFC Archive and Agent service logs are written to a log file inC:\Documentum\DocLink\log (assuming default installation). These logfiles use the naming convention ’dmal*.log’ for the Archive services and ’dmagent*.log’for the Agent service. To change the log locations and debug levels, go to the followingregistry settings:

For RFC Archive: HKEY_LOCAL_MACHINE > SOFTWARE > Documentum > Doclink >Archive > Docbase > <repository name>@<RFC connection name>

For Agent: 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 thereare any problems and to make sure the software runs properly. Once the software runsas expected, be sure to set the debug level back to 0. If debugging is left on, log filesfill up quickly even if nothing is archived, and can eventually consume a tremendousamount of disk space.

Starting RFC archive processes on UNIXThe only Content Services services that can be run on UNIX are the RFC Archiveprocesses. The Agent service can only run on a Windows server.


Starting Processes

Before starting the Archive RFC processes on UNIX, the RFC destination name must beidentical, and unique for each repository-SAP connection, in three locations:

• dmal.ini file• SAP RFC configuration (SM59)• Content Services WebAdmin - ArchiveLink RFC configurationIt is recommended that one of the following naming conventions be used, depending onthe intended uses of Content Services for SAP and the number of systems that will beintegrated in the development, testing and production environments:<DOCBASENAME>_<SAPSYSID_CLIENT> (ex: APINVOICE_PRD_100)<DCTMHOSTNAME>_<SAPSYSID_CLIENT> (ex: NTDCTMPRD01_PRD_100)<DCTMHOSTNAME>_<SAPHOSTNAME> (ex: NTDCTMPRD01_SAPPRD01)

Refer to Configuring SAP R/3 for Content Services for SAP to configure the SAP RFCDestination and Content Services for SAP User Guide for Administrators to configure theContent Services RFC Destination using the WebAdmin.

Use the following procedure to start the required UNIX processes:

1. Log on to UNIX with the ArchiveLink user account created for the SAP ArchiveLinkconnection.

2. Start the Archive processes with the following commands:% cd /home/dmadmin/dmal

% dmarchivelink <repository_name> <SAP_system> [RFC Destination nameas configured with WebAdmin]

This starts two UNIX processes that can be verified with the UNIX ps command.

3. Verify that the Archive processes started correctly by examining the two log files:• /tmp/dmalxxxxxx.log

/tmp/dmalservxxxxxx.log

Note: The log file directory is by default /tmp but you can configure the directorywith the log_dir parameter in the dmal.ini file.

The two processes should remain running, and only the start message should bewritten in the log file. If either of the processes fails, look in the log files, or the inboxof the operator you have defined, for messages indicating the cause of failure. If oneof the processes appears to be running still, stop that process before attemptingto restart both processes again.When running the Archive processes for the first time, set the debug level inDMAL.INI to 3. This allows you to see if there are any problems and to make sure theprocesses run properly. Once the processes run as expected, set the debug level backto 0. If debugging is switched on, log files fill up quickly even if nothing is archived.


Starting Processes

The Archive Handler process is configured and running properly if the log file’/tmp/dmalxxxxxx.log’ looks like the following example (please give it time to startup):Fri Nov 15 04:20:19 1996: Starting Content Services Archive Request

Handler Version XXX

Fri Nov 15 04:20:19 1996: Docbase is serpent

>>> Connected to Docbase: serpent serpent

>>> Configuration read

>>> argv for RfcAccept:

>>> -aDMAL.RFC_PROG -g/H/204.79.199.2/H/147.204.2.232/S/3297/

H/hs8100 -xsapgw00

>>> Running RfcAccept

>>> SAP open

>>> Running RfcEnvironment

>>> Running RfcInstallFunction

>>> SAP event handler ok, entering event loop...

>>> Calling RfcDispatch...

The Archive Server process is configured and running properly if the log file '/tmp/dmalservxxxxxx.log'

looks like the following example:

Wed Nov 15 04:20:19 2000: Starting Content Services Archive Request

Server Version XXX

>>> Connected to Docbase: serpent serpent

>>> Configuration read

>>> RfcOpen hostname = /H/204.79.199.2/H/147.204.2.232/S/


Starting Processes

3297/H/hs8100

>>> system number = 0

>>> gateway = /H/204.79.199.2/H/147.204.2.232/S/3297/

H/hs8100

>>> gateway service = sapgw00

>>> client = 850

>>> user = documentum

>>> RFC connection is open

>>> Query is: select * from dmi_queue_item where

(delete_flag=0) and (name=user)

and (event like 'sap_%') order by priority DESC, date_sent

>>> Entering Docbase query loop


Starting Processes


Chapter 4Installing Print List TransformationFilters

OverviewThis chapter describe the Content Services Print list Transformation Filters. Theseconcepts are described in the following sections:

• On-demand rendering versus stored rendering, page 53• Configuring EMC Documentum Content Server for on-demand rendering, page 54.

On-demand rendering versus stored renderingIf you are planning to use Content Services for SAP to archive reports (SAP Print lists), itis possible to render the SAP proprietary Print list format (ALF) into text, HTML, andPDF renditions. There are two ways to achieve this:

• Configure the archive to generate the desired renditions when the Print list is stored• Configure the Documentum Content Server to generate a desired rendition when a

Print list is viewed, for example on-demandUsing on-demand rendering reduces the initial storage requirements needed to storereports and renditions. However, performance is reduced when viewing a report,because on-the-fly rendering occurs. On-the-fly renditions are stored in the Documentumrepository for future use.

Stored rendering refers to the usage of built-in filters to generate desired documentrenditions whena document is archived in the repository. Refer to the Specifying a built-inlter section of Content Services for SAP Administration Guide for more information onusing built-in filters for stored rendering.


Installing Print List Transformation Filters

Conguring EMC Documentum Content Serverfor on-demand rendering

To congure EMC Documentum Content Server to render ALF reports into HTML, PDF,or TXT formats:

1. Copy the transformation executable onto EMC Documentum Content Server:

a. On the installation media, locate the transformation executable.• For Windows installations, this file is called "alf2htlm.exe".• For UNIX installations, this file is called "alf2htlm".

b. Copy this file into the EMC Documentum Content Server bin directory (forexample: \Documentum\Product\5.2.5\bin)

2. Copy the transformation scripts onto EMC Documentum Content Server:

a. On the installation media, locate the transformation scripts.• For Windows installations, these are called convert_alf2pdf.bat,

convert_alf2crtext.bat, and convert_alf2html.bat.• For UNIX installations, these are called convert_alf2pdf, convert_alf2crtext,

and convert_alf2html.b. Copy these scripts into the EMC Documentum Content Server Script Convert

Directory (for example: \Documentum\Product\5.2.5\Convert\Scripts)

3. Update the convert table:The EMC Documentum Content Server Script Convert Directory (for example:\Documentum\Product\5.2.5\Convert\Scripts) contains a file called convert.tblUsing a text editor, append entries to this table to add the ALF transformations.#

# Converts SAP Printlists into open formats

#

alf2crtext sap_printlist T_t.crtext .

alf2chtml sap_printlist T_t.html .

alf2pdf sap_printlist T_t.pdf .

4. Save your changes and close the file.



The settings will now take effect. It is not necessary to restart/reinitialize the EMCDocumentum Content Server.




Chapter 5Installing Content Services for SAP ClientComponents

OverviewThis chapter describes procedures required to install the client components of ContentServices for SAP:• View• Capture• Manage


• System configuration and dependencies, page 57• User roles and client components, page 58• Installation prerequisites, page 59• Customizing installation, page 59• Installing Content Services for SAP Client Components, page 62• Postinstallation tasks, page 65

System conguration and dependenciesContent Services for SAP is an integrated suite of products that provide documentmanagement, imaging and archiving services. Services can be installed on differentphysical machines in different locations as long as the required functional componentsfor each specific service are on the same machine. The following table provides anoverview of possible system configurations and the functional component dependenciesfor each service or function:


Installing Content Services for SAP Client Components

Table 5-1. System conguration and dependencies

System configuration Functional component dependencies(must be on same physical machine)

Browser enabled viewing client - viewdocuments by selecting a link in SAP GUI

SAP GUI + View - installed with Webtopintegration

OLE viewing client - view documents byselecting a link in SAP GUI or by calling aDRL directly from the repository

SAP GUI + View

OLE viewing client - view documents bycalling a DRL directly from the repository

View

Scan and Link to SAP Capture + SAP GUI + View or WebView

SAP DMS Linking - Links Documentumdocuments to SAP equipment, material,functional location, customer, vendor,WBS element, or document info record

View + Manage

User roles and client componentsThe client components of Content Services for SAP are installed according to the role ofthe user. There are four defined roles. These are:

• Document Controller

This role covers those who release documents to SAP and maintain the links to thosedocuments. They will have access to the Manage, View, WebView, and Capturecomponents of Content Services for SAP.

• Capture Operator

This role covers users who want to scan documents into the Documentum repositoryand create links to the appropriate records in SAP. They will have access to the View,WebView, and Capture components of Content Services for SAP.

• Standard User

This role covers users who want to view documents that are archived in theEMC Documentum repository. They will have access to the View and WebViewcomponents of Content Services for SAP.

Note: The Manage component is launched directly from the View component.However, if Content Services for SAP is installed using the Standard User installationoption, the Manage menu will not be accessible.



Installation prerequisites• Windows 2000 Server, Windows 2003 Server, or Windows XP Professional.• Internet Explorer 4.x/5.x or later or Netscape 4.x is required for WebView (does

not work on Netscape 6)• SAPGUI• Each user should have user account in SAP and in the repository that’s integrated

with SAP• If a DMCL.INI is present on the client PC, make sure it’s in the WINDOWS or

WINNT directory• Content Services users should be "Power users" on the Windows operating system,

not "Restricted users". Restricted users attempting to use Content Servicescomponents will get an error indicating that the registry cannot be accessed orupdate.

Customizing installationTo change your client installation you must modify the setup.ini file. You can specifyinstall components and install directories and also the formats to be used by documenttypes. If you do not specify your requirements, the defaults will be used.

By default, the View and WebView components are installed into the SAP directory.In the past, it was typically installed into C:\DMVIEW. If you want to install intoC:\DMVIEW, you will need to edit the installer SETUP.INI file to set the entry viewdirin the [Install] section to your required directory. Alternatively, change your SAPapplication setting to remove the application path for DmView/WebView.

Similarly, if you want to change the Windows default application used to open particulardocument types (Notepad to open .TXT files for example), you will need to edit theSETUP.INI.

Document types can be customized at the client stations through the View component.

Use the setup.ini file if you want to apply the same defaults across multiple clientworkstations.

Following is an example of the setup.ini file.SETUP.INI

[Startup]

AppName=External Viewing Services for SAP



FreeDiskSpace=483

EnableLangDlg=Y

[ISUPDATE]

UpdateURL=http://

# Installer Version External Viewing Services 5.3 SP1 Docbase Version 1.2

# ------------------------------------------------------------------------------

# Section: Install

# ------------------------------------------------------------------------------

# This section allows you to specify install components and install directories

# For example, you can specify

# [Install]

# view=1

# webview=1

# viewdir=c:\dmview

# To install View and WebView into c:\dmview

# The install component settings are only used if the install is run silently

# You can run a silent install by running "setup /s"

# [Install]

# view=0 or 1

# manage=0 or 1

# webview=0 or 1

# capture=0 or 1



# archiveview=0 or 1

# targetdir=a directory

# viewdir= a directory

[Install]

# ------------------------------------------------------------------------------

# Section: Formats

# Use this section to specify format preferences for viewing specific document

# types. For example

# [Formats]

# crtext=notepad %s

# will view text files using notepad. The key name should correspond to a

# Documentum format type.

# ------------------------------------------------------------------------------

[Formats]

Upgrading Content Services for SAPIf you are upgrading your client installation, here is some information you need to know.

• You must uninstall any previous version of the View, Capture, and Managecomponents using Windows Control Panel > Add/Remove Programs.

• After you have run the uninstaller, you must navigate to the Content Services forSAP installation directories and manually delete any leftover files.

• If you moved the dmview and dmwebview files after installation, the uninstallerwill not remove those files. Be sure to remove the files before installing ContentServices for SAP.

• The Manage component is no longer dependent on the WorkSpace client. It’s nowintegrated with the View component.



• Copy the files from the CD or Documentum’s FTP site to a hard disk drive ifnecessary (see Installing Content Services for SAP Client Components, page 62.) Theinstallation files can be copied to and run from the client workstation or a sharednetwork drive.

• Run the installer for Content Services for SAP.

Note: If you are using this install program to replace an existing client installation,you may get a warning that DMAPI.EXE is still running. In this case you will needto stop this program before restarting the installation.

To stop DMAPI.EXE.

1. Use Ctrl + Alt + Delete to open the Task Manager or Close Programs window.

2. Locate and highlight the DMAPI.EXE program.

3. Click End Process or End Task.

Installing Content Services for SAP ClientComponents

To install Content Services for SAP:

1. Download and unzip the current release of Content Services for SAP installation filesto a temporary directory on your local machine.This URL will take you to the download center login page where you can downloadthe latest version of Content Services for SAP: https://documentum.subscribenet.com.Your default login ID is your e-mail address. If you cannot locate your password usethe password finder at the bottom of the login page.

Note: Make sure the folder in which you unzip the release does not haveany of the following special characters: ! \ / : * ? " < > |. For example, ifthe 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.

2. Navigate to ..\Content_Services_sap\client\setup.exe in the directory where youunzipped the release.



5. Select the client component to install.• Administration Installation




Installs the View, WebView, Capture, and Manage components of ContentServices.

• Scanning Installation

Installs the View and Capture components of Content Services.• Standard User Installation

Installs the View and WebView components of Content Services.6. Click Next.

The Choose Destination Location dialog appears.The default destination folder where the components will be installed will beC:\Program Files\Documentum\DocLink. If you want to change this, use theBrowse button to navigate to the required folder and double click on the foldername. SAP interfaces must be able to locate the View component; usually, theSAPGUI default directory is the best location. The default directory for the View,WebView and ArchivelinkView is C:\Program Files\SAPpc\sapgui, which is theresident directory for SAPGUI.

Note: ArchiveLink expects dmview/dmwebview to be found in the SAPGUIdirectory. If these programs are moved, ArchiveLink may not function as expectedfrom SAPGUI. Also, dmview and dmwebview are used by both ArchiveLink andDMS interfaces. These paths are configured separately in SAP. Unless multiplecopies of dmview exist, the path must match the path configured in both ArchiveLinkand DMS. For more information see the SAP configuration manual.

7. Click Next.

8. If you want to use Webtop as the default viewer, select the Display Using Webtopcheckbox.

9. Enter the URL to your Webtop installation. The convention for the Webtop URL ishttp://<localhost>: <port number>/webtop/component/drl, where• <localhost> is the name of the host on which the Webtop installation is running,

and• <port number> is the appropriate number.

10. When prompted, test the Webtop URL in a browser to ensure it is functional. Youshould see a Webtop login screen when you paste the Webtop URL into the Addressfield of your browser. If you do not see the Webtop login screen, consult yournetwork or Webtop administrator for a valid Webtop URL.

11. The Configure WebTop dialog appears. If you want to install Acrobat annotationssupport, click Yes; otherwise click No.The Start Copying Files dialog appears, displaying the settings that you have chosen.

12. Click Next.

13. The files are copied and the installation is completed.



The Setup Complete dialog appears.

14. Click Finish.

Conguring the View component for Webtop

To congure the View component so that you can view and edit content using Webtop:

1. Install Content Services for SAP.

2. Launch the View client via Start > Programs > Documentum eConnector for SAP> View.

3. Select Edit > Preferences. You’ll be prompted to log on to a repository. Select therepository configured for Content Services for SAP.

4. Select a document format type, for example Microsoft Word or FOLDER (at theend of the list).

5. Select the View Using Webtop radio button.

6. Click Apply.

Silent Installation

You may want to roll out a particular client install across several workstations. This iswhat is known as a "silent" install. One important requirement is that the installationis identical from workstation to workstation. For example, if the installer detects a fileand displays a dialog, you must ensure that the same file is detected on all workstationsusing that silent install file (ex: DMCL.INI). If not, the order of, and perhaps responsesto, the dialogs will change.

To run a silent installation:

1. Firstly, make sure no previous installation exists.

2. Before you start, end the dmapi.exe process from the Task Manager or ClosePrograms window (use Ctrl + Alt + Delete to open the window).

3. Run a sample installation with the following command line option:"setup -r".

This creates an installation script in the windows directory (C:\WINNT orC:\WINDOWS). The name of the script is "setup.iss". Make sure the client machinesare identical to the recording machine. For instance, if you know that the clientmachines where the silent install will be performed do not have a dmcl.ini file, then



you should not have a dmcl.ini file on the machine where you are creating therecording file. The environment should be exactly the same. If the environments arenot the same you will get resultcode=-12 in the setup.log, which means the dialogorder has changed.This file records the installation dialogs, so don’t hit back buttons. Whatever optionsare chosen (for example the docbroker) will be used during all the silent installs. Youcan open the file & look at the options.

4. Copy "setup.iss" into the setup kit (from where you run "setup.exe").

5. To test on the same machine, end the dmapi.exe process and uninstall any clientsoftware. Run silent installer: Run "setup -s".Other meaningful result codes in the log file include:• 0 Success.• -1 General error.• -2 Invalid mode.• -3 Required data not found in the Setup.iss file.• -4 Not enough memory available.• -5 File does not exist.• -6 Cannot write to the response file.• -7 Unable to write to the log file.• -8 Invalid path to the InstallShield Silent response file.• -9 Not a valid list type (string or number).• -10 Data type is invalid.• -11 Unknown error during setup.• -12 Dialog boxes are out of order.• -51 Cannot create the specified folder.• -52 Cannot access the specified file or folder.• -53 Invalid option selected.

Postinstallation tasks• Using Doclink Capture



Doclink capture must be run as a superuser once to make sure all config objects areupgraded to the current release/version of SAP.


Chapter 6Testing the Installation

OverviewThis chapter discusses how to test the installed components.


• Testing the installation using WebAdmin, page 67• Testing an RFC archive installation, page 71

Testing the installation using WebAdminThe WebAdmin tool is used to set up and run an SAP query in order to test theSAP connection. See the User Guide for Administrators manual supplied with yourinstallation for full details on using the WebAdmin tool.

To test the installation using WebAdmin, you must perform the following tasks:

1. Ensuring that the Prerequisites for testing the installation, page 68 are met.

2. Connecting to WebAdmin, page 68

3. Configuring the SAP server, page 69

4. Configuring an SAP user, page 69

5. Creating an SAP query, page 70

6. Testing an SAP query, page 70


Testing the Installation

Prerequisites for testing the installation

Table 6-1. Prerequisites for testing the installation

Prerequisite Details

Content Services You must have completed all thepreceding installation stages.

SAP You must have completed the DMSconfiguration tasks in Configuring SAP R/3for Content Services for SAP.

WebAdmin Complete the SAP Server and SAP Userconfigurations. Refer to Configuring anSAP user, page 69and Creating an SAPquery, page 70.

Connecting to WebAdmin

To connect to the WebAdmin tool:

1. Choose Start>Programs>Documentum Content Services for SAP>Administrator oropen you browser and enter the URL for the WebAdmin tool.• From the WebAdmin server, the URL is http://localhost/Content

Services/Administrator• From a remote location, the URL is http://<webadmin_hostname>/Content

Services/Administrator

Where [WebAdmin server] is the name of the Microsoft Internet InformationServer (IIS) which has been configured for Content Services WebAdmin.

The Login dialog appears.

2. Select the repository.This will be the repository you configured for Content Services for SAP.

3. Enter the repository user name dm_doclink_sap and the password. dm_doclink_sapis the Content Services for SAP administrative superuser account that should alwaysbe used for making configurations changes in the WebAdmin.

Note: If this user account has been created with an alternate OS user name, enter theOS name here (which serves as an alias for dm_doclink_sap).

4. Enter the Windows domain name if required. Consult you network administratorfor the correct domain name.



5. Choose the required language from the drop-down list.

6. Click Log in.The Content Services for SAP-WebAdmin/Documentum window appears.

Conguring the SAP server

To create the SAP server conguration:

1. Select SAP® on the left panel and the Server tab in the right panel.

2. From the Choose a Server: drop-down list select Default Server.The SAP Server window displays.

3. Enter the host name or IP Address for the server.The entry you use depends on the capability of your network to resolve IP addressesto domain names.

4. Enter the SAP System Name and SAP System Number in the appropriate fields.

5. Click the Save button.If the System Number began with 0, the leading 0 will not display after saving. Thiswill not cause any problems.

Note: Most of the SAP SERVER and SAP USER information can be obtained bylaunching SAP logon for the SAPGUI, selecting the correct SAP server, then selectingthe properties button.

Conguring an SAP user

To congure an SAP user:

1. Select SAP® on the left panel and the User tab in the right panel.

2. Select Default User from the Choose a User: drop-down list.The SAP User Configuration window appears.

3. Enter a password for the user.

4. Enter the SAP Client Number if required.

5. Choose the language from the drop-down list.

6. Click the Save button.



Note: Most of the SAP SERVER and SAP USER information can be obtained bylaunching SAPlogon for the SAPGUI, selecting the correct SAP server, then selectingthe properties button.

Creating an SAP query

Use the following procedure to create a query:

1. Select SAP® on the left panel and the Query tab in the right panel.

2. From the Query Type drop-down list, choose Equipment by short text.

3. From the Choose a Query drop-down list, choose Create a new configuration.

4. In New Query’s Name, enter Select ALL.

5. In Condition Composer select Description and enter the parameter *, as follows:Description=*

6. Click the down arrow to add the rule to the Query Conditions field.

7. Click the Save button.

Testing an SAP query

To test the query:

1. Choose Default Server from the Test on: drop-down list.

2. Choose Default User from the as: drop-down list.

3. Enter 10 in theMax Records: field.

4. Click the Test button.If the connection is made, you will see a list of SAP data. If the connection fails,review your settings in WebAdmin for SAP Server and SAP User. Make sure thatthey identically match the settings used to connect to SAP via a SAPGUI logonsession. Also ensure that the minimum configuration steps were carried out forSAP DMS.



Testing an RFC archive installationUse the following procedure to validate the installation:

1. Before the Archive Server and Handler services are started for the first time, switchon debugging by setting the debug level in the registry or dmal.ini file to 3.

2. Restart your services to initiate new log files.

3. Start SAPGUI and connect to your R/3 system.

4. Type /nsm59 into the command field.A new window appears, listing the folder hierarchy.

5. Double click on the plus symbol in front of the folder labeled TCP/IP Connections.A new window appears, displaying a list of all RFC Destinations.

6. Double click on the RFC destination created for Content Services for SAP.

7. Click on Test Connection.

a. If the connection passes, a message appears on the status bar, stating that theconnection is OK.A new window appears, displaying some performance figures.

b. Verify the connection further by checking the log files.The following entries should appear in the UNIX log file ’/tmp/dmalxxxxxx.log’or the Windows ’\Documentum\Doclink\log\dmal*.log’::>>> SAP open>>> Running RfcEnvironment>>> Running RfcInstallFunction>>> SAP event handler ok, entering event loop...>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...:

c. If the connection fails, check the following:• The Archive Handler and Archive Server services are running.• If installed on Windows - the Log On As user account and password in both

the Archive Handler and Archive Server service startup Properties matchthe SAP user account created for Content Services Archive.

• If installed on UNIX the user account and password in the dmal.ini filematch the SAP user account created for Content Services Archive.



• The RFC Destination Name used to install the Content Services ArchiveHandler and Server services exactly matches the RFC Destination Nameconfigured in SAP.

• The RFC Destination Name and Program ID configured in the WebAdmin> ArchiveLink > RFC Destination is in uppercase, and exactly matches theRFC Destination Name configured in SAP.


Chapter 7Troubleshooting Installation Issues

OverviewThis chapter contains the following topics:• Troubleshooting IIS-related issues, page 73• Correcting SAP queries (BAPI configuration), page 74

Troubleshooting IIS-related issuesCommon IIS problems include lack of security rights, a minimal IIS install which didn’tinclude the Windows Scripting Host, inaccurate anonymous logon configuration, orpossible firewall issues.

If you get an error instead of a page of HTML code, use the following troubleshooting steps:

1. Launch the Internet Services Manager and navigate to <hostname>/Default WebSite/Content Services.

2. Select Content Services, then right-click and select Properties.

3. Go to the Directory Security tab and select the Edit button next to AnonymousAccess.

4. In the Authentication Methods window, make sure Anonymous Access is checked,and then select the Edit button next to Anonymous Access. Selecting any of theAuthenticated Access options can create problems.

5. You should only be using Anonymous Access with the Anonymous user calledIUSR_<hostname>. If a different username is entered, change it.

6. If you get a 408/409 error, most likely the IIS VB scripting option ’Windows ScriptingHost’ is not installed. Run the IIS installation again and select the Windows ScriptingHost installation option.

7. Finally, work with the Intranet IT group to resolve any firewall issues preventingthe Content Services host server from communicating with either the DocumentumContent host server or the SAP host server.


Troubleshooting Installation Issues

Correcting SAP queries (BAPI conguration)Frequently, the matchcode strings for SAP Queries change from SAP version to SAPversion. In some cases we have found they have changed from hotpack to hotpackwithin a version. For instance the matchcode types for Material queries may not beconsistent between 4.6B and 4.6C. If you have configured your repository for the correctSAP version using the Content Services for SAP Server installer and you have difficultiesrunning SAP queries successfully for some objects, you may need to make a manualmodification to the BAPI configuration object in the repository.

The symptoms are as follows:

Running an SAP query fromWebadmin or Manage produces an error message similar tothe following:Illegal query class: Functional Location Cannot execute queryclass 'SAP' with query name 'Functional Location by text'.Function 'QUERY_EXEC' did not execute.

where, for example, Functional Location was configured by your installer in yourrepository under /System/DocLink/SAP/BAPI/.

Follow these steps to manually modify the BAPI conguration object in the repository:

1. Launch the Documentum client and log on to the SAP configured repository.

2. Locate the BAPI configuration object under /System/DocLink/SAP/BAPI/. There maybe several objects with similar names. Select the object of type sap_query_type_cad.For example: Functional location by text.

3. Open the attributes/properties for the BAPI configuration object.

4. Note the attribute entry for Matchcode Type:. This must exactly match the SAPquery listed on the search tab for that SAP object.For example: Matchcode Type: Text (= Description)

5. Launch the SAP GUI and navigate to the SAP object display window for the querytype in question.For example: Go to SAP Transaction IL03 - Display Functional Location: Initial screen

6. Open the SAP object search window and navigate through the search criteria tabsuntil the Matchcode Type entered in the repository BAPI configuration object islocated.For example: Place the cursor in the FunctLocation field and select the Search icon atthe right of the field, then use the arrows in the search window to navigate throughthe tabs. Note the tab labeled "Text (=Description)" in the image below.

7. Compare the SAPMatchcode on the search tab to the BAPI Matchcode Type attributein the repository. These must match in order for the query to run successfully. If



they’re different, edit the repository BAPI Matchcode Type attribute to make itidentical to the SAP Matchcode.

8. Save the BAPI configuration object in the repository.

9. Re-run the SAP query for the Content Services WebAdmin.

SAP 4.6b BAPI workaround for German language

If you are using the SAP 4.6B in the German language (DE) and are testing the queriesfor Material by description (DE), you must use the settings described below in order toavoid an error similar to the following:Illegal query class: Material zur Bezeichnung Cannot executequery class 'SAP' with query name 'Pumpen'. Function'QUERY_EXEC' did not execute.

Change the matchcode_type attribute entry to:Materialnummer/-kurztext




Chapter 8Uninstalling Content Services for SAP

OverviewThis chapter describes procedures required to uninstall the server and client componentsof Content Services for SAP from a Windows machine.

These concepts are described in the following section:

• Uninstalling Content Services for SAP server components, page 77• Uninstalling Content Services for SAP client components, page 79

Note: Uninstalling does not remove folders and files that were created after theinitial installation. Uninstalling does not remove cabinets, folders, or data from theDocumentum Content server. This task can be accomplished manually if desired.

Uninstalling Content Services for SAP servercomponents

Note: The operation of uninstalling Content Services for SAP is not recommended fora production repository. It’s included here for test and development activities thatrequire a refreshed repository.

Use the following steps to uninstall a previous version of Content Services for SAP fromthe Windows Content Services for SAP host server.

Proceed as follows:

1. Verify that no pending jobs or requests remain in the queues.

2. Check the Content Services scheduled jobs using the WebAdmin. If there arejobs scheduled to run during the time the uninstall and reinstall will take place,deactivate them.

3. Stop all Content Services Archive and Agent services.

4. Stop the IIS Admin Service and World Wide Web Publishing Service.

5. Uninstall the Content Services Archive and Agent services. See Removing ContentServices for SAP Windows services, page 40.


Uninstalling Content Services for SAP

6. Remove the Content Services for SAP Server software using the instructions inRemoving the Content Services for SAP software, page 78.

7. If the uninstall is to include Content Services configuration objects or SAP linkedobjects located in the repository, use the instructions in Deleting default SAPconfiguration information or data, page 78.

8. Reinstall Content Services for SAP using the instructions in Chapter 2, InstallingContent Services for SAP Server Components.

9. Reactivate any Content Services scheduled jobs that were deactivated before theuninstall began. Please note that deleting the SAP configuration information or datafrom the repository will deleted these scheduled jobs.

Removing the Content Services for SAP software

Proceed as follows to remove the Content Services for SAP software:

1. Log in as a member of the administrator group to the Windows server whereContent Services for SAP is installed.

2. From the Control Panel, use Add/Remove Programs and select DocumentumContent Services for SAP Server Components.

3. Click Remove.

4. Check to see whether the Documentum\DocLink directory still exists. If so, deletethe DocLink directory.

5. Open REGEDIT, navigate to HKEY_LOCAL_MACHINE> SOFTWARE>Documentum, and delete the following registry keys: Doclink, Doclink Server, andDocumentum Content Services for SAP (server).

6. Shut down and restart the computer.This procedure only deletes programs. To remove the Content Services Archive andAgent services see Removing Content Services for SAP Windows services, page 40.To remove the Content Services configuration objects or SAP linked objects from therepository, use the instructions in Deleting default SAP configuration informationor data, page 78.

Deleting default SAP conguration information or dataNote: This operation is not recommended for a production repository. It’s included herefor test and development activities that require a refreshed repository. If deletion willinclude objects that are linked to SAP, the links must be removed from both SAP and therepository before deleting those objects. Not doing so will cause corruption of the SAP



and/or Documentum databases. The procedures for removing links varies according tothe type of link and the SAP interface used (Incoming documents, Outgoing documents,Print Lists, Data Archiving, Automated linking, Document Management linking).

Proceed as follows:

1. Log into the repository as the dm_doclink_sap user ID or work-around alias ID.When logging in to the repository, use the OS user name “tuser1”. The system willautomatically translate “tuser1” into dm_doclink_sap user internally.

2. Delete the cabinet “SAP” (where the example data is stored).

3. Locate and delete any other locations where SAP data has been stored. (SAP datacan be stored outside of the SAP cabinet. The SAP cabinet is just the locationrecommended by the default configurations.)

4. Delete the folder under the System cabinet called "Doclink" (where all of the SAPWebAdmin configurations are stored).

Uninstalling Content Services for SAP clientcomponents

First, you must "release" any existing programs from use, or you will receive errorsindicating that files are in use. This is done by stopping the dmapi.exe process.

To stop DMAPI.EXE:

1. Press Ctrl + Alt + Delete to open the Task Manager or Close Programs window.

2. Locate and highlight the DMAPI.EXE program.

3. Click End Process or End Task.

To remove Content Services for SAP:

1. Log in as a member of the administrator group to the machine where ContentServices for SAP is installed.

2. From the Control Panel, use Add/Remove Programs and select Content Servicesfor SAP.

3. Click Remove.

4. Check to see that dmview.exe and dmwebview.exe were removed from the SAPGUIdirectory (default location is C:\Program Files\SAPpc\SapGui). This is the defaultinstallation directory for DmView and DmWebView.



Note: If these files have been copied or moved to another directory they must beremoved manually.

The references should now be deleted from the Start > Programsmenu.

5. Shut down and restart your computer.


Index

Aadministration installation, 62Administrative Console, 15Agent services, 15, 27ALF class, 16ALF format, 16archived data, 16Archiving Server, 14

BBAPI, 34, 74

Ccapture operator, 7, 58changing agent services, 40class

ALF, 16FAX, 16OTF, 16REO, 16

configuration procedures, 44configuring, 33, 38connecting, 68connection broker, 44Content Services, 35, 38, 40 to 43, 49Content Services for SAP

defined, 13Content Services for SAP administrator, 7create, 35, 70creating links, 7

DDB2, 7DCML.INI, 32default application, 59destination folder, 63directory for SAPGUI, 63

dmal directory, 41dmal.ini file, 42, 49dmarchivelink program, 42dmcl.ini file, 42, 44document, 59

incoming, 16outgoing, 16scanned, 16supported formats in SAP, 16

document controller, 7, 58document formats, supported in SAP, 16

Eerrors, 35event viewer, 35

FFAX class, 16format

ALF, 16PDF, 16REO, 16Tiff, 16

format preferences, 59

Hhost name, 32

Iinstall, 41 to 42, 57, 59, 62 to 63intended audience, 7IP address, 32

Mmaintaining links, 7


Index

OOracle, 7OTF class, 16

PPDF format, 16prerequisites, 67

system administrator, 7Print Lists, 16

ALF class, 16ALF format, 16

properties, 38

Rreleasing documents to SAP, 7remove, 40REO class, 16REO format, 16Reports, see Print Listsrequest handler program, 42

SSAP, 34, 67, 74

supported document formats in, 16SAPGUI, 63SAPINFO, 42scanning documents, 7scanning installation, 63shared directory, 37SQL Server, 7standard, 58, 63standard user, 7start-up condition, 35

starting, 38supported databases, 7

DB2, 7Oracle, 7SQL Server, 7Sybase, 7

supported document formats in SAP, 16ALF class, 16ALF format, 16FAX class, 16OTF class, 16PDF format, 16REO class, 16REO format, 16Tiff format, 16

Sybase, 7system administrator, 7

prerequisites, 7

Ttesting

installation, 67the SAP connection, 67

Tiff format, 16

Uuninstall, 77user roles, 7

WWebAdmin, 15, 35, 38, 67 to 68WebView, 59
