Page Comparison

...

• If you are not familiar with the installation of RPM packages, please refer to the regular user's guide or your Linux system documentation.
• You do not need to stop running emulator instance before upgrading the license server.
• Please refer to the general Charon user's guide for information on how to upgrade the Charon emulator software.
• If the old license server was uninstalled before installing the new version (instead of performing an upgrade), the license (V2C file) must be imported again using the v2c utility.

To upgrade the license server package, perform the following steps (SFTP is used as a sample file transfer method):

...

In the description below, the placeholders used have the following meaning:

• <mykey> is the private key of the key-pair you associated with your cloud instance
  (

...

• for an on-premises VMware

...

• installation or an installation on a physical system where logging in with username/password is allowed, this is not needed).
• <user> is the user associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user

...

• on your VMware virtual machine;
  for an instance installed from a

...

• Stromasys-provided Charon AL or VE emulator marketplace image, use

...

• user charon for SFTP

...

• and user sshuser for interactive login.
• <linux-ip> is the ip address of your license server system.
  

Perform the following steps to install the VE License Server software:

1. Copy the license server software package to the license server host (if needed):
   
   1. For example, use sftp to connect to the VE license server system.
      # sftp -i ~/.ssh/<mykey>  <user>@<linux-ip>
   2. Copy the software package to the license server system using the following
   sftp
   1. SFTP command:
      > put <local-path-to-license-server-package>


2. Use ssh to log in on the license server systemhost.
   # ssh-i ~/.ssh/<mykey> <user>@<linux-ip>
3. <mykey> is the private key of the key-pair you associated with your cloud instance
   (not needed for on-premises VMware installations that allow logins with username/password)
<user> is the user for interactive login associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user of your VMware virtual machine;
for an instance installed from a prepackaged, Stromasys-provided Charon AL or VE emulator marketplace image, use sshuser).<linux-ip> the ip address of your license server system


4. As a privileged user (root) go to the directory where you stored the installation package and update the package. If you used the VE image and copied the file using SFTP to user charon, the file will be in the hierarchy under /charon/storage.install the package:
   1. Become the root user:          # sudo -i
   2. Go to the package location:     # cd <path-to-package-directory>
If you used SFTP to copy the package to an instance installed from a prepackaged Charon marketplace image, the home directory of the charon user and the default location for file transfers is /charon/storage.
   3. For VE license server 2.2.4 and above, unpack the archive and agree to the end-user license agreement:
      
      1. # chmod a+x license-server-<version>.rpm.sh
      2. # ./license-server-<version>.rpm.sh
         This will display the EULA. After agreeing to it, the RPM installation package will be unpacked in the current directory.
   4. Install the package:             
      1. Linux 7.x: # yum update license-server*.rpm
      2. Linux 8.x and 9.x: # dnf update license-server*.rpm

Normally, the license server will restart and continue to work normally. To check the status, perform the following steps:

• Look at Review the content of the license server log: /opt/license-server/log/license.log
• Use the ps command to check that the server is running:
  # ps -ef |grep license-server
• Starting with version 1.1.18, a new parameter to the license server is available to display the license server status:
  # cd /opt/license-server
# ./license_server -s

...