Profile augmentation depends on the type of profile, whether you changed the configuration information, 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. Use these rules and limitations to ensure a properly functioning feature-pack environment.
To use the functionality provided in the Feature Pack for CEA, you must either augment existing profiles or create new profiles enabled with feature-pack functionality. Profile creation and augmentation are done using the customization jobs and the associated instructions created by the Profile Management Tool.
You can have a mix of augmented and unaugmented profiles that share a single WebSphere Application Server installation. Feature-pack functionality is available only within profiles that have been augmented.
Profile | Supported | Not supported |
---|---|---|
Standalone application server | Augmentation of an existing standalone application server if the standalone application server is lower than Version 7.0 | |
Deployment manager | Augmentation of an existing deployment manager if the deployment manager is lower than Version 7.0 | |
Managed (custom) node | Augmentation of an existing managed (custom) node if the node is lower than Version 7.0 | |
Network Deployment cell | Important: To enable feature-pack functionality in
a federated application server, you must augment the cell's deployment
manager profile as well as the federated application server profile
with the feature pack.
|
![]() When you federate a WebSphere Application Server Version 7.0.0.9 standalone server into a working WebSphere Application Server Version 7.0.0.9 cell that is enabled with the Feature Pack for CEA Version 1.0.0.3 and afterwards try to augment the new node with the Feature Pack for CEA Version 1.0.0.3, a 500 Java error prevents you from enabling feature-pack functionality. Follow
the recommended steps for adding a new node that is enabled with the
Feature Pack for CEA Version 1.0.0.3 to a WebSphere Application Server
Version 7.0.0.9 cell that is enabled with the Feature Pack for CEA
Version 1.0.0.3.
|
Administrative agent | ![]() ![]() |
Augmentation of an existing management profile with an administrative agent if the profile is lower than Version 7.0 |
Job manager | Creation or augmentation of a job manager
to enable it for a feature pack However, you can use a job manager in a feature-pack environment. |
|
Secure proxy server | Creation or augmentation of a secure proxy
server to enable it for a feature pack However, you can use a secure proxy server in a feature-pack environment. |
|
Secure proxy administrative agent | Creation or augmentation of a secure proxy
administrative agent to enable it for a feature pack However, you can use a secure proxy administrative agent in a feature-pack environment. |
Function | Rules |
---|---|
Addition of a node | |
Application installation | |
Server configuration template use | |
Cluster management | |
Configuration-archive export and import | If a configuration contains feature-pack capabilities, exporting a configuration to a configuration archive and importing a configuration from a configuration archive are not supported. If you run one of the import or export commands of the ConfigArchiveOperations command group against one of these configurations, the command might complete without reporting an error. No message is displayed when importing or exporting; however, no confirmation exists for imported configuration success. |
You cannot unaugment profiles that have been enabled with feature-pack functionality in WebSphere Application Server for z/OS Version 7.0.