{"id":2892,"date":"2012-06-05T18:51:15","date_gmt":"2012-06-05T13:21:15","guid":{"rendered":"http:\/\/JitendraZaa.com\/blog\/?p=2892"},"modified":"2018-11-09T16:49:55","modified_gmt":"2018-11-09T21:49:55","slug":"salesforce-migration-tool-ant","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/salesforce-migration-tool-ant\/","title":{"rendered":"Complete Salesforce Deployment Guide using Ant Migration Tool"},"content":{"rendered":"

Following are the many tools available for\u00a0Salesforce deployment like<\/p>\n

    \n
  1. Change sets (From Salesforce site)<\/li>\n
  2. Eclipse (Using “Deploy to force.com server” option in Eclipse)<\/li>\n
  3. ANT (Java based tool)<\/li>\n<\/ol>\n

    We are going to discuss the ANT based migration, step by step:<\/p>\n

    Prerequisite:<\/strong>
    \nJDK 1.5 or above<\/p>\n

    Step 1:<\/strong>
    \nDownload ANT distribution from – “http:\/\/ant.apache.org\/bindownload.cgi<\/a>”<\/p>\n

    Step 2:<\/strong>
    \nSet Environment variable “ANT_HOME<\/em>“. The path should be of parent folder of “bin”.\u00a0Also add the “bin” folder to your path.<\/p>\n

    Step 3:<\/strong>
    \nCheck whether ANT is installed or not properly by running command “ant -version<\/em>“.\u00a0It might be possible that you receive message something like unable to find tools.jar<\/strong>. You can copy this jar from “JDK_HOME\/lib\/tools.jar” to “JRE\/lib” folder.<\/p>\n

    <\/p>\n

    \"Salesforce<\/a>
    Salesforce Get ANT version<\/figcaption><\/figure>\n

    In above screen you can see that before copying tools.jar<\/strong> I was getting warning.<\/p>\n

    Step 4:<\/strong><\/p>\n

    Login to salesforce and navigate to “Your Name |Setup | Develop | Tools”<\/strong>\u00a0and download “Force.com Migration tool”<\/strong>.<\/p>\n

    Unzip the downloaded file to the directory of your choice. Copy the “ant-salesforce.jar”<\/strong> file from the unzipped file into the ant lib directory.<\/p>\n

    To start with deployment using ANT, we will need “build.xml”<\/strong> and “build.properties”<\/strong> file. As there is no need of “build.properties” however its good to have it so that the configuration related settings are in different file. You can copy both files from “sample” folder of unzipped content from salesforce. Following is the structure of “build.properties” file.<\/p>\n

    \r\n# build.properties\r\n# Specify the login credentials for the desired Salesforce organization\r\nsf.username = &amp;amp;amp;lt;SFDCUserName&amp;amp;amp;gt;\r\nsf.password = &amp;amp;amp;lt;SFDCPasswrd&amp;amp;amp;gt;\r\n#sf.pkgName = &amp;amp;amp;lt;Insert comma separated package names to be retrieved&amp;amp;amp;gt;\r\n#sf.zipFile = &amp;amp;amp;lt;Insert path of the zipfile to be retrieved&amp;amp;amp;gt;\r\n#sf.metadataType = &amp;amp;amp;lt;Insert metadata type name for which listMetadata or bulkRetrieve operations are to be performed&amp;amp;amp;gt;\r\n# Use 'https:\/\/login.salesforce.com' for production or developer edition (the default if not specified).\r\n# Use 'https:\/\/test.salesforce.com for sandbox.\r\nsf.serverurl = https:\/\/test.salesforce.com\r\n<\/pre>\n
    Step 5:<\/strong>
    \nCopy all folders with source code from source organization using eclipse. Lets say the root folder name is “test1”.
    \nCreate “build.properties”<\/strong>\u00a0from above code snippet or copy it from unzipped folder. Now create “build.xml”<\/strong> needed by ANT. Following is the example of build.xml file:<\/p>\n
    \r\n<project name="Shivasoft ANT Tutorial" default="deployCode" basedir="." xmlns:sf="antlib:com.salesforce">\r\n    <property file="build.properties"\/>\r\n    <property environment="env"\/>\r\n    <!-- Shows deploying code &amp;amp;amp;amp; running tests for code in directory -->\r\n    <target name="deployCode" depends="proxy">\r\n      <sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="test1">\r\n        <runTest>TestClassName<\/runTest>\r\n      <\/sf:deploy>\r\n    <\/target>\r\n    <!-- Shows removing code; only succeeds if done after deployCode -->\r\n    <target name="undeployCode">\r\n      <sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="removecodepkg"\/>\r\n    <\/target>\r\n\t<target name="proxy">\r\n\t\t<property name="proxy.host" value=" ProxyURL " \/>\r\n\t\t<property name="proxy.port" value="1234" \/>\r\n\t\t<property name="proxy.user" value="UserName" \/>\r\n\t\t<property name="proxy.pwd" value="Password" \/>\r\n\t\t<setproxy proxyhost="${proxy.host}" proxyport="${proxy.port}" proxyuser="${proxy.user}" proxypassword="${proxy.pwd}" \/>\r\n\t<\/target>\r\n<\/project>\r\n<\/pre>\n
    Attribute “deployRoot<\/strong>” means the root folder from which the code should be copied and tag \u00a0means the testclasses which should run after the deployment. At last, go to the folder “test1” from command line and run command “ant deployCode”.<\/p>\n
     <\/p>\n
    \"Salesforce<\/a>
    Salesforce Migration using-ANT<\/figcaption><\/figure>\n
    Checking the status of the task:<\/strong><\/span>
    \nTo know the status of task you can run command:
    \nAnt targetName <\/strong>-Dsf.asyncRequestId=requestID <\/strong><\/p>\n
    Using Proxy in ANT migration tool:<\/strong><\/span>
    \nIf your organization uses the proxy then add below target in “build.xml” and specify this target as dependent.<\/p>\n
    \r\n<target name="proxy">\r\n\t\t<property name="proxy.host" value=" ProxyURL " \/>\r\n\t\t<property name="proxy.port" value="1234" \/>\r\n\t\t<property name="proxy.user" value="UserName" \/>\r\n\t\t<property name="proxy.pwd" value="Password" \/>\r\n\t\t<setproxy proxyhost="${proxy.host}" proxyport="${proxy.port}" proxyuser="${proxy.user}" proxypassword="${proxy.pwd}" \/>\r\n\t<\/target>\r\n<\/pre>\n
    Retrieve content from Salesforce Organization:<\/strong><\/span>
    \ncreate “package.xml” for the list of component to be retrieved and add following task in “build.xml”.<\/p>\n
    \r\n<!-- Retrieve an unpackaged set of metadata from your org -->\r\n<!-- The file unpackaged\/package.xml lists what is to be retrieved -->\r\n<target name="test" depends="proxy">\r\n  <mkdir dir="retrieveUnpackaged"\/>\r\n  <!-- Retrieve the contents into another directory -->\r\n  <sf:retrieve username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" retrieveTarget="retrieveUnpackaged" unpackaged="unpackaged\/package.xml" unzip="false" \/>\r\n<\/target>\r\n<\/pre>\n
    “Unzip” attribute specifies that the code retrieved should be in Zip format or not. By default the value is true means it will not in zip format.<\/p>\n
    Delete components from Salesforce Organization using “destructiveChanges.xml” :<\/strong>
    \nIn some cases, we may want to delete some components like Object or fields from Salesforce Organization. In this case, Only “package.xml” will not work. We need to create “destructiveChanges.xml” file also. Syntax for this file is exactly same as of “package.xml”, except that here we cannot define wildcards. So, to undeploy anything from Salesforce org, we need two xml files – “package.xml” and “destructiveChanges.xml<\/span>“.<\/p>\n
    Below is complete code of build.xml, which includes retrieve, Undeploy and Deploy commands.<\/p>\n
    \r\n<project name="Shivasoft Demo Org" default="deployCode" basedir="." xmlns:sf="antlib:com.salesforce">\r\n\t<!-- Get all settings like Server Path, username and passwords from "build.properties" file -->\r\n    <property file="build.properties"\/>\r\n    <property environment="env"\/>\r\n\t<!-- Sequence 1 - Get All information from Source, Retrieve the contents into Src directory -->\r\n\t<target name="SFDCFetch">\r\n\t  <!-- -->\r\n\t  <sf:retrieve username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" retrieveTarget="src" unpackaged="package.xml"\/>\r\n\t<\/target>\r\n\r\n\t<!-- Sequence 3 - Deploy to Target System, Package.xml is present in Src folder -->\r\n\t<target name="deploy">\r\n      <sf:deploy username="${sf1.username}" password="${sf1.password}" serverurl="${sf.serverurl}" deployroot="Src">\r\n      <\/sf:deploy>\r\n    <\/target> \r\n\r\n\t<!-- Sequence 2 - If you want to remove some components, destructiveChanges.xml and Package.xml present in Delete Folder -->\r\n\t<target name="unDeploy">\r\n      <sf:deploy username="${sf1.username}" password="${sf1.password}" serverurl="${sf.serverurl}" deployroot="Delete">\r\n      <\/sf:deploy>\r\n    <\/target>\r\n<\/project>\r\n<\/pre>\n
    You may also be interested to check how to automate daily Salesforce backup<\/a>.<\/p>\n
    How to Create Change set from Package.xml<\/h3>\n
    Step 1 :<\/strong> Create Empty Changeset, lets say its name is changeset2
    \nStep 2 :<\/strong> add fullname<\/strong> tag in package.xml. Fullname needs to be the name of changeset created in Step 1<\/p>\n
    \r\n<?xml version="1.0" encoding="UTF-8"?>\r\n<Package xmlns="http:\/\/soap.sforce.com\/2006\/04\/metadata">\r\n<fullName>Changeset2<\/fullName>\r\n    <types>\r\n        <members>AdditionalQuestionTriggerHandler<\/members>\r\n...\r\n...\r\n<\/package>\r\n<\/pre>\n
    Step 3 :<\/strong> src folder name which contains package.xml needs to have changeset name, in our case changeset2<\/p>\n
    How to Create Package.xml from\u00a0Change set<\/h3>\n
    Use below ANT script<\/p>\n
    \r\n<target name="retrieveChangeset">  \r\n  <sf:retrieve \r\nusername="${sf.username}" \r\npassword="${sf.password}" \r\nserverurl="${sf.serverurl}" \r\nretrieveTarget="changesetfolder" \r\npackageNames="changesetname" \/> \r\n<\/target>\r\n<\/pre>\n
     <\/p>\n
    Update [03-Apr-2017]<\/p>\n
    Question<\/span> : Why Salesforce ANT Migration tool is giving wrong Username, Security token or password error, even when everything is correct ?<\/strong>
    \nAns :<\/strong> If your password contains “$”, then ANT tool ignores this characters. So, to correct this, we need to add one more “$”.<\/p>\n
    Question : I am getting unable to find tools.jar files error. I don’t have access to server so cannot place tools.jar manually. Can I fix this error using build.xml by placing jar files in relative folder?<\/strong><\/p>\n
    Ans :<\/strong> You can include any jar file to be in class path. Add below lines in build.xml. All jar files are placed in lib folder.<\/p>\n
    \r\n<path id="class.path">\r\n<pathelement location="${build}"\/>\r\n<fileset dir=".\/lib">\r\n<include name="**\/*.jar" \/>\r\n<\/fileset>\r\n<\/path>\r\n\r\n<taskdef resource="com\/salesforce\/antlib.xml" uri="antlib:com.salesforce" classpathref="class.path"\/>\r\n<\/pre>\n
    Question : Why I am getting error like\u00a0java.lang.OutOfMemoryError: Java heap space while retrieving metadata from Salesforce.\u00a0<\/strong><\/p>\n
    Ans : It is possible that you are retrieving metadata of some big organization with lots of changes. In this case, Java JVM running on system\u00a0needs more memory (RAM) in order to process it. It can be done in two ways<\/p>\n
    1. Before running ANT command, run below command which will set the RAM allocated for JVM to 1GB. If you are not a Windows user, then use export instead of set in below command.<\/p>\n
    \r\nset ANT_OPTS=-Xmx1g\r\n<\/pre>\n
    2. Problem in above solution is that, you would need to execute set command every time before using ANT. For permanent solution, open ant.bat<\/strong> file in bin folder of ANT installation (Same installation folder referred in ANT_HOME). And, at very first line, write below command and save it.<\/p>\n
    \r\nset ANT_OPTS=-Xmx1g\r\n<\/pre>\n
    I hope this article will help newbie to learn ant migration tool.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Step by Step tutorial of Salesforce Migration using ANT tool with Proxy settings and retrieving content from Salesforce Organization. Also fix some common errors like java.lang.OutOfMemoryError or unable to find tools.jar<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"jz_research_post":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[23,9],"tags":[261,262,452,75,86,329,331,268],"class_list":["post-2892","post","type-post","status-publish","format-standard","hentry","category-configuration","category-salesforce","tag-ant","tag-ant-migration-tool","tag-changeset","tag-deployment","tag-eclipse","tag-java","tag-salesforce","tag-salesforce-migration"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":3902,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/automated-daily-backup-using-ant-migration-tool-and-git\/","url_meta":{"origin":2892,"position":0},"title":"Automated Daily Backup of Salesforce Using ANT Migration Tool and GIT","author":"Jitendra","date":"July 5, 2014","format":false,"excerpt":"In few\u00a0previous articles, I have talked about how to use \"ANT Migration tool in Salesforce\" and \"How to Use EGit plugin in Eclipse to work with Git\". So to make this article short, I assume that you are already familiar with ANT Migration tool provided by Salesforce and Git. During\u2026","rel":"","context":"In "Configuration"","block_context":{"text":"Configuration","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/configuration\/"},"img":{"alt_text":"Salesforce Automated Script for Data Backup Using CommandLine","src":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2014\/07\/Salesforce-Automated-Script-for-Data-Backup-Using-CommandLine.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2014\/07\/Salesforce-Automated-Script-for-Data-Backup-Using-CommandLine.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2014\/07\/Salesforce-Automated-Script-for-Data-Backup-Using-CommandLine.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":5478,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/delete-components-using-ant-migration-tool-video\/","url_meta":{"origin":2892,"position":1},"title":"Delete Components using Ant Migration tool – Video","author":"Jitendra","date":"April 27, 2016","format":false,"excerpt":"This video tutorial shows that how we can delete components like Apex class, trigger from Salesforce using ANT migration tool.","rel":"","context":"In "Salesforce"","block_context":{"text":"Salesforce","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/img.youtube.com\/vi\/3kMGy6OeJAc\/0.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":5595,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/dynamically-remove-xml-content-from-metadata-before-salesforce-deployment-using-xmltask-video\/","url_meta":{"origin":2892,"position":2},"title":"Dynamically remove XML content from metadata before Salesforce deployment using xmlTask – Video","author":"Jitendra","date":"August 18, 2016","format":false,"excerpt":"Example - automatically remove listview before deployment","rel":"","context":"In "Salesforce"","block_context":{"text":"Salesforce","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/"},"img":{"alt_text":"Using XMLTask in ANT for Salesforce Deployment","src":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2016\/08\/2016-07-15.png?fit=922%2C519&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2016\/08\/2016-07-15.png?fit=922%2C519&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2016\/08\/2016-07-15.png?fit=922%2C519&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2016\/08\/2016-07-15.png?fit=922%2C519&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":4276,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/continuous-integration-in-salesforce-using-jenkins-and-git-video-tutorial\/","url_meta":{"origin":2892,"position":3},"title":"Continuous integration in Salesforce Using Jenkins and Git | Video Tutorial","author":"Jitendra","date":"March 23, 2015","format":false,"excerpt":"As your Salesforce Organization undergoes heavy customization and frequent builds, moving changes from one Sandbox to other sandboxes starts taking longer time and effort. Also, in normal Salesforce project, there are chances that you will have minimum three sandboxes likely Developer Sandbox, QA Sandbox and UAT Sandbox. After some time\u2026","rel":"","context":"In "Salesforce"","block_context":{"text":"Salesforce","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/"},"img":{"alt_text":"Salesforce - Jenkins Git Polling Log","src":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2015\/03\/Salesforce-Jenkins-Git-Polling-Log.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2015\/03\/Salesforce-Jenkins-Git-Polling-Log.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2015\/03\/Salesforce-Jenkins-Git-Polling-Log.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2015\/03\/Salesforce-Jenkins-Git-Polling-Log.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":5935,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/continuous-integration-ci-in-salesforce-using-team-foundation-server-tfs-video\/","url_meta":{"origin":2892,"position":4},"title":"Continuous Integration (CI) in Salesforce using Team Foundation Server (TFS) – Video","author":"Jitendra","date":"March 20, 2017","format":false,"excerpt":"Step by step guide to set up Continuous Integration (CI) for Salesforce using Team Foundation Server (TFS) with video tutorial","rel":"","context":"In "Salesforce"","block_context":{"text":"Salesforce","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/"},"img":{"alt_text":"Team Foundation Server (TFS) - New Build definition - Select repository","src":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/03\/Team-Foundation-Server-TFS-New-Build-definition-Select-repository.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/03\/Team-Foundation-Server-TFS-New-Build-definition-Select-repository.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/03\/Team-Foundation-Server-TFS-New-Build-definition-Select-repository.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/03\/Team-Foundation-Server-TFS-New-Build-definition-Select-repository.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6209,"url":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/how-to-retrieve-and-deploy-custom-metadata-types-using-ant\/","url_meta":{"origin":2892,"position":5},"title":"How to Retrieve and Deploy Custom Metadata Types using ANT","author":"Jitendra","date":"August 27, 2017","format":false,"excerpt":"Using Salesforce ANT Migration toolkit to retrieve and deploy custom metadata types with record. Sample Package.xml and ANT script included.","rel":"","context":"In "Salesforce"","block_context":{"text":"Salesforce","link":"https:\/\/www.jitendrazaa.com\/blog\/category\/salesforce\/"},"img":{"alt_text":"Sample of Package.xml to deploy Custom Metadata Types","src":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/08\/Sample-of-Package.xml-to-deploy-Custom-Metadata-Types.png?fit=1051%2C330&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/08\/Sample-of-Package.xml-to-deploy-Custom-Metadata-Types.png?fit=1051%2C330&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/08\/Sample-of-Package.xml-to-deploy-Custom-Metadata-Types.png?fit=1051%2C330&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/08\/Sample-of-Package.xml-to-deploy-Custom-Metadata-Types.png?fit=1051%2C330&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/www.jitendrazaa.com\/blog\/wp-content\/uploads\/2017\/08\/Sample-of-Package.xml-to-deploy-Custom-Metadata-Types.png?fit=1051%2C330&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/posts\/2892","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/comments?post=2892"}],"version-history":[{"count":8,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/posts\/2892\/revisions"}],"predecessor-version":[{"id":6646,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/posts\/2892\/revisions\/6646"}],"wp:attachment":[{"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/media?parent=2892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/categories?post=2892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jitendrazaa.com\/blog\/wp-json\/wp\/v2\/tags?post=2892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}