Installation on UNIX and Linux (Known Issues)

Installing on Linux

On Linux, the RPM installer for Enterprise Developer for Eclipse installs a 64-bit version of Java. When you start the installation, if the 32-bit version of Java is already installed on your Linux machine, you might not be able to install Enterprise Developer. This is a known issue with the Oracle Java installers for Linux which prevents you from installing both the 32-bit and the 64-bit versions of Java on the same machine. To work around this problem:

• Download the 64-bit Java distribution in a compressed .tar format from the Oracle Web site.
• Untar the distribution into a location different from the one used for the 32-bit Java version. For example, untar in /usr/local/java64 and not in /usr/local/java.
• Set JAVA_HOME and LD_LIBRARY_PATH to the 64-bit version of Java so that it is used to install and run Enterprise Developer.

Installing on Ubuntu 10.10 and later

Every version of Ubuntu starting with 10.10 comes with a setting that prevents an application from using ptrace to attach to another process. This prevents the PL/I debugger from attaching to user processes, and therefore debugging fails. To prevent this problem, disable the offending setting as follows before installing Enterprise Developer:

1. Using any text editor, open the /proc/sys/kernel/yama/ptrace_scope file.
2. Set pctrace=0.

For more information, see Debugging applications that run on Ubuntu (ptrace restriction).

Installing on Red Hat 8.x s390

On Red Hat 8.x s390, the RPM non-root install method is not supported due to errors given by cpio. You receive the following messages:

error: unpacking of archive failed on file /usr/lib/.build-id/1b/af99f26c6b4c00ca499a3199a574b73aeb3854;6092b79c: cpio: symlink failed - No such file or directory
error: Micro_Focus_cobol_server-7.0.0.0-100700.s390x: install failed

As a result, the installation in this scenario is incomplete.

Installing while using AFS/Kerberos authentication

If you are using AFS/Kerberos authentication to log onto your Linux system then you need to ensure you have a local user ID which SOA and Enterprise Developer components of the product can use. This user ID must be set up prior to running the installer. When running the installer you need to specify -ESadminID=[User ID] on the command line so it is used by the installer.

License Server

You need to configure the computer hostname to ensure the license server will start properly.

To avoid performance issues, "localhost" and the computer hostname must not both be mapped to IP address 127.0.0.1. You should only map "localhost" to IP address 127.0.0.1.

The following is an example of how to specify these entries correctly in the /etc/hosts file:

127.0.0.1 localhost.localdomain localhost
IP machinelonghostname machineshorthostname

where IP is the unique IP address of the computer in xx.xx.xx.xx format.