+

Search Tips   |   Advanced Search

Clustered environment: Install with response file on AIX


First install IBM Installation Manager. Then use a response file to install IBM WebSphere Portal and IBM WAS in a clustered environment. Record response files on the same OS you plan for the installation. For multiple operating systems, record a response file for each operating system.

The bit architecture of the installation program uses:

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.

There are sample response files, located in...

Manually update these files based on the environment. Also replace the following lines in the sample response files if you installed WAS and WebSphere Portal from the live repository (Passport Advantage):


Use a response file for installation

  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:

    • GUI...

        ./install

    • Silently...

        ./userinstc -acceptLicense -log /tmp/install.log

    • From Portal Setup disk...

        ./setup.sh

    To change display language, add the LaunchPadLocale language code.

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

      File > Update

  5. To record a response file:

    This step does not install WebSphere Portal. You are only recording the response file used to install portal later.

    1. Start XMing server

    2. Run...

        -> xauth list
        myhost/unix:11 MIT-MAGIC-COOKIE-1 f652e7adabf3df07e8a43b824b413107
        myhost/unix:10 MIT-MAGIC-COOKIE-1 9151b1915643d032810e11191a351f93
        -> sudo su -
        # xauth add myhost/unix:10 MIT-MAGIC-COOKIE-1 9151b1915643d032810e11191a351f93
        # DISPLAY=localhost:10.0
        # export DISPLAY
        # cd /opt/IBM/InstallationManager/eclipse
        # ./IBMIM -record responsefile.xml -skipInstall /opt/IBM/Portal/Websphere1/PortalServer

    3. Navigate through the IBM Installation Manager panels and set values for the environment.

      Before adding the repositories, make sure they are located in a directory accessible to all required computers.

      On the panel...

        Select the features to install

      ...keep the default selection checked to create a new Portal server profile.

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

    5. Click Next.

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

    7. Accept the license agreement and then click Next.

    8. Select shared resources directory and then click Next.

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

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

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

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

    13. Click Profile configuration details.

    14. Select either the Standard or Advanced configuration mode.

      Select Advanced to specify URI information.

    15. Click Next.

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

    17. After the Installation Manager finishes creating the response file, click Finish and then close the Installation Manager to complete the response file recording.

    18. If installing on a different computer, copy the response file to the response file directory on that computer.

  6. If the repository URL requires authentication, use imutilsc.sh to create a keyring file store for credentials.

    The keyring file stores the credentials required for the repositories. The IBM Installation Manager command-line tool imutilsc is available from the installation tools directory. 

    ./imutilsc saveCredential -url repository_URL \
           -userName credential_userName \
           -userPassword password  \
           -keyring keyring_file  \
         [ -password keyringfile_password ] \
         [ -proxyHost proxy_host -proxyPort proxy_port \
         [ -proxyUsername proxy_username -proxyUserPassword proxyuser_password ] \
         [ -useSocks ] ] \
         [ -verbose ]

    If installing on a different computer, copy the keyring file to that computer.

  7. Install WebSphere Portal and IBM WAS...

      ./imcl -acceptLicense -input /path/to/response.xml -log /path/to/log/files

    To use your repository keyring file...

      -keyring /path/to/keyring -password keyringfile_password

  8. Verify the installation was successful; access WebSphere Portal using...

      http://myserver:myport/wps/portal


Parent: Install WebSphere Portal on AIX on the primary node