Appeon > Coding
Yes, other Java Web applications can be integrated with Appeon Web applications. This can be done in a number of ways depending on what you are trying to achieve. There are hooks to integrate at the client-side as well as the server-side, including consuming/exposing business logic via native Java calls or Web services.
The use the PFC modified by Appeon is optional. But we think it would be helpful to use our version of PFC if your are really doing a Web conversion of PFC application using Appeon for PowerBuilder.
Appeon supports .NET Framework 2.0 or above. All .NET code blocks (i.e. #if defined PBWEBFORM …. #endif) must be removed from the PBLs. Appeon cannot parse these. .NET code needs to be deployed as assemblies to IIS and it can either be called via Web services or natively. Most customers prefer to call natively. To do so, please follow these steps: CALLING .NET/COM SERVER COMPONENTS APPLIES TO Appeon Server for .NET. The Appeon Server for .NET is not available in Sybase distribution. For di...
Appeon Mobile supports Mobile SDK Integration, allowing to easily access local mobile resources and peripherals such as mobile cameras, GPS, and so on. Developers will call the mobile SDK from their PB application. The corresponding features will not be simulated under Windows with the Appeon Mobile Emulator, but they will be available after deploying/installing on the mobile device.
The version of the PFC is included in the demo applications installed with Appeon Mobile Developer Edition. Appeon compatible version of the PFC: The framework PBLs are located in C:UsersPublicDocumentsAppeonDeveloper2015appeondemoACF_Framework
In order to preserve the productivity and enable a true code-once-deploy-everywhere experience, the evolutions of the mobile app continue to be coded with PB. The source code can not be modified through Xcode/eclipse
You can set the "outer join syntax" setting in Appeon developer the way you do it in PB. After the settings are done please redeploy your application with full deployment mode.
Appeon mobile will migrate most PB features by using a specific mobile application code generator for each target OS device. Version 1.0 add the mobile SDK integration, starting with the most common/obvious features across iOS and Android, and extending this integration step by step based on customers feedbacks.
When a PowerBuilder application is processed through Appeon, how does Appeon determine which part of the code of the application resides on the application server and which resides in the web page? The file downloading parts are handled on Web Server side; the front PB codes are handled on Client side, and the DB related codes (such as dw, e-sql) and the NVOs are handled on Application Server.
The destination directory should be a relative path to the upload file directory on the file server. ( for ex: the '\\webdev-02\inetpub\PHDOC' is a abolute path). The upload file directory on the file server is the value of file-path in %FileService_HOME%\appeonfileserver.xml (for example: C:\inetpub\wwwroot\fileservice\appeonfileserver.xml), the content of the xml file is like below(the upload file directory on the file server is 'C:\appeon' in this file): Please refer to Appeon Help | Appeon Workar...
Usually this kind of problems are caused by PB codes. You can use Appeon Performance Analyzer to help with the debug of this IE unstable problem.
You can find the source code of the Appeon Mobile sample application on C:\Users\Public\Documents\Appeon\Developer2013\appeondemo
IN APPEON 2015 Please go to the AEM> Welcome > Application > Client Features > Your application > Application title IN APPEON 2013/APPEON 6.6 Please go to the AEM> Welcome > Application Client Features > [acf] to delete the For Developer Use Only from the Application Title (see attached - for dev use only). IN APPEON 6.5 Please go to AEM Console> Application Properties> Basic Information> [your application] (e.g. [xmi_demo]) to remove the title (see attached - change title on APB 6.5)
Not all the print functions are supported by Appeon Mobile. Please see more information here  Links: ------  http://www.appeon.com/support/documents/appeon_online_help/1.5/features_help_for_appeon_mobile/ch07s01s01.html#System_Functions_Print_Functions
In Appeon mobile 1.0 and 1.5 the end user can print through a WiFi printer by calling the AirPrint only. This is determined by iOS but not Appeon, and Appeon just call the system API provided by iOS to implement the print function. Appeon cannot give you specific instructions about how to configure and use this feature. In this link you can see what kind of print functions Appeon supports. In case you need to know more about the configuration or AirPrint please go to apple website  Links: --...
Appeon Mobile 1.0 and 1.5 doesn't support the Run function, only one application can be run on the mobile device for Mobile 1.0 and 1.5.
If your application is SDI architecture the application window will float around. The application window will be bound to the browser window only when the application is MDI architecture.
Appeon 2013 only supports generating the pdf file but doesn't support to open this generated pdf file directly on mobile. Please upload the pdf file to the server via Appeon FileService, then you can open it by web browser on mobile, for example: Inet inet_base inet_base = create inet inet_base.HyperlinkToURL("http://126.96.36.199/pdf/1.pdf ") Links: ------  http://188.8.131.52/pdf/1.pdf
Please create the image for a barcode by using function eon_mobile_barcodeex.of_create(), please refer to Appeon Help | Workarounds & API Guide | Appeon Workarounds PBL Reference | Mobile Device API | Barcode chapter for details.
The TableBlob which is a new feature of PB 12.5 is not supported by Appeon at present, please try to work around this issue by following the steps below: 1. Add column FILE_PATH to datawindow object and have the property 'Display As Picture' checked . 2. Retrieve the blob data from database and write it to a image file. 3. Set the file path above as the value of column FILE_PATH.
If you are using a numeric edit mask type ###,###.00 (comma to separate the groups and point for decimals) in development and that this format is not respected once you deployed your application using Appeon 2013 R2, it is deployed as #.###,00 (points to separate the groups and comma for te decimals), please try the following solution: The issue is caused by the language settings on the mobile device. The PB app also uses the language settings. As shown in the screenshot attached, the text is shown accord...
How can I find Oracle's session ID regarding Appeon session ID and/or Appeon transaction ID ? Please use Dynamic Database Connection to make sure each client uses a different DB user to connect to the database. And then you can determine by using the DB user. Here is the explanation regarding Dynamic Database Connection: Select whether to enable dynamic database connection. When it is on, the LogID and LogPass of the Transaction object will be used to connect to the database; when it is off, the us...
Please refer to the following help for reference: http://www.appeon.com/support/documents/appeon_online_help/2015/installation_guide/bk01ch03s05.html [http://www.appeon.com/support/documents/appeon_online_help/2015/installation_guide/bk01ch03s05.html] Also, please refer to the following help for the AEM configuration backup and exporting/importing an application profile (Please back up these configurations/settings before you migrate your Appeon 6.5 to 2015): AEM Configuration Backup http://www.appeon.co...
The file path is appeongetcachedir() + '/config/aws$ini$.xml', for example: x9*7^^/sdcard/Android/data/com.appeon.mobile/files/1b726971/config/aws$ini$.xml You cannot use fileexists to judge if the ini file exists or not for the Appeon web application. The INI Files tool determines whether the Appeon deployed applications would download XML files that emulate INI files to the clients for profile functions, or directly use the XML files stored in Appeon Server database. Please refer to article below for mor...
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.
Appeon supports Dynamic transaction object to data source mapping, you can create two data sources to connect different database. Please refer to the following steps: 1. Add data source pointing to different database in AEM; 2. Follow below online help documentation to setup transaction object to data source mapping using dynamic transaction in Appeon Web Application rather than doing it in AEM. http://www.appeon.com/support/documents/appeon_online_help/2015/server_configuration_guide_for_net/ch03s05s01.htm...