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.


Console command output as JSON object / in-memory representation

If you invoke a Traveler console command, you can redirect the output / response to a textfile instead of the console.
This is great, if you are invoking the command from within a server based plugin or agent.
You can then read the textfile and extract the information that you need in your program. We do this a lot in our products @midpoints.

Parsing of the textfiles was and is PITA, because the information is unstructured. And ( and this happened ) if IBM / HCL changes the output then we might run into a problem, because our parse might not return the correct part of the file.

This becomes more complicated, if you have an HA environment with 2 - n servers in a pool.

The ‚tell traveler -s * stat show‘ command for example returns all information for ALL servers in a pool in one textfile. That is OK, but if you want to extract the information for one specific server from that file, this is not easy. And also, the returned information is not consistent for other commands that support the -s * option when speaking of how to find the start of a new "server block"

It would make our live a lot easier, if we could have the output in JSON format.
Also, an in-memory representation of the command output would be much appreciated.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 15 2018
  • Attach files