Sie sind auf Seite 1von 44

MEGA 2009 SP2 Deployment Guide

Last updated: November 18, 2009 Created: January 5, 2004

Authors: Christophe Cdard, Jrme Horber

CONTENTS

Summary This document describes the technical configurations necessary for installation of MEGA 2009 SP2 (MEGA Modeling Suite). It presents the different typical architectures and for each one, the recommended workstation and server configurations, and the installation procedures. The appendix gives solutions to problems you may encounter during installation. Guide Contents ............................................................................................................. 2 Common deployment models.............................................................................. 4 Deployment comparison table ............................................................................. 4 Stand-alone workstation .................................................................................... 4 WAN deployment .............................................................................................. 5 LAN deployment ............................................................................................... 5 LAN-RDBMS deployment .................................................................................... 6 Citrix Terminal server deployment ....................................................................... 7 MEGA Advisor deployment.................................................................................. 7 Configuration requirements................................................................................ 8 Stand-alone Workstation .................................................................................... 8 WAN deployment .............................................................................................. 9 LAN deployment ............................................................................................. 10 LAN-RDBMS deployment .................................................................................. 11 Client ............................................................................................................ 12 Citrix/Terminal server deployment ..................................................................... 13 MEGA Advisor deployment................................................................................ 15 Additional requirements for specific MEGA products.............................................. 16 Installation procedures .................................................................................... 19 Definitions ..................................................................................................... 19 Components ................................................................................................... 20 HASP driver.................................................................................................... 20 Stand-alone workstation .................................................................................. 21 WAN deployment ............................................................................................ 22 LAN deployment ............................................................................................. 27 LAN-RDBMS deployment .................................................................................. 32 Citrix/Terminal server deployment ..................................................................... 32 MEGA Advisor deployment................................................................................ 32 Removing MEGA ............................................................................................... 33 Remarks ........................................................................................................ 33
MEGA 2009 SP2 Deployment Guide page 2/44

Uninstalling MEGA Stand-alone ......................................................................... 33 Uninstalling MEGA Server ................................................................................. 33 Uninstalling MEGA Client (LAN deployment) ........................................................ 33 Uninstalling MEGA Client (WAN deployment) ....................................................... 33 Uninstalling RDBMS client (LAN-RDBMS deployment) ........................................... 34 Additional information...................................................................................... 35 Windows Service Pack ..................................................................................... 35 Anti-virus configuration.................................................................................... 35 Firewall configuration....................................................................................... 35 Physical backup configuration ........................................................................... 35 Technical documentation .................................................................................. 36 SVG format diagrams in generated Websites ....................................................... 36 Using Oriental Languages ................................................................................. 36 Installed folder and file details......................................................................... 37 User files ....................................................................................................... 37 Program folder access permissions .................................................................... 37 Environment folder access permissions............................................................... 38 Appendix .......................................................................................................... 40 Architecture FAQs ........................................................................................... 40 Installation FAQs............................................................................................. 42 MEGA License FAQs ......................................................................................... 44

MEGA 2009 SP2 Deployment Guide

page 3/44

COMMON DEPLOYMENT MODELS


MEGA Modeling Suite products can be deployed in different typical architectures: Stand-alone WAN deployment LAN deployment LAN-RDBMS client Citrix/Terminal Server deployment In Addition, the MEGA Advisor deployment is documented.
Other deployment models For specific requirements, other deployment models are possible. For further information, contact your sales representative.

Deployment comparison table


This table can help you choose the appropriate deployment model: Bandwidth / User > 10 Mbit/s 1 user 2 - 50 users More than 50 users WAN deployment or RDBMS deployment or Citrix/Terminal Server deployment Citrix/Terminal Server deployment Citrix/Terminal Server deployment

Stand-alone

LAN deployment or WAN deployment or RDBMS deployment WAN deployment Citrix/Terminal Server deployment

2 - 10 Mbit/s < 2 Mbit/s

Stand-alone Stand-alone

* Thin client deployment is described in a separate article, 'Citrix Terminal Server Deployment'. Above 50 users, we recommend a specific study to confirm that the deployment model and the administration procedures are appropriate to project activity and technical architecture used. With RDBMS deployment, we recommend a specific study to confirm that the deployment model and the administration procedures are appropriate to project activity and technical architecture used.

Stand-alone workstation
The Programs and the repository are installed on the workstation.
This architecture is recommended for single users or local evaluation. Data cannot be shared with other MEGA users.

MEGA 2009 SP2 Deployment Guide

page 4/44

WAN deployment
The programs and the repository are installed on a file server. The workstation runs a local copy of programs and has a local cache for data. Local programs are synchronized automatically when the file server is updated.
This architecture is recommended for working groups distributed over multiple sites.

LAN deployment
The programs and the repository are installed on a file server. The workstation uses shortcuts to load programs from the file server. It can also have a local copy of programs. Data is saved on the file server.
This architecture is recommended for working groups on a LAN.

MEGA 2009 SP2 Deployment Guide

page 5/44

LAN-RDBMS deployment
The programs and environment files are installed on a file server. The repository is stored on a relational database server (Oracle, SQL server). The workstation has a local copy of programs. Core data is saved on the database server.
The most common deployment mode is described here. For other deployments a specific study in necessary

Sql Server

Oracle

MEGA 2009 SP2 Deployment Guide

page 6/44

Citrix Terminal server deployment


The programs are installed on an application server, such as a Citrix or Terminal server. The repository is installed on a file server. The client runs a session on the application server. Data is saved on the file server.
This architecture is recommended for working groups distributed over multiple sites.

MEGA Advisor deployment


MEGA Advisor is a web application enabling to consult the content of the MEGA repository.
The most common deployment mode is described here. For other deployments a specific study in necessary. Note that a MEGA Must license is required on the server

Intra net MEGA R ep ository Inte rnet MEGA Se rv er W eb c lie nt MEGA Ad v isor App lic a tion serv e r

MEGA 2009 SP2 Deployment Guide

page 7/44

CONFIGURATION REQUIREMENTS
Configuration requirements depend on the selected deployment architecture.

Stand-alone Workstation

Operating system

Windows 7.0 Windows Vista SP1 Windows XP Professional SP2 or SP3 Internet Explorer: 6.0 or higher Adobe Reader: 5.0 or higher See also the section additional requirement of this document Processor 3 GHz or faster recommended RAM For Windows XP Minimum 512 MB 2 GB or higher recommended For Windows Vista/7.0 Minimum 1 GB 2.5 GB or higher recommended Resolution and colors Minimum 65536 colors (16-bit) Minimum 800 x 600 1024 x 768 or better recommended Disk space 2.5 GB minimum 3.5 GB recommended

Additional software

Hardware

For Windows 2000, see the section 'Architecture FAQs' later in this document.

MEGA 2009 SP2 Deployment Guide

page 8/44

WAN deployment

Client
Operating system Windows 7.0 Windows Vista SP1 Windows XP Professional SP2 or SP3 Internet Explorer: 6.0 or higher Adobe Reader: 5.0 or higher See also the section additional requirement of this document Processor 3 GHz or faster recommended RAM For Windows XP Minimum 512 MB 2 GB or higher recommended For Windows Vista/7.0 Minimum 1 GB 2.5 GB or higher recommended Resolution and colors Minimum 65536 colors (16-bit) Minimum 800 x 600 1024 x 768 or better recommended Disk space 600 MB Network bandwidth 2 Mbit/s minimum

Additional software

Hardware

File Server
Operating system Windows Server 2008 Windows Server 2008 R2 Windows Server 2003 SP1 or SP2 Windows Server 2003 SR2 For other file system a specific study in necessary Programs: 3 GB recommended Data: 1 GB recommended per environment RAM: see system requirements, 1 GB recommended. CPU: see system requirements.
page 9/44

Disk space Hardware

MEGA 2009 SP2 Deployment Guide

For Windows 2000, see the section 'Architecture FAQs' later in this document.

LAN deployment

Client
Operating system Windows 7.0 Windows Vista SP1 Windows XP Professional SP2 or SP3 Internet Explorer: 6.0 or higher Adobe Reader: 5.0 or higher See also the section additional requirement of this document Processor 3 GHz or faster recommended RAM For Windows XP Minimum 512 MB 2 GB or higher recommended For Windows Vista/7.0 Minimum 1 GB 2.5 GB or higher recommended Resolution and colors Minimum 65536 colors (16-bit) Minimum 800 x 600 1024 x 768 or better recommended Network bandwidth 100 Mbit/s or 1 Gbit/s recommended

Additional software

Hardware

File server
Operating system Windows Server 2008 Windows Server 2008 R2 Windows Server 2003 SP1 or SP2 Windows Server 2003 SR2 For other file system a specific study in necessary Programs: 3 GB recommended Data: 1 GB recommended per environment RAM: see system requirements, 1 GB recommended. CPU: see system requirements.
page 10/44

Disk space Hardware

MEGA 2009 SP2 Deployment Guide

For Windows 2000, see the section 'Architecture FAQs' later in this document.

LAN-RDBMS deployment
Sql Server

Oracle

MEGA 2009 SP2 Deployment Guide

page 11/44

Client
Operating system Windows 7.0 Windows Vista SP1 Windows XP Professional SP2 or SP3 Internet Explorer: 6.0 or higher RDBMS client For Oracle Nothing is needed. Oracle instant client is installed with MEGA programs (server side). For SQL Server SQL server 2008 native client Adobe Reader: 5.0 or higher See also the section additional requirement of this document Processor 3 GHz or faster recommended RAM For Windows XP Minimum 512 MB 2 GB or higher recommended For Windows Vista/7.0 Minimum 1 GB 2.5 GB or higher recommended Resolution and colors Minimum 65536 colors (16-bit) Minimum 800 x 600 1024 x 768 or better recommended Network bandwidth to database server 5 Mbit/s higher recommended

Additional software

Hardware

File server
Operating system Windows Server 2008 Windows Server 2008 R2 Windows Server 2003 SP1 or SP2 Windows Server 2003 SR2 For other file system a specific study in necessary Programs: 3 GB recommended Data: 1 GB recommended per environment RAM: see system requirements, 1 GB recommended. CPU: see system requirements.

Disk space Hardware

MEGA 2009 SP2 Deployment Guide

page 12/44

Database server
Operating system RDMS see RDBMS requirements Oracle Database Server 11 Standard or Enterprise Edition Version 11.1.0.6* Oracle Database Server 10g R2 Standard or Enterprise Edition Versions 10.2.0.4 or higher SQL Server 2008 Standard or Enterprise Edition SQL Server 2005 Standard or Enterprise Edition * Data: 1 GB recommended per repository RAM: a specific study is required. Refer to the separate article 'RDBMS Deployment' CPU: see RDBMS requirements.

Disk space Hardware

For Windows 2000, see the section 'Architecture FAQs' later in this document. * Versions qualified from MEGA 2009 SP2 CP2.0.

Citrix/Terminal server deployment

Client
Operating system Citrix presentation server client Windows 32/64 bit clients (95/98/2000:XP/2003/Vista/2008) WinCE/PocketPC clients Linux clients UNIX clients Mac clients Java clients IBM OS/2 clients Remote Desktop Web Connection Windows 98/NT/2000/XP/Vista/7.0 Remote Desktop Connection Windows 98/NT/2000/XP/Vista/7.0 No specific requirement for MEGA.

Hardware

MEGA 2009 SP2 Deployment Guide

page 13/44

Application server
Operating system Windows Server 2008 Windows Server 2008 Windows Server 2003 Windows Server 2003 Internet Explorer: 6.0

R2 SP1 or SP2 SR2 or higher

Application server layer

Citrix Presentation Server 3.0, 4.0 or 4.5 Standard Edition Advanced Edition Enterprise Edition Platinium Edition Microsoft 2003 Server Terminal Services Adobe Reader: 5.0 or higher See also the section additional requirement of this document Processor 1 CPU at 3 GHz or faster for 16 users RAM 512 MB minimum for the Terminal Server system and for the Citrix system 250 MB or more per user for the client and MEGA Resolution 65000 colors minimum. Internet bandwidth Average 100 Kbit/s per concurrent user for commonly used features

Additional software

Hardware

File Server
Operating system Windows Server 2008 Windows Server 2008 R2 Windows Server 2003 SP1 or SP2 Windows Server 2003 SR2 For other file system a specific study in necessary Programs: 3 GB recommended Data: 1 GB recommended per environment RAM: see system requirements, 1 GB recommended. CPU: see system requirements.

Disk space Hardware

For Windows 2000, see the section 'Architecture FAQs' later in this document.

MEGA 2009 SP2 Deployment Guide

page 14/44

MEGA Advisor deployment


MEGA Advisor is a web application enabling to consult the content of the MEGA repository.
The most common deployment mode is described here. For other deployments a specific study in necessary. Note that a MEGA Must license is required on the server

Intra net MEGA R ep ository Inte rnet MEGA Se rv er W eb c lie nt MEGA Ad v isor App lic a tion serv e r

Client
HTML client MS Internet Explorer IE 6.0, IE 7.0 Mozilla Firefox Firefox 2.0, 3.0 Network bandwith 256 KBit/s or higher

Hardware

Application and Web Server (MEGA Advisor only)


Operating system Windows 2008 Server Windows 2003 Server SP1 or SP2 For other file system a specific study in necessary Processor Multi core server. RAM 2 GB minimum. 1 GB for the system 200 MB per MEGA connection profile* (consultation mode) recommended. Disk space 3 GB for MEGA Server and MEGA Advisor installation 300 MB per MEGA connection profile* for cache Select upper quality components for disk, disk controller card MS Internet Information Server 6.0 MS Internet Information Server compatibility mode) ASP .NET .NET Framework 2.0 or higher 7.0 (with IIS 6.0

Hardware

Web Server

Script layer

* A MEGA connection profile is a couple: repository accessed x repository language.


MEGA 2009 SP2 Deployment Guide page 15/44

For common configurations (less that 5 profiles), a 2-core processor is enough to handle the load.

Application and Web Server (MEGA Advisor and Web Editor)


Operating system Windows 2008 Server Windows 2003 Server SP1 or SP2 For other file system a specific study in necessary Processor Multi core server. RAM 2 GB minimum. 1 GB for the system 200 MB per MEGA connection profile (consultation mode) recommended. 200 MB per concurrent user (update mode) recommended Disk space 3 GB for MEGA Server and MEGA Advisor installation 300 MB per MEGA connection profile for cache Select upper quality components for disk, disk controller card MS Internet Information Server 6.0 MS Internet Information Server compatibility mode) ASP .NET .NET Framework 2.0 or higher 7.0 (with IIS 6.0

Hardware

Web Server

Script layer

* A MEGA connection profile is a couple: repository accessed x repository language.

Additional requirements for specific MEGA products


Document generation in collaboration with MS-Word
The MS Word document generation feature supports Ms Word version 2002 (XP), 2003 and 2007. All workstations in a MEGA working group should have the same version of MS-Word installed. In stand-alone, LAN, and WAN deployment architectures, MEGA requires local installation of MS Word on each workstation.

Document generation in collaboration with OpenOffice


The Open Office document generation feature supports OpenOffice version 2.3.0. All workstations in a MEGA working group should have the same version of Open Office installed. In stand-alone, LAN, and WAN deployment architectures, MEGA requires local installation of Open Office Writer on each workstation.

MEGA 2009 SP2 Deployment Guide

page 16/44

MEGA Database Designer


The corresponding 32-bit ODBC driver is required for the database to be reverse engineered (Oracle, DB2, SQL Server).

MEGA Simulation
The simulation report features requires version 2002, 2003 or 2007 of MS Excel.

MEGA Advisor and MEGA Web Editor


These applications have been qualified for these HTML browsers: Internet explorer 8.x Yes* Yes* Internet explorer 7.x Yes* Yes* Internet explorer 6.x Yes* Yes* Mozilla Firefox 3.x Yes* Yes* Mozilla Firefox 2.x Yes* Yes*

MEGA Advisor MEGA Advisor and MEGA Web Editor

* Display of popup menu onto diagram map is slightly different Internet Explorer.

MEGA Publisher - Web Publisher


The web site templates have been qualified for these HTML browsers: Internet explorer 8.x Yes Internet explorer 7.x Yes Internet explorer 6.x Yes Mozilla Firefox 3.x Yes* Mozilla Firefox 2.x Yes*

MEGA Enterprise Portal

* Absolute Risk Map is not displayed with Mozilla Firefox.

MEGA Exchange - API


Script API functions can be used in: Applications supporting COM (MS Visual Basic version 6, MS Office version 2002/2003/2007..) .Net applications. VB Script, JavaScript, PERL Java API functions can be used in Java application (Eclipse) The Excel editor and report features requires version 2002, 2003 or 2007 of MS Excel.

Import/Export
Depending of the MEGA Product, different import and export features are available. The Erwin Import feature supports the version 4.1 and 7.0 of Computer Associates Allfusion ERwin Data Modeler. The Power Designer Import feature supports the version 11 and 12.5 of Sybase Power Designer. The Oracle Designer Import feature supports version 10g of Oracle Designer. The XMI Export feature supports version 2.1 of XMI.
page 17/44

MEGA 2009 SP2 Deployment Guide

The XMI Import feature supports XMI 1.0 (UML 1.3) The Rose Import/Export feature support version 2000, 2002 and 2003if IBM Rational Rose. The XPDL (BPMN) Export feature supports version 2.0 of the XPDL language. The Solman Import/Export feature support versions 4.7, 7.0 and 7.0 EPH1 of SAP Solution Manager. The Appian Export feature supports version 5.7 and 6.0 of Appian. The Doors Import/Export features support versions 8.1, 8.2 and 8.3 of IBM Telelogic Doors. The Web Services Import feature supports version 2.0 and 3.0 of the UDDI protocol. MEGA Designer - Integration. The WSDL Import feature supports version 1.1 of WSDL standard. The BPEL4WS Export feature supports version 1.1 of the BPEL4WS language. The XPDL Export feature supports version 2.0 of the XPDL language. The BPEL Export feature supports version 1.1 of the BPEL language. The Visio import feature supports version 2002, 2003 or 2007 of MS Visio. The MS Project export feature supports version 2002 of MS Project. The Casewise import feature supports version 9.3 of Casewise Corporate Modeler. The Popkin import feature supports version 10.1 of IBM Rational System Architect.

MEGA 2009 SP2 Deployment Guide

page 18/44

INSTALLATION PROCEDURES

Definitions
Environment Workspace of a user or group of users. In a default installation, the 'Demonstration' environment is located in the folder <MEGA installation file>\Demonstration. Several predefined users are created: o Administrator ('Administrator' user). o User. o Guest (for MEGA Advisor connections) o Change Requester 1 (for MEGA Advisor connections) o Change Requester 2 (for MEGA Advisor connections)

For GBMS storage: Permissions on the root folder of the environment and its subfolders should be of 'Full control' type for MEGA users. The environment contains created and customized data. It should be physically backed up daily (backup is discussed later in this document). 'Demonstration' environment Example environment that includes: A demonstration repository 'Adventure' containing sample models. A repository 'MEGA (Tutorial)' for illustration of chapters of the user guides. A user 'Mister Guide' for working in the MEGA (Tutorial) repository Other users corresponding to specific profiles, for working in the demonstration repositories. These users are configured for a restricted view of the repositories and of MEGA products. Example: o Alan - (Process, BPMN design) o o Thomas - (All Products)
This environment should not be used to enter production data. A new separate environment should be created for this purpose. 'Demonstration' environment files are likely to be deleted at version removal, or reinitialized at version or service pack update.

MEGA 2009 SP2 Deployment Guide

page 19/44

Components
Different components can be installed. Example Environment MEGA Software o Administration Program o MUST License Management Program o MEGA Advisor o Utilities o Example files o MEGA Documentation A feature description (comment) is available in the installation wizard. For each component, several installation policies are proposed: 'This feature will be installed on local hard drives': in this mode, all components selected are available when required. 'This feature, and all sub-features, will be installed on local hard drives': this mode is recommended to ensure that all components selected are available when required. 'This feature will not be available': this feature is appropriate only if the component is optional and if the customer considers if will never be used.

HASP driver
Unlike previous versions of MEGA, HASP device driver is not installed by the MEGA installation program. If you use the HASP protection system on a new machine, you need to install it separately with the appropriate utility (Example: Hinstall.exe). Please consult the technical article 'HASP License Deployment'. Consult your MEGA administrator to find out if you need this driver installation.

MEGA 2009 SP2 Deployment Guide

page 20/44

Stand-alone workstation
Prerequisites
Confirm that you have: Local administrator rights for the workstation (for update of the system). 'Full control' of the installation folder. 2.5 GB free space on the installation folder drive. Verify the system of the machine.

Installing MEGA stand-alone

Insert the MEGA disk in the disk drive. The installation program will start running automatically.
If the program does not start automatically, run the "\_default\Disk1\Setup.exe" program on the disk.

Select the language of the user interface. Accept the license agreement. Choose whether the MEGA application is installed for all users or for the current user. Indicate the folder in which you wish to install MEGA. This folder must not be the root of the drive. For example, C:\Program files\MEGA. In the 'Setup type' window, select 'Complete installation'. Run the installation and wait for confirmation of completion. The MEGA application is installed The system of the machine is updated (registry, libraries). The MEGA components selected by default are installed.

Components installed

Installing the MEGA license


Consult your sales representative to obtain a license. You will get a license file and instructions to install it.

MEGA 2009 SP2 Deployment Guide

page 21/44

WAN deployment
Overview
WAN deployment includes the following steps: Installing the MEGA Server on the file server. Installing the MEGA license. Installing a new environment. Configuring MEGA users. Installing a MEGA Client on each workstation.

Installing the MEGA Server on the file server

Prerequisites The installation program must be run from the server console of the server. Only one installation of MEGA 2009 SP2 is authorized on each machine. Confirm that you have: Local administrator rights for the machine used for installation (for update of the system). 'Full control' of the installation folder of the file server. 2.5 GB free space on the installation folder disk.

On the server disk, create a folder and make it accessible to all users. This folder will be used to host MEGA programs (Example: \\SVRNAME\Software). If you use a network drive letter for this folder, this letter should be defined on all workstations.

MEGA 2009 SP2 Deployment Guide

page 22/44

MEGA Server installation Insert the MEGA disk in the disk drive. The installation program will start running automatically.
If the program does not start automatically, run the "\_default\Disk1\Setup.exe" program on the disk.

Select the language of the user interface. Accept the license agreement. Choose whether the MEGA application is installed for all users or the current user. Indicate the folder in which you wish to install MEGA. It must be a sub-folder of the MEGA shared folder (\\SRVNAME\Software\Mega) In the 'Setup type' window, select 'Server Installation' to control the components installed. Clear the 'Example environment' component by selecting 'The feature will not be available' Run the installation and wait for confirmation of completion. The MEGA application is installed. The system of the machine used for installation is updated (registry, libraries). The selected MEGA components are installed.

Components installed

Installing the MEGA license


Consult your sales representative to obtain a license. You will get a license file and instructions to install it.

MEGA 2009 SP2 Deployment Guide

page 23/44

Installing a new environment

Prerequisites Confirm that you have: 'Full control' of the installation folder. 200 MB free space on the installation folder drive. Select as the installation folder a network address accessible to all users. If you use a network drive letter at installation, the same letter should be defined on all workstations. Installation procedure Start the 'Administration' program. Right-click the 'Environments' folder and select 'New'. For 'Location', select or create the environment root folder. For example, \\Server1\Teamworking\MEGA\Data. Enter a value for 'Name'. If the environment is called 'Standard', a folder will be created with the same name, for example in \\Server1\Teamworking\MEGA\Data\Standard. Click 'OK' to create the new environment. When processing is completed, the environment should appear in the list. Right-click the new environment and select 'Open'. Identify yourself as 'Administrator', and then click 'OK'. Right-click the 'Repositories' folder and select 'New'. Enter a value for 'Name' and keep the default location. Click 'OK' to create the new repository. When processing is completed, the new repository should appear in the list. Exit the MEGA administration program.

Configuring MEGA users


Procedure Run the MEGA administration program. Open the environment (for example with the Administrator user). Select the User Accounts > Users folder Right click and select 'Manage'. Click on the button 'New'. Configure the user properties. Click 'OK' to create the user. Exit the 'Manage Users' dialog box. Exit the MEGA administration program.

MEGA 2009 SP2 Deployment Guide

page 24/44

If you do not know how to set obligatory properties when creating a user, use the following values: Repository Access Mode: Implicit access. Authorization: Administrator. Confidentiality area: Standard. Authentication mode: MEGA. Syntax for the Command line property /K'<list of product/option codes>' Examples: MEGA Process only: /K'PRO,LAN' MEGA Process and MEGA Architecture /K'PRO,ARC,LAN' For the list of common product/option codes, see the section MEGA Licence FAQs of this document. MEGA Must license can propose bundled products: bundle codes are then displayed in the MEGA Must User Manager Utility. To list the product codes of the products of your license: Menu Help > About MEGA Click button 'System information'

MEGA 2009 SP2 Deployment Guide

page 25/44

Installing a MEGA client on each workstation

Prerequisites Confirm that you have: A MEGA server installation. 600 MB free space and 'Full control' of the local installation folder. Rights to update the workstation registry (recommended). Network bandwidth of 10 Mbit/s minimum during installation. For each client, identify if a system update is necessary to run specific programs using MEGA API scripts. If you do not know how to answer this question, consult the functional administrator of MEGA. For each client, identify if the installation of a HASP device driver is appropriate. For more information, consult the section 'Installation FAQs' later in this document. If you do not know how to answer this question, consult the functional administrator of MEGA. Installation procedure Browse to the installation of MEGA on the file server Run <MEGA installation folder>\Install\WanSetup\WanSetup.exe. Select the language for the user interface. Select the folder for local programs. For example, C:\program files\MEGA\MEGALocal. For local cache activation, o Select 'Yes, I want to activate local cache. For MEGA registration, o Select 'Yes, I want to register MEGA in my system' if a system update is identified as required for this machine (recommended). o Select 'Do not register MEGA' otherwise. Verify installation settings and click 'Next' to perform installation. The machine system libraries are not modified. The workstation registry is modified if registration is requested. MEGA programs are copied on a local folder. MEGA local cache is enabled for all users of this MEGA client.

Components installed o o o o

MEGA 2009 SP2 Deployment Guide

page 26/44

LAN deployment
Overview
LAN deployment includes the following steps: Installing the MEGA Server on the file server. Installing the MEGA license. Installing a new environment. Configuring MEGA users. Configuring MEGA workstations.

When configuring MEGA workstations, you can: Create only MEGA shortcuts on each workstation. Create a local copy of programs (automatic consistency check with the MEGA Server).

Installing the MEGA Server on the file server

Prerequisites The installation program must be run from the server console of the server. Only one installation of MEGA 2009 SP2 is authorized on each machine. Confirm that you have: Local administrator rights for the machine used for installation (for update of the system). 'Full control' of the installation folder of the file server. 2.5 Go free space on the installation folder disk.

On the server disk, share a folder and make it accessible to all users. This folder will be used to host MEGA programs and MEGA data (Example: \\SVRNAME\Software). If you use a network drive letter for this folder, this letter should be defined on all workstations.

MEGA 2009 SP2 Deployment Guide

page 27/44

MEGA Server installation Insert the MEGA disk in the disk drive. The installation program will start running automatically.
If the program does not start automatically, run the "\_default\Disk1\Setup.exe" program on the disk.

Select the language of the user interface. Accept the license agreement. Choose whether the MEGA application is installed for all users or the current user. Indicate the folder in which you wish to install MEGA. It must be a sub-folder of the MEGA shared folder (\\SRVNAME\Software\Mega) In the 'Setup type' window, select 'Server Installation' to control the components installed. Clear the 'Example environment' component by selecting 'The feature will not be available' Run the installation and wait for confirmation of completion. The MEGA application is installed The system of the machine used for installation is updated (registry, libraries). The selected MEGA components are installed.

Components installed

Installing the MEGA license


Consult your sales representative to obtain a license. You will get a license file and instructions to install it.

MEGA 2009 SP2 Deployment Guide

page 28/44

Installing a new environment

Prerequisites Confirm that you have: 'Full control' of the installation folder. 200 MB free space on the installation folder drive.

Select as the installation folder a network address accessible to all users. If you use a network drive letter at installation, the same letter should be defined on all workstations. Installation procedure Start the 'Administration' program. Right-click the 'Environments' folder and select 'New'. For 'Location', select or create the environment root folder. For example, \\Server1\Teamworking\MEGA\Data. Enter a value for 'Name'. If the environment is called 'Standard', a folder will be created with the same name, for example in \\Server1\Teamworking\MEGA\Data\Standard. Click 'OK' to create the new environment. When processing is completed, the environment should appear in the list. Right-click the new environment and select 'Open'. Identify yourself as 'Administrator', and then click 'OK'. Right-click the 'Repositories' folder and select 'New'. Enter a value for 'Name' and keep the default location. Click 'OK' to create the new repository. When processing is completed, the new repository should appear in the list. Exit the MEGA administration program.

MEGA 2009 SP2 Deployment Guide

page 29/44

Configuring MEGA users


Procedure Run the MEGA administration program. Open the environment (for example with the Administrator user). Select the User Accounts > Users folder Right click and select 'Manage'. Click on the button 'New'. Configure the user properties. Click 'OK' to create the user. Exit the 'Manage Users' dialog box. Exit the MEGA administration program. If you do not know how to set obligatory properties when creating a user, use the following values: Repository Access Mode: Implicit access. Authorization: Administrator. Confidentiality area: Standard. Authentication mode: MEGA. Syntax for the Command line property /K'<list of product/option codes>' Examples: MEGA Process only: /K'PRO,LAN' MEGA Process and MEGA Architecture /K'PRO,ARC,LAN' For the list of common product/option codes, see the section MEGA Licence FAQs of this document. MEGA Must license can propose bundled products: bundle codes are then displayed in the MEGA Must User Manager Utility. To list the product codes of the products of your license: Menu Help > About MEGA Click button 'System information'

Configuring each workstation (MEGA shortcuts)

MEGA 2009 SP2 Deployment Guide

page 30/44

Prerequisites Confirm that you have: A MEGA server installation. 50 MB free space and 'Full control' of the local installation folder. Rights to update the workstation registry (recommended).

For every client, identify for which program a shortcut is appropriate: o Mega.exe: appropriate for all users. o Administration: appropriate for users performing application tasks. o Licensing.exe: appropriate for users managing MEGA Must licences. If you do not know how to answer this question, consult the functional administrator of MEGA. Installation procedure Create a shortcut for the appropriate programs. Example: shortcut on \\SRVNAME\Software\Mega\Mega.exe

It is also recommended to register the MEGA application in the client registry. For this, execute the application 'Mgwmapp.exe' in command-line mode with the /regserver parameter. Example: "\\SRVNAME\Software\Mega\System\Mgwmapp.exe" /regserver Components installed No component is installed locally if only shortcuts have been created. Registry is updated if the MEGA application has been registered.

Configuring each workstation (Local copy of programs)

Prerequisites Confirm that you have: A MEGA server installation. 600 MB free space and 'Full control' of the local installation folder. Rights to update the workstation registry (recommended).

Installation procedure Browse to the installation of MEGA on the file server Run <MEGA installation folder>\Install\WanSetup\WanSetup.exe. Select the language for the user interface.
page 31/44

MEGA 2009 SP2 Deployment Guide

Select the folder for local programs. For example, C:\program files\MEGA\MEGALocal. For local cache activation, o Keep 'No, I do not want to activate local cache'. For MEGA registration, o Select 'Yes, I want to register MEGA in my system' if a system update is identified as required for this machine (recommended). o Select 'Do not register MEGA' otherwise. Verify installation settings and click 'Next' to perform installation.

Components installed o o o The machine system libraries are not modified. The workstation registry is modified if registration is requested. MEGA programs are copied on a local folder.

LAN-RDBMS deployment
Refer to the separate article 'RDBMS Deployment MEGA 2009' for complete instructions.

Citrix/Terminal server deployment


Refer to the separate article 'Citrix Terminal Server Deployment MEGA 2009' for complete instructions.

MEGA Advisor deployment


For complete instructions, refer to the separate article 'MEGA 2009 Advisor Deployment Guide'.

MEGA 2009 SP2 Deployment Guide

page 32/44

REMOVING MEGA

Remarks
The uninstallation program may not delete all folders, since some files are created after installation. You must delete remaining folders after checking that these do not relate to the environment (containing data).

Uninstalling MEGA Stand-alone


On the machine from where MEGA was installed: In the Control Panel, click 'Add or Remove Programs'. Select the icon corresponding to MEGA installation (MEGA 2009 SP2). Click 'Remove' and confirm the removal..

Uninstalling MEGA Server


On the machine from where MEGA was installed: In the Control Panel, click 'Add or Remove Programs'. Select the icon corresponding to MEGA installation (MEGA 2009 SP2). Click 'Remove' and confirm the removal.

Uninstalling MEGA Client (LAN deployment)


If only shortcuts have been installed, remove shortcuts to MEGA programs. No uninstallation program is provided for this. If a local copy of programs has been performed with registration of MEGA, on each workstation from where a MEGA Client was installed: In the Control Panel, click 'Add or Remove Programs'. Select the icon corresponding to MEGA installation (MEGA Wan Client).* Click 'Change/Remove' Select 'Remove' then 'Next' Verify settings and click 'Next' to trigger removal. * Even if a MEGA client was installed for LAN deployment, it is tagged as 'MEGA Wan Client'. Alternative procedure: On each workstation from where a MEGA Client was installed: Browse to the installation of MEGA on the file server. Run <MEGA installation folder>\Install\WanSetup\WanSetup.exe. Select 'Remove', click on 'Next', then click on 'Next' to run the uninstall program. Click 'Finish' to exit the WanSetup program.

Uninstalling MEGA Client (WAN deployment)


On each workstation from where a MEGA Client was installed: Browse to the installation of MEGA on the file server. Run <MEGA installation folder>\Install\WanSetup\WanSetup.exe. Select 'Remove', click on 'Next', then click on 'Next' to run the uninstall program. Click 'Finish' to exit the WanSetup program.

MEGA 2009 SP2 Deployment Guide

page 33/44

Uninstalling RDBMS client (LAN-RDBMS deployment)


Refer to the separate article 'RDBMS Deployment MEGA 2009' for complete instructions.

MEGA 2009 SP2 Deployment Guide

page 34/44

ADDITIONAL INFORMATION

Windows Service Pack


It is essential to check compatibility with MEGA before installing a new Windows Service Pack on a machine where MEGA is installed.

Anti-virus configuration
For the generation functions of MEGA to operate normally, your anti-virus software should not prohibit script execution.

Firewall configuration
For the generation functions of MEGA to operate normally, your firewall or anti-virus software should not prohibit the execution of the following processes: mgwmwmu.exe: MEGA Advisor mgwmwas.exe: MEGA Web Access (main process) mgwspro.exe: MEGA Web Access (sub process) mgwmwum.exe: MEGA Web Access User manager mgwusrmng.exe: MEGA Must license manager utility (MEGA Must license).

Physical backup configuration


We recommend systematic backup of the complete folder of each MEGA environment and its subfolders. Such a backup will contain the core of MEGA data: A 'Db' folder with all user repositories. A 'Sysdb' folder with systemdb repository. A 'Mega_usr' folder with user customizations. Folders containing deliveries located other than in an environment folder can also be backed up. Examples: Folder of shared document. By default, in the 'Document' folder of the MEGA repository folder. Folder of generated Web sites. By default, in the 'Intranet' folder of the MEGA environment folder. Folder of detached documents: By default, in the 'Approve' folder of the MEGA repository folders. The 'CFG' and 'Mega_usr' folders of each MEGA installation folder may contain certain configurations and customization files: these can also be backed up. Other folders can be created by users to document or archive customizations: these can also be backed-up. Notes: Files created in the user folder are not considered as data. If MEGA is deployed with offline mode, a specific procedure is required. If MEGA is deployed with LAN-RDBMS deployment mode, a specific procedure is required. Please refer to the article 'RDBMS Deployment'.

MEGA 2009 SP2 Deployment Guide

page 35/44

It is not necessary to back up MEGA programs (server or client). It is however necessary to document deployment choices made by the project.

Frequency: We recommend daily data backup if the project is active. Backup mode (GBMS storage): We recommend data backup in full backup and cold backup mode, at least for MEGA repository files. We have found that with some file systems, differential/incremental backup did not save MEGA repository files correctly. We can not guarantee hot backup mode either. To ensure a valid backup, the files must not be accessed during the backup processing. For this, you can: Make the shared folder temporarily not available at file server level. Use the MEGA option 'Authorize dispatch for the environment'

Technical documentation
User guides are supplied in .pdf format. You must install Adobe Reader 5.0 or higher to consult these. The \AcroRead folder of the MEGA disk contains an Acrobat Reader installation program. The different versions of Adobe Reader are available free of charge at the following address: http://www.adobe.com/products/acrobat/readstep2_allversions.html

SVG format diagrams in generated Websites


An SVG viewer must be installed to display diagrams in SVG (Scalable Vector Graphics) format. MEGA recommends the use of Adobe SVG viewer 3.0, available free of charge at the following address: http://www.adobe.com/support/downloads/product.jsp?product=46&platform=Windows

Using Oriental Languages


MEGA supports oriental languages, such as Chinese, Korean or Japanese, etc. Please read the article 'Multilinguism deployment' for specific requirements.

MEGA 2009 SP2 Deployment Guide

page 36/44

INSTALLED FOLDER AND FILE DETAILS

User files
The different files are created at user level (application data and local settings): File Megawks.ini MegaErrYYYYMMDD.txt MEGASETTINGS.INI When Example C:\Documents and Settings\User01\Application Data\Mega C:\Documents and Settings\User01\Local Settings\Application Data\Mega C:\Documents and Settings\User01\Application Data\Mega

using MEGA, each user must have: A personal 'application data' folder where he or she can read, write and delete. A personal 'local settings' folder where he or she can read, write and delete. A personal' 'temporary' folder where he or she can read, write and delete. Access to environment shared folders.

Program folder access permissions


To install or update MEGA, you need to have full control on all of the following folders. When installation is completed, the administrators who manage MEGA repositories need the following 'Administrator rights'. Other MEGA users need the following 'User rights'. It is also possible to secure access to MEGA data files. In this mode, which is based on ACL technology, updates to the MEGA repository data files (.EMB, .EML) require a system account. This means that users can update the data files through MEGA, but they cannot move, change, or delete the physical data files. Refer to the article 'Repository data access protection' for more information. Refer to the table below for the correspondence between the permission names referred to in the subsequent tables, and the specific access rights. Permission name / Access rights Read No delete Full control Read X X X Execute X X X Write Delete

X X

Folder <Installation folder> <Installation folder> \Cfg

Contents Main programs MEGA program configuration (Contains list of accessible environments) Product documentation and technical articles (PDF) Workstation and environment installation Java resources for future use.

Administrator rights Full control Full control

User rights Read Read

<Installation folder> \Documentation and subfolders <Installation folder> \Install and sub-folders <Installation folder> \java and sub-folders
MEGA 2009 SP2 Deployment Guide

Full control Full control Full control

Read Read Read

page 37/44

Folder <Installation folder> \Mega_Std and sub-folders <Installation folder> \Mega_Usr <Installation folder> \Samples and sub-folders <Installation folder> \System and sub-folders <Installation folder> \Utilities and sub-folders

Contents Resource files (.ICO, .MGS, .BMP, .DOT.. files) Customized resources (.MGS, .DOT files) Sample resources Program files (DLL) and online help files (CHM) Program utilities

Administrator rights Full control Full control Full control Full control Full control

User rights Read Read Read Read Read

Environment folder access permissions


By default, the workspace (MEGA environment) is a sub-directory of the installation directory (MEGA site). Folder <Environment folder> <Environment folder> \Db <Environment folder> \Db\<Repository> Contents Environment main folder Repository folders Repository folder. If the repository is stored in the GBMS storage format (default), each MEGA repository consists of 4 files (.EMA, .EMB, .EMS, EMV). If the repository is stored in Oracle, each MEGA repository consists of 2 files (. EMV, .EMO) and files on the database server. If the repository is stored in SQL Server, each MEGA repository consists of 2 files (. EMV, .EMQ) and files on the database server. Documents detached from MEGA. This folder can be configured. Administrator rights Full control Full control Full control User rights Full control Read No delete

By default <Environment folder> \Db\<Repository> \<Approve <Environment folder> \Db\<Repository> \<Repository>.Lock <Environment folder> \Db\<Repository> \<Repository>.Log <Environment folder> \Db\<Repository> \<Repository>.Transac tions
MEGA 2009 SP2 Deployment Guide

Full control

Full control

Repository locks. One file (.EMK) per lock placed. These files can be created and deleted during use of MEGA with GBMS storage format only Repository backup logfile. One file (.MGL) per administration session or per dispatched transaction. These files can be created and deleted during use of MEGA. Repository transactions. If the repository is stored in the GBMS format (default), each MEGA transaction consists in two files per
page 38/44

Full control

Full control

Full control

Full control

Full control

Full control

Folder

Contents transaction (.EMB and .EMS). These files are created on opening a transaction and deleted at each dispatch. If the repository is stored in Oracle or SQL Server, each MEGA transaction is saved in specific tables. Repository shared documents folder (default) Personal folders of the users Repository folder administration work

Administrator rights

User rights

<Environment folder> \Db\<Repository> \Document <Environment folder> \Db\<Repository> \USER and sub-folders <Environment folder> \Db\<Repository> \WORK <Environment folder> \Intranet <Environment folder> \Mega_Usr <Environment folder> \SysDb <Environment folder> \SysDb\SystemDb.Tran sactions

Full control Full control Full control Full control Full control Full control

Full control Full control Full control Full control Read No delete

<Environment folder> \SysDb\SystemDb.Lock

<Environment folder> \SysDb\SystemDb.Log

<Environment folder> \SysDb\USER and subfolders <Environment folder> \SysDb\WORK

Default root folder for HTML page generation. Not created by the installation. Folder containing customized resources (.MGS, .DOT files) Environment system repository. Consists of 4 files (SystemDb.ema, SystemDb.emb, SystemDb.ems, SystemDb.emv) Systemdb transactions. If the repository is stored in the GBMS format (default), each MEGA systemdb transaction consists in two files per transaction (.EMB and .EMS). These files are created on opening a transaction and deleted at each dispatch. If the repository is stored in Oracle or SQL Server, each MEGA systemdb transaction is saved in specific tables. Systemdb locks. One file (.EMK) per lock placed. These files can be created and deleted during use of MEGA with GBMS storage format only Systemdb repository backup logfile. One file (.MGL) per administration session or per dispatched transaction. These files can be created and deleted during use of MEGA. User report folders Systemdb folder administration work

Full control

Full control

Full control

Full control

Full control

Full control

Full control Full control

Full control Full control

MEGA 2009 SP2 Deployment Guide

page 39/44

APPENDIX

Architecture FAQs
Does MEGA support storage in RDBMS? Yes. MEGA systemdb and user repositories can be stored in RDMS (Relational Database Management System) . Different version of Oracle and SQL server are supported. It is still necessary to create an environment folder. What is GBMS/RDBMS storage? There are different storage formats for a MEGA repository: GBMS (MEGA DBMS, proprietary format). Oracle (RDBMS, Oracle). SQL Server (RDBMS, SQL Server).

More generally speaking: A MEGA environment is called a GBMS environment if its systemdb repository and user repositories are stored in the GBMS format. A MEGA environment is called a RDBMS environment if its systemdb repository and user repositories are stored in the Oracle or SQL Server format. Does MEGA run with Citrix? Yes. Refer to the section Citrix/Terminal server deployment' of this document and the article 'Citrix Terminal Server Deployment' for more information. Does MEGA run with Terminal server? Yes. Refer to the section 'Thin client deployment' of this document and the article 'Citrix Terminal Server Deployment' for more information. What is recommended for mobile users? MEGA recommends a stand-alone installation with an offline mode configuration. Note that a local license is required. Please refer to the article 'Managing Stand-Alone Workstations > Connection Modes in MEGA > Changing to Offline Mode' for more information. Does MEGA support dual core processors? Yes. MEGA can run on dual core processor machines. However, the MEGA application is not designed to benefit from dual core processor performances. Does MEGA support Windows 2000? Windows 2000 SP3 or SP4 is still supported fro MEGA 2009 as operating system for the client, file server or application server. It is supported for the following deployment modes: standalone, Lan deployment, Wan deployment, Citrix/Terminal server deployment. However it is not recommended (deprecated status). Support of Windows 2000 will be abandoned in the future versions of MEGA. For each Windows 2000 machine, it is necessary to install Microsoft runtime. This is made by installing 'Microsoft Visual C++ 2005 Redistributable Package (x86)' (file vcredist_x86.exe).
MEGA 2009 SP2 Deployment Guide page 40/44

This installation package is installed in the folder \Install\VCRuntime of a MEGA installation (MEGA 2009 SP1 CP2.0 and higher). It can be also be downloaded from Microsoft web site. http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99220B62A191EE&displaylang=en

MEGA 2009 SP2 Deployment Guide

page 41/44

Installation FAQs
What is the impact of the choice 'Install the application for'? Depending on this choice, the MEGA installation is valid: For all the Windows profiles using this machine (All users). Only for the user performing the installation (current user). Are there recommendations for the shared folder? Yes, as follows: Recommended configuration DFS For example, \\Soft\Mega UNC For example, \\Sr001\Soft\Mega Network letter For example, M:\Mega Where M: is mapped on \\Sr001\Soft Requirement: all users must configure network letter M: Not recommended configuration Administrative share For example, \\Server\c$\Mega Network letter (root) For example, M :\ Where M: is mapped on \\Sr001\Soft\Mega How to identify if a system update is required for a client machine? This depends on the client customizations. Examples: Only standard MEGA features are used: system update is not required. Customized features exist but they do not use MEGA API script: system update is not required. Customized features exit and they use MEGA API script: system update is required if the API script code created an instance of the MEGA application. If you do not know how to answer this question, consult the author of the code. How to identify if the installation of a HASP device driver is appropriate for a client machine? Installation of a HASP diver driver is appropriate if: The user of this machine is using a HASP key as local license. No HASP device driver has been installed on this machine (new machine or machine never used to run MEGA). Installation of a HASP diver driver is not appropriate if: The user of this machine is not using a HASP key. In most cases, users are using a network license. A HASP device driver has been installed on this machine. The machine is installed with Vista (installation of Vista has already installed the required elements). Do I risk losing my data when removing a MEGA installation? No, if you have created an environment from scratch. Yes, if you are working in the Demonstration environment.
MEGA 2009 SP2 Deployment Guide page 42/44

What is the HASP device driver? It is possible to use HASP4 devices on a parallel or USB port as a local license for MEGA or as a locking device for local/network licences. When using such licenses, installation of a HASP4 device driver is necessary so that the device is detected by the system. Installing the HASP4 driver requires local administrator rights on the machine. The latest version of the HASP4 drivers can be downloaded from the web site http://www.aladdin.com. What processes are active when MEGA is running? Process running mgwmapp.exe Comment MEGA Application (shortcut Mega or Administration) in interactive/batch mode

What processes are active when MEGA Advisor is running? Process running mgwmwmu.exe mgwmwas.exe mgwspro.exe mgwmwum.exe Comment MEGA Advisor MEGA Web Access (main process) MEGA Web Access (sub process) MEGA Web Access User manager (when executed manually)

Which programs run on the file server? With WAN/LAN deployment, no programs are executed on the file server. MEGA uses file services only. If this file server also runs a license server, the corresponding service will be installed and running. Server modification is sensitive. Can installation be carried out not installing anything that will modify the server system? Yes. With WAN/LAN deployment, no system components are required on the server. As soon as a workstation is used to install on the server, no system components will be installed on the server. Note that if the file server also has to run a license server, the system will need to be updated. How do I install programs and data in different folders? The 'Server installation' option of Setup.exe allows you to distinguish the site installation folder from the environment installation folder (data). When starting MEGA the following message is displayed: "The version of your client's installation is not the same as the server. Do you want to synchronize your MEGA client and copy all files from the MEGA server?' This message can appear in the case of a WAN deployment or a LAN deployment with local copy of programs. There is a difference between program file versions of the MEGA client and MEGA server (reference). You cannot execute MEGA when these versions are not identical. Respond with 'OK' to the question. Synchronization consists of copying the program files from the MEGA Server (System and Mega_Std folders) to the local folders of the MEGA Client (System and Mega_Std folders). It is not necessary to be an administrator on the workstation to execute this synchronization, but you must be able to update the local directory and files on the client.

MEGA 2009 SP2 Deployment Guide

page 43/44

MEGA License FAQs


How to determine the products programmed on a MEGA license? Execute MEGA with this license. In the MEGA desktop, select 'Help > About MEGA'. In the dialog box that opens, click the 'System information' button.

What is the list of common product/option Codes Appian Process Architect powered by MEGA: APN Lan: LAN MEGA Advisor: ADV MEGA Architecture: ARC MEGA Business Data: DMO MEGA Control & Risk: CRK MEGA Database Designer: DBB MEGA Designer-Development: DEV MEGA Designer-Integration: INT MEGA Exchange-API: API MEGA Exchange-Generation: GEN MEGA IT Planning: ITP MEGA Merise: AAD MEGA Process (BPMN): PMN MEGA Process: PRO MEGA Publisher-Document: DOC MEGA Publisher-Web: WEB MEGA Requirement Tracker: MDS MEGA Simulation: SIM MEGA SolMan: SAP MEGA Studio: MTS MEGA Suite for DoDAF: DOD MEGA Suite for NAF: NAF MEGA Supervisor: SUP MEGA System Blueprint: ITD MEGA Web Access: MWA MEGA Web Editor: MWE Repository Storage (ORACLE) : RSO Repository Storage (SQL Server): RSQ

Other questions For other questions, contact MEGA Support.

MEGA 2009 SP2 Deployment Guide

page 44/44

Das könnte Ihnen auch gefallen