EMC Documentum ArchiveServicesforSAP · PDF file(SAP) ArchiveServicesforSAP AdministrationGuide Describeshowtoconfigure ArchiveServicesusingthe WebAdmintool. ArchiveServices Administrator

EMC® Documentum®

Archive Services for SAPVersion 6.0

Installation GuideP/N 300005491 Rev A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748‑91031‑508‑435‑1000www.EMC.com

Copyright © 2004 ‑ 2007 EMC Corporation. All rights reserved.

Published September 2007

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up‑to‑date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Table of Contents

Preface ........................................................................................................................... 9

Chapter 1 Introducing Archive Services for SAP ................................................... 13Overview ................................................................................................... 13Archive Services for SAP architecture .......................................................... 14Supported SAP document formats............................................................... 15SAP and Archive Services for SAP terms ...................................................... 15

Chapter 2 Installing Archive Services for SAP ....................................................... 19Overview ................................................................................................... 19Installation scenarios .................................................................................. 19All‑in‑one installation ............................................................................. 20Separate Archive Services ....................................................................... 20Integration with EMC Centera................................................................. 20Advanced scalability options for Tomcat server ........................................ 20

Installation prerequisites ............................................................................. 21General prerequisites .............................................................................. 21Software prerequisites ............................................................................ 21

Preinstallation tasks .................................................................................... 21Installing databases ................................................................................ 22Preparing EMC Documentum Content Server .......................................... 22Installing Content Server..................................................................... 22Configuring Content Server ................................................................ 23

Preparing the repository ......................................................................... 24Creating connections to EMC Centera ...................................................... 24Preparing the application server host ....................................................... 24Ensuring sufficient temporary disk space on the host ............................ 25Ensuring the Java heap size is sufficient ............................................... 25Supported operating systems and application servers ........................... 25

Preparing the application server software................................................. 25Preparing Tomcat ............................................................................... 26Overview ....................................................................................... 26Installing Tomcat ............................................................................ 26Verifying Apache Tomcat ................................................................ 27Configuring Tomcat in UNIX .......................................................... 27Configuring HP‑UX to run Java server in productionmode ......................................................................................... 27

Preparing BEAWebLogic.................................................................... 27Preparing IBMWebSphere .................................................................. 29Preparing Sun Java System Application Server ..................................... 29

Obtaining the latest copy of the product from the DocumentumDownload Center ................................................................................... 30

Installing Archive Services for SAP .............................................................. 30Installing the EI Core docapp file ............................................................. 31Preparing the assap.war file .................................................................... 31

EMC Documentum Archive Services for SAP Version 6.0 Installation Guide 3

Table of Contents

Deploying the assap.war file ................................................................... 32Deploying assap.war using Apache Tomcat.......................................... 32Deploying assap.war using BEAWebLogic .......................................... 33Deploying assap.war using IBMWebSphere......................................... 34ClassLoader Setting ........................................................................ 35

Significant system objects........................................................................ 35dfc.properties ..................................................................................... 36log4j.properties .................................................................................. 36docbases.properties ............................................................................ 36al.properties ....................................................................................... 36

Installing RFC archiving services ................................................................. 37Installing RFC components on Windows.................................................. 37Overview ........................................................................................... 37Installing RFC components ................................................................. 37Creating RFC services ......................................................................... 38

Installing RFC components on UNIX ....................................................... 39Installing the archive .......................................................................... 39Configuring RFC archiving services..................................................... 40Overview ....................................................................................... 40Configuring trusted login................................................................ 40Example:.................................................................................... 42

Configuring dfc.properties .............................................................. 42Example:.................................................................................... 42

Postinstallation configuration ...................................................................... 42Configuring RFC services........................................................................ 43Overview ........................................................................................... 43Configuring RFC Windows services..................................................... 43Configuring RFC UNIX processes........................................................ 44Configuring logging ........................................................................... 47

Configuring the temporary store ............................................................. 47Customizing the dfc.properties file for optimum performance................... 48

Chapter 3 Upgrading Archive Services for SAP ..................................................... 51Overview ................................................................................................... 51Upgrading from Archive Services for SAP 5.3 SPx ........................................ 51Upgrading from Content Services for SAP – Archiving Server 5.3 .................. 52Upgrading RFC archiving services............................................................... 52

Chapter 4 Testing the Installation .......................................................................... 55Overview ................................................................................................... 55Setting up repository connections ................................................................ 55Displaying configured repository connections .............................................. 56Defining an ArchiveID in WebAdmin .......................................................... 56Defining a logical ArchiveID in SAP ............................................................ 58Testing connection between SAP and Archive Services.................................. 59Creating a Document Type in SAP ............................................................... 59Archiving a Print List.................................................................................. 60Viewing a Print List .................................................................................... 61

Chapter 5 Troubleshooting Installation Issues ...................................................... 63Overview ................................................................................................... 63High levels of logging ................................................................................. 63

4 EMC Documentum Archive Services for SAP Version 6.0 Installation Guide

Table of Contents

Incorrect Tomcat installation ....................................................................... 64

Chapter 6 Uninstalling Archive Services for SAP .................................................. 67Overview ................................................................................................... 67Preuninstallation tasks ................................................................................ 67Overview ............................................................................................... 67Preparing application servers for Archive Services for SAPuninstallation ......................................................................................... 67

Uninstalling Archive Services for SAP.......................................................... 68Uninstalling using Apache Tomcat .......................................................... 68Uninstalling using BEAWebLogic ........................................................... 68Uninstalling using IBMWebSphere ......................................................... 69

Uninstalling RFC archiving services............................................................. 69Overview ............................................................................................... 69Removing RFC Windows services ........................................................... 69Uninstalling RFC archiving services on Windows ..................................... 70Uninstalling RFC archiving services on UNIX .......................................... 71

Appendix A Advanced Installation Option for Load Balancing ................................. 73Overview ................................................................................................... 73Installing Tomcat ........................................................................................ 73Installing Apache ....................................................................................... 73Installing connectors for Apache and Tomcat................................................ 74Guidelines for configuring Apache and Tomcat for load balancing ................ 74


Table of Contents

List of Figures

Figure 1. Archive Services and SAP ............................................................................... 14


Table of Contents

List of Tables

Table 1. Terms and definitions ..................................................................................... 15Table 2. Unpacked files ............................................................................................... 40Table 3. Parameters in archives’ configuration page....................................................... 57


Table of Contents


Preface

Purpose of this guideThis guide explains how to install and configure Archive Services for SAP 6.0 (ArchiveServices 6.0). It contains information about installation requirements, and providestask‑based instructions for installing the software.

Note: For the sake of brevity, throughout this document, Archive Services for SAP willbe referred to as Archive Services.

Intended audienceThis manual is primarily intended for qualified consultants and system administrators.This role covers those who install and configure Archive Services for SAP.

The Archive Services for SAP application integrates two enterprise‑level softwarepackages: the EMC®Documentum® content management system with the SAP R/3system. Archive Services for SAP requires detailed knowledge of the SAP DMS andArchiveLink interfaces. Consultants and system administrators must have experiencewith the software products listed in the “Software Requirements” section of the ArchiveServices for SAP Release Notes.

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

Revision history

Revision date Description

September 2007 Initial publication of document forArchive Services for SAP 6.0

Typographic conventionsThis guide uses the following text conventions.


Preface

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 Archive Services. The product and documentation suite can be foundon EMC Powerlink at: https://powerlink.emc.com.

From Powerlink, you can download the latest version of Archive Services and the relateddocumentation suite. To access the contents in Powerlink, you will need to provide thelogin 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.

Archive Services for SAP — Documentation suite

Title Description Target role

Archive Services for SAPRelease Notes

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

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

Archive Services for SAPInstallation Guide

Provides the proceduresfor installing ArchiveServices.

System Administrator


https://documentum.subscribenet.com

Preface

Title Description Target role

Configuring SAP R/3 forArchive Services for SAP

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

System Administrator(SAP)

Archive Services for SAPAdministration Guide

Describes how to configureArchive Services using theWebAdmin tool.

Archive ServicesAdministrator

Archive Services for SAPUser Guide

Describes how SAP usersview documents.

Standard User

Note: Archive Services extensively uses the SAP ArchiveLink component. Refer to yourSAP ArchiveLink documentation for information on how you can perform advancedtasks.


Preface


Chapter 1Introducing Archive Services for SAP

OverviewThe Archive Services application integrates the EMC® Documentum® contentmanagement system with the SAP R/3 system. Based on SAP HTTP ArchiveLink 4.5interface, Archive Services provides a technology bridge between EMC Documentumand SAP R/3.

Archive Services for SAP provides the following functionalities:

• Enables users to access and display documents stored in a Documentum repositoryfrom within a variety of SAP modules.

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

in Documentum.This chapter covers the following topics:• Archive Services for SAP architecture, page 14• Supported SAP document formats, page 15• SAP and Archive Services for SAP terms, page 15


Introducing Archive Services for SAP

Archive Services for SAP architectureFigure 1. Archive Services and SAP

Archive Services for SAP consists of the following components:

• HTTP archiving services

A server component that, using an HTTP connection to SAP, enables you to archivereports, data, incoming and outgoing documents from SAP to the Documentumrepository. Archive Services is a J2EE servlet that communicates with SAPArchiveLink. The reports and archived documents can later be retrieved and viewedthrough SAPGUI.



• RFC archiving services

A server component that enables you to archive reports, data, incoming andoutgoing documents from SAP to the EMC 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.

• WebAdmin

An administrative console that allows you to:

— Create, configure, and manage archives.

— Manage certificates for the archive.

— Create repository connections for Archive Services.

— Configure document archival for Archive Services.

Note: Refer to the EMC Documentum Archive Services for SAP Release Notes for detailedinformation about 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)

SAP and Archive Services for SAP termsThis section presents terms and their definitions as used in this guide.

Table 1. Terms and definitions

Term Definition

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



Term Definition

HTTP Archiving Services Server component that, using an HTTPconnection to SAP, enables you to archivereports, data, incoming and outgoingdocuments from SAP to the Documentumrepository. HTTP Archiving Services is aJ2EE servlet that communicates with SAPArchiveLink. The reports and archiveddocuments can later be retrieved andviewed.

RFC Archiving Server A server component that enables youto archive reports, data, incoming andoutgoing documents from SAP to theEMC Documentum repository. Thearchived reports and documents canlater be retrieved and viewed throughSAPGUI and Documentum clients. Thiscomponent uses SAP Remote FunctionCalls (RFCs) to communicate with SAP.

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

DMCL Documentum Client Library. Managescommunication between clients and EMCDocumentum Content Server. Contains alibrary of API calls that are used by clientsfor execution on the EMC DocumentumContent Server. All client requests to theEMC Documentum Content Server gothrough the DMCL.

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

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.

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

Original Document Paper based version of a document.

Example 11.An invoice may consist of two sheets ofpaper received from a supplier. Paperdocuments are scanned in and stored aselectronic originals in Documentum.

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




Chapter 2Installing Archive Services for SAP

OverviewThis chapter describes the installation process for Archive Services.

Installing Archive Services consists of the following high‑level tasks; each of these tasks,in turn, are procedures containing several low‑level tasks:

1. Installation scenarios, page 19

2. Installation prerequisites, page 21

3. Preinstallation tasks, page 21

4.

5. Installing RFC archiving services, page 37

6. Significant system objects, page 35

7. Postinstallation configuration, page 42

Installation scenariosArchive Services may be installed in various configurations, depending on how it ismixed and matched with Content‑Addressed storage systems like EMC Centera® orthird‑party applications like Apache and Tomcat. Different configurations may alsobe arrived at depending on how and where Content Server and Archive Services areinstalled. The possible basic configurations are as follows:

• All‑in‑one installation, page 20• Separate Archive Services, page 20• Integration with EMC Centera, page 20• Advanced scalability options for Tomcat server, page 20Secondary configurations may be arrived at by mixing and matching the four basicconfigurations, where possible.


Installing Archive Services for SAP

Allinone installation

You may install the repository, Documentum Administrator (DA), Tomcat, and ArchiveServices on one system. This installation scenario is supported on all the operatingsystems that are supported by Archive Services for SAP. Information on the operatingsystems that Archive Services for SAP supports is in the EMC Documentum ArchiveServices for SAP Release Notes.

Separate Archive Services

In this installation configuration, Archive Services need not be installed on the samesystem where the repository is installed. You can install Content Server and DA on onesystem (running any OS). On another system, you can install JDK, a supported WebApplication Server, such as Tomcat or BEA Weblogic, Documentum Foundation Classes(DFC), and Archive Services (running any OS). Archive Services may be configured toaccess the repository that’s installed on the other machine.

Integration with EMC Centera

Archive Services integrates with EMC’s Content‑Addressed storage systems, EMCCentera. Customers using Archive Services along with EMC Centera can formulate rulesthat determine where information is archived, and how long it is retained.

For EMC Centera connectivity, configure the Documentum server to use a CA store. Formore details, please refer to the EMC Documentum Content Server Administration Guide.

Advanced scalability options for Tomcat server

Archive Services may be installed on a Tomcat server where Apache (refer to InstallingApache, page 73) and Tomcat (refer to Installing Tomcat, page 26) are configured to useload‑balancing between multiple Tomcat sessions. This configuration is particularlypowerful when used in tandem with multiple Tomcat hosts. Use modjk (refer toInstalling connectors for Apache and Tomcat, page 74) as a connector for communicationsbetween Apache and Tomcat.

Appendix A, Advanced Installation Option for Load Balancing contains moreinformation on installing Archive Services on a Tomcat server in a load balancingconfiguration.



Installation prerequisites

General prerequisites

The person installing Archive Services 6.0 should have administrative experience withthe software products listed in the EMC Documentum Archive Services for SAP ReleaseNotes.

Note:• Unless the person installing the product has the prerequisite experience, EMC

Documentum recommends that you do not perform installations using only EMCDocumentum manuals as a guide.

• EMC Documentum Support can only assist with systems which were installedby qualified persons following the specific instructions outlined in both thedocumentation and the training manual.

Software prerequisites

Archive Services depends on specific versions of Documentum and third‑party products.Refer to the Software Requirements section of the Archive Services for SAP Release Notes fordetailed information about software prerequisites for Archive Services.

Preinstallation tasksBefore installing Archive Services 6.0, you must perform the following tasks :

• Installing databases, page 22• Preparing EMC Documentum Content Server, page 22• Preparing the repository, page 24• Creating connections to EMC Centera, page 24• Preparing the application server host, page 24• Preparing the application server software, page 25• Obtaining the latest copy of the product from the Documentum Download Center,

page 30



Installing databases

Installation of Archive Services requires that a Content Server is previously installed;Content Server’s installation, in its turn, requires an existing installation of a database.Depending on your enterprise’s requirements, you may install any database of yourchoice. Content Server supports the following databases:

• DB2• Oracle• SQL Server• SybaseTo a large extent, you can configure the database per your organization’s specificrequirements. However, when a database is going to be used with Content Server, youneed to keep in mind certain specific requirements. Please refer to the Preparing theDatabase for Content Server Installation section of the Content Server Installation Guide formore information.

Preparing EMC Documentum Content Server

This section contains the following topics:• Installing Content Server, page 22• Configuring Content Server, page 23

Installing Content Server

Archive Services is installed on top of existing installations of Content Server. Wheninstalling Content Server for the purposes of using with Archive Services subsequently,please keep the following points in mind:• Most of the default settings that appear in the installation wizard are acceptable.• Type valid values in fields where you are required to provide inputs.• One of the possible installation scenarios of Archive Services is the integration with

EMC Centera, a Content Addressed (CA) storage system. If you have a valid licensefor EMC Centera, you may wish to enable Archive Services’s integration with EMCCentera.

— In one of the relevant Documentum Content Server — Select Feature pages ofthe Content Server installation wizard, be sure to select the Enable ContentServices for EMC Centera checkbox.

— In the License Key field, type a valid license key for EMC Centera.



• In the Document Content Server — Select Java Method Server Ports page of theinstallation wizard, accept the default values that appear and click Next.

The ports used by Apache Tomcat, as indicated here, is different from the portsthat you will configure for a subsequent installation of Tomcat (refer to InstallingTomcat, page 26).

Note: The Tomcat installation, as indicated in the Content Server installation wizard,is a scaled‑down version; do not deploy Archive Services with this installation ofTomcat. For the purposes of Archive Services, install Tomcat again as indicatedin Installing Tomcat, page 26.

For more information, refer to the following sections of the Content Server InstallationGuide:

• Preparing for Content Server Installation• Express Installation• Custom Installation• Postinstallation TasksIf you wish to install advanced components of Content Server, please refer to otherrelevant sections of the Content Server Installation Guide

Configuring Content Server

After you install Content Server, you need to configure it. When running the ServerConfiguration program, for the purposes of using with Archive Services subsequently,please keep the following points in mind:

• If you have a valid license for EMC Centera, and you wish to integrate ArchiveServices with EMC Centera, do the following:

— In one of the relevant Server Configuration Program— Select Feature pages, besure to select the Enable Content Services for EMC Centera checkbox.

— In the License Key field, type a valid license key for EMC Centera.

• Most of the default values that appear in the Server Configuration Program areacceptable for a subsequent installation of and use with Archive Services. Therefore,you may wish to configure Content Server quickly. In the Server ConfigurationProgram — Select Configuration Type page, choose Express Configuration.



• You could use Content Server and Archive Services in a test environment or aproduction environment:

— Test environment

In the Server Configuration Program — Enter repository information page,choose MEDIUM 180MB from the Repository Size drop‑down list.

— Production environment

Depending on the data storage requirements of your enterprise, from theRepository Size drop‑down list, choose a higher repository size.

For more information, refer to the Configuring the Server and Repository section of theContent Server Installation Guide.

Preparing the repository

The repository should be up, running and performing before you install ArchiveServices. Archive Services requires a fully functional repository; in addition, it writesconfiguration objects into the designated repository during the install. The installationcreates an SAP cabinet in the repository and writes Archive Services administrationobjects in the System cabinet.

Creating connections to EMC Centera

If your installation scenario (refer to Installation scenarios, page 19) includes connectionsto EMC Centera, you will have to create content‑addressable (CA) stores. For moreinformation on creating CA stores, refer to the Creating Content‑Addressed Stores sectionof the Archive Services for SAP Administration Guide.

Preparing the application server host

This section contains the following topics:• Ensuring sufficient temporary disk space on the host, page 25• Ensuring the Java heap size is sufficient, page 25• Supported operating systems and application servers, page 25



Ensuring sufficient temporary disk space on the host

Application servers vary as to how much temporary disk space they require when anapplication is installed. Allow at least half a gigabyte of free disk space on the applicationserver host for installing Archive Services for SAP:• On Windows hosts, ensure that the free space is on the drive to which the TEMP

environment variable points.• On UNIX hosts, ensure that the free space is in $TEMP.• On AIX with WebSphere, the temporary directory used by WebSphere is /tmp.

Ensuring the Java heap size is sufficient

Setting the Java heap size properly is important to avoid out‑of‑memory errors:• For BEA, Tomcat, and Oracle, set the heap size to 512 MB.• For Websphere, set the heap size to 1024 MB.

Supported operating systems and application servers

Archive Services can be installed on different combinations of operating systems andapplication servers. For more information on supported combinations, refer to the“Software requirements” section of the Archive Services for SAP Release Notes.

Preparing the application server software

Before you run the installer for Archive Services, install a supported J2EE applicationserver (refer to Supported operating systems and application servers, page 25) or theApache Tomcat servlet container on the application server host and ensure that it cansuccessfully serve sample JSP pages.

This section contains information on preparing the application server software beforeinstalling Archive Services:• Preparing Tomcat, page 26• Preparing BEA WebLogic, page 27• Preparing IBM WebSphere, page 29• Preparing Sun Java System Application Server, page 29EMC Documentum does not provide support for installing or running applicationservers. Refer to the documentation for each application server for instructions on



installing, stopping, starting, and running the application server. Contact the applicationserver vendor for technical support.

Preparing Tomcat

Overview

Archive Services is designed to run on Apache Tomcat application server. LeveragingTomcat provides Archive Services with the following advantages:• Platform neutrality• Enhanced performance• ScalabilityThe Tomcat configuration needs to be modified to enable it to find all the building blocksof the ArchiveLink component.

This section contains the following topics:• Installing Tomcat, page 26• Verifying Apache Tomcat, page 27• Configuring Tomcat in UNIX, page 27

Installing Tomcat

In the Tomcat installation wizard, be sure to install Tomcat with J2SE/JDK, and not JRE.

All other default values that appear in the installation wizard are acceptable. By default,Apache Tomcat uses port 8080 for the HTTP connector port. However, the default portused by the Tomcat instance installed with EMC Documentum Content Server is 9080(refer to Installing Content Server, page 22); you should not confuse the two.

For detailed installation, configuration, and administration instructions, refer to thedocumentation available on the Tomcat website (http://jakarta.apache.org/tomcat/).

If Tomcat is installed to run from the command line, the CATALINA_HOMEenvironment variable must be set properly.

On UNIX, Tomcat is always started from a command line, but this is also an option inWindows installations. For complete information on setting CATALINA_HOME, referto Apache’s documentation for Tomcat.


http://jakarta.apache.org/tomcat/


Verifying Apache Tomcat

After you install Tomcat, use these instructions to verify that Tomcat is running correctly.

To verify that Apache Tomcat is running:

1. Open the default server home page in a browser:http://host_name:port_number

where host_name is the computer where Tomcat is installed and port_number is theport on which it listens. Substitute localhost for host_name if the browser is on theTomcat host.

2. Click JSP Examples on the left side of the Tomcat home page.

3. Execute one of the examples.

Configuring Tomcat in UNIX

Configuring HPUX to run Java server in production mode

By default, HP‑UX is not configured to run a Java server in production mode. Forexample, HP‑UX must be configured to support a larger number of threads per process.HP provides an out‑of‑the‑box tool that automatically configures an HP system to runa Java server in production mode. Download this tool from the following location:http://www.hp.com/products1/unix/java/java2/outofbox/index.html.

Preparing BEA WebLogic

A BEA WebLogic installation must meet the following requirements before ArchiveServices is installed:• WebLogic must be correctly installed in either single application server or Managed

Server configuration.

Refer to BEA’s documentation for instructions.• Set up a server alias and domain for the application.

Ensure that the domain name does not contain any spaces.

If you are installing multiple applications, you must decide whether to install themin the same domain or not. When multiple applications are installed in the samedomain, all applications are started and stopped at the same time. If the applicationsare installed in different domains, they can be started and stopped separately andeach application runs as a separate Java process.


http://www.hp.com/products1/unix/java/java2/outofbox/index.html


• Ensure that the installation directory does not contain any spaces.

For example, installing to C:\Program Files\BEA does not work.• Determine two unused ports on which WebLogic can listen.

The default port for HTTP requests is 7001. The default port for HTTPS requests is7002.

• On Windows, decide whether to run WebLogic as a service or from the commandline.

This is determined when you configure WebLogic, not when the EMC Documentumapplication is installed.

If you start WebLogic from the command line, to stop it, you must kill the process.• Install Archive Services as the same user who installed the application server.• WebLogic must be running when you install Archive Services.• On HP‑UX with WebLogic 8.1, ensure that you install and run the HP Java

Out‑of‑Box Kernel Configuration bundle.

Download the bundle from HP’s web site athttp://www.hp.com/products1/unix/java/java2/outofbox/downloads/license_java_oob.html. Release notes for the bundle are located athttp://www.hp.com/products1/unix/java/java2/outofbox/infolibrary/rnotes_oob_v2.03.html.

• EMC Documentum recommends creating a different domain in BEA WebLogicfor each instance of Archive Services.

• Install to an instance of the application server running in development mode.

Refer to the BEA WebLogic documentation for the correct procedure when you areready to deploy an application in production mode.

• In a WebLogic Managed Server environment, you must modify the main BEA serverconfig.xml file and the load balancer web.xml file.

To each of these files, add the following lines of code (or, if this code already exists,change the parameter value to false):<initparam><paramname>KeepAliveEnabled</paramname><paramvalue>false</paramvalue>

</initparam>

Do not make the above change in a single server environment, where the changecauses runtime errors.

• BEA WebLogic can slow down, throw exceptions, or crash with an application thathas a large number of Java Server Pages.

BEA recommends setting the MaxPermSize parameter to 128 to avoid theseproblems.


http://www.hp.com/products1/unix/java/java2/outofbox/downloads/license_java_oob.html

http://www.hp.com/products1/unix/java/java2/outofbox/downloads/license_java_oob.html

http://www.hp.com/products1/unix/java/java2/outofbox/infolibrary/rnotes_oob_v2.03.html

http://www.hp.com/products1/unix/java/java2/outofbox/infolibrary/rnotes_oob_v2.03.html


• On WebLogic 8 with Solaris, ensure that the performance tuning option Use NativeI/O is set correctly:

— Turn the setting off

or

— After installing the WDK application, edit the startDocumentum.sh file andadd $BEA_HOME/weblogic81/server/lib/solaris to the ‑Djava.library.pathoption.

Preparing IBM WebSphere

Ensure that the following requirements are fulfilled before you install Archive Serviceson IBM WebSphere:• Install IBM WebSphere as the root user.• Test the IBM samples to ensure that WebSphere is running properly.

For documentation and information about the Samples Gallery, refer to theWebSphere Information Center Library at http://www‑3.ibm.com/software/webservers/appserv/infocenter.html.

• The WebSphere instance on which you are installing or uninstalling Archive Servicesmust be running during installation.

• Install Archive Services as the root user (the same user who installed the applicationserver).

Preparing Sun Java System Application Server

The following requirements must be met before installing Archive Services on the SunJava System application server:• Install Archive Services on Sun Java System as the root user.• Install Archive Services in the default domain and default instance.• The administration server must be running when you install or uninstall Archive

Services.• The target servers must also be running when you install or uninstall Archive

Services.• The application server must be running before starting to install or uninstall Archive

Services.


http://www-3.ibm.com/software/webservers/appserv/infocenter.html

http://www-3.ibm.com/software/webservers/appserv/infocenter.html


• Turn the ACL setting off for the virtual server where you intend to deploy ArchiveServices.

Perform the following tasks:

1. Log in to Sun Java System Application Server’s administrative console with validcredentials.

2. In the left pane, browse to App Server Instances > Server_Name > HTTP Server >Virtual Servers > Server_Name.The <Server_Name>: HTTP Server: Virtual Servers: <Server_Name> page appears.

3. Click General.

4. Clear ACLs.

5. Click Save.

Obtaining the latest copy of the product from theDocumentum Download Center

To ensure that you install the current version of this product, visit the EMC DownloadCenter at https://emc.subscribenet.com and review the product versions available foryour platform.

Download the following files:• assap.war.zip• Enterprise_Integration_Core.zip

Installing Archive Services for SAPThis section contains the following topics:• Installing the EI Core docapp file, page 31• Preparing the assap.war file• Deploying the assap.war file• Significant system objects


https://emc.subscribenet.com


Installing the EI Core docapp file

This section provides instructions for installing the Install EI Core docapp file on alloperating systems.

To continue the installation on all operating systems:

1. Extract the Enterprise_Integration_Core compressed file (Enterprise_Integration_Core.zip for windows and Enterprise_Integration_Core.tar for UNIX) to a temporarylocation.

2. Start the EMC Documentum Application Installer and log into a repository as auser with superuser privileges.The Select DocApp Archive dialog box appears.

3. Click Browse and locate the Enterprise_Integration_Core docapp folder.

4. Select the Enterprise_Integration_Core docapp folder and click OK.

5. Click Start Installation.An information message appears indicating that the installation will take a fewminutes to complete.

6. Click Yes to continue.The EMC Documentum Application Installer installs the DocApp archive.

7. After the installation completes, check the DocApp’s installation log file(<docapp_name>.html) for any docapp installation‑related errors.The <docapp_name>.html log file is created in the directory where the EMCDocumentum Application Installer starts.

Note: More information on installing docapps is in the How to Use section of EMCDocumentum Application Installer online help.

Preparing the assap.war file

The following procedure describes how to prepare the assap.war file for installation.

Note: Perform this procedure after you deploy the war file if you are running a TomcatWeb Server.

To prepare the assap.war file for installation:

1. Rename assap.war.zip to assap.war.

2. Copy the assap.war file to a temporary directory.



3. Unjar the file using the following jar command:jar –xvf assap.warThe war file is extracted to a directory called ’assap’.

4. Edit dfc.properties file in the assap/WEB‑INF/classes folder as follows:

a. Enter the docbroker host name. For example:dfc.docbroker.host[0]=100.100.100.100

b. Enter the docbroker port number. For example:dfc.docbroker.port[0]=1489 optional, default 1489

c. Optionally, enter the DFC data directory. For example:dfc.data.dir=C:/Documentum

d. Enter the DFC global BOF registry docbase name. For example:dfc.bof.registry.repository= cssap53_dev_assap

e. Enter the DFC global BOF registry docbase user name. For example:dfc.bof.registry.username=dm_bof_registry

f. Enter the DFC global BOF registry docbase user encrypted password. Forexample:dfc.bof.registry.password=kBb9DmXB6pQ\=

5. Re‑create the assap.war from the temporary folder using the following command:jar –cvf assap.war assap

6. Deploy AS SAP war file using the application server procedure appropriate foryour installation.

Deploying the assap.war file

This section provides instructions for deploying the AS SAP war file on all operatingsystems using selected application servers.

Deploying assap.war using Apache Tomcat

To deploy using Apache Tomcat:

1. Ensure Apache Tomcat is configured to deploy the assap.war file in unpacked mode.

This is the Apache Tomcat default setting.



2. Copy the re‑jarred assap.war file to the <<Tomcat>>/webapps folder.

3. Restart the Apache Tomcat server.

Deploying assap.war using BEA WebLogic

Follow the steps 1 through 4 in Preparing the assap.war file and copy all the files toa folder, such as assap.

To deploy using BEA WebLogic:

1. Start the BEA WebLogic server.

http://<ip>:7001/console

2. Enter your user ID and password.

The entries are case sensitive.

The BEA WebLogic server window appears.

3. Click Deployments in the left panel.

4. Click Lock & Edit also located in the left panel.

5. Click Install.

6. Using the Install Application Assistant, locate the assap directory you want to install.

Specifiying the assap directory installs all components in and below the directory.For example:

100.100.100.100/export/home0/bea02/softwares

7. Select the assap directory and click Next.

8. Specify whether to target the installation as an application or a shared library.

9. Click Next.

10. Select the servers and/or clusters to which you want to deploy AS SAP.

Note: If you have not created additional Managed Servers or clusters, you will notsee this page.

11. Click Next.

12. Optionally, accept the defaults for these settings about the deployment, or updatethem:

• Deployed Web application name.

• Application security model.



• How the source directory contents were made available to targeted ManagedServers and clusters.

13. Click Next.

14. Review the configuration settings you specified:

• app‑root

• /app

• /plan

Note: If you install an application that follows this directory structure and there isno deployment plan in the /plan directory, the WebLogic server automatically createsa deployment plan for you.

15. Click Finish.

If you chose to immediately go to the deployment’s configuration screen, click thetabs to set additional configuration settings for the Web application. If you choseto change this information later, the Administration Console returns you to theDeployments table, which should now include your newly‑installedWeb application.

16. Click Activate Changes in left panel.

This commits all changes made.

Note: Not all changes take effect immediately—some require a restart.

Deploying assap.war using IBM WebSphere

To deploy using IBM WebSphere:

1. Start the IBM WebSphere server. For example:

http://10.31.150.113.9060/ibm/console

2. Enter your user ID.

The Integrated Solutions Console screen appears.

3. Expand Applications and click Enterprise Applications.

4. Click Install in the Enterprise Applications panel.

5. Select Local file system if the file is located on a local machine, otherwise selectRemote file system with context root as assap.

6. Select the (*) Show me all installation options and parameters and press Next.

7. Accept the defaults in the next screen and click Continue.



8. In the following screen select Precompile JavaServer Pages files and enter assapas the Application Name. Click Next.

9. In theMap modules to servers screen select the assap.war file for the module andclick Next.

10. In the Provide options to compile JSPs screen enter 15 under JDK source leveland click Next.

Note: The JDK source level specifies the level at which the Java compiler compilesJSP Java sources. Valid values are 13, 14, and 15. The default value is 13, whichspecifies source level 1.3.

11. Select JSP enable class reloading and click Next.

12. Select both checkboxes to map shared libraries and click Next.

13. Select to map virtual hosts and click Next.

14. Click Finish.

The message ADMA5013I: Application assap installed successfully indicates asuccessful installation.

ClassLoader Setting

To complete the installation:

1. Browse to Application > Enterprise Applications and click assap.

2. ClickManage Modules under theModules heading.

3. In the following screen click the assap hyper link.

4. In Class loader order drop‑down box, select Class loaded with application classloader first and click OK.

5. In the next screen click Save.

6. In the Manage Modules screen, assap appears selected in red.

7. Log out and restart the server to deploy AS SAP.

Significant system objects

This section contains the following topics:• dfc.properties, page 36• log4j.properties, page 36



• docbases.properties, page 36• al.properties, page 36

dfc.properties

Documentum stores data in the dfc.properties file located in the <Tomcat_installation_directory>\webapps\<Archive_Services_virtual_directory>\WEB‑INF\classesdirectory.

For more information, refer to the Documentum Foundation Classes Installation Guide.

log4j.properties

All logging details are available in thelog4j.properties file available in the followingdirectory:

<Tomcat‑Installation‑Directory>\webapps\<Archive Services–Virtual–Directory>\WEB‑INF

By default, the log output goes to the alserver.log file available in the following directory:

<Tomcat‑Installation‑Directory>\webapps\<Archive Services–Virtual–Directory>\WEB‑INF/logs

Log4j.properties can be changed during runtime of servlet, and updates are detectedautomatically.

docbases.properties

This file contains the repository login configuration details such as the server ID, username, and password.

If you intend to edit this file, we recommend that you use WebAdmin for this purpose(refer to Setting up repository connections, page 55).

For more information, refer to the Configuring, Viewing, and Editing Repository Connectionssection of the Archive Services for SAP Administration Guide.

al.properties

The system parameters for the Archive Services servlet are defined in al.properties.al.properties is located in the following directory:



<Tomcat‑Installation‑Directory>\webapps\<Archive Services‑Virtual‑Directory>\WEB‑INF

Installing RFC archiving servicesThe RFC installer installs RFC archiving services. In order to use RFC archiving, youmust have Archive Services for SAP or Content Services for SAP installed on yourmachine.

This section contains the following topics:• Installing RFC components on Windows, page 37• Installing RFC components on UNIX, page 39

Installing RFC components on Windows

Overview

This section contains the following topics:• Installing RFC components, page 37• Creating RFC services, page 38

Installing RFC components

To install RFC components:

1. Download RFC archiving services’ installer archive (refer to the Obtaining the latestcopy of the product from the Documentum Download Center, page 30).

2. Extract the contents of the compressed .zip file to a temporary directory.

3. In the temporary directory, double‑click the Setup.exe file.The Installation WizardWelcome dialog box is displayed. Click Next.The Setup Type dialog box is displayed.

4. Select Copy Software to install the software.Click Next.

5. In the Enter Product License Key dialog box, enter the product license key. ClickNext.The Select Components dialog box is displayed.



6. Select the Archive Services for SAP (RFC) checkbox to install the RFC component.Click Next.

7. If you have any Documentum products installed on your machine, the system willask for permission to overwrite the dfc.properties file. Click Yes to overwrite.

8. The Start Copying Files dialog box is displayed. Click Next to install the selectedcomponents.

9. At the end of the installation, the Setup Complete dialog box is displayed. ClickFinish.

Creating RFC services

To create RFC service:

1. Double‑click the Setup.exe file.The Installation WizardWelcome dialog box is displayed. Click Next.

2. In the Setup Type dialog box, select Service Create to create the RFC service. ClickNext.

3. In the Archive Services for SAP (RFC) Parameters dialog box, enter the followinginformation:

Item Description

Docbase to be used withArchive Services forSAP (RFC)

Name of the repository to connect to.

SAP RFC DestinationName

Name of the RFC destination as configured in WebAdmin, as described in the EMC Documentum ArchiveServices for SAP Administration Guide.

Docbase User Name Repository user.

Password Password of the repository user.

NT Domain Name Optional Windows NT domain name. This is requiredif the repository user is in a different domain.

4. Click Next.

5. The Ready to create services dialog box displays all the RFC services that will becreated. Click Next.

6. Click OK in the Information dialog box.

7. A dialog asks you whether you want to create another service.



Do one of the following:• If you want to create another service, click Yes and repeat steps 3–6.• If you do not want to create another service, click No.

The Setup Complete dialog box is displayed.8. Click Finish.

The following services are created:• RFC Archive Handler <repository‑name>/<RFC_Destination_Name>• RFC Archive Server <repository‑name>/<RFC_Destination_Name>

Installing RFC components on UNIX

You can install RFC components on UNIX. RFC archiving services is supported only onthe following UNIX platforms:• HP–UX• Solaris

Note: RFC archiving services is not available on AIX.

For technical support, visit EMC Powerlink at: http://powerlink.emc.com.This section contains the following topics:

• Installing the archive, page 39• Configuring RFC archiving services, page 40

Installing the archive

EMC Documentum recommends you install the software in the EMC DocumentumContent Server installation directory tree under the Documentum Administrator UNIXaccount.

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.

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

3. Download the RFC installer to the system where you want to install RFC archivingservices (refer to Obtaining the latest copy of the product from the DocumentumDownload Center, page 30).


http://softwaresupport.emc.com


Copy the installer to the directory that you created in step 2.

4. Uncompress the RFC installer.

5. Unpack the RFC installation file.The following files are unpacked:

Table 2. Unpacked files

File name Description

dmarchivelink ArchiveLink Request Handler program

dfc.properties Sample dfc.properties

sapinfo Program to test the SAP RFC connection

dmal.ini Sample RFC archive configuration file

alfilter Sample filter that extracts the first textline of a PrintList

alfilter.cpp Source code of sample filter

alf2html PDF/HTML filter

Configuring RFC archiving services

Overview

After copying software to the installation directory and unpacking the same, configureRFC archiving services for UNIX systems. Configure the following files in the RFCarchiving services installation directory:

• dmal.ini

• dfc.properties

This section contains the following topics:• Configuring trusted login, page 40• Configuring dfc.properties, page 42

Configuring trusted login

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



Trusted login can be used when RFC archiving services runs on the same server platformas EMC Documentum Content Server. Use the UNIX account that corresponds to anEMC Documentum user configured in the repository.

The UNIX user needs the privileges to read and write to the spool directories configuredfor each archive. In EMC Documentum, the RFC archiving services 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‑directoryof the RFC archiving services program, dmarchivelink . It may also be located inthe directory defined by the environment variable $DOCUMENTUM. The dmal.ini filecontains configuration information that allows RFC archiving services to connect to therepository. All other configuration information is stored in the repository in specialrepository 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 Archive Services for SAP and Archive Services for SAPAdministration Guide for more details.

• docbase_user: Enter repository user under which RFC archiving services is running.This user will be the owner of the documents created. We recommend that youcreate a special repository user under which the ArchiveLink processes 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. We recommend running under the repository user account so thepassword does not have to be written down. If you use the password make sure the file isonly 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=freddocbase_password=foo.bar[Debug]debug_level=3

Configuring dfc.properties

The standard EMC Documentum client configuration file is named dfc.properties. Theminimum configuration required is the host name or IP address of the host running theconnection broker. You can use the host name if it is configured in ‘/etc/hosts’ UNIXconfiguration file. The dfc.properties file may reside in the run‑directory and installationdirectory of the Content Services Archive software or it may also be located in a directoryspecified by the environment variable $DOCUMENTUM.

Edit dfc.properties in the RFC archiving services installation directory to configure thehost name or IP address that runs the connection broker.

Example:

[DOCBROKER_PRIMARY]host=maverick

Postinstallation configurationThis section contains the following topics:• Configuring RFC services, page 43



• Configuring the temporary store, page 47• Customizing the dfc.properties file for optimum performance, page 48

Configuring RFC services

Overview

This section contains the following topics:• Configuring RFC Windows services, page 43• Configuring RFC UNIX processes, page 44• Configuring logging, page 47

Configuring RFC Windows services

Before 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)• WebAdmin — ArchiveLink RFC configurationIt is recommended that one of the following naming conventions be used, depending onthe intended uses of Archive Services for SAP and the number of systems that will beintegrated in the development, testing and production environments:<REPOSITORYNAME>_<SAPSYSID_CLIENT> (ex: APINVOICE_PRD_100)<DOCUMENTUMHOSTNAME>_<SAPSYSID_CLIENT> (ex: NTDCTMPRD01_PRD_100)<DOCUMENTUMHOSTNAME>_<SAPHOSTNAME> (ex: NTDCTMPRD01_SAPPRD01)

Refer to Configuring SAP R/3 for Archive Services for SAP to configure the SAP RFCDestination and Archive Services for SAP Administration Guide to configure the ArchiveServices for SAP RFC Destination using the WebAdmin.

To configure RFC services:

1. Access the Windows Services.

2. Locate the following RFC services:• RFC Archive Handler <repository‑name>/<RFC_Destination_Name>• RFC Archive Server <repository‑name>/<RFC_Destination_Name>



3. Right‑click the RFC Archive Handler service, and then select Properties.

4. From the Properties dialog box, click Log On.

5. Select This account.Enter valid login credentials of the host SAP R3 system; this information is used byRFC Archive Services to access the shared directory located in the host SAP R3system.

Note: A user with the login credentials described in this step should have beencreated already on the system where RFC Archive Services are run.

6. Click OK.

7. Repeat steps 3–6 for the RFC Archive Server service.

Configuring RFC UNIX processes

Before starting the Archive Services for SAP RFC processes on UNIX, the RFC destinationname must be identical, and unique for each repository‑SAP connection, in threelocations:

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

Refer to Configuring SAP R/3 for Archive Services for SAP to configure the SAP RFCDestination and Archive Services for SAP Administration Guide to configure the ArchiveServices for SAP RFC Destination using WebAdmin.

Starting 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 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.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 RFC 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/

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



Configuring logging

If the RFC Archive services encounter any errors during start up or while running, thereare 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. Archive Services for SAP errors may be classified as Source names ʺArchiveServices for SAPʺ or ʺService Control Manager.ʺ

RFC Archive aservice logs are written to a log file in C:\Documentum\DocLink\log(assuming default installation). These log files use the naming convention ’dmal*.log’for the RFC Archive service. To change the log locations and debug levels, go to thefollowing registry settings:

HKEY_LOCAL_MACHINE > SOFTWARE > Documentum > Doclink > Archive >Docbase > <repository name>@<RFC connection 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.

Configuring the temporary store

The al.properties file is located in <Tomcat‑Installation‑Directory>\webapps\<Virtual‑Directory>\WEB‑INF. You must configure the al.properties file so that it points to a validdirectory in the file system with complete access rights; Archive Services writes data tofile in this temporary store before reading or writing to HTTP request.

For example, you could customize the relevant section of the al.properties file as follows:archiving.tempDir=C:\\archivelink

Note: If you’re running Archive Services on UNIX, you will need to customize the filedifferently. In UNIX, you could customize the relevant section as follows::archiving.tempDir=/usr/temp/AL_SERVER_DATA



Customizing the dfc.properties file for optimumperformance

Certain parameters must be customized in the dfc.properties file in order to optimizeDocumentum Client Library’s (DMCL’s) behavior; this is necessary to obtain optimumperformance from Archive Services.

To customize parameters in dfc.properties:

1. Choose Start > Run.

2. In the Open field, type dfc.properties.The dfc.properties file opens.

Note: In UNIX, the dfc.properties file is usually available in $DOCUMENTUM.

3. Add the following attribute to dfc.properties:max_session_count = 10

This attribute determines the maximum number of sessions.

Note: The value for this attribute is determined by the following formula:

max_session_count ≥ [docbases.numberOfConnections (default: 9) *numberOfDocbases] + 1.

In this formula, the following attributes:• docbases.numberOfConnections

This attribute determines the number of connections established by therepository. The default value is 9.

• numberOfDocbases

This attribute indicates the number of repositories that have been installed. Ifyou have installed one repository, this value will be 1.

occur in the al.properties file (refer to Configuring the temporary store, page 47).

After installing the first repository, you must set the value of max_session_count as10 because, per the formula, max_session_count ≥ [docbases.numberOfConnections(default: 9) * numberOfDocbases (1)] + 1.

Example 21.If you have 3 repositories installed, and the value of docbases.numberOfConnectionsis 5, then max_session_count should be ≥ 16.

4. Set the values of the following attributes as indicated below:cache_queries = Tlocal_diskfull_warn = 100



local_purge_on_diskfull = Tlocal_path = <directory_where_cached_objects_are_stored>

Note: Customizing these attributes (cache_queries, local_diskfull_limit, andlocal_purge_on_diskfull) is not mandatory for Archive Services to function correctly.These customized attributes improve the performance of Archive Services; ArchiveServices, however, will function even if these attributes are not set. However, it ismandatory to add max_session_count to dfc.properties.




Chapter 3Upgrading Archive Services for SAP

OverviewBefore upgrading Archive Services, depending on existing infrastructure and yourneeds, you need to determine how you want to deploy the application in your enterprise.

Note: Before starting any upgrades, make sure that the version of the DocumentumApplication Installer used to install any docapps is the same version as that of theContent Server.

You can consider the following upgrade paths:• Upgrading from Archive Services for SAP 5.3 SPx, page 51• Upgrading from Content Services for SAP – Archiving Server 5.3, page 52• Upgrading RFC archiving services, page 52

Upgrading from Archive Services for SAP 5.3SPx

You can upgrade directly from AS SAP 5.3 SPx to AS SAP 6.0. Upgrading to AS SAP 6.0involves:• Uninstalling previous versions of the application• Installing the Enterprise Integration Core docapp• Installing Archive Services for SAP 6.0 (refer to Chapter 2, Installing Archive Services

for SAP)For upgrading to AS SAP 6.0, refer to the table in Supported operating systems andapplication servers, page 25 to understand possible upgrade path, depending on youroperating system and application server environments.

Note: When you upgrade from AS SAP 5.3 SPx to 6.0, you should install RFC archivingservices separately (refer to Installing RFC archiving services, page 37).


Upgrading Archive Services for SAP

Upgrading from Content Services for SAP –Archiving Server 5.3

You can upgrade directly from Content Services for SAP – Archiving Server 5.3 toArchive Services for SAP 6.0. Upgrading to Archive Services for SAP 5.3 SP3 involves:• Uninstalling previous versions of the application• Installing Archive Services for SAP 6.0 (refer to Chapter 2, Installing Archive Services

for SAP)

Note: When you upgrade from Content Services for SAP – Archiving Server 5.3 toArchive Services for SAP 6.0, you should install RFC archiving services separately (referto Installing RFC archiving services, page 37).

Upgrading RFC archiving servicesArchive Services for SAP gives you an archiving‑only environment. You do not haveaccess to additional capabilities, available in Content Services for SAP, such as theAgent, View, Manage, and Capture components. If you need these advanced features,you should install or upgrade to Content Services for SAP 6.0 to work with ArchiveServices for SAP 6.0.

In addition to Archive Services for SAP, if you are also installing or upgrading from anearlier version of Content Services for SAP to Content Services for SAP 6.0, note thefollowing details:• From 5.3 SP3 onwards, RFC archiving services is not a part of Content Services for

SAP; this component has been moved to Archive Services for SAP 5.3 SP3.• If you have configured RFC archives using versions of Content Services of SAP lower

than 5.3 SP3, you cannot access them without a functional installation of ArchiveServices for SAP 5.3 SP3. To ensure that Archive Services for SAP 5.3 SP3 can accessRFC archives that were created using versions of Content Services of SAP lower than5.3 SP3, you must upgrade RFC archiving services.



• Upgrading RFC archiving services involves:

— Stopping all RFC services

Make sure that there are no pending requests in the server queue.

— Uninstalling previous version of RFC archiving services

— Installing the current version of RFC archiving services (refer to Installing RFCarchiving services, page 37)

— Installing the Enterprise Integration Core docapp (refer to Installing theEnterprise Integration Core docapp)




Chapter 4Testing the Installation

OverviewAfter installing Archive Services, test the installation by:

• Setting up repository connections, page 55• Displaying configured repository connections, page 56• Defining an ArchiveID in WebAdmin, page 56• Defining a logical ArchiveID in SAP, page 58• Testing connection between SAP and Archive Services, page 59• Creating a Document Type in SAP, page 59• Archiving a Print List, page 60• Viewing a Print List, page 61

Setting up repository connections1. Open a Web browser and connect to WebAdmin. Usually, this URL is as follows:

http://<server>:<port number>/<Archive Services–Virtual–Directory>/jsp/login.jsp.

From the Repository field, select the repository for which you would like toconfigure connections.

Note: This functionality is not available in the Content Services for SAP 5.2.5 SP3WebAdmin

2. From the left pane, click on ArchiveLink

3. From the right pane, click Repositories.

4. From theChoose a Repository drop‑down list, selectCreate a New Configuration ....

5. In the Repository Name field, type the name of the repository that you wish toconnect to.

6. In the User Name field, type a valid user name for the repository.

7. In the User Password field, type the corresponding password for the user name.


Testing the Installation

8. In the Domain field, type the domain name that the user is a member of.

9. Click Create.

A new repository connection has been created. The docbases.properties file isupdated with the details entered above.

Note: Repository connections typically need to be configured only once, immediatelyafter the installation.

10. To save the repository connection configuration, click Save.

11. To test the newly created repository connection, click Test Connection.

An information message appears below Test Connection, indicating that therepository connection has been tested successfully.

Displaying configured repository connectionsIn your web browser, enter the following URL:

http://<server>:<Tomcat–port–number>/<Archive Services Virtual Directory>/archivelink/<name‑of‑repository>?serverInfo&pVersion=0045.

The output that is displayed should list all the archives configured in the repository.

Note: By default, any warnings or errors will appear in <Tomcat‑Installation‑Directory>\webapps\<Archive Services–Virtual–Directory>\WEB‑INF\logs\alserver.log.

Defining an ArchiveID in WebAdmin1. Connect to WebAdmin, and log in to the appropriate repository. Typically, the URL

to access WebAdmin is as follows:http://<server>:<Tomcat‑port‑number>/<Archive Services for SAP‑virtual‑directory>/jsp/login.jsp<Archive Services for SAP‑virtual‑directory> refers to the virtual directory that youdefined previously (refer to Installing the EI Core docapp file, page 31).

2. Click ArchiveLink.Ensure that the Archives tab is open.

3. From the Choose an Archive: drop‑down list:• Select Create a New Configuration

or• Select an existing archive to view or edit it.



The archive configuration page opens in the right pane.

Note: If you do not wish to create a new archive, you can also copy an existingarchive and name it differently.

To copy an archive, perform the following tasks:

1. Select an existing archive to edit it.

2. Click Copy.

3. In the Explorer User Prompt dialog box that appears, type a new name for thearchive.

4. Click OK.

The copied archive is now available for you to view or edit.

Skip to step 5 to know what parameters can be configured for the archive.

4. If you are creating a new archive, in the New Archive’s Name: field, type a namefor the archive.If you’re viewing or editing an existing archive, skip to step 5.

5. The following parameters can be configured.

Table 3. Parameters in archives’ configuration page

Fieldname Description

Archive ID Name of the SAP archive (as defined inthe OAC0 — Defining a Logical ArchiveIDin SAP section of the ConfiguringSAP R/3 for Archive Services for SAPdocument).

SAP Document Type Set to NONE (HTTP provided).

Documentum Type Specifies the Documentum documenttype. Refer to the Configuring theRepository Document Type section of theArchive Services for SAP AdministrationGuide.

Attribute Map The attribute map is used to define theDocumentum attributes of an archiveddocument.

There is a special attribute “FOLDER”that can be configured. To specify thefolder path, use the following format:ʺFOLDER=ʺ/SAP/Archive/AAʺ



Fieldname Description

In the Attribute map, you can also setthe following attributes:

• a_storage_type• a_retention_date

Note: For more information, refer to theSetting EMC Centera‑related Attributes inArchive Services section of the ArchiveServices for SAP Administration Guide.

6. To save the archive configuration, click Save.

Note: The aim of this exercise is to test if the installation has been successful; therefore, ifan existing archive is available for reuse, it is not necessary to create a new archive fortesting purposes. However, if you wish, you may create a new archive or reuse anyArchiveID that has been created previously.

Defining a logical ArchiveID in SAPLogical ArchiveI,Ds are created in SAP using the SAP GUI. The name of the logicalArchiveID must be the same as the ArchiveID created using WebAdmin in Defining anArchiveID in WebAdmin, page 56.

To define a logical ArchiveID in SAP:

1. Execute the following transaction in the transaction code field: oac0.

2. In the Display Content Repositories: Overview page, click on any contentrepository (specifically whose Storage type is HTTP content server).

3. In the Display Content Repositories: Detail page, click the Display/Change iconThe Copy as ... button is now enabled.

4. Click the Copy as ... button.

5. Edit the Content Rep. field so that it’s the same as ArchiveID created usingWebAdmin.

6. In the Transfer drctry field, enter the directory path where SAP can write the PrintList until it is in the Storage Queue.

7. In the HTTP Server field, type your system name.

Note: You are recommended to type the IP address of your system in this field.



8. In the HTTP Script field, type the following:/<Archive Services Virtual Directory>/archivelink/<nameofrepository>

9. To save the logical ArchiveID configuration, choose Content Repository > Save.

Testing connection between SAP and ArchiveServices

1. Execute the following transaction in the transaction code field:oac0

2. In the Display Content Repositories: Overview page, click on any contentrepository (specifically whose Storage type is HTTP content server).

3. In the Display Content Repositories: Detail page, click Test connection.An information messages appears at the bottom of the page, indicating that theconnection test has been successful.

Creating a Document Type in SAPTo fully test the archival and retrieval cycle, a simple Print List can be configured byfollowing the instructions give below:

1. Execute the following transaction in the transaction code field: oac3.The Display View “Links for Content Repositoriesʺ: Overview screen appears.

2. Select Table View > Display > Change.

3. From the list, select any item with the ObjectType SOOD.

4. Click the Copy As ... icon and execute.

5. In the page that appears, enter any piece of text starting with the alphabet Z in theDocument type field.Thus, Z<Your Text> will be the document type.

6. In the Storage system field, enter the name of the logical ArchiveID that you createdearlier (refer to Defining a logical ArchiveID in SAP, page 58), where the documentswill be archived.

7. Save your changes.



Archiving a Print List1. Execute the following transaction in the transaction code field: f.21.

2. Click Execute.

3. In the List of Customer Open Items page that appears, choose List > Print.The Print Screen List dialog box appears.

4. Click Properties.The Spool Request Attributes dialog box appears.

5. In the Parameters name column, click Output Options.

6. From the Storage Mode drop‑down menu, select Archive only.

Note: Whenever you edit a parameter in this dialog box, we recommend that youcheck the Show Selected Print Parameters on Initial Screen checkbox. This ensuresthat the customized settings are available in the initial Print Screen List dialog box.

7. Set the Object Type to SOOD.

8. In the Document Type field, type the document type you created earlier (Creating aDocument Type in SAP, page 59) and execute it.

9. Type additional information in the Information field.This label may be anything you wish; for example, your initials.

10. Optionally, type a description of the Print List in the Text field.

11. In the Parameter name column, select General attributes > Time of printing.

12. From the Time of print drop‑down list, select Print out immediately.

13. Click Continue in the Spool Request Attributes dialog box.

14. Click Continue in the Print Screen List dialog box.

15. Execute the following transaction in the transaction code field: oam1 to view thestatus of the document in the storage queue.The ArchiveLink Monitor screen appears.The Print List is now queued, waiting for the scheduler to pick it up and transfer itto the archive.The OAAT ‑ Scheduling Jobs section of the Configuring SAP R/3 for Archive Services forSAP document contains information about configuring the ArchiveLink scheduler.

16. To accelerate the transfer of the Print List from the queue to the archive in therepository, click Storage Queue.The Queue: Content server (CARA) screen appears. You should now see an entryfor the newly‑archived Print List in this screen.



17. To view the archiving parameter details, double‑click the Print List entry.The Archiving request window opens.Verify that the details are correct

18. To archive the Print List in an archive located in a repository, click Execute.You should see a confirmation message that the queue has been processed.If no errors occur, you can continue testing by displaying the archived Print List.

Viewing a Print ListTo view the Print List, do one of the following:

1. In a Documentum client (Webtop or Desktop), directly locate to the ArchiveIDcreated previously in the repository (see Defining an ArchiveID in WebAdmin,page 56).

2. Execute the following transaction in SAP in the transaction code field: oadd.In the ArchiveLink: Hit List for Stored Print Lists page for a particular item, selectPrint List > Display From Content Server.SAP executes the GET command to retrieve the document from the Documentumarchive. The retrieved document has the DocumentID of the Print List inDocumentum.




Chapter 5Troubleshooting Installation Issues

OverviewThis chapter discusses commonly encountered issues in Archive Services and how youcan resolve them. The topics covered in this chapter as follows:

• High levels of logging, page 63• Incorrect Tomcat installation, page 64

High levels of loggingYou may encounter high levels of logging if the logging parameter for Archive Serviceshas been set as DEBUG or WARN. By default, this parameter is set as WARN. If you hadset the logging parameter as DEBUG, Archive Services documents logs each and everyrequest; in a production environment, this can translate into a extremely high logginglevels. This causes the following problems:

• Because Archive Services writes each and every request to a log, this take upenormous storage space in a production environment.

• High levels of logging penalize the performance of the host in a productionenvironment.

When the logging level is set to DEBUG, Archive Services writes certain parametersof each request to memory. With each request, the amount of memory used byArchive Services increases incrementally. This leads to a performance penalty.

To change the logging level:

1. Open the log4j.properties file.In Windows, this file is usually available in the following location:<Tomcat‑Installation‑Directory>\webapps\<Archive Services–Virtual–Directory>\WEB‑INF

2. Locate the following parameters:#log4j.logger.com.documentum.ei=WARN

#log4j.logger.com.documentum.ei=INFO#log4j.logger.com.documentum.ei=DEBUG


Troubleshooting Installation Issues

Note: Depending on the setting for logging levels in your environment, one of theparameters indicated above will not be commented (the hash symbol (#) will notprecede the parameter). By default, the logging level is set as WARN.

3. Depending on what level of logging you want, do not comment the required loggingparameter.Ensure that the other two parameters are commented.

Example 51.If you want to set the logging level as INFO, edit the logging parameters as follows:

#log4j.logger.com.documentum.ei=WARNlog4j.logger.com.documentum.ei=INFO#log4j.logger.com.documentum.ei=DEBUG

4. Save the file.

Note: Setting the logging level as DEBUG is only necessary when you need totroubleshoot any issues with Archive Services. In a production environment, the DEBUGlogging parameter in Archive Services should be commented to turn it off.

Incorrect Tomcat installationAfter installing Archive Services, when you connect to WebAdmin for the first time, youmight get a JSP error. When you analyze the technical information displayed with theerror message, you can following informational line:Unable to find a javac compiler; com.sun.tools.javac.Main is not on theclasspath.

This error message is displayed because you chose the JRE option, and not the J2SEoption, in the Tomcat installation wizard.

To resolve this issue:• Download and install a full J2SE/JDK on a local machine.• Copy the tools.jar from the following directory:

<J2SE‑Installation‑Directory>/lib• Paste it to the following directory:

<Tomcat‑Installation‑Directory>/common/lib



• Restart Tomcat.




Chapter 6Uninstalling Archive Services for SAP

OverviewUninstalling Archive Services consists of the following high‑level tasks; each of thesetasks, in turn, are procedures containing low‑level tasks:

1. Preuninstallation tasks, page 67

2. Uninstalling Archive Services for SAP, page 68

3. Uninstalling RFC archiving services, page 69

Preuninstallation tasks

Overview

This section contains the following topics:• Preparing application servers for Archive Services for SAP uninstallation, page 67• Removing RFC Windows services, page 69

Preparing application servers for Archive Services forSAP uninstallation

• Close all browser sessions that are running WebAdmin.


Uninstalling Archive Services for SAP

• Ensure that the application server is in the correct state.

— Apache Tomcat must be stopped.

— BEA WebLogic must be running.

— IBM WebSphere must be running.

— Oracle Application Server must be running.

— Sun Java System Application Server must be running.

Uninstalling Archive Services for SAPThis section contains the following topics:• Uninstalling using BEA WebLogic, page 68• Uninstalling using IBM WebSphere, page 69

Uninstalling using Apache Tomcat

To uninstall using Apache Tomcat:

1. Stop the Apache Tomcat server.

2. Delete the assap.war file from the <<Tomcat>>/webapps folder.

3. Restart the Apache Tomcat server.

Uninstalling using BEA WebLogicTo uninstall using BEA WebLogic:

1. Start the BEA WebLogic server.

2. Enter your user ID and password.The entries are case sensitive.The BEA WebLogic server window appears.

3. Click Deployments in the left panel.

4. Click Lock & Edit also located in the left panel.

5. Click the Stop tab under Deployments and select Force Stop Now.

6. Click Yes in the Stop Application Assistant screen.



7. Click the Delete tab under Deployments.

8. Click Yes in the Delete Application Assistant screen.

9. Click Activate Changes in the left panel.

Uninstalling using IBM WebSphereTo uninstall using IBM WebSphere:

1. Start the IBM WebSphere server. For example:http://10.31.150.113.9060/ibm/console

2. Enter your user ID.The Integrated Solutions Console screen appears.

3. Expand Applications and click Enterprise Applications.

4. Select assap and click Stop.The message [‑]Messages Application assap on server server1 and nodecmaqaaix113Node01 stopped successfully appears with assap selected for uninstall..

5. Click Uninstall and then OK in the confirmation screen.

6. In theMessages window, click the Save hyperlink to save directly to the masterconfiguration.

Uninstalling RFC archiving services

Overview

This section contains the following topics:• Uninstalling RFC archiving services on Windows, page 70• Uninstalling RFC archiving services on UNIX, page 71

Removing RFC Windows servicesTo remove RFC Windows services:

1. Navigate to the temporary directory where you extracted the contents of the RFCinstaller archive.



2. In the temporary directory, double–click the Setup.exe file.TheWelcome page of the installation wizard appears. Click Next.The Setup Type page appears.

3. To remove RFC services, select Service Remove, and click Next.

4. In the page that appears, type the name of the repository from where you wantto remove RFC services.Click Next.The Delete Service: SAP RFC Destination page appears.

5. Type the SAP RFC destination of the RFC service that you want to remove andclick Next.The Ready to delete service(s) page appears.

6. Verify the summary and click Next.The required RFC services are removed.A confirmation dialog box appears.

7. Do one of the following:• If you want to remove another service, click Yes and repeat steps 3–6 for the

required services.• If you do not want to remove another RFC service, click No.

The Setup Complete dialog box appears.8. Click Finish.

Uninstalling RFC archiving services on WindowsTo uninstall RFC archiving services from Windows hosts:

1. In the system where RFC archiving services is installed, open Add/RemovePrograms from Control Panel, select EMC Documentum Archive Services forSAP (RFC), and click Change/Remove.

2. The Confirm File Deletion dialog box appears asking you to confirm the action.Click Yes.

3. The uninstaller runs. A confirmation window appears indicating that RFC archivingservices has been uninstalled successfully.

4. Click OK.



Uninstalling RFC archiving services on UNIXTo uninstall RFC archiving services on UNIX:

1. Stop the dmarchivelink process.

2. Delete the dmal folder that you created when installing RFC archiving services (referto Installing RFC components on UNIX, page 39).




Appendix A

Advanced Installation Option for LoadBalancing

OverviewArchive Services may be installed on a Tomcat server where Apache (refer to InstallingApache, page 73) and Tomcat (refer to Installing Tomcat, page 26) are configured to useload‑balancing between multiple Tomcat sessions. This configuration is particularlypowerful when used in tandem with multiple Tomcat hosts. Use mod‑jk (refer toInstalling connectors for Apache and Tomcat, page 74) as a connector for communicationsbetween Apache and Tomcat.

This section contains the following topics:

• Installing Apache, page 73• Installing connectors for Apache and Tomcat, page 74• Guidelines for configuring Apache and Tomcat for load balancing, page 74

Installing TomcatInstalling Tomcat, page 26 contains detailed information on installing and configuringTomcat for the purposes of Archive Services.

Installing ApacheNote: If you do not intend to install Archive Services in a load balancing scenario, skip toPreparing Tomcat, page 26.

If your installation scenario (refer to Installation scenarios, page 19) is based on a loadbalancing configuration, you should install Apache. For installation, configuration, andadministration instructions, refer to the documentation available in Apache’s Web site(http://httpd.apache.org).


http://httpd.apache.org

Advanced Installation Option for Load Balancing

Installing connectors for Apache and TomcatIf your installation scenario (refer to Installation scenarios, page 19) is based on a loadbalancing configuration, in addition to installing Apache, you must download (from theWeb) and install mod_jk, a plug‑in that handles the communication between Apacheand Tomcat.

For detailed installation, configuration, and administration instructions, refer to thedocumentation available in Tomcat’s Web site (http://jakarta.apache.org/tomcat/).

Guidelines for configuring Apache and Tomcatfor load balancing

Use the following steps as broad guidelines while configuring Apache andTomcat for advanced scalability. For detailed information, please referto the specific documentation available in the Jakarta project’s website:http://jakarta.apache.org/tomcat/connectors‑doc/config/workers.html

• Obtain the installation file for Tomcat 5.0.28 (or higher) from the Web and installthe same.

Depending on your load balancing requirement, install Tomcat on two or more hosts.• Obtain the installation files for Apache from the Web and install the same.• Obtain the installation files for mod_jk, a plug‑in that handles the communication

between Apache and Tomcat, from the Web and install the same.• In Apache:

— Edit the Apache configuration file (httpd.conf).

Provide the path to the plug‑in (mod_jk) in this file.

— Create a workers.properties file. In this file:

— The number of workers that you create should be equal to the number ofTomcat instances that have been installed.

— Specify the percentage of load that will be balanced by each worker.


http://jakarta.apache.org/tomcat/

http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html


• In each Tomcat instance, edit server.xml to disable the stand‑alone configuration.

This ensures that each Tomcat instance is a worker that is running to perform Servletrequests coming from Apache.

You now have a working load balancing configuration using Apache and Tomcat.




Index

8080, port used by Tomcat for ArchiveServices, 26

9080, port used by Tomcat for ContentServer, 26

Aa_retention_date, 58a_storage_type, 58Administrative Console, 15advanced scalability options, 20, 73

configuring, see load balancing usingApache and Tomcat, configuring

al.properties, 36configuring in UNIX, 47configuring in Windows, 47configuring postinstallation, 47directory path, 47docbases.numberOfConnections, 48numberOfDocbases, 48

ALF class, 15ALF format, 15all‑in‑one installation, 20Apache, 74

configuration file, 74configuration file, httpd.conf, 74installing, 73workers.properties file, 74

Apache and Tomcat for load balancing,configuring, 74

Apache TomcatJava heap size, 25verifying, 27

application server host requirementsJava heap size, 25

application serverstemporary disk space requirements, 25

Archive Services, 9installing, 19integration with EMC Centera, 22 to 23

obtaining latest copy of, 30uninstalling, 67 to 68

Archive Services for SAP, 9defined, 13upgrading, 51

archived data, 15ArchiveID, 57

defining in WebAdmin, 56ArchiveLink Monitor window, 60Archiving request window, 61archiving.tempDir

customizing in Windows, 47archiving.upload.tempDir

customizing in UNIX, 47Attribute Map, 58attributes

a_retention_date, 58a_storage_type, 58EMC Centera‑related, 58in dfc.properties, cache_queries, 49in dfc.properties, local_diskfull_limit, 49in dfc.properties, local_purge_on_

diskfull, 49in dfc.properties, max_session_count, 49

BBEA WebLogic, 28

development mode, 28domains, 27HP‑UX, 28installation owner, 28Java heap size, 25Managed Server environments, 28Managed Servers, 27MaxPermSize parameter, 28performance tuning, 29port numbers, 28server aliases, 27


Index

Ccache_queries, 49class

ALF, 15FAX, 15OTF, 15REO, 15

configuration fileApache, 74

configuration file, httpd.confApache, 74

configuration procedures, 42configuring

al.properties in UNIX, 47al.properties in Windows, 47al.properties, postinstallation, 47Apache and Tomcat for advanced

scalability, see load balancing usingApache and Tomcat, configuring

Apache and Tomcat for load balancing, 74archive parameters, 57Archive Services, postinstallation, 42Content Server, 23Content Server and Archive Services for

production environment, 24Content Server and Archive Services for

test environment, 24Content Server, express configuration, 23Content Server, repository size —

MEDIUM 180MB, 24HP‑UX to run Java server in production

mode, 27load balancing using Apache and Tomcat,

configuring, 74repository size, MEDIUM 180MB, 24RFC services, 43RFC, postinstallation, 43Tomcat on UNIX, 27

connectionbetween SAP and Archive Services,

testing of, 59connection broker, 42connections, setting up repository, 55connectors for Apache and Tomcat

installing, 74Content Server

configuration program, see ServerConfiguration Program

configuring, 23

express configuration, 23installing, 22Tomcat, 23

Content Server and Archive Servicesconfiguring for production

environment, 24configuring for test environment, 24

Content Services, 39 to 40, 45Content Services for EMC Centera,

enabling, 22 to 23Content Services for SAP 5.2.5 SP3

WebAdmin, 55creating

connections to EMC Centera, 24document type, 59RFC services, 37

customizingarchiving.tempDir in Windows, 47archiving.upload.tempDir in UNIX, 47dfc.properties, 48

Ddatabases

installing, 22DB2, 22DEBUG

logging level, 63turning off, 63

definingArchiveID in WebAdmin, 56logical ArchiveID in SAP, 58

development mode, 28dfc.properties, 36

cache_queries, 49customizing, 48docbases.numberOfConnections, 48local_diskfull_limit, 49local_purge_on_diskfull, 49max_session_count, 48opening in UNIX, 48opening in Windows, 48path in UNIX, 36path in Windows, 36

dfc.properties file, 40, 42disk space requirements, 25displaying

repository configurations, 56dmal directory, 39dmal.ini file, 40, 45


Index

dmarchivelink program, 40docbases.numberOfConnections, 48docbases.properties, 36document

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

document formats, supported in SAP, 15document type

creating, 59DocumentID, 61Documentum Client Library, see DMCLDocumentum document type, see

Documentum TypeDocumentum Download Center, see

SubscribenetDocumentum Type, 57domains, BEA WebLogic, 27

EEMC Centera, see EMC Centera

creating connections to, 24integration with, installation scenario, 20

EMC Centera, enabling Content Servicesfor, 22 to 23

EMC Centera‑related attributes, 58Enabling

Content Services for EMC Centera, 22 to23

ensuringthe working of repository, 24

excessive logging, troubleshooting, 63express configuration, Content Server, 23

Ff.21, 60FAX class, 15format

ALF, 15PDF, 15REO, 15Tiff, 15

Ggeneral prerequisites, 21

HHP‑UX, 28

configuring to run Java server inproduction mode, 27

HTTP Archiving Server, 14httpd.conf, 74

IIBM WebSphere

Java heap size, 25preinstallation requirements, 29root user, 29

install, 39 to 40installation

requirements, 9testing, 55troubleshooting issues, 63

installation ownerBEA WebLogic, 28

installation prerequisites, see installing,prerequisites

installation scenarios, 19advanced scalability options, 20, 73all‑in‑one installation, 20integration with EMC Centera, 20separate Archive Services, 20

installingadvanced scalability options, see

installation scenarios, advancedscalability options

all‑in‑one installation, see installationscenarios, all‑in‑one installation

Apache, 73application server software, 25Archive Services, 19connectors for Apache and Tomcat, 74Content Server, 22databases, 22integration with EMC Centera, see

installation scenarios, integrationwith Centera

mod_jk, 74on Windows, 31 to 32prerequisites, 21RFC components, 37scenarios, see installation scenariosseparate Archive Services, see installation

scenarios, separate Archive ServicesSolaris, 31 to 32


Index

Tomcat, 26integration with EMC Centera, 20intended audience, 9

JJava

heap size, 25

Lload balancing, see advanced scalability

optionsload balancing using Apache and Tomcat,

configuring, 74local_diskfull_limit, 49local_purge_on_diskfull, 49log4j.debug, 63log4j.properties

directory path in Windows, 63log4j.debug, 63turning off DEBUG, 63

Log4j.properties, 36logging level, DEBUG, 63logical ArchiveID, defining in SAP, 58

Mmax_session_count, 48maximum number of sessions, 48MaxPermSize parameter on BEA

WebLogic, 28MEDIUM 180MB, 24mod_jk

installing, 74utility, 74

Nnumber of connections established by

repository, 48number of repositories installed, 48number of workers, workers.properties

file, 74numberOfDocbases, 48

Ooac0, 57 to 59oac3, 59oadd, 61

oam1, 60ObjectType, SOOD, 59obtaining

latest copy of Archive Services, 30opening

dfc.properties in UNIX, 48dfc.properties in Windows, 48

Oracle, 22Oracle Application Server

Java heap size, 25OTF class, 15out of memory errors, 25

Pparameters in archives configuration

page, 57PDF format, 15percentage of load, workers.properties

file, 74performance

tuning, 29plug‑in, mod_jk, see mod_jkport numbers

BEA WebLogic, 28postinstallation configuration, 42preinstallation requirements

application server software, preparing, 25HP‑UX with BEA WebLogic 8.1, 28IBM WebSphere, 29Java heap size, 25Sun Java System Application Server, 29temporary disk space, 25WebLogic domain, 27

preinstallation tasks, 67preparing

Tomcat for installing Archive Services, 26prerequisites

general, 21installing, 21software, 21system administrator, 9

Print Listsending, 60viewing, 61

Print Lists, 15ALF class, 15ALF format, 15

production environment


Index

configuring Content Server and ArchiveServices for, 24

production mode, configuring HP‑UX to runJava server in, 27

Purpose of the Guide, 9

RREO class, 15REO format, 15Reports, see Print Listsrepository

displaying configurations, 56ensuring the working of, 24number of connections established by, 48number of, installed, 48setting up connections, 55testing connections, 56

repository size, MEDIUM 180MB, 24request handler program, 40RFC

configuring, postinstallation, 43creating services, 38installing components, 37uninstalling services, 69

RFC components, 37RFC services, 38, 43, 69root user, 29

SSAP

defining logical ArchiveID in, 58Print List, sending, 60supported document formats in, 15transaction code, f.21, 60transaction code, oac0, 57 to 59transaction code, oac3, 59transaction code, oadd, 61transaction code, oam1, 60

SAP Document Type, 57SAPGUI

ArchiveLink Monitor window, 60Archiving request window, 61Test connection button, 59Transfer drctry field, 58

SAPINFO, 40scenarios, installation, 19

advanced scalability options, 20, 73all‑in‑one installation, 20

integration with EMC Centera, 20separate Archive Services, 20

sending, Print List, 60separate Archive Services, 20server aliases, BEA WebLogic, 27Server Configuration Program, 23server.xml, 75setting

repository connections, 55setting attributes, EMC Centera‑

related, 58significant system files, 35software prerequisites, 21SOOD, ObjectType, 59SQL Server, 22Subscribenet, 30Sun Java System Application Server

preinstallation requirements, 29root user, 29

supported databases, 22DB2, 22Oracle, 22SQL Server, 22Sybase, 22

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

Sybase, 22system administrator, 9

prerequisites, 9system files, significant, 35

Ttemporary disk space requirements, 25Test Connection, 56Test connection button, SAPGUI, 59test environment

configuring Content Server andArchive Services for, 24

testingconnection between SAP and Archive

Services, 59installation, 55


Index

repository connections, 56Tiff format, 15Tomcat, 74

configuring on UNIX, 27installing, 26port 8080, 26port 9080, 26preparing for installing Archive

Services, 26scaled‑down version of, 23server.xml, 75used by Content Server, 23

transaction codef.21, 60oac0, 58 to 59oac3, 59oadd, 61oam1, 60

transaction code, oac0, 57Transfer drctry field, 58troubleshooting

excessive logging, 63installation issues, 63

turning off DEBUG, 63

Uuninstalling

Archive Services, 68RFC services, 69

uninstalling, Archive Services, 67UNIX

configuring al.properties in, 47opening dfc.properties in, 48

upgradingArchive Services for SAP, 51

Vviewing

Print List, 61

WWebAdmin, 15

Content Services for SAP 5.2.5 SP3, 55defining ArchiveID in, 56

Windowsconfiguring al.properties in, 47opening dfc.properties in, 48

workers.properties file, 74number of workers, 74percentage of load, 74
