[IBM i]

Installing and removing features on IBM i operating systems using response files

You can install and remove a product feature using Installation Manager response files.

About this task

Perform this procedure to use Installation Manager to install or remove a feature silently using a response file.

Like other Installation Manager operations, you can invoke a modification using the imcl command-line tool. Go to the IBM® Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center for more information.

Optional features: In the following list of optional features, the offering names to be used in the response files are enclosed in parentheses:
  • EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)

    This option installs 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.

    Tip: Unexpected errors might occur if applications that are provided with IBM WebSphere Application Server, such as the samples, require the optional EJBDeploy tool for pre-EJB 3.0 modules but the feature is not installed. If you deploy and use applications that might require pre-EJB 3.0 modules, include the optional EJBDeploy feature in all WebSphere Application Server installations that will be used by servers running the pre-EJB 3.0 applications.
  • Standalone thin clients, resource adapters, and embeddable containers
    • Standalone thin clients and resource adapters (thinclient)

      This option installs 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)

      This option installs the embeddable EJB container.

      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 option installs the sample applications for learning and demonstration environments.

    The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to 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 Version 8.5.0.x 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 - Express (with the com.ibm.websphere.liberty.EXPRESS.v85 offering ID). After installing WebSphere Application Server Liberty - Express, 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.
Restriction: You cannot use the Installation Manager to modify an installation and add or remove the full WebSphere Application Server profile feature or the Liberty profile feature.

Procedure

  1. Optional: If the repository requires a username and password, create a keyring file to access this repository.

    For more information on creating a keyring file for Installation Manager, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

    Tip: When creating a keyring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.
    Note: Starting in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. When you use Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

    There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.

    For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.

  2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  3. On a CL command line, run the STRQSH command to start the Qshell command shell.
  4. Use a response file to install or remove a feature.
    Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and modify the product. For example:
    ./imcl
      input $HOME/WASFiles/temp/modify_response_file.xml 
      -log $HOME/WASFiles/temp/modify_log.xml 
      -keyring $HOME/WASFiles/temp/im.keyring
    Note: The program might write important post-installation instructions to standard output.

    For more information on using Installation Manager, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

Example

Task topic    

Terms and conditions for information centers | Feedback

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