The following components are required to install Essential Architecture Manager.

• Protege. This is the core modelling tool platform for Essential AM. The "Full Protege" package is recommended.
  
• Essential Widgets. A set of extension components from the Essential Project that are plugged into Protege. These include:
  • AutoTextWidget
    
  • ReportTabWidget (Essential Architecture Reporting tab)
    
• Apache Tomcat or your favourite Java Web Application Server. The application server environment for running the Essential Viewer software.
• Essential Viewer
  
• Essential Meta Model. The core meta model and base repository for Essential Architecture Manager.

Having downloaded the essentialinstall.jar file from the Download section, please check that you have the software pre-requisites available.

Before starting the install of Essential Architecture Manager, confirm whether or not a JVM has been installed. From a command prompt, type:

java -version

The resulting message from Java should show a JVM version at or above version 1.5.x. If a JVM is already present that meets the required version, there is no need to install the JVM that is provided with Protege.

If you do not already have a Java Runtime Environment installed, please download and install the correct JRE/JVM for your platform.

If you have not already installed Protege, install it by running the installation program.

The following steps should be followed to install Protege on a Microsoft Windows Platform.

• Run the install_protege.exe file.
  
• Select the option to install "Everything" as this will include the optional tab widgets that may prove useful at a later date, e.g. Prompt, Jambalaya.
• Select the installation folder, preferably take the default in Program Files\Protege_x.x.x
• Select the JVM that Protege should use. If from Step 3, a suitable JVM (version 1.5 or above) has already been installed, select that JVM.
  • Select either from the list show or find the version discovered in Step 3 using the "Choose Another" button. This may require investigation of the Java Control Panel in the Windows Control Panel. NOTE: You must select the specific java.exe file to use.
• Select 'Next' until the installation completes.

Run the Protege installer for your platform and follow these steps:

• Select the option to install "Everything" as this will include the optional tab widgets that may prove useful at a later date, e.g. Prompt, Jambalaya.
• Select the installation folder, preferably take the default
  
• Select the JVM that Protege should use. If from Step 3, a suitable JVM (version 1.5 or above) has already been installed (this will be the case on Mac OS X), select that JVM.
  • Select either from the list shown or find the version discovered in Step 3 using the "Choose Another" button.
• NOTE: You must select the specific java.exe file to use.
• Select 'Next' until the installation completes.

3.3 Configure Protege

Please open Protege now.

• Go to the 'File' menu and select 'Preferences'.
• Un-select the option 'Sort class tree (Classes Tab)' to ensure that the Essential Meta Model class hierarchy is shown in the correct order.
• Click OK and exit Protege.

This configuration is not required in Protege 3.3.1 and the preference is not available

If you do not already have Tomcat (or an alternative Java Application Server that can run Java Servlets) installed, please install it by running the installation program for your platform.

Like Protege, Tomcat requires Java v1.5 or above. For simplicity, select the same JVM that was selected Essential Architecture Manager Installation Guide during the Protege installation. In this case when prompted by the Tomcat installer, select the path to the folder "jre".

Having installed the pre-requisites, run the Essential Architecture Manager installer, which will guide you through the rest of the installation process. The following sections in this guide provide additional detail about the options for the installer and the questions that it will ask.

To run the installer:

Double click on the Essential Install JAR File.

If, for some reason the installer is not recognised as an executable JAR file, use the following command at command prompt/terminal window:

java -jar essentialinstall.jar

You will now see the welcome panel of the installer and will be guided through the install process.

The Information Panel provides important information about the installation and pre-requisites. Please read these before proceeding to the license agreement.

The Essential Architecture Manager installer is divided into packages, enabling the installer to be used for installation possibilities.

For standalone installations, the 'Server' pack is optional but you can select all the install packages.

Essential Architecture Manager includes plugins that must be installed into your Protege and Apache Tomcat (or alternative Java Web Application Server) installations.

The installer will ask you to specify the location of both your Protege and Apache Tomcat (or alternative Java Web Application Server). An attempt to automatically find Protege and Apache Tomcat in typical installation locations will be made. If the installer cannot find your Protege and Apache Tomcat installations, please use the 'Browse...' button to specify the folders in which they are installed.

When you select an location for either Protege, the installer will verify that location to ensure that you have selected a valid folder. Select the correct deployment location for Essential Viewer in your Web Application Server installation. For Apache Tomcat, select <Tomcat Install>/webapps. For other Java Web Application Servers, please refer to your supplier's documentation for Web Application deployment to find the correct location for deploying the Essential Viewer WAR file.

Both the meta-model and the model for Essential Architecture Manager are contained in the repository which is controlled from a Protege project file, and has the file extension, .pprj

Next, specify to the target location of your empty Essential Architecture Manager Repository. The installer will create a directory to hold the meta-model and model configuration files in the folder that you specify. In stand-alone mode, we recommend using the file-based datastore for the repository. This directory will also contain the data files for the model and meta-model, e.g.

/EssentialAM/Repository

Even though this is a stand-alone installation, to aid future migrations to a server-based multi-user installation, you can choose to install the Server components of the installation.

If you are installing to a fresh installation of Protege, select the default option to install the server configuration directly into the Protege environment.

However, if you are installing Essential Architecture Manager to a machine that already has Protege installed and running as a server in a multi-user environment, you should select an alternative location at this step of the installion, e.g. your Essential Repository location, to avoid the existing server configuration being over-written.

The installer will now install all the components of Essential Architecture Manager to the locations that you have specified in the above steps.

When the installation has completed successfully, you can create an automated installer to repeat this installation configuration, e.g. to install another verbatim copy on another machine. Select the 'Generate an automated installation script' option and specify the name and location of your automated install script.

See the Automated Installer article for how to use this installation script.