[Linux]

Preparing SUSE Linux Enterprise Server 12 for installation

You might have to complete additional steps to prepare a SUSE Linux Enterprise Server Version 12 system for a WebSphere Application Server installation.

Before you begin

Complete all steps in Preparing Linux systems for installation. Those steps are common to any Linux system.

For information about the WebSphere Application Server offerings that support the POWER® Little Endian (LE) architecture, see WebSphere Application Server product offerings for supported operating systems.

Procedure

  • Verify that the appropriate library package or packages exist on your SUSE Linux Enterprise Server Version 12 operating system.
    To install all packages that the product requires, run the following command:
    zypper install libgtk-3-0-32bit libgthread-2_0-0-32bit libXtst6-32bit libstdc++6-32bit
    Avoid Trouble: If you plan to use the Profile Management Tool (PMT), you can encounter issues using GTK+ 3.0. For more information, see Managing profiles using the graphical user interface.

    Run the following commands to install the required packages for a specific product component:

    • WebSphere Configuration Tools (WCT):
      zypper install libgtk-3-0-32bit libgthread-2_0-0-32bit libXtst6-32bit
    • Edge Caching Proxy:
      zypper install libstdc++33-32bit

      This package requires the SLE-Module-Legacy product repository.

  • For POWER Little Endian (LE), review the following platform-specific limitations:
    • IBM® Installation Manager Version 1.8.0 or later is required.
    • WebSphere Configuration Tools, including the Profile Management Tool, are supported in command-line only mode.
    • Java™ 7.1 is the default and only provided SDK.
    • Edge Caching Proxy is not supported on this architecture.
    • Load Balancer for IPv4 and IPv6 components Content Based Routing (CBR) and Site Selector are not supported.
    • IBM HTTP Server and the WebSphere web server plug-in do not have a Federal Information Processing Standards (FIPS) 140-2 certified implementation. To use these components in uncertified FIPS 140-2 mode, set the native environment variable ICC_IGNORE_FIPS to yes.

What to do next

After you complete the steps in this article, see What to do next in Preparing Linux systems for installation.