notes/domino rel-7 und nsfdb2 - neue potenziale bei der integration von dokumenten und daten

Notes/Domino Rel-7 und NSFDB2 - Neue Potenziale bei der Integration von Dokumenten und Daten

Notes/Domino Rel-7 und NSFDB2 - Neue Potenziale bei der Integration von Dokumenten und Daten

Dr. Ludwig NastanskyProfessor of Business Computing

Groupware Competence CenterUniversity of Paderborn, Germany

Dr. Ludwig NastanskyProfessor of Business Computing

Groupware Competence CenterUniversity of Paderborn, Germany

ProfilProfil

Prof. Dr. Ludwig Nastansky Professor of Business Information Systems head of Groupware Competence Center in N/D research & business since N/D Rel-1 founder of several university spin-offs co-founder of German Notes User Group founder & chairman supervisory board PAVONE AG

Prof. Dr. Ludwig Nastansky Professor of Business Information Systems head of Groupware Competence Center in N/D research & business since N/D Rel-1 founder of several university spin-offs co-founder of German Notes User Group founder & chairman supervisory board PAVONE AG

AgendaAgenda 1 Einführung 2 Domino Access Views (DAV)

Szenarios Technologie, Tips N/D DB2 Paradigma Tabellenschnittstelle live demo

3 Query Views Szenarios Technologie, Tips Paradigma „federated data“ live demos

4 Zusammenfassung

1 Einführung 2 Domino Access Views (DAV)

Szenarios Technologie, Tips N/D DB2 Paradigma Tabellenschnittstelle live demo

3 Query Views Szenarios Technologie, Tips Paradigma „federated data“ live demos

4 Zusammenfassung

1 Introduction1 Introduction

Focus on DAV & Query Views in NSFDB2Goals

put N/D DB2 integration in right context show innovative & efficient N/D DB2 integration

options envision new approaches for N/D & DB2 application

development start thinking about required changes in infrastructure take home tips for first implementations

No NSFDB2 basics will be coveredPresentation mainly based on beta 2 code

Focus on DAV & Query Views in NSFDB2Goals

put N/D DB2 integration in right context show innovative & efficient N/D DB2 integration

options envision new approaches for N/D & DB2 application

development start thinking about required changes in infrastructure take home tips for first implementations

No NSFDB2 basics will be coveredPresentation mainly based on beta 2 code

Notes/Domino & DB2 Integration, finally… ?Notes/Domino & DB2 Integration, finally… ?

New RDB-functionalities provided by DAV & Query Views RDB functionalities in N/D have been an issue since N/D

Rel-2 Many successful approaches for N/D RDB connectivity

have appeared: DECS, LEI, SAP connector, … NSFDB2 is the smoothest and most radical integration

ever Besides, that the DB2 guys will finally admit that N/D is

based on a real DB-engine … … the core issues are unchanged

N/D RDB integration is not (only) about technology but (much more) about application domains, IT-strategies,

top-down system architectures, functionality concepts

New RDB-functionalities provided by DAV & Query Views RDB functionalities in N/D have been an issue since N/D

Rel-2 Many successful approaches for N/D RDB connectivity

have appeared: DECS, LEI, SAP connector, … NSFDB2 is the smoothest and most radical integration

ever Besides, that the DB2 guys will finally admit that N/D is

based on a real DB-engine … … the core issues are unchanged

N/D RDB integration is not (only) about technology but (much more) about application domains, IT-strategies,

top-down system architectures, functionality concepts

Documents vs. Relational DataDocuments vs. Relational Data

strategic orientation & communication centric

knowledge & information management

tool paradigm on objects – code re-use

compound documents, semi-structured, very flexible data types

multimedia, links, embedded methods decentralized, buttom-up, user

workplace & collaboration centric replication, information sharing,

robust distribution, redundancy, message objects

support of mobile, nomadic and disconnected user workplace

strategic orientation & communication centric

knowledge & information management

tool paradigm on objects – code re-use

compound documents, semi-structured, very flexible data types

multimedia, links, embedded methods decentralized, buttom-up, user

workplace & collaboration centric replication, information sharing,

robust distribution, redundancy, message objects

support of mobile, nomadic and disconnected user workplace

operational orientation & data centric

transaction processing & high volume

automation paradigm on data – code efficiency

records, tables, structured data, restricted flexibility, strict formats

transactions, dynamic central organization, top-down,

system centric access coordination, integrity,

redundancy elimination, 2-phase commit, ACID

static office-based and server-connected workplace

operational orientation & data centric

transaction processing & high volume

automation paradigm on data – code efficiency

records, tables, structured data, restricted flexibility, strict formats

transactions, dynamic central organization, top-down,

system centric access coordination, integrity,

redundancy elimination, 2-phase commit, ACID

static office-based and server-connected workplace

N/D worldN/D world DB2/RDB worldDB2/RDB world

Integration, Cooperation, FederationIntegration, Cooperation, Federation Challenge: bring together the best of the two worlds

as much as needed and as much as makes sense from a business value perspective

Position: N/D RDB/DB2 integration is just one instance of the innumerable system integration tasks taking place currently

The integration is between equal partners stay cool, no religion involved, don't demonize

Purpose integration of data across system boundaries cooperation of separate applications federation of N/D applications with DB2-data and, vice versa, DB2

applications with N/D data NSFDB2 brings RDB/SQL functionalities to N/D – let us start with

one principal N/D-modelling challenge using a typical scenario

Challenge: bring together the best of the two worlds as much as needed and as much as makes sense from a business

value perspective Position: N/D RDB/DB2 integration is just one instance of the

innumerable system integration tasks taking place currently The integration is between equal partners

stay cool, no religion involved, don't demonize Purpose

integration of data across system boundaries cooperation of separate applications federation of N/D applications with DB2-data and, vice versa, DB2

applications with N/D data NSFDB2 brings RDB/SQL functionalities to N/D – let us start with

one principal N/D-modelling challenge using a typical scenario

Scenario 1 - Model Employee–Room RelationScenario 1 - Model Employee–Room Relation

Solution in N/D is clumsy

We need to hard-code relational dependancy by duplicating data in documents and thus creating redundancy

- Option #1: Lookup "LastName" in "Employees" view and save in Room-form

- Option #2: Lookup "Room" in "Room list" view and save in Employee-form

- [Option #3: Enforce consistent user entry in related documents]

Solution in N/D is clumsy

We need to hard-code relational dependancy by duplicating data in documents and thus creating redundancy

- Option #1: Lookup "LastName" in "Employees" view and save in Room-form

- Option #2: Lookup "Room" in "Room list" view and save in Employee-form

- [Option #3: Enforce consistent user entry in related documents]

#1#1 #2#2

Start: two

independent

lists

Start: two

independent

lists

Goal: model

Employee-Room

relation

Goal: model

Employee-Room

relation

N/D challenge: Model Employee–Room Relation N/D challenge: Model Employee–Room Relation

Problem: View "Employee in room" cannot be generated without duplicating

"Room"-field and "LastName"-field in "Employee"-document and "Room"-document respectively

reason: @LookUp not allowed in view columns Synchronization has to be modeled Modelling the synchronization is possible, but clumsy, e.g.

use scheduled agents to collect & update changes set up (very) disciplined user entry infrastructure enforcing

consistent update over involved document collection Avoiding redundancy of field entries would help considerably Solution with new options of NSFDB2: Data duplication is not

necessary using Domino Access Views (DAV) and Query Views

Problem: View "Employee in room" cannot be generated without duplicating

"Room"-field and "LastName"-field in "Employee"-document and "Room"-document respectively

reason: @LookUp not allowed in view columns Synchronization has to be modeled Modelling the synchronization is possible, but clumsy, e.g.

use scheduled agents to collect & update changes set up (very) disciplined user entry infrastructure enforcing

consistent update over involved document collection Avoiding redundancy of field entries would help considerably Solution with new options of NSFDB2: Data duplication is not

necessary using Domino Access Views (DAV) and Query Views

DAV vs. Query ViewsDAV vs. Query Views

DB2NSF

DB2

update, insert, delete

Domino data flow

DAV related data flow

Control

Domino

NSFNote Table

ApplicationsSQL

redundantlystore

Access Views

Access ViewsDB2View

Access Views

Access ViewsDB2

Table

DAV

Access Views

Access Views

DB2 DataTable

read

read

read

UDF

DB2 data flow

Query

Views

Query

ViewsQuery

Views

Query

ViewsN/D

View

N/D

ViewQueryView

AgendaAgenda 1 Introduction2 Domino Access Views (DAV)

scenario technology, tips live demo

3 Query Views scenarios technology, tips federated data paradigm live demos

4 Summary

1 Introduction2 Domino Access Views (DAV)



4 Summary

DAV - OverviewDAV - Overview Redundantly store N/D data in DB2 table DB2 view that corresponds to the table is used for SQL

operations DAV is not a N/D UI element, i.e. not N/D standard view DAV is tabular cross-reference entity for N/DDB2 data

exchange; N/D-view analogue, but not accessible in Notes client Expose N/D data to

SQL applications JDBC, ODBC DB2 tools and applications relational reporting tools (Crystal Reports etc.) Query Views

No DECS, LEI, connectors needed

Redundantly store N/D data in DB2 table DB2 view that corresponds to the table is used for SQL

operations DAV is not a N/D UI element, i.e. not N/D standard view DAV is tabular cross-reference entity for N/DDB2 data

exchange; N/D-view analogue, but not accessible in Notes client Expose N/D data to

SQL applications JDBC, ODBC DB2 tools and applications relational reporting tools (Crystal Reports etc.) Query Views

No DECS, LEI, connectors needed

DAV ArchitectureDAV Architecture

DB2



Domino data flow

Control

Domino Designer

Domino

NSFNote Table

Access Views

Access ViewsDB2View Applications

SQL

Access Views

Access ViewsDB2

Table

DAV Design Document

design

define

stored inUDF

read

redundantlystore

DAV

DB2NSF

DAV Data: N/DDB2 InteractionDAV Data: N/DDB2 Interaction

DB2



Domino data flow

Control

Domino Designer

Domino

NSFNote Table

Access Views

Access Views Applications

SQL

Access Views

Access Views

DAV Design Document

design

define

stored inUDF

read

redundantlystore

DAV

DB2NSF

form basedselection

user basedselection

DB2 Table

DB2 View

DAV – Field DefinitionDAV – Field Definition

Field 6

DAV DesignDocument

Field 5

Field 4

Field 3

Field 2

Field 1 Fields are elementsof forms

Fields are itemsin notes

New fields, that do notexist in N/D databaseyet

etc. …

DAV – Architecture SummaryDAV – Architecture Summary Using SQL, you can

read N/D data with security semantics enforced from an SQL perspective, this adds "row level security" to

DB2 data insert, update, delete with full N/D semantics

DB2 handles security for read operations (fast) DB2 Access for Lotus Domino (aka UDF server) handles

N/D security on insert, update, delete DAV calls UDF server Domino handles replication conflicts, document locking etc. Domino handles ACL, reader fields etc. user mapping required for security

(Domino Administrator)

Using SQL, you can read N/D data with security semantics enforced from an SQL perspective, this adds "row level security" to

DB2 data insert, update, delete with full N/D semantics

DB2 handles security for read operations (fast) DB2 Access for Lotus Domino (aka UDF server) handles

N/D security on insert, update, delete DAV calls UDF server Domino handles replication conflicts, document locking etc. Domino handles ACL, reader fields etc. user mapping required for security

(Domino Administrator)

Scenario 2: Integration #1Scenario 2: Integration #1 Application and data integration demands for N/D and

DB2, e. g. analysis using MIS reporting using Crystal Reports HR uses existing DB2 application salesforce uses mobile N/D application salesforce orders are processed by DB2 application customer uses J2EE application with DB2 backend to file

orders Challenge

integration of applications synchronization of data

Application and data integration demands for N/D and DB2, e. g.

analysis using MIS reporting using Crystal Reports HR uses existing DB2 application salesforce uses mobile N/D application salesforce orders are processed by DB2 application customer uses J2EE application with DB2 backend to file

orders Challenge

integration of applications synchronization of data

Scenario 2: Integration #2Scenario 2: Integration #2 Solution: integration via DAV

make N/D document based data available for corporate SQL applications via DAV:

expose N/D data to DB2 for read and write populate N/D documents with DB2 based data from SQL

applications via DAV: make DB2 data available for N/D documents make DB2 data available in flexible N/D view context

Benefits enrich N/D environment with DB2 based application options enrich DB2 environment with N/D based application options

Solution: integration via DAV make N/D document based data available for corporate SQL

applications via DAV: expose N/D data to DB2 for read and write

populate N/D documents with DB2 based data from SQL applications via DAV:

make DB2 data available for N/D documents make DB2 data available in flexible N/D view context

Benefits enrich N/D environment with DB2 based application options enrich DB2 environment with N/D based application options

Scenario 2: Mobile SalesforceScenario 2: Mobile Salesforce

Salesforce uses mobile N/D applicationOrders are replicated into central NSFDB2DB2 application works on data exposed via DAV

N/D adds offline functionality to DB2 via replication Transactions are processed in DB2

Salesforce replicates transaction status back to mobile device

Salesforce uses mobile N/D applicationOrders are replicated into central NSFDB2DB2 application works on data exposed via DAV

N/D adds offline functionality to DB2 via replication Transactions are processed in DB2

Salesforce replicates transaction status back to mobile device

Demo 1: DAV Design, Use & RemarksDemo 1: DAV Design, Use & Remarks

Design a Domino Access ViewCreate and populate DAVLook at created elements in DB2Modify data from SQL application

Design a Domino Access ViewCreate and populate DAVLook at created elements in DB2Modify data from SQL application

Updated by DB2 application

DAV Design - #1DAV Design - #1

Creation in DB2 via Domino DesignerNew shared resourceDatabase has to be in NSFDB2 formatDefine view selection based on 1 or more formsDefine one form to calculate fields

for insert and update operations

Creation in DB2 via Domino DesignerNew shared resourceDatabase has to be in NSFDB2 formatDefine view selection based on 1 or more formsDefine one form to calculate fields

for insert and update operations


Define advanced properties include UNID to be able to open documents in Query

views modified time

Define advanced properties include UNID to be able to open documents in Query

views modified time


Select formSelect N/D fieldsModify selected field definitions

DB2 data type (automatic default mapping) modify column length if you expect many values

Select formSelect N/D fieldsModify selected field definitions

DB2 data type (automatic default mapping) modify column length if you expect many values


Create DAV in DB2Populate DAV

asynchronous background task DAVPOP can take a long time in large databases

Create DAV in DB2Populate DAV

asynchronous background task DAVPOP can take a long time in large databases

DAV UseDAV Use

DAV Remarks - #1DAV Remarks - #1

Structure clash between N/D flexibilityand restricted DB2 tables

DB2 requires fixed column/field length especially N/D text fields have to be considered do not modify truncated data

Think about multi value handlingList fields

reduce DB2 column length sum length for multi value fields use alias if possible

Structure clash between N/D flexibilityand restricted DB2 tables

DB2 requires fixed column/field length especially N/D text fields have to be considered do not modify truncated data

Think about multi value handlingList fields

reduce DB2 column length sum length for multi value fields use alias if possible

DAV Remarks - #2DAV Remarks - #2

UDF server neededDesign document replicates in NSF, but is not

visible locallyDoes not support formula, rich text and

rich text light data typesInclude only fields you really need

UDF server neededDesign document replicates in NSF, but is not

visible locallyDoes not support formula, rich text and

rich text light data typesInclude only fields you really need

DAV SummaryDAV Summary

Domino Designer as a development tool for DB2Expose N/D data to SQL applicationsMake N/D functionalities easily available for DB2

applications, examples: N/D semantics offer additional value to SQL

applications ("row level security") enrich DB2 with disconnected options

Potential to lower cost for application integration with existing infrastructure

Domino Designer as a development tool for DB2Expose N/D data to SQL applicationsMake N/D functionalities easily available for DB2

applications, examples: N/D semantics offer additional value to SQL

applications ("row level security") enrich DB2 with disconnected options

Potential to lower cost for application integration with existing infrastructure

AgendaAgenda 1 Introduction 2 Domino Access Views (DAV)


3 Query Viewsscenarios technology, tips federated data paradigm live demos

4 Summary

1 Introduction 2 Domino Access Views (DAV)


3 Query Viewsscenarios technology, tips federated data paradigm live demos

4 Summary

Query Views - OverviewQuery Views - Overview

N/D views which are enabled for SQL queriesSQL queries are used in view selection formula

contextUsage examples

filter documents (dynamic view selection formula) add DB2 data to a N/D view use retrieved DB2 data in column formulas combine N/D data with external DB2 data

N/D views which are enabled for SQL queriesSQL queries are used in view selection formula

contextUsage examples

filter documents (dynamic view selection formula) add DB2 data to a N/D view use retrieved DB2 data in column formulas combine N/D data with external DB2 data

Query Views - DesignQuery Views - Design

DB2NSF

DB2Domino data flowControl

Domino

NSFNote Tableredundantly

store

Access Views

Access ViewsDB2View

Access Views

Access ViewsDB2

Table

DAV

Access Views

Access Views

DB2 DataTable

Query View Design

Documentdesign

stored in

Domino Designer

Query

Views

Query

ViewsQuery

Views

Query

ViewsN/D

View

N/D

ViewQueryView SQL Query

SQL Query

Query Views – Data FlowQuery Views – Data Flow

DB2NSF

DB2

Domino data flow


Control

Domino

NSFNote Tableredundantly

store

Access Views

Access ViewsDB2View

Access Views

Access ViewsDB2

Table

DAV

Access Views

Access Views

DB2 DataTable

read

read

UDF

DB2 data flow

Query

Views

Query

ViewsQuery

Views

Query

ViewsN/D

View

N/D

ViewQueryView

Query Views – Data Federation #1 Query Views – Data Federation #1 Rows can be populated by

N/D documents in the current database (via DAV only) DAV data in DB2 not in the current database DB2 data combinations between these via SQL JOIN

Thus Query Views can display data from current N/D database exposed by DAV other N/D databases exposed by DAV N/D documents exposed by DAV, with additional data via

SQL JOIN Native (non N/D originating) DB2 data

Keep this in mind during clicking rows

Rows can be populated by N/D documents in the current database (via DAV only) DAV data in DB2 not in the current database DB2 data combinations between these via SQL JOIN

Thus Query Views can display data from current N/D database exposed by DAV other N/D databases exposed by DAV N/D documents exposed by DAV, with additional data via

SQL JOIN Native (non N/D originating) DB2 data

Keep this in mind during clicking rows

Query Views – Data Federation #2Query Views – Data Federation #2

"Federated data" do not originate from current N/D database

A row can contain document values plus federated data

"normal" N/D field content has to be included in DAV has to be included in SQL selection

result of a column formula calculation DB2 data objects retrieved using SQL Query "double click" yields opening of document

"Federated data" do not originate from current N/D database

A row can contain document values plus federated data

"normal" N/D field content has to be included in DAV has to be included in SQL selection

result of a column formula calculation DB2 data objects retrieved using SQL Query "double click" yields opening of document

Query Views – Data Federation #3Query Views – Data Federation #3

A row can be defined by federated data only all values result from DB2 data objects "double click" on row makes no sense (in most

cases) and yields error message can be used for data consolidation from different NSF

files same application different application see "Scenario 5"

A row can be defined by federated data only all values result from DB2 data objects "double click" on row makes no sense (in most

cases) and yields error message can be used for data consolidation from different NSF

files same application different application see "Scenario 5"

Query Views – SQL Query RulesQuery Views – SQL Query Rules Query is defined in N/D formula language context Query supports standard SQL

SQL JOIN SQL UNION ORDER BY etc.

Queries that do not produce a result set are not allowed security mechanism prevents deletion/update from view

Query is defined in N/D formula language context Query supports standard SQL

SQL JOIN SQL UNION ORDER BY etc.

Queries that do not produce a result set are not allowed security mechanism prevents deletion/update from view

Query Views Are DynamicQuery Views Are Dynamic

No persistent view index involved efficient DB2 indexing is used queries can be user specific parameterized and personalized lookups are allowed to collect N/D data for query

construction

No persistent view index involved efficient DB2 indexing is used queries can be user specific parameterized and personalized lookups are allowed to collect N/D data for query

construction

Scenario 3 – Federated Data in ViewsScenario 3 – Federated Data in Views HR uses N/D to manage resource data Everyone can view employee name and phone number Only HR is allowed to view salary Security challenge

field encryption requires complex key management mechanisms such as "hide when" are not security features @DBLookup is not supported in column formulas

Solution store data in different database or document use Query Views and SQL JOIN to add federated data

HR uses N/D to manage resource data Everyone can view employee name and phone number Only HR is allowed to view salary Security challenge

field encryption requires complex key management mechanisms such as "hide when" are not security features @DBLookup is not supported in column formulas

Solution store data in different database or document use Query Views and SQL JOIN to add federated data

SQL JOINSQL JOIN

NSFDB2 EmpUSA.nsf

DAVEMPLOYEE

NSFDB2 Salary.nsf

DB2

DAVSALARY

EMPID,NAME,PHONE

EMPID,SALARY

Query View D1

NAME PHONE SALARY EMPID

Record Set 1

Record Set 2

Record Set n

Result Set of:“SELECT

A.NAME , A.PHONE , B.SALARY, A.EMPIDFROM

EMPUSA.EMPLOYEE A LEFT OUTER JOIN SALARY.SALARY B

ON A.EMPID = B.EMPID ORDER BY

A.NAME”

B

A

Demo 2Demo 2

Design a Query ViewJOIN data from other N/D database

Design a Query ViewJOIN data from other N/D database

Data from other database

RemarksRemarks

In most N/D scenarios, LEFT OUTER JOIN is most applicable

ensures all documents are displayed leaves column empty if federated data does not

match

Do not include multiple NoteID fields in result set

use specific selection instead of * wrong document might be opened

In most N/D scenarios, LEFT OUTER JOIN is most applicable

ensures all documents are displayed leaves column empty if federated data does not

match

Do not include multiple NoteID fields in result set

use specific selection instead of * wrong document might be opened

Scenario 4 – Dynamic SelectionScenario 4 – Dynamic Selection Workflow application Very large number of documents Users only need a small subset of documents Users want to select which documents to display Users want profile based personal selection settings Challenge (in N/D context)

@DBLookup in selection formula is not possible @UserName only works in private views bad performance due to large view index

Solution Query Views don't have a static view index Query statement(s) can be based on N/D dynamic formula

mechanism

Workflow application Very large number of documents Users only need a small subset of documents Users want to select which documents to display Users want profile based personal selection settings Challenge (in N/D context)

@DBLookup in selection formula is not possible @UserName only works in private views bad performance due to large view index

Solution Query Views don't have a static view index Query statement(s) can be based on N/D dynamic formula

mechanism

User selected data

Demo 3Demo 3

Design a Query ViewDynamic selection using @PromptDynamic user preference

Design a Query ViewDynamic selection using @PromptDynamic user preference

Query Views – SQL UNION applicationQuery Views – SQL UNION application

Dynamic formulas allow user specific aggregations

Aggregate documents from multiple N/D databases into "single point of access"

Returns federated data sets and documentsAllows for design of aggregated views

Dynamic formulas allow user specific aggregations

Aggregate documents from multiple N/D databases into "single point of access"

Returns federated data sets and documentsAllows for design of aggregated views

DB2

SQL UNION – Aggregated ViewsSQL UNION – Aggregated Views

SQL Query View

Notes Client

"Select A.Lastname, A.Firstname from Asia.Employee AUNIONSelect B.Lastname, B.Firstname from EMEA.Employee BUNIONSelect C.Lastname, C.Firstname from USA.Employee C"

NSFDB2 EMEA.nsf

DAVEmployee

NSFDB2 USA.nsf

DAVEmployee

NSFDB2 Asia.nsf

DAVEmployee

Scenario 5 – Aggregated ViewsScenario 5 – Aggregated Views User tasks are dispersed over multiple workflow

and project management applications User is active in multiple teamrooms Challenge

user has to open many databases to get his job done user is not up to date if new tasks appear

Solution a single view displays all documents a user needs from

multiple databases use Query View and SQL UNION to display federated

(virtual) "documents" retrieving originating (real) documents accessible needs

specific attention…

User tasks are dispersed over multiple workflowand project management applications

User is active in multiple teamrooms Challenge

user has to open many databases to get his job done user is not up to date if new tasks appear

Solution a single view displays all documents a user needs from

multiple databases use Query View and SQL UNION to display federated

(virtual) "documents" retrieving originating (real) documents accessible needs

specific attention…

Demo 4Demo 4

Design an aggregated viewDisplay external documents from multiple N/D

databases in Query ViewImplement access mechanism to open external

documents

Design an aggregated viewDisplay external documents from multiple N/D

databases in Query ViewImplement access mechanism to open external

documents

SQL UNION RemarksSQL UNION Remarks

Take in account that DAV field order defines column order of corresponding DB2 table

Number of fields has to be equal in both result sets

Data types have to be equal for merged columns

Take in account that DAV field order defines column order of corresponding DB2 table

Number of fields has to be equal in both result sets

Data types have to be equal for merged columns

UNIONUNION

VARCHAR VARCHAR DOUBLEDATEResult Set 1

VARCHAR VARCHAR DOUBLEDATEResult Set 2

Retrieve Documents From Federated Data - #1Retrieve Documents From Federated Data - #1

View includes rows with federated data not related to documents of current database which originate from (real) documents of external

databases Thus, document related N/D objects are not accessible

document collection document context caret note ID not available

View entry objects (rows) originating from external documents do exist

Use caret category to identify row context requires unique value in sort column

View includes rows with federated data not related to documents of current database which originate from (real) documents of external

databases Thus, document related N/D objects are not accessible

document collection document context caret note ID not available

View entry objects (rows) originating from external documents do exist

Use caret category to identify row context requires unique value in sort column

Retrieve Documents From Federated Data - #2Retrieve Documents From Federated Data - #2

Include necessary data to access external document to (hidden) designated column(s)

UNID / Note ID servername path or replica ID

Intercept QueryOpenDocument eventCreate backend document object that

represents external documentOpen external document in Notes Client UI

Include necessary data to access external document to (hidden) designated column(s)

UNID / Note ID servername path or replica ID

Intercept QueryOpenDocument eventCreate backend document object that

represents external documentOpen external document in Notes Client UI

Federated Data - RemarksFederated Data - Remarks

Does not work with categorized views (currently)

Dynamic resort has to be considered would change caret category

Wishlist for subsequent releases identifier for row selection context

(other than caret category) provide data of external document automatically

(servername, path or replica ID in addition to UNID) support response hierarchies

Does not work with categorized views (currently)

Dynamic resort has to be considered would change caret category

Wishlist for subsequent releases identifier for row selection context

(other than caret category) provide data of external document automatically

(servername, path or replica ID in addition to UNID) support response hierarchies

Enterprise Infrastructure RequirementsEnterprise Infrastructure Requirements

Prerequisites for aggregated viewsRequirements for applications

follow data structure policies use common set of application templates

Evaluate using DB2 as data store

Prerequisites for aggregated viewsRequirements for applications

follow data structure policies use common set of application templates

Evaluate using DB2 as data store

Query Views - PerformanceQuery Views - Performance Performance lower than NSF for "as is" usage Beta code – this is just guessing DB2 result sets

possible advantage for small result sets out of large document collections

no view index stored live SQL query on open or refresh

For certain scenarios Query Views could help to handle performance issues -

appropriate redesign has to be done Query Views do not work locally

Performance lower than NSF for "as is" usage Beta code – this is just guessing DB2 result sets

possible advantage for small result sets out of large document collections

no view index stored live SQL query on open or refresh

For certain scenarios Query Views could help to handle performance issues -

appropriate redesign has to be done Query Views do not work locally

Query View RemarksQuery View Remarks

DB2 user mapping necessary for securityDefault for maximum number of returned rows

is 500 at server levelFederated data not available locallyFederated data must be available in DAV or DB2

tableQuery views with federated data do not update

automatically query is not re-executed use SHIFT-F9 to update

DB2 user mapping necessary for securityDefault for maximum number of returned rows

is 500 at server levelFederated data not available locallyFederated data must be available in DAV or DB2

tableQuery views with federated data do not update

automatically query is not re-executed use SHIFT-F9 to update

Query View GuidelinesQuery View Guidelines

Verify if schema name matches selection formula

N/D column sorting overrides DB2 sortingAlways use @GetDB2Schema to determine the

schema name for query (available in beta 3)Verify if network account names are available on

new server

Verify if schema name matches selection formula

N/D column sorting overrides DB2 sortingAlways use @GetDB2Schema to determine the

schema name for query (available in beta 3)Verify if network account names are available on

new server

Query View SummaryQuery View Summary

JOINS solve basic N/D problem with relationsNew features offer the potential to create

applications that enable users to work more efficiently

Agregated views offer a new way to create a single point of access to all documents a user needs

Potential to address current problem scenarios with respect to performance/scalability

JOINS solve basic N/D problem with relationsNew features offer the potential to create

applications that enable users to work more efficiently

Agregated views offer a new way to create a single point of access to all documents a user needs

Potential to address current problem scenarios with respect to performance/scalability

AgendaAgenda 1 Introduction 2 Domino Access Views (DAV)



4 Summary

1 Introduction 2 Domino Access Views (DAV)



4 Summary

Conclusion/SummaryConclusion/Summary

Start thinking about scenarios in your companyStart consolidating your application landscapeLook into DB2 administrationGet skills in SQL programmingPrepare applications to utilize DAV and Query

ViewsStart nagging IBM to make NSFDB2 to easily run

on client

Start thinking about scenarios in your companyStart consolidating your application landscapeLook into DB2 administrationGet skills in SQL programmingPrepare applications to utilize DAV and Query

ViewsStart nagging IBM to make NSFDB2 to easily run

on client

Contact InformationContact Information

Dr. Ludwig Nastanskymailto:[email protected]@pavone.de

University of PaderbornGroupware Competence Centerhttp://gcc.upb.de

Dr. Ludwig Nastanskymailto:[email protected]@pavone.de

University of PaderbornGroupware Competence Centerhttp://gcc.upb.de

mailto:[email protected]


