<![CDATA[Novalys Help Desk]]> <![CDATA[Appeon Web - What can I do with Appeon WEB for PowerBuilder?]]> Using ONLY existing PowerBuilder programming skills and working ONLY with the familiar PowerBuilder IDE, Appeon for PowerBuilder enables you to:

· Immediately starting building new n-tier Web applications, which deploy to either .NET or Java platform, with the unbeatable ease and productivity of PowerBuilder.

· Deploy existing PowerBuilder client/server applications to the Web and either .NET or Java platform in the shortest amount of time, at the lowest cost, and with the least risk.


]]> <![CDATA[Do I need any additional skills besides PowerBuilder to use Appeo...]]> to the page-by-page metaphor.


]]> <![CDATA[Appeon Web - Is the PB-to-Web process really 100% automatic? ]]> Normal 0 21 MicrosoftInternetExplorer4

The Web migration process that reads PowerBuilder PBLs and generates an n-tier Web application is 100% automated with Appeon for PowerBuilder. If you build a new application with PowerBuilder to Appeon standards, it can in fact be deployed to the Web at the click of a button. However, some work, typically very minimal, will be required to deploy an existing and traditionally client/server application to the Web (i.e. perform a Web conversion).

An Appeon Web conversion is actually much simpler than typical Web migrations. In an Appeon Web conversion, you will only need to perform standard PowerBuilder client/server programming. The PowerBuilder programming you perform is to
1) Remove/workaround unsupported PowerBuilder code that cannot be converted to the Web and that is critical in running the application in PowerBuilder, and
2) Optimize the PowerBuilder code to achieve better Web runtime performance (if desired). 


]]> <![CDATA[Appeon Web - How is Appeon for PowerBuilder different from other ...]]> Normal 0 21 MicrosoftInternetExplorer4 Appeon for PowerBuilder is different from other Web migration framework because:
  1. Once the PowerBuilder application has been modified to meet the requirements for moving to the Web, Appeon automatically transforms entire PowerBuilder applications to n-tier Web applications many times faster than any other development methodology. Other migration frameworks are essentially rewrites, only moving very limited pieces of your application.
  2.  Appeon utilizes only one set of native PowerBuilder source code for both the client/server and Web deployment of the application. This is useful for customers that have business requirements to offer both deployment methods without incurring cost of 2 separate projects. 
  3.  Appeon requires only PowerBuilder skills. Other solutions typically require HTML/JavaScript and Java/.NET skills, as well as a deep understanding of issues encountered developing Web applications for the n-tier architecture, such as security, performance, and scalability.
]]> <![CDATA[What is Appeon for PowerBuilder?]]> Appeon for PowerBuilder (APB) is a solution for PowerBuilder developers to build Rich Internet Applications (RIA) rapidly and easily. APB automatically deploys any existing Client/Server applications to the Web with minimal effort. There is no faster or easier way for PowerBuilder developers to embrace the Web and Java or .NET technologies.

  • No need to retool your PowerBuilder development team and force them to work with less productive tools
  • No need to throw away engineering-years of investments in your existing PowerBuilder applications
  • No need to retrain your end-users to work with a new inferior page-by-page user interface

Appeon for PowerBuilder consists of a PowerBuilder IDE plug-in (Appeon Developer) and the Java/.NET application server runtime (Appeon Server).

]]> <![CDATA[Appeon Mobile - Are you using HTML5 or creating real native targe...]]> No, we do NOT use HTML.
We are producing real Native targets that allow for native integration with the mobile SDK, richer UI and functionality, and faster performance.]]> <![CDATA[Appeon Mobile - What is the email to request a copy of Appeon Mob...]]> appeon.mobile@novalys.net]]> <![CDATA[Appeon Web -Factors affecting Appeon performance ]]> The performance of the application depends on the complexity of the application itself and how it is coded, the hardware and the network connection.  You will find our recommendations below concerning these three points:

•  In terms of hardware:

  1. Type of of processors: at least 1 multi-core CPU per server running at 1.8 GHz or faster.
  2. RAM memory: at least 2 GB of free RAM (4 GB is recommended) plus 2GB free hard drive space (for Appeon Server Installation only). In general, we recommend 8G memory or above for 100 concurrent users sessions.
  3. Storage:  it depends on the volume of your application. You will need a similar volume as the volume of your PB code multiplied by the number of deployments.

•  In terms of network connectivity, we recommend a minimum of 100 Kbps per user with a max latency of 150 ms and zero packet loss.

•  In terms of code, there are number of factors that can affect the performance. But the most important and most common is excessive server calls imitated by the PB code.  A server call occurs any time there is a call to the database. 

 

 

]]> <![CDATA[Appeon Web - How to run multiple application sessions ]]> Multiple Appeon applications cannot be run in the same Internet Explorer session. You will find more information below:

With IE 7, it is unsupported to tab browse multiple Appeon applications deployed with the same Appeon version, as all tabs are sharing the same session in IE 7.

With IE 8\9\10, by default, you can run no more than two Appeon web applications in different tab pages, or different IE browsers.  If you want to run multiple Appeon Web applications (more than 3) with IE 8\9\10, you can:


1. Click the New Session item on the File menu of IE 8\9. Then access Appeon applications in the new opened IE browser.
2. Run iexplore.exe with the -nomerge parameter so that whenever you open a new IE browser, new session will be created. For example, you can change the shortcut of IE 8\9 to "C:\Program Files\Internet Explorer\iexplore.exe" –nomerge.

]]> <![CDATA[Differences between ISUG's NFR licence and Appeon DE License]]>

The ISUG license is a developer license, with the same functionnalities than a Appeon Developer license.

There’s no functional difference between Appeon official DE license and ISUG DE license except the subsequent two points.

1)      ISUG license comes with no support or maintenance;

2)      One ISUG member can only get one ISUG DE license;

 

 

]]> <![CDATA[PB applications access to the local hard drive ]]> PB Application running in Appeon can access the local hard drive.You can use the ‘fileExists’, ‘FileOpen’, ‘FileRead’ and ‘FileWrite’ functions.

]]> <![CDATA[Appeon Web - How to open and copy a file on the mapped Drive in L...]]> Appeon supports to open a file on the mapped Drive and copy file to a mapped Drive, but it requires that the mapped drive ( X:\) is added on every client, and every client has read and write permission to this mapped drive. 

It requires mapping the X:\Drive for every client machine, but not the Application Server, and you cannot map the X:\Drive for a client machine in WAN, so it works in LAN only. 

If you want to upload and download files on the web in WAN, please use the AppeonFileService I mentioned above.

Appeon provides a AppeonFileService object which is for downloading and uploading files on the web, please refer to Appeon Help | Appeon Workarounds Guide | Appeon Workarounds PBL Reference | File Upload and Download chapter for details.


]]> <![CDATA[Can Appeon Web and Appeon Mobile be in the same machine? ]]>

Appeon Web 6.6 developer license will come with the Mobile module and vice versa. Then you will be able to have both: Appeon Web and Appeon Mobile on your development machine. 

However, when talking about the Application server, you must use different machines per version: one server for Appeon Mobile and a separate server for Appeon Web.

If you just have one server available you may use VMWare and create an instance per version or purchase Appeon Universal version (includes Appeon Web and Appeon Mobile)

]]> <![CDATA[Average size of the downloaded items on the client]]> What's the average size of the downloaded items on the client machine?

Appeon ActiveX’s size is around 5.9 MB on 32bit machine and 9.26MB on 64bit machine.  

Other files (like html, JS file, dll/ocx, picture files, ini, etc.) will be downloaded to the client side, but the number and size of the these files really depend on the each application.  

If you want to know the size of your application once downloaded on the client machine, you can deploy it locally and run the application.

You will find the download files by default under C:\Users\<USERNAME>\AppData\Roaming\appeon\<APPLICATION_NAME>

The ini file will be stored by default with the IE cookies.

]]> <![CDATA[Appeon Web 6.6 & 7.0]]> Appeon 6.6 has been released on May 16 2013.  It supports MySQL and SAP Hana database, Amazon, Azure, and Rackspace cloud.  It supports IE 10 (without using the compatibility mode that is required if using Appeon 6.5.1), and the Appeon Web debugger works with IE 9 or 10 (instead of only IE 8 as in Appeon 6.5.1).

Appeon 7.0 will be released by the end of 2014 and it will support cross-browser on Windows OS.  It will also  support more modern UI.  But a browser plug-in will still be required.

]]> <![CDATA[Appeon - Performance tuning guide]]> Most of the performance issues that a web-enabled application has are related to the PB code. Once a c/s application is deployed on the WEB with Appeon, the powerscript needs to be tuned. 

You can refer to the Appeon Performance Tuning Guide and to the document "How to debut the Appeon Application "- see attachment.

We also recommend you read Yakov Werde’s article called "Appeon Performance Tuning" (see attached). This article explains why PB code can have problems on the Web  and explains Technique #4 in the Performance Tuning Guide .

From the techniques used in the Performance Tuning Guide, we advise the use of technique # 1 - to move the logic of your application to the stored procedures.

]]> <![CDATA[Important : How to upgrade Appeon Workspace 2013 R2 ?]]> The enterprise provisioning profile in Appeon Workspace (AWS 2013 R2 Build 0110, Build 0126, or Build 0136 (JP) ) will expire on November 7th 2014 and AWS will stop working after that.

You would need to use the latest AWS by following Appeon instructions to solve this issue. 

Note that unless you submitted your own AWS or your app as standalone app to Apple store, you need to follow the instructions to fix this issue.   Read more detailed information and follow instructions from http://demo.appeon.com/awsupdate/upgrade_aws.html.  

Also please note that in the future you won’t need to re-do this procedure since we will merge this change to an Appeon EBF. 

We are sorry for all the inconvenience that we caused and highly appreciate all your understanding and patience that you’ve given to us!

]]> <![CDATA[Appeon Web- Why the Appeon plug-ins is required for Appeon Web Ap...]]> Appeon plug-ins is required for Appeon web application, Appeon uses the standard COM technology. Appeon for PowerBuilder contains some client-side ActiveX plug-ins. 

Just like other popular development software, C++ apps also use some base classes, such as MFC, ATL, etc., or other supporting files and PowerBuilder apps use PBVM, etc. Appeon Active X is similar to the PowerBuilder Virtual Machine (PBVM) except that they are implemented in JavaScript and C++, rendering UI and handling some non-database-related business logic. 
It’s just different in how it is deployed: the related EXE or other supporting files of the app will be installed in the PC’s disk in C/S structure while Appeon uses Micorsoft Active Template Library technology to install the supporting files of the app via COM objects and then demos the PB app logic in downloaded WYSIWYG Web pages.
Appeon plug-in has been digitally signed by verisign (note verisign’s sign and authentication business is actually not taken over by Symantec so in a way Appeon’s security is verified by Symantec) 

]]>