08.06.2014 Views

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Aggregation blocks (FanOut and FanIn)<br />

Aggregation is an important MFC pattern. It enables a single inbound request to map into<br />

multiple outbound service invocations, the responses from which can be aggregated into a<br />

single response to the original request. Before you develop mediations using aggregation<br />

design patterns, you need to consider several performance factors. See the developerWorks<br />

topic about best practices, “Aggregation design patterns and performance considerations in<br />

WebSphere Enterprise Service Bus V7.5” at the following location:<br />

http://www.ibm.com/developerworks/websphere/library/techarticles/1111_norris/1111_<br />

norris.html<br />

Configuring Mediation Flow Component resources<br />

When creating resources using Integration Designer, the application developer might choose<br />

to use preconfigured MFC resources or let the tool generate the mediation flow-related<br />

resources that it requires. Both approaches have their advantages and disadvantages.<br />

Preconfigured resources help in the following circumstances:<br />

► Existing resources are to be used<br />

► External creation and tuning scripts are to be applied<br />

Preconfigured resources also allow easier post-deployment adjustment.<br />

Tooling-created resources are suitable if no further need exists for creating resources using<br />

scripts or the administrative console. Most performance tuning options can be changed<br />

because they are now exposed in the tooling.<br />

In our performance tests, we used preconfigured resources because segregating the<br />

performance tuning from the business logic makes it possible to maintain the configuration for<br />

different scenarios in a single script.<br />

3.3 Browser environment considerations<br />

When using a browser for developing or evaluating Business Process Manager client<br />

solutions through the Process Portal or Business Space, developers often alter the<br />

configuration of the browser to perform debugging, tracing, and other browser functions.<br />

However, some of these configuration changes can dramatically affect the performance of the<br />

Business Process Manager solution. Before rolling out a solution to production or obtaining<br />

performance measurements, review this section and observe its guidelines.<br />

Disable or uninstall add-ins or extensions for production use<br />

An important consideration is using add-ins or extensions for your browser environment. If<br />

you experience performance problems while using the browser, make sure you disable or<br />

uninstall all add-ins or extensions unless they are necessary.<br />

Avoid Developer Tools render or compatibility mode in Internet Explorer<br />

In Internet Explorer (IE), placing the browser in compatibility mode or in a render mode<br />

equivalent to an older browser version by using the Developer Tools is possible. This option<br />

can be useful for developing or debugging solutions (for example, making an IE 8 browser<br />

behave as an IE 7 browser for compatibility testing). However, make sure that you do not use<br />

these settings in production.<br />

44 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices

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

Saved successfully!

Ooh no, something went wrong!