Skip to main content
P
18-Opal
pshashipreetham18-Opal
18-Opal
October 25, 2023
Solved

Single DB for Two Thingworx Instances

  • October 25, 2023
  • 2 replies
  • 3228 views

Hi,

 

I look forward to doing a minimal Connection Server installation due to high traffic to the Thingworx Platform.

 

Present Scenario: 1 Thingworx Instance with 1 Postgres DB & 1 Influx DB

Required Scenario: 1 Connection Server with 2 Thingworx Platforms with 1 Postgres DB & 1 Influx DB

 

Can the required Scenario be achievable with 1 Postgres DB and 1 Influx DB for both Thingworx Instances? and is it a best practise?

 

Thanks,

 

 

Best answer by pshashipreetham

With the help of @Jimwang and after lots of documentation searches on the PTC Knowledge base, concluded below.

pshashipreetham_0-1699100313022.png

 

2 replies

J
Jimwang16-Pearl
16-Pearl
October 25, 2023

Technically you can use one Postgresql for multiple Thingworx instances as long as the Thingworx instances are using different Database/schema. For example, your postgresql instance has two Databases dB1 and dB2, each Thingworx instance connects to its own database dB1 and dB2 respectively.

However, this is not a good best practices, especially for production system, for example, if you need to restart the postgresql, all the Thingworx instances are impacted.

 

    P
    18-Opal
    pshashipreetham18-OpalAuthor
    18-Opal
    October 25, 2023

    hi @Jimwang ,

     

    Thanks for the quick response. Do we also need the Zoo keeper if we are using the Connection Server?

     

    Thanks,

    J
    Jimwang16-Pearl
    16-Pearl
    October 26, 2023

    If your Thingworx Platforms are configured as High Availability Cluster, yes, it is required to install Zookeeper, otherwise, you don't need to use zookeeper

      P
      18-Opal
      pshashipreetham18-OpalAuthorAnswer
      18-Opal
      November 4, 2023

      With the help of @Jimwang and after lots of documentation searches on the PTC Knowledge base, concluded below.

      pshashipreetham_0-1699100313022.png

       

        Terms & ConditionsCookie settingsAccessibility statement