In order to migrate to Bridge 7, find below a summary of all migration issues you need to keep in mind.

Software Versions

MagicDraw Version

E2E BUILDER 7 is designed for MagicDraw UML 18.0. If you need to migrate BUILDER projects from older MagicDraw versions, refer to Migrating Builder Projects to MagicDraw 18.

E2E Software

BRIDGE 7 contains many new features and improvements that lead to dependencies between Builder, Analyzer and Bridge versions. Please make sure that you update all components to version 7. You cannot e.g. deploy services that have been compiled with BRIDGE 7 to an older E2E Bridge.

Update all software components to BRIDGE 7, BRIDGE first, then BUILDER and ANALYZER.

Apache

With BRIDGE 7 we updated Apache to version 2.4. Refer to the Apache pages for more information on behavior changes. If you have changed the proxy templates of your BRIDGE installation, you will need to merge your modifications with the new templates provided with BRIDGE 7.

If you have modified the proxy templates as described on Configuring the Proxy,  your proxy template modifications will be kept after a BRIDGE update. The system templates (folder <your Bridge data directory>/proxies/system_templates), however, will be updated to the new Apache version.
Your changes may not fulfill the needs of Apache 2.4, and you may need to re-apply your changes to the new templates. In this case, copy the newly provided templates from folder system_templates to folder templates and merge your changes to the new template.

Java

In order to run the BRIDGE installer, you need  a specific Java version: since Bridge 7.2.0 use Java version 11 or newer.

BRIDGE License

To use BRIDGE 7, you need a new BRIDGE license - please contact us at info@e2ebridge.com for more information.
The BRIDGE installer will check your Bridge license. When updating a BRIDGE to a new version (e.g. BRIDGE 6 to BRIDGE 7), you need to apply the new license before updating the system.

Service Repositories

Services that have been compiled with E2E BUILDER 7 can only be run on an E2E BRIDGE 7. On the other side, all old repositories of BRIDGE 5.1 and BRIDGE 6.0 that have been compiled with older compilers, will still run on BRIDGE 7.

Compiler

Old Component Diagrams

With introduction of BRIDGE 6 in 2013, we deprecated the old component and deployment diagram and replaced them by a new, simplified component diagram:

As of BRIDGE 7, we removed the support for the old component and deployment diagram from the E2E Compiler - only models with the new component diagram will compile. Before compiling such a model with E2E Compiler 7, you need to replace the old component and deployment diagrams by the simplified ones as described on The Components Wizard. If your service contains more than one deployment, please refer to Defining More Than One Deployment.

Local Variable Re-declaration

As of Builder 6.0.29 / 7.2.0, the Compiler reports an error, if a local variable is re-declared within Action Script. You will need to change your implementation, if the Compiler points you to a implementation like this.

Refer to Compiler Reports Error: Local variable is re-declared for more information.

Node.js

With BRIDGE 7, we updated the integrated Node.js to version 8 (Carbon, 8.9.1 ). If you are running own Node.js services, please make sure that they are Node.js 8 compatible.

REST

With BRIDGE 7, we introduced a new option jsonCompact on the <<RESTAlias>> and <<REST service>> components (see REST Service Reference and REST Adapter Reference). With this option, you can control the generation of JSON: pretty or compact.

If you compile a service using REST with a BRIDGE 7 compiler, this option defaults to true (= compact JSON). This is in contrast to BRIDGE 6, where pretty JSON was generated in absence of this option. Set this option to false, if you need pretty JSON to be generated.