|
|||||
|
|
|||||
| OmniMark CI 4.0 installation procedure (UNIX) | |||||
| ------ |
Use the following procedure to install OmniMark 4.0 software and examples on a UNIX workstation. Note that these procedures include notes about differences among specific UNIX platforms. Super-user privileges are required to perform many of these steps. If you do not have such privileges, then this software should be installed by your system administrator. OmniMark 4.0 is configured to run in authorized mode only, requiring you to install or properly update the proper FLEXlm License Manager software on your license manager server machine. Overview of the FLEXlm License Manager.
Use the following command to create a new directory to contain the OmniMark software and examples:
mkdir /opt/local/omni40
This guide uses /opt/local/omni40 as the pathname of the installation directory. If you use a different pathname, then substitute your pathname wherever you see /opt/local/omni40.
After you have made the new directory, change to that directory.
cd /opt/local/omni40
Copy the installation file from the CD-ROM, or download the file om40.tar.Z from the OmniMark Technologies software download page
. Make sure that you copy the om40.tar.Z file appropriate for the platform on which you will be running the license manager.
If you are downloading from the Web, download om40.tar.Z to your installation directory. Copy the om40.tar.Z file from the appropriate platform subdirectory on the CD-ROM to your installation directory. For instance, if you are installing from CD-ROM, and it is mounted on the directory /cdrom, and you're installing on the Solaris platform, you would use the following command:
cp /cdrom/solaris/om40.tar.Z .
Extract and install the software
Execute the following command to extract and install the contents of om40.tar.Z in the OmniMark installation directory:
For HP-UX platforms
zcat om40.tar.Z | tar xvf -
For other UNIX platforms
zcat om40.tar.Z | tar xvpf -
Set the environment variable OMNIMARK_LICENSE_FILE to contain the port number and hostname that the license manager server is using:
In the Bourne shell (sh) and the Korn shell (ksh)
OMNIMARK_LICENSE_FILE="TCP/IP_Server_Address@Server_Name" export OMNIMARK_LICENSE_FILE
In the C shell (csh)
setenv OMNIMARK_LICENSE_FILE "TCP/IP_Server_Address@Server_Name"
Test installation and authorization
To test that OmniMark 4.0 has been installed and authorized correctly, use the steps following to test it.
First, ensure that OmniMark can communicate with the license manager. To do this, you will need to know:
lmgrd) is running on
After installing the license manager software (see Installing the license manager), you can test that OmniMark can successfully communicate with the license manager by running the "test.xom" script. This script appears in the top level of the OmniMark installation directory and can be run with the following command line:
bin/omnimark -s test.xom
If you receive the output "success", then OmniMark is successfully communicating with the FLEXlm License Manager.
Upgrading from an earlier version of OmniMark
If you are upgrading from an earlier version of OmniMark, replace the old version executable with the new OmniMark executable. You may want to rename rather than delete the old executable so your users can still run it if they wish.
Configuring a new installation of OmniMark
If this is a new installation of OmniMark, you need to place the OmniMark 4.0 executable in your user's search path. If you already have a directory like /usr/local/bin or /opt/local/bin, then you can create a symbolic link in that directory to the new OmniMark executable. If you do not have such a directory, you can create one.
You must modify each user's .profile or .login file to set the OMNIMARK_LICENSE_FILE variable. Use the Bourne shell syntax for .profile files, and the C shell syntax for .login files.
Have your users log out and log back in again; they should now be able to run OmniMark 4.0.
If your platform supports external functions, you may also wish to copy or link the file h/omxfapi.h into a new or existing directory containing C include files.
| ------ |
| ---- |