Explore topic-wise InterviewSolutions in .

When you HANDLE an ERROR INSIDE a called sub-process or group and want to re-throw the error to the caller (happens by DEFAULT if you don’t handle the error in the called process)

When you handle an error inside a called sub-process or group and want to re-throw the error to the caller (happens by default if you don’t handle the error in the called process)

We can USE REPEAT on ERROR until TRUE.

We can use Repeat on Error until true.

The THREE SCENARIOS are:

1. Shared VARIABLES across BW engines.
2. Locking across GROUPS in multiple BW engines.
3. Wait Notify across BW engines.

The three scenarios are:

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

• Peer means all of them have the same WEIGHT. In this CASE when one engine fails another one takes over and continues processing till it fails.
• In master secondary configuration WEIGHTS are unequal, the secondary starts processing when master fails. But when master recovers, secondary STOPS and master continues processing.

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

The options for configuring storage for PROCESS engine’s CHECKPOINT repository are:

• Local FILE
• DATABASE. 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:

An EAR file can CONTAIN local project resources, LIBRARY BUILDER resources, and files as specified in Alias Library resources. In ADDITION, the TIBCO Designer class path may INCLUDE references to other files that are included in the EAR file.

An EAR file can contain local project resources, Library Builder resources, and files as specified in Alias Library resources. In addition, the TIBCO Designer class path may include references to other files that are included in the EAR file.

1. GUI MODE
2. CONSOLE mode
3. SILENT mode

You can change the value of a global variable when you deploy your project in TIBCO Administrator.

See the section on modifying runtime variables in TIBCO BusinessWorks Administration for more information on using TIBCO Administrator.

You can also specify values for global variables when starting a process engine on the command line. To do this, specify the following as a command line argument when starting the process engine:

-tibco.clientVar.<variablePathAndName&GT; <value>

where variablePathAndName is the name of the variable you wish to set, INCLUDING the path to the variable if it is contained in a folder. Value is the value you wish to set the variable to.

For EXAMPLE: if you have a global variable named item1 contained in a folder named myGroup and you wish to set its value to 500, add the following argument to the command line when starting the process engine:

-tibco.clientVar.myGroup/item1 500

You can change the value of a global variable when you deploy your project in TIBCO Administrator.

See the section on modifying runtime variables in TIBCO BusinessWorks Administration for more information on using TIBCO Administrator.

You can also specify values for global variables when starting a process engine on the command line. To do this, specify the following as a command line argument when starting the process engine:

-tibco.clientVar.<variablePathAndName> <value>

where variablePathAndName is the name of the variable you wish to set, including the path to the variable if it is contained in a folder. Value is the value you wish to set the variable to.

For example: if you have a global variable named item1 contained in a folder named myGroup and you wish to set its value to 500, add the following argument to the command line when starting the process engine:

-tibco.clientVar.myGroup/item1 500

SQL DIRECT is USED to execute command dynamically using output of other activities. This ACTIVITY allows you to execute commands which other activities in the JDBC don’t ALLOW, like DDL command create table.

SQL direct is used to execute command dynamically using output of other activities. This activity allows you to execute commands which other activities in the JDBC don’t allow, like DDL command create table.

All the PROCESSES which have this KEY in their sequencing key FIELD will be EXECUTED in the order they were created.

All the processes which have this key in their sequencing key field will be executed in the order they were created.

It is used to call process INSTANCES in the ORDER they are CREATED.

It is used to call process instances in the order they are created.

JMS QUEUE receiver with confirm activity. Sequencing KEY in a MISC tab of the configuration could ALSO be USED.

JMS Queue receiver with confirm activity. Sequencing key in a misc tab of the configuration could also be used.

USE JOB shared VARIABLE in a CRITICAL SECTION.

Use job shared variable in a critical section.

SOAP event source is used for single OPERATION, single end. SERVICE palette is used for MULTIPLE operations, multiple end bindings like http, jms.

Soap event source is used for single operation, single end. Service palette is used for multiple operations, multiple end bindings like http, jms.

We WRITE to OUTPUT to the QUEUE from which we RECEIVED the REQUEST.

We write to output to the queue from which we received the request.

Prefetch is fetching the MESSAGES from the server before RECEIVER calls. FAILSAFE property enables to write PERSISTENCE messages to the file with synchronous i/o calls.

Prefetch is fetching the messages from the server before receiver calls. Failsafe property enables to write persistence messages to the file with synchronous i/o calls.

There are 6 modes of ACKNOWLEDGEMENT. They are:

1. Auto: message is acknowledged AUTOMATICALLY
2. Client: use confirm activity for acknowledgement
3. TIBCO EMS Explicit: use confirm activity for acknowledgement, only available for TIBCO EMS
4. TIBCO EMS no ack
5. Dups ok: message is acknowledged automatically on its receipt
6. TRANSACTIONAL: when a TRANSACTION is included in a PROCESS definition. The message is ack when the transaction commits.

There are 6 modes of acknowledgement. They are:

There are three types of variables available in TIBCO. They are:

Global variables: Global variables are USED for assigning constants a value which is used over a project.

Process variables: Process variables are again of four types.

They are:

• Activity output
• Predefined process variables
• Error variables
• USER defined process variables.
• Predefined process variables INCLUDE $_GlobalVarialbes and $_ProcessContext
• shared variables – User defined process variables could be defined at a process definition level and ASSIGNED a value by using an assign activity.

There are three types of variables available in TIBCO. They are:

Global variables: Global variables are used for assigning constants a value which is used over a project.

Process variables: Process variables are again of four types.

They are:

File palette, GENERALL activities palette, JDBC palette, HTTP palette, jms palette, PARSE palette, service palette, soap palette, wsdl palette.

File palette, generall activities palette, jdbc palette, http palette, jms palette, parse palette, service palette, soap palette, wsdl palette.

FETCHES 4 MESSAGES

Fetches 4 messages

MESSAGE STAYS on the QUEUE.

Message stays on the queue.

ITERATE, repeat until TRUE, repeat on ERROR until true, critical section, transaction, pick first, while true.

Iterate, repeat until true, repeat on error until true, critical section, transaction, pick first, while true.

The CONTENTS of the FILE will PERSIST.

The contents of the file will persist.

Critical section is used to sync process instances so that only once process instance executes the grouped activities at any given time. Any concurrently running process instances that contain a corresponding critical section group wait until the process instance that is CURRENTLY executing the critical section group completes. Particularly used for controlling access to shared variables. Critical section is one of the group actions. Others are iterating, repeat until true, repeat on error until true, while true, pick FIRST and transaction. If we select critical section as the group, then we get two options. Single group and multiple groups.

Single Group

If you wish to synchronize process instances for a single process definition in a single process engine (only one ear(instance) is deployed), perform the following:

1. Create a group around the activities you wish to synchronize.
2. Specify Critical Section for the Group Action field.
3. Specify Single Group for the Scope field.
4. Only one process instance at any given time will execute the activities contained in the Critical Section group.

Multiple Groups:

If you wish to synchronize process instances for multiple process definitions, or if you wish to synchronize process instances across multiple process engines, perform the following:

• Create a Lock shared configuration resource and specify a name for the resource.
• To perform the synchronization across multiple process engines, CHECK the Multi-Engine field of the Lock resource. When the process instances are EXECUTED by the same process engine, locking is performed in memory. When the process instances are executed across multiple engines, the process engines must be configured to use a database for STORAGE, and a database transaction is performed to ensure that only one process instance is executing the critical section group at any given time.
• Create a group around the activities you wish to synchronize.
• Specify Critical Section for the Group Action Field.
• Specify Multiple Groups for the Scope field.
• Use the Browse button in the Lock Object field to locate the Lock shared configuration resource you created in Step 1.
• Perform steps 3 to 6 for any process definitions you wish to synchronize. Make sure you specify the same Lock shared configuration object for all Critical Section groups.

Critical section is used to sync process instances so that only once process instance executes the grouped activities at any given time. Any concurrently running process instances that contain a corresponding critical section group wait until the process instance that is currently executing the critical section group completes. Particularly used for controlling access to shared variables. Critical section is one of the group actions. Others are iterating, repeat until true, repeat on error until true, while true, pick first and transaction. If we select critical section as the group, then we get two options. Single group and multiple groups.

Single Group

If you wish to synchronize process instances for a single process definition in a single process engine (only one ear(instance) is deployed), perform the following:

Multiple Groups:

If you wish to synchronize process instances for multiple process definitions, or if you wish to synchronize process instances across multiple process engines, perform the following: