Tailor an ABLApp installation using Ant
- Last Updated: February 11, 2026
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
The default build.xml file in the
instance-name/ablapps/app-name/tlr directory
serves as a template build file for ABL application deployment tailoring. This can be
customized to fit your build needs during application deployment, post-application
deployment, and during other application lifecycle events. The following targets are
defined and called by our tooling.
-
ablapp_deploy—Called when an ABLApp is being prepared to be imported. -
ablapp_deployed—Called when an ABLApp is finished being imported. -
ablapp_export—Called when an ABLApp is being prepared to be exported. -
ablapp_exported—Called when an ABLApp is finished being exported.
PAS for OpenEdge tooling currently does not have support for undeploying an
ABL application in a single command. However, undeploying a web application that is part of
the ABLApp will cause these targets to be called. This is done multiple times as each web
application that comprises the ABLApp is undeployed:
-
ablapp_undeploy—Called when an ABLApp is being prepared to be undeployed. -
ablapp_undeployed—Called when an ABLApp is being prepared to be imported.
The following tailoring build.xml file provides an example of how to set environment variables, compile ABL code, and create and start an OpenEdge database when the ABL application is deployed to a PAS for OpenEdge instance:
|