· Mar 30

Business Process vs Business Process Component

I had an interesting scenario come up, as when we moved from eGate to Ensemble and we will be moving to IRIS here in the near future I was taught to create Business Processes for writing to and extracting data from outside MS SQL Databases.

That works ok for simple messages but I have a case where I have a rather large MFN message coming in from a vendor. The normal Business Process of reading in the HL7, and parsing the message into Stored Procedure structure calls has worked in the past with smaller messaging like ADT, etc. This message is so large and so much looping is needed especially in some segments that can have over 500 repeating segments has slowed down the Business Process quite a bit. I started sending 37,000 + plus messages last night and the system is still not catching up. 

  • So my question is this for rather large messaging is it ideal to maybe split up the Business Process into multiple Business Process components?
  • What is the true advantage or reason to use Business Process components?

Please and thanks

Product version: Caché 2018.1
$ZV: Cache for UNIX (IBM AIX for System Power System-64) 2018.1.3 (Build 414U) Mon Oct 28 2019 11:24:02 EDT
Discussion (2)2
Log in or sign up to continue

A Business Process Component is the BPL analogue of a subroutine or function and is called exclusively from a BPL. The idea is that they can be reusable components applicable to potentially multiple, different business processes. I don't think that's really what you're looking for.

If you don't have a FIFO concern with this database processing and are thinking that increasing the number of parallel processes performing these database activities might improve performance, you could try increasing the pool size for the BP.