Deploy war application to multiple tomcat servers using ANT Script

It is tedious work if you have say 5 servers and you need to deploy same application in all servers manually.
So, I developed below ant script which will deploy the application in all servers with single command.
All you need to do is to update server details in the build.properties file.


build.xml

<?xml version="1.0" encoding="UTF-8"?>
<project name="OneClickDeploy" default="deploy" basedir=".">
<property file="build.properties" />
<property name="war-file-name" value="${project-name}.war" />
<property name="build-directory" value="${build-directory}" />

<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask" />
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask" />
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask" />
<target name="deploy" description="deploy to tomcat">
<echo>deploying to server ${tomcat-manager-url1} </echo>
<!-- 
  undeploy application
<undeploy 
url="${tomcat-manager-url1}"
username="${tomcat-manager-username1}"
password="${tomcat-manager-password1}"
path="/${project-name}"
/>
-->
<!-- 
  reload application
<reload 
url="${tomcat-manager-url1}"
username="${tomcat-manager-username1}"
password="${tomcat-manager-password1}"
path="/${project-name}"
war="file:/${build-directory}/${war-file-name}
/>
-->
<deploy 
url="${tomcat-manager-url1}"
username="${tomcat-manager-username1}"
password="${tomcat-manager-password1}"
path="/${project-name}"
war="file:/${build-directory}/${war-file-name}"
/>
<echo>deploying to server ${tomcat-manager-url2} </echo>
<!--
  undeploy application
<undeploy 
url="${tomcat-manager-url2}"
username="${tomcat-manager-username2}"
password="${tomcat-manager-password2}"
path="/${project-name}"
war="file:/${build-directory}/${war-file-name}"
/> 
-->
<!-- 
  reload application
<reload 
url="${tomcat-manager-url2}"
username="${tomcat-manager-username2}"
password="${tomcat-manager-password2}"
path="/${project-name}"
war="file:/${build-directory}/${war-file-name}
/>
-->
<deploy 
url="${tomcat-manager-url2}"
username="${tomcat-manager-username2}"
password="${tomcat-manager-password2}"
path="/${project-name}"
war="file:/${build-directory}/${war-file-name}"
/>
</target>
</project>

build.properties

#build.properties file
#project name or the application context name. if your application accessible using http://localhost:8080/iiq then provide project-name as iiq
project-name=myapp
#compiled project war file directory
build-directory=C:/Users/Desktop/OneClickDeploy

#Server1 tomcat details, tomcat user should have role 'manager-script', update context.xml in webapps/manager/META-INF to access manager console from out-site server machine
tomcat-manager-url1=http://<HOSTNAME>:8080/manager/text
tomcat-manager-username1=root
tomcat-manager-password1=root

tomcat-manager-url2=http://<HOSTNAME>:8080/manager/text
tomcat-manager-username2=root
tomcat-manager-password2=root

Prerequisite:

1. Local machine
o Working ANT console
o Tomcat libraries should be included to classpath or to ANTs lib directory
o Keep build.properties and build.xml in same directory

2. Server machine
o Up and Running Tomcat server
o Tomcat server manager console should be accessible from local machine
Ex: You should be able to access http://<SERVER_HOST>:8080/manager from local
machine
Required settings can be updated in context.xml in /webapps/manager/META-INF
o Tomcat user with deploy permission using scripts
Ex: add below line in tomcat-users.xml
<user username="root" password="root" roles="admin-
gui,manager-gui,manager-script"/>


Execution: Simply open command prompt on build.xml directory and run ant command


Comments

Post a Comment

Popular posts from this blog

Rules in Sailpoint

Rules in Sailpoint Below are few commonly used rules in Sailpoint Sailpoint rules gets executed in the below order during aggregation Flow: Pre-Iterate Rule BuildMap Rule Managed Entitlement Customization Rule Customization rule Correlation rule Manager correlation rule Creation rule PostIterate Rule Pre-Iterate Rule: 1st rule that runs during aggregation You can perform below operations in this rule Check file existence Modify the data in the files Merge files BuildMap Rule: 2nd Rule thats runs during aggregation, Using build map rule you can deal with application schema ex: populate value for custom column for the application. Build map is not available for connected apps(JDBC has jdbc buildmap). Available only for disconnected apps like delimited files. Customization Rule:  Runs after buildmap rule, this can be used to transform data of resource object/account data during account aggregation Ex: if you have status value...
Read more

Sailpoint Installation Steps (IdentityIQ 7.3 Installation in Windows Machine)

This document helps you set up Sailpoint IdentityIQ 7.3 in Windows Operating System Softwares Required: MySQL 5.6 server Click here to download Apache Tomcat  9.0 Click here to download Java JDK 1.8 and above Click here to download Sailpoint IdentityIQ 7.3 application You may require to login into Sailpoint community to download Install the above softwares, update JDK, MySQL paths in environment Path variable Note: If you are facing issue in MySQL service then try running below commands mysqld –install net start mysql Sailpoint Configuration Steps: Create an \idenityiq directory under the Tomcat webapps directory: for example, C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\identityiq Unzip the identityiq-7.3.zip file. Copy iidentityiq.war file to the C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\identityiq Run below command to extract identityiq.war jar -xvf C:\Program Files\Apa...
Read more

How to create provisioning plan in Sailpoint

//Provide application name, attributes, operation ProvisioningPlan plan = new ProvisioningPlan(); List requests = new ArrayList(); List attributes = new ArrayList(); /*Identity identity = context.getObjectById(Identity.class, formModel.get("identity"));*/ AccountRequest account = new AccountRequest(); account.setApplication("HR_Staging"); account.setOperation(AccountRequest.Operation.Create); attributes.add(new AttributeRequest("FIRST_NAME", identity .getAttribute("firstname"))); attributes.add(new AttributeRequest("LAST_NAME", identity .getAttribute("lastname"))); account.setAttributeRequests(attributes); requests.add(account); //plan.setIdentity(identity); plan.setAccountRequests(requests); System.out.println("Plan xml : " + plan.toXml());
Read more