We have already purchased Appeon 2.7. Regarding our project
our application size is approx. 40 MB and we are using PB
9.0, EAServer , iAnywhere (after couple of days we ll use
Oracle 8i and PB 8.0). We are facing following problems at
the time of migration ::
1) Once application deployed, second time deployment (full /
incremental) becomes very slow. Why?
2) System hung up after 3 or 4 time of deployment.
3) While deploying the application, in the third step, after
completion of 100% process, an error occurs -- Error :
commit local appeon Server, can't get connected.
4)Deployment Process takes ample of time, about 4 hrs.(full
deployment). How can we reduce the time?
5) What can we do just for testing 1 component other than
deploying it to web? Right now, we are deploying the
application using "incremental deployment" option.
6)how can we remove the session ID after closing an Internet
Explorer / Application.
Awaiting for your prompt reply.
(Sr. S/w Engg.)
From: Niraj Choksi
Subject: problem in migration
X-Mailer: WebNews to Mail Gateway v1.1t
Date: 29 Sep 2004 05:02:21 -0700
X-Trace: forums-1-dub 1096459341 10.22.241.41 (29 Sep 2004 05:02:21 -0700)
X-Original-Trace: 29 Sep 2004 05:02:21 -0700, 10.22.241.41
Xref: forums-1-dub sybase.public.appeon:441
Article PK: 20747
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: problem in migration
Content-Type: text/plain; charset="us-ascii"
Date: 30 Sep 2004 03:34:50 -0700
X-Trace: forums-1-dub 1096540490 18.104.22.168 (30 Sep 2004 03:34:50 -0700)
X-Original-Trace: 30 Sep 2004 03:34:50 -0700, web110.discountasp.net
Xref: forums-1-dub sybase.public.appeon:444
Article PK: 12543
Thanks for choosing Appeon!
Here are the feedback from Appeon engineers on the six issues mentioned in your
1) Issue: Full/incremental deployment very slow
<ANS> It is strange that the second time deployment is slower than the first
time, but please be aware that the Web deployment is a process that can be very
CPU and memory intensive. Before you do the application deployment, free most
of the computer resources.
Another suggestion from Appeon engineer is: do full/incremental build for the
PowerBuilder application in PowerBuilder IDE before doing the deployment. It
saves some time for Appeon on analyzing the code.
2) Issue: System hung up after 3 to 4 deployment
<ANS> If it happens, please restart EAServer, restart PowerBuilder, and kill the
PBParser.exe in the Task Manager. If you provide the source code we can better
locate the problem. But based on your description, we suspect that there must
be many unsupported features in the application that have affected the Developer
Performance. The recommendation is, you first perform feature analysis for the
application, remove most of the unsupported features, and then deploy the
3) Error: commit local appeon Server, can't get connected.
<ANS> This is because EAServer is not started. Please start EAServer that
Appeon Server is installed to from the Windows Start menu.
4) Deployment Process takes ample of time
<ANS> The best suggestion is that you upgrade to Appeon 2.8. Appeon 2.8 is much
much better that Appeon 2.7 in both the deployment performance (3X faster) and
runtime performance (3-6X faster). Please contact Sybase sales for getting
5) Testing one component instead of deploying to the Web
<ANS> In this case, please make full use of Appeon Developer preview functions.
You may need to refer to the Appeon Developer User Guide for detailed
instructions on how to do previews successfully.
6) Remove the session ID
<ANS> The session ID is automatically killed and released once you exit the Web
application. You can also run AEM and go to Server Properties | Active Sessions
for manually killing a session.
On 29 Sep 2004 05:02:21 -0700,