Virtual Enterprise now checks for the deployment manager's memory usage.

Traditionally, virtual enterprise would not account for the deployment manager's memory usage since the best practice recommendation was to host the deployment manager on a separate node. Hence, dynamic cluster instances would not be candidates to run on that node. However, with the advent of support for hardware virtualization platforms like VMware in 6.1.0.3, it is quite possible that the deployment manager may reside on the same physical machine (but in a separate virtual machine) as dynamic cluster instances, and hence, their memory needs to be accounted for when dealing with memory overload protection.

Keep this in mind, especially during POC or POT engagements when hardware resources are limited, that the default memory protection (designed to prevent paging) may engage with 6.1.0.3 when it did not engage in previous releases if the deployment manager was co-located on machines with app servers. Changes to the overload protection customer properties, or the node.memory custom property, can be used to increase the memory the placement controller will allocate to a node (at the sacrifice of paging) to get DC instances started when in automatic mode in these constrained environments.