x

For current information about supported releases:

1. Go to http://techsupport.informationbuilders.com.

   The Information Builders Technical Support home page opens.

2. In the Quick Links section on the right side of the page, click Supported Systems/Adapters.

   The Supported Systems and Adapters page opens.

3. Click the link for the server release you want.

   The Supported Systems and Adapters page for that release opens.

4. Click the link for your platform.

   The support chart for that platform opens.

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.

x

The IBM i - QShell Interpreter (IBM i Installation Option 30) must be installed to use the server. 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.

x

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.x, the general minimum JVM level is 1.5 or higher, since a number of components require 1.5. In narrow cases, a lower JVM level may be used, but is not advised nor has it been specifically tested. This section discusses JVM installation and configuration.

When you install a Java SDK, the JRE is included. The SDK build type in use must also match in terms of 32-bit or 64-bit to the bit type of the server in use. If a JVM from the SDK of a JRE is not on the library path or is an inappropriate bit type, a Failed to find JVM message as well as debugging information will be written to the start log, which will indicate a failed JSCOM3 service.

The current default/preferred JRE for the server is JRE 1.5, since this is the minimum requirement for some server components and JRE 1.4 is past its EOSL date. JRE 1.6 is also out and is known to work, so it is also an option to install. The following URL has Java EOL and EOSL information:

http://java.sun.com/products/archive/eol.policy.html

You can generally change the behavior of a JVM to revert to a prior release level from the Web Console by selecting Configuration/Monitor from the Workspace menu, opening the Java Services folder, right-clicking Default, and selecting Properties and adding a property, such as Java version 1.5. Version 1.4 is not recommended.

Note: As of V7R1, IBM no longer supports the use of this property as a change method.

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 JVM requirements. However, a default JVM level of the machine may not be 1.5 or higher, therefore some corrective action may be required. The easiest way to determine the default for the server iadmin ID is the do QSH CMD('java -version'), which will display the default release level for the ID. There are several choices to address this, but it also varies by operating system levels due to changes or restrictions by IBM.

For V6R1 or lower, the choices are:

• Switch the Java default property of the machine to 1.5 or higher, which may or may not be desirable based on other applications that may be using Java.
• Switch the server iadmin ID Java default property to 1.5 or higher.
• Set JAVA_HOME to point to the desired release, as of V7R1.
• Configure the server to have a 1.5 (or higher) JVM property.

For V7R1, the choices are:

• Change the machine's Java (5761-JV1) install options to point at the desired JVM level as a machine default. This may or may not be desirable based on other applications that may be using Java.
• Set JAVA_HOME to point at a desired JVM release level.

On V5R4 or V6R1 systems, to change or add a Java property of java_version=1.5, 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.5">>
   /QIBM/UserData/Java400/SystemDefault.properties')

or

QSH CMD('echo "java.version=1.5" >> $HOME/SystemDefault.properties')

On V5R4 or V6R1 systems, to configure the server JVM property, use the Web Console to access the Java Listener tuning:

1. Select Workspace from the menu.
2. Open the Java Services folder.
3. Right-click DEFAULT and select Properties.

   The Java Services Configuration pane opens.

4. Expand the JVM Settings section.
5. Under Non-standard JVM options, enter -Djava.version=1.5 in the JVM_OPTIONS field.
6. Click Save and Restart Java Services.

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:

JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit

The variable may be set in any of the following ways:

• As a system variable set from the profile of the server iadmin ID, using INLPGM exit, a JOBD RQSDTA() CL option, or any number of other methods for setting system variables within the environment of a job.
• As an exported QSH variable in any script that is used to call the edastart script.
• As a system variable in any customized CL that is used to call the QSH IFS edastart script, or as an export variable within the QSH portion of the CL.
• Add to the edaenv.cfg environment configuration file of the server.

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:

1. Select Workspace from menu bar.
2. Open the Java Services folder.
3. Right-click DEFAULT and select Properties.

   The Java Services Configuration pane opens.

4. Expand the Class Path section.
5. Add the desired full path jar names (one per line).
6. Click Save and Restart Java Services.

If JVM-based adapters or features are not required, the message Failed to find JVM is normal and can be ignored.

x

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.

x

The Web Console server requires one of the following Web browsers:

• Microsoft Internet Explorer® 7 or higher.
• Mozilla Firefox® 3.5 or higher.
• Google Chrome® 10.0 or higher.
• Apple Safari® 5.0 or higher.

The Opera™ browser does not support RIA (Rich Internet Application), the default appearance mode of the 7.7.x Web Console. Opera 5.0 or higher seems to operate properly in HTML mode, and the Web Console detects this and switches to this mode automatically. Since HTML mode is less extensively tested, Opera is considered unofficially supported at this time. Please report any issues you find to customer service.

x

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.

Version	During Install	After Install
V5R4	2 GB	1 GB
V6R1 or higher	2 GB	1 GB

x

Memory and shared memory usage depend on the following elements:

• Number of data access agents.
• Type of access that is performed, such as joins and large retrieval.
• Connection queue.

Actual memory usage differs between applications and the server load.

x

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.

x

When installing and using the server, you need several types of operating system user IDs:

• Server administrator IDs (iadmin). Server administrators use this ID to install, start, configure, and stop the server.

  The operating system ID you use when installing the server owns the server files and is the default server administrator. 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.

• User and application IDs. When users and applications try to access the server while it is running with security set to OPSYS, they are authenticated against the operating system. You need to make IBM i IDs available to use so they can access the server. When running in OPSYS mode, server data access agents impersonate these IDs before performing any file access on their behalf. Other security modes do not require special user IDs.

  For more information about running the server in OPSYS mode, see Step 6. Configuring the Server With Different Security Providers.

• Server system ID (iserver). You have the option of creating a user ID that is QSECOFR for internal use by the server to proxy the authority of QSECOFR. The ID can be an account never used for logging in. You might wish to create an iserver ID if, for example, you do not want certain server processes to appear as owned by QSECOFR.

  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.

x

The installation process creates these high-level directories:

• Home directory. This installation directory stores the server program links and other files. We refer to this as EDAHOME, and when the server is running, the full path is stored in the environment variable EDAHOME. The default directory is

  ibi/srv77/home[suffix]

  suffix

  Is optional when installing and maintaining a single release of the server. It is required if installing and maintaining multiple server releases, to ensure that each installed release has a uniquely-named home directory. For example:

  /home/iadmin/ibi/srv77/home77

• Home library. This installation library contains the actual server programs that appear in the home directory as symbolic links. The default library name is SRV77, but you can specify any valid library name.
• Configuration directory. The files that control the behavior of each server instance reside here. We refer to this as EDACONF, and when the server is running, the full path is stored in the environment variable EDACONF. The default directory is

  ibi/srv77/server_type[suffix]

  where:

  server_type

  Designates the type of server. The default values are:

  FFS	for a Full-Function Server
  DM	for a DataMigrator Server
  WFS	for a WebFOCUS Reporting Server
  WFM	for a Shared Application Server for WebFOCUS Maintain

  suffix

  Optional for an initial default installation and configuration. Required when configuring additional instances of the server. You must add a suffix to the directory name to ensure that each server instance has a uniquely-named configuration directory. For example:

  /home/iadmin/ibi/srv77/ffs002

• Application directory. This is the default location for storing applications. We refer to this as APPROOT, and when the server is running, the full path is stored in the environment variable APPROOT. This directory may be shared by applications created with other Information Builders products. It defaults to

  ibi/apps

  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.

• Profiles directory. The user and group profiles reside here, as does the admin.cfg file, which specifies the server administrator. We refer to this as EDAPRFU, and when the server is running, the full path is stored in the environment variable EDAPRFU. This directory defaults to

  ibi/profiles