Use to view the running or completed sessions.
A session is an execution (of a scenario, a mapping, a package, or a procedure) undertaken by an execution agent. A session is made up of steps which are made up of tasks.
The Session Editor has the following tabs:
| Properties | Description |
|---|---|
| Instance ID | Internal ID of the session within the work repository. |
| Global ID | Global unique identifier for the session specific across work repositories. |
| Session Name | Name of the session. |
| Status | The session status when the Session Editor was opened. The possible states are Done, Error, Running, Waiting, Queued, and Warning. |
| Scenario Name | Name of the scenario, package, mapping, procedure, and so forth, executed in this session. |
| Context | Context in which the execution was run. |
| Scenario Version | Version (for a scenario). |
| Physical Agent | Agent responsible for the execution of the tasks in this session. |
| Start | Start date and time of execution of the session. |
| End | End date and time of execution of the session. |
| Duration (seconds) | Time taken for execution of the session. |
| Return code | Return code for the session. |
| URL | An optional URL link that enables you to view details such as execution structure, metrics, error messages, and logs using a UI specific to the execution. For example, Oozie Web Console or MapReduce JobTracker. |
Concurrent Execution Controller
| Properties | Description |
|---|---|
| Limit Concurrent Executions | If checked, enables the Concurrent Execution Controller for the Session. |
| Violation Behavior | Specifies the violation behavior action. Default is Raise Error and End Execution. |
| Wait Polling Interval | Specifies the polling frequency (in seconds) for the wait behavior to check for its turn to run. This field accepts only a positive integer, and it is enabled only when Violation Behavior is selected as Wait.
Note: A newly generated scenario or a newly created load plan has blank as the default value, meaning that the runtime agent determines the actual value used for the polling (currently the default is 30 seconds in the runtime agent). |
| Properties | Description |
|---|---|
| No. of Inserts | Number of rows inserted during the session. |
| No. of Updates | Number of rows updated during the session. |
| No. of Deletes | Number of rows deleted during the session. |
| No. of Errors | Number of rows in error in the session. |
| No. of Rows | Total number of rows handled during this session. |
| Properties | Description |
|---|---|
| Error Message | Session execution error message, if any. |
| Execution information details | Number of running child sessions, successful child sessions, and failed child sessions. |
Use to view steps and executions statistics of a given session.
In the Steps Hierarchy table, each row represents a step. For more details on the properties displayed in this table and the actions you can perform, see the Steps section in the Load Plan Run Editor.
To bring up the Session Task Editor, double-click on a task. Select a task, to show the Source Code and Target Code fields. A Code Type field appears. Select the Executed Code value when you want to see the code that was executed as part of the task execution. As this is historic information of a particular task, execution cannot be edited.
Select the Pre-execution Code value to set the code that would be used by the agent/runtime at the next execution of the task. You can edit this information.
Click Edit and use as Pre-execution Code to open the Pre-executed Code dialog.
In the Pre-execution Code dialog, enter or edit code in the Query box. Click Save Pre-executed Code to save code you have entered. Click Cancel to reject all changes and return to the Property Inspector.
In the Property Inspector, click Revert to original Pre-execution Code to undo any changes or new code you have entered and restore the original Pre-execution code.
Blueprints show all the steps and task hierarchy of the selected session. You can also view and edit the source and target code for any task within the session.
You can only see a blueprint on the tab of the properties of a session. You see the same blueprint in different sessions based on a given mapping. If you make edits to a blueprint, the edited code is used for all sessions run from a mapping. Even if you delete all of the sessions, the cached blueprint survives and is reused when you next start a session from the unchanged mapping.
After you edit a mapping, new sessions that run based on it, do not use a previously cached blueprint; instead, a new blueprint is generated. If you want to preserve a blueprint, you must either create a scenario from the current mapping, or make a copy of your mapping before editing it (to preserve the blueprint for sessions run on that mapping).
In the Steps Hierarchy table, each row represents a step. You can set break points on blueprint steps and tasks for debugging purposes. See Debugger for more details.
For more details on the properties displayed in this table and the actions you can perform, see the Steps section in the Load Plan Run editor.
Select a task to show the Property Inspector with Source Code and Target Code fields.
Click Edit and use as Pre-execution Code to open the Pre-executed Code dialog.
In the Pre-execution Code dialog, enter or edit code in the Query box. Click Save Pre-executed Code to save code you have entered. Click Cancel to reject all changes and return to the Property Inspector.
In the Property Inspector, click Revert to original Pre-execution Code to undo any changes or new code you have entered and restore the original Pre-execution code.
Use to view a summary of the Oozie or MapReduce job details when a session is executed within a Hadoop cluster.
| Properties | Description |
|---|---|
| External ID | ID representing the execution in the external system, for example, an Oozie Job ID when the execution is in Oozie. |
| Path | Reference representing the object being executed in an external system, for example, an Oozie workflow when the execution is in Oozie. |
| Last Refresh | Last time the execution log details were refreshed. |
| Runs | Number of times this execution was performed. |
| Properties | Description |
|---|---|
| Execution Details | Displays optional text summarizing the execution with details from the external system. It might also contain embedded links to native UIs for the external system, such as the Oozie Web Console and MapReduce JobTracker. |
Oracle Fusion Middleware Integrating Big Data with Oracle Data Integrator
Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator