New Features in Oracle Data Integrator 12c (12.1.2)
Declarative
Flow-Based User Interface
The new declarative
flow-based user interface combines the simplicity and ease-of-use of the
declarative approach with the flexibility and extensibility of configurable
flows. Mappings (the successor of the Interface concept in Oracle Data
Integrator 11g)
connect sources to targets through a flow of components such as Join, Filter,
Aggregate, Set, Split, and so on.
Reusable Mappings can be
used to encapsulate flow sections that can then be reused in multiple mappings.
A reusable mapping can have input and output signatures to connect to an
enclosing flow; it can also contain sources and targets that are encapsulated
inside the reusable mapping.
A mapping can now load
multiple targets as part of a single flow. The order of target loading can be
specified, and the Split component can be optionally used to route rows into
different targets, based on one or several conditions.
Mappings, Packages,
Procedures, and Scenarios can now be debugged in a step-by-step debugger. Users
can manually traverse task execution within these objects and set breakpoints
to interrupt execution at pre-defined locations. Values of variables can be
introspected and changed during a debugging session, and data of underlying
sources and targets can be queried, including the content of uncommitted
transactions.
The runtime execution
has been improved to enhance performance. Various changes have been made to
reduce overhead of session execution, including the introduction of blueprints,
which are cached execution plans for sessions. Performance is improved by
loading sources in parallel into the staging area. Parallelism of loads can be
customized in the physical view of a map. Users also have the option to use
unique names for temporary database objects, allowing parallel execution of the
same mapping.
The integration of
Oracle GoldenGate as a source for the Change Data Capture (CDC) framework has
been improved in the following areas:
·
Oracle GoldenGate source and
target systems are now configured as data servers in Topology. Extract and
replicate processes are represented by physical and logical schemas. This
representation in Topology allows separate configuration of multiple contexts,
following the general context philosophy.
·
Most Oracle GoldenGate
parameters can now be added to extract and replicate processes in the physical
schema configuration. The UI provides support for selecting parameters from
lists. This minimizes the need for the modification of Oracle GoldenGate
parameter files after generation.
·
A single mapping can now be
used for journalized CDC load and bulk load of a target. This is enabled by the
Oracle GoldenGate JKM using the source model as opposed to the Oracle
GoldenGate replication target, as well as configuration of journalizing in
mapping as part of a deployment specification. Multiple deployment
specifications can be used in a single mapping for journalized load and bulk
load.
·
Oracle GoldenGate parameter
files can now be automatically deployed and started to source and target Oracle
GoldenGate instances through the JAgent technology.
Oracle Data Integrator
standalone agents are now managed through the WebLogic Management Framework.
This has the following advantages:
·
UI-driven configuration through
Configuration Wizard
·
Multiple configurations can be
maintained in separate domains
·
Node Manager can be used to
control and automatically restart agents
Oracle Data Integrator
can now use the authorization model in Oracle Platform Security Services (OPSS)
to control access to resources. Enterprise roles can be mapped into Oracle Data
Integrator roles to authorize enterprise users across different tools.
The following XML Schema
constructs are now supported:
·
list and union - List or
union-based elements are mapped into VARCHAR columns.
·
substitutionGroup - Elements
based on substitution groups create a table each for all types of the
substitution group.
·
Mixed content - Elements with
mixed content map into a VARCHAR column that contains text and markup content
of the element.
·
Annotation - Content of XML
schema annotations are stored in the table metadata.
Oracle Warehouse Builder
(OWB) jobs can now be executed in Oracle Data Integrator through the
OdiStartOwbJob
tool.
The OWB repository is configured as a data server in Topology. All the details
of the OWB job execution are displayed as a session in the Operator tree. For
more information about this feature, see "OdiStartOwbJob".
Master and Work
Repositories now use unique IDs following the GUID convention. This avoids
collisions during import of artifacts and allows for easier management and
consolidation of multiple repositories in an organization.
No comments:
Post a Comment