Chapter 3 Building Information Liquidity Diagrams
The General tab contains the following properties:
| Property | Description |
|---|---|
| Name | The name of the item which should be clear and meaningful, and should convey the item's purpose to non-technical users. |
| Code | The technical name of the item used for generating code or scripts, which may be abbreviated, and should not generally include spaces. |
| Comment | Descriptive comment for the database. |
| Stereotype | Extends the semantics of an object derived from existing objects but specific to your needs. You can type stereotypes directly in the Stereotype box of the object property sheet or select a value from the list if you have previously defined stereotypes in an embedded or imported extended model definition (.XEM). |
| Server | Name of the server on which the database is defined. A server hosts the database that stores the tables gathering information. You can use the tools to the right of the list to create an object, browse the complete tree of available objects or view the properties of the currently selected object. For more information about servers, see the Servers (ILM) section. |
| Type | Undefined, RepConnector and UltraLite. Type for the database that influences the generation. They are defined in the extended model definitions (XEM) attached to the model. You can visualize in the Preview tab the generated code according to the type you selected. |
The following types are available for a database. Depending on the type you select and on the extended model definition attached to the model, the symbol of the database in the diagram changes accordingly:
| Database type | Symbol | When to use |
|---|---|---|
| Undefined | 
|
When you need to represent any standard relational database |
| UltraLite | 
|
When you need to replicate data on mobile devices (PDA, Pocket PC etc.), between persons wherever they may be |
| RepConnector | 
|
When you need to capture database changes in real time and deliver them in XML to message queues, that can be used by any supported message queuing system |
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |