Install WebSphere Portal on Linux

 

+

Search Tips   |   Advanced Search

 

IBM WebSphere Portal is installed as a single component, with an integrated Derby database. This allows one to get WebSphere Portal up and running quickly for a proof of concept phase.

Portal can be expanded to include...

Before installing WebSphere Portal review...

To install WebSphere Portal:

  1. Verify fully qualified host name is properly configured.

      ping yourserver.setgetweb.com

  2. Type

      ping localhost

    ...verify the 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. To install WebSphere Portal using a non-root user

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

    2. Create a new group user and add the new user to the new group.

    3. Change the rights of the non-root user:

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

    4. 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. Install Portal binaries using one of the following install commands...

      Option Description
      GUI ./install.sh
      Console mode ./install.sh -console
      Silent install ./install.sh -options /path/to/file/response_filename

      A sample install response file, installresponse.txt, and uninstall response file, uninstallresponse.txt, are located in the setup CD root.

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

    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"

    For coexisting installations, define ports...

    • For installing coexisting installations, start your other Java processes and then allow the installation program to detect active ports during installation time

    • To display the Ports Configuration panel in the GUI or console mode installation program

        -W adminPortBlock.active=false -W portalPortBlock.active=false

    • To 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 between 10000 and 65000 for both WAS and WebSphere Portal.

    To 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:

      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

      ...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. If you installed WebSphere Portal Content and want to enable the sample IBM Lotus WCM content.

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

    Run this 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.

    The configure-express task...

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

        Administration > Access > Users and Groups.

    • Creates two new Web Content Management Libraries:

      • Internet Web Content 6.1.0
      • 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.

        http://yourserver:yourport/wps/portal/intranet
        http://yourserver:yourport/wps/portal/internet and...

    • Creates several sample credential slots, including...

      • "Default slot for Email"
      • "Default slot for Feeds"
      • "Default slot for Miscellaneous"
      • "Default slot for Web Clipping"
      • "Default slot for WCM

      Navigate to...

    • 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. 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. To generate...

      ConfigEngine_HOME/log/wp_PortMatrix.txt

    ...which lists WebSphere Portal ports...

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

 

Parent topic

Prepare the primary node on Linux

Next topic:

Configure WebSphere Portal to use a remote database

 

Related tasks


Use the Web content member fixer tool