Installation Requirements for PDS

The server runs on any supported release of z/OS. For current information about supported releases, see the ibi™ WebFOCUS® Release Notes.

In general, the operating system should have the latest cumulative patch levels applied. Confirm that your server installation software is labeled for your operating system level.

JVM Requirements for Java Services

If JVM-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 JVM release level is (Undefined variable: productvar.jvmVersion) or higher, due to the required internal components of the server. As already noted, (Undefined variable: productvar.jvmVersion) and Java 11 is explicitly tested, and use of any other release must be self-certified by the customer if they choose to not use (Undefined variable: productvar.jvmVersion) or Java 11. The Java Listener does not start unless (Undefined variable: productvar.jvmVersion) (or higher) is in use. The following URL has Java EOL and EOSL information: http://www.oracle.com/technetwork/java/eol-135779.html

Installing maintenance updates to the EDAHOME of an existing server running releases prior to production 7.7.05 also have the requirement of moving up all dependent configurations to use (Undefined variable: productvar.jvmVersion) (as instructed in this section).

You may install a Java JRE or a Java SDK. When you install a Java SDK, the JRE component (where the JVM is installed) is included, so either is allowed. If using servlet, the Java SDK is required for the jar command, so it is generally preferred over the Java JRE. The SDK or JRE build type must also match the bit size of the server, which is 64-bit. If an appropriate JVM from a JRE or SDK is not found on the library path or using variables as described below, or is not the appropriate bit type, a Failed to find JVM message is displayed. Further Java Services debugging information about loading the JVM is written to the server start log indicating JSCOM3 start failed, as well as additional information that might be useful in resolving the problem. JSCOM3 is the actual process name for the Java Services Listener and the terms are often used interchangeably.

Specify the JDK JRE bin and server (or client) subdirectories in the load library path environment variable. A server restart is required, plus the appropriate JVM must be on the path if switching JRE levels. The load library path is prompted at installation time if JVM-based adapters or features are required. Otherwise, it can be manually set by editing the EDAENV file by using any of the following methods:

• For Java JDK, set JDK_HOME (to the install home location) in the server environment configuration file (EDAENV).
• For Java JRE, set JAVA_HOME (to the install home location) in the server environment configuration file (EDAENV).
• Use a library path (LIBPATH) to set explicit pathing. Use of JDK_HOME or JAVA_HOME is preferred as they are less prone to error. The JRE bin and server (or client) subdirectories must be specified in a path-based environment variable and a server restart is required.

To change or add operating system environment variables, set and export the variable in a .profile or script that always gets called during a server start. It is very common to place variables in the server edastart script, but it is recommended that they are placed in a script that in turn calls edastart (so that the edastart script remains).

To change or add a variable in a server environment start-up file (EDACONF bin\edaenv.cfg), either edit the file in a text editor before starting the server or perform the following steps.

Procedure
1. Start the server (services such as Java Listener might fail until configured and the server is restarted).
2. Open the WebFOCUS Reporting Server browser interface and log in by using an administrator ID.
3. From the main menu, select Workspace.
4. In the navigation pane, open the Configuration Files and Miscellaneous folders.
5. Right-click Environment - edaenv.cfg and select Edit.
6. Make the desired edit.
7. Save the file.
8. Restart the server (changes are not effective until you restart the server).

The format of the 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 require quotation marks. Variables are always uppercase.

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.

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.

IP Port Number Requirements

The installation process prompts for two IP port numbers: the TCP Listener and HTTP Listener. It also uses the next two consecutive ports after the supplied HTTP Listener port for FDS use. This results in a total of four IP ports.

The supplied IP port numbers must be above the IANA registered well-known reserve range (numbers under 1024) and not over the maximum legal number (65535). Do not use IP port numbers already used by other applications or products. You can use commands such as Netstat or netstat to reveal the actual ports in use.

Browser Requirements

The WebFOCUS Reporting Server browser interface requires one of the following web browsers:

• Microsoft Edge.
• Mozilla Firefox® 59 or higher.
• Google Chrome® 65 or higher.

Disk Space Requirements

The server disk space requirements are:

Supplied (EDAHOME) Data Sets	3390 Cylinders
high_level_qualifier.P.HOME.ACX	2
high_level_qualifier.P.HOME.BIN	1100
high_level_qualifier.P.HOME.CICS.LOAD	10
high_level_qualifier.P.HOME.ERR	500
high_level_qualifier.P.HOME.ETC	100
high_level_qualifier.P.HOME.FEX	25
high_level_qualifier.P.HOME.LOAD	750
high_level_qualifier.P.HOME.MAS	4

Configuration (EDACONF) Data Sets	3390 Cylinders
high_level_qualifier.WFS.CONF.ACX	2
high_level_qualifier.WFS.CONF.CFG	2
high_level_qualifier.WFS.CONF.MAS	2
high_level_qualifier.WFS.CONF.PRF	2

Installation Data Sets	3390 Cylinders
high_level_qualifier.HOME.DATA	10
high_level_qualifier.WFS.DATA	2

Application Data Sets	3390 Cylinders
approot.IBISAMP.type.DATA	38 (across 14 data sets)
approot.BASEAPP.type.DATA	56 (14 data sets using 4 cylinders per file)

Deferred Execution Data Sets (Optional)	3390 Cylinders
high_level_qualifier.WFS.CONF.DFM.DEL	5
high_level_qualifier.WFS.CONF.DFM.RPE	5
high_level_qualifier.WFS.CONF.DFM.RPF	5
high_level_qualifier.WFS.CONF.DFM.RPO	100
high_level_qualifier.WFS.CONF.DFM.RQD	5
high_level_qualifier.WFS.CONF.DFM.RQF	5
high_level_qualifier.WFS.CONF.DFM.RQO	5
high_level_qualifier.WFS.CONF.DFM.RQP	5

Supplementary Data Sets	3390 Cylinders
high_level_qualifier.WFS.SYSRPC.FOCUS	1
high_level_qualifier.WFS.ETLLOG.FOCUS	1
high_level_qualifier.WFS.ETLSTATS.FOCUS	1
high_level_qualifier.WFS.CONF.SMARTLIB.DATA	1

where:

Memory Requirements

Memory usage of a configured environment consists of the following elements:

• Workspace Manager
• Listeners
• Concurrently running application agents

Actual memory usage depends on application features, and varies depending on the application. The SHRLIBRGNSIZE parameter (defined on SYS1.PARMLIB, member BPXPRMxx) can affect the amount of memory that the server address space allocates. For SHRLIBRGNSIZE, we recommend the default MVS installation value of 64Mb:

SHRLIBRGNSIZE(67108864)

Server memory usage:

• The workspace (including Listeners) uses 200 megabytes.
• Each pre-started agent requires 4 megabytes.

The minimum amount of memory for a newly installed server with no workload is 250Mb. However, depending on usage, workload, and configuration options, 500Mb is recommended to start, to be adjusted as needed.

Communication Requirements

You need four TCP/IP ports for each server instance that you configure. Three of these ports must be consecutive. Specify these port numbers during installation. You might require additional ports depending on which options you configure later.

The server supports only IBM TCP/IP. It does not support Interlink or any other third-party TCP/IP.

USS Segment Requirements

PDS deployment requires each user of the server to be identified to USS by means of a default segment definition. This default OMVS segment is defined when USS is installed as a part of z/OS. Refer to your IBM UNIX System Services documentation for more information about this subject.

ZFS Home and Configuration Directory Requirements

Libraries and the APIs supporting them must reside in the ZFS file system to enable the following features:

• Server-side graphics

They are also required for the following Java-based and SAP-based adapters:

• Call Java
• EJB
• JDBC
• Microsoft SQL Server
• SQL SAP
• SAP BWB

During installation, a panel with a list of adapters to be configured is displayed. If any of the above adapters are selected, the installation requires the path for two ZFS locations as follows:

• edahome_dir. Provide the edahome path for the dll modules that interface with Java/SAP and must reside in ZFS. The directory is created with 755 permissions, if it does not exist.
• edaconf_dir. Provide the edaconf path to be used for both configuration files (such as codepage files), as well as the root location for temporary files (such as traces and logs), that must reside in ZFS. If it does not exist, the directory is created with 755 permissions.

If no data adapters are selected, the next panel allows an optional configuration for the JSCOM3 listener. If server-side graphics support is desired, the listener must be configured and all three paths are required (edahome_dir, edaconf_dir, plus the path to Java passed to either JDK_HOME or JAVA_HOME).

If edaconf_dir is not defined during installation , it is not possible to configure it later by using the WebFOCUS Reporting Server browser interface. The server has to be re-installed, configuring the JSCOM3 listener.