This topic applies only on the i5/OS operating system.

Installing Feature Pack for Web Services on IBM i

Install a feature pack directly from your iSeries server onto an existing Version 6.1 application server.

Before you begin

The WebSphere Application Server Feature Pack for Web Services extends the capabilities of the application server to enable Web services messages to be sent asynchronously, reliably, and securely, focusing on interoperability with other vendors and to provide support for the Java API for XML Web Services (JAX-WS) 2.0 programming model.

Before starting this installation, complete the following actions:

  1. Read Planning to install the Feature Pack for Web Services.
  2. Ensure that your user profile has *ALLOBJ and *SECADM special authorities.
  3. Determine if the application server is already installed on your server. The feature pack must be installed on an existing application server installation.
    1. Enter the Display Software Resources (DSPSFWRSC) command on a CL command line.
    2. Look for an entry with the product Resource ID 5733W61.
      • If you do not find the product Resource ID, then this product has not been installed on your iSeries server.
      • If you find the product Resources ID, ensure that at least one of the following entries is displayed:
        • 5733W61 2 5102 WebSphere Application Server V6.1
        • 5733W61 1 5101 WebSphere Application Server V6.1 Express
        • 5733W61 3 5103 WebSphere Application Server V6.1 Network Deployment
  4. Install a WebSphere Application Server Version 6.1 product if you have not done so already. Update the application server to at least version 6.1.0.13.
  5. Download the feature pack and extract the contents to an integrated file system (IFS) directory on the iSeries system on which you will install.

    For example, create two directories, web20_download and web20_installation_image. Then, download the feature pack to the web20_download directory and then extract the downloaded file to the web20_installation_image directory. Do not move any files out of the web20_installation_image directory.

  6. The operating-system requirements for a feature pack are the same as for an application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation. The following space is required:
    • 1450 MB of free space available in your target installation directory for the feature pack and included maintenance. This is in addition to the required application server product.
    • 600 MB of free space available in your temporary directory
Restriction: You cannot install a feature pack remotely, for example from a Windows workstation. You must install a feature pack on an IBM i server using a local command-line installation.
Note: If you installed WebSphere Application Server Version 6.1 for IBM i using the refresh 6.1.0.11 full installation image, you might experience a problem installing the feature pack. The refresh image is missing the enabling interim fixes needed to install the feature pack. You must apply interim fix PK55550 to install the missing enabling interim fix needed to install the feature pack. You can also resolve the problem by upgrading the application server to Version 6.1.0.13 or higher.

This problem does not exist if the application server was installed using the original Version 6.1 full installation image and upgraded with regular fix packs.

About this task

This topic describes how to install the Feature Pack for Web Services silently using the installation program. You can install the feature pack from Qshell using the INSTALL command. You can also use the RUNJVA command to invoke the installation wizard.

The installation program installs the following program files if they are not already installed:
  • WebSphere Application Server Version 6.1 Fix Pack 9 (6.1.0.9)
  • Feature pack enablement extensions
  • WebSphere® Application Server Version 6.1 Feature Pack for Web Services
Avoid trouble Avoid trouble: If you are planning to install multiple feature packs on the application server product, then there might be other steps to consider based on your topology. See Installing and configuring multiple feature packs for more information.gotcha

Procedure

  1. Log on to the iSeries system with a user profile that has *ALLOBJ and *SECADM special authorities.
  2. Copy the responsefile.WEBSV.txt file located in the WEBSV subdirectory of the extracted install image.
  3. Edit the copy of the response file. You can edit the file using a mapped drive and a text editor or by using the EDTF CL command from the IBM i system command line.

    Set values for the following options where app_server_root is the directory path to your WebSphere Application Server installation:

    -OPT silentInstallLicenseAcceptance="true"
    -OPT installLocation=app_server_root

    To override any option in the response file with command-line options, include the following option in the response file:

    -OPT overrideResponsefileOptions=true
  4. Optional: You can set values to create new application server and deployment manager profiles which are already augmented with the feature pack, or you can augment existing deployment manager profiles. You can also choose to create and augment profiles after installation. See "What to do next" on this page for more information. Change the following values in the response file to work with profiles during installation:
    Restriction: For Feature Pack for Web Services you can only augment an existing deployment manager profile. It is recommended that you create a new deployment manager profile or a new application server profile that is already enabled with the feature pack functionality. Use the profile creation tasks to create these profiles. The deployment manager and application server are the only profile types which can be created with the feature pack functionality.
    • To create a new standalone application server or deployment manager profile already augmented with the feature pack, complete the following actions:
      1. Uncomment the following line: -OPT createProfile="true"
      2. Uncomment and edit the following line: -OPT profileType="standAlone". You can choose standAlone or deploymentManager
      3. Go to either the stand alone application server section or the deployment manager section near the bottom of the file and uncomment and edit the values as needed.
    • To augment an existing deployment manager profile, uncomment the following line and edit the values for <profile_name> and app_server_root:
      -OPT PROF_augment="-profileName <profile_name> -templatePath app_server_root/profileTemplates/WEBSERVICES/dmgr.wsfep"
      
  5. Stop all processes for the application server product on which you are installing the feature pack.

    Stop the application server and any other product processes. For example, for the Network Deployment product, stop the deployment manager, the node agent, and all application server processes.

  6. Verify that the host server jobs have started on your iSeries server.

    The host server jobs allow the installation code to run on iSeries. On a CL command line, enter the following command:

    STRHOSTSVR SERVER(*ALL)
  7. If you have not already done so, read the IBM International Program License Agreement located in the lafiles directory.

    If you agree to the terms of the agreement, continue with the installation process.

  8. Invoke the installation program for the feature pack.

    Run the INSTALL command from Qshell or use the RUNJVA command from the CL command line.

    In the following example commands, path/responsefile represents the fully qualified path of the response file that you edited:

    • Run the INSTALL command from Qshell.
      1. On a CL command line, issue the STRQSH command to start the Qshell command shell.
      2. Issue the installation command from the WEBSV subdirectory of the extracted install image to start the installation program:
        install -options path/responsefile -silent
        Important: Do not exit the Qshell session (PF3) until the installation has completed. Doing so might cause the installation to stop prematurely.
    • Or, issue the RUNJVA command from the CL command line:

      At the CL command line, enter the RUNJVA command in the WEBSV subdirectory of the extracted install image. Enter the full command on one line. The command is shown here on more lines for formatting clarity:

      RUNJVA 
        CLASS(run) PARM('-options' 'path/responsefile' '-silent') 
        CLASSPATH('setup.jar') 
        PROP(
          ('Xbootclasspath/p' 'java/endorsed/xml.jar') 
          (java.version 1.5) 
          (is.debug 1)
         )
  9. For security purposes, if the host servers were not running prior to installation, it is recommended that you run the end host server (ENDHOSTSVR) command after the installation is complete.

Results

The installation program records events in the log files and installs the feature pack.

Troubleshooting

If the installation program is interrupted for any reason while feature pack files are being installed, then examine the messages that the installation program displays and the information in the installation logs. Correct the problems identified and try installing the product again. Since the feature pack installation contains the feature pack and various fix packs, an installation failure might occur at different points in the process.

What to do next

Applying Maintenance

Use the Update Installer to install maintenance packages for any of the installable WebSphere software components in the product package. Read the "Installing maintenance packages" topic for more information.

Apply the current feature pack fix pack to Feature Pack for Web Services. You must synchronize the versions of any installed feature pack with the application server. For example, if your application server is at Version 6.1.0.9, then you must upgrade to 6.1.0.13 if you wish to upgrade the feature pack to 6.1.0.13.

Use the Update Installer to install maintenance packages for any of the installable WebSphere software components in the product package. See Applying maintenance for the Feature Pack for Web Services with the Update Installer for more information.

Profiles

In order to use the feature pack functionality, you must first create a new profile enabled with the feature pack, or augment an existing deployment manager profile.

For the Feature Pack for Web Services you can only augment the deployment manager profile type. It is recommended that you create a new deployment manager profile or a new application server profile that is already enabled for the feature pack. Use the profile creation tasks to create these profiles.

Samples

The Feature Pack for Web Services provides several sample applications that you can install onto an application server profile that has been created with the feature pack functionality. See Installing Web Services Samples with the console for more information.




In this information ...


Related reference

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: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_is_instloc_fep
File name: tins_is_instloc_fep.html