Explore topic-wise InterviewSolutions in .

SW_IP_xxx SYSTEM FIELD VALUES

SW_IP_xxx system field values

No LIMIT

No Limit

CHECK the SWDIRlogssw_warn or sw_error LOG FILES to SEE if any ERROR messages were logged.

Check the SWDIRlogssw_warn or sw_error log files to see if any error messages were logged.

• Case data changes will be imported, but the case will NOT be MOVED ALONG the process.
• Case data changes will be imported, and the AUDIT trail will be updated to record the Event trigger.

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

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

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 following command.

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.

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 following command.

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.

The options for configuring STORAGE for process engine’s CHECKPOINT repository are:

Local File: Information is stored in a local file which in case of engine crash/failure and same information is used to resume the process flow once engine is up. This mechanism WORKS only in case of single server or load BALANCING APPROACH.

Database: Information is stored in a database table which is used to resume engine later. Fault tolerant engines can recover from a checkpoint only when database is used.

The options for configuring storage for process engine’s checkpoint repository are:

Local File: Information is stored in a local file which in case of engine crash/failure and same information is used to resume the process flow once engine is up. This mechanism works only in case of single server or load balancing approach.

Database: Information is stored in a database table which is used to resume engine later. Fault tolerant engines can recover from a checkpoint only when database is used.

There are following four types of panels available in TIBCO designer window:

1. PROJECT Panel: This panel shows project hierarchy.
2. DESIGN Panel: This panel is USED to design new BW Processes in TIBCO.
3. Palette Panel: This Panel has all the available Palettes with bundled activities which can be dragged and used in design panel during process DEVELOPMENT.
4. Configuration Panel: Configurations INCLUDING input, output details for any activity are specified in the configuration panel.

There are following four types of panels available in TIBCO designer window:

TIBCO provides Inspector ACTIVITY which can be used for debugging PURPOSES while developing applications in TIBCO designer. Inspector activity can be used to write all OUTPUT information of designer activities to a LOCAL file including PROCESS variables and other details.

TIBCO provides Inspector activity which can be used for debugging purposes while developing applications in TIBCO designer. Inspector activity can be used to write all output information of designer activities to a local file including process variables and other details.

Vcrepo.dat file is used to store certain properties like TIBCO RV encoding, display name; description ETC. vcrepo.dat file gets created automatically when a TIBCO BW PROJECT is saved for the FIRST time. This file can be used for identification purposes.

Vcrepo.dat file is used to store certain properties like TIBCO RV encoding, display name; description etc. vcrepo.dat file gets created automatically when a TIBCO BW project is saved for the first time. This file can be used for identification purposes.

• TIBCO Runtime AGENT (TRA) is responsible for starting and STOPPING of processes RUNNING on a machine.
• TRA provides runtime environment for TIBCO applications.

TRA runs on EVERY TIBCO machine in the background.

TRA runs on every TIBCO machine in the background.