Use to create and customize your knowledge modules.
Knowledge Modules (KMs) are components of Oracle Data Integrator Open Connector technology. KMs contain the knowledge required by Oracle Data Integrator to perform a specific set of tasks against a specific technology or set of technologies.
The Knowledge Modules Editor has the following tabs:
Options (not for SKM)
For an LKM, IKM, RKM, JKM, and CKM, the definition tab appears with the following fields.
| Properties | Description |
|---|---|
| Name | Name of the knowledge module (KM), as it appears in the user interface. |
| Type | Type of KM |
| Consistent Set Journalizing / Simple Journalizing | This field appears only for a journalizing KM and defines which journalizing mode is managed by this knowledge module. |
| Default KM for this pair of technologies | Shows that the KM will be selected by default for the data servers with technologies shown in Source technology and Target Technology |
| Multi-Connections | Shows if the KM has access to paired data servers. If this box is selected, it becomes possible to exchange data loading commands between two data servers, of different technologies if necessary. For example, on procedure commands, you would be able to specify a command "Select ...." in one database and a command "Insert into another database" to transfer the whole result. |
| Oracle GoldenGate JKM with JAgent | Marks the knowledge module as Oracle GoldenGate Knowledge Module to make visible JAgent configuration options in physical schema, logical schemas, and models. This field only appears for the Journalizing Knowledge Module. |
| Source Technology | Source technology used by default on the procedure commands. This information is only available if the procedure is "Multi-connections"-type. |
| Target Technology | The default technology to which the commands of this procedure will be addressed. |
| Description | Detailed description of the KM. |
For an SKM, the tab appears with the following fields:
| Properties | Description |
|---|---|
| Name | Name of the KM, as it appears in the user interface. |
| Command Text | Code of the SKM. |
| Description | Detailed description of the KM. |
| Source Technology | Source technology used by default on the procedure commands. This information is only available if the procedure is "Multi-connections"-type. |
| Target Technology | The default technology to which the commands of this procedure will be addressed. |
There is no Details or Options tab for an SKM.
A Knowledge Module task is the unit of command in the execution in the Knowledge Module task list. Each task contains information about the operation to be performed on the source and target.
| Properties | Description |
|---|---|
| Name | Name of the command, as it appears in the user interface. |
| Type | Specifies the type of the task. |
| Log Counter | Shows which counter (Insert, Update, Delete or Errors) records the number of rows processed by this command. |
| Log Level | Logging level of the command. At execution time, commands can be kept in the log based on their log level. |
| Ignore Errors | Shows that the procedure is not interrupted in case of an invalid return code. If this box is selected, the procedure command goes into "warning" instead of "error", and the procedure is not be stopped. |
| Log Final Command | Select to log final code for source and target commands. This improves the readability of logs which have a lot of runtime parameters.
Use this option only for tasks that do not contain passwords or other sensitive data.nad |
| Properties | Description |
|---|---|
| Journalized Table in current source schema | If checked, the task is generated only if one of the source tables is journalized in the current source schema. |
| Properties | Description |
|---|---|
| Create Temporary Indexes | If checked, the task is generated only for temporary indexes. |
| Properties | Description |
|---|---|
| Technology | Technology on which the command is executed.
Note: To use Oracle Data Integrator Tools (commands) in KM procedure commands or procedures commands, you must set the technology to ODI Tools. To use OS commands or to execute external programs, you must set the technology to Operating System |
| Transaction Isolation | Transaction isolation level for Select orders. The isolation levels shown are those of the SQL ISO. They are not supported by all data servers.
The levels of isolation are: Default: The transaction keeps the connection's isolation level. Read Uncommitted: The transaction can read data not committed by another transaction. Read Committed: The transaction can only read data committed by other transactions (in general, this is the default mode of many data servers). Repeatable Read: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified and committed by another transaction in the meantime. Serializable: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified, deleted, or created and committed by another transaction in the meantime. |
| Context | Execution context of the query. If "Execution context" is left, the command will be executed in the execution context chosen on launching or on the step. |
| Schema | Logical schema for execution. The logical schema, linked to the context, allows the physical execution schema to be defined. |
| Transaction | You can execute commands on several concurrent transactions (numbered from 0 to 9) or work off-transaction by choosing the option Autocommit. |
| Commit | If your command is being executed in a transaction (numbered 0 to 9), you can decide to continue or to commit the current transaction according to the following modes:
No Commit: The transaction is not committed. In this case, it can be committed in a later command. If a session ends normally, all transactions are committed by default. Commit: The transaction is committed. Commit 1000 rows: Oracle Data Integrator commits every 1000 records processed. This choice is only possible on a loading procedure command, that is, one containing a source command returning a result set and a destination command that carries out inserts. |
| Command | Text of the command expressed in a native language or in a standard language (such as SQL, PL/SQL, Transact-SQL, shell, and so forth). You can use the Expression Editor, accessible through the button to the right of the text.
Warning: If the command is made of random characters, then the procedure is encrypted. For more details about encryption and decryption, see "Encrypting and Decrypting Procedures" in Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator. |
| Properties | Description |
|---|---|
| Technology | Technology on which the command is executed.
Note: To use Oracle Data Integrator Tools (commands) in KM procedure commands or procedures commands, you must set the technology to ODI Tools. To use OS commands or to execute external programs, you must set the technology to Operating System |
| Transaction Isolation | Transaction isolation level for Select orders. The isolation levels shown are those of the SQL ISO. They are not supported by all data servers.
The levels of isolation are: Default: The transaction keeps the connection's isolation level. Read Uncommitted: The transaction can read data not committed by another transaction. Read Committed: The transaction can only read data committed by other transactions (in general, this is the default mode of many data servers). Repeatable Read: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified and committed by another transaction in the meantime. Serializable: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified, deleted, or created and committed by another transaction in the meantime. |
| Context | Execution context of the query. If "Execution context" is left, the command will be executed in the execution context chosen on launching or on the step. |
| Schema | Logical schema for execution. The logical schema, linked to the context, allows the physical execution schema to be defined. |
| Transaction | You can execute commands on several concurrent transactions (numbered from 0 to 9) or work off-transaction by choosing the option Autocommit. |
| Commit | If your command is being executed in a transaction (numbered 0 to 9), you can decide to continue or to commit the current transaction according to the following modes:
No Commit: The transaction is not committed. In this case, it can be committed in a later command. If a session ends normally, all transactions are committed by default. Commit: The transaction is committed. Commit 1000 rows: Oracle Data Integrator commits every 1000 records processed. This choice is only possible on a loading procedure command, that is, one containing a source command returning a result set and a destination command that carries out inserts. |
| Command | Text of the command expressed in a native language or in a standard language (such as SQL, PL/SQL, Transact-SQL, shell, and so forth). You can use the Expression Editor, accessible through the button to the right of the text.
Warning: If the command is made of random characters, then the procedure is encrypted. For more details about encryption and decryption, see "Encrypting and Decrypting Procedures" in Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator. |
| Properties | Description |
|---|---|
| Always Execute | If checked, the Task executes under any conditions. If not checked, the Task executes under the conditions set in the Options tab.
Note: Only Boolean Knowledge Module options are shown in the Options tab. |
| Is Executed | If checked, the Task executes under this condition individually. |
| Name | Name of the boolean option. |
| Description | Description of the boolean option. |
| Name | Description |
|---|---|
| Expand All | Expands all the task groups. |
| Collapse All | Collapses all the task groups in task hierarchy. |
| Add | Adds a new task. |
| Delete | Deletes the selected task. |
| Up | Moves the selected task up in the list. |
| Down | Moves the selected task down in the list. |
| Move task to top | Moves the selected task to the top. |
| Move task to bottom | Moves the selected task to the bottom. |
| Select Columns | Adds a task property to the task table. |
A KM can be parameterized when executed with options. The Options tab allows all options to be displayed, as well as their default values. The options values specified on this tab are only used during execution of the KM.
| Properties | Description |
|---|---|
| Name | Name of the option. It is a common practice to use upper-case names with underscores ("_") such as DETECTION_STRATEGY. |
| Type | Datatype of the option.
Possible values are Boolean, Choice, Text, or Value. Boolean options can be true or false. A choice option allows you to choose the option value from a pre-defined list of option values. These values can be edited using the Edit Choice Dialog. Value options can hold an alphanumeric value up to 250 characters, and Text options can hold an alphanumeric value of unlimited length and are parsed for variable and sequence references. |
| Default Value | Value of the option that is set by default. |
| Condition Expression | Click the condition expression cell against a particular option to enter or edit the groovy script, which will determine if a Knowledge Module option should be disabled, enabled, shown, or hidden. |
| Description | Text that will be shown in the Oracle Data Integrator UI next to the option. Text should be short to be readable in a single line inside a table. |
| Name | Description |
|---|---|
| Expand All | Expands all the option groups. |
| Collapse All | Collapses all the option groups. |
| Add | Adds a new option or option group. |
| Delete | Deletes the selected option or option group. |
| Move Up | Moves the selected option up within the option group or an entire option group up in the list of option groups. If an option is not within an option group, it will be moved up in the list of ungrouped options. |
| Move Down | Moves the selected option down within the option group or an entire option group down in the list of option groups. If an option is not within an option group, it will be moved down in the list of ungrouped options. |
| Move Out | Moves an option out of an option group.
Note: This option is disabled if an ungrouped option or an option group is selected. |
| Move In | Moves an ungrouped option into an option group.
Note: This option is disabled if an option within a group or an option group is selected. |
| Move to top | Moves the selected option to the top of the option group or an entire option group to the top of the list of option groups. If an option is not within an option group, it will be moved to the top of the list of ungrouped options. |
| Move to bottom | Moves the selected option to the bottom of the option group or an entire option group to the bottom of the list of option groups. If an option is not within an option group, it will be moved to the bottom of the list of ungrouped options. |
| Select Column | Selects or deselects the columns to be displayed in the table. |
Use to view and manage versions of your Knowledge Module.
A version is a backup copy of an object and is checked in at a given time and may be restored later. Versions are saved in the Master Repository.
The version management system allows flags on developed objects (such as projects, models, and so forth) to be set automatically to indicate their status (such as new or modified). The version management system also allows these objects to be backed up as stable checkpoints, and later restored from these checkpoints. These checkpoints are created for individual objects in the form of versions.
Creation and Update Information
| Properties | Description |
|---|---|
| Created by | User who created the knowledge module. |
| Created on | Date and time when the object was created. |
| Updated by | User who updated the knowledge module. |
| Updated on | Date and time when the object was updated. |
| Properties | Description |
|---|---|
| Internal ID | Internal ID that enables object identification.
|
| Build Number | Internal build number to track the release. |
| Customization Status | Can take the following values:
|
| Properties | Description |
|---|---|
| Current Version: N/A (created) | This table lists the version number, the creation date of the version, the name of the user who created the version, and a version description.
You can perform the following actions by clicking the corresponding button:
See "Working with Version" for more information. |
Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator
Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator
Oracle Fusion Middleware Developing Knowledge Modules with Oracle Data Integrator
Oracle Fusion Middleware Integrating Big Data with Oracle Data Integrator