Chapter 3 Building Information Liquidity Diagrams
You create the following objects in an information liquidity diagram:
| Object | Tool | Description |
|---|---|---|
| Database |
|
Data store based on a relational model and stored in one or several Physical Data Models. See Databases (ILM). |
| Server |
|
Hosts the database that stores the tables gathering information. See Servers (ILM). |
| XML Document |
|
Data store that contains data written under the XML format. Provides access to the XSM model. See XML Documents (ILM). |
| Data Access Application |
|
Data processing application that provides access to the OOM model. See Data Access Applications (ILM). |
| Conceptual Data |
|
Data store based on conceptual data and stored in one or several Conceptual Data Models. See Conceptual Data (ILM). |
| Business Process |
|
Data store based on a process model and stored in one or several Business Process Models. See Business Process (ILM). |
| Transformation process |
|
Data movement process that lets you design and document data transformations using Data Transformation Diagrams and Transformation Control Flow Diagrams. See the "Data Transformation Basics" chapter. |
| Flat file |
|
File that contains data and its format. See Flat Files (ILM). |
| Data Access Link |
|
Relationship that documents the way data is mapped between two data stores (database, data access application, conceptual data or XML document). See Data Access Links (ILM). |
| Replication process |
|
Represents a server engine which role is to make a copy of data incoming from a given database into one or several databases or replication processes. See Replication Processes (ILM). |
| Replication Server |
|
Represents a Replication Server. This tool only displays when the Replication Server XEM is attached to the ILM. See the "Working with Replication Server" chapter. |
| MobiLink |
|
Represents a MobiLink Server. This tool only displays when the MobiLink XEM is attached to the ILM. See the "Working with Mobilink" chapter. |
| Publication | N/A | Defines published data or procedures for a database connection. It allows the identification of a set of data to replicate and from where it is extracted. See Publications (ILM). |
| Article | N/A | Corresponds to a PDM table or view. It allows the identification of tables or views to replicate. See Articles (ILM). |
| Where clause | N/A | Script that complements the code generation (SQL) to restrict the rows of a table you want to replicate. See Article property sheet Where Clause tab. |
| Column | N/A | Data structure that contains an individual data item within a row (record) model equivalent of a database field. See Columns (ILM). |
| Procedure | N/A | Precompiled collection of SQL statements stored under a name in the database and processed as a unit. See Procedures (ILM). |
| Subscription | N/A | Establishes a link between a publication and a database connection. It defines where data published via the publication must be replicated. See Subscriptions (ILM). |
| User | N/A | Name that identifies a person or group working with objects in an ILM. See Users (ILM). |
| Connection group | N/A | Set of data connections that provides a relay in case the primary database goes down. See Data Connection Groups (ILM). |
| Event script | N/A | Defines how events on the replication process or on an article are implemented. See Event Scripts (ILM). |
| Process connection |
|
Relationship that specifies the way data is moved between two replication processes or between two transformation processes. See Process Connections (ILM). |
| Data connection |
|
Relationship that specifies the way data is moved between a database and a replication process, a data store and a transformation process or two data stores. See Data Connections (ILM). |
| Generation link |
|
Relationship that documents generation dependencies between at least two data stores (database, XML document, conceptual data, business process or data access application). See Generation Links (ILM). |
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |