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<br />
Chapter 3.<br />
Development best practices<br />
This chapter presents best practices that are relevant to solution developers. It addresses<br />
modeling, design, and development choices that are made while designing and implementing<br />
a Business Process Manager V8.0 solution. Business Process Manager Advanced Edition<br />
offers two authoring environments. These authoring environments both interact with the<br />
Process Center, which is a shared repository and runtime environment.<br />
►<br />
►<br />
In the Process Designer environment, you can model, develop, and deploy BPMN<br />
business processes, which often have human interactions. The Process Designer is the<br />
only authoring tool for Business Process Manager V8.0 Standard Edition.<br />
In the Integration Designer environment, you can build and implement services that are<br />
automated or that start other services, such as web services, enterprise resource<br />
applications, or applications running in CICS and IMS. These services and applications<br />
exist in the enterprise. It is also the tool to use to author Business Process Execution<br />
Language (BPEL) business processes.<br />
Two individuals with separate roles and skill sets work together when developing Business<br />
Process Manager applications. These roles correspond to the Process Designer and<br />
Integration Designer environments.<br />
►<br />
►<br />
The business author is responsible for authoring all business processes. The business<br />
author is able to use services but is not interested in the implementation details or how<br />
they work. The business author uses Process Designer to create business process<br />
diagrams (BPDs), and utilizes advanced integration services (AISs) to collaborate with the<br />
integration programmer.<br />
The integration programmer is responsible for doing all of the integration work necessary<br />
to support the processes the business author creates. For example, the integration<br />
programmer implements all the AISs and produces mappings between back-end formats<br />
and the requirements of current applications. The integration programmer uses<br />
Integration Designer.<br />
The remainder of this chapter is organized based on the type of user, with separate sections<br />
describing Process Designer (business author) and Integration Designer (integration<br />
programmer) best practices. Additionally, the chapter provides developer considerations for<br />
browser environments, and for WebSphere InterChange Server migration.<br />
© Copyright <strong>IBM</strong> Corp. 2013. All rights reserved. 23