[AIX HP-UX Linux Solaris Windows]This topic applies only on the IBM i operating system.

Augmentation rules and limitations for feature packs on non-z/OS operating systems

Rules and limitations apply to augmentation and unaugmentation of profiles. Use these rules and limitations to ensure a properly functioning feature-pack environment.

Augmentation rules and limitations

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:

[Linux] [HP-UX] [Solaris] [AIX]
app_server_root/properties/
[Windows]
app_server_root\properties\
Avoid trouble 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.

This table lists the augmentation rules and limitations for feature packs on non-z/OS operating systems.

Profiles Supported Not supported
Standalone application server
  • Creation of a new Version 7.0 application server profile that is enabled for the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0

    You must install the feature pack onto the product first. When you create the application server profile for the feature, the feature pack automatically augments the profile with feature capabilities.

  • Augmentation of an existing Version 7.0 application server profile

    The application server profile might have had configuration changes made to it.

    The application server profile might have been created before or after you applied the feature pack.

Augmentation of an existing standalone application server if the standalone application server is lower than Version 7.0
Deployment manager
  • Creation of a new Version 7.0 management profile with a deployment manager that is enabled for the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0

    You must install the feature pack onto the product first. When you create the management profile with a deployment manager for the feature, the feature pack automatically augments the profile with feature capabilities.

  • Augmentation of an existing Version 7.0 management profile with a deployment manager

    The configuration of the management profile with a deployment manager might have changed.

    The management profile with a deployment manager might have been created before or after you applied the feature pack.

Augmentation of an existing management profile with a deployment manager if the profile is lower than Version 7.0
Managed (custom) node
  • Creation of a new Version 7.0 managed (custom) profile that is enabled for the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0

    You must install the feature pack onto the product first. When you create the managed (custom) profile for the feature, the feature pack automatically augments the profile with feature capabilities.

  • Augmentation of an existing Version 7.0 managed (custom) profile

    The configuration of the managed (custom) profile might have changed.

    The managed (custom) profile might have been created before or after you applied the feature pack.

Augmentation of an existing managed (custom) node if the node is lower than Version 7.0
Network Deployment cell
  • Creation of a new Version 7.0 cell profile that is enabled for the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0

    You must install the feature pack onto the Network Deployment product first. When you create the deployment manager profile and the federated application server profile for the feature, the feature pack automatically augments the profile with feature capabilities.

  • Augmentation of an existing Version 7.0 cell profile with the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0
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
Administrative agent
  • Creation of a new Version 7.0 management profile with an administrative agent that is enabled for the OSGi Applications or Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0

    You must install the feature pack onto the product first. When you create the management profile for the feature, the feature pack automatically augments the profile with feature capabilities.

  • Augmentation of an existing Version 7.0 management profile with an administrative agent to enable it for the OSGi Applications or Java Persistence API 2.0 feature.
Note: If you augment an application server with a feature that is registered with an administrative agent, you also must augment its administrative agent with the feature.
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.

Unaugmentation rules and limitations

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.

This table lists the augmentation rules and limitations for 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.
  • 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, 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, 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, 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.



Related tasks
Managing profiles on non-z/OS operating systems
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 12, 2013 3:32:32 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=rpro_augment
File name: rpro_augment.html