TIBCO iProcess Engine Architecture Guide

Below you will find brief information for iProcess Engine. The TIBCO iProcess Engine is a robust platform for automating and managing business processes. It facilitates workflow streamlining, improves efficiency, and ensures compliance. Provides tools for design, execution, and monitoring.

PDF
Document
TIBCO iProcess Engine Architecture Guide + AI Chat | Manualzz

Advertisement

Advertisement

/

Advertisement

Key features

  • Business process automation

  • Workflow management

  • Integration capabilities

  • Scalable architecture

  • Process monitoring

  • Transaction control

Frequently asked questions

TIBCO iProcess Engine case data is stored in a database.

Work items appear in work queues based on the process definition and user access privileges.

Process Sentinels manage the starting, stopping, and running of all the server processes.

User questions

E F

Patricia E.

Which processes run on a slave node in a node cluster, and what happens to work items if the master node is turned off?

Slave nodes run background processes (such as BG, Case Prediction/BGPREDICT, and Deadline Manager) and slave Process Sentinels, while foreground processes (Work Queue Server, Work Item Server, RPC Pool Server, and RPC Listeners) run on the master server. If the master node is turned off, active work queues cannot be accessed by clients, but work items are not lost; they persist in the shared database and remain intact when restarted.

E F

Patricia E.

How do clients locate and connect to an engine node in the architecture?

Clients connect using Remote Procedure Call (RPC) by contacting an RPC Listener (TCP or UDP). The RPC service number is defined in Line 11 of the swdefs file. Once connected, the listener directs the client to a pool server, Work Queue Server (WQS), and Work Item Servers (WIS).

E F

Patricia E.

How is a node cluster configured across multiple servers?

A node cluster consists of engine installations across multiple servers that all point to a single database instance. Server assignments and executables for each machine are configured in the process_config table in the database, which Process Sentinels read to determine process startup.

Preparing document for printing…
0%