Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
►<br />
►<br />
►<br />
– The generated BPEL flows still use the WICS APIs to perform BO and<br />
collaboration-level tasks. Development effort spent cleaning up the migrated BPEL to<br />
use Business Process Manager APIs instead of the ICS APIs results in better<br />
performance and better maintainability.<br />
– You might be able to replace BPEL processes produced by migration with other<br />
artifacts. All WebSphere InterChange Server collaborations are currently migrated into<br />
BPEL processes. For certain scenarios, other Business Process Manager server<br />
artifacts (for example, business rules) might be better choices. Investigate the BPEL<br />
processes produced by migration to ensure that the processes are the best fit for your<br />
scenario.<br />
Disable Message Logger calls in migration-generated Mediation Flow Components<br />
(MFCs). The WebSphere InterChange Server Migration wizard in Integration Designer<br />
generates an MFC to deal with the mapping details of a connector. This MFC contains the<br />
code for handling synchronous and asynchronous calls to maps that transform<br />
application-specific BOs to generic BOs and generic BOs to application-specific objects.<br />
The generated MFC contains embedded MessageLogger calls that log the message to a<br />
database. Disable these calls if they are not required in your business scenario to reduce<br />
writes to the database and thus improve performance. (Select the MessageLogger<br />
instance, choose the Details panel, and clear the Enabled check box.)<br />
Reduce memory pressure by splitting the shared library generated by the migration<br />
wizard. The migration wizard creates a single shared library and puts all migrated BOs,<br />
maps, and relationships into it. All the migrated modules share this library by copy. This<br />
sharing can cause memory bloat for cases where the shared library is large and many<br />
modules are present. The solution is to manually refactor the shared library into multiple<br />
libraries based on functionality or usage and modify modules to reference only the shared<br />
libraries that they need.<br />
If the original WebSphere InterChange Server maps contain many custom map steps, the<br />
development effort spent in rewriting those map steps results in better performance. The<br />
WebSphere InterChange Server Migration wizard in Integration Designer V8.0 generates<br />
maps that use the ICS APIs at a translation layer above Business Process Manager V8.0<br />
server technologies. Removing this layer by making direct use of Business Process<br />
Manager V8.0 server APIs avoids the cost of translation and produces better performance.<br />
46 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
Change language