Steps described in this article are only applicable to earlier versions of ODE. Use the latest version for better ODE experience.

Once you have built a desired Vault Structure (Hubs, Links and Satellites), as well as defined the Data Source, you are ready to hook them together.

There are 2 places where this needs to occur – Source Columns need to be related to the desired Satellites.

One source can be hooked up to multiple Satellites, although all of the Satellites, coming from a single source, need to report to the same Hub or Vault.

For example, the Customer Table, coming from SAPB1, might be broken up into a Customer_Details and a Customer_Address Satellite, both of which report up to the Customer Hub.

This is simply a matter of hooking each column, from the source, to the desired satellite.

In addition, the controlling Object (Hub or Link) needs to know which columns, in the source, are governing the Hub or Link Keys.

For each Hub in the structure (multiples if the Owner is a Link), the Driving key columns need to be hooked up to the Hub Key Columns correctly.

At the time of writing, ODE cannot process a Link, which is related to the same Hub more than once (Same As or Hierarchical Link).

These need to be built through a Master Hub, which can have multiple Links to the same Hub.

ODE Config Logical Model - Hookup Focus

To Hook the Columns up to the Satellites:

{Configuration Database}. [dbo].[dv_satellite_column_insert]

Parameters:

  • @satellite_key – the Key of the owning Satellite
  • @column_key – the Key of the Column
  • @release_number –  If you want the new Hub to be part of a specific release, provide the Release Number. If not, Zero.

 

To Hook the Key Column(s) up to the Hub(s):

Note that if the Hub has a Multi Part key, this procedure will be run multiple times, once for each column.

{Configuration Database}. [dbo].[dv_hub_column_insert]

Parameters:

  • @hub_key_column_key – the key of the Hub_Key to which the column needs to be related
  • @column_key – the Key of the Column
  • @release_number –  If you want the new Hub to be part of a specific release, provide the Release Number. If not, Zero.

Example:

EXECUTE [dbo].[dv_hub_column_insert]
 @hub_key_column_key = 123
,@column_key = 456
,@release_number = 2015001
EXECUTE [dbo].[dv_satellite_column_insert]
 @satellite_key = 321
,@column_key = 654
,@release_number = 2015001