Architecture

Below are the components in IBM BPM architecture:

1. Process Apps
   A Process Application is the container for a solution, much like a project. First you will create the Process Application within the Process Center Console and you give it both name and a unique tag, or an acronym, that is no more than seven characters in length. Once created, a Process Application can have additional artifacts added to it using the BPM Process Designer (PD) tooling. Both the Process Application and its artifacts are stored in a repository managed by the Process Center.
   Process Applications can be created via the Process Center console, either via its web interface or from within BPM PD. The button to create a new Process Application is on the main Process Apps page. When a new Process Application is created, a dialog opens asking for a name and acronym for the new application.
   A "state" of the Process Application can be captured in a "snapshot" anytime. In creating a snapshot, all artifacts and their respective content are captured at that moment. Modifications done to the Process Application after the snapshot are not represented in previous snapshots. More snapshots can be created anytime.
   Process Applications generally house one or more Business Process Definitions. These Business Process Definitions are models of processes that at some future date will become executable. In this book, I make use of the terminologies BPDs and BPMN processes interchangeably since they mean the same thing.
2. Toolkits
   A Toolkit can be considered as a container for artifacts used in solutions, much like a Process Application. However, unlike a Process Application, a Toolkit itself does not result in a deployable application. Rather, the contents of the Toolkit may be "included" or "used" by one or more Process Applications.
   Whenever Process Center is installed and configured, an IBM-supplied Toolkit called "System Data" gets automatically imported into the repository. See System Data Toolkit for more details.  
   This toolkit is marked as read-only and it is implicitly dependent on all other Process Applications and Toolkits. The System Data Toolkit contains core definitions for data structures and other items common across all Process Applications.
   The toolkits have their own tabs in the Process Center console. There, creation, exportation, management of new toolkits can be done similarly to process applications.
   Similarly, as in Process Application, one can take snapshots of Toolkits. By doing this, all artifacts inside a toolkit are considered a particular version. In order to add a toolkit as a dependency of a Process Application, the toolkit itself must first have at least one snapshot associated with it. This is because the dependency added to the Process Application is not just the name of the Toolkit, but a snapshot of that Toolkit. Once a snapshot of the Toolkit has been taken, in the Designer view of PD a dependency can be added by clicking the + icon next to the Toolkits entry. A list of potential Toolkits and their associated snapshots will be shown for selection. Every solution developed using IBM BPM is encapsulated in its own Process Application (Process App). The Process App is the deployable unit to a Process Server for execution. This is all very well when developing just one solution, but when a second solution is developed, it soon becomes apparent that many of the first solution's artifacts can be used by the second. While it is certainly possible to copy these artifacts from one solution into another, this results in duplication. Any changes to one of the copies would either have to be repeated in the other or risk the copies getting out of sync. A better option is to be able to have a single definition of an artifact that can be used by both solutions. This produces a set of common artifacts used by applications. This concept is supported by IBM BPM through the use of "toolkits." A toolkit is a named collection of artifacts that differ from a process application in one critical way: it doesn't deploy. Artifacts contained in a created toolkit can then be used in other process apps, and even in other toolkits, by declaring dependencies. The dependency is declared; the artifacts inside that toolkit are then wholly available to the solution—as if they were copied in—without the actual duplication. As with any human endeavor, there is a right and wrong way to go about organizing artifacts in a toolkit. We will now consider some suggestions on what tends to work well and what doesn't.
   
3. IBM BPM Components
   • Process Server
     IBM BPM Process Server is a robust, scalable runtime environment for the execution of business processes and services modeled in IBM Business Process Manager (BPM). It is the execution engine for process applications that help organizations effectively automate and manage their business processes. Basically, IBM BPM Process Server represents the deployment and runtime environment for business process definitions created using design tools from IBM BPM. Such process definitions are contained within Process Applications and Toolkits and define the sequence of activities, business rules, data transformations, and integrations involved in realizing the specific business goals. The Process Server itself has to guarantee the reliable and effective execution of these processes with respect to the defined business logic and policy. Long-running business processes with complexity are one of the key strengths of the IBM BPM Process Server. Of the key features it supports, process instance persistence makes it possible for a process to be paused and later resumed if need be, so that important business operations do not get disrupted. This becomes particularly relevant for processes that require human intervention or interaction with external systems, as it allows for seamless continuation in case of interruptions. The Process Server comes with fully developed monitoring and management capabilities. Through the use of the IBM BPM Process Portal and other administrative tools, end-users can track process performance, monitor KPIs, and obtain a real-time "sense" regarding process execution. This helps an organization leverage visibility to know where bottlenecks are, thus optimizing its processes to ensure conformance to business standards and regulations. Another backbone of the IBM BPM Process Server is integration. This allows integration with a very large base of enterprise systems, databases, and applications, and enables the smooth exchange of data between these and interoperability. This integration capability enables the implementation of end-to-end business processes that span several systems and organizational boundaries. Security is in-built at the very center of any IBM BPM Process Server. It thus backs various rigorous measures, such as authentication, authorization, and encryption, in protecting organizational data and providing access and run-time rights for process execution to only authorized users. In a nutshell, IBM BPM Process Server is an enterprise business process execution and management platform that provides scalability, reliability, and wide integration capabilities. Handling of complex workflows and support for real-time monitoring add to its security features, making this tool an important building block for any BPM strategy within an organization.
   • Process Center
     Essentially, IBM BPM Process Center is a fully-fledged development and management environment for creating, testing, and deploying business process applications. It provides the umbrella Process Center in IBM Business Process Manager that facilitates an excellent collaborative working space for process designers, developers, and business analysts to work together seamlessly. At the heart of the Process Center is its ability to manage the entire life cycle of process applications. This includes business process modeling tools, user interface design, definition of business rules, and integration with external systems. It is this which gives organizations the ability to construct sophisticated and efficient business process solutions based on strategic goals. Process Center supports version control and change management, so teams can track changes and versions, and be certain that all relevant stakeholders are updated. This is important for coherence but also to avoid editing conflicts in a case where various users may be working on different parts of a process application simultaneously. Another primary feature of Process Center is collaboration. It offers a shared repository where all process assets—process models, data definitions, and service implementations—are stored and managed for the project. This center-based approach facilitates collaboration among people to a very great extent by reusing created artifacts and guaranteeing that everyone works with the most recent information. It also features powerful test and validation tools within the Process Center. Simulate process execution, test business rules, and validate integrations before deploying applications to the production environment. This enables any problems to be detected and resolved early in the development cycle, reducing the likelihood of errors and improving the quality of the final solution. Process Center makes deployment smooth. A process application is deployed to the IBM BPM Process Server for execution once ready. The Process Center efficiently controls and handles deployment. Besides this, there are sound governance features of the Process Center that empower the organization to define and enforce policies and standards in the development of processes. This assists in ensuring compliance with regulatory provisions as well as internal guidelines, improving the overall quality and consistency of process applications. Finally, IBM BPM Process Center is a very powerful tool when it comes to developing, managing, and deploying business process applications. With its comprehensive collaboration, version control, test, and governance features, it is therefore an element of prime importance in any initiative of BPM where efficiency, consistency, and quality are wanted in process development.
   • Process Designer
     IBM BPM Process Designer offers a powerful and intuitive environment for business analysts, process designers, and developers to create and optimize business process models. It is one of the key components of the IBM Business Process Manager (BPM) suite that provides an intuitive user interface for designing, simulating, and refining business processes.

Basically, IBM BPM Process Designer provides a drag-and-drop facility to the user for creating fine details of process models. This quite graphical approach is taken to detail the sequence of activities, decision points, and data flows constituting a business process. Thus, the steps can be defined for the process, tasks assigned to individual roles, and the rules and conditions set up for process execution.

Process Designer really closes the gap between business and IT. It allows business analysts to outline their processes in business terminology, after which it provides the developers with details of the implementation for an integration or other advanced functionalities. The kind of collaboration assures that the final process models will be sound from both a technical and business point of view.

A number of modeling notations are also sustained by IBM BPM Process Designer. It ranges from simple process flow to Business Process Model and Notation, which is an industry standard. This brings clarity and standardization, consequently enhancing readability to process models by ensuring all process stakeholders work on the same page. The Process Designer provides capabilities to create reusable components like sub-processes and business rules, promoting consistency and efficiency across different process models.

The Process Designer provides a facility for simulation and testing. With respect to this, the user can simulate the execution of a process in order to detect bottlenecks and performance under various scenarios. In addition, through the testing of business rules and performance under various scenarios, early detection of problems is enabled and continuous improvement of process models is allowed prior to their deployment.

The other critical dimension in process designer is integration. This provides a collection of tools to integrate the processes with external systems, databases, and services—with a view to guaranteeing data flow and inter-operability among all of them. This is very important in constructing end-to-end business processes that cut across different systems and departments.

Other than modeling, documentation, and annotation features in IBM BPM Process Designer are offered for elements of a process model. The provision of this information will thus contextualize every element in the process model, which is very instrumental in understanding and communicating among the different parties who are stakeholders.

In a nutshell, IBM BPM Process Designer is indispensable for business process creation, enhancement, and optimization. Through its user-friendly interface, powerful simulation, and hassle-free integration options, it has become an anchor of the IBM BPM suite in driving collaboration and efficiency for any process development.

1. • Performance Datawarehouse
   • Process Center Console
   • Process Portal
   • Process Admin Console