Clustered environment: Install with GUI on Windows

The IBM Installation Manager gathers essential information, such as host name and node, verifies the operating system and its prerequisites, available disk space, and any required software prerequisites, and then performs the installation.

The bit architecture of the installation program uses:

• The bit architecture of the operating system
• The bit architecture of the existing WAS

When you install onto a 64-bit operating system, WebSphere Portal installs as a 64-bit version. We can force a 32-bit application installation onto a 64-bit operating system.

IBM Installation Manager

1. Verify the fully qualified host name...
   ping myserver.myco.com

2. Verify network configuration...
   ping localhost

3. For servers with a firewall, antivirus, screen saver, and/or desktop search engine enabled, disable them before installing.
   

4. Install IBM Installation Manager:

   • Run the install task to install the IBM Installation Manager from the IBM Installation Manager media.

   • Run the setup.exe task from the Portal Setup disk if you have a Windows 32-bit operating system and to start the launchpad.

   • Run the setup64.exe task from the Portal Setup disk if you have a Windows 64-bit operating system and to start the launchpad. Right-click on setup64.exe, then select "Run as administrator", to launch.

     To search for IBM Installation Manager updates, navigate to...

     File > Update

5. Add the repositories where the installation media exists:

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

   2. Select Browse and navigate to the IBM WAS service repository and then click OK.

   3. Ensure all required repositories are checked.

   4. Click Test Connections.

   5. Select Apply.

   6. Select OK.

6. On the main IBM Installation Manager panel, select Install to begin the installation process.

   On the panel...

   Select the features to install

   ...keep the default selection checked to create a new Portal server profile. This profile is used as the primary node for the cluster. There is also an option to create a local dmgr profile. Only select this option in a test environment where to automate the process of creating a local dmgr profile. Expand the WebSphere Portal package and select the dmgr Profile augmented with WebSphere Portal check box. Then on the Install Packages panel: Configuration details panel, click Dmgr Profile configuration details and enter the appropriate information for the dmgr.

   1. On the Select packages to install panel, select both the WAS and WebSphere Portal packages.

   2. Click Next.

   3. On the panel...
      Select the fixes to install

      ...select the following fixes based on how we are accessing the repository:

      When you install WAS and WebSphere Portal together from the live repository (Passport Advantage)

      • 8.0.0.3-WS-WAS-IFPM59935
      • 8.0.0.3-WS-WAS-IFPM60670
      • 8.0.0.3-WS-WASProd-IFPM60134
      • 8.0.0.3-WS-WAS-IFPM61934

      When you install WAS and WebSphere Portal together from the local repository (DVD or downloaded eImage)

      • 8.0.0.3-WS-WAS-TFPM59935
      • 8.0.0.3-WS-WAS-TFPM60670
      • 8.0.0.3-WS-WASProd-TFPM60134
      • 8.0.0.3-WS-WAS-TFPM61934

   4. Accept the license agreement and then click Next.

   5. Select shared resources directory and then click Next.

   6. Set Installation Directory:

      The installation directory must be empty and must not contain any of the following characters: ~ ! @ # $ % ^ & * ( ) _ + { } | < > ? ` = [ ] ; ' , . "

      1. Select the WAS Package Group Name and then select the installation directory path.

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

      3. Click Next.

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

   8. On the panel...
      Select the features to install

      ...expand the WAS and WebSphere Portal packages

      To force a 32-bit installation on the 64-bit operating system, expand the IBM WAS Network Deployment feature. Then expand IBM Software Development Kit. Under IBM Software Development Kit, select 32-bit SDK for Java.

   9. On the Configuration panel, select the type of profile template to install: Full, Base, or Custom.
      

   10. Click Profile configuration details.
       

   11. Select either the Standard or Advanced configuration mode.
       

       If the host name is incorrect, you must correct the information.

       For example, if the host name displays: serve3.server3.rtp.raleigh.ibm.com, change it to server3.rtp.raleigh.ibm.com

       Select Advanced to specify URI information.

   12. Click Next.

   13. Confirm the information on the Summary panel and then click Install.

Complete the following steps after a successful installation:

1. After a successful installation, the summary panel displays. Choose the radio button...
   Portal First Steps

   ...and then click Finish to start the servers and begin configuring WebSphere Portal.

   To access the First Steps panels later, we can either select First Steps from the Start menu or we can run the firststeps.bat task from the WP_PROFILE\PortalServer\firststeps directory. Add the LaunchPadLocale language_code to the firststeps task to change the display to the user locale or to another language.

2. If you changed the context root on the panel...
   Configuration for IBM WebSphere Portal: Profile configuration details: Advanced panel

   ...complete the steps in the Change the portal URI.

Parent: Install WebSphere Portal on Windows on the primary node