This chapter contains reference information about dialog boxes for SQL Developer Data Modeler. The dialog boxes sometimes have multiple panes, each reflecting a logical grouping of properties for that type of object.
For an explanation of any dialog box, click the Help button or press the F1 key.
This dialog box is displayed when you click the Add (+) icon in an Events pane for an object for which events are relevant.
New Event: Lets you create a new event and associate this event with the object.
Available Event: Lets you select an existing event to be associated with the object.
Name (new event): Name of the new event.
Type (new event): Type of the new event: Clock/Calendar, Person, or Storage.
All Events: List of events from which to select for an available event.
This dialog box displays the properties of an exclusive relationship group (arc). Arcs are displayed in a logical model or relational model diagram, and are explained in Section 1.3.4.7.
Name: Name of the arc.
Entity (logical model) or Table (relational model): Name of the logical model entity or relational model table associated with this arc.
Mandatory (relational model): Controls whether there must exist only one relationship for each instance of the entity or table.
Include into DDL Script (relational model): Controls whether the arc requirements are included in any generated DDL statements.
Relations (logical model) or Foreign Keys (relational model)
Lists the logical model relations or relational model foreign keys in this arc. To view or edit the properties of a listed relation or foreign key, double-click its item.
This dialog box displays the properties of an attribute, which is a component of an entity in the Logical Model.
Name: Name of the attribute.
Synonym: Synonym for the attribute.
Preferred Abbreviation: Name that will be used for any corresponding table column during forward-engineering if the Use Preferred Abbreviations option is enabled in the Engineering dialog box.
Long Name: Long name in the format: entity-name.attribute-name.
Allow Nulls: Controls whether null values are allowed for the attribute. If this option is enabled, a null value is allowed; if this option is disabled, a non-null value is mandatory.
Datatype: Enables you to specify a domain, logical type, distinct type, collection type, or structured type as the data type of the attribute. You can click the ellipsis (...) button to specify further details for the selected type.
Entity: Name of the entity with which the attribute is associated.
Source Name: User-specified name of the source for this attribute.
Source Type: Manual, System, Derived, or Aggregate.
Formula Description: For a derived or aggregate source type, the formula for the attribute.
Scope: For a structured type with Reference enabled, limits the scope by specifying the table in which the type is implemented.
Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type is generated in the DDL.
Constraint Name: Name of the constraint.
Default Value: Default value for the attribute.
Use Domain Constraints: Controls whether the properties defined in Domains Administration for the associated domain are used. If this option is disabled, you can use the remaining fields to specify the database type for the constraint and the ranges or a list of values.
Constraint: Enables you to specify a constraint for one or more types of databases.
Ranges: Enables you to specify one or more value ranges for the attribute.
Value List: Enables you to specify a list of valid values for the attribute.
For a structured data type, lists all subtypes for the attribute, and lets you specify whether each is permitted for the attribute.
Enables you to specify the relational models to which this attribute should be propagated in forward engineering operations.
Engineer: Controls whether the attribute is propagated to the specified Relational Design (model) during forward engineering operations.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
See Section 3.9, "Common Information in Dialog Boxes".
Comment text to be included in database objects that are generated based on this modeling object.
This dialog box is displayed if you specify the Change Object Names Prefix command on the logical model or a relational model. Specify the new prefix to replace a specified current prefix. You can restrict the changes to selected types of objects.
Current Prefix: Prefix to be changed to the new prefix.
New Prefix: Prefix to replace all occurrences of the current prefix in names for the selected types of objects.
Case Sensitive: Controls whether case sensitivity is applied in searching for old strings to be replaced by new strings.
Apply to: Specify the types of objects for which to perform the prefix replacement. The types of objects depend on the type of model (logical or relational).
Change requests allow details of proposed changes affecting model objects to be recorded. They may also be used to keep a historical record of implemented or rejected changes. A change request object can be associated with one or more model objects.
Name: Name of the change request.
Comment: Optional descriptive comment text.
Notes: Optional note text, such as background information or implementation notes.
Reason:
Status: Current status of the change request: Proposed, Agreed (accepted), Implemented, Implementing (implementation in progress), or Rejected.
Completed: Indicates whether the work on the change request is completed.
Request Date: The date when the change request was made.
Completion Date: The date when the work on the change request was completed.
Implementation Note: Optional note about the implementation of the change request.
Summary: Displays read-only summary information.
When you click Help and then Check for Updates, you can check for and download available Data Modeler updates. The following pages may be displayed. (If you have enabled the Data Modeler preference to check for updates automatically at startup, and if you click to see available updates at startup, the Updates page is displayed.)
If you are unable to check for updates because your system is behind a firewall, you may need to set the user preferences for Web Browser and Proxy.
Source: Select the source or sources to be checked for available updates: any or all of some specified online update centers, or a local ZIP file containing an update bundle. You can also click Add to add a user-defined update center.
Updates: If any updates are available from the selected source or sources, select those that you want to download.The available updates include certain third-party JDBC drivers, which require that you agree to the terms of their licenses.
The Show Upgrades Only option restricts the display to upgrades of currently installed Data Modeler components. To enable the display of all new and updated components, whether currently installed or not, uncheck this option.
After you click Next, you may be prompted to enter your Oracle Web Account user name and password. If you do not have an account, you can click the Sign Up link.
License Agreements (displayed only if you selected any updates that require a license agreement): For each update that requires you to agree to the terms of a license, review the license text and click I Agree. You must do this for each applicable license.
Download: If you selected any updates to download, this page displays the progress of the download operation.
Summary: Displays information about the updates that were downloaded. After you click Finish, you will be asked if you want to install the updates now and restart Data Modeler.
This dialog box displays the properties of collection type, which is part of the Data Types Model.
Name: Name of the collection type.
Collection Type: ARRAY for a Varray collection type (an ordered collection of elements), or COLLECTION for a nested table collection type (can have any number of elements).
Max Element: For a Varray type, the maximum number of elements it can contain.
Datatype: The data type of each element.
This dialog box displays the properties of a table column, which is part of the Relational Models.
Name: Name of the column.
Long Name: Long name in the format: table-name.column-name
Engineer: Controls whether the column will be considered during reverse engineering operations. If this option is disabled, this column and its properties are not considered when the table is reverse engineered into the associated entity in the logical model.
Allow Nulls: Controls whether null values are allowed for the column. If this option is enabled, a null value is allowed; if this option is disabled, a non-null value is mandatory.
Table: Name of the table with which the column is associated.
Datatype: Enables you to specify a domain, logical type, distinct type, collection type, or structured type as the data type of the column. You can click the ellipsis (...) button to specify further details for the selected type.
Type: Manual, System, Derived, or Aggregate.
Computed: Indicates whether the column is a virtual column. A virtual column is not stored on disk. Rather, the database derives the values in a virtual column on demand by computing a set of expressions or functions.
Column Expression: For a derived or aggregate type, the expression for computing the value in the column.
Scope: For a structured type with Reference enabled, limits the scope by specifying the table in which the type is implemented.
Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type is generated in the DDL.
Constraint Name: Name of the constraint.
Uses Default: Controls whether the default value is used for this column.
Default Value: Default value for the column.
Use Domain Constraints: Controls whether the properties defined in Domains Administration for the associated domain are used. If this option is disabled, you can use the remaining fields to specify the database type for the constraint and the ranges or a list of values.
Constraint: Enables you to specify a constraint for one or more types of databases.
Ranges: Enables you to specify one or more value ranges for the column.
Value List: Enables you to specify a list of valid values for the column.
Specifies information that will be used to create a sequence for automatically incrementing values in this column when rows are inserted into the table.
Start with: Starting value of the sequence.
Increment by: Interval between successive numbers in the sequence.
Min value: Lowest possible value for the sequence. The default is 1 for an ascending sequence and -(10^26) for a descending sequence.
Max value: Highest possible value for the sequence. The default is 10^27 for an ascending sequence and -1 for a descending sequence.
Cycle: Indicates whether the sequence "wraps around" to reuse numbers after reaching its maximum value (for an ascending sequence) or its minimum value (for a descending sequence). If cycling of values is not enabled, the sequence cannot generate more values after reaching its maximum or minimum value.
Disable Cache and Cache: If Disable Cache is checked, sequence values are not preallocated in cache. If Disable Cache is not checked, sequence values are preallocated in cache, which can improve application performance; and Cache size indicates the number of sequence values preallocated in cache.
Order: Indicates whether sequence numbers are generated in the order in which they are requested. If no ordering is specified, sequence numbers are not guaranteed to be in the order in which they were requested.
Sequence Name: Name of the sequence. Must be unique within the database schema. If a sequence with the same name already exists in the physical model, the existing sequence is used.
Trigger Name: The name for the before-insert trigger that will be automatically created if Generate Trigger is enabled. This trigger uses the sequence to generate a new value for the primary key when a row is inserted. If a trigger with the same name already exists in the physical model, the existing trigger is used
Generate Trigger: Controls whether or not to generate the trigger automatically.
Specifies any relevant security-related properties for the column: whether it contains personally identifiable information (PII), contains sensitive information, or should be masked when displayed.
For a structured data type, lists all subtypes for the attribute, and lets you specify whether each is permitted for the attribute.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
Many dialog boxes let you include comments and notes about a modeling object, and to see a summary of the current information. You can also often view, add, and delete business model objects (documents, responsible parties, and so on) that are associated with the object.
Optional descriptive comment text about the modeling object.
Note that for some objects you can specify both Comments and Comments in RDBMS. Any Comments in RDBMS text is included in DDL statements that are generated for creating the object in a database.
Optional note text, such as background information or implementation notes.
Displays a tree representation of objects that are related in some way to the currently selected object. You can expand and collapse the tree and double-click some leaf-node objects in the tree, but you cannot add or delete related objects in the tree.
Lists any relevant measurements. To add a measurement, click the Add (+) icon; to remove a measurement from the object definition, select it and click the Remove (X) icon. (See also Measurement Properties.)
Lists any relevant change requests. To add a change request, click the Add (+) icon; to remove a change request from the object definition, select it and click the Remove (X) icon. (See also Change Request Properties.)
Lists any relevant responsible parties. To add a responsible party, click the Add (+) icon; to remove a responsible party from the object definition, select it and click the Remove (X) icon. (See also Responsible Party Properties.)
Lists any relevant documents. To add a document, click the Add (+) icon; to remove a document from the object definition, select it and click the Remove (X) icon. (See also Document Properties.)
Displays read-only summary information.
This dialog box is displayed if you click View Compare Mapping in the Relational Models dialog box.
It displays any mappings between source and target columns; and for each mapping you can select, edit, or delete it.
Lets you apply a filter to restrict the types of objects and specific objects to be included when models are imported.
Filter: You can include all objects, or only new, deleted, or modified objects.
This dialog box lets you control the types of objects and specific objects to be merged when two relational models are compared and merged. Objects from the selected model in the file that you opened are on the left, and objects from the selected model in the currently open design are on the right.
You can expand and collapse the display of the relational models. If you select a specific table or view, the Details, Options, and perhaps other panes at the bottom display information for that object.
Filter: Lets you display all objects in both models, or display only new, deleted, or modified objects
To update the selected relational model in the current design by merging objects from the selected relational model in the external file, click Merge.
Include Comments: Controls whether comments are included in the compare and merge operation.
DDL type: Type of DDL statements to be generated.
Replace Existing Files: Controls whether any existing DDL files will automatically be replaced.
Unload Directory: Directory or folder in which to save DDL files.
This dialog box, which is displayed if you click Configure in the Extensions preferences pane, enables you to select from among available versioning support extensions for Data Modeler. For information about using versioning with Data Modeler, see Section 1.9.
If you change any existing settings, you will need to restart Data Modeler.
This dialog box displays the properties of a contact object, which is a type of Business Information object.
Name: Name of the contact object. For example, it might be the name of a person, a role, a group, a department, or a company.
Lists any email objects. To add an email object, click the Add (+) icon; to remove an email object from the contact definition, select it and click the Remove (X) icon. (See also Email Properties.)
Lists any location objects. To add a location object, click the Add (+) icon; to remove a location object from the contact definition, select it and click the Remove (X) icon. (See also Location Properties.)
Lists any telephone objects. To add a telephone object, click the Add (+) icon; to remove a telephone object from the contact definition, select it and click the Remove (X) icon. (See also Telephone Properties.)
Lists any relevant URLs. To add a URL, click the Add (+) icon; to remove a URL from the contact definition, select it and click the Remove (X) icon. (See also Resource Locator Properties.)
Use this dialog box to create a database connection.
Connection Name: A descriptive name or alias for the connection. Example: HR_Local
Connection type: Type of database to which to connect: Oracle (JDBC) or JDBC ODBC Bridge.
Username: Name of the database user for the connection. This user must have sufficient privileges to perform the tasks that you want to perform while connected to the database.
Password: Password associated with the specified database user.
Role: Database role (if any) associated with the user.
Save Password: Specify whether to save the password with the connection information. If the password is saved, users of the connection will not be promoted to enter the password.
Enter Custom JDBC URL: If you select this option, enter the URL for connecting directly from Java to the database; overrides any other connection type specification. If you are using TNS or a naming service with the OCI driver, you must specify this information: Example:
jdbc:oracle:thin:scott/@localhost:1521:orcl
Note that in this example, the "/" is required, and the user will be prompted to enter the password.
To use a custom JDBC URL, the system on which Data Modeler is running must have an Oracle Client installation that contains the JDBC and orai18n libraries, is present on the path, and is version 10.2 or later.
Driver: thin (JDBC driver) or oci8 (thick) (if available)
Host Name: Host system for the Oracle database. Example: localhost
JDBC Port: Listener port. Example: 1521
SID: Database name. Example: orcl
Service Name: Network service name of the database (for a remote database connection over a secure connection).
Datasource Name: Name of an existing ODBC data source.
Extra Parameters: Additional parameters for the connection.
Test Connection: Performs a test of the connection, and indicates success or a specific error.
This dialog box is displayed if you right-click a relational model name in the browser and select Create Discovered Foreign Keys. It can help you to discover hidden foreign key relationships in the model. It is based on name and data type matching between columns in primary key columns, unique constraints, and other columns in tables.
You specify one or two foreign key column name policies to be used in the discovery process, and you can scan repeatedly with different policies and other options to see the keys that have been discovered.
If the relational model already contains foreign keys, then creating "discovered" foreign keys may create some foreign keys that seem "duplicates" of existing foreign keys (same basic information, but different foreign key names). All discovered foreign keys have the Name createdByFKDiscoverer and the Value true in the Dynamic Properties pane of the Foreign Key Properties dialog box.
Column to Filter and Filter: Lets you restrict the display based on a string in the name of the table, column, referred table, or referred key.
Referred Table: The table containing the key referred to by the specified column or columns in Table.
Referred Key: The key in Referred Table.
Table: The table in which the specified column or columns refer to the Referred Key in Referred Table.
Columns: The column or combination of columns in Table.
Single Use of FK Column: If this option is enabled, a foreign key column can be bound only to one foreign key.
FK Column Name Policy: The policy or policies to be applied when you click Scan Again:
Referred Column: The foreign key column has the same name as the referred column.
PK Column Template: The name of the foreign key column is equal to the name generated using the FK Column Template defined in the preferences for Naming Standard.
Referred and Template: First applies the Referred Column policy, then the PK Column Template policy.
Template and Referred: First applies the PK Column Template policy, then the Referred Column policy.
Scan Again: Searches for foreign key relationships using the specified policies and options, and refreshes the list above in the dialog box.
OK: Creates foreign keys based on the results of the most recent scan, and closes the dialog box. (If you want to remove the discovered foreign keys, click Edit, then select Remove Discovered Foreign Keys.)
Cancel: Does not create foreign keys, and closes the dialog box.
This dialog box displays the properties of a cube, which is part of the multidimensional model. It is displayed when you view the properties of a cube or when you import cube views metadata. (Importing cube views metadata enables you to create a multidimensional model based on an existing implementation.)
Cubes are first-class database objects that store data in a dimensional format. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the cube.
Virtual: Indicates whether this is a virtual cube or an actual cube. A virtual cube combines multiple actual cubes into a single logical cube.
Partitioned: Controls whether the cube is partitioned. Partitioning is a method of physically storing the measures in a cube. It improves the performance of large measures.
Part. Dimension: Dimension for partitioning the cube. (For example, if your partitioning strategy is driven primarily by life-cycle management considerations, then you should partition the cube on the Time dimension.) The dimension must have at least one level-based hierarchy and its members should be distributed evenly, such that every parent at a particular level has roughly the same number of children.
Part. Hierarchy: Hierarchy to be used for partitioning. If the dimension has multiple hierarchies, choose the one that has the most members; it should be defined as the default hierarchy.
Part. Level: Level to be used for partitioning. Each dimension member at that level is stored in a separate partition, along with its descendants. Any dimension members that are at higher levels or are not in the hierarchy are stored together in the top partition. The size of the top partition should not exceed the size of the level-based partitions.
Global Composites: Controls whether the cube will use one global composite or multiple composites. An unpartitioned cube always has one composite for the cube, whether it is compressed or uncompressed. A partitioned compressed cube always has a composite for each partition. A choice between single (global) and multiple composites is available only for uncompressed, partitioned cubes.
When in doubt, do not choose this option. The cube will have one composite for each partition.
Compressed Composites: Controls whether composites are compressed or uncompressed. Cubes that are very sparse often use a compressed composite.
Full Cube Materialization: Materialized view for a cube that has been enhanced with materialized view capabilities. A cube materialized view can be incrementally refreshed at prescheduled times or on demand through the Oracle Database materialized view subsystem. It can also serve as a target for transparent rewrite of queries against the source tables.
Lists unselected, available entities for the cube on the left and selected cubes on the right. Use the arrow keys to move selected entities from one side to the other.
Use Fact Entities Only: Controls whether only tables in a star schema that contain facts are displayed.
Lists any joins for the cube. To add a join, click the Add (+) icon; to remove a join from the cube definition, select it and click the Remove (X) icon. (See also Join Properties.)
Lists any dimensions for the cube. To add a dimension, click the Add (+) icon; to remove a dimension from the cube definition, select it and click the Remove (X) icon. (See also Dimension Properties.)
Default Operator: Default operator assigned to the dimension.
IsSparse: If selected, null values and empty fields are excluded, in order to manage space.
Calculated measures can add information-rich data to a cube. The data set is calculated on the fly, so no data is stored. You can add as many calculated measures as you like without increasing the size of the database.
Lists any slices for which values are precalculated (precomputed) and stored in the cube during data maintenance. To add a precalculated slice, click the Add (+) icon; to remove a precalculated slice from the cube definition, select it and click the Remove (X) icon. (See also Slice Properties.)
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Mycubes if the Short Name is Mycube
Lists any relevant SQL Access to Oracle Analytic Workspaces (AW) objects. To add a SQL Access to Oracle AW object, click the Add (+) icon; to remove a SQL Access to Oracle AW object from the cube definition, select it and click the Remove (X) icon. To edit a SQL Access to Oracle AW object, double-click its item, or click its item and click the Properties icon. (See also SQL Access to Oracle AW Properties.)
Description of the cube.
Description of the partitioning for the cube.
This wizard is displayed when you click File, then Import, then Data Dictionary. It enables you to connect to an existing database (Oracle or supported third-party) and to create one or more relational models based on the metadata in that database.
The specific steps and fields depend on the type of database that you connect to. This topic describes information for an Oracle Database connection.
Displays a list of database connections, from which you must select one. If no connections exist or if the one you want is not displayed, click Add to display the Database Connection Editor dialog box, or click Import to display the Import Database Connections dialog box.
Select the schemas from which to import. Note: Metadata will be extracted only for schemas that the user associated with the connection is authorized to access. A separate subview will be created within the relational model for each Oracle Database schema from which metadata is extracted. (To see a subview, expand the Subviews node, right-click the subview name, and select Show Diagram.)
Select All and Deselect All (this page and next page): Enable you to conveniently select or deselect all displayed items, and then deselect or select individual items.
All Selected: Controls whether all items are initially selected or deselected when you move to the next page (Select Objects to Import).
Secondary Tables: Includes secondary tables in the metadata extraction.
Spatial Properties: Includes Oracle Spatial properties in the metadata extraction.
Select the objects for the metadata extraction. For each type of object to be imported, click its associated tab (Tables, Views, Users, and so on), and select the desired objects. For each tab, you can select or deselect all, or you can select and deselect individual objects of that type.
Displays a summary page with the number of objects of specified types to be imported. (If no objects or any type are to be imported, go back to the Select Objects to Import page and select at least one object.)
To perform the import operation, click Finish.
This dialog box is displayed if you add or edit a database connection while using the Data Dictionary Import (Metadata Extraction) wizard. The specific fields depend on the connection type that you select; this topic describes the fields for an Oracle connection.
Type: Type of database to which to connect: Oracle, Microsoft SQL Server 2000 or 2005, IDB DB2 or UDB, or JDBC ODBC Bridge.
For a third-party database connection, you must have specified the appropriate driver in Third Party JDBC Drivers under General Options (see Section 1.5.2).
Name: A descriptive name or alias for the connection. Example: HR_Local
Host: Host system for the Oracle database. Example: localhost
Port: Listener port. Example: 1521
SID: Database name. Example: orcl
Username: Name of the database user for the connection. This user must have sufficient privileges to perform the tasks that you want perform while connected to the database.
Password: Password associated with the specified database user.
This dialog box is displayed after you select a relational model for which to generate Data Definition Language (DDL) statements. It is also displayed if you click View, then DDL File Editor, or if you click the Generate DDL toolbar icon when a relational model diagram is displayed.
Physical model (list): Select the physical model (type of database) for which to generate DDL statements. Example: Oracle 11g
Generate: Displays the DDL Generation Options dialog box. After you select the options, the resulting DDL statements are displayed in this dialog box.
Clear: Clears the display of generated DDL statements. If the generated DDL code does not meet your needs, click Clear, make any necessary changes to the model, and start the generation process again.
Find: Displays a box for finding a text string in the generated DDL statements.
Save: Lets you save the generated DDL statements to a script file.
This dialog box is displayed when you click Generate in the DDL File Editor dialog box. These options control the content to be included in the generated script.
Buttons at the bottom: Design Rules displays the Design Rules dialog box, enabling you to check your current design for any violations of predefined design rules before you generate the DDL. Include Comments causes comments to be included in the statements. Apply Name Substitution causes old name strings to be replaced with new strings as specified in the Name Substitution pane. You can also select Regular DDL, Advanced Interactive DDL, or Advanced CL DDL.
Advanced Interactive DDL and Advanced CL (command-line) DDL create an ODM (Oracle Data Mining) advanced script with support for interactive (SQL*Plus or SQL Developer) or command-line (SQL*Plus only) setting of the following input parameters: start step, stop step, log file, and log level (1,2 or 3). Format for SQL*Plus execution of a resulting Advanced CL DDL script:
SQL> sqlplus user/password@name @script_name start_step stop_step log_file log_level
Lets you select types of objects and specific objects for which to generate CREATE statements. You can select Tree View for an expandable display of all available objects, or a tab (Tables, PK and UK Constraints, and so on) for a subset of objects.
Adds DROP statements for objects of the selected types before any CREATE statements, to drop any existing objects with the same name before creating new objects.
You can include drop dependencies to add CASCADE to the DROP statements.
Lets you specify old strings to be replaced with new strings in object names when the DDL statements are generated.
Selected: Controls whether the item is enforced in the generation process.
Case Sensitive: Controls whether case sensitivity is applied in searching for old strings to be replaced by new strings.
For Advanced DDL only: Specifies any Oracle errors to be ignored during script execution. For the error Number or Type, specify a hyphen and significant digits without leading zeroes; for example, specify -942 for ORA-00942. The error description is informational only and does not affect the script execution.
This dialog box displays the properties of the Database Design.
Name: Name of the database design.
Design rules are rules that can be applied to check and enforce the integrity and consistency of designs. Data Modeler comes with many predefined design rules, and you can add your own custom design rules. You can also define functions or methods to create custom transformations, and can group these transformations into libraries.
If you click Tools and then Design Rules, you can select one of the following:
This dialog box enables you to apply Design Rules and to group design rules into Rule Sets.
This tab enables you to check your current design (logical, relational, and process models) for any violations of predefined Data Modeler design rules. You can check all design rules or selected rules; each violation of the specified rules results in a warning or error message, as appropriate. You are encouraged to check your models against the design rules often, especially before any forward or reverse engineering operations and before generating DDL statements for a physical model.
Examples of design rule warnings and errors include a primary key with the wrong naming standards, a flow without information structures, and an external agent without data elements.
For any error, you can double-click its item to display the properties for the associated object, where you can correct the problem.
Expand All: Expands the display to show all design rules in all categories and subcategories. When one or more categories are expanded, you can select individual rules, ranges of rules, or a combination.
Collapse All: Collapses the display to show only the design rule major category names (General, Logical, Relational, Process Model, Physical).
Apply All: Applies all design rules to the current design; displays a warning or error message for each violation of a rule.
Apply Selected: Applies only the selected design rules to the current design; displays a warning or error message for each violation of a rule.
Clear: Clears any displayed warning and error messages.
This tab enables you to create and edit named rule sets. A rule set is a collection of rules that you want to be able to check as a set.
To create a rule set, click the Add Rule Set (plus sign) icon, specify a name for the rule set, double-click the rule set number (or click the Rule Set Properties pencil icon), and use the Rule Set Properties dialog box to move desired rules from the All Rules column into the Selected Rules column.
Apply All RS: Applies the design rules in all rule sets to the current design; displays a warning or error message for each violation of a rule.
Apply Selected RS: Applies only the design rules in the selected rule set or rule sets to the current design; displays a warning or error message for each violation of a rule.
Clear: Clears any displayed warning and error messages.
The Custom Rules dialog box enables you to create custom design rules using a language supported by the rules execution engine, such as the Mozilla Rhino JavaScript implementation.
Name: Name of the custom rule.
Object: Type of the objects to which to apply this rule. Examples include Table, Column, Entity, and Attribute.
Engine: Implementation used for interpreting and executing the rule.
Type: Severity if a violation of the rule is detected (Warning or Error).
Variable: Name of the variable associated with the rule.
Rule Script Library: Library containing the method associated with the rule.
Rule Script Method: Method associated with the rule. (To modify a method, use the Custom Libraries dialog box.)
You can save custom rules that you create, export custom rules that you have saved, and import design rules from an XML file.
The Custom Libraries dialog box enables you to view, create, and delete libraries for custom design rules, and within a selected library to add, delete, and edit the methods associated with custom design rules.
For information about design rules and custom design rules, see Section 3.23, "Design Rules".
The Custom Transformation Scripts dialog box enables you to view, create, delete, and edit custom transformation scripts for implementing custom design rules.
Name: Name of the custom transformation.
Object: Type of models (logical or relational) to which to apply this transformation.
Engine: Implementation used for interpreting and executing the transformation.
Variable: Name of the variable associated with the transformation.
Script Library: Library containing the method associated with the transformation.
Script Method: Method associated with the transformation.
You can save custom transformations that you create, export custom transformations to an XML file, and import transformations from an XML file.
This dialog box displays the properties of a dimension in a multidimensional model.
A dimension (or more precisely, a cube dimension) is a first-class database object. It stores a list of values that serves as an index to the data stored in a cube. These values, or dimension members, represent all levels of aggregation. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the dimension. Examples: Customer, Product, Channel, Time
Use Natural Keys: Controls whether natural (source) keys or surrogate keys are used from the relational sources for the dimension members. If this option is enabled, source keys are read from the relational sources without modification. If this option is disabled, surrogate keys ensure uniqueness by adding a level prefix to the members while loading them into the analytic workspace.
Time Dimension: Controls whether the dimension is a Time dimension or a User dimension. If this option is enabled, you must define a Time dimension with at least one level to support time-based analysis, such as a custom measure that calculates the difference from the prior period.
Lists hierarchies associated with the dimension. To view or edit a hierarchy definition, double-click its item. (See also Hierarchy Properties.)
Lists levels associated with the dimension. To view or edit a level definition, double-click its item. (See also Level Properties.)
For a Slowly Changing Dimension (SCD), lists slowly changing attributes associated with the dimension. To view or edit an attribute definition, double-click its item. (See also Attribute Properties.)
Lists calculated members associated with the dimension. A calculated member enables the summation (simple plus or minus) or aggregation (using the Aggregation operator for the cube) of a set of dimension members that are specified by a user. To add a calculated member, click the Add (+) icon; to remove a calculated member from the dimension definition, select it and click the Remove (X) icon.
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Mydimensions if the Short Name is Mydimension
Description of the dimension.
This dialog box displays the properties of a display object.
Name: Name of the display object.
Visible: (Does not apply to this model.)
This dialog box displays the properties of a distinct type, which is part of the Data Types Model.
Name: Name of the user-defined distinct type.
Logical Type: The logical type from which the distinct type is derived.
(The remaining fields -- Size, Precision, and Scale -- are available only if they apply to this distinct type.)
Comment text to be included in database objects that are generated based on this modeling object.
This dialog box lets you view and modify information for a document object, which is a type of Business Information object.
Name: Name of the document object.
Reference: Descriptive phrase with reference information about the object, such as its location.
Type: Descriptive phrase indicating the type of document, such as General Procedure or Technical Specification.
Lists the objects currently associated with this document. To view the properties of any listed object, double-click its entry.
This dialog box displays information about an existing domain. Much of the information is read-only, and some fields apply only to certain kinds of domains. To add a user-defined domain or to remove a domain, click Tools, then Domains Administration, and use the Domains Administration dialog box.
Name: Name of the domain object.
Synonym: Synonym for the domain.
Long Name: Long name for the domain.
File Name: Name of the file containing the domain definition.
Logical Type: Logical type of the domain.
Size: Maximum size of data in columns based on the domain.
Precision: For a numeric domain, the maximum number of significant decimal digits.
Scale: For a numeric domain, the number of digits from the decimal point to the least significant digit.
Check Constraint: Constraints, both generic and database product-specific, on data values permitted for the domain. If constraints apply to the domain, you can double-click to edit the generic and product-specific constraints.
Ranges: Ranges of data values permitted.
Value List: List of data values permitted.
Lists attributes (logical model) and columns (relational model) that are based on this domain.
This dialog box is displayed if you click Tools, then Domains Administration.
Domains File: XML file containing the domain definitions (if other than the default). You can click Select to search for a file. (Note: To import domains for use, click File, then Import, then Domains.)
Available Domains: Displays the available domains (types). Select a domain to view or edit its properties. (Some properties are relevant only to specific domains.)
Name: Name of the selected domain (if one is selected).
Logical Type: Logical type of the selected domain.
Size: Maximum size of the data for this type.
Precision: For a numeric domain, the maximum number of significant decimal digits.
Scale: For a numeric domain, the number of digits from the decimal point to the least significant digit.
Synonym: Synonym for the domain.
Comment: Comment about the domain.
Check Constraint: Lets you view and edit constraints (general and specific to physical models) for the domain.
Ranges: Lets you specify one or more data value ranges for the domain.
Value List: Lets you specify data values for the domain.
This dialog box displays the properties of an email object, which is a type of Business Information object.
Name: Name of the email object.
Email Address: Email address in the standard format. Example: smith@example.com
Email Type: Descriptive phrase indicating the type of email object, using any naming scheme suited to your needs. Examples: Work, Personal
Lists the contact objects currently associated with this email object. To view the properties of any listed contact object, double-click its entry.
Depending on the context, this dialog box lets you update the logical model from a selected relational model or update a relational model from the logical model, control which parts of the logical model are reflected in a relational model, or restrict the types of objects and specific objects to be merged when two relational models are compared and merged.
Filter: You can include all objects, or only new, deleted, or modified objects.
Displays detailed information about the selected model object.
Show Engineering in the Main Browser: Controls whether a check box is added for each object in the browser window, with the box checked if the object has been engineered.
Engineer Coordinates: Controls whether to position the tables resulting from the forward engineering process in the same way as their source entities.
Engineer Only Objects Created in "<model>": Controls whether only objects that were explicitly created in the specified model are engineered, or whether those objects plus other objects that were created as a result of previous forward or reverse engineering operations should be engineered.
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.
Use Preferred Abbreviations: Controls whether any specified preferred abbreviations for entities and attributes are used for corresponding table and column names when the logical model is engineered to create a relational model.
Lets you select types of objects (entity/table, attribute/column, key/index, relation/foreign key, entity view/view), and for each pair indicate which of its properties are selected for use in the forward or reverse engineering operation. You can also specify the following options.
Show Selected Properties Only: Controls whether all properties for displayed objects are shown or only properties enabled (checked) under Selected.
Don't Apply for New Objects:
Exclude Unchecked Objects from Tree: Controls whether unchecked objects are included or excluded in the tree display.
Update Tree: Updates the logical and relational model tree displays to reflect the currently selected options.
Synchronization of Deleted Objects
Lets you select and deselect pairs of objects, with each pair containing a deleted object and the associated object to be deleted in the generated model if the pair is selected.
Overlapping and Folding Unique Identifiers (UIDs)
For engineering from the logical model to a relational model, displays information about any keys that overlap or are overlapped.
This dialog box displays the properties of an entity, which is part of the Logical Model.
Name: Name of the entity.
Synonyms: Synonyms for the entity.
Synonym to display: Synonym to display for the entity.
Preferred Abbreviation: Name that will be used for any corresponding table during forward-engineering if the Use Preferred Abbreviations option is enabled in the Engineering dialog box.
Long Name: Long name to be used in entity-name.attribute-name displays.
FWD Engineer Strategy: This field is important when you are working with supertype and subtype entities. It defines the strategy of engineering entities to relational model tables:
Single Table: The subtype entity metadata are included in the supertype table. There are no subtype tables.
Table per Child: The supertype entity metadata is included in the subtype tables. There is no supertype table.
Table for each Entity: A separate table is generated for each supertype and subtype entity.
Based on Structured Type: If the entity is based on a structured type, select it from the list. The entity will contain the attributes as defined in the structured type.
Super Type: If the entity is a subtype, select its supertype from the list. The entity inherits all attributes from the specified supertype.
Source: Description of the source type. Examples: DDL, COBOL Copybook, IDMS Schema
Type: Classification type, from the list defined in the General Options. Examples: Fact, Dimension, Logging, Summary, Temporary.
Scope: For an entity classified as Temporary, you can specify a scope, such as Session or Application.
Allow Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type generation in the DDL is allowed.
Lists the attributes currently defined for the entity. The properties for each attribute include its name and data type, and whether it is the primary unique identifier (Primary UID), a relation unique identifier (Relation UID, comparable to foreign key), or a required field (M, for mandatory).
To add an attribute, click the Add (+) icon; to delete an attribute, select it and click the Remove (X) icon; to view the properties of an attribute, double-click in the cell to the left of the name.
Lists the unique identifiers (UIDs) currently defined for the entity. The properties for each key include its name and whether it is included in the primary unique identifier (PUID).
To make the attribute a unique identifier, click the Add (+) icon; to make the attribute not a unique identifier, select it and click the Remove (X) icon; to view the properties of a unique identifier, double-click its name.
Lists any relations associated with the entity, To view the properties of a relation, double-click its name.
Volumes: Minimum: Minimum data volume for the entity.
Volumes: Expected: Expected or typical data volume for the entity.
Volumes: Maximum: Maximum data volume for the entity.
Growth Rate: Percent: Expected growth rate percentage for the entity, for each period as specified in the next field.
Growth Rate: Year/Month/Day: The period (year, month, or day) to which the expected growth rate applies.
Normal Form: The required normal form (database normalization) for the entity: None, First, Second, Third, or Fourth.
Adequately Normalized?: YES indicates that the model is sufficiently normalized. NO indicates that the model is not sufficiently normalized, and that additional normalization may be required on the relational model.
Enables you to specify the relational models to which this entity should be propagated in forward engineering operations.
Engineer: Controls whether the entity is propagated to the specified Relational Design (model) during forward engineering operations.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of an event, which is part of the Process Model.
Name: Name of the event.
Synonym: Synonym for the event.
Flow: Flow object that is associated with the event. To view or edit the Flow Properties, click the flow name.
Event Text: Application-defined or user-defined event text string.
Type: Application-defined or user-defined string identifying the type of event.
Lists the process triggered by the event. To view the Process Properties, double-click its entry.
Specify options for days when the event is to run: unlimited or limited number of occurrences; day or days of the week, or day of one or all months; specific quarter or all; and specific fiscal or calendar year, or all years. Zero (0) in a field means all or unlimited.
Specify options for times during the day when the event is to run: open or close of the business day, when convenient during the day, or at a specified time or at a specified interval.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
By exporting cube views metadata, you can deploy them in a UDB v8.1 physical environment.
Default Schema: Name of the default schema.
Dimensional Model: Name of the multidimensional model to be exported.
Relational Model: Name of the relational model.
Physical (DB2 or UDB) Model: Name of the physical model.
Exports the design to a Microsoft XMLA (XML for Analysis) file.
Database Name: Name of the database.
Dimensional Model: Name of the multidimensional model.
By exporting to Oracle Analytic Workspace (AW), you can create the analytic workspace based on a multidimensional model. For more information about working with analytic workspaces, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Default Schema: Name of the default schema.
Dimensional Model: Name of the multidimensional model.
Relational Model: Name of the relational model.
Oracle Model: Name of the Oracle model.
Oracle AW Name: Name of the Oracle analytic workspace.
Export Mode: Mode or scope of the export operation: re-create the analytical workspace, export all or only new calculated measures, or export only metadata.
Populate Created Cubes: Controls whether the created cubes are populated with their data.
Output XML File: Name of the XML file to contain the exported definition. To select an output directory or folder, click the ellipsis (...) button.
JDBC Connection: JDBC connection to use for the export operation.
New JDBC Connection: Enables you to create a new JDBC connection. To create a new connection, click Create.
Test Selected Connection: To test the selected JDBC connection, click Test. A message is displayed indicating either that the connection is available or that an error occurred.
Displays cubes and slices selected for the export operation.
Exports the design to the reporting repository in the reporting schema (explained in Section 1.8, "Data Modeler Reports"). To perform the export, you must select a connection and click OK.
Connections: Displays the names of database connections, from which you must choose one to serve as the reporting repository. To create a new database connection, click the Add Connection (+) icon; to delete an existing connection, select it and click the Remove Connection (X) icon; to edit an existing connection, double-click its entry, or select it and click the Connection Properties icon.
Comments: Optional descriptive text or notes about the connections.
Export Diagrams as PDF: If this option is enabled, diagrams in the design are exported in PDF format and stored as BLOBs; if this option is not enabled, diagrams are exported in XML format.
Drop Repository: Enables you to drop (delete) the reporting repository in the schema of the selected database connection. After the existing repository is dropped, a new empty repository is automatically created in this schema.
Delete Designs: Enables you to select a repository connection and then one or more designs within that repository, to have the information about those designs deleted from the repository.
Export Glossary: Enables you to specify a Data Modeler glossary file, to have its information exported to the reporting repository.
Delete Glossary: Enables you to select a glossary in the reporting repository, to have its information deleted from the repository.
This dialog box displays the properties of an external agent object, which is part of the Process Model.
Name: Name of the external agent.
Synonym: Synonym for the external agent.
Type: Type of external agent: Organization Unit, System, Role, or Other.
Displays flows coming into the external agent. To view the Flow Properties, double-click the flow item or select the item and click the Properties icon. (To add a flow, use the New Flow icon on the data flow diagram.)
Displays flows going out from the external agent. To view the Flow Properties, double-click the flow item or select the item and click the Properties icon. (To add a flow, use the New Flow icon on the data flow diagram.)
Owner: Owner of the external agent.
Source: Source of the external agent: where the information for the external agent comes from.
File Name: Name of the external agent file.
Location: Location of the external agent file.
File Type: Type of file: CSV (comma-separated values), fixed-length fields, Excel spreadsheet, or plain text.
Field Separator: Character (for example, comma) that separates fields.
Data Capture Type: Specifies whether the data capture is a full refresh or is limited to a specified type of capture operation.
Self Describing: Indicates whether the field is self-describing.
Skip Records: Number of records to be skipped at the top of the data file.
Text Delimiter: Text delimiter character that is used in text strings (single or double quotes).
Lists the external data elements currently defined for the external agent. To add an element, click the Add (+) icon; to remove an element from the definition, select it and click the Remove (X) icon; to view the properties of an element, double-click it or select it and click the Properties icon.
External Data: Name of the external data object.
Type: Logical type of the external data.
Starting Position: Starting position of the element in the data file.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a data element for an external agent object, which is part of the Process Model.
Name: Name of the external data object. You might want it to include a sequence number, for example, MyExtData_1.
Comment: Comment about this data element.
Logical Type: Logical type associated with this external data object.
Starting Position: Starting position of the external data object in the data file, where 0 (zero) is the first position.
Description: Optional description of the external data object.
Structured: Indicates whether this external data object is linked to a record structure.
Record Structure: If Structured is enabled, lists the available record structures; select one for this external data object.
This dialog box is displayed if you click the Find icon when a diagram is selected. Specify an object name and an object type, then click Find.
Object to Find: Name of the object to find. You must specify a complete string match, or include the asterisk (*) wildcard for any string. For example, specifying cust or customer will not find a table named customers; however, specifying cust* will find that table.
Case Sensitive: Controls whether the search for the object to find is case sensitive.
Object Type: Limits the search for objects to the specified type of object. (The available types depend on the type of diagram.)
This dialog box displays the properties of a flow (data flow) object, which is part of the Process Model.
Name: Name of the flow.
Synonym: Synonym for the flow.
Source: Source of the flow, for example, a process.
Destination: Destination of the flow, for example, an information store.
Parent Flow: Name of the parent flow, if any.
Logging Flow: Controls whether logging is activated for the flow.
Event: Flow event. You can click New to create a new flow event.
Operations: Options that control the types of operations that can be performed in the flow (create, read, update, delete).
Lists any component flows associated with the flow. To view or edit a component flow, double-click its item.
Lists any information structures associated with the flow. To add an information structure, click the Add (+) icon; to remove an information structure from the flow definition, select it and click the Remove (X) icon. (See also Information Structure Properties.)
Lists any external data objects associated with the flow. To view or edit an external data object, double-click its item.
Description of the system objective for this flow.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a foreign key relation, which is part of the definition of a table in Relational Models.
Name: Name of the foreign key.
Table: Name of the table containing this foreign key (a column whose value must match a value in a primary key or unique key column in another table).
PK/UK Index: The primary key, unique key, or index to which this foreign key refers (for example, the primary key column in another value that must contain a matching value for each value in the foreign key column).
Delete Rule: Action to take automatically when a row in the referenced table (in PK/UK Index) is deleted and rows with that value exist in the table containing this foreign key: NO ACTION (shown by a crossing line in diagrams) performs no action on these rows; CASCADE (shown by an "X") deletes these rows; SET NULL (shown by a small circle) sets null all columns in those rows that can be set to a null value; RESTRICT (also shown by one crossing line) prevents those rows from being deleted.
Source Table Synonym: Name or synonym of the table containing the primary or unique key to which this foreign key refers.
Target Table Synonym: Name or synonym of the table containing this foreign key column.
Mandatory: Controls whether referential integrity is enforced. If this option is enabled, referential integrity is enforced (that is, a matching value in the table for the referenced primary or unique key is mandatory; and if a matching value does not exist, a record cannot be created in the current table). If this option is not enabled, referential integrity is not enforced, and applications that use the database must deal with any potential problems caused by inconsistent data.
Transferable (Updateable): Controls whether the foreign key relationship is transferable (that is, updateable). In a non-transferable relationship, each foreign key value cannot be changed; for example, if a line item has a non-transferable relationship to an order, a line item cannot be reassigned later to another order. In a transferable relationship, a foreign key value can be changed; for example, an employee could be transferred later from one department to another.
If the foreign key relationship is non-transferable, a diamond appears on the line in the diagram.
Generate in DDL: Controls whether the foreign key creation is included when DDL statements are generated to be used to create the database.
In Arc: Controls whether the foreign key relationship should be included in An exclusive relationship group (arc). For more information, see Section 1.3.4.7, "Arcs".
Lists each parent column and child column pair in the foreign key definition.
For foreign keys that have been discovered (see Section 3.16, "Create Discovered Foreign Keys"), contains the Name createdByFKDiscoverer and the Value true.
This dialog box is displayed if you click Tools, then Glossary Editor, and either specify a file name that does not exist (for example, my_terms.glossary) in a selected location to create a new glossary file, or select an existing glossary file for editing. (See also Naming Standard under Data Modeler.)
A glossary in Data Modeler is a set of accepted terms that may or must be used in the design. Glossaries are used by Design Rules to ensure that the model complies with your set naming standards or when engineering between the logical and relational models. You can create a new glossary from scratch, use existing glossaries, or generate a new glossary based on an existing logical model.
Do not modify glossary files (XML format) in an external text editor. Instead, create and modify glossaries using the glossary editor within Data Modeler.
Name: Name of the glossary. Example: Project XYZ glossary
Description: Brief description of the glossary.
Incomplete Modifiers: Controls whether all terms used in names do or do not need to be defined in the glossary. If this option is enabled, it is not mandatory that modifiers and qualifiers be defined in the glossary; as a consequence, name validation will succeed if name parts that are not in the glossary correspond to a modifier or qualifier in the name structure.
Case Sensitive: Controls whether name validation using this glossary will be case sensitive. For example, if this option is enabled, "Code" and "CODE" are considered different values.
Unique Abbreviations: Controls whether uniqueness of abbreviations is required. If this option is disabled, uniqueness is not required, thus allowing one abbreviation to be used for all forms of a single word. In this case, for example, ADMIN could be an abbreviation for Administrator, Administration, and Administrative (that is, three terms with the same abbreviation). Such definitions should be maintained carefully because name validation (and name translation) will return correct results only if all terms have the same classification settings. If this option is enabled, name validation will report non-unique abbreviations (alternate ones are also included) and words without abbreviations.
Separator and Sep. char.: Define a word separator for multi-word terms. Note that separator settings are checked when a glossary is loaded into the glossary editor; and if the separator is not a space character, a warning is displayed, and you can change the separator to a space.
Filter: Lets you display all glossary entries or restrict the display to entries that include a specified classification. ("Unclassified" shows only entries that have no classification.)
Words: To add a glossary entry, click the Add (+) icon and complete the information on the new line for the entry; to delete a glossary entry, select its entry and click the Remove (X) icon; to edit an entry, select its entry and modify the information.
Name (of entry): Glossary term associated with this entry.
Plural: Optional plural form of the associated entry (for example, AMOUNTS as the plural for AMOUNT). If a Plural value is specified, the singular and plural are considered the same during design rule validation and during transformation for entities and tables.
Abbreviation: Abbreviation for the glossary term.
Alt Abbreviation: Alternative abbreviation for the glossary term.
Prime, Class, Modifier, Qualifier: Specify as many classification types (prime word, class word, modifier, qualifier) as apply to the glossary entry. Name patterns can be defined for entities, attributes, tables, columns, and domains. A name pattern defines the structure of the name in the form of an unrestricted sequence of permitted word types and their optionality.
Prime: The prime word identifies the object or element being defined. Typically, these objects represent a person, place, thing, or event about which an organization wishes to maintain information. Prime words may act as primary search identifiers when querying a database system and provide a basic list of keywords for developing a general-to-specific classification scheme based on business usages. CUSTOMER in Customer Address is an example of a prime word.
Class: A class word is the most important noun in a data element name. Class words identify the use or purpose of a data element. Class words designate the type of information maintained about the object (prime word) of the data element name. ADDRESS in Customer Address is an example of a class word
Modifier: A modifier gives additional information about the class word or prime word. Modifiers may be adjectives or nouns. DELIVERY in Customer Delivery Address is an example of a modifier. Other modifier examples: ANNUAL, QUARTERLY, MOST, LEAST
Qualifier: A qualifier is a special kind of modifier that is used with a class word to further describe a characteristic of the class word within a domain of values, or to specify a type of information which can be attached to an object. Examples: FEET, METERS, SECONDS, WEEKS
Short Description: Short description of the entry.
Import: Lets you specify a glossary file and import its entries.
Export: Lets you export the glossary to a comma-separated values (CSV) file.
Save: Saves the current entries into the currently open glossary file.
Save As: Saves the current entries in a glossary file that you specify.
This dialog box is displayed when you view the properties of a hierarchy in a multidimensional model.
A hierarchy is a way to organize data at different levels of aggregation. Hierarchies are used to define data aggregation; for example, in a Time dimension, a hierarchy might be used to aggregate data from days to months to quarters to years. Hierarchies are also used to define a navigational drill path. In a relational table, hierarchies can be defined as part of a dimension object.
For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the hierarchy.
Value Based Hierarchy: Controls whether this is a value-based hierarchy, that is, a hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named.
Time Based Hierarchy: Controls whether this is a time-based hierarchy, that is, a hierarchy composed of time-related levels such as Month, Quarter, and Year.
Ragged Hierarchy: Controls whether this is a ragged hierarchy, that is, a hierarchy in which leaf nodes can be located at different levels.
Default Hierarchy: Controls whether this is the default hierarchy for the dimension.
Lists levels associated with the hierarchy. To view or edit a level definition, double-click its item. (See also Level Properties.)
Lists rollup links associated with the hierarchy. To view or edit a rollup link definition, double-click its item. (See also Rollup Link Properties.)
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Myhierarchies if the Short Name is Myhierarchy
Description of the hierarchy.
This dialog box is displayed if you click File, then Import, then Domains. You can import domains from an XML file, for example, to use domains that you created for another design.
Open Domain File: Displays a dialog box for specifying the XML file containing domain definitions to be imported.
Import in Default Domains: Controls whether the imported domains will be saved in a file named defaultdomains.xml and placed in the types directory (folder) under the location where you installed Data Modeler. The domain definitions in the defaultdomains.xml file are available whenever you use Data Modeler.
Domains in File: Displays the domains in the domain file that you opened.
Filter: Lets you control whether all domains are displayed, or only new or modified domains.
Corresponding Domains in Design <name>: Displays any corresponding domains in the current design.
This dialog box is displayed if you click Import in the Glossary Editor and specify a glossary file with glossary terms (naming standard definitions) to be imported. You can import definitions from an external glossary and then modify the details.
The possible words to be imported and the corresponding words in the current glossary are displayed. You can select and deselect words to import.
Separator settings are checked when the terms from the external glossary are loaded into the glossary editor. If the separator is not the space character, a report showing all terms with a space in the name is displayed, and you are given the option to replace the space with a defined glossary separator.
This dialog box is displayed if you specify to import mapped models in the Import VAR File: Select Type of Import dialog box.
Logical Model: Select the file containing the logical model.
Relational Models: Lists the relational models to be included. To add a model, click Add; to remove a model, click its name and click Remove.
This wizard enables you to import an Oracle Designer design into Data Modeler.
Specify information to connect to the database with the Oracle Designer design. Select an existing connection, or click Add to specify information for a new connection.
To test a connection, select it and click Test Connection.
To move to the next wizard page, select a connection and click Next.
Follow the instructions on the remaining wizard pages to select the work area, select application systems, select objects to import, and generate the design. Click Next to move to a next page, and click Finish on the last page to perform the import operation.
For Select Objects to Import, if you are importing from a versioned Designer repository, only objects that have been checked in appear in the list of objects that you can import.
This wizard is displayed if you click File, then Import, then Data Modeler Design, and then specify an XML file containing a Data Modeler design.
Lists the logical model and any relational models in the specified file, and lets you select which models (individually or all) to include in the import operation.
Identifies the number of logical and physical designs that will be generated. To continue the import operation, click Finish, which displays the Compare Modeling Designs dialog box.
This dialog box is displayed if you click Import to import database connections in the Data Dictionary Import (Metadata Extraction) wizard.
File Name: Click Browse to find the XML file containing database connection definitions that have been exported from SQL Developer or Data Modeler.
Connections: Displays the names of database connections in the specified file.
Click OK to import the database connections.
This dialog box is displayed when you click File, then Import, then VAR File. You can import model definitions from a VAR file.
Import Single Model: Imports only a single model describing a logical or relational model.
Import Mapped Models: Imports a mapped model describing a logical model and a relational model, as well as the mappings between them.
Import Process Model: Causes the process model to be included in the import operation.
Select VAR Type: Type of VAR file: Sterling COOL:DBA V2.1, Sterling Bnsteam V7.2, or Cayenne Bnsteam V7.2.
This dialog box displays the properties of an index, including several types of "index" such as primary key or unique key. These are objects that can be defined on one or more table columns in Relational Models.
Name: Name of the index object.
Long Name: Long name for display purposes.
Engineer: Controls whether the index will be considered during reverse engineering operations. If this option is disabled, this index and its properties are not considered when the relational model is reverse engineered into the logical model
Table: Table containing the column or columns to be indexed.
State: State or purpose of the index: Plain Index, Primary Constraint, Unique Constraint, or Unique Plain Index.
Sort Order Columns: Displays the column names and their sort order in the index.
Index Expression: Indicates whether this is a function-based index, which is an index based on an expression.
Spatial Index: Indicates whether this is a spatial index (with INDEXTYPE of MDSYS.SPATIAL_INDEX).
Generate in DDL: Controls whether the index creation is included when DDL statements are generated to be used to create the database.
Displays columns that are available to be added to the index definition on the left, and columns that are included in the index definition on the right. You can select columns and use the arrow keys to move them from one side to the other.
Specification of the expression for a function-based index (if Index Expression is enabled under General properties).
Spatial properties for a spatial index.
Constrain to Layer Type: Constrains the index to a specified type of layer.
Geodetic Index: Indicates whether the index is on geodetic or projected data.
Number of Dimensions: Number of spatial dimensions to be indexed. Example: 2 for longitude and latitude
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box lets you view and modify information for an information store object, which is part of the Process Model.
Name: Name of the information store.
Synonym: Synonym for the information store.
Type: Where the data for the information store is stored: RDBMS for a relational database, File for an external file, Object for an object, or Temporary for temporary storage.
RDBMS Type: If Type is RDBMS, the database type (physical model) for the information store.
Object Type: If Type is Object, the object type.
Implementation Name: If Type is Object, the implementation name.
Scope: If Type is Temporary, the scope of the data: when the data is available (for example, Session or Application).
Lists the attributes associated with this information store. To view the properties of any listed attribute, double-click its entry.
Lists each entity and corresponding table associated with this information store. To view the properties of any listed entity, double-click its entry
Lists the processes associated with this information store. To view the properties of any listed process, double-click its entry.
Lists the information flows associated with this information store. To view the properties of any listed information flow, double-click its entry.
Description of the system objective for this information store.
Owner: Owner of the information store.
Source: Source of the information store: where the information for the information store comes from.
File Name: Name of the information store file.
Location: Location of the information store file.
File Type: Type of file: CSV (comma-separated values), fixed-length fields, Excel spreadsheet, or plain text.
Field Separator: Character (for example, comma) that separates fields.
Data Capture Type: Specifies whether the data capture is a full refresh or is limited to a specified type of capture operation.
Self Describing: Indicates whether the field is self-describing.
Skip Records: Number of records to be skipped at the top of the data file.
Text Delimiter: Text delimiter character that is used in text strings (single or double quotes).
Lists the external data elements currently defined for the external agent. To add an element, click the Add (+) icon; to delete an element, select it and click the Remove (X) icon; to view the properties of an element, double-click it or select it and click the Properties icon.
External Data: Name of the external data object.
Type: Logical type of the external data.
Starting Position: Starting position of the element in the data file.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box lets you view and modify information for an information structure object, which is part of the Process Model.
Name: Name of the information structure.
Synonym: Synonym for the information structure.
Lists the attributes associated with this information structure. To view the properties of any listed attribute, double-click its entry.
Lists each entity and corresponding table associated with this information structure. To view the properties of any listed entity, double-click its entry
Lists the information flows associated with this information structure. To view the properties of any listed information flow, double-click its entry.
Volume: Initial or current data volume for the information structure.
Growth Rate: Percent: Percent of growth expected in a time period specified in the next field. For example, if you expect growth of 5 percent each month, enter 5 in this field and select Month for the next field.
Growth Rate: Year/Month/Day: Time period associated with the expected growth rate.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the inheritance properties between a subtype entity and a supertype entity in a hierarchy (see Inheritances under Logical Model).
Name: Name of the inheritance relationship.
Long Name: Long name showing the relationship between the entities.
Supertype: Supertype entity in the relationship.
Subtype: Subtype entity in the relationship.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box is displayed when you view the properties of a join in a cube in a multidimensional model. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the join object.
Left Entity: Left entity in the join operation.
Right Entity: Right entity in the join operation.
Existing Relation:
Cardinality: Cardinality relationship between the left and right entities: 1:1 (one to one), 1:* (one to many), or *:1 (many to one).
Dominant Role: Entity with the dominant role.
Lists the left and right entity for each attribute pair. You can add and remove pairs. For each pair, you can specify the left and right entities.
This dialog box is displayed when you view the properties of a level in a multidimensional model.
For business analysis, data is typically summarized by level. For example, the database may contain daily snapshots of a transactional database. Days are the base level. You might summarize this data at the weekly, quarterly, and yearly levels. Thus, levels provide a convenient way of identifying the dimension members at a particular distance from the detail data.
For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the level. Examples: customer, product
Level Entity: Entity associated with this level. Example: customers in customers.customer
Value Based Hierarchy: Controls whether the hierarchy is value-based or level-based. (the latter being more common). If this option is enabled, a value-based hierarchy is used, in which the parent-child relations do not have named levels. If this option is disabled, a value-based hierarchy is used.
Root Identification: For a value-based hierarchy, specify one of the following: Parent is Null, Root has Value, or Parent has Value.
Default Attribute: Default descriptive attribute (if required).
Selection criteria for this level.
Selection Criteria Description
Description of the selection criteria for this level.
Displays any attributes that are keys for the level. To add a level key object, click the Add (+) icon; to remove a level key object from the level definition, select it and click the Remove (X) icon. To edit a level key object, double-click its item, or click its item and click the Properties icon.
Name: Name of the attribute.
Attribute: Fully qualified name of the attribute.
Indexed: Controls whether the attribute is indexed.
Slow Changing: Indicates whether this is a Slowly Changing Attribute; and if so, what type. None means it is not a Slowly Changing Attribute; and Type 1, Type 2, or Type 3 means it is a Slowly Changing Attribute of the specified type.
For a level with a value-based hierarchy, lists the attributes of the parent entity.
Lets you add calculated attributes to the level definition and remove them from the definition. For each calculated attribute, you can specify the associated expression.
Displays attributes of the level for Oracle Analytic Workspaces.
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Mylevels if the Short Name is Mylevel
Lets you specify the name and value columns for use with Microsoft OLAP.
Description of the level.
Description of the partitioning for the level.
This dialog box displays the properties of a location object, which is a type of Business Information object.
Name: Name of the location object.
Location Type: Descriptive phrase indicating the type of location object, using any naming scheme suited to your needs.
Address: Street address, in a format appropriate for the locale.
City: Name of the city or town.
Post Code: Postal code, in a format appropriate for the area or country.
Area: Part of the country, such as the two-character state abbreviation for a United States address.
Country: Country code or name.
Lists the contact objects currently associated with this email object. To view the properties of any listed contact object, double-click its entry.
This dialog box is used to specify a logical data type for a user-defined attribute.
Logical Type: Name of the logical type.
Size: Maximum size of the data for this type.
Precision: For a numeric type, the maximum number of significant decimal digits.
Scale: For a numeric type, the number of digits from the decimal point to the least significant digit.
Measure folders in the multidimensional model group measures together so that they can be identified and accessed easily. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the measure folder object.
Lists any relevant measures. To add a measure, click the Add (+) icon; to remove a measure from the measure folder definition, select it and click the Remove (X) icon. (See also Measure Properties.)
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Myfolders if the Short Name is Myfolder
This dialog box displays the properties of a measure in a multidimensional model.
Measures store the facts collected about your business, such as Costs or Units Sold. Each measure belongs to a particular cube, and thus shares particular characteristics with other measures in the cube, such as the same dimensions. The default characteristics of a measure are inherited from the cube.
For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the measure. Example: Sales
Is Formula: Controls whether the measure is defined by the formula specified in the Formula field. If you do not specify a formula, the function specified in the Aggregation Function field in used.
Custom Formula: Identifies whether the formula is a custom formula.
Formula: Formula if this is a formula-based measure.
Formula Type: Type of formula: none, Base, OLAP, or Microsoft-computed.
Based On Fact: Name of the fact associated with the measure.
Addivity: Fully-Additive (additive across all dimensions), Semi-Additive (additive across some dimensions), or Non-Additive.
Aggregation Function: Function to be used for aggregation.
Where Clause: WHERE clause limiting the aggregation.
Functions: Lists the aggregation functions and measure aliases. To add an aggregation function, click the Add (+) icon; to remove an aggregation function from the measure property definition, select it and click the Remove (X) icon. To set summary levels for a measure alias, select its item and click the Set Oracle AW Presummarized Levels icon.
For a measure based on an Oracle OLAP formula, specifies the OLAP operator and other information.
Short Name: Short descriptive name that can be used by applications instead of the long name. Example: Sales
Long Name: Long descriptive name, typically used for display. Example: Unit Sales
Plural Name: Plural name (for reporting purposes). For example: Mymeasures if the Short Name is Mymeasure
Description of the measure. Example: Unit sales measure
Measurements allow metrics to be defined for model objects, indicating the value of some object attribute. For example, they may be used to hold actual, estimated, or planned values for the size of a table, the number of rows in a table, the number of pages in an index, the number of different values in a column, and so on. This flexibility allows for product or project extensions, without changing the model.
Name: Name of the measurement object.
Comment: Optional descriptive comment text.
Notes: Optional note text, such as background information or implementation notes.
Value: Numeric value associated with the measure. Example: 10 if the measure is for 10 meters
Unit: Unit of measurement associated with the value. Example: Meter
Type: Type of value: Measure (measured), Estimate (estimated), Plan (planned), Minimum, Maximum, or Average.
Creation Date: The date when the measurement object was established.
Effective Date: The date when the measurement object is effective. For measured values, the effective and creation dates should be the same. For estimated actual values, the creation date may be later than the effective date. For planned values, the effective date is normally later than the creation date.
Summary: Displays read-only summary information.
This dialog box defines the properties of a method used to implement a structured data type.
Name: Name of the method.
Constructor: Controls whether a constructor is created for the method.
Overridden Method: The method that this method overrides (if any).
Return Value: NO RETURN if there is no return value, or the data type of the returned value.
Lists the name and data type of each parameter for the method.
To add a parameter, click the Add (+) icon; to delete a parameter select it and click the Remove (X) icon; to move a parameter up or down in the list, select it and click the appropriate arrow.
Code that implements the method.
The Business Information model has the following properties.
Name: Name of the business information model.
Visible: (Does not apply to this model.)
Data Flow Diagrams, which are part of the Process Model, have the following properties.
Name: Name of the data flow diagram.
Visible: Controls whether the data flow diagram is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the data flow diagram name in the object browser.
Displays any processes associated with the data flow diagram. To view or edit the Process Properties, select it and click the Properties icon. To move a process up or down in the order within the data flow, select it and use the arrow icons.
The Data Types Model has the following properties.
Name: Name of the data types model.
Visible: Controls whether the data types model diagram is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the data types model in the object browser.
The Logical Model has the following properties.
Name: Name of the logical model.
Visible: Controls whether the diagram for the logical model is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the logical model name in the object browser.
You can specify the following naming rules for entities, attributes, and views:
Max Name Length: Maximum number of characters in the name.
Character Case: Controls whether you can use only uppercase or lowercase characters, or both uppercase and lowercase (that is, mixed case).
Valid Characters: Specify either All Valid (no restrictions), or disable All Valid and then select the valid set of characters.
A multidimensional model has the following properties.
Name: Name of the multidimensional model.
Visible: Controls whether the multidimensional model diagram is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the multidimensional model name in the object browser.
The Process Model has the following properties.
Name: Name of the process model.
Visible: Controls whether the diagram for the process model is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the process model name in the object browser.
Relational Models have the following properties.
Name: Name of the relational model.
Visible: Controls whether the diagram for this relational model is displayed in the Data Modeler window. You can also control the visibility by selecting Show or Hide on the context menu after you right-click the relational model name in the object browser.
RDBMS Type: Type of database.
RDBMS Site: RDBMS site. You can select a site of the specified RDBMS Type. (RDBMS sites are explained in Section 1.3.6, "Physical Models".)
You can specify the following naming rules for tables, columns, and views:
Max Name Length: Maximum number of characters in the name.
Character Case: Controls whether you can use only uppercase or lowercase characters, or both uppercase and lowercase (that is, mixed case).
Valid Characters: Specify either All Valid (no restrictions), or disable All Valid and then select the valid set of characters.
This dialog box is displayed after you click Tools, then Name Abbreviations. You must specify a .csv (comma-separated values) file containing pairs in the following format: string-to-use, string-to-be-changed (with or without a space after the comma). In each pair, the second term is the spelling that is to be changed to the first term in names or parts of names (separated by underscores or spaces) in relational models of the current design after you click OK.
As an example, the following lines in a .csv file cause the strings CUS and CUSTOMER to be changed to CUST:
CUST, CUSTOMER CUST, CUS
For example, a column named customer_id would be changed to cust_id, and a column named cus_last_name would be changed to cust_last_name. (Thus, the resulting names are not necessarily "abbreviated"; they are just made consistent.)
Select a .csv File: Find the .csv file containing the comma-separated value pairs.
All Objects: Controls whether the name changes are applied to tables, columns, indexes, and views, or only to the types of objects that you specify.
Keep Letter Case: Controls whether the letter case of the current name is retained when the name string is changed. If this option is disabled, any spelling (case) of the name to be changed uses the case as specified in the pair in the .csv file. For example, if this option is disabled and if the string pair is CUST,CUSTOMER, a name of customer_first_name would be changed to CUST_first_name.
Note: Do not confuse "Name abbreviations" with naming standardization, which is wider in scope and is integrated with the checking of Design Rules. Naming standardization is implemented through Data Modeler user options, as explained in Section 1.5.2.5, "Naming Standard".
This dialog box is displayed when you attempt to add or edit a database connection for use in an import or export operation. For import operations from a data dictionary, you can connect to an Oracle database or a supported third-party database. For export operations, you can connect to an Oracle Database, for use as the Data Modeler reporting repository (which is explained in Section 1.8, "Data Modeler Reports").
When you have finished entering the connection information, test the connection, as explained in After Specifying the Connection Information.
Some of the following fields apply only to certain kinds of database connections.
Connection Name: An alias for a connection to the database using the information that you enter. (The connection name is not stored in the database, and the connection is not a database object.) Suggestion: Include the database name (SID) and user name in the connection name. Example: personnel_herman for connecting to the personnel database as user Herman.
User Name: Name of the database user for the connection. This user must have sufficient privileges to perform the tasks that you want perform while connected to the database, such as creating, editing, and deleting tables, views, and other objects.
Password: Password associated with the specified database user.
Save Password: If this option is checked, the password is saved with the connection information, and you will not be prompted for the password on subsequent attempts to connect using this connection.
The remaining fields are grouped under tabs according to the database type. See Oracle tab or Other databases (third-party) tabs.
The following information applies to a connection to an Oracle database.
Role: The set of privileges to be associated with the connection. For a user that has been granted the SYSDBA system privilege, you can specify a connection that includes the privilege.
Connection Type: Select Basic, TNS, or Advanced. (The display of fields changes to reflect any change in connection type.)
Host Name: Host system for the Oracle database.
Port: Listener port.
SID: Database name.
Service Name: Network service name of the database (for a remote database connection over a secure connection).
Network Alias: Oracle Net alias for the database. (The list for selecting a network alias is initially filled from the tnsnames.ora file on your system, if that file exists.)
Connect Identifier: Oracle Net connect identifier.
Custom JDBC URL: URL for connecting directly from Java to the database; overrides any other connection type specification. If you are using TNS or a naming service with the OCI driver, you must specify this information: Example:
jdbc:oracle:thin:scott/@localhost:1521:orcl
Note that in this example, the "/" is required, and the user will be prompted to enter the password.
To use a custom JDBC URL, the system on which Data Modeler is running must have an Oracle Client installation that contains the JDBC and orai18n libraries, is present on the path, and is version 10.2 or later.
Other databases (third-party) tabs
The following information applies to a connection to a third-party (non-Oracle) database.
Host Name: Host system for the database.
Port: Listener port.
Database: Database name.
JDBC-ODBC Bridge or Other Third Party Driver (JDBC ODBC Bridge tab): Indicates a JDBC to ODBC bridge driver or another third-party driver.
ODBC Alias (JDBC-ODBC Bridge): Name of an existing ODBC data source.
JDBC URL (Other Third Party Driver): URL for connecting directly from Java to the database; overrides any other connection type specification.
Driver Class (Other Third Party Driver): The name of the driver class that will be used for the connection (for example, com.microsoft.jdbc.sqlserver.SQLServerDriver). This name can be found in the JDBC driver specification (usually shipped with the driver).
After Specifying the Connection Information
To test the connection using the specified information, click Test Connection. A message is displayed indicating the result of the test.
To add the new connection or to complete any edits to an existing connection, click OK.
This dialog box displays the properties of a process object, which is part of the Process Model.
Name: Name of the process.
Synonym: Synonym for the process.
Sources Filter Condition: A filter for the data on the source level, using SQL valid in a WHERE clause (but without including the WHERE keyword). Example: dept_id = 'ENG'
Sources Join Condition: A join between two or more sources used in the process, using SQL valid in a WHERE clause (but without including the WHERE keyword). Example: table1.dept_id = table2.dept_id
Type: Type of process: Primitive (standalone), Composite (consisting of multiple outer processes, or Use transformation task (as specified in the next field).
Use Transformation Task: Select the transformation task to use.
Text for a short definition of the process.
Interactive/Batch: Mode: Batch, Interactive, Manual, or Unknown.
Minimum Acceptable Throughput: Batch Min. Transactions: For batch mode, minimum acceptable number of processing operations for each specified Minimum Acceptable Throughput Batch Time Unit. Example: 100 for 100 operations each hour.
Minimum Acceptable Throughput: Batch Time Unit: Unit of time for the specified minimum acceptable number of processing operations. Example: Hour for 100 operations each hour.
Longest Acceptable Response Time: Numeric unit of the longest acceptable response time. Example: 5 for 5 seconds.
Longest Acceptable Response Time Unit: Time measure unit of the longest acceptable response time. Example: Second for 5 seconds.
Expected Frequency Times: Number of times the process is expected to be used within each Expected Frequency Time Unit. Example: 50 for 50 times each day.
Expected Frequency Time Unit: Time measure unit for the Expected Frequency Times. Example: Day for 50 times each day.
Priority: Descriptive term for the priority of the process: Low, Medium, High, or None.
You can specify, for each day the process is run, either no peak periods (times with a high level or activity or demand) or one or more one-hour intervals.
Displays information structures associated with the process. To view the Information Structure Properties, double-click an information structure item or select the item and click the Properties icon.
Displays events associated with the process. Includes a separate area for flow events. To view the Event Properties, double-click an information structure item or select the item and click the Properties icon. To add an event, click the Add (+) icon; to remove an event from the process definition, select it and click the Remove (X) icon.
Displays flows coming into the process. To view the Flow Properties, double-click the flow item or select the item and click the Properties icon. (To add a flow, use the New Flow icon on the data flow diagram.)
Displays flows going out from the process. To view the Flow Properties, double-click the flow item or select the item and click the Properties icon. (To add a flow, use the New Flow icon on the data flow diagram.)
Displays attributes processed by the process. To view the Attribute Properties, double-click an attribute item or select the item and click the Properties icon.
Displays entities processed by the process. To view the Entity Properties, double-click an entity item or select the item and click the Properties icon.
Displays mappings between task input parameters and their sources.
Lets you specify, for each target element, the type of transformation: As it is, Derivation, Aggregation. Summarization, or Complex Formula. (Each Target Element matches an item from the Processed Attributes pane.)
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box is displayed when you click Tools, then RDBMS Site Administration. It lets you view RDBMS sites, add sites, and edit and remove sites that you added. You cannot remove or change the properties of any predefined sites. (For an explanation of RDBMS sites, see Section 1.3.6, "Physical Models".)
Lists currently defined RDBMS sites. If you select a site, its name and RDBMS type are displayed. To add a user-defined site, click Add, specify the name and RDBMS type, and click Apply; to remove a user-defined site, click its entry under RDBMS Sites and click Remove.
Lets you specify an external XML file containing RDBMS site definitions, after which its sites are displayed. If you select a site, its name and RDBMS type are displayed. To add a site, click Add, specify the name and RDBMS type, and click Apply; to remove a site, click its entry under RDBMS Sites and click Remove. To save in the XML file any changes that you have made in this dialog box, click Save.
This dialog box displays the properties of a record structure.
Name: Name of the record structure.
Displays external data objects associated with the record structure. To view the external data object properties, double-click an item or select the item and click the Properties icon. To add an external data object, click the Add (+) icon; to remove an external data object from the record structure definition, select it and click the Remove (X) icon.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a relation, which is part of the Logical Model.
Name: Name of the relation.
Long Name: Long name for display purposes.
Source: Source entity for the relation.
Name on Source: Text describing the role of the source entity in the relation (for example, "has"). This text is displayed in the logical model diagram if you select Show, then Labels from the diagram context menu.
Source Entity Synonym: Synonym for the source entity.
Source to Target Cardinality: Cardinality of source records to target records with the same key value: * for many, or 1 for one.
Source Optional: Controls whether the source entity in the relation must contain one or more instances. If this option is enabled, there can be zero source instances; if this option is disabled, one or more source instances are required.
Target: Target entity for the relation
Name on Target: Text describing the role of the target entity in the relation (for example, "any number of"). This text is displayed in the logical model diagram if you select Show, then Labels from the diagram context menu.
Target Entity Synonym: Synonym for the target entity.
Target to Source Cardinality: Cardinality of target records to source records with the same key value: * for many, or 1 for one
Target Optional: Controls whether the target entity in the relation must contain one or more instances. If this option is enabled, there can be zero target instances; if this option is disabled, one or more target instances are required.
Dominant Role: Entity with the dominant role.
Identifying: Controls whether this is an identifying relationship. When there is an identifying relationship between a parent entity and a child entity, when the relational model is generated, the following occurs in the child table: the foreign key to the parent becomes part of the primary key of the child. (In non-identifying relationships, the foreign key to the parent table is just another column in the child table and is not part of the primary key.)
Enables you to specify the relational models to which this relation should be propagated in forward engineering operations.
Engineer: Controls whether the relation is propagated to the specified Relational Design (model) during forward engineering operations.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
The Relational Models dialog box identifies two relational models to be compared and merged. This box is displayed if you click Tools, then Compare/Merge Models.
From: Source relational model to be merged into the destination model.
To: Destination relational model into which objects from the source relational model are to be merged.
Database Type: Select the Oracle physical model whose data types are to be used.
View Compare Mapping: Displays the Compare Mapping dialog box.
When you click OK, the Compare Models dialog box is displayed, in which you can apply a filter to restrict the types of objects and specific objects to be merged.
This dialog box is displayed if you click Manage under Templates when generating a report (described in Generating Reports as RTF, HTML, or PDF Files). Use this dialog box to create, edit, delete, and save report templates, which let you customize the types of objects to be included in a report.
Templates: Lists report templates that have been created.
To create a new template click Add. To edit a listed template, select it and click Edit. To deleted a listed template, select it and click Remove. To save a template after making any desired edits, click Save.
Template Name: Name for the template. Suggestion: Choose a meaningful name, such as Columns_and_Comments or Foreign_Keys_All (if you select Foreign Keys - Referred From and Foreign Keys - Referring To).
Columns, Column Comments, Constraints, Foreign Keys - Referred From, Foreign Keys - Referring To, Indexes: Select (check) the types of objects to be included in this template.
This dialog box displays the properties of a resource locator object, which is a type of Business Information object.
Name: Name of the resource locator object.
URL: Uniform Resource Locator, if the resource locator is a Web address.
A resource locator object can have multiple contact objects associated with it, with the contact objects in an order that can indicate the level of responsibility for the resource. For example, if two contacts are listed for a URL, the first one listed might be the primary webmaster.
This dialog box displays the properties of a responsible party object, which is a type of Business Information object.
Name: Name of the responsible party object. Examples: a person's name, a role (such as Project Leader), or a department (such as Quality Assurance).
Responsibility: Brief description of the nature of the responsibility. Example: "Overall project management"
A responsible party object can have multiple contact objects associated with it, with the contact objects in an order that can indicate the sequence in which to attempt to contact the party. For example, if the office, mobile, and home contacts are listed in that order, that may mean that the responsible party should be called first at the office, then on his or her mobile phone, and finally at home.
This dialog box displays the properties of a role object, which is part of the Process Model.
Name: Name of the role.
Synonym: Synonym for the role.
Description: Description of the role.
Lets you add, delete, and edit processes associated with the role.
Lets you view and modify entities associated with the role and operations permitted on that entity (create, read, update, delete) by the role.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a rollup link in a multidimensional model. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
This dialog box displays the properties of rule set that is selected on the Rule Sets tab of the Design Rules dialog box. To specify design rules to be included in this rule set, select the desired rules and move them from the All Rules column into the Selected Rules column.
This dialog box displays the properties of a database schema, which can be associated with tables and other objects in Relational Models. If you associate a relational model object with a schema, the schema name appears in diagrams and it is used during DDL generation.
Name: Name of the database schema.
For tables, views, and indexes, All (available) objects of that type and Selected objects of that type are displayed. To associate an object with the schema, select it under All and click the Add (right-arrow) icon to move it to the Selected column. To remove an association, select it under Selected and click the Remove (left-arrow) icon to move it to the All column.
Comment text to be included in database objects that are generated based on this modeling object.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents
This dialog box is displayed if you click File, then Import, then DDL File to import definitions from one or more data definition language (DDL) files into a relational model. To add a file to the list to be imported, click the Add DDL Files (+) icon; to remove a file from the list, select it and click the Remove DDL Files (X) icon.
Import to: Name of the relational model into which to import the definitions in the specified file or files.
Swap Target Model: This option (if available) determines which definitions are merged into which definitions, and which model appears in the left and right panes of the Relational Models dialog box for merging (if that box is displayed). For the ensuing import and merge operation, if this option is enabled, a script is generated in which your current relational model is merged into the specified database (DDL files); but if this option is not enabled, the definitions in the imported files are merged into your relational model.
Skip Merge Dialog: If this option is enabled, the Relational Models dialog box is not displayed before the import operation occurs.
This is a standard box for selecting a file for an operation: use Location to navigate to the folder in which to save or open the file, then select or specify the file name (including any extension) and, if necessary, the file type.
This dialog box is used to specify, for entities or tables in a multidimensional model, the classification type for each: Fact, Dimension, Logging, Summary, or Temporary.
You can specify colors to be used in diagrams for each classification type in the Diagram: Classification Types user preferences.
This dialog box is used to specify the data type for a user-defined attribute. Select the category for this type (Logical, Distinct, Collection, or Structured), then select the specific type within that category.
If you specify Logical Type and click the displayed type, the Logical Type dialog box is displayed.
Reference: For a structured type, controls whether the type is created as a REF (reference). A REF is a logical pointer to a row object that is constructed from the object identifier (OID) of the referenced object and is an Oracle built-in data type. REFs and collections of REFs model associations among objects, particularly many-to-one relationships, thus reducing the need for foreign keys.
This dialog box displays the properties of a slice of a cube in a multidimensional model. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the slice.
Read Only: Controls whether the data in the slice is read-only.
Calculated measures can add information-rich data to a cube. The data set is calculated on the fly, so no data is stored. You can add as many calculated measures as you like without increasing the size of the database.
Lists any dimension/hierarchy/level combinations for the slice. To add a level, click the Add (+) icon; to remove a level from the slice definition, select it and click the Remove (X) icon. (See also Level Properties.)
Lists any dimensions for the slice. To add a dimension, click the Add (+) icon; to remove a dimension from the slice definition, select it and click the Remove (X) icon. (See also Dimension Properties.)
Lists any attributes and their mappings for a specified entity.
Lets you specify one or more selection criteria (name, WHERE clause, and other details for each).
Short Name: Short descriptive name that can be used by applications instead of the long name.
Long Name: Long descriptive name, typically used for display.
Plural Name: Plural name (for reporting purposes). For example: Myslices if the Short Name is Myslice
Lists any relevant SQL Access to Oracle Analytic Workspaces (AW) objects. To add a SQL Access to Oracle AW object, click the Add (+) icon; to remove a SQL Access to Oracle AW object from the slice definition, select it and click the Remove (X) icon. To edit a SQL Access to Oracle AW object, double-click its item, or click its item and click the Properties icon. (See also SQL Access to Oracle AW Properties.)
Description of the slice.
Displays the properties of the spatial column or columns in a spatial table. The properties correspond to attributes and options for the SDO_GEOMETRY type, which is documented in Oracle Spatial Developer's Guide.
Name: Name of the spatial definition object.
Spatial Column: Name of the spatial column.
Use Function: Identifies whether a function is used to compute the column value.
Function Expression: Function expression if Use Function is enabled.
Coordinate System ID: Oracle Spatial SRID value. Example: 8307 for the WGS 84 longitude/latitude system that uses the Greenwich prime meridian.
Create Spatial Index: Controls whether a spatial index is created.
Spatial Index Name: Name for the spatial index.
Dimensional Information: For each dimension, specify the name, lower and upper boundaries, and the tolerance. Example: Name = longitude, Low boundary = -180, Upper boundary = 180, Tolerance = 10 (for 10 meters).
This dialog box displays the properties of a SQL Access to Oracle Analytic Workspaces (AW) object in a multidimensional model. For more information about working with multidimensional data, see Oracle OLAP User's Guide and the online help for Analytic Workspace Manager.
Name: Name of the object.
AW Name: Analytic workspace where the source data is stored.
Include GIDs: Controls whether the grouping ID for each dimension member is included.
Use Object Types: Controls whether the next two fields (Object Type Name and Table Type Name) are accessible.
Object Type Name: Name of the object type.
Table Type Name: Name of the table type.
Use Model Clause: Controls whether the Include RowToCell default statement will be included in the SQL statement.
Include RowToCell: Controls whether the Use Model Clause default statement will be included in the SQL statement.
SQL Statements: Displays a dialog box in which you can view, modify, and change the order of attributes, and also see the SQL statement that reflects the current specifications. On the SQL Statement tabs in this box, the Show Formatted Limit Map option enables dimension information to be formated (divided over several lines).
Lists any dimensions associated with the object. For each dimension, you can specify predefined attributes and hierarchies. To add a dimensions and attributes item, click the Add (+) icon and select the elements to be included; to remove a dimensions and attributes item from the object definition, select it and click the Remove (X) icon.
Calculated measures can add information-rich data to a cube. The data set is calculated on the fly, so no data is stored. You can add as many calculated measures as you like without increasing the size of the database.
Description of the SQL Access to Oracle AW object.
This dialog box defines properties of an attribute of a structured data type.
Name: Name of the attribute.
Datatype: Data type of the attribute.
Mandatory: Controls whether a value will be required in all columns that are based on this data type.
This dialog box is displayed when you create a new data type or edit a structured type listed in the display for Data Types.
Name: Name of the structured type.
Super Type: If this is a subtype, name of its supertype.
Final: Controls whether objects of this type can be inherited from in the definition of another type. If this option is enabled, this type cannot be inherited from (it cannot be a supertype in a type definition).
Instantiable: Controls whether objects of this type can be created. If this option is enabled, objects of this type can be created.
Lists the attributes currently defined for the structured type. The properties for each attribute include its name and data type.
To add an attribute, click the Add (+) icon; to delete an attribute, select it and click the Remove (X) icon; to move an attribute up or down in the list, select it and click the appropriate arrow; to view the properties of an attribute, double-click in the cell to the left of the name.
Lists the methods currently defined for the structured type.
To add a method, click the Add (+) icon; to delete a method, select it and click the Remove (X) icon; to move a method up or down in the list, select it and click the appropriate arrow; to view the properties of a method, double-click its name.
Use this dialog box to add a versioning property for the currently selected file or folder.
Use this dialog box to bring a new file under Subversion control.
Files List: Lists the names and physical locations of the files that will be added to Subversion.
Use this dialog box to apply a previously generated patch. A patch must be applied to the same revision/tag from which it was generated.
The name and location are displayed for the project or set of files to which the patch will be applied.
Patch Source: Specify where the patch will be obtained from: the system clipboard or a file.
This dialog box is displayed when you right-click a remote directory in the Subversion repository and select Branch/Tag. Create a branch by copying the current working copy or a revision from the repository to a selected location in the repository.
From: Location of the working copy or revision.
Working Copy: Causes the current working copy to be copied.
HEAD Revision: Causes the HEAD revision (the latest revision in the repository) to be copied.
Use Revision: Causes the revision specified in the text box to be copied. To see a list of revisions from which you can choose, click List Revisions.
To: Destination location.
Comment: Optional descriptive comment.
Switch to new branch/tag: If this option is checked, the existing working copy is switched to the new branch.
After you click OK, the SVN Console - Log pane is displayed at the bottom, with messages about commands that were executed.
Use this dialog box to check out modules from a Subversion repository, to create the initial local copies of files and folders that are being stored within a Subversion repository. It is these local copies, stored outside the Subversion repository, that you work on. This location and the files within it constitute the Subversion "working copy".
Note: With Subversion, there is no "check in" procedure, so you do not check in files that you have updated and check them out again when you next want to work on them. Instead, when you have finished working on your local copies of files, you commit them to the Subversion repository to bring the files held there up to date. Also, if you want to incorporate into your local copies changes that other developers have committed to the Subversion repository, you update them.
Destination: Directory or folder into which to place the checked out files. If this destination is not empty, a warning message will be displayed asking if you are sure you want to check out into this directory. (Attempting to check out files into a non-empty destination might reflect a mistake in specifying the destination, or it might be your intention.)
Use Revision: If this option is checked, the revision you specify in the text box is used. To see the available revisions, click the binoculars icon.
Depth: The level of recursion for selecting files to be checked out, from Infinity (all children at all levels under the selected item in the Versioning browser hierarchy) through Empty (only this item and no children).
Use this dialog box to commit individual files to the Subversion repository. If a file is a child of a changed parent that has not been committed, you must either first commit the parent or instead commit the working copy.
The committed files will replace those in the repository as the most recent. Other developers who subsequently check out or update from these files will see the file changed in comparison with the previous version held in the repository.
Files List: Lists the names and physical locations of the files that will be committed to the Subversion repository.
Keep Locks: Retains the locks that you previously obtained on the files that you are about to commit. This will mean that other developers will still not be able to commit changes they may have made to the files.
Comments: Comments to accompany the commit action. You will later be able to see these comments when viewing the list of versions of a particular file.
Use this dialog box to commit the working copy to the Subversion repository. The committed files will replace those in the repository as the most recent. Other developers who subsequently check out or update from these files will see the file changed in comparison with the previous version held in the repository.
Files List: Lists the names and physical locations of the working copy that will be committed to the Subversion repository.
Keep Locks: Retains the locks that you previously obtained on the files that you are about to commit. This will mean that other developers will still not be able to commit changes they may have made to the files.
Comments: Comments to accompany the commit action. You will later be able to see these comments when viewing the list of versions of a particular file.
This dialog box is displayed if you attempt to check out from the repository root, as opposed to from the branches, tags, or trunk of the repository. To proceed with the checkout from the root, click Yes; to cancel this request, click No.
Skip This Message Next Time: If you enable this option, on future requests to check out from the repository root, this dialog box will not be displayed and the operation will proceed as if you had clicked Yes.
Use this dialog box to create a remote directory for a connection in a Subversion repository.
Directory Name: Directory name to be associated with the specified URL.
Comments: Optional descriptive comment.
This information applies to creating a Subversion repository. A connection to the repository will be created automatically. For information about Data Modeler support for versioning and Subversion, see Section 1.9.
Repository Path: Location for the new Subversion repository. You can Browse to select the location.
File System Type: Data storage system type for the repository. For information about choosing a system, see "Version Control with Subversion" at http://svnbook.red-bean.com/.
Native: The file system type being used by the operating system.
Berkeley DB: Causes a Berkeley DB database to be used as the data storage system.
Connection Name: Name for this connection. If you leave this box blank, the connection will be given a name based on the URL of the repository location.
This information applies to creating or editing a Subversion connection. For information about Data Modeler support for versioning and Subversion, see Section 1.9.
Repository URL: Full, valid URL for the location of the Subversion repository. The following are URL schemas and the access methods they map to:
file:/// -- Direct repository access (on local disk)
http://-- Access via WebDAV protocol to Subversion-aware Apache server
https:// -- Same as http://, but with SSL encryption
svn:// -- Access via custom protocol to an svnserve server
svn+ssh:// -- Same as svn://, but through an SSH tunnel
Connection Name: Name for this connection. If you leave this box blank, the connection will be given a name based on the URL of the repository location.
User Name: User name known to the repository, if the repository requires user and password validation.
Password: Password for the specified user, or blank if a password is not required.
Test Read Access: Attempts to establish a connection for read access to the Subversion repository.
Status: Displays the result of the test (success or an error message).
Use this dialog box to delete the selected resources (such as a file or directory) in the repository.
Comments: Comment explaining the deletion.
This dialog box is displayed if you click Edit "server" in the Versioning: Subversion: General preferences pane. You can modify the Subversion configuration file directly.
Reset: Discards any changes that you have made and leaves the dialog box open.
To save any changes and close the box, click OK; to discard any changes and close the box, click Cancel.
Use this dialog box to copy files from the Subversion repository to a local file system directory, or to copy working copies to a local file system directory.
Working Copy Path: The location of the files that will be copied for export. Only files that are under Subversion control will be exported.
Destination Path: A path that includes the directory where you want the files to be copied to.
Use this dialog box to export the details of one or more current Subversion connections to a file. The details can subsequently be imported from the file to re-create the connections.
File Name: The location and name for the file that will contain the connection details, or browse to a file/location using the Browse button.
Connections: Select one or more connections whose details will be exported.
This dialog box displays version history information about Subversion files.
Use this dialog box to mark a file, or a pattern that identifies common file names, as content that Subversion should ignore. (This dialog box sets the svn:ignore property for the specified content.)
Often, a directory contains files that should not be kept under version control. For example, log files from a debug or batch operation do not need to be tracked or merged, yet they are often in the same directory as the shared code for a project. Such files should be marked to be ignored by Subversion.
Use this dialog box to import the details of Subversion connections from a previously created file.
File Name: The location and name for the file that contains the connection details, or browse to a file/location using the Browse button.
Connections: Select one or more connections whose details will be imported. If a connection to be imported already exists with the same URL, you will be asked to confirm whether you want to overwrite the existing connection details with the details in the imported connection.
Use this wizard to import source files into the Subversion repository To go from one step to the next, click Next; to go back to the previous step, click Back.
Use to identify the Subversion repository, and directory within the repository, where the imported files will be stored.
Repository Connection: The connection for the Subversion repository in which you wish to store the imported files.
Path: The directory within the Subversion repository for storing the imported files.
Source Directory: The directory containing the source files that you want to import into Subversion. Initially contains a path based on the item that was selected when you launched the wizard.
Comments: Comment text to accompany the imported files. The comments are recorded with the files in the Subversion repository and will be viewable with the version history of the files. You must enter some comment text; otherwise, an error will occur when you click Finish to attempt to perform the import operation.
Filters that will be applied to the import operation. If you do not want one or more of the filters to be applied, move them from Selected Filters to Available Filters using the left arrow keys. If necessary, you can use the right arrow keys to move filters from Available Filters to Selected Filters.
New: Displays a dialog box in which you can create a new filter that will be applied to the import operation. New filters are added to the Selected Filters list.
You can configure options specific to the import operation.
Do Not Recurse: If this option is enabled, it prevents files being imported from directories subordinate to the one you identified on the Source page.
Perform Checkout : If this option is enabled, the imported source files will be checked out after import.
Displays the selected options for the import operation. To make any changes, click Back. To perform the operation, click Finish.
Use this dialog box to perform a Subversion lock operation on one or more checked out files (working copies).
Files List: Lists the names and physical locations of the files to be locked. You can individually select and deselect files.
Steal Lock: Breaks any existing locks and relocks the files for your use. Causes the --force option to be added to the underlying svn lock command.
Comments: Comments to accompany the action.
A merge operation copies changes made in one branch to another branch, or copies changes from a branch to the trunk (main line of development). It is typically used to bring another developer's work into your own files, and to merge private development back into the main line of development.
The merge is created by comparing the content of two revisions within the Subversion repository, and applying the differences to a Subversion working copy. If you subsequently wish to use the result of the merge in the main line of development, you commit the working copy to the Subversion repository in the usual way.
Specify the following:
Merge Type: Merge Selected Revision Range, Reintegrate a Branch, or Merge Two Different Trees.
Merge Resource
Merge Options
Your selection for Merge Type affects the content of subsequent displays, which can include the following.
From URL and its (start) revision to merge: The resource that is the basis of the comparison. (The resource entered in the To URL box will be compared against the resource entered here.)
HEAD Revision from Repository: Causes the comparison to be made against the most recently committed resources in the Subversion repository.
Use Revision: Causes the comparison to be made against a resource in the Subversion repository with a particular revision number. When selected, the accompanying text box becomes available. You can then enter a revision number into the text box, or click the List Revisions button to select the revision that you require.
To URL and its (end) revision to merge: The resource that will be compared with the base resource selected in the From URL box.
Same as "From" URL: Uses the same base repository location for both elements of the comparison.
Ignore Ancestry: Ignores any relationships between resources in the Subversion repository when comparing the start and end revisions. The effect of this will be to retain resources that have names identical to those they are being compared with, even though the resources have no common ancestry. The alternative is that a resource that predates an identically named one may be deleted and replaced with the later resource.
Dry Run: Causes the comparison to be performed without the changes being applied to the Subversion working copy. The results of the comparison are displayed in the Messages - Log window.
This window shows files that have been added, modified or removed, either locally or remotely; files whose content conflicts with other versions of the same file; and files that have not been added to source control. This window is opened automatically when you first initiate an action that changes the local source control status of a file. You can also open this window manually.
The window shows any outgoing changes (files that have been added, modified or removed locally, and local files whose content conflicts with remote files), candidates (files that have been created locally but not yet added to source control), and incoming changes (files that have been added, modified or removed at a remote location).
This dialog box is displayed if you right-click a node under a connection in the Versioning navigator and select Properties. It displays properties and property values for the selected object.
Use this dialog box to begin the process of removing the listed files from the Subversion repository.
After you have clicked OK, the listed files will appear on the Outgoing tab of the Pending Changes window. The files will be removed from the Subversion dialog when you next commit the individual files or the working copy that they are part of.
Use this dialog box to select the location of a Subversion repository when using the branching, merging, and switching facilities. Locations in this dialog are shown as directories and objects. The chosen location is ultimately returned from this dialog as a URL.
Repository Connection: If the required location already exists, select it from the browser tree.
To create a new location, navigate to a parent directory, then select the Create New Remote Directory icon. This opens a dialog box that will show the location of the parent object (in the form of a URL) and let you name a directory beneath that one that will become the new location.
Use this dialog box to revert files to their previous state.
If the contents of a file have been changed, the file will be reverted to its base revision. If a file has been added but not yet committed, it will revert to unadded status. If a file is scheduled for removal (in the Pending Changes window), it will be added back to the navigator and given its previous status
Files List: Lists the names and physical locations of the files that will be reverted.
Recursive: Select if you want the revert operation to recurse into child objects of those selected.
Use this dialog box to update the current working copy of the specified file from the specified repository and revision.
From URL: Full URL for the repository location associated with the current working copy.
To URL: Full URL for the repository location to use to update the current working copy.
HEAD Revision: Causes the HEAD revision (the latest revision in the repository) to be used for the update operation.
Use Revision: Causes the revision specified in the text box to be used for the update operation. To see a list of revisions from which you can choose, click List Revisions.
Use this dialog box to perform a Subversion unlock operation on one or more locked, checked out files (working copies).
Files List: Lists the names and physical locations of the files to be unlocked. You can individually select and deselect files.
Force Unlock: Breaks any existing locks and unlocks the files. Causes the --force option to be added to the underlying svn unlock command.
Use this dialog box to incorporate into your local copies changes that other developers have committed to the Subversion repository.
Files List: Lists the names and physical locations of the files that will be updated with content from the Subversion repository.
Use Revision: Updates the files with content from a particular revision within the Subversion repository. Enter the revision number in the adjacent text box. If not selected, the files will be updated from the HEAD revision.
Ignore Externals: Select if you do not want the update operation to apply to external working copies created as the result of externals definition handling. Externals definitions are used to pull data from multiple repositories. See the Subversion documentation for details.
Recursive: Deselect if you do not want the update operation to recurse into child objects of those selected.
Use this dialog box to update individual files with content from the Subversion repository.
Files List: Lists the names and physical locations of the files that will be updated with content from the Subversion repository.
Use Revision: Updates the files with content from a particular revision within the Subversion repository. Enter the revision number in the adjacent text box. If not selected, the files will be updated from the HEAD revision.
Ignore Externals: Select if you do not want the update operation to apply to external working copies created as the result of externals definition handling. Externals definitions are used to pull data from multiple repositories. See the Subversion documentation for details.
Recursive: Deselect if you do not want the update operation to recurse into child objects of those selected.
This dialog box displays general and versioning information about the currently selected file or folder.
Use this dialog box to resolve conflicts when there are conflicts in the values for certain properties.
Filter: Lets you control the list of properties displayed.
Consider "Changed Time" Property: If this option is enabled, two properties with identical content but different timestamps for the last change are considered to be different and thus potentially in conflict. If this option is not enabled, creation timestamps are ignored in comparing properties.
Details tab: For each property, shows the property name, a Selected box indicating whether it is to be merged if you click Merge, and the values for the property in the left and right columns shown at the top of the box.
Merge: Merges the selected property definitions
Close: Closes the dialog box without performing a merge.
This dialog box displays the properties of a subview. (See also Section 1.3.4.1, "Logical Diagram and Subviews" and Section 1.3.5.1, "Relational Diagram and Subviews".)
Name: Name of the subview.
Visible: Controls whether the subview diagram is displayed in the Data Modeler window. You can also control the visibility by selecting Show Diagram or Hide Diagram on the context menu after you right-click the subview in the object browser.
This dialog box displays the properties of a table, which is part of Relational Models.
You can click Naming Rules to apply the current naming rules to specified types of objects related to this table definition. For example, if you applied naming rules to Check Constraints and if a table-level constraint was named PRODUCTS_Check, the name would be changed to PRODUCTS_CK (if the table name was PRODUCTS).
Name: Name of the table.
Long Name: Long name in the form: relational-model-name:table-name
Engineer: Controls whether the table will be considered during reverse engineering operations. If this option is disabled, this table and its properties are not considered when the relational model is reverse engineered into the logical model.
PK Name: Name of the primary key of the table.
Type: Classification type, from the list defined in the General Options. Examples: Fact, Dimension, Logging, Summary, Temporary.
Temp Table Scope: For a table classified as Temporary, you can specify a scope, such as Session or Dimension.
Register as Spatial Table: For a table with a column of type SDO_GEOMETRY, creates the spatial index and inserts the appropriate entry in the USER_SDO_GEOM_METADATA view.
Allow Type Substitution: For a structured type with Reference disabled, or for a structured type applied to a table, controls whether a substitutional structured type generation in the DDL is allowed.
Details tab
Lists the columns currently defined for the table. The properties for each column include its name and data type, and whether it is the primary key (PK), a foreign key (FK), or a required field (M, for mandatory).
To add a column, click the Add (+) icon; to delete a column, select it and click the Remove (X) icon; to view the properties of a column, double-click in the cell to the left of the name.
Overview tab
Lists each column, its data type, and if it is a primary key, foreign key, or mandatory.
Security tab
Lists each column and any relevant security-related properties for each: whether it contains personally identifiable information (PII), contains sensitive information, or should be masked when displayed.
Shows the current primary key (if any) of the table, and lets you change the primary key.
Lists any unique constraints. You can add, modify, and delete unique constraints. For each constraint, specify the column whose values must be unique or multiple columns that must have unique combinations of values.
Lists the indexes currently defined for the table. The properties for each index include its name, its state, and whether to generate the index when the table is created.
To add an index, click the Add (+) icon; to delete an index, select it and click the Remove (X) icon; to view the properties of an index, double-click in the cell to the left of the name.
Lists any table-level constraints that are defined by a validation rule (an expression that must evaluate to true for the data to be valid).
Lists the foreign keys currently defined for the table. The properties for each key include its name, its parent table, its delete rule, and whether to generate a foreign key constraint for it when the table is created.
To add a foreign key, click the Add (+) icon; to delete a foreign key, select it and click the Remove (X) icon; to view the properties of a foreign key, double-click in the cell to the left of the name.
For each column based on a structured data type that has attributes, lists each attribute (in column-name.attribute-name format). For each attribute, you can specify whether it is the primary key (PK), a foreign key (FK), or a required field (M, for mandatory).
Displays any OID (object identifier) settings and primary key columns based on a structured type.
OID Is Primary Key: Indicates whether the OID is the primary key of the table.
User Defined or System Generated: Indicates whether the OID is user-defined or generated by the database system.
PK Columns for Table Based on Structured Type: Displays the column name and data type for primary key columns that are based on a structured type.
Volumes: Minimum: Minimum data volume for the table.
Volumes: Expected: Expected or typical data volume for the table.
Volumes: Maximum: Maximum data volume for the table.
Growth Rate: Percent: Expected growth rate percentage for the table, for each period as specified in the next field.
Growth Rate: Year/Month/Day: The period (year, month, or day) to which the expected growth rate applies.
Normal Form: The required normal form (database normalization) for the table: None, First, Second, Third, or Fourth.
Adequately Normalized?: YES indicates that the model is sufficiently normalized. NO indicates that the model is not sufficiently normalized, and that additional normalization may be required on the relational model.
Displays any currently defined Oracle Spatial properties, each being a data column (type SDO_GEOMETRY or a function that evaluates to an SDO_GEOMETRY object) in the table. You can double-click an item's name to display its Spatial Definition Properties.
Displays information about column groups, which can be used to group related columns for possible use in generating a user interface. For example, a column group named Name could include columns first_name and last_name, and a column group named Address could include columns street_address, city, state, and postal_code.
To add a column group, click the Add (+) icon, specify the column group name, select the desired columns and move them to the right side, and optionally enter descriptive text in the Notes box; to delete a column group, select its entry and click the Remove (X) icon.
Comment text to be included in database objects that are generated based on this modeling object.
Enables you to specify scripts to be run automatically at specified times or stages: before the table is dropped or renamed, before the table is created, after the table is created, and at the end of any script specified for the table.
Include into DDL Script: Controls whether the text of the specified scripts is included into the DDL script for operations on the table.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
Creates views based on tables in a selected relational model. This dialog is displayed if you click Tools, then Table to View Wizard.
The tables in the selected relational model are displayed. Select all tables or a subset, optionally specify any naming rule, and click Generate. A view is created for each selected table. Each view selects all columns from the table, although you can later modify the view definition as needed. By default (if no Naming Rule is specified), each view name is its associated table name, prefixed with V_. For example, if a table name is BOOKS, the associated view name by default will be V_BOOKS.
Naming Rule: Displays any variables (relational model name or table name, or both in the specified order) that will be prefixed to the view name instead of V_. To display a dialog box for selecting variables for the naming rule, click Add Variable. For example, assume that the relational model name is Library and the table name is BOOKS:
If you specify only table name, the name of the generated view will be BOOKS. That is, all views will have the same name as their associated tables.
If you specify only model name, the name of the generated view will be Library. You should probably not choose this option, because all views will have names starting with the model name and jv1, jv2, and so on added to names after the first one.
If you specify model name and table name, the name of the generated view will be LibraryBOOKS.
This dialog box displays the properties of a telephone object, which is a type of Business Information object.
Name: Name of the telephone object.
Phone Number: Telephone number, in any format appropriate for your needs. For example, you may want to include the country code for international dialing.
Phone Type: Type of phone, in any format appropriate for your needs. Examples: Mobile, Office, Home.
Lists any relevant contacts. To view the properties of a contact, double-click its name. (See also Contact Properties.)
This dialog box displays the properties of a transformation package object, which is part of the Process Model and is described in Section 1.3.3.2, "Transformation Processes and Packages".
Name: Name of the transformation package.
Comment: Optional descriptive comment text.
This dialog box displays the properties of a transformation task object, which is part of the Process Model.
Name: Name of the transformation task.
Comment: Optional descriptive comment text.
Visible: Controls whether the transformation task is displayed in the Data Modeler window.
Displays all sources and selected sources side by side, and lets you select items and use the arrow icons to move items from one side to the other.
Displays all targets and selected targets side by side, and lets you select items and use the arrow icons to move items from one side to the other.
Displays the primary transformation for the transformation task. To view the properties of the primary transformation, double-click its name. (See also Transformation Properties.)
This dialog box displays the properties of a transformation, which is part of the Process Model.
Name: Name of the transformation.
Synonym: Synonym for the transformation.
Sources Filter Condition:
Sources Join Condition:
Primary: Controls whether this is the primary transformation for the associated transformation task.
Lists any relevant information structures. To view the properties of an information structure, double-click its name. (See also Information Structure Properties.)
Lists any attributes processed by the transformation. To view the properties of an attribute, double-click its name. (See also Attribute Properties.)
Lists any entities processed by the transformation. To view the properties of an entity, double-click its name. (See also Entity Properties.)
Displays any targets and sources for the transformation. For each target element, includes the type of transformation: As it is, Derivation, Aggregation. Summarization, or Complex Formula.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a transformation flow, which is part of the Process Model.
Name: Name of the transformation flow.
Synonym: Synonym for the transformation flow.
Source: Click to display the input parameters.
Destination: Click to display the Transformation Properties of the associated transformation.
Logging Flow: Controls whether the flow is specifically for logging operations. Creating a separate logging flow might simplify keeping track of information.
Operations: Specifies types of operations that the transformation flow can perform (create, read, update, delete).
Lists any relevant information structures. To view the properties of an information structure, double-click its name. (See also Information Structure Properties.)
Lists any relevant external data objects. To view the properties of an external data object, double-click its name.
Description of the system objective for this transformation flow.
Comments, Notes, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box is displayed when you click Tools, then Types Administration. It enables you to manage the mappings between logical data types and native data types for specific supported database products, and to add and remove logical types.
For each logical type, you can select the type in the list on the left to view its mappings to a type in each supported database product.
To add a logical type and specify its mappings, click Add. To delete a logical type, select the type and click Remove. To modify the mappings for a logical type (predefined or user-defined), select the type, click Modify, and specify the mapping information for any desired database products.
For each supported database product, you can view the mappings between its native types and Data Modeler logical types.
Creates domains based on data types in the selected models (logical, relational, or a combination). This dialog is displayed if you click Tools, then Types to Domains Wizard.
This wizard provides a convenient way to generate domains based on the types associated with attributes of entities in the logical model and columns of tables in relational models.
If you later want to edit or delete any of the generated domain definitions, you can do so using the Domains Administration dialog box.
Create New Domains: Controls whether existing domain definitions are overwritten if a generated new domain has the same name as an existing domain. If this option is enabled, those existing domain definitions are overwritten; if this option is not enabled, existing domains are not overwritten if the generated new domain would have the same name.
This dialog box displays the properties of a candidate key, which is an object defined in the Logical Model.
Name: Name of the key.
Synonym: Synonym for the key.
Long Name: Long name for display purposes.
State: State or purpose of the key: Primary Key or Unique Key.
Displays attributes and relations that are available to be added to the key definition on the left, and attributes and relations that are included in the index definition on the right. You can select attributes and relations and use the arrow keys to move them from one side to the other.
Enables you to specify the relational models to which this key should be propagated in forward engineering operations.
Engineer: Controls whether the key is propagated to the specified Relational Design (model) during forward engineering operations.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
This dialog box displays the properties of a view, which is part of Relational Models.
Name: Name of the view.
Query Builder: Click to display a query builder interface, in which you can create a view from the query by specifying tables and columns, as well as other information. In the query builder:
You can drag and drop tables into the main area; click to select columns to be included; view, copy, and paste the query SQL; and edit the SQL, or make it read-only reflecting the main diagram.
Filter Metadata Objects by Diagram makes it easier to find objects when there are very many metadata objects.
Show Structure Tree shows a structure view of the query.
Show Criteria List lets you specify criteria for the SELECT statement. Your specifications can affect the WHERE clause, and any GROUP BY, HAVING and ORDER BY clauses.
Based on Structured Type: For a view based on a structured type, the name of the type.
OID Columns: Object identifier (OID) column name or names.
Allow Type Substitution: If applicable, controls whether a substitutional structured type generation in the DDL is allowed
Displays any currently defined columns in the view.
SQL for View on Structured Type
For a view on a structured type, the SQL statement for the view.
Comment text to be included in database objects that are generated based on this modeling object.
Before Drop/Rename: Statements to execute before the view is dropped or renamed.
Before Create: Statements to execute before the view is created.
After Create: Statements to execute after the view is created.
End of Script: Statements to execute after all other statements in the script have been executed.
Include into DDL Script: Enables user-defined scripts to be included in the generated DDL at defined events, such as before drop or end of script.
Comments, Notes, Impact Analysis, Measurements, Change Requests, Responsible Parties, Documents, Summary
Creates tables based on views in a selected relational model. This dialog is displayed if you click Tools, then View to Table Wizard.
The views in the selected relational model are displayed. Select all views or a subset, optionally specify any naming rule, and click Generate. A table is created for each selected view. Each table selects all columns from the view, although you can later modify the view definition as needed. By default (if no Naming Rule is specified), each table name is its associated view name, prefixed with T_. For example, if a view name is BOOKS, the associated table name by default will be T_BOOKS.
Naming Rule: Displays any variables (relational model name or view name, or both in the specified order) that will be prefixed to the table name instead of T_. To display a dialog box for selecting variables for the naming rule, click Add Variable. For example, assume that the relational model name is Library and the view name is BOOKS:
If you specify only view name, the name of the generated table will be BOOKS. That is, all tables will have the same name as their associated views.
If you specify only model name, the name of the generated table will be Library. You should probably not choose this option, because all tables will have names starting with the model name and jt1, jt2, and so on added to names after the first one.
If you specify model name and view name, the name of the generated table will be LibraryBOOKS.
This dialog box is displayed if you right-click a tab on the right side of the Data Modeler window and select Windows. It lists all currently open editing panes.
Activate: Moves the focus to the selected pane and leaves the dialog box open.
Close: Closes the selected pane and leaves the dialog box open.
If you double-click a name, focus is moved to that pane and the dialog box is closed.