Contents

Important information for Charon-PAR software upgrades:

• Upgrading to this Charon-PAR from an older version requires a license update (independent of license type used). Please contact your VAR or Stromasys representative to plan the update.
• Applicable to HASP licenses only: Charon-PAR version 3.0 and higher is incompatible with licenses of earlier versions. Earlier product versions are incompatible with licenses for Charon-PAR 3.0 and higher. Charon-PAR/PA3 licenses for version 3.0 are not backward compatible for emulators running with version 2.x.

Charon-PAR Software Packaging and Installation

The Charon-PAR software can be provided in different formats. At the time of writing, the following software packaging was available:

• A set of RPM packages for installations on all supported platforms and environments.
• A marketplace AMI containing the base operating system and the preinstalled Charon-PAR software. At the time of writing, this format was planned for AWS (starting with Charon-PAR 3.0.6). Please contact your Stromasys representative for details about availability on AWS and other cloud platforms.

Installing Charon-PAR from RPM Installation Packages

Charon-PAR RPM Software Packages Overview

Charon-PAR is provided as a set of RPM-packages.

The following table lists the required installation packages (the placeholder <version> denotes the version of the package, for example, 3.0.6):

Please note: the VE license server RPM package is not part of the Charon-PAR set of RPM packages. Stromasys or your Stromasys VAR will provide you with the software or a download link.

Important if there is more than one emulator product installed on the same Charon host system: the Charon-PAR version 3.0 and higher emulator kits contain the haspvlib library and the hasp_srm_view and hasp_update utilities. This means that there may be installation conflicts with other Charon emulator products on the same host systems. Such conflicts can be overcome either by not installing the conflicting modules of the other products (if possible), or by forcing the installation of the Charon-PAR kit. Please refer to the documentation of your host system (man rpm) in such cases and ensure that this will not negatively influence any other installed products. If you use the --force option for an installation, please uninstall older packages of the same product before.

Obtaining the Charon-PAR software:

The software can be downloaded from the Stromasys fileserver. If required, please contact your Stromasys representative or your VAR partner. They will provide the download information or the software packages to you.

Additional requirements for a successful installation:

• The packages above have installation dependencies that are normally satisfied automatically from the standard software repositories when installing packages with yum or dnf. If the standard repositories are not available, please refer to How to install the glibc.i686 package without an Internet connection. The document explains - among other points - how to create a local repository.
• Additional packages may be required to be installed on the host operating system. They will be discussed in the sections where they are relevant.
• If additionally required packages are not available in the standard repositories of the host operating system, additional repositories can be installed using, for example, the EPEL repository (more information: https://fedoraproject.org/wiki/EPEL).

Additional requirements for initial emulator setup:

• For the installation of a Charon-PAR/PA3 emulated system, a preinstalled MPE/iX 7.5 disk image (mpe75a.dsk.bz2) is required. This will be provided by Stromasys.
• For the installation of a Charon-PAR/PA9 emulated system, a HP-UX ISO is required. It must be provided by the customer.

Charon-PAR RPM Installation Command Overview

The following table provides an overview of the installation commands for the supported host operating systems. For details, please refer to the relevant man-pages on Linux. The table only lists command-line installation options for Linux. There are also graphical installation tools. To describe all of them is outside the scope of this document.

Sentinel Runtime RPM Installation

This package is a prerequisite for the Charon-PAR emulator package. So it must be installed. However, the runtime software installed is only needed for HASP licensing. It is not relevant for VE licensing.

Important points:

• The aksusbd package version 7.63 requires the 32-bit glibc-library. On supported Linux distributions, this library is available through the standard repositories. The relevant package is glibc.i686 on Red Hat Enterprise Linux and CentOS. Unless version 7.63 is needed to solve a specific problem, aksusbd version 8.13 which does not have this limitation should be used.
• Normally, the aksusbd package installation with yum or dnf installs the 32-bit glibc and other dependency automatically (provided package repositories are available). Red Hat Enterprise must be registered to access the Red Hat repositories, or the installation CD must be mounted. Should the Charon host system not have access to the Internet, please refer to How to install the glibc.i686 package without an Internet connection for further information.
• When installing the aksusbd package version 8.13 in some CentOS 7.x environments it was observed that the aksusbd service did not start automatically after a new installation or an upgrade. The following error was displayed during the installation: Failed to restart aksusbd.service: Access denied. If this happens, uninstall the aksusbd package and reboot the system. After rebooting the system, re-install the package. The cause of this sporadic problem has not yet been identified.

The aksusbd package installs the programs aksusbd and hasplmd in /usr/sbin.

The example below shows the installation of the aksusbd package (version 8.13):

# dnf install aksusbd-8.13-1.x86_64.rpm 
Last metadata expiration check: 0:59:01 ago on Mi 18 Mai 2022 15:16:11 CEST.
Dependencies resolved.
================================================================================
 Package          Architecture    Version           Repository             Size
================================================================================
Installing:
 aksusbd          x86_64          8.13-1            @commandline          7.1 M

Transaction Summary
================================================================================
Install  1 Package

Total size: 7.1 M
Installed size: 14 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Running scriptlet: aksusbd-8.13-1.x86_64                                  1/1 
  Installing       : aksusbd-8.13-1.x86_64                                  1/1 
  Running scriptlet: aksusbd-8.13-1.x86_64                                  1/1 
Created symlink /etc/systemd/system/multi-user.target.wants/aksusbd.service → /etc/systemd/system/aksusbd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/hasplmd.service → /etc/systemd/system/hasplmd.service.

  Verifying        : aksusbd-8.13-1.x86_64                                  1/1 

Installed:
  aksusbd-8.13-1.x86_64                                                         

Complete!

Installing the Charon-PAR RPM Packages

To install the Charon-PAR packages perform the following steps:

The following shows a sample installation of the Charon-PAR emulator package on CentOS 8:

# dnf install charon-par-3.0.0-21400.ed1d4d8.el8.x86_64.rpm
Last metadata expiration check: 1:27:20 ago on Wed 29 Jul 2020 07:39:18 PM CEST.
Dependencies resolved.
================================================================================
 Package        Arch       Version                       Repository        Size
================================================================================
Installing:
 charon-par     x86_64     3.0.0-21400.ed1d4d8.el8       @commandline     6.0 M

Transaction Summary
================================================================================
Install  1 Package

Total size: 6.0 M
Installed size: 32 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Running scriptlet: charon-par-3.0.0-21400.ed1d4d8.el8.x86_64              1/1 
  Installing       : charon-par-3.0.0-21400.ed1d4d8.el8.x86_64              1/1 
  Running scriptlet: charon-par-3.0.0-21400.ed1d4d8.el8.x86_64              1/1 
  Verifying        : charon-par-3.0.0-21400.ed1d4d8.el8.x86_64              1/1 
Installed products updated.

Installed:
  charon-par-3.0.0-21400.ed1d4d8.el8.x86_64                                     

Complete!

Location of Charon-PAR Files

Charon-PAR is installed under /opt/charon.

• /opt/charon/bin: executable of emulator and utilities
• /opt/charon/cfg: template configuration files for emulated systems and PuTTY session definitions (to connect to the emulated console).
• /opt/charon/doc: license agreement and Release Notes (WHATSNEW file)

To add the installation path to your PATH variable, become the root user and create the file /etc/profile.d/charon.sh with the following content:

PATH=$PATH:/opt/charon/bin; export PATH

The updated PATH variable will become active after the next login. You can also execute this command directly: # . /etc/profile.d/charon.sh

Cloud-specific marketplace images can be used to launch a Charon-PAR host instance in a cloud instead of installing the RPM packages on a Linux instance in the cloud. Marketplace images contain the following software:

• The underlying Linux operating system.
• The preinstalled Charon emulator product.
• Utilities required by the emulator product.

For further information, please refer to the cloud-specific Getting Started Guide of your product.

At the time of writing, such a marketplace image was planned for AWS. Please contact your Stromasys representative with any questions regarding availability.