EMC Documentum ArchiveServicesforSAP · PDF fileArchiveServicesforSAP Version7.2 InstallationGuide EMCCorporation ... • Enterprise_Integrations_SAP_ILM.zip—ContainstheASSAPILMapplication,whichincludes

EMC® Documentum®

Archive Services for SAPVersion 7.2

Installation Guide

EMC CorporationCorporate Headquarters:

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

Legal Notice

Copyright © 2005–2016 EMC Corporation. All Rights Reserved.

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 CORPORATIONMAKES 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. Adobe and Adobe PDFLibrary are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarksused herein are the property of their respective owners.

Documentation Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you have feedbackabout how we can make our documentation better or easier to use, please send us your feedback [email protected].

Table of Contents

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

Chapter 1 Preparing to Install Archive Services for SAP .............................................. 9General prerequisites ......................................................................................... 9Software prerequisites ....................................................................................... 9Installation scenarios ......................................................................................... 9All-in-one installation ................................................................................... 10Separate AS SAP .......................................................................................... 10Integration with EMC Centera....................................................................... 10Advanced scalability options for Tomcat server .............................................. 10

Installing required EMC Documentum software ................................................. 10Installing EMC Documentum Administrator .................................................. 11

SAP R/3 or ECC server (UNIX or Windows) ....................................................... 11Preinstallation checklist .................................................................................... 11

Chapter 2 Installing Archive Services for SAP ............................................................. 13Preparing the repository ................................................................................... 13Creating connections to EMC Centera ................................................................ 13Preparing the application server host ................................................................. 13Ensuring sufficient temporary disk space on the host ...................................... 13Ensuring the Java heap size is sufficient ......................................................... 14Supported operating systems and application servers ..................................... 14

Obtaining current version software from Documentum DownloadCenter.............................................................................................................. 14Installing Enterprise Integration Core DAR file................................................... 14Installing WebAdmin in Documentum Administrator......................................... 16Deploying the assap.war file.............................................................................. 17Deploying assap.war using Apache Tomcat.................................................... 17Deploying assap.war using Sun One Application Server /Sun GlassFish Enterprise Server ................................................................................... 18Deploying assap.war on BEAWeblogic .......................................................... 19Deploying assap.war on IBMWebSphere ....................................................... 20ClassLoader setting .................................................................................. 21

Deploying assap.war on JBoss Application Server........................................... 21Editing and viewing the al.properties file using JConsole ................................ 21Configuration for Apache Tomcat .............................................................. 21Configuration for BEAWeblogic................................................................ 22Configuration for IBMWebSphere ............................................................. 22Editing al.properties using JConsole .......................................................... 22

Significant system objects .............................................................................. 23dfc.properties ........................................................................................... 23log4j.properties ........................................................................................ 23docbases.properties .................................................................................. 23al.properties ............................................................................................. 23

EMC Documentum Archive Services for SAP 7.2 Installation Guide 3

Table of Contents

Postinstallation configuration ............................................................................ 24Configuring the temporary store ................................................................... 24Customizing the dfc.properties file for optimum performance ......................... 24

Archive Services for SAP ILM extension, installation, and configuration .............. 25Setup for AS SAP ILM extension.................................................................... 25WebDAV service configuration ...................................................................... 26Configuring dfc.properties ........................................................................ 27Configuring web.xml ................................................................................ 27Copying the required JAR files .................................................................. 28Copying AS SAP ILM namespace JAR file to dmWebDAV .......................... 28Configuring the Administrative User for SAP ILM ..................................... 28

Enabling Privileged DFC on WebDAV for RPS ............................................... 29Installing the Enterprise_Integrations_SAP_ILM.dar file ................................. 29Dar installation objects for AS SAP ILM extension ...................................... 29

Creating default objects for AS SAP ILM extension WebDAVcustomization using ConfigSAPILM tool........................................................ 30DmSapILM.properties customization............................................................. 31EMC Centera integration with ILM................................................................ 32To verify details of clips stored on EMC Centera ............................................. 33

Installing PrintList Transformation Filters .......................................................... 33On-demand rendering compared with stored rendering ................................. 33Configuring EMC Documentum Content Server for on-demandrendering ..................................................................................................... 34

Chapter 3 Upgrading Archive Services for SAP ........................................................... 35Upgrading from AS SAP 5.3 SPx........................................................................ 35Upgrading from AS SAP 6.0, 6.0 SP1 ................................................................. 35Upgrading from AS SAP 6.5 SPx, 6.7, 6.7 SPx, 7.0, to 7.2 ...................................... 36Additional steps to upgrade Archive Services for SAP ........................................ 36

Chapter 4 Testing the installation ................................................................................ 39Logging in to WebAdmin through Documentum Administrator.......................... 39Configuring HTTP repositories for archive linking.............................................. 40Creating an archive in WebAdmin ..................................................................... 41Defining a logical ArchiveID in SAP .................................................................. 42Testing the connection between SAP and AS SAP ............................................... 43Creating a Document Type in SAP ..................................................................... 43Archiving a PrintList ........................................................................................ 43Viewing a Print List .......................................................................................... 45

Chapter 5 Troubleshooting installation issues ............................................................ 47High levels of logging ....................................................................................... 47Incorrect Tomcat installation ............................................................................. 48Performance issues with ACS ............................................................................ 48Inability to perform certain operations when using Archive Servicesfor SAP on IBMWebsphere 5.1.1.9 ..................................................................... 48Unable to create a repository in Webadmin if the archivelink.key fileis not found...................................................................................................... 49

Chapter 6 Uninstalling Archive Services for SAP ........................................................ 51Preparing application servers for AS SAP uninstallation ..................................... 51

4 EMC Documentum Archive Services for SAP 7.2 Installation Guide

Table of Contents

Uninstalling AS SAP using Apache Tomcat ........................................................ 51Uninstalling AS SAP using BEAWeblogic .......................................................... 51Uninstalling using IBMWebSphere ................................................................... 52

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

Appendix B Installing a DAR file using the DAR Installer GUI ........................................ 55


Table of Contents

List of Tables

Table 1. Parameters in archives’ configuration page............................................................. 41Table 2. DAR Installer fields .............................................................................................. 56


Preface

Purpose of this guideThis guide explains how to install and configure Archive Services for SAP (AS SAP) 7.2. It containsinformation about installation requirements, and provides task-based instructions for installingthe software.

Intended audienceThis manual is primarily intended for qualified consultants and system administrators. This rolecovers those who install and configure AS SAP.

The AS SAP application integrates two enterprise-level software packages: the EMC Documentumcontent management system with the SAP R/3 or ECC system. AS SAP requires detailed knowledgeof the SAP DMS and ArchiveLink interfaces. Consultants and system administrators must haveexperience with the software products listed in the ’Archive Services for SAP System Requirements’chapter of the EMC Documentum 7.2 Environment and System Requirements Guide.

Revision history

Revision date Description

May 2016 Initial publication

Typographic conventions

Convention Description

> Represents a pop-up or pull-down menu.

<Text enclosed within angle brackets> Represents a variable name for which you must providea value, or a defined term.

Information in this fontRepresents code samples, user input, and computeroutput.


Preface

Convention Description

[] square brackets Used in method command syntax specifications, squarebrackets indicate an optional argument.

{} curly brackets Used in method command syntax specifications, curlybrackets indicate an optional argument that can berepeated more than once.

Related documentationThis manual forms part of a documentation suite designed to support those who install, configure,and use AS SAP. The product and documentation suite available for download from EMC OnlineSupport (https://support.emc.com).

AS SAP — Documentation suite

Title Description Target role

EMC Documentum ArchiveServices for SAP Release Notes

Provides an overview ofnew and amended features,known bugs, limitations, anddocumentation correctness andclarifications.

Standard User, SystemAdministrator, SystemAdministrator (SAP), andArchive Services Administrator

EMC Documentum ArchiveServices for SAP InstallationGuide

Provides the procedures forinstalling Archive Services.

System Administrator

EMC Documentum ArchiveServices for SAP ConfigurationGuide

Describes the configurationtasks that need to beperformed in SAP to enablecommunication between SAPand Archive Services.

System Administrator (SAP)

EMC Documentum ArchiveServices for SAP AdministrationGuide

Describes the procedure toconfigure Archive Servicesusing the WebAdmin tool.

Archive Services Administrator

EMC Documentum ArchiveServices for SAP User Guide

Describes how SAP users viewdocuments using SAP GUI.

Standard User

Note: AS SAP extensively uses the SAP ArchiveLink component. The SAP ArchiveLinkdocumentation provides information on how you can perform advanced tasks.


https://support.emc.com

Chapter 1Preparing to Install Archive Servicesfor SAP

This chapter provides information about preparing to install AS SAP.

General prerequisitesTo install AS SAP, you must have administrative experience with the software products listed in theEMC Documentum 7.2 Environment and System Requirements Guide.

Note:• Unless you have the prerequisite experience, EMC Documentum recommends that you do notperform installations using only EMC Documentum manuals as guidance.

• EMC Documentum Support can assist you only with systems that were installed by qualifiedpersons following the specific instructions outlined in both the documentation and the trainingmanual.

Software prerequisitesAS SAP depends on specific versions of Documentum and third-party products, as described in the’Archive Services for SAP System Requirements’ chapter of the EMC Documentum 7.2 Environment andSystem Requirements Guide.

Installation scenariosAS SAP may be installed in various configurations, depending on how it is mixed and matchedwith content addressed storage systems such as EMC Centera® or third-party applications such asApache and Tomcat. Different configurations may also be arrived at depending on how and wherethe content server and AS SAP are installed. The possible basic configurations are described inthe following sections.


Preparing to Install Archive Services for SAP

All-in-one installation

Youmay install the repository, Application Server (for example, Tomcat), DocumentumAdministrator(DA), and AS SAP on one system. This installation scenario is supported on all the operating systemsthat are supported by AS SAP. Information on the operating systems that AS SAP supports isprovided in the EMC Documentum 7.2 Environment and System Requirements Guide.

Separate AS SAP

In this installation configuration, AS SAP need not be installed on the same system where therepository is installed. You can install Content Server and DA on one system (running any OS). Onanother supported Operating System, you can install JDK, a supported Web Application Server, suchas Tomcat or BEA Weblogic, and AS SAP (running any OS). AS SAP may be configured to access therepository that is installed on the other machine.

Integration with EMC Centera

AS SAP integrates with EMC’s content addressed storage system, EMC Centera. Customers usingAS SAP along with EMC Centera can formulate rules that determine where information is archived,and how long it is retained.

For EMC Centera connectivity, configure the Documentum server to use a CA store, as described inthe EMC Documentum Content Server Administration Guide.

Advanced scalability options for Tomcat server

AS SAP may be installed on a Tomcat server. Tomcat can be configured to use load balancing betweenmultiple Tomcat sessions. This configuration is particularly powerful when used in tandem withmultiple Tomcat hosts. Use mod-jk as described in Installing connectors for Apache and Tomcat,page 53, as a connector for communications between Apache and Tomcat.

Appendix A, Advanced Installation Option for Load Balancing contains more information oninstalling AS SAP on a Tomcat server in a load-balancing configuration.

Installing required EMC Documentum softwareThis section contains information about EMC Documentum software that you must install priorto installing AS SAP.



Installing EMC Documentum Administrator

After you install the database and Documentum Content Server, install Documentum Administratoras documented in the EMC Documentum Administrator Deployment Guide.

After the Documentum Administrator installation is complete, install AS SAP as described inInstalling Archive Services for SAP.

SAP R/3 or ECC server (UNIX or Windows)Manual configuration of SAP ArchiveLink is a prerequisite for installation of AS SAP, as described inthe EMC Documentum Archive Services for SAP Configuration Guide.

Caution: Documentum is not responsible for problems encountered during installation due toSAP-related issues, such as empty or wrongly configured tables, required support packages, hotfixes, or OSS Notes. Documentum requires that you read and apply all ArchiveLink-related OSSNotes and patches prior to AS SAP installation. Documentum support is not responsible foranswering SAP configuration questions or problems.

Preinstallation checklistYou must follow the information in the preinstallation checklist before you install AS SAP. If thepreinstallation tasks are not done, your system will not function properly:

1. Launch SAP GUI from the intended AS SAP server or client and log in to the SAP system youwant to support. If this test fails, you must resolve the connection between AS SAP and the SAPsystem before proceeding.

2. Be sure all previous versions of AS SAP is either physically removed or deactivated.

3. The repository should be up, running, and performing before installing AS SAP. AS SAP requiresa fully functioning repository and writes configuration objects into the chosen repository duringthe install.

4. Create a directory on the SAP server. This directory will be used by SAP to store files temporarilyuntil they are transported into Documentum.

5. Make sure the application server and Documentum Administrator is up and running. WebAdminis installed after installing Documentum Administrator.

Note: Starting from the 6.5 release, the administration console for both AS SAP and CS SAP is thesame. Installing the WebAdmin (packaged as dmei_webadmin.zip) component on DA enables users



to administer both CS SAP and AS SAP. However, CS SAP requires the HVPS component in additionto what AS SAP requires, for executing the DMS related activities.


Chapter 2Installing Archive Services for SAP

This chapter describes the installation process for AS SAP.

Preparing the repositoryThe repository must be up, running, and performing before you install AS SAP. AS SAP requires afully functional repository so that during installation, an SAP cabinet can be created and AS SAPadministration objects can be written to that cabinet in the designated repository.

Creating connections to EMC CenteraIf your installation scenario, as described in Integration with EMC Centera, includes connectionsto EMC Centera, you will have to create CA stores. More information on creating CA stores is inthe ’Creating Content-Addressed Stores’ section of the EMC Documentum Archive Services for SAPAdministration Guide.

Preparing the application server hostThis section contains information about preparing the application server host for use with AS SAP.

Ensuring sufficient temporary disk space on the host

Application servers vary as to how much temporary disk space they require when an applicationis installed. Allow at least half a gigabyte of free disk space on the application server host forinstalling AS SAP:• On Windows hosts, ensure that the free space is on the drive to which the TEMP environmentvariable points.

• On UNIX hosts, ensure that the free space is in $TEMP.

• On AIX with WebSphere, the temporary directory used by WebSphere is /tmp.


Installing Archive Services for SAP

Ensuring the Java heap size is sufficient

Setting the Java heap size appropriately 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

You can install AS SAP on different combinations of operating systems and application servers.More information on supported combinations is in the ’Software requirements’ section of the EMCDocumentum 7.2 Environment and System Requirements Guide.

Obtaining current version software fromDocumentum Download CenterTo ensure that you install the current version of this product, visit the EMC Download Center athttps://EMC.subscribenet.com and review the product versions available for your platform.

For Windows, download Archive_Services_for_SAP_7.2_Windows.zip, which contains the followingfiles:

• Enterprise_Integrations_Core.zip — Contains the Enterprise Integrations Core DAR file andrelevant script files for installing the DAR using the command line.

• dmei_webadmin.zip — Contains the WebAdmin administration component that would beinstalled on DA.

• assap.war — Contains the AS SAP application.

• Enterprise_Integrations_SAP_ILM.zip — Contains the AS SAP ILM application, which includesthe Enterprise_Integrations_SAP_ILM.dar and other related files.

For Solaris, AIX, Linux, HPUX and HPUX IA64, download the respective Archive_Services_for_SAP_7.2_<OS>.tar, which contains the following files:

• Enterprise_Integrations_Core.tar

• dmei_webadmin.tar

• assap.war

• Enterprise_Integrations_SAP_ILM.tar

Installing Enterprise Integration Core DAR fileThis section provides instructions for installing Enterprise_Integrations_Core.dar files on allDocumentum Composer supported operating systems.


https://emc.subscribenet.com


Note: Use the information in this section to install other .dar files.

Ensure that the dfc.properties of the Composer utility includes the Global repository details.

Documentum Composer is located in the system where Content Server 6.5 or above is installed. InWindows OS, you can locate Composer in %DOCUMENTUM%\product\7.2\install\composer onthe system where Content Server is installed. Alternatively, you can also download the latest versionof Composer from the EMC Online Support site (https://support.emc.com).

If the repository used for installing the Enterprise_Integrations_Core.dar files is not a Globalrepository, then install the Enterprise_Integrations_Core.dar files on both the Global repositoryand the repository used for AS SAP.

You can also use the Composer GUI to install DARs. The Composer GUI is specific to the Windowsenvironment. If Content Server is running on an UNIX environment, you can connect to repositoriesfrom the Composer GUI installed on your Windows system after you make the required changes inthe dfc.properties file of Composer.

1. Extract the contents of the following to a temporary directory:• Enterprise_Integrations_Core.zip for Windows

• Enterprise_Integrations_Core.tar for UNIX

The temporary directory will now contain the following files:• dmant.bat (Windows)

• dmant.sh (UNIX/Linux)

• DARInstallScript.xml (composer ANT install script)

• install.properties (installation properties)

• Enterprise_Integrations_Core.dar (DAR filename)

2. You can install the Enterprise_Integrations_Core.dar using the DAR Installer GUI in the Windowsenvironments as described in Installing a DAR file using the DAR Installer GUI. Alternatively,you can also install the DAR file using headless Composer.

3. Follow the steps below to install the DAR file using headless Composer:

a. Update the install.properties file with the repository name, credentials, and the location ofthe DAR file, as follows:• dar.docbase = <repository_name>

• dar.username = <repository_install_owner_username>

• dar.password = <repository_install_owner_password>

• dar.domain = <domain> (optional)

• dar.core.file = <absolute path>

b. The DARInstallScript.xml must have an emc.install ant task for every dar file.

c. Specify the location of the headless Composer and workspace in the dmant.bat file:• Set the ECLIPSE environment variable to the headless Composer directory on yourmachine.

• Set the WORKSPACE environment variable to a clean directory. For example:


https://support.emc.com


echo offsetlocalset ECLIPSE=C:\ComposerHeadlessset WORKSPACE=C:\ComposerHeadless\workspaceset BUILDFILE=%1java -Xmx1024m -XX: MaxPermSize=128m -cp %ECLIPSE%\startup.jar org.eclipse.core.launcher.Main-clean -data %WORKSPACE%application org.eclipse.ant.core.antRunner-buildfile %BUILDFILE%

Note: The Ant tasks do not pick up the settings from the eclipse.ini file. This means thatyou have to set those parameters on the command line when invoking Java.

For UNIX environments, add -Dlogpath=<path> to the Java command.

d. Run the Ant task as follows:• For Windows — <directory path of batch file and xml file>:dmant.bat DARInstallScript.xml

• For UNIX — Change sh script mode:$ chmod a+rx dmant.sh

<directory path of batch file and xml file>$./dmant.sh DARInstallScript.xml

Installing WebAdmin in DocumentumAdministratorTo complete the WebAdmin installation:1. Ensure you have completed all the installation procedures listed earlier in this section before

continuing with this procedure.

2. Extract the content of dmei_webadmin.zip (Windows) or dmei_webadmin.tar (UNIX) to atemporary directory.

3. Copy the dmeiwebadmin folder into the Documentum Administrator (DA) folder that wascreated during the installation of DA.

4. Copy the WEB-INF folder into the DA folder, selecting yes when prompted to overwrite allthe contents of the existing WEB-INF folder.

5. Copy the theme folder inside the custom folder into the DA\custom folder, selecting yes whenprompted to overwrite all the contents of the existing theme folder.

6. Open the file DA\Custom\app.xml in a text editor and make the following change:

<application extends="webtop/app.xml”>

to

<application extends="dmeiwebadmin/app.xml”>

7. Close and save the file.

WebAdmin is ready for use. The EMC Documentum Archive Services for SAP Administration Guide hasadditional information about using WebAdmin to administer your system.



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

To prepare the assap.war file for installation:

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

2. Create a directory named assap.

3. Copy the assap.war file to the assap directory created in step 2.

4. Unjar the file using the following jar command:jar –xvf assap.war

The war file is extracted to the directory named assap.

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

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

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

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

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

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

f. Type the DFC global BOF registry docbase user-encrypted password. For example:dfc.bof.registry.password=kBb9DmXB6pQ\=

6. Based on the operating system being used, edit the log4j.properties to have the correct pathfor the log file.

7. Re-create the assap.war from the temporary folder using the jar -cvf command.

8. Deploy the AS SAP war file using the application server procedure appropriate for yourinstallation.

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 rejarred assap.war file to the <<Tomcat>>/webapps folder.

3. Restart the Apache Tomcat server.



Deploying assap.war using Sun One Application Server/Sun Glass Fish Enterprise Server

To deploy using Sun One Application Server/Sun Glass Fish Enterprise Server:

1. Connect to application server admin page. For example, http://10.8.2.106:4848.

2. Type the Username/Password.

3. Click theWeb Application link.

4. Click the Deploy button to deploy the assap war file by typing the path of the assap war file.

5. Click Next and give ‘assap’ as the Application name and context Root, and click Finish.

6. Add the following permission to the server policy present in the location:SUN_APP_SERVER_DOMAINS_HOME/domains/domain1/server1/config/server.policygrant {permission java.util.PropertyPermission "*", "read,write";permission java.io.FilePermission "${documentum}/-","read, write, delete";permission java.io.FilePermission "${user.home}/-","read, write, delete";permission java.io.FilePermission "/tmp/-", "read, write, delete";permission java.io.FilePermission "${java.io.tmpdir}/-","read, write, delete";permission java.io.FilePermission "$S(INSTANCE_CONFIG_DIRECTORY)/-","read, write, delete";permission java.lang.RuntimePermission "createClassLoader";permission java.net.SocketPermission "*", "connect,accept";Permission java.lang.RuntimePermission "getProtectionDomain";permission java.lang.RuntimePermission "shutdownHooks";permission java.lang.reflect.ReflectPermission "*";permission java.security.AllPermission;};

7. Restart the application server.



Deploying assap.war on BEA Weblogic

Follow the steps 1 through 4 in Deploying the assap.war file and copy all the files to a folder, such asassap.

To deploy on BEA Weblogic:1. Unjar assap.war into a directory named assap, as follows:

jar -xvf assap.war

Note: The directory name is case-sensitive.

Ensure the node manager of the BEA Weblogic domain is active.

2. Start the BEA Weblogic server:http://<ip>:7001/console

3. Type your user ID and password.

The entries are case-sensitive.

The BEA WebLogic server window appears.

4. Click Deployments on the left panel.

5. Click Lock & Edit also located on the left panel.

6. Click Install.

7. Using the Install Application Assistant, locate the assap directory you created in step 1.

Specifying the assap directory installs all components in and below the directory. For example:100.100.100.100/export/home0/bea02/softwares

8. Select the assap directory and click Next.

9. Specify whether to target the installation as ’application.’

10. Click Next.

11. Select the servers and clusters, or both, to which you want to deploy AS SAP.

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

12. Click Next.

13. Optionally, accept the defaults for these settings about the deployment, or update them:

• Deployed Web application name.

• Application security model.

• How the source directory contents were made available to targeted Managed Servers andclusters.

14. Click Next.

15. Review the configuration settings you specified:

• app-root

• /app

• /plan



Note: If you install an application that follows this directory structure and there is no deploymentplan in the /plan directory, the Weblogic server automatically creates a deployment plan for you.

16. Click Finish.

If you chose to immediately go to the deployment’s configuration screen, click tabs to setadditional configuration settings for the Web application. If you chose to change this informationlater, the Administration Console returns you to the Deployments table, which will now includeyour newly installed Web application.

17. Click Activate Changes on the left panel.

This commits all changes.

Note: All changes do not take effect immediately-some require a restart.

Deploying assap.war on IBM WebSphere

To deploy on IBM WebSphere:1. Start the IBM WebSphere server. For example:

http://10.31.150.113.9060/ibm/console

2. Type 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 select Remote filesystem with context root as assap.

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

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

8. In the following screen, select Precompile JavaServer Pages files and type assap as theApplication Name. Click Next.

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

10. In the Provide options to compile JSPs screen, type 15 under JDK source level and click Next.

Note: The JDK source level specifies the level at which the Java compiler compiles JSP Javasources. Valid values are 13, 14, and 15. The default value is 13, which specifies 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.

For WebSphere Application Server Version 7.0, change the context root of application to /assap.

14. Click Finish.

The following message indicates a successful installation.ADMA5013I: Application assap installed successfully



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 hyperlink.

4. In the Class loader order list box, select Class loaded with application class loader first andclick OK.

5. In the next screen, click Save.

6. In theManage Modules screen, assap appears selected in red.

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

Deploying assap.war on JBoss Application Server

To deploy on JBoss:

1. Unjar the rejarred assap.war file using the following command:jar -xvf assap.war

The war file is extracted to a directory called assap.

2. Rename the assap directory to assap.war.

3. Copy the assap.war folder to <<JBOSS_HOME>>\server\default\deploy folder.

4. Restart the application server.

Editing and viewing the al.properties file usingJConsole

This section describes the following procedures that are used for viewing and editing the al.propertiesfile in the JConsole editor without the need for restarting the application server:• Configuration for Apache Tomcat

• Configuration for BEA Weblogic

• Configuration for IBM WebSphere

• Editing properties using JConsole

Configuration for Apache Tomcat

To enable the JMX agent for Apache Tomcat for a Windows environment, add



the following line in the <TOMCAT Home DIR>\bin\catalina.bat file:set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=9999-Dcom.sun.management.jmxremote.authenticate=false-Dcom.sun.management.jmxremote.ssl=false

To enable the JMX agent for Apache Tomcat for a Solaris environment, add the following line inthe <TOMCAT Home DIR>\bin\catalina.sh file:set JAVA_OPTS=$JAVA_OPTS -Dcom.sun.management.jmxremote.port=9999-Dcom.sun.management.jmxremote.authenticate=false-Dcom.sun.management.jmxremote.ssl=false

Configuration for BEA Weblogic

To enable the JMX agent for BEA Weblogic, using the Documentum Administrator Console, add thefollowing line into the field of Arguments under Servers > <Application Server Name> > Server Start:-Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

Configuration for IBM WebSphere

To enable the JMX agent for IBM WebSphere 6.1:1. Using the Documentum Administrator console, add the following line into

Application servers><Application Server Name> > Process Definition > Java Virtual Machine> Generic JVM Argument:-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote

2. Add, or un-comment, the following lines in the <Your WebSphere JRE>/lib/management/management.properties file:

com.sun.management.jmxremote.port=9999

com.sun.management.jmxremote.authenticate=false

com.sun.management.jmxremote.ssl=false

Editing al.properties using JConsole

To edit the al.properties file using JConsole:1. Open a command prompt at:

<JAVA_HOME>/bin

2. Type JConsole

The JConsole editor displays.

3. In the remote tab, type <Host Name> and the JMX port number.

Use 9999 for the JMX port number.



4. Click Connect.

5. In the com.documentum.ei.al.jmx.mbeans section, navigate to theMbeans tab and clickAlProperties.

6. Edit the desired properties and press Enter.

Significant system objects

This section contains information about significant system objects installed during AS SAP warfile deployment.

dfc.properties

Documentum stores data in the dfc.properties file located in the <Tomcat_installation_directory>\webapps\<Archive_Services_virtual_directory>\WEB-INF\classes directory.

More information is in the EMC Documentum Foundation Classes Installation Guide.

log4j.properties

All logging details are available in thelog4j.properties file available in the following directory:<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 detected automatically.

docbases.properties

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

If you intend to edit this file, we recommend that you use WebAdmin for this purpose. Moreinformation is in the ’Configuring, Viewing, and Editing Repository Connections’ section of the EMCDocumentum Archive Services for SAP Administration Guide.

al.properties

The system parameters for the AS SAP servlet are defined in al.properties. al.properties is locatedin the following directory:<Tomcat-Installation-Directory>\webapps\<Archive Services-Virtual-Directory>\WEB-INF



Postinstallation configurationThis section contains AS SAP post-installation configuration information.

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 valid directory inthe file system with complete access rights; AS SAP writes data to file in this temporary store beforereading 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 are running AS SAP on UNIX, you will need to customize the file differently. 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 optimize DocumentumClient Library’s (DMCL’s) behavior; this is necessary to obtain optimum performance from AS SAP.

To customize parameters in dfc.properties:

1. Select 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:dfc.session.max_count = 10

This attribute determines the maximum number of sessions.

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

dfc.session.max_count ≥ [docbases.numberOfConnections (default: 9) * numberOfDocbases] + 1.

In this formula, the following attributes occur in the al.properties file, as described in Configuringthe temporary store, page 24:• docbases.numberOfConnections



This attribute determines the number of connections established by the repository. Thedefault value is 9.

• numberOfDocbases

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

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

If you have three repositories installed, and the value of docbases.numberOfConnections is 5,then dfc.session.max_count should be ≥ 16.

4. Set the values of the following attributes as indicated below:dfc.session.max_countdfc.data.local_dir = ${dfc.data.user_dir}/localdfc.data.local_diskfull_limit = 0dfc.data.local_purge_on_diskfull = true

Note: Customizing these attributes is not mandatory for AS SAP to function correctly:• dfc.data.local_diskfull_limit

• dfc.data.local_purge_on_diskfull

These customized attributes improve the performance of AS SAP, although AS SAP functionseven if these attributes are not set. It is mandatory to add dfc.session.max_count to dfc.properties.

Archive Services for SAP ILM extension,installation, and configurationUnzip the Enterprise_Integrations_SAP_ILM.zip (Enterprise_Integrations_SAP_ILM.tar for UNIX) toa local directory. The following files are contained in the directory:• Enterprise_Integrations_SAP_ILM.dar and the related dar installer scripts

• ConfigSAPILM.jar

• dmwebdav.jar

• Namespace.jar

Note: Do not install the AS SAP ILM extension if you do not specifically plan to use the AS SAPILM extension.

Setup for AS SAP ILM extension

To set up your AS SAP ILM extension installation solution, ensure the following steps are completed:

1. Retention Policy Services Licensing is enabled during installation of the content server.



Note: If the content server is already installed, log in to Documentum Administration withadministrator rights and adjust your licensing setting using the licensing link on the mainadministration page.

2. Install RPS and PRM dar files on the repository in the same order (RPS installation guideprovides more details).

3. Install dmwebdav.war on a web server.

4. Install rpsa.war and da.war (if it is not already installed) preferably on a different web serverthan the dmwebdav.

5. dmWebDAV service configuration:

• Edit the dfc.properties to connect to the configured repository.

• Edit the web.xml file of dmwebdav with information on the repository to be used forILM-based archiving.

• Copy the necessary RPS library files to dmwebdav/WEB-INF/lib directory.

• Copy SAP ILM namespace JAR file to dmwebdav/WEB-INF/lib directory.

Note: The application server needs to be restarted if you make changes to the dfc.properties orthe web.xml file or if you copy jar files to webdav’s lib folder.

6. Install Enterprise_Integrations_Core.dar (if it is not already installed) on the repository.

7. Install the Enterprise_Integrations_ILM.dar.

8. Enable Privileged DFC on WebDAV for RPS using the Privileged Clients utility in DA.

9. Create default objects for AS SAP ILM extension—execute ConfigSAPILM tool.

10. Configure DmSapILM.properteis. To customize the DM WebDav server functionality, editthe properties.

11. If using EMC Centera, create EMC Centera store with retention attribute information. EMCCentera integration with ILM provides more details.

The AS SAP ILM extension solution is ready to run.

WebDAV service configuration

WebDAV is distributed as a WAR file containing all the application files. The EMC DocumentumWebDAV Installation Guide has complete information about the WebDAV installation procedure.These two application files must be edited for ILM configuration:

• dfc.properties

• web.xml

• DmSapILM.properties



Configuring dfc.properties

Set field dfc.docbroker.host[0] to the name of your docbroker machine.

Configuring web.xml

Set these web.xml parameter values as follows.

Parameter name Value

docbase docbase name (your docbase)

auth-type BASIC (default)

documentObjectType_docbaseName sap_ilm_document

folderObjectType_docbaseName sap_ilm_folder

return200ForCollection yes

extensions-enabled true

Note: The parameter names documentObjectType_docbaseName and folderObjectType_docbaseName should be changed to documentObjectType_<your docbase name> andfolderObjectType_<your docbase name> respectively.

The following is an example excerpt of a web.xml file for a repository named dctmsapilm:<init-param><param-name>docbase</param-name><param-value>dctmsapilm</param-value><description>Name of the Docbase to be made accessible through Documentum WebDAV Services</description></init-param>

<init-param><param-name>documentObjectType_ dctmsapilm</param-name><param-value>sap_ilm_document</param-value><description>The docbase object type that will be used while creating new objects.</description></init-param>

<init-param><param-name>folderObjectType_ dctmsapilm</param-name><param-value>sap_ilm_folder</param-value><description>The docbase object type that will be used while creating new objects.</description></init-param>

<init-param><param-name>return200ForCollection</param-name><param-value>yes</param-value><description>This is to enable new certification for SAP Client,this returns 200instead of 403 for collection objects for a HEAD/GET method.

</description></init-param>



Copying the required JAR files

Copy these JAR files from the WEB-INF\lib directory of a Retention Policy Services Administrator(RPSA) installation to the WEB-INF\lib directory of the dmWebDAV installation:

• DmcPolicyEngine.jar

• DmcPrm.jar

• DmcRecords.jar

• DmcRps.jar

• IDmcPolicyEngine.jar

• IDmcPrm.jar

• IDmcPrmModules.jar

• IDmcRps.jar

• IDmcRpsModules.jar

Copying AS SAP ILM namespace JAR file to dmWebDAV

Copy the namespace.jar and dmwebdav.jar present in the AS SAP installer to dmwebdav/WEB-INF/libDirectory.

Configuring the Administrative User for SAP ILM

AS SAP ILM administrator user should be a member of dmc_rps_retention_manager group, which iscreated by RPS installation.

To configure the administrative user for SAP ILM:1. Connect to WebAdmin, as described in Logging in to WebAdmin through Documentum

Administrator.

2. Click to expand the System subnode and select the DocLink subnode.

The SAPILM screen appears.

3. Edit the DmSapILM.properties file, as follows:

SAPILM.admin.username = <admin user name> — Name of the administrative user.

SAPILM.admin.password— Password of the administrator user in encrypted format. UseDFC utility for encryption.

4. Click OK to save the new administrative user for SAP ILM configuration.



Enabling Privileged DFC on WebDAV for RPS

DFC client instance for dmwebdav and DFC client instance used for executing configSAPILM, shouldbe privileged, to complete any ILM actions. Global repository name should be the same for bothDFC instances. In order to achieve this, as mentioned below, first open dmwebdav url, so that DFCinstance is registered in the global repository. Then enable privileged client for dmwebdav DFCinstance from Documentum Administrator (DA). RPS version 6.7 SPx is required for SAP ILM, whichuses Privileged DFC to dynamically grant users permissions in the repository.

Note: You can use the same dfc instance of dmwebdav for executing configSAPILM tool, so thatprevileged dfc client is reused.

Configure Privileged DFC for specific instances of dfc.jar when multiple dfc.jar files are presentfollowing these guidelines:

1. After installing WebDAV, connect to WebDAV by using Microsoft Internet Explorer and selectingFile > Open.

2. Type your WebDAV URL (http://<host>:<port>/dmwebdav/files) and select Open as Web Folder.

The file dfc.keystore is created in the same directory as your dfc.properties file.

3. Open dfc.keystore in a text editor and search on dfc.

A string beginning with dfc_ followed by 28 alphanumeric characters, used as the ClientID byDA, is found; for example, dfc_hIQLX2KxxqSHgkIGcu7TD6nX3Nka.

4. Start DA, navigate to the Privileged Clients node, and select File >Manage Clients.

A list of clients and dfc.jar files connected to the content server appears.

5. Locate the ClientID retrieved from your dfc.keystore file, move it the right, and click OK.

6. Right-click the new entry from the list and select Approve Privilege.

Privileged DFC is now enabled.

Installing the Enterprise_Integrations_SAP_ILM.dar file

Use the information in theInstalling a DAR file section to first install the Enterprise_Integrations_Core.dar file, and then as guidance for installing the Enterprise_Integrations_SAP_ILM.dar file.

Dar installation objects for AS SAP ILM extension

The dar file installs these objects:• dm_type sap_ilm_document: This object derives from dm_document. The attributes for thisobject are:

— al_object_type: string(10)

— al_obj_id: string(50)

— al_crep_id: string(2)



— al_doc_type: string(10)

— al_store_date: dm_time

— al_doc_class: string(20)

— al_mime_type: string(128)

— al_table: string(5)

• dm_type sap_ilm_folder: This object derives from dm_folder with the attribute origin: string(16).

• BOF module: This module implements the WebDAV namespace extension interface.

Creating default objects for AS SAP ILM extensionWebDAV customization using ConfigSAPILM tool

The Java configuration application is a CLI command that must be run to enable SAP ILMWebDav.

Note: Be sure to enable the DFC instance used to execute configSAPILM tool as a privileged clientfrom inside the Documentum Administrator.

To create the RPS policies, use the command:PATH_TO_WEB_INF/lib/dfc.jar;PATH_TO_WEB_INF\classes; PATH_TO_CONFIGJAR\ConfigSAPILM.jar;PATH_TO_WEB_INF/lib/IDmcPolicyEngine.jar;PATH_TO_WEB_INF/lib\IDmcRps.jar;PATH_TO_WEB_INF/lib\IDmcRpsModules.jar;PATH_TO_WEB_INF/lib\DmcPolicyEngine.jar;PATH_TO_WEB_INF/lib\DmcRecords.jar;PATH_TO_WEB_INF/lib\DmcRps.jar" com.documentum.ei.tools.ConfigSAPILM docbaseuser passworddocbase [domain]

where:

PATH_TO_CONFIGJAR is the full path of the directory containing the file ConfigSAPILM.jar

PATH_TO_WEBAPP_LIB is the full path to the WEBINF directory of the WebDAV web application.For e.g. PATH_TO_WEBAPP_LIB =C:/tomcat/webapps/dmwebdav/WEB-INF

The user specified must be configured as an RPS Retention Manager (dm_group:dmc_rps_retentionmanager) and have enough privileges to create a user.

The configuration performs the following actions:

• Creates a dm_user object sap_ilm_user:

— Initial password is set to 1Lmus3r

• Creates a dm_group object sap_ilm_group.

• Adds sap_ilm_user to the dm_group’s dmc_rps_retentionmanager, and sap_ilm_group.

• Creates an RPS Contact object that maps to the sap_ilm_group object.

• Creates an RPS Authority object that maps to the created Contact.



• Creates two RPS Condition Objects. The Authority is set to the created Authority object:

— expiration_date in the category SAPILM

• Two policies sap_container and sap_non_container are created. Even the RPS users are requiredto run configSAPILM tool to use SAP ILM capabilities, to pre create these policies.

If you see any errors during execution of the configSAPILM tool, navigate to privileged clients andensure that the DFC instance is registered as privileged. It is important to observe the configSAPILMtool execution complete without errors.

Note: If you execute configSAPILM tool with a dfc instance do not have privileged clientship, a nullpointer exception will be shown. In case if you observe any null pointer exception while executingconfigSAPILM tool:• Open RPSA and navigate to contacts.

• Edit the contact "sap_ilm_group."

• If the field "user" is empty, add user sap_ilm_user from the list.

• Execute the configSAPILM tool again.

DmSapILM.properties customization

Parameter Description

Version Indicates WebDav version (for example, 1.0)

SAPILM.admin.user SAP ILM Admin user id (for example, <user>)

SAPILM.admin.password SAP ILM Admin password in encrypted format (for example,<password>). Use DFC utility for encryption.

CenteraRetentionAttribute Indicates Centera retention policy, (for example, true or false), it issame as i_retain_until attribute value

forceEmptyCollectionDelete To delete an empty collection forcibly from WebDav (for example,true or false)

SAPILM.admin.runHybrid • It is recommended to set the SAPILM.admin.runHybrid propertyto false.

• To handle high scalability and huge volume of RPS requests, usethe RM/RPS 6.7SP2 Asynchronous capabilities. For details, referthe EMC Documentum Records Client 6.7 Administration and UserGuide.



Parameter Description

• In addition to RPS asynchronous capabilities, use the followingproperties for asynchronous processing of Retention PolicyApplication at the DMWebdavserver layer

— SAPILM.admin.runHybrid

— SAPILM.admin.timeInMsForProppatchStart

• If the SAPILM.admin.runHybrid property is set totrue, then the Proppatch requests is applied in anasynchronous manner with a delay as specified in propertySAPILM.admin.timeInMsForProppatchStart (for example,SAPILM.admin.runHybrid=false).

SAPILM.admin.timeInMsForProppatchStart

It is a time interval in Ms(Milli Second) based on which the RetentionPolicy Application request is launched. This property is applicableonly when the SAPILM.admin.runHybrid property is set to true.This time in millisecond should be arrived based on the systemconfiguration used to run the Proppatch requests (for example,:10000 in milliseconds).

EMC Centera integration with ILM

It is expected that most customers who use the SAP ILM solution will do so to store their data onEMC Centera. The SAP ILM WebDAV component and the RPS layer are fully integrated with theContent Services for EMC Centera (CSEC). When used with an EMC Centera, all ILM-relatedsettings sent from SAP are forwarded through RPS to CSEC, subsequently enforcing protectionon the hardware layer.

To configure the RPS, CSEC, and Content Server:1. Adjust the storage settings for the sap_ilm_document type in the Documentum Administrator.

2. Create a Centera store with an attribute name, for example, i_retain_until, as the retentionattribute name.

Note: While creating the Centera Store, make sure that the Event based retention option ischecked and the Application provides Retention option is unchecked

3. Once you have created the new store, set the default store property of the type sap_ilm_documentto the newly created store object.

4. Assign this storage as default store for the type "sap_ilm_document".

5. Edit the DmSapILM.properties file of DM WebDav as follows:

add CenteraRetentionAttribute=<Boolean value configured for centera store>

For example:

CenteraRetentionAttribute=true



To verify details of clips stored on EMC CenteraNote: This is applicable if Centera is used for storing content and ensuring its retention.

In order to verify the details about any document that is archived into Centera:

• Find out the r_object_id of the document using DA.

• Open apitester, either from DA or IAPI:Execute fetch,c,<<r_object_id>>Execute getpath,c,l

• A long hexadecimal string 7INF9TV6J4M7VeEONRNE2D3FGEBG4140SGV1B50IAO3BRRPRJIVI5is shown. It is the Centera clip ID.

• Use Centera APIs, JCASScript for connecting to Centera pool directly.

• Go to the command prompt, execute java -jar JCASScript.jar.

• Open pool by executing command po <<ip_address>>?<<pea file absolute path>>, whereip_address is the IP address of Centera cluster and pea file absolute path is the complete pathto .pea file

• Open the clip by executing command co<<clip_ id>>. It displays the clip details.

• Use the clip command crv to list the contents.

Installing PrintList Transformation FiltersThis section describe the AS SAP PrintList Transformation Filters.

Note: PrintList transformation filters require appropriate licensing and can be configured onlythrough the AS SAP WebAdmin tool.

On-demand rendering compared with stored rendering

If you are planning to use AS SAP to archive reports (SAP Print lists), it is possible to render theSAP proprietary PrintList format (ALF) into text, HTML, and PDF renditions. There are two waysto achieve this:

• Configure the archive to generate the desired renditions when the PrintList is stored.

• Configure the Documentum Content Server to generate a desired rendition when a PrintList isviewed, for example, on-demand.

Using on-demand rendering reduces the initial storage requirements needed to store reports andrenditions. However, performance is reduced when viewing a report, because on-the-fly renderingoccurs. On-the-fly renditions are stored in the Documentum repository for future use.

Stored rendering refers to the usage of built-in filters to generate desired document renditions when aPrintList is archived in the repository, as described in the ’Specifying a built-in lter’ section of EMCDocumentum Archive Services for SAP Administration Guide.



Configuring EMC Documentum Content Server foron-demand rendering

To configure EMC Documentum Content Server to render ALF reports into HTML, PDF, or TXTformats:

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

a. On the installation media, locate the transformation executable:For Windows installations, this file is called "alf2html.exe."

b. Copy this file into the EMC Documentum Content Server bin directory (for example:\Documentum\Product\6.0\bin).

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

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

b. Copy these scripts into the EMC Documentum Content Server Script Convert Directory (forexample: \Documentum\Product\6.0\Convert\Scripts).

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

# Converts SAP Printlists into open formats

#

alf2crtext sap_printlist T_t.crtext .

alf2chtml sap_printlist T_t.html .

alf2pdf sap_printlist T_t.pdf .

4. Save your changes and close the file.The settings will now take effect. It is not necessary to restart/reinitialize the EMC DocumentumContent Server.


Chapter 3Upgrading Archive Services for SAP

Before upgrading AS SAP, depending on existing infrastructure and your needs, you need todetermine how you want to deploy the application in your enterprise.

Upgrading from AS SAP 5.3 SPxYou can upgrade directly from AS SAP 5.3 SPx to AS SAP 6.7, 6.7 SPx, 7.0, or 7.2. The upgradesteps involve:• Uninstalling the previous versions of AS SAP. Use the standard uninstall procedure asrecommended by the respective application server, as described in Uninstalling Archive Servicesfor SAP.

• Installing the AS SAP server software as described in Chapter 2, Installing Archive Services forSAP.

Upgrading from AS SAP 6.0, 6.0 SP1You can upgrade directly from AS SAP 6.0 and 6.0 SP1 to AS SAP 6.7, 6.7 SPx, 7.0, or 7.2:

1. Ensure that the application server on which AS SAP is installed is stopped.

2. Stop the CS SAP service if installed.

3. Delete the dependency and bof modules that were installed by CS SAP 6.0 or 6.0 SP1 docapp at/System/Modules by logging into the repository using Documentum Administrator:

a. Execute the following query:— select * from dmc_java_library where object_name=’dmei_core_lib’— select * from dmc_java_library where object_name=’dmei_doclink_lib’— select * from dmc_java_library where object_name=’hvps_lib’

Note: Record the r_object_id of the above folders.

b. Execute the following query to remove any dependencies:— delete dm_relation objects where parent_id=’<r_object_id for each of the above 3 folders>’

c. Delete the three folders listed in step 3a manually, or by executing the following DQL:


Upgrading Archive Services for SAP

— delete dmc_java_library objects where object_name=’<folder_name>’

Note: If deleting manually, all subfolders and their files must be deleted first.

4. Install Enterprise_Integrations_Core.dar and the assap.war as directed in this guide.

Upgrading from AS SAP 6.5 SPx, 6.7, 6.7 SPx,7.0, to 7.2Upgrading to the latest version of service packs involves the following steps:

1. Stop the application server running assap.war, delete the assap.war, and replace with newassap.war.

2. Install the latest version of AS SAP by following the standard installation procedure. Ensure theEnterprise_Integrations_Core.dar file is installed on global repository as well as on the repositorybeing used for AS SAP.

3. For integration of AS SAP Information Lifecycle Manager (AS SAP ILM) with Centera, theDmSapILM.properties file has to be edited after you upgrade the service pack.

Note: Make sure that the version of Composer used to install the DAR files matches the version of theAS SAP Service Pack being installed.

Additional steps to upgrade Archive Servicesfor SAPUpgrade of Archive Services for SAP from 5.3 SPx to 6.0 and later, or 6.5 and later does not work asexpected. To resolve this issue, an upgrade from 5.3 SPx to 6.0 and later, or 6.5 and later requires 5.3SPx to be uninstalled first. The 5.3 SPx AS SAP installer on Tomcat web server appends additionallines to the catalina.bat or catalina.sh (in case of UNIX environments) files. The following linesmust be removed manually:rem ----- The next two lines were added by a Documentum installer- please do not remove this comment -----

set CATALINA_OPTS=%CATALINA_OPTS% -Djava.library.path="C:\Program Files\Documentum\shared" -Xms256m -Xmx256m -verbose:gc

set CLASSPATH=C:\Program Files\Documentum\shared\DmcRecords.jar;C:\Program Files\Documentum\shared\messageArchive.jar;C:\Program Files\Documentum\shared\messageService.jar;C:\Program Files\Documentum\shared\bpmutil.jar;C:\Program Files\Documentum\shared\ctsTransformImpl.jar;C:\Program Files\Documentum\shared\ctsTransform.jar;C:\Program Files\Documentum\shared\collaboration.jar;C:\Program Files\Documentum\shared\ci.jar;C:\Program Files\Documentum\shared\castor-0.9.5.2.jar;C:\Program Files\Documentum\shared\commons-jxpath-1.2.jar;C:\Program Files\Documentum\shared\XformsCommon.jar;C:\Program Files\Documentum\shared\xforms.jar;C:\Program Files\Documentum\shared\subscription.jar;C:\Program Files\Documentum\shared\workflow.jar;



C:\Program Files\Documentum\shared\xml-apis.jar;C:\Program Files\Documentum\shared\xalan.jar;C:\Program Files\Documentum\shared\log4j.jar;C:\Program Files\Documentum\shared\bsf.jar;C:\Program Files\Documentum\shared\All-MB.jar;C:\Program Files\Documentum\shared\xtrim-api.jar;C:\Program Files\Documentum\shared\dfcbase.jar;C:\Program Files\Documentum\shared\dfc.jar;C:\Documentum\config;%CLASSPATH%

For an upgrade on other application servers, you must remove any references to DFC 5.3 SPx in thestartup scripts accordingly.




Chapter 4Testing the installation

Use the information in this chapter to test the AS SAP installation.

Complete information about the functions included in this chapter is in the EMC Documentum ArchiveServices for SAP Administration Guide and EMC Documentum Archive Services for SAP User Guide.

Logging in to WebAdmin through DocumentumAdministratorLog in to Documentum Administrator before using WebAdmin to configure AS SAP.

Note: The EMC Documentum Documentum Administrator User Guide has complete information aboutusing Documentum Administrator.

To connect to WebAdmin through Documentum Administrator:

1. Start a web browser on a client machine.

2. Connect to the following URL, where host is the host where Documentum Administrator isinstalled and portnumber is a port number provided during application server installation:http://host:portnumber/da/

3. Type your login name and password on the Documentum Administrator Login page.

4. Select a repository from the list box.

If you change the repository, retype your password.

5. In the Location list (if available), select the location on your organization’s network from whichyou are accessing Documentum Administrator.

This allows you to access content from the nearest storage area in the network. Depending onyour organization’s setup, this location might be a fixed value.

6. To view additional options, clickMore Options:• To connect to the repository using a particular server, select that server from the Server list box.

The default is Any Running Server.

• If the repository is running in domain-required mode, type the domain name.

• To set the session locale to another language, select the language from the list box.


Testing the installation

Note: Do not click the Additional Accessibility Options link on the login page. DocumentumAdministrator does not support the accessibility options.

• To change your password in a repository, click Change Password, select a repository, and typeyour old and new passwords, and then click Change Password.

Note: If LDAP user authentication is used, you cannot change your password from this page.A system administrator must change your password on the LDAP server.

7. Click Login.

The System Information page appears with information about the system.

The EMC Documentum Documentum Administrator User Guide has complete information aboutusing Documentum Administrator and logging in to repositories available in DocumentumAdministrator.

Configuring HTTP repositories for archivelinkingTo configure HTTP repositories for archive linking:1. Connect to WebAdmin, as described in Logging in to WebAdmin through Documentum

Administrator.

2. Click to expand the ArchiveLink subnode and select the Repositories subnode.

The Repositories screen appears.

3. Select File > New > Repository from the menu at the top of the Repository screen.

The New Repository screen appears.

4. Type the connection information for the new repository, as follows:

Repository Name: — Name of the new repository.

User Name: —Username associated with the user of the new repository.

User Password: —User password associated with the username of the user of the new repository.

Domain: — Domain in which the new repository resides.

Note: Click Test Connection to test the information typed above.

5. Type the connection information for the global repository associated with the new repository,as follows:

User Name: —Username associated with the user of the global repository.

User Password: — User password associated with the username of the user of the globalrepository.

Domain: — Domain in which the global repository resides.

6. Click OK to save the new repository configuration.



Creating an archive in WebAdminUse WebAdmin to view an archive.

Note: The EMC Documentum Archive Services for SAP Administration Guide has complete informationabout creating, viewing, and editing archives using WebAdmin:

1. Connect to WebAdmin, as described in Logging in to WebAdmin through DocumentumAdministrator, page 39.

2. Click to expand the ArchiveLink sub-node and select the Archive sub-node.The Archive screen appears.

3. Select File > New > Archive from the menu at the top of the Archive screen.The New Archive screen appears.

4. Type the archive name in the Archive Name: field.You can use up to 30 character long names for archives when supported by SAP.

5. The following parameters can be configured.

Table 1. Parameters in archives’ configuration page

Fieldname Description

Archive ID Name of the SAP archive, as defined in the ’OAC0 —Defining a Logical ArchiveID in SAP’ section of the EMCDocumentum Archive Services for SAP Configuration Guide.

SAP Document Type Set to NONE (HTTP provided).

Documentum Type Specifies the Documentum document type, as defined inthe ’Configuring the Repository Document Type’ sectionof the Archive Services for SAP Administration Guide.

Workflow Set to No Workflow.

Attribute Map The attribute map is used to define the Documentumattributes of an archived document.

There is a special attribute "FOLDER” that can beconfigured. To specify the folder path, use the followingformat: "FOLDER="/SAP/Archive/AA"

In the Attribute map, you can also set the followingattributes:

• a_storage_type

• a_retention_date

Note: More information is in the ’Setting EMCCentera-related Attributes in Archive Services’ section



Fieldname Description

of the EMC Documentum Archive Services for SAPAdministration Guide.

Filtering Used to define a custom filter. Used to define the output:• Text

• PDF

• HTML

Note: The aim of this exercise is to test if the installation has been successful; therefore, if an existingarchive is available for reuse, it is not necessary to create a new archive for testing purposes. However,if you want, you may create a new archive or reuse any ArchiveID that has been created previously,as described in the EMC Documentum Archive Services for SAP Administration Guide.

Defining a logical ArchiveID in SAPLogical ArchiveIDs are created in SAP using the SAP GUI. The name of the logical ArchiveID mustbe the same as the ArchiveID viewed using WebAdmin, as described in Creating an archive inWebAdmin, page 41.

To define a logical ArchiveID in SAP:

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

2. In theDisplay Content Repositories: Overview page, click on any content repository (specificallywhose Storage type is HTTP content server).

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

4. Click Copy as ....

5. Edit the Content Rep. field so that it is the same as the ArchiveID created using WebAdmin.

6. In the Transfer drctry field, type the directory path where SAP can write the Print List untilit 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/<name-of-repository>

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



Testing the connection between SAP and ASSAPTo test the connection between SAP and AS SAP:

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

2. In theDisplay Content Repositories: Overview page, click on any content repository (specificallywhose Storage type is HTTP content server).

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

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

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, type any piece of text starting with the alphabet Z in the Documenttype field.Thus, Z<Your Text> will be the document type.

6. In the Storage system field, type the name of the logical ArchiveID that you created earlier inDefining a logical ArchiveID in SAP, page 42, where the documents will be archived.

7. Save your changes.

Archiving a PrintListTo archive a PrintList:

1. 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, select 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 list box, select Archive only.

Note: Whenever you edit a parameter in this dialog box, we recommend that you select ShowSelected Print Parameters on Initial Screen. This ensures that the customized settings areavailable 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 in Creating a DocumentType in SAP, page 43, and execute it.

9. Type additional information in the Information field.This label may be anything you want; 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 list box, 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. To view the status of the document in the storage queue, execute the following transaction inthe transaction code field:oam1.The ArchiveLink Monitor screen appears.The Print List is now queued, waiting for the scheduler to pick it up and transfer it to the archive.The ’OAAT - Scheduling Jobs’ section of the EMC Documentum Archive Services for SAPConfiguration Guide contains information about configuring the ArchiveLink scheduler.

16. To accelerate the transfer of the Print List from the queue to the archive in the repository, clickStorage Queue.The Queue: Content server (CARA) screen appears. You should now see an entry for the newlyarchived 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 the following:

1. Connect to WebAdmin, as described in Logging in to WebAdmin through DocumentumAdministrator, page 39.

2. Click to expand the ArchiveLink sub-node and select the Archive sub-node.The Archive screen appears.

3. Select an archive in the Archive screen.

4. Right-click the archive and select Properties from the menu.The Properties screen appears.

5. Note the ArchiveID of the selected archive.

6. Execute the following transaction in SAP in the transaction code field:oadd.

7. In the ArchiveLink: Hit List for Stored Print Lists page for a particular item, select Print List >Display From Content Server.SAP executes the GET command to retrieve the document from the Documentum archive. Theretrieved document has the ArchiveID of the Print List in Documentum.




Chapter 5Troubleshooting installation issues

This chapter discusses commonly encountered issues in AS SAP and how you can resolve them.

High levels of loggingYou may encounter high levels of logging if the logging parameter for Archive Services has been setas DEBUG or WARN. By default, this parameter is set as WARN. If you had set the logging parameteras DEBUG, Archive Services documents log each and every request; in a production environment,this can translate into a extremely high logging levels. This causes the following problems:

• Because Archive Services writes each and every request to a log, this uses enormous storagespace in a production environment.

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

When the logging level is set to DEBUG, Archive Services writes certain parameters of eachrequest to memory. With each request, the amount of memory used by Archive Services increasesincrementally. 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

Note: Depending on the setting for logging levels in your environment, one of the parametersindicated above will not be commented (the hash symbol (#) will not precede 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 logging parameter.Ensure that the other two parameters are commented.

Example 5-1.If you want to set the logging level as INFO, edit the logging parameters as follows:#log4j.logger.com.documentum.ei=WARN


Troubleshooting installation issues

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

4. Save the file.

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

Incorrect Tomcat installationAfter installing Archive Services, when you connect to WebAdmin for the first time, you mightget this JSP error: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 J2SE option, in theTomcat 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.

Performance issues with ACSThe performance of Archive Services for SAP fetch operations is comparatively low when ACS isenabled as compared to when ACS is disabled, if you set the log level to DEBUG. To improve theperformance, set the log level to WARN or INFO.

Inability to perform certain operations whenusing Archive Services for SAP on IBMWebsphere 5.1.1.9Case 1

If you have deployed Archive Services on IBMWebsphere 5.1.1 Cumulative Fix 9 (5.1.1.9), you cannotperform certain operations on SAP 4.7; the following error message appears:

HTTP 411 Content Header Error



Resolve this issue by applying patch 129 to the SAP kernel; this ensures that the SAP kernel isupgraded to level 640_REL. More information is in SAP note 925327 available in the SAP Servicewebsite: http://service.sap.com.

Case 2

After upgrading the SAP kernel as described in Case 1, if you perform the RSCMSTH2 andRSCMSTH3 certification tests, the following error message may appear:comp data mimetype <blank> instead text/html

This is a known SAP issue; for information on resolving this issue, refer to SAP note 631790 availablein the SAP Service website: http://service.sap.com.

Unable to create a repository in Webadmin ifthe archivelink.key file is not foundIn Webadmin, you will not be able to create a repository in Archive Link >Repositories, if thearchivelink.key file is missing in the <DA Deployment Directory>/WEB-INF/classes folder.


http://service.sap.com

http://service.sap.com



Chapter 6Uninstalling Archive Services for SAP

Uninstalling AS SAP consists of the high-level tasks and procedures listed in this chapter.

Preparing application servers for AS SAPuninstallationTo prepare application servers for AS SAP uninstallation:• Close all browser sessions that are running WebAdmin.

• 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 AS SAP using Apache TomcatTo 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 AS SAP using BEA WeblogicTo uninstall using BEA Weblogic:

1. Start the BEA Weblogic server.

2. Type your user ID and password.


Uninstalling Archive Services for SAP

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. Type your user ID.The Integrated Solutions Console screen appears.

3. Expand Applications and click Enterprise Applications.

4. Select assap and click Stop.The following message appears with assap selected for uninstall:[-]Messages Application assap on server server1 andnode cmaqaaix113Node01 stopped successfully

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

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


Appendix A

Advanced Installation Option for LoadBalancing

AS SAP may be installed on a Tomcat server where Apache and Tomcat are configured to use loadbalancing between multiple Tomcat sessions. This configuration is particularly powerful when usedin tandem with multiple Tomcat hosts. Use mod-jk as a connector for communications betweenApache and Tomcat.

Installing connectors for Apache and TomcatIf your installation scenario is based on a load-balancing configuration, in addition to installingApache, you must download (from the Web) and install mod_jk, a plug-in that handles thecommunication between Apache and Tomcat.

For detailed installation, configuration, and administration instructions, refer to the documentationavailable in Tomcat’s website (http://jakarta.apache.org/tomcat/).

Guidelines for configuring Apache and Tomcatfor load balancingUse the following steps as broad guidelines while configuring Apache and Tomcat for advancedscalability. Detailed information is in the specific documentation available in the Jakarta project’swebsite http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html

• Obtain the installation file for Tomcat 5.0.28 (or later) from the Web and install the 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 betweenApache and Tomcat, from the Web and install the same.

• In Apache:

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


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

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

Advanced Installation Option for Load Balancing

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 of Tomcat instancesthat have been installed.

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

• 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 Servlet requestscoming from Apache.

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


Appendix B

Installing a DAR file using the DARInstaller GUI

You can use the DAR Installer GUI to install a DAR file to a repository if you do not want to use theinterface within Composer.

Note: The Dar Installer GUI is only supported for Windows environment.

If the repository used for installing the Enterprise_Integrations_Core.dar files is not a Globalrepository, then the Enterprise_Integrations_Core.dar files must be installed on both the Globalrepository and the repository used for AS SAP.

The DAR Installer GUI requires Composer to be installed, but does not launch the full ComposerIDE. The DAR Installer GUI is useful in cases where you want to de-couple the development of DARfiles from the installation of DAR files. It is also useful in situations where installation of DAR files isrequired as part of a deployment process. When you open the DAR Installer GUI, it creates threefolders in your Composer installation directory:

• darinstallerconfig — Contains configuration files for the DAR Installer GUI.

• darinstallerlogs — Default location of the log files.

• darinstallerworkspaces — Workspaces that are created and used by the DAR Installer GUI.The DAR Installer GUI does not delete these workspaces automatically, so you occasionallyneed to clean up this directory. The workspace directories are named in the following form:darinstaller_workspace_yyyy-mm-dd-hh-mm-ss.

The DAR Installer requires you to fill in certain values that are marked with an asterisk (*). All otherfields are optional. The following table provides a description of the fields for the DAR Installer Utility

To install a dar file:

1. Download the DAR Installer zip file. You can find the DAR Installer GUI at https://EMC.subscribenet.com/control/dctm/search. Search for "Composer” to reach the DocumentumComposer download site. Documentum Headless Composer GUI is also available within the CSinstallation at C:\Documentum\product\7.2\install\composer\ComposerHeadless.

2. Unzip the DAR Installer zip file to the root of your Composer or headless Composer installationdirectory.

3. Run darinstaller.exe, which is located in the Composer root directory, to start the DAR InstallerGUI.

4. In the DAR Details section, specify values for the fields.


https://emc.subscribenet.com/control/dctm/search

https://emc.subscribenet.com/control/dctm/search

Installing a DAR file using the DAR Installer GUI

5. In the Connection Broker Details section, specify values for Connection Broker Host andConnection Broker Port and click Connect.

6. In the Repository Details section, specify values for the fields and click Install to install theDAR file to the repository.

You can view the log for the DAR installation by selecting the log file from the Log File list box andclicking Open.

Table 2. DAR Installer fields

Parameter Required Description

DAR Yes The absolute file path to the .dar file that you want to install.The file path cannot contain any I18N characters or theinstallation will fail.

Input file No The absolute file path to the install-based parameter file.

Local folder No The absolute file path to localized .properties files. If youwant to make your application available in other languages,you need to localize the project data such as labels, tabs,and descriptions.

Log file No The file to save the log to. If this is not specified, the filedefaults to <DAR>.log.

Connection brokerhost

Yes The address of the connection broker.

Connection brokerport

Yes The port of the connection broker repository.

Repository Yes The name of the repository that you want to install theDAR file to. Click on the Connect button after enteringthe Docbroker host and port to retrieve the availablerepositories.

User name Yes The login name for the repository.

Password Yes The password for logging into the repository.

Domain No The domain where the repository resides.


Index

Aa_retention_date, 42a_storage_type, 42advanced scalability options, 10, 53

configuring, 53See also load balancing using

Apache and Tomcat,configuring

al.properties, 23configuring in UNIX, 24configuring in Windows, 24configuring postinstallation, 24directory path, 24docbases.numberOfConnections, 25numberOfDocbases, 25

all-in-one installation, 10Apache, 53

configuration file, 54configuration file, httpd.conf, 54workers.properties file, 54

Apache and Tomcat for load balancing,configuring, 53

Apache TomcatJava heap size, 14

application server host requirementsJava heap size, 14

application serverstemporary disk space requirements, 13

Archiveviewing in WebAdmin, 41

Archive Services, 7installing, 13obtaining latest copy of, 14uninstalling, 51

Archive Services for SAP, 7See also Archive Servicesupgrading, 35

ArchiveID, 41ArchiveLink Monitor window, 44Archiving request window, 44

archiving.tempDircustomizing in Windows, 24

archiving.upload.tempDircustomizing in UNIX, 24

Attribute Map, 42attributes

a_retention_date, 42a_storage_type, 42EMC Centera-related, 42in dfc.properties, cache_queries, 25in dfc.properties, dfc.session.max_

count, 25in dfc.properties, local_diskfull_

limit, 25in dfc.properties, local_purge_on_

diskfull, 25

BBEA Weblogic

Java heap size, 14

Ccache_queries, 25configuration file

Apache, 54configuration file, httpd.conf

Apache, 54configuring

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

scalability, 53See also load balancing using

Apache and Tomcat,configuring

Apache and Tomcat for loadbalancing, 53

archive parameters, 41


Index

Archive Services, postinstallation, 24load balancing using Apache and

Tomcat, configuring, 53connection

between SAP and Archive Services,testing of, 43

connections, setting up repository, 39connectors for Apache and Tomcat

installing, 53creating

connections to EMC Centera, 13document type, 43

customizingarchiving.tempDir in Windows, 24archiving.upload.tempDir in UNIX, 24dfc.properties, 24

DDEBUG

logging level, 47turning off, 47

defininglogical ArchiveID in SAP, 42

dfc.properties, 23cache_queries, 25customizing, 24dfc.session.max_count, 24docbases.numberOfConnections, 24local_diskfull_limit, 25local_purge_on_diskfull, 25opening in UNIX, 24opening in Windows, 24path in UNIX, 23path in Windows, 23

dfc.session.max_count, 24disk space requirements, 13DmSAPILM properties, 31docbases.numberOfConnections, 24 to 25docbases.properties, 23document type

creating, 43DocumentID, 45Documentum Client Library. See DMCLDocumentum document type. See

Documentum TypeDocumentum Download Center. See

SubscribenetDocumentum Type, 41

EEMC Centera

creating connections to, 13integration with, installation

scenario, 10EMC Centera-related attributes, 42ensuring

the working of repository, 13excessive logging, troubleshooting, 47

Ff.21, 43

Ggeneral prerequisites, 9

Hhttpd.conf, 54

IIBM WebSphere

Java heap size, 14installation

requirements, 7testing, 39troubleshooting issues, 47

installation scenariosadvanced scalability options, 10, 53all-in-one installation, 10integration with EMC Centera, 10separate Archive Services, 10

installingadvanced scalability options, 10, 53

See also installation scenarios,advanced scalability options

all-in-one installation, 10See also installation scenarios,

all-in-one installationArchive Services, 13connectors for Apache and Tomcat, 53integration with EMC Centera, 10

See also installation scenarios,integration with Centera

mod_jk, 53on Windows, 14


Index

separate Archive Services, 10See also installation scenarios,

separate Archive ServicesSolaris, 14

integration with EMC Centera, 10intended audience, 7

JJava

heap size, 14

Lload balancing. See advanced scalability

optionsload balancing using Apache and Tomcat,

configuring, 53local_diskfull_limit, 25local_purge_on_diskfull, 25log4j.debug, 47log4j.properties

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

Log4j.properties, 23logging level, DEBUG, 47logical ArchiveID, defining in SAP, 42

Mmaximum number of sessions, 24mod_jk

installing, 53utility, 53

Nnumber of connections established by

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

file, 54numberOfDocbases, 25

Ooac0, 41 to 43oac3, 43oadd, 45oam1, 44

ObjectType, SOOD, 43obtaining

latest copy of Archive Services, 14opening

dfc.properties in UNIX, 24dfc.properties in Windows, 24

Oracle Application ServerJava heap size, 14

out of memory errors, 14

Pparameters in archives configuration

page, 41percentage of load, workers.properties

file, 54plug-in, mod_jk. See mod_jkpostinstallation configuration, 24preinstallation requirements

Java heap size, 14temporary disk space, 13

preinstallation tasks, 51prerequisites

general, 9software, 9system administrator, 7

Print Listsending, 43viewing, 45

Purpose, 7

Rrepository

ensuring the working of, 13number of connections established

by, 25number of, installed, 25setting up connections, 39

SSAP

defining logical ArchiveID in, 42Print List, sending, 43transaction code, f.21, 43transaction code, oac0, 41 to 43transaction code, oac3, 43transaction code, oadd, 45transaction code, oam1, 44

SAP Document Type, 41


Index

SAP ILMDmSAPILM properties, 31

SAPGUIArchiveLink Monitor window, 44Archiving request window, 44Test connection button, 43Transfer drctry field, 42

scenarios, installationadvanced scalability options, 10, 53all-in-one installation, 10integration with EMC Centera, 10separate Archive Services, 10

sending, Print List, 43separate Archive Services, 10server.xml, 54setting

repository connections, 39setting attributes, EMC Centera-related, 42significant system files, 23software prerequisites, 9SOOD, ObjectType, 43Subscribenet, 14system administrator, 7

prerequisites, 7system files, significant, 23

Ttemporary disk space requirements, 13Test connection button, SAPGUI, 43testing

connection between SAP and ArchiveServices, 43

installation, 39Tomcat, 53

server.xml, 54transaction code

f.21, 43oac0, 42 to 43oac3, 43oadd, 45oam1, 44

transaction code, oac0, 41Transfer drctry field, 42troubleshooting

excessive logging, 47installation issues, 47

turning off DEBUG, 47

Uuninstalling, Archive Services, 51UNIX

configuring al.properties in, 24opening dfc.properties in, 24

upgradingArchive Services for SAP, 35

Vviewing

Archive in WebAdmin, 41Print List, 45

WWebAdmin

viewing an Archive, 41Windows

configuring al.properties in, 24opening dfc.properties in, 24

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


Documents

EMC Documentum ArchiveServicesforSAP · PDF fileArchiveServicesforSAP Version7.2 InstallationGuide EMCCorporation ... • Enterprise_Integrations_SAP_ILM.zip—ContainstheASSAPILMapplication,whichincludes