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.
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:
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 server installation software is labeled for your operating system level.
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.
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 from the JRE of the SDK 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.
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:
The System Properties window opens.
The Environment Variables window opens.
The Edit System Variable window opens.
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.
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 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 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.
The installation of the server requires 40MB of temporary disk space on your Windows %HOME% drive and 1 GB of permanent disk space on the designated hard disk.
Memory usage depends on the following elements:
The memory requirements for installation and operation of the server are:
(This includes memory used by the primary one-per-server-instance processes such as Workspace Manager, the print log, Deferred Listener, HTTP Listener, and TCP Listener.)
These numbers apply when the server is in an idle state, so they may fluctuate slightly.
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.
Depending on your security environment and company security policies, you need two types of Windows logon privileges:
The installation of the server requires that you are logged on as an administrator or as a member of the Administrator group. Administrators of the server are also responsible for tasks such as starting, stopping, pausing, resuming, and restarting services on remote or local computers.
Although Administrative privileges are required only during installation, a Server Administrator needs to have at least Power User privileges in order to run the server as a service.
Note that the name iadmin is used to refer to the server administrator ID throughout this manual, but you may use any name for this ID.
A server administrator ID and password are encrypted and stored in the server configuration file. You must keep these IDs and passwords synchronized with Windows IDs and passwords to start the server with security set to OPSYS. When starting the server with security set to OPSYS, if the server administrator does not have a password, or the password is not synchronized with Windows, the server starts in safe mode, and not all functionality is available. For details about how to fix this problem, see Troubleshooting for Windows.
For security purposes, you should not allow users and applications to use administrator or a member of the administrator group user ID. The server administrator ID should be available only to users who require server administrative privileges.
For more information about running the server in secure mode, see Choosing a Security Provider.
You can run the installation procedure in:
There are several tools available for administering the server:
For more information about the Web Console, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.
For more information about Developer Studio, see the Developer Studio Application Development Getting Started manual.
For more information about the Data Management Console, see the DataMigrator User's Guide.
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:
Before installing the server, you need to create a shared folder on the computer on which you will install the server.
Access to the server by means of the Data Management Console (DMC) is limited by system security. To use the DMC, you can open it in several ways, such as:
The location of dmcstart.bat defaults to ibi\srv77\dm\bin.
The Data Management Console is maintained locally on each client machine in Documents and Settings\UserID\Application Data\Information Builders. This requires 2M of disk space.
To use the loopback node, reconfigure it to connect to the share server host name, replacing the host name, localhost.
iWay Software |