|Configuring for Other Aspera Products|
These steps are described in detail below.
If you haven't already, follow the steps in Standard Installation to install Connect Server.
The transfer server that you will use with Aspera for SharePoint must be installed on a host separate from your Microsoft SharePoint environment hosts.
All steps must be performed as root.
The system user authenticates the actual ascp transfer and must be an operating system account.
Run the following command to (1) create the system user sharepoint; (2) configure it to use the Aspera secure shell, aspshell; and (3) create the group sharepoint and assign the new system user to it.
# /usr/sbin/useradd -r sharepoint -s /bin/aspshell-r -g sharepoint
The standard location for the public key is in the user's home directory.
The Aspera-provided key file is located in:
# mkdir /home/aspera_user_1/.ssh
# cat /opt/aspera/var/aspera_id_dsa.pub >> /home/sharepoint/.ssh/authorized_keys
# chown -R sharepoint:sharepoint /home/sharepoint/.ssh/authorized_keys # chmod 600 /home/sharepoint/.ssh/authorized_keys # chmod 700 /home/sharepoint # chmod 700 /home/sharepoint/.ssh
The aspera.conf file is found in the following location:
In the <central_server> section, find <persistent_store> and ensure that it is set to enable (the default value).
This setting allows the retention of the historical transfer data that the stats collector uses.
For additional details on configuring token authorization, see Setting Up Token Authorization.
In the <file_system> section, find <dir_allowed> and ensure that it is set to true.
In the server section, find <server_name> and ensure that server_ip_or_name is replaced with the name or IP address of your server.
<central_server> <persistent_store>enable</persistent_store> </central_server> ... <user> <name>sharepoint</name> <authorization> <transfer> <in> <value>token</value> </in> <out> <value>token</value> </out> </transfer> <token> <encryption_key>gj5o930t78m34ejme9dx</encryption_key> </token> </authorization> <file_system> <access> <paths> <path> <dir_allowed>true</dir_allowed> </path> </paths> </access> ... </user> ... <server> <server_name>server_ip_or_name</server_name> </server>
# /etc/init.d/asperanoded restart # /etc/init.d/asperacentral restart
Verify that your transfer server license is Connect Server-enabled. (Aspera for SharePoint requires a Connect Server-enabled license.)
To check this from the command line, run ascp -A and review the enabled settings list.
Enabled settings: connect, mobile, cargo, node, proxy, http_fallback_server, group_configuration, shared_endpoints, desktop_gui
If the list includes connect, you have a Connect Server-enabled license.
You can also check the license from the Connect Server desktop client GUI. The License dialog (Tools > License) includes the Connect Clients Enabled field. If it is set to Yes, you have a Connect Server-enabled license.
Because this Faspex configuration uses Connect Server as a remote transfer service, it requires the Aspera Node API. For this reason, whenever you update your Connect Server license (see Updating the Product License), you must reload the asperanoded service afterwards. Reload the asperanoded service by running asnodeadmin, found in the following location:
# /opt/aspera/bin/asnodeadmin --reload
A node user is the entity that Aspera's applications use for authentication between the Web application and the transfer server.
# /opt/aspera/bin/asnodeadmin -a -u node_sharepoint -p s3cur3_p433 -x sharepoint
# /opt/aspera/bin/asnodeadmin --reload
# /opt/aspera/bin/asnodeadmin -l
The output for this command should resemble the following:
List of node user(s): user system/transfer user acls ==================== ======================= ==================== sharepointnode sharepoint  spnode aspera_user_1 
Add the transfer server to your Aspera for SharePoint installation, mapping it to a document library. For details, see the IBM Aspera for Microsoft SharePoint Administrator's Guide at http://downloads.asperasoft.com/en/downloads/47.