Before you install, review the requirements in the following topics. Exact requirements vary according to your configuration and the number of users and deployed applications.
Processor. The software 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 server instances (or any of their components) on the primary domain controller (PDC) or on the backup domain controllers (BDC).
Supported Software Releases. The software 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 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.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
Installing maintenance updates to the EDAHOME of an existing server running releases prior to production 7.7.05 will also have the requirement of moving up all dependent configurations to use Java 1.6 (as instructed in this section).
You may install a Java JRE or a Java SDK. When you install a Java SDK, the JRE component (where the JVM lives) is included, so either is allowed. If using servlet, the Java SDK is required for the jar command, so it is generally preferred over the Java JRE. The SDK or JRE build type must also match the 32-bit or 64-bit bit type of the server. If an appropriate JVM from a JRE or SDK is not found on the library path or using variables as described below, or is not the appropriate bit type, 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.
There are several ways to specify the JVM location:
To change or add a variable in the server environment start up file (EDACONF bin\edaenv.cfg), either edit the file in a text editor before starting the server (a start menu icon is also available under the configure folder) or:
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.
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, and the JVM environment is not configured, 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 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).
The Web Console requires one of the following web browsers:
The installation requires 40MB of temporary disk space on your Windows %HOME% drive and approximately 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 the OPSYS Security Provider, no special authorities are needed for the IDs.
Note: PTH is a security provider in which IDs and passwords are created and maintained solely within the realm of the server. It is effectively an internal security provider that uses internally saved passwords, and not an outside provider for authorization. PTH is the default provider for new installations. Prior release level servers that are upgraded to 7.7.06 or higher will maintain their previous providers (as these properties are stored within the EDACONF configuration of a server, which is unaffected by upgrades). An administrator for an upgraded site may use the Web Console Access Control page to set specific features that they may not have done previously.
For more information about running the server in secure mode, see Security Providers.
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 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 in a way that makes the Data Management Console available to remote users as a shared tool. You can choose between:
Before installing, you need to create a shared folder on the computer on which you will install the software.
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 |