WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

             Personalize the table of contents and search results
             New or updated topic for this feature pack

z/OS augmentation rules and limitations for feature packs

Augmenting a profile depends on whether you changed the configuration information, the type of profile, and so on. You must have the correct combination of feature packs in order to add a node, manage clusters, install applications, and manage server templates.

Augmentation rules and limitations

The following table provides additional augmentation rules.

Table 1. Rules for profile augmentation
Profiles Supported
Application server
  • Creation of a new application server that is enabled for the Feature Pack for Web Services

    You must install the Feature Pack for Web Services prior to creating the new application server. Use the Profile Management tool for z/OS to generate the required customization jobs and the associated instructions.

Deployment manager
  • Augmentation of an existing deployment manager for Feature Pack for Web Services. This action is supported as long as the version of all the federated nodes in the cell is Version 6.1 or higher.

    The deployment manager profile might have had configuration changes made to it.

    You must install the Feature Pack for Web Services prior to augmenting the existing deployment manager. Use the Profile Management tool for z/OS to generate the required customization jobs and the associated instructions.

  • Creation of a new deployment manager that is enabled for the Feature Pack for Web Services

    You must install the Feature Pack for Web Services prior to creating the new deployment manager. Use the Profile Management tool for z/OS to generate the required customization jobs and the associated instructions.

Unaugmentation rules and limitations

Unaugmentation of feature pack profiles is unsupported on WebSphere Application Server for z/OS.

It is important to backup your configuration filesystem before augmenting.

Augmentation rules and limitations for a mixed-cell environment

When you perform tasks between nodes, or between nodes and the deployment manager, the feature packs must be compatible.

Table 2. Augmentation in a mixed-cell environment
Function Rules
Addition of a node
  • You can add a node to a cell as long as the deployment manager has been augmented with at least the same set of feature packs as the node. The deployment manager might have been augmented with additional feature packs.
  • You can add a node with no feature pack profile to a cell, even though the deployment manager is augmented with some feature packs. However, the node that you add must be at Version 6.1 or higher.
  • You cannot add a node with a particular feature pack profile to a cell, if the deployment manager has not been augmented with that feature pack.
Application installation
  • You can target an application that requires feature pack functionality to an application server on a node that has been augmented with feature packs that contain that functionality.
  • You cannot target an application that requires feature pack functionality to an application server on a node that has not been augmented with that feature pack functionality.
  • You can target an application that does not require feature pack functionality to an application server on a node with or without feature pack augmentation.
Server configuration template
  • You can use the server configuration template to create a server on another node that is augmented with the same feature pack.
  • If you attempt to use a server configuration template to create a server on another node that is augmented with a different feature pack, then the operation fails. The scenario is not supported.
Configuration archive export and import
  • If a configuration contains feature pack capabilities, then exporting a configuration to a configuration archive and importing a configuration from a configuration archive are unsupported. If you run one of the import or export commands of the ConfigArchiveOperations command group against one of these configurations, then the command might complete without reporting an error. No message is displayed when importing or exporting. However, no confirmation exists for imported configuration success.
Reference topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/rins_wsfeplimit_zos.html