[z/OS]

Adding and removing features on z/OS

Use IBM® Installation Manager to add and remove features for the WebSphere® Application Server for z/OS® product.

Before you begin

Obtain the product repository for WebSphere Application Server for z/OS Version 8.5. The following instructions assume that the repository is mounted at /usr/lpp/InstallationManagerRepository/HBBO850. The repository can be mounted read-only.

Decide which features you need. Each installed copy of WebSphere Application Server for z/OS can have a different set of installed features.

The following features are available for the WebSphere Application Server base product. The keyword name for each feature is provided in parentheses.
[8.5.5.0 or later]
  • WebSphere Application Server full profile (core.feature)
    You must install core.feature.
    • EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)

      This optional feature contains the EJBDeploy tool for pre-EJB 3.0 modules.

      Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.

    • Standalone thin clients and resource adapters (thinclient)

      This optional feature contains the IBM standalone thin clients and resource adapters. IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.

    • Embeddable EJB container (embeddablecontainer)

      The embeddable EJB container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

    • Sample applications (samples)

      This optional feature contains the PlantsByWebSphere sample application. The samples feature is recommended for installation in learning and demonstration environments, such as development environments; however, it is not recommended for installation in production application server environments.

[8.5.5.0 or later] Note: In WebSphere Application Server Version 8.5.5.0, the Liberty profile was promoted from a feature to an independently installable offering. You cannot make an inplace update of the Version 8.5.0.x Liberty profile feature. The wlp folder includes the Liberty runtime and any user data or server configurations that you have saved in the wlp/usr folder. If you have a combined full-profile and Liberty-profile Version 8.5.0.x installation, the update program will back up the wlp folder for the existing Liberty profile feature into the wlp.bak_<timestamp> folder and uninstall the feature during an update to Version 8.5.5.0 or higher. You can continue using Liberty from the backed-up location or copy it elsewhere. To update the Liberty profile to Version 8.5.5.0 or higher, you then must install WebSphere Application Server Liberty for z/OS (with the com.ibm.websphere.liberty.zOS.v85 offering ID). After installing WebSphere Application Server Liberty for z/OS, you can move any user data and server configurations from the wlp.bak_<timestamp> folder to the new Liberty installation. See Updating the Liberty profile from Version 8.5.0 to Version 8.5.5 for more information.
  • WebSphere Application Server full profile (core.feature)
    Installing this application-server feature gives you the traditional standards-based Java Platform, Enterprise Edition (Java EE) compliant application foundation, offering broad programming model choice and low total cost of ownership through high performance and high manageability.
    • EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)

      This optional feature contains the EJBDeploy tool for pre-EJB 3.0 modules.

      Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.

    • Standalone thin clients and resource adapters (thinclient)

      This optional feature contains the IBM standalone thin clients and resource adapters. IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.

    • Embeddable EJB container (embeddablecontainer)

      The embeddable EJB container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

    • Sample applications (samples)

      This optional feature contains the PlantsByWebSphere sample application. The samples feature is recommended for installation in learning and demonstration environments, such as development environments; however, it is not recommended for installation in production application server environments.

  • WebSphere Application Server Liberty profile (liberty)

    Installing this application-server feature gives you a lightweight profile of the application server along with a simplified configuration approach for the development environment. Its fast restart times, small size, and ease of use make it a good option for building web applications that do not require the full JEE environment of traditional enterprise application server profiles. The Liberty profile also can be used in production; and because it is a dynamic configuration, the application server provisions only the features required by the running applications.

Notes:
  • You must install core.feature (full WebSphere Application Server profile), liberty (Liberty profile), or both.
  • You cannot use the Installation Manager modify, update, or rollback functions to modify this installation later and add or remove core.feature (full WebSphere Application Server profile) or liberty (Liberty profile). You can use these functions to add or remove the ejbdeploy, thinclient, embeddablecontainer, or samples subfeature of core.feature later.

Procedure

  1. Mount the product file system for the product to which features are being added or removed.
  2. Log in to the Unix System Services shell under the Installation Manager user ID, and change the directory to the eclipse/tools subdirectory of the Installation Manager binaries location.
    For example:
    cd /InstallationManager/bin/eclipse/tools
  3. View a list of the features installed with the product.
    You do this by issuing the following Installation Manager command-line command:
    imcl listInstalledPackages -features -long
    Tip: When you install a new copy of the WebSphere Application Server for z/OS and do not specify the features to be installed, the following features are installed by default:
    • core.feature
    • ejbdeploy
    • thinclient
    • embeddablecontainer
    To install the product with a different assortment of features, add a complete list of features that you want (separated by commas) after the package name in the imcl install command. For example, the following command:
    imcl install com.ibm.websphere.zOS.v85,core.feature,samples,thinclient
      -installationDirectory installation_location
      -repositories list_of_repository_locations 
      -sharedResourcesDirectory shared_data_location 
      -acceptLicense
    would install the product with the core.feature, samples, and thinclient features but not the ejbdeploy, liberty, or embeddablecontainer features.
  4. To add one or more features to an existing product installation, issue the imcl command and specify the features to be added.
    For example:
    imcl modify com.ibm.websphere.zOS.v85
      -addFeatures embeddablecontainer
      -repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.zOS.v85
      -installationDirectory installation_location
    This will add the embeddablecontainer feature if it is in not already installed.
  5. To remove one or more features from an existing product installation, issue the imcl command and specify the features to be removed.
    For example:
    imcl modify com.ibm.websphere.zOS.v85
      -removeFeatures embeddablecontainer
      -repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.zOS.v85
      -installationDirectory installation_location
    This will remove the embeddablecontainer optional feature.
    Note: Before removing optional features, make sure that none of your applications depend on the features being present.
  6. When the appropriate features are added or removed, unmount the product file system and remount it read-only for use by WebSphere Application Server nodes and servers.

What to do next

Customize or make use of any new features that you added.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-zos&topic=tins_installation_zos_options
File name: tins_installation_zos_options.html