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


Chapter 1 Introduction : Overview

Overview
The TIBCO iProcess Objects Server receives requests for services or data from a client application developed with either TIBCO iProcess Objects (COM, Java, or C++) or TIBCO iProcess Server Objects (Java or .NET). It processes the request, then makes the appropriate call to a TIBCO iProcess Engine to initiate the desired service or obtain the desired information.
Therefore, the TIBCO iProcess Objects Server acts as a gateway between the client application and the TIBCO iProcess Engine, as follows.
The client application must establish a connection with a TIBCO iProcess Objects Server. This can be accomplished in a variety of ways — see TIBCO iProcess Objects Programmer’s Guide or TIBCO iProcess Server Objects Programmer’s Guide for information.
After communication is established between the client and TIBCO iProcess Objects Server, TIBCO iProcess Objects Server waits for request messages from the client. When TIBCO iProcess Objects Server receives a request message, it in turn makes calls to the TIBCO iProcess Engine to perform functions such as locking work items, moving work items to other work queues, writing data to the database, etc.
Message Timeout
As described above, client applications make requests to TIBCO iProcess Objects Server, then wait for a response. Because of this, you may have a desire to configure the client so that if a specified period of time elapses waiting for a response from the server, the client will timeout and generate an error. To configure this “message wait time,” you must add a Registry key (Windows systems) or environment variable (UNIX systems), and set it to the number of milliseconds you would like the client to wait before timing out.
Registry key for TIBCO iProcess Objects:

 
HKEY_LOCAL_MACHINE\SOFTWARE\Staffware plc\Staffware SEO Client\MessageWaitTime

 
Registry key for TIBCO iProcess Server Objects:

 
HKEY_LOCAL_MACHINE\SOFTWARE\Staffware plc\Staffware SSO Client\MessageWaitTime

 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Staffware plc\...
Environment variable:
MessageWaitTime
If the number of milliseconds specified by MessageWaitTime is exceeded, the client will generate an swTimeoutErr error. If MessageWaitTime is set to 0 (zero), the client will not timeout. By default (i.e., if you do not set MessageWaitTime), Windows clients timeout in 30 seconds; UNIX clients timeout in 60 seconds.
TIBCO iProcess Objects Server Version
Prior to version 10.2.0, TIBCO iProcess Objects Servers were called "Tibco iProcess Objects (SPO) Servers". They had version numbers either with or without an "i". Servers with an "i" (e.g., i10.0(4.0)) were used with TIBCO iProcess Engines; Servers without an "i" (e.g., 9.3(5.0)) were used with TIBCO Process Engines.
From version 10.2.0 forward, these servers are called TIBCO iProcess Objects Servers and their version number will always be 3 digits, with no "i"; these servers will be used with TIBCO iProcess Engines.
You can determine the version of your TIBCO iProcess Objects Server by executing one of the following:
SWDIR\bin\swentobjsv -v (Windows) or $SWDIR/bin/swentobjsv -v (UNIX)
what $SWDIR/bin/swentobjsv (UNIX only) - The output of this command contains the same as the swentobjsv -v command. However, using this command does not require having the SWDIR or any other environment variables configured. The what command will also run even if there is a compatibility problem between the iProcess Objects Server and engine libraries in $SWDIR/libs, and will run even if the engine libraries are missing.
Note that internally the TIBCO iProcess Objects Server version number is still in the older format. Therefore, the commands above will show version 10.2.1 as version i10.2(1.0).

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