Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Multiexcerpt include
MultiExcerptNameInstallPhaseGraphic
PageWithExcerptInstalling and upgrading

Summary

Excerpt

Guidance for deploying the 1E Client onto Red Hat Enterprise Linux devices, including installation and uninstallation. Only the Tachyon features of 1E Client are available on Linux and other non-Windows OS.

Requirements

Multiexcerpt include
MultiExcerptNamePrereqIntro
PageWithExcerptDeploying 1E Client on Windows

Guidance provided below is for installation on Red Hat Enterprise.

Multiexcerpt include
MultiExcerptNameCommonRequirements
PageWithExcerptDeploying 1E Client on Windows

Deployment choices

Multiexcerpt include
MultiExcerptNameDeployment Choices
PageWithExcerptDeploying 1E Client on Windows

Deploying the 1E Client is normally achieved using your existing software deployment tool.

Non-Windows installation account

Multiexcerpt include
MultiExcerptNameTachyonNonWindowsInstallationAccount1EClientNonWindowsInstallationAccount
PageWithExcerptDeploying 1E Client on macOSCommon client requirements

Certificate files

Each Tachyon client device requires a .pfx certificate file. Please refer to Client certificates below, for steps to create and use the .pfx file.

For Linux devices, the Tachyon client does not use proprietary certificate stores. Instead, the client requires the certificate exists as a .PFX file in the client installation folder structure.

Multiexcerpt include
MultiExcerptNameClient_Certificate_Requirements
PageWithExcerptTachyon client requirements


Advanced Panelboxes for Confluence
namegrey
titleOn this page:

Table of Contents
maxLevel3
minLevel2
indent20px
excludeSummary|On this page|In this section...
separatornewline


Preparation

Multiexcerpt include
MultiExcerptNameNonWindowsInstallationPackage
PageWithExcerptDeploying 1E Client on macOS

Within the zip, the Linux 1E Client is provided as the following .rpm files:

  • 1e.client-CentOS_7_x64_v5.0.0.xxx.rpm
  • 1e.client-Fedora_21_x64_v5.0.0.xxx.rpm
  • 1e.client-openSUSE_42.1_x64_v5.0.0.xxx.rpm
  • 1e.client-RHEL_6.2_x64_v5.0.0.xxx.rpm
  • 1e.client-RHEL_6.2_x86_v5.0.0.xxx.rpm
  • 1e.client-RHEL_7.1_x64_v5.0.0.xxx.rpm
  • 1e.client-RHEL_8.1_x64_v5.0.0.xxx.rpm
  • 1e.client-SLES_12.2_x64_v5.0.0.xxx.rpm



Installation

The basic command to install an RPM package is rpm -i <package_file>. Although RPM, by design, does not support configuration during installation (with the Linux recommended approach being to configure after installation) - the 1E Client does in fact support configuration through the use of environment variables. These can be easily set in a bash command line by one or more space-separated name=value pairs preceding the install command. So, if the RPM package file name is 1e.client-RHEL_7.1_x64_v5.0.0.745.rpm and the Tachyon Server (assuming that the switch and the background channel are both installed on the Tachyon Server) has the DNS Name FQDN tachyon.acme.local then the command to run would be:

Code Block
languagebash
sudo SWITCH=tachyon.acme.local:4000 BACKGROUNDCHANNELURL=https://tachyon.acme.local:443/Background/ rpm -i 1e.client-RHEL_7.1_x64_v5.0.0.745.rpm

Please refer to 1E Client configuration settings and installer properties for a list of other configuration properties that can be configured in the same way. 

Note
The correct case for each property must be used when entering the Linux installer command.


Note

When the package starts to install you may notice that the ldconfig command generates a warning saying that a .py file is not an ELF file - it has the wrong magic bytes at the start.

This is because ldconfig assumes all files in /usr/lib are ELF files, and that file is a python file.

You can safely ignore this warning.

After the package is installed the application configuration files will be installed to the following directory:

Code Block
languagebash
/etc/1E/Client

After running the Linux RPM package the client is installed and started as a daemon (service).

The client certificate Tachyon.pfx and a cacert.pem file are required in the hidden directory: /etc/1E/Client/.sslcerts 

If Tachyon.pfx contains the same certificate trust chain as the Tachyon Switch, then cacert.pem is optional. This is because the client will have already cached the public certificates when it parses Tachyon.pfx and cacert.pem will be duplicating the public certificate information. If Tachyon.pfx is using a different certificate trust chain from the Tachyon Switch, then cacert.pem is always required.

Reconfiguration

Please refer to 1E Client command-line parameters if you would like to see details of other CLI commands.

Info

This method is suitable for reconfiguring all 1E Client settings on non-Windows devices because only Tachyon client features are available and all settings are stored in the 1E Client configuration file.

Example:

Multiexcerpt
MultiExcerptNameReconfigureExample


Code Block
/usr/sbin/1E.Client -reconfigure Switch=ACME-DMZ01.ACME.LOCAL:4000 BackgroundChannelUrl=https://ACME-DMZ01.ACME.LOCAL:443/Background/ -restart



Client certificates

Each client device requires its own certificate, which must be created as a .pfx file.

Using OpenSSL to create the .pfx file

Multiexcerpt include
SpaceWithExcerptcom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@4bf569a
MultiExcerptNameNonWindowsCertUsingOpenSSL
PageWithExcerptTCN50:Preparation

Storing the .pfx on the client

Multiexcerpt include
MultiExcerptNameSSLcertificateFileMethod
PageWithExcerptDeploying 1E Client on macOS

Uninstallation

Multiexcerpt
MultiExcerptName1EClientUninstall

The following command-line can be used to uninstall the 1E Client on Linux:

Code Block
languagebash
sudo rpm -e 1e.client

Uninstallation will leave behind files, folders and registry entries that were created after installation:

LocationArtifactsRecommendation
Installation folderNone.
Logs folder

Log files remain.

The log files can be deleted or renamed. If not deleted, then a new installation that uses the same logs folder will continue to use the old log file.

Client\Persist folder remains.

You should keep the Persist folder, which contains status information about current instructions, only if you intend to re-install the 1E Client.