To update a BRIDGE® using an installer, there are two standard update routines available:

• Guided update with a GUI (see Guided Update of the BRIDGE with GUI)
• GUI-less update (see Updating a GUI-less Installation of the BRIDGE)

Preliminary Notes

• Bridge 7 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.
  Otherwise the installer will complain about a license mismatch: "Your current license version '<your old version>' is not valid for upgrading to Bridge version '<target version>'. Please update the license first and run the update installation again."

• As of Bridge 7, the BRIDGE uses Apache 2.4. You can find information on behavior changes on the Apache pages.

  If you have modified the Apache configuration as described on Configuring the Proxy, you may need to apply your changes to the new Apache templates that have been provided with the update. Please refer to the mentioned page for more information.

• The BRIDGE Installer overwrites file server.xml upon updating the Bridge. The old server.xml is copied to server.xml.old. If you changed the server.xml of your BRIDGE installation (to e.g. apply an individual Tomcat configuration), you can re-apply your changes from the copy.
  But please note, that there will be only one copy of server.xml: server.xml.old will get overwritten on every update.
• When updating the BRIDGE, all deployed services (xUML, Node.js, and Java services) will be kept. However, the automatic startup option will be ignored on the very first start-up after the update.