Install and configure WebSphere Portal v6

 

+
Search Tips   |   Advanced Search

 

 

Installation scenarios

 

Windows and UNIX installation scenarios

WebSphere Portal with WAS and Cloudscape database installed locally

This scenario focuses on installing and configuring WebSphere Portal only with no options. After you have successfully installed and configured WebSphere Portal we can add on to it.

  1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

  2. Quick installation scenario

 

 

Install WebSphere Portal into an existing environment without WAS

This scenario focuses on installing and configuring WebSphere Portal in an environment where an existing WAS is running without security enabled. After you have successfully installed and configured WebSphere Portal in this environment we can add on to it.

  1. WebSphere Portal

    1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

    2. Plan for WebSphere Portal

    3. Install WebSphere Portal to an existing environment with WebSphere Application Server :

      After you complete installation, you will be guided to the following configuration steps, which have specific properties and tasks that apply to an environment where WebSphere Application Server security has not been enabled.

    4. Configure WebSphere Portal security. Choose the method of security that matches the environment.

    5. Verify WebSphere Portal

 

WebSphere Portal with a more robust database

This scenario focuses on using WebSphere Portal with a more robust database to replace the default Cloudscape database. WebSphere Portal uses a database to store configuration and user information.

  1. WebSphere Portal

    1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

    2. Plan for WebSphere Portal

    3. Install WebSphere Portal

    4. Verify WebSphere Portal

  2. Configure databases

    1. Plan for databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    2. Install databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    3. Create databases and users [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    4. Transferring all domains [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    5. Verify database connections

 

WebSphere Portal with a more robust database and extended security using an LDAP directory

This scenario focuses on using WebSphere Portal with a more robust database and an LDAP directory.

  1. WebSphere Portal

    1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

    2. Plan for WebSphere Portal

    3. Install WebSphere Portal

    4. Verify WebSphere Portal

  2. Configure databases

    1. Plan for databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    2. Install databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    3. Create databases and users [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    4. Transferring all domains [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    5. Verify database connections

  3. LDAP user registry

    1. Install LDAP [ Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    2. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    3. Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    4. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    5. Verify LDAP

 

WebSphere Portal with Lotus Domino Integration

This scenario focuses on the products and components that are important for setting up a collaborative portal environment. Also, if you already have WebSphere Portal installed, we can enable collaboration by installing and configuring the required products.

  1. WebSphere Portal

    1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

    2. Plan for WebSphere Portal

    3. Install WebSphere Portal

    4. Verify WebSphere Portal

  2. Configure databases

    1. Plan for databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    2. Install databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    3. Create databases and users [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    4. Transferring all domains [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    5. Verify database connections

  3. LDAP user registry

    1. Install LDAP [ Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    2. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    3. Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    4. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    5. Verify LDAP

  4. Lotus Domino Integration

    1. Plan a portal with Domino Integration

    2. Lotus QuickPlace | Lotus Sametime ]

    3. Lotus QuickPlace | Lotus Sametime ]

    4. Confirming installation of Domino and Extended Products Portlets components

 

WebSphere Portal with extended security using an external security manager

This scenario focuses on using WebSphere Portal with an external security manager, such as IBM Tivoli Access Manager for e-business, to extend authentication or add authorization.

  1. WebSphere Portal

    1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

    2. Plan for WebSphere Portal

    3. Install WebSphere Portal

    4. Verify WebSphere Portal

  2. Configure databases

    1. Plan for databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    2. Install databases [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    3. Create databases and users [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    4. Transferring all domains [ DB2 | DB2 for z/OS | Oracle | SQL Server ]

    5. Verify database connections

  3. LDAP user registry

    1. Install LDAP [ Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    2. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    3. Tivoli Directory Server | Domino Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    4. Tivoli Directory Server | Domino Directory | Active Directory | Novell eDirectory | Sun Java System Directory Server | Active Directory Application Mode]

    5. Verify LDAP

  4. External security managers (Choose either Tivoli Access Manager or Computer Associates eTrust SiteMinder)

 

WebSphere Portal in a cluster environment

This scenario focuses on installing WebSphere Portal in a cluster environment.

  1. Prepare the operating system [ AIX |HP-UX |Linux | Solaris | Windows ]

  2. Clustering and WebSphere Portal

 

WebSphere Portal and Web Content Management

This scenario focuses on using Web Content Management with WebSphere Portal to create and manage Web content.

Web Content Management technology is included with WebSphere Portal by default. With Web Content Management we can manage the creation and design of Web pages, including a site's framework and navigation, and oversee the entire Web content lifecycle from creation to publication.

To use the authoring capability of Web Content Management, manually install the Authoring portlet. For more information, refer to Install the Authoring portlet.

[Back to installation scenarios]

 

Local debug portlet development environment

This scenario focuses on installing Rational Application Developer and WebSphere Portal for portlet development.

Local debug portlet development environment

Rational Application Developer is installed, go to...

RAD_HOME\rad_prod\install.html

For example...

C:\Program Files\IBM\Rational\SDP\6.0\rad_prod\install.html

If Rational Application Developer is not installed go to http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi and search on "Rational Application Developer "

For more information, see...

http://www.ibm.com/software/awdtools/developer/application/

[Back to installation scenarios]

 

Remote server attach portlet development environment

This scenario focuses on installing Rational Application Developer and WebSphere Portal for portlet development.

Remote server attach development environment

Install WebSphere Portal on the server using one of the following installation paths:

 

Custom installation

This scenario focuses on allowing you to create a scenario that suits your specific business needs. After you have become familiar with the other scenarios on this page, we can create your own custom scenario. Choose from the following components to get started.

Refer to the following instructions for each component:

 

i5/OS installation scenarios

To install WebSphere Portal for iSeries with WAS v6.0.2.7 or higher, WAS must be installed into the default installation directory. If WAS is not installed in the default installation directory, WebSphere Portal cannot be installed.

 

Install and configure WebSphere Portal for iSeries

This scenario focuses on locally or remotely installing WebSphere Portal and performing a basic configuration using the Install and configure option of the installation program. This scenario results in a functional portal configuration that might require manual adjustments through the use of configuration tasks.

Refer to the following instructions:

  1. Make the plans

  2. Verify that the system meets all hardware and software requirements.

  3. Prepare the iSeries machine

  4. Install WebSphere Portal

    Installing and configuring will...

    • Copy install image files
    • Create a WAS profile (wp_profile)
    • Add files into the WAS profile.
    • Perform a basic configuration of WebSphere Portal on the profile
    • Launch a configuration wizard to complete database and security configuration tasks.

    If an installation has already been completed, running the installation program again presents the default option of Config only. This option allows the addition of more than one portal on the same iSeries server where WebSphere Portal was installed. This option has the identical functions as the Install and configure option.

  5. Install IBM Tivoli License Compliance Manager.

    While it is installable, IBM Tivoli License Compliance Manager is not supported at this time on i5/OS.

  6. Verify and launch WebSphere Portal .

  7. Add any optional WebSphere Portal components not included in this installation scenario.

  8. To install more than one copy of WebSphere Portal on the same machine, repeat this installation scenario, starting with this step.

 

Install only. Configure WebSphere Portal later

  1. Make the plans

  2. Verify that the system meets all hardware and software requirements.

  3. Prepare the iSeries machine

  4. Install WebSphere Portal

  5. When the Install only option finishes, the install image files are merely copied from the Setup CD to the hard drive. At this point the CD is no longer required, and we can continue installation remotely by starting install400.bat from a mapped drive on a Windows PC, or locally by starting the install.sh file on the iSeries machine. You must choose the Install and configure option of installation scenario 1 to complete the installation of WebSphere Portal.

  6. At the completion of the installation program, the Cloudscape database is installed and can be used if you are installing a test environment. But for a production environment, use the DB2 for iSeries database, which is native to iSeries. We can start with this file to complete the modification and configuration steps to set up WebSphere Portal to work with DB2 for iSeries, see Configure databases.

    • Database configuring is not required when installing on a secondary node in a cluster.

    • If you choose to transfer from Cloudscape to DB2 for iSeries, there is no option to transfer back to Cloudscape.

  7. Configure WebSphere Portal for use with the HTTP server

  8. Document Rendering on i5/OS

  9. Add any optional WebSphere Portal components not included in this installation scenario.

  10. Install IBM Tivoli License Compliance Manager.

    While it is installable, IBM Tivoli License Compliance Manager is not supported at this time on i5/OS.

  11. Verify and launch WebSphere Portal .

 

 

Optional components

The following components are optional, and can be added after completing one of the previous installation scenarios.

Refer to the following instructions for each component: