For some PerfectChef features CoreMedia makes use of the Apache HTTP server (see Section 5.4, “Connecting with an IBM WCS Shop” for details) , especially rewrite rules and handling of HTTPS requests (which is why Login does not work with a standalone Tomcat). The triangular communication between CAE, WCS and the client raises some more low level technical constraints concerning the cookie domain and cross domain Ajax requests. Without going into detail here, the easiest way to solve all such problems flexibly during development is to hide the CAE and the WCS behind a common Apache proxy. Moreover, according to the production setup you should test your development with Apache anyway to make sure that your features work correctly. Since Apache configuration is a tedious task, CoreMedia provides a virtual machine with a preconfigured Apache server, which you can easily use and maintain.
Since CAE and WCS invoke each other mutually, there must be a 1:1 relationship between them, otherwise some LiveContext features will not work correctly. This means you would need two WCS instances for your Preview and Live CAE. However, a WCS instance needs quite some resources, and for most development use cases it is feasible to dispense a fully featured system and work with a shared WCS instance for the Preview and the Live CAE. Therefore, this setup refers to a single WCS instance.
 |  |  |
 |