June 2011 - Meta Integration releases new version 7

Meta Integration® Metadata Management (MIMM)

README

Table of Contents

1. Copyright Notice
2. Release Changes
3. System requirements
4. MIR Database Server Setup
   1. MIR Database on Microsoft SQL Server
   2. MIR Database on Oracle
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
   4. Custom integration with an external Single Sign-On (SSO) environment

1. Copyright Notice

Copyright © Meta Integration Technology, Inc. 1997-2012.
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

v8.0 (scheduled for 9/30/2012)

• NEW: Metadata Authoring (MA)'s Data Model Editor for Metadata Documenting
• model documentation: editing business names and descriptions in the property panel (for documenting models extracting from live databases via JDBC)
• model subsetting: downsizing a model at the entity/table level, or attribute/column level (for reuse from standard or enterprise models)
• basic model editing: right click add or delete on a schema/package, entities/tables, attributes/columns

v7.1 (scheduled for 3/31/2012)

• NEW: Metadata Authoring (MA)'s Model Mapping Editor for Data Flow and Semantic Flow
• NEW: Metadata Authoring (MA)'s Business Rule Editor for Data Quality and Data Governance
• with Data Driven Metadata Discovery of Data Types (including enumeration values)

v7.0.2 GA (scheduled for 1/31/2012)
General Availability for complete metadata management)

• UPDATED: Metadata Management (MM) for large scale multi model ETL/DI metadata
• UPDATED: Metadata Version & Configuration Management (MV) for large scale multi model ETL/DI metadata

v7.0.1 LA (10/6/2011)
Limited Availability and Limited Functionality for data modeling tool management

• UPDATED: User Experience
• UPDATED: Performance, Scalability, and Concurrency Control
• UPDATED: Packaging, Installation, and Administration

v6.2 (10/15/2010)

• NEW: Metadata Authoring (MA)'s Business Glossary Editor for Data Governance

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

Users only need an internet browser:

• Microsoft Internet Explorer (IE) v8 or newer. Note that older versions of IE (especially running on old versions of Windows like XP) are not officially supported as users may encounter some minor layout issues for this modern web 2.0 application (all issues have been resolved by Microsoft in any recent version of Windows and IE).
• Mozilla Firefox v5 or newer
• Google Chrome v14 or newer
• Apple Safari v5 or newer

• Adobe Flash v8 or newer

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 SP3 (with current Windows update), Vista, Windows 2003 Server, Windows 2008 Server, or Windows 7.
  Any variations of Windows newer than XP are recommended, and are supported with automatic InstallShield setup.
  • Ensure that installer is executed with full Administrator priviledge
  • 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 6 (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)

Database Administrator priviledges are required to install/uninstall the database.

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 R2 64-bit
• Database server install needs to support text search

Virtual Memory: For a Windows based database server, be sure to either:

• set the page file size to be managed automatically by OS
• or it should be at least 3 times the memory or RAM size for the machine.

4. MIR Database Server Setup

4.1 MIR Database on Microsoft SQL Server

Database Requirement 1 - Full-text Search

SQL Server must have the Full-text Search component installed and running. This can be confirmed by making sure a service called "SQL Full-text Search" (SQL Server 2005) or "SQL Full-text Filter Daemon Launcher" (SQL Server 2008) is running in the Services panel or the SQL Server Configuration Manager.

This Full-text Search component can be added to any existing SQL Server, except for SQL Server Express. In case of SQL Server Express, the Full-text search compoenent is only available in the "Advanced Services" package:
For 2008 R2, download SQLEXPRADV_xxx_xxx.EXE
For 2005, download SQLEXPR_ADV.EXE

In the some cases, (e.g. SQL Server Express 2005), make sure "Full-Text search indexing"check box is enabled for the MIR database. This can be verified or changed by using the SQL Server Management Studio: first sign in, then right click on the MIR database and select properties, finally go in the File area to find the above check box, and restart SQL Server.

Database Requirement 2 - Mixed-Authentication Mode

The Mixed-Authentication Mode is usually set during during the SQL Server installation process.

The Mixed-Authentication Mode can be verified or changed by using the SQL Server Management Studio: first sign in, then right click on the root of the tree (instance of SQL Server Express), go to Security, and finally select “SQL Server and Windows Authentication mode”

Database Requirement 3 - TCP/IP Protocol Enabled

The TCP/IP Protocol must be enabled in the SQL Server Configuration Manager for both the named instance and the client protocols (Make sure you restart the service after chaning).

Database Preparation

Login to SQL server as a user with server admin role and execute the following commands to create a database "MIR" and a user "MIR" with password "MIR123" (or another one):

EXEC sp_configure 'clr enabled', 1 RECONFIGURE Go CREATE LOGIN MIR WITH PASSWORD = 'MIR123'; CREATE DATABASE MIR; ALTER DATABASE MIR SET SINGLE_USER WITH ROLLBACK IMMEDIATE; ALTER DATABASE MIR SET READ_COMMITTED_SNAPSHOT ON; ALTER DATABASE MIR SET MULTI_USER WITH ROLLBACK IMMEDIATE; ALTER AUTHORIZATION ON DATABASE::MIR to MIR;

Database Connection

Advanced SQL Server Administrators may define ("hard-code") a set of TCP/IP ports for SQL Server to run over the network. However, Microsoft now recommends to run the "SQL Server Browser" service which can done either in the Services panel or the SQL Server Configuration Manager. For more information, read: How to: Configure Express to accept remote connections

The connection string syntax is:
jdbc:sqlserver://<dbServer>:<dbPortNumber>;databasename=<dbName>

To connect to a named SQL server instance other than the default:

• If the SQL Server browser service is running:
  • If the named instance is configured to listen on dynamic ports:
    In the installer, specify only the instance name (in the format HOSTNAME\INSTANCENAME) and no port (the port field should be left empty).
    e.g. jdbc:sqlserver://localhost\sqlexpress;databaseName=MIR;
  • If the named instance is configured to listen on static IP ports:
    The SQL Server instance must be configured to run on a static TCP/IP port and that port must be specified in the installer.
    e.g. jdbc:sqlserver://localhost\sqlexpress:1433;databaseName=MIR;
• If the SQL Server browser service is not running: In the installer, specify only the instance port
  e.g. jdbc:sqlserver://localhost:1433;databaseName=MIR;

Note 1: The default database instance name for SQL Server Express is "sqlexpress, and "sqlserver" for any other SQL Server edition.
Note 2: The default SQL Server TCP/IP port number is 1433.

4.2 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".
• Set a quota amount for the user MIR:
  • ALTER USER MIR QUOTA quota ON USERS;
  • To resolved this error: "Database exception occured: ORA-01950: no privileges on tablespace 'USERS'"
• 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.3 MIR Database Connection

5. MIR Application Server Installation and Setup

5.1 Default install on Windows with bundled Tomcat

• Run the InstallShield program (by right-clicking and selecting "Run as Administrator" where available) following built-in steps and instructions.
• Prepare a MIR Database with a MIR user per instructions above or use the embedded SQL Server Express DB (no setup required).
• In the services manager in Windows, right-click on the Meta Integration service and under the "Log On" tab define an account by name under which the service will run. Be sure to use an account name which has full access to any API based product you are also installing on the server for bridge connectivity.
• Start the service. You may do so either from the Windows services manager or Start -> Program Files -> Meta Integration -> Server Restart (Service).
• Open your web browser and go to the address for the server.
  By default it is http://localhost:19980/MM
  You may also go to Start -> All Programs -> Meta Integration -> Metadata Management.
• When asked for a license file. Select Download license information and send that host file with your license request.
• After you have received it, browse for the license file and click on Save.
• Login as "Administrator" with password "Administrator". You may change the Administrator password by way of the web based user interface at Tools -> Administration -> Users.
• Provide connection information for the database you created above.
• You may configure memory usage and limitations for the app server by going to Start -> All Programs -> Meta Integration -> Server Configure.

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-2012 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

5.4 Custom integration with an external Single Sign-On (SSO) environment

Please follow the steps below to enable SSO, follow the instructions in the following file:

{MM_HOME}/data/tomcat/conf/server.xml

MIMM ships with a default keystore file located at:

{MM_HOME}/data/tomcat/conf/keystore.

This keystore is also imported into the JRE certificates shipped with MIMM. If you want to use a different certificate, you must:

1. Change the referenced (in server.xml) connector entry parameters (keystoreFile and keystorePass) to point to the correct keystore file and password.
2. Import that certificate into the JRE that is being used by this tomcat. The default JRE is located under {MM_HOME}/jre. Use the following commands:
• cd {MM_HOME}/jre/lib/security
• move jssecacers jssecacers.old
• {MM_HOME}/jre/bin/keytool -importkeystore -srckeystore {your_keystore} -keystore jssecacerts
• Restart MIMM.

After the configuration, by default use one of the following URLs to Access MIMM:

• http://localhost:19980/MM OR. All requests to this port will be redirected to the SSL port.
• https://localhost:8443/MM

Or use the ports specified in the server.xml file. E.g.,

<Connector port="19980" redirectPort="8443"/>
<Connector
port="8443" maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
keystoreFile="conf\keystore" keystorePass="changeit"
clientAuth="false" sslProtocol="TLS"/>