Most enterprise-scale “production-use topologies” will likely place the major components of each domain on a separate servers, yielding a federation of communicating distributed applications.
For example, the PLM domain might be deployed to one 64G 8-Core 64-bit x86 workstation with Terabyte disks running RedHat or CentOS Linux for just the Windchill application and its Apache Httpd web application server. A second similar server with a redundant array of disks would host the Oracle SQL server for Windchill content.
The Jazz ALM suite, consisting of JTS, CCM, RM, GC, DM, QM, LQE, LDX, RELM, and JRS might be deployed to 8 or 9 separate 64G 4-Core x86 workstations with Terabyte disks such that each application runs on its own dedicated CPUs and disks. A separate 64G 8-Core 64-bit x86 workstation with a redundant array of disks would host the IBM DB2 database for all Jazz content.
As of 2018, it is most likely that all this compute capability would be virtualized on scalable, elastic Infrastructure as a Service.
Finally, separate 64G 4-Core 64-bit x86 Windows or Linux servers might be allocated to run Tomcat to host the multiple RLIA Adapters that are responsible for subsets of the organizations ALM and PLM project areas. (For not every ALM ProjectArea must relate with every PLM Product container.)
Figure: Possible Production-use Deployment Topology
With this flexible, scalable topology, a large enterprise should be able to exploit the realization of an ALM / PLM integration and experience improved business workflow with practical, representative content in each of the repositories and with daily sustained use by a global workforce.
Capabilities that must be offered by each of the chosen application servers (for Jazz, Windchill, and the Adapter) are stated in Web/Application Servers' Required Capabilities. Briefly, the chosen web application server has to be running JDK 8 and has to offer modern security features. Review the requirements for the exact capabilities needed.