TIBCO Application Development 2 — Questions and Answers
Question 1: In TIBCO ActiveMatrix BusinessWorks 6, which deployment model uses OSGi bundles to package application artifacts?
- Module-based deployment using OSGi bundles within AppNodes (Correct answer)
- WAR file deployment on Apache Tomcat
- EAR file deployment on JBoss EAP
- Flat JAR deployment on a standalone JVM
Correct answer: Module-based deployment using OSGi bundles within AppNodes
TIBCO BW 6 uses an OSGi container. Applications are packaged as OSGi bundles and deployed into AppNodes running on AppSpaces, leveraging the OSGi service registry for modularity.
TIBCO ActiveMatrix BusinessWorks 6 is built on Eclipse Equinox, an OSGi framework. Each BW application is structured as one or more OSGi bundles (module projects) that declare their dependencies via bundle manifests. The BW runtime (AppNode) is itself an OSGi container that loads these bundles, resolves inter-bundle dependencies, and provides lifecycle management. This architecture enables hot deployment, fine-grained versioning, and sharing of common libraries across applications without application server redeployment.
Question 2: What is the purpose of a Shared Module in TIBCO BusinessWorks?
- To reuse common processes, schemas, and resources across multiple application modules (Correct answer)
- To share a single database connection across multiple servers
- To expose REST endpoints publicly on the internet
- To package BPMN diagrams for import into TIBCO BPM
Correct answer: To reuse common processes, schemas, and resources across multiple application modules
A Shared Module in BW is a reusable library containing common process templates, XSD schemas, WSDL definitions, or shared resources that multiple Application Modules can reference.
In TIBCO BusinessWorks 6, the project model includes Application Modules (containing runnable processes) and Shared Modules (containing reusable artifacts). A Shared Module is not directly deployable — it exports its artifacts as OSGi packages that Application Modules import. Common use cases include shared JDBC connection pools, common XSD schemas, utility subprocess libraries, and shared HTTP connections.
Question 3: Which activity in TIBCO BusinessWorks is used to call an external REST service?
- REST Invoke activity via the HTTP Client palette (Correct answer)
- SOAP Invoke activity
- JDBC Query activity
- JMS Publish activity
Correct answer: REST Invoke activity via the HTTP Client palette
The REST Invoke (or HTTP Client Invoke) activity is the standard way to make outbound REST/HTTP calls to external services from a BW process.
TIBCO BusinessWorks provides a built-in HTTP Client palette containing the HTTP Client Invoke activity (referred to as REST Invoke when used with REST bindings). The activity is configured with a resource reference pointing to an HTTP Connection resource. At runtime the activity performs the HTTP call, allowing process data to be mapped to URL path parameters, query strings, headers, and the request body.
Question 4: In TIBCO BW, what is the role of the Mapper activity?
- To transform data between activity inputs and outputs using XPath or schema mappings (Correct answer)
- To map database tables to XML schemas automatically
- To deploy process binaries to remote AppNodes
- To configure the BW runtime cluster topology
Correct answer: To transform data between activity inputs and outputs using XPath or schema mappings
The Mapper activity performs data transformation, allowing developers to visually map and transform data between process variables using XPath expressions and schema-to-schema drag-and-drop mappings.
Every TIBCO BusinessWorks process passes data between activities via process variables. The Mapper activity allows developers to define XPath transformations that move, rename, and reshape data. The BW Studio editor provides a graphical mapper with drag-and-drop schema mapping and a custom XPath function library. Complex transformations use XSLT-style constructs including for-each, if/then/else, and string manipulation functions.
Question 5: What does the Transaction Manager resource in TIBCO BusinessWorks enable?
- Coordinating XA transactions across multiple resources such as databases and JMS brokers to ensure atomicity (Correct answer)
- Managing user authentication sessions for REST APIs
- Scheduling periodic background jobs within BW processes
- Controlling file system access for file adapter activities
Correct answer: Coordinating XA transactions across multiple resources such as databases and JMS brokers to ensure atomicity
The Transaction Manager resource configures XA (two-phase commit) transaction coordination so that a group of database and JMS operations either all succeed or all roll back together.
When a TIBCO BusinessWorks process needs to update a database and publish a JMS message atomically, it uses a Transaction Group activity and configures a Transaction Manager resource. The Transaction Manager implements the XA protocol, coordinating a two-phase commit across all enlisted resources. If any participant fails during commit, the Transaction Manager sends rollback instructions to all others, ensuring the entire operation is atomic.
Question 6: Which BW 6 feature allows an application to be packaged and deployed as a Docker container on Kubernetes?
- TIBCO BusinessWorks Container Edition (BWCE) (Correct answer)
- TIBCO BW Classic Edition on JBoss
- TIBCO ActiveMatrix ESB standalone mode
- TIBCO Flogo for container deployment
Correct answer: TIBCO BusinessWorks Container Edition (BWCE)
TIBCO BusinessWorks Container Edition (BWCE) is the Dockerised version of BW that packages processes as Docker images for deployment on Kubernetes and other container orchestration platforms.
TIBCO BusinessWorks Container Edition extends the BW 6 application model for cloud-native deployments. Developers build BW applications in Business Studio as normal, then use Maven or Gradle plugins to generate a Docker image that includes the BW runtime and application bundle. BWCE applications are stateless, read their configuration from environment variables (12-factor app pattern), and integrate with Kubernetes-native features like health probes and horizontal pod autoscaling.
In TIBCO ActiveMatrix BusinessWorks 6, which deployment model uses OSGi bundles to package application artifacts?