+

Search Tips   |   Advanced Search

Install HCL WebSphere Portal in Linux using the graphical user interface

Use the IBM Installation Manager to install HCL DX, IBM WebSphere Application Server, and the Apache Derby database.

The installation program verifies the operating system and its prerequisites, available disk space, and any required software prerequisites before installation. We cannot install two instances of the server at the same time, even if we are installing to different directories. Install each server completely before installing the next one.

  1. Start all servers and applications that require a port number to avoid port conflicts when you install HCL DX. If we are installing multiple copies of HCL WebSphere Portal on the server, start the existing Configuration Wizard servers. Also, when using the IBM Installation Manager graphical user interface in Linux, the package libXtst.i686 and all dependent packages are required as a prerequisite.

    Note: Currently, the cw_profile starting point always defaults to 10200. If we install a second version of portal on the same server, customize the cw_profile port value. Edit...

      IM_ROOT/InstallationManager/eclipse/IBMIM.ini

    ...and add...

      -Dcwprofile_startingport=new_starting_port_number

  2. Start the IBM Installation Manager .

  3. After we install or upgrade the IBM Installation Manager, complete the following steps to add the repositories where the installation media exists:

    1. Open the IBM Installation Manager and go to File > Preferences > Repositories.

    2. Select Add Repositories.

    3. Select Browse, go to the directory where the repository.config file is found and then click OK:

      • Base server path: \SETUP\products\WP95_Server\
      • Offering path: \SETUP\products\WP95_xxxx\ where WP95_xxxx is the offering type (WCM, ENABLE, EXTEND, etc.)

      Note: Repositories for the base server and for all offering types must be added to IBM Installation Manager.

    4. Ensure that all required repositories are checked. Then, click Test Connections to ensure that the IBM Installation Manager can successfully access the directory where the service repositories are stored.

      Note: If we are installing more than just the base server, add the repositories for Offerings and SETUP.

    5. Select Apply.

    6. Select OK.

  4. On the main IBM Installation Manager panel, select Install.

  5. Optional: If we are installing Portal to an existing copy of WebSphere Application Server, then select only HCL WebSphere Portal Server on the Install Packages screen. To complete this installation option, your existing copy of WebSphere Application Server must meet the following requirements:

    • WebSphere Application Server 9.0.5.15 or later
    • Java v8.0.5.
    • No existing Portal profile

    Skip the following step, if we choose to install to an existing copy of WebSphere Application Server.

  6. Use the IBM Installation Manager, do the following:

    1. Install HCL WebSphere Portal 8.5 on WebSphere Application Server 9.0.5.15 with the required fixes.
    2. Update HCL WebSphere Portal 8.5 to CF213, and then run applyCF.sh.

    3. Install HCL WebSphere Portal Server 9.5, along with applicable extended offerings (like WCM, ENABLE, EXTEND, etc.).

    Note: The IBM WebSphere SDK Java Technology Edition option is required for an HCL WebSphere Portal installation even though it might be marked as "Optional" on the Select packages to install screen.

    Tip: For a HCL WebSphere Portal Enable license, select both the HCL WebSphere Portal Server Express and HCL WebSphere Portal Enable packages.

  7. On Install Packages: Select the fixes to install screen, select any required fixes. Then, click Next.

  8. Accept the license agreement and then click Next.

  9. Enter the directory where to store shared resources and then click Next.

  10. Complete the following steps on the Install Packages: Installation Directory panel:

    The installation directory specified must NOT contain any files or the following characters: ~ ! @ # $ % ^ & * ( ) + { } | < > ? ` = [ ] ; ' , . " and spaces.

    1. Select the WebSphere Application Server Package Group Name and then enter the installation directory path.

    2. Select the HCL WebSphere Portal Package Group Name and then enter the installation directory path.

    3. Click Next.

  11. Select the translations to install and then click Next.

  12. Optional: If you chose to install Portal to an existing copy of WebSphere Application Server, select the available copy of WebSphere Application Server, and click Next.

    Note: Skip this step, if we are not installing Portal to an existing copy of WebSphere Application Server.

  13. On Install Packages: Select the features to install, expand the WebSphere Application Server and HCL WebSphere Portal and WCM packagess to modify the features we want to install and then click Next.

    Note: Ensure that Portal Server Profile is selected to create a profile that contains the Portal application server and the product binary files. Clear this option if we need a binary only installation for migration or the clustered environment.

    Note: As we select the items, read the Details section for information.

  14. On Profile configuration details, enter the user ID and password for the configuration wizard administrator. Then, click Next.

  15. If we selected the Portal Server Profile package, click Enter the Administrator user ID and password for the Portal Server. Then, select either the Standard or Advanced configuration mode and then enter the parameter details for the selected configuration mode.

    Note:

    • If the Portal instance will be federated to a Deployment Manager (for example, WAS cluster), use a UserID (for both Portal Admin and WAS Admin) that is not found in the corporate LDAP.

    • Select Advanced if we want to specify Uniform Resource Identifier (URI) information that is specific to your company.

  16. Confirm the Summary information and then click Install.


What to do next

After a successful installation, the summary displays. Choose the Portal First Steps radio button and then click Finish to start the servers and begin configuring HCL WebSphere Portal with the Configuration Wizard.

Tip: To access First Steps later, we can either select First Steps from the Start menu or we can run the firststeps.exe./firststeps.sh task from the wp_profile_root/PortalServer/installer/wp.firststeps directory. Add the LaunchPadLocale language_code to the firststeps task to change the display to the user locale or to another language.

Before accessing WebSphere Application Server, configure the software license agreement to set the usage limit from the Proof of Entitlement (POE) or invoice. Go to Configure software license information for information.Attention: When we install WebSphere Application Server and HCL WebSphere Portal together, we might find the following message in the SystemErr.log file:

This message is part of the installation process and is not repeated after the installation is complete. Therefore, the message can be ignored.

After you upgrade to CF08 or higher, we can upgrade your SDK to version 7.1. Go to Upgrading the SDK for information.

Parent topic: Run the HCL WebSphere Portal installer in Linux