AIX stand-alone: Install WebSphere Portal


Overview

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 environment to include high availability failover, a more robust database, and LDAP-based authentication.


Pre-Install

  1. Prepare the AIX OS
  2. Review installation methods, options, and sources
  3. Review WebSphere Portal detailed system requirements


Install

  1. To verify that fully qualified host name is properly configured....

      ping myserver.yourcompany.com

  2. To verify that network is properly configured...

      ping localhost

  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

    WAS installations that have an existing WebSphere Portal v7.0 profile or that do not meet the correct software versions will not be included in the list of available, existing WAS instances. Ensure that the existing WAS instance, and Apache Derby, are installed at the supported level.

  4. To install WebSphere Portal using a non-root user (Optional)

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

    2. Create a non-root user and change ownership:

      1. Create a new group AIX group, create a new user, and add the new user to the new group.

      2. 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. If you are also installing WAS as a non-root user, choose one of the following additional tasks based on whether you have a 32-bit or 64-bit AIXOS:

        OS Additional task
        32-bit OS chmod -R g+rwx /A-Setup
        chgrp -R group_name /A-Setup
        64-bit OS chmod -R g+rwx /A-Setup
        chgrp -R group_name /A-Setup

    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. Run the installation command...

    Type Task
    GUI ./install.sh
    Console ./install.sh -console
    Silent ./install.sh -options "/path/to/response_filename"

    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 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"

    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 installation was successful; access WebSphere Portal using...

      http://myserver:10039/wps/portal

    To generate the server1_PortMatrix.txt and WebSphere_Portal_PortMatrix.txt files:

        cd WP_PROFILE/ConfigEngine


      ./ConfigEngine.sh list-server-ports -DWasPassword=foo
      ./ConfigEngine.sh list-server-ports-by-name -DServerName=server1 -DWasPassword=foo
      ./ConfigEngine.sh list-server-ports-by-name -DServerName=WebSphere_Portal -DWasPassword=foo

    The port files are located in...

      WP_PROFILE/ConfigEngine/log/

  7. To enable the sample IBM WCM content, such as internet and intranet sample sites.

        cd WP_PROFILE/ConfigEngine


      ./ConfigEngine.sh configure-express -DPortalAdminPwd=foo -DWasPassword=foo

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

    The command...

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

    2. Creates two new Web Content Manager Libraries:

      • Internet Web Content 7.0.0
      • Intranet Web Content 7.0.0

      To view, navigate to...

        Administration | Portal Content | Web Content Libraries

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

    4. Creates two new theme policies:

      • InternetStyle
      • IntranetStyle

      These styles are applied to sample Internet and intranet sites. Navigate to Theme Customizer and then select the style.

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

    6. Creates two virtual portals with context roots of wps/portal/intranet and wps/portal/internet. These are the sample Internet and intranet sites. To access...

        http://myserver:port/wps/portal/internet
        http://myserver:port/wps/portal/intranet

    7. Creates several sample credential slots, including...

      • Default slot for E-mail
      • Default slot for Feeds
      • Default slot for Miscellaneous
      • Default slot for Web Clipping
      • Default slot for Web Content Management

      To view, navigate to...

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

    1. Edit...

        WP_PROFILE/PortalServer/wcm/shared/app/config/wcmservices/MemberFixerModule.properties

      Add the following lines to the file

      uid=xyzadmin,o=defaultWIMFileBasedRealm -> portal_admin_DN
      cn=contentauthors,o=defaultWIMFileBasedRealm -> content_authors_group_DN

      Ensure the portal administrator you specify for portal_admin_DN is a member of the group you specify for content_authors_group_DN, otherwise the portal administrator cannot access the Web content libraries for the Intranet and Internet Site Templates.

      If you plan to run the express-memberfixer task in an environment with multiple realms, if it exists, remove group...

        cn=contentauthors,o=defaultWIMFileBasedRealm

      If this group exists in an environment with multiple realms, the Member Fixer task does not have any effect.

    2. Save changes and close the file.

    3. Run...

          cd WP_PROFILE/ConfigEngine


        ./ConfigEngine.sh express-memberfixer -DPortalAdminPwd=foo -DWasPassword=foo

  9. You can change the ports for WAS or WebSphere Portal

    The starting port parameter is required for a successful completion of the modify-ports-by-startport task. Once you specify a start port, this port becomes the base for assigning port values. The code increments this value as each port is assigned, which means that the WebSphere Portal ports will be assigned incrementally starting with the port defined with the modify-ports-by-startport task.

    1. Stop the server1 and WebSphere_Portal servers.

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

      Commands to change port numbers using the starting port number

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

      Sample port files are available on the Setup disc.

      		./ConfigEngine.sh modify-ports-by-portsfile -DWasPassword=foo -DModifyPortsServer=servername -DPortsFile=/full/path/to/portsfile

      The following is an example of the information within a port file although the port values will be different based on environment: 

        BOOTSTRAP_ADDRESS=10035
SOAP_CONNECTOR_ADDRESS=10025
ORB_LISTENER_ADDRESS=10034 
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=10041
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=10036
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=10033
WC_adminhost=10042
WC_defaulthost=10039
DCS_UNICAST_ADDRESS=10030
WC_adminhost_secure=10032
WC_defaulthost_secure=10029
SIP_DEFAULTHOST=10027
SIP_DEFAULTHOST_SECURE=10026
IPC_CONNECTOR_ADDRESS=10037
SIB_ENDPOINT_ADDRESS=10028
SIB_ENDPOINT_SECURE_ADDRESS=10038
SIB_MQ_ENDPOINT_ADDRESS=10040
SIB_MQ_ENDPOINT_SECURE_ADDRESS=10031

    3. Restart the server1 and WebSphere_Portal servers.

You can create additional WebSphere Portal profiles immediately after installation and then configure each profile individually or you can continue to configure WebSphere Portal environment and then create multiple profiles so that each profile has the same configuration.


Parent

Set up a stand-alone server on AIX


Previous

Prepare the AIX OS


Next topic

Configure WebSphere Portal to use a database


Related concepts

Data collection and symptom analysis
Use the web content member fixer task
Create multiple profiles on AIX
Advanced installation parameters
Explore the sample site templates


+

Search Tips   |   Advanced Search