Download PDF (1.3 MB) - IBM Redbooks

Business object instance validator
The lazy parsing instance validator provides a higher fidelity validation of BOs, particularly for
facet validation of property values. Because of these improvements in fidelity, the lazy parsing
instance validator catches functional issues not detected in eager parsing mode and provides
more detailed error messages.
Migration of XSL style sheets
When an application authored using WebSphere Integration Developer V7.0.0.1 or earlier,
the application is migrated using Integration Designer V8.0 and rebuilt. Extensible Stylesheet
Language Transformation (XSLT) style sheets are regenerated from the associated map files.
Extensible Style Sheet Language (XSL) style sheets built by Integration Designer V8.0 no
longer contain white space or indent directives. This change improves performance in lazy
parsing mode. However, if an XSLT primitive refers directly to manually edited style sheet, the
style sheet is not regenerated when the application is built. In this case, performance
improves by removing the white space directive ( ) if it
appears, and by ensuring that indentation is disabled (indent="no") unless required.
Private APIs
The BO programming model provides support for BO application programming interfaces
(APIs) and a set of Service Data Object (SDO) APIs. In some cases, applications might use
additional implementation-specific APIs that are not part of the supported APIs for BOs. For
example, an application might use the Eclipse Modeling Framework (EMF) APIs. Although
these APIs might have worked in prior Business Process Manager releases and in eager
parsing mode, they are not supported APIs for accessing BOs. EMF APIs are considered
private to the implementation of BOs and should not be used by applications.
For these reasons, remove private APIs from the application and ensure that all BO access
takes place using the supported API set.
Service Message Object Eclipse Modeling Framework APIs
A Mediation Flow Component makes it possible to manipulate message content using the
Java classes and interfaces provided in the com.ibm.websphere.sibx.smobo package. For
lazy parsing, the Java interfaces in the com.ibm.websphere.sibx.smobo package can still be
used. However, methods that refer directly to Eclipse Modeling Framework (EMF) classes and
interfaces or that are inherited from EMF interfaces are likely to fail. Also, the Service
Message Object (SMO) and its contents cannot be cast to EMF objects when using lazy
parsing.
Migration
All applications developed before Business Process Manager V7.5 used eager parsing mode,
by default. When Business Process Manager runtime migration moves these applications,
they continue to run in eager parsing mode.
To enable an application, that was originally developed using eager parsing, to use lazy
parsing, first use the Integration Designer to move the artifacts of the application. After
migration, use the Integration Designer to configure the application to use lazy parsing.
For information about moving artifacts in the Integration Designer, see “Migrating source
artifacts” in the IBM Business Process Manager Information Center:
http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/index.jsp?topic=%2Fcom.ibm.wbpm.
wid.imuc.doc%2Ftopics%2Ftmigsrcartwid.html
34 IBM Business Process Manager V8.0 Performance Tuning and Best Practices