Skip to main content
Sep 24, 2025 8:49 AM UTC
Solved

Codebeamer + Thingworx Platform and Flow Install

 

Is it ok to install Thingworx Platform and Flow on the same VM as Codebeamer and postgreSQL or should they be on a separate server? This is for Windchill-codebeamer integration.

 

1758206569712.jpg

Oct 18, 2025 12:08 PM UTC

Hi @rhart ,


Codebeamer and ThingWorx are both resource-intensive Java applications, each running its own Tomcat service and handling large heap memory operations. PostgreSQL also needs consistent disk I/O and memory access. Running all three on one VM leads to contention, slow response times, and instability.

 

Recommended setup:

  • VM 1: Codebeamer application

  • VM 2: PostgreSQL database

  • VM 3: ThingWorx Platform and Flow

They can communicate over HTTPS without issue.


For testing or small demos, you can host them on a single VM if you allocate high resources (≥ 16 CPU, 64 GB RAM), but for Windchill-Codebeamer integration in production, always separate them.

 

Thanks,

2 replies

Community Manager
Sep 30, 2025 1:45 PM UTC

Hi @rhart 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant.

 

Best regards,

Oct 18, 2025 12:08 PM UTC

Hi @rhart ,


Codebeamer and ThingWorx are both resource-intensive Java applications, each running its own Tomcat service and handling large heap memory operations. PostgreSQL also needs consistent disk I/O and memory access. Running all three on one VM leads to contention, slow response times, and instability.

 

Recommended setup:

  • VM 1: Codebeamer application

  • VM 2: PostgreSQL database

  • VM 3: ThingWorx Platform and Flow

They can communicate over HTTPS without issue.


For testing or small demos, you can host them on a single VM if you allocate high resources (≥ 16 CPU, 64 GB RAM), but for Windchill-Codebeamer integration in production, always separate them.

 

Thanks,