x

The server is supported on most major platforms, including AIX, HP-UX, Linux, Solaris, and Tru64. 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

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. Some UNIX vendors have standalone JRE packages available, but only full SDK packages are supported for server purposes. 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 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 or 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 available and can also be used. 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, selecting Properties, and adding a property, such as java.version=1.5. (Version 1.4 is not recommended.)

There are several ways to specify the JVM location:

• For Java JDK, set JDK_HOME (to the install home location) in environment or server environment start-up file (edaenv.cfg).
• For Java JRE, set JAVA_HOME (to the install home location) in environment or server environment configuration file (edaenv.cfg).
• Use library path or IBI_JNIPATH 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.

The JDK JRE bin and server (or client) subdirectories must be specified 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 may be set by using any of the following methods.

• Set the JDK_HOME variable to the name of the Java SDK home directory and the required directories will be added internally using the library load path (LIBPATH on AIX, SHLIB_PATH on HP-UX, LD_LIBRARY_PATH on all other platforms.)
• Set the JVM server or client directory (in which libjvm resides) and its parent directory to the IBI_JNIPATH Java library load path. For example, on Linux:

  export IBI_JNIPATH=/usr/jdk1.5.0_11/jre/lib/i386/server:
  /usr/jdk1.5.0_11/jre/lib/i386:$IBI_LIBPATH

• Set or append the JVM server or client directory (in which libjvm resides) and its parent directory to the internal library load path (IBI_LIBPATH). This is least preferred method and only documented for backward compatibility. For example:

  export IBI_JNIPATH=/usr/jdk1.5.0_11/jre/lib/i386/server:
  /usr/jdk1.5.0_11/jre/lib/i386:$IBI_LIBPATH

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.

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 in megabytes. Specific sizes may vary slightly depending on the release being used and the options selected during configuration. The usage numbers do not include space for actual applications, databases, sort space, output preparation, or logs.

Platform	After Installation - 32bit	After Installation - 64bit
AIX	500 MB	500 MB
HP-UX PA-RISC	400 MB	550 MB
HP-UX IA60 (Integrity)	660 MB	680 MB
Linux for Intel/AMD	460 MB	465 MB
Linux for Itanium	Not supported	540 MB
Linux for pSeries	470 MB	Not supported
Linux for zSeries	450 MB	450 MB
Solaris Sparc	520 MB	500-550 MB (depends on OS level)
Solaris x86	500 MB	525 MB

During installation, the disk space required is approximately 20 megabytes more than double the After Installation size. These numbers do not include space for applications. The ibisamp sample application requires an additional six megabytes.

x

Memory and shared memory usage depends on:

• Number of data access agents.
• Type of access performed (for example, joins, large-scale retrieval, and so on).
• Connection queue.

Memory usage differs depending on your implementation of UNIX and your server load.

The following table shows the approximate memory requirements for installing and running the server.

Platform	Memory Per Agent	Other Memory *
HP-UX	2 MB	8 MB
AIX (32 bit)	2 MB	6 MB
AIX (64 bit)	12 MB	45 MB
Solaris (Sparc)	15 MB	60 MB
Solaris (Intel)	8 MB	30 MB

* Other memory includes memory used by the primary one-per-server daemon processes, such as the Workspace Manager, the print log, Deferred Listener, HTTP Listener, and TCP Listener.

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 two 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-superuser) ID. However, you should not install the server as root. The server administrator ID should have a Korn, Bourne, or Bash shell as the default logon shell.

  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 in secure mode, they are authenticated against the operating system. You need to make UNIX IDs available to them so that they can access the server. Server data access agents impersonate these IDs before performing any file access on their behalf.

  For more information about running the server in secure mode, see Choosing a Security Provider Mode.