Dynamic application environments (DAE) are supported with OW54622 on z/OS V1.2 or higher. Middleware that supports DAEs can be configured with less effort and less errorprone due to the avoidance of duplicate definitions in the middleware and WLM. In contrast to normal application environments, DAEs are managed on the scope of a single system only.

WebSphere Application Server V5 is the first middleware to exploit DAEs. If you are running z/OS 1.2 or higher, you may choose to use dynamic application environments. In this case, use the WebSphere administrative console to turn on the dynamic application environment and to provide the JCL procedure name for the servant and the JCL Parm for the servant.

With DAE WebSphere multinode capabilities are also supported. For each dynamic application environment, a node name refers to the daemon group name (or short cell) that is used to associate all the WAS spaces that are in the same cell. The node name can be used in the enhanced operating commands to VARY or DISPLAY dynamic application environments. Other filter options permitted for the vary and display commands are subsystem type and subsystem name.

To protect DAEs, resource profiles according to the following pattern have to be created and access granted for them:

• subsystem_type.subsystem_name.application_environment_name.node_name

Note: The maximum length of this profile name must not exceed 44 characters.