Free TCA-TIBCO-BusinessWorks sample questions

Correct answers: In a Shared Module.; Invoked via a 'Call Process' activity from the fault handlers.

Correct answer: The database update will be automatically rolled back by the transaction manager.

When JDBC and JMS activities are placed within the same transaction group of type 'XA', they participate in a distributed, two-phase commit transaction. The transaction manager ensures atomicity. If the 'JDBC Update' completes its part of the transaction (phase one) but the 'Send JMS Message' fails before it can commit (phase two), the transaction manager will issue a rollback command to all participants. Therefore, the database update will be rolled back to maintain data consistency across both resources.

Correct answer: False

This statement is false. For managed fault tolerance, where the engine actively manages failover between AppNodes, the persistence mode must be set to 'group'. This allows AppNodes in the AppSpace to share state and coordinate failover. The 'datastore' persistence mode is used for non-managed fault tolerance, where an external load balancer is typically responsible for directing traffic to a hot standby.

Correct answer: upload

The `bwadmin upload` command is specifically used to transfer an application archive (EAR) file from the local file system to a specific domain and AppSpace managed by the bwagent. This is a prerequisite step before the application can be deployed, started, or managed using other `bwadmin` commands like `deploy` and `start`.

Correct answer: Enable activity tracing in the launch configuration for the application.

Enabling activity tracing in the Debug or Run Configuration is the designed feature for this exact purpose. When enabled, the engine automatically records the input and output data for every executed activity, which can then be inspected in the Console view. This avoids the tedious process of setting individual breakpoints and provides a complete execution trace for the job.

Correct answers: An HTTP Connector Shared Resource.; A JAAS Login Module Resource.; An Identity Provider Shared Resource.

Correct answer: Persistence Mode: group, Activation: Single AppNode

This configuration enables managed fault tolerance. The 'group' persistence mode allows AppNodes within the AppSpace to share state via the shared file system. The 'Single AppNode' activation setting ensures that only one AppNode is active at any time for the application. If the active node fails, the TIBCO ActiveMatrix BusinessWorks engine automatically promotes a standby node to active, which then uses the shared state to resume any recoverable, checkpointed jobs.

Correct answer: bwobfuscator

The `bwobfuscator` utility is the specific command-line tool provided by TIBCO to create obfuscated (OBF) password strings. The administrator runs this tool with the plain-text password as input, and it outputs a string prefixed with 'OBF:'. This output string is then copied into the `bwagent.ini` file to secure the password.

Correct answer: To synchronize execution for a group of activities across multiple process instances.

A 'Critical Section' group is a concurrency control mechanism. It ensures that the activities contained within it are executed by only one process instance at a time for a given scope (e.g., across all jobs for that process, or jobs sharing a specific lock object). This is used to protect shared resources, such as a file or a non-thread-safe legacy system, from simultaneous access by concurrent jobs.

Correct answer: The `OrderProcessing` Application Module must be re-exported to generate a new EAR file and then deployed.

When a Shared Module is changed, any Application Module that depends on it must be rebuilt to include the updated code. The deployment unit in BusinessWorks is the Application EAR file. Therefore, the `OrderProcessing` Application Module must be re-exported from BusinessStudio, which will package the latest version of the `CommonLogging` module into the new EAR file. This new EAR must then be deployed to the environment.