|Configuring for Other Aspera Products|
The steps below show how to set up IBM Aspera Enterprise Server as a transfer server for IBM Aspera Shares. The procedure assumes you have already set up your Shares application. For general information on setting up a transfer server (using the Node API), see Set up for Node API.
Follow the instructions in Installation and Upgrades to install Enterprise Server either locally (on the same host as Shares) or remotely.
The steps below must be performed with administrator permissions.
Create a user account—for example, aspera_user_1—on your operating system by clicking. (Creating a user account requires administrator permissions.)
Configure the operating system user in Enterprise Server to make it an Aspera transfer user. For instructions, see Setting Up Users.
> asnodeadmin -a -u node_api_username -p node_api_passwd -x aspera_user_1
Adding, modifying, or deleting a node user triggers automatic reloading of the configuration and license files, as well as the user database.
For example, if the file transfer user is aspera_user_1, the standard location for the public key is in the user's home folder, as follows:
The Aspera-provided key file is located in:
C:\Program Files [(x86)]\Aspera\Enterprise Server\var\aspera_tokenauth_id_rsa.pub
Open a command prompt window and run the following commands to create the user's public key folder:
> cd user_home_folder > md .ssh
Use a text editor to create the following file (with no file extension), if the file does not already exist:user_home_folder\.ssh\authorized_keys
Copy the contents of aspera_tokenauth_id_rsa.pub to the authorized_keys file. Update the folder permissions in Windows Explorer by right-clicking the .ssh folder, selecting Properties, and then selecting the Security tab. Here, you can set permissions to read, write, and execute (full control).
> asconfigurator -x "set_server_data;server_name,server_ip_or_name" > asconfigurator -x "set_central_server_data;persistent_store,enable" > asconfigurator -x "set_http_server_data;enable_http,true" > asconfigurator -x "set_http_server_data;enable_https,true"
> asconfigurator -x "set_user_data;user_name,username;authorization_transfer_in_value,token" > asconfigurator -x "set_user_data;user_name,username;authorization_transfer_in_value,token" > asconfigurator -x "set_user_data;user_name,username;token_encryption_key,encryption_key"The encryption key should be a string of random characters (at least 20 recommended).
Alternatively, you can configure token-authorization settings to apply to all users in a group or to apply them globally for all users. For more information, see User, Group and Default Configurations.
You can restart the Aspera Central from the Computer Management window. Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera Central, and click Restart.
Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera NodeD, and click Restart.