Answer Posted / wmlead

Lets assume we have a code where we are using open ssh and in the try block we are doing a sftp login .

So in case of success or error either step we would have to do a logout . So to avoid code duplication both in end of try and catch block we can have a finally block (exit on done). Do a logout in this sequence.

Also it can hold good when we do a manual connection to a DB and irrespective of success or failure we want to close connection.

Main(Exit on success)
|
|----Try(Exit on Failure)
|
|----Catch(Exit on Done)
Finally(Exit on Done)

How we can catch exception error on run time mode using flow language in webmethods?

1141

---

Where do you implemented pub-sub architecture?

1033

---

What are the advantages of eai?

1070

---

post me important interview question on webmethods

2740

---

How many minutes have you spent in your lifetime reading documentation or actually (gasp) working with any webMethods product on a real project?

2519

---

can any one please post Q and Ans for Trading Networks in webMethods

2429

---

Explain what is indices in map flow step?

1018

---

Explain about pub-sub architecture?

1030

---

When Should You Use Flow Diagram View?

2579

---

how to configure sap adapter6.1

2464

---

Explain header handlers in web services

2579

---

If I have a parent sequence with the property set- exit on success, and the try sequence block set to exit on failure, and the catch sequence block too set to failure, what is the result?

1052

---

When we use repeate, exit flow steps?

1014

---

How many kinds of log files in webmethods?

1003

---

When we use repeate flow steps?

1003

---