module owb targets

All information Copyright Bayon Technologies, Inc.

OWB Targets

Targets (OWF/File/Schema), CIF, permissions, etc


Targets are:

Physical Implementations ofObjects, Mappings, DataProcess FlowsFile Load Mappings

Where the actual “work” occurs “Controlled” by RUNTIME REPOSITORY


Targets Overview


Target Types

Not Oracle terminologyTarget SchemaWorkflow TargetFile System Target


Target Types


Corporate Information Factory

Overall Architecture Put forth by Inmon/Imhoff Three Tiers (really)

StageDWMarts


Targets and Locations

Targets are PHYSICAL locations for OWB physical objects

Three layers instead of two (log/phys)Logical Module (Design)Logical Location (Design)Physical Location (Runtime)


DW_MOD_LOC2-- Oracle 9i

DW_MODORACLE MODULE

DW_MOD_LOC1-- Oracle 10g

PHYSICALLOCATION

LOGICALLOCATION

LOGICALMODULE

RUNTIMEDESIGN

DW_TGT2

DW_TGT1 OWBRT

db10g.host.com

DW_TGT2

DW_TGT1 OWBRT

db9i.host.com


Connectors

Inter-module access Built at DEPLOYMENT Usually

Schema resolutionDBLink


Connectors


Schema Based / Security

Most target schemas are in the same database (3 tier split for logical reasons)

Most connectors are SCHEMA prefixes Connectors are faster and more capable than

DBLinks Security must be setup outside of OWB for

select/execute permissions for TGT to TGT interaction


Questions

In addition to being just a ptr, what is the one piece of defined information in the LOGICAL location?

What registration information will be required for the following targets?Target SchemaWorkflow TargetFile System Target

module owb targets

Technology