Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Build Times

10 posts in Appeon (partner product) Last posting was on 2004-01-15 02:05:01.0Z
Matt Bell Posted on 2004-01-05 16:51:04.0Z
Reply-To: "Matt Bell" <matt@argosys.com>
From: "Matt Bell" <matt@argosys.com>
Newsgroups: sybase.public.appeon
Subject: Build Times
Lines: 12
Organization: Argo Systems
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4927.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
NNTP-Posting-Host: www.argosys.com
X-Original-NNTP-Posting-Host: www.argosys.com
Message-ID: <3ff995f8$1@forums-1-dub>
Date: 5 Jan 2004 08:51:04 -0800
X-Trace: forums-1-dub 1073321464 68.157.154.79 (5 Jan 2004 08:51:04 -0800)
X-Original-Trace: 5 Jan 2004 08:51:04 -0800, www.argosys.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:20
Article PK: 20539

Hi All,
We've been testing Appeon here at the office, and the biggest thing I'm
noticing is it takes several days for appeon to analyze our application for
deployment, infact I've yet to actually get it to complete and give me an
analysis report on unsupported features. Is this a configuration issue, or
does it just take that long?

Matt Bell
Argo Systems


Rex Geissler Posted on 2004-01-06 00:36:30.0Z
From: "Rex Geissler" <Rex.Geissler@sybase.com>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub>
Subject: Re: Build Times
Lines: 102
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: vpn-concord-051.sybase.com
X-Original-NNTP-Posting-Host: vpn-concord-051.sybase.com
Message-ID: <3ffa030e@forums-1-dub>
Date: 5 Jan 2004 16:36:30 -0800
X-Trace: forums-1-dub 1073349390 158.159.8.51 (5 Jan 2004 16:36:30 -0800)
X-Original-Trace: 5 Jan 2004 16:36:30 -0800, vpn-concord-051.sybase.com
X-Authenticated-User: appeon
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:22
Article PK: 12343

Hi Matt,

What Appeon version are you using because Appeon 2.7 is usually 5-15 times
faster for the Feature Analysis, first-time Full Application Deployment, and
the subsequent Incremental Deployment is faster and more stable as well?

Here are a few examples based on the following configuration:

· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for Appeon
Developer is 1.8 GHz)
· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4 Build
10501, Appeon 2.7

Size of PBLs in MB Feature Analysis (Min) Full Application
Deployment (Min)
14.5 5
55
20 9
61
7.65 4
24
11.7 8
28
11.9 2
16
10.6 8
28


These are more details from the Appeon 2.7 Developer User Guide:

"8.2 Deployment performance

Web deployment is a process that can be very CPU and memory intensive, so we
recommend you use the most powerful development computer possible for Appeon
Developer.

· Generally, a faster CPU will speed up the entire Web deployment process.
· Large memory is useful to ensure that the memory will not be exhausted
when analyzing a large or complex application.
· For more information regarding system requirements for the development
computer, refer to the system requirements outlined in the Appeon
Installation Guide.
Be sure to close out any unnecessary running programs and Windows services
in order to have the most memory available for the deployment process.

8.3 Deployment duration

Although the deployment process is fully automated, it is not instantaneous.
The deployment process can be very CPU and memory intensive, and take a
significant amount of time depending on the size and complexity of the
application and the processing power of the machine running the deployment.
The following is an example of how long it takes to deploy an application.

For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM converting
an application with 3.29 MB in PBLs (not including images); Task 1 takes two
minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
seconds (for a local deployment)...

Since the initial deployment (full deployment) can be time-consuming, Appeon
has built-in a feature into the Application Deployment Wizard to
dramatically reduce the deployment time for subsequent deployments. This
feature dramatically reduces the deployment time by performing only a
partial rebuild and partial deployment of the application, called
Incremental Deployment. An Incremental Deployment is used when you make
changes to an application after it has been initially deployed, and
re-deploy the application in order to see the changes take effect.

Specifically, an Incremental Deployment will greatly reduce the time for
Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
Incremental Deployment can save up to 80% of the total time. For a remote
deployment, such as an FTP deployment, Task 3 will usually take longer than
a local deployment, since latency and bandwidth is increased.

A third deployment option, Deploy Already Generated Application, can be used
to deploy a previously deployed application to a different server, or
refresh the Web files on a server where the application has already been
deployed. This option eliminates the two most time-consuming steps - it
bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
Generation) and only performs Task 3 (Web Deployment)."

Regards, Rex

"Matt Bell" <matt@argosys.com> wrote in message
news:3ff995f8$1@forums-1-dub...
> Hi All,
> We've been testing Appeon here at the office, and the biggest thing I'm
> noticing is it takes several days for appeon to analyze our application
for
> deployment, infact I've yet to actually get it to complete and give me an
> analysis report on unsupported features. Is this a configuration issue,
or
> does it just take that long?
>
> Matt Bell
> Argo Systems
>
>
>


Anonymous Posted on 2004-01-08 17:23:34.0Z
From: "Anonymous" <Anonymous@Anywhere.net>
Newsgroups: sybase.public.appeon
Organization: 208.29.51.50
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: Build Times
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 64.79.161.46
Message-ID: <3ffd942c$1@forums-2-dub>
X-Original-Trace: 8 Jan 2004 09:32:28 -0800, 64.79.161.46
Lines: 120
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 8 Jan 2004 09:08:57 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 8 Jan 2004 09:23:34 -0800
X-Trace: forums-1-dub 1073582614 10.22.108.75 (8 Jan 2004 09:23:34 -0800)
X-Original-Trace: 8 Jan 2004 09:23:34 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:31
Article PK: 12348

After completed the deployment of a one-screen hello world application, I
started the "auto-pilot" mode deployment of a considerably big application--more
than 100 PBLs totaling more than 100MB. Started since 11PM last night. It
still hasn't finished yet (step one finished in 105 minutes, step 2 in progress
as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did not do any
analysis. The application was migrated from PB7 to PB8 yesterday afternoon.
Passed compiled (full regenerate) in PB8 first, then configured the Appeon
deployment. The configuration does not allow more than one application
object--the current application is the only one allowed to exist in all PBLs. I
simply moved the other application objects out to a backup PBL file.

I will check the deployment again tonight to see if the process really completed
or crashed or some other result. This is a "stress test" for deployment.


On 5 Jan 2004 16:36:30 -0800,
in sybase.public.appeon

Rex Geissler <Rex.Geissler@sybase.com> wrote:
>Hi Matt,
>
>What Appeon version are you using because Appeon 2.7 is usually 5-15 times
>faster for the Feature Analysis, first-time Full Application Deployment, and
>the subsequent Incremental Deployment is faster and more stable as well?
>
>Here are a few examples based on the following configuration:
>
>· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for Appeon
>Developer is 1.8 GHz)
>· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4 Build
>10501, Appeon 2.7
>
>Size of PBLs in MB Feature Analysis (Min) Full Application
>Deployment (Min)
>14.5 5
>55
>20 9
>61
>7.65 4
>24
>11.7 8
>28
>11.9 2
>16
>10.6 8
>28
>
>
>These are more details from the Appeon 2.7 Developer User Guide:
>
>"8.2 Deployment performance
>
>Web deployment is a process that can be very CPU and memory intensive, so we
>recommend you use the most powerful development computer possible for Appeon
>Developer.
>
>· Generally, a faster CPU will speed up the entire Web deployment process.
>· Large memory is useful to ensure that the memory will not be exhausted
>when analyzing a large or complex application.
>· For more information regarding system requirements for the development
>computer, refer to the system requirements outlined in the Appeon
>Installation Guide.
>Be sure to close out any unnecessary running programs and Windows services
>in order to have the most memory available for the deployment process.
>
>8.3 Deployment duration
>
>Although the deployment process is fully automated, it is not instantaneous.
>The deployment process can be very CPU and memory intensive, and take a
>significant amount of time depending on the size and complexity of the
>application and the processing power of the machine running the deployment.
>The following is an example of how long it takes to deploy an application.
>
>For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM converting
>an application with 3.29 MB in PBLs (not including images); Task 1 takes two
>minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
>seconds (for a local deployment)...
>
>Since the initial deployment (full deployment) can be time-consuming, Appeon
>has built-in a feature into the Application Deployment Wizard to
>dramatically reduce the deployment time for subsequent deployments. This
>feature dramatically reduces the deployment time by performing only a
>partial rebuild and partial deployment of the application, called
>Incremental Deployment. An Incremental Deployment is used when you make
>changes to an application after it has been initially deployed, and
>re-deploy the application in order to see the changes take effect.
>
>Specifically, an Incremental Deployment will greatly reduce the time for
>Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
>Incremental Deployment can save up to 80% of the total time. For a remote
>deployment, such as an FTP deployment, Task 3 will usually take longer than
>a local deployment, since latency and bandwidth is increased.
>
>A third deployment option, Deploy Already Generated Application, can be used
>to deploy a previously deployed application to a different server, or
>refresh the Web files on a server where the application has already been
>deployed. This option eliminates the two most time-consuming steps - it
>bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
>Generation) and only performs Task 3 (Web Deployment)."
>
>Regards, Rex
>
>
>"Matt Bell" <matt@argosys.com> wrote in message
>news:3ff995f8$1@forums-1-dub...
>> Hi All,
>> We've been testing Appeon here at the office, and the biggest thing I'm
>> noticing is it takes several days for appeon to analyze our application
>for
>> deployment, infact I've yet to actually get it to complete and give me an
>> analysis report on unsupported features. Is this a configuration issue,
>or
>> does it just take that long?
>>
>> Matt Bell
>> Argo Systems
>>
>>
>>
>
>


Rex Geissler Posted on 2004-01-08 21:16:08.0Z
From: "Rex Geissler" <Rex.Geissler@sybase.com>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub>
Subject: Re: Build Times
Lines: 164
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: rgeissle-w2k.sybase.com
X-Original-NNTP-Posting-Host: rgeissle-w2k.sybase.com
Message-ID: <3ffdc898$1@forums-1-dub>
Date: 8 Jan 2004 13:16:08 -0800
X-Trace: forums-1-dub 1073596568 10.20.20.145 (8 Jan 2004 13:16:08 -0800)
X-Original-Trace: 8 Jan 2004 13:16:08 -0800, rgeissle-w2k.sybase.com
X-Authenticated-User: appeon
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:32
Article PK: 20541

Appeon Developer PC Hardware requirements are the following:

· A Pentium-class processor running at 1.8 GHz or faster
· At least 512 MB RAM (1 GB RAM recommended)
· 250MB available hard drive space (for Appeon Developer installation only).
Each PowerBuilder application conversion project will require additional
hard drive space based on the size of the PowerBuilder application.

Appeon 2.7 only supports applications with PBLs total up to 50 MB. There is
a whitepaper available to help break up applications into apps totalling
less than 50 MB.

Rex

"Anonymous" <Anonymous@Anywhere.net> wrote in message
news:3ffd942c$1@forums-2-dub...
> After completed the deployment of a one-screen hello world application, I
> started the "auto-pilot" mode deployment of a considerably big
application--more
> than 100 PBLs totaling more than 100MB. Started since 11PM last night.
It
> still hasn't finished yet (step one finished in 105 minutes, step 2 in
progress
> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did not do
any
> analysis. The application was migrated from PB7 to PB8 yesterday
afternoon.
> Passed compiled (full regenerate) in PB8 first, then configured the Appeon
> deployment. The configuration does not allow more than one application
> object--the current application is the only one allowed to exist in all
PBLs. I
> simply moved the other application objects out to a backup PBL file.
>
> I will check the deployment again tonight to see if the process really
completed
> or crashed or some other result. This is a "stress test" for deployment.
>
>
> On 5 Jan 2004 16:36:30 -0800,
> in sybase.public.appeon
> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >Hi Matt,
> >
> >What Appeon version are you using because Appeon 2.7 is usually 5-15
times
> >faster for the Feature Analysis, first-time Full Application Deployment,
and
> >the subsequent Incremental Deployment is faster and more stable as well?
> >
> >Here are a few examples based on the following configuration:
> >
> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for
Appeon
> >Developer is 1.8 GHz)
> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4 Build
> >10501, Appeon 2.7
> >
> >Size of PBLs in MB Feature Analysis (Min) Full Application
> >Deployment (Min)
> >14.5 5
> >55
> >20 9
> >61
> >7.65 4
> >24
> >11.7 8
> >28
> >11.9 2
> >16
> >10.6 8
> >28
> >
> >
> >These are more details from the Appeon 2.7 Developer User Guide:
> >
> >"8.2 Deployment performance
> >
> >Web deployment is a process that can be very CPU and memory intensive, so
we
> >recommend you use the most powerful development computer possible for
Appeon
> >Developer.
> >
> >· Generally, a faster CPU will speed up the entire Web deployment
process.
> >· Large memory is useful to ensure that the memory will not be exhausted
> >when analyzing a large or complex application.
> >· For more information regarding system requirements for the development
> >computer, refer to the system requirements outlined in the Appeon
> >Installation Guide.
> >Be sure to close out any unnecessary running programs and Windows
services
> >in order to have the most memory available for the deployment process.
> >
> >8.3 Deployment duration
> >
> >Although the deployment process is fully automated, it is not
instantaneous.
> >The deployment process can be very CPU and memory intensive, and take a
> >significant amount of time depending on the size and complexity of the
> >application and the processing power of the machine running the
deployment.
> >The following is an example of how long it takes to deploy an
application.
> >
> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
converting
> >an application with 3.29 MB in PBLs (not including images); Task 1 takes
two
> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
> >seconds (for a local deployment)...
> >
> >Since the initial deployment (full deployment) can be time-consuming,
Appeon
> >has built-in a feature into the Application Deployment Wizard to
> >dramatically reduce the deployment time for subsequent deployments. This
> >feature dramatically reduces the deployment time by performing only a
> >partial rebuild and partial deployment of the application, called
> >Incremental Deployment. An Incremental Deployment is used when you make
> >changes to an application after it has been initially deployed, and
> >re-deploy the application in order to see the changes take effect.
> >
> >Specifically, an Incremental Deployment will greatly reduce the time for
> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
> >Incremental Deployment can save up to 80% of the total time. For a
remote
> >deployment, such as an FTP deployment, Task 3 will usually take longer
than
> >a local deployment, since latency and bandwidth is increased.
> >
> >A third deployment option, Deploy Already Generated Application, can be
used
> >to deploy a previously deployed application to a different server, or
> >refresh the Web files on a server where the application has already been
> >deployed. This option eliminates the two most time-consuming steps - it
> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
> >Generation) and only performs Task 3 (Web Deployment)."
> >
> >Regards, Rex
> >
> >
> >"Matt Bell" <matt@argosys.com> wrote in message
> >news:3ff995f8$1@forums-1-dub...
> >> Hi All,
> >> We've been testing Appeon here at the office, and the biggest thing I'm
> >> noticing is it takes several days for appeon to analyze our application
> >for
> >> deployment, infact I've yet to actually get it to complete and give me
an
> >> analysis report on unsupported features. Is this a configuration
issue,
> >or
> >> does it just take that long?
> >>
> >> Matt Bell
> >> Argo Systems
> >>
> >>
> >>
> >
> >


"Anonymous" <Anonymous Posted on 2004-01-09 17:06:25.0Z
From: "Anonymous" <Anonymous@frustrated_about_appeon.net>
Newsgroups: sybase.public.appeon
Organization: 208.29.51.50
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: Build Times
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 64.79.161.46
Message-ID: <3ffee1aa$1@forums-2-dub>
X-Original-Trace: 9 Jan 2004 09:15:22 -0800, 64.79.161.46
Lines: 174
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 9 Jan 2004 08:51:42 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 9 Jan 2004 09:06:25 -0800
X-Trace: forums-1-dub 1073667985 10.22.108.75 (9 Jan 2004 09:06:25 -0800)
X-Original-Trace: 9 Jan 2004 09:06:25 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:33
Article PK: 20543

I cut down the size of PBL files. The deployment using appeon 2.7 is a total
failure: it gets stuck at the end of the second step for more than 8 hours,
after the log info reaches this line----"Generating index index.html". This
symptom is repeatable.

BTW, the full compile of the app in PB8.04 environment is quick.

On 8 Jan 2004 13:16:08 -0800,
in sybase.public.appeon

Rex Geissler <Rex.Geissler@sybase.com> wrote:
>Appeon Developer PC Hardware requirements are the following:
>
>· A Pentium-class processor running at 1.8 GHz or faster
>· At least 512 MB RAM (1 GB RAM recommended)
>· 250MB available hard drive space (for Appeon Developer installation only).
>Each PowerBuilder application conversion project will require additional
>hard drive space based on the size of the PowerBuilder application.
>
>Appeon 2.7 only supports applications with PBLs total up to 50 MB. There is
>a whitepaper available to help break up applications into apps totalling
>less than 50 MB.
>
>Rex
>
>
>"Anonymous" <Anonymous@Anywhere.net> wrote in message
>news:3ffd942c$1@forums-2-dub...
>> After completed the deployment of a one-screen hello world application, I
>> started the "auto-pilot" mode deployment of a considerably big
>application--more
>> than 100 PBLs totaling more than 100MB. Started since 11PM last night.
>It
>> still hasn't finished yet (step one finished in 105 minutes, step 2 in
>progress
>> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did not do
>any
>> analysis. The application was migrated from PB7 to PB8 yesterday
>afternoon.
>> Passed compiled (full regenerate) in PB8 first, then configured the Appeon
>> deployment. The configuration does not allow more than one application
>> object--the current application is the only one allowed to exist in all
>PBLs. I
>> simply moved the other application objects out to a backup PBL file.
>>
>> I will check the deployment again tonight to see if the process really
>completed
>> or crashed or some other result. This is a "stress test" for deployment.
>>
>>
>> On 5 Jan 2004 16:36:30 -0800,
>> in sybase.public.appeon
>> Rex Geissler <Rex.Geissler@sybase.com> wrote:
>> >Hi Matt,
>> >
>> >What Appeon version are you using because Appeon 2.7 is usually 5-15
>times
>> >faster for the Feature Analysis, first-time Full Application Deployment,
>and
>> >the subsequent Incremental Deployment is faster and more stable as well?
>> >
>> >Here are a few examples based on the following configuration:
>> >
>> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for
>Appeon
>> >Developer is 1.8 GHz)
>> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4 Build
>> >10501, Appeon 2.7
>> >
>> >Size of PBLs in MB Feature Analysis (Min) Full Application
>> >Deployment (Min)
>> >14.5 5
>> >55
>> >20 9
>> >61
>> >7.65 4
>> >24
>> >11.7 8
>> >28
>> >11.9 2
>> >16
>> >10.6 8
>> >28
>> >
>> >
>> >These are more details from the Appeon 2.7 Developer User Guide:
>> >
>> >"8.2 Deployment performance
>> >
>> >Web deployment is a process that can be very CPU and memory intensive, so
>we
>> >recommend you use the most powerful development computer possible for
>Appeon
>> >Developer.
>> >
>> >· Generally, a faster CPU will speed up the entire Web deployment
>process.
>> >· Large memory is useful to ensure that the memory will not be exhausted
>> >when analyzing a large or complex application.
>> >· For more information regarding system requirements for the development
>> >computer, refer to the system requirements outlined in the Appeon
>> >Installation Guide.
>> >Be sure to close out any unnecessary running programs and Windows
>services
>> >in order to have the most memory available for the deployment process.
>> >
>> >8.3 Deployment duration
>> >
>> >Although the deployment process is fully automated, it is not
>instantaneous.
>> >The deployment process can be very CPU and memory intensive, and take a
>> >significant amount of time depending on the size and complexity of the
>> >application and the processing power of the machine running the
>deployment.
>> >The following is an example of how long it takes to deploy an
>application.
>> >
>> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
>converting
>> >an application with 3.29 MB in PBLs (not including images); Task 1 takes
>two
>> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
>> >seconds (for a local deployment)...
>> >
>> >Since the initial deployment (full deployment) can be time-consuming,
>Appeon
>> >has built-in a feature into the Application Deployment Wizard to
>> >dramatically reduce the deployment time for subsequent deployments. This
>> >feature dramatically reduces the deployment time by performing only a
>> >partial rebuild and partial deployment of the application, called
>> >Incremental Deployment. An Incremental Deployment is used when you make
>> >changes to an application after it has been initially deployed, and
>> >re-deploy the application in order to see the changes take effect.
>> >
>> >Specifically, an Incremental Deployment will greatly reduce the time for
>> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
>> >Incremental Deployment can save up to 80% of the total time. For a
>remote
>> >deployment, such as an FTP deployment, Task 3 will usually take longer
>than
>> >a local deployment, since latency and bandwidth is increased.
>> >
>> >A third deployment option, Deploy Already Generated Application, can be
>used
>> >to deploy a previously deployed application to a different server, or
>> >refresh the Web files on a server where the application has already been
>> >deployed. This option eliminates the two most time-consuming steps - it
>> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
>> >Generation) and only performs Task 3 (Web Deployment)."
>> >
>> >Regards, Rex
>> >
>> >
>> >"Matt Bell" <matt@argosys.com> wrote in message
>> >news:3ff995f8$1@forums-1-dub...
>> >> Hi All,
>> >> We've been testing Appeon here at the office, and the biggest thing I'm
>> >> noticing is it takes several days for appeon to analyze our application
>> >for
>> >> deployment, infact I've yet to actually get it to complete and give me
>an
>> >> analysis report on unsupported features. Is this a configuration
>issue,
>> >or
>> >> does it just take that long?
>> >>
>> >> Matt Bell
>> >> Argo Systems
>> >>
>> >>
>> >>
>> >
>> >
>
>


Julie Jiang Posted on 2004-01-12 10:21:45.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub> <3ffee1aa$1@forums-2-dub>
Subject: Re: Build Times
Lines: 243
Organization: Appeon Corporation
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4922.1500
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800
X-Original-NNTP-Posting-Host: 61.144.207.54
Message-ID: <4002775c@forums-2-dub>
X-Original-Trace: 12 Jan 2004 02:30:52 -0800, 61.144.207.54
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 12 Jan 2004 02:06:46 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 12 Jan 2004 02:21:45 -0800
X-Trace: forums-1-dub 1073902905 10.22.108.75 (12 Jan 2004 02:21:45 -0800)
X-Original-Trace: 12 Jan 2004 02:21:45 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:36
Article PK: 20545

During the "Generating index index.html" phase, Appeon Developer combines
the generated Web files and creates the Unsupported Features Report for the
application. There are several factors that decide how long this step will
take: number of windows, global structures, global functions, and quantity
of unsupported features in the application. In general, it should take less
than 15 minutes in this step for a 100M application. Obviously, the
described case is abnormal and must have special cause in it.

However, Appeon engineers cannot tell what is the cause based on the
information provided. Can you please reply to the following questions? It
will be very helpful for the engineers to further investigate:
1) There is a PBParser icon on windows tray if the deployment wizard is
working. Please check whether the arrows in the icon turn red steadily.
(If Yes, the PBParser is still running).

2) Whether a UFA_Report.xml is already created in the Web application folder
(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful for
us to judge when the application stops working)

3) Whether a GWF_Report.xml is already created in the Web application folder
(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful for
us to judge when the application stops working)

4) Whether an application.js file is already created (in the
%Appeon%\Developer\appname\release/debug\wcode) ? Is the file empty or with
content?

5) How large is the virtual memory in your machine? The size should be
between 2~4 times of the physical memory.

6) What is the size of the cutdown application? Can you send the application
and database file to Appeon?

If possible, please also send us the error screenshot.

Thanks,
Julie Jiang
Appeon Corporation

"Anonymous" <Anonymous@frustrated_about_appeon.net> wrote in message
news:3ffee1aa$1@forums-2-dub...
> I cut down the size of PBL files. The deployment using appeon 2.7 is a
total
> failure: it gets stuck at the end of the second step for more than 8
hours,
> after the log info reaches this line----"Generating index index.html".
This
> symptom is repeatable.
>
> BTW, the full compile of the app in PB8.04 environment is quick.
>
> On 8 Jan 2004 13:16:08 -0800,
> in sybase.public.appeon
> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >Appeon Developer PC Hardware requirements are the following:
> >
> >· A Pentium-class processor running at 1.8 GHz or faster
> >· At least 512 MB RAM (1 GB RAM recommended)
> >· 250MB available hard drive space (for Appeon Developer installation
only).
> >Each PowerBuilder application conversion project will require additional
> >hard drive space based on the size of the PowerBuilder application.
> >
> >Appeon 2.7 only supports applications with PBLs total up to 50 MB. There
is
> >a whitepaper available to help break up applications into apps totalling
> >less than 50 MB.
> >
> >Rex
> >
> >
> >"Anonymous" <Anonymous@Anywhere.net> wrote in message
> >news:3ffd942c$1@forums-2-dub...
> >> After completed the deployment of a one-screen hello world application,
I
> >> started the "auto-pilot" mode deployment of a considerably big
> >application--more
> >> than 100 PBLs totaling more than 100MB. Started since 11PM last night.
> >It
> >> still hasn't finished yet (step one finished in 105 minutes, step 2 in
> >progress
> >> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did not
do
> >any
> >> analysis. The application was migrated from PB7 to PB8 yesterday
> >afternoon.
> >> Passed compiled (full regenerate) in PB8 first, then configured the
Appeon
> >> deployment. The configuration does not allow more than one application
> >> object--the current application is the only one allowed to exist in all
> >PBLs. I
> >> simply moved the other application objects out to a backup PBL file.
> >>
> >> I will check the deployment again tonight to see if the process really
> >completed
> >> or crashed or some other result. This is a "stress test" for
deployment.
> >>
> >>
> >> On 5 Jan 2004 16:36:30 -0800,
> >> in sybase.public.appeon
> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >> >Hi Matt,
> >> >
> >> >What Appeon version are you using because Appeon 2.7 is usually 5-15
> >times
> >> >faster for the Feature Analysis, first-time Full Application
Deployment,
> >and
> >> >the subsequent Incremental Deployment is faster and more stable as
well?
> >> >
> >> >Here are a few examples based on the following configuration:
> >> >
> >> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for
> >Appeon
> >> >Developer is 1.8 GHz)
> >> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4
Build
> >> >10501, Appeon 2.7
> >> >
> >> >Size of PBLs in MB Feature Analysis (Min) Full Application
> >> >Deployment (Min)
> >> >14.5 5
> >> >55
> >> >20 9
> >> >61
> >> >7.65 4
> >> >24
> >> >11.7 8
> >> >28
> >> >11.9 2
> >> >16
> >> >10.6 8
> >> >28
> >> >
> >> >
> >> >These are more details from the Appeon 2.7 Developer User Guide:
> >> >
> >> >"8.2 Deployment performance
> >> >
> >> >Web deployment is a process that can be very CPU and memory intensive,
so
> >we
> >> >recommend you use the most powerful development computer possible for
> >Appeon
> >> >Developer.
> >> >
> >> >· Generally, a faster CPU will speed up the entire Web deployment
> >process.
> >> >· Large memory is useful to ensure that the memory will not be
exhausted
> >> >when analyzing a large or complex application.
> >> >· For more information regarding system requirements for the
development
> >> >computer, refer to the system requirements outlined in the Appeon
> >> >Installation Guide.
> >> >Be sure to close out any unnecessary running programs and Windows
> >services
> >> >in order to have the most memory available for the deployment process.
> >> >
> >> >8.3 Deployment duration
> >> >
> >> >Although the deployment process is fully automated, it is not
> >instantaneous.
> >> >The deployment process can be very CPU and memory intensive, and take
a
> >> >significant amount of time depending on the size and complexity of the
> >> >application and the processing power of the machine running the
> >deployment.
> >> >The following is an example of how long it takes to deploy an
> >application.
> >> >
> >> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
> >converting
> >> >an application with 3.29 MB in PBLs (not including images); Task 1
takes
> >two
> >> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
> >> >seconds (for a local deployment)...
> >> >
> >> >Since the initial deployment (full deployment) can be time-consuming,
> >Appeon
> >> >has built-in a feature into the Application Deployment Wizard to
> >> >dramatically reduce the deployment time for subsequent deployments.
This
> >> >feature dramatically reduces the deployment time by performing only a
> >> >partial rebuild and partial deployment of the application, called
> >> >Incremental Deployment. An Incremental Deployment is used when you
make
> >> >changes to an application after it has been initially deployed, and
> >> >re-deploy the application in order to see the changes take effect.
> >> >
> >> >Specifically, an Incremental Deployment will greatly reduce the time
for
> >> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
> >> >Incremental Deployment can save up to 80% of the total time. For a
> >remote
> >> >deployment, such as an FTP deployment, Task 3 will usually take longer
> >than
> >> >a local deployment, since latency and bandwidth is increased.
> >> >
> >> >A third deployment option, Deploy Already Generated Application, can
be
> >used
> >> >to deploy a previously deployed application to a different server, or
> >> >refresh the Web files on a server where the application has already
been
> >> >deployed. This option eliminates the two most time-consuming steps -
it
> >> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
> >> >Generation) and only performs Task 3 (Web Deployment)."
> >> >
> >> >Regards, Rex
> >> >
> >> >
> >> >"Matt Bell" <matt@argosys.com> wrote in message
> >> >news:3ff995f8$1@forums-1-dub...
> >> >> Hi All,
> >> >> We've been testing Appeon here at the office, and the biggest thing
I'm
> >> >> noticing is it takes several days for appeon to analyze our
application
> >> >for
> >> >> deployment, infact I've yet to actually get it to complete and give
me
> >an
> >> >> analysis report on unsupported features. Is this a configuration
> >issue,
> >> >or
> >> >> does it just take that long?
> >> >>
> >> >> Matt Bell
> >> >> Argo Systems
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >
> >


Anonymous Posted on 2004-01-12 18:43:11.0Z
From: "Anonymous" <Anonymous@Anywhere.net>
Newsgroups: sybase.public.appeon
Organization: 208.29.51.50
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub> <3ffee1aa$1@forums-2-dub> <4002775c@forums-2-dub>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: Build Times
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 64.79.161.46
Message-ID: <4002ece4$1@forums-2-dub>
X-Original-Trace: 12 Jan 2004 10:52:20 -0800, 64.79.161.46
Lines: 298
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 12 Jan 2004 10:28:12 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 12 Jan 2004 10:43:11 -0800
X-Trace: forums-1-dub 1073932991 10.22.108.75 (12 Jan 2004 10:43:11 -0800)
X-Original-Trace: 12 Jan 2004 10:43:11 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:37
Article PK: 12350

The reply is inserted to the orginal text body below, thanks.


On 12 Jan 2004 02:21:45 -0800,
in sybase.public.appeon

Julie Jiang <julie.jiang@appeon.net> wrote:
>During the "Generating index index.html" phase, Appeon Developer combines
>the generated Web files and creates the Unsupported Features Report for the
>application. There are several factors that decide how long this step will
>take: number of windows, global structures, global functions, and quantity
>of unsupported features in the application. In general, it should take less
>than 15 minutes in this step for a 100M application. Obviously, the
>described case is abnormal and must have special cause in it.
>
>However, Appeon engineers cannot tell what is the cause based on the
>information provided. Can you please reply to the following questions? It
>will be very helpful for the engineers to further investigate:
>1) There is a PBParser icon on windows tray if the deployment wizard is
>working. Please check whether the arrows in the icon turn red steadily.
>(If Yes, the PBParser is still running).
>

Yes. The small icon (double arrow shaped) keeps blinking.


>2) Whether a UFA_Report.xml is already created in the Web application folder
>(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful for
>us to judge when the application stops working)
>


Yes it is.



>3) Whether a GWF_Report.xml is already created in the Web application folder
>(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful for
>us to judge when the application stops working)
>

Probably it is, I will check it again when I go back home. All work currently
is done at home as self-study and evalueation (aka not making money until your
tool works for more complex code)

>4) Whether an application.js file is already created (in the
>%Appeon%\Developer\appname\release/debug\wcode) ? Is the file empty or with
>content?

Yes. BUT only when I hit end process (the process has been running overnight,
longer than 8 hours) the size of the file is apparently too small.

I tried the appeon on another pb app, this one is smaller, 26 MB size. It
finished in 5 hours, more or less, not exact time because I turn it on and left
to do something else. When I check that [app_name].js file, it is 10.6MB size.
It will not be useful either intranet or internet due to the sheer size.



>
>5) How large is the virtual memory in your machine? The size should be
>between 2~4 times of the physical memory.

I set it to 1.5GB in the system setting of win2000 PC


>
>6) What is the size of the cutdown application? Can you send the application
>and database file to Appeon?
>

They are too big, I have to admit. I do have smaller applications. Those are
for small potatoes. They won't be able to afford your appeon. That is why I
spent most of my time in trying bigger applications (25MB to 50MB---your limit
is 50MB in the manual). The big guys will pay but only if it can produce
benefit for them.


>If possible, please also send us the error screenshot.
>


The screen shows a progress bar saying generate index index.html
the blue portion is covering all the length of the bar, with text saying 100%
completion. The finish button and the finish and run button are both disabled.
Cancel button is enabled. I cancelled the process, then ctrl-alt-del to go to
task list, terminate the pbparser and adt.exe.



>Thanks,
>Julie Jiang
>Appeon Corporation
>
>"Anonymous" <Anonymous@frustrated_about_appeon.net> wrote in message
>news:3ffee1aa$1@forums-2-dub...
>> I cut down the size of PBL files. The deployment using appeon 2.7 is a
>total
>> failure: it gets stuck at the end of the second step for more than 8
>hours,
>> after the log info reaches this line----"Generating index index.html".
>This
>> symptom is repeatable.
>>
>> BTW, the full compile of the app in PB8.04 environment is quick.
>>
>> On 8 Jan 2004 13:16:08 -0800,
>> in sybase.public.appeon
>> Rex Geissler <Rex.Geissler@sybase.com> wrote:
>> >Appeon Developer PC Hardware requirements are the following:
>> >
>> >· A Pentium-class processor running at 1.8 GHz or faster
>> >· At least 512 MB RAM (1 GB RAM recommended)
>> >· 250MB available hard drive space (for Appeon Developer installation
>only).
>> >Each PowerBuilder application conversion project will require additional
>> >hard drive space based on the size of the PowerBuilder application.
>> >
>> >Appeon 2.7 only supports applications with PBLs total up to 50 MB. There
>is
>> >a whitepaper available to help break up applications into apps totalling
>> >less than 50 MB.
>> >
>> >Rex
>> >
>> >
>> >"Anonymous" <Anonymous@Anywhere.net> wrote in message
>> >news:3ffd942c$1@forums-2-dub...
>> >> After completed the deployment of a one-screen hello world application,
>I
>> >> started the "auto-pilot" mode deployment of a considerably big
>> >application--more
>> >> than 100 PBLs totaling more than 100MB. Started since 11PM last night.
>> >It
>> >> still hasn't finished yet (step one finished in 105 minutes, step 2 in
>> >progress
>> >> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did not
>do
>> >any
>> >> analysis. The application was migrated from PB7 to PB8 yesterday
>> >afternoon.
>> >> Passed compiled (full regenerate) in PB8 first, then configured the
>Appeon
>> >> deployment. The configuration does not allow more than one application
>> >> object--the current application is the only one allowed to exist in all
>> >PBLs. I
>> >> simply moved the other application objects out to a backup PBL file.
>> >>
>> >> I will check the deployment again tonight to see if the process really
>> >completed
>> >> or crashed or some other result. This is a "stress test" for
>deployment.
>> >>
>> >>
>> >> On 5 Jan 2004 16:36:30 -0800,
>> >> in sybase.public.appeon
>> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
>> >> >Hi Matt,
>> >> >
>> >> >What Appeon version are you using because Appeon 2.7 is usually 5-15
>> >times
>> >> >faster for the Feature Analysis, first-time Full Application
>Deployment,
>> >and
>> >> >the subsequent Incremental Deployment is faster and more stable as
>well?
>> >> >
>> >> >Here are a few examples based on the following configuration:
>> >> >
>> >> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements for
>> >Appeon
>> >> >Developer is 1.8 GHz)
>> >> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4
>Build
>> >> >10501, Appeon 2.7
>> >> >
>> >> >Size of PBLs in MB Feature Analysis (Min) Full Application
>> >> >Deployment (Min)
>> >> >14.5 5
>> >> >55
>> >> >20 9
>> >> >61
>> >> >7.65 4
>> >> >24
>> >> >11.7 8
>> >> >28
>> >> >11.9 2
>> >> >16
>> >> >10.6 8
>> >> >28
>> >> >
>> >> >
>> >> >These are more details from the Appeon 2.7 Developer User Guide:
>> >> >
>> >> >"8.2 Deployment performance
>> >> >
>> >> >Web deployment is a process that can be very CPU and memory intensive,
>so
>> >we
>> >> >recommend you use the most powerful development computer possible for
>> >Appeon
>> >> >Developer.
>> >> >
>> >> >· Generally, a faster CPU will speed up the entire Web deployment
>> >process.
>> >> >· Large memory is useful to ensure that the memory will not be
>exhausted
>> >> >when analyzing a large or complex application.
>> >> >· For more information regarding system requirements for the
>development
>> >> >computer, refer to the system requirements outlined in the Appeon
>> >> >Installation Guide.
>> >> >Be sure to close out any unnecessary running programs and Windows
>> >services
>> >> >in order to have the most memory available for the deployment process.
>> >> >
>> >> >8.3 Deployment duration
>> >> >
>> >> >Although the deployment process is fully automated, it is not
>> >instantaneous.
>> >> >The deployment process can be very CPU and memory intensive, and take
>a
>> >> >significant amount of time depending on the size and complexity of the
>> >> >application and the processing power of the machine running the
>> >deployment.
>> >> >The following is an example of how long it takes to deploy an
>> >application.
>> >> >
>> >> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
>> >converting
>> >> >an application with 3.29 MB in PBLs (not including images); Task 1
>takes
>> >two
>> >> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only 15
>> >> >seconds (for a local deployment)...
>> >> >
>> >> >Since the initial deployment (full deployment) can be time-consuming,
>> >Appeon
>> >> >has built-in a feature into the Application Deployment Wizard to
>> >> >dramatically reduce the deployment time for subsequent deployments.
>This
>> >> >feature dramatically reduces the deployment time by performing only a
>> >> >partial rebuild and partial deployment of the application, called
>> >> >Incremental Deployment. An Incremental Deployment is used when you
>make
>> >> >changes to an application after it has been initially deployed, and
>> >> >re-deploy the application in order to see the changes take effect.
>> >> >
>> >> >Specifically, an Incremental Deployment will greatly reduce the time
>for
>> >> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
>> >> >Incremental Deployment can save up to 80% of the total time. For a
>> >remote
>> >> >deployment, such as an FTP deployment, Task 3 will usually take longer
>> >than
>> >> >a local deployment, since latency and bandwidth is increased.
>> >> >
>> >> >A third deployment option, Deploy Already Generated Application, can
>be
>> >used
>> >> >to deploy a previously deployed application to a different server, or
>> >> >refresh the Web files on a server where the application has already
>been
>> >> >deployed. This option eliminates the two most time-consuming steps -
>it
>> >> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web Files
>> >> >Generation) and only performs Task 3 (Web Deployment)."
>> >> >
>> >> >Regards, Rex
>> >> >
>> >> >
>> >> >"Matt Bell" <matt@argosys.com> wrote in message
>> >> >news:3ff995f8$1@forums-1-dub...
>> >> >> Hi All,
>> >> >> We've been testing Appeon here at the office, and the biggest thing
>I'm
>> >> >> noticing is it takes several days for appeon to analyze our
>application
>> >> >for
>> >> >> deployment, infact I've yet to actually get it to complete and give
>me
>> >an
>> >> >> analysis report on unsupported features. Is this a configuration
>> >issue,
>> >> >or
>> >> >> does it just take that long?
>> >> >>
>> >> >> Matt Bell
>> >> >> Argo Systems
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >
>> >
>
>


Julie Jiang Posted on 2004-01-13 10:09:38.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub> <3ffee1aa$1@forums-2-dub> <4002775c@forums-2-dub> <4002ece4$1@forums-2-dub>
Subject: Re: Build Times
Lines: 376
Organization: Appeon Corporation
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4922.1500
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800
NNTP-Posting-Host: 61.144.207.54
X-Original-NNTP-Posting-Host: 61.144.207.54
Message-ID: <4003c3e2@forums-1-dub>
Date: 13 Jan 2004 02:09:38 -0800
X-Trace: forums-1-dub 1073988578 61.144.207.54 (13 Jan 2004 02:09:38 -0800)
X-Original-Trace: 13 Jan 2004 02:09:38 -0800, 61.144.207.54
X-Authenticated-User: appeon
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:39
Article PK: 20546

Thank you for your prompt feedback. Based on your feedback, Appeon engineer
judges that the Web files have already been generated for the application.

Check in the folder %Appeon%\Developer\Appname\release/debug folder for the
Performance_Report.xml file: if the file exists but is empty, the most
possible reason for the problem is that some syntax in the application goes
abnormal after being migrated from PB 7 to PB 8. The parser cannot
understand the syntax, so it cannot continue its task smoothly.

Nevertheless, since the Web application files are already generated, you can
go to Appeon Developer Wizard and directly deploy the application: Select
the deployment mode as "Deploy already generated application", and Appeon
Developer will go to the step 3 and deploy the generated files to Appeon
Server. Please check whether the Web application can run well.

Still, you will be more than welcomed to send the problematic PowerBuilder
application and database to Appeon for deep debugging.

Thanks,
Julie Jiang
Appeon Corporation

"Anonymous" <Anonymous@Anywhere.net> wrote in message
news:4002ece4$1@forums-2-dub...
> The reply is inserted to the orginal text body below, thanks.
>
>
> On 12 Jan 2004 02:21:45 -0800,
> in sybase.public.appeon
> Julie Jiang <julie.jiang@appeon.net> wrote:
> >During the "Generating index index.html" phase, Appeon Developer combines
> >the generated Web files and creates the Unsupported Features Report for
the
> >application. There are several factors that decide how long this step
will
> >take: number of windows, global structures, global functions, and
quantity
> >of unsupported features in the application. In general, it should take
less
> >than 15 minutes in this step for a 100M application. Obviously, the
> >described case is abnormal and must have special cause in it.
> >
> >However, Appeon engineers cannot tell what is the cause based on the
> >information provided. Can you please reply to the following questions?
It
> >will be very helpful for the engineers to further investigate:
> >1) There is a PBParser icon on windows tray if the deployment wizard is
> >working. Please check whether the arrows in the icon turn red steadily.
> >(If Yes, the PBParser is still running).
> >
>
>
> Yes. The small icon (double arrow shaped) keeps blinking.
>
>
> >2) Whether a UFA_Report.xml is already created in the Web application
folder
> >(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful
for
> >us to judge when the application stops working)
> >
>
>
> Yes it is.
>
>
>
> >3) Whether a GWF_Report.xml is already created in the Web application
folder
> >(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful
for
> >us to judge when the application stops working)
> >
>
> Probably it is, I will check it again when I go back home. All work
currently
> is done at home as self-study and evalueation (aka not making money until
your
> tool works for more complex code)
>
> >4) Whether an application.js file is already created (in the
> >%Appeon%\Developer\appname\release/debug\wcode) ? Is the file empty or
with
> >content?
>
> Yes. BUT only when I hit end process (the process has been running
overnight,
> longer than 8 hours) the size of the file is apparently too small.
>
> I tried the appeon on another pb app, this one is smaller, 26 MB size. It
> finished in 5 hours, more or less, not exact time because I turn it on and
left
> to do something else. When I check that [app_name].js file, it is 10.6MB
size.
> It will not be useful either intranet or internet due to the sheer size.
>
>
>
> >
> >5) How large is the virtual memory in your machine? The size should be
> >between 2~4 times of the physical memory.
>
> I set it to 1.5GB in the system setting of win2000 PC
>
>
> >
> >6) What is the size of the cutdown application? Can you send the
application
> >and database file to Appeon?
> >
>
> They are too big, I have to admit. I do have smaller applications. Those
are
> for small potatoes. They won't be able to afford your appeon. That is
why I
> spent most of my time in trying bigger applications (25MB to 50MB---your
limit
> is 50MB in the manual). The big guys will pay but only if it can produce
> benefit for them.
>
>
> >If possible, please also send us the error screenshot.
> >
>
>
> The screen shows a progress bar saying generate index index.html
> the blue portion is covering all the length of the bar, with text saying
100%
> completion. The finish button and the finish and run button are both
disabled.
> Cancel button is enabled. I cancelled the process, then ctrl-alt-del to
go to
> task list, terminate the pbparser and adt.exe.
>
>
>
> >Thanks,
> >Julie Jiang
> >Appeon Corporation
> >
> >"Anonymous" <Anonymous@frustrated_about_appeon.net> wrote in message
> >news:3ffee1aa$1@forums-2-dub...
> >> I cut down the size of PBL files. The deployment using appeon 2.7 is a
> >total
> >> failure: it gets stuck at the end of the second step for more than 8
> >hours,
> >> after the log info reaches this line----"Generating index index.html".
> >This
> >> symptom is repeatable.
> >>
> >> BTW, the full compile of the app in PB8.04 environment is quick.
> >>
> >> On 8 Jan 2004 13:16:08 -0800,
> >> in sybase.public.appeon
> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >> >Appeon Developer PC Hardware requirements are the following:
> >> >
> >> >· A Pentium-class processor running at 1.8 GHz or faster
> >> >· At least 512 MB RAM (1 GB RAM recommended)
> >> >· 250MB available hard drive space (for Appeon Developer installation
> >only).
> >> >Each PowerBuilder application conversion project will require
additional
> >> >hard drive space based on the size of the PowerBuilder application.
> >> >
> >> >Appeon 2.7 only supports applications with PBLs total up to 50 MB.
There
> >is
> >> >a whitepaper available to help break up applications into apps
totalling
> >> >less than 50 MB.
> >> >
> >> >Rex
> >> >
> >> >
> >> >"Anonymous" <Anonymous@Anywhere.net> wrote in message
> >> >news:3ffd942c$1@forums-2-dub...
> >> >> After completed the deployment of a one-screen hello world
application,
> >I
> >> >> started the "auto-pilot" mode deployment of a considerably big
> >> >application--more
> >> >> than 100 PBLs totaling more than 100MB. Started since 11PM last
night.
> >> >It
> >> >> still hasn't finished yet (step one finished in 105 minutes, step 2
in
> >> >progress
> >> >> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did
not
> >do
> >> >any
> >> >> analysis. The application was migrated from PB7 to PB8 yesterday
> >> >afternoon.
> >> >> Passed compiled (full regenerate) in PB8 first, then configured the
> >Appeon
> >> >> deployment. The configuration does not allow more than one
application
> >> >> object--the current application is the only one allowed to exist in
all
> >> >PBLs. I
> >> >> simply moved the other application objects out to a backup PBL file.
> >> >>
> >> >> I will check the deployment again tonight to see if the process
really
> >> >completed
> >> >> or crashed or some other result. This is a "stress test" for
> >deployment.
> >> >>
> >> >>
> >> >> On 5 Jan 2004 16:36:30 -0800,
> >> >> in sybase.public.appeon
> >> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >> >> >Hi Matt,
> >> >> >
> >> >> >What Appeon version are you using because Appeon 2.7 is usually
5-15
> >> >times
> >> >> >faster for the Feature Analysis, first-time Full Application
> >Deployment,
> >> >and
> >> >> >the subsequent Incremental Deployment is faster and more stable as
> >well?
> >> >> >
> >> >> >Here are a few examples based on the following configuration:
> >> >> >
> >> >> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements
for
> >> >Appeon
> >> >> >Developer is 1.8 GHz)
> >> >> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4
> >Build
> >> >> >10501, Appeon 2.7
> >> >> >
> >> >> >Size of PBLs in MB Feature Analysis (Min) Full Application
> >> >> >Deployment (Min)
> >> >> >14.5 5
> >> >> >55
> >> >> >20 9
> >> >> >61
> >> >> >7.65 4
> >> >> >24
> >> >> >11.7 8
> >> >> >28
> >> >> >11.9 2
> >> >> >16
> >> >> >10.6 8
> >> >> >28
> >> >> >
> >> >> >
> >> >> >These are more details from the Appeon 2.7 Developer User Guide:
> >> >> >
> >> >> >"8.2 Deployment performance
> >> >> >
> >> >> >Web deployment is a process that can be very CPU and memory
intensive,
> >so
> >> >we
> >> >> >recommend you use the most powerful development computer possible
for
> >> >Appeon
> >> >> >Developer.
> >> >> >
> >> >> >· Generally, a faster CPU will speed up the entire Web deployment
> >> >process.
> >> >> >· Large memory is useful to ensure that the memory will not be
> >exhausted
> >> >> >when analyzing a large or complex application.
> >> >> >· For more information regarding system requirements for the
> >development
> >> >> >computer, refer to the system requirements outlined in the Appeon
> >> >> >Installation Guide.
> >> >> >Be sure to close out any unnecessary running programs and Windows
> >> >services
> >> >> >in order to have the most memory available for the deployment
process.
> >> >> >
> >> >> >8.3 Deployment duration
> >> >> >
> >> >> >Although the deployment process is fully automated, it is not
> >> >instantaneous.
> >> >> >The deployment process can be very CPU and memory intensive, and
take
> >a
> >> >> >significant amount of time depending on the size and complexity of
the
> >> >> >application and the processing power of the machine running the
> >> >deployment.
> >> >> >The following is an example of how long it takes to deploy an
> >> >application.
> >> >> >
> >> >> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
> >> >converting
> >> >> >an application with 3.29 MB in PBLs (not including images); Task 1
> >takes
> >> >two
> >> >> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only
15
> >> >> >seconds (for a local deployment)...
> >> >> >
> >> >> >Since the initial deployment (full deployment) can be
time-consuming,
> >> >Appeon
> >> >> >has built-in a feature into the Application Deployment Wizard to
> >> >> >dramatically reduce the deployment time for subsequent deployments.
> >This
> >> >> >feature dramatically reduces the deployment time by performing only
a
> >> >> >partial rebuild and partial deployment of the application, called
> >> >> >Incremental Deployment. An Incremental Deployment is used when you
> >make
> >> >> >changes to an application after it has been initially deployed, and
> >> >> >re-deploy the application in order to see the changes take effect.
> >> >> >
> >> >> >Specifically, an Incremental Deployment will greatly reduce the
time
> >for
> >> >> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
> >> >> >Incremental Deployment can save up to 80% of the total time. For a
> >> >remote
> >> >> >deployment, such as an FTP deployment, Task 3 will usually take
longer
> >> >than
> >> >> >a local deployment, since latency and bandwidth is increased.
> >> >> >
> >> >> >A third deployment option, Deploy Already Generated Application,
can
> >be
> >> >used
> >> >> >to deploy a previously deployed application to a different server,
or
> >> >> >refresh the Web files on a server where the application has already
> >been
> >> >> >deployed. This option eliminates the two most time-consuming
steps -
> >it
> >> >> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web
Files
> >> >> >Generation) and only performs Task 3 (Web Deployment)."
> >> >> >
> >> >> >Regards, Rex
> >> >> >
> >> >> >
> >> >> >"Matt Bell" <matt@argosys.com> wrote in message
> >> >> >news:3ff995f8$1@forums-1-dub...
> >> >> >> Hi All,
> >> >> >> We've been testing Appeon here at the office, and the biggest
thing
> >I'm
> >> >> >> noticing is it takes several days for appeon to analyze our
> >application
> >> >> >for
> >> >> >> deployment, infact I've yet to actually get it to complete and
give
> >me
> >> >an
> >> >> >> analysis report on unsupported features. Is this a configuration
> >> >issue,
> >> >> >or
> >> >> >> does it just take that long?
> >> >> >>
> >> >> >> Matt Bell
> >> >> >> Argo Systems
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >


Lilian Pigallio Posted on 2004-01-13 14:08:38.0Z
From: "Lilian Pigallio" <lpigallio@nospam.com>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub> <3ffee1aa$1@forums-2-dub> <4002775c@forums-2-dub> <4002ece4$1@forums-2-dub> <4003c3e2@forums-1-dub>
Subject: Re: Build Times
Lines: 419
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: nat-lan.dev.amadeus.net
X-Original-NNTP-Posting-Host: nat-lan.dev.amadeus.net
Message-ID: <4003fbe6@forums-1-dub>
Date: 13 Jan 2004 06:08:38 -0800
X-Trace: forums-1-dub 1074002918 62.210.124.226 (13 Jan 2004 06:08:38 -0800)
X-Original-Trace: 13 Jan 2004 06:08:38 -0800, nat-lan.dev.amadeus.net
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:40
Article PK: 12352

Great (and quick) support :))

"Julie Jiang" <julie.jiang@appeon.net> wrote in message
news:4003c3e2@forums-1-dub...
> Thank you for your prompt feedback. Based on your feedback, Appeon
engineer
> judges that the Web files have already been generated for the application.
>
> Check in the folder %Appeon%\Developer\Appname\release/debug folder for
the
> Performance_Report.xml file: if the file exists but is empty, the most
> possible reason for the problem is that some syntax in the application
goes
> abnormal after being migrated from PB 7 to PB 8. The parser cannot
> understand the syntax, so it cannot continue its task smoothly.
>
> Nevertheless, since the Web application files are already generated, you
can
> go to Appeon Developer Wizard and directly deploy the application: Select
> the deployment mode as "Deploy already generated application", and Appeon
> Developer will go to the step 3 and deploy the generated files to Appeon
> Server. Please check whether the Web application can run well.
>
> Still, you will be more than welcomed to send the problematic PowerBuilder
> application and database to Appeon for deep debugging.
>
> Thanks,
> Julie Jiang
> Appeon Corporation
>
>
>
> "Anonymous" <Anonymous@Anywhere.net> wrote in message
> news:4002ece4$1@forums-2-dub...
> > The reply is inserted to the orginal text body below, thanks.
> >
> >
> > On 12 Jan 2004 02:21:45 -0800,
> > in sybase.public.appeon
> > Julie Jiang <julie.jiang@appeon.net> wrote:
> > >During the "Generating index index.html" phase, Appeon Developer
combines
> > >the generated Web files and creates the Unsupported Features Report for
> the
> > >application. There are several factors that decide how long this step
> will
> > >take: number of windows, global structures, global functions, and
> quantity
> > >of unsupported features in the application. In general, it should take
> less
> > >than 15 minutes in this step for a 100M application. Obviously, the
> > >described case is abnormal and must have special cause in it.
> > >
> > >However, Appeon engineers cannot tell what is the cause based on the
> > >information provided. Can you please reply to the following questions?
> It
> > >will be very helpful for the engineers to further investigate:
> > >1) There is a PBParser icon on windows tray if the deployment wizard is
> > >working. Please check whether the arrows in the icon turn red
steadily.
> > >(If Yes, the PBParser is still running).
> > >
> >
> >
> > Yes. The small icon (double arrow shaped) keeps blinking.
> >
> >
> > >2) Whether a UFA_Report.xml is already created in the Web application
> folder
> > >(in the %Appeon%\Developer\appname\release/debug)? (This will be
helpful
> for
> > >us to judge when the application stops working)
> > >
> >
> >
> > Yes it is.
> >
> >
> >
> > >3) Whether a GWF_Report.xml is already created in the Web application
> folder
> > >(in the %Appeon%\Developer\appname\release/debug)? (This will be
helpful
> for
> > >us to judge when the application stops working)
> > >
> >
> > Probably it is, I will check it again when I go back home. All work
> currently
> > is done at home as self-study and evalueation (aka not making money
until
> your
> > tool works for more complex code)
> >
> > >4) Whether an application.js file is already created (in the
> > >%Appeon%\Developer\appname\release/debug\wcode) ? Is the file empty or
> with
> > >content?
> >
> > Yes. BUT only when I hit end process (the process has been running
> overnight,
> > longer than 8 hours) the size of the file is apparently too small.
> >
> > I tried the appeon on another pb app, this one is smaller, 26 MB size.
It
> > finished in 5 hours, more or less, not exact time because I turn it on
and
> left
> > to do something else. When I check that [app_name].js file, it is
10.6MB
> size.
> > It will not be useful either intranet or internet due to the sheer size.
> >
> >
> >
> > >
> > >5) How large is the virtual memory in your machine? The size should be
> > >between 2~4 times of the physical memory.
> >
> > I set it to 1.5GB in the system setting of win2000 PC
> >
> >
> > >
> > >6) What is the size of the cutdown application? Can you send the
> application
> > >and database file to Appeon?
> > >
> >
> > They are too big, I have to admit. I do have smaller applications.
Those
> are
> > for small potatoes. They won't be able to afford your appeon. That is
> why I
> > spent most of my time in trying bigger applications (25MB to 50MB---your
> limit
> > is 50MB in the manual). The big guys will pay but only if it can
produce
> > benefit for them.
> >
> >
> > >If possible, please also send us the error screenshot.
> > >
> >
> >
> > The screen shows a progress bar saying generate index index.html
> > the blue portion is covering all the length of the bar, with text saying
> 100%
> > completion. The finish button and the finish and run button are both
> disabled.
> > Cancel button is enabled. I cancelled the process, then ctrl-alt-del to
> go to
> > task list, terminate the pbparser and adt.exe.
> >
> >
> >
> > >Thanks,
> > >Julie Jiang
> > >Appeon Corporation
> > >
> > >"Anonymous" <Anonymous@frustrated_about_appeon.net> wrote in message
> > >news:3ffee1aa$1@forums-2-dub...
> > >> I cut down the size of PBL files. The deployment using appeon 2.7 is
a
> > >total
> > >> failure: it gets stuck at the end of the second step for more than 8
> > >hours,
> > >> after the log info reaches this line----"Generating index
index.html".
> > >This
> > >> symptom is repeatable.
> > >>
> > >> BTW, the full compile of the app in PB8.04 environment is quick.
> > >>
> > >> On 8 Jan 2004 13:16:08 -0800,
> > >> in sybase.public.appeon
> > >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> > >> >Appeon Developer PC Hardware requirements are the following:
> > >> >
> > >> >· A Pentium-class processor running at 1.8 GHz or faster
> > >> >· At least 512 MB RAM (1 GB RAM recommended)
> > >> >· 250MB available hard drive space (for Appeon Developer
installation
> > >only).
> > >> >Each PowerBuilder application conversion project will require
> additional
> > >> >hard drive space based on the size of the PowerBuilder application.
> > >> >
> > >> >Appeon 2.7 only supports applications with PBLs total up to 50 MB.
> There
> > >is
> > >> >a whitepaper available to help break up applications into apps
> totalling
> > >> >less than 50 MB.
> > >> >
> > >> >Rex
> > >> >
> > >> >
> > >> >"Anonymous" <Anonymous@Anywhere.net> wrote in message
> > >> >news:3ffd942c$1@forums-2-dub...
> > >> >> After completed the deployment of a one-screen hello world
> application,
> > >I
> > >> >> started the "auto-pilot" mode deployment of a considerably big
> > >> >application--more
> > >> >> than 100 PBLs totaling more than 100MB. Started since 11PM last
> night.
> > >> >It
> > >> >> still hasn't finished yet (step one finished in 105 minutes, step
2
> in
> > >> >progress
> > >> >> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did
> not
> > >do
> > >> >any
> > >> >> analysis. The application was migrated from PB7 to PB8 yesterday
> > >> >afternoon.
> > >> >> Passed compiled (full regenerate) in PB8 first, then configured
the
> > >Appeon
> > >> >> deployment. The configuration does not allow more than one
> application
> > >> >> object--the current application is the only one allowed to exist
in
> all
> > >> >PBLs. I
> > >> >> simply moved the other application objects out to a backup PBL
file.
> > >> >>
> > >> >> I will check the deployment again tonight to see if the process
> really
> > >> >completed
> > >> >> or crashed or some other result. This is a "stress test" for
> > >deployment.
> > >> >>
> > >> >>
> > >> >> On 5 Jan 2004 16:36:30 -0800,
> > >> >> in sybase.public.appeon
> > >> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> > >> >> >Hi Matt,
> > >> >> >
> > >> >> >What Appeon version are you using because Appeon 2.7 is usually
> 5-15
> > >> >times
> > >> >> >faster for the Feature Analysis, first-time Full Application
> > >Deployment,
> > >> >and
> > >> >> >the subsequent Incremental Deployment is faster and more stable
as
> > >well?
> > >> >> >
> > >> >> >Here are a few examples based on the following configuration:
> > >> >> >
> > >> >> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements
> for
> > >> >Appeon
> > >> >> >Developer is 1.8 GHz)
> > >> >> >· Software: Windows 2000 Professional (English), PowerBuilder
8.0.4
> > >Build
> > >> >> >10501, Appeon 2.7
> > >> >> >
> > >> >> >Size of PBLs in MB Feature Analysis (Min) Full
Application
> > >> >> >Deployment (Min)
> > >> >> >14.5 5
> > >> >> >55
> > >> >> >20 9
> > >> >> >61
> > >> >> >7.65 4
> > >> >> >24
> > >> >> >11.7 8
> > >> >> >28
> > >> >> >11.9 2
> > >> >> >16
> > >> >> >10.6 8
> > >> >> >28
> > >> >> >
> > >> >> >
> > >> >> >These are more details from the Appeon 2.7 Developer User Guide:
> > >> >> >
> > >> >> >"8.2 Deployment performance
> > >> >> >
> > >> >> >Web deployment is a process that can be very CPU and memory
> intensive,
> > >so
> > >> >we
> > >> >> >recommend you use the most powerful development computer possible
> for
> > >> >Appeon
> > >> >> >Developer.
> > >> >> >
> > >> >> >· Generally, a faster CPU will speed up the entire Web deployment
> > >> >process.
> > >> >> >· Large memory is useful to ensure that the memory will not be
> > >exhausted
> > >> >> >when analyzing a large or complex application.
> > >> >> >· For more information regarding system requirements for the
> > >development
> > >> >> >computer, refer to the system requirements outlined in the Appeon
> > >> >> >Installation Guide.
> > >> >> >Be sure to close out any unnecessary running programs and Windows
> > >> >services
> > >> >> >in order to have the most memory available for the deployment
> process.
> > >> >> >
> > >> >> >8.3 Deployment duration
> > >> >> >
> > >> >> >Although the deployment process is fully automated, it is not
> > >> >instantaneous.
> > >> >> >The deployment process can be very CPU and memory intensive, and
> take
> > >a
> > >> >> >significant amount of time depending on the size and complexity
of
> the
> > >> >> >application and the processing power of the machine running the
> > >> >deployment.
> > >> >> >The following is an example of how long it takes to deploy an
> > >> >application.
> > >> >> >
> > >> >> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
> > >> >converting
> > >> >> >an application with 3.29 MB in PBLs (not including images); Task
1
> > >takes
> > >> >two
> > >> >> >minutes, Task 2 takes one and a half minutes, and Task 3 takes
only
> 15
> > >> >> >seconds (for a local deployment)...
> > >> >> >
> > >> >> >Since the initial deployment (full deployment) can be
> time-consuming,
> > >> >Appeon
> > >> >> >has built-in a feature into the Application Deployment Wizard to
> > >> >> >dramatically reduce the deployment time for subsequent
deployments.
> > >This
> > >> >> >feature dramatically reduces the deployment time by performing
only
> a
> > >> >> >partial rebuild and partial deployment of the application, called
> > >> >> >Incremental Deployment. An Incremental Deployment is used when
you
> > >make
> > >> >> >changes to an application after it has been initially deployed,
and
> > >> >> >re-deploy the application in order to see the changes take
effect.
> > >> >> >
> > >> >> >Specifically, an Incremental Deployment will greatly reduce the
> time
> > >for
> > >> >> >Task 1, Task 2, and Task 3. When compared to a Full Deployment,
an
> > >> >> >Incremental Deployment can save up to 80% of the total time. For
a
> > >> >remote
> > >> >> >deployment, such as an FTP deployment, Task 3 will usually take
> longer
> > >> >than
> > >> >> >a local deployment, since latency and bandwidth is increased.
> > >> >> >
> > >> >> >A third deployment option, Deploy Already Generated Application,
> can
> > >be
> > >> >used
> > >> >> >to deploy a previously deployed application to a different
server,
> or
> > >> >> >refresh the Web files on a server where the application has
already
> > >been
> > >> >> >deployed. This option eliminates the two most time-consuming
> steps -
> > >it
> > >> >> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web
> Files
> > >> >> >Generation) and only performs Task 3 (Web Deployment)."
> > >> >> >
> > >> >> >Regards, Rex
> > >> >> >
> > >> >> >
> > >> >> >"Matt Bell" <matt@argosys.com> wrote in message
> > >> >> >news:3ff995f8$1@forums-1-dub...
> > >> >> >> Hi All,
> > >> >> >> We've been testing Appeon here at the office, and the biggest
> thing
> > >I'm
> > >> >> >> noticing is it takes several days for appeon to analyze our
> > >application
> > >> >> >for
> > >> >> >> deployment, infact I've yet to actually get it to complete and
> give
> > >me
> > >> >an
> > >> >> >> analysis report on unsupported features. Is this a
configuration
> > >> >issue,
> > >> >> >or
> > >> >> >> does it just take that long?
> > >> >> >>
> > >> >> >> Matt Bell
> > >> >> >> Argo Systems
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >
> > >> >
> > >
> > >
>
>


Armeen Mazda Posted on 2004-01-15 02:05:01.0Z
From: "Armeen Mazda" <armeen.mazda@appeon.net>
Newsgroups: sybase.public.appeon
References: <3ff995f8$1@forums-1-dub> <3ffa030e@forums-1-dub> <3ffd942c$1@forums-2-dub> <3ffdc898$1@forums-1-dub> <3ffee1aa$1@forums-2-dub> <4002775c@forums-2-dub> <4002ece4$1@forums-2-dub>
Subject: Re: Build Times
Lines: 374
Organization: Appeon Corporation
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: 61.144.207.54
X-Original-NNTP-Posting-Host: 61.144.207.54
Message-ID: <4005f54d@forums-1-dub>
Date: 14 Jan 2004 18:05:01 -0800
X-Trace: forums-1-dub 1074132301 61.144.207.54 (14 Jan 2004 18:05:01 -0800)
X-Original-Trace: 14 Jan 2004 18:05:01 -0800, 61.144.207.54
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:41
Article PK: 20549

Matt,

We are working on introducing a lower-priced version of Appeon for very
small applications with a small number of users (i.e. the small potatoes).
As far as for your clients who have greater needs, I should point out that
you can serve accounts with applications larger than 50MB. For example, if
the customer has a 100MB application, you can break it up into 2-3 modules
where each module is 50MB or less.

Based on the information Juile has provided, it seems to me that there is
some legacy PB7 code or some PB feature in your application that is tripping
up the Appeon Developer. Otherwise, your application should take an hour or
so for the initial Full Deployment. Subsequent deployments using the
Incremental Deployment option should only take a few minutes. We will be
happy to analyze the code for you and point out the cause of the problem.
If you are unable to provide us with the problematic code or test case,
Julie's workaround will allow you to proceed.

Regards,
Armeen Mazda
Appeon Corporation

"Anonymous" <Anonymous@Anywhere.net> wrote in message
news:4002ece4$1@forums-2-dub...
> The reply is inserted to the orginal text body below, thanks.
>
>
> On 12 Jan 2004 02:21:45 -0800,
> in sybase.public.appeon
> Julie Jiang <julie.jiang@appeon.net> wrote:
> >During the "Generating index index.html" phase, Appeon Developer combines
> >the generated Web files and creates the Unsupported Features Report for
the
> >application. There are several factors that decide how long this step
will
> >take: number of windows, global structures, global functions, and
quantity
> >of unsupported features in the application. In general, it should take
less
> >than 15 minutes in this step for a 100M application. Obviously, the
> >described case is abnormal and must have special cause in it.
> >
> >However, Appeon engineers cannot tell what is the cause based on the
> >information provided. Can you please reply to the following questions?
It
> >will be very helpful for the engineers to further investigate:
> >1) There is a PBParser icon on windows tray if the deployment wizard is
> >working. Please check whether the arrows in the icon turn red steadily.
> >(If Yes, the PBParser is still running).
> >
>
>
> Yes. The small icon (double arrow shaped) keeps blinking.
>
>
> >2) Whether a UFA_Report.xml is already created in the Web application
folder
> >(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful
for
> >us to judge when the application stops working)
> >
>
>
> Yes it is.
>
>
>
> >3) Whether a GWF_Report.xml is already created in the Web application
folder
> >(in the %Appeon%\Developer\appname\release/debug)? (This will be helpful
for
> >us to judge when the application stops working)
> >
>
> Probably it is, I will check it again when I go back home. All work
currently
> is done at home as self-study and evalueation (aka not making money until
your
> tool works for more complex code)
>
> >4) Whether an application.js file is already created (in the
> >%Appeon%\Developer\appname\release/debug\wcode) ? Is the file empty or
with
> >content?
>
> Yes. BUT only when I hit end process (the process has been running
overnight,
> longer than 8 hours) the size of the file is apparently too small.
>
> I tried the appeon on another pb app, this one is smaller, 26 MB size. It
> finished in 5 hours, more or less, not exact time because I turn it on and
left
> to do something else. When I check that [app_name].js file, it is 10.6MB
size.
> It will not be useful either intranet or internet due to the sheer size.
>
>
>
> >
> >5) How large is the virtual memory in your machine? The size should be
> >between 2~4 times of the physical memory.
>
> I set it to 1.5GB in the system setting of win2000 PC
>
>
> >
> >6) What is the size of the cutdown application? Can you send the
application
> >and database file to Appeon?
> >
>
> They are too big, I have to admit. I do have smaller applications. Those
are
> for small potatoes. They won't be able to afford your appeon. That is
why I
> spent most of my time in trying bigger applications (25MB to 50MB---your
limit
> is 50MB in the manual). The big guys will pay but only if it can produce
> benefit for them.
>
>
> >If possible, please also send us the error screenshot.
> >
>
>
> The screen shows a progress bar saying generate index index.html
> the blue portion is covering all the length of the bar, with text saying
100%
> completion. The finish button and the finish and run button are both
disabled.
> Cancel button is enabled. I cancelled the process, then ctrl-alt-del to
go to
> task list, terminate the pbparser and adt.exe.
>
>
>
> >Thanks,
> >Julie Jiang
> >Appeon Corporation
> >
> >"Anonymous" <Anonymous@frustrated_about_appeon.net> wrote in message
> >news:3ffee1aa$1@forums-2-dub...
> >> I cut down the size of PBL files. The deployment using appeon 2.7 is a
> >total
> >> failure: it gets stuck at the end of the second step for more than 8
> >hours,
> >> after the log info reaches this line----"Generating index index.html".
> >This
> >> symptom is repeatable.
> >>
> >> BTW, the full compile of the app in PB8.04 environment is quick.
> >>
> >> On 8 Jan 2004 13:16:08 -0800,
> >> in sybase.public.appeon
> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >> >Appeon Developer PC Hardware requirements are the following:
> >> >
> >> >· A Pentium-class processor running at 1.8 GHz or faster
> >> >· At least 512 MB RAM (1 GB RAM recommended)
> >> >· 250MB available hard drive space (for Appeon Developer installation
> >only).
> >> >Each PowerBuilder application conversion project will require
additional
> >> >hard drive space based on the size of the PowerBuilder application.
> >> >
> >> >Appeon 2.7 only supports applications with PBLs total up to 50 MB.
There
> >is
> >> >a whitepaper available to help break up applications into apps
totalling
> >> >less than 50 MB.
> >> >
> >> >Rex
> >> >
> >> >
> >> >"Anonymous" <Anonymous@Anywhere.net> wrote in message
> >> >news:3ffd942c$1@forums-2-dub...
> >> >> After completed the deployment of a one-screen hello world
application,
> >I
> >> >> started the "auto-pilot" mode deployment of a considerably big
> >> >application--more
> >> >> than 100 PBLs totaling more than 100MB. Started since 11PM last
night.
> >> >It
> >> >> still hasn't finished yet (step one finished in 105 minutes, step 2
in
> >> >progress
> >> >> as of now). PC is an old server 550Hz one CPU, 512 MB RAM. I did
not
> >do
> >> >any
> >> >> analysis. The application was migrated from PB7 to PB8 yesterday
> >> >afternoon.
> >> >> Passed compiled (full regenerate) in PB8 first, then configured the
> >Appeon
> >> >> deployment. The configuration does not allow more than one
application
> >> >> object--the current application is the only one allowed to exist in
all
> >> >PBLs. I
> >> >> simply moved the other application objects out to a backup PBL file.
> >> >>
> >> >> I will check the deployment again tonight to see if the process
really
> >> >completed
> >> >> or crashed or some other result. This is a "stress test" for
> >deployment.
> >> >>
> >> >>
> >> >> On 5 Jan 2004 16:36:30 -0800,
> >> >> in sybase.public.appeon
> >> >> Rex Geissler <Rex.Geissler@sybase.com> wrote:
> >> >> >Hi Matt,
> >> >> >
> >> >> >What Appeon version are you using because Appeon 2.7 is usually
5-15
> >> >times
> >> >> >faster for the Feature Analysis, first-time Full Application
> >Deployment,
> >> >and
> >> >> >the subsequent Incremental Deployment is faster and more stable as
> >well?
> >> >> >
> >> >> >Here are a few examples based on the following configuration:
> >> >> >
> >> >> >· Hardware: P4, 1.3 GHz, 512 MB RAM (but the System Requirements
for
> >> >Appeon
> >> >> >Developer is 1.8 GHz)
> >> >> >· Software: Windows 2000 Professional (English), PowerBuilder 8.0.4
> >Build
> >> >> >10501, Appeon 2.7
> >> >> >
> >> >> >Size of PBLs in MB Feature Analysis (Min) Full Application
> >> >> >Deployment (Min)
> >> >> >14.5 5
> >> >> >55
> >> >> >20 9
> >> >> >61
> >> >> >7.65 4
> >> >> >24
> >> >> >11.7 8
> >> >> >28
> >> >> >11.9 2
> >> >> >16
> >> >> >10.6 8
> >> >> >28
> >> >> >
> >> >> >
> >> >> >These are more details from the Appeon 2.7 Developer User Guide:
> >> >> >
> >> >> >"8.2 Deployment performance
> >> >> >
> >> >> >Web deployment is a process that can be very CPU and memory
intensive,
> >so
> >> >we
> >> >> >recommend you use the most powerful development computer possible
for
> >> >Appeon
> >> >> >Developer.
> >> >> >
> >> >> >· Generally, a faster CPU will speed up the entire Web deployment
> >> >process.
> >> >> >· Large memory is useful to ensure that the memory will not be
> >exhausted
> >> >> >when analyzing a large or complex application.
> >> >> >· For more information regarding system requirements for the
> >development
> >> >> >computer, refer to the system requirements outlined in the Appeon
> >> >> >Installation Guide.
> >> >> >Be sure to close out any unnecessary running programs and Windows
> >> >services
> >> >> >in order to have the most memory available for the deployment
process.
> >> >> >
> >> >> >8.3 Deployment duration
> >> >> >
> >> >> >Although the deployment process is fully automated, it is not
> >> >instantaneous.
> >> >> >The deployment process can be very CPU and memory intensive, and
take
> >a
> >> >> >significant amount of time depending on the size and complexity of
the
> >> >> >application and the processing power of the machine running the
> >> >deployment.
> >> >> >The following is an example of how long it takes to deploy an
> >> >application.
> >> >> >
> >> >> >For a Pentium-class processor running at 1.8 GHZ with 256 MB RAM
> >> >converting
> >> >> >an application with 3.29 MB in PBLs (not including images); Task 1
> >takes
> >> >two
> >> >> >minutes, Task 2 takes one and a half minutes, and Task 3 takes only
15
> >> >> >seconds (for a local deployment)...
> >> >> >
> >> >> >Since the initial deployment (full deployment) can be
time-consuming,
> >> >Appeon
> >> >> >has built-in a feature into the Application Deployment Wizard to
> >> >> >dramatically reduce the deployment time for subsequent deployments.
> >This
> >> >> >feature dramatically reduces the deployment time by performing only
a
> >> >> >partial rebuild and partial deployment of the application, called
> >> >> >Incremental Deployment. An Incremental Deployment is used when you
> >make
> >> >> >changes to an application after it has been initially deployed, and
> >> >> >re-deploy the application in order to see the changes take effect.
> >> >> >
> >> >> >Specifically, an Incremental Deployment will greatly reduce the
time
> >for
> >> >> >Task 1, Task 2, and Task 3. When compared to a Full Deployment, an
> >> >> >Incremental Deployment can save up to 80% of the total time. For a
> >> >remote
> >> >> >deployment, such as an FTP deployment, Task 3 will usually take
longer
> >> >than
> >> >> >a local deployment, since latency and bandwidth is increased.
> >> >> >
> >> >> >A third deployment option, Deploy Already Generated Application,
can
> >be
> >> >used
> >> >> >to deploy a previously deployed application to a different server,
or
> >> >> >refresh the Web files on a server where the application has already
> >been
> >> >> >deployed. This option eliminates the two most time-consuming
steps -
> >it
> >> >> >bypasses Task 1 (Application Source Code Export) and Task 2 (Web
Files
> >> >> >Generation) and only performs Task 3 (Web Deployment)."
> >> >> >
> >> >> >Regards, Rex
> >> >> >
> >> >> >
> >> >> >"Matt Bell" <matt@argosys.com> wrote in message
> >> >> >news:3ff995f8$1@forums-1-dub...
> >> >> >> Hi All,
> >> >> >> We've been testing Appeon here at the office, and the biggest
thing
> >I'm
> >> >> >> noticing is it takes several days for appeon to analyze our
> >application
> >> >> >for
> >> >> >> deployment, infact I've yet to actually get it to complete and
give
> >me
> >> >an
> >> >> >> analysis report on unsupported features. Is this a configuration
> >> >issue,
> >> >> >or
> >> >> >> does it just take that long?
> >> >> >>
> >> >> >> Matt Bell
> >> >> >> Argo Systems
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >