|Configuring for Other Aspera Products|
The steps below describe configuring IBM Aspera Connect Server as the transfer server for IBM Aspera Faspex.
The transfer server can be set up in either of the following configurations:
All steps must be performed with administrator permissions.
The system user authenticates the actual ascp transfer and must be an operating system account. To create a new system user faspex on your Windows system, go to Control Panel > User Accounts. After adding the faspex user, change the user's password.
Create the directory C:\faspex_packages.
In Server Configuration, open the Users tab. Then click the button.
In the Add User dialog that appears, fill in the name faspex and click OK. The faspex user is added to the user list.
To specify a docroot, select faspex in the user list and click the Docroot tab in the right panel. For the Absolute Path setting, select the Override box, and under Effective Value fill in the following:
For the read, write, and browse settings, select the
Override boxes and select true.
You can also add and configure the faspex user for Connect Server by modifying aspera.conf, instead of using the application GUI. For details, see Setting Up Users.
> asconfigurator -x "set_server_data;server_name,server_ip_or_name" > asconfigurator -x "set_central_server_data;persistent_store,enable" > asconfigurator -x "set_user_data;username,faspex;dir_allowed,true"
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.
> ascp -A Enabled settings: connect, mobile, cargo, node, proxy, http_fallback_server, group_configuration, shared_endpoints, desktop_gui
If the list includes connect and http_fallback_server, you have a Faspex-enabled server license.
If you update your Connect Server license (see Updating the Product License), you must reload the asperanoded service afterwards. Reload the asperanoded service by running the following command:
> asnodeadmin --reload
> asnodeadmin -a -u node-admin -p s3cur3_p433 -x faspex > asnodeadmin.exe --reload
C:\Program Files [(x86)]\Aspera\Enterprise Server\var\aspera_tokenauth_id_rsa.pub
Create an .ssh folder (if it does not already exist) in the Faspex user's home folder: C:\Users\faspex\.ssh . Use a text editor to create (or modify) the authorized_keys file, with no file extension, in the .ssh folder. Add the faspex user's key string into this file and save it. Note that some text editors add a .txt extension to the filename automatically. Be sure to remove the extension if it was added to the filename.