Install WebSphere Portal on AIX

 

+

Search Tips   |   Advanced Search

 

IBM WebSphere Portal is installed as a single component, complete with an integrated database for storing information. This allows one to get WebSphere Portal up and running quickly for a proof of concept phase where you can immediately begin building and working with it. You can also expand your environment to include high availability failover, a more robust database, and LDAP-based authentication.

Review the Supported hardware and software requirements for your operating system and ensure that all hardware and software matches the minimum product level before installing WebSphere Portal.

Review Installation methods, options, and sources before installing to determine your installation source location and installation method.

To install WebSphere Portal:

  1. Type...

    ping yourserver.setgetweb.com

    ...to verify that your fully qualified host.name is properly configured.

  2. Type ping localhost to verify that your network is properly configured.

  3. If you are installing with an existing WAS instance, ensure it is installed at the supported level and has the following features installed:

    • Application Server
    • Administration
      • Scripted Administration
      • Administrative Console
    • Ant and Deployment Tools
      • Deploy Tool
      • Ant Utilities

  4. Optional

    To install WebSphere Portal using a non-root user

    1. Install the current supported version of WAS as a root user.

    2. To create a non-root user and to change ownership:

      1. Use the appropriate system commands to create a new group, to create a new user, and to add the new user to the new group.

      2. To change the rights of the non-root user: 

        chmod -R g+rwx /usr/IBM chgrp -R group_name /usr/IBM chmod -R g+wr /tmp chgrp -R group_name /tmp chmod -R g+wr /var/tmp chgrp -R group_name /var/tmp

    3. Launch the installation program and install to an existing WAS using the non-root user and set the installation location to a unique location under the path where non-root permissions were granted.

  5. Enter one of the following installation commands:

    Option Description
    GUI ./install.sh
    Console mode ./install.sh -console
    Silent install ./install.sh -options /path/to/installresponse.txt

    To uninstall...

    ./install.sh -options /path/to/uninstallresponse.txt

    Sample files are available in the setup CD root.

    Put quotation marks around the file name if there are spaces in the directory path or file name.

    If the installation program does not detect a WAS instance that you know exists, exit the installation program and pass the WAS instance location using the command line. For example...

    ./install.sh -W was.undetectedWas="/my/WAS/location"

    Choose one of the following methods to define ports during installation; this is especially important if installing coexisting installations:

    Option Description
    Allow the installation program to detect active ports during installation time Start up all existing Java processes to to ensure that WAS and WebSphere Portal will not use their ports.

    Use if installing coexisting installations.

    Display the Ports Configuration panel in the GUI or console mode installation program -W adminPortBlock.active=false
    -W portalPortBlock.active=false
    Specify the port range to scan for

    • WAS:

      -W adminPortBlockInput.startingPortToScan=port
      -W adminPortBlockInput.endingPortToScan=port

    • WebSphere Portal:

      -W portalPortBlockInput.startingPortToScan=port
      -W portalPortBlockInput.endingPortToScan=port

    By default the installation program starts scanning for active
    ports at 10000 and ends at 65000 for both WAS and WebSphere Portal.

    Specify the port block size

    • WAS:

      -W adminPortBlockInput.portBlockSize=block size

    • WebSphere Portal:

      -W portalPortBlockInput.portBlockSize=block size

    The block size cannot be less than 25 ports for both WAS and WebSphere Portal.

    Modify the port files

    • WAS:

      Edit...

      WASDefaultPortsFile.props

      ...located on the Setup disc with the WAS port range. Then add...

      -W adminPortBlockInput.portsFilePath=/path/to/ports/file

      ...to the installation command or in the response file.

    • WebSphere Portal:

      Edit...

      WPDefaultPortsFile.props

      ...located on the Setup disc with the WebSphere Portal port range. Then add...

      -W portalPortBlockInput.portsFilePath=/path/to/ports/file

      ...to the installation command or in the response file.

    The valid port range for both WAS and WebSphere Portal is 1 to 65535.

    If the GUI or console mode installation program fails to detect ports for either WAS or WebSphere Portal, a warning message displays and the installer offers another chance to enter the values. If the silent installation fails to detect ports for either WAS or WebSphere Portal, the installer will exit.

    If installing coexisting installations, add one of the following parameters to your installation command to set the profile as either default (true) or non-default (false):

    • -W detectProfileAction.isDefault="True"

    • -W detectProfileAction.isDefault="False"

    Add the following three parameters to modify the default profile name and profile path:

    • -W detectProfileAction.isDefault="True"

    • -W detectProfileAction.profileName="your_profile"

    • -W detectProfileAction.profilePath="C:\full\path\your_profile"

  6. Optional

    To enable the sample IBM Lotus WCM content.

    cd WP_PROFILE/ConfigEngine
    ./ConfigEngine.sh configure-express -DPortalAdminPwd=wpsadmin -DWasPassword=password

    Run the configure-express before configuring your database, user registry, context root, security, etc. If you ran any tasks other than the install task, do not run this task.

    • Creates a group called contentAuthors; members of this group are given privileges to create content in the sample Internet and intranet sites.

      Navigate to...

      Administration > Access > Users and Groups

    • Creates two new Web Content Management Libraries: "Internet Web Content 6.1.0" and "Intranet Web Content 6.1.0".

      Navigate to...

      Administration > Portal Content > Web Content Libraries.

    • Adds a portlet filter and applies the filter to various portlets in the sample Internet and intranet sites. You can see the definition of the filter in the WAS Administration console and examining the custom resources under the Environment area.

    • Creates two new theme policies: InternetStyle and IntranetStyle. These styles are applied to sample Internet and intranet sites.

      Navigate to...

      Theme Customizer and then select the style.

    • Creates several portlet clones of the Web Content Management rendering portlet. These portlet clones are used on sample Internet and intranet sites.

    • Creates two virtual portals with context roots of wps/portal/intranet and wps/portal/internet. These are the sample Internet and intranet sites. Go to http://yourserver:yourport/wps/portal/internet and http://yourserver:yourport/wps/portal/intranet to access them.

    • Creates several sample credential slots, including "Default slot for Email", "Default slot for Feeds", "Default slot for Miscellaneous", "Default slot for Web Clipping", and "Default slot for WCM ".

      Navigate to...

      Administration > Access > Credential Vault > Manage System Vault Slots.

    • Modifies the portlet palette to include some new portlets. Click the Portlets link to see the portlet palette.

    After you run the configure-express task, the owner of the items in the Web content libraries containing the Internet and Intranet Site Template content is listed as xyzadmin. To update the owner information for these items to correspond to your portal administrator ID, run the Member Fixer tool.

  7. Optional

    To change the ports for WAS or WebSphere Portal:

    1. Stop the server1 and WebSphere_Portal servers.

    2. Run one of the following commands for each server change:

      Method Task
      Start port number 
      ./ConfigEngine.sh modify-ports-by-startport 
                  -DModifyPortsServer=server 
                  -DStartPort=starting 
      port number
      Port file

      Sample port files are available on the Setup disc. 

      ./ConfigEngine.sh modify-ports-by-portsfile 
                 -DModifyPortsServer=server 
                 -DPortsFile=/path/to/ports/file

    3. Restart the server1 and WebSphere_Portal servers.

  8. Optional

    Run...

    cd WP_PROFILE/ConfigEngine
    ./ConfigEngine.sh list-server-ports task

    ...to generate the file...

    ConfigEngine_HOME/log/wp_PortMatrix.txt

    ...that lists WebSphere Portal ports.

 

Parent topic

Preparing the primary node on AIX

Next topic:

Configure WebSphere Portal to use a remote database

 

Related tasks

Use the Web content member fixer tool