Export an ABL application (export)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Purpose
Exports an ABL application from an existing PAS for OpenEdge instance into an OpenEdge Archive (.oear) file.
Syntax
|
Parameters
- -appName ABL_app _name
- The name of the ABL Application that will be exported into an OpenEdge Archive (.oear) file. An ABL application is a logical grouping of ABL web applications. It consists of a session manager, one or more multi-session agents, and one or more deployed ABL web applications.
- general_options
- Specify one or more of the general TCMAN options. Run
tcman.sh help exportto see which general options are appropriate. - -archiveBaseName
- Base name of the .oear file. The default is the specified ABL application name
- -archiveClassifier
- Classifier used in archive name.
- -archiveVersion
- Version used in manifest and archive name.
- -destDir
- The output directory for the .oear file. The default is the current directory.
- -instanceDir
- Location of the instance. The default is $CATALINA_BASE.
- -full
- Specifies a full export of oeabl.war-based web applications
as WAR files. If present, the oeabl.war-based web applications are exported
in full as WAR files (for example, ROOT.war). Otherwise, the
tcman exportscript runs a diff of an oeabl.war-based web application against oeabl.war and only includes files modified or added into a zip file. When the OEAR package is deployed to a new instance, thetcman importscript applies - -help
- Prints the help page for the command.
Example
Export the ABL application oepas1 as an .oear file:
|