TIBCO BW: Implementing Parallel Processing Solutions

While developing processes in TIBCO BW with a liner single control flow, often we face bottleneck situations and our a certain activity taking longer time may result in a delay for subsequent activities as well. For example, If we opt for a liner sequential processing logic in our TIBCO BW Code, If a JDBC activity gets halted or delays due to any database or network issues, activities next to this will also suffer. To avoid this problem, one can go for parallel processing technique in TIBCO BW implementation.

How to Implement Parallel Processing in TIBCO:

Sub processes which are called from a parent process normally run in the same job (same thread) and hence, they exhibit a sequential flow. For parallel processing, It is required to spawn new jobs for the sub processes. This is achieved by checking Spawn checkbox while calling a sub-process form the parent process.

Scenario: Parent and Sub Process running in Same Job (No Spawning)

In this scenario, I am going to create a parent process and a sub process and will call the sub-process from the parent process without checking Spawn option.

The two processes are very simple in this case and they are created just to simulate the sequential and parallel processing and have no other implementation inside.

Below is the parent process which is calling a sub-process without Spawn:

parent process with no spawn

Child process is simple with just Start and End activities (with a transition from Start to End activity).

 

Now when I load the two processes in the designer tester and run a Job for parent process, both processes get executed in the same thread (job) in a sequential manner:

tibco sequential process running

 

Scenario: Parent and Sub Process running with separate Jobs (With Spawning)

Now let us achieve parallel processing by using Spawn option. In the parent process while calling sub-process, check the Spawn checkbox as shown below:

parent process with spawn

Now if the load the two processes in designer tester and start our parent process Job, we can see that a new Job is created for child process as well and both processes are running in parallel in separate threads:

tester parallel processes in tibco

 

Ajmal Abbasi

Ajmal Hussain Abbasi is Integration Consultant By Profession with 13+ years experience in Integration domain mainly with TIBCO products. He has extensive practical knowledge of TIBCO Business Works, TIBCO Cloud, TIBCO Flogo, TIBCO Mashery, TIBCO Spotfire, EMS and TIBCO ActiveSpaces. He has worked on a number of highly critical integration projects in various sectors by using his skills in TIBCO Flogo, TIBCO API Management (Mashery), TCI, Tibco Designer, TIBCO Business Studio, Adapters, TIBCO EMS, RV, Administrator, TIBCO BE, TIBCO ActiveSpaces etc. Ajmal Abbasi has experience with MuleSoft ESB as well. Ajmal Abbasi is also experienced in the area of API Management particularly with WSO2 API management platforms. Ajmal Abbasi is also experienced in developing solutions using Core Java and J2EE Technologies. You can contact Ajmal Abbasi for Consultancy, Technical Assistance and Technical Discussions.

More Posts - Website - Facebook - LinkedIn - YouTube

7 thoughts on “TIBCO BW: Implementing Parallel Processing Solutions

  1. vasudeva reddy

    i need to know the how to implement the filter condition for price range in transition condition

    Reply
  2. Ram

    I have been following this blog since few months .Its a Good Place for understanding concepts in TIBCO .
    Great Work Ajmal …. You explain things in very Simple Manner in such a way that a Beginner also can catch hold of the Concepts Easily ……Thank you …

    Reply
  3. Subodh

    Hi,

    Your WebSite is excellent for learning tibco.

    Can you write a blog on Which process starters can participate in LoadBalancing and which activities participate in FT Mode.

    Regards,
    Subodh

    Reply
  4. Pingback: TIBCO Asyncronized Process | Joys Of My Life

  5. Wesley Nurse

    What version of Tibco you are using here?. I was under the impression that versions of tibco below 6.0 did not have multithreading.. hence, spawning does not run job in different threads but rather, in different processes (which is not the same thing). Was i wrong about tibco 5.x not being multithreaded?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *