

You may get errors when running the 'Import-Module' line. 'C:\Neo4J' | Initialize-Neo4jServer -ListenOnIPAddress 127.0.0.1 -PassThru | Install-Neo4jServer -PassThruĪnd if you've had enough of it already. Import-Module C:\Neo4j\bin\Neo4j-Management.psd1 Then execute the following commands (assuming you've unzipped the contents to C:\Neo4J): Shortly after the machine restarted, I was able to open a browser and access the Neo4j admin portal.Step 4 - Open Powershell as Administrator and set up the service To test this setting, I went back to the Windows Azure portal and restarted my virtual machine. In the vi editor, I added the full path to Neo4j and the start command. This file is located in the etc directory. There is a file named rc.local that my research suggests is the place to put commands to run when a Unix server is started. After successful login, you land at a prompt as shown here.Ĭonfigure Virtual Machine to Start Neo4j on Startup… For the login name and password, use the user and password specified in the deployment script (above). Make sure the Port is set to 22, which is the SSH port of the virtual machine.Ĭlick Open to open a session to the virtual machine.

) of the virtual machine in Host Name field. PuTTY is the tool I used to SSH into the virtual machine. To mitigate this disruption that my application will experience when this virtual machine is restarted, I configured it to start Neo4j automatically (see below). However, when Windows Azure decides to recycle your virtual machine (and it will), you will have to connect back to your virtual machine and restart Neo4j. Starting the server I found to be a pretty simple task. Configure the Virtual Machine / Start Neo4jĪt the time of this writing, this image does not automatically start the Neo4j server. Now that the virtual machine is up and running, I can connect to it for some final configuration settings. You can give the endpoint any name you like but the protocol needs to be TCP and the port 7474. This is explained in the documentation for this image (although easy to miss if you’re not paying close attention). Next, add a public endpoint for port 7474. It took a minute or two for mine to finish starting up before it reached the “running” status. Go into your Azure portal and you should see your new image there. If you just have one then you don’t need it. I added the subscription parameter to my script since I have multiple subscriptions. Replacing the DNS name, user, and password with your preferences should be all you need. This will create the script you need to deploy this image.

I chose this one from Cognosys.Ĭlick the Deployment Script link and choose the region you want to create the virtual machine in.

A search for “neo” returns a couple of options.
