Windows cluster: Install WebSphere Portal

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.

To install WebSphere Portal on the primary node.

  1. Installation methods, options, and sources

  2. WebSphere Portal detailed system requirements

  3. Verify the fully qualified host name is configured...

      ping myserver.myco.com

  4. Type ping localhost on a command line to verify that network is properly configured.

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

    Besides ensuring that the existing WAS instance is at the supported level, verify that Apache Derby is installed at the supported level before installing WebSphere Portal. See WebSphere Portal detailed system requirements for supported levels.

  6. If you are installing on a server with a firewall, antivirus, and/or desktop search engine enabled, disable them before installing. If you do not disable them and the installation program detects them, a warning message displays during the installation.

  7. Choose one of the following installation commands:

    If you are installing WebSphere Portal on Windows™ Vista or 7, right click on the Cmd icon and select Run as administrator to start the installer from an administrator window.
    Advance installation parameters: To customize installation, you can add various parameters to installation commands; for example, you can specify port information. See "Advanced installation parameters" under Related references at the end of this document for information.

    Type Task
    GUI install.bat
    Console mode install.bat -console
    Silent install install.bat -options "/path/to/installresponse.txt"

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

  8. To verify success go to...

      http://myserver:port/wps/portal

  9. Generate the server1_PortMatrix.txt and WebSphere_Portal_PortMatrix.txt files:

      Files are created in WP_profile/ConfigEngine/log/ and list the WAS (server1) and WebSphere Portal (WebSphere_Portal) ports for installation.

      • ConfigEngine.bat list-server-ports -DWasPassword=foo

      • ConfigEngine.bat list-server-ports-by-name -DServerName=server1 -DWasPassword=foo

      • ConfigEngine.bat list-server-ports-by-name -DServerName=WebSphere_Portal -DWasPassword=foo

  10. To enable the sample WCM internet and intranet sites, run...

        cd WP_PROFILE/ConfigEngine


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

    Run configure-express 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 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 Manager Libraries: "Internet Web Content 7.0.0" and "Intranet Web Content 7.0.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 Manager 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://myserver:port/wps/portal/internet and http://myserver:port/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.

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

    1. Edit...

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

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

    3. Save changes and close the file.

    4. Run the ConfigEngine.bat express-memberfixer -DPortalAdminPwd=foo -DWasPassword=foo located in the WP_PROFILE/ConfigEngine.

  12. Optional. If you need to 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.bat modify-ports-by-startport -DWasPassword=foo -DModifyPortsServer=servername -DStartPort=starting port number
        Port file Sample port files are available on the Setup disc. ConfigEngine.bat modify-ports-by-portsfile -DWasPassword=foo -DModifyPortsServer=servername -DPortsFile=full path to ports file 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

  13. Restart the server1 and WebSphere_Portal servers.


Parent

Prepare the primary node on Windows


Next topic

Windows clustered server: Configure WebSphere Portal to use a database
Data collection and symptom analysis


Related tasks


Create a Portal custom profile on Windows
Prepare the system for multiple profile support on Windows
Create multiple profiles on Windows
Advanced installation parameters


Explore the sample site templates

 


+

Search Tips   |   Advanced Search