Skip to main content
hortemt1-Visitor
1-Visitor
August 31, 2017
Solved

Thingworx 8 - DSE for all data storage and HA

  • August 31, 2017
  • 10 replies
  • 4438 views

We are looking into database persistent providers for Thingworx 8, however we have been unable to find documentation or architecture diagrams for using DSE to store the model and data providers. Does anyone have experience with this? Also, can DSE be used for all data storage in a HA production environment without PostgreSQL?

Best answer by posipova

Which part is conflicting? Aplogies for misunderstanding if it happened - DSE cannot be a model provider but can be a data provider.  By default, once you isntall the psotgreql your persistence provider is postgresql and it's set for both model and data provider. Once DSE is connected, you may add a second persistence provider to set as a data provider for all or selected value streams, streams, data tables, blogs, wikis. Hope this makes sense.

10 replies

posipova20-Turquoise
20-Turquoise
September 1, 2017

DSE is not supported as a model provider, hence it's not possible to do completely without postgresql.

Some of the available documentation:

Digital Media Publisher

https://support.ptc.com/WCMS/files/166016/en/Getting_Started_with_DataStax_Enterprise_and_ThingWorx_1.pdf

hortemt1-VisitorAuthor
1-Visitor
September 1, 2017

Thank you for the response!

The "Getting Started with DataStax Enterprise and ThingWorx" document that you sent does not explicitly mention that.

In addition, there is other documentation that is conflicting to your statement:

In ThingWorx, value streams, streams, data tables, blogs, and wikis are data providers. Data providers are databases that store run time data. Run time data is data that is persisted once things are composed and used by connected devices to store their data (such as temperature, humidity, or position). Model providers are used to store the metadata for the things. Persistence providers are initially set to have one database for both model providers and data providers, but administrators can separate them based on requirements.

Link:

PTC

posipova20-TurquoiseAnswer
20-Turquoise
September 1, 2017

Which part is conflicting? Aplogies for misunderstanding if it happened - DSE cannot be a model provider but can be a data provider.  By default, once you isntall the psotgreql your persistence provider is postgresql and it's set for both model and data provider. Once DSE is connected, you may add a second persistence provider to set as a data provider for all or selected value streams, streams, data tables, blogs, wikis. Hope this makes sense.

Terms & ConditionsAccessibility statement