BPM 7.5 includes a feature known as the Process Inspector. This feature, in Process Designer, allows developers to run and debug processes in the Process Center authoring environment, as well as, remote Process Server environments that are connected to the Process Center. Process Inspector provides a centralized location for viewing and debugging running process instances in any environment connected to your Process Center. Table 1 below outlines some of the main tasks that the Inspector allows a developer to perform.
In order to use the Inspector functionality to its full potential, it is important to ensure that each of your BPM cells has unique names. According to the IBM BPM 7.5 InfoCenter,
“Use a unique name for the deployment manager cell. A cell name must be unique in any circumstance in which the product is running on the same physical workstation or cluster of workstations, such as a Sysplex. Additionally, a cell name must be unique in any circumstance in which network connectivity between entities is required either between the cells or from a client that must communicate with each of the cells. Cell names also must be unique if their name spaces are going to be federated. Otherwise, you might encounter symptoms such as a javax.naming.Name NotFoundException exception, in which case, you need to create uniquely named cells.” (IBM, 2011)Process Inspector does make use of connectivity between the cells and also from a client that must communicate with each of the cells. When connecting to Process Center through the Inspector, there is cross-cell communication that occurs when Inspector goes to look for the running instances you have in one of your remote Process Server environments. As an example, if a developer has deployed code onto the Process Center server (also known as the playback server) and is now ready to test the code on a remote Process Server environment, Process Inspector will allow the developer to kick off a process instance and debug the code step by step through the process, provided the snapshot has already been deployed to the remote Process Server. The drop down box in Figure 1 shows the various Process Server environments that are connected to the Process Center.
Normally, after selecting an environment to test your process instance on, Inspector would connect to the remote Process Server and allow you to execute your tests. However, if your BPM cells for all of your environments are named with the exact same name, you may see a screen resembling Figure 2, even though you have already successfully deployed the snapshot.
When the BPM cell names are all the same, cross-cell communication experiences issues that will cause you to lose key functionality of the products, as described above. Figure 3 provides a high level view (as an example) of the connectivity between Process Designer (which contains Process Inspector), Process Center, and Process Server environments:
In conclusion, it is imperative that you review the pre-requisites for installing IBM BPM 7.5 Advanced, or any products for that matter, thoroughly to ensure a successful implementation. The old saying “measure twice and cut once” is always a good rule of thumb to avoid rework and further expense down the road.
IBM. (2011). Naming considerations for profiles, nodes, servers, hosts, and cells. Retrieved February 16, 2012, from IBM Business Process Manager 7.5 InfoCenter: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/index.jsp?topic=%2Fcom.ibm.wbpm.main.doc%2Ftopics%2Fcins_naming.html
IBM. (2011). Running and debugging processes with the Inspector. Retrieved February 16, 2012, from IBM Business Process Manager 7.5 InfoCenter: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/index.jsp?topic=%2Fcom.ibm.wbpm.wle.editor.doc%2Ftopics%2Frunning_debugging_procs.html
Markowitz, E. (2011, 11). Product Development Director at Prolifics.
Seth Gagnon, a Senior Consultant for Prolifics, has over seven years experience in the healthcare industry and has worked with business process management technology to automate member enrollment and claim adjudication for a Fortune 200 healthcare client. He has experience in IBM middleware products such as WebSphere Application Server, WebSphere Process Server, WebSphere Business Process Manager, and other products in the IBM BPM stack. Seth received his BS in Management Information Systems from the University of CT and his MS in Technology Commercialization from Northeastern University.