Automation support
As discussed, several changes would facilitate automatic WLM operation, as described here.
Changes to startServer.sh
WebSphere appservers have a unique server name within a domain or cell. The generic WebSphere architecture specifies that an LPAR is in only one domain or cell, so the server name is a unique identifier within the LPAR. You could modify startServer.sh script to issue the wlmassign command to set the Java process WLM class and subclass.
Extensions
As described in 2.1.2, Workload management, WLM configurations are specified in terms of relative resource shares, not absolute values. A script could convert from absolute units such as percentage processor use and Mb of memory to shares.
Failover configurations
As described, fallback operation may require changes to the WLM configuration, when workload is transferred to a single LPAR. This could be handled by generating multiple WLM configurations using WARM, or a separate script to reconfigure WLM for a specific fallback situation.