Stepping Into and Out of a MAP Step

You can use the step commands to debug individual transformers within a MAP step.

1. Debug the service as described in Debugging a Flow Service.

3. In Designer, select Run > Step Into or click

on the Debug view toolbar.

In Pipeline view, Designer highlights the links to the transformer (but does not execute) a transformer in the MAP step. Keep in mind that transformers in a MAP step are independent of each other and do not execute in a specific order.

4. If the transformer is a flow service and you want to step into the transformer, do the following:

a. Select Run > Step Into or click

on the Debug view toolbar. Designer executes the links to the transformer and steps into the transformer (flow service). Continue stepping through the transformer using Step Into or Step Over.

To return to the MAP step pipeline, select Run > Step Return or click

on the Debug view toolbar.

b. Select Run > Step Over or click

to execute the links between the transformer to the variables in Pipeline Out.

c. Repeat the above steps each transformer that you want to individually execute in the MAP step. If you want to execute the next transformer without stepping through transformer and link execution, select Run > Step Over.

5. If the transformer is not a flow service or you do not want to step into it, select Run > Step Over or click

on the Debug view toolbar.

6. If you want to return to the parent without stepping through the entire MAP, select Run > Step Return or click

on the Debug view toolbar. This executes the remaining transformers in the MAP, returns to the parent flow service, and selects (but does not execute) the next step in the parent flow service.

If you select Step Return, Designer executes the remaining steps in the MAP and returns to the parent automatically. However, Designer stops executing if it encounters an enabled breakpoint.

You can use Step Into to step into a transformer that is not a flow service.

In Debug view, under the service thread stack frame, Designer displays MAPINVOKE before Designer executes the transformer. Designer displays MAPCOPY right after the service executes but before Designer executes the links from the transformer to the variables in Pipeline Out.