Designing processes - EMC Community Network
Designing processes - EMC Community Network Designing processes - EMC Community Network
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
- Page 46 and 47: Designing the Process 3. On the Tim
- Page 48 and 49: Designing the Process 48 EMC Docume
- Page 50 and 51: Designing the Process Inter-process
- Page 52 and 53: Designing the Process In the HTTP I
- Page 54 and 55: Designing the Process For the child
- Page 56 and 57: Designing the Process at or right a
- Page 58 and 59: Designing the Process Enabling repo
- Page 60 and 61: Designing the Process Performance a
- Page 62 and 63: Designing the Process 62 EMC Docume
- Page 64 and 65: Creating the User Interface mind th
- Page 66 and 67: Creating the User Interface Figure
- Page 68 and 69: Creating the User Interface 4. Sele
- Page 70 and 71: Creating the User Interface Figure
- Page 72 and 73: Creating the User Interface Figure
- Page 74 and 75: Creating the User Interface Figure
- Page 76 and 77: Creating the User Interface Adaptor
- Page 78 and 79: Creating the User Interface Figure
- Page 80 and 81: Creating the User Interface 5. Spec
- Page 82 and 83: Creating the User Interface 1. Open
- Page 84 and 85: Creating the User Interface 11. In
- Page 86 and 87: Creating the User Interface Working
- Page 88 and 89: Creating the User Interface 88 EMC
- Page 90 and 91: Monitoring Business Activity • pu
- Page 92 and 93: Monitoring Business Activity (PRS).
- Page 94 and 95: Monitoring Business Activity • Us
- Page 98 and 99: Performance and Scalability Factors
- Page 100 and 101: Performance and Scalability Skill-s
- Page 102 and 103: Performance and Scalability
- Page 104 and 105: Performance and Scalability If regi
- Page 106 and 107: Performance and Scalability 106 EMC
- Page 108 and 109: Deploying the Application At deploy
- Page 110 and 111: Deploying the Application 110 EMC D
- Page 112 and 113: Archiving the Application • When
- Page 114 and 115: Archiving the Application b. Log in
- Page 116 and 117: Archiving the Application 5. Create
- Page 118 and 119: Archiving the Application h. Select
- Page 120 and 121: Archiving the Application 120 EMC D
- Page 122 and 123: Prototyping overview Prototyping ov
- Page 124 and 125: Understanding the approach to proto
- Page 126 and 127: Create and run the New Account Appl
- Page 128 and 129: Designing the New Account Applicati
- Page 130 and 131: Designing the New Account Applicati
- Page 132 and 133: Design dashboard and add dashlets 1
- Page 134 and 135: Design dashboard and add dashlets 1
- Page 136 and 137: Process Duration alert 3. From the
- Page 138 and 139: Process Duration alert 17. On the k
- Page 140 and 141: Designing the New Account Process -
- Page 142 and 143: Designing the New Account Process -
- Page 144 and 145: Running the Average Duration proces
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