Micro Focus recommends that you install this product with superuser permissions. If, however, you need to perform a non-root installation, check the information below. The setup file supports installing into non-root owned directories.
By default, most user account areas can only be accessed by the owner. In order for all of the users to be able to use the product and License Manager, the installation must be in an account whose $HOME directory all other users on the machine can access.
chmod +x
-noroot
This installs the product in the default location, $HOME/microfocus/EnterpriseDeveloper, where $HOME should point to the top-level login directory for the current user.
The product configuration files are stored in $HOME/microfocus/config, and the CAS regions are stored in $HOME/microfocus/es, by default.
Once the installation is complete, you need to run the cobsetenv script in order to set up your COBOL environment. To do this, execute the following command:
. $HOME/microfocus/VisualCOBOL/cobsetenv
. $HOME/microfocus/EnterpriseDeveloper/cobsetenv
If you use any custom environment-setting scripts, you need to add the MFCES_INIT_LOCATION environment variable to them as follows:
MFCES_INIT_LOCATION=$HOME/microfocus/licensing/ces/bin/ces.ini export MFCES_INIT_LOCATION
This provides the location of the ces.ini licensing configuration file in the non-root installation area for the COBOL Run-Time System.
The /etc/services file for the registration of port 86 is owned by the root user and cannot be changed without superuser permissions.
You need to ensure that this file includes the mfcobol port entries. On most new operating systems, the entries are present.
However, on some operating systems these port entries might be missing. The setup file reports this issue before installing the product. To resolve it, you need to edit /etc/services manually in a text editor with root permissions and add the following two lines:
mfcobol 86/tcp # Micro Focus Cobol mfcobol 86/udp # Micro Focus Cobol
Specify -ESadminID="username", if you want to use the SOA functionality.
For non-default installation locations for the product and the product configuration files, use the -installlocation, - mfconfiglocation, and -CASrtDIR command line arguments. See Install Options for details.