May 2010 - Meta Integration releases new version 6.1

Meta Integration® Repository (MIR) Server
"Metadata Management" Solution

README

Table of Contents

1. Copyright Notice
2. Release Changes
3. System requirements
4. MIR Database Server Setup
   1. MIR Database on Oracle
   2. MIR Database on Microsoft SQL Server
5. MIR Application Server Installation and Setup
   1. Default install on Windows with bundled Tomcat
   2. Custom install on other Web Application Server Engines
   3. Custom install on other Unix/Linux Operating Systems

1. Copyright Notice

Copyright © Meta Integration Technology, Inc. 1997-2010.
All Rights Reserved.
Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
Other product and company names (or logos) mentioned herein may be the trademarks of their respective owners.
http://www.metaintegration.com

2. Release Changes

v6.2.0 (scheduled for 2010/Q3)

• NEW: Metadata Authoring (MA) for Business Glossary and Data Dictionary purposes

v6.0.6 (12/04/2009)

• UPDATE: Major improvements and bug fixes on MIMB for metadata harvesting especially from all BI tools, and in particular Microsoft SSAS/SSRS. See MIMB ReadMe for details
• UPDATE: Significant performance improvements in display of lineage of large configurations
• UPDATE: Change in display of diagrams for larger models to show smaller subject areas by default, improving performance
• UPDATE: Significant performance improvements in mapper UI when mapping very large models
• UPDATE: Added ability to view and sort by all columns defined for a given profile in the business UI

v6.0.5 (MIMB GA, MIMM GA) (09/28/2009)

• UPDATE: Minor improvements and bug fixes
• UPDATE: Administration->Database tab for database performance management
• UPDATE: New script supporting performance testing and tuning

v6.0.4 (MIMB GA, MIMM beta5) (06/02/2009)

• NEW: Automatic and Scheduled Metadata Harvester, Metadata Mapper, LDAP User Integration, Role based business and technical web user interface, Role based Metadata Security Manager

v6.0.3 (MIMB GA, MIMM beta4) (01/28/2009)

• NEW: Version Manager, Configuration Version Manager, Version Migrator, Business User Interface, Model based Metadata Reporter, Metadata Profiling

v6.0.2 (MIMB GA, MIMM beta3) (10/31/2008)

• NEW: Graphical Lineage Analyzer, Business Lineage and Impact Analyzer, Enterprise wide Metadata Search Engine and Reporter, Enterprise Configuration Management, Metadata Stitcher, Metadata Configuration Manager

v6.0.1 (MIMB GA, MIMM beta2) (07/22/2008)

• NEW: Model based Diagram Visualizer, Graphical Lineage Analyzer

v6.0.0 (MIMB GA, MIMM Beta1) (05/31/2008)

• NEW: Model Import, Model Browser, Model Subsetter, Model Export

3. System requirements

Important preliminary disclaimer notice on all requirements

1. The following requirements only define the minimal requirements allowing to run the application with reasonable performance based on the provided tutorial, or any small business uses cases. The actual requirements for enterprise wide use cases based on larger models and configurations do require significantly greater ressources to obtain acceptable performance.
    
2. The following requirements are based on:
   • actual physical hardware (no virtual environment),
   • minimal to no network overhead (assuming both the database and application servers to be locally installed),
   • vendor's default install of the current version of their software (with all current service or fix packs),
   • no other applications sharing such hardware (starting from a clean machine),

   Any other hardware/software configurations are acceptable as long as they provide the same (or better) results on the provided performance benchmark. In such case, if any problem is discovered (e.g. scalability or performance issues), then the customer must be able to reproduce the issue using an environment that conforms to the minimum performance requirements as defined above.

   Potential known issues include (but are not limited to) the following:

   • actual usable hardware performance on virtual environments (e.g VMWare configuration and licenses)
   • network overhead on remote servers (e.g. bandwidth, proxy, VPN issues, VMWare inter OS network limitations without a proper license, etc.)
   • shared resources with competing applications on the same OS, or between OS on a virtual environment,
   • licensing limitations (e.g. most database server licenses limit the number of usable core/CPU)
   • vendor software known limitations and requirements (e.g. Oracle on VMWare vs Oracle VM)

Web Client requirements

• Microsoft Internet Explorer 6 or newer (recommended)
• Mozilla Firefox

Web Application Server

Hardware Miniumum Requirements (based on physical hardware performance, not a virtual environment):

• 2 GHZ or higher quad core processor
• 4 GB RAM (8 GB if 64bit OS using 64bits Web Application Server).
• 10 GB of disk space (all storage is primarily in the database server)

Operating System Requirements:

• Microsoft Windows XP, Vista, 2003 Server or 2008 Server - Any variations of Windows newer than XP are recommended, and are supported with automatic InstallShield setup
• Ensure that Microsoft .NET Framework 3.5 or higher
• Ensure that all current Microsoft Windows critical updates have been applied


• Linux, Redhat, Sun Solaris, and other Unix variations (only on demand) - Unix operating systems are NOT supported by default and they will require manual install and configuration.

Web Application Server Engine Requirements:

• Apache Tomcat (bundled)
• IBM WebSphere on demand only (not supported by default, and requires manual install and configuration)

Java Runtime Environment (JRE):

• Sun JRE 5 (bundled and recommended)

Database Server

Hardware Miniumum Requirements (based on physical hardware performance, not a virtual environment):

• 2 GHZ or higher quad core processor
• 4 GB RAM (8 GB if 64bit OS using 64bits Web Application Server).
• 10 GB of disk space (or more as needed for the data)

The MIR Database Server can reuse your existing Oracle or SQL Server servers:

• Oracle 10gR2 to 12 64-bit (recommended for large enterprise, default supported version)
• The character set of the database must be UTF8 (AL32UTF8); because the Oracle Intermedia Search can only index columns of type VARCHAR or CLOB (not the national variants NVARCHAR and NCLOB respectively)
• The CTXSYS user must be installed: the installation script can be found in <ORACLE_HOME>/ctx/admin/catctx.sql
• The number of users and CPU/Processors can be verified as follows:
   select * from v$license;
• The database edition installed can be verified as follows:
   select banner from v$version where BANNER like '%Edition%';
• Microsoft SQL Server 2005 to 2008 64-bit
• Database server install needs to support text search

4. MIR Database Server Setup

4.1 MIR Database on Oracle

• Create a user "MIR":
  • add the "EXECUTE" privilege on the package "CTX_DDL" to the user "MIR" which can be done as follows:
    • log into your database as SYS and execute the following statement:
       GRANT EXECUTE ON CTXSYS.CTX_DDL TO MIR;
    • Or log into the Oracle Enterprise Manager as SYS. Then go to "Server", then "Users". Select the user MIR and "Edit". Go to "Object privileges", select object type "Package" and "Add". Type in CTXSYS.CTX_DDL, and add the "EXECUTE" privilege. Then click "OK" and "APPLY".
  • add the "EXECUTE" privilege on the package "DBMS_LOCK" to the user "MIR" which can be done as follows:
    • log into your database as SYS and execute the following statement:
       GRANT EXECUTE ON SYS.DBMS_LOCK TO MIR;
    • Or log into the Oracle Enterprise Manager as SYS. Then go to "Server", then "Users". Select the user MIR and "Edit". Go to "Object privileges", select object type "Package" and "Add". Type in SYS.DBMS_LOCK, and add the "EXECUTE" privilege. Then click "OK" and "APPLY".
  • add the "EXECUTE" privilege on the package "DBMS_SCHEDULER" to the user "MIR" which can be done as follows:
    • log into your database as SYS and execute the following statement:
       GRANT EXECUTE ON SYS.DBMS_SCHEDULER TO MIR;
    • Or log into the Oracle Enterprise Manager as SYS. Then go to "Server", then "Users". Select the user MIR and "Edit". Go to "Object privileges", select object type "Package" and "Add". Type in SYS.DBMS_SCHEDULER, and add the "EXECUTE" privilege. Then click "OK" and "APPLY".
• The database schema "MIR" should be automatically created as side effect of creating the user "MIR".
• In order to create the database through the script, either add the "DBA" role to the user "MIR", or add the following system privileges to the user "MIR"
  • CREATE JOB
  • CREATE PROCEDURE
  • CREATE SEQUENCE
  • CREATE TABLE
  • CREATE TRIGGER
  • CREATE TYPE
  • CREATE VIEW
  You can remove the grant of the role, or system privileges once the script ran successfully.

4.2 MIR Database on Microsoft SQL Server

• Login to SQL server as a user with server admin role. Enable CLR on SQL Server by executing the following commands:
  • "EXEC sp_configure 'clr enabled', 1"
  • "RECONFIGURE"
• Create a user "MIR":
  • select SQL Server Authentication, and do not enforce password policy so that the user does not have to change the password the first time (as the MIR database creation script would not be able to do that)
• Create a database "MIR":
  • set the owner to be user "MIR"
  • Enable "Use full-text indexing". You may do this by executing the following command on the database in a query window.
    "EXEC sp_fulltext_database 'enable'"
  • Execute the following command on the database in a query window. This option will enable read operations on the database without acquiring any shared locks and hence reducing the chances for deadlocks.
    "ALTER DATABASE MIR SET READ_COMMITTED_SNAPSHOT ON"

5. MIR Application Server Installation and Setup

5.1 Default install on Windows with bundled Tomcat

• Prepare a MIR Database server with a MIR user per instructions above
• Run the InstallShield program following built-in steps and instructions
• Set the license key by default in:
  "C:\Program Files\Meta Integration\conf\MIRSetup.xml"
• Define access to any remote metadata harvesting agents (MIMB Servers) by default:
  "C:\Program Files\Meta Integration\conf\MIRWebSetup.xml"
• Restart the MIR Web Application Server (using services)
• If desired, run the script to create the metadata management tutorial, by default:
  "C:\Program Files\Meta Integration\scripts\MIRCreateTutorialMetadataManagement.bat"
• Login as "Administrator" with password "Administrator" on your web browser, by default:
  http://localhost:19980/MIRWeb
• You may configure memory for the app server in Tomcat by executing install-dir\tomcat\bin\tomcat5w.exe //MS//MITI6WS

5.2 Custom install on other Web Application Server Engines

Apache Tomcat 64bits on 64 bits OS

IBM WebSphere

5.3 Custom install on other Unix/Linux Operating Systems

Linux

Redhat

Sun Solaris

Copyright © Meta Integration Technology, Inc. 1997-2010 All Rights Reserved. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. http://www.metaintegration.com