Download PDF (1.3 MB) - IBM Redbooks

More documents

Recommendations

Info

In addition, you can customize the number of threads for the Work Manager that use these settings by clicking Resources Asynchronous Beans Work Managers BPENavigationWorkManager. Increase the minimum number of threads from its default value of 5, and increase the maximum number of threads from its default value of 12, using the methodology outlined in 4.7.3, “Tuning for maximum concurrency” on page 64. If the thread pool size is modified, also modify the work request queue size and set it to be twice the maximum number of threads. 4.8.2 Tuning the business process container for Java Message Service navigation If JMS-based navigation is configured, you must optimize the following resources for efficient navigation of business processes: ► Activation specification BPEInternalActivationSpec The Maximum Concurrent Endpoints parameter specifies the parallelism that is used for process navigation across all process instances. Increase the value of this parameter to increase the number of business processes run concurrently. Find this resource in the administrative console by clicking Resources Activation Specifications BPEInternalActivationSpec. ► JMS connection factory BPECFC Set the connection pool size to the number of threads in the BPEInternalActivationSpec plus 10%. Find this resource in the administrative console by clicking Resources JMS Connection factories BPECFC Connection pool properties. This connection factory is also used when Work Manager-based navigation is in use, but only for error situations or if the server is highly overloaded. 4.8.3 Tuning task list and process list queries The programmer creates task list and process list queries in Business Process Manager applications by using the standard query APIs, that is, query() and queryAll(), and related REST and web services interfaces. Task list and process list queries are also created by the query table APIs queryEntities() and queryRows(). All task list and process list queries result in SQL queries against the BPC database. These SQL queries might need special tuning to provide optimal response times, as follows: ► Up-to-date database statistics are key for good SQL query response times. ► Databases offer tools to tune SQL queries. In most cases, additional indexes improve query performance with some potential impact on process navigation performance. For DB2, the DB2 design advisor can be used to guide in choosing indexes. 4.8.4 Tuning Business Process Choreographer API calls Business Process Choreographer (BPC) API calls are triggered by requests external to the Business Process Manager server run time. Examples include remote EJB requests, web service requests, web requests over HTTP, requests that come through the SCA layer, or JMS requests. The connection pools associated with each of these communication mechanisms might need tuning. 74 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
Consider the following hints when tuning the connection pools: ► API calls for task list and process list queries might take more time to respond, depending on the tuning of the database and the amount of data in the database. ► Ensure that concurrency (parallelism) is sufficiently high to handle the load and to use the processor. However, increasing the parallelism of API call execution beyond what is necessary can negatively influence response times. Also, increased parallelism can put excessive load on the BPC database. When tuning the parallelism of API calls, measure response times before and after tuning, and adjust the parallelism if necessary. 4.8.5 Tuning intermediate components for concurrency If the input business object is handled by a single thread from end to end, the tuning for the edge components is normally adequate. In many situations, however, multiple thread switches exist during the end-to-end execution path. Tuning the system to ensure adequate concurrency for each asynchronous segment of the execution path is important. Asynchronous invocations of an SCA component use an MDB to listen for incoming events that arrive in the associated input queue. Each SCA module defines an MDB and its corresponding activation specification (JNDI name is sca/module name/ActivationSpec). The SCA module MDB is shared by all asynchronous SCA components within the module, including SCA export components. Take this shared state into account when you configure the maxConcurrency property value of ActivationSpec. SCA module MDBs use the same default thread pool as those for JMS exports. The asynchronicity in a long-running business process occurs at transaction boundaries (see 3.2.9, “Transactional considerations” on page 38 for more details about settings that affect transaction boundaries). BPE defines an internal MDB and its ActivationSpec as BPEInternalActivationSpec. The maxConcurrency parameter must be tuned by following the same guideline as for SCA module and JMS export MDBs (as described in 4.7.3, “Tuning for maximum concurrency” on page 64). The only issue is that only one BPEInternalActivationSpec exists for a single Business Process Manager server. 4.9 Mediation flow component tuning Additional configuration options are relevant to tuning Mediation Flow Components. These are described in this section. See 5.2, “Mediation Flow Component settings” on page 104 for a suggested set of initial values to use. 4.9.1 Tuning the database if using persistent messaging If you use persistent messaging, the configuration of your database is important. Use a remote DB2 instance with a fast disk array as the database server. You might benefit from tuning the connection pooling and statement cache of the data source. For more information about tuning DB2, see the following sections: ► 4.13, “General database tuning” on page 80 ► 4.14, “DB2-specific database tuning” on page 82 See the relevant references in “Related publications” on page 107. Chapter 4. Performance tuning and configuration 75
Page 1:
IBM ® WebSphere ® Front cover IBM
Page 4 and 5:
Note: Before using this information
Page 6 and 7:
3.1.8 Preventing WSDL validation fr
Page 8 and 9:
4.15.4 Sizing log files appropriate
Page 10 and 11:
Trademarks IBM, the IBM logo, and i
Page 12 and 13:
Now you can become a published auth
Page 14 and 15:
1.1 Products covered in this public
Page 16 and 17:
4 IBM Business Process Manager V8.0
Page 18 and 19:
2.1 Top tuning and deployment guide
Page 20 and 21:
Two individuals with the following
Page 22 and 23:
Turn off auto-tracking in business
Page 24 and 25:
Avoid use of anonymous derived type
Page 26 and 27:
► ► Independent Disks (RAID) ad
Page 28 and 29:
that can process 10 requests per se
Page 30 and 31:
2.4.2 Use a high-performing browser
Page 32 and 33:
Batched inputs: Sending large objec
Page 34 and 35:
2.7 Business Monitor This section d
Page 36 and 37: 3.1 Process Designer development be
Page 38 and 39: 3.1.5 Use sequential system lane ac
Page 40 and 41: 3.2 Integration Designer best pract
Page 42 and 43: 3.2.4 Business object parsing mode
Page 44 and 45: Applications benefiting from lazy p
Page 46 and 47: Business object instance validator
Page 48 and 49: 3.2.6 Business Process Execution La
Page 50 and 51: Client systems that follow a page-f
Page 52 and 53: 3.2.10 Invocation style considerati
Page 54 and 55: If a number of services in a FanOut
Page 56 and 57: Aggregation blocks (FanOut and FanI
Page 58 and 59: ► ► ► - The generated BPEL fl
Page 60 and 61: 4.1 Performance tuning methodology
Page 62 and 63: This information is useful for obta
Page 64 and 65: ► ► ► ► Messaging and messa
Page 66 and 67: If you click Generational Concurren
Page 68 and 69: 4.3.7 Messaging engine properties T
Page 70 and 71: ► ► Ensure that database statis
Page 72 and 73: 4.5.8 Define Authentication Alias w
Page 74 and 75: 4.6 Process Center tuning Because a
Page 76 and 77: peak throughput, so if an adapter i
Page 78 and 79: esources (for example, a DB2 databa
Page 80 and 81: Use the following steps to place al
Page 82 and 83: 4.7.5 Clustered topology tuning One
Page 84 and 85: To check the Business Space target
Page 88 and 89: 4.9.2 Disabling event distribution
Page 90 and 91: This processing and reporting mode
Page 92 and 93: 4.13 General database tuning This s
Page 94 and 95: 4.14 DB2-specific database tuning P
Page 96 and 97: Increasing the primary log file siz
Page 98 and 99: When running clustered applications
Page 100 and 101: Using materialized query tables Whe
Page 102 and 103: 4.15.8 Special considerations for l
Page 104 and 105: 4.16.1 Monitoring garbage collectio
Page 106 and 107: Increasing the maximum size of the
Page 108 and 109: 96 IBM Business Process Manager V8.
Page 110 and 111: 5.1 Business Process Manager server
Page 112 and 113: Tuning variations Microflow: Number
Page 114 and 115: DB2 database server in three-tiered
Page 116 and 117: ► Set the Maximum Connections pro
Page 118 and 119: 106 IBM Business Process Manager V8
Page 120: ► ► ► ► ► Understanding a
show all

Download PDF (1.3 MB) - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?