With n-Tier NVOs, you can work around:
-
A large amount of unsupported DataWindow (DW) syntax (functions, events, properties, dot notation and expressions) in conjunction with the Appeon distributed DataWindow technique (Windows only) (support of DW Get/SetFullState, Get/SetChanges)
-
Some unsupported non-visual PowerBuilder system objects
-
Some unsupported system functions
N-Tier NVOs can also:
-
Remove Web browser limitations by running PowerBuilder NVO code inside the EAServer hosting Appeon Server
-
Connect to DLLs
-
Connect to other PowerBuilder NVOs & Java/EJBs in the EAServer hosting Appeon Server.
-
Connect to EJBs in SAP EAServer, Oracle WebLogic, IBM WebSphere, TmaxSoft JEUS, JBoss, and other J2EE-compliant application servers through PowerBuilder 9.0 PBNI/EJB support
-
Connect to remote Web Services or .NET components
-
Create and expose Web Services from PowerBuilder NVOs using the EAServer Web Services Toolkit
-
Connect to C++ Classes/DLLs through PBNI and vice-versa
-
Connect to Messaging Systems through Message Queues (JMS, MQSeries, Tibco)
-
Create XML result sets for sending to other companies/departments using PowerBuilder 9.0 XML DataWindow or PBDOM functionality
-
Consume XML result sets from other companies/departments using PowerBuilder 9.0 XML DataWindow or PBDOM functionality
-
Create PDF DataWindow files and/or manipulate text files using the PowerBuilder 9.0 DataWindow SaveAs (PDF) functionality
-
Move logic and processing from the client to the server. The more you move to the server, the faster the client will run and the lighter and less complex the Web files will be. For example, there was an application from a large Japanese conglomerate that took more than ten seconds to execute a DataWindow Update. The complex validation rules in the Update were consolidated into n-Tier NVOs, and the DataWindow Update now only takes one second.
