Rules and limitations apply to augmentation and unaugmentation of profiles. Use these rules and limitations to ensure a properly functioning feature-pack environment.
You can determine the template that was used for creating the profile by viewing the profile registry in the profileRegistry.xml file. By default, this file is located in the following directory:
app_server_root/properties/
app_server_root\properties\
Profiles | 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 management profile with a deployment manager if the profile 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 or feature functionality
in a federated application server, you must augment the cell's
deployment manager as well as the federated application server with
the feature pack or feature.
|
Augmentation of an existing Network Deployment
cell if the cell is lower than Version 7.0![]() 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 | Note: Currently, this
profile has no requirements for feature-pack capability; however,
if you augment an application server with the feature pack that is
registered with an administrative agent, you also must augment its
administrative agent with the feature pack.
|
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
the feature pack However, you can use a job manager in the feature-pack environment. |
|
Secure proxy | Creation or augmentation of a secure proxy server to enable
it for the feature pack However, you can use a secure proxy server in the feature-pack environment. |
|
Secure proxy administrative agent | Creation or augmentation of a secure proxy administrative
agent to enable it for the feature pack However, you can use a secure proxy administrative agent in the feature-pack environment. |
When you perform tasks between nodes, or between nodes and the deployment manager, the feature packs must be compatible.
Function | Rules |
---|---|
Addition of a node | |
Application installation | |
Server configuration template | |
Cluster management | |
Configuration archive export and import |