Backward Compatibility of AWM Models

AWM model format

The AWM model format in Enterprise Developer 2.3 has changed significantly since earlier versions of Enterprise Developer. This change was made to introduce some new AWM function packages and has the following effect:

• AWM models created with Enterprise Developer 2.3 or later are not supported in earlier versions of Enterprise Developer.
• AWM models created with earlier versions of Enterprise Developer are supported in Enterprise Developer 2.3 or later. When loading such models in the newer versions of Enterprise Developer, they are automatically converted to the new format introduced in the 2.3 release.
• Micro Focus recommends that you create a back-up of models created with an earlier version of Enterprise Developer before you open them in Enterprise Developer 2.3 or later for editing.

  When you open older models in the editor in version 2.3 or later, you receive a warning that the model is outdated and will be converted to the new format. If you change the model and save it in Enterprise Developer 2.3 or later, that model is no longer supported under earlier versions of Enterprise Developer.

Component name changes

A number of AWM components have been renamed in Enterprise Developer 2.3 or later to make them compliant with the Micro Focus standards. This affects almost all IDs that contain "de.soforte" or "de.soforte.taurus": they have been renamed to "com.microfocus" and "com.microfocus.awm" respectively.

This change affects the following components:

The .options file within the Eclipse installation folder:

References to "soforte.taurus" have been changed to "microfocus.awm" in the .options file in the Eclipse installation folder for Enterprise Developer 2.3 and later.

Issue:

The .options file is not updated automatically when installing Enterprise Developer 2.3 or later as an upgrade.

Resolution:

To ensure the file is updated, manually delete the eclipse folder in %Public%\Micro Focus\Enterprise Developer before you start installing Enterprise Developer 2.3 or later.

If you use a local master configuration file, you need to create a back-up of it before deleting the eclipse folder. After installing Enterprise Developer 2.3 or later, move the backed-up copy of the file into the new eclipse folder that the 2.3 installation has created in the location specified above.

Existing workspaces:

Issue:

The IDs of the Team Developer (TD) perspective and the views associated with it have changed. As a result, after you upgrade to Enterprise Developer 2.3, old workspaces which used the TD perspective do not work properly.

Resolution:

You must use a new and clean workspace.

Existing DCTL members:

Issue:

Old DCTL members that were used to generate a model for ISPF dialogs from an XML control data set member are no longer supported.

Resolution:

Change the references in the headers of the DCTL members from "www.soforte.com" to "www.microfocus.com". For example:

<tau:dialogAppls xmlns:tau="https://www.microfocus.com/controlFile/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://www.microfocus.com/controlFile/ bundleentry://824.fwk24010558/XSD/controlFile.xsd ">

Plug-ins:

Issue:

As a result of the component name change, plug-ins developed using the AWM API in earlier versions of Enterprise Developer do not work in 2.3.

Resolution:

You need to update any existing plug-ins. To do this, you need to change the strings "de.soforte" and "de.soforte.taurus" to "com.microfocus" and "com.microfocus.awm" respectively, in the following components:

• The plug-in projects
• Any Java packages
• Any extension point IDs
• The AWM model name space

The following steps guide you through the process of updating any AWM plug-ins created with a version of Enterprise Developerearlier than 2.3:

1. Start Enterprise Developer 2.3 and open the Plug-in Development perspective.
2. Select all plug-in projects for AWM in the Package Explorer View.
3. Click Search > File.
4. Specify the following details in the Search dialog box:
   • Type de.soforte.taurus in Containing text.
   • Type MANIFEST.MF,plugin.xml in File name patterns.
   • Click Selected resources under Scope

   

5. Click Replace.
6. In the Replace Text Matches dialog box, specify the following string in the With field: com.microfocus.awm:

   

7. Repeat steps 1-5 to replace de.soforte with com.microfocus.
8. Check whether any Java classes in your projects include references to "de.soforte.taurus" or "de.soforte". To replace such references, repeat the steps above but specify “*” in the File name pattern field in the Search dialog box.
9. Ensure that all plug-in projects for AWM are still selected in the Package Explorer view.
10. Right-click one of the projects and click Source > Organize Imports.
11. Click Project > Clean and choose to clean all projects.

    By default, Eclipse rebuilds the projects. There should be no build errors caused by name conflicts.