{"id":32886,"date":"2017-06-06T04:15:05","date_gmt":"2017-06-06T12:15:05","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=32886"},"modified":"2019-02-14T15:51:35","modified_gmt":"2019-02-14T23:51:35","slug":"building-and-deploying-a-java-application-to-oracle-weblogic-server-running-in-azure-vm-with-microsoft-visual-studio-team-services","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/building-and-deploying-a-java-application-to-oracle-weblogic-server-running-in-azure-vm-with-microsoft-visual-studio-team-services\/","title":{"rendered":"Building and Deploying a Java Application to Oracle WebLogic Server Running in Azure VM with Microsoft Visual Studio Team Services"},"content":{"rendered":"

If you are interested in Microsoft Visual Studio Team Services (VSTS) platform and Java development<\/a>, maybe you know that VSTS has everything you need to organize CI\/CD pipeline for your Java application development. Visual Studio ALM Blog has a lot of useful and helpful resources<\/a> describing how to build and deploy your Java application and artifacts to Azure App Service or Azure VM running lightweight open source Tomcat or Jetty servlet container with VSTS. But what if you are going to use\/using enterprise grade Java EE application server like Oracle WebLogic Server in Azure VM<\/a> and you have a requirement to seamlessly integrate it with your VSTS CI\/CD pipeline? Quick answer is: \u00abyes, it is possible\u00bb. Microsoft VSTS has very flexible mechanism of build\/release definitions which allows you to configure your CI\/CD pipeline according your requirements and compile, build and deploy your Java EE application to Oracle WebLogic Server. In this article, I will consider the basic steps you need to do to configure your infrastructure for WebLogic deployment.<\/p>\n

Prerequisites<\/h2>\n

In the world of Java development, Apache Maven<\/a> is a well-known and proven build automation system for simplifying build process for Java projects and widely using by Java developers. Oracle WebLogic Server also provides support for Maven through the provisioning of plug-ins that enable developers to perform various operations on WebLogic Server within a Maven environment. The task of automated deployment to local\/remote WebLogic Server instances was simplified since Oracle updated Oracle WebLogic Maven plugin and made it available in Oracle Maven Repository<\/a>. WebLogic Maven plugin (weblogic-maven-plugin)\u00a0provides functionality to install, start and stop server instances, create domains, execute WLST<\/a> scripts, and compile and deploy Java applications. You can find out more details about its functionality in official WebLogic Maven Plugin documentation<\/a>. Good news that you may not install this plug-in manually now, instead of this you can use Oracle Maven Repository<\/a>. Alternatively, you can configure the plugin manually if you do not want to use remote repository. To start it usage you must accept license agreement<\/a> and make some modifications in your Maven settings and project POM artifact. We will consider basic steps in this post, but you can find more details in official documentation<\/a>. In our case, we are going to deploy our private VSTS Build Agent running on Azure VM instead of the VSTS hosted agent. Then we need to make some modifications in Maven configuration to access Oracle Maven Repository.<\/p>\n

Microsoft Azure platform supports Oracle Software<\/a> including Oracle WebLogic Server<\/a> to run enterprise grade Java EE deployments. Despite WebLogic Server Infrastructure deployment in Microsoft Azure is out of the scope of this article, you can find all required information in official documentation<\/a>.<\/p>\n

In our case, I am using use Azure VM running Oracle WebLogic Server Quick Installer Distribution with one Admin Server instance listening 7001<\/strong> port number and WebLogic domain is configured in development mode. But feel free to experiment with your custom WebLogic Domain configuration for more complex deployments.<\/p>\n

Infrastructure configuration<\/h2>\n

Step 1<\/h4>\n

Before provisioning of VSTS Agent VM we need to create an agent pool<\/a>. Login to your VSTS account, go to Settings<\/strong> menu and then to Agent Pool<\/strong> Click New Pool\u2026<\/strong> and then enter the pool name. Remember and note your pool name since we will need it during VSTS Agent VM provisioning.<\/p>\n

\"\"<\/a><\/p>\n

Step 2<\/h4>\n

Now we need to provision VSTS Agent VM with all required software components for building of our Java web application. To simplify this step, instead of manually creating Azure VM, I\u2019ve prepared an Azure ARM Template<\/a> which will create Oracle Linux 7.2<\/em> VM<\/em> and run the shell script to install all required components for building and deployment. You can find ARM template artifacts on GitHub<\/a>. To deploy VM using your Azure subscription just simply click button below:\n<\/a><\/p>\n

<\/a><\/p>\n

Then you will need to select your Subscription<\/strong>, Location<\/strong> to deploy, Resource Group<\/strong>, and supply an Admin Username<\/strong>, Password<\/strong>, and unique DNS name<\/strong> for the machine. The machine type will be a Standard D1_V2<\/strong>. You will also need to specify the VSTS Account Name<\/strong> to use and a Personal Access Token (PAT)<\/strong>. If you don\u2019t have a personal access token, follow this link<\/a> to create one. Finally, you need to define VSTS Agent Pool Name<\/strong> (the one you\u2019ve created on the previous step 1<\/em>) and VSTS Agent Name. The VM will be deployed to a Resource Group <\/em>along with a virtual network and some other required resources. You can delete this resource group to remove all the created resources at any time. Please allow about 10 – 15 minutes to complete provisioning and configuration.<\/p>\n

\"\"<\/a><\/p>\n

Once deployment completed, you should see the following resources created in the Azure Portal<\/strong>:<\/p>\n

\"\"<\/a><\/p>\n

Step 3<\/h3>\n

The VM provisioned on previous step includes the following components:<\/p>\n