OpenLink Software Support Page
- Applying UDA Licenses
- Single-Tier (Express Edition)
- Single-Tier (Lite Edition)
- Release 6.x
- Apply 6.x Lite Edition License Files on Mac OS X
- Apply 6.x Lite Edition License Files on Unix
- Apply 6.x Lite Edition License Files on Windows
- Releases 4.x-5.x
- Apply 4.x-5.x Lite Edition License Files on Mac OS X
- Apply 4.x-5.x Lite Edition License Files on Unix
- Apply 4.x-5.x Lite Edition License Files on Windows
- Releases 1.x-3.x
- Multi-Tier Edition
- Release 6.x
- Apply 6.x Multi-Tier License Files on Mac OS X
- Apply 6.x Multi-Tier License Files on Unix
- Apply 6.x Multi-Tier License Files on Windows
- Releases 4.x-5.x
- Apply 4.x-5.x Multi-Tier License Files on Mac OS X
- Apply 4.x-5.x Multi-Tier License Files on Unix
- Apply 4.x-5.x License Files on Windows
- Releases 1.x-3.x
Applying UDA Licenses
Single-Tier (Express Edition)
Release 6.x
Apply 6.x Express Edition License Files on Mac OS X
- Launch Terminal.app (/Applications/Utilities/).
- Run these commands:
cd "/Library/Application Support/openlink/bin" oplmgr +stop
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Replace the old license file with the new license file. You can rename or move the old file, if you think you may need to revert to it.
- Go back to Terminal.app.
- Execute this command
./oplmgr +start
- Test your connection.
Apply 6.x Express Edition License Files on Windows
- Launch the Services or Component Services utility (Start menu >> Control Panels >> Administrative Tools).
- Locate the OpenLink License Manager service.
- Stop the OpenLink License Manager service.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Replace the old license file with the new license file. You can rename or move the old file, if you think you may need to revert to it.
- Go back to the Services utility.
- Restart the OpenLink License Manager.
- Test your connection.
Single-Tier (Lite Edition)
Release 6.x
Apply 6.x Lite Edition License Files on Mac OS X
- Launch Terminal.app (/Applications/Utilities/).
- Run these commands:
cd "/Library/Application Support/openlink/bin" oplmgr +stop
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Replace the old license file with the new license file. You can rename or move the old file, if you think you may need to revert to it.
- Go back to Terminal.app.
- Execute this command
./oplmgr +start
- Test your connection.
Apply 6.x Lite Edition License Files on Unix
- cd into the root of your OpenLink installation.
- Use the bash or sh command to open a bash or Bourne shell.
- Execute this command: . ./openlink.sh
- cd into the bin sub-directory of the OpenLink installation.
- Execute this command: ./oplmgr +stop
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Use binary ftp to transer the new license to the Unix box, if required.
- Place the new license in the bin sub-directory of the OpenLink installation.
- Use the export command to set an OPL LICENSE_DIR variable that points to this directory.
For example:
export OPL_LICENSE_DIR=/usr/openlink/bin
- Execute this command: oplmgr +start
Apply 6.x Lite Edition License Files on Windows
- Expand the Start menu.
- Click the Control Panel icon.
- Open the Administrative Tools folder.
- Launch the Services utility.
- Locate the OpenLink License Manager service.
- Stop the OpenLink License Manager service.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license file with the new license file.
- Go back to the Services utility.
- Restart the OpenLink License Manager.
Releases 4.x-5.x
Apply 4.x-5.x Lite Edition License Files on Mac OS X
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license file with the new license file.
Apply 4.x-5.x Lite Edition License Files on Unix
- cd into the root of your OpenLink installation.
- Use the bash or sh command to open a bash or Bourne shell.
- Execute this command: . ./openlink.sh
- cd into the bin sub-directory of the OpenLink installation.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Use binary ftp to transer the new license to the Unix box, if required.
- Place the new license in the bin sub-directory of the OpenLink installation.
- Use the export command to set an OPL LICENSE_DIR variable that points to this directory.
For example:
export OPL_LICENSE_DIR=/usr/openlink/bin
- Open a client application.
- Test a connection to initialize the terms of the new license.
Apply 4.x-5.x Lite Edition License Files on Windows
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license file with the new license file.
Releases 1.x-3.x
Apply 1.x-3.x Lite Edition License Files on Windows
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Save the file to the bin sub-directory of your OpenLink server components installation.
- Expand the Start menu.
- Click the My Computer icon.
- Navigate into the bin sub-directory of the OpenLink installation.
- Double Click the RegKey icon.
- Use the RegKey program's Directory Explorer to identify the OpenLink license.
- Hit Enter.
- Follow the on screen instructions presented by the RegKey dialog.
Multi-Tier Edition
Release 6.x
Apply 6.x Multi-Tier License Files on Mac OS X
- Open your Finder.
- Click the Applications icon.
- Expand the Utilities menu tree.
- Double Click the Termina*l icon.
- cd into the /Library/Application Support/openlink/bin directory.
- Run this command: oplmgr +stop
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license with the new license.
- Go back to the Terminal.
- Execute this command: ./oplmgr +start
Apply 6.x Multi-Tier License Files on Unix
- cd into the root of your OpenLink installation.
- Use the bash or sh command to open a bash or Bourne shell.
- Execute this command: . ./openlink.sh
- cd into the bin sub-directory of the OpenLink installation.
- Execute this command: ./oplmgr +stop
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Use binary ftp to transer the new license to the Unix box, if required.
- Place the new license in the bin sub-directory of the OpenLink installation.
- Use the export command to set an OPL LICENSE_DIR variable that points to this directory.
For example:
export OPL_LICENSE_DIR=/usr/openlink/bin
- Execute this command: oplmgr +start
Apply 6.x Multi-Tier License Files on Windows
- Expand the Start menu.
- Click the Control Panel icon.
- Open the Administrative Tools folder.
- Launch the Services utility.
- Locate the OpenLink License Manager service.
- Stop the OpenLink License Manager service.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license file with the new license file.
- Go back to the Services utility.
- Restart the OpenLink License Manager.
Releases 4.x-5.x
Apply 4.x-5.x Multi-Tier License Files on Mac OS X
- Open your Finder.
- Click the Applications icon.
- Expand the Utilities menu tree.
- Double Click the Terminal icon.
- cd into the /Library/Application Support/openlink/bin directory.
- Run this command: oplshut -fy
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license with the new license.
- Go back to the Terminal.
- Execute this command: oplrqb
Apply 4.x-5.x Multi-Tier License Files on Unix
- cd into the root of your OpenLink installation.
- Use the bash or sh command to open a bash or Bourne shell.
- Execute this command: . ./openlink.sh
- cd into the bin sub-directory of the OpenLink installation.
- Execute this command: ./oplshut -fy
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Use binary ftp to transer the new license to the Unix box, if required.
- Place the new license in the bin sub-directory of the OpenLink installation.
- Use the export command to set an OPL LICENSE_DIR variable that points to this directory.
For example:
export OPL_LICENSE_DIR=/usr/openlink/bin
- Execute this command: oplrqb
Apply 4.x-5.x License Files on Windows
- Expand the Start menu.
- Click the Control Panel icon.
- Open the Administrative Tools folder.
- Launch the Services utility.
- Locate the OpenLink Request Broker service.
- Stop the OpenLink Request Broker service.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Over-write the old license file with the new license file.
- Go back to the Services utility.
- Restart the OpenLink Request Broker.
Releases 1.x-3.x
Apply 1.x-3.x Multi-Tier License Files on Unix
- cd into the root of your OpenLink installation.
- Use the bash or sh command to open a bash or Bourne shell.
- Execute this command: . ./openlink.sh
- cd into the bin sub-directory of the OpenLink installation.
- Execute this command: ./oplshut -fy
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Use binary ftp to transer the new license to the Unix box, if required.
- Place the new license in the bin sub-directory of the OpenLink installation.
- Rename the license file register.ini.
For example:
mv 5641.ini register.ini
- Execute this command: ./oplshut -fy
- Execute this command: ./register.ini
- Execute this command: ./oplrqb
Apply 1.x-3.x Multi-Tier License Files on Windows
- Expand the Start menu.
- Click the Control Panel icon.
- Open the Administrative Tools folder.
- Launch the Services utility.
- Locate the OpenLink Request Broker service.
- Stop the OpenLink Request Broker service.
- Retrieve your new OpenLink license file from an email or ODS Briefcase.
- Save the file to the Desktop.
- Rename the file register.ini.
- Move register.ini to the bin sub-directory of the OpenLink installation.
- Open an MS-DOS command prompt.
- cd into the bin sub-directory of the OpenLink installation.
- Run this command: register
- Exit the MS-DOS command prompt.
- Go back to the Services utility.
- Restart the OpenLink Request Broker.
CategoryLicensing CategorySupport CategoryDocumentation