0759-0762

Previous Table of Contents Next

Page 759

Figure 31.1.
The Tablespace
Analysis screen.


The Maintain Users Screen

You use the Maintain Users screen to manage the internal security for the Designer/2000 products. (See Figure 31.2.) This screen does not correspond to database security in any way. A user with read-only privileges here still could access the Repository tables via such products as SQL*Plus, for example. The user must exist in the database to be used in the Repository. The user may have one of two roles: Manager or User . In addition to access to all the modeling and generation tools, the manager also controls the application access rights and version.

Figure 31.2.
The Maintain Users
screen.


Maintain Users Dialog Box Table Items

You can select the Oracle username from the drop-down listbox, which lists all users on the database instance.

There are two Designer/2000 roles: User and Manager. The User role is the default; it gives access to all Designer/2000 components . The exception is that a user cannot access the Application menu in the Repository Object Navigator. The Manager role has access to all Designer/2000 tools except for the Repository Administration utility. Only the Repository owner can access the RAU. A manager also is the only user type that can be an application system owner.

Two modes also can be assigned to users: Read and Write. The Read mode gives read-only access to the Repository via the Designer/2000 tools. The Write mode gives full read and write access to the Repository via the Designer/2000 tools.

Page 760

CAUTION
The Read and Write modes only affect the Designer/2000 tools internally; they do not correspond to user database privileges!

You can scroll the user-spread table horizontally to see the editable Description field. Here, the Repository manager can enter some meaningful text to identify the Repository user.

The final item in this spread table is the Repository user-creation date. This is not directly editable.

NOTE
Privileges still need to be granted for each application by the application owner. The owner can do this by choosing Application Grant Access from the Repository Object Navigator.
Buttons

The buttons for the Maintain User screen provide the following actions:

  • Insert: Inserts a new record into the spread table
  • Delete: Deletes a record from the spread table
  • Reconcile: Performs the additions, deletions, and changes saved in the spread table; reconciliation must be initiated in order for changes to take effect
  • Save: Saves the current spread table; available only after an insertion, deletion, or modification action
  • Help: Brings up online help

The User Extensibility Screen

The User Extensibility screen enables organizations to add element types, association types, and text types to the Repository. (See Figure 31.3.) These extensions enable organizations to add objects that are not currently included in the Repository. In addition to the object, you can add up to 10 properties for the object. The extension is permanent; therefore, you must reinstall the RAU to get rid of it. The extension also is global; all applications using the Repository will include the extension. The extensions are not visible from the modeling tools. The extension objects are not exported and imported automatically; however, as a separate step, you can choose to include them. Normally, you will not experience problems with this procedure; however, if you are importing the objects into a Repository that uses the same object in a different property, you will encounter problems.

Page 761

Figure 31.3.
The User Extensibility
screen.


Element Type

An element type is a top-level object in an application system. User extensions for the element type can have short names of E0 through E99. The types of elements that come as defaults for an application in Designer/2000 include the following:

  • Events
  • Entities
  • Tables
  • Modules
Association Type

An association type defines the meta-model association between elements. User extensions for the association type can have short names of A0 through A99. Designer/2000-supplied associations include elements such as the following:

  • Application Document: Links application systems to documents
  • Trigger Column Usage: Links database triggers to columns
  • Module Function Usage: Links functions to modules
Text Type

A text type is basically any object best defined in a textual mode. These text items can be anything needed to better document your system. Examples of Designer/2000-provided text items follow:

  • Description
  • PL/SQL block
  • Where/Validation condition

Page 762

Extending the Repository

You can add extensions in two ways: by creating new types or by modifying existing types. To add a new type, follow these steps:

  1. Select one of the Type radio buttons on the left of the User Extensibility screen and click New.
  2. Fill in the information for that type.
  3. Add any properties or text type usages required.
  4. Publish the new type by clicking the Publish button.
  5. Submit the DDL (this actually updates the Repository meta-model).
CAUTION
After an extension is published, you cannot edit or delete it.

The second way to extend the Repository is to add new properties or text type uses to existing types. To do this, edit one of the user objects and edit the properties, or click the New button and select an existing type to add. Then publish the changes.

CAUTION
After you publish a user extension, you can change only the Length, Precision, Mandatory, and Case Mode fields.

The User Extensions Section

The User Extensions section provides three options for user extensions:

  • Maintain User Extensions
  • Load
  • Extract

The Matrix Diagrammer

The Matrix Diagrammer is a designer/project leader tool. It is nothing more than a Repository-reporting tool that displays in a GUI format or provides printed output. The reporting is performed in a matrix style, so there are rows, columns, and a condition on which to report. You can use these reports to show completion of or missing items in the application-design process. Figure 31.4 shows a matrix diagram.

Previous Table of Contents Next


Oracle Unleashed
Oracle Development Unleashed (3rd Edition)
ISBN: 0672315750
EAN: 2147483647
Year: 1997
Pages: 391

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net