Installing as an Upgrade

This release works concurrently with the previous version of Micro Focus Enterprise Developer Unix Components, so you do not need to uninstall it. See the rest of this topic for considerations when installing alongside older releases.

Install the latest version in a different location and set the environment to point to it. To do this, run the Micro Focus Enterprise Developer Unix Components installer with the –installlocation option:

1. Execute the following command:

   ./InstallFile -installlocation="/opt/microfocus/EnterpriseDeveloper"

   Note: You can use variables when specifying an absolute path for –installlocation. For example, the following examples are equivalent:

   -installlocation="/home/myid/installdir"

   -installlocation="$HOME/installdir"

2. Execute cobsetenv to set the environment and point to the new install location:

   . <product-install-dir>/bin/cobsetenv

   Note: cobsetenv is only compatible with POSIX-like shells, such as bash, ksh, or XPG4 sh. It is not compatible with C-shell or pre-XPG4 Bourne shell.

Preserving the Licensing Configuration Alongside Older Releases

The following is required when you use release 10.0 alongside earlier supported releases of this product on the same machine. The licensing configuration file has changed in release 10.0 and you need to ensure that the older releases do not overwrite it as this can result in issue with licensing and auto-start setup.

You can do this in one of the following ways:

• Execute the following after you install release 10.0:

  touch /var/microfocuslicensing/SKIP_SAFENET_INSTALL
  touch /opt/microfocus/licensing/SKIP_AUTOPASS_INSTALL
  

• Alternatively, when installing releases earlier than 10.0, use the following command line options during the installation:

  -skipsafenet -skipautopass

  This skips the license installation step for those releases and preserves the licensing configuration for release 10.0.

Preserving Product Configuration

The following information applies when you are upgrading from releases 8.0, 9.0, and above.

If you install this release to the same install location as release 8.0 or above, the product in the current location is moved to a backup directory name.

For example, if the 7.0 product is installed in the default install location, /opt/microfocus/EnterpriseDeveloper, during the installation process it is moved to /opt/microfocus/EnterpriseDeveloper.BKP.YYYY-MM-DD.HH:MM:SS. The new release will be installed in /opt/microfocus/EnterpriseDeveloper. The backup location will store your original installation along with any files you deployed to that directory. It will also contain any configuration files you modified post-install.

When installing 9.0 and above the installer moves a number of specific configuration files to a different configuration location and symbolically links them back to the new release install location. The configuration location will be one of the following:

• The default config location is /opt/microfocus/config/.
• For non-root installation, the default location is $HOME/microfocus/config/.
• To specify your own configuration location, run the setup file with the following command-line option: -mfconfiglocation=[location]

The setup file creates a directory in the configuration location using a 5-digit checksum of the $COBDIR path. This is so that each configuration location is unique to each product installation. The configuration files and directories are then placed in this COBDIR checksum directory. In the following example, the install location generates a checksum of 39082.

The file /opt/microfocus/config/39082/COBDIRlocation.txt details the COBDIR the configuration area is associated with.

If you have changed any other files in the original installation, you need to be copy these manually from the backup directory, /opt/microfocus/EnterpriseDeveloper.BKP.YYYY-MM-DD.HH:MM:SS, into the install location after the upgrade installation is complete.

You can access the configuration area from $COBDIR/etc/config.

Currently, the setup file only moves the following files and directories, where applicable: