CA ERwin Data Modeler Workgroup Edition

Transcription

1 CA ERwin Data Modeler Workgroup Edition Implementation Guide Version 9.0.0

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or 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 YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA ERwin Data Modeler Workgroup Edition (CA ERwin DM WE) CA ERwin Data Modeler Navigator Edition (CA ERwin DM NE)

4 Documentation Changes The following documentation updates have been made since the last release (r8.2) of this documentation: Installing and Configuring Mart (see page 17) Updated this section per the new Mart architecture requirements. Prepare your DBMS Environment (see page 22) Updated this section to remove topics that are not relevant per the new Mart architecture.

5 Contact CA Technologies Understanding your Support Review support maintenance programs and offerings. Registering for Support Access the CA Support online registration site to register for product support. Accessing Technical Support For your convenience, CA Technologies provides easy access to "One Stop" support for all editions of CA ERwin Data Modeler, and includes the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product For information about other Home Office, Small Business, and Enterprise CA Technologies products, visit Provide Feedback If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is also available on the CA Support website, found at CA ERwin Data Modeler News and Events Visit to get up-to-date news, announcements, and events. View video demos and read up on customer success stories and articles by industry experts.

6

7 Contents Chapter 1: Modeling in the Multiuser Environment 11 CA ERwin Data Modeler Workgroup Edition Model Life Cycle Frameworks Model-Driven Development Framework System-Driven Model Framework Informational Model Framework Chapter 2: Mart Architecture 14 Chapter 3: Checklist 15 Chapter 4: Installing and Configuring Mart 17 Review the Prerequisites Prepare Your DBMS Environment Tasks to Create a Microsoft SQL Server DBMS Tasks to Create a Sybase DBMS Transact-SQL Commands Tasks to Create an Oracle DBMS Mart Creation Requirements Install CA ERwin Mart Server Use Mart Server as a Windows Service Prepare to Use IIS with Mart Configure IIS Web Server Initialize Mart Initialize SQL Server Mart Initialize an Oracle Mart Log In to CA ERwin Mart Administrator and Configure Settings Chapter 5: Troubleshooting 40 Port out of range Call failed on the server Application Internal Error ORA TNS listener does not currently know of service requested in connect descriptor Mart already exists. Specify another database name Initialize page is not loading in Internet Explorer Contents 7

8 The Tomcat server is not starting properly. The Configure button is disabled A connection with the server could not be established The server name or address could not be resolved Invalid user ID or password Error Unable to load the web page from my web browser Test connection failed Appendix A: Sample Files 49 Sample workers.properties File Sample isapi_redirect.properties File Sample isapi_redirect.reg File Sample uniworkers.properties File Sample uriworkermap.properties File Chapter 6: Upgrading Mart 53 Review the Prerequisites Running CA ERwin DM on a 64-bit Operating System Select the Working Directory Enter the Source Mart Details Enter the Destination Mart Details Select the Data to Upgrade Select Upgrade Options Select Models View the Upgrade Status Log Files Troubleshooting Test Connection Failed--Source Mart Your License does not Permit Connection to this Mart Test Connection Failed--Destination Mart Unable to Select Upgrade Models Check Box Appendix B: Microsoft SQL Server and Sybase Tuning Recommendations 69 Physical Tuning Parameters Database Placement Data Redundancy Server-Level Tuning Parameters Named Cache Configuration Database Tuning Parameters Transaction Log Implementation Guide

9 Threshold Procedures "trunc. log on chkpt" Option Database and Log Sizing How to Maintain an Efficient Database DBCC Commands Appendix C: Oracle Tuning Recommendations 75 Recommended Disk Configurations Database Configuration Maximum Number of Processes Shared Pool Buffer Cache Redo Log Files Increase Space in Redo Logs Redo Log Buffer Checkpoints Storage Parameters Rollback Segments Set Optimal Configuration for the Rollback Logs Tablespaces Appendix D: CA ERwin Data Modeler Workgroup Edition Performance 87 Optimize the Performance Reindex the Database Run the Oracle DBMS Reindex Script Example: Microsoft SQL Server DBMS Reindex Script Troubleshooting the Reindexing Script Run the Database Statistics Index 95 Contents 9

10

11 Chapter 1: Modeling in the Multiuser Environment CA ERwin Data Modeler Workgroup Edition coordinates the development and management of data models created with CA ERwin Data Modeler. This section contains the following topics: CA ERwin Data Modeler Workgroup Edition (see page 11) Model Life Cycle Frameworks (see page 12) CA ERwin Data Modeler Workgroup Edition CA ERwin Data Modeler Workgroup Edition provides a multiuser modeling environment that makes coordinated, large-scale modeling possible. It enables collaboration among project managers, data modeling team members, and standards administrators by providing workgroup modeling services, including conflict resolution, versioning, security, and standards management. You can coordinate the efforts of model teams to document existing systems, create new ebusiness systems, and drive data standardization. Model sharing encourages teamwork, so modelers can work together more efficiently to optimize model-based development. Your modelers get more work done in less time with better results. Workgroup modeling operates in a three-tier architecture, where CA ERwin Data Modeler connects to Mart server through a web server. The models are held in a database or Mart; you can use Microsoft SQL Server, Oracle, or Sybase as the host database. Chapter 1: Modeling in the Multiuser Environment 11

12 Model Life Cycle Frameworks Workgroup modeling features are provided to help control updates to models when you are opening, closing, and saving models. The administrator installs the program and initializes the database on the DBMS server. The administrator also has the responsibility of setting up the library structure in which models are organized, and assigning security profiles to users. After a model is saved to the database, control of who can work on the model and how changes are saved to the model is handled by profiles, making it possible for workgroups to work on large models without confusion. CA ERwin Data Modeler Workgroup Edition supports many security and administrative features related to its multiuser capabilities. For this reason, routine management is usually performed by a dedicated administrator. Administrators can find detailed information regarding their tasks and responsibilities in the Administration Guide. You can also use CA ERwin Data Modeler Navigator Edition with CA ERwin Data Modeler Workgroup Edition. Read-only access is permitted to data models, so your workgroup can use this to share information with others without the risk that unauthorized changes might be saved to Mart. Model Life Cycle Frameworks Use one of the following model life cycle frameworks in your organization: Model-Driven Development Changes to the schema are made to the model first and then forward-engineered. System-Driven Models Changes are made directly to the schema and the schema is reverse-engineered into the model to reflect the changes. Informational Models Contains logical-only models, enterprise-wide models, or standards and sample models. Each type of framework has different considerations that you must think about when configuring your 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. 12 Implementation Guide

13 Model Life Cycle Frameworks 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 can follow a path like this: Create the library structure (for example, Development, Test, and Production) and populate them with CA ERwin Data Modeler templates. Create the logical model in a development library. Promote the model to the test library when it is ready. Generate the schema from the test library. Modify the test model as required and synchronize it to the schema. Promote the model to the production library when it is ready. Publish the refreshed production model. Update the enterprise-wide model, if necessary. Incorporate changes into the development model for further changes, and repeat the process. 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 can follow a path as described below: Create the library structure (for example, Reverse Eng, Test, Production). You do not require CA ERwin Data Modeler templates because you do not create models from scratch. Reverse engineer the model from the information system into the designated library. Enhance the model with logical information and input from analysts. Update the model to reflect changes in the physical schema. Create a version of the model. Synchronize the schema and the model using Complete Compare. Publish the model. Repeat the last three steps as the system is modified. Chapter 1: Modeling in the Multiuser Environment 13

14 Model Life Cycle Frameworks Informational Model Framework In the Informational Model framework, CA ERwin Data Modeler Workgroup Edition contains 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 can follow a path as described below: Create the library structure and populate them with templates. Develop the initial model. Use reverse engineering and model new components as required. Publish the initial model to the appropriate parties for modification and refinement. Get approval, and then version the model. Publish the approved model. Update and publish models as the enterprise model evolves. Chapter 2: Mart Architecture In the previous versions, CA ERwin Data Modeler connected to the Mart server directly. Now, CA ERwin Data Modeler connects to the Mart server through a web server. The following diagram shows the new architecture: 14 Implementation Guide

15 Model Life Cycle Frameworks The new architecture has the following benefits: Separate logical and physical users: In the previous versions, Mart (or Model Manager) users required database level privileges to access Mart functionality. The Mart database administrators added or deleted users in the Mart database. This approach is changed now. The logical users are separated from physical users, so Mart Administrators can create Mart users without creating the corresponding database users. Authentication through Active Directory services: Earlier, if you wanted to provide access to a user group, you added each user individually. Now, because of the new architecture, you can use the Active Directory services and can provide access to the group. Anyone who is part of the group gets access. Mart administration outside CA ERwin Data Modeler: In the previous versions, Mart Administrators used CA ERwin Data Modeler for administrative activities such as permissions management. This required non-modelers to know how to use CA ERwin Data Modeler. In the new architecture, the administration component (CA ERwin Web Admin) is built on a separate layer on top of CA ERwin Data Modeler and is hosted on a Web server. Mart Administrators can access CA ERwin Web Admin from any computer and can perform administrative activities through a web console. Chapter 3: Checklist Chapter 3: Checklist 15

16 Model Life Cycle Frameworks To use Oracle as the Mart database: You know the user name and password to connect to the database. You know the port number where Oracle is running. You know the name of the database. You know the IP address or the name of the computer where the database is running. You have created a data tablespace of at least 32 MB. You have created an index of at least 32 MB. You have created a temporary tablespace. You have assigned data tablespace as default tablespace to this user. You have assigned the temporary tablespace that you have created to this user. You have created the CA ERwin Data Modeler Workgroup Edition Installer role. You have granted Oracle privileges to the Installer role. To use SQL Server as the Mart database: You know the user name and password to connect to the database. You have verified that SQL Server is running. You have verified that TCP/IP is enabled. You know the port number where SQL Server is running, if you are not using the default port. You know the IP address or the name of the computer where the database is running. You know the name of the database. The minimum size of the database is 60 MB. The minimum file size of the transaction log is 50 MB. The size of tempdb is at least 16 MB. To use Sybase as the Mart database: You know the user name and password to connect to the database. If you are not using the default port, you know the port number where Sybase is running. You know the IP address or the name of the computer where the database is running. You know the name of the database. The minimum size of the database is 32 MB. You have located the data device on a different disk than the transaction log. 16 Implementation Guide

17 Model Life Cycle Frameworks The size of the Stored Procedure Cache is at least 20MB. The size of tempdb is at least 16MB. You have allocated at least 64MB RAM to the database server. To use IIS to connect to Mart: You know the server name where you have installed Tomcat. You know the server name where you have installed IIS. You have created the Worker.properties, isapi_redirect.reg, isapi_redirect.properties, uriworkermap.properties, and uniworker.properties files. To install Mart Server: You know the server name where you have installed the web server. For example, you know the computer name where Tomcat is installed. If you have changed the default port number, you know the port number on which the web server is running. You know the computer name where you have created the Mart database. You know the port number where the database is running. You know the database instance name if you are using SQL Server. You know the user name and password to connect to the database. Chapter 4: Installing and Configuring Mart Mart comprises the following components: Database Applications Web server The Mart application includes a web-based component named CA ERwin Mart Administrator. CA ERwin Mart Administrator helps you manage Mart through a web console. The Web server hosts CA ERwin Mart Administrator and you can use a Web server of your choice. If you have not installed a Web server, use the ERwin Mart Server option and install Tomcat. Chapter 4: Installing and Configuring Mart 17

18 Model Life Cycle Frameworks Install one of the following databases for the Mart database: SQL Server 2000, 2005, 2008, or 2012 Oracle 10g or 11g Sybase 15.x After installing Web server and the Mart server, provide the details of their properties. The following diagram illustrates how to install and configure Mart: 18 Implementation Guide

19 Review the Prerequisites Complete the following steps to install and configure Mart: 1. Review the prerequisites (see page 19). 2. Prepare Your DBMS Environment. (see page 22) 3. Install CA ERwin Mart Server. (see page 31) 4. (Optional) Use MartServer as a Windows Service. (see page 34) 5. (Optional) Prepare to Use IIS with Mart. (see page 34) 6. Initialize Mart (see page 36). 7. Log in to CA ERwin Mart Administrator and configure options (see page 39). Review the Prerequisites Before you install Mart components, help ensure that the minimum system requirements that are outlined in this topic are met. System requirements for Mart server Hardware requirements (based on physical hardware performance, not a virtual environment): 2 GHZ or higher dual core processor 4 GB RAM (8 GB or more for large marts) 4 GB of disk space or more as required to support your specific mart Chapter 4: Installing and Configuring Mart 19

20 Review the Prerequisites Operating system: Microsoft Windows Vista Microsoft Windows 2008 Server SP2 Microsoft Windows 2003 Server SP2 Microsoft Windows XP SP3 Microsoft Windows 7 Notes: CA ERwin Data Modeler has only been certified on the 32-bit versions of the Windows operating systems described in the preceding list. CA ERwin Data Modeler is a 32-bit application. You may experience problems running CA ERwin Data Modeler on a 64-bit operating system. CA ERwin Data Modeler is compatible with Microsoft Windows 8 Release Preview. You may experience problems with shortcuts and CA ERwin DM third-party components. Microsoft.NET Framework 3.5 or higher All current Microsoft Windows critical updates are applied Database: The Mart Server can use a standalone or share an existing database server: Microsoft SQL Server 2000, 2005, 2008, or 2012 Oracle 10g or 11g Sybase 15.x CA ERwin Mart Administrator web client: Supported browsers: Microsoft Internet Explorer 8 or newer Mozilla Firefox v.9.0 or newer Google Chrome 14 or newer Apple Safari 5 or newer Adobe Flash plug-in version 8 or newer for the respective browser 20 Implementation Guide

21 Review the Prerequisites Other requirements Help ensure that the following additional requirements are met: If you want to use Microsoft IIS as the web server, you have configured it. The DBMS is installed and prepared for creating the Mart Database. The Mart database is created. At least one user with administrator privileges is present. If you are using Oracle, you have run the initial queries. For more information about the initial queries, see the Implementation Guide. Note: For Microsoft SQL Server 2005, 2008, and 2012 select Mixed Mode Authentication during installation. For Oracle Version 10g and 11g, modify the following parameters in the initialization file (InitSID.ora): Remote_OS_Authent= OS_Authent_Prefix=TRUE If you want to add Windows Group users, you have the Active Directory Server details. Important disclaimer notice on all requirements 1. The requirements mentioned previously define the minimum requirements which permit CA ERwin Data Modeler r9 to run with reasonable performance based on a small business use case scenario. The actual requirements for an enterprise wide use case based on larger models and configurations require significantly greater resources to obtain acceptable performance. 2. These requirements are based on actual physical hardware (no virtual environment) and the following assumptions: Minimal to no network overhead (both the database and application servers are locally installed) Vendor's default install of the current version of their software (with all current service or fix packs) No other applications sharing the defined hardware configuration (e.g., a clean machine) Any other hardware/software configurations are acceptable as long as they provide the same (or better) performance characteristics identified. Chapter 4: Installing and Configuring Mart 21

22 Prepare Your DBMS Environment Prepare Your DBMS Environment Perform the following setup tasks in your DBMS environment before you can install and use the software: 1. Install the DBMS on the server where you plan to store the mart. For more information about memory and disk space requirements, see the system requirements for each DBMS (Microsoft SQL Server, Sybase, and Oracle). 2. Create the mart. Use the DBMS features to create or identify the required storage objects and the mart. The specific requirements vary depending on your DBMS type. Note: To create, update, or delete a mart in CA ERwin Data Modeler Workgroup Edition, you must have the following database rights: For Microsoft SQL Server 2000, 2005, 2008, and 2012 you must be the database owner (dbo). Notes: The dbo is no longer required to have the sysadmin role. The SQL Server 2005, 2008, and 2012 TRUSTWORTHY database property is no longer required for the mart. After you install this product, you can optionally reset this property to OFF. For Oracle, you must be the database schema owner and have the DBA role. 22 Implementation Guide

23 Prepare Your DBMS Environment Tasks to Create a Microsoft SQL Server DBMS The following tasks must be performed by the DBA and system administrator responsible for installing CA ERwin Data Modeler Workgroup Edition on a Microsoft SQL Server DBMS: 1. Use a graphical user interface (GUI) tool, ISQL (all versions), SQL Administrator, or Enterprise Manager to create the CA ERwin Data Modeler Workgroup Edition database. If a GUI tool is not available, you can use ISQL to type in the appropriate commands manually. Your database should meet the following criteria: The initial size of the database file should be set to 60 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. Note: For best performance ensure that separate devices are used to store the data and the transaction log. 2. Verify tempdb size. Microsoft SQL Server 2005 Permissions 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. For SQL Server 2000, you only need the public permission assigned to save to Mart. However, when the repository is on a SQL Server 2005 instance, you must have the bulkadmin permission designated too. The ability to do bulk inserts (which the public permission permitted previously) is no longer part of the public permission. As the administrator, you explicitly define this permission. Assign the bulkadmin permission to the physical user that connects to the database. If you do not define the permission, when you create a mart using a SQL Server 2005 database, and save it, an error appears. Chapter 4: Installing and Configuring Mart 23

24 Prepare Your DBMS Environment Specify Use of Foreign Characters With Microsoft SQL Server 2000 For Microsoft SQL Server 2000, select specific settings in the Client Network Utility to have certain foreign language characters in your models recognized. Follow these steps: 1. Click Programs, Microsoft SQL Server, Client Network Utility on the Start menu. The SQL Server Client Network Utility dialog opens. 2. Select the following check boxes on the DB-Library Options tab: Automatic ANSI to OEM conversion Use international settings 3. Click OK. Your configuration is set to recognize foreign language characters in your models. Specify Use of Foreign Characters With Microsoft SQL Server 2005 For Microsoft SQL Server 2005, 2008, and 2012 modify your registry settings to have certain foreign language characters in your models recognized. Follow these steps: 1. Click Run on the Start menu. 2. Enter regedit. The Registry Editor opens. 3. Verify or add the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\DB-Lib] "AutoAnsiToOem"="ON" "UseIntlSettings"="ON" 4. Click File, Exit. Your configuration is set to recognize foreign language characters in your models. 24 Implementation Guide

25 Prepare Your DBMS Environment Tasks to Create a Sybase DBMS The DBA and the system administrator responsible for installing the software on a Sybase database management system perform the following tasks: 1. Use a graphical user interface (GUI) tool, ISQL (all versions), SQL Administrator, Sybase Central Java, or Enterprise Manager to create the mart database. If a GUI tool is not available, use ISQL to type the appropriate commands manually. Your database must meet the following criteria: The size of the data device you create determines the size of the database. The minimum database size is 32 MB so there has to be at least one device that is 32 MB. Create the data device on a different disk (and disk controller) than the transaction log. For optimum performance, verify that separate devices are used to store the 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. Verify 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 installation creates more than 100 stored procedures. The client invokes these stored procedures to control changes to the data in the database. 3. Verify tempdb size. Significant temporary space is required for installation and use. The temporary segments need at least 16 MB of available space. Increase the available space as the number of concurrent users increase. 4. Verify the memory allocated to the database server. Allocate at least 32 MB of RAM to the database server. The amount of RAM allocated is ideally half of the available RAM on the server. Chapter 4: Installing and Configuring Mart 25

26 Prepare Your DBMS Environment Transact-SQL Commands If a graphical DBMS access tool is not available, you can use Transact-SQL commands through ISQL. Example: Create a device using the Transact-SQL DISK INIT command through ISQL 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 */ Example: Create a database using the Transact-SQL CREATE DATABASE command through ISQL 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. */ Example: Add logins to the database with the sp_addlogin and sp_adduser commands using Transact-SQL through ISQL sp_addlogin login_id [, passwd [, defdb [, deflanguage]]] sp_adduser login_id [, username [, grpname]] After you execute 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] 26 Implementation Guide

27 Prepare Your DBMS Environment Tasks to Create an Oracle DBMS The DBA and the system administrator responsible for installing the software on an Oracle database management system performs these tasks. Use graphical tools or SQL *Plus (all versions), SQL*DBA, or the Oracle Enterprise Management Console to perform these tasks. Examples of SQL commands are included where appropriate. Data file paths, data file sizes, role names, and user names are included for example only. 1. Check SYSTEM tablespace. The 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 often needs 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 tablespaces. 3. Create a 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; Chapter 4: Installing and Configuring Mart 27

28 Prepare Your DBMS Environment 4. Create a 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 a 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 about syntax and options regarding tablespace creation, see the appropriate Oracle documentation. 6. Create an Oracle user with DBA privileges to be used by the CA ERwin Data Modeler Workgroup Edition Installer or designated schema owner. Assign the data tablespace as this user s default tablespace, and the 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 the CA ERwin Data Modeler Workgroup Edition Installer role. The following example is the role required by the Oracle user installing CA ERwin Data Modeler Workgroup Edition. CREATE ROLE MMINSTALL; 28 Implementation Guide

29 Prepare Your DBMS Environment 8. Grant Oracle privileges to the Installer role. The following example shows the Oracle privileges that the CA ERwin Data Modeler Workgroup Edition Installer needs to install 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 the CA ERwin Data Modeler Workgroup Edition User role. For example: CREATE ROLE MMUSER; When you select this role as the CA ERwin Data Modeler Workgroup Edition User role during Step 4 of the installation procedure, the Setup program generates grant statements that grant object level privileges to this role. 10. Grant the create session Oracle privilege to the 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 database. 11. Grant the CA ERwin Data Modeler Workgroup Edition User role to the Installer role. For example: grant MMUSER to MMINSTALL; 12. Select the CA ERwin Data Modeler Workgroup Edition tablespaces and User role. When prompted for tablespace and role information, select the CA ERwin Data Modeler Workgroup Edition data tablespace, the CA ERwin Data Modeler Workgroup Edition index tablespace, and the CA ERwin Data Modeler Workgroup Edition User role (the role created in Step 9). Chapter 4: Installing and Configuring Mart 29

30 Prepare Your DBMS Environment Database Objects Installation Install the software on an Oracle DBMS to create the following database objects: Tables Indexes Stored procedures Public synonyms Oracle SQL Commands If a graphical DBMS access tool is not available, you can use Oracle SQL commands through SQL*DBA or SQL*Plus. Example: Create a tablespace using 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 */ ); Example: Create an Oracle user using 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 */ ; Example: Grant user privileges using the GRANT command GRANT role_or_privilege_name TO user_or_role ; 30 Implementation Guide

31 Install CA ERwin Mart Server Mart Creation Requirements To create the mart, you must meet one of the following requirements: You must be the database owner (dbo) in the target database on the Microsoft SQL Server 2005, 2008, 2012 or Sybase server Note: The database owner (dbo) is necessary only during the software installation or upgrade. It is not necessary after you create the mart. You must be the database schema owner user and have the DBA role in the target database on the Oracle server. Install CA ERwin Mart Server The Mart Server and Mart Admin war files are deployed on a Web server. You can either use an existing web server, or install the web server through the CA ERwin MartServer Installation Wizard. You must install CA ERwin Mart Server and configure it regardless of whether you use Mart Server as a Windows service. Follow these steps: 1. Do one of the following tasks: Insert the installation DVD and select Mart Server Installation. Download the Mart Server.exe file from the online CA Technologies product page and run it. The CA ERwin MartServer Installation Wizard appears. 2. Go through the wizard steps to install CA ERwin Mart Server. Depending on the options you select, CA ERwin Mart Server and/or Java Runtime Environment (JRE) and Tomcat are installed. Note: If Java (any version) is already available in the computer and the environment variable JRE_HOME is set, the installer overwrites JRE_HOME with the new Java path. The JRE version that is shipped with the installer is 1.6.0_31. If a Tomcat web server is already installed in the computer and the environment variable CATALINA_HOME is set, the installer replaces CATALINA_HOME with the new path. 3. After you close the wizard, from the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, Configure MartServer. The CA ERwin Mart Configuration dialog appears. Chapter 4: Installing and Configuring Mart 31

32 Install CA ERwin Mart Server Configure the CA ERwin Mart Server 1. Complete the following fields in the Mart Server tab: Database Type Port No. Specifies database server type. Specifies the port number of the database server. Server Name Specifies the name of the database server where you have installed the Mart database. For example, suppose that you are using SQL Server 2008 as the Mart database. Enter the name of the computer where SQL Server 2008 is installed. Instance Name Specifies the name of the database instance. Database Name Specifies the name of the Mart database. Note: Use a new database. Do not specify the name of an existing database that you have used for an older version of Mart. User Name Specifies the user name to connect to the Mart database. Password Specifies the password to connect to the Mart database. Note: The following fields--domain Controller Name, Domain/User Name, and Password are required only if you are using Active Directory authentication. Domain Controller Name Specifies the fully qualified name of the Active Directory Server (Domain Controller). Domain/User Name Specifies the domain name and user name in the <domain name>/<user name> format. Password Specifies the password of the domain user. 32 Implementation Guide

33 Install CA ERwin Mart Server Configure CA ERwin Mart Administrator 1. Enter the following information in the Mart Administrator tab: Server Name Specifies the name of the computer where the Web Server is present. For example, if you are using Tomcat, enter the name of the computer where Tomcat is installed. Default: localhost Port Number Use IIS Specifies the port number on which the Web Server is running. Default: Specifies that you want to use the IIS web server to connect to Mart. This check box is available only if you have configured IIS. Application Name Specifies the application name with which the Web Server is identified. Default: MartServer 2. Click Configure. The CA ERwin Mart Administrator and the Mart Server are configured. More information: Configure IIS Web Server (see page 35) Chapter 4: Installing and Configuring Mart 33

34 Use Mart Server as a Windows Service Use Mart Server as a Windows Service CA ERwin DM Version 9.0 Mart provides two ways to start the web server that hosts Mart Server: Start the web server manually. Use a Windows service to start the web server. For example, if you have used Tomcat as the web server to host Mart Server, you can start Tomcat in two ways: Start Tomcat through the startup.bat file or through a shortcut to this file. Use a Windows service to start Tomcat. The benefits of using a Windows service to start a web server are as follows: Any user with administrative privileges on a computer can start the Windows service, whereas, only designated users can start a web server manually. A Windows service runs regardless of whether a user has logged in. A manually-started web server shuts down when the user who started it logs out. Follow these steps: 1. From the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, Create MartServer Service to create the MartServer Windows service. Creating the service is a one-time task. After the service is created, you only have to start and stop the service. 2. From the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, Start MartServer Service to start the web server. Prepare to Use IIS with Mart If you want to use Microsoft Internet Information Services (IIS) as the web server, configure it before deploying Mart Server. 34 Implementation Guide

35 Prepare to Use IIS with Mart Configure IIS Web Server The Mart Server is built using Java technology. Therefore, if you want to connect to Mart through IIS, configure IIS to use the JK ISAPI redirector plugin. Using this plugin, IIS sends servlet and JSP requests to Tomcat. Follow these steps: 1. Help ensure that Tomcat is working properly. Open a browser and type the following in the Address bar: The default Tomcat home page appears. <servername> is the name of the computer where you have installed Tomcat is the default port number where Tomcat is running. If you are using a different port number, use that port number here. In addition, help ensure that the port number you are using is included in the server.xml file. Typically, the server.xml file is available in the <Tomcat_Home>/conf folder. 2. Install IIS. 3. Create a folder on the computer where you have installed IIS. Download the isapi_redirect.dll file for Windows from the Apache Tomcat website and copy to the new folder. 4. Create the workers.properties file in the folder that you created in the previous step. 5. Create the uniworkers.properties file in the folder that you created in Step Follow these steps and create an IIS filter for the DLL placed in Step 5: a. From the Windows Start menu, click Run, and then type inetmgr. The Internet Information Services (IIS) Manager window opens. b. Click the computer name, Sites. c. Click Default WebSite, right-click and select Add Virtual Directory. The Add Virtual Directory dialog appears. d. Enter the path for the isapi_redirect.dll file in the Physical Path field and click OK. e. Click the newly added virtual directory. The Default Web Site Home window opens. f. Double-click ISAPI filters and click Add in the top right corner. g. Enter the filter name. Enter the path for the isapi_redirect.dll file in the Executables field. h. Click OK. 7. Create the isapi_redirect.reg file to indicate the location of workers.properties files are created previously. Double-click this file and update the registry. Chapter 4: Installing and Configuring Mart 35

36 Initialize Mart 8. Restart the IIS web server. 9. Stop the MartServer service and start it again. Note: See the Appendix for sample workers.properties, uniworkers.properties, isapi_redirect.reg, isapi_redirect.properties, and uriworkermap.properties files. Initialize Mart When you access the Mart database through CA ERwin Mart Administrator for the first time, you must initialize the database. Note: Before you proceed, verify that you have installed a DBMS and created the Mart database. If you are using Oracle, verify that you have run the initial queries. If the Mart is already initialized, the Login page appears. When you open CA ERwin Mart Administrator for the first time, the Initialize Mart web page that is relevant to your Mart database appears. Note: Initializing a Sybase Mart is same as initializing a SQL Server Mart. More information: Prepare Your DBMS Environment (see page 22) 36 Implementation Guide

37 Initialize Mart Initialize SQL Server Mart Initialize a SQL Server Mart Follow these steps: 1. If you are using MartServer as a Windows service, help ensure that the service is started. If not, from the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, Start Mart Server to start the Mart Server. A Windows command prompt window appears and indicates when the server starts. 2. From the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, CA ERwin Mart Administrator. CA ERwin Mart Administrator opens in your default browser. 3. Complete the following fields: Username Defines the user name with which you want to access the Mart. Password Defines the password for the user name. Confirm Password Confirms the password that you entered in the previous field. Address Defines the address for the user account that you are creating. 4. Click Initialize. The user name is added as an administrator of Mart, Mart is initialized, and the Login web page appears. Initializing is a one-time task. After Mart is initialized, the user who initialized must log in first. Later, any other user who wants to use CA ERwin Mart Administrator can log in. Note: The user name that is entered here is an application level user and not a database user. Remember the password that you have entered here, because without the password you cannot log in to CA ERwin Mart Administrator for the first time. Chapter 4: Installing and Configuring Mart 37

38 Initialize Mart Initialize an Oracle Mart Initialize an Oracle Mart Follow these steps: 1. If you are using MartServer as a Windows service, help ensure that the service is started. If not, from the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, Start Mart Server to start the Mart Server. A Windows command prompt window appears and indicates when the server starts. 2. From the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, CA ERwin Mart Administrator. CA ERwin Mart Administrator open in your default browser. 3. Complete the following fields: Username Defines the user name with which you want to access the Mart. Password Defines the password for the user name. Confirm Password Confirms the password that you entered in the previous field. Address Defines the address for the user account that you are creating. Mart Role Defines the role of the user for the Mart. Table Tablespace Defines the table tablespace in which the Mart tables are created. Index Tablespace Defines the index tablespace in which the Mart indexes are created. 4. Click Initialize. The user name is added as an administrator of Mart, Mart is initialized, and the Login web page appears. Initializing is a one-time task. After Mart is initialized, the user who initialized must log in first. Later, any other user who wants to use CA ERwin Mart Administrator can log in. Note: The user name that is entered here is an application level user and not a database user. Remember the password that you have entered here, because without the password you cannot log in to CA ERwin Mart Administrator for the first time. 38 Implementation Guide

39 Log In to CA ERwin Mart Administrator and Configure Settings Log In to CA ERwin Mart Administrator and Configure Settings After Mart is initialized, the user who initialized must log in first. When you log in to Mart for the first time, configure it per the requirements of your organization. You can configure the following settings: Default profile for the model creator Use default password notification Follow these steps: 1. From the Windows Start menu, click All Programs, CA, ERwin, ERwin Mart Server r9, CA ERwin Mart Administrator and log in. The CA ERwin Mart Administrator home page appears. 2. Click Settings. 3. Complete the following fields: Default profile for model creator Specifies the profile that is assigned to a user on a model. This profile is assigned whenever a user creates a model and saves it to Mart for the first time. The user inherits the permissions of the default profile selected here on the model that is saved. For example, suppose that User1 is assigned with Modeler profile and the System Administrator selects Architect as the default profile for model creator. If User1 creates Model1 and saves it to Mart, for Model1, User1 inherits the permissions of Architect. Now, suppose that the System Administrator selects Viewer as the default profile for model creator, and suppose that User1 creates Model2 and saves it to Mart. For Model2, User1 inherits the permissions of Viewer. Use Default Password Specifies the default password that you want to use for new users and for resetting passwords, in the absence of an SMTP server for s. Note: Select this option only if you do not have an SMTP server that is configured for s. SMTP host name Specifies the name of the SMTP host. Enter the name in the mail.domain.com format. Notification s are sent from this server. Port number Specifies the port number of the SMTP server. The default port number is 25. If your company is using an alternate port number for the mail server, specify that port number. Authenticate Chapter 4: Installing and Configuring Mart 39