AllFusion Model Manager - support.ca.com · This documentation and related computer software program ... Oracle Tuning Recommendations ... Rollback Segments

AllFusion® Model Manager

Administrator Guide r7

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

Copyright © 2006 CA. All rights reserved.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Introduction Modeling in the Multi-User Environment ....................................................... 1-1 The Administrator’s Tasks..................................................................... 1-2

Create and Delete the AllFusion MM Database .............................................. 1-2 Install, Initialize, and Upgrade AllFusion MM ............................................... 1-2 Create and Maintain a Library Structure .................................................... 1-3 Administer Security ....................................................................... 1-3 Manage User Sessions ..................................................................... 1-3 Develop and Administer Standards......................................................... 1-3 Generate Reports and Perform Other Administrative Tasks ................................... 1-3

Understand Your License Agreement........................................................... 1-4 Checking the System Requirements ............................................................ 1-5

Database Server Requirements ............................................................. 1-5 Administrator Server Requirements ........................................................ 1-6 Client Requirements....................................................................... 1-6

Preparing Your DBMS Environment............................................................ 1-7 Suggested Server Connection Software...................................................... 1-8 Database Requirements.................................................................... 1-8

For More Information ......................................................................... 1-9 Customer Support ........................................................................ 1-9

Contents iii

Chapter 2: Install and Initialize AllFusion MM Install the Administrative Files ................................................................. 2-1 How an AllFusion MM Database is Initialized ................................................... 2-3

Initialize AllFusion MM on a Microsoft SQL Server or Sybase DBMS ........................... 2-4 Check Settings in the Microsoft SQL Server Client Network Utility ......................... 2-6 Check Database Compatibility Level for Microsoft SQL Server 2005 ........................ 2-6

Initialize AllFusion MM on an Oracle DBMS ................................................. 2-7 Delete the AllFusion MM Database ............................................................. 2-9

Chapter 3: Upgrading AllFusion MM Upgrade Your License ......................................................................... 3-1 Before You Install AllFusion MM ............................................................... 3-1 AllFusion MM Database Upgrade Recommendations............................................. 3-2

Microsoft SQL Server or Sybase DBMS Upgrade Considerations ............................... 3-3 Oracle DBMS Upgrade Considerations ...................................................... 3-3 AllFusion MM 4.1.4 to AllFusion MM r7 Conversion.......................................... 3-3

Upgrade the AllFusion MM Software ........................................................... 3-4 Install the AllFusion MM Software Upgrade ................................................. 3-4

The Conversion Process........................................................................ 3-5 AllFusion MM Property Conversion......................................................... 3-5 AllFusion ERwin DM and AllFusion PM Model Property Conversion .......................... 3-5

Converting the AllFusion MM Database......................................................... 3-6 Manual Conversion........................................................................ 3-6 Automated Conversion .................................................................... 3-7 Convert Your AllFusion MM Database on a Microsoft SQL Server or Sybase DBMS.............. 3-7 Convert Your AllFusion MM Database on an Oracle DBMS.................................... 3-9

iv AllFusion Model Manager Administrator Guide

Chapter 4: Manage Security and Sessions Manage Security.............................................................................. 4-1 The AllFusion MM Security Manager........................................................... 4-2 Security Profiles .............................................................................. 4-3

Assign Permissions ....................................................................... 4-4 Default Security Profiles - AllFusion ERwin DM ......................................... 4-5 Default Security Profiles - AllFusion PM................................................. 4-6

Assign a User to a Security Profile .......................................................... 4-6 Assign a User to a Security Profile ...................................................... 4-8 Change a User's Security Profile ........................................................ 4-8 Remove a User from a Security Profile .................................................. 4-9

Inheriting and Overriding Security Permissions ................................................. 4-9 Create and Modify Security Profiles ........................................................... 4-11

Create a New Profile ..................................................................... 4-12 Change a Profile Name ................................................................... 4-12 Change a Profile's Permissions ............................................................ 4-12 Delete a Profile .......................................................................... 4-12

Use Security to Manage Your License Agreement ............................................... 4-13 Manage Sessions............................................................................. 4-13

Use AllFusion MM Session Manager....................................................... 4-13 Terminate a Session ...................................................................... 4-14

Interrupted Session................................................................... 4-14

Chapter 5: Create and Maintain Libraries Libraries ..................................................................................... 5-1 Plan Your Library Structure ................................................................... 5-2

Determine Your Lifecycle Framework....................................................... 5-2 Consider Your Library Structure ........................................................... 5-3 Suggested Lifecycle for the Model-driven Development Framework ........................... 5-4 Suggested Lifecycle for the System-driven Model Framework ................................. 5-4 Suggested Lifecycle for the Informational Model Framework.................................. 5-5 Suggested Lifecycle for the Business Process Model Framework ............................... 5-5 Moving Models into Production............................................................ 5-6

Create and Maintain Libraries ................................................................. 5-7 Create a Library .......................................................................... 5-7 Rename a Library ......................................................................... 5-7 Delete a Library........................................................................... 5-8 Rename a Model in a Library............................................................... 5-8 Delete a Model in a Library ................................................................ 5-8

Contents v

Chapter 6: Generate Reports Reports....................................................................................... 6-1 Create Administrative Reports ................................................................. 6-1 Create a Security Manager Report .............................................................. 6-3 Share AllFusion ERwin DM Reports Through AllFusion MM...................................... 6-4

Create Shared Reports ..................................................................... 6-5 Modify a Shared Report.................................................................... 6-6 Delete a Shared Report..................................................................... 6-6 Copy a Shared Report...................................................................... 6-6

Appendix A: Create the AllFusion MM Database Create the AllFusion MM Database on Microsoft SQL Server ..................................... A-1 Create the AllFusion MM Database on Sybase .................................................. A-2 Post-Database-Creation Tasks for Microsoft SQL and Sybase ..................................... A-3

Microsoft SQL Server Connections ......................................................... A-4 Sybase Connections....................................................................... A-4 Useful Transact SQL Commands........................................................... A-4

Create a Device Example .............................................................. A-4 Create a Database Example ............................................................ A-4 Create Logins Example................................................................ A-5

Troubleshoot Installation Problems ........................................................ A-5 Unable to Create AllFusion MM Database during Install ................................. A-5 SQL Server 2000 (using db-lib) error 4147, severity 15 error during the creation of the AllFusion MM Database ........................................................................ A-6 System Logs are Full .................................................................. A-6 SQL 1105 Error ....................................................................... A-6 Upgrade the AllFusion MM Version .................................................... A-7

Create the AllFusion MM Database on Oracle................................................... A-7 Oracle Connections ...................................................................... A-11 Installed AllFusion MM Objects........................................................... A-12 Useful Oracle SQL Commands............................................................ A-12

Create a Tablespace .................................................................. A-12 Create a Rollback Segment............................................................ A-12 Create Oracle Users .................................................................. A-13 Grant Privileges to Users ............................................................. A-13

vi AllFusion Model Manager Administrator Guide

Troubleshoot Installation Problems ........................................................A-13 AllFusion MM Fails to Connect to Oracle ...............................................A-13 Unable to Create the AllFusion MM Database During Install .............................A-14 Tablespace is Full (Unable to Allocate Extents) ..........................................A-14 The Rollback Segment has Reached the Maximum Number of Extents.....................A-14 Upgrade the AllFusion MM Version ...................................................A-14 Cannot Access AllFusion MM After it is Installed .......................................A-15

Appendix B: Microsoft SQL and Sybase Server Tuning Recommendations Physical Tuning Parameters ................................................................... B-1

Hardware Configurations.................................................................. B-1 Database Placement ....................................................................... B-2 Data Redundancy ......................................................................... B-2

Server-Level Tuning Parameters ............................................................... B-2 Named Cache Configuration................................................................... B-3 Database Tuning Parameters................................................................... B-3

Transaction Log........................................................................... B-3 Threshold Procedures ..................................................................... B-4 Database Options ......................................................................... B-4

Check Database Compatibility Level for Microsoft SQL Server 2005........................ B-4 Database and Log Sizing ...................................................................... B-5 Maintenance ................................................................................. B-5

Nightly Maintenance Script ................................................................ B-6 DBCC Commands ........................................................................ B-6

Contents vii

Appendix C: Oracle Tuning Recommendations Recommended Disk Configurations............................................................ C-2 Database Configuration....................................................................... C-3

Processes ................................................................................ C-3 Shared Pool .............................................................................. C-3 Buffer Cache ............................................................................. C-4 Redo Log Files ........................................................................... C-4 Redo Log Buffer.......................................................................... C-7

Checkpoints.......................................................................... C-7 Storage Parameters ........................................................................... C-7

Rollback Segments........................................................................ C-8 Tablespaces ............................................................................. C-11

Tables .............................................................................. C-11 Indexes ............................................................................. C-12

Index

viii AllFusion Model Manager Administrator Guide

Chapter

1 Introduction

Modeling in the Multi-User Environment AllFusion® Model Manager is part of the AllFusion® Modeling Suite that provides a multiuser modeling environment that makes coordinated, large-scale modeling possible. The workgroup modeling services that AllFusion Model Manager (AllFusion MM) provides includes conflict resolution, versioning, security, and standards management among project managers, standards administrators, and users of AllFusion® ERwin® Data Modeler and AllFusion® Process Modeler.

AllFusion MM uses a client/server environment and is seamlessly integrated with AllFusion ERwin Data Modeler (AllFusion ERwin DM) and AllFusion Process Modeler (AllFusion PM). AllFusion ERwin DM and AllFusion PM act as AllFusion MM clients, and the AllFusion MM database hosts the repository in which models are stored is set up on the server. The following diagram shows a typical AllFusion MM environment:

Introduction 1–1

The Administrator’s Tasks

Since many special security and administrative features associated with multiuser systems are supported, the routine management of the AllFusion MM environment is usually assigned to a dedicated administrator. This guide describes the tasks and responsibilities of the AllFusion MM administrator. This guide assumes that the administrator understands database and modeling concepts.

The Administrator’s Tasks When you install the AllFusion MM software, the administrator is automatically granted Administrator security status. This allows the administrator to assign user permissions and perform all required maintenance or administrative tasks.

An administrator’s responsibilities fall into these categories:

Create and delete the AllFusion MM database

Install, initialize, and upgrade AllFusion MM

Create and maintain a library structure

Administer security

Manage user sessions

Develop and administer standards

Generate reports and perform other administrative tasks

Create and Delete the AllFusion MM Database

These tasks include performing initial database setup tasks to prepare your DBMS environment for installation. You must be the dbo (Microsoft SQL Server or Sybase) or the schema owner (Oracle) of the database that contains AllFusion MM. For more information about database preparation tips for your DBMS, see the appendix “Creating the AllFusion MM Database.”

Install, Initialize, and Upgrade AllFusion MM

These tasks include installing administrative files, initializing the AllFusion MM database on your DBMS server, upgrading your license agreement to allow more users to access AllFusion MM, and upgrading your current version of AllFusion MM whenever a new version becomes available.

1–2 AllFusion Model Manager Administrator Guide

The Administrator’s Tasks

Create and Maintain a Library Structure

The administrator is responsible for creating libraries and determining how best to structure the AllFusion MM database for their organization. The administrator can also grant security permission to other users for creating libraries. Libraries are managed in AllFusion MM Library Manager in the client product (AllFusion ERwin DM or AllFusion PM) when connected to AllFusion MM.

Administer Security

Security profiles determine who can change the data contained in AllFusion MM. By understanding the activities that each member of a workgroup performs, the administrator can assign the necessary privileges and customize permissions to meet the exact needs of the workgroup. The administrator can also add and delete users from the AllFusion MM database. Security administration is usually performed in the AllFusion MM Security Manager in the client product (AllFusion ERwin DM or AllFusion PM) when connected to AllFusion MM.

Manage User Sessions

Occasionally, user sessions must be terminated. The administrator can perform this task directly or assign another user with the appropriate security permission to terminate user sessions. Managing user sessions is performed in AllFusion MM Session Manager in the client product (AllFusion ERwin DM or AllFusion PM) when connected to AllFusion MM.

Develop and Administer Standards

AllFusion ERwin DM includes a naming standards tool and data type standards tool that can help your workgroup create and manage model naming and data type standards. Because naming and data type standards use external files, the administrator must also manage these files in the AllFusion MM database.

Generate Reports and Perform Other Administrative Tasks

The administrator can use the Data Browser, a versatile reporting module, to run and customize AllFusion ERwin DM reports against the AllFusion MM database. For example, the administrator can generate AllFusion MM Security Manager reports and shared AllFusion ERwin DM reports.

Introduction 1–3

Understand Your License Agreement

Understand Your License Agreement As part of the administrative process, you must assign a security profile to each user. When a user enters a login name to connect to AllFusion MM, the AllFusion MM License Manager checks whether the login name has a valid security profile and verifies that the maximum number of users is not exceeded. You see an error message if the maximum number of users allowed by your license is exceeded.

During installation, you enter a license key, which specifies the maximum number of authorized AllFusion MM users that your installation supports. If you have exceeded your maximum number of users and want to add additional users, you must do one of the following:

Upgrade your AllFusion MM license. For more information, see Upgrade Your License in the chapter “Upgrade AllFusion MM.”

Remove one of the existing users and add the new user. For more information, see Assign a User to a Security Profile in the chapter “Manage Security and Sessions.”

Purchase AllFusion® Model Navigator, which includes special editions of AllFusion ERwin DM and AllFusion PM for those users who need read-only access to AllFusion MM. You can use AllFusion Model Navigator (AllFusion MN) to open and print models and generate reports, but you cannot save changes to the AllFusion MM database or save to a file. You can use the AllFusion MM security feature to assign AllFusion MN users to a special security profile that is not counted toward your license agreement. For more information, see Use Security to Manage Your License Agreement in the chapter “Manage Security and Sessions.”


Checking the System Requirements

Checking the System Requirements Before you install AllFusion MM, you must verify that your system requirements meet at least the minimum specifications, and that you have verified and prepared your DBMS environment for installation. The chapter “Install and Initialize AllFusion MM” outlines the installation process of the administrative files.

Database Server Requirements

Verify that the system you are using as a database server meets the minimum requirements summarized in the following table. Greater CPU speed, and more RAM and disk space result in better performance.

System Component

Microsoft SQL Server Version 7.0 or 2000

Sybase System 12.x

Oracle Server Version 8.1.7, 9i, 10g

CPU Any Microsoft SQL Server supported platform

Any Sybase supported platform

Any Oracle supported platform

RAM 512 MB 512 MB 512 MB

Disk space 60 MB 60 MB 60 MB

Operating system

Any Microsoft supported operating system

Any Sybase supported operating system

Any Oracle supported operating system

Note: The memory requirement of 512 MB is for the minimum size models of only a few entities. Larger size models may need greater memory. Experience has shown that 1 GB RAM and 500 MB disk space seems to be the most effective for our clients.

Introduction 1–5

Checking the System Requirements

Administrator Server Requirements

Verify that the machine where the AllFusion MM software and license key are installed met the minimum requirements summarized in the following table. The greater CPU speed, and more RAM and disk space result in better performance. Note, that while not recommended, the AllFusion MM software and license key can be installed on the same machine that the database resides on.

System Component

Administrator’s Workstation or File Server (for administrative files)

CPU At least a Pentium

RAM 256 MB

Disk space 85 MB

Operating system

Microsoft Windows ME, 2000, XP, 2003 Server.

Note: The disk space required for the administrative files used to create and manage the AllFusion MM database is separate from the disk space required to accommodate models on the server where the AllFusion MM database is located.

Client Requirements

To use the data modeling and multi-user features, you must also install an AllFusion MM client such as AllFusion ERwin DM or AllFusion PM on each client workstation. Each client workstation must have access to the DBMS on which the AllFusion MM database is installed. It is recommended that client workstations have at least 256 MB of RAM.

Note: The memory requirement of 256 MB is for the minimum size models of only a few entities. Larger size models may need greater memory. Experience has shown that 512 MB seems to be the most effective for our clients. For models 5 MB or larger, we recommend 1 GB RAM or above. For more information about specific system requirements, see the AllFusion ERwin Data Modeler and AllFusion Process Modeler documentation.


Preparing Your DBMS Environment

Preparing Your DBMS Environment You must perform the following setup tasks in your DBMS environment before you can install and use AllFusion MM:

Install the DBMS- Install the DBMS on the server where you plan to store the AllFusion MM database. For more information about memory and disk space requirements, see the system requirements for the supported versions of each DBMS (Microsoft SQL Server, Sybase, and Oracle).

Create (or identify) the AllFusion MM database- Use the DBMS features to create or identify the required storage objects and the AllFusion MM database. The specific requirements vary depending on your DBMS type. For more information about DBMS configuration and tuning, see the appropriate appendix in this guide.

Create a user profile for each database user- Use the DBMS features to create a user profile for each AllFusion MM user in the database where the AllFusion MM database is stored. For more information, see your DBMS administrator's documentation.

Note: Each user must have Windows authentication enabled (on databases that support Windows authentication) or a valid login name on the DBMS and permission to access the database in which the AllFusion MM database is stored.

Install DBMS client software on each client workstation- To connect a client workstation to the DBMS server, you must install the appropriate client connection software (for example, SQL*Net) on each workstation. The connection software you use depends on your DBMS type. For more information, see Suggested Server Connection Software in this chapter.

Verify the client/server connection- Use a test command (for example, ping) to check the client/server connection between each client workstation and the DBMS server. Alternatively, use another application on a client workstation (for example, ISQL/W, SQLPLUS, or PowerBuilder) to check the connection. For more information about testing the client/server connection, see your DBMS documentation.

Install an AllFusion MM client on each client workstation- Install the client software using the CD-ROM that shipped with each AllFusion MM client (AllFusion ERwin DM or AllFusion PM). Then, any user with an AllFusion MM login and password and the appropriate DBMS client connection software can connect to the AllFusion MM database from that client workstation.

Introduction 1–7

Preparing Your DBMS Environment

Suggested Server Connection Software

The software you use to connect client workstations to your server depends on the type of server you are using and your personal preference. The following table lists some commonly used DBMS client software connection packages:

DBMS Suggested Software

Microsoft SQL Server or Sybase

Microsoft SQL Server client installation, Open Client/C Developer's Kit for PC Windows and Net-Library for PC Windows, CT-LIB, or equivalent software

Oracle Oracle “Required Files,” SQL*Net, and TCP/IP or equivalent communication software

Note: For more information about memory and disk space requirements, see your DMBS documentation.

Database Requirements

To create the AllFusion MM database, you must be defined as a user with the proper authority for the DBMS you are using. You must be the dbo in the target database on the Microsoft SQL or Sybase server or the DBA for the Oracle server.

Note: The DBA role is necessary only during the AllFusion MM installation or upgrade. It is not necessary after you create the database.

Microsoft SQL 2005 Note: By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower. See Check Database Compatibility Level for Microsoft SQL Server 2005 in the Install and Initialize AllFusion MM Chapter of this guide.


For More Information

For More Information For more information about getting started, see the Getting Started that is included with your documentation. It contains basic information and examples of most AllFusion MM features. You can also open the online help from the Help menu and you can press the F1 key in any dialog for task-specific help.

Customer Support

In addition, you can obtain procedural information and answers to any questions you may encounter by contacting Customer Support for assistance at http://ca.com/support 24 hours a day, 7 days a week.

Introduction 1–9

http://ca.com/support

Chapter

2 Install and Initialize AllFusion MM

Install the Administrative Files Once you have verified the system requirements and prepared the DBMS environment, you are ready to install the administrative files. After installation, you must initialize the AllFusion MM database before client users can save and access models. You can initialize the database at the end of the AllFusion MM installation process, or you can choose to initialize the AllFusion MM database at a later time.

The installation of the administrative files is the same for each supported DBMS (Microsoft SQL Server, Sybase, or Oracle). The Setup program displays a series of instructions to guide you through the installation process.

To install the administrative files, follow these steps:

1. Insert the AllFusion MM CD into your CD-ROM drive.

If your autorun function is enabled, the Setup program starts automatically.

If your autorun function is not enabled, follow these steps to start the Setup program:

a. Click Start on the taskbar, and then choose Run to open the Run dialog.

b. Type d:\setup in the Run dialog, where d is your CD-ROM drive.

c. Click OK. The Setup program starts.

2. Click Next when the Welcome dialog opens.

3. In the License Agreement dialog, read the End User License Agreement, scroll down and click I Agree.

Install and Initialize AllFusion MM 2–1

Install the Administrative Files

4. Follow the instructions provided by the installation wizard. The wizard asks a series of questions you must answer, including:

User and Company information

Destination Location

5. When prompted to choose a Setup Type, you can choose Complete or Custom.

Choose Complete to install all program features.

Choose Custom to install selected features. A new windows displays options to select specific features for installation. You can also evaluate the space needed to install each feature, and change the destination folder for the files.

6. Click Next to continue with the installation wizard. When prompted, click Install to start the installation process.

The program files are copied.

Important! You need to install or upgrade the license key before you initialize the database.

7. Click Finish to exit the wizard. Both check boxes on this dialog are selected by default.

Launch CA AllFusion Model Manager r7.

Show the readme file.

The readme file and AllFusion MM opens. If you cleared the Launch Application check box, you are returned to Windows.

8. Click Finish.

The AllFusion MM Connection Manager dialog opens.


How an AllFusion MM Database is Initialized

How an AllFusion MM Database is Initialized After you install the administrative files and create an AllFusion MM database, you must initialize the database to create the tables and install the stored procedures and queries that manage client workgroup models. You cannot use AllFusion MM until you initialize the AllFusion MM database.

Important! You need to install or upgrade the license key before you initialize the database. Follow the instructions in the AllFusion Model Manager Getting Started to install the license key before you launch the application.

To initialize an AllFusion MM database, you must connect to the AllFusion MM database by either of the following methods:

At the end of the AllFusion MM installation process when you select the Launch Application check box and click Finish.

When you choose AllFusion Model Manager in the AllFusion Model Manager program group in the Start menu.

You must be logged on to the DBMS as the dbo (Microsoft SQL Server or Sybase) or the schema owner (Oracle) of the database that contains AllFusion MM. After you connect to the DBMS, the AllFusion MM Manager dialog opens. The AllFusion MM Manager dialog is slightly different depending on the specific DBMS you use. For more information, see Initializing AllFusion MM on a Microsoft SQL Server or Sybase DBMS or see Initializing AllFusion MM on an Oracle DBMS in this chapter.



Initialize AllFusion MM on a Microsoft SQL Server or Sybase DBMS

You must be logged on to the DBMS as the dbo of the database that contains AllFusion MM.

To initialize AllFusion MM on a Microsoft SQL Server or Sybase DBMS, follow these steps:

1. If you did not launch AllFusion MM during the installation process, you can launch it by clicking Start, Programs, Computer Associates, AllFusion, Model Manager r7, and then Model Manager r7 to open the AllFusion MM Connection Manager.

2. In the AllFusion MM Connection Manager, enter the following information:

For an authentication type, select one of the following:

– Use Windows Authentication if you use Windows usernames and passwords to secure database access and are currently logged onto your machine as the user who is the dbo of the database containing AllFusion MM.

– Use database authentication, to enter the login name and password for the dbo of the database containing AllFusion MM.

Select the Microsoft SQL Server version (for example, Microsoft SQL Server 2000 - using db-lib) in Host DBMS.

Enter the server name (for example, sqlmart) in DBMS Connection.

Enter the name of the AllFusion MM master database in Master Database. If you leave Master Database blank, you can choose the AllFusion MM database from a list in the next dialog.

Note: If you have previously entered this information, you can click the History drop down list to automatically populate the Host DBMS, DBMS connection, and Master database name previously used.

3. Click Connect to connect to the AllFusion MM database and open the AllFusion MM Manager dialog.

Note: If you left Master database blank, the Select AllFusion MM Master Database dialog opens for you to choose the AllFusion MM master database.



4. In the AllFusion MM Manager dialog, verify the AllFusion MM master database name in the Database field:

5. Click Create to create the tables and stored procedures in the selected database. When it completes, the AllFusion MM Security Manager opens.

Important! The AllFusion MM database and the AllFusion MM Control Tables (mmMaster and mmLicense) must be installed on the same database.

6. In the AllFusion MM Security Manager dialog, your user name is automatically added to the Administrator profile in the Security Profile list. Use the controls in the AllFusion MM Security Manager dialog to assign additional security profiles. You can also do this later from AllFusion ERwin DM or AllFusion PM. For more information, see the chapter “Managing Security and Sessions.”

Important! If you do not see the AllFusion MM Security Manager dialog, it may be hidden behind other open applications. Minimize all applications or use the Alt-Tab keys until you find it.

7. When you are done assigning profiles, click OK.

The Setup Complete message displays.

8. Click OK to return to Windows.



Check Settings in the Microsoft SQL Server Client Network Utility

For Microsoft SQL Server, it is necessary to select specific settings in the Client Network Utility to have certain foreign language characters in your models recognized by AllFusion MM.

To verify that the settings in your configuration are correct, follow these steps:

1. From the Start menu, select Programs, Microsoft SQL Server, then Client Network Utility.

2. Click the DB-Library Options tab in the SQL Server Client Network Utility dialog.

3. Select the following checkboxes on the DB-Library Options tab:

Automatic ANSI to OEM conversion

Use international settings

4. Click OK.

Check Database Compatibility Level for Microsoft SQL Server 2005

By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower.

To change the database compatibility level from the database UI, follow these steps:

1. From the Start menu, select Programs, Microsoft SQL Server 2005, SQL Server Management Studio and connect to the server.

2. Right-click on the database and select Properties.

The Database Properties dialog opens.

3. Select SQL Server 2005 (80 or lower) in the Compatibility level field and click OK.

The database compatibility is modified.

Note: The database compatibility level can also be modified by running the following code: sp_dbcmptlevel@dbname = “dbname”, @ new_cmptlevel=80



Initialize AllFusion MM on an Oracle DBMS

You must be logged on to the DBMS as the schema owner of the database that contains AllFusion MM.

To initialize AllFusion MM on an Oracle DBMS, follow these steps:

1. If you did not launch AllFusion MM during the installation process, you can launch it by clicking Start, Programs, Computer Associates, AllFusion, Model Manager r7, and then Model Manager r7 to open the AllFusion MM Connection Manager.

2. In the AllFusion MM Connection Manager, enter the following information:

For an authentication type select one of the following:

– Use Windows Authentication if you use Windows usernames and passwords to secure database access and are currently logged onto your machine as the user who is the schema owner of the database containing AllFusion MM.

Note: For further information about Windows Authentication in Oracle, please consult your Oracle documentation or DBA.

– Use database authentication, to enter the login name and password for the schema owner of the database containing AllFusion MM.

Select the Oracle DBMS version (for example Oracle 9i) in Host DBMS.

Enter the name of the AllFusion MM database in DBMS Connection.

Note: If you have previously entered this information, you can click the History drop down list to automatically populate the Host DBMS, DBMS Connection, and Master database string previously used.

3. Click Connect to connect to the AllFusion MM database.

The AllFusion MM Manager dialog opens.



4. In the AllFusion MM Manager dialog, you must select the following:

The Oracle MMUSER security role from the AllFusion MM Role drop-down list.

Note: This role is created in step 10 of the procedure for creating the AllFusion MM database on Oracle, in the appendix “Creating the AllFusion MM Database”. Other user roles will be able to connect to AllFusion MM, but they will encounter access problems.

The Table tablespace you want to store the AllFusion MM tables in.

Optionally, select the Index Tablespace you want to store AllFusion MM indexes in.

Note: You can store tables and indexes in the same tablespace or in different tablespaces. For more information, see the appendix “Creating the AllFusion MM Database.”

5. Click Create to automatically create the AllFusion MM objects.

The AllFusion MM Security Manager dialog opens.

6. Your user name is automatically added to the Administrator profile in the Security Profile list. Use the controls in the AllFusion MM Security Manager dialog to assign additional security profiles. You can also do this later from AllFusion ERwin DM or AllFusion PM. For more information, see the chapter “Managing Security and Sessions.”

Important! If you do not see the AllFusion MM Security Manager dialog, it may be hidden behind other open applications. Minimize all applications or use the Alt-Tab keys until you find it.

7. When you are done assigning profiles, click OK.

The Setup Complete message displays.

8. Click OK to return to Windows.


Delete the AllFusion MM Database

Delete the AllFusion MM Database Important! Removing the AllFusion MM database is a drastic measure and should only be done after careful consideration.

To delete the AllFusion MM database, follow these steps:

1. Connect to the AllFusion MM database.

The AllFusion MM Manager dialog opens.

2. Connect to the database you want to delete, and click the Delete button.

The AllFusion MM database is deleted.

Verify that the mmMaster and mmLicense tables no longer exist. If they do exist, remove them manually using your DBMS tools.


Chapter

3 Upgrading AllFusion MM

Upgrade Your License If you need to add more users than your current license allows, contact Computer Associates for an additional license file. For more information about contacting Computer Associates, see the chapter "Introduction."

To upgrade your license, you must be assigned to the Administrator security profile in AllFusion MM and you must be logged on as the dbo (for Microsoft SQL Server or Sybase) or the schema owner (for Oracle). After you upgrade the license file, you must connect to AllFusion MM to refresh your database.

Note: If you upgrade your AllFusion MM user license with the AllFusion MM software, the Setup program automatically detects your new license key and a message displays confirming the AllFusion MM license upgrade.

Before You Install AllFusion MM Review the hardware and software requirements and the list of supported target databases in the AllFusion MM readme file.

If you installed an earlier version of AllFusion MM (pre-r7) it is not necessary to remove that version to use r7. Since AllFusion MM is installed to a new folder, you can continue to work with the earlier version, if you have sufficient disk space on your PC for both versions.

Upgrading AllFusion MM 3–1

AllFusion MM Database Upgrade Recommendations

AllFusion MM Database Upgrade Recommendations It is advantageous, whenever possible, to explore the upgrade process in a test environment before attempting to upgrade your production AllFusion MM. By doing so, you become aware of any challenges that may exist, and you have few, if any, surprises when you actually convert your production AllFusion MM. To convert your database as efficiently and fast as possible, follow these recommendations:

Make a full backup of the current AllFusion MM database using the backup utility for your DBMS before upgrading.

Be sure all models in your mart have been opened and saved by an AllFusion 4.1.4 client before you convert to AllFusion MM r7.

Have all users check in any off-line models and ensure that there are no active sessions on the AllFusion MM database and that no models are checked out.

Remove any obsolete models in the current AllFusion MM database to reduce the size of the database, which improves the conversion speed.

Verify that you have synchronized AllFusion ERwin DM and AllFusion PM models if you synchronize data.

Verify that your client version is compatible with the database version to which you are migrating.

Increase the size of the database to at least three times the size of the previous AllFusion MM database for temporary conversion objects.

Verify that there are no outstanding technical support issues with respect to the AllFusion MM database.

For an Oracle DBMS, turn on AUTOEXTEND to automatically extend the AllFusion MM datafile when full.

For a SQL2000 DBMS, make sure the Auto grow file is turned on, with your choice of File Growth and unrestricted File Growth for both data files and transaction logs.

Review the AllFusion MM Readme file.

Run the upgrade during off-peak hours.

Truncate the database log file.

If possible, start the conversion from the server to eliminate the possibility of network speed becoming a bottleneck. Have at least 512 MB RAM (1 GB recommended) on the client, typically more memory means faster performance.

Log on to your DBMS as either the dbo (Microsoft SQL or Sybase) or schema owner (Oracle) of the database that contains AllFusion MM.


AllFusion MM Database Upgrade Recommendations

Microsoft SQL Server or Sybase DBMS Upgrade Considerations

On a Microsoft SQL Server or Sybase DBMS, if you are updating from a previous AllFusion MM version and the system logs are full, you may not be able to overwrite your previous AllFusion MM installation with the current version. Before you install the new version of AllFusion MM, use a DBMS utility (such as Microsoft SQL Object Manager) and type the appropriate command to purge the transaction log.

Note: By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower. See Check Database Compatibility Level for Microsoft SQL Server 2005 in the Install and Initialize AllFusion MM Chapter of this guide.

Oracle DBMS Upgrade Considerations

On an Oracle DBMS, before you start the conversion, it is important that you turn on AUTOEXTEND to automatically extend the AllFusion MM datafile when full.

AllFusion MM 4.1.4 to AllFusion MM r7 Conversion

Verify that the AllFusion MM database is version 4.1.4 (Build 3643 or later). If it is a version earlier than 4.1.4, you need to upgrade to 4.1.4 before you can upgrade to r7. We recommend you upgrade to the latest Service Pack for AllFusion MM Version 4.1.4. You must open and save your models in AllFusion MM Version 4.1.4 before you can upgrade to AllFusion MM r7. See http://ca.com/supportconnect/ for details on upgrading to AllFusion MM Version 4.1.4.


Upgrade the AllFusion MM Software

Upgrade the AllFusion MM Software Computer Associates periodically releases new versions of the AllFusion MM software and supported client software products, AllFusion ERwin DM and AllFusion PM. The AllFusion MM upgrade process prepares the AllFusion MM tables and stored procedures to accommodate new AllFusion MM and AllFusion MM client functionality, but does not change or delete any data stored in the AllFusion MM database. To upgrade the software, you must be assigned to the Administrator security profile in AllFusion MM and you must be logged on as the dbo (for Microsoft SQL Server or Sybase) or the schema owner (for Oracle).

The AllFusion MM software should be installed or upgraded on the computer that houses the CA License Key. That workstation is typically the same computer that the AllFusion MM administrator uses or the first computer that was used to install the AllFusion MM software.

The AllFusion MM database upgrade process is slightly different depending on your DBMS. For more information about specific procedures, see the particular section on the database you are running in this chapter.

Install the AllFusion MM Software Upgrade

To upgrade the AllFusion MM software to a new version you must log on to your DBMS as either the dbo (Microsoft SQL Server or Sybase) or schema owner (Oracle) of the database that contains the AllFusion MM database.

To upgrade the AllFusion MM software, follow these steps:

1. Close all AllFusion MM client connections.

2. Insert the AllFusion MM r7 CD in your CD-ROM drive.

If your autorun function is enabled, the Setup program starts automatically.

If your autorun function is not enabled, follow these steps to start the Setup program:

a. Click Start on the taskbar, and then choose Run.

The Run dialog opens.

b. Type d:\setup in the Run dialog, where d is your CD-ROM drive and click OK.

The Setup program starts. Follow the instructions on your screen.

3. When the InstallShield Wizard Complete dialog opens, select the Launch Application check box, and then click Finish.

The installation completes and the AllFusion MM Connection Manager opens.


The Conversion Process

The Conversion Process The AllFusion MM conversion systematically converts an AllFusion MM database, including all AllFusion MM properties and all AllFusion ERwin DM and AllFusion PM models.

The time it takes to convert an AllFusion MM database varies for each installation. Server speed, size, complexity, and the number of models in the AllFusion MM database are several factors that influence conversion time.

AllFusion MM Property Conversion

The conversion process upgrades the following AllFusion MM properties:

All user names and security profiles (even if the user no longer exists in the database)

All session information

All libraries- The complete AllFusion MM library structure is preserved.

Access information is not converted. Access information is stored internally for tracking purposes.

AllFusion ERwin DM and AllFusion PM Model Property Conversion

The model conversion process converts all AllFusion ERwin DM and AllFusion PM model properties including:

Model data- AllFusion ERwin DM and AllFusion PM models in AllFusion MM are converted. The converted models are the same as if opening an .er1 file with the upgraded client (r7) and saving the model to AllFusion MM r7.

All model objects- AllFusion ERwin DM and AllFusion PM accept all model objects from earlier versions.

All object properties- All model properties such as object names and user-defined properties (UDPs) are fully retained.


Converting the AllFusion MM Database

Converting the AllFusion MM Database The following conversion methods are available to convert your existing AllFusion MM, ERwin DM, and AllFusion PM client models:

Manual Conversion— Move your models from your old AllFusion MM to your new AllFusion MM, one model at a time.

Automated Conversion— Install your new AllFusion MM and initialize the database in the same location as your old AllFusion MM. Convert all existing AllFusion ERwin DM and AllFusion PM models in the old AllFusion MM database to the new AllFusion MM at the same time.

Manual Conversion

Use the Create option on the AllFusion MM dialog to manually convert your models. You move your models from your old AllFusion MM to your new AllFusion MM, one model at a time. The following are some advantages to the manual method:

select the models you want to move, and leave those that you do not.

“clean up” your mart if there are many models or versions which are no longer in use, which would extend conversion time.

run both Model Manager versions simultaneously, and move incrementally, model by model, to the new AllFusion MM.

host your new AllFusion MM on a different server or database platform than your old AllFusion MM version.

The disadvantages, of course, are that the version history is lost on any models checked into the new mart. And, being a manual process, it is time consuming and labor intensive.



Automated Conversion

Use the Update option on the AllFusion MM Manager dialog to convert your all your models at once. Your existing AllFusion ERwin DM and AllFusion PM models in the old AllFusion MM mart are converted automatically to the new AllFusion MM at the same time.

The main advantage to this method is that it is automated and all models retain their full history. The disadvantage may be that it takes a long time if your mart is large, or your client/server hardware is limited. The automated conversion must be done in the same database instance as your previous version of AllFusion MM, which may require more space than is available, or may require you to move your old version of AllFusion MM, if you cannot create additional space.

Convert Your AllFusion MM Database on a Microsoft SQL Server or Sybase DBMS

To convert your AllFusion MM 4.1.4. database to an AllFusion MM r7 database, follow these steps:

1. Log on to your DBMS machine that contains the AllFusion MM database as the dbo.

2. If you did not launch AllFusion MM r7 during the installation process, you can launch it by clicking Start, Programs, Computer Associates, AllFusion, Model Manager r7, and then Model Manager r7.

The AllFusion MM Connection Manager opens.

3. In the AllFusion MM Connection Manager, complete the following dialog information and click Connect.

For an authentication type, select one of the following:

– Use Windows Authentication if you use Windows usernames and passwords to secure database access and are currently logged onto your machine as the user who is the dbo of the database containing AllFusion MM.

– Use database authentication, to enter the login name and password for the dbo of the database containing AllFusion MM.

Select the Microsoft SQL Server version (for example, Microsoft SQL Server 2000 - using db-lib) in Host DBMS.

Enter the server name (for example, sqlmart) in DBMS Connection.

Enter the name of the AllFusion MM 4.1.4 database in Master Database.

Note: You can click the History drop down list to select the host DBMS, DBMS connection string, and AllFusion MM name previously used.



4. The AllFusion MM Manager dialog displays, indicating that an AllFusion MM database exists and the status of that database.

5. Click Truncate Log Before Any Action if you want to remove the database transaction log.

Truncating the database transaction log is especially important for Microsoft SQL Server and Sybase users since a large transaction log may cause the database upgrade to hang. You cannot remove the transaction log after conversion begins.

6. Verify the database name in the Status window. If you are converting from a 4.1.4 Model Manager, choose one of these options:

Create– Creates an empty mart, and then you manually open and save existing models to convert your data.

Convert– Creates a new mart with the current version of AllFusion and automatically copies the data from the old mart into the new mart.

If you are converting from a previous r7 version, choose one of these options:

Update– Updates the current AllFusion MM database to be compatible with the current AllFusion ERwin DM release. This button is enabled only when an earlier version of an AllFusion MM database is recognized.

Convert– Creates a new mart with the current version of AllFusion and automatically copies the data from the old mart into the new mart.

Note: Create and Update are mutually exclusive and the text of the Update/Create button changes depending upon the version of the AllFusion MM database detected.

The AllFusion MM Manager displays conversion progress messages.

7. Click OK on the Upgrade has Successfully Completed message dialog.

The Status now shows “No Update is necessary”.

8. Click Close to exit out of the dialog.

The AllFusion DM/AllFusion MM administrative setup is complete.

9. When the Computer Associates AllFusion MM Setup Complete dialog displays, click OK.

All the existing AllFusion ERwin DM and AllFusion PM models in the AllFusion MM 4.1.4 database are initialized and prepared for the r7 internal structure. The model is not fully converted until you open and save the model in AllFusion MM r7 for the first time. For this reason, it may take a few minutes longer to open the model the first time to complete the process.

The same user profile assignments exist as before the conversion. If you need to make changes to user profiles, you can access the AllFusion MM Security Manager in the Services menu or click the AllFusion MM User Permissions icon on the AllFusion MM Toolbar.



Convert Your AllFusion MM Database on an Oracle DBMS

To convert your AllFusion MM 4.1.4. database to a AllFusion MM r7 database, follow these steps:

1. Log on to your DBMS machine that contains the AllFusion MM database as the schema owner.

2. If you did not launch AllFusion MM during the installation process, you can launch it by clicking Start, Programs, Computer Associates, AllFusion, AllFusion Model Manager r7, and then Model Manager r7.

The AllFusion MM Connection Manager opens.

3. In the AllFusion MM Connection Manager, complete the following dialog information and click Connect.

For an authentication type select one of the following:

– Use Windows Authentication if you use Windows usernames and passwords to secure database access and are currently logged onto your machine as the user who is the schema owner of the database containing AllFusion MM.

– Use database authentication, to enter the login name and password for the schema owner of the database containing AllFusion MM.

Select the Oracle DBMS version (for example Oracle 9i) in Host DBMS.

Enter the name of the AllFusion MM 4.1.4 database in DBMS Connection.

Note: You can click the History drop down list to select the host DBMS and DBMS connection string previously used.

4. The AllFusion MM Manager dialog displays, indicating that an AllFusion MM database exists and the status of that database.

5. Select the AllFusion MM Role (MMUSER) used to initialize AllFusion MM 4.1.4 in the Role drop down list, and the tablespace that contains the AllFusion MM 4.1.4 database you want to convert. The dropdown box will not be active if there is only one tablespace.



6. Verify the database name in the Status window. If you are converting from a 4.1.4 Model Manager, choose one of these options:

Create– You can create an empty mart, and then open and save existing models to convert your data.

Convert– Creates a new mart with the current version of AllFusion and copies the data from the old mart into the new mart.

If you are converting from a previous r7 version, choose one of these options:

Update– Updates the current AllFusion MM database to be compatible with the current AllFusion ERwin DM release. This button is enabled only when an earlier version of an AllFusion MM database is recognized.

Convert– Creates a new mart with the current version of AllFusion and copies the data from the old mart into the new mart.

Note: Create and Update are mutually exclusive and the text of the Update/Create button changes depending upon the version of the AllFusion MM database detected.

The AllFusion MM Manager displays conversion progress messages.

7. Click OK on the Upgrade has Successfully Completed message dialog.

The Status now shows “No Update is necessary”.

8. Click Close to exit out of the dialog.

The AllFusion DM/AllFusion MM administrative setup is complete.

9. When the Computer Associates AllFusion MM Setup Complete dialog displays, click OK.

The same user profile assignments exist as before the conversion. If you need to make changes to user profiles, you can access the AllFusion MM Security Manager in the Services menu or click the AllFusion MM User Permissions icon on the AllFusion MM toolbar.

All the existing AllFusion ERwin DM and AllFusion PM models in the AllFusion MM 4.1.4 database are initialized and prepared for the r7 internal structure. The model is not fully converted until you open and save the model in AllFusion MM r7 with AllFusion ERwin DM or AllFusion PM for the first time. It may take a few minutes longer to open the model the first time to complete the process.


Chapter

4 Manage Security and Sessions

Manage Security AllFusion MM provides a comprehensive security system that prevents unauthorized users from adding, modifying, or deleting objects in the AllFusion MM database. To ensure security, all AllFusion MM objects are divided into hierarchical security classes and all users are assigned to a security profile.

Security profiles control the actions each user can perform on a particular class of objects. You can assign users to the predefined security profiles or create customized profiles to fit your environment. By assigning a user to more than one security profile, you can customize each user’s permission to manipulate different objects in the AllFusion MM database. This role-based security provides complete control over model access and updates, with the flexibility to restrict users by library, model, subject area, and entity.

To manage security, you must be assigned the Administrator security profile for the AllFusion MM database. When you first initialize the AllFusion MM database, you assign the Administrator security profile to your database user name (the dbo for Microsoft SQL Server or Sybase or schema owner for Oracle). After AllFusion MM database initialization, you manage security from the AllFusion MM Security Manager in AllFusion ERwin DM or AllFusion PM. You can also assign AllFusion MM Administrator permission to another database user for day-to-day security management.

Manage Security and Sessions 4–1

The AllFusion MM Security Manager

The AllFusion MM Security Manager The AllFusion MM Security Manager assigns user security profiles and creates custom security profiles. You must be connected to the AllFusion MM database in order to open the AllFusion MM Security Manager.

Note: AllFusion MM Security Manager starts automatically at the end of the AllFusion MM installation and initialization process for you to assign user security profiles immediately after you create an AllFusion MM database.

To start AllFusion MM Security Manager, choose Security from the Services menu in AllFusion ERwin DM or AllFusion PM. The AllFusion MM Security Manager dialog opens, displaying the existing users in the User list. The following dialog shows an example:

The User pane lists the users you define in your DBMS. You must add, change, and delete users directly from the DBMS. For example, you can use the Enterprise Manager in Microsoft SQL Server. To use AllFusion MM, you must assign each DBMS user to an AllFusion MM security profile.

AllFusion MM manages your license agreement by counting every user with a security profile as a licensed user. Your registration ID determines the maximum number of users that can access the AllFusion MM database. If the number of users exceeds the limit of your license agreement, a warning message prompts you to remove the unauthorized users. For more information, see Understanding Your License Agreement in the chapter “Introduction.”


Security Profiles

Security Profiles A security profile is a set of permissions that control the actions a user can perform on a specific group of objects, called a permission object class, in the AllFusion MM database. During installation, five hierarchical security profiles are automatically created. These predefined security profiles are:

Administrator (highest security profile)

Architect

Modeler

Viewer

Guest

The following diagram shows users assigned to the predefined security profiles:

Each predefined security profile grants a set of create, update, and delete permissions on each set of permission object classes. By assigning a user to a security profile, you associate an object class and a set of permissions with that user name—thereby preventing the user from making unauthorized changes to the AllFusion MM database. Whenever a user tries to create, update, or delete an object, the user’s security profile is checked to determine if the operation is permitted for that user.


Security Profiles

During installation, the current DBMS user name is assigned to the Administrator security profile, which provides unlimited access to all objects, including the permission to create other users and assign their security privileges. The following diagram shows the Administrator permissions and permissions that could be granted to the Architect and Modelers security profiles:

Assign Permissions

The following tables show which permissions are associated with each predefined security profile for AllFusion ERwin DM and AllFusion PM. An X in a security profile column means the AllFusion MM permission is granted; a blank means that permission is denied.

Use the following tables to determine which permissions are needed to create, modify, or delete objects. Find the object you want to update in the AllFusion MM Object column, and then locate the corresponding permission in the AllFusion MM Permission column.

You must be assigned to a security profile that grants the proper permission for the changes you want to make. For example, to update entities, your security profile must have Update Entity permission.


Security Profiles

Default Security Profiles - AllFusion ERwin DM

The following table shows the AllFusion MM Default Security Profiles for AllFusion ERwin DM:

Permission Object Class

AllFusion MM Object

AllFusion MM Permission

AllFusion MM Default Security Profile for AllFusion ERwin DM

Admin-istrator

Architect Modeler Viewer/ Guest

Mart

Library

Manage AllFusion MM database Create Library Delete Library Update Library

X

X X X

X X X

Library Model (Mart model) Create Model

Delete Model Update Model

X X X

X X X

X X X

Model Entity (for example, Entity Name, Entity Definition, Table Properties) Relationship (for example, Rolename, Name, Verb Phrase, Cardinality, Type) Stored Display, Text Block

Create Entity Delete Entity Update Entity

X X X

X X X

X X X

Domain (for example, Domain Name, Datatype, Default Value, Definition, Null Option, Validation Rules)

Create Domain Delete Domain Update Domain

X X X

X X X

X X X

Data Rule Create Data Rule Delete Data Rule Update Data Rule

X X X

X X X

X X X

Bitmap Create Bitmap Delete Bitmap Update Bitmap

X X X

X X X

X X X

Data Source Create Data Source Delete Data Source Update Data Source

X X X

X X X

X X X

Data Source Table Create Data Source Table Delete Data Source Table Update Data Source Table

X X X

X X X

X X X

Data Source Column Create Data Source Column Delete Data Source Column Update Data Source Column

X

X

X

X

X

X

X

X

X

Subject Area Create Subject Area Delete Subject Area

X X

X X

X X

UDP Key Create UDP Key Delete UDP Key Update UDP Key

X X X

X X X

X X X

Entity Attribute (for example, Attribute Properties, Column Properties)

Create Attribute Delete Attribute Update Attribute

X X X

X X X

X X X

Subject Area Subject Area (Change membership of subject area)

Manage Subject Area X X X


Security Profiles

Default Security Profiles - AllFusion PM

The following table shows the AllFusion MM Default Security Profiles for AllFusion PM:

Permission Object Class

AllFusion MM Object

AllFusion MM Permission

AllFusion MM Default Security Profiles for AllFusion PM

Admin-istrator

Architect Modeler Viewer/ Guest

Mart

Library

Manage AllFusion MM database Create Library Update Library Delete Library

X

X X X

X X X

X X X

Library Model (Mart) Create Model

Delete Model Update Model

X X X

X X X

X X X

Note: The Viewer and Guest security profiles for AllFusion ERwin DM and AllFusion PM are initially assigned no permissions. For more information, see Create and Modify Security Profiles in this chapter.

Assign a User to a Security Profile

To access AllFusion MM, each DBMS user must be assigned to a security profile. You can assign the predefined AllFusion MM security profiles, or you can create a custom security profile. For more information, see Create and Modify Security Profiles in this chapter.

By assigning a user to a particular security profile you can control the actions that the user can perform on a given type of object. You can even assign a user to more than one security profile to customize each user’s rights to manipulate objects in the AllFusion MM database. For example, you can assign a user to the Architect profile in one library to grant extensive read or write privileges and assign the same user to the Viewer profile in a second library to grant read-only permissions.


Security Profiles

When you assign the predefined security profiles to AllFusion MM users, follow these guidelines:

Assign the Administrator profile to the user responsible for creating, updating, and deleting the AllFusion MM database, adding and removing users, and assigning users to security profiles.

Assign the Architect profile to experienced modelers who are responsible for managing one or more libraries, including the objects in those libraries.

Assign the Modeler profile to users who need to work on AllFusion ERwin DM or AllFusion PM models stored in the AllFusion MM database.

Assign the Viewer profile to users who should be able to view, but not change, the AllFusion ERwin DM or AllFusion PM models stored in the AllFusion MM database. The default Viewer profile has no create, update, or delete permissions. You can use the default Viewer security profile to limit the permissions of a user in a particular object class.

Assign the Guest profile to users who are using the AllFusion MN edition of AllFusion ERwin DM or AllFusion PM to access AllFusion MM. The Guest profile has no create, update, or delete permissions and is assigned at the Mart level (the base level in the library object class hierarchy). Users assigned to the Guest profile are not counted as licensed users. For more information, see Use Security to Manage Your License Agreement in this chapter.

Note: To add, change, or delete a security profile, you must be assigned to the Administrator security profile for the AllFusion MM database.


Security Profiles

Assign a User to a Security Profile

To assign a security profile to a user you must first choose Security Manager on the Services menu to open the AllFusion MM Security Manager dialog. Next select the permission object class (for example, Mart) from the list at the top of the dialog, and then drag-and-drop each user name from the User list to the appropriate security profile icon in the Security Profile list. For more information about detailed procedures, see the AllFusion ERwin Data Modeler Online Help or the AllFusion Process Modeler Online Help.

For example, if you select the Mart library object and drag user01 to the Administrator profile, that user is granted Administrator-level permissions on the Mart library. The following dialog shows an example:

Note: Be sure to assign the Guest security profile to all users that are using the AllFusion MN edition of AllFusion ERwin DM or AllFusion PM so that they will not be counted as licensed users.

Change a User's Security Profile

To change a user’s security profile you must first choose Security Manager on the Services menu to open the AllFusion MM Security Manager dialog. Next select the permission object class from the list at the top of the dialog and open the security profile containing the user being reassigned. Drag the user’s name back to the User list. Now, drag the icon for that user to the new security profile in the Security Profile list. For more information about detailed procedures, see the AllFusion ERwin Data Modeler Online Help or the AllFusion Process Modeler Online Help.


Inheriting and Overriding Security Permissions

Remove a User from a Security Profile

To remove a user from a security profile you must first choose Security Manager on the Services menu to open the AllFusion MM Security Manager dialog. Next select the permission object class from which you want to remove the user and open the security profile containing the user being removed. Drag the user’s name back to the User list.

Inheriting and Overriding Security Permissions When you assign a user to a security profile, the user automatically inherits equivalent permissions on all lower-level objects. For example, if you assign a user to the Architect profile at the highest level in the object class hierarchy (the Mart level), the user is automatically assigned Architect-level permissions for all object classes below it (in AllFusion ERwin DM: Library, Model, and Subject Area).

You can override the inherited security profile at a lower level for any user by simply changing the security profile of the lower level object you choose. A security profile assigned to a specific object overrides any security permissions inherited from a higher-level object class. To override security permissions inherited by a user, select a permission object class or an individual object and drag the user to the security profile you want to assign.

If you assign a user to a new security profile for an object in the Mart object class hierarchy (for example, a model), the user retains all permissions granted by other security profiles, except for the permissions that the new security profile overrides.


Inheriting and Overriding Security Permissions

In the following diagram, the user has Viewer permission in the AllFusion MM database and Architect permission in the library:

By default, both the Viewer and Guest security profiles are read-only security profiles at the Mart level. When a user is assigned to a read-only security profile, the permissions defined in that profile are automatically applied to all lower object classes in the Mart object class hierarchy.

While you can assign the Viewer profile to limit the permissions of a user in a particular object class, it is better to use the Guest profile exclusively for users that use AllFusion MN to access AllFusion MM. The Guest security profile is not counted toward your license limit.

Note: To add, change, or delete a security profile, you must be assigned to the Administrator security profile for the AllFusion MM database.

To override a user’s inherited security permissions, follow these steps:

1. When connected to AllFusion MM, click AllFusion MM User Permissions on the AllFusion MM toolbar or choose Security Manager on the Services menu.

2. Select the object class or individual object (such as Videostore Library) for which you want to override the user’s inherited security permissions.


Create and Modify Security Profiles

3. Drag the icon for the user from the User list to the desired security profile in the Security Profile list. The security profile you assign for a specific object overrides any security permissions inherited from a higher-level permission object class.

Create and Modify Security Profiles To create, update, or delete a security profile, you must use the AllFusion MM Security Profile Manager. You must be assigned the Administrator security profile for the AllFusion MM database that you want to create, update, or delete in.

To create or modify a security profile, follow these steps:

1. Choose AllFusion MM User Permissions on the AllFusion MM toolbar or AllFusion MM Security Manager from the Services menu.

The AllFusion MM Security Manager dialog opens.

2. Click Profile.

The AllFusion MM Security Profile Manager dialog opens.

3. Select a Security Profile from the top of the dialog and an object class from the bottom of the dialog.

The Permission list in the right pane displays all of the available permissions for the selected object class.

4. Select the check box to grant permission or clear the check box to deny permission.


Create and Modify Security Profiles

By default, the Guest security profile prevents a user from creating, updating, or deleting information in the AllFusion MM database. Assign the Guest security profile exclusively to users who use an AllFusion MN edition of AllFusion ERwin DM or AllFusion PM.

5. Click OK.

The Security Profile has been modified.

Create a New Profile

To create a new profile, type the name in the Profile Name box that you want to assign to the profile and click New. The new profile is added to the Security Profile list. By default, new profiles have no permissions.

Change a Profile Name

To change the name of a profile, click on that profile, edit the name in the Profile Name box, and click Update.

Change a Profile's Permissions

To change the permissions associated with a security profile, select the profile (for example, Architect). Click the appropriate object class (for example, Mart), and then select the check box to grant permission to perform an activity (for example, Create Library). Click Update when you are finished.

Important! Changing the Guest security profile is not permitted.

Delete a Profile

To delete an existing profile, select the profile and then click the Delete button.


Use Security to Manage Your License Agreement

Use Security to Manage Your License Agreement Each time you add an AllFusion MM user, AllFusion MM counts the number of users to determine if you have exceeded the limits of your license agreement. If you exceed the number of users allowed by your license agreement, you must remove any extra users.

If your workgroup includes users who need to view or run reports on AllFusion ERwin DM models or AllFusion PM models stored in the AllFusion MM database, you can purchase AllFusion Model Navigator (AllFusion MN) and assign users to the default Guest security profile. Assigning users to the Guest security profile lets them access AllFusion MM information without counting towards the number of users allowed by your license. AllFusion MN is a read-only version of the AllFusion MM client, you cannot save an AllFusion ERwin DM model or AllFusion PM model to the AllFusion MM database or to a file.

Manage Sessions When a user logs on to the AllFusion MM database, this event is recorded as the start of a session. During a session, the models that a user opens and the current lock mode of a model are tracked. As the administrator, you may need to terminate a user’s session so that other users can access any models locked by that user. For example, if a user is working offsite on a model and has locked the corresponding model, you can terminate the user’s session to unlock the model so that others can access it.

Each session has its own Action Log, which logs the transaction information containing real time changes made to a model. Once you have logged out, the Action Log is cleared.

Use AllFusion MM Session Manager

Use AllFusion MM Session Manager to view the list of users and the lock status of any open models. To start AllFusion MM Session Manager, choose Session from the AllFusion MM menu.

The Users list displays all users, whether or not they are currently logged on to the AllFusion MM database. Only users with open models display in the Open Models list. The lock status of the diagram or model is indicated by the lock symbol that appears before the diagram or model name. A green lock indicates a model locked by the current user. A red lock indicates a model locked by a different user. A yellow lock indicates a model opened but not locked.


Manage Sessions

Terminate a Session

To terminate a session, open the AllFusion MM Session Manager dialog and click a user name in the Users list. Click Terminate.

Note: You must be assigned to the Administrator security profile to terminate a session.

You are asked to confirm that you want to terminate all locks held by the selected user. Any locks placed on the models opened by that user are removed and the session is terminated. Terminating a session prevents the user from saving current changes back to the AllFusion MM database.

Interrupted Session

If AllFusion ERwin DM or AllFusion PM is interrupted by a system failure, when the user who previously locked a model logs on again, the user is given a list of all the diagrams they had open and are informed if they proceed, the diagrams will be closed and all locks will be lost.


Chapter

5 Create and Maintain Libraries

Libraries Libraries are used to store AllFusion ERwin DM and AllFusion PM models that can be shared by users. Libraries can help you organize projects by grouping models together. For example, you can create a library to store models shared by a certain workgroup, security level, or target server. There is no limit to the number of libraries you can create, and there is no limit to the number of models you can store in a library. By organizing your business process models and data models in libraries, you can also easily manage model merging and conflict resolution. The following diagram shows an example:

Library creation and management should be done by the administrator or someone who is similarly designated. Whoever manages libraries must have the necessary security permissions to create, update, or delete a library. For more information about security permissions, see Using Security Profiles in the chapter “Managing Security and Sessions.”

You create and maintain libraries in the AllFusion MM Library Manager. To open the AllFusion MM Library Manager, choose Library from the Services menu in AllFusion ERwin DM and AllFusion PM.

Create and Maintain Libraries 5–1

Plan Your Library Structure

Plan Your Library Structure Before you set up your library structure in the AllFusion MM Library Manager, you should review how the workgroup modeling process works in your organization. To help you review your workgroup modeling process, answer the following questions:

Do you plan to use both AllFusion ERwin DM and AllFusion PM with AllFusion MM?

If using AllFusion ERwin DM and AllFusion PM with AllFusion MM, do you plan to share entities and attributes with AllFusion ERwin DM and AllFusion PM models?

How will AllFusion ERwin DM models be moved from the development library to the production library?

How will your approval process for moving models be documented and enforced?

How will AllFusion ERwin DM models be merged into the enterprise model and who will control this process?

Will you use versioning to record a model’s milestones?

Who will have what type of access to each library?

Will AllFusion ERwin DM models be generated to multiple target environments (such as Microsoft SQL Server and Oracle)?

How will you be warehousing your data?

Determine Your Lifecycle Framework

Once you answer these questions you should determine which of the following model lifecycle frameworks you use in your organization:

Model-driven Development- Changes to the schema are made to the AllFusion ERwin DM model first and then forward engineered.

System-driven Models- Changes are made directly to the schema and the model is reverse-engineered in AllFusion ERwin DM to reflect the changes.

Informational Models- The AllFusion MM database contains AllFusion ERwin DM logical-only models, enterprise-wide models, or standards and sample models.

Business Process Models- Contains models generated by AllFusion PM.



Consider Your Library Structure

Each type of framework has different considerations that you need to think about when configuring your AllFusion MM database and developing its supporting policies. You are not required to choose a particular framework, however, it helps to know your development process before building a library structure.

Depending on the framework, you should consider any or all of these suggestions when building a library structure:

Practical Library Names Use practical and functional library names that help all users understand the purpose and type of models contained in the library. For example, you can use the popular format: Short System Name+Version+Stage (for example, Ora_8_Production).

Model naming and datatype standards (AllFusion ERwin DM) The enforcement of AllFusion ERwin DM naming and datatype standards is supported, which is vital to efficient workgroup modeling. For more information, see the AllFusion ERwin Data Modeler Online Help.

Rules for model promotion You should define a rigid and documented model approval and promotion process using different libraries for each development phase.

Rules for model versioning You should define versioning rules using different libraries for each development version (for example, Development Beta 1).

User rights and security You can apply stricter rights to libraries that contain mature models nearing the latter stages of development. You can also apply strict rights to individual models.

Publication You can generate reports to communicate milestones in the model development process.

Schema generation rules (AllFusion ERwin DM) You can set up a library where you generate model schema. Generally, you generate model schema of only promoted models in the latter stages of development.



The following sections address these considerations for each type of framework.

Suggested Lifecycle for the Model-driven Development Framework

In the Model-driven framework, the model is always the source of all changes. You create a new database schema by forward engineering the model. The life cycle of a model in the Model-driven Development framework may follow a path like this:

1. Create the library structure (for example, Development, Test, and Production) and populate them with AllFusion ERwin DM templates.

2. Create the logical model in a development library.

3. Promote the model to the test library when it is ready.

4. Generate the schema from the test library.

5. Modify the test model as required and synchronize it to the schema.

6. Promote the model to the production library when it is ready.

7. Publish the refreshed production model.

8. Update the enterprise-wide model, if necessary.

9. Incorporate changes into the development model for further changes, and repeat the process.

Suggested Lifecycle for the System-driven Model Framework

In the System-driven framework, there is an established information system from which you can reverse engineer database tables. The life cycle of a model in the System-driven Development framework may follow a path like this:

1. Create the library structure (for example, Reverse Engr, Test, Production). You should not require AllFusion ERwin DM templates since you do not create models from scratch.

2. Reverse engineer the model from the information system into the designated library.

3. Enhance the model with logical information and input from analysts.

4. Update the model to reflect changes in the physical schema.

5. Create a version of the model.

6. Synchronize the schema and the model using Complete Compare.

7. Publish the model.

8. Repeat steps 5 through 7 as the system is modified.



Suggested Lifecycle for the Informational Model Framework

In the Informational Model framework, AllFusion MM contains AllFusion ERwin DM logical-only models, enterprise-wide models, or standards and sample models. There is no forward engineering with the intent of using the schema. The life cycle of a model in the Informational Model framework may follow a path like this:

1. Create the library structure and populate them with AllFusion ERwin DM templates.

2. Develop the initial model. Use reverse engineering and model new components as required.

3. Publish the initial model to the appropriate parties for modification and refinement.

4. Get approval, and then version the model.

5. Publish the approved model.

6. Update and publish models as the enterprise model evolves.

Suggested Lifecycle for the Business Process Model Framework

In the Business Process Model framework, you use AllFusion PM to design business process models that define business processes in your organization. You can optionally export entities and attributes to AllFusion ERwin DM to develop a model-driven information system that adheres to the business process rules. The life cycle of a model in the Business Process Model framework may follow a path like this:

1. Create a working version of an AS-IS model of selected subjects.

2. Critique and analyze the model.

3. Move the model through draft, recommended, and publication versions.

4. Publish the model at the end of the cycle.

5. Create working TO-BE models of the model from Step 4 that incorporates management’s future vision.

6. Update the model as changes and enhancements are approved and as support systems are integrated into the models.

7. Version the modified models based upon the approval of the changes and enhancements.

8. Publish the revised models when each version becomes stable.



Moving Models into Production

During the model development lifecycle, it is vital that you have an organized library structure so that only those models intended for production are moved to that level. You should structure your libraries into at least three distinct types:

Development Libraries— contain models that are being created or updated.

Test Libraries— contain finished models that are being tested prior to moving them to production.

Production Libraries— contain the finished models that were tested and debugged.

After you have created your libraries, determine the security levels for each library. The following three examples should give you an idea of how you can use libraries and security together to help safeguard the project models:

The entire modeling team can have access to the development library and read-only access to the test and production libraries. Authorized project leaders can be assigned to move models from the development library to the test library, and then from the test to the production library.

Models from other libraries (like Sales and Accounting) can be merged from their own libraries in the enterprise model. Modelers working on projects in the Sales or Accounting libraries can have read-only access to the enterprise library and full access to their own projects. Assign one person or group to manage integration into the enterprise model.

Modelers should have full access to their own libraries and read-only access to the libraries of others. This type of security enhances production since everyone can see what everyone else is working on, all models are stored in one location, and permissions can be changed as different collaborations among modelers become necessary.

For more information, see the chapter “Managing Security and Sessions.”


Create and Maintain Libraries

Create and Maintain Libraries Creating libraries is a fast and easy process. You create, maintain, and delete libraries in the AllFusion MM Library Manager, which you can open by choosing Library Manager from the Services menu in AllFusion ERwin DM and AllFusion PM.

Create a Library 1. Choose AllFusion MM Library Manager from the toolbar or the Services

menu.

The AllFusion MM Library Manager dialog opens.

2. Select the Mart in which you want to create the library.

3. Enter the name of the library in the Name field.

4. Click Create.

The library is created.

Rename a Library 1. Choose AllFusion MM Library Manager from the toolbar or the Services

menu.


2. Select the Mart and locate the library you want to rename.

3. Enter the new name of the library in the Name field.

4. Click Update.

The library is renamed.


Create and Maintain Libraries

Delete a Library

When you delete a library, all of the models stored in that library are also deleted. You cannot delete a locked library, or a library that contains a locked model. To save a model before deleting the library, save the model as an AllFusion ERwin DM or AllFusion PM file or save the model to a different library.

To delete a library:

1. Choose AllFusion MM Library Manager from the toolbar or the Services menu.


Note: If you use both AllFusion ERwin DM and AllFusion PM in AllFusion MM, you will only see the models in the library for the client that you have open. Since models that belong to the other client are hidden, you could inadvertently delete these models. Therefore, verify that no models for the other client are stored in the library that you want to delete.

2. Select the library you want to delete.

3. Click Delete.

The library is deleted.

Rename a Model in a Library

In the AllFusion MM Library Manager dialog, select the model you want to rename. Enter the new name of the model in the Name field and click Update.

Delete a Model in a Library

In the AllFusion MM Library Manager dialog, select the model you want to delete and click Delete.


Chapter

6 Generate Reports

Reports Users typically work from a common set of libraries, models, and submodels, and must be able to share information about these objects with other users. One way to share information is by using reports, which detail the information and definitions for a model in a tabular format.

All users can run a number of reports in the Data Browser to view the contents of specific libraries and models, and use standard and customized AllFusion ERwin DM reports to see model information in more detail. However, there are two specific reporting tasks that the administrator performs:

Creating AllFusion MM Security Manager reports

Creating shared AllFusion ERwin DM reports

This chapter explains how to create and use these reports.

Create Administrative Reports Reports are generated and viewed using the Data Browser. Access the Data Browser by clicking the Data Browser icon on the toolbar. The available reports vary depending upon whether you are connected to AllFusion MM, if you are working in the AllFusion MM Security Manager or AllFusion MM Library Manager, and so on. The Data Browser stores the definitions of standard and customized reports. These definitions appear in the report tree on the left side of the browser.

The General folder contains administrative reports organized by object class (such as Global and Diagram). The reports in each class run across the entire contents of that class and library. This folder appears in the tree control when you are connected to the AllFusion MM database.

Generate Reports 6–1

Create Administrative Reports

As the administrator, you can use many of the reports in the General folder to help you manage the AllFusion MM database. For example, Global reports let you view information about existing model locks, open objects, and users.

After you run a report and generate a result set, you can customize the content and appearance of the result set, and create and save your own custom report views. You can also:

Use the Data Browser search features to find information in the result set

Specify a search expression for one or more columns so that the Data Browser finds only the result set rows that satisfy all of the search expressions

Find a change of value in a column

Hide result set rows that do not match the search

To run a report, double-click any report name associated with the report icon ( ). The name of the result set returned by the report is displayed below the original report. The results appear in the Result Set Area. For more information, see the online help.

Tree Control Result Set


Create a Security Manager Report

Create a Security Manager Report AllFusion MM provides one predefined security report. This report provides information about the security profiles assigned to each user and the permissions associated with those profiles.

To access this report, select the Security option from the Services menu. When the AllFusion MM Security Manager dialog opens, click the Report button to open the Data Browser. The tree control in the Data Browser displays a Security Reports folder containing the report. Double-click the Security Report icon in the tree control to generate the result set. The result set shows the following information:

User- The name of the AllFusion MM user (for example, JSMITH).

Object Name- The Object Name is always Current Mart for an AllFusion MM Security Manager Report.

Profile Name- The security profile name (for example, Administrator).

Profile Description- A description of the security profile (for example, Administrator).

Application- The name of the AllFusion MM client application (for example AllFusion ERwin DM).

Permission- The name of the security permission (for example, Create Library).

Granted -The permission status; 1 indicates the permission is granted, 0 indicates the permission is not granted.

After you generate the report you can use the Data Browser features to customize the appearance of a result set, find one or more specific items in the result set, print the result set, or export the result set to HTML or other formats.

Note: You can also generate a report listing the changes you have made using the AllFusion MM Security Manager. For more information, see the chapter “Managing Security and Sessions.”


Share AllFusion ERwin DM Reports Through AllFusion MM

The following dialog shows a sample AllFusion MM Security Manager report:

Share AllFusion ERwin DM Reports Through AllFusion MM You can select individual AllFusion ERwin DM reports and save them in the AllFusion MM database for company-wide use. Only an AllFusion MM user with an Administrator security profile can:

Create a shared AllFusion ERwin DM report

Edit a shared AllFusion ERwin DM report

Create a new report folder to store result sets

Delete a shared AllFusion ERwin DM report

Note: AllFusion MM does not provide versioning and merging features for reports. Changes may be overwritten if multiple administrators are editing and saving shared AllFusion ERwin DM reports to the AllFusion MM database.



Create Shared Reports

To create a shared AllFusion ERwin DM report, you must first open the Data Browser by clicking the Data Browser button on the AllFusion ERwin DM toolbar. If the reports you want to save in the AllFusion MM database appear in the active AllFusion ERwin DM Reports (.erp) file, you can copy them to the AllFusion MM database by selecting the report in the tree control and choosing the Copy Report to AllFusion MM option on the AllFusion ERwin DM Reports menu. The following diagram shows an example:

Note: If you are having trouble locating the report you want to share, it may not be in the active .erp file. Locate the .erp file containing the report by choosing Open Report File from the AllFusion ERwin DM Reports menu and specifying the path and file name of the .erp report you want to open.

The first time an administrator saves an AllFusion ERwin DM report in the AllFusion MM database, the browser creates a new folder called Shared AllFusion ERwin DM Reports. When a report is copied, the browser keeps the folder structure associated with a report and lists it under the Shared AllFusion ERwin DM Reports folder. For example, when the AllFusion ERwin DM Reports/Attributes Report (shown in the previous example) is saved to the AllFusion MM database, it becomes the Shared AllFusion ERwin DM Reports/Attributes Report.



Modify a Shared Report

You can modify the contents, sort order, or format of a report. To modify a shared report, log on to the AllFusion MM database that contains the shared AllFusion ERwin DM report and locate the report you want to modify. Right-click the report name and choose Edit Report from the popup menu.

Note: AllFusion MM users who have the browser open when a change is applied do not see the change immediately; the change appears when they reopen the browser.

Delete a Shared Report

To delete a shared report, log on to the AllFusion MM database that contains the shared AllFusion ERwin DM report and locate the report you want to delete. Select the report and press the Delete key.

Copy a Shared Report

To copy a shared report from AllFusion MM to AllFusion ERwin DM, log on to the AllFusion MM database that contains the shared AllFusion ERwin DM report and locate the report you want to copy. Select the report and choose Copy Report to File from the AllFusion ERwin DM Reports menu. AllFusion ERwin DM then copies the selected report to the AllFusion ERwin DM Reports folder.


Appendix

A Create the AllFusion MM Database

Create the AllFusion MM Database on Microsoft SQL Server These instructions are for the DBAs and system administrators responsible for installing AllFusion MM on a Microsoft SQL Server database management system. The information provided includes troubleshooting tips on installation and Microsoft SQL Server connectivity software requirements.

Note: By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower. See Check Database Compatibility Level for Microsoft SQL Server 2005 in the Install and Initialize AllFusion MM Chapter of this guide.

To install AllFusion MM on a Microsoft SQL Server database management system, follow these steps:

1. Create a database to contain AllFusion MM.

To create the database you can use a graphical user interface (GUI) tool, ISQL (all versions), SQL Administrator, or Enterprise Manager. If a GUI tool is not available, you can use ISQL to type in the appropriate commands manually. Some examples of command statements are included in this appendix.

Your AllFusion MM database should meet the following criteria:

The initial size of the database file should be set to 500 MB

The initial size of the transaction log file should be set to 50 MB

Set the maximum file size to unrestricted file growth for both files (recommended, but not required).

Increase the Set Auto grow file by 10 percent (recommended, but not required).

The new database is owned by the user who created it.

Set the Truncate Log on Checkpoint option and have the server generate checkpoints frequently. By selecting this option, the log is emptied periodically and should not fill up and cause rollbacks.

Create the AllFusion MM Database A–1

Create the AllFusion MM Database on Sybase

Note: For best performance ensure that separate devices are used to store the AllFusion MM data and the transaction log.

2. Add users.

For users to access the database you must either add existing logins as users to the database or create new logins and add them as users of the database. A login is an entity allowed to connect to the database server; a user gives a login the right to use a particular database.

If you use Windows security, you must add Windows users to the database.

3. Check tempdb size.

Significant temporary space is required for installation and use. The temporary segments need at least 16 MB of available space. You should also increase available space as the number of concurrent users increase.

Create the AllFusion MM Database on Sybase These instructions are for the DBAs and system administrators responsible for installing AllFusion MM on a Sybase database management system.

To install AllFusion MM on a Sybase database management system, follow these steps:

1. Create devices and databases.

To create the device you can use a graphical user interface (GUI) tool, ISQL (all versions), SQL Administrator, or Enterprise Manager. If a GUI tool is not available, you can use ISQL to type in the appropriate commands manually. Some examples of command statements are included in this appendix.

The size of the data device you create determines the size of the database. For AllFusion MM, the minimum database size is 32 MB so there has to be at least one device that is 32 MB. You should also locate the data device on a different disk (and disk controller) than the transaction log.

For optimum performance, ensure that separate devices are used to store the AllFusion MM data and the transaction log. For example, you can increase performance by creating a 50 MB data device and a 25 MB log device. A minimum of 40 MB of disk space (data and log) is required.

2. Add users.

For users to access the database you must either add existing logins as users to the database or create new logins and add them as users of the database. A login is an entity allowed to connect to the database server; a user gives a login the right to use a particular database.

A–2 AllFusion Model Manager Administrator Guide

Post-Database-Creation Tasks for Microsoft SQL and Sybase

3. Check the Stored Procedure Cache.

Set the Stored Procedure Cache size to at least 8 MB. Setting it higher improves performance, especially when many users are accessing the server concurrently. Setting it lower results in fatal errors and rollbacks when the Stored Procedure Cache size is exceeded.

Note: The AllFusion MM installation creates more than 100 stored procedures. The AllFusion MM client invokes these stored procedures to control changes to the data in the AllFusion MM database.

4. Check tempdb size.

Significant temporary space is required for installation and use. The temporary segments need at least 16 MB of available space. You should also increase available space as the number of concurrent users increase.

5. Check memory allocated to the database server.

Allocate at least 32 MB of RAM to the database server. The amount of RAM allocated should be half of the available RAM on the server machine.

Post-Database-Creation Tasks for Microsoft SQL and Sybase After you complete these steps, run the Administrative Setup program located on the AllFusion MM CD-ROM. The Setup program prompts you for an AllFusion MM installation directory. By default this directory is C:\Program Files\CA\AllFusion ERwin Model Manager r7, but the path may have been changed during installation.

Note: Do not attempt to run the AllFusion MM Setup program unless you are certain that the computer you are using can connect to the target server. For more information about tips on how to determine if your installation computer can connect to the target server, see Microsoft SQL Server Connections or Sybase Connections in this appendix.

When you install AllFusion MM, the Microsoft SQL installer can be ‘owner,’ ‘user with DB owner privileges,’ or ‘user with alias as DB owner privileges.’ The Sybase installer can be ‘owner,’ ‘user with sa_role,’ or ‘user with alias as DB owner.’



Microsoft SQL Server Connections

AllFusion MM uses DB_LIBRARY to connect to Microsoft SQL.

Sybase Connections

AllFusion MM uses CT_LIBRARY to connect to Sybse.

Useful Transact SQL Commands

If a graphical DBMS access tool is not available you can use Transact SQL commands through ISQL. Use the following examples to help you create a device, create a database, and add logins.

Create a Device Example

To create a device, use the Transact SQL DISK INIT command through ISQL, follow these steps: DISK INIT NAME = 'mmdata', /* The logical name. */ PHYSNAME = 'C:\SQL\DATA\mmdata.dat', /* The physical name. */ VDEVNO = 1<= virtual_device_number => 255 /* System dependent. */ SIZE = number_of_2K_blocks /* 1024 here is 2MB!!! */ [, VSTART = virtual_address, /* Optional */ CNTRLTYPE = controller_number] /* Optional */

Create a Database Example

To create a database, use the Transact SQL CREATE DATABASE command through ISQL, follow these steps: CREATE DATABASE mmmaster [ON {DEFAULT | database_device} [= size_in_megabytes] /* The device created in #1. */ [, database_device [= size_in_megabytes]]...] /* A database can span devices. */ [LOG ON database device [= size_in_megabytes>] /* Separate log device. */ [, database device [= size_in_megabytes]]...] /* A transaction log can span devices. */



Create Logins Example

To add logins to the database, refer to the following example of the sp_addlogin and sp_adduser commands using Transact SQL through ISQL, follow these steps: sp_addlogin login_id [, passwd [, defdb [, deflanguage]]]

and sp_adduser login_id [, username [, grpname]]

Once you have executed these commands, the DBA can alias an existing login as the Database Owner (dbo) or change the dbo to an existing login using sp_changedbowner.

Use ISQL to execute the following: sp_changedbowner login_id [,true]

where login_id is the login ID of the new database owner.

Troubleshoot Installation Problems

The following provides help for solving minor problems during installation:

Unable to Create AllFusion MM Database during Install Symptom:

I am unable to create the AllFusion MM database during an initial install.

Solution:

Rerun the AllFusion ERwin DM installation program, but clear all of the AllFusion MM Installation Options in the AllFusion MM Installation dialog.



SQL Server 2000 (using db-lib) error 4147, severity 15 error during the creation of the AllFusion MM Database

Symptom:

When I am trying to initialize my mart on Microsoft SQL 2005, I am getting an SQL Server 2000 error.

Solution:

By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower. See Check Database Compatibility Level for Microsoft SQL Server 2005 in the Install and Initialize AllFusion MM Chapter of this guide for details on how to set this option.

System Logs are Full Symptom:

I receive a message that the system logs are full.

Solution:

Use a DBMS utility (for example, SQL Object Manager) and type the appropriate command (for example, dump tran <erwinmm> with no_log) to purge the transaction log before you install a new version of AllFusion MM. Increase the size of the log file before you reinstall.

SQL 1105 Error Symptom:

When I am upgrading to AllFusion MM r7, during the Mart conversion process, I get the message “Sql 1105”.

Solution:

Stop the conversion process, and either free hard disk space or add hard disk. You should delete the already created r7 AllFusion MM tables and then re-attempt the conversion.


Create the AllFusion MM Database on Oracle

Upgrade the AllFusion MM Version Symptom:

I need to upgrade my AllFusion MM database to the newest version.

Solution:

After you have upgraded your AllFusion MM software, open AllFusion MM (double-click on the AllFusion MM Icon in Windows Program Manager) and click the Update button in the AllFusion MM dialog to update the AllFusion MM tables and stored procedures without overwriting your existing data.

Create the AllFusion MM Database on Oracle These instructions are for the DBAs and system administrators responsible for installing AllFusion MM on an Oracle database management system. Information provided in this section includes troubleshooting tips on installation and Oracle connectivity software requirements.

You must perform the following steps to install AllFusion MM on an Oracle database management system. These steps may be performed using graphical tools but you can also use SQL *Plus (all versions), SQL*DBA (either command line or full screen mode), or the Oracle Enterprise Management Console that ships with Oracle Version 8.0 or later. Examples of SQL commands are included where appropriate. Data file paths, data file sizes, role names, and user names are included for example only.

To install AllFusion MM on an Oracle database management system, follow these steps:

1. Check SYSTEM tablespace.

The AllFusion MM installation creates several stored procedures. All triggers, stored procedures, and packages are kept in the Oracle SYSTEM tablespace. The standard size of the SYSTEM tablespace assumes that you are not using procedural options, so the SYSTEM tablespace will often need to be expanded. If other Oracle applications are not using procedural code, then the SYSTEM tablespace should be expanded to 32 MB. If other Oracle applications also use procedural code, expand the SYSTEM tablespace to at least 32 MB.



2. Check Rollback Segment tablespace.

If your instance uses UNDO tablespace, do not create rollback segments.

Significant rollback space is required for installation and use. The rollback segments should be in their own separate tablespace and each have at least 16 MB of available space. There should be one rollback segment for every four concurrent users, with a maximum of 50 rollback segments. The available space should scale upward with increasing numbers of rollback segments. Finally, the rollback segment optimal parameter should be set to control rollback segment growth and space consumption.

Note: For steps 3, 4, and 5, use Dictionary-managed tablespace.

3. Create an AllFusion MM data tablespace of at least 32 MB.

For example: CREATE TABLESPACE MyMart DATAFILE ‘/db01/oracle/rdbms9i/data/mymart.ora’ SIZE 100M; Or For Locally Managed extents: CREATE TABLESPACE Mymart DATAFILE ‘/db01/oracle/rdbms9i/data/mymart.ora‘ SIZE 100M; EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO

4. Create an AllFusion MM index tablespace of at least 32 MB.

For example: CREATE TABLESPACE MMARTINDEX DATAFILE ‘/db02/oracle/rdbms9i/data/mmartindex.ora‘ SIZE 75M; Or For Locally Managed extents: CREATE TABLESPACE MMARTINDEX DATAFILE ‘/db02/oracle/rdbms9i/data/mmartindex.ora‘ SIZE 75M; EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO

5. Create an AllFusion MM temporary tablespace.

For example: CREATE TEMPORARY TABLESPACE MMTEMP TEMPFILE ‘/db03/oracle/rdbms9i/data/mmarttemp.ora‘ SIZE 50M; Or For Locally Managed extents: CREATE TEMPORARY TABLESPACE MMTEMP TEMPFILE ‘/db03/oracle/rdbms9i/data/mmarttemp.ora‘ SIZE 50M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Note: For more details on syntax and options regarding tablespace creation, see the appropriate Oracle documentation.



6. Create an Oracle user with DBA privileges to be used by the AllFusion MM Installer or designated schema owner.

Assign the AllFusion MM data tablespace as this user’s default tablespace, and the AllFusion MM temporary tablespace as this user’s temporary tablespace. For example: CREATE USER STEVE IDENTIFIED BY STEVE DEFAULT TABLESPACE MyMart TEMPORARY TABLESPACE MMTEMP QUOTA UNLIMITED ON MyMart QUOTA UNLIMITED ON MMARTINDEX;

7. Create an AllFusion MM Installer role.

The following example is the role required by the Oracle user installing AllFusion MM. CREATE ROLE MMINSTALL;

8. Grant Oracle privileges to the AllFusion MM Installer role.

The following example shows the Oracle privileges that the AllFusion MM Installer needs to install AllFusion MM on Oracle. For the last command, you must log in as sys with the sysdba role in the user-name or the command will fail. grant create sequence to MMINSTALL; grant create table to MMINSTALL; grant create view to MMINSTALL; grant drop public synonym to MMINSTALL; grant create public synonym to MMINSTALL; grant create procedure to MMINSTALL; grant select on dba_data_files to MMINSTALL;

9. Create an AllFusion MM User role.

For example: CREATE ROLE MMUSER;

When you select this role as the AllFusion MM User role during Step 4 of the installation procedure, the Setup program generates grant statements that grant object level privileges to this role. For more information about the details on Step 4 of the installation process, see Initializing AllFusion MM on an Oracle DBMS in the chapter “Installing and Initializing AllFusion MM.”



10. Grant the create session Oracle privilege to the AllFusion MM User role.

For example: grant create session to MMUSER;

Note: The create session privilege is the only privilege that an Oracle user needs to use the AllFusion MM database.

11. Grant the AllFusion MM User role to each Oracle user that uses AllFusion MM.

For example: grant MMUSER to USER1; grant MMUSER to USER2; grant MMUSER to USER3; . . .

Important! You must specify the User role name created in Step 9 for these grant statements.

12. Grant the AllFusion MM User role to the AllFusion MM Installer role.

For example: grant MMUSER to MMINSTALL;

13. Grant the AllFusion MM Installer role to the AllFusion MM Installer user. You must also grant DBA privileges to the user you designate as the AllFusion MM Installer.

For example: grant MMINSTALL to STEVE; grant DBA to STEVE;

Note: The DBA role is necessary only during the AllFusion MM installation or upgrade. You can strip the installer of the DBA role after the installation or upgrade is complete.

14. Run the AllFusion MM Setup program.

When the setup is complete, choose the Initialize AllFusion MM option and connect to Oracle as the AllFusion MM Installer user (for example, STEVE).



15. Select the AllFusion MM tablespaces and AllFusion MM User role.

When prompted for tablespace and role information, choose the AllFusion MM data tablespace, the AllFusion MM index tablespace, and the AllFusion MM User role (the role created in Step 9).

16. Add the AllFusion MM Installer user as the AllFusion MM administrator.

When the AllFusion MM Security Manager is opened, drag the AllFusion MM Installer User icon to the AllFusion MM administrator security profile. You can also designate one of the users with the MMUSER role (from step 12) for routine operations. This completes the setup and you can begin using AllFusion MM.

Note: After successful installation, you can revoke the AllFusion MM Installer role and grant the AllFusion MM User role to the AllFusion MM Installer user.

Oracle Connections

AllFusion MM uses Oracle SQL*Net for client access to the database server. Although Oracle provides two utilities (SQL*Net Configuration tool and Network Manager tool) for defining your network, clients, and server, you need a network administrator to perform this task. The server system administrator is usually the best candidate.

Note: For more information about these utilities, see the Oracle SQL*Net Administrator’s Guide.

SQL*Net requires certain files on both the server and client machines. These files can be generated by the Oracle networking tools, but can also be created using a text editor. Since Oracle will not support those sites that generate these files manually, it is better to use the appropriate Oracle utilities. The following table lists the files required by SQL*Net:

File Name Required On File Contents

TNSNAMES.ORA Client and Server A list of service names and connect descriptors for network destinations (tells the client where it can make connections)

SQLNET.ORA Client and Server A list of optional diagnostic parameters

LISTENER.ORA Server only A list of names and addresses of all listeners on a machine and the Oracle SIDs for the databases known on that machine



Installed AllFusion MM Objects

Installing AllFusion MM on an Oracle database management system creates the following database objects:

Tables

Indexes

Stored procedures

Public synonyms

Useful Oracle SQL Commands

If a graphical DBMS access tool is not available, you can use Oracle SQL commands through SQL*DBA or SQL*Plus. Use the following examples to help you create a tablespace, create a rollback segment, and create a user. For more information, see the Oracle SQL Language Reference Manual.

Create a Tablespace

To create a tablespace, use the CREATE TABLESPACE command: CREATE TABLESPACE mm_data /* The tablespace name. */ DATAFILE ‘C:\ORANT\DATABASE\mmdata.dat‘ /* The data file name. */ SIZE integer_value K or M or G /* The data file size */ DEFAULT STORAGE ( /* The default storage parameters */ INITIAL integer_value K or M or G /* The initial extent size */ NEXT integer_value K or M or G /* The next extent size */ PCTINCREASE integer_value /* The percent to grow extents */ MINEXTENTS integer_value /* The minimum number of extents */ MAXEXTENTS integer_value /* The maximum number of extents */ );

Create a Rollback Segment

To create a rollback segment, use the CREATE ROLLBACK SEGMENT command: CREATE PUBLIC ROLLBACK SEGMENT mm_rbs_1 /* The rollback segment name */ TABLESPACE mm_rbs /* the tablespace name for the RBS */ STORAGE ( /* The storage parameters for the RBS */ INITIAL integer_value K or M or G /* The initial extent size */ NEXT integer_value K or M or G /* The next extent size */ PCTINCREASE integer_value /* The percent to grow extents */ MINEXTENTS integer_value /* The minimum number of extents */ MAXEXTENTS integer_value /* The maximum number of extents */ OPTIMAL integer_value K or M or G /* the optimal size for the RBS */ );



Create Oracle Users

To create a user, use the CREATE USER command: CREATE USER mm_user_1 /* The user id name */ IDENIFIED BY password /* The user password */ DEAFULT TABLESPACE tablespace_name /* The user’s default tablespace */ TEMPORARY TABLESPACE tablespace_name /* The user’s temporary tablespace */ QUOTA unlimited_or_integer_K_M_G ON tablespace_name /* The user’s quota on a tablespace */ ;

Grant Privileges to Users

To grant a user privileges, use the GRANT command: GRANT role_or_privilege_name TO user_or_role ;

Troubleshoot Installation Problems

The following provides help during installation:

AllFusion MM Fails to Connect to Oracle Symptom:

AllFusion MM fails to connect to Oracle.

Solution:

Check that you have supplied the correct Oracle user ID and password, and the correct SQL*Net connect string.

Ping the server to verify that network connectivity is functioning.

Verify that the client TNSNAMES.ORA file is current and correct, and the SQL*Net Listener is currently running on the server.



Unable to Create the AllFusion MM Database During Install Symptom:

I am unable to create the AllFusion MM database during an initial installation.

Solution:

Rerun the AllFusion ERwin DM installation program, but clear all of the installation options in the AllFusion ERwin DM installation dialog.

Tablespace is Full (Unable to Allocate Extents) Symptom:

I receive a message that the tablespace is full (unable to allocate extents).

Solution:

Use a DBMS utility (like Oracle Enterprise Management Console) and type the appropriate command to either add another data file to the tablespace or extend the current data file.

The Rollback Segment has Reached the Maximum Number of Extents Symptom:

I receive a message that the rollback segment has reached the maximum number of extents.

Solution:

Use a DBMS utility (like Oracle Enterprise Management Console) and change the rollback segment to use both larger initial and next extents; you may want to increase the pctincrease parameter too.

Upgrade the AllFusion MM Version Symptom:

I need to upgrade my AllFusion MM database to the newest version.

Solution:

After you have upgraded your AllFusion MM software, open AllFusion MM (double-click on the AllFusion MM Icon in Windows Program Manager) and click the Update button in the AllFusion MM dialog to update the AllFusion MM tables and stored procedures without overwriting your existing data.



Cannot Access AllFusion MM After it is Installed Symptom:

I cannot access AllFusion MM after it is installed.

Solution:

Verify that the User role created during the creation of the AllFusion MM database was specified when the AllFusion MM database was initialized on the Oracle DBMS.


Appendix

B Microsoft SQL and Sybase Server Tuning Recommendations

The AllFusion MM database is quite dynamic, with many queries and data manipulations performed with each model save and load. Although the Microsoft SQL Server and Sybase architectures differ in some ways, the basic operation and configuration of both server environments is the same. Where appropriate, this appendix draws attention to the differences between the two architectures.

This appendix contains performance tuning guidelines for the AllFusion MM database including:

Placement of log and database files

Server-level tuning parameters

Database tuning parameters

Database and log sizing

Database maintenance

Physical Tuning Parameters The configuration changes that must be made to Microsoft SQL Server and Sybase for optimum performance with maximum fault tolerance and recoverability are provided in the following sections.

Hardware Configurations

Consider implementing AllFusion MM on a multiprocessor system, especially if multiple data modelers are saving information simultaneously. Install AllFusion MM on a stand-alone Microsoft SQL server, if possible, or on a development machine. The AllFusion MM database's overhead noticeably affects other databases running on the same system during save and load operations. If few modelers save and load simultaneously, the overhead is less.

To improve caching performance, implement AllFusion MM on server machines that have at least 256 MB of RAM.

Microsoft SQL and Sybase Server Tuning Recommendations B–1

Server-Level Tuning Parameters

Database Placement

AllFusion MM databases are written to in bursts of activity. Stored procedures and bulk insert statements are used to minimize overhead when saving data to Microsoft SQL Server. To optimize performance, place the database on low activity Microsoft SQL Server files. If possible, place the log and data segments on different physical drives to reduce contention between log writes and database reads.

Data Redundancy

Make sure that the transaction log is mirrored on a separate drive to maximize recoverability of the AllFusion MM database. If the uptime of the database is considered critical, mirror both the database and the transaction logs; you may also want to mirror the other Microsoft SQL Server files. Consider OS mirroring to speed the mirroring process and make it easier to manage.

Server-Level Tuning Parameters Server-level tuning task recommendations are:

Configure Microsoft SQL Server to use as much memory as possible. Allocating more memory to the Microsoft SQL Server caching mechanisms means less physical reads from the disk and improved database query performance.

Allow several megabytes of disk space for the procedure cache since AllFusion MM uses many stored procedures.

Configure two additional user connections for each simultaneous AllFusion MM user. Two connections per session are used.

The following table shows the recommended configuration parameters for a Microsoft SQL Server running AllFusion MM:

Parameter Type Recommended Value Notes

memory (Sybase 11: "total memory")

512 MB More memory implies less physical I/O

procedural cache 30 percent AllFusion MM is stored procedure intensive

user connections 2 times the number of concurrent sessions

Add this value to existing user connection values

B–2 AllFusion Model Manager Administrator Guide

Named Cache Configuration

Named Cache Configuration For Sybase systems, consider setting up a 4 KB pool for the default data cache. Sybase writes I/O to the log more often in 4 KB increments than in 2 KB increments (the default). You can set up a 4 KB I/O pool using sp_poolconfig, but you must restart Microsoft SQL Server to enable the 4 KB I/O writes to the log. Set the pool up as a smaller subset of the cache.

Note: Be careful when making changes to the data caching systems in Sybase. Monitor your changes with SQL Monitor or sp_sysmon to ensure that the changes you make do not starve the 2 KB I/O pool or other caches.

The following table shows the recommended size of the 4 KB I/O pool for small, medium, and large servers:

Server Size Data Cache Size 4 KB I/O Pool Size

Small 128 MB 4 MB

Medium 512 MB 6 MB

Large 1 GB 10 MB

Database Tuning Parameters Make database tuning adjustments in three different areas:

Transaction log

Threshold procedures

Database options

Transaction Log

Microsoft SQL Server keeps a transaction log for each database. The transaction log keeps a before and after image of each change made in the database, and can be backed up independently of the database by issuing a DUMP TRANSACTION command.

Note: A side effect of the DUMP TRANSACTION command is that it clears the inactive transactions from the log to reduce its size.

Back up the transaction log frequently. This keeps the transaction log small and reduces the amount of data lost in the event of a severe database corruption.


Database Tuning Parameters

Threshold Procedures

For Sybase, enable a threshold procedure for the last-chance threshold to back up the log when it runs out of disk space. Since Microsoft SQL Server does not provide such an option, you must back up the log frequently to keep the log small.

The following shows a sample Sybase threshold action procedure: create procedure sp_thresholdaction @dbname char(40), @segment_name char(40), @space_left int, @status int as /* make the thresholdaction procedure backup the log */ declare @backdevice varchar(255) select @backdevice= '/u/backups/tranfile'+ convert(char(8),getdate(),4) dump transaction mart to @backdevice go

Database Options

To ensure maximum recoverability, do not enable the “trunc.log on chkpt” option, since the log is cleared automatically after each checkpoint operation. If the database device becomes damaged with the log device still active and this option is set, the database cannot be recovered using the log files since they will be almost empty.

Check Database Compatibility Level for Microsoft SQL Server 2005

By default for Microsoft SQL Server 2005, the compatibility level for a new database created in Microsoft SQL Server 2005 is “90”. It is necessary to set the database compatibility level to 80 or lower.

To change the database compatibility level from the database UI, follow these steps:

1. From the Start menu, select Programs, Microsoft SQL Server 2005, SQL Server Management Studio and connect to the server.

The Database Properties dialog opens.

2. Select SQL Server 2005 (80 or lower) in the Compatibility level field and click OK.

The database compatibility is modified.

Note: The database compatibility level can also be modified by running the following code: sp_dbcmptlevel@dbname = “dbname”, @ new_cmptlevel=80


Database and Log Sizing

Database and Log Sizing Since the AllFusion MM database is a dynamic database environment, allow plenty of space for the models you create. Tests have shown that models generate between 10 KB and 20 KB of data per entity during initial save times. Log overhead per object is approximately 15 KB to 21 KB per entity. Typically, you might size the log between 15 to 25 percent of the size of the database device. Instead, allocate 50 to 65 percent of the database size to the log to avoid running out of room in the log for a typical model save.

A typical AllFusion MM database can range in size between 50 MB and 300 MB. Size the transaction log accordingly. A 50 MB data device can store several large models (about 2,500 entities and 100,000 total objects), but keep in mind that the database becomes more flexible and has less storage space issues when the data device is large.

The following table shows the recommended database size and log size for small, medium, and large AllFusion MM databases:

Database Size Database Device Transaction Log Device

Small 50 MB 30 MB

Medium 150 MB 50 MB

Large 300 MB 100 MB

Maintenance To maintain an efficient AllFusion MM database, perform the following maintenance tasks:

Run UPDATE STATISTICS and execute sp_recompile frequently on every table in the AllFusion MM database. This keeps the statistics up-to-date for the indexes, resulting in better overall performance.

Periodically recreate the clustered indexes in the database to reduce fragmentation. Be sure to back up the database and transaction log daily.

Run DBCC CheckDB(), DBCC CheckCatalog(), and DBCC CheckAlloc() or DBCC NewAlloc() on the AllFusion MM database nightly, if possible, to check for corruption and inconsistencies in the database. Check the output of these queries and look for keywords like corrupt. Any problems detected by these commands are sent to the query output, so save the files and scan them regularly.


Maintenance

The following table shows maintenance tasks and the recommended frequency for performing these tasks:

Maintenance Task Recommended Frequency

Reason

DBCC Checkdb Nightly Check for corruption in databases.

DBCC NewAlloc Weekly Check for allocation corruption (Microsoft SQL Server only).

DBCC CheckAlloc Weekly Check for allocation corruption (Microsoft SQL Server only).

DBCC CheckCatalog Weekly Check for system table inconsistencies.

UPDATE STATISTICS Nightly Recreates the statistics page for each index.

EXEC sp_recompile Nightly Tells which stored procedures have changed.

Backup Database Weekly Full backup of database should be done at least weekly, if not nightly.

Backup Transaction Log

Daily Backing up the transaction log daily saves all committed transactions and clears the log.

Nightly Maintenance Script

The following script is the recommended nightly maintenance script: UPDATE STATISTICS mmObject go UPDATE STATISTICS mmObjectProperty go

DBCC Commands

Use the following DBCC commands to perform maintenance tasks on the AllFusion MM database: DBCC CheckDB(mart) go DBCC CheckAlloc(mart) go DBCC CheckCatalog(mart) go


Appendix

C Oracle Tuning Recommendations

Oracle servers are available on many different platforms ranging from PCs to mainframes. To support the wide range of hardware platforms and application requirements, Oracle servers have a number of configuration options that you can use to tailor the behavior of an Oracle database. You can also use these configuration options to tailor your AllFusion MM database.

If the Oracle server is not dedicated solely to AllFusion MM, as database administrator you must be careful to balance the requirements of all users on the server. This is particularly true for database servers that support OLTP (On Line Transaction Processing) applications that require very tight response characteristics.

Recommendations for the following settings that are required for optimum performance from an AllFusion MM database stored on an Oracle server are provided for:

Disk configuration

Database configuration

Physical storage object parameters

Oracle database backup and recovery information are not included. For more information, see the Oracle documentation.

Oracle Tuning Recommendations C–1

Recommended Disk Configurations

Recommended Disk Configurations The layout of Oracle database files on physical disk drives plays a major role in the performance of the database. When used with AllFusion MM, Oracle is called upon to perform large bursts of database operations (fetches, inserts, updates, and deletes) in a short period of time. This usage pattern often requires Oracle to perform a significant amount of disk I/O operations. For good performance, it is imperative that as many I/O operations as possible be performed in parallel. This enables Oracle to retrieve data faster during fetches and to write data faster during inserts, updates, and deletes.

To maximize I/O access parallelism, split the Oracle database files across many physical disks. Ideally, you should place the database on four physical disks. If this is not possible, you can use three, two, or one disk systems. The following diagram shows configurations for the placement of the database in four, three, two, and one disk systems:

Note: Installing Oracle on a single disk system causes significant performance degradation.

C–2 AllFusion Model Manager Administrator Guide

Database Configuration

Database Configuration Proper database configuration is essential to both the smooth operation and good performance of an Oracle database. You can use the configuration options described in the following sections to optimize the Oracle server for AllFusion MM processes.

Processes

Oracle must be preconfigured at startup with a maximum number of processes that can access the database. The parameter that controls the maximum number of processes, called PROCESSES, is defined in the INIT.ora or INIT<SID>.ora file. It should be set to the maximum potential number of concurrent users plus seven. The additional seven are for Oracle background processes that must also access the database. Setting the number of processes at a lower value may prevent some users from accessing the server during peak usage times. Setting the number of processes at a higher value may waste a small amount of system memory resources.

Shared Pool

The shared pool is an area of Oracle's memory that includes two main structures:

The library cache, which stores parsed SQL and PL/SQL statements

The dictionary cache, which stores the Oracle data dictionary (or Oracle's metadata)

The SHARED_POOL_SIZE parameter is defined in the INIT.ora or INIT<SID>.ora file and is used to regulate the size of the shared pool. Set the SHARED_POOL_SIZE parameter to a minimum of 3500000 (3.5 million). Setting the shared pool to a smaller value may degrade performance, forcing Oracle to do disk I/O to retrieve objects that cannot fit into the shared pool. A larger shared pool may be required, depending on the size and number of models and the number of users accessing AllFusion MM.



Buffer Cache

The buffer cache serves as a memory cache for all data going to and from Oracle data files. When Oracle needs a block of data it first checks whether that block exists in the buffer cache. If it does, Oracle gets the data from the buffer cache—avoiding an expensive disk access. Having a large enough buffer cache allows the Oracle server to bypass most I/O requests.

Buffer cache size is controlled by the DB_BLOCK_BUFFERS parameter defined in the INIT.ora or INIT<SID>.ora file. Set the buffer cache to a minimum of 4 MB. Values smaller than 4 MB force Oracle to do many more I/O requests and significantly degrades the performance. Values larger than 4 MB improve performance and should be used if memory is available.

Note: In Oracle, the DB_BLOCK_BUFFERS parameter is specified as a number of database blocks rather than actual size in bytes. To compute the value of DB_BLOCK_BUFFERS, divide the desired buffer cache size in bytes by the database block size defined by the DB_BLOCK_SIZE parameter in the INIT.ora or INIT<SID>.ora file.

Redo Log Files

Redo log files contain a record of all Data Manipulation Language (DML) commands (such as INSERT, UPDATE, and DELETE commands) performed on the database. As DMLs are performed, the Oracle engine writes them into sequential Redo log files. Periodically, an Oracle background process retrieves the DMLs from the Redo log files and writes the actual changes to the Oracle tablespace files. This mechanism allows Oracle to defer most of the I/O burden associated with DMLs to a background process that does not slow down the client processes.

Note: Oracle Redo log files are treated by the database engine as a ring. When one file fills up, the engine performs a log switch and starts writing to the next log file in the ring. When that log file fills, the engine switches again, and so on.

The number and size of the Redo log files is an important performance consideration. If the log files are too small or if there are not enough of them in the ring, Oracle may have to stall on a log switch. If this happens, the DMLs in the next log in the ring may not have been written to the tablespace files, and therefore the next log file has not been archived by the background ARCH process. For more information about Redo log archiving, see the Oracle documentation.

Redo log files are initially created when the database is created. However, Redo log files can be added or deleted at any time using Data Definition Language (DDL) statements.



You should have at least four Redo log files, each 2 MB in size. A smaller number of Redo log files or a smaller Redo log file size may cause I/O bottlenecks. If the disk space is available, using more than four Redo log files further reduces the chances of delayed log switches. Larger Redo log files improve performance, but care must be taken to adequately schedule checkpoints that write DMLs stored in the Redo logs to the tablespace files.

If the number of disks permits, you should mirror Redo log files by creating Redo log groups with two mirrored members per group. This offers the database some protection against single disk errors.

To increase space in the Redo logs, follow these steps:

1. Log into Oracle using SQL*Plus as SYSDBA or SYSOPER.

2. Run the following script to create eight Redo logs that are 2 MB each: rem -- parm1 -- temp dir

rem Generate creation script SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_11.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_11.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_12.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_12.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_13.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_13.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_14.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_14.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_15.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_15.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) )



|| 'REDO_16.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_16.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_17.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_17.LOG' ) UNION SELECT 'ALTER DATABASE ADD LOGFILE ''' || SUBSTR ( MEMBER , 1 , INSTR ( MEMBER , '\' , -1 , 1 ) ) || 'REDO_18.LOG'' SIZE 2M ;' from V$LOGFILE where ROWNUM = 1 and not exists ( SELECT 1 from V$LOGFILE where MEMBER like '%REDO_18.LOG' ) . Spool &1.AddLog.ORA / Spool Off COMMIT ; SELECT 'ALTER SYSTEM SWITCH LOGFILE ;' from V$LOG where ROWNUM < 5 . Spool &1.SwtchLog.ORA / Spool Off COMMIT ; rem Generate Deletion script SELECT 'ALTER DATABASE DROP LOGFILE GROUP ' || TO_CHAR ( GROUP# ) || ' ;' from V$LOG where BYTES < 2097152 . Spool &1.DropLog.ORA / Spool Off COMMIT ; @&1.AddLog.ORA $Del &1.AddLog.ORA COMMIT ; @&1.SwtchLog.ORA $Del &1.SwtchLog.ORA COMMIT ; @&1.DropLog.ORA $Del &1.DropLog.ORA COMMIT ;

3. Run the following query to verify the new Redo log configuration: SQLWKS> select group#, status, bytes from v$log;

Note: Oracle does not allow you to drop an older Redo log file that is still active. If that happens, drop that log file manually.


Storage Parameters

Redo Log Buffer

The Redo log buffer is an area in memory that Oracle uses to collect DMLs before they are written to the Redo log files. The log file write occurs when either a transaction commits or a Redo log buffer is full. Since AllFusion MM tends to generate fairly large transactions, use a log buffer size of 163840 bytes. (For single disk Oracle installations, use a log buffer size of 655360 bytes.) Setting the Redo log buffer size to a value smaller than the recommended value may degrade I/O performance. Using a larger value requires more memory.

The Redo log buffer size is defined using the LOG_BUFFER parameter in the INIT.ora or INIT<SID>.ora file.

Checkpoints

An Oracle checkpoint is an event that posts DMLs from the Redo log files to the tablespace files. Checkpoints always occur after a Redo log file switch and can also be configured to occur at predefined time intervals. For AllFusion MM, which generates large transactions, checkpoints should occur only after log switches to minimize I/O. To ensure a checkpoint only after a log switch, do not set the LOG_CHECKPOINT_INTERVAL and LOG_CHECKPOINT_TIMEOUT parameters in the INIT.ora or INIT<SID>.ora file.

Storage Parameters Object storage parameters in Oracle determine the amount of space allocated for each object in the database. Setting these parameters correctly is critical to both operation and performance of the database. Incorrect storage allocations can quickly cause a database object to run out of space, which prevents AllFusion MM from saving models to the repository. Inefficient selection of storage parameters can lead to performance problems by forcing Oracle to do time-consuming space management operations during DML statement execution.

Recommendations for storage parameter values for the following three different model categories are provided:

Small data models: 1 to 50 Entities

Medium data models: 51 to 100 Entities

Large data models: over 100 Entities


Storage Parameters

Rollback Segments

Note: If you do not use rollback segments, you can skip this topic.

Rollback segments contain undo information for all changes performed by noncommitted transactions. Rollback segments are a shared resource used by all active transactions in the database. When a transaction starts, Oracle binds that transaction to a particular rollback segment. As DMLs in the transaction execute, rollback segment space is used. For large transactions, rollback segments may need to allocate new extents as the transaction continues. When the transaction ends, a properly configured Oracle database releases the additional rollback extents so that they can be used for other rollback segments. To ensure that the additional rollback extents are released, configure the OPTIMAL parameter for each rollback segment.

Use a maximum of five transactions per rollback segment by setting the TRANSACTIONS_PER_ROLLBACK_SEGMENT parameter in the INIT.ora or INIT<SID>.ora file. Use the following rollback segment storage parameters for small, medium, and large models:

Model Type Initial Extent Size Next Extent Size Optimal Size

Small 1 MB 1 MB ~ 2 MB x (# of transactions)

Medium 6 MB 6 MB ~ 12 MB x (# of transactions)

Large 6 MB 6 MB ~ 12 MB x (# of transactions)

Note: In the previous table, “# of transactions” is the maximum number of simultaneous AllFusion MM connections to Oracle.


Storage Parameters

In Oracle it is common to see the following error statement when the Rollback logs are not set up optimally:

ORA-01562 failed to extend rollback segment number string

To set the optimal configuration for the Rollback logs of large databases, follow these steps:

1. Login to Oracle as SYS or SYSTEM.

2. Run the following query and check the result to view the current configuration of the Rollback Segments: SQLWKS> select SEGMENT_NAME, INITIAL_EXTENT, NEXT_EXTENT, MIN_EXTENTS, MAX_EXTENTS, STATUS from dba_rollback_segs; SEGMENT_NAME INITIAL_EX NEXT_EXTEN MIN_EXTENT MAX_EXTENT STATUS ------------ ---------- ---------- ---------- ---------- ------- SYSTEM 51200 51200 2 121 ONLINE RB_TEMP 102400 102400 2 121 OFFLINE RB1 2097152 2097152 2 121 ONLINE RB2 2097152 2097152 2 121 ONLINE RB3 2097152 2097152 2 121 ONLINE RB4 2097152 2097152 2 121 ONLINE RB5 2097152 2097152 2 121 ONLINE RB6 2097152 2097152 2 121 ONLINE RB7 2097152 2097152 2 121 ONLINE RB8 2097152 2097152 2 121 OFFLINE RB9 2097152 2097152 2 121 OFFLINE RB10 2097152 2097152 2 121 OFFLINE RB11 2097152 2097152 2 121 OFFLINE RB12 2097152 2097152 2 121 OFFLINE RB13 2097152 2097152 2 121 OFFLINE RB14 2097152 2097152 2 121 OFFLINE RB15 2097152 2097152 2 121 OFFLINE RB16 2097152 2097152 2 121 OFFLINE 18 rows selected.

Note: In this example, there are sixteen rollback segments with 2 MB INITIAL EXTENT, 2 MB NEXT EXTENT, and MAX EXTENTS of 121 MB.


Storage Parameters

3. Run the following query for each Rollback Segment: alter rollback segment rb1 offline; drop rollback segment rb1; create public rollback segment rb1 tablespace rollback_data storage (initial 6M next 6M minextents 2 maxextents 121 optimal 12M); alter rollback segment rb1 online; alter rollback segment rb2 offline; drop rollback segment rb2; create public rollback segment rb2 tablespace rollback_data storage (initial 6M next 6M minextents 2 maxextents 121 optimal 12M); alter rollback segment rb2 online; <Repeat for each Rollback Segment>

This query sets the optimal Rollback Segment configuration to 6 MB INITIAL EXTENT, 6 MB NEXT EXTENT, 2 MB MIN EXTENT, 121 MB MAX EXTENT, and 12 MB OPTIMAL.

4. Run the following query to verify the Rollback segment configuration changes: SQLWKS> select SEGMENT_NAME, INITIAL_EXTENT, NEXT_EXTENT, MIN_EXTENTS,MAX_EXTENTS, STATUS from dba_rollback_segs; SEGMENT_NAME INITIAL_EX NEXT_EXTEN MIN_EXTENT MAX_EXTENT STATUS ------------ ---------- ---------- ---------- ---------- ------- SYSTEM 51200 51200 2 121 ONLINE RB_TEMP 102400 102400 2 121 OFFLINE RB1 6291456 6291456 2 121 ONLINE RB2 6291456 6291456 2 121 ONLINE RB3 6291456 6291456 2 121 ONLINE RB4 6291456 6291456 2 121 ONLINE RB5 6291456 6291456 2 121 ONLINE RB6 6291456 6291456 2 121 ONLINE RB7 6291456 6291456 2 121 ONLINE RB8 6291456 6291456 2 121 ONLINE RB9 6291456 6291456 2 121 ONLINE RB10 6291456 6291456 2 121 ONLINE RB11 6291456 6291456 2 121 ONLINE RB12 6291456 6291456 2 121 ONLINE RB13 6291456 6291456 2 121 ONLINE RB14 6291456 6291456 2 121 ONLINE RB15 6291456 6291456 2 121 ONLINE RB16 6291456 6291456 2 121 ONLINE 18 rows selected.


Storage Parameters

Tablespaces

To improve performance you can create more than one tablespace for indexes. Then, after you install AllFusion MM, you can move some indexes into the other tablespaces.

The following table lists the suggested initial sizes for the AllFusion MM DATA and INDEX tablespaces:

Tablespace Small Medium Large

DATA 32 MB 51 MB 232 MB

INDEX 32 MB 28 MB 139 MB

DATA and INDEX tablespaces with these initial sizes can accommodate at least ten AllFusion MM models or versions.

Tables

The following table lists the recommended initial extent sizes in kilobytes for the most important AllFusion MM tables for small, medium, and large models:

Recommended Initial Extent Size (KB)

Table Name Small Medium Large

mmObject 1096 2193 10963

mmObjectProperty 3288 6579 32889

These initial extent sizes are chosen so that they can accommodate two versions of a model. These values are the recommended values of the INITIAL parameter in the STORAGE clause of the CREATE TABLE statement. The size of the next extent (NEXT parameter in the STORAGE clause) should be half of the corresponding initial size.


Storage Parameters

Indexes

The following table lists the recommended initial extent sizes in kilobytes for the most important AllFusion MM indexes for small, medium, and large models:

Recommended Initial Extent Size (KB)

Index Name Small Medium Large

XPKmmObject 1415 2829 14146

XPKmmObjectProperty 2098 4195 20975


Index

A

configuration administrative reports, 6-1 Oracle database, C-2, C-3

administrative tasks connections DBMS requirements, 1-5

to Microsoft SQL Server, A-4 introduction, 1-2 to Oracle, A-11 system requirements, 1-5 to Sybase Server, A-4

AllFusion ERwin DM reports conversion sharing in AllFusion MM, 6-1, 6-4

AllFusion Erwin DM and AllFusion PM Model Properties, 3-5 AllFusion MM database

creating on Microsoft SQL Server, A-1 AllFusion MM Properties, 3-5 creating on Oracle, A-7 from an AllFusion MM 4.1.4 database to an

AllFusion MM r7 database using Microsoft SQL Server or Sybase, 3-7

creating on Sybase, A-2 deleting, 2-9 objects, A-12 from an AllFusion MM 4.1.4 database to an

AllFusion MM r7 database using Oracle DBMS, 3-9

post-database-creation tasks, A-3

AllFusion MM Security Manager prerequisites, 3-2 features, 4-1 understanding the process, 3-5 reports, 6-3

D B

Data Browser, 6-1 browsing AllFusion MM information, 6-1 data cache size

Sybase, B-3 buffer cache Oracle, C-3 data redundancy

for Microsoft SQL Server, B-2

data tablespace sizing C Oracle, C-11

database configuration client connection software Oracle, C-3

for AllFusion MM, 1-8

Index–1

I database options Microsoft SQL Server, B-4

database placement index tablespace sizing for Microsoft SQL Server, B-2

Oracle, C-11 database sizing

indexes Microsoft SQL Server, B-5 Oracle, C-12

DBCC commands initializing AllFusion MM, 2-3 Microsoft SQL Server, B-6

on Microsoft SQL Server, 2-4 DBMS on Oracle, 2-7

database creation authority, 1-8 on Sybase, 2-4 preparing for AllFusion MM, 1-7

Installation Windows authentication, 1-7 prerequisites, 3-1

default security profiles installation of AllFusion MM in AllFusion MM, 4-2

administrative files, 2-1 deleting connections, A-4, A-11

AllFusion MM database, 2-9 database objects, A-12 on Microsoft SQL or Sybase, A-5 dialogs on Microsoft SQL Server, A-1, A-4 AllFusion MM Security Manager, 4-2 on Oracle, A-7, A-11, A-12, A-13 AllFusion MM Session Manager, 4-13 on Sybase, A-2, A-4 Users in AllFusion MM, 4-2 preparing your DBMS for, 1-7 troubleshooting installation problems, A-5, A-13 disk configurations

for Oracle, C-2 introduction, 1-1

E L

extent sizes license agreement Oracle indexes, C-12 understanding, 1-4 Oracle tables, C-11 upgrading, 3-1

log sizing Microsoft SQL Server, B-5 F

M finding more information, 1-9

maintenance H Microsoft SQL Server, B-5

maintenance script hardware configurations Microsoft SQL Server, B-6

for Microsoft SQL Server, B-1

Index–2 Administrator Guide

P

Microsoft SQL Server connections, A-4

Permission object class converting your database from AllFusion MM 4.1.4 to AllFusion MM r7, 3-7 in AllFuion MM, 4-3

data redundancy, B-2 physical tuning parameters database options, B-4 data redundancy, B-2 database placement, B-2 database placement, B-2 database sizing, B-5 hardware configurations, B-1 DBA steps for AllFusion MM installation, A-1 Microsoft SQL and Sybase, B-1 DBCC commands, B-6

prerequisites hardware configurations, B-1 to installing AllFusion MM, 1-7 initializing AllFusion MM on, 2-4

installing AllFusion MM on, A-1, A-4 log sizing, B-5

R maintenance, B-5 nightly maintenance script, B-6 server-level tuning, B-2

redo log buffer threshold procedures, B-4 Oracle, C-7 Transact SQL commands, A-4

transaction log, B-3 redo log files troubleshooting installation problems, A-5 Oracle, C-4 upgrading AllFusion MM on, 3-4

reports AllFusion MM Security Manager, 6-3 on AllFusion MM information, 6-1 O savingAllFusion ERwin DM reports to AllFusion MM, 6-4

Oracle rollback segments buffer cache, C-3 Oracle, C-8 connections, A-11 converting your database from AllFusion MM 4.1.4 to AllFusion MM r7, 3-9 S database configuration, C-3 DBA steps for AllFusion MM installation, A-7 disk configurations, C-2 security indexes, C-12 features, 4-1 initializing AllFusion MM on, 2-7 reports, 6-3 installing AllFusion MM on, A-7, A-11, A-12 redo log buffer, C-7 security permissions redo log files, C-4 inheriting, 4-9 rollback segment, C-8 overriding, 4-9 shared pool, C-3 overriding inherited permissions, 4-10 SQL commands, A-12

security profiles storage parameters, C-7 assigning to an AllFusion MM user, 4-6 tables, C-11 in AllFusion MM, 4-3 tablespaces, C-11 migrating permissions, 4-9 troubleshooting installation problems, A-13 permission object classes for AllFusion ERwin DM, 4-4

upgrading AllFusion MM on, 3-4

Index–3

server-level tuning Microsoft SQL Server, B-2

session managing, 4-13

shared AllFusion ERwin DM reports creating, 6-4 creating a local copy of, 6-6

shared pool Oracle, C-3

sizing Microsoft SQL Server database, B-5 Microsoft SQL Server log, B-5 Oracle index tablespaces, C-12 Oracle rollback segments, C-8 Oracle tables, C-11 Oracle tablespace, C-11

storage parameters Oracle, C-7

Sybase connections, A-4 converting your database from AllFusion MM 4.1.4 to AllFusion MM r7, 3-7 data cache size, B-3 DBA steps for AllFusion MM installation, A-2 initializing AllFusion MM on, 2-4 installing AllFusion MM on, A-2, A-4 troubleshooting installation problems, A-5 upgrading AllFusion MM on, 3-4

System requirements, 1-5

T

tables Oracle, C-11

tablespaces Oracle, C-11

threshold procedures Microsoft SQL Server, B-4

Transact SQL useful commands, A-4

transaction log Microsoft SQL Server, B-3

troubleshooting installation problems Microsoft SQL, A-5 Oracle, A-13 Sybase, A-5

tuning recommendations physical tuning parameters, B-1, B-2

U

upgrading AllFusion MM on Microsoft SQL Server, 3-4 AllFusion MM on Oracle, 3-4 AllFusion MM on Sybase, 3-4 AllFusion MM software, 3-4 license, 3-1

Index–4 Administrator Guide

Documents

AllFusion Model Manager - support.ca.com · This documentation and related computer software program ... Oracle Tuning Recommendations ... Rollback Segments