Azure has two different deployment models for creating and working with resources: Resource Manager and classic. This article covers using the classic deployment model. Microsoft recommends that most new deployments use the
Resource Manager model.
With Azure, you can use a virtual machine to provide server capabilities. As an example, a virtual machine running on Azure can be configured to host a Java application server, such as Apache Tomcat. After you complete this guide, you will have an understanding of how to create a virtual machine running on Azure and configure it to run a Java application server.
You will learn:
How to create a virtual machine that has a Java Development Kit (JDK) already installed.
How to remotely sign in to your virtual machine.
How to install a Java application server on your virtual machine.
How to create an endpoint for your virtual machine.
How to open a port in the firewall for your application server.
For the purposes of this tutorial, an Apache Tomcat application server will be installed on a virtual machine. The completed installation will result in a Tomcat installation such as the following.
Click the name of the virtual machine that you want to sign in to.
After the virtual machine has started, a pop-up menu at the bottom of the page allows connections.
Respond to the prompts as needed to connect to the virtual machine. This should entail saving or opening the .rdp file that contains the connection details. You might have to copy the url:port as the last part of the first line of the .rdp file and paste it in a remote sign-in application.
To install a Java application server on your virtual machine
You can copy a Java application server to your virtual machine, or you can install a Java application server through an installer.
For the purposes of this tutorial, Tomcat will be installed.
When you are signed in to your virtual machine, open a browser session to Apache Tomcat.
Double-click the link for 32-bit/64-bit Windows Service Installer. By using this technique, Tomcat will be installed as a Windows service.
When prompted, choose to run the installer.
Within the Apache Tomcat Setup wizard, follow the prompts to install Tomcat. For the purposes of this tutorial, accepting the defaults is fine. When you reach the Completing the Apache Tomcat Setup Wizard dialog box, you can optionally check Run Apache Tomcat to have Tomcat start now. Click Finish to complete the Tomcat setup process.
To start Tomcat
If you did not choose to run Tomcat in the Completing the Apache Tomcat Setup Wizard dialog box, start it by opening a command prompt on your virtual machine and running net start Tomcat7.
You should now see Tomcat running if you run the virtual machine's browser and open http://localhost:8080.
To see Tomcat running from external machines, you need to create an endpoint and open a port.
Click the name of the virtual machine that is running your Java application server.
In the Add endpoint dialog box, ensure Add standalone endpoint is selected, and then click Next.
In the New endpoint details dialog box:
Specify a name for the endpoint; for example, HttpIn.
Specify TCP for the protocol.
Specify 80 for the public port.
Specify 8080 for the private port.
Click the Complete button to close the dialog box. Your endpoint will now be created.
To open a port in the firewall for your virtual machine
Sign in to your virtual machine.
Click Windows Start.
Click Control Panel.
Click System and Security, click Windows Firewall, and then click Advanced Settings.
Click Inbound Rules, and then click New Rule.
For the Rule Type, select Port, and then click Next.
On the Protocol and Ports screen, select TCP, specify 8080 as the Specific local port, and then click Next.
On the Action screen, select Allow the connection, and then click Next.
On the Profile screen, ensure that Domain, Private, and Public are selected, and then click Next.
On the Name screen, specify a name for the rule, such as HttpIn (the rule name is not required to match the endpoint name, however), and then click Finish.
At this point, your Tomcat website should be viewable from an external browser by using a URL of the form http://your_DNS_name.cloudapp.net, where your_DNS_name is the DNS name you specified when you created the virtual machine.
Application lifecycle considerations
You could create your own web application archive (WAR) and add it to the webapps folder. For example, create a basic Java Service Page (JSP) dynamic web project and export it as a WAR file, copy the WAR to the Apache Tomcat webapps folder on the virtual machine, then run it in a browser.
By default when the Tomcat service is installed, it is set to start manually. You can switch it to start automatically by using the Services snap-in. Start the Services snap-in by clicking Windows Start, Administrative Tools, and then Services. Double-click the Apache Tomcat service and set Startup type to Automatic.
The benefit of having Tomcat start automatically is that it will start if the virtual machine is rebooted (for example, after software updates that require a reboot are installed).
Learn about other services (such as Azure Storage, service bus, and SQL Database) that you may want to include with your Java applications by viewing the information available at the Java Developer Center.