|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.
If you change aspera.conf , you must restart asperacentral and asperanoded.Go to Control Panel > Administrative Tools > Services and restart Aspera Central and Aspera NodeD.
If you are setting up Connect Server as a remote transfer server node, continue with the steps below.
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; faspex is then added to the user list.
To specify a docroot, make sure faspex is selected in the user list, and click the
Docroot tab in the right panel. For the Absolute Path setting,
check the Override box, and under Effective Value fill in
/Users/faspex/faspex_packages. For the read, write, and browse
settings, check 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.
C:\Program Files (x86)\Aspera\Enterprise Server\etc\aspera.conf
Below is a typical aspera.conf file. Yours may differ, particularly if you have installed other Aspera products. Copy any absent portions from the example below. Modify the following settings, as necessary:
<?xml version='1.0' encoding='UTF-8'?> <CONF version="2"> <central_server> <address>127.0.0.1</address> <port>40001</port> <compact_on_startup>enable</compact_on_startup> <persistent_store>enable</persistent_store> <persistent_store_on_error>ignore</persistent_store_on_error> <persistent_store_max_age>86400</persistent_store_max_age> <event_buffer_overrun>block</event_buffer_overrun> </central_server> <default> <file_system> <pre_calculate_job_size>yes</pre_calculate_job_size> </file_system> </default> <aaa> <realms> <realm> <users> <user> <name>faspex</name> <file_system> <access> <paths> <path> <absolute>C:\faspex_packages</absolute> <show_as>/</show_as> <dir_allowed>true</dir_allowed> </path> </paths> </access> <directory_create_mode>770</directory_create_mode> <file_create_mode>660</file_create_mode> </file_system> <authorization> <transfer> <in> <value>token</value> </in> <out> <value>token</value> </out> </transfer> <token> <encryption_key>af208360-dbdd-4033-a35b-2370941f37e9</encryption_key> </token> </authorization> </user> </users> </realm> </realms> </aaa> <http_server> <http_port>8080</http_port> <enable_http>1</enable_http> <https_port>8443</https_port> <enable_https>1</enable_https> </http_server> <server> <server_name>server_ip_or_name</server_name> </server> </CONF>
After modifying aspera.conf, restart Aspera Central and Aspera NodeD services.
You can restart these services from the Windows Computer Management window, accessible from Control Panel > Administrative Tools > Computer Management > Services and Applications > Services; click (highlight) the service and click More Actions.
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.
You can also check the license from the Connect Server desktop client GUI. Click Tools > License and if Connect Clients Enabled and Http Fallback Server Enabled are set to Yes, you have a Faspex-enabled 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:
> "C:\Program Files [(x86)]\Aspera\Enterprise Server\bin\asnodeadmin.exe --reload
Set up the node user and associate it with the faspex user by running the asnodeadmin command, as in the following example in which node-admin is the node user, s3cur3_p433 is the node user's password, and faspex is the system user. Then run asnodeadmin again to reload asperanoded.
> asnodeadmin.exe -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.