The following are the complete steps in the deployment process:
Step 1: Application Source Code Export.
Appeon Developer exports the objects in the PBLs to xml files after a preliminary analysis is performed.
Generating DWSQL (There are ODBC / Native Interface in DB Settings in Application Profile Configuration and the purpose of this is to generate DWSQL in the application).
Exporting PB object.
Step 2: Appeon Application File Generation.
Appeon Developer converts the objects in the PBLs into JS files. Please see the following for the mapping.
Application/Global function/Global structure ----> Index.html, Application.js
Window ----> Window.js
Menu ----> Menu.js
Userobject ----> Userobject.js
Datawindow ----> Datawindow.dat
And Appeon Developer also generates two files (AppInfo.xml and Application.xml) for auto updates of the JS files and security verifications.
Step 3: Appeon Application Deployment.
Appeon Developer deploys the following:
Deploying INI file(s) to Appeon Server.
Deploying DataWindow SQL to Appeon Server.
Deploying embedded SQL to Appeon Server.
Deploying Web Service DataWindow Web Service URL to Appeon Server.
Deploying Application settings to Appeon Server.
Deploying Appeon application files (JS or WAR file) to all Web server(s).
Step 3 is related to Appeon Server and Web Servers.
Therefore Appeon Developer not only deploys the Appeon application files to the Web Server but also deploys others such as the spallation values of DW / ESQL / JS to the Appeon Server.
So, there’re only two methods to deploy an app:
1. Deploy an app via the Deploy button in the Appeon Developer (Configure and then deploy);
2. Package an app via the Package button in the Appeon Developer.
You will need to use the above two methods to deploy/package an app from Windows to the Appeon Server if the Appeon server is installed on Linux/Unix.