Hi Carl,
I'm just finishing off a setting-up project for a client with the same services, but a different platform (Windows only, SQL Server).
One pitfall to look out for is the network. The keystore requires IPv4. If your network runs IPv6, you'll have to use a license file instead.
I don't have the specs on the VM, but we run the cloud and DB servers on the same host. I see no reason to split them unless you're getting into network security issues, which you shouldn't if you're all on a LAN. Remember, the cloud service is just a proxy for one or more databases -- you want to minimize that overhead.
Our original intent was to run the keystore on the same server as well, but because IPv6 turned out to be a key requirement we scrapped that. Here you might want to consider service robustness. People who use EA don't have to work in DBMS repositories, but they have to have a license. So if you co-deploy these services and the host goes down you lose both the databases and the licenses, which affects those using file-based repositories. (There's no need to separate the cloud service for this reason, since the cloud service can't do anything if the databases are unavailable.)
This organization uses a lot of EA-generated HTML, so we decided to set up a web server to serve this up due to performance issues when browsing directly over the (Windows) network file system (this is a corporate intranet spanning several countries). The setup for that is quite simple: the server exports a file share where users can place their EA-generated HTML dumps. The web server can then serve up the HTML from what to it is a local directory, giving good performance when the models are browsed.
We deployed the web server to the same host as the database and cloud servers, for cost and complexity reasons. For robustness, it should instead be deployed on a different host. The web server has no need to communicate with either the databases or the cloud service.
Finally, in case you need to manage firewalls, these are the network ports used by the EA client and services:
- Keystore service: single TCP port (default 7770) for EA client and KeystoreManager (admin).
- Cloud service: one TCP port (default 803) for SSCloudServicesClient (admin), one TCP port (default 804) for EA client.
In addition, both the cloud server and the EA client need to connect to whatever port the database server listens on (the EA client doesn't need this if you're planning to connect exclusively via the cloud service). If you implement a web server as outlined, the EA client needs to be able to access the network file system, but then it probably needs to do that anyway for MDG Technologies.
HTH,
/Uffe
