• Topic
  • Discussion
  • SupportWeb.LicenseApplyingLicenseFiles(Last) -- Owiki? , 2016-08-19 14:59:28 Edit owiki 2016-08-19 14:59:28

    OpenLink Software Support Page

    Applying UDA Licenses

    Single-Tier (Express Edition)

    Release 6.x

    Apply 6.x Express Edition License Files on Mac OS X
    1. Launch Terminal.app (/Applications/Utilities/).
    2. Run these commands:

      cd "/Library/Application Support/openlink/bin" oplmgr +stop

    3. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    4. 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.
    5. Go back to Terminal.app.
    6. Execute this command

      ./oplmgr +start

    7. Test your connection.
    Apply 6.x Express Edition License Files on Windows
    1. Launch the Services or Component Services utility (Start menu >> Control Panels >> Administrative Tools).
    2. Locate the OpenLink License Manager service.
    3. Stop the OpenLink License Manager service.
    4. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    5. 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.
    6. Go back to the Services utility.
    7. Restart the OpenLink License Manager.
    8. Test your connection.

    Single-Tier (Lite Edition)

    Release 6.x

    Apply 6.x Lite Edition License Files on Mac OS X
    1. Launch Terminal.app (/Applications/Utilities/).
    2. Run these commands:

      cd "/Library/Application Support/openlink/bin" oplmgr +stop

    3. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    4. 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.
    5. Go back to Terminal.app.
    6. Execute this command

      ./oplmgr +start

    7. Test your connection.
    Apply 6.x Lite Edition License Files on Unix
    1. cd into the root of your OpenLink installation.
    2. Use the bash or sh command to open a bash or Bourne shell.
    3. Execute this command: . ./openlink.sh
    4. cd into the bin sub-directory of the OpenLink installation.
    5. Execute this command: ./oplmgr +stop
    6. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    7. Use binary ftp to transer the new license to the Unix box, if required.
    8. Place the new license in the bin sub-directory of the OpenLink installation.
    9. 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

    10. Execute this command: oplmgr +start
    Apply 6.x Lite Edition License Files on Windows
    1. Expand the Start menu.
    2. Click the Control Panel icon.
    3. Open the Administrative Tools folder.
    4. Launch the Services utility.
    5. Locate the OpenLink License Manager service.
    6. Stop the OpenLink License Manager service.
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Over-write the old license file with the new license file.
    9. Go back to the Services utility.
    10. Restart the OpenLink License Manager.

    Releases 4.x-5.x

    Apply 4.x-5.x Lite Edition License Files on Mac OS X
    1. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    2. Over-write the old license file with the new license file.
    Apply 4.x-5.x Lite Edition License Files on Unix
    1. cd into the root of your OpenLink installation.
    2. Use the bash or sh command to open a bash or Bourne shell.
    3. Execute this command: . ./openlink.sh
    4. cd into the bin sub-directory of the OpenLink installation.
    5. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    6. Use binary ftp to transer the new license to the Unix box, if required.
    7. Place the new license in the bin sub-directory of the OpenLink installation.
    8. 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

    9. Open a client application.
    10. Test a connection to initialize the terms of the new license.
    Apply 4.x-5.x Lite Edition License Files on Windows
    1. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    2. 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
    1. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    2. Save the file to the bin sub-directory of your OpenLink server components installation.
    3. Expand the Start menu.
    4. Click the My Computer icon.
    5. Navigate into the bin sub-directory of the OpenLink installation.
    6. Double Click the RegKey icon.
    7. Use the RegKey program's Directory Explorer to identify the OpenLink license.
    8. Hit Enter.
    9. 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
    1. Open your Finder.
    2. Click the Applications icon.
    3. Expand the Utilities menu tree.
    4. Double Click the Termina*l icon.
    5. cd into the /Library/Application Support/openlink/bin directory.
    6. Run this command: oplmgr +stop
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Over-write the old license with the new license.
    9. Go back to the Terminal.
    10. Execute this command: ./oplmgr +start
    Apply 6.x Multi-Tier License Files on Unix
    1. cd into the root of your OpenLink installation.
    2. Use the bash or sh command to open a bash or Bourne shell.
    3. Execute this command: . ./openlink.sh
    4. cd into the bin sub-directory of the OpenLink installation.
    5. Execute this command: ./oplmgr +stop
    6. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    7. Use binary ftp to transer the new license to the Unix box, if required.
    8. Place the new license in the bin sub-directory of the OpenLink installation.
    9. 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

    10. Execute this command: oplmgr +start
    Apply 6.x Multi-Tier License Files on Windows
    1. Expand the Start menu.
    2. Click the Control Panel icon.
    3. Open the Administrative Tools folder.
    4. Launch the Services utility.
    5. Locate the OpenLink License Manager service.
    6. Stop the OpenLink License Manager service.
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Over-write the old license file with the new license file.
    9. Go back to the Services utility.
    10. Restart the OpenLink License Manager.

    Releases 4.x-5.x

    Apply 4.x-5.x Multi-Tier License Files on Mac OS X
    1. Open your Finder.
    2. Click the Applications icon.
    3. Expand the Utilities menu tree.
    4. Double Click the Terminal icon.
    5. cd into the /Library/Application Support/openlink/bin directory.
    6. Run this command: oplshut -fy
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Over-write the old license with the new license.
    9. Go back to the Terminal.
    10. Execute this command: oplrqb
    Apply 4.x-5.x Multi-Tier License Files on Unix
    1. cd into the root of your OpenLink installation.
    2. Use the bash or sh command to open a bash or Bourne shell.
    3. Execute this command: . ./openlink.sh
    4. cd into the bin sub-directory of the OpenLink installation.
    5. Execute this command: ./oplshut -fy
    6. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    7. Use binary ftp to transer the new license to the Unix box, if required.
    8. Place the new license in the bin sub-directory of the OpenLink installation.
    9. 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

    10. Execute this command: oplrqb
    Apply 4.x-5.x License Files on Windows
    1. Expand the Start menu.
    2. Click the Control Panel icon.
    3. Open the Administrative Tools folder.
    4. Launch the Services utility.
    5. Locate the OpenLink Request Broker service.
    6. Stop the OpenLink Request Broker service.
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Over-write the old license file with the new license file.
    9. Go back to the Services utility.
    10. Restart the OpenLink Request Broker.

    Releases 1.x-3.x

    Apply 1.x-3.x Multi-Tier License Files on Unix
    1. cd into the root of your OpenLink installation.
    2. Use the bash or sh command to open a bash or Bourne shell.
    3. Execute this command: . ./openlink.sh
    4. cd into the bin sub-directory of the OpenLink installation.
    5. Execute this command: ./oplshut -fy
    6. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    7. Use binary ftp to transer the new license to the Unix box, if required.
    8. Place the new license in the bin sub-directory of the OpenLink installation.
    9. Rename the license file register.ini. For example:

      mv 5641.ini register.ini

    10. Execute this command: ./oplshut -fy
    11. Execute this command: ./register.ini
    12. Execute this command: ./oplrqb
    Apply 1.x-3.x Multi-Tier License Files on Windows
    1. Expand the Start menu.
    2. Click the Control Panel icon.
    3. Open the Administrative Tools folder.
    4. Launch the Services utility.
    5. Locate the OpenLink Request Broker service.
    6. Stop the OpenLink Request Broker service.
    7. Retrieve your new OpenLink license file from an email or ODS Briefcase.
    8. Save the file to the Desktop.
    9. Rename the file register.ini.
    10. Move register.ini to the bin sub-directory of the OpenLink installation.
    11. Open an MS-DOS command prompt.
    12. cd into the bin sub-directory of the OpenLink installation.
    13. Run this command: register
    14. Exit the MS-DOS command prompt.
    15. Go back to the Services utility.
    16. Restart the OpenLink Request Broker.

    CategoryLicensing CategorySupport CategoryDocumentation