Install WebSphere Portal on Solaris on the primary node

WebSphere Portal is installed as a single component, complete with an integrated database for storing information. This allows you 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 and create a custom profile for the node that will be added to the cluster. If you already installed WebSphere Portal, you can skip to the last step to create the custom profile.

  1. Type ping on a command line to verify that your fully qualified host name is properly configured.

  2. Type ping localhost on a command line 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:

    Besides ensuring that the existing WAS instance is at the supported level, you will also need to ensure that Apache Derby is installed at the supported level before installing WebSphere Portal. See WebSphere Portal detailed system requirements for supported levels.

    • Application Server

    • Administration

      • Scripted Administration

      • Administrative Console

    • Ant and Deployment Tools

      • Deploy Tool

      • Ant Utilities

  4. Optional: Perform the following steps if you want to install WebSphere Portal using a non-root user:

    Restriction: Although it is possible to install WAS as a non-root user, there are limitations to this option that can affect WebSphere Portal functionality, which is why you should install WAS as a root user.

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

    2. Open a command prompt and perform the following steps 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. Run...


        s to 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

    3. Launch the installation program per the next step. During the installation, select the 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. Choose one of the following installation commands based on the installation method you want to use to install WebSphere Portal; see Installation Methods for more information:

    Advance installation parameters: To customize your installation, you can add various parameters to your installation commands; for example, you can specify your port information. See Advanced installation parameters.

    Restriction: When defining your installation path, the ONLY supported characters are ASCII letters [A-Z and a-z], numbers [0-9], slashes [/ or \, depending on your operating system], and the dash [-].

    Option Description
    GUI ./
    Console mode ./ -console
    Silent install ./ -options "path_to_file/response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory.

    Do not place the response file in a path that contains a space and do not put a space in the file name.

    If you have a Solaris 9 on Sun SPARC, you MUST either add the -W defaults.force32bit=true parameter to your installation command or install the 32-bit WAS product before installing WebSphere Portal to prevent the installer from automatically selecting a 64-bit environment.

    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, ./ -W was.undetectedWas="/my/WAS/location".

    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.

  6. Verify your installation was successful; access WebSphere Portal using the http://yourserver:yourport/wps/portal format. Run...

      ./ list-server-ports -DWasPassword=password


      profile_root/ConfigEngine generate the profile_root/ConfigEngine/log/wp_PortMatrix.txt file that lists WebSphere Portal ports for your installation.

  7. Optional: After the WebSphere Portal installation completes successfully, run the ./ configure-express -DPortalAdminPwd=password -DWasPassword=password task, from profile_root/ConfigEngine, if you want to enable the sample IBM Lotus Web Content Management content, such as internet and intranet sample sites.

    Restriction: Run...


    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.

    See for tutorials on how to use the sample content.

    The sample content includes:

    • Creates a group called contentAuthors; members of this group are given privileges to create content in the sample Internet and intranet sites. Navigate to the Administration area and then click 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 the Administration area and then click 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 E-mail", "Default slot for Feeds", "Default slot for Miscellaneous", "Default slot for Web Clipping", and "Default slot for Web Content Management". Navigate to the Administration area and then click 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.

  8. Optional: If you ran the configure-express task, the owner of the items in the Web content libraries containing the Internet and Intranet Site Template content will be listed as uid=xyzadmin,o=defaultWIMFileBasedRealm.

    To update the owner information for these items to correspond to the portal administrator ID, complete the following steps:

    1. Edit...


    2. Add the following line to the file:

      uid=xyzadmin,o=defaultWIMFileBasedRealm -> portal_admin_DN

      Replace portal_admin_DN with the distinguished name of the portal administrator.

    3. Save changes and close the file.

    4. Run the ./ action-express-memberfixer -DPortalAdminPwd=password -DWasPassword=password task, located in profile_root/ConfigEngine.

  9. Optional: Perform the following steps if 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
      Starting port number ./ modify-ports-by-startport -DWasPassword=password -DModifyPortsServer=servername -DStartPort=starting port number
      Port file

      Sample port files are available on the Setup disc.

      ./ modify-ports-by-portsfile -DWasPassword=password -DModifyPortsServer=servername -DPortsFile=full path to ports fileThe following is an example of the information within a port file although the port values will be different based on your environment:


    3. Restart the server1 and WebSphere_Portal servers.

  10. To prevent Out of Memory errors, perform the following steps to set the MaxPermSize: Tip: If Maximum Heap Size is set to 2048 M or higher, set the MaxPermSize to a quarter of the value entered for the Maximum Heap Size; for example, if your Maximum Heap Size is 3000 M, set MaxPermSize to 7.0 M. If your Maximum Heap Size is less than 2048 M, set MaxPermSize to 512 M.

    1. Log in to the WAS Administration Console.

    2. Click Servers > Server Types > WebSphere appservers > WebSphere_Portal.

    3. Under Server Infrastructure, click Java and Process Management > Process Definitions > Additional Properties > Java Virtual Machine.

    4. In the Generic JVM arguments field, change the MaxPermSize value to -XX:MaxPermSize=numeric value, where numeric value is a quarter of the value entered for the Maximum Heap Size.

      If MaxPermSize does not exist in the Generic JVM arguments field, add it to the field but do not replace existing information in the Generic JVM arguments field with the MaxPermSize information.

    5. Click OK to save your changes.

    6. Click Save to save your changes to the master configuration.

    7. Log out of the WAS Administration Console.

    8. Restart the server1 and WebSphere_Portal servers.

Parent topic:

Prepare the primary node on Solaris

Next topic:

Set up a remote database

Related concepts

Installation methods
IBM Support Assistant Lite for WebSphere Portal

Related reference

Advanced installation parameters