page249
336
Entitled Data Sharing
You will extend the newly created share
share_poc
to include entitled objects that
cannot pass straight through to your share. The entitlement engine curates the data
content of a shared object acting as the filter engine.
Designing a Filter Engine
As you have seen, sharing unentitled objects is relatively simple. Sharing entitled objects,
that is, a subset of data contained within an object, is not simple.
Creating a limited scope number of bespoke objects for an individual client is easy.
When the limited scope changes, you will find yourself overwhelmed with demand.
Therefore, adopting a pattern-based approach to generating bespoke objects is the only
viable way forward.
The first decision is to determine where to build your entitlement engine, and for the
purposes of this example, you will reuse the
tpc_owner
schema. For a real-
world implementation, you may choose to develop your entitlement engine within a
separate schema.
Filter Engine Requirements
For simplicity’s sake you will reuse the table
base_customer_order
from a previous
chapter as the data source for generating customer-specific filtered data.
Table 9-1 shows the table
base_customer_order
definition.
Table 9-1.
base_customer_order Table Definition
Attribute Name
Datatype
customer_key
NUMBER (38,0)
customer_name
VARCHAR(25)
order_key
NUMBER (38,0)
order_date
DATE
nation_name
VARCHAR(25)
region_name
VARCHAR(25)
Chapter 9
Client expeCtations