Chapter 3: Technology Options

 < Day Day Up > 



This chapter discusses the technology options available for the secure portal implemented by WebSphere Portal and Tivoli Access Manager for e-business. The first section describes the technology choices made in the product mappings and software components, primarily for WebSphere Portal. The second section describes the security-related technology choices and considerations.

3.1 Software components

The installation and configuration process for WebSphere Portal has been significantly changed in version 5.0 to give customers more flexibility and control. The new process is designed for you to get WebSphere Portal up and running quickly first. The installation program has been simplified and now simply installs the following components:

  • WebSphere Portal

  • WebSphere Application Server (including IBM HTTP Server)

  • IBM Cloudscape database

Thus, you can now install an initial portal without much planning or much input during installation.

Configuration tasks are provided to get WebSphere Portal working in your specific environment. The configuration tasks are commands that you run to customize WebSphere Portal to use different software, for instance using a database other than the default IBM Cloudscape database or using an LDAP server for the user registry. You can use configuration tasks to alter the portal configuration without having to reinstall the product. Thus, the configuration of WebSphere Portal V5.0 is designed to evolve over time.

Configuration tasks are based upon Ant, an open-source Java-based build tool available from The Apache Software Foundation.

The following section describes the choices made in selecting the software components for WebSphere Portal.

3.1.1 WebSphere Portal

For the secure portal, we will not be implementing any team collaborative features such as instant messaging. WebSphere Portal Enable for Multiplatforms is sufficient for our solution.

Note 

The core of WebSphere Portal is the same in both Enable and Extend editions. An installation of WebSphere Portal Enable for Multiplatforms can be upgraded to Extend later on, for example by using configuration tasks.

Database

A database is required for WebSphere Portal. It uses the database to store portal configuration and user information. By default, WebSphere Portal installs and uses an IBM Cloudscape database. IBM Cloudscape is well suited to basic portal environments. This is sufficient for our solution.

Note 

WebSphere Portal's use of the IBM Cloudscape database is not intended for deployment in a production environment. It is designed more as a staging area as you install and configure your portal. WebSphere Portal will integrate with other database software and use of a more robust database, such as DB2, is recommended. Refer to the IBM WebSphere Portal V5 Handbook, SG24-6098, Section 4.5, "Migrate database from Cloudscape to DB2" for more details.

Note 

The IBM Cloudscape database used by WebSphere Portal is separate from the IBM Cloudscape database installed and used by the underlying WebSphere Application Server for its Samples Gallery.

User registry

The user registry contains the database of users and groups for WebSphere Portal. It is often used for security purposes, such as authentication and authorization. WebSphere Portal relies on the underlying WebSphere Application Server for its user registry services. WebSphere Application Server supports several options for user registries:

  • Local OS - from the local operating system of the WebSphere Application Server

  • LDAP - from an LDAP server

  • Custom - from a custom-implemented user registry

By default, WebSphere Portal uses its IBM Cloudscape database as a WebSphere Application Server custom user registry.

In order to integrate WebSphere Portal and Tivoli Access Manager for e-business, they must know the same users and groups. In our solution, we will share the user registry between the two software components by configuring them to use the same LDAP server. An LDAP server is the only user registry option that is common to both WebSphere Portal and Tivoli Access Manager for e-business.

IBM Directory Server

WebSphere Portal V5.0 ships with IBM Directory Server V5.1. However, WebSphere Portal V5.0 will support IBM Directory Server V4.1.

Tivoli Access Manager for e-business V4.1 ships with IBM Directory Server V4.1. However, patch 6 for Tivoli Access Manager for e-business introduces compatibility support for IBM Directory Server V5.1.Unfortunately, TAM V4.1 still uses the V4.1 directory client and there is no way to mix them if they are on the same machine. If you had a dedicated LDAP server machine, you could use IDS V5.1. Therefore, IBM Directory Server 4.1 is sufficient for our solution.

Note 

IBM Directory Server V5.1 may be used to take advantage of new features such as the redesigned Web administration GUI.



 < Day Day Up > 



Secure Portal. Using Websphere Portal V5 and Tivoli Access Manager V4. 1
A Secure Portal Using Websphere Portal V5 and Tivoli Access Manager V4.1
ISBN: 073849853X
EAN: 2147483647
Year: 2003
Pages: 73
Authors: IBM Redbooks

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net