Updates to both the Essential Widgets and to Essential Viewer are now available for download from the Downloads page. These updates are also both included in a new release of Essential Architecture Manager (version 1.0.1).

Essential Widgets Update

Essential Widgets 2.1 fixes the AutoText widget bug found when running with the final release of Protege 3.4. Thanks to the Protege Team for their help with resolving this issue.

Upgrading to Protege 3.4 from RC1

Essential Architecture Manager is now fully compatible with the final release of Protege 3.4 (Build 533).

Users who wish to upgrade their Protege installation to version 3.4 should install this along-side Protege 3.4 RC1 (or earlier versions).

Essential Viewer Update

Essential Viewer 2.0.1 delivers small bug fixes to several of the reports. This update replaces the previous essential_viewer web application and is recommended for use with the new sample repository.

New Release of Essential Architecture Manager

A new version of Essential Architecture Manager - version 1.0.1 - which contains both of these updates plus the baseline repository is also now available for download.

This release is fully compatible with Protege 3.4 (Build 533).Essential Architecture Manager and Protege 3.4

Essential Architecture Manager and Protege 3.4

Recommended platform for Essential Architecture Manager

Protege 3.4 will now become the recommended platform for Essential Architecture Manager and the platform for future developments of the Essential Project. The Essential Project will continue to provide support for existing installations of Essential Architecture Manager using Protege 3.3.1.

Please note, however, that the Protege Team now no longer support Protege 3.3.1.

Upgrading to Protege 3.4 from 3.3.1

Users who wish to move to Protege 3.4 from Protege 3.3.1 should note that they should not attempt to install version 3.4 onto the existing version 3.3.1 installation. Rather, Protege 3.4 should be installed along-side any existing versions.

Impacts to Essential Architecture Manager

For new installations and stand-alone installations, there is no impact. Simply install Protege 3.4,  deploy the Essential Widgets to the plugins directory of the new Protege installation and continue to work with your existing repositories. Having completed the installation of Protege 3.4 , users should start Protege and then go to the File->Preferences menu item and un-select the option to sort the class browser items.

Migrating Multi-User Essential Architecture Manager deployments

Users who have completed a multi-user installation that is using a database to store the repository using Protege 3.3.1 need to do the following to migrate the repository to Protege 3.4.

The underlying database structure has changed in Protege 3.4, so the following steps must be followed to migrate the repository to use in Protege 3.4.

• In Protege 3.3.1, open your Essential Architecture Manager repository project.
• From the File menu, select the option to Convert the project to an alternative format. Select the Protege files (PPRJ, PINS, PONT)
• Save this project to a new file on your file system and close Protege 3.3.1
• Open this new project file in Protege 3.4
• Follow the steps in the admin article to convert this project back to the database format.

Protege 3.4 Full (Build 533) Release Notes

For more information about the new full release of Protege 3.4 (Build 533), please see the Protege 3.4 Full Release Notes.

Contact

For more information about using Protege 3.4 with the Essential Project tools, please contact the Essential Project Team via the forums.