Point-Click Deployment of Neo4J to Windows Azure
In this article, I will show you how to deploy Neo4J into Azure VMs in minutes. No coding, no Visual Studio, just point-click deployment for free.
Table of Contents
Create a Windows Azure Subscription if you don’t have one already
Locating the package
Navigate to Dynamic Deploy , Register and Sign In
Click on Deploy
Select a supported Datacenter
Upload your .publishsettings file
Select a subscription
If you have multiple subscriptions, a dropdown list will pop-up giving you a choice of subscription for deployment.
Storage and Compute
Select an existing Storage Account and a Hosted Service or create new ones as required
Select VM Size
Note down username and create a password
Wait till the VM gets deployed
Check the Logs (optional)
Browse to the URL http://[yourhostedservicename]:7474 to view the Neo4J admin page
Note: I recommend you to lock down the admin interface by commenting the following in neo4j-server.properties file
# any connection. Please see the security section in the neo4j
# manual before modifying this.
Use the admin name you noted earlier and the password you created for your VM to RDP into the VM from Windows Azure portal.
Also check your email for RDP information.
Dynamic Deploy stored neo4j in the following directory
Note: I also recommend to copy the data files into an external attached drive so that the data is not lost.
Neo4J runs as a Windows Service on the VM with name Neo4j-Server.
Attach an External Drive
Go to Windows Azure portal and attach an external drive to the neo4j VM
Once you attach the disk, RDP into the VM and format it. I have given my drive the letter “Q”
Changing the Data Directory
Next, you can change the data directory in neo4j-server.properties (Note: Shutdown the Neo4J service before changing the data directory)
# location of the database directory
Then copy the contents of the C:\ddapplications\neo4j-community-1.8.2\data\graph.db directory to Q:/data/graph.db
Restart the Neo4J service
Browse the admin interface to check if it works
Verify the data directory path on the admin interface
You can copy some of the sample datasets to the new graph.db directory for better testing.