Client applications make use of the objects in the TIBCO
iProcess Server Objects by making method calls that either
retrieve or modify data. These method calls cause messages
to be sent to a TIBCO iProcess Objects Server. The TIBCO
iProcess Objects Server acts as a gateway between the
client applications created with TIBCO iProcess Server
Objects, and the TIBCO iProcess Engine, where the actual
processing and storage of data occurs. The TIBCO iProcess
Engine manages all data, routing work items and updating
the appropriate work queues.
Server Objects communicate with the TIBCO iProcess Objects
Server via TCP/IP .Objects Server communicate with the
TIBCO iProcess Engine via UDP
Check the SWDIRlogssw_warn or sw_error log files to see
if any error messages were logged.
► Short lock. This is the standard lock normally set
by the TIBCO iProcess Workspace. A short lock is removed
when a user keeps or releases a work item. In the event
that short locks are left behind because, for example, the
iProcess Workspace crashed, the only way to remove the
short lock is to re-start the iProcess Engine or use the
► Long lock. A lock that is persistent and can only
be removed using sal_llock_frm_init() by the user holding
the lock. Long locks are not normally used by TIBCO
iProcess Workspace, but may be set by SAL SDK programs or
the TIBCO iProcess Objects Client. Re-starting the iProcess
Engine has no effect on long locks, so a work item locked
in this way remains inaccessible to every iProcess user
until it is manually unlocked.
BPM is an automation of processes that exists in an
organisation.There are challeges that can be more
efficiently handled through different technologies using
BPM. Ex: webMethods technology(using Designer).
Through BPM an organisation can
> Monitor its working efficiency in rendering services to
> Identify the areas that needs to be modified/improvise.
> easily address the problem areas.