Answer / moolawebmethods

We have 3 types of JDBC Adapter Transactions.

1)NO_TRANSACTION:The connection automatically commits the
operations.

2)LOCAL_TRANSACTION:The connection uses local transactions.

If we plan to use the connection with BatchInsertSQL or
BatchUpdateSQl adapter services,we must specify
LOCAL_TRANSACTIONS types.
If we are configuring a BasicNotification and using the
exactly once notification and delete stored records options
we must configure the notification to use LOCAL_TRANSACTION
type.

3)XA_TRANSACTION:The connection uses XA transactions.

When we are connecting to Teradata we use XA transaction.

Answer / bhokalibaba

While reading this material please do not confuse a Transaction with an Operation. A transaction might consist of multiple operations like select, insert, delete,update etc. Also multiple operations can be of two types:

A series of operations i.e operations taking place one after the other and are inter-related.
A batch of operations which takes place concurrently all together.

Description:
Some transactions involve a series of related operations, not just one single operation always. In webmethods such multiple operations are performed even using a single adapter service or a flow service or a Java service or in multiple steps in a flow service.

There is a loophole in such kind of transaction if the different operations are performed in different DB servers not in same DB server:

The webmethods makes use of multiple connections in one service itself, in this case.

If either of the operation fails in the transaction, the other operations which have been already performed in other DB servers will not be notified for roll back. This would result in incomplete transaction.

To get rid of this problem we have something called 2-Phase commit. That is whenever such multiple operations occur in multiple, distributed DB servers, they(the operations) occur in 2 phases. And also the operations are monitored by a coordinator.

The coordinator asks the data-source of the operation if it is ready to commit the operation in so called Prepare Phase.
If the operation is ready to be committed, the operation gets committed in the data-source in so called Commit Phase.

If not, then the coordinator rolls back all the previous operations from the DB servers to avoid an incomplete transaction from happening.

This concept of multiple operations in multiple, distributed DB servers in one single transaction belongs to DB not to webmethods. It's just webmethods supports such kind of transaction using so called XA_Transaction type of connection.

XA transaction stands for distributed transaction. It is also called Global Transaction.

Local transactions differ from XA_Transaction in using one single connection rather than multiple, distributed Database servers to perform a series of operations. In local transactions, it is not a big deal to commit all operations or roll back the operations together in case of a failure in any operation, as all the operations take place in one single data-source in one single DB server. So coordinator is also not required in local transactions.


No Transaction: If a connections is of type ''no connection'' then even if an operation fails,it does not matter, the other operations in the transaction will be committed. This is because such transactions have auto-commit capability only, no rolling back.

Answer / malli

1.No_Transaction : It is a auto commit transaction.
2.Local_Transaction : It is a local and one way transaction.
3.XA_Transaction : It is a two way transaction

Answer / ajitabh kumar sharma

There are three transaction types related to JDBC Adapter:

1. NO_TRANSACTION: The transaction gets committed automatically.
2. LOCAL_TRANSACTION: It involves transaction using only one
database [Non distributed transaction]
3. XA_TRANSACTION: It is used to control distributed
transaction and supports 2PC protocol etc.

Answer / guest

There are 3 tranaction types in JDBC adapter
1) NO_TANSACTION
2)LOCAL_TRANSACTION
3)XA_TRANSACTION

Answer / gowtham raj

1.Local transaction
2.XA transaction
3.NO transaction

Answer / rahul sharma

1. NO_TRANSACTION:This is , the connection automatically commits for all the Operation.
2.LOCAL_TRANSACTION:The connection uses local transactions[Using Only one database].

3.XA_TRANSACTION: This transaction type allows the connection to support two-phase transactions executed across multiple
databases.

Answer / nvijay

three types jdbc adapter transaction:
1)local-transaction:commit&rollback must be used in bach
insert&bach uppdate

Which value have to set for EnableAudit log while package replication?

1 Answers   TCS,

gate ways in webmethods

4 Answers   IBM,

How to Change the Order of Steps in a Flow Service?

1 Answers  

How can you see partner data using webservice.

1 Answers   Mphasis,

what is the variable need to keep in the clearpipeline service

1 Answers   Wipro,

i have partner A,and partner B, then i want to send a document to partner B, what are requirements i will provide to partners ?

1 Answers   IBM,

What is correlation ID?

1 Answers   Colt,

what is the difference of using transformer in service & direct invoke of service?

3 Answers   Cap Gemini, Siemens,

What happens to the locks on elements when we replicate a package?

1 Answers  

Hi I am using Wenmethods 7.1 since many years. I am on Webmethods project. Today my Boss asked me about CLSRIM (Webmethods service, when one server is down, automatically another will take over. Can you please throw some light on above ? OR from where can I get some help ? IT IS URGENT...... Komalika

4 Answers  

Who is Best Prime Minister of India

3 Answers  

How to Restore a Session on a Server?

1 Answers