What is the critical section in TIBCO Business works and what is it used for?
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:
- Create a group around the activities you wish to synchronize.
- Specify Critical Section for the Group Action field.
- Specify Single Group for the Scope field.
- 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.
If there are three activities in the critical section, jdbc update then a write file and then again jdbc update. If the second jdbc update fails, then what will happen to the file written by write file activity?
The contents of the file will persist.
What are different types of transaction groups supported in TIBCO BW?
Iterate, repeat until true, repeat on error until true, critical section, transaction, pick first, while true.
Can two queue receivers listen to the same queue? If yes, if the message arrives on the queue, when receiver receives it?
The queue which has made connection first. First come first serve.
If the message has hit the queue, and there are no receivers for it, and the receiver comes alive after 6 hours, what happens to the message?
Message stays on the queue.
If there are five messages and prefetch property is set to 4 then what happens?
Fetches 4 messages
What all palettes you have worked in TIBCO BW?
File palette, generall activities palette, jdbc palette, http palette, jms palette, parse palette, service palette, soap palette, wsdl palette.
What are the different types of variables available in TIBCO?
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.
What are the different acknowledgment modes for a message?
There are 6 modes of acknowledgement. They are –
- Auto – message is acknowledged automatically
- Client – use confirm activity for acknowledgement
- TIBCO EMS Explicit – use confirm activity for acknowledgement, only available for TIBCO EMS
- TIBCO EMS no ack
- Dups ok – message is acknowledged automatically on its receipt
- Transactional – when a transaction is included in a process definition. The message is ack when the transaction commits.
What is prefetch and failsafe?
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.
How do you send a response from a web service?
We write to output to the queue from which we received the request.
What is the difference between soap event source and service palette?
Soap event source is used for single operation, single end. Service palette is used for multiple operations, multiple end bindings like http, jms.
If you want to count the number of times a job is called, how will you go about doing it?
Use job shared variable in a critical section.
If there are hundred messages lying on the queue, what will you do and which activity will you use to retrieve one message at a time?
JMS Queue receiver with confirm activity. Sequencing key in a misc tab of the configuration could also be used.
What is the sequencing key in the misc tab used for?
It is used to call process instances in the order they are created.
What happens if I put a static value say ‘nitin’ in the sequencing key?
All the processes which have this key in their sequencing key field will be executed in the order they were created.
What is SQL direct? What is it used for?
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.
Can you change a value of a global variable at runtime?
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
What are the modes ofTIBCO BW Installations?
- GUI mode
- Console mode
- Silent mode
If you have installed a particular version of TIBCO software e.g. TIBCO BW X.Y.Z, What are X, Y and Z number stands for?
Integration can be at different application layers:
- X:Patch
- Y:Major
- Z:Minor
What is the role of TRA?
TRA stands for TIBCO Runtime Agent.
The TRA has two main functions:
- Supplies an agent that is running in the background on each machine.
- The agent is responsible for starting and stopping processes that run on a machine according to the deployment information.
- The agent monitors the machine. That information is then visible via TIBCO Administrator.
- Supplies the run-time environment, that is, all shared libraries including third-party libraries.
What are the resources that get included in the EAR file, created by the TIBCO Designer?
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.
What are the different modes of service invocation?
Services can be invoked in several ways.
A one-way operation is executed once and does not wait for a response.
A request-response operation is executed once and waits for one response. In a request-response service, communication flows in both directions. The complete interaction consists of two point-to-point messages—a request and a response. The interaction is only considered complete after the response has arrived.
– Publication (notification) means an operation sends information on an as-needed basis, potentially multiple times.
– Subscription means incoming information is processed on an as-needed basis, potentially multiple times.
What are the TIBCO BW activities that can participate in transactions?
Not all TIBCO BusinessWorks activities can participate in a transaction. Only the following types of activities have transactional capabilities:
– JDBC activities
– JMS activities
– ActiveEnterprise Adapter activities that use JMS transports
– EJB activities
– TIBCO iProcess BusinessWorks Connector activities
What are the different types of Transactions TIBCO provides?
TIBCO BusinessWorks offers a variety of types of transactions that can be used in different situations. You can use the type of transaction that suits the needs of your integration project. When you create a transaction group, you must specify the type of transaction. TIBCO BusinessWorks supports the following types of transactions:
- JDBC
- Java Transaction API (JTA) UserTransaction
XA Transaction
