Designing processes - EMC Community Network

More documents

Recommendations

Info

Performance and Scalability Skill-set matching Skill-set matching is another feature that, if not used wisely, can lead to system performance issues. There are two reasons for system performance issues. First, skill-set matching involves row-by-row processing where every task that returns in a task list is evaluated against the user’s competency. This is a drain on system resources. Second, skill-set matching does not use task list database query language (DQL) optimizations. Without skill-set matching, a task list brings back the first 100 to 300 tasks. This means that the data list generated requires less resource consumption and performs faster. To bring back the tasks to the user when the system matches user skills against tasks, it requires the whole data list. This means that all tasks are sent to the application server for evaluation against the skill-set. If a task list contains 10,000 tasks, it brings back 10,000 tasks. Even if the user matches one task out of 10,000 the system still brings back 10,000 tasks, which takes time. A task list with 10,000 tasks that does not match skill-sets brings back 100 to 300 tasks depending on the number of SDTs involved. It is a best practice to calculate a baseline timing of a task list before implementing skill-sets. This baseline calculation enables you to determine how skill-set matching impacts performance. It is important to realize that performance costs grow as the number of tasks grow in a task list. For example, a task list that returns 100,000 tasks is unusable. Logins The user login operation takes 2 seconds to 10 seconds to complete. The variable that most influences the login time is the landing tab that opens after a user logs in. If the client prefers a fast login, then set the landing page to the default page or to a blank search page. However, if the user has a preference about the tab, then the time to log in can take longer. Recommended application server settings EMC recommends using the following application server settings: Recommended Java Flags for a tomcat server JAVA_OPTS=-server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -XX:+UseParallelOldGC Server flag (-server) explanation JVM server mode provides better performance for long running tests. This must be the first flag. Permanent generation (-XX:MaxPermSize) explanation The application dynamically generates and loads many classes expanding the space in the heap to accommodate its reuse. Parallel garbage collection (-XX:+UseParallelOldGC) explanation This allows the JVM to use parallel garbage collection for the full collections. JVM Capacity Heap size and threads control the number of users the JVM can support. A JVM can accommodate 150 to 300 users per instance depending on the user activity footprint (opening large forms can reduce the number of users) and throughput (how fast they are trying to finish the tasks). Response times degrade as more users enter the JVM. The degradation is due to non-availability of free heap space and users waiting for available threads. EMC recommends a 1024 MB heap. A heap size smaller than 512 MB 100 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Performance and Scalability results in an out-of-memory error. If the permanent generation is not increased to a minimum of 128 MB, it could also result in an out-of-memory error. The CPU is the first resource to bottleneck on this tier. The application server is the most scalable tier in the system because there is no limit to the number of JVM or servers that can be added. Additional tips • Configure JVM memory minimum and maximum heap size arguments to be the same. • If running Oracle WebLogic or IBM Web Sphere application server, apply different JVM memory arguments for Administrative and Managed Servers (less resources). Allocate less memory to the administrative server of each cluster and more memory to the managed server. • Each JVM has a finite capacity number of users it can accommodate. To increase the number of users a physical server can accommodate, create several JVM nodes on the server. Each JVM needs to have a different port. It is not uncommon for a physical server to have 4, 8, or 12 JVM instances. • If running WebLogic, have one Internet Information Services (IIS) server installed on each web server host machine and for each IIS server installation provide appropriate mappings to the different cluster Internet Protocols (IPs). • If running WebLogic, use JRockit. • Turn off AnnotationHelper for Tomcat 6.x. To turn off AnnotationHelper, set metadata-complete=true in the tag of the web.xml file. • In web.xml, you can increase the value of to push off the expiration date for files, such as icons and images, on the client side cache. Recommended Content Server settings To ensure that Content Server is running to its potential, turn off mail notification, if possible. To turn off mail notification, put MAIL_NOTIFICATION=F in the server.ini and reboot. Also, narrow the audit trails to track only the essential events. Audits can slow down response times and increase CPU on the Content Server and database. Increasing CPU usage decreases performance on the content server. The Content Server is scalable. You can add a second Content Server to the same or different server without causing a problem, but both Content Servers should be close in proximity. If a second Content Server is created either on the same or a different server, configure the server.ini file to make it also project to the docbroker with the same proximity. Turn off debugging on the process engine. By default, the debug mode is turned on. This results in unnecessary Input/Output (IO) and CPU resource consumption. To turn off debugging, copy and paste the following to the xml file: %Documentum%\jboss4.3.0\server\DctmServer_MethodServer\conf\jboss-log4j.xml (Windows) $DOCUMENTUM_SHARED/jboss4.3.0/server/DctmServer_MethodServer/conf/jboss-log4j.xml (UNIX/Linux) EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 101
Page 1 and 2:
EMC ® Documentum ® xCelerated Com
Page 3 and 4:
Table of Contents Chapter 1 Overvie
Page 5:
Table of Contents Chapter 8 Cleanin
Page 8 and 9:
Preface 8 EMC Documentum xCelerated
Page 10 and 11:
Overview • Provides security and
Page 12 and 13:
Overview 12 EMC Documentum xCelerat
Page 14 and 15:
Product Overview Documentum ECM pla
Page 16 and 17:
Product Overview Process automation
Page 18 and 19:
Planning and Designing the Applicat
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Creating the Data Model submitter_a
Page 32 and 33:
Creating the Data Model should occu
Page 34 and 35:
Designing the Process Defining acti
Page 36 and 37:
Designing the Process The transitio
Page 38 and 39:
Designing the Process 2. Add a seco
Page 40 and 41:
Designing the Process The end resul
Page 42 and 43:
Designing the Process To copy all v
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 76 and 77: Creating the User Interface Adaptor
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 96 and 97: Performance and Scalability System
Page 98 and 99: Performance and Scalability Factors
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
Page 146 and 147: Designing the Average Duration repo
Page 148 and 149: Designing the New Account by Custom
Page 150 and 151:
Designing the New Accounts by Custo
Page 152 and 153:
Designing the New Accounts Opened t
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Designing the New Accounts Opened L
Page 160 and 161:
Completing the prototype dashboard
Page 163 and 164:
Index A activities count children,
Page 165:
Index designing activity triggers,
show all

Designing processes - EMC Community Network

Create successful ePaper yourself

Delete template?

Save as template?