...
- If the license server is combined with the Charon-SSP emulator software on the same instance, the instance used must satisfy the requirements of the Charon-SSP host and all instances that will run on it. If this requirement exists, please refer to the your Charon-SSP user's guide for details.
Additional general requirements:
- In the AWS cloud, an IAM role allowing the ListUsers action (IAMReadOnlyAccess in the example below) must be attached to the instance. This can be done during the launch of the instance as shown in the sample below.
Alternatively, the role can be set/changed by selecting the instance, right-clicking on it, and selecting Instance Settings Security > Modify IAM Role (in the older AWS console, use the Action menu). If such a role has not yet been defined, please refer to Creating and Attaching an AWS IAM Role and to the documentation provided by AWS for additional information.
...
The VE license server software requires matching Charon-SSP emulator software. The necessary features are available in Charon-SSP 4.2.x and its pre-releaseslater. Stromasys or your Stromasys VAR will provide you with the software or a download link. In certain cloud environments, Stromasys may offer a prepackaged Charon-SSP VE image on the cloud marketplace. This image includes the Charon-SSP emulator software (already installed) and the VE License Server RPM package (can be installed optionally). If you use a Charon host in the cloud and the instance was launched from such a prepackaged image, the required VE-capable emulator software is already installed (refer to the respective cloud-specific Getting Started Guide for more information).
Please note: The protocol versions used by the emulator software and the license server must be compatible. The software checks for compatible protocol versions and and reports an error should there be a mismatch.
...
- Management components (not VE-specific):
- charon-agent-ssp-<version>-x86_64.rpm
- charon-director-ssp-<version>.rpm
- charon-manager-ssp-<version>.rpm
- VE-capable emulator software:
- charon-ssp-<architecture>-<version>.ve.el7-x86_64.rpm
- charon-ssp-<architecture>-<version>.ve.el8-x86_64.rpm
In the above list, the parameters placeholders have the following meaning:
- <version> indicates the software version (e.g., 4.2.25).
- <architecture> indicates the type of emulated SPARC covered by the software (currently it can have the values 4m, 4u, 4v, 4u+, or 4v+).
- The string ve in the package containing the Charon emulator software indicates that this version of the emulator requires a VE license server.
- The string el7 denotes packages intended for Red Hat/CentOS/Oracle Linux 7.x.
- The string el8 denotes packages intended for Red Hat/CentOS/Oracle Linux 8.x.
- Charon Agent, Manager, and Director are not license-model specific.
...
- Copy the license server software package to the cloud instance (if still required):
- Use sftp to connect to the cloud instance.
# sftp -i ~/.ssh/<mykey><user>@<cloud-instance-ip>
where- <mykey> is the private key of the key-pair you associated with your cloud instance
- <user> is the user associated with your cloud instance (e.g., opc on OCI, or centos for a CentOS instance on AWS; for an instance installed from a prepackaged Charon-SSP VE image, use the SFTP user charon)
- <cloud-instance-ip> the ip address of your cloud instance
- Copy the software package to the cloud instance using the following sftp command:
> put <local-path-to-license-server-package>
- Use sftp to connect to the cloud instance.
- Use ssh to log in on the cloud instance.
# ssh-i ~/.ssh/<mykey> <user>@<cloud-instance-ip>- <mykey> is the private key of the key-pair you associated with your cloud instance
- <user> is the user for interactive login associated with your cloud instance (e.g., opc on OCI, or centos for a CentOS instance on AWS; for an instance installed from a prepackaged Charon-SSP VE image, use sshuser)
- <cloud-instance-ip> the ip address of your cloud instance
- As a privileged user (root) go to the directory where you stored the installation package and install the package:
- Become the root user:
# sudo -i - Go to the package location:
# cd <path-to-package-directory>On an instance installed from a prepackaged Charon-SSP VE image, the installation package is stored under /charon/storage) - Install the package:
- Linux 7.x:
# yum install license-server*.rpm - Linux 8.x:
# dnf install license-server*.rpm
- Linux 7.x:
- Become the root user:
...
| Code Block | ||
|---|---|---|
| ||
# yum install charon*.rpm (lines removed) Resolving Dependencies --> Running transaction check (lines removed) Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: charon-agent-ssp x86_64 4.2.35-1 /charon-agent-ssp-4.2.35-x86_64 32 M charon-director-ssp x86_64 4.2.35-1 /charon-director-ssp-4.2.35 287 k charon-manager-ssp x86_64 4.2.35-1 /charon-manager-ssp-4.2.35 5.8 M charon-ssp-4m x86_64 4.2.35.ve.el7-1 /charon-ssp-4m-4.2.35.ve.el7-x86_64 6.1 M charon-ssp-4u+ x86_64 4.2.35.ve.el7-1 /charon-ssp-4u+-4.2.35.ve.el7-x86_64 54 M charon-ssp-4v+ x86_64 4.2.35.ve.el7-1 /charon-ssp-4v+-4.2.35.ve.el7-x86_64 54 M Installing for dependencies: (lines removed) Transaction Summary ================================================================================ Install 6 Packages (+32 Dependent packages) Total size: 161 M Total download size: 8.9 M Installed size: 183 M Is this ok [y/d/N]: y Downloading packages: (lines removed) Running transaction check Running transaction test Transaction test succeeded Running transaction (lines removed) Installed: charon-agent-ssp.x86_64 0:4.2.35-1 charon-director-ssp.x86_64 0:4.2.35-1 charon-manager-ssp.x86_64 0:4.2.35-1 charon-ssp-4m.x86_64 0:4.2.35.ve.el7-1 charon-ssp-4u+.x86_64 0:4.2.35.ve.el7-1 charon-ssp-4v+.x86_64 0:4.2.35.ve.el7-1 (lines removed) Complete! |
...