UNIX Installation Requirements

Topics:

Before you install, review the following requirements.

Type

Description

Operating System

Product version must be compatible with operating system bit size (32 on 32, 32 on 64 or 64 on 64).

AIX

HP-UX IA64

Linux for x86

Linux for x86_64

Linux for pSeries Kernel-2.6.18

Linux for zSeries

Solaris SPARC

Solaris x86

The Information Builders Technical Support web site maintains a current list of supported operating systems and levels.

Disk Space

Space for installation

Space after installation

Approximately 2.2 G

Approximately 1.1 G

IP Ports

Up to six consecutive IP ports (two in reserve for typical extra features).

Additional Java Listeners (post install option) require additional ports (beyond basic reserve).

Java

Java JRE or Java SDK (aka JDK) 1.7 or higher

Used for Java-based adapters, server-side graphics, XBRL, or user-written CALLJAVA applications are to be used. For additional information, see JVM Requirements for Java Services (Server Installations Only).

Memory

Common framework plus per agent memory.

O/S

HP-UX

AIX

Solaris (SPARC)

Solaris (Intel)

Linux for x86

Linux for x86_64

Linux for pSeries 64b

Linux for zSeries 64b

Linux for zSeries 32b

Per Agent/Common

1 MB/45 MB

5 MB/50 MB

19 MB/125 MB

10 MB/72 MB

7 MB/59 MB

9 MB/87 MB

27 MB/165 MB

10 MB/93 MB

7.5 MB/72 MB

Web Browser

Needed for using the Web Console.

Microsoft Internet Explorer® 9 or higher.

Microsoft Edge

Mozilla Firefox® 27 or higher.

Google Chrome® 33 or higher.

Apple Safari® 7.0 or higher.

Apple Mobile iOS® v5

Opera 19 or higher.

JVM Requirements for Java Services (Server Installations Only)

If Java-based adapters, server-side graphics, XBRL, or user-written CALLJAVA applications are to be used, a Java Runtime Environment (JRE) JVM must be installed on the machine, and the server must be configured to use it.

The minimum Java JVM release level is 1.7 or higher, due to required internal components of the server. The Java Listener will not start unless the applicable minimal level for the platform is used by setting JAVA_HOME/JDK_HOME values. For platforms where Java 1.6 is the only choice, expect edaprint jar errors on loading the ibi.webfoc.wfapi.IBICreateCGIGif class and expect that server-side graphics will not function.

The following URL has Java EOL and EOSL information:

http://www.oracle.com/technetwork/java/eol-135779.html

You may install a Java JRE or a Java SDK (aka JDK). The JRE or SDK build version must also match the 32-bit or 64-bit bit type of the server. When you install a Java SDK, the JRE component (where the JVM lives) is also included, so either is allowed.

However, if you are using the servlet feature, the Java SDK is required for access to the jar command, so an SDK install is generally preferred over a JRE install.

There are several ways to specify the Java JVM location:

  • For Java JDK, set JDK_HOME (to the install home location) in the environment or server environment start-up file (edaenv.cfg).
  • For Java JRE, set JAVA_HOME (to the install home location) in the environment or server environment configuration file (edaenv.cfg).

If JDK_HOME and JAVA_HOME variables are both declared, the JDK_HOME value will be used.

To change or add a variable in the server environment start up file (EDACONF bin/edaenv.cfg), either edit the file in a text editor before starting the server or:

  1. Start the server (services like Java Listener may fail until configured and the server is restarted).
  2. Open the Web Console and sign in using an administrator ID.
  3. Select Workspace from the main menu.
  4. In the navigation pane, open the Configuration Files and Miscellaneous folders.
  5. Right-click Environment - edaenv.cfg, and click Edit.
  6. Make the desired edit.
  7. Save the file.
  8. Restart the server (changes are not effective until server is restarted).

The format of edaenv.cfg variables is one per line in name=value pairs. Spaces before and after the equal sign are optional. Values with embedded spaces do not have to be enclosed in quotation marks.

To add classes to the JVM class path for customer-written CALLJAVA applications, set and export the CLASSPATH variable to the operating system level before server start-up or use the Web Console to set the Java Listener IBI_CLASSPATH property.

If JVM-based adapters or features are not required, and the JVM environment is not configured, the message Failed to find JVM is normal and can be ignored.

WebFOCUS

Feedback