OpenLink License Manager Usage Notes






Start the License Manager Process

Mac OS X

  1. Open a Mac Terminal.
  2. Navigate to this directory: /Library/Application Support/openlink/bin
  3. Execute this command: oplmgr +start

Unix

  1. Open a Unix terminal.
  2. Navigate to the root of your OpenLink UDA or Virtuoso installation.
  3. Use one of the following scripts to set Virtuoso-related environment variables:
    • bash, bourne, korn shells - openlink.sh
    • C shells - openlink.csh
    • bash, bourne, korn shells - virtuoso-enterprise.sh
    • C shells - virtuoso-enterprise.csh
  4. If OpenLink License Manager version is 1.3.5 or less
    • Set and export an OPL_LICENSE_DIR variable that passes the path to the directory that contains your OpenLink UDA or Virtuoso license.
    • Navigate to the bin sub-directory of the OpenLink installation.
    • Execute this command: oplmgr +start
  5. If OpenLink License Manager version is 1.3.6 or greater
    • Navigate to the bin sub-directory of the OpenLink installation.
    • Execute this command: oplmgr +start +directory <path to directory containing license>


Note: OpenLink recommends that you create an /etc/init.d/ script that runs `oplmgr +start' on boot-up.

Windows

  1. Login to Windows.
  2. Open the Services or Component Services utility that resides in the Control Panel or its Administrative Tools sub-folder.
  3. Locate the OpenLink License Manager process.
  4. Highlight the OpenLink License Manager process.
  5. Click the Start icon.


Stop the License Manager Process

Mac OS X

  1. Open a Mac Terminal.
  2. Navigate to this directory: /Library/Application Support/openlink/bin
  3. Execute this command: oplmgr +stop

Unix

  1. Open a Unix terminal.
  2. Navigate to the root of your OpenLink UDA or Virtuoso installation.
  3. Use one of the following scripts to set Virtuoso-related environment variables:
    • bash, bourne, korn shells - openlink.sh
    • C shells - openlink.csh
    • bash, bourne, korn shells - virtuoso-enterprise.sh
    • C shells - virtuoso-enterprise.csh
  4. Navigate to the bin sub-directory of the OpenLink installation.
  5. Execute this command: oplmgr +stop

Windows

  1. Login to Windows.
  2. Open the Services or Component Services utility that resides in the Control Panel or its Administrative Tools sub-folder.
  3. Locate the OpenLink License Manager process.
  4. Highlight the OpenLink License Manager process.
  5. Click the Stop icon.


Reinitialize the License Manager Process

Mac OS X

  1. Open a Mac Terminal.
  2. Navigate to this directory: /Library/Application Support/openlink/bin
  3. Execute this command: oplmgr +reload

Unix

  1. Open a Unix terminal.
  2. Navigate to the root of your OpenLink UDA or Virtuoso installation.
  3. Use one of the following scripts to set Virtuoso-related environment variables:
    • bash, bourne, korn shells - openlink.sh
    • C shells - openlink.csh
    • bash, bourne, korn shells - virtuoso-enterprise.sh
    • C shells - virtuoso-enterprise.csh
  4. Set and export an OPL_LICENSE_DIR variable that passes the path to the directory that contains your OpenLink UDA or Virtuoso license.
  5. Navigate to the bin sub-directory of the OpenLink installation.
  6. Execute this command: oplmgr +reload

Windows

  1. Login to Windows.
  2. Open the Services or Component Services utility that resides in the Control Panel or its Administrative Tools sub-folder.
  3. Locate the OpenLink License Manager process.
  4. Highlight the OpenLink License Manager process.
  5. Click the Restart icon.


Additional Usage Notes

The license manager accepts the command-line options shown below on all platforms. Any unrecognized command-line arguments will produce this output, including "--help" and "-?".

bash$ oplmgr --help
OpenLink License Manager
Version 1.2.2 as of Thu Feb 15 2007 (Release 6.0 cvsid 00084).
Compiled for Linux 2.4.20-46.9.legacysmp (i686-generic-linux-glibc23-32)
Copyright (C) OpenLink Software.

Usage:
oplmgr [-shrutp] [+start] [+stop] [+reload] [+user arg] [+chroot arg] [+pidfile arg]
+start     start the license manager
+stop      stop the license manager
+reload    force a configuration reload
+user      run as the specified user
+chroot    perform a chroot to the specified directory
+pidfile   pid file to use for server operation


Related Documentation