Windows Installation Requirements

Before you install, review the following requirements.

Type	Description
Operating System	Windows 10 or Windows Server 2012 or higher. The server is a 64-bit product, which must be installed on a 64-bit operating system. The ibi™ WebFOCUS® Release Notes maintains a current list of supported operating systems and levels.
Disk Space	Approximately 5.5G.(plus additional space during installation)
IP Ports	Up to six consecutive IP ports (two in reserve for typical extra features). Additional Java Listeners (post-installation option) require additional ports (beyond basic reserve).
Java	Java JRE or Java SDK (also known as JDK) 8 or higher Used for Java-based adapters, server-side graphics, XBRL, or user-written CALLJAVA applications. For additional information, see JVM Requirements for Java Services (Server Installations Only). Note: Java 8 and Java 11 are explicitly tested and certified to be compatible with the WebFOCUS Reporting Server. Other Java releases may be compatible with the WebFOCUS Reporting Server. If you use an untested Java release, you must self-certify its compatibility with the WebFOCUS Reporting Server and accept responsibility for using an untested release.
Memory	The memory requirements for installation and operation of the server are: General memory: 30 Mb. (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.5 Mb. These numbers apply when the server is in an idle state, so they may fluctuate slightly.
Web Browser	Needed for using the WebFOCUS Reporting Server browser interface. Microsoft Edge Mozilla Firefox® 59 or higher. Google Chrome® 65 or higher.
Node.js Caching	The Node.js Caching feature enables WebFOCUS Reporting Server independent caching, which allows external access to WebFOCUS Reporting Server In-Document Analytics outputs. This feature is normally configured automatically at server installation time, if Node Package Manager (npm) and Node.js are detected during the installation. This may be configured post-installation if not detected, failed during installation, or for older configurations that had software upgraded to Release 8207.28 or higher. For information on npm and Node.js installation requirements and post-configuration instructions for adding the Node.js Caching feature to a qualifying existing configuration, or correcting the configuration, see Appendix A. Caching Support for Node.js.

JVM Requirements for Java Services (Server Installations Only)

Many modern data adapters, server-side graphics, and other services use a Java JVM to implement execution. These require a Java JVM to be installed (separate from the server) and that the server is configured to use it.

The minimum Java JVM release level is 8 or higher, due to required internal components of the server. As already noted, only Java release 8 and release 11 are explicitly tested, and use of any other release must be self-certified by the customer if they choose not to use release 8 or release 11. The Java Listener do not start properly (and will show errors in edaprint) if 8 (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 commercial Oracle Java JRE, Oracle Java SDK (also known as JDK), or an open-source OpenJDK (from such sites as adoptopenjdk.net or azul.com). The JRE or SDK build version must be 64-bit. When you install a Java SDK, the JRE component (where the JVM is installed) is also included, so either is allowed. However, if you are using the servlet feature, a Java SDK (JDK) is required for access to the jar command, so an SDK (JDK) installation is generally preferred over a JRE installation.

An automatic Windows Registry look-up feature for the latest highest commercial Oracle Java is available on the system. This feature only requires that an appropriate 8 or higher commercial Oracle Java JRE or SDK of the correct bit size has been installed on the system, using the standard commercial Oracle Java Installer, which registers the installation to the Windows Registry. In addition, it requires that no explicit variables be set on the system that would cause an override. If a commercial Oracle JRE and SDK are both installed (and no override variables are set), the SDK is used.

The automatic look-up feature also applies to select third-party Java vendors as listed in Appendix B. Common Windows-Based Java Implementations and when the third-party Java is installed as described in Appendix B. Common Windows-Based Java Implementations. Installing one of these third-party Java implementations, as described, sets up registry keys like commercial Oracle Java, so the JDK is automatically found, as it is with a real commercial Oracle Java installation.

The automatic look-up feature does not apply to a commercial Oracle Java JRE or SDK that has simply been copied to disk using an archive tool such as WinZip or 7zip, as this method does not register the installation. If this has been done, use explicit variables to configure the server.

The automatic look-up feature also does not apply to Oracle OpenJDK https://openjdk.java.net/, as its standard installation method is to unzip (copy) to disk, and the installation is not registered.

This automatic look-up feature also does not apply to any other Java download site providing a Java installer that does not register its location, or registers it differently from a commercial Oracle Java installation (such as Azul OpenJDK https://www.azul.com/).

Explicit JAVA_HOME or JDK_HOME variables, described below, may be used to manually configure Java access (to override locations found by the automatic Java look-up feature or because an unregistered Java is in use). While OpenJDK uses a different directory organization from the Oracle JDK and JRE, the Azul OpenJDK directory structure is more like the Oracle JDK and JRE. The server is aware of both implementations when it attempts to locate and set up use of the actual Java JVM DLL (so you should use JAVA_HOME= or JDK_HOME= to point at the desired implementation).

Some third-party Java JDK/JRE providers, such as Adpotopenjdk.com, provide not only classic JDK and JRE implementations (also known as Hotspot), but also Eclipse OpenJ9 Java virtual machine (JVM) implementations. While the server Java Listener starts with either implementation, it has been found that some third-party JDBC DBMS drivers do not work with some Adpotopenjdk.com Open9J implementations (Vertica and Snowflake JDBC Drivers, in particular, on Windows). If your site chooses to use an Open9J implementation or other third-party JVM provider and experiences JDBC DBMS problems, a classic Java (Hotspot) implementation from Oracle or Adpotopenjdk.com should be installed and tested to confirm that the server software and DBMS setup are not at issue (and to correct, if needed). If the Open9J implementation is still desired, the site should follow up with the Open9J JVM or DBMS provider as to why this combination fails.

Installation of any third-party Java JVM that follows the same directory structure as any of the known implementations should work, but use of such alternate packages should be self-certified.

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 is 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 display in EDAPRINT. Reviewing and following the instructions in this section usually correct the problem.

JSCOM3 is the actual process name for the Java Services Listener and those terms, as well as the term Java Listener, 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 the environment or server environment start-up file (edaenv.cfg).
For Java JRE, set JAVA_HOME (to the Java JRE install home location) in the 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 WebFOCUS Reporting Server browser interface 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 the 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 WebFOCUS Reporting Server browser interface 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 below the minimum level), various EDAPRINT Java Listener fail messages are normal, acceptable, and can be ignored. However, this is not a recommended situation. If you make a support call, make the representative aware of this, as it may take them unnecessary time to analyze the situation and realize that these messages are normal for your configuration and not part of the problem being called in.

Did you find this helpful?

Yes No