Custom properties modify the application placement controller configuration. You can use these settings to tune the application placement controller behavior beyond the settings that are in the administrative console.
You can use the cpuUtilizationThreshold custom property to define the percentage of processor power that you can use on each node in a cell.
The cpuUtilizationThreshold custom property defines the percentage of processor power that is used on the nodes in your environment. The default value is 100, which means that 100% of the processor can be used on each node in the cell. For configurations that involve z/OS® nodes, you must set this value to less than 100.
The application placement controller attempts to compute placements so that the utilization of any node does not exceed the defined threshold. The application placement controller considers all processes, including processes that are not related to WebSphere® Application Server or WebSphere Extended Deployment when making these calculations.
You can use the GenerateUniquePorts custom property to generate unique ports for each dynamic cluster member.
default (z/OS) | false Attention: If vertical stacking
is enabled for a z/OS dynamic cluster, the port allocation strategy
is forced to true, to generate unique ports for each dynamic cluster
member.
|
default (distributed platforms) | true |
You can use the memoryProfile.isDisabled custom property to disable the memory profiler.
Under the default operation, the application placement controller profiles dynamic clusters online to determine their memory usage. You can disable this default operation by setting the memoryProfiler.isDisabled custom property to true. When the memory profiler is disabled, the application placement controller assumes a default memory usage value. This memory usage value is computed as 64k + 1.2 maxHeapSize, where maxHeapSize is the maximum heap size setting in the server template of the dynamic cluster.
You can use the OverlappingCells custom property when two WebSphere Extended Deployment cells share the same physical host. Configuring this property ensures that the application placement controller does not overuse resources on the shared host.
See Configuring application placement for cells that share the same nodes for more information about how to set this custom property.
user_name:password@deployment_manager_host:port.SOAPIf you are connecting three or more cells, separate the custom property values for each cell with a comma.
You can use these custom properties to define how much memory on each node to reserve for processes that are not related to WebSphere Application Server or WebSphere Extended Deployment.
reservedMemoryFixed + reservedMemoryPercent * (totalNodeMemory - reservedMemoryFixed)
Property name | Definition | Default |
---|---|---|
reservedMemoryFixed | A fixed amount of memory to reserve. | 64 MB |
reservedMemoryPercent | A percentage of memory to reserve. | 5% |
Use this custom property to define a replacement to the reservedMemory default custom property. This custom property uses the node free memory statistic, plus the memory calculated for any dynamic cluster instances that are already on the node, to calculate the memory available for launching additional dynamic cluster instances.