Exporting an ABL Service

The Export ABL Web Application wizard allows you to package an ABL service as a .WAR file to deploy as a complete web application or to export services incrementally by creating a .ZIP file that contains .PAAR files for each selected ABL REST and ABL Data Object (REST RPC) and .gen and pdo.handlers file for ABL Data Object (WebHandler). If you selected WebSpeed services, .properties or .handlers files are created. You can use the .WAR file or the .ZIP file to deploy the packaged Web application to a remote server.

To export as ABL Web Application:

1. In the Project Explorer view, select the ABL Web App project that contains the ABL services that you want to export as a Web application.

2. Right-click the project and click Export from the context menu. The Export ABL Web Application dialog box opens.

3. The Project drop-down list displays the project you have selected in Step 1. You can select a different project from the drop-down list.

4. In the Destination drop-down list, specify a location or click drop-down displays only the ABL Web App projects in your current workspace.Browse to select a different location for the Web application.

Export ABL services for Progress Application Server to export the services by creating a single .WAR file for all the selected ABL services in the project.

Export services for incremental deployment to export services by creating a .ZIP file that contains .PAAR file for each selected ABL REST, .PAAR and .json files for each selected REST based Data Object Service, .handlers files for selected ABL WebSpeed services, and pdo .handlers and .gen files of WebSpeed based Data Object Services.

6. Select the Service Name check box to select all the services in the project or click the individual ABL services that you want to export..

When you export an ABL Service of any type fully, a .WAR file with PASOE content folder of ABL WebApp project is exported with some other files depending on the ABL Service type as follows:

When you export ABL Service of REST type, .PAAR files for each selected service is generated in the WEB-INF/adapters/rest/servicename location.

When you export ABL Service of WebSpeed type, merge.properties files is generated in the WEB-INF/tlr location. This file contains multiple entries for each handler of the selected services:

When you export REST based ABL Service of Data Object type, .PAAR files for each selected service is generated in the WEB-INF/adapters/rest/servicename location and servicename.json

When you export WebSpeed based ABL Service of Data Object type, merge.properties file is generated the file in the static folder.WEB-INF/tlr file in the location with a single entry as follows:

When you export an ABL Service of any type incrementally, a .ZIP file containing the static folder of ABL WebApp project and the openedge folder in the Web-INF folder is exported with some other files depending on the ABL Service type as follows:

When you export an ABL Service of REST type, .PAAR files for each selected service is generated in the WEB-INF/adapters/rest/servicename location.

When you export an ABL Service of WebSpeed type, servicename.handlers file for each service is created in in WEB-INF/openedge location. Here is an example of .handlers file:

{
"version": "1.0",
"servicename": "sampleWebSpeedservice",
"handlers": [{
"className": "SamplehandlerClass",
"URIs": [
"\/uri1",
"\/uri2"
]
}]
}

When you export a REST based ABL Service of Data Object type, .PAAR files for each selected service is generated in the WEB-INF/adapters/rest/servicename location and servicename.json file in the static folder.

When you export a WebSpeed based ABL Service of Data Object type, servicename.json file in Static folder and servicename.gen file in the WEB-INF/openedge location are generated. A single pdo.handlers file for all the selected services is generated in the WEB-INF/tlr location as follows:

{
"version": "1.0",
"serviceName": "pdo",
"handlers": [{
"className": "OpenEdge.Web.DataObject.DataObjectHandler",
"URIs": ["\/pdo\/"]
}]
}