UNIX/Linux Installation Requirements
Before you install, review the following requirements.
|
Type |
Description |
|
|---|---|---|
|
Operating System |
Product version must be compatible with the operating system bit size (64-bit servers on 64-bit operating systems is the only supported combination). AIX Linux for x86_64 Linux for pSeries Kernel-2.6.32 Linux for zSeries Solaris SPARC Solaris x86_64 The ibi™ WebFOCUS® Release Notes maintains a current list of supported operating systems and levels. |
|
|
Disk Space |
Space for installation Space after installation |
Approximately 6G Approximately 3G |
|
IP Ports |
Up to six consecutive IP ports (two in reserve for typical extra features). Additional Java Listeners (postinstallation 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 Common framework plus per agent memory. |
O/S AIX Solaris (SPARC) Solaris (Intel) Linux for x86_64 Linux for pSeries 64b Linux for zSeries 64b |
Per Agent/Common 5 MB/50 MB 19 MB/125 MB 10 MB/72 MB 9 MB/87 MB 27 MB/165 MB 10 MB/93 MB |
|
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 postinstallation 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. |
|
A minimally configured (bare-bones) Linux distribution (such as Alpine and Amazon EC2 t2.micro) may not be a viable run-time platform for the server because of missing utility tools (commands) and libraries. The sheer number of Linux distributions and subconfigurations makes it hard to be exact about the specific issues that might be encountered when trying to use a minimally configured (bare-bones) Linux distribution. However, the issues are typically missing dll errors and tput (missing ncurses) errors at server start-up. Adding the specific missing packages or tools to a distribution will generally allow minimal Linux distributions to be viable for the server and keep a somewhat minimal footprint, but it is the responsibility of the customer to research and resolve such issues.
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 be configured to use it. You may install a commercial Oracle Java JRE, Oracle Java SDK (also known as JDK) or an open-source OpenJDK from one of the vendors listed in Appendix B. Common Windows-Based Java Implementations.
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 will not start unless the applicable minimal level for the platform is used by setting JAVA_HOME/JDK_HOME values.
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 (if available), Oracle Java SDK (also known as JDK, if available), an open-source OpenJDK (from such sites as adoptopenjdk.net or azul.com), or the Java that may have come with the operating system (or available separately from the operating system vendor). The JRE or SDK build version must also match the bit type of the server, which is 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 using the servlet feature, the Java SDK is required for access to the jar command, so an SDK installation is generally preferred over a JRE installation.
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, plus the directory structure may also vary from implementations delivered by the operating system vendor. The server is aware of all of these implementations when it attempts to locate and set up the use of the actual Java JVM DLL (so you can 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 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.
Use explicit variables 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 is 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:
- 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 click 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 and export the CLASSPATH variable to 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 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.