Appeon requires SQL Server 2000 or newer.

Appeon Server for J2EE Application Servers supports DB2 (Appeon Server for EAServer , WebLogic, WebSphere, or JBoss), but Appeon Server for .NET does not support DB2.

MySQL, Sybase ASA, Sybase ASE, Microsoft SQL Server, Oracle, IBM DB2, Informix, and Teradata.

Appeon Mobile supports EAServer, all mainstream Java application servers and IIS for .NET are supported.

All data is ONLY stored on the server-side DB, unless "Offline Access font-size: medium;">If offline capability is required, then some data must be temporarily cached on the device. Appeon Mobile gives the developer full control and transparency over the data caching and synchronization. We provide APIs allowing developers to decide what data to cache, what sync strategy to use, etc. (Appeon Mobile 1.5 and over)

Please follow the steps below to restart Appeon Server on WebSphere: 1. Stop Appeon Server Stopping WebSphere Application Server will shut down Appeon Server. So first Change to the $WebSphere/AppServer/bin/ folder, for example, /export/home/IBM/WebSphere/AppServer/bin/, and run the_stopServer.sh_ file. ./stopServer.sh server1 2. Starting Appeon Server Change to the $appeon/bin/ folder, for example, /export/home/IBM/WebSphere/AppServer/appeon/bin/ and run the appeonserver.sh file. Wh...

If you have Appeon Web and Appeon Mobile as separate licenses you cannot install them on the same server. The definition of same server is either a) the same physical server that is not virtualized b) the same virtual server in the case of virtualized physical server If you need to install both licenses on the same server you must request an upgrade to the Appeon Universal license

It's not a simple configuration to declare the list of Mobile devises allowed to connect to the mobile application in AEM. However, as part of the customer username/password authentication that they have coded in their PB application, they can add an additional check to make sure that the mobile devise is an authorized one. Appeon provides a PB function the customer can call to retrieve the mobile device ID. The function is: eon_mobile_deviceex.of_getdeviceid() Appeon is not a Web server. It runs...

For .net and EAserver, it is application file, for others Application server, for example: JBoss, WebLogic, etc., it is war file.

INI files are saved in /config/ aws$ini$.xml, for example, /mnt/shell/emulated/0/Android/data/com.appeon.mobile/files/5730031d/config/ aws$ini$.xml Both Appeon Web and Appeon Mobile support INI files and the related functions. Appeon Developer deploys the INI File to the Appeon server and saves them in xml format to the client. Therefore you cannot judge if the INI files exist in Appeon the way you judge them via FileExist in the PB C/S architecture.

You can try deploy the application to the production server with the methods below. Method 1: Package a server deployment project by using the Appeon Developer, then copy package file to production server and install it. For more details please refer to: https://www.appeon.com/support/documents/appeon_online_help/2016/appeon_developer_user_guide/ch10s01.html [https://www.appeon.com/support/documents/appeon_online_help/2016/appeon_developer_user_guide/ch10s01.html] Method 2: Configure the Appeon Server and...