Create a High-Speed Transfer Server instance by using the Platform UI.
Before you beginTo create an High-Speed Transfer Server (HSTS) service
instance by using the Platform UI, you must have already:
- If your environment does not provide public IP addresses for worker nodes, you must use Aspera
Proxy to allow transfers from clients to the HSTS instance, which requires additional configuration
of your HSTS instance. See Using Aspera Proxy with HSTS.
- When deploying multiple HSTS instances, you must use a unique name for each namespace (project)
that you create.
- Log in to Platform UI.
- Click Integration Instances.
- Click Create an instance.
- Select High speed transfer server and click
- Select one of the following options: Quick start,
Development, or Production and then click
- Make sure the UI Form perspective is selected for the configuration
The UI Form view gives the standard configuration options and is
selected by default. The YAML view opens an editor where you can add the parameters and values to
- In the Details section:
- Add the Instance name.
Note: The instance name can be changed. If you
don't change your instance name, the default name of the instance is the type of configuration
template you selected:
- Add the Namespace.
Important: If you selected a single
namespace-scoped deployment, the option to change the Namespace for the operand is
- In the License section:
- Enable the Accept License checkbox to accept the conditions of your
- In the Aspera License field, enter your license.
- From the License Use drop-down, select your license use type (for
AsperaProduction or AsperaNonProduction use).
Note: To obtain full HSTS performance, you need an
Aspera production environment license.
- In the Redis section, add your Redis configuration:
- If you want to use Redis, Sentinel,
Redis tls, or Persistence, enter the configuration
Important: When you need to upgrade Cloud Pak for Integration,
you will not be able to perform the upgrade until you perform a backup and restore of the Redis
database (in other words, the database needs to be relocated).
- In the Storage section, add your storage configuration:
- Click the YAML perspective tab to assign the Claim
name. This refers to the persistent volume storage used when transferring files. For
- From the Storage class dropdown menu, select the storage and make sure
that the storage supports ReadWriteMany so you can use it for the claim.
- Enable the Delete Claim checkbox if you want the claim to be deleted when
the operand is deleted.
- In the Size field, enter the total amount of storage that is required for
- In the Mount Path field, change the name if you want to use a different
mountPath specification is required; it defines where the storage is
mounted to the pod.
- If you want to change the operand version, enter a value for the desired operand version.
- Add the Node API credentials to your
YAML file by switching the configuration
The HSTS operator automatically creates the HSTS Node API credentials. The credentials
consist of a unique Node API username and password, which are stored in a secret called
. If you want to
change the credentials (username and password) see: Optional: Create an Aspera node credentials secret
- Click Create. When the entry in the Status column
displays Ready, HSTS is running.