Designing processes - EMC Community Network
Designing processes - EMC Community Network Designing processes - EMC Community Network
Monitoring Business Activity • Use both report filters and dashlet filters as methods to reduce the number of records that appear in simple reports. This is especially true for bar and pie charts where 12 or more records make these reports difficult to read. • Modify the length of bar chart labels with the Limit Characters chart property. • Edit entity field captions so they are shorter. • Suppress chart animation in the Chart Properties window. • Remove the chart legend. • Use computed columns to shorten long date values. Computed Column dates and sorting The Computed Columns feature can be used to display Start Date and Time data in a number of date formats. For example, the Start Date and Time value of April 7, 2009 3:46:40 PM can be formatted as April 7, 2009, 4/7/2009, or Apr 7. The new date format can be displayed as the x-axis in a report. To display dates chronologically (and not alphabetically), select the original Start Date and Time column in the Sort field of the Chart Data window. In the following example, a computed column (date) is selected as the x-axis while Start Date and Time is selected as the sort column. 94 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Chapter 8 Performance and Scalability This chapter discusses the following: • General approach to performance • System configuration guidelines • Factors that affect performance and scalability • Recommended application server settings • Recommended Content Server settings • Recommended database server settings • Tuning and troubleshooting performance problems General approach to performance This section discusses general performance theory. Performance analysis treats a large number of different metrics, such as response time, throughput, efficiency, and capacity. The two that are the most important to process-based applications are response time and throughput. • Response time measures the amount of time you must wait to receive any response to a request; for example, running a series of automated activities may incur a response time of one second between each one. • Throughput measures the number of transactions the system can process per unit of time; for example, a system may be able to handle only 100 TaskSpace searches per minute. As you design the application, you should: • Not go deep. The reason for the recommendation to not go deep is that every layer of database tables generates additional joins that impact performance. You should keep your inheritance hierarchy as flat as you can. • Tune for the highest-yield queries. Yield is the number of times a query is executed multiplied by the execution time of the query. By anticipating the yield and tuning it for the highest-yield query, your performance does not degrade unacceptably for that use case. To achieve this you may need to de-normalize, pulling attributes into one or two physical tables. In general, the recommended approach to performance testing is to carry out two classes of tests: • Single user profiling — In single-user profiling you run unit tests, such as collecting Documentum Class Library (DMCL)/DFC traces. • Load testing — In load testing you are looking for bottlenecks and capacity issues. EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 95
- Page 44 and 45: Designing the Process because the i
- 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 96 and 97: Performance and Scalability System
- 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 -
Monitoring Business Activity<br />
• Use both report filters and dashlet filters as methods to reduce the number of records that appear<br />
in simple reports. This is especially true for bar and pie charts where 12 or more records make<br />
these reports difficult to read.<br />
• Modify the length of bar chart labels with the Limit Characters chart property.<br />
• Edit entity field captions so they are shorter.<br />
• Suppress chart animation in the Chart Properties window.<br />
• Remove the chart legend.<br />
• Use computed columns to shorten long date values.<br />
Computed Column dates and sorting<br />
The Computed Columns feature can be used to display Start Date and Time data in a number of date<br />
formats. For example, the Start Date and Time value of April 7, 2009 3:46:40 PM can be formatted<br />
as April 7, 2009, 4/7/2009, or Apr 7. The new date format can be displayed as the x-axis in a report. To<br />
display dates chronologically (and not alphabetically), select the original Start Date and Time column<br />
in the Sort field of the Chart Data window. In the following example, a computed column (date) is<br />
selected as the x-axis while Start Date and Time is selected as the sort column.<br />
94 <strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Change language