TIBCO Top 10 Interview Questions and Answers given below have been compiled based on the level of significance of the modules/area they cover. In actual, TIBCO BW is an ocean and once can’t sail through it with just 10 moves. However, below TIBCO Top 10 Interview Questions and Answers will greatly help you to get yourself prepared for a TIBCO interview when interview is just above your head and you don’t have much time to go deep into the lengthy book notes.
If you want to prepare yourself for TIBCO RV only, you can refer to TIBCO RV Top 10 Interview Questions and Answers also:
Q1: What is the role of TRA (Tibco Runtime Agent)?
Ans: There are two main functions of TRA:
1. TIBCO Runtime Agent (TRA) is responsible for starting and stopping of processes running on a machine.
2. TRA provides runtime environment for TIBCO applications.
TRA runs on every TIBCO machine in the background.
Q2: What type of resources in TIBCO EAR file?
Ans: Following type of resources are typically added in EAR file in TIBCO:
- Local Project Resources (Processes, Schemas, Connections, Services, Variables etc)
- Library Builder Resources Files.
- Files referred in designer CLASSPATH
- Files under Designer Installation directory
Q3: What is vcrepo.dat and when this file is created in TIBCO?
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.
Q4: While debugging TIBCO BW processes, which activity can be used to write complete schema information to a file?
Ans: 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.
Q5: How Restful web services can be developed in TIBCO?
Ans: TIBCO provides a Plugin for REST and JSON which can be used to develop Restful web services in TIBCO designer.
Q6: Can we have backward transitions in TIBCO BW Processes?
Ans: In TIBCO Designer Processes, transitions between activities are always uni-directional. This means that we can’t go back to a previous transition from any point.
Q7: What are different Panels of TIBCO designer window and what is the purpose of each?
Ans: There are following four types of panels available in TIBCO designer window:
- Project Panel: This panel shows project hierarchy.
- Design Panel: This panel is used to design new BW Processes in TIBCO.
- Palette Panel: This Panel has all the available Palettes with bundled activities which can be dragged and used in design panel during process development.
- Configuration Panel: Configurations including input, output details for any activity are specified in the configuration panel.
Q8: What are the three levels of validations that can be performed in TIBCO designer?
Ans: Following are the three levels of validations supported by TIBCO BW:
1. Activity level validation
2. Process level validation
3. Project level validation
Q9: What is difference between fault tolerant and Load balanced deployment in TIBCO?
Load balancing is done between two or more servers where the load is distributed between servers to avoid any server crashes due to heavy load on a single server.
Fault tolerance is achieved between two servers where one server acts as a primary and the second server acts as a secondary/backup server for the primary server. Whenever failure occurs for primary server, the backup secondary server becomes the primary server.
Q10: What are the options for configuring storage for process engine’s checkpoint repository ?
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.