Skip to main content
D
Do11-Visitor
1-Visitor
September 9, 2019
Solved

Edge device data replicator for Dev & Test

  • September 9, 2019
  • 2 replies
  • 1161 views

When you are do dev work and when testing, you obviously need to do this in the context of data from devices in the field streaming in...

 

It is not practical to have a set of "test or dev" devices as this would provide neither a realistic breadth of data nor the volume of data against which to dev or test.

 

I have been wondering how people work with this problem.

 

This got me to thinking, could one use something like the connection server and then split your updates to two ThingWorx instances?

 

Any other ideas on how to handle this?

Best answer by slangley

Hi @Do1.

 

For testing ingestion, many customers use simulators for generating the needed volume.  It would be expected that load testing would occur in Test while QA would be used for validating functionality.  In regard to splitting messages from one connection server to 2 different ThingWorx instances, this is not a supported scenario.

 

Please let us know if you have further questions.

 

Regards.

 

--Sharon

 

 

2 replies

S
slangleyCommunity ManagerAnswer
Support
September 10, 2019

Hi @Do1.

 

For testing ingestion, many customers use simulators for generating the needed volume.  It would be expected that load testing would occur in Test while QA would be used for validating functionality.  In regard to splitting messages from one connection server to 2 different ThingWorx instances, this is not a supported scenario.

 

Please let us know if you have further questions.

 

Regards.

 

--Sharon

 

 

S
slangleyCommunity Manager
Support
September 24, 2019

Hi @Do1.

 

If the previous response answered your question, please mark it as the Accepted Solution for the benefit of others on the community.

 

Regards.

 

--Sharon

Terms & ConditionsAccessibility statement