In this section:
Before beginning installation, review the requirements in the following topics.
For current information about supported releases:
The Information Builders Technical Support home page opens.
The Supported Systems and Adapters page opens.
The Supported Systems and Adapters page for that release opens.
The support chart for that platform opens.
In general, the operating system should have the latest cumulative patch levels applied.
Confirm that your installation software is labeled for your operating system level.
The IBM i - QShell Interpreter (IBM i Installation Option 30) must be installed to use the product. The QShell Interpreter is a free optional feature of IBM i. The easiest way to check if this feature is installed is to enter QSH on the IBM i command line. If it is installed, a UNIX-like environment starts (F3 to exit). If it is not installed, you receive a Command QSH in library *LIBL not found message. If it is not installed, install it before proceeding.
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.
As of 7.7.05 and 8.0.01 production releases, the minimum JVM release level is 1.6 or higher, due to required internal components of the server. The Java Listener will not start unless 1.6 (or higher) is in use. Prior 7.x releases would allow the listener to start with any release, and sub-components would fail if they required a higher Java Level. The primary reason for this change is that Java 1.5 (and prior releases) are past their End of Service Life (EOSL) dates, and, as such, are unsupportable, in addition to lacking newer functionality. The following URL has Java EOL and EOSL information:
The location of the JVM on IBM i is controlled by the object QSYS/QJVAJNI. This is normally on the system path, so you do not need to do anything to fulfill basic JVM find requirements. However, if the default JVM level of the machine is not 1.6 or higher, corrective action may be required to access the correct JVM level.
Java is always pre-installed by IBM on IBM i systems and the only question is the current default release level in use.
If the default JVM is not found or is set to an appropriate release at server start time, a Failed to find JVM message will be displayed. Further Java Services debugging information about loading the JVM will be written to the server start log, indicating JSCOM3 start failed, as well as additional information that may be useful in resolving the problem. JSCOM3 is the actual process name for the Java Services Listener, and the terms are often used interchangeably.
The easiest way to determine the current default for the server iadmin ID is to issue the command QSH CMD('java -version'), which will display the default release level for the ID.
There are several choices on how to address using the correct JVM level, but also varies by operating system levels due to changes or restrictions by IBM.
For V6R1 or lower, the choices are:
For V7R1, the choices are:
On V6R1 systems, to change or add a Java property of java_version=1.6, use EDTF against the /QIBM/UserData/Java400/SystemDefault.properties file or the server ID home directory SystemDefault.properties file. If an editor is not available, you can also create or append to the Java system or user property files using the following:
QSH CMD('echo "java.version=1.6">> /QIBM/UserData/Java400/SystemDefault.properties')
QSH CMD('echo "java.version=1.6" >> $HOME/SystemDefault.properties')
On V6R1 systems, you may also configure the server JVM properties for the release level using the Web Console to access the Java Listener tuning:
The Java Services Configuration pane opens.
In V7R1 systems, the various Java releases that may be available will be found in the /QOpenSys/QIBM/ProdData/JavaVM folder. For example:
/QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit /QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit /QOpenSys/QIBM/ProdData/JavaVM/jdk50/64bit /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit
To use the JVM from one of these releases, specifically for the server iadmin ID (if it is not already the system default), set the JAVA_HOME variable to point at a 32bit JDK. For example:
The variable may be set in any of the following ways:
Use of the -Djava property on V7R1 and higher is not an option, and if it was used previously under V6R1, and the machine is upgraded to V7R1, the Java release must be configured using V7R1 methods (described above).
To change or add operating system environment variables, set and export the variable in a .profile, script, or CL 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 be placed in a script that in turn calls edastart (so that the edastart script remains vanilla).
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:
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 require quoting. Variables are always uppercase.
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 by using the Web Console to access the Java Listener:
The Java Services Configuration pane opens.
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.
The install 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). Additionally, do not use IP port numbers already being used by other applications or products. Netstat, or netstat like commands, should reveal what actual ports are in use.
The server can send emails using STMP protocols. To use these features, the server needs the TCP/IP host name (or number) and port number for an accessible SMTP server (the default port number is 25).
The installation process allows this information to be set at installation time, but it may also be added (or changed) afterward using the Web Console. To change it from the Web Console, select Workspace from the main menu, and then select E-Mail SMTP Server from the ribbon.
The installation panel for supplying the SMTP information will also have inputs for the default email sender address (the from address for users reading an email from the server if none was specified in the originating application) and the server administrator email address (the address to send administrative warnings to, such as an agent crash).
The Web Console requires one of the following web browsers:
The following are approximate disk space requirements. Specific sizes may vary slightly with options selected during configuration. The usage numbers do not include space for actual applications, data sources, sort space, output preparation, or logs.
V6R1 or higher
Memory and shared memory usage depend on the following elements:
Actual memory usage differs between applications and the server load.
You need four TCP/IP ports for each server instance that you configure. Three of these ports must be consecutive. You specify these port numbers during installation. You may require additional ports depending on which options you configure later.
When installing and using the server, you need several types of operating system user IDs:
The operating system ID you use when installing the server owns the server files and is the default server administrator for OPSYS mode. You can create a new operating system ID to run and own the server files, or use any ordinary (non-QSECOFR) ID.
Note that the name iadmin is used to refer to the server administrator ID and group throughout this manual, but you may use any name for this ID.
For security purposes, you should not allow users and applications to use the iadmin ID. It should be available only to users who require server administrative privileges.
Note that the name iserver is used to refer to the server system ID throughout this manual, but you may use any name for this ID.
For specific information on creating IDs, see Step 2. Creating User IDs.
The installation process creates these high-level directories:
Is optional when installing and maintaining a single release of the product. It is required if installing and maintaining multiple server releases, to ensure that each installed release has a uniquely-named home directory. For example:
Designates the type of product. The default values are:
for a Full-Function Server.
for a DataMigrator Server.
for a WebFOCUS Reporting Server.
for a Shared Application Server for WebFOCUS Maintain.
Optional for an initial default installation and configuration. Required when configuring additional instances of the product. You must add a suffix to the directory name to ensure that each instance has a uniquely-named configuration directory. For example:
Security for application directories is handled at the operating system level. To avoid any possibility of these directories being accessed inappropriately by means of APP commands (such as APP DELETE AppDirName), use directory security to set the appropriate permissions on these directories.