Thingworx 8 - DSE for all data storage and HA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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?
Solved! Go to Solution.
- Labels:
-
Troubleshooting
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
DSE is not supported as a model provider, hence it's not possible to do completely without postgresql.
Some of the available documentation:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
This helps, thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Another question. Is it possible to use SQL Server as the model provider through the JDBC connection and not use PostgreSQL at all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
You may use MS SQL directly (not through the JDBC connector).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Makes sense, thank you for the reply!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
No problem! Let me know if you have any more questions :-)