Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
3.2 Integration Designer best practices<br />
The following best practices pertain to the development of well-performing solutions through<br />
the Integration Designer.<br />
3.2.1 Using share-by-reference libraries where possible<br />
Often, definitions of interfaces, BOs, data maps, mediation subflows, relationships, roles, and<br />
web service ports must be shared so that resources in several modules can use them. These<br />
resources are stored in the library. Libraries can be deployed in several ways:<br />
► With a process application<br />
► With the dependent module<br />
► Globally<br />
You can make your choice in the dependency editor. If you associate a library with a process<br />
application, then you select the application in the editor. The library is shared within the<br />
deployed process application, meaning only one copy is in memory. We call this type of library<br />
a share-by-reference library. The share-by-reference library is a feature that was introduced<br />
in Business Process Manager V7.5.<br />
If you choose to deploy a library with the module, the deployment action creates a copy of the<br />
library for each module when the module is deployed. This type of library is known as a<br />
share-by-value library. Deploying the library with the module is the default setting when the<br />
library is not associated with a process application.<br />
More details about Business Process Manager V8.0 library types is in “Libraries” in the<br />
information center for <strong>IBM</strong> Business Process Manager, Version 8.0, all platforms:<br />
http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/index.jsp?topic=%2Fcom.ibm.wbpm.<br />
wid.main.doc%2Fnewapp%2Ftopics%2Fclibrary.html<br />
3.2.2 Ensure content in Toolkits is needed for multiple applications<br />
Toolkits are copied into each process application that uses them. As such, ensure that a<br />
Toolkit’s content is only artifacts that are needed by multiple process applications to reduce<br />
the size and complexity of the PC Repository. Include process application-specific content<br />
only in the process application itself.<br />
3.2.3 Advanced Content Deployment considerations<br />
Content included in a Process Application (PA) or Toolkit that is authored with the Integration<br />
Designer is considered Advanced Content. When the tip or snapshot of a PA or Toolkit is<br />
activated or deployed, Advanced Content is processed over a different path than Standard<br />
Content. Deployment of Advanced Content often takes much longer to deploy than Standard<br />
Content. This is because Advanced Content is packaged into SCA modules and libraries, and<br />
deployed as Business Level Applications (BLAs) and J2EE EARs on the Process Center or<br />
Process Server. Because each deployed BLA and EAR consumes a non-trivial amount of<br />
resource on the server (memory, disk space, CPU cycles), Advanced Content deployments<br />
should be done the minimum number of times that is practical. Also, Snapshots and PA or<br />
Toolkit Tips that are no longer needed should be proactively cleaned up by deactivating and<br />
undeploying their Advanced Content. These topics are discussed further in the remainder of<br />
this section.<br />
28 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices