Micro Focus Enterprise Server for .NET 3.0 > Windows Azure Support > Using Azure File Storage with Enterprise Server for .NET > Deploy Artifacts to a File Storage Drive.

Deploy Artifacts to a File Storage Drive.

Deploying artifacts ( programs, mapsets etc) to an azure drive running under a Enterprise Server for .NET Azure instance can be done in a number of ways .

Use the AZCopy tool provided by Microsoft.

This is a high speed copy operation that can be used to deploy files to an Azure File Storage instance.
The tool and usage descriptions are available from http://azure.microsoft.com/en-gb/documentation/articles/storage-use-azcopy/

Install an FTP server onto the monitor roles and use it to move files backwards and forwards .

We don't recommend a particular FTP serve to use, but the ftp server does need to be a standalone ftp server ( not require installation using MSI or other installer technology).
The example below will use an FTP server called xlight.

Purchase xlight from http://www.xlightftpd.com/
Install xlight onto your local machine and run it .
- Configure the server to have a user id and password
- Associate the user account with a drive/path . e.g. v:\
- Save and exit
Create a self extracting zip archive using a tool like 7zip or pkzip.
- Call it smallftp.exe
Copy the smallftp.exe file to a known location on your hard drive ( we used the default reference directory).

Create a new command file called startftp.exe with the following contents .

:file_check
REM seemap.cmd is created when the share is made available by the role startup processing.
IF EXIST seemap.cmd (GOTO file_exists) ELSE (timeout 5 >NUL)
GOTO file_check

:file_exists
REM Map the drive
call seemap v:
d:
REM Extract the archive
e:smallftp -o"d:\" -y
REM Change to the ftp directory and start the server.
cd smallftp
start xlight -startall
:eof

Configure the monitor role in the deployment project to package the two new files startftp.cmd and smallftp.exe .
Configure the monitor startup commands to run startftp.cmd as a background task.

Deploy the system to Azure. When the monitor roles are running, you should be able to ftp to your ftp server using <Service>.cloudapp.net on port 21. Port 21 is exposed as part of the default deployment on the monitor role for this purpose.

Once an ftp server is online, you can move files backwards and forwards using an ftp client.

You can also use the seedeploy tool as discussed in cmd seedeploy using the cdrv:// url syntax. The seedeploy tool for File Storage use is reliant on the ftp server being available.