Before beginning installation, review the requirements in the following topics.
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.
|
OpenVMS Release |
CD Label |
|---|---|
|
7.3-2 Alpha |
OpenVMS V7.3-2 Alpha |
|
8.3-1H1 IA64 |
OpenVMS 8.3-1H1 IA64 (Integrity) |
Third-party TCP/IP packages from Process Software have also been tested in the past at the Multinet 4.4 and TCPWare 5.6 levels for basic connect and data retrieval, and are known to be operational and require no special configuration. If you have a problem using third-party TCP/IP products, be sure to specify the product, the release, and any installed patches when contacting Customer Support Services.
In OpenVMS 8.x, some DBMS vendors changed their products to use IEEE floating point for single (F) /double (D) float data, while others have retained use of G_FLOAT float point or depend upon the application itself. In order to support these varying float-type sources, OpenVMS 8.x servers use the SET VMSFLOATCONV = IEEE/G_FLOAT command to select the float type of the data, and it would be used in the server profile (edaprof.prf). Sites that use both IEEE and G_FLOAT data sources will need separate server configurations with the appropriate SET VMSFLOATCONV = IEEE/G_FLOAT command and a hub-sub configuration to allow the joining of data.
OpenVMS 8.x releases prior to the 7.7.02 server used separate builds type to read the different float types. As of 7.7.02, SET VMSFLOATCONV = IEEE/G-FLOAT is used. For configuration information, see Configuring for IEEE/G_FLOAT Float Data.
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.
If JAVA* logicals are not active system-wide or are for Java 1.4 or 1.5, when we require 1.6, you must make the Java 1.6 logicals active by installing the desired Java SDK (from HP), and either at the system level or at the server level, execute the DCL initialization script that comes with the Java SDK (for example, @SYS$COMMON:[JAVA$60.COM]JAVA$60_SETUP.COM or any system symbol that may have been set up for Java 1.6 activation). At the server level, this could be done by adding the Java initialization script to the server edaenv.com file in the EDACONF bin directory (create it if needed). As of the 7.7.x release, the edaenv.com file is pre-created (on new installs) with standard DCL to initialize the required Java level. Older installs upgraded to 7.7.05 may need the edaenv.cfg file adjusted to use Java 1.6.
The OpenVMS Java logical JAVA$CLASSPATH is not currently supported for adding classes to the JVM class path for customer-written CALLJAVA applications. To add classes, use the logical CLASSPATH using UNIX style conventions enclosed in quotes as described in OpenVMS Java documentation or use the Web Console to set the Java Listener IBI_CLASSPATH property.
If JVM-based adapter 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 following are approximate disk space requirements. Specific sizes may vary slightly according to the options that were selected during configuration. The usage numbers do not include space for actual applications, databases, sort space, output preparation, or logs.
|
Platform |
Version |
After Install |
|---|---|---|
|
OpenVMS for IA64 (Integrity) |
8.3-1H1 |
1,100,000 blocks |
Memory usage in a configured environment is determined by the following factors:
Actual memory usage varies depending on the features used by the application, and will increase or decrease as agents change between active and idle states.
The Workspace Manager makes use of a specific system resource known as shared memory. Each individually configured server, with or without adapters, uses one shared memory. The size of this memory varies based upon the sizes of the agents table and the queue.
Generally, shared memory use does not require special configuration. It is just a resource that system administrators like to know is being used so they can monitor it with the SHOW MEMORY/POOLED command (non-paged section).
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 for OPSYS mode. You can create a new operating system ID to run and own the server files, or use any existing ID, provided it is set up as described in Step 2. Creating User IDs.
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.
If Active Technologies has been licensed, the installation path of the server (which is typically under the iadmin home directory) must not include any dollar signs ($) in the device or path name (as is common in OpenVMS device names like DISK$DKA0). Dollar signs in the EDAHOME path causes the underlying Flex Compiler to fail, regardless of the OpenVMS Java configuration. This requirement provides a simple workaround if Active Technologies is being used. Use of a concealed or regular logical to hide dollar signs in the installation path is allowed.
| iWay Software |