You can debug the Service Bus components that are deployed on an integrated or standalone WebLogic Server. JDeveloper can manage the lifecycle for a local integrated WebLogic server instance. When you configure a local integrated server, you can select Let JDeveloper Manage the lifecycle for this server instance. With this configuration, JDeveloper starts the server when you select the Run or Debug command. If the integrated server is not configured to be managed by JDeveloper, you need to manually start and stop the server; however you can still use the Run command to deploy the service to be tested to the server. If the integrated server is remote, do not select Let JDeveloper Manage the lifecycle for this server instance.

When you use a standalone server for debugging, the configuration is the same whether it is local or remote. You do not need to configure the server in the application properties. With a standalone server, you cannot use the Run command from the Application Navigator. Instead, you need to manually deploy the Service Bus application to the server using the Deploy command, and you need to start the test console manually.

Debugging can be performed on either a local or remote WebLogic server. A local debugging session is started by setting breakpoints in source files, and then starting the debugger. When debugging a Service Bus component, you have complete control over the execution flow and can view and modify values of variables.

Remote debugging requires two JDeveloper processes: a debugger and a debugee. The debugee is a running server that may or may not be defined in JDeveloper and may reside on a different platform. A Service Bus application must be deployed on the debugee server. In order to perform remote debugging, you must configure a run configuration in the project properties, as described in How to Create Run Configuration for Remote Debugging.

A breakpoint marks a point in a pipeline or split-join where message processing pauses. This lets you examine the values of some or all of the message variables. By setting breakpoints in potential problem areas of your message flow, you can run data through a message flow until it reaches a location you want to debug. When a breakpoint is encountered, message processing pauses and the debugger focuses on the action containing the breakpoint in the source editor. You can then use the debugger to view the state of your program. Breakpoints are flexible in that they can be set before you begin debugging or at any time while you are debugging.

Breakpoints can be added to the following nodes on a pipeline:

• Route node

• Route action

• Branch node

• Pipeline pair path (request or response)

• Stage (both in pipeline pairs and error handlers)

• Stage action (both in pipeline pairs and error handlers)

You can add breakpoints to all split-join actions, but toggling a breakpoint on an If node toggles the breakpoint for the If condition within the If node and not the If node itself.

JDeveloper provides several different debugging windows with the debugger, where you can view and analyze data as it moves through the debugging process. Service Bus utilizes the following debugging windows:

• Breakpoints

• Data

• Watches

• Stack

• Threads

• Log

For more information about these windows, see "Using the Debugger Windows" in Developing Applications with Oracle JDeveloper.

Starting in 12.2.1, JDeveloper has been enhanced to debug XSLT maps using the SOA Debugger.

You can invoke this feature from Service Bus split-join and pipeline editors and from the XSLT test tool in JDeveloper. For information on debugging XSLT maps and setting breakpoints in the XSLT map editor, see Debugging the XSLT Map in Developing SOA Applications with Oracle SOA Suite.

1. From the main menu click Application and select Project Properties.
2. In the navigation pane, select Run/Debug, and then click New on the Run/Debug page.
3. On the Create Run Configuration dialog, enter a name for the new configuration and select an existing run configuration to copy the initial properties from.
4. Click OK.
5. In the Run Configurations section of the Run/Debug page, select the configuration you just created and then click Edit.

   The Edit Run Configuration window appears with the Launch Settings page displayed.

6. Select Remote Debugging, and modify any other fields as needed.
7. In the navigation pane, select Remote under Tool Settings > Debugger.
8. In the Protocol field, select Attach to Service Bus.
9. Do one or both of the following:

   • To connect a specific server automatically when you select this run configuration, enter the host name, port number, and a timeout value.

   • To display a dialog that lets you enter host information when you select this run configuration, select Show Dialog Box Before Connecting Debugger.

   If you perform both of the above steps, the dialog appears when you select the run configuration, and is already populated with the connection information you specified above.

10. Click OK, and then click OK again.
11. Click Save.

1. From the main menu click Application and select Project Properties.
2. Select Run/Debug.
3. In the Run Configurations list, select the run configuration you want to use, and then click OK.

1. Open the pipeline or split-join you want to debug in its editor.
2. Expand the actions until you see the node to which you want to add a breakpoint.
3. Right-click the node, and select Toggle Breakpoint.

   A red icon appears next to the node to indicate that a breakpoint is set.

4. Repeat the above step for each node to which you want to add a breakpoint.
5. To disable a breakpoint, right-click the node and select Disable Breakpoint.

   You can also enable, disable, and remove breakpoints from the Breakpoints view, as described in How to Remove or Disable Breakpoints and How to Enable a Disabled Breakpoint.

6. To remove a breakpoint, right-click the node and select Toggle Breakpoint again.
7. Begin debugging, as described in How to Debug Using Breakpoints.

Exception breakpoints do not halt execution at a set point; you set exception breakpoints in JDeveloper’s Breakpoints window instead of in a specific location.

1. In JDeveloper, navigate to the Breakpoints window. If this window is not visible, from the Window menu, select Breakpoints to open the window.
2. Click the Add Breakpoint icon, and then select Pipeline Exception Breakpoint or Split/Join Exception Breakpoint to add an exception breakpoint of the selected type.
3. On the Definition tab, select the exception type used for this breakpoint from the Exception Type list.

   See Pipeline Exception Breakpoints and Split-Join Exception Breakpoints for information about the exception types available for pipeline and split-join exception breakpoints.

4. If supported by the selected type, enter a specific exception error code into the Error Code field, or enter an asterisk (*) to halt execution when any exception of the selected type is thrown.
5. (Optional) Configure the options on the Conditions and Actions tabs, if necessary.
6. Click OK.

1. Define the breakpoints for the component to debug, as described in How to Set Breakpoints on Service Bus Components..
2. Right-click the pipeline or split-join in the Application Navigator, and select Debug.

   The Test Console appears.

   Note:

   If you do not have a domain running, the Create Default Domain dialog appears. Enter the connection information for the integrated server and click OK. This may take several minutes.

3. Enter the test data in the Request Document section, and configure any additional input.

   For more information, see Using the Test Console.

4. Click Execute on the Test Console.

   The Test Console executes the command, but pauses when it reaches the first breakpoint and returns to the editor for the pipeline or split-join. The breakpoint icon is now blue instead of red to indicate where the debugger is stopped.

5. In the Log window at the bottom of JDeveloper, click Data.

   In this window, you can view variable values at the current state in processing. For information about what you can do here, see Working with the Debugger Windows.

6. To continue working through the message processing, perform the steps under How to Step Through a Debugging Session.

1. Begin debugging the pipeline or split-join as described in How to Debug Using Breakpoints.

   When the debugger reaches a breakpoint, you can begin to step through.

2. To find the action on which the current breakpoint is stopped, click the Find Execution Point icon.

   The current breakpoint icon is blue instead of red.

3. To step over a breakpoint and move to the next action, click the Step Over icon.
4. To step into the next valid location in the message flow, click the Step Into icon.
5. To step out of a breakpoint frame, click the Step Out icon.
6. If the debugger is paused on a breakpoint, click the Resume icon to resume processing. The process runs until the next breakpoint is reached.

1. Click the Terminate icon in the tools menu.

   The Terminate Debugger Process dialog appears.

2. Select Detach or Terminate.

   Both options terminate the debugger connection to the server and the process continues to run on the server until it completes.

3. If you selected Detach, click the debugger icon in the tools menu to resume debugging.

1. If the Breakpoints window is not open, select Window > Breakpoints from the main menu.
2. Right-click a breakpoint and select Edit, or select the breakpoint and click the Edit icon on the Breakpoint toolbar.

   The Edit Breakpoint dialog appears with a Definition tab, a Conditions tab, and an Actions tab.

3. Make any necessary changes to the breakpoint options.

   For more information about the Definition and Actions tabs, click Help.

4. To save the changes, click OK.

1. To remove an individual breakpoint, right-click the action associated with the breakpoint in the pipeline or split-join editor and select Toggle Breakpoint. You can also select the breakpoint in the Breakpoints window, and click Delete. You must remove exception breakpoints using the Breakpoints window.
2. To remove all breakpoints, right-click in the Breakpoints window, and select Delete All.
3. To disable an individual breakpoint, right-click the action associated with the breakpoint in the pipeline or split-join editor and select Disable Breakpoint. You can also select the breakpoint in the Breakpoints window, and click Disable. You must disable exception breakpoints using the Breakpoints window.
4. To disable all breakpoints, right-click in the Breakpoints window, and select Disable All.

1. To enable an individual breakpoint, right-click the action associated with the breakpoint in the pipeline or split-join editor and select Enable Breakpoint. You can also select the breakpoint in the Breakpoints window, and click Enable. You must enable exception breakpoints using the Breakpoints window.
2. To enable all breakpoints that have been set, right-click in the Breakpoints window, and select Enable All.

1. Begin debugging and when the debugger reaches a breakpoint, click the Data tab in the Log window.
2. Expand the variables in the Name column to view the values of each variable and node.
3. To modify a variable value, double-click the value and enter the new value in the dialog that appears.
4. To view the entire string that defines the variable value, right-click the variable and select View Whole Value.

1. Begin debugging and when the debugger reaches a breakpoint, click the Data tab in the Log window.
2. In the Name column, expand the nodes until you see the variable you want to watch.
3. Right-click the variable and select Watch.

   The Watch window opens with a new row defining the watch for the selected variable.