Questions? Feedback?powered byOlark live chat software

We are sorry to say that EAServer was not part of the agreement with SAP, and as such the EAServer target has been discontinued since PowerBuilder 2017.

There are essentially two options if you want to avoid a complete rewrite of your EAServer-deployed PowerBuilder NVOs:

  1. If your NVOs do not have server-side dependencies, consider migrating your NVOs back to the PowerBuilder client-side; or
  2. Otherwise, we recommend migrating your NVOs to the new server-side .NET C# targets (either assemblies or Web services), which will be introduced in PowerBuilder 2019 (originally named as PowerBuilder 2018).  It provides migration solutions for the key parts of an NVO: DataWindow/DataStore objects, embedded SQL, PowerScript logic, and transaction management.  
  •  For DataWindow/DataStore objects, a conversion engine will be provided in the PowerBuilder IDE to automatically migrate the existing DataWindow/DataStore data objects to C# DataStores.  As such, DataWindows/DataStores can be directly reused in C# with minimal effort.
  •  For embedded SQL, the developer can basically copy n’ paste into the new C# SQLExecutor object. As such, embedded SQL can be directly reused in C# with minimal effort.
  •  For PowerScript logic, a C# DataStore is provided with virtually the same properties, events, and functions as PowerScript, such that existing PowerScript logic ends up essentially being a “port” effort to C#. While this will require writing C# by hand, the C# can essentially follow the way the PowerScript is currently written if desired.  
  •  For transaction management, a C# DataContext object is provided to do complex transaction that spans across multiple NVOs. It also supports stateless processing as in EAServer.  Data caching is provided by the .NET framework itself.

We recommend carefully studying the PowerBuilder roadmap and migrating off of EAServer as soon as possible.  If you choose to continue using EAServer, you can use PowerBuilder 2017 to maintain your desktop apps and older versions of PowerBuilder to maintain the EAServer-deployed PowerBuilder NVOs.