Minimum Hardware Configurations for
EMC Documentum Archive Services for SAP
Practical Sizing Guide
Abstract
The sizing of hardware in a deployment of EMC Document Archive Services for SAP is determined by a number of factors. Starting from minimum requirements, this guide offers actionable information to give a head start in the planning process. Configurations with single server, multiple machines and optional load balancing are discussed.
Minimum Hardware Configurations for EMC Documentum Archive Services for SAP 2
Copyright © 2006 EMC Corporation. All rights reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com
Table of Contents
Executive summary ... 4
Introduction ... 4
Hardware configurations... 4
Single machine ... 4
Multiple machines ... 4
HTTP-based load-balancing Archive Services for SAP... 5
Sizing for UNIX hardware ... 5
Scalability ... 5
Processor impact ... 6
I/O impact... 6
Network bandwidth impact... 6
Minimum Hardware Configurations for EMC Documentum Archive Services for SAP 4
Executive summary
The expected volume of archived content, specific for each type of archiving, gives the starting point for hardware estimates.
Hardware can be configured with a Single Server, Multiple Servers, and using HTTP-based load-balancing.
Introduction
Generally, use the Documentum System Sizing Tool available via the CustomerNet Developer website to determine hardware requirements. Use anticipated volume estimates for archiving to input equivalents of users.
At the minimum collect the following information as applicable to the customer requirements: Data-Archiving: Planned number and size of ADK files per month for archiving. Printlist Archiving: Planned number and size of ALF files per month for archiving Assume ratio of 1-5 read accesses for each printlist for retrieval. Imaging: Planned number of incoming documents for archiving.
Assume 40K-50K per TIFF page for size.
Assume ratio of 5-10 read accesses for each image for retrieval.
Hardware configurations
Single machine
EMC Documentum Content Server, Database and Archive Services for SAP are hosted on a single machine.
• 2 Processors or more (with Pentium IV Class processor if the OS is Windows 2000 or Windows 2003)
• 4 GB RAM
• 100 GB free HDD with RAID 0 (2 disks, test only) or RAID 5 (min 3 disks, recommended for production)
• An initial JAVA Heap Size of 512 MB in the Catalina properties is also recommended. • 1GB/s network connections to the SAP server.
For larger environments, use the Documentum System Sizing Tool. For Archive Services for SAP, add 1-2 processors and 1-2 GB of RAM.
Multiple machines
Content Server and the Database are hosted on one server machine, and the Archive Services for SAP is on another server machine.
• Content Server + Database machine
o 2 Processor or more (with Pentium IV Class processor if the OS is Windows 2000 or Windows 2003)
o 4 GB RAM
• 100 GB free HDD with RAID 0 (2 disks, test only) or RAID 5 (min 3 disks, production) • Archive Services for SAP machine
o 1 Processor or more (with Pentium IV Class processor if the OS is Windows 2000 or Windows 2003)
o 2 GB RAM
o 20 GB free HDD, recommend RAID 0 (2 disks, test only) or RAID 5 (min 3 disks, production) configuration
o An initial JAVA Heap Size of 512 MB in the Catalina properties is also recommended. • A Network Bandwidth of 1 Gbps or more between the two machines
• 1GB/s network connections to the SAP server.
Note: The Database can be Oracle 9i or later or a MS SQL Server 2000, Web Application Server being Tomcat 5.0.28.
HTTP-based load-balancing Archive Services for SAP
Content Server and the Database are hosted on one server machine, and Archive Services for SAP is installed on multiple server machines, using Apache Tomcat Load-Balancing
(http://tomcat.apache.org/tomcat-5.0-doc/balancer-howto.html) • Content Server and Database machine
o Use Content Server Sizing tool
o Input equivalents of user sessions based on estimated archiving and retrieval activity • Archive Services for SAP machines
o 1 Processor or more (with Pentium IV Class processor if the OS is Windows 2000 or Windows 2003)
o 2 GB RAM
o 20 GB free HDD, recommend RAID 0 (2 disks, test only) or RAID 5 (min 3 disks, production) configuration
o An initial JAVA Heap Size of 512 MB in the Catalina properties is also recommended. • A Network Bandwidth of 1 Gbps or more between the all machines
• 1GB/s network connections to the SAP server
Sizing for UNIX hardware
For Unix hardware use rough equivalents of the above Windows sizing. Refer to the manufacturer data sheets for details on processor speed, memory consumption and I/O performance.
Please refer to the Release Notes for details on supported operating systems and hardware architectures. Physical machines hosting the solution components like database, Content Server, Archive Server and SAP servers may be of any combination of hardware platforms, as long as appropriate network connectivity is provided.
Scalability
Minimum Hardware Configurations for EMC Documentum Archive Services for SAP 6
Processor impact
It is observed that scaling up the system with more processors improves the performance of archiving considerably. When the number of processors is increased from 1 to 2, there is a 40% - 45% reduction in the response time of archive creation. The search and retrieval operations also show improvement of up to 30%.
I/O impact
I/O-related devices of the machine, on which Archive Services for SAP is installed, have significant impact on the performance of the application. When using striped disks with RAID 0, there is a 15% - 18% reduction in the response time. This is especially true when large archived documents are fetched. If the repository and database also run on striped disks with RAID 0, there is 10% – 12% reduction in the response time for creation of archives.
Network bandwidth impact
A good network connectivity between the SAP system, the repository, the database, and the application server running Archive Services for SAP improves the performance considerably. When the network connectivity between repository machine and application server machine is increased from 100 mbps to 1Gbps, there is a 40% improvement in the throughput of Archive Services for SAP.
Conclusion
The minimum hardware configuration recommended for EMC Documentum Archive Services for SAP is a moderate PC-strength server. More processing power and configurations with multiple machines are available for higher performance, starting from configurations detailed in this paper.
