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.

Maintenance of the application

4 posts in Appeon (partner product) Last posting was on 2004-03-23 10:17:41.0Z
SyBo Posted on 2004-03-18 14:13:34.0Z
Sender: 3066.4059ae7a.1804289383@sybase.com
From: SyBo
Newsgroups: sybase.public.appeon
Subject: Maintenance of the application
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <4059ae8b.3067.846930886@sybase.com>
X-Original-NNTP-Posting-Host: 10.22.241.42
X-Original-Trace: 18 Mar 2004 06:13:31 -0800, 10.22.241.42
Lines: 13
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 18 Mar 2004 06:13:33 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 18 Mar 2004 06:13:34 -0800
X-Trace: forums-1-dub 1079619214 10.22.108.75 (18 Mar 2004 06:13:34 -0800)
X-Original-Trace: 18 Mar 2004 06:13:34 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:167
Article PK: 12413

We have a client-server application that we convert to an
web-application, but the maintenance is still remaining on
the C/S-application.
Most of the unsupported features are solved with changing
the code to NVO-objects.
But how do we still maintenance the client-server
application if there are NVO-EAServer objects instead of
userobjects?
Has someone the same workstill or does someone has an idea
how to solve this?

Kind Regards,
SyBo


Julie Jiang Posted on 2004-03-19 09:59:38.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <4059ae8b.3067.846930886@sybase.com>
Subject: Re: Maintenance of the application
Lines: 100
Organization: Appeon Corporation
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0DC4_01C40DDC.78F36600"
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.53
X-Original-NNTP-Posting-Host: 61.144.207.53
Message-ID: <405ac48a@forums-1-dub>
Date: 19 Mar 2004 01:59:38 -0800
X-Trace: forums-1-dub 1079690378 61.144.207.53 (19 Mar 2004 01:59:38 -0800)
X-Original-Trace: 19 Mar 2004 01:59:38 -0800, 61.144.207.53
X-Authenticated-User: appeon
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:169
Article PK: 12411

Hi,
 
You are right, "the maintenance is still remaining on the C/S application". One advantage of it is that you can maintain the C/S application and the Web application at the same time.  You continue using the C/S application in intranet, and use the Web application in Internet.
 
If some change is made to a server NVO, you need to re-deploy the modified NVO to EAServer (including generating stubs/skeletons, as instructed in the section 4.2, Distributed desktop applications, in the Appeon Migration Guide) - the same as deploying a new package. However, if no change is made to the application source code, it is not necessary to perform incremental/full deployment of the application.
 
Regards,
Julie Jiang
Appeon Corporation
 
<SyBo> wrote in message news:4059ae8b.3067.846930886@sybase.com...
> We have a client-server application that we convert to an
> web-application, but the maintenance is still remaining on
> the C/S-application.
> Most of the unsupported features are solved with changing
> the code to NVO-objects.
> But how do we still maintenance the client-server
> application if there are NVO-EAServer objects instead of
> userobjects?
> Has someone the same workstill or does someone has an idea
> how to solve this?
>
> Kind Regards,
> SyBo


SyBo Posted on 2004-03-22 09:49:45.0Z
Sender: 1d1d.405eb6a3.1804289383@sybase.com
From: SyBo
Newsgroups: sybase.public.appeon
Subject: Re: Maintenance of the application
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <405eb6b9.1d1f.846930886@sybase.com>
References: <4059ae8b.3067.846930886@sybase.com><405ac48a@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Mar 2004 01:49:45 -0800
X-Trace: forums-1-dub 1079948985 10.22.241.41 (22 Mar 2004 01:49:45 -0800)
X-Original-Trace: 22 Mar 2004 01:49:45 -0800, 10.22.241.41
Lines: 11
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:173
Article PK: 12412

Hi Julie Jiang,

Thanks for you answer. But what I don't understand is that
after making the proxy object you have to move the
nvo-object to another application (together with the
proxy-project). Our main application is the C/S, so that we
can't move the nvo-object to another application. Have you a
suggestion how we can handle the maintenance?

Thanks,
SyBo


Julie Jiang Posted on 2004-03-23 10:17:41.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <4059ae8b.3067.846930886@sybase.com><405ac48a@forums-1-dub> <405eb6b9.1d1f.846930886@sybase.com>
Subject: Re: Maintenance of the application
Lines: 96
Organization: Appeon Corporation
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09DF_01C41103.927F0AF0"
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.53
X-Original-NNTP-Posting-Host: 61.144.207.53
Message-ID: <40600ec5@forums-1-dub>
Date: 23 Mar 2004 02:17:41 -0800
X-Trace: forums-1-dub 1080037061 61.144.207.53 (23 Mar 2004 02:17:41 -0800)
X-Original-Trace: 23 Mar 2004 02:17:41 -0800, 61.144.207.53
X-Authenticated-User: appeon
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:176
Article PK: 20617

Hi SyBo,
 
As we can get from your previous email, you have created a number of NVO-EAServer objects in the application, so your application is a PowerBuilder distributed application.  For such distributed applications, a common PowerBuilder technique is to move the NVO-EAServer objects into another application, so that when the NVO is called, the application knows whether the call is targeted for the Proxy object or for the NVO-EAServer object. 
 
Appeon only requires you to maintain the PowerBuilder distributed application in the way as maintaining a normal distributed application.  For the Web application maintenance, please use the method I suggested in my first reply.
 
Regards,
Julie
 
 
<SyBo> wrote in message news:405eb6b9.1d1f.846930886@sybase.com...
> Hi Julie Jiang,
>
> Thanks for you answer. But what I don't understand is that
> after making the proxy object you have to move the
> nvo-object to another application (together with the
> proxy-project). Our main application is the C/S, so that we
> can't move the nvo-object to another application. Have you a
> suggestion how we can handle the maintenance?
>
> Thanks,
> SyBo