Package | Description |
---|---|
oracle.odi.interfaces.interactive |
Provides interfaces for interactive handling of Oracle Data Integrator interfaces.
|
oracle.odi.interfaces.interactive.support |
This package and its sub-packages provide the implementations for interactive handling of Oracle Data Integrator interfaces.
|
oracle.odi.interfaces.interactive.support.issues.autofixmanager |
Contains classes which handles the auto-fixing of Oracle Data Integrator interface sub-component issues.
|
Modifier and Type | Interface and Description |
---|---|
interface |
IInteractiveInterfaceHelperWithActions
Deprecated.
this class/method belongs to 11g SDK and is deprecated in 12c release.
Any class implementing this interface is a helper to manipulate Odi interfaces in an interactive way.
|
Modifier and Type | Method and Description |
---|---|
void |
IAutoFixManager.autoFix(IInterfaceAction pOriginalAction,
IImpacts pOriginalImpacts,
IInterfaceActionListener pInterfaceActionListener,
IInterfaceUndoListener pInterfaceUndoListener,
IInteractiveInterfaceHelper pInterfaceHelper)
Deprecated.
This method will execute automatic fixes for ODI interface objects.
|
Modifier and Type | Class and Description |
---|---|
class |
InteractiveInterfaceHelperWithActions
Deprecated.
this class/method belongs to 11g SDK and is deprecated in 12c release.
InterfaceInterfaceHelperWithActions is a helper class that works in conjunction with
the interactive interface action classes found in package
oracle.odi.interfaces.interactive.support.actions
in order to create or modify the ODI interface objects that define the execution behavior of the interface.
The objects that can be created or modified include sources, targets, mappings,
filter, joins, and other clauses that define an ETL operation.
General Concepts: The general usage of the interactive interface helper and action classes is as follows: First create instance of this interface helper class. Then create an action class by calling it's constructor. Then call this helper's performAction method
with a reference to the action class as one of the calling parameters.
Performing the action: Though the action classes themselves have a performAction method, it is for internal
use only. The creation or modification action should be performed using the performAction
method in this helper class. Here is an example of creating a join object between two sources:
InteractiveInterfaceHelperWithActions interactiveHelper = new InteractiveInterfaceHelperWithActions(odiInterface, myOdiInstance, myOdiInstance.getTransactionalEntityManager(), new SourceSetComputerEraser(odiInterface), new SourceSetCreatorNew(), new SourceSetNameProviderBasicIncrement(), new MappingPersistencePolicyDefault());
Expression Strings: Many of the action class constructors require an expression string as a calling parameter. The expression strings may refer to objects that can be used in the interface, such as source table columns, variables, sequences, etc. When referring to source table columns in an expression string, the source table alias must be used. For example, if two join sources EMP and DEPT have aliases "EMP_ALIAS" and "DEPT_ALIAS", then the passed-in SQL join condition string might be "EMP_ALIAS.DEPTNO = DEPT_ALIAS.DEPTNO". A reliable way to create the join condition string is to create an Expression
object by calling ExpressionStringBuilder class methods, then call method
getAsString on the resultant Expression object. Here is an example
of creating the expression string "<mySrcDataStore1_alias>.DEPT_ID = <mySrcDataStore2_alias>.DEPT_ID":
ExpressionStringBuilder stringBuilder = new ExpressionStringBuilder(getLanguageProvider().getSnpsLanguageByTechnologyName(mySourceDataStore1.getModel().getTechnology().getInternalName()));
The advantage of creating it this way is that the actual string values of the data store aliases and columns do not need to be known when the code is written, and the code will remain accurate even if the alias names are later changed. Reverse Actions: Most action classes will call an undo listener to add a reverse or undo action that can be performed to undo the action itself. Auto-fix manager: This helper can contain an instance of the <@link IAutoFixManager> interface. Depending on the functionality of the particular auto-fix manager implementation, it may cause problems or issues to be automatically fixed after an action is performed. Source Set Computer/Creator: This helper also contains a ISourceSetComputer and a ISourceSetCreator
interface instance object. Each interface contains a set of SourceSet objects, which
group the executable objects (e.g. joins and mappings) according to their execution location.
The source sets must be created according to some strategy, after the interface objects
have all been added. For the SDK, the source set computer and creator do this work. The
source set computer determines the strategy for creating source sets based on the interface
objects, settings, and KMs. The source set creator actually creates each source set, and
is called by the source set computer. A common source set computer implementation that
can be used for many generic cases is SourceSetComputerRetainer . The source set
computer and creator implementation instance can be passed to the helper in it's constructor.
Retrieving the created object: When an action is performed that creates a new object, for example InterfaceActionAddFilter ,
then it may be useful at some point to retrieve a reference to the newly created object or
objects. The <@link IImpacts> interface instance that is returned from the performAction
call can be used to retrieve the object. Here is a sample method that could be used to retrieve
the objects.
protected <T extends IInterfaceSubComponent> T findAddedObject(IImpacts impacts, Class<T> clazz) {
for (InterfaceObjectModification modif : impacts.getModifications())
if (clazz.isInstance(modif.getModifiedObject()) && modif.getModification().equals(InterfaceObjectModification.Modification.OBJECT_ADDED))
return (T) modif.getModifiedObject();
System.out.println("Could not find new object of type " + clazz.getName());
return null;
}
The key to this method is the use of the getModifiedObject() in the IImpacts interface.
|
Modifier and Type | Method and Description |
---|---|
void |
AutoFixManagerComposer.autoFix(IInterfaceAction pOriginalAction,
IImpacts pOriginalImpacts,
IInterfaceActionListener pInterfaceActionListener,
IInterfaceUndoListener pInterfaceUndoListener,
IInteractiveInterfaceHelper pInterfaceHelper)
Deprecated.
|
void |
AutoFixManagerEnableText.autoFix(IInterfaceAction pOriginalAction,
IImpacts pOriginalImpacts,
IInterfaceActionListener pInterfaceActionListener,
IInterfaceUndoListener pInterfaceUndoListener,
IInteractiveInterfaceHelper pInterfaceHelper)
Deprecated.
|
void |
AutoFixManagerLazy.autoFix(IInterfaceAction pOriginalAction,
IImpacts pOriginalImpacts,
IInterfaceActionListener pInterfaceActionListener,
IInterfaceUndoListener pInterfaceUndoListener,
IInteractiveInterfaceHelper pInterfaceHelper)
Deprecated.
Dummy implementation.
|
void |
AutoFixManagerNewObjects.autoFix(IInterfaceAction pOriginalAction,
IImpacts impacts,
IInterfaceActionListener pInterfaceActionListener,
IInterfaceUndoListener pInterfaceUndoListener,
IInteractiveInterfaceHelper pInterfaceHelper)
Deprecated.
Fixes WARNING, CRITICAL, or FATAL issues for the sub-component that has been added and also for the target columns of the target data store if the added sub-component is a source data store.
|