Hi All,

I would like to  request for references to GatewayScript Programming best practices and / or good/bad experiences on programming techniques/constructs , diagnostics and debugging.

Thanks,

Paul

------------------------------
Paul Dango
------------------------------

• GatewayScript Programming best practices - create CommonJS compliant code:
  https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=gateway-programming-model-gatewayscript
• good/bad experiences on programming techniques/constructs
  - write "async" code only if you know what you are doing 
  - better use "buffer" datatype (works for up to 1GB size) than "buffers" datatype (has no size limit, list of buffer objects internally)
  - make sure that any input cannot cause a GatewayScript to run for 2min or more unless you want to see watchdog reload:
  https://community.ibm.com/community/user/integration/discussion/avoid-transactions-running-for-more-than-2-minutes-or-accept-the-risk-for-datapower-watchdog-reload#bmda4604b3-6db6-48c2-88b1-238cd2cf2ddb
  [easiest way to do this is "for(;;){}" ;-) ]
• debugging
  during dev use "debugger" statement in script and connect to session in CLI allowing single step, continue, variable inspection and change, ...
  https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=gatewayscript-debugger-sessions

------------------------------
Hermann Stamm-Wilbrandt
Compiler Level 3 support, IBM DataPower Gateways
IBM
Boeblingen
------------------------------

Adding a recommendation to observe the GwS runtime engine availability using the gatewayscript-status status provider:

X3DP:idg(config)# sh gatewayscript-st

Available run times: 64 
   In-use run times: 0 
        Queued work: 0
   Runtime failures: 0 

During stress and performance testing, I recommend polling this status provider periodically to confirm if queuing is present or not.  For maximum performance you never want to see run time pool exhaustion.

------------------------------
Ivan Heninger
------------------------------