Designing processes - EMC Community Network

Designing processes - EMC Community Network Designing processes - EMC Community Network

community.emc.com
from community.emc.com More from this publisher
30.01.2015 Views

Performance and Scalability System configuration guidelines During the planning phase of a project it is important to define the scalability and performance requirements of the solution. Some process-based applications are high volume and require special considerations for deployment in a production environment. System configurations for production deployment can be grouped roughly by size as follows: • Small — Fewer than 300 TaskSpace users, fewer than 10,000 active workflow instances, one central location • Medium — Fewer than 2,000 TaskSpace users and fewer than 100,000 active workflow instances, distributed architecture • Large — More than 2,000 TaskSpace users, more than 100,000 active workflows, distributed architecture with clustering and failover To be accurate, identify sizing parameters such as the numbers of documents, number of activities per process, process duration, and the amount of data processed. One approach is for the project team to create a template that captures relevant sizing parameters and then validates the template with the client. Specify in the template the types of actions required for different volume levels. Large volumes of processes can raise issues of High Availability and Disaster Recovery, which require more complex and robust hardware requirements. Listing the types of equipment to support various volume levels helps clients make informed business decisions. Small configurations The recommended approach to host small configuration environments is to use WMware. Create a separate virtual machine for every tier. Each tier should have roughly 2 to 4 Central Processing Units (CPUs) with 4 GB to 8 GB of Random Access Memory (RAM). A WMware configuration could include: • TaskSpace application server • Content server • Database server • BAM application server • BAM server • BAM database server Medium configurations The recommended approach for medium configuration environments is to use enterprise machines. Software clustering can be used at the application server, database server, and content server levels. WMware can be used for the TaskSpace application server and the BAM application server. Large servers ranging from 4 CPUs to 16 CPUs and 8 GB to 32 GB of RAM are used for each of the following tiers: • TaskSpace application server • Content server • Database server 96 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide

Performance and Scalability • BAM application server • BAM server • BAM database server • BOCS server at branch offices If required, this type of configuration supports multiple content server instances on a single machine and multiple content servers implemented on multiple machines. Large configurations Enterprise machines are used to host large configuration environments. Large configurations include hardware and software clustering at the application server, database server, and content server levels. WMware can be used for the TaskSpace application server and the BAM application server. Large servers with machines ranging from 16 CPUs to 64 CPUs and 32 GB to 128 GB of RAM are used for each of the following tiers: • TaskSpace application server • Content server • Database server • BAM application server • BAM server • BAM database server • BOCS server at branch offices Configuration best practices EMC recommends the following best practices: • Do not run TaskSpace and BAM on the same Java Virtual Machine (JVM). • Keep databases on separate servers. • If WMware is used, ensure that there is a fast pipeline to the Storage Area Network/Network Attached Storage (SAN/NAS). EMC recommends using dedicated Fiber or 10 gigabit Internet Small Computer System Interface (ISCSI). • The network must not experience performance issues and it must have minimal latency. Documentum products are network sensitive and require a high speed network. • All tiers of the server environment must be co-located in the same data center. Consider system sizing during the design phase, since volumetric considerations influence the system design. For example, some process transactions, like the Task List, are high yield, which means that they are performed frequently. A transaction like that can perform well in a test environment, but can cause performance problems when you have many users making simultaneous transactions. Each transaction queries the database that must return results in under one second. Aggregate demand on the database adversely impacts user performance when a browser is unable to render screens in a timely fashion. It can take five seconds or longer in some cases. If there are thousands of simultaneous users querying the database, there may not be enough bandwidth to accommodate the demand and performance continues to degrade. EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 97

Performance and Scalability<br />

System configuration guidelines<br />

During the planning phase of a project it is important to define the scalability and performance<br />

requirements of the solution. Some process-based applications are high volume and require special<br />

considerations for deployment in a production environment. System configurations for production<br />

deployment can be grouped roughly by size as follows:<br />

• Small — Fewer than 300 TaskSpace users, fewer than 10,000 active workflow instances, one<br />

central location<br />

• Medium — Fewer than 2,000 TaskSpace users and fewer than 100,000 active workflow instances,<br />

distributed architecture<br />

• Large — More than 2,000 TaskSpace users, more than 100,000 active workflows, distributed<br />

architecture with clustering and failover<br />

To be accurate, identify sizing parameters such as the numbers of documents, number of activities per<br />

process, process duration, and the amount of data processed. One approach is for the project team<br />

to create a template that captures relevant sizing parameters and then validates the template with the<br />

client. Specify in the template the types of actions required for different volume levels. Large volumes<br />

of <strong>processes</strong> can raise issues of High Availability and Disaster Recovery, which require more complex<br />

and robust hardware requirements. Listing the types of equipment to support various volume levels<br />

helps clients make informed business decisions.<br />

Small configurations<br />

The recommended approach to host small configuration environments is to use WMware. Create a<br />

separate virtual machine for every tier. Each tier should have roughly 2 to 4 Central Processing<br />

Units (CPUs) with 4 GB to 8 GB of Random Access Memory (RAM). A WMware configuration<br />

could include:<br />

• TaskSpace application server<br />

• Content server<br />

• Database server<br />

• BAM application server<br />

• BAM server<br />

• BAM database server<br />

Medium configurations<br />

The recommended approach for medium configuration environments is to use enterprise machines.<br />

Software clustering can be used at the application server, database server, and content server levels.<br />

WMware can be used for the TaskSpace application server and the BAM application server. Large<br />

servers ranging from 4 CPUs to 16 CPUs and 8 GB to 32 GB of RAM are used for each of the<br />

following tiers:<br />

• TaskSpace application server<br />

• Content server<br />

• Database server<br />

96 <strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!