Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved EA server migration

  1. How-to
0
Votes
Undo
  1. Sally D
    Sally D
  2. PowerBuilder
  3. Tuesday, 31 July 2018 06:41 AM UTC

For a C/S product, if need to migrate to pb2017version. How to migrate the EA server?  Thanks for help

OrcaScript Build with Git/SVN PB2017 R3
2017 R3 LTS
Accepted Answer
Sally D
Sally D Accepted Answer Pending Moderation
  1. Tuesday, 31 July 2018 07:32 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Armeen,

 

Thanks for reply soon. Is the obsolete feature you said which is using .net assembly and visual stutio to develop?

 

And if using PB2018, we need to change our C/S architecture to B/S with the auto migration tool to C#?

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 1 August 2018 02:43 AM UTC


Hi Sally,



The obsolete feature is the .NET assembly target in the native PowerBuilder IDE (not Visual Studio). The Visual Studio IDE Sybase created for PB 12 was never launched to the market by Appeon due to poor market adoption and quality issues.



There is no need to change from a PowerBuilder desktop client to a Web browser client. Of course you can do this, but this could be a lot more extra work depending on how you decide to migrate to a B/S architecture. In case you do want to run in the web browser, we have a product called PowerServer Web that automatically converts a PowerBuilder desktop client (most PB features) to run in a web browser. A free developer edition is included with the PowerBuilder Universal Edition license.



Now back to your EAServer question, the migration tools provided in PB 2018 to port the EAServer NVOs to C# .NET assemblies focuses on the DataWindows. The PowerScript would need to be hand-coded in C#, but since the coding is based on DataWindow and the C# DataWindow has similar properties, events, functions, so I think you will find it is not very difficult. Please take a look at these code examples to get an idea: http://showcase.appeon.com/showcase_2_201.html



Once your EAServer NVOs are ported to C# .NET assemblies with PowerBuilder 2018, your existing PowerBuilder client can call these C# .NET assemblies as REST Web APIs. In PowerBuilder 2017 R3 we added tons of features so DataWindows can readily and easily consume REST Web APIs. In PowerBuilder 2018, we also automatically create a REST Web API wrapper around your .NET assemblies (if you choose the C# Web API target option that is shown in the video).



Hope this clears some things up. I think it'll make a lot more sense if you grab an "insider" release of PB 2018 and try to do a proof-of-concept migration of one of your EAServer NVOs.



Regards,

Armeen
  1. Helpful
Sally D
  1. Sally D
  2. Wednesday, 1 August 2018 03:22 AM UTC
Hi Armeen,

Thanks a lot. I sent an email to sales.dept to get the insider release of PB 2018. But no responding till now. Do you know any other procedure to get that?
  1. Helpful
There are no comments made yet.
Responses (3)
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Tuesday, 31 July 2018 11:58 AM UTC
  2. PowerBuilder
  3. # 1

Another option(s) would be to convert your EA Server code to Java or .NET and expose that functionality as web services.  Then you would modify your client code to call the web services instead of EA Server components.  I've done a ton of EA Server work over the years, so if you need any help please don't hesitate to shoot me an email.

 

Kevin

kjr_23@yahoo.com

Comment
Sally D
  1. Sally D
  2. Wednesday, 1 August 2018 01:34 AM UTC
Thanks Kevin, I have sent to your yahoo email to confirm more detail method, please check.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 31 July 2018 07:18 AM UTC
  2. PowerBuilder
  3. # 2

There are generally two options/approaches that would be the least amount of work:

1. Convert the EAServer NVOs to client-side NVOs (i.e. go back to a 2-tier client/server app)

2. Port your EAServer NVOs to C# Web APIs with PB 2018: https://www.appeon.com/pb2018.html 

Appeon is providing EAServer customers with "insider" releases of PB 2018 so they can begin their migration now.  You would need to contact the sales dept. sales@appeon.com to arrange this.

For the sake of being complete, PowerBuilder does have a .NET Web Service target that deploys existing PowerScript NVOs as SOAP Web services, but that is an obsolete feature.  So even though it is in the product, it is not being enhanced or receiving updates and therefore it is not wise to use that as an EAServer migration approach.

Comment
Sally D
  1. Sally D
  2. Tuesday, 31 July 2018 07:40 AM UTC
Hi Armeen,

Thanks for reply soon. Is the obsolete feature you said which is using .net assembly and visual stutio to develop?

And if using PB2018, we need to change our C/S architecture to B/S with the auto migration tool to C#?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.