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 apc.log.enablePlacementLog custom property to enable or disable logs from being saved to the apc.log log file. The apc.log log file contains information about placement decisions. IBM support can use this log file to help understand the placement decisions that are being made by the application placement controller.
Scope | Application placement controller |
---|---|
Valid values | No value: The placement log is enabled. false: The placement log is disabled. |
You can use the apc.log.LogFileSize custom property to set the size of the application placement controller log file, the apc.log file, to a size in megabytes. The default size is 20 megabytes, but you can change the default value.
Scope | Application placement controller |
---|---|
Valid values | An integer value of the number of megabytes for the log file. For example, if you enter 100, the log file would be 100 megabytes. |
You can use the apc.log.numHistoricalFiles custom property to set the number of log files that are saved for the application placement controller. When the application placement controller log file reaches its maximum size, the historical file is saved if this value is greater than 1. If the value is equal to 1, the historical data appends to the existing file.
Scope | Application placement controller |
---|---|
Valid values | An integer value that specifies the number of historical files you want to save, for example, 2. |
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 Virtual Enterprise when making these calculations.
Scope | Application placement controller: applies to all nodes in the cell. Node: applies to a specific node. |
---|---|
Valid values | An integer value that specifies the percentage of processor power to use on each node in the cell. |
You can use the GenerateUniquePorts custom property to generate unique ports for each dynamic cluster member.
Scope | Node group, node |
---|---|
Valid values | true: Unique ports are generated for each dynamic cluster member. false: Unique ports are created for the first dynamic cluster member, and subsequent dynamic cluster members use the same ports. |
Default | z/OS platforms: 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.
Distributed platforms: true |
You can use the maintenanceModeOnOperationFail custom property to move a server into maintenance mode when the server start fails. The default value is false, which, instead of placing the server into maintenance mode when a server start fails, generates a runtime task. This runtime task contains a notification that the application placement controller did not receive notification about the completion of the server start.
Scope | Application placement controller |
---|---|
Valid values | true: Places the server into maintenance mode when the server start fails. false: Generates a runtime task when a server start fails. |
Default | false |
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.
Scope | Application placement controller |
---|---|
Valid values | true: Disables the memory profiler. false: Enables the memory profiler. |
Default | false |
You can use the OverlappingCells custom property when two WebSphere Virtual Enterprise 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.
Scope | Application placement controller |
---|---|
Valid values | Enter the custom property value in the following
format:
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 Virtual Enterprise.
reservedMemoryFixed + reservedMemoryPercent * (totalNodeMemory - reservedMemoryFixed)The reservedMemoryFixed custom property specifies a fixed amount of memory to reserve. The reservedMemoryPercent custom property specifies a percentage of memory to reserve.
Scope | Application placement controller |
---|---|
Valid values | To set the value for the entire cell: Type the name of the custom property as reservedMemoryFixed or reservedMemoryPercent. To set the value for a particular node: Type the name of the custom property, either reservedMemoryFixed.node_name or reservedMemoryPercent.node_name, where node_name is the name of your node. For example, if your node is named node1, the names of your custom properties are reservedMemoryFixed.node1 and reservedMemoryPercent.node1. |
Default | reservedMemoryFixed: 64 MB reservedMemoryPercent: 5% |
Use this custom property to take a server out of maintenance mode after the server starts. If the maintenanceModeOnOperationFail custom property is enabled, the server is placed into maintenance mode after the server start fails. When the server starts successfully, you can use this property to move the started server out of maintenance mode automatically.
Scope | Application placement controller |
---|---|
Valid values | true: Moves the started server out of maintenance mode automatically. false: Leaves the server in maintenance mode after it is started. |
Default | false |
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.
Scope | Application placement controller |
---|---|
Valid values | true: Automatically calculates available memory. false: Use reservedMemory default custom properties to define available memory. |