One thing you could do is run the self test.
python -m unittest test.self_test
Capture the output and paste it back into this thread and we can take a look to see that everything is normal.
Another thing you can do is verify that
gwe can successfully activate by running
gwe --gateway-cik. You should see a 40-char string printed to your terminal once it’s been activated.
To test out
gmq, try using
curl commands like the ones in the docs here.
There’s also a lightweight CLI called
gdc for the Exosite HTTP Data API that can be used to communicate to either Exosite directly, or to
gmq. You can find the docs here (but the location may change - sorry). The main trick with using
gdc to send data via
gmq is to implement
- Override the default
localhost:8090 with the
gdc --host option.
- Disable SSL with the
gdc --no-ssl as
gmq communicates unencrypted on localhost.
- Disable the Product Domain feature with the
gmq --no-product-domain. By default, the Product ID is pre-pended to the
host (i.e. a9y794hj0a28h.m2.exosite.com).
- Disable form encoding of outbound data with the
gmq --no-form-encode. This ensures your data is not form encoded twice (i.e. once by
gdc and then again by
Putting these 4 together your
gdc command line would look something like this:
gdc write $CIK $DATAPORT $MY_DATA --host localhost:8090 --no-ssl --no-product-domain --no-form-encode
If you don’t want to use
gmq, you can drop all those options and just use:
gdc write $CIK $DATAPORT $MY_DATA