- Michael Volkert
- PowerBuilder
- Wednesday, 28 October 2020 11:44 AM UTC
Dear Community,
I work as a software developer for ERGO Direkt AG. I would be very happy to receive a professional assessment of the following situation.
We have been developing a surface with the PowerBuilder (Powerscript) technology for our claims and benefits processing software since the 1990s. The communication between the PowerBuilder and our JAVA backend takes place with stateful EJBs (Java 1.7). Adjustments and further developments are currently being implemented with the PowerBuilder version 2017 R3. The PowerGen 2017 tool (E. Crane Computing) supports our build process for generating the client application.
The knowledge and experience regarding PowerBuilder and PowerScript are rather limited after leaving our lead developer within the team. In this way, features and adjustments to the interfaces can be implemented, but the specialist knowledge of the general build process and communication based on interfaces within PowerBuilder is virtually non-existent.
Our goal is now:
- make changes (including stateful EJBs -> REST web services) to the extent that a development with the PowerBuilder technology is future-proof for the next few decades
- replace support tools such as PowerGen 2017 and execute build processes using the PowerBuilder features that are already included
The following questions:
1. How about here, the right way to achieve our goals?
2. What difficulties can we face in implementation?
Thank you in advance for your advice and assessment.
Best regards
Michael Volkert
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.