Rules and limitations apply to augmentation and unaugmentation
of deployment manager, application server, custom, and cell profiles, and
to interactions between nodes or nodes and the deployment manager. Use these
rules and limitations to ensure a properly functioning feature pack environment.
Augmentation rules and limitations
- The latest feature pack that you apply might require augmentation of the
Network Deployment profiles or the profile of a prerequisite feature pack.
If so, you can have a mix of augmented and unaugmented profiles. However,
you must have at least one profile augmented for this latest feature pack
to use its capabilities.
- For multiple feature packs, you must first install all the feature packs,
augment the profile for each of the feature packs, and then make configuration
changes for those feature packs. The order of installing or augmenting the
feature packs does not matter, unless a particular feature pack requires you
to install another feature pack first. You can only make configuration changes
after you augment the profile.
newfeatIf you have multiple feature
packs installed, then uninstalling one feature pack unaugments the deployment
manager profile for that feature pack. The other feature packs remain usable
for the deployment manager profile.
The following table provides additional augmentation rules for a particular
type of profile.
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, unless you are running
on Version 6.1.0.21 or later
|
Cell |
|
|
Unaugmentation rules and limitations
newfeatExcept for the deployment manager profile, unaugmentation
of feature pack profiles by users is unsupported. If a deployment manager
profile is augmented, then both the feature pack uninstaller program and the
delete profile action invoke unaugmentation actions for that profile before
invoking the uninstall action or the delete action, respectively.
Whenever
unaugmentation of a feature pack profile occurs, a message is generated indicating
that the applications in the profile are expected to fail.
When a deployment manager profile is unaugmented for a feature pack,
other profiles augmented with the same feature pack in the cell fail.
The
following table describes what action to take for each type of feature pack
profile as an alternative to unaugmenation.
Table 2. Alternative to unaugmenting
profiles
Profile |
Alternatives to Unaugmentation |
Application server |
- Application server that has not been federated: Use the manageprofiles command
to delete the profile.
- Federated application server: Unfederate the node, and use the manageprofiles command
to delete the profile. Otherwise, an orphan node is left in the deployment
manager.
|
Deployment manager |
Do one of the following actions:
- Remove all federated nodes from the deployment manager. Then, use the manageprofiles command
to delete the deployment manager profile. Otherwise, all federated nodes become
orphans. However, existing applications continue to run successfully.
- Run the uninstaller program to uninstall a feature pack from the deployment
manager. The uninstaller program unaugments the deployment manager profile.
|
Custom |
- No alternative exists, since augmentation of custom profiles is not supported.
|
Cell |
- No alternative exists, since augmentation of cell profiles is not supported.
|
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 3. 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 can target an application that does not require feature pack functionality
to an application server on a node with or without feature pack augmentation.
- 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.
|
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.
|
Cluster management |
- When you add a new member to a cluster, the new member must be able to
run all the applications that have been targeted for the cluster.
- If an application targeted for the cluster requires a specific feature
pack, you must add the new member from a node that is enabled with that feature
pack. Otherwise, an error occurs.
- If no application on the cluster requires a specific feature pack, then
you can add the new member to the cluster from a node with a feature pack
or a node without a feature pack.
|
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. The export or import might succeed
in one case and fail in another case. If you run one of the export or import
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, do not expect
the imported configuration to function correctly.
|