Monitoring iTunes Transporter transfers via the Aspera Management Console

Question:

How can I monitor or manage transfers to Apple iTunes using the Apple Transporter in my Aspera Management Console?

Solution:

Apple iTunes provides an application, Apple Transporter, for customers to upload content to the iTunes store. This tool is enabled for Aspera transfers. Because this application runs separate and distinct from any Aspera software installed on the same node the transfers are not reported to the Aspera Management Console. Since release 1.7.7 of the Apple Transporter, Apple has provided a command line option to allow those transfers to report to a console if the computer (node) where the Transporter is installed is already a managed node in your Aspera Console. To enable this a single option needs to be added to the iTunes command line. The flag is -D and the syntax is:

-Daspera.altManagementPort=portnum

where portnum is the asperacentral.port used by the Aspera installation (P2P, Enterprise Server or Connect Server).

The asperacentral.port is a file that is created on the system when asperacentral is started. (This is started automatically when the system is powered on.) Each time asperacentral is restarted the value in asperacentral.port file will change. By dynamically reading the value of this file you can continue to automate transfers to iTunes and have the added benefit of managing these transfers (including monitoring and reporting) in your Console. To do this edit the script used to run the Apple Transporter transfers and add the following:

On Linux:

Add the following line to your variables in the script

PORT =$(cat /opt/aspera/var/run/aspera/asperacentral.port)

and then add the command line option

-Daspera.altManagementPort=$PORT

 

On Mac:

Add the following line to your variables in the script

PORT =$(cat > /Library/Aspera/var/run/aspera/asperacentral.port)

and then add the command line option

-Daspera.altManagementPort=$PORT

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk