cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X

Thingworx 8 - DSE for all data storage and HA

hortemt
3-Visitor

Thingworx 8 - DSE for all data storage and HA

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?

1 ACCEPTED SOLUTION

Accepted Solutions
posipova
20-Turquoise
(To:hortemt)

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.

View solution in original post

10 REPLIES 10
posipova
20-Turquoise
(To:hortemt)

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

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

posipova
20-Turquoise
(To:hortemt)

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.

This helps, thank you!

Another question. Is it possible to use SQL Server as the model provider through the JDBC connection and not use PostgreSQL at all?

posipova
20-Turquoise
(To:hortemt)

You may use MS SQL directly (not through the JDBC connector).

Is there documentation on how to do that?

In the "Getting Started with MS SQL Server and ThingWorx" guide, it has JDBC as the only option:

ThingWorx connects to the MS SQL database using a SQL JDBC driver. For more information on JDBC connection properties, refer to the following:

Setting the Connection Properties

posipova
20-Turquoise
(To:hortemt)

Yes this is the coorect guide to follow, meaning you download the MS SQL version of the Thingworx 8 platform package: http://support.ptc.com/WCMS/files/172634/en/Getting_Started_with_MS_SQL_Server_and_ThingWorx_1.pdf

By the JDBC connector I meant the option of installing a different flavor of model provider (i.e H2, postgresql) and then connecting a SQL database through the extension.

Makes sense, thank you for the reply!

posipova
20-Turquoise
(To:hortemt)

No problem! Let me know if you have any more questions :-)

Top Tags