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 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 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 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.

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.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:

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

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:

• Switch the Java default property of the machine to 1.6 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.6 or higher.
• Configure the server to have a 1.6 (or higher) JVM property, as described below. (This is now done automatically for new installs on V5R4 and V6R1.)

For V7R1, the choices are:

• Change the 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 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')

or

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:

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.6 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/jdk60/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.

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:

1. Start the server (services like Java Listener may fail until configured and the server is restarted).
2. Open the Web Console and log on using an administrator ID.
3. Select Workspace from the main menu.
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 (changes are not effective until restart).

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:

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, and the JVM environment is not configured, 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 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).

x

The Web Console requires one of the following web browsers:

• Microsoft Internet Explorer® 9 or higher.
• Mozilla Firefox® 27 or higher.
• Google Chrome® 33 or higher.
• Apple Safari® 7 or higher and Mobile iOS v5.
• Opera 19 or higher.

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, and stop the server. This ID is also used to configure the server if the server is configured to run with an OPSYS (operating system) Security Provider.

  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.

• User and application IDs. When users and applications try to access the server, the server is normally running with one or more Security Providers that do authorization logic.
• 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 product program links and other files. We refer to this as EDAHOME, and when the product 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 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:

  /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 product instance reside here. We refer to this as EDACONF, and when the product is running, the full path is stored in the environment variable EDACONF. The default directory is

  ibi/srv77/product_type[suffix]

  where:

  product_type

  Designates the type of product. 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 product. You must add a suffix to the directory name to ensure that each instance has a uniquely-named configuration directory. For example:

  /home/iadmin/ibi/srv77/ffs002

• Application directory. This is the default location for storing applications. It is a folder under the server internal location known as APPROOT. This directory may be shared by applications created with other Information Builders products. The APPROOT location 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