I've come to know that for amazon aws connection using psoc6 (cypress board) and modus toolbox sample code i.e. anycloud mqtt client , the ALPN(application layer protocol negotiation) is "x-amzn-mqtt-ca" which is on port 443 likewise is what is the ALPN for IBM Watson?
Setting the ALPN isn't supported on IBM Watson IoT Platform. If you want to connect via port 443 then you can use HTTPS as described on this page https://www.ibm.com/support/knowledgecenter/en/SSQP8H/iot/platform/reference/mqtt/index.html
Related
I have accidentally deleted Watson IoT service on my space. I have created a recent one and tried to configure a mqtt subscriber via node-red to send data to the new service.
It always shows disconnected to the service even though I did all the configuration requirements. ( Server , topic , token authentification .. ).
PS: I am using port 1883 and I have changed the service security to TLS optional.
What should I look up for ? Do I have to change other changed settings ?
I have built a working IBM api connect service (loopback) that provides local mySQL data to/from an angular website. I now want to move this service to an Ubuntu web server (appache) so that I can open up the website to external traffic. I have moved installed api connect onto the server and moved the project files across.
But I don't understand how to run the project so that it is available externally. When I run API connect the api is available on a local port address: Web server listening at: http://127.0.0.1:9000.
But in my webpage (angularjs) I can't call this as it tries to connect on the client machine, not server.
Has anyone done this before and if so, can you offer any advice?
You should configure your Apache as a reverse proxy, so that it forwards requests from your public ip address at port 80 (or 443 if you want SSL) to localhost:9000. See https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html or https://www.nginx.com/resources/admin-guide/reverse-proxy/ if you'd like to try out Nginx.
I know we can send heartbeat payload through device monitoring topic. But do we have any another way where any IP capable device can send heartbeat to IBM Watson Platform through any IBM services or database for device tracking?
I assume with "any IP capable device" you mean you don't want/can install a MQTT stack?
You can use HTTP(S) instead, as described here
fyi: You don't need the IBM API client, any MQTT library is sufficient then you can also use MQTT instead HTTP(S)
I plan to set the Secure Gateway Client at DMZ at on-premise environment, so I need to open Outbound ports for SG Client to connect to SG on Bluemix. The following question is similar to my question, but the answer doesn't show the needed ports.
For the Bluemix Secure Gateway service, how does the data center's network need to be configured?
For the Bluemix Secure Gateway service, how does the data center's network need to be configured?
The following Bluemix Doc shows Outbound 443 is needed.
https://www.ng.bluemix.net/docs/troubleshoot/SecureGateway/ts_index-gentopic1.html#ts_sg_006
What are the best practices for running the Secure Gateway client?
Before you install the Docker client into your environment, ensure that both the internet and your on-premises assets are accessible and all host names are resolvable by a DNS. The client uses outbound port 443 to connect to the IBM Bluemix environment, normally this port is open since its secure. Ensure you check or modify additional firewall and IP Table rules that might apply.
But, the tcpdump, which I got when I executed "docker run -it ibmcom/secure-gateway-client XXXX", showed that SG Client used Outbound 443 and 9000. Is it collect that all ports SG Client uses are Outbound 443 and 9000 ?
Correct, if you are closing down both outbound and inbound ports using your firewall, then for outbound allow ports 443/9000. So your initial assertion is correct.
I'm using SMACK library (JAVA) to handle XMPP connection on an android platform and i would like to know if google support BOSH.
Recently my mobile operator locked some ports and now i'm limited to 80 and 8080 ports so BOSH would be a great solution.
thanks for your time
Well after some research and tests i conclude that is possible to connect using port 80 instead 5222 recommended by google. Connecting via port 80 doesn't use BOSH so you can use any XMPP client library to connect over.