Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
I have a Thingworx foundation server and am trying to get the EMS started on the same machine, but am having some trouble. These are the steps I have followed:
1. I installed MED-61060-CD-053_SP5_Microserver-5-3-4-2383-Win32
2. I configured the config.json file with this (the app key is from my ThingWorx application key
Solved! Go to Solution.
Hi @apdams
your config.json does not show anything on port 8000, shouldn't you check the url http://192.168.1.33:8084/Thingworx/Things/LocalEms/Properties/isConnected instead ?
Christophe
I think I am making progress, but still not all the way there.
I changed my config.json to look like this:
{
"ws_servers": [{
"host": "192.168.1.33",
"port": 80
}],
"appKey": "c03fa7e6-ab2f-47bd-9b0b-3d93e2bd03c9",
"logger": {
"publish_directory": "logs",
"level": "DEBUG",
"publish_level": "INFO",
"max_file_storage": 2000000,
"auto_flush": true,
"flush_chunk_size": 16384,
"buffer_size": 4096
},
"ws_connection": {
"encryption": "none",
"verbose": true
},
"http_server" : {
"host": "192.168.1.33",
"port": 8084,
"ssl": false,
"content_read_timeout": 20000,
"authenticate": false
},
"file": {
"virtual_dirs": [
{"logs": "logs"},
{"instruction":"instruction"}
],
"staging_dir": "c:\\ems\\microserver\\staging"
}
}
From the output when I run wsems, I think it is getting further. This is the output:
Hi Sharon
I have (I think) made more progress.
This is my latest config file (changed the ws_servers port to 8080):
{
"ws_servers": [{
"host": "192.168.1.33",
"port": 8080
}],
"appKey": "c03fa7e6-ab2f-47bd-9b0b-3d93e2bd03c9",
"logger": {
"publish_directory": "logs",
"level": "DEBUG",
"publish_level": "INFO",
"max_file_storage": 2000000,
"auto_flush": true,
"flush_chunk_size": 16384,
"buffer_size": 4096
},
"ws_connection": {
"encryption": "none",
"verbose": true
},
"http_server" : {
"host": "192.168.1.33",
"port": 8084,
"ssl": false,
"content_read_timeout": 20000,
"authenticate": false
},
"certificates":{
"validate":false,
"allow_self_signed":true
},
"file": {
"virtual_dirs": [
{"logs": "logs"},
{"instruction":"instruction"}
],
"staging_dir": "c:\\ems\\microserver\\staging"
}
}
Now, when I run wsems on the command prompt, it sort of looks like it is working. This is what I get:
rows | |
0 | |
isConnected | false |
datashape | |
fieldDefinitions | |
isConnected | |
name | "isConnected" |
description | "" |
baseType | "BOOLEAN" |
aspects | {} |
Hi @apdams
your config.json does not show anything on port 8000, shouldn't you check the url http://192.168.1.33:8084/Thingworx/Things/LocalEms/Properties/isConnected instead ?
Christophe
i Christophe
That was it.
Thanks a lot
Adrian
Hi Christophe
Something very strange has happened. Earlier, my EMS was working and I could query the connected status and it was returning true. I am running the same config file, but now I am getting this in the output and the connected status is false:
What is happening here?
Adrian
Turns out to be the application key had expired.
Suggestion: the error message "api:sendMessageBlocking: Receive failed." is not particularly useful. Something like "application key has expired" would be more useful