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

Unaugmenting a profile using the command prompt

You must unaugment or delete your profiles from your environment to remove feature-pack functionality. Use the manageprofiles command to unaugment existing profiles in a feature-pack environment.

Before you begin

Install the feature pack on top of an existing WebSphere® Application Server, Network Deployment installation. Reference the installation topics in the information center for additional information about installing the feature pack in your environment.

Remove all installed applications that require feature-pack functions that are located in the profile being unaugmented. If you unaugment profiles without removing the applications, the applications might not be usable.

About this task

There are two ways to unaugment profiles that are using a feature-pack environment:
  • Uninstall the feature pack from your environment. The augmented profiles are automatically unaugmented before the uninstallation begins.
  • Use the -unaugment parameter with the manageprofiles command-line tool to unaugment a profile.
Important: Profiles augmented by a feature pack or feature must be unaugmented or deleted before the feature pack or feature is uninstalled. Profiles that are unaugmented should be deleted because they might not be valid after the feature pack or feature is uninstalled.
Complete this task to unaugment specific profiles that are augmented for the feature-pack environment using the manageprofiles command-line tool.

The following example unaugments an application server profile that was previously augmented for the feature pack.

Procedure

  1. Stop any servers running for the profile that you are unaugmenting.
  2. Open your command utility.
    • [AIX Solaris HP-UX Linux Windows] Open a command prompt, and navigate to the app_server_root/bin directory.
  3. Unaugment your profile.

    Use the manageprofiles command-line tool and the -unaugment parameter to remove the configuration for the augmented feature from the profile.

    The following command examples unaugment the myDMGR deployment manager profile with the Java Persistence API 2.0 feature in a WebSphere Application Server, Network Deployment environment.
    • If the deployment manager was created as part of a cell profile:
      [Windows]
      manageprofiles.bat -unaugment -profileName myDMGR -templatePath 
      app_server_root\profileTemplates\JPA\cell.jpafep\dmgr
      [Linux] [Solaris] [HP-UX] [AIX]
      manageprofiles.sh -unaugment -profileName myDMGR -templatePath 
      app_server_root/profileTemplates/JPA/cell.jpafep/dmgr
    • If the deployment manager was created as a management profile of type deployment manager:
      [Windows]
      manageprofiles.bat -unaugment -profileName myDMGR -templatePath 
      app_server_root\profileTemplates\JPA\management.jpafep
      [Linux] [Solaris] [HP-UX] [AIX]
      manageprofiles.sh -unaugment -profileName myDMGR -templatePath 
      app_server_root/profileTemplates/JPA/management.jpafep
    Tip: If you do not know how the profile was originally created, perform one of the following actions:
    • Look in the app_server_root/properties/profileRegistry.xml file, where the subelement related to the profile will point to the template that was used to create it.
    • Use the -listAugments parameter with the manageprofiles command to list the registered augments on the profile from the profile registry. For example:
      manageprofiles(.bat)(.sh) -listAugments -profileName profile_name
    The following command examples unaugment the myDMGR deployment manager profile with the OSGi Applications feature in a WebSphere Application Server, Network Deployment environment.
    • If the deployment manager was created as part of a cell profile:
      [Windows]
      manageprofiles.bat -unaugment -profileName myDMGR -templatePath 
      app_server_root\profileTemplates\aries\cell.ariesfep\dmgr
      [Linux] [Solaris] [HP-UX] [AIX]
      manageprofiles.sh -unaugment -profileName myDMGR -templatePath 
      app_server_root/profileTemplates/aries/cell.ariesfep/dmgr
    • If the deployment manager was created as a management profile of type deployment manager:
      [Windows]
      manageprofiles.bat -unaugment -profileName myDMGR -templatePath 
      app_server_root\profileTemplates\aries\management.ariesfep
      [Linux] [Solaris] [HP-UX] [AIX]
      manageprofiles.sh -unaugment -profileName myDMGR -templatePath 
      app_server_root/profileTemplates/aries/management.ariesfep
    Tip: If you do not know how the profile was originally created, perform one of the following actions:
    • Look in the app_server_root/properties/profileRegistry.xml file, where the subelement related to the profile will point to the template that was used to create it.
    • Use the -listAugments parameter with the manageprofiles command to list the registered augments on the profile from the profile registry. For example:
      manageprofiles(.bat)(.sh) -listAugments -profileName profile_name
    Note: The -unaugment argument unaugments only the last augmentation applied to the profile unless both the -templatePath and -ignoreStack parameters are specified as well.

Results

The command returns a message indicating whether the profile was unaugmented successfully.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task 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=txml_wsfpunaugment
File name: txml_wsfpunaugment.html