Installation Requirements

In this section:

Before you install the server, review the requirements in the following topics. Exact requirements vary according to your configuration and the number of users and deployed applications.


Top of page

x
Platform and Operating Environment Requirements

Processor. The server runs on all Intel® Pentium®-based computers 400 MHz and higher.

For security reasons as well as performance considerations, it is advisable not to run a server instance (or any of its components) on the primary domain controller (PDC) or on the backup domain controllers (BDC).

Supported Software Releases. The server is supported on most major releases of Microsoft Windows. 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.


Top of page

x
JVM Requirements for the Listener for Java

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 77x, 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.

You may install a Java JRE or a Java SDK. When you install the Java SDK, the JRE is included. If using servlet, the Java SDK is required for the jar command so is generally preferred over Java JRE. The SDK or JRE 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 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. The following URL has Java EOL and EOSL information:

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

You can revert to using JRE 1.4 from the Web Console by selecting Configuration/Monitor from the Workspace menu,opening the Java Services folder, right-clicking Default, and selecting Properties.

There are several ways to specify the JVM location:

The IBI_JNIPATH variable may be set as a system-wide environment variable or as a server variable in the environment start-up file (edaenv.cfg). If using PATH, the JVM directory should be set as part of the system-wide PATH environment variable. The environment start-up file (edaenv.cfg) is not recommended for PATH, since it does not support %PATH% syntax. In addition, an expanded %PATH% string effectively locks PATH separately from any machine changes to %PATH%.

To change or add an environment variable, perform these steps:

  1. Right-click My Computer and select Properties.

    The System Properties window opens.

  2. Select the Advanced tab and click Environment Variables...

    The Environment Variables window opens.

  3. In the System variables list, select Path and click Edit or Add.

    The Edit System Variable window opens.

  4. Set or append the JRE bin and client subdirectories in the Variable Value field, and then click OK three times.

To add classes to the JVM class path for customer-written CALLJAVA applications, set the CLASSPATH variable at 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.


Top of page

x
Browser Requirements

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

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


Top of page

x
Disk Space Requirements

The installation of the server requires 40MB of temporary disk space on your Windows %HOME% drive and 340 MB of permanent disk space on the designated hard disk.


Top of page

x
Memory Requirements

Memory usage depends on the following elements:

The memory requirements for installation and operation of the server are:

These numbers apply when the server is in an idle state, so they may fluctuate slightly.


Top of page

x
Communications Requirements

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.


Top of page

x
User ID Requirements

Depending on your security environment and company security policies, you need two types of Windows logon privileges:


Top of page

x
Choosing Between Interactive and Silent Installation

You can run the installation procedure in:


Top of page

x
Choosing Between Private and Shared Access to the Data Management Console

There are several tools available for administering the server:

You can install the server in a way that makes the Data Management Console available to remote users as a shared tool. You can choose between:


iWay Software