The document provides an overview of the architecture of the iProcess server, detailing its components organized into nodes and clusters for load balancing or fault tolerance. It describes the roles of different processes, including process sentinels, foreground and background processes, and the mbox set for communication. Additionally, it explains client interface options and offers techniques for resolving locked procedures and listing cases within a Tibco iProcess procedure.

1. www.adlearnings.com

2. www.adlearnings.com
If you are looking formore detail in iProcess Server’s architecture we can see that its engines are
organized into nodes, where a node is formed by 1 or N iProcess Engine servers sharing a database
instance. If there is more than one engine for load balancing or fault tolerance, it’s called a node
cluster. Engines use Remote Procedure Calls (RPC) to communicate with the clients and can be
split into four parts:
• Process Sentinels
• Foreground Processes
• Background Processes
• MBox Set

3. www.adlearnings.com
Process Sentinels: which are responsible for making sure that the rest of the processes are
running.
Foreground Processes: processes dealing with user interaction.
Background Processes: processes performing the “internal” tasks.
MBox Set: communication link between background and foreground processes
The Server comes with a client interface called Objects Server which provides an API to interact
with the engine. It is available in two “flavors”:
Process Objects (TPO): a thick client implementation API for COM/C++/Java.
Server Objects (TSO): a thin client implementation API for EJB and .NET.
Business Processes executed by the iProcess Server can interact with external systems as well
using EAI plugins. There are plug-ins for different systems, including BusinessWorks, Oracle, Java,
SQL Server and scripts.

4. www.adlearnings.com
Unlock a locked iProcess Procedure:
When you don’t properly close your iProcess procedure you have a chance of locking the object
for further use.For some strange cosmic reason, this happens to me a lot. To fix this quickly in a
DEV environment connect to the iProcess database and search for the following tables, find the
record and delete it.
List cases in a Procedure in TIBCO iProcess:
Commands to do: 1) To List cases in a process
In the command prompt on the server run
2) To List all outstanding cases per process plist –o PROC >outfilePROC.txt
3) To Check outstanding steps plist -D PROC >outfilePROC.txt
4) Check WIS and system setup plist -w PROC >outfilePROC.txt
5) Check contents of a queue plist -mWv PROC >outfilePROC.txt

5. www.adlearnings.com
Visit : www.adlearnings.com
Mobile No: +91 7331128598
Like : facebook.com/adlearnings
Goole+: plus.google.com/+Adlearningstibcoonlinetraining

6. www.adlearnings.com
Thank You
For
Watching