Skip to main content
V
Vimal_Rawat14-Alexandrite
14-Alexandrite
February 25, 2023
Solved

Unable to run Thingworx Integration Runtime:"Endpoint reconnection was unsuccessful."

  • February 25, 2023
  • 2 replies
  • 2986 views

Hi,

I am trying to run Thingworx Integration Runtime but it is not able to connect to the Thingworx instance.

After running the below command from cmd:-

"java -DconfigFile=integrationRuntime-settings.json -jar integration-runtime-8.0.12-b1455.jar"

I can see the service trying to start but then at the end i get the message  "Endpoint not connected", which it attempts to reconnect but never connects.

 

 

Best answer by TonyZhang

Hi @pshashipreetham 

If you can access ThingWorx Composer or Mashup, you should be able find the IP in the URL address.

replace the IP with localhost in the integrationRuntime-settings.json.

Make sure you can access/ping the IP address from the server where you are running Integration Runtime.

 

If your ThingWorx is running in HA cluster mode, you will need to install and run Connection server to route the websocket communication.

The Integration Connector uses WebSockets to communicate with ThingWorx. A typical HA landscape uses multiple Connection Servers with a load balancer in front of the Connection Servers. In an HA landscape, the Integration Runtime must route through the configured load balancer and to a Connection Server.

 

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
February 26, 2023

Articles:

Discussions earlier:

V
Vimal_Rawat14-AlexandriteAuthor
14-Alexandrite
February 27, 2023

Hi, I tried to go through these but none of them are clear to me. All I want to do is connect to SAP to consume data in form of OData inside Thingworx. I followed the documentation to run the Thingworx integration runtime but it wont just connect. I used the similar kind of configurations to run EMS which doesn't have this problem, so i am assuming nothing is wrong on the configuration settings.

T
TonyZhang16-Pearl
16-Pearl
March 7, 2023

Hi @Vimal_Rawat 

Could you please review the "integrationRuntime-settings.json" and make sure the ThingWorx appKey, host, and port is configured correctly? Also make sure the appKey is not expired in ThingWorx.

If still doesn't work, try setting "ignoreSSLErrors" to "true".

"Thingworx": {
    "appKey": "1234abcd-xxxx-yyyy-zzzz-5678efgh",
    "host": "localhost",
    "port": "8443",
    "basePath": "/Thingworx",
    "sslEnable": "true",
    "ignoreSSLErrors": "false"
  },

 

Then open the cmd as Administrator to run the command to ensure you have permission to access the json file and execute the jar file 

See Initial Setup of Integration Runtime Service for Integration Connectors

 

pshashipreetham
18-Opal
pshashipreetham18-Opal
18-Opal
March 30, 2023

Hi @TonyZhang,

I tried it with the root user, but it didn't work. In my case, I am not sure if it is localhost or something else. Can you help me out with how I can find on what my Thingworx is working on?

Thanks,

T
TonyZhang16-PearlAnswer
16-Pearl
March 31, 2023

Hi @pshashipreetham 

If you can access ThingWorx Composer or Mashup, you should be able find the IP in the URL address.

replace the IP with localhost in the integrationRuntime-settings.json.

Make sure you can access/ping the IP address from the server where you are running Integration Runtime.

 

If your ThingWorx is running in HA cluster mode, you will need to install and run Connection server to route the websocket communication.

The Integration Connector uses WebSockets to communicate with ThingWorx. A typical HA landscape uses multiple Connection Servers with a load balancer in front of the Connection Servers. In an HA landscape, the Integration Runtime must route through the configured load balancer and to a Connection Server.

 

    Terms & ConditionsAccessibility statement