Tibco Iprocess

This Discussion is given by my one of the Dearest Friend Kiran Nakka,Who is working with me ,as he is working on Iprocess so he shared some of his points for you.....

so For Iprocess related queries Kiran will communicate....



This posting is made in the attempt to help you (the fellow HCLites, who are new to iProcess) in opening your closed mouth when you come across with iProcess in your formal discussions. Below is the quick learning stuff regarding iProcess Engine which make you familiar with iProcess Engine architecture and its internal components. What are you waiting for... make your eyes free for a while to scan the below contents.

What is iProcess?

As you all aware that iProcess is a BPM tool offered by TIBCO in acquisition with Staffware, which facilitates the management of Business Processes and promising the ability to handle both human centric and integration-centric processes in a single platform.

iProcess Engine Architecture:

TIBCO iProcess Engine runs on Windows or a variety of UNIX platforms, and supports Oracle, SQL Server, or DB2 databases. To understand the flow of data and relationship between processes, the iProcess Engine can be split into four major areas as shown below:

1. Process Sentinels

2. Foreground Processes

3. Background Processes

4. Message Box Sets

1. Process Sentinels: These are like escorts to the famous politician that will guard and control of all the TIBCO iProcess Engine Processes. Some of the major responsibilities include

a. Start processes during a Server start up or upon a system administrator request. It will control the order in which the processes are started.

b. Detect failed processes and restart them automatically. Shut down the processes when the system is shutdown or upon a system administrator request to stop the system

c. Monitor other Process Sentinels and restart them if they fail. Maintain the list of all active user logins.

d. Processes that are controlled by the Process Sentinels are listed below:

1. Background (BG)

2. Database Queue Daemon(DBQD)

3. Deadline Manager(DLMGR)

4. Introspection Activity Publication JMS (IAPJMS)

5. Prediction (BGPREDICT)

6. RPC Background (RPCBG) – RPC_TCP_LI and RPC_UDP_LI

7. RPC Pool Server(RPC_POOL)

8. iProcess Objects Server

9. WIS MBOX Daemon (WISMBD)

10. Work Item Server (WIS)

11. Work Queue Server (WQS)

2. Foreground Processes: These are like PA to the same famous politician that represent the Work Queues and are responsible to communicate with a desktop (iProcess Workspace) or browser based iProcess Client Program and for passing any requests such as released work items to the background area for processing. The processes that operate in the foreground are listed below:

a. Work Queue Server (WQS) – Handles the listing of iProcess Work Queues

b. Work Item Server (WIS) – Handles the listing of work items in the work queues. By default we have two WIS processes.

c. WIS Mbox Daemon (WISMBD) – WISMBD operates between WIS MBox Set and WIS RPC processes forwarding messages from one to the other.

d. RPC Listeners: These are started by the Process Sentinels and are the first iProcess Engine foreground processes to be started. A listener is started for both TCP and UDP protocols (RPC_ _TCP_LI and RPC_UDP_LI). The RPC number for the listener process is the same for both TCP and UDP.

e. RPC Pool Server: It is responsible for handling RPC requests from a TIBCO iProcess Workspace to access and update data in the iProcess Engine instance.

3. Background Processes: These are like the actual activities done by the innocent staff on behalf of the same famous politician that will automates the process orchestration and integration activities(EAI Steps), updating the database with new instance data, and checking for deadlines. The processes that operate in the background are listed below:

a. Background (BG) – This is the core background process that interprets the business rules that have been defined in the iProcess Modeler. This process is also responsible for dequeuing of messages from the MBox Sets

b. Case prediction (BGPREDICT) – This process is responsible for updating prediction data. (Stored in the database)

c. Database Queue Daemon (DBQD) – Caches a configurable number of messages from the database for each available queue. This process is only currently used on the DB2 version of the TIBCO iProcess Engine

d. Deadline Manager(DLMGR) – This process is responsible for monitoring deadlines in cases of procedures

e. Introspection Activity Publication JMS (IAPJMS) – This process is responsible for receiving messages containing activity monitoring information from the background processes and routing these to the specific JMS topic

f. RPC Background(RPCBG) – This process handles the Jump To and Case Suspend features in the iProcess Suite

4. Message Box Sets (MBOX Sets): The foreground and background processes communicate with each other using messages which contain information about iProcess Case (Release / Keep / Forward it) data. A message is processed by the case instruction processors. MBOX Sets is a generic named used for a container in which these messages are stored.

Hope, I have provided enough information regarding iProcess Engine Architecture. You can dig more by reading the PDFs available at our fileserver. What more... Open your mouth and talk about iProcess and not to forget the Tag “The more we discuss the more we gain”.

Thanks,

Kiran Nakka

♫

kiran.kik09@gmail.com