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.
Avoid trouble: When you create
the application server profile, a default server1 process is created.
If you delete the server1 process, the profile becomes a custom profile
and is governed by the rules for a custom profile.
gotcha
Table 1. Rules for profile augmentation
Profiles |
Supported |
Not supported |
Application server |
|
|
Deployment manager |
- User-initiated augmentation of a Network Deployment deployment
manager profile. This action is supported as long as the version of
all the federated nodes in the cell is Version 6.1 or higher.
The
Network Deployment deployment manager profile configuration might
have changed.
The Network Deployment deployment manager profile
might have been created before or after you applied the feature pack.
newfeatCreation of a new
deployment manager profile that is enabled for the Feature Pack for Web Services.You must install the Feature Pack for Web Services onto the Network
Deployment product first. When you create the deployment manager profile
for the Feature Pack for Web Services, the Feature Pack for Web Services automatically augments
the profile with Feature Pack for Web Services capabilities.
|
- Augmentation of a Network Deployment deployment manager profile
for a feature pack is not supported if the version of a federated
node in the cell is lower than Version 6.1.
|
Custom |
If you are running on Version 6.1.0.21 or later,
creation of a custom profile enabled for Feature
Pack for Web Services. You must install the Feature Pack for Web Services onto the Network Deployment product
first. When you create the custom profile for the Feature Pack for Web Services, the Feature
Pack for Web Services automatically augments the profile with Feature Pack for Web Services capabilities.
|
- Creation of a custom profile enabled for a feature pack, unless
you are running on Version 6.1.0.21 or later
- Augmentation of a Network Deployment custom profile
Note: The Feature Pack for Enterprise JavaBeans 3.0 does not
support the creation and augmentation of custom profiles.
|
Cell |
|
|
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.
|