Discover our knowledge. Read our blogs!

Learn more

We build all our solutions with WSO2 and we are proud that we are Platinum Value-Added Reseller of WSO2.

Learn more

WSO2 Enterprise Integrator: Business Process Innovation - Part 1

4 min read

WSO2 Enterprise Integrator: Business Process Innovation - Part 1The need for efficient Business Process Management (BPM) to increase productivity and improve competitiveness is an essential business requirement. In that same stretch, the capabilities of IT organizations to meet the accompanied technical revolution can be burdensome. Especially with Line of Business (LOB) software developed with a closed version of RPG, Microsoft Access or some legacy .Net.

In that case, management is forced to make expensive choices to replace or upgrade these platforms, which have proven to be reliable over decades. That should not always be the case for those that chose to implement a middleware. Existing knowledge of WSO2 gained through an Enterprise Service Bus (ESB) or API implementation will boost IT’s ability to drive the innovative change.

This series of blogs will demonstrate how WSO2 ESB development knowledge, combined with a tacit understanding of the (LOB) IT team, can be used to implement a cost-effective process with the WSO2 Enterprise Integrator.

The four-eyes principle

The typical implementation of LOB decisions is role based, with a single form built into the logic of the application. When it comes time to replace that with a dual review process, it becomes clear that rewriting that accumulated logic will be costly.

This dual review or the four-eyes principle, in a nutshell, states that two roles or organizational units must independently review / approve a business case. The Business Process Modelling and Notation (BPMN) diagram in figure 1 visually depicts this principle.

Figure 1: Four-eyes principle

Figure 1: Four eyes principle

The process in the diagram has the following steps with the decisions in between.

  • Initiation
  • First review
  • Second review
  • Implementation
  • End

Figure 2: First review process

Figure 2: First review process

The start of the review process, this sub-process gets executed. Any additional data is collected with a system call. Then a human interaction occurs to review the data. This sub-process ends with a recorded choice of approval or rejection. The primary process evaluates the decision in this first review before moving to the next step.

Figure 3: Second review process

Figure 3: Second review process

As it’s clear by now the diagram for the second review is identical to the first review process. The only differentiable aspect here is the lane name in the image. As with any procedure, there can be exceptions. Figure 4 depicts the exception handling cases.

Figure 4: Exception handling process

Figure 4: Exception handling process

Conclusion

At this stage, BPMN models represent the requirements of the four-eyes business. In subsequent parts of this series, I will show how to develop the models in the diagrams using WSO2 EI tooling. I will also demonstrate how to extract & transform data within LOB systems using the WSO2 EI data service profile, and deploy & run the process into the WSO2 EI business process profile.

New Call-to-action

Care to share?
   
Picture of Philip Akyempon
Published August 6, 2020

Philip Akyempon

Philip is a Senior Integration Consultant. He has more than eight years experience in software development and systems integration. At Yenlo, he implements service-oriented architecture (SOA) solutions using WSO2 technology. Philip is specialized in WSO2 API, WSO2 ESB, WSO2 BPS and WSO2 DSS. Besides these technical skills, he is passionate regarding the benefit of IT professionalism within organizations and is certified in ArchiMate 2.1 and TOGAF 9.

Responses

Stay up to date with the latest articles