Technical Interview Questions and Answers :: WebMethod

you can use start and commit transaction to control JDBC manually such as use Local Transaction that will let you control DB by put inside your service start transaction when service start and when it done will invoke commit or rollback in case there is an error

No Discussion on this question yet!

Broker - Broker’s role is to manage the routing of documents between applications running on different Integration Servers. For an Integration Server to join in this process, it must first be configured to connect to Broker.

Broker Server - The server which host broker instance is called broker server.

Type of Flow service

The INVOKE Step

The BRANCH Step

The REPEAT Step

The SEQUENCE Step

The LOOP Step 

The EXIT Step 

The MAP Step

LOOP - The LOOP step repeats a sequence of child steps once for each element in an array that you specify. For example, if your pipeline contains an array of purchase‐order line items, you could use a LOOP step to process each line item in the array. To specify the sequence of steps that make up the body of the loop (that is, the set of steps you want the LOOP to repeat), you indent those steps beneath the LOOP.

REPEAT- The REPEAT step allows you to conditionally repeat a sequence of child steps based on the success or failure of those steps. You can use REPEAT to:

Re-execute (retry) a set of steps if any step within the set fails.

Re-execute a set of steps until one of the steps within the set fails.

The EXIT flow step allows you to exit the entire flow service or a single flow step. You specify whether you want to exit from:

The nearest ancestor (parent) LOOP or REPEAT flow step to the EXIT flow step.

The parent flow step of the EXIT flow step.

A specified ancestor flow step to the EXIT flow step.

The entire flow service.

Properties used in exit step

Exit from- The flow step from which you want to exit. Specify any one of $loop, $parent $flow Label.

Signal - Whether the exit is to be considered a success or a failure.Specify one of the following:

Specify… To…

SUCCESS Exit the flow service or flow step with a success condition.

FAILURE Exit the flow service or flow step with a failure condition. An exception is thrown after the exit. You specify the error message with the Failure message property.

Failure message The text of the exception message you want to display. If you want to use the value of a pipeline variable for this property, type the variable name between % symbols (for example,%mymessage%).

This property is not used when Signal is set to SUCCESS

SEQUENCE -  You use the SEQUENCE step to build a set of steps that you want to treat as a group. Steps in a group are executed in order, one after another. By default, all steps in a flow service, except for children of a BRANCH step, are executed as though they were members of an implicit SEQUENCE step (that is, they execute in order, one after another). However, there are times when it is useful to explicitly group a set of steps.

BRANCH  - The BRANCH step allows you to conditionally execute a step based on the value of a variable at run time. For example, you might use a BRANCH step to process a purchase order one way if the PaymentType value is “CREDIT CARD” and another way if it is “CORP ACCT”.

Branch on a switch value. Use a variable to determine which child step executes. At run time, the BRANCH step matches the value of the switch variable to the Label property of each of its targets. It executes the child step whose label matches the value of the switch.

Branch on an expression. Use an expression to determine which child step executes. At run time, the BRANCH step evaluates the expression in the Label property of each child step. It executes the first child step whose expression evaluates to “true.”

INVOKE  - Use the INVOKE step to request a service within a flow. You can use the INVOKE step to:

􀂄 Invoke any type of service, including other flow services and Web service connectors.

􀂄 Invoke any service for which the caller of the current flow has access rights on the local webMethods Integration Server.

􀂄 Invoke built‐in services and services on other webMethods Integration Servers.

􀂄 Invoke flow services recursively (that is, a flow service that calls itself). If you use a flow service recursively, bear in mind that you must provide a means to end the recursion.

􀂄 Invoke any service, validating its input and/or output.

Yes, it should be accessable if it is declared before the main sequence as an individual variable.

Scope of a variable is limited when declared inside a sequence when scope is mentioned.