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.

modularization

5 posts in Appeon (partner product) Last posting was on 2005-03-31 18:54:47.0Z
Terence Posted on 2005-03-15 03:56:25.0Z
From: "Terence" <tamagcaoili@yahoo.com>
Newsgroups: sybase.public.appeon
Organization: 222.126.62.229
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: modularization
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: web110.discountasp.net
X-Original-NNTP-Posting-Host: web110.discountasp.net
Message-ID: <42365ce9@forums-1-dub>
Date: 14 Mar 2005 19:56:25 -0800
X-Trace: forums-1-dub 1110858985 64.79.161.40 (14 Mar 2005 19:56:25 -0800)
X-Original-Trace: 14 Mar 2005 19:56:25 -0800, web110.discountasp.net
Lines: 59
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:717
Article PK: 12671

Good day to all.

We are using appeon to move our client-server application to the web/n-tier
environment. We are in the initial stage of the project and need advice on
modularization.

The problem is that our application is so intertwined that it is difficult to
modularize. Removing the coupling of the modules is not possible as it is
essential to the functionality of the software. Another thing is that our
application size is 450MB.

Can we deploy modules separately then have them call each other?

We decided to break the application into several subsystems, but first we
identified the base object libraries. The size was:

Base Objects 37.2M

Then we create subsystem deployment targets wherein we include in each the "Base
Object libraries".
SIZE DEPLOYMENT SIZE
Subsystem 1 58.9M + 37.2M = 96.1M
Subsystem 2 57.5M + 37.2M = 94.7M
Subsystem 3 45.8M + 37.2M = 83.0M
Subsystem 4 61.0M + 37.2M = 98.2M
Subsystem 5 37.7M + 37.2M = 74.9M
Subsystem 6 55.8M + 37.2M = 93.0M

Notice that we were able to break each deployment targets to less than 100M.

Now for each target we will add a library called blank. Upon building each, it
will error objects that are not found because it is located in another
subsystem. For objects that are not found, we will create a blank object with
the same name in the blank library.

After these, we expect that all submodules are ready for APPEON migration
analysis. We will assign each subsystem to 1 person.

The first to be analyse is the first subsystem.

Problems encountered with the first subsystem that can be fixed by simple search
and replace will be immeadiately applied also to the other modules.

Problems encountered that will need coding modification will be done first in
the first subsystem. The solution will be documented in a knowledge repository
and then assign each team member to do the necessary similar modification to
their modules.

Upon successful migration of the first subsystem, the second subsystem will be
analyzed, and so on, and so forth.

The 6 subsystem would be deployed into 6 EAServer directories. Upon migrating
all subsystems, all non blank objects from subsystems 2 to 6 will be copied to
the subsytem 1 EAServer directory.

Is this feasible?

---== Posted via the PFCGuide Web Newsreader ==---
http://www.pfcguide.com/_newsgroups/group_list.asp


Julie Jiang Posted on 2005-03-15 10:48:16.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <42365ce9@forums-1-dub>
Subject: Re: modularization
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: 210.21.221.178
X-Original-NNTP-Posting-Host: 210.21.221.178
Message-ID: <4236bd70@forums-1-dub>
Date: 15 Mar 2005 02:48:16 -0800
X-Trace: forums-1-dub 1110883696 210.21.221.178 (15 Mar 2005 02:48:16 -0800)
X-Original-Trace: 15 Mar 2005 02:48:16 -0800, 210.21.221.178
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:719
Article PK: 12672

I cannot quite understand your last sentence, "upon migrating all
subsystems, all non blank objects from subsystems 2 to 6 will be copied to
the subsytem 1 EAServer directory", I am not sure what you will achieve out
of it. I think more feasible way is, after all the subsystems are migrated
successfully, you add several hyperlinks in the subsystem 1 for accessing to
subsystems 2 to 6.

I will talk tomorrow with the engineers and study more about your plan.

Regards,
Julie

"Terence" <tamagcaoili@yahoo.com> wrote in message
news:42365ce9@forums-1-dub...
> Good day to all.
>
> We are using appeon to move our client-server application to the
web/n-tier
> environment. We are in the initial stage of the project and need advice on
> modularization.
>
> The problem is that our application is so intertwined that it is difficult
to
> modularize. Removing the coupling of the modules is not possible as it is
> essential to the functionality of the software. Another thing is that our
> application size is 450MB.
>
> Can we deploy modules separately then have them call each other?
>
> We decided to break the application into several subsystems, but first we
> identified the base object libraries. The size was:
>
> Base Objects 37.2M
>
> Then we create subsystem deployment targets wherein we include in each the
"Base
> Object libraries".
> SIZE DEPLOYMENT SIZE
> Subsystem 1 58.9M + 37.2M = 96.1M
> Subsystem 2 57.5M + 37.2M = 94.7M
> Subsystem 3 45.8M + 37.2M = 83.0M
> Subsystem 4 61.0M + 37.2M = 98.2M
> Subsystem 5 37.7M + 37.2M = 74.9M
> Subsystem 6 55.8M + 37.2M = 93.0M
>
> Notice that we were able to break each deployment targets to less than
100M.
>
> Now for each target we will add a library called blank. Upon building
each, it
> will error objects that are not found because it is located in another
> subsystem. For objects that are not found, we will create a blank object
with
> the same name in the blank library.
>
> After these, we expect that all submodules are ready for APPEON migration
> analysis. We will assign each subsystem to 1 person.
>
> The first to be analyse is the first subsystem.
>
> Problems encountered with the first subsystem that can be fixed by simple
search
> and replace will be immeadiately applied also to the other modules.
>
> Problems encountered that will need coding modification will be done first
in
> the first subsystem. The solution will be documented in a knowledge
repository
> and then assign each team member to do the necessary similar modification
to
> their modules.
>
> Upon successful migration of the first subsystem, the second subsystem
will be
> analyzed, and so on, and so forth.
>
> The 6 subsystem would be deployed into 6 EAServer directories. Upon
migrating
> all subsystems, all non blank objects from subsystems 2 to 6 will be
copied to
> the subsytem 1 EAServer directory.
>
> Is this feasible?
>
> ---== Posted via the PFCGuide Web Newsreader ==---
> http://www.pfcguide.com/_newsgroups/group_list.asp


Julie Jiang Posted on 2005-03-16 10:06:32.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <42365ce9@forums-1-dub> <4236bd70@forums-1-dub>
Subject: Re: modularization
Lines: 135
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: 210.21.221.178
X-Original-NNTP-Posting-Host: 210.21.221.178
Message-ID: <42380528@forums-1-dub>
Date: 16 Mar 2005 02:06:32 -0800
X-Trace: forums-1-dub 1110967592 210.21.221.178 (16 Mar 2005 02:06:32 -0800)
X-Original-Trace: 16 Mar 2005 02:06:32 -0800, 210.21.221.178
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:720
Article PK: 20873

Since the application is indeed large (450MB), we agree with you that the
application should be split into modules. But as the initial stage of the
project, we think a better approach should be the following:

1) Analyzing what are the core logics in the application that will be used
over the application, and trying to put the logics in n-Tier NVOs so that
the logics can be used by the 6 systems.

2) Dividing the application into 6 systems, and making sure the systems are
independent of each other, except that they use the common n-Tier NVOs.

Your plan is to make the systems call each other after the systems are
converted to the Web. However, Appeon-deployed applications do not offer
open interfaces to each other. So we suggest you place the common logics in
server NVOs for building up the communication between the systems.

3) Concentrating on the deployment of the systems.

Any question about this approach, please let me know.

Regards,
Julie

"Julie Jiang" <julie.jiang@appeon.net> wrote in message
news:4236bd70@forums-1-dub...
> I cannot quite understand your last sentence, "upon migrating all
> subsystems, all non blank objects from subsystems 2 to 6 will be copied to
> the subsytem 1 EAServer directory", I am not sure what you will achieve
out
> of it. I think more feasible way is, after all the subsystems are
migrated
> successfully, you add several hyperlinks in the subsystem 1 for accessing
to
> subsystems 2 to 6.
>
> I will talk tomorrow with the engineers and study more about your plan.
>
> Regards,
> Julie
>
>
> "Terence" <tamagcaoili@yahoo.com> wrote in message
> news:42365ce9@forums-1-dub...
> > Good day to all.
> >
> > We are using appeon to move our client-server application to the
> web/n-tier
> > environment. We are in the initial stage of the project and need advice
on
> > modularization.
> >
> > The problem is that our application is so intertwined that it is
difficult
> to
> > modularize. Removing the coupling of the modules is not possible as it
is
> > essential to the functionality of the software. Another thing is that
our
> > application size is 450MB.
> >
> > Can we deploy modules separately then have them call each other?
> >
> > We decided to break the application into several subsystems, but first
we
> > identified the base object libraries. The size was:
> >
> > Base Objects 37.2M
> >
> > Then we create subsystem deployment targets wherein we include in each
the
> "Base
> > Object libraries".
> > SIZE DEPLOYMENT SIZE
> > Subsystem 1 58.9M + 37.2M = 96.1M
> > Subsystem 2 57.5M + 37.2M = 94.7M
> > Subsystem 3 45.8M + 37.2M = 83.0M
> > Subsystem 4 61.0M + 37.2M = 98.2M
> > Subsystem 5 37.7M + 37.2M = 74.9M
> > Subsystem 6 55.8M + 37.2M = 93.0M
> >
> > Notice that we were able to break each deployment targets to less than
> 100M.
> >
> > Now for each target we will add a library called blank. Upon building
> each, it
> > will error objects that are not found because it is located in another
> > subsystem. For objects that are not found, we will create a blank object
> with
> > the same name in the blank library.
> >
> > After these, we expect that all submodules are ready for APPEON
migration
> > analysis. We will assign each subsystem to 1 person.
> >
> > The first to be analyse is the first subsystem.
> >
> > Problems encountered with the first subsystem that can be fixed by
simple
> search
> > and replace will be immeadiately applied also to the other modules.
> >
> > Problems encountered that will need coding modification will be done
first
> in
> > the first subsystem. The solution will be documented in a knowledge
> repository
> > and then assign each team member to do the necessary similar
modification
> to
> > their modules.
> >
> > Upon successful migration of the first subsystem, the second subsystem
> will be
> > analyzed, and so on, and so forth.
> >
> > The 6 subsystem would be deployed into 6 EAServer directories. Upon
> migrating
> > all subsystems, all non blank objects from subsystems 2 to 6 will be
> copied to
> > the subsytem 1 EAServer directory.
> >
> > Is this feasible?
> >
> > ---== Posted via the PFCGuide Web Newsreader ==---
> > http://www.pfcguide.com/_newsgroups/group_list.asp
>
>


Terence Posted on 2005-03-17 05:06:11.0Z
From: "Terence" <tamagcaoili@yahoo.com>
Newsgroups: sybase.public.appeon
Organization: 222.126.62.229
References: <42365ce9@forums-1-dub> <4236bd70@forums-1-dub> <42380528@forums-1-dub>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: modularization
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: web110.discountasp.net
X-Original-NNTP-Posting-Host: web110.discountasp.net
Message-ID: <42391043$1@forums-1-dub>
Date: 16 Mar 2005 21:06:11 -0800
X-Trace: forums-1-dub 1111035971 64.79.161.40 (16 Mar 2005 21:06:11 -0800)
X-Original-Trace: 16 Mar 2005 21:06:11 -0800, web110.discountasp.net
Lines: 141
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:722
Article PK: 20876

Thanks for the info. I think I need to know how the application is deployed to
the appeon server before I try anything else.

On 16 Mar 2005 02:06:32 -0800,
in sybase.public.appeon

Julie Jiang <julie.jiang@appeon.net> wrote:
>Since the application is indeed large (450MB), we agree with you that the
>application should be split into modules. But as the initial stage of the
>project, we think a better approach should be the following:
>
>1) Analyzing what are the core logics in the application that will be used
>over the application, and trying to put the logics in n-Tier NVOs so that
>the logics can be used by the 6 systems.
>
>2) Dividing the application into 6 systems, and making sure the systems are
>independent of each other, except that they use the common n-Tier NVOs.
>
>Your plan is to make the systems call each other after the systems are
>converted to the Web. However, Appeon-deployed applications do not offer
>open interfaces to each other. So we suggest you place the common logics in
>server NVOs for building up the communication between the systems.
>
>3) Concentrating on the deployment of the systems.
>
>Any question about this approach, please let me know.
>
>Regards,
>Julie
>
>
>
>
>
>
>
>"Julie Jiang" <julie.jiang@appeon.net> wrote in message
>news:4236bd70@forums-1-dub...
>> I cannot quite understand your last sentence, "upon migrating all
>> subsystems, all non blank objects from subsystems 2 to 6 will be copied to
>> the subsytem 1 EAServer directory", I am not sure what you will achieve
>out
>> of it. I think more feasible way is, after all the subsystems are
>migrated
>> successfully, you add several hyperlinks in the subsystem 1 for accessing
>to
>> subsystems 2 to 6.
>>
>> I will talk tomorrow with the engineers and study more about your plan.
>>
>> Regards,
>> Julie
>>
>>
>> "Terence" <tamagcaoili@yahoo.com> wrote in message
>> news:42365ce9@forums-1-dub...
>> > Good day to all.
>> >
>> > We are using appeon to move our client-server application to the
>> web/n-tier
>> > environment. We are in the initial stage of the project and need advice
>on
>> > modularization.
>> >
>> > The problem is that our application is so intertwined that it is
>difficult
>> to
>> > modularize. Removing the coupling of the modules is not possible as it
>is
>> > essential to the functionality of the software. Another thing is that
>our
>> > application size is 450MB.
>> >
>> > Can we deploy modules separately then have them call each other?
>> >
>> > We decided to break the application into several subsystems, but first
>we
>> > identified the base object libraries. The size was:
>> >
>> > Base Objects 37.2M
>> >
>> > Then we create subsystem deployment targets wherein we include in each
>the
>> "Base
>> > Object libraries".
>> > SIZE DEPLOYMENT SIZE
>> > Subsystem 1 58.9M + 37.2M = 96.1M
>> > Subsystem 2 57.5M + 37.2M = 94.7M
>> > Subsystem 3 45.8M + 37.2M = 83.0M
>> > Subsystem 4 61.0M + 37.2M = 98.2M
>> > Subsystem 5 37.7M + 37.2M = 74.9M
>> > Subsystem 6 55.8M + 37.2M = 93.0M
>> >
>> > Notice that we were able to break each deployment targets to less than
>> 100M.
>> >
>> > Now for each target we will add a library called blank. Upon building
>> each, it
>> > will error objects that are not found because it is located in another
>> > subsystem. For objects that are not found, we will create a blank object
>> with
>> > the same name in the blank library.
>> >
>> > After these, we expect that all submodules are ready for APPEON
>migration
>> > analysis. We will assign each subsystem to 1 person.
>> >
>> > The first to be analyse is the first subsystem.
>> >
>> > Problems encountered with the first subsystem that can be fixed by
>simple
>> search
>> > and replace will be immeadiately applied also to the other modules.
>> >
>> > Problems encountered that will need coding modification will be done
>first
>> in
>> > the first subsystem. The solution will be documented in a knowledge
>> repository
>> > and then assign each team member to do the necessary similar
>modification
>> to
>> > their modules.
>> >
>> > Upon successful migration of the first subsystem, the second subsystem
>> will be
>> > analyzed, and so on, and so forth.
>> >
>> > The 6 subsystem would be deployed into 6 EAServer directories. Upon
>> migrating
>> > all subsystems, all non blank objects from subsystems 2 to 6 will be
>> copied to
>> > the subsytem 1 EAServer directory.
>> >
>> > Is this feasible?
>> >
>> > ---== Posted via the PFCGuide Web Newsreader ==---
>> > http://www.pfcguide.com/_newsgroups/group_list.asp
>>
>>
>
>


Dean Jones Posted on 2005-03-31 18:54:47.0Z
From: "Dean Jones" <dean_dot_jones_at_powerobjects_dot_com>
Newsgroups: sybase.public.appeon
References: <42365ce9@forums-1-dub>
Subject: Re: modularization
Lines: 90
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
NNTP-Posting-Host: 216.207.144.172
X-Original-NNTP-Posting-Host: 216.207.144.172
Message-ID: <424c4777@forums-1-dub>
Date: 31 Mar 2005 10:54:47 -0800
X-Trace: forums-1-dub 1112295287 216.207.144.172 (31 Mar 2005 10:54:47 -0800)
X-Original-Trace: 31 Mar 2005 10:54:47 -0800, 216.207.144.172
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:764
Article PK: 20881

If you are taking time to move this to a web application now is the time to
break this application into several smaller modules.

You state that due to its size you cannot seperate. I believe its worth
taking the time now and seperate as you move to the web.

--
Dean Jones [TeamSybase]
CEO
Certified PowerBuilder Developer
www.powerobjects.com
(612) 339-3355 ext 112

"Terence" <tamagcaoili@yahoo.com> wrote in message
news:42365ce9@forums-1-dub...
> Good day to all.
>
> We are using appeon to move our client-server application to the
> web/n-tier
> environment. We are in the initial stage of the project and need advice on
> modularization.
>
> The problem is that our application is so intertwined that it is difficult
> to
> modularize. Removing the coupling of the modules is not possible as it is
> essential to the functionality of the software. Another thing is that our
> application size is 450MB.
>
> Can we deploy modules separately then have them call each other?
>
> We decided to break the application into several subsystems, but first we
> identified the base object libraries. The size was:
>
> Base Objects 37.2M
>
> Then we create subsystem deployment targets wherein we include in each the
> "Base
> Object libraries".
> SIZE DEPLOYMENT SIZE
> Subsystem 1 58.9M + 37.2M = 96.1M
> Subsystem 2 57.5M + 37.2M = 94.7M
> Subsystem 3 45.8M + 37.2M = 83.0M
> Subsystem 4 61.0M + 37.2M = 98.2M
> Subsystem 5 37.7M + 37.2M = 74.9M
> Subsystem 6 55.8M + 37.2M = 93.0M
>
> Notice that we were able to break each deployment targets to less than
> 100M.
>
> Now for each target we will add a library called blank. Upon building
> each, it
> will error objects that are not found because it is located in another
> subsystem. For objects that are not found, we will create a blank object
> with
> the same name in the blank library.
>
> After these, we expect that all submodules are ready for APPEON migration
> analysis. We will assign each subsystem to 1 person.
>
> The first to be analyse is the first subsystem.
>
> Problems encountered with the first subsystem that can be fixed by simple
> search
> and replace will be immeadiately applied also to the other modules.
>
> Problems encountered that will need coding modification will be done first
> in
> the first subsystem. The solution will be documented in a knowledge
> repository
> and then assign each team member to do the necessary similar modification
> to
> their modules.
>
> Upon successful migration of the first subsystem, the second subsystem
> will be
> analyzed, and so on, and so forth.
>
> The 6 subsystem would be deployed into 6 EAServer directories. Upon
> migrating
> all subsystems, all non blank objects from subsystems 2 to 6 will be
> copied to
> the subsytem 1 EAServer directory.
>
> Is this feasible?
>
> ---== Posted via the PFCGuide Web Newsreader ==---
> http://www.pfcguide.com/_newsgroups/group_list.asp