Skip to Content
author's profile photo Former Member
Former Member

What is the EAServer Upgrade Path?

One of our major systems, created in 1995, is currently deployed under PowerBuilder 10.5.

We use EAServer 5.5 to make selected reports available via the web as PDFs. These are dynamic reports, generating their results based on user specified input parameters.

I've been asked to come up with recommendations on possible upgrade paths for this functionality.

I understand that there is a more recent version of EAServer, but I have heard that migration to the more recent version is difficult, and that the more recent version has problems, and is less stable than the tried-and-true 5.5 version. In fact, when I go to the Sybase site and look for information on EAServer, I get directed to pages talking about SAP NetWeaver. So upgrading to EAServer 6 doesn't really look like a great long-term solution.

Can anyone give us any recommendations for a good upgrade path for our existing reporting functionality?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Jul 31, 2013 at 03:44 PM

    If SAP was to come out tomorrow and announce the end-of-life for the product (not something I'm expecting, just a hypothetical situation), I would suggest that you have a couple of options.

    1. Convert the existing deployed objects into either ASP.Net ( PB Classic ) or WCF ( PB.Net ) web services. This would require quite a bit of rewrite. Note also that if you are currently using the GetFullState, SetFullState, etc. approach to passing datawindow data, that PB.Net and PB Classic use different (and incompatible) formats for passing the data.

    2. Wait and see if SAP provides the capability to deploy PowerBuilder objects into NetWeaver with PowerBuilder 15. It was mentioned as part of the roadmap. However, the also mentioned that the would deploy as servlets rather than EJBs, so you could still be looking at some rewrite.

    Given that the 2nd option isn't available yet to evaluate, you might just consider continuing with your current configuration for a while. Is there something that it isn't supporting now that you need? As they say, "no upgrade ever goes unpunished", so you'd only want to upgrade if there were significant new capabilities resulting from it.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 31, 2013 at 11:51 AM

    Hi Sue;

    EAS v5.5 was Sybase's best release of the application server. Since going to v6.x - EAS has not been the same - functionally, stability or performance wise.

    Sybase has not been enhancing EAS since 6.3 and the main developers and architect have been reassigned to other Sybase products (and now SAP) for many years. AFAIK (sorry to be blunt here) there is no migration path for EAS applications. Even NetWeaver is whole different architecture than EAS and does not support NVUO's (aka the PBVM) anyway - so its a non-starter.

    I keep hoping that SAP will wake up to the fact that they need to bring back Distributed PowerBuilder (DPB) to replace the soon to be EOL for EAS. DPB was the forerunner to EAS and had all the bells and whistles for remote NVUO support .. plus it was free! :-)

    Regards ... Chris

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 31, 2013 at 08:25 AM

    We are in the same situation. We use EAServer 5.5 in production and try to migrate to
    EAServer 6 without final success. We are also looking for a long-term solution
    after EAServer 6 and are interested in a good upgrade path.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 07, 2014 at 03:04 PM

    Hi Guys & Gals

    Since EAS is now official EOL at the end of this year I have been looking at the options open to us.

    My preferred route is to go Fat Client and then Appeon, has anyone converted to FAT client who could shed some light on the potential pitfalls of ding so.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.