Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Introduction to the TIBCO iProcess Engine : iProcess Physical Architecture

iProcess Physical Architecture
The following section describes:
Installing the iProcess Engine on a Single Server
A TIBCO iProcess Engine installation on one server is known as a TIBCO iProcess Engine node. All the iProcess Engine processes are run on a single server.
The following diagram shows a TIBCO iProcess Engine (node) that comprises of one server.

 
.

 
Installing the iProcess Engine on a Node Cluster
Installing the TIBCO iProcess Engine on multiple servers that all use the same database instance is known as a node cluster architecture. You can convert from a single-server to a node cluster at any time simply by adding another server to the installation. In the node cluster architecture, you can have a number of TIBCO iProcess Engine processes running on different servers, but they act as though they are a single iProcess Engine. Node clusters improve load balancing and performance. However, all the TIBCO iProcess Engine case data such as fields and their values in forms will be stored in one TIBCO iProcess Engine database instance.
The following diagram illustrates a TIBCO iProcess Engine (node cluster) that uses two servers to run TIBCO iProcess Engine processes. They can all access iProcess case data from the same TIBCO iProcess Engine database instance.

 

 
Note that:
TIBCO iProcess Workspace and TIBCO iProcess Engine Communication
The TIBCO iProcess Engine uses a client/server model for communication where there is a two way communication path between each TIBCO iProcess Workspace client and TIBCO iProcess Engine server. The communication protocol used for this communication is called Remote Procedure Call (RPC).
Information keyed in at the client needs to be passed to the TIBCO iProcess Engine for processing, for example when completing an insurance claim form, the new or updated data needs to be processed, stored, or updated so that subsequent steps can use the information. Information also needs to be passed from the TIBCO iProcess Engine to one of the TIBCO iProcess Workspaces, for example to tell the client what the next step in the business process is or show previous details about a work item that has already been entered.
Refer to Network Communication for more information about TIBCO iProcess Workspace and TIBCO iProcess Engine communication.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved