WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Application placement custom properties

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.

cpuUtilizationThreshold [Version 6.0.1 and later]

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.

[For z/OS operating system] Important: This property must be defined and must be set to a value less than 100 for configurations that involve z/OS nodes.
You can set this property on the cell to apply to all the nodes in the cell or you can specify the value for a particular node in your configuration. To define the property to specify the threshold for all nodes in the cell, perform the following steps:
  1. In the administrative console, click Operational policies > Autonomic Managers > Application Placement Controller > Custom Properties > New.
  2. Type the name of the custom property as cpuUtilizationThreshold.
  3. Specify the percentage of processor power to use on each node in the cell.
  4. Click Apply and save your configuration.
GenerateUniquePorts [Version 6.0.1 and later]

You can use the GenerateUniquePorts custom property to generate unique ports for each dynamic cluster member.

[For z/OS operating system] By default, dynamic cluster members on distributed nodes are created with unique ports, while z/OS nodes do not have unique ports. On the z/OS platform, port numbers are usually set symmetrically according to specific range of numbers. The first dynamic cluster member always has unique ports, and these port numbers are applied to the other dynamic cluster members. You can set this property on the node group or on an individual node.
  • Setting the custom property on the node group:
    1. In the administrative console, click System administration > Node groups > node_group_name > Custom Properties > New .
    2. Type GenerateUniquePorts as the name of the custom property.
    3. Specify the value as true or false. By specifying true, unique ports are generated for each dynamic cluster member. By specifying false, unique ports are created for the first dynamic cluster member, and subsequent dynamic cluster members use the same ports.
  • Setting the custom property on a node:
    1. In the administrative console, click System administration > Node groups > node_group_name > Custom Properties > New .
    2. Type GenerateUniquePorts.node_name as the name of the custom property, where the node_name variable is the name of the node in the node group.
    3. Specify the value as true or false. By specifying true, unique ports are generated for each dynamic cluster member on the specified node. By specifying false, unique ports are created for the first dynamic cluster member on the node, and subsequent dynamic cluster members use the same ports.
Table 1. GenerateUniquePorts custom property default values
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
memoryProfiler.isDisabled

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.

Perform the following steps to disable the memory profiler:
  1. In the administrative console, click Operational policies > Autonomic Managers > Application Placement Controller > Custom Properties > New.
  2. Type the name as memoryProfiler.isDisabled and set the value to true.
  3. Click Apply and save your configuration.
OverlappingCells [Version 6.0.2 only]

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.

Enter the custom property value in the following format:
user_name:password@deployment_manager_host:port.SOAP 
If you are connecting three or more cells, separate the custom property values for each cell with a comma.
  • user_name: Specifies the name of the user that can log into the other cell.
  • password: Specifies the password for that user. You can encode the password so that it does not display in plain text in the administrative console. To encode a password, use the encodePassword script.
  • deployment_manager_host: Specifies the name of the deployment manager host for the other cell.
  • port: Specifies the SOAP port that is associated with the deployment manager, for example, the SOAP_CONNECTOR_ADDRESS port.
reservedMemoryFixed and reservedMemoryPercent [Version 6.0.1 and later]

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.

When these properties are defined, the total memory on a node for processes that are not related to WebSphere Application Server or WebSphere Extended Deployment can be calculated using the following formula:
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%
You can define these custom properties across the entire cell to apply to all nodes in the cell, or on individual nodes. To define these custom properties for all nodes in the cell, perform the following steps:
  1. In the administrative console, click Operational policies > Autonomic Managers > Application Placement Controller > Custom Properties > New.
  2. Type the name of the custom property, either reservedMemoryFixed or reservedMemoryPercent.
  3. Specify the reserved memory value to apply to all nodes in the cell.
  4. Click Apply and save your configuration.
To define the custom properties for a particular node in your cell, perform the following steps:
  1. In the administrative console, click Operational policies > Autonomic Managers > Application Placement Controller > Custom Properties > New.
  2. 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.
  3. Specify the reserved memory value to apply for the specified node.
  4. Click Apply and save your configuration.
useNodeFreeMemory

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.

To define the custom property for a particular node in your cell, perform the following steps:
  1. In the administrative console, click Operational policies > Autonomic Managers > Application Placement Controller > Custom Properties > New.
  2. Type the name of the custom property as: useNodeFreeMemory.
  3. Specify true as the value to apply to all nodes in the cell.
  4. Click Apply and save your configuration.



Related tasks
Creating dynamic clusters
Configuring dynamic application placement
Related information
Dynamic cluster custom properties
Reference topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:14:15 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/reference/rodplacecustprop.html