Steps for moving unsupported features or business logic to Appeon Server

Step 1: Create new PowerBuilder NVO objects; add user functions, events and/or properties to them as necessary. Place unsupported code or business logic in these functions/events.

Step 2: Deploy the NVOs holding unsupported features to the EAServer hosting Appeon Server that is used for Web deployment of the target PowerBuilder application. To deploy an EAServer component from a PowerBuilder NVO, use the EAServer Component Project wizard in PowerBuilder.

Step 3: Generate stubs and skeletons of the server NVO components that you have deployed in the previous step.

Step 4: Make sure the Bind Thread property of each server component is enabled in the Properties | Instances tab.

Step 5: Build the EAServer Proxy objects in the target application Client. The Proxy objects act as agents for Server NVO Components. To define an EAServer Proxy object, use the EAServer proxy object generator in the PowerBuilder Project painter.

Step 6: At the target application Client, modify the Connection object properties and connect to the deployment Appeon Server.

Step 7: Instantiate the Server NVO Components and call their methods to replace the original unsupported code in the target PowerBuilder application.

Step 8: Run and debug the target application in PowerBuilder to ensure the application client works correctly with Server NVO Components, then perform a full build and optimize the application target in the PowerBuilder IDE.

For more information on deploying and using EAServer components from PowerBuilder NVOs, refer to PowerBuilder Help and SAP EAServer documentation.