In this section: |
Before beginning server 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 server installation software is labeled for your operating system level.
OpenVMS Release |
CD Label |
---|---|
7.3-2 Alpha |
OpenVMS V7.3-2 Alpha |
8.2-1 IA64 |
OpenVMS V8.2-1 IA64 IEEE |
8.2-1 Alpha |
OpenVMS V8.2-1 Alpha IEEE |
8.3-1H1 IA64 |
OpenVMS V8.3-1H1 IA64 IEEE |
Third-party TCP/IP packages from Process Software have also been tested 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 VMSFLOATCNV = 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 VMSFLOATCNV = 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 VMSFLOATCNV = 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 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.
When you install the Java SDK, the JRE is included. The SDK 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.
If JAVA* logicals are not active system-wide or are for Java 1.4, when we require 1.5, you must make the logicals active by installing the desired Java SDK (from HP), and either at the system level or for the server level, execute the DCL initialization script that comes with the Java SDK. At the server level, this would 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 77x, the edaenv.com file is pre-created with DCL to initialize 1.5.
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, the message Failed to find JVM is normal and can be ignored.
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.
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 Alpha |
7.3-2 |
705,000 blocks |
8.2 |
650,000 blocks | |
OpenVMS for IA64 |
8.2-1 |
980,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. 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.
For more information about running the server in secure mode, see Step 6. Configuring the Server With Different Security Modes.
iWay Software |