In this section: |
Before you install the server, review the requirements in the following topics.
The server is supported on most major platforms, including AIX, HP-UX, Linux, Solaris, and Tru64. 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.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:
export IBI_JNIPATH=/usr/jdk1.6.0_38/jre/lib/i386/server: /usr/jdk1.6.0_38/jre/lib/i386:$IBI_LIBPATH
export IBI_JNIPATH=/usr/jdk1.6.0_38/jre/lib/i386/server: /usr/jdk1.6.0_38/jre/lib/i386:$IBI_LIBPATH
To change or add operating system environment variables, set and export the variable in a .profile or script 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:
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 upper case.
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.
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 has outbound email features using STMP protocols. To use these features, the TCP/IP host name (or number) and port number for an accessible SMTP server must be configured (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.
If the defaults are not taken at the prompt for directories and port numbers, an additional prompt for the SMTP Server host name occurs. If an SMTP Server host name is supplied, the process will then prompt for the SMTP Server port number and inputs for 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 (address to send administrative warnings to, such as an agent crash).
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 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 IA64 (Integrity) |
660 MB |
680 MB |
Linux for Intel/AMD |
450MB |
460 MB |
Linux for pSeries |
Not supported |
470 MB |
Linux for zSeries |
450 MB |
460 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.
Memory and shared memory usage depends on:
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.
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.
When installing and using the server, you need two types of operating system user IDs:
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.
For more information about running the server in secure mode, see Choosing a Security Provider Mode.
iWay Software |