The System Administrators have exclusive access to install and manage ESAM utilities, which can then be used to administer the health of ESAM. These utilities ensure that ESAM services are accessible during the OpenEdge runtime and provide continuity of service to OpenEdge operations. System Administrators can fix errors related to the OpenEdge installation and registration of the OpenEdge root install path <DLC> with ESAM by checking the details of the installation events that are streamed to different log files at different stages of the installation process.

Review OpenEdge installer status

During the OpenEdge installation, a log file is automatically generated. The log file captures the install status of all the supported files, applications, and OpenEdge components. The final status of the ESAM installation is also recorded in the OpenEdge installation log file.

On Windows, the OpenEdge installation log file named oesetup.log, is created in the C:\Windows directory.

For more information on the OpenEdge installation log file created in Windows, see Run the silent installation on Windows platforms.

On UNIX, the OpenEdge installation log file named install.log, is created in the installer’s home directory.

For more information on the OpenEdge installation log file created in UNIX, see Run the silent installation on UNIX or Linux Machines.

Review ESAM installer status

The ESAM installer runs in silent mode automatically at the beginning of an OpenEdge installation. When the OpenEdge installer invokes the ESAM installer, the status of all the events associated with the ESAM installation is recorded in the ESAM installer log file named ESAM_Install_dd_mm_yyyy_hh_mm_ss.log. This log file also includes details about all the files and subdirectories created in the ESAM directory path.

On Windows, the ESAM install log file is created in the C:\Windows\System32\openedge.d\audit directory. On UNIX, it is created in the /etc/openedge.d/audit directory.

Repair ESAM installation

If an ESAM installation fails, a System Administrator can check the ESAM install log file ESAM_Install_dd_mm_yyyy_hh_mm_ss.log to know more about the reason for failure. After the reason for the ESAM installation failure has been identified and fixed, the administrator needs to run the ESAM installer manually, to resolve the previous failure.
Note: The location of the ESAM installer is in the <absolute-path-to- DLC>\install directory.

On Windows, run the ESAM installer by running the following script: 

InstallESAM.bat

On UNIX, run the ESAM installer by running the following script: 

InstallESAM

Review OpenEdge root install path registration status

The details of the OpenEdge root install path <DLC> registration process during the OpenEdge installation are captured in the esam.log file. This log file is created in the <DLC>\Install directory. The OpenEdge root install path <DLC> should be registered with ESAM after the OpenEdge installation finishes. A post-install tailoring process attempts to register the new <DLC> path in the ESAM registry, which the installation can rely upon at runtime as a trusted path.

Restore OpenEdge root install path registration

It is possible for the ESAM installation to succeed while the registration of OpenEdge root install path <DLC>with ESAM fails. If this happens, you can check the esam.log file to know more about the reason for failure.

After the issue is resolved, a System Administrator can run a setdlc script in the sbin sub- directory of ESAM directory path to manually invoke the <DLC> registration process with ESAM.

On Windows, run the following script to start the OpenEdge root install path <DLC> registration process with ESAM: 
setdlc.bat -esamregisterDLC <absolute-path-to-DLC>
On UNIX, run the following script to start the OpenEdge root install path <DLC> registration process with ESAM: 
setdlc -esamregisterDLC <absolute-path-to-DLC>
Note: After OpenEdge is installed, various runtime issues, such as an OpenEdge component failing to validate the OpenEdge root install path <DLC> , are recorded in the oesec.log file. The oesec.log file is a protected audit log file that keeps track of administrative activities and other security issues. For more information on OpenEdge runtime issues, see Troubleshoot OpenEdge runtime service failures.