Mac OS X OpenLink License Manager Usage Notes

The default and suggested locations of OpenLink License files varies depending on the operating system in use and License Manager version.

Determining the Installed Version of the License Manager

The License Manager (oplmgr) version can be determined with the command oplmgr -? .

oplmgr -?
OpenLink License Manager
Version 1.3.6 as of Fri Nov 15 2013 (Release 6.3, g127d4a9)
Compiled for Mac OS X 11.4.2 (x86_64-apple-macosx10.7)
Copyright (C) 1993-2013 OpenLink Software.

Usage:
  oplmgr [-shrdupf] [+start] [+stop] [+reload] [+directory arg] [+user arg]
         [+pidfile arg] [+foreground]
  +start        start the license manager
  +stop         stop the license manager
  +reload       force a configuration reload
  +directory    where to look for licenses (default .)
  +user         run as the specified user
  +pidfile      pid file to use for server operation
  +foreground   run in the foreground

Version 1.3.6 or higher uses the new +directory parameter option for the oplmgr program to specify the location license files should be found.

$ bin/oplmgr -?
OpenLink License Manager
Version 1.3.5 as of Mon Jul 02 2012 (Release 6.3 cvsid 00096).
Compiled for Mac OS X 11.4.2 (x86_64-apple-macosx10.7)
Copyright (C) 1993-2012 OpenLink Software.

Usage:
  oplmgr [-shrutpf] [+start] [+stop] [+reload] [+user arg] [+chroot arg]
         [+pidfile arg] [+foreground]
  +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
  +foreground   run in the foreground

Version 1.3.5 and previous used the OPL_LICENSE_DIR environment variable to locate the license file directory(ies).

Location of License files

License Manager version 1.3.6 and later (UDA Release 6.3 and later)

• Default License Folder:
  
  

  
  /Library/Application Support/openlink/Licenses/
  

  
  
  
• Discovery sequence: only the directory(ies) specified with the +directory or -d option, or the single default diretory, . a/k/a the oplmgr's pwd, will be checked.

If you choose to situate your license files in an alternative location, you can restart the license manager using the new +directory option which is used to identify the folder into which your license files have been placed. Note: If you use an alternate location, you will also need to edit the startup script, /Library/LaunchDaemons/com.openlinksw.oplmgr.plist, to target the new location.

Unlike previous versions, License Manager (oplmgr) version 1.3.6 and higher will search only the directory(ies) specified with the +directory or -d option.

The OpenLink installer places an automatic start-up script on Mac OS X machines, /Library/LaunchDaemons/com.openlinksw.oplmgr.plist such that the License Manager is always started on boot. The License Manager can also be started and stopped manually using the "oplmgr +[start | stop]" Terminal.app commands.

See the following note on Special Guidance for Mac OS X

License Manager version 1.3.5 and earlier (UDA Release 6.3 and earlier)

• Default License Folder:
  
  

  
  /Library/Application Support/openlink/bin/
  

  
  
  
• Discovery sequence: Default Folder and then any folder exposed by $OPL_LICENSE_DIR environment variable.

Versions 1.3.5 or lower of the OpenLink License Manager (oplmgr) will always search the default /Library/Application Support/openlink/bin/ folder before any others.

The OpenLink installer places an automatic start-up script on Mac OS X machines, such that the License Manager is always started on boot. The License Manager can also be started and stopped manually using the "oplmgr +[start | stop]" Terminal.app commands.

See the following note on Special Guidance for Mac OS X

Related Documentation

• Firewall Considerations for Multi-Tier "Enterprise" Edition Data Access Drivers
  
• Configuring Server-side Firewalls for Multi-Tier Connectivity
  
• OpenLink License Manager Networking Considerations
  
• Configure Multi-Tier Request Broker for Use on Machines with Multiple Network Cards
  
• Start the License Manager Process