Welcome to the #dominoforever Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated jointly by the IBM & HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino page.


Replace with Node-RED

Build as functionality for Node-RED.

This may require routing some processes through NRPC or gRPC to avoid errors if agents are hidden from web.

https://www.npmjs.com/package/node-red-contrib-odbc seems to cover ODBC integration. The format files may need convertinginto a JavaScript function, but a Node-RED node may allow DevOps to set these up more easily. Certainly the LEI approach of a text file is not intuitive.

Some more flexible approach may be required for more flexible threading and success / failure routing.

Add functionality to migrate existing LEI environments to Node-RED.

This may require some hard decisions about pricing, but LEI is basically in maintenance mode, with no new functionality as far as I know. For example, I don't think it's possible to schedule a job to call a REST service and set up OAuth. Whether the migration tool and/or Node-RED nodes are licensed, or whether it is covered by a separate support agreement, there are options for replacing the current revenue. But by migrating to a more modern open-source platform, it may reduce current support costs of keeping it running on the latest Domino versions as well as finding a way to allow customers to migrate their LEI environments as part of a move to DAC or other cloud alternatives.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 6 2018
  • Attach files