Micro Focus Visual COBOL 2.3 for Eclipse (Windows) > Welcome > Product Information > Installing Micro Focus Visual COBOL Development Hub > Installing Visual COBOL Development Hub > Installing

Installing

Note:

During the installation process, the installer configures the product's Enterprise Server System Administrator Process User ID. The Process User ID will be the owner of all Enterprise Server processes except the one for the Micro Focus Directory Server (MFDS). The Directory Server process (Enterprise Server Administration) runs as root as this allows it to access the system files and ports.

All Enterprise Server processes you start from Enterprise Server Administration run under the Process User ID which can affects the file access and creation.

By default, the installer uses the login id of the user that runs the installer for the Process User ID. To change the user id after you complete the installation, execute $COBDIR/bin/casperm.sh.

These are the steps to install this product:

Give execute permissions to the setup file:

chmod +x setup_visualcobol_devhub_2.3_platform

Run the installer with superuser permissions:
```
./setup_visualcobol_devhub_2.3_platform
```
If you don't run this as superuser you will be prompted to enter the superuser password during the installation.

The COBOL environment is installed by default into /opt/microfocus/VisualCOBOL, (COBDIR).

To install in a different location use the -installlocation="Location" parameter to specify an alternative directory location. For example:
```
./setup_visualcobol_devhub_2.3_platform -installlocation="full path of new location"
```
Note: You can use variables or the tilde syntax for the path for –installlocation. For example, the following examples are equivalent:
```
-installlocation="/home/myid/installdir"
```
```
-installlocation="~myid/installdir"
```
```
-installlocation="~/installdir"
```
```
-installlocation="$HOME/installdir"
```
You can see details about which additional parameters can be passed to the install script if you enter the -help option.

You can use the following options to configure the Enterprise Server installation: [ -ESsysLog="location" ] [ -ESadminID="User ID" ] [ -CASrtDir="location" ], where:

-ESsysLog

Specifies a location in which the build will create the Enterprise Server System log file - for example, -ESsysLog="/home/esuser/logs". The default location is /var/mfcobol/logs.

-ESadminID

Sets the Enterprise Server System Administrator Process User ID from the command line - for example, -EDadminID="esadm". The default user ID is the one that runs the installer.

-CASrtDir

Specifies the location were the Enterprise Server run-time system files are placed - for example, -CASrtDir="/home/esuser/casrt/es". The default location is /var/mfcobol/es.
Note:
- The installation of this product could affect the SafeNet Sentinel licensed components running on your machine. During installation licensing is shutdown to allow files to be updated. To ensure the processes running on your machine are not affected, you need to use the -skipsafenet option, which skips the installation of SafeNet:
```
./setup_visualcobol_devhub_2.3_platform -skipsafenet
```
- To protect the SafeNet Sentinel installation from accidental updating you can create an empty file named SKIP_SAFENET_INSTALL in /var/microfocuslicensing/ as follows:
```
touch /var/microfocuslicensing/SKIP_SAFENET_INSTALL
```
  While the file is present, the SafeNet installer does not make changes to the installation or shutdown the running license daemons. If licensing needs to be updated later, remove the file and install Sentinel RMS server manually.

To set up your product, execute:

. /opt/microfocus/VisualCOBOL/bin/cobsetenv

To verify that your product is installed, execute:
```
cob -V
```

Important: These commands set the environment only for the current shell. You need to execute them for each new shell that you start.

To avoid having to run cobsetenv for every shell, add these commands to the shell initialization files (such as etc/profile, etc/bashrc).

Note that 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.

Note: For information about the Micro Focus Visual COBOL Development Hub, check the help for Visual COBOL for Eclipse that is available online on the Micro Focus Infocenter.