Install IBM DataPower XC10 appliance


  1. Install the appliance hardware
  2. Initialize the appliance
  3. Install WXS client
  4. Uninstall WXS client
  5. Troubleshoot the product installation


Install the appliance hardware

  1. Physically install the appliance in the rack.

    1. Unpack the appliance. Locate all supplied power cords, the serial cables, and the rails.

    2. Identify the rack location for installation, and ensure that there is sufficient space above and below the appliance for ventilation and appliance maintenance.

    3. Secure the mounting rails.

    4. Install the appliance on the rails, and slide the appliance into place.

    5. From the front of the appliance, use network cables to connect the appliance to your network. Ethernet cables are not supplied.

      • Connect the MGMT0 management port to a 1 gigabit network.

      • For non-management traffic for the data grid, use either the left Ethernet module (1 gigabit ports), or the right Ethernet module (10 gigabit ports).

    6. Use the supplied power cords to connect power supplies to power outlets.

    7. From a serial console, establish a connection to the CONSOLE connector on the front of the device, configured with 9600 baud 8N1 (8 bits per character, no parity, 1 stop bit), and no flow control.

      Use the supplied serial cable or PL-2303 USB-to-serial cable to make the connection. If you are using the PL-2303 USB-to-serial cable, download and install a driver for the cable. The recommended terminal emulation on the serial console is VT100.

    8. Press the power button.

      The green power LED light is illuminated and the serial console displays.

    9. The login prompt displays.

      For the initial appliance configuration, log in with the user ID and password:

        xcadmin/xcadmin

    Do not lose the xcadmin user ID and password

    If you lose this information, you cannot log back in to the appliance and send the appliance back to IBM for remanufacturing, which erases all data on the appliance. To ensure access to the xcadmin user ID and password, consider configuring an SMTP server and email address so you can reset the xcadmin password.

    Do not attempt to physically open the case of the appliance

    Opening the case triggers a security fault and the appliance no longer operates. It must then be returned to IBM for remanufacturing.

  2. Configure the appliance for access with the serial console.

    A wizard guides you through the process of accepting the license agreements and configuring the Ethernet ports.

  3. Update the appliance firmware to the latest version.

  4. To monitor the progress of the appliance startup after the firmware upgrade, run the start-progress command

    When this command returns STARTED, the appliance is ready for use.

  5. Start the user interface.

    1. In the Web browser address bar, enter the URL and port information defined during the device initialization.

      You can also use the IP address or host name, for example:

        https://myXC10.ibm.com

      Use the secure HTTP protocol (HTTPS).

    2. Enter xcadmin in the User field.

    3. Enter xcadmin in the Password field.

    4. Click Log In. To log out, click Log Out.

    If the Welcome page displays, authentication of the local xcadmin account was successful.

  6. Confirm the operational states of the appliance.

    • The green Power LED light at front of the appliance is illuminated.
    • The amber Fault LED light at front of the appliance is not illuminated.
    • The green Caching LED light at the front of the appliance is illuminated.
    • The amber Caching Error LED light at the front of the appliance is not illuminated.
    • The LCD on the front of the appliance displays the product release and build version.

    If you have concerns, contact IBM Support.


Initialize the appliance

To perform the initial configuration, use a serial connection between an ASCII terminal or PC running terminal emulation software to the serial port on the appliance.

For PCs use a PC-based serial communications program for Windows or Linux.

For the ASCII terminal, you can use a dedicated hardware device, such as a VT100-style console, or a PC running an emulator, such as HyperTerminal or Minicom. Use either the supplied serial cable or PL-2303 USB-to-serial cable to make the connection to the appliance.

If you are using the PL-2303 USB-to-serial cable, download and install a driver for the cable before proceeding.

Use a 1 gigabit network connection for the MGMT0 management port. Use either the left Ethernet module (1 gigabit ports), or the right Ethernet module (10 gigabit ports).

Before defining the base configuration, determine...

Use this task to initialize theDataPower XC10 appliance for the first time. The first time you sign onto the appliance the process is slightly different from signing on afterward.

  1. Do not attempt to physically open the case of the appliance.

    Opening the case triggers a security fault and the appliance no longer operates. Run the device clear-intrusion command to restore the appliance.

  2. Do not misplace the serial cable that was included with the appliance.

    You need this cable for the initial appliance setup, and it could also be needed later for problem determination. This cable has been specially designed to work with this appliance. Other serial cables might not work with this appliance.

Perform the initial, base firmware configuration. This configuration is the minimal configuration to add a WebSphere DataPower XC10 appliance to your environment.

  1. Initialize the appliance...

    1. Connect your serial console to the appliance using the serial cable or USB-to-serial cable supplied with the appliance.

      Connect the cable to the CONSOLE connector on the front of the device and have the ASCII terminal or a PC running terminal emulation software running, so you can see messages from the appliance as it starts. Configure the emulation software with 9600 baud 8N1 (8 bits per character, no parity, 1 stop bit), and no flow control. The recommended terminal emulation on the serial console is VT100.

    2. Power on the appliance

      The power button is on the front of the appliance. Wait for a few seconds for the appliance to boot. When the appliance is on:

      • The green power LED light illuminates on the front of the appliance and the fans start.

      • The login prompt displays in the serial console. For the initial appliance configuration, log in with the user ID and default password:

          xcadmin/xcadmin

    3. Accept the WebSphere DataPower XC10 appliance license agreements.

      Before proceeding, for the first time, accept the licenses. Type Accept, Reject, or StartOver at each license prompt.

    4. Configure the MGMT Ethernet port. Provide the IP address in classless inter-domain routing (CIDR) format.

    5. Configure the default gateway for the MGMT Ethernet port.

    6. Configure the Ethernet ports for the data grid.

      Specify whether you are using all 1 gigabit ports or all 10 gigabit ports. Configure the CIDR address for the applicable ports.

    7. Configure the DNS servers.

      Specify a valid IP address for your DNS server.

  2. Update the appliance firmware.

    To download or update the WebSphere DataPower XC10 appliance firmware, have Appliance administration permissions. The appliance is not required to have connectivity to the external internet to retrieve the firmware update.

  3. If you are installing the firmware for the first time on a new appliance, after the restart from the firmware upgrade finishes, run the clear-all command on the appliance.

    1. Connect to the appliance using the xcadmin user.

    2. Run the clear-all command.

      Console> clear-all
      Force Stopped all XC-10 processes
      Deleting configuration data and logs
      Deleting grid data 

      Do not run any other commands before running the clear-all command. Running other commands can create problems with the appliance configuration.

    3. After running clear-all, you can use the start-progress command to monitor the percentage of completion for the restart. When the start-progress command displays a response of STARTED, you can log in to the user interface.

      Do not run any other commands while the clear-all command is running. Use only the start-progress command to monitor the progress.

  4. To secure the configuration, change the password for the xcadmin user.

      user password <old_password> <new_password>

    The default password is xcadmin.

  5. Use the user interface with a Web browser to verify the configuration.

    1. Open a Web browser and enter the URL defined during the device initialization. For example:

        https://myXC10.ibm.com

      Use the https protocol, not http.

    2. Log on to the appliance.

      Log on to the appliance with the local xcadmin account and password.

    3. Click Log In.

      If the Welcome page displays, authentication of the local xcadmin account is successful.

  6. Complete the configuration.

The initial setup for the WebSphere DataPower XC10 appliance is complete. Configure the appliance settings in the user interface. These settings include users and user groups, security, email delivery, DNS servers, and date and time settings.


xcadmin password

After setting the administrative (xcadmin) user ID and password, store the information in a reliable location. You can configure email delivery to enable the ability for password resets in the user interface.


Save the user ID and password

The xcadmin user ID and password are necessary to log on to the appliance so put them in a secure location after you change them. If you lose them, and you have no means to recover them, then the appliance must be returned to IBM for remanufacturing


Email reset of passwords

If you configure email delivery, all users can restore their passwords by clicking a Forgot password? link on the user interface login screen. An email is delivered to the user that contains a new generated password.

The only way to reset the xcadmin password is through the Forgot password? link on the user interface login screen. If you forget the password and do not have email delivery configured, then reset the appliance with the device RESET command, which resets all of the appliance settings. RESET command.


Change the xcadmin password

You can edit the password for xcadmin in the user interface or in the command line interface for the appliance.

To change the password in the user interface, edit the user.

To change the password in the command line interface for the appliance, you can use the user password command.


Install WXS client

For the appliance to work with WebSphere Application Server or clients in a stand-alone environment, either...

WAS applications can leverage the WXS client for dynamic cache or and HTTP sessions. Simple Data Grids can be used in an embedded WAS environment or in a stand-alone environment.

Summary of install steps...

  1. Download and install the IBM Installation Manager.

  2. Install the product repositories into IM.

    Available product offerings for WXS client include:

    • WXS client in a stand-alone environment
    • WXS client for WAS v6
    • WXS client for WAS v7
    • WXS client for WAS v8

  3. Download the WXS client from the support site.

  4. Run the installation using the Installation Manager.

    • Embedded client installation

      To use dynamic cache, HTTP sessions, or simple data grids, use the embedded installation.

    • Stand-alone client installation

      Use the client installation in a stand-alone environment with simple data grids only.

    • Silent installation

      Install the client in a stand-alone environment or in an embedded WAS environment using a response file.


Install IM and WXS client product offerings

You can install IM using...

A file is a compressed archive that contains installation images.

There are two options to access product repositories.

Option 1: Access product repositories on the physical media, and use local installation...

  1. Install Installation Manager
  2. Use IM to install the product offering from the product repositories on the media.

Option 2: Download product repositories from Passport Advantage, and use local installation...

  1. Download the repositories from Passport Advantage.
  2. Install Installation Manager.
  3. Use IM to install the product from downloaded product repositories.


Install WXS client v8.5 within WAS

  1. Install within a WAS v8 environment...

    1. Install Installation Manager.

    2. Download the WAS v8.5 repositories .

      You can install the WXS client into either WAS ND or WAS Liberty profile.

    3. Install WAS v8.5

    4. Stop all running java processes the WAS environment.

    5. Download WXS client and create repository within Installation Manager

    6. Use Installation Manager to install WXS client for WAS ND v8 or WAS

      Install WXS client into the same directory in which you installed WAS. For example, if you installed WAS in /was_root, then also choose /was_root as the target directory for the WXS client installation. Verify the target installation directory does not contain an existing installation of WXS client.

  2. Install within a WAS v7 environment

    1. Install WAS v7 using the ISMP installer.

    2. Verify the target installation directory does not contain an existing installation of WXS client.

    3. Stop all running java processes the WAS environment.

    4. Install Installation Manager.

    5. Create WXS client v8.5 repository in Installation Manager

    6. Use Installation Manager to install WXS client for WAS v7

      For install option, select Client. For install directory, select either DMGR or WCS home directories.

      During the WXS client installation, the installer will ask if you want to augment the nodes. Augmentation can also be performed after the install using the profile management tool.

    7. Import WAS v7 into IM to complete the installation

      Importing WAS v7 into Installation Manager management of fix packs for the product from one location.

      If you augment the nodes during the install, to verify that augmentation was successful, run...

        ./versionInfo.sh

  3. Install within a WAS v6 environment...

    1. Install WAS v6 using the ISMP installer.

    2. Verify the target installation directory does not contain an existing installation of WXS client.

    3. Stop all running java processes the WAS environment.

    4. Install Installation Manager.

    5. Use IM, install the eXtreme Scale WXS client for WAS v6


Install Installation Manager with GUI

Install WXS v8.6 repositories, first install Installation Manager.

You can install IM using a wizard console. If required, set up X-Windows.

  1. Administrative installation...

      cd /path/to/IM/install/files
      ./install

  2. User installation...

      cd /path/to/IM/install/files
      ./userinst

  3. UNIX group-mode installation...

      cd /path/to/IM/install/files
      ./groupinst

    Group mode allows multiple users to use a single instance of IM to manage software packages. If you do not install IM using group mode, you will not be able to use group mode to manage any of the products that you install later using this IM.

    Change the installation location from the default location in the current user's home directory to a location that is accessible by all users in the group.

    Set up your groups, permissions, and environment variables based on IM instructions

  4. Make sure the IM package is selected, and click Next.

  5. Accept the terms in the license agreements, and click Next.

  6. Click Next.

  7. Review the summary information, and click Install. If the installation is successful, the program displays a message indicating that installation is successful. If the installation is not successful, click View Log File to troubleshoot the problem.

  8. Add the product repository to your IM preferences.

    1. Start IM.
    2. In the top menu, click File > Preferences.
    3. Select Repositories.
    4. Click Add Repository.
    5. Enter the path to the repository.config file in the location containing the repository files, for example:

      • C:\repositories\product_name\local-repositories
      • /var/repositories/product_name/local-repositories

    6. Click OK.

  9. Clear any locations listed in the Repositories window that you will not be using.

  10. Click Apply.

  11. Click OK.

  12. Click File > Exit to close Installation Manager.

After successfully installing Installation Manager and setting up the repository, you can continue to install WXS WXS client or WXS for WAS for product offering.


Install WXS client with GUI

Use the IM from the wizard console to install WXS client product offerings.

If required, set up X-Windows.

Install the product files for the Installation Manager and have access to necessary repositories.

  1. Start IM.

    You can start IM in group mode with the ./IBMIM command.

    • Group mode allows multiple users to use a single instance of IM to manage software packages.
    • For more information about using group mode, read the Group mode road maps in the IM v1.5 Information Center.

  2. Click Install.

    If you are prompted to authenticate, use the IBM ID and password that you registered with on the program website.

    IM searches its defined repositories for available packages.

  3. Select one of the following product offerings and the appropriate version.

    • WXS client in a stand-alone environment
    • WXS client for WAS v6
    • WXS client for WAS v7
    • WXS client for WAS v8

    If you already have the product installed on your system, a message indicates the product is already installed. To create another installation of the product in another location, click Continue.

    If Search service repositories during installation and updates option is selected on the IM Repository preference page and you are connected to the Internet, you can click Check for Other Versions and Extensions. By doing so, you can search for updates in the default update repositories for the selected packages. In this case, you do not need to add the specific service-repository URL to the IM Repository preference page.

    1. Select the fixes to install.

      Any recommended fixes are selected by default.

      If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

    2. Click Next.

    IM might prompt you to update to the latest level of IM when it connects to the repository. If you are prompted, update to the newer version before you continue. Read the IBM Installation Manager v1.5 Information Center for information about automatic updates.

  4. Accept the terms in the license agreements, and click Next.

  5. Specify the installation root directory for the product.

    The panel also specifies the shared resources directory and disk-space information.

    The first time that you install a package using IM, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.

    Deleting the default target location and leaving an installation-directory field empty prevents you from continuing.

    Do not use symbolic links as the destination directory.

    Symbolic links are not supported.

    Do not use a semicolon in the directory name.

    If the target directory includes a semicolon, the WXS does not install as expected. A semicolon is the character used to construct the class path on Windows systems.

    The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.

  6. Click Next.

  7. Select the languages for which translated should content be installed.

    English is always selected.

  8. Click Next.

  9. Select the features to install.

    Depending on which product offering you selected, you can choose from the following features:

    • Console

      Available for all WXS product offerings. Monitoring console. Chart current and historical statistics. Use the charting capabilities in the monitoring console of WXS to view the overall performance of the data grids in your environment.

    • Samples

      Available for all WXS product offerings.

  10. Click Next.

  11. Review the summary information, and click Install.

    • If the installation is successful, the program gives you a message to indicate that installation is successful.

      The program might also specify important post-installation instructions as well.

    • If the installation is not successful, click View Log File to troubleshoot the problem.

  12. Select which tool you want to start when this installation is finished.

    • Select pmt.sh to create a profile if you want to create a new application server profile with settings appropriate for a production environment.

    • Select pmt.sh to create an application server profile for a development environment if you want to create an application server profile with settings appropriate for a development environment.

      The development settings are appropriate for a development environment where frequent application updates are performed and system resources are at a minimum. Do not use the development settings for production servers.

    • Select None if you do not want to create a new profile when this installation is finished.

    The option to start the pmt.sh is only available when a version of WAS containing the pmt.sh is installed.

  13. Click Finish.

  14. Click File > Exit to close Installation Manager.

  15. If you are integrating with WAS v7, import WAS v7 into IM to complete the installation


Install IM with scripts

In order to access the product repositories so that you can install WXS client product offerings, install IM. You can install IM from the command line. Install the product files for the Installation Manager and have access to necessary repositories.

  1. Change to the location containing the IM installation files, and run one of the following commands:

    Administrative installation:

      ./installc -acceptLicense -log log_file_path_and_name

    Non-administrative installation:

      ./userinstc -acceptLicense -log log_file_path_and_name

    Group-mode installation:

    ./groupinstc -acceptLicense -dataLocation application_data_location -log log_file_path_and_name -installationDirectory Installation_Manager_home

    Group mode allows multiple users to use a single instance of IM to manage software packages.

    Group mode is not available on Windows operating systems.

    If you do not install IM using group mode, you will not be able to use group mode to manage any of the products that you install later using this IM.

    Make sure that you change the installation location from the default location in the current user's home directory to a location that is accessible by all users in the group.

    maps in the Set up your groups, permissions, and environment variables

  2. Optional: If the repository requires a user name and password, create a keyring file to access this repository.

    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 specified.

After successfully installing IM and setting up the repository, you can continue to install WXS WXS client or WXS for WAS product offering.


Install WXS client with scripts

Use the IM from the command line to install WXS client product offerings. Install the product files for the Installation Manager and have access to necessary repositories.

  1. Log on to your system.

  2. cd IM_INSTALL/eclipse/tools

  3. Verify the product repository is available.

    ./imcl listAvailablePackages -repositories source_repository
    

    You should see one or more levels of the offering.

  4. Use the imcl command to install the product.

    ./imcl install com.ibm.websphere.offering_version,optional_feature_ID
      -repositories source_repository 
      -installationDirectory installation_directory 
      -sharedResourcesDirectory shared_directory
      -accessRights access_mode
      -preferences preference_key=value
      -properties property_key=value
      -keyring keyring_file -password password   -acceptLicense
    

    The offering_ID is the offering ID that is listed in Offering IDs for WXS client products.

    The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.0.20110503_0200 for example).

    • If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.

    • If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.

    The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:

    imcl listAvailablePackages -repositories source_repository
    

    You can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.

    • If the offering version is not specified, the -installFixes option defaults to all.
    • If the offering version is specified, the -installFixes option defaults to none.

  5. You can add a list of features that are separated by commas. An example follows:

    imcl -acceptLicense install com.ibm.websphere.WXS.v85,xs.console.feature,xs.samples.feature 
    

    • xs.console.feature

      Available for all product offerings. Monitoring console. Chart current and historical statistics. This console provides some preconfigured charts for high-level overviews, and has a custom reports page that you can use to build charts from the available statistics. Use the charting capabilities in the monitoring console of WXS to view the overall performance of the data grids in your environment

    • xs.samples.feature

      Available for all product offerings. You can choose to install samples.

    If you previously specified the mode in which to install Installation Manager, the -accessRights parameter is not required

    If you experience issues later, IM can save earlier versions of a package to roll back to. When IM rolls back a package to a previous version, the current version of the files is uninstalled and the earlier versions are reinstalled. If you choose not to save the files for rollback, you can prevent the files from being saved by specifying a preference:

    -preference com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=False
    

    Even if you choose not to save files for rollback, you can still access product files for rollback from the repository.

    The program might write important post-installation instructions to standard output.


Install IBM Installation Manager with response files

In order to access the product repositories so that you can install WXS client product offerings, install IM. You can install IM with response files. Install the product files for the Installation Manager and have access to necessary repositories.

Change to the location containing the IM installation files, and run one of the following commands to install IM.

Administrative installation:

    ./installc -acceptLicense -log log_file_path_and_name

Non-administrative installation:

    ./userinstc -acceptLicense -log log_file_path_and_name

Group-mode installation:

./groupinstc -acceptLicense -dataLocation application_data_location -log log_file_path_and_name -installationDirectory Installation_Manager_home

Group mode allows multiple users to use a single instance of IM to manage software packages. Group mode does not mean that two people can use the single instance of IM at the same time.

Group mode is not available on Windows operating systems.

If you do not install IM using group mode, you will not be able to use group mode to manage any of the products that you install later using this IM.

Make sure that you change the installation location from the default location in the current user's home directory to a location that is accessible by all users in the group.

Set up your groups, permissions, and environment variables

After successfully installing IM and setting up the repository, you can continue to install WXS WXS client or WXS for WAS for product offering.


Install WXS client using a response file

Use the IM with a response file to install WXS client product offerings. Install the product files for the Installation Manager and have access to necessary repositories.

Using IM, you can work with response files to install the product in various ways. You can record a response file with GUI.

  1. cd IM_INSTALL/eclipse

  2. Start IM from the command line using the -record option.

    For example:

      ./IBMIM -skipInstall /var/temp/imRegistry -record /var/temp/install_response_file.xml
      

  3. Non-administrator:

    ./IBMIM -skipInstall $HOME/var/temp/imRegistry 
            -record $HOME/var/temp/install_response_file.xml
    

    When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:

    • No files are installed, and this speeds up the recording.

    • If you use a temporary data location with the -skipInstall parameter, IM writes the installation registry to the specified data location while recording. When you start IM again without the -skipInstall parameter, you then can use your response file to install against the real installation registry.

      The -skipInstall operation should not be used on the actual agent data location used by IM. This operation is unsupported. Use a clean writable location, and reuse that location for future recording sessions.

  4. Add repositories to your IM preferences.

    1. In the top menu, click File > Preferences

    2. Select Repositories

    3. Perform the following actions for each repository:

      1. Click Add Repository.

      2. Enter the path to the repository.config file in the remote web-based repository or the local directory into which you unpacked the repository files.

        For example:

        • Remote repositories:

          https://downloads.mycorp.com:8080/WXS_85_repository
          

        • Local repositories:

          • C:\repositories\wxs85\local-repositories
          • /var/repositories/wxs85/local-repositories

      3. Click OK.

      4. Click Apply.

      5. Click OK.

    4. Click Install.

      If you are prompted to authenticate, use the IBM ID and password that you registered with on the program website.

      Installation Manager searches its defined repositories for available packages.

  5. Select one the following product offerings and the appropriate version:

    • WXS client in a stand-alone environment
    • WXS client for WAS v6
    • WXS client for WAS v7
    • WXS client for WAS v8

    If you already have the product installed on your system, a message indicates the product is already installed. To create another installation of the product in another location, click Continue.

    If Search service repositories during installation and updates option is selected on the IM Repository preference page and you are connected to the Internet, you can click Check for Other Versions and Extensions. By doing so, you can search for updates in the default update repositories for the selected packages. In this case, you do not need to add the specific service-repository URL to the IM Repository preference page.

  6. Select the fixes to install.

    Any recommended fixes are selected by default.

    If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

  7. Click Next.

  8. Accept the terms in the license agreements, and click Next.

  9. Specify the installation root directory for the product.

    The panel also specifies the shared resources directory and disk-space information.

    The first time that you install a package using IM, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.

    Deleting the default target location and leaving an installation-directory field empty prevents you from continuing.

    Do not use symbolic links as the destination directory. Symbolic links are not supported.

    The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.

  10. Click Next.

  11. Select the languages for which translated content should be installed.

    English is always selected.

  12. Click Next.

  13. Select the features to install.

    • Console

      Available for all WXS product offerings. Monitoring console. Chart current and historical statistics. Use the charting capabilities in the monitoring console of WXS to view the overall performance of the data grids in your environment.

    • Samples

      Available for all WXS product offerings.

  14. Click Next.

  15. Review the summary information, and click Install.

    • If the installation is successful, the program gives you a message to indicate that installation is successful.

      The program might also specify important post-installation instructions as well.

    • If the installation is not successful, click View Log File to troubleshoot the problem.

  16. Click Finish.

  17. Click File > Exit to close IM.


Create a keyring

After using the IM to record a response file to install WXS WXS client product offerings, you can choose to create a keyring file. If you are using a remote repository that requires authentication, then you can create a keyring for installation.

Record a response file.

  1. cd IM_INSTALL/eclipse

  2. Start IM from the command line using the -record option.

    For example:

    • Administrator or non-administrator:

      IBMIM.exe -skipInstall "C:\temp\imRegistry" 
        -keyring C:\IM\im.keyring 
        -record C:\temp\keyring_response_file.xml
      

    • Administrator:

      ./IBMIM -skipInstall /var/temp/imRegistry 
        -keyring /var/IM/im.keyring 
        -record /var/temp/keyring_response_file.xml
      

    • Non-administrator:

      ./IBMIM -skipInstall $HOME/var/temp/imRegistry 
        -keyring $HOME/var/IM/im.keyring 
        -record $HOME/var/temp/keyring_response_file.xml
      

  3. When a window opens that requests your credentials for the authenticated remote repository, enter the correct credentials and save them.

  4. Close IM.


Uninstall WXS client using IM

Use IBM Installation Manager to uninstall WXS client product offerings.


Uninstall WXS client with GUI

Use wizard console of IBM Installation Manager to uninstall WXS client.

  1. Uninstall the product.

    1. Stop all processes that are running in your environment.

    2. Start IM.

    3. Click Uninstall.

    4. In the Uninstall Packages window

      1. Select one of the following and the appropriate version:

        • WXS client in a stand-alone environment
        • WXS client forWAS v6
        • WXS client for WAS v7
        • WXS client for WAS v8

      2. Click Next.

    5. Review the summary information.

    6. Click Uninstall.

      • If the uninstallation is successful, the program displays a message that indicates success.
      • If the uninstallation is not successful, click View log to troubleshoot the problem.

    7. Click Finish.

    8. Click File > Exit to close IM.

  2. Optional: Uninstall IM.

    Before you can uninstall IM, uninstall all of the packages that were installed by IM.

    Read the IBM Installation Manager v1.5 Information Center for information about performing this procedure.


Uninstall WXS client with scripts

You can uninstall WXS client using IM from the command line.

  1. Log on to your system.

  2. Stop all processes that are running in your environment.

  3. Change to the eclipse/tools subdirectory in the directory where you installed IM.

  4. Use the imcl command to uninstall the product.

    ./imcl uninstall 
           com.ibm.websphere.v85,optional_feature_ID
           -installationDirectory installation_directory
    

    The offering_ID is the offering ID that is listed in Offering IDs for WXS client products.

      You can remove a list of features that are separated by commas.the feature ID. For example,

      imcl uninstall com.ibm.websphere.WXS.v85,xs.console.feature,xs.samples.feature 
      

      • client indicates the stand-alone client feature
      • server indicates the stand-alone server feature
      • console indicates the web based monitoring console
      • samples indicates the samples

    • If a list of features is not specified, the entire product is uninstalled.

    Go to the IBM Installation Manager v1.5 Information Center

  5. Optional: Uninstall IM.

    Before you can uninstall IM, uninstall all of the packages that were installed by IM.

    Read the IBM Installation Manager v1.5 Information Center for information about using the uninstall script to perform this procedure.


Uninstall WXS client with response files

You can uninstall WXS client using IM with response files.

Optional: Perform or record the installation of IM and installation of the product to a temporary installation registry on one of your systems so that you can use this temporary registry to record the uninstallation without using the standard registry where IM is installed.

Using IM, you can work with response files to uninstall the product in a variety of ways. You can record a response file with GUI as described in the following procedure, or you can generate a new response file by hand or by taking an example and modifying it.

  1. Stop all processes that are running in your environment.

  2. Optional: Record a response file to uninstall the product: On one of your systems, perform the following actions to record a response file that will uninstall the product:

    1. From a command line, change to the eclipse subdirectory in the directory where you installed IM.

    2. Start IM from the command line using the -record option.

      For example:

      • Administrator or non-administrator:

        IBMIM.exe -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\uninstall_response_file.xml
        

      • Administrator:

        ./IBMIM -skipInstall /var/temp/imRegistry 
          -record /var/temp/uninstall_response_file.xml
        

      • Non-administrator:

        ./IBMIM -skipInstall $HOME/var/temp/imRegistry 
          -record $HOME/var/temp/uninstall_response_file.xml
        

      If you choose to use the -skipInstall parameter with a temporary installation registry created, IM uses the temporary installation registry while recording the response file. When the -skipInstall parameter is specified, no product packages are installed or uninstalled. All of the actions performed in IM simply update the installation data stored in the specified temporary registry. After the response file is generated, it can be used to uninstall the product, removing the product files and updating the standard installation registry.

      The -skipInstall operation should not be used on the actual agent data location used by IM. This is unsupported. Use a clean writable location, and re-use that location for future recording sessions.

    3. Click Uninstall.

    4. In the Uninstall Packages window

      1. Select one of the following and the appropriate version:

        • WXS client in a stand-alone environment
        • WXS client for WAS v6
        • WXS client for WAS v7
        • WXS client for WAS v8

      2. Click Next.

      3. Click Next.

    5. Review the summary information.

    6. Click Uninstall.

      • If the uninstallation is successful, the program displays a message that indicates success.
      • If the uninstallation is not successful, click View log to troubleshoot the problem.

    7. Click Finish.

    8. Click File > Exit to close IM.

  3. Use the response file to uninstall the product:

    From a command line on each of the systems from which you want to uninstall the product, change to the eclipse/tools subdirectory in the directory where you installed IM and use the response file that you created to uninstall the product.

    Windows admin...

    imcl.exe 
      input C:\temp\uninstall_response_file.xml 
      -log C:\temp\uninstall_log.xml
    

    Linux admin...

    ./imcl input /var/temp/uninstall_response_file.xml \
           -log /var/temp/uninstall_log.xml
    

    Linux non-administrator...

    ./imcl input HOME/var/temp/uninstall_response_file.xml \
           -log HOME/var/temp/uninstall_log.xml
    

  4. Optional: List all installed packages to verify the uninstallation.

      ./imcl listInstalledPackages

  5. Optional: Uninstall IM.

    Before you can uninstall IM, uninstall all of the packages that were installed by IM.


Troubleshoot the product installation

To view IM go to...

An individual log file can be opened by selecting it in the table and then clicking the Open log file icon.

Logs are located in the logs directory of Installation Manager's application data location. For example:

By default, some HP-UX systems are configured to not use DNS to resolve host names. This could result in Installation Manager not being able to connect to an external repository. You can ping the repository, but nslookup does not return anything. Work with your system administrator to configure your machine to use DNS, or use the IP address of the repository.

In some cases, you might need to bypass existing checking mechanisms in IM.

If you need to use any of these bypass methods, contact IBM Support for assistance in developing a solution that does not involve bypassing the IM checking mechanisms.

Read the release notes to learn more about the latest version of IM.

To access the release notes...

If a fatal error occurs when you try to install the product...

versionInfo.sh and historyInfo.sh return version and history information based on all of the installation, uninstallation, update, and rollback activities performed on the system.