Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The Profound.js Connector is the commercial add-on to the Profound.js Framework and Visual Designer that adds robust IBM i connectivity capabilities and API. The Connector features are installed into an IBM i library that match the Profound.js instance name.

Below is a list of some of the features provided by the Profound.js Connector.

  • Ability for legacy code to start utilizing any Node.js module, and immediately realize the benefits of the open source ecosystem, including the use of Web services, npm, IoT, and Watson in your applications
  • Ability to modernize RPG to Node in a step by step iterative manner, rather than using an “all or nothing” approach
  • IBM i DB2 Node.js driver for both Record Level Access and SQL operations, including support for overrides and QTEMP in an interactive job
  • Ability to code Node.js logic in a top-down manner suitable for transactional business applications (“callback hell” is automatically avoided)
  • Integration with Profound UI’s Rich Display or HTML-based user interface technologies
  • Ability for Node.js modules to act like native ILE programs on IBM i
  • Ability to call RPG, CL, and COBOL programs seamlessly
  • Capability to call 5250 green-screen interactive commands from Node, and having them render as HTML5 on-the-fly
  • Ability for Node.js to be called from RPG, CL, or the command line using a standard IBM i CALL
  • Support for all native IBM i data types and seamless handling of parameters between native programs and Node.js
  • Ability to call any service program procedure on IBM i from Node, including operating system API
  • Ability to automatically expose any existing legacy logic as SOA web services, even when legacy programs are not well-modularized and screen logic is intermingled with business logic
  • Conversion service can automatically modularize existing code, make it more readable, introduce modern object-oriented concepts, and remove dead code

 

·         Ability for legacy code to start utilizing any Node.js module, and immediately realize the benefits of the open source ecosystem, including the use of Web services, npm, IoT, and Watson in your applications

·         Ability to modernize RPG to Node in a step by step iterative manner, rather than using an “all or nothing” approach

·         IBM i DB2 Node.js driver for both Record Level Access and SQL operations, including support for overrides and QTEMP in an interactive job

·         Ability for Node.js modules to act like native ILE programs on IBM i

·         Ability to call RPG, CL, and COBOL programs seamlessly

·         Capability to call 5250 green-screen interactive commands from Node, and having them render as HTML5 on-the-fly

·         Ability for Node.js to be called from RPG, CL, or the command line using a standard IBM i CALL

·         Support for all native IBM i data types and seamless handling of parameters between native programs and Node.js

·         Ability to call any service program procedure on IBM i from Node, including operating system API

·         Ability to automatically expose any existing legacy logic as SOA web services, even when legacy programs are not well-modularized and screen logic is intermingled with business logic

Labels
  • No labels