- GUI mode
- Console mode
- Silent mode
Integration can be at different application layers:
- X:Patch
- Y:Major
- Z:Minor
TRA stands for TIBCO Runtime Agent.
The TRA has two main functions:
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.
An EAR file can contain local project resources, LibraryBuilder resources, and files as specified in AliasLibrary resources. In addition, the TIBCO Designer classpath may include references to other files that are included in the EAR file.
5.What are the revision control system options in TIBCO designer?
- File sharing
- VSS
- Perforce
- XML Canon
- ClearCase
- iPlanet
- CVS
- PVCS
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.
TIBCO Designer creates a file named vcrepo.dat in the project root directory when you first save the project. This file is used to store properties such as display name, TIBCO Rendezvous encoding, and description. This file can be used for identification in place of the project root directory and can be used as the repository locator string (repoUrl).
8.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
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
The Java Transaction API (JTA) UserTransaction type allows:
- JDBC
- JMS
- ActiveEnterprise Adapter (using JMS transports)
- EJB activities
to participate in transactions.
No comments:
Post a Comment