Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseLink/DesignDocs/MultiTenantFeatures

< EclipseLink‎ | DesignDocs
Revision as of 12:40, 7 December 2010 by Tom.ware.oracle.com (Talk | contribs) (Purpose)

UNDER CONSTRUCTION

UNDER CONSTRUCTION

Purpose

EclipseLink provides a number of features that help with the challenges of developing multi tenant applications. This document will provide an overview of some of the ways EclipseLink can be used to support multi tenant applications.

In particular, this document will focus on applications where the application provider provides a core application and the tenant needs to extend the data provided in the application. (like Oracle Applications flex columns)

e.g. The application provider provides an Employee class that includes name and address. The tenant also wants to store the Employee Number. How can the application be architected to make storing that kind of extra data easy.

From a persistence-layer point of view, there are two areas where you must design to allow extra data.

  1. The object model and metadata
  2. The database

We will outline the options for both areas.

Object Model and Metadata

Database

Object Model

Copyright © Eclipse Foundation, Inc. All Rights Reserved.