Installation > Installation for Windows > Windows Installation Requirements

Windows Installation Requirements

Topics:

JVM Requirements for Java Services (Server Installations Only)

Before you install, review the following requirements.

Type	Description
Operating System	Windows 7 or higher or Windows Server 2003 or higher. Product version must be compatible with operating system bit size (32 on 32, 32 on 64 or 64 on 64). The Information Builders Technical Support web site maintains a current list of supported operating systems and levels.
Disk Space	Approximately 1.5G (plus additional space during installation). Integrated Hyperstage releases use approximately 3G of disk space.
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	The memory requirements for installation and operation of the server are: General memory: 30Mb. (This includes memory used by the primary one-per-server-instance processes such as Workspace Manager, the print log, Deferred Listener, HTTP Listener, and TCP Listener.) Memory per active agent: 3.5Mb. These numbers apply when the server is in an idle state, so they may fluctuate slightly.
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 properly (and will show errors in edaprint) if 1.7 (or higher) is not in use.

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 using the servlet feature, the Java SDK is required for access to the jar command, so a SDK install is generally preferred over a JRE install.

New to 7707 and higher server release levels is an automatic Windows Registry look-up feature of the latest highest Java available on the system. This feature simply requires that an appropriate 1.7 or higher Java JRE or SDK of the correct bit size has been installed on the system using the standard Oracle Java Installer, which registers the installation to the Windows Registry (and that no explicit variables are set on the system that would cause an override). If a JRE and SDK are both installed, the SDK will be used. The automatic look-up feature does not apply to a Java JRE or SDK that has simply been dumped to disk as this does not register the install (if this is the case, use explicit variables to configure the server).

Explicit JAVA_HOME or JDK_HOME variables may be setup to manually configure Java access (to override locations found by the automatic Java look-up feature or because an unregistered Java is in use) as described below.

At server start-up time, if none of the above is true, the server Java Listener may still start if applicable JVM directories happen to be on the system PATH, but this not a recommended method as it is not explicit.

If an appropriate JVM is not found at server start-up time, various failed to find JVM messages will be displayed in EDAPRINT. Reviewing and following the instructions in this section will usually correct the problem.

JSCOM3 is the actual process name for the Java Services Listener and the terms are often used interchangeably.

To use explicit variables to specify the Java JVM location, do the following:

For Java SDK set JDK_HOME (to the Java SDK install home location) in system wide environment or server environment start up file (edaenv.cfg).
For Java JRE set JAVA_HOME (to the Java JRE install home location) in system wide environment or server environment configuration file (edaenv.cfg).

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 (a start menu icon is also available under the configure folder) or:

Start the server (services like Java Listener may fail until configured and the server is restarted).
Open the Web Console and sign in using an administrator ID.
Select Workspace from the main menu.
In the navigation pane, open the Configuration Files and Miscellaneous folders.
Right-click Environment - edaenv.cfg and select Edit.
Make the desired edit.
Save the file.
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 the CLASSPATH variable at the operating system level before server start-up or use the Web Console to set the Java Listener IBI_CLASSPATH property.

If Java JVM-based adapters or features are not required, and no Java is installed (or is 1.6 or lower), the various EDAPRINT Java Listener fail messages are normal and can be ignored. However, this not recommended as a support calls may unintentionally center on this unless they are also told that it is intentional.

	WebFOCUS

Feedback