|
Operations Guide
|
Different versions of UM have some differences in how the files are offered for download. As of 6.11, the following zip files are available for download:
The first four contain the binary software for that product (all platforms). The last contains HTML and PDF documentation for all UM products and features.
For the binary software, the zip file contains a set of per-platform package installers, and a set of Java jar files. The jar files should be copied to wherever you keep your Java jars. The package installers should be installed as described below.
There are many different ways to install UM on a host, but they can generally be categorized in three groups:
Running the UM package installer is typically only done for hosts being prepared for development use. Once an application system is developed, UM is usually installed by the user's own Application Installer.
Note that the DRO package installer needs the corresponding version of UM to be already installed and accessible in the current working directory before it can be installed.
A product's Unix Package Installer is an executable file with the file suffix ".sh". It is in the form of a self-extracting archive, sometimes called a "shell archive".
It is often necessary to set the file permissions to allow execution of the file.
Running the UM Package Installer on a Unix host does nothing more than copy the files under the current working directory. The installer does not perform any other installation actions.
For example, to install the UMQ base product:
This creates a directory named "UMQ_6.17" which contains all the files and sub-directories needed to develop and test UM-based applications. It does not contain the documentation, which is shipped in its own zip file.
A product's Windows Package Installer is an executable file with the file suffix ".exe".
Running the UM Package Installer on a Windows host does the following:
"PATH" environment variable to include UM's "bin" folder. To run the installer, simply double-click the package installer icon.
Note that once an application system is developed, UM is usually installed by the user's own Application Installer.
Java
The UM Java API is a wrapper around the UM dynamic library (JNI). The jar files are shipped with the package installers, and should be saved wherever you store your jar files.
Note that the Java jar file version must match the underlying UM library version.
Stratus OpenVOS Package
The Stratus OpenVOS package is a self-extracting archive that contains the Ultra Messaging Streaming Edition (UMS) for the Stratus OpenVOS platform.
Ultra Messaging supports Stratus OpenVOS Release 17.0.2aq.
RESTRICTIONS:
The following Ultra Messaging components and features do not run on the Stratus OpenVOS platform:
HP NonStop Package
The HP NonStop package is a self-extracting archive that contains the Ultra Messaging Persistence Edition (UMP) for the HP NonStop platform.
Ultra Messaging supports HP NonStop Version J06-17.
RESTRICTIONS:
The following components and features do not run on the HP NonStop platform.
It is generally not necessary to run the UM Package Installer to use UM on a host. For the most part, all you need to do is copy the runtime files to any desired location on your host. In the case of running UM daemons as Windows Services, there are some additional steps necessary; see Copy Windows Runtime Files.
Informatica generally recommends that UM runtime files be stored in the "lib" and "bin" sub-directories in the structure that the installer creates. If the brokered queuing feature is used, then the "broker" sub-directory should also be included. For example:
Notice that the "include" sub-directory is missing. Those files are only needed for development, not for production runtime.
For ease of use, users typically include "lib" in their library search path (e.g. "LD_LIBRARY_PATH" environment variable), and include "bin" in their "PATH".
No other specialized installation steps are needed for UM.
Alternatively, the contents of "bin" can be copied to wherever you already store your application executables, and the contents of "lib" can be copied to wherever you store your application dynamic libraries.
Informatica generally recommends that UM runtime files be stored in the "bin" sub-folder in the structure that the installer creates. If the brokered queuing feature is used, then the "broker" sub-directory should also be included. For example:
Notice that the "include" and "lib" sub-folders are missing. Those files are only needed for development, not for production runtime.
For ease of use, users typically include "bin" in their "PATH" environment variable.
No other specialized installation steps are needed for UM applications. However, if you want to run one or more UM daemons as Windows Services, then there are some additional steps necessary, described in UM Daemons as Windows Services.
Alternatively, the contents of "bin" can be copied to wherever you already store your application executables.
UM is intended to be integrated into a user's own application system. Each user decides how his application system is packaged and installed.
UM users typically do not run the UM package installer as part of their application installation procedure. Rather, the UM runtime files are typically packaged with the user's application files.
The requirements for the user's application installation procedure are the same as outlined in Copy UM Runtime Files, and for the most part, consist simply of copying the UM files to the host.
In the case of running UM daemons as Windows Services, there are some additional steps necessary; see Copy Windows Runtime Files.