Hi,

for 1+2 I use this since 2010 (I developed coproc2):
https://github.com/ibm-datapower/datapower-tools/tree/master/coproc2

For 3 I use most times curl, because it does not modify stuff and tells you the truth and nothing but the truth.
With "-v" and "--data-binary", you will loose the truth part if abbreviating as "-d" because that is "--data". 

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

Thanks Harmann, 

I will go through these definitely. These appears as tools to validate the coding done. Where do you prefer to write the code in general? Just a notepad++ or anything specific to avoid bugs in syntax & format?

Thanks again !

Hi,

for 1+2 I use this since 2010 (I developed coproc2):
https://github.com/ibm-datapower/datapower-tools/tree/master/coproc2

For 3 I use most times curl, because it does not modify stuff and tells you the truth and nothing but the truth.
With "-v" and "--data-binary", you will loose the truth part if abbreviating as "-d" because that is "--data". 

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

>  Where do you prefer to write the code in general? Just a notepad++ or anything specific to avoid bugs in syntax & format?
>
I stopped using Windows when joining DataPower team in 2007.
Since 1990 I use vi editor, these days vim (vi improved) with its syntax highlighting for more than 500 different syntax.

If forced to do something on a Windows computer, I use cygwin and vi if available.
If not notepad/wordpad/notepad++.

For formatting XML I use "xmllint --format file.xml".
For pretty printing JSON I send it against DataPower loopback XMLFW service executing "store:///identity-json.js".

Thanks Harmann, 

I will go through these definitely. These appears as tools to validate the coding done. Where do you prefer to write the code in general? Just a notepad++ or anything specific to avoid bugs in syntax & format?

Thanks again !

Hi,

for 1+2 I use this since 2010 (I developed coproc2):
https://github.com/ibm-datapower/datapower-tools/tree/master/coproc2

For 3 I use most times curl, because it does not modify stuff and tells you the truth and nothing but the truth.
With "-v" and "--data-binary", you will loose the truth part if abbreviating as "-d" because that is "--data". 

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

>  Where do you prefer to write the code in general? Just a notepad++ or anything specific to avoid bugs in syntax & format?
>
I stopped using Windows when joining DataPower team in 2007.
Since 1990 I use vi editor, these days vim (vi improved) with its syntax highlighting for more than 500 different syntax.

If forced to do something on a Windows computer, I use cygwin and vi if available.
If not notepad/wordpad/notepad++.

For formatting XML I use "xmllint --format file.xml".
For pretty printing JSON I send it against DataPower loopback XMLFW service executing "store:///identity-json.js".

Thanks Harmann, 

I will go through these definitely. These appears as tools to validate the coding done. Where do you prefer to write the code in general? Just a notepad++ or anything specific to avoid bugs in syntax & format?

Thanks again !

Hi,

for 1+2 I use this since 2010 (I developed coproc2):
https://github.com/ibm-datapower/datapower-tools/tree/master/coproc2

For 3 I use most times curl, because it does not modify stuff and tells you the truth and nothing but the truth.
With "-v" and "--data-binary", you will loose the truth part if abbreviating as "-d" because that is "--data". 

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

Also consider using DPOD for troubleshooting and debugging your new services. If you don't already have it, the Dev Edition is free.

DPOD collects the logs and the Probe data, so once you (or someone else) invoke a request, you can inspect in DPOD the transaction logs, payloads, content, variables, action rules, errors, latency, etc. and  easily understand what went wrong and how to fix it.