Using Asynchronous Web Services with Callback

Monitoring Integration Processes 21-5 4. Review in the list of sessions the status of your sessions.

21.2.2 Monitoring Load Plan Runs

To monitor your Load Plan runs: 1. In the Operator Navigator, expand the Load Plan Executions accordion.

2. Expand the All Executions node and click Refresh in the Navigator toolbar.

3. Review in the list the status of your Load Plan run. 4. Double-click this Load Plan run to open the Load Plan Run editor. 5. In the Load Plan Run editor, select the Steps tab. 6. Review the state of the Load Plan steps. On this tab, you can perform the following tasks: ■ Click Refresh in the Editor toolbar to update the content of the table. ■ For the Run Scenario steps, you can click in the Session ID column to open the session started by this Load Plan for this step.

21.2.3 Handling Failed Sessions

When your session ends in error or with a warning, you can analyze the error in Operator Navigator. To analyze an error: 1. In the Operator Navigator, identify the session, the step and the task in error. 2. Double click the task in error. The Task editor opens. 3. On the Definition tab in the Execution Statistics section, the return code and message give the error that stopped the session. 4. On the Code tab, the source and target code for the task is displayed and can be reviewed and edited. 5. On the Connection tab, you can review the source and target connections against which the code is executed. You can fix the code of the command in the Code tab and apply your changes. Restarting a Session is possible after performing this action. The session will restart from the task in error. Note: Fixing the code in the session’s task does not fix the source object that was executed interface, procedure, package or scenario. This source object must be fixed in Designer Navigator and the scenario if any must be regenerated. Modifying the code within the session is useful for debugging issues. WARNING: When a session fails, all connections and transactions to the source and target systems are rolled back. As a consequence, uncommitted statements on transactions are not applied. 21-6 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

21.2.4 Reviewing Successful Sessions

When your session ends successfully, you can view the changes performed in Operator Navigator. These changes include record statistics such as the number of inserts, updates, deletes, errors, and the total number of rows as well as execution statistics indicating start and end time of the execution, the duration in seconds, the return code, and the message if any. Session level statistics aggregate the statistics of all the steps of this session, and each step’s statistics aggregate the statistics of all the tasks within this step. To review the execution statistics:

1. In the Operator Navigator, identify the session, the step or the task to review.

2. Double click the session, the step or the task. The corresponding editor opens.

3. The record and execution statistics are displayed on the Definition tab. Note that

for session steps in which an interface has been executed or a datastore check has been performed also the target table details are displayed. Record Statistics Execution Statistics Target Table Details Properties Description No. of Inserts Number of rows inserted during the sessionsteptask. No. of Updates Number of rows updated during the sessionsteptask. No. of Deletes Number of rows deleted during the sessionsteptask. No. of Errors Number of rows in error in the sessionsteptask. No. of Rows Total number of rows handled during this sessionsteptask. Properties Description Start Start date and time of execution of the sessionsteptask. End End date and time of execution of the sessionsteptask. Duration seconds The time taken for execution of the sessionsteptask. Return code Return code for the sessionsteptask. Properties Description Table Name Name of the target datastore. Model Code Code of the Model in which the target datastore is stored. Resource Name Resource name of the target datastore. Logical Schema Logical schema of this datastore. Forced Context Code The context of the target datastore. Monitoring Integration Processes 21-7

21.2.5 Handling Failed Load Plans

When a Load Plan ends in error, review the sessions that have failed and caused the Load Plan to fail. Fix the source of the session failure. You can restart the Load Plan instance. See Section 20.7, Restarting a Load Plan Run for more information. Note that it will restart depending on the Restart Type defined on its steps. See Section 14.2.4, Handling Load Plan Exceptions and Restartability for more information.

21.2.6 Reviewing Successful Load Plans

When your Load Plan ends successfully, you can review the execution statistics from the Load Plan run editor. You can also review the statistics for each session started for this Load Plan in the session editor. To review the Load Plan run execution statistics: 1. In the Operator Navigator, identify the Load Plan run to review. 2. Double click the Load Plan run. The corresponding editor opens. 3. The record and execution statistics are displayed on the Steps tab.

21.3 Managing your Executions

Managing your development executions takes place in Operator Navigator. You can manage your executions during the execution process itself or once the execution has finished depending on the action that you wish to perform. The actions that you can perform are: ■ Managing Sessions ■ Managing Load Plan Executions ■ Managing the Log ■ Managing Scenarios and Load Plans ■ Managing Schedules

21.3.1 Managing Sessions

Managing sessions involves the following tasks ■ New sessions can be created by executing run-time objects or scenarios. See Chapter 20, Running Integration Processes for more information on starting sessions. ■ Sessions in progress can be aborted. How to stop sessions is covered in Section 20.5, Stopping a Session . ■ Sessions failed, or stopped by user action can be restarted. Restarting sessions is covered in Section 20.4, Restarting a Session . In addition to these tasks, it may be necessary in production to deal with stale sessions.