EMC Documentum ArchiveServicesforSAP · PDF fileArchiveServicesforSAP Version6.5 InstallationGuide P/N300-006-287RevA04 EMCCorporation ... • Enterprise_Integrations_SAP_ILM.darandtherelateddarinstallerscripts

EMC® Documentum®

Archive Services for SAPVersion 6.5

Installation Guide

P/N 300-006-287 Rev A04

EMC CorporationCorporate Headquarters:

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

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

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kindwith respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitnessfor a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarksused herein are the property of their respective owners.© Copyright 2010 EMC Corporation. All rights reserved.

Table of Contents

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

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

Installing required EMC Documentum software ................................................. 12Installing EMC Documentum Administrator .................................................. 13

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

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

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

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

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

EMC Documentum Archive Services for SAP Version 6.5 Installation Guide 3

Table of Contents

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

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

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

Optional customization of AS SAP ILM extension RPS policy mapping ............ 32Creating default objects for AS SAP ILM extension WebDAVcustomization—using ConfigSAPILM tool ................................................. 33Config.properties customization ................................................................ 34

EMC Centera integration with ILM................................................................ 34To verify details of clips stored on EMC Centera ............................................. 35

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

Chapter 3 Upgrading Archive Services for SAP ........................................................... 39Upgrading from AS SAP 5.3 SPx........................................................................ 39Upgrading from AS SAP 6.0, 6.0 SP1 ................................................................. 39Upgrading from AS SAP 6.5 SPx........................................................................ 40

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

Chapter 5 Troubleshooting Installation Issues ............................................................ 49High levels of logging ....................................................................................... 49Incorrect Tomcat installation ............................................................................. 50

Chapter 6 Uninstalling Archive Services for SAP ........................................................ 51Preparing application servers for AS SAP uninstallation ..................................... 51Uninstalling AS SAP using Apache Tomcat ........................................................ 51Uninstalling AS SAP using BEAWeblogic .......................................................... 51Uninstalling using IBMWebSphere ................................................................... 52

4 EMC Documentum Archive Services for SAP Version 6.5 Installation Guide

Table of Contents

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............................................................. 43Table 2. DAR Installer fields .............................................................................................. 56


Preface

Purpose of this guideThis guide explains how to install and configure Archive Services for SAP (AS SAP) 6.5. 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 ’Software Requirements’ section of the EMCDocumentum Archive Services for SAP Release Notes.

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

Revision history

Revision date Description

July 2008 Initial publication of document for AS SAP 6.5.

December 2008 Update publication of document for AS SAP6.5 Rev A02.

June 2009 Update publication of document for AS SAP6.5 Rev A03.

March 2010 Update publication of document for AS SAP6.5 Rev A04.

Typographic conventionsThis guide uses the following text conventions.


Preface

Typographic conventions used in this guide

Convention Description

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

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

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

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

{} curly brackets Used in method command syntax specifications,curly brackets indicate an optional argumentthat can be repeated 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 can be found on EMC Powerlink athttp://Powerlink.EMC.com.

From Powerlink, you can download the latest version of AS SAP and the related documentationsuite. To access the contents in Powerlink, you will need to provide the login credentials assigned toyou when you first applied for access.

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

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,miscellaneous technical notes,and documentation correctnessand clarifications.

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 be performedin SAP so that SAP cancommunicate with ArchiveServices.

System Administrator (SAP)


http://powerlink.emc.com

Preface

Title Description Target role

EMC Documentum ArchiveServices for SAP AdministrationGuide

Describes how to configureArchive Services using theWebAdmin tool.

Archive Services Administrator

EMC Documentum ArchiveServices for SAP User Guide

Describes how SAP users viewdocuments.

Standard User

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


Preface


Chapter 1Preparing to Install Archive Servicesfor SAP

This chapter provides information about preparing to install AS SAP.

General prerequisitesThe person installing AS SAP should have administrative experience with the software productslisted in the EMC Documentum Archive Services for SAP Release Notes.

Note:• Unless the person installing the product has the prerequisite experience, EMC Documentumrecommends that you do not perform installations using only EMC Documentum manuals asguidance.

• EMC Documentum Support can assist only with systems that were installed by qualified personsfollowing the specific instructions outlined in both the documentation and the training manual.

Software prerequisitesAS SAP depends on specific versions of Documentum and third-party products, as described in the’Software Requirements’ section of the EMC Documentum Archive Services for SAP Release Notes.

Installation scenariosAS SAP may be installed in various configurations, depending on how it is mixed and matched withcontent addressed storage systems like EMC Centera® or third-party applications like Apache andTomcat. Different configurations may also be arrived at depending on how and where the contentserver and AS SAP are installed. The possible basic configurations are described in the followingsections.


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 is in theEMC Documentum Archive Services for SAP Release Notes.

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’s 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 must be installed priorto installing AS SAP.



Installing EMC Documentum Administrator

After the database and Documentum Content Server have been installed, install DocumentumAdministrator as 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, or needed support packages,hot fixes, or OSS Notes. Documentum requires that you read and apply all ArchiveLink-relatedOSS Notes and patches prior to AS SAP installation. Documentum support is not responsiblefor answering 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: From 6.5 release, the administration console for both AS SAP and CS SAP is the same. InstallingWebAdmin (packaged as dmei_webadmin.zip) component on DA would enable users to administer



both CS SAP and AS SAP. However, the CS SAP would need HVPS component in addition to whatAS 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 should be up, running, and performing before you install AS SAP. AS SAP requiresa fully functional repository so that during install, 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 properly is important to avoid out-of-memory errors:• For BEA, Tomcat, and Oracle, set the heap size to 512 MB.

• For WebSphere, set the heap size to 1024 MB.

Supported operating systems and application servers

AS SAP can be installed on different combinations of operating systems and application servers.More information on supported combinations is in the ’Software requirements’ section of the EMCDocumentum Archive Services for SAP Release Notes.

Obtaining current version software from theDocumentum 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_6.5_Windows.zip, contains the following files:

• 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_6.5_<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.

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


https://emc.subscribenet.com


Ensure that the dfc.properties of the composer utility has the Global repository details specified.

The Documentum Composer can be located in the system where content server 6.5 or above isinstalled. In Windows OS, the composer could be located in %DOCUMENTUM%\product\6.5\install\composer on the system where Content Server is installed. Alternatively, the latest versionof the composer can be downloaded from Powerlink®.

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.

Users comfortable with the GUI mode, can make use of the Composer GUI to install DARs. TheComposer GUI is specific to Windows environment. If the Content Server is running on an UNIXenvironment, you could still connect to the repositories from the Composer GUI installed on yourWindows system making the needed changes to the dfc.properties of the 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 should 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. The Enterprise_Integrations_Core.dar can be installed using the DAR Installer GUI in Windowsenvironments as described in Installing a DAR file using the DAR Installer GUI. Alternatively, theDAR file can be installed using the headless composer as described below.

3. Follow the steps below to install the DAR file using the 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 should 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 Composer Headless directory on yourmachine.

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



set 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: Ant tasks do not pick up the settings in the eclipse.ini file. This means thoseparameters have to be set 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 of 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 created duringthe Documentum Administrator installation.

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 a directory called 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 in the left panel.

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

6. Click Install.

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

Specifiying 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 the 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 should nowinclude your newly installed Web application.

17. Click Activate Changes in left panel.

This commits all changes made.

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

Deploying assap.war 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 the (*) Show me all installation options and parameters and press Next.

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

8. In the following screen, select Precompile JavaServer Pages files and 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 procedures used for viewing and editing the al.properties file in the JConsoleeditor without the need for restarting the application server as follows:• 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 the <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 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 postinstallation 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 26:• 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.

EMC Documentum 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 are the files 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. Config.properties customization: Edit config.properties specifying details of the install ownerand EMC Centera attributes in case EMC Centera is being used for archiving.

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

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

• DmcRecords.jar

• DmcRps.jar

• IDmcPolicyEngine.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, whichis created by RPS installation. For RPS versions below 6.5 SP1, administrative user should be amember of dm_retention_managers group.

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 config.properties file, as follows:

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

SAPILM.admin.password— Password of the administrative user.

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 DFC



instance from Documentum Administrator (DA). RPS version 6.5 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 clickOK.

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 Installing a DAR file section to first install the Enterprise_Integrations_Core.darfile, 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:• config.properties in /System/Doclink/SAPILM

• 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. The module implements the WebDAV namespace extension interface.

Optional customization of AS SAP ILM extension RPSpolicy mapping

The only optional configuration parameter for the AS SAP ILM extension is provided for users whoalready use RPS, and enables consistent retention policies across the docbase.

Adjust the /System/Doclink/SAPILM/config.properties file located in the docbase as listed in thefollowing table.

Note: Adjusting the config.properties file in the docbase is optional, and only required when usingRPS policies other than the default policies available with AS SAP ILM extension.

Parameter Value

NAME.path=/path/in/docbase Substitute NAME with SAPILM.

NAME.policy=rpsPolicy Substitute NAME with SAPILM.

Substitute rpsPolicy with the name of an existingpolicy that conforms to the Policy Optionsguidelines below.

Note: The first configuration creates RPS ’1Phase + Final’ policies. There are many optionsthat must be selected for the overall policy onthe info tab.

Policy Options

Note: Any number of policies can be mapped to a directory.

Option Value

Retention Strategy Linked

Disposition Strategy Destroy All

Immutability Rule Do not change

Rendition Rule All Renditions

Virtual Document Retention Rule Retain Root and Children

Snapshot Retention Rule Retain Root and Children

Extended Immutability Rule Do not change

Extended Rendition Rule All Renditions

The AS SAP ILM extension reads the config.properties file for custom policies. When the BOFmodule gets a request to apply a retention policy, it will first read this file and see if the path specified



in the PropPatch request is configured for special behavior. If the path is configured, the specifiedpolicy is applied.

Creating default objects for AS SAP ILM extension WebDAVcustomization—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:

— StartDate in the category SAPILM

— FulfillDate in the category SAPILM

• RPS policy named SAPILM0YEARS is created.

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.

Config.properties customization

From DA navigate to /System/Doclink/SAP ILM folder and edit the config.properties as follows:SAPILM.test.path=/SAPILM/OverrideSAPILM.test.policy=overrideSAPILM.admin.username=<install_owner>SAPILM.admin.password=<password>UseRPS=false

For EMC Centera:SAPILM.test.path=/SAPILM/OverrideSAPILM.test.policy=overrideSAPILM.admin.username=<install_owner>SAPILM.admin.password=<password>CenteraRetentionAttribute=i_retain_untilUseRPS=false

Note: For this release, only UseRPS= false is supported.

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 config.properties file located at System > Doclink > SAPILM as follows:

add CenteraRetentionAttribute=<same attribute name configured for centera store>

For example:

CenteraRetentionAttribute=<i_retain_until>

To verify details of clips stored on EMC CenteraNote: This is applicable if Centera is used for storing content and ensuring 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.5. Upgrading to AS SAP 6.5 involves:• Uninstalling previous versions of the AS SAP application. Use the standard uninstall procedureas recommended by the respective application server, as described in Uninstalling ArchiveServices for SAP.

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

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.5:

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:— delete dmc_java_library objects where object_name=’<folder_name>’


Upgrading Archive Services for SAP

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 SPxUpgrading to the latest version of service packs involves the following steps:

1. Stop the application server running assap.war, and delete the assap.war installation.

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, theconfig.properties file has to be edited after you upgrade the service pack.

Note: Make sure the Composer used to install the DAR files matches the version of the AS SAPService pack being installed.


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

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 inSAP’ section of the EMC Documentum ArchiveServices for SAP Configuration Guide.

SAP Document Type Set to NONE (HTTP provided).

Documentum Type Specifies the Documentum document type,as defined in the ’Configuring the RepositoryDocument Type’ section of the Archive Servicesfor SAP Administration Guide.

Workflow Set to No Workflow.

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

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

In the Attribute map, you can also set thefollowing attributes:

• a_storage_type

• a_retention_date



Fieldname Description

Note: More information is in the ’SettingEMC Centera-related Attributes in ArchiveServices’ section of the EMC DocumentumArchive Services for SAP Administration Guide.

Filtering Used to define a custom filter. Used to definethe 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 43.

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 44, 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 45, 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 41.

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


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 by going to https://EMC.subscribenet.com/control/dctm/search and searching for "Composer” to reach the DocumentumComposer download site. Documentum Headless Composer GUI is available within the CSinstallation also at C:\Documentum\product\6.5\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 containany I18N characters or theinstallation will fail.

Input file No The absolute file path to theinstall-based parameter file.

Local folder No The absolute file path tolocalized .properties files.If you want to make yourapplication available in otherlanguages, you need to localizethe project data such as labels,tabs, and descriptions.

Log file No The file to save the log to. If thisis not specified, the file defaultsto <DAR>.log.

Connection broker host Yes The address of the connectionbroker.

Connection broker port Yes The port of the connectionbroker repository.

Repository Yes The name of the repository thatyou want to install the DAR fileto. Click on the Connect buttonafter entering the Docbrokerhost and port to retrieve theavailable repositories.

User name Yes The login name for therepository.



Password Yes The password for logging intothe repository.

Domain No The domain where therepository resides.




Index

Aa_retention_date, 44a_storage_type, 44advanced scalability options, 12, 53

configuring. See load balancing usingApache and Tomcat, configuring

al.properties, 25configuring in UNIX, 26configuring in Windows, 26configuring postinstallation, 26directory path, 26docbases.numberOfConnections, 27numberOfDocbases, 27

all-in-one installation, 12Apache, 53

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

Apache and Tomcat for load balancing,configuring, 53

Apache TomcatJava heap size, 16

application server host requirementsJava heap size, 16

application serverstemporary disk space requirements, 15

Archiveviewing in WebAdmin, 43

Archive Services, 7installing, 15obtaining latest copy of, 16uninstalling, 51

Archive Services for SAP, 7upgrading, 39

ArchiveID, 43ArchiveLink Monitor window, 46Archiving request window, 46archiving.tempDir

customizing in Windows, 26archiving.upload.tempDir

customizing in UNIX, 26Attribute Map, 44attributes

a_retention_date, 44a_storage_type, 44EMC Centera-related, 44in dfc.properties, cache_queries, 27in dfc.properties, dfc.session.max_

count, 27in dfc.properties, local_diskfull_

limit, 27in dfc.properties, local_purge_on_

diskfull, 27

BBEA Weblogic

Java heap size, 16

Ccache_queries, 27configuration file

Apache, 54configuration file, httpd.conf

Apache, 54configuring

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

scalability. See load balancingusing Apache and Tomcat,configuring

Apache and Tomcat for loadbalancing, 53

archive parameters, 43Archive Services, postinstallation, 26load balancing using Apache and

Tomcat, configuring, 53connection


Index

between SAP and Archive Services,testing of, 45

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

installing, 53creating

connections to EMC Centera, 15document type, 45

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

DDEBUG

logging level, 49turning off, 49

defininglogical ArchiveID in SAP, 44

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

dfc.session.max_count, 26disk space requirements, 15docbases.numberOfConnections, 26 to 27docbases.properties, 25document type

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

Documentum TypeDocumentum Download Center. See

SubscribenetDocumentum Type, 43

EEMC Centera

creating connections to, 15

integration with, installationscenario, 12

EMC Centera-related attributes, 44ensuring

the working of repository, 15excessive logging, troubleshooting, 49

Ff.21, 45

Ggeneral prerequisites, 11

Hhttpd.conf, 54

IIBM WebSphere

Java heap size, 16installation

requirements, 7testing, 41troubleshooting issues, 49

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

installingadvanced scalability options. See

installation scenarios, advancedscalability options

all-in-one installation. See installationscenarios, all-in-one installation

Archive Services, 15connectors for Apache and Tomcat, 53integration with EMC Centera. See

installation scenarios, integrationwith Centera

mod_jk, 53on Windows, 16separate Archive Services. See

installation scenarios, separateArchive Services

Solaris, 16integration with EMC Centera, 12intended audience, 7


Index

JJava

heap size, 16

Lload balancing. See advanced scalability

optionsload balancing using Apache and Tomcat,

configuring, 53local_diskfull_limit, 27local_purge_on_diskfull, 27log4j.debug, 49log4j.properties

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

Log4j.properties, 25logging level, DEBUG, 49logical ArchiveID, defining in SAP, 44

Mmaximum number of sessions, 26mod_jk

installing, 53utility, 53

Nnumber of connections established by

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

file, 54numberOfDocbases, 27

Ooac0, 43 to 45oac3, 45oadd, 47oam1, 46ObjectType, SOOD, 45obtaining

latest copy of Archive Services, 16opening

dfc.properties in UNIX, 26dfc.properties in Windows, 26

Oracle Application ServerJava heap size, 16

out of memory errors, 16

Pparameters in archives configuration

page, 43percentage of load, workers.properties

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

Java heap size, 16temporary disk space, 15

preinstallation tasks, 51prerequisites

general, 11software, 11system administrator, 7

Print Listsending, 45viewing, 47

Purpose of the Guide, 7

Rrepository

ensuring the working of, 15number of connections established

by, 27number of, installed, 27setting up connections, 41

SSAP

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

SAP Document Type, 43SAPGUI

ArchiveLink Monitor window, 46Archiving request window, 46Test connection button, 45Transfer drctry field, 44

scenarios, installationadvanced scalability options, 12, 53all-in-one installation, 12


Index

integration with EMC Centera, 12separate Archive Services, 12

sending, Print List, 45separate Archive Services, 12server.xml, 54setting

repository connections, 41setting attributes, EMC Centera-related, 44significant system files, 25software prerequisites, 11SOOD, ObjectType, 45Subscribenet, 16system administrator, 7

prerequisites, 7system files, significant, 25

Ttemporary disk space requirements, 15Test connection button, SAPGUI, 45testing

connection between SAP and ArchiveServices, 45

installation, 41Tomcat, 53

server.xml, 54transaction code

f.21, 45oac0, 44 to 45oac3, 45oadd, 47oam1, 46

transaction code, oac0, 43Transfer drctry field, 44troubleshooting

excessive logging, 49installation issues, 49

turning off DEBUG, 49

Uuninstalling, Archive Services, 51UNIX

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

upgradingArchive Services for SAP, 39

Vviewing

Archive in WebAdmin, 43Print List, 47

WWebAdmin

viewing an Archive, 43Windows

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

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


Documents

EMC Documentum ArchiveServicesforSAP · PDF fileArchiveServicesforSAP Version6.5 InstallationGuide P/N300-006-287RevA04 EMCCorporation ... • Enterprise_Integrations_SAP_ILM.darandtherelateddarinstallerscripts