Fix Pack 8550

Liberty profile: featureManager command

Use the featureManager command to install a feature, and to obtain details of all the features that are installed.

The feature that you want to install must be packaged as a subsystem archive (ESA file).

Syntax

The command syntax is as follows:

featureManager action [options]
where action can take one of the following values:
install
Install a feature from an enterprise subsystem archive (ESA) file. This action uses the OSGI-INF/SUBSYTEM.MF file from the ESA file as a new feature manifest that can be copied into the ${wlp.user.dir}/extensions/lib/features directory (or product extension directory if a value is specified for the --to property) being renamed after the symbolic name of the subsystem. All of the bundles for the subsystem will be extracted into the ${wlp.user.dir}/extensions/lib directory and renamed as {bundle symbolic name}_{bundle version}.jar. License files, checksum files, localization files and other subsystem content will also be extracted to the location defined in the subsystem manifest.
featureList
Generate an XML file that contains a report that details all the features that are installed.
help
Display help information for a specified action.

Options

The following options are available for the featureManager install command:
--acceptLicense
Automatically indicate acceptance of license terms and conditions.
--to=install_option
where install_option can take one of the following values:
  • usr: The feature is installed as a user feature. This is the default value.
  • extension: The location to which you want to install the feature. You can install the feature to any configured product extension location.
--viewLicenseAgreement
View license agreement.
--viewLicenseInfo
View license information.
--when-file-exists=exist_option
Specifies the action to take if a file to be installed already exists. exist_option can take one of the following values:
  • fail: Cancel the installation.
  • ignore: Continue the installation and ignore the file that exists.
  • replace: Overwrite the existing file.
subsytem_archive_location
Specifies the location of the subsystem archive (ESA file) that you want to install. You can specify a file name or a URL.
The following options are available for the featureManager featureList command:
--encoding=charset
where charset is the character set to use when creating the XML report file.
--locale=language
where language specifies the language to use when creating the XML report file. This consists of the ISO-639 two-letter lowercase language code, optionally followed by an underscore and the ISO-3166 uppercase two-letter country code.
--productExtension=name
where name is the product extension name whose features are to be listed. If the product extension is installed in the default user location, use the keyword: usr. If this option is not specified, the action is taken on Liberty core.
XML_report_file_name
Specifies the name of the XML report file that you want to create.

Usage examples

The following example installs the subsystem archive my_feature.esa as a user feature:
featureManager install my_feature.esa --to=usr
The following example installs the subsystem archive my_feature.esa to the my_extension product extension location:
featureManager install my_feature.esa --to=my_extension
The following example generates a report for all installed Liberty core features; the report is written to the file my_feature_report.xml using the Brazilian Portuguese language:
featureManager featureList my_feature_report.xml --locale=pt_BR
The following example generates a report that contains all installed features that are defined in the product extension that is installed in the default user location wlp/usr/extension, which is known by the runtime environment as the usr product extension. The report is written to the file my_feature_report.xml:
featureManager featureList --productExtension=usr my_feature_report.xml
The following example generates a report that contains all features that are defined in the product extension that is installed in the location pointed to by the content in the productExtensionName.properties file in the product installation's etc/extensions directory. The report is written to the file my_feature_report.xml:
featureManager featureList --productExtension=productExtensionName my_feature_report.xml
The following example displays help information for the install action:
featureManager help install

Icon that indicates the type of topic Reference topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=rwlp_command_featuremanager
File name: rwlp_command_featuremanager.html