Deploying the Aspera for SharePoint Application

Deploy the Aspera for SharePoint application into your existing SharePoint installation. Perform the following steps on your SharePoint server:

[Optional] Verify that all prerequisites are in place.
1. Confirm that wildcard DNS is set up.
```
> ASConfiguratorCmd.exe /CheckWildcardDNS remoteWebServerURL
```
2. Confirm that the remote web server's DNS is set up.
```
> ASConfiguratorCmd.exe /CheckRemoteWebDNS remoteWebServerURL
```
3. Confirm that the certificate file is a wildcard certificate.
```
> ASConfiguratorCmd.exe /CheckWildcardCertificate pathToCertificate.cer
```
4. Confirm that the SharePoint timer service SPTimer is running.
```
> ASConfiguratorCmd.exe /CheckSPTimer
```
5. Confirm that the SharePoint App Management Service is running.
```
> ASConfiguratorCmd.exe /CheckAppManagement
```
6. Confirm that the the SharePoint Subscription Settings Service is running.
```
> ASConfiguratorCmd.exe /CheckSubscriptionSettingsService
```
Aspera for SharePoint is a high-trust application. In this step, you will create the trust relationship between the remote web server and the SharePoint server.
Note: This part of your configuration depends heavily on your organization's particular environment and security policies. Before running these commands, consult Aspera Technical Support.
1. To configure the Aspera for SharePoint application as a Trust Broker (so that it can issue tokens for multiple applications), run the following:
```
> ASConfiguratorCmd.exe /SetupHighTrust remoteWebServerURL 
      pathToCertificate.pfx pathToCertificate.cer 'Aspera SharePoint'
```
2. If you did not purchase an SSL certificate for the remote web server, run the following commands to allow SharePoint apps to use HTTP instead of HTTPS:
  Note: CAUTION: For security reasons, this practice is not recommended.
```
> ASConfiguratorCmd.exe /AllowOAuthOverHttp
```
```
> ASConfiguratorCmd.exe /AllowMetaDataOverHttp
```
Deploy the SPApp.app file on your SharePoint server.
With the exception of Step a) below, all of these actions must be performed for each Site Collection.

Note: The remote web server must be in place before you perform this step.
1. [Advanced] If you need to generate a new GUID for the token issuer or client, run the following:
  Note: In most cases, you will use the default GUIDs.
```
> ASConfiguratorCmd.exe /NewGuid
```
2. Update the .app file for your configuration.
  Note: You must perform this step for each Site Collection.
```
> ASConfiguratorCmd.exe /UpdateAppFile SPApp.app clientID remoteWebServerURL [false|true]
```
  The last parameter in the sequence above specifies whether to use an HTTP endpoint. In the interest of better security, Aspera recommends that you specify false for this parameter.
3. Upload SPApp.app to SharePoint.
```
> ASConfiguratorCmd.exe /InstallApp sharepointServer clientID SPApp.app packageFileLocation
```
4. Set permissions for the app.
```
> ASConfiguratorCmd.exe /SetupAppPermissions sharepointServer clientID SPApp.app
```

After deploying Aspera for SharePoint, or at any point in the course of maintaining your installation, you may need to troubleshoot the application. For details on utilities for troubleshooting, see Troubleshooting.