wpf overview ent

7/29/2019 Wpf Overview Ent

1/59

M WebSphere Portal for Multiplatforms Version 5.0.2

verview Guide

st updated on May 12, 2005

Copyright 2000, 2005 International Business Machines Corp.

roduct overview

What's new

Product description

Key featuresVersatile framework

Customization

Portlets

Content Management

Application integration

Mobile portals

Security

Collaboration

Components overview

Accessibility features

About this information

Resources and support

Resources for learning

dditional resources

Resources for learning

Resources and support

Directory structure

lossary

rademarks

1


2/59

roduct overview

his section provides overview information about WebSphere Portal. Included in this section is a list ofew features, a description of the product, an overview of its main components, and information abouthat each component provides to the overall solution. Also, information about the Information Center aks to additional information are provided.

elated information

q What's new

q Product description

q Key features

q Components overview

q Accessibility features

q About this information

q Resources and support

q Resources for learning

2


3/59

What's new

ebSphere Portal includes the following new features:

q Support for new platformsIn addition to the platforms that were supported by WebSphere Portal V5, you can now install th

version of WebSphere Portal on the following platforms:r Microsoft Windows 2003r RedHat Linux for zSeries 7.2 2.4 Kernelr Solaris 9r SuSE SLES for S/390 8 2.4 Kernel

See the Supported Hardware and Software topic for information on supported operating systemq Support for WebSphere Application Server V5.0.2

WebSphere Application Server V5.0.2 is required for this version of WebSphere Portal.q Portal Toolkit support for WebSphere Studio V5.1

The Portal Toolkit that is shipped with this version of WebSphere Portal now supports WebSphStudio V5.1 for portal development.

q Support for Lotus Sametime V3.1You can now use instant messaging and online awareness, based on Lotus Sametime V3.1technology.

q Try Lotus Workplace Web Content Management Version 1.1Lotus Workplace Web Content Management integrates with IBM WebSphere Portal, Lotus DomDocument Manager, Lotus Workflow, and IBM DB2 Content Manager. A restricted use license provided with this version of WebSphere Portal. For more information see http://www.lotus.com

products/product5.nsf/wdocs/homepage.

elated information


q Key features






3
http://www.lotus.com/products/product5.nsf/wdocs/homepagehttp://www.lotus.com/products/product5.nsf/wdocs/homepagehttp://www.lotus.com/products/product5.nsf/wdocs/homepagehttp://www.lotus.com/products/product5.nsf/wdocs/homepage


4/59

roduct description

ebSphere Portal overview

ebSphere Portal consists of middleware, applications (called portlets), and development tools for

ilding and managing secure business-to-business (B2B), business-to-consumer (B2C), and businesmployee (B2E) portals. A portal is a Web site that provides users with a single point of access to Webased resources by aggregating those resources in one place and by requiring that users log in only tortal itself, and not to each portlet they use. WebSphere Portal can deliver Web content to WAP-enab

evices and i-Mode phones, and to various Web browsers.

s an administrator, you can customize WebSphere Portal to meet the needs of your organization, used user groups. You can adapt the look and feel of the portal to fit the standards of your organization customize page content for users and groups in accordance with business rules and user profiles.

sers, such as business partners, customers, or employees, can further customize their own views of rtal. Users can add portlets to pages and arrange them as they want and control portlet color schem

y aggregating portlets in one place and giving users the power to customize their own desktops,ebSphere Portal gives users a means for doing business efficiently and with high satisfaction.

ortlets are central to WebSphere Portal. As special reusable Java servlets that appear as defined reg portal pages, portlets provide access to many different applications, services, and Web content.ebSphere Portal ships a rich set of standard portlets, including portlets for displaying syndicated con

ansforming XML, and accessing search engines and Web pages. Portlets for accessing Lotus Notes,crosoft Exchange, and instant messaging are also included. Several third-party portlets are alsoailable. Examples include Enterprise Resource Planning (ERP) and Customer Relationshipanagement (CRM) portlets. WebSphere Portal also ships an API that portlet developers can use to

eate custom portlets.

ebSphere platform overview

ebSphere(R) is infrastructure software for dynamic e-business,elivering a proven, secure, and reliable software portfolio.

oviding comprehensive e-business leadership, WebSphereolves to meet the demands of companies that are faced withallenging business environments, such as the need forcreasing operations efficiencies, strengthening customer loyalty,

d integrating disparate systems.

eading customers toward dynamic e-business means WebSphereovides answers to these challenging business environments.ebSphere is the only e-business platform that can provideerything you need to build, deploy, and integrate your e-siness, including: Foundation and Tools, Business Portals, Business Integration, and Transaction

ervers and Tools.

ogether, these facets of the WebSphere software platform close the gap between business strategy a

4


5/59

ormation technology, allowing you to create and operate a dynamic e-business.

xplore the WebSphere pyramid to discover how each side can help power your business and drive yoccess.

elated information

q What's new

q Key features






5


6/59

ey features

his section provides links to descriptions of key features that expand the range, power, and usability oe entire solution.

q Versatile framework

q Customizationq Portlets

q Content management

q Application integration

q Mobile portals

q Security

q Collaboration

elated information

q What's new







6


7/59

ersatile framework

ebSphere Portal provides users a consistent view of portal applications and allows users to defineecific sets of applications that are presented in a single context. Depending on the requesting devicee rendering of this application set has to vary to fulfill the requirements of the device. The tasks of thegregation, which are repeated with each request coming from the device, are:

q Gather information about the user, the device, and the selected language.q Select the active portlets from the set of applications to which the user has access.q Aggregate the output of the active portlets into a coherent, usable display.

ebSphere Portal also provides the ability to create a custom navigation model, which includes suchatures as:

q Multilevel navigationq Customized themes and skinsq Custom navigation - navigation tree can be contributed to by portlets themselvesq Custom arrangement of portlets (and thus content) on a page

nother aspect of the versatile framework is the ability to personalize a user's portal experience, usingontent spots" that render subscribed content (from WebSphere Portal content publishing) based on ter and user's role in the portal.

elated information

q Key features

7


8/59

ustomization

ustomizing the user's portal experience is one of the main goals of WebSphere Portal. To achieve thebSphere Portal provides user and administrative portlets for customizing content and the look andyout of pages. In addition, tools are provided that allow subject matter experts to personalize contente needs and interests of each site visitor.

his topic is divided into the following subtopics:

q Customizing portal pages

q Personalization

q Universal access

q Related information

ustomizing portal pages

sers can have one or more custom pages and access each one through a different portal page. A pan contain a group of pages that is organized for a specific purpose. Each page can have a different sportlets. Depending on authorizations, users can change the look and feel of their pages by using skd page layouts. Also, page navigation hierarchy is tree-based, allowing any depth of nested pages.

he contents of each page can be set by the user or by an administrator. Administrators can specify thrtain portlets be required, so that users are unable to move them or to remove them from the pages.

ach page can have its own color scheme and column layout.

sers now have the ability to rearrange portlets on a page right on the page itself, using the Show Tooption. Clicking this option exposes controls on the page around each portlet, allowing the user to adju

e position of the portlet on the page, and add or remove portlets from the page.

Cascading authorization

The permission to grant or revoke access to customize a page or portion of a page can bedelegated from a portal administrator to other portal administrators or users. The right tomodify a page can be determined by the administrator. Administrators can control the editauthority that other administrators have on a page and its contents. This is best explainedthrough an example.

The first administrator can determine that a page will have two columns and not allow thecolumn layout to be modified by any other administrators.

Another administrator with lesser access cannot modify the column layout but can addportlets to these columns. This administrator adds a company news portlet to column oneand a stock portlet to column two. This administrator wants these portlets to be available toeveryone and does not want them removed. However, additional portlets can be added tothe columns. Therefore, the portlets are locked and cannot be removed by otheradministrators with lesser access.

8
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


9/59

Skins and themes

WebSphere Portal uses Java Server Page (JSP) templates, cascading style sheets, andimages to define the look of pages. These can be modified to control visual aspects of theportal, perhaps to add company-specific brand elements or to achieve a different colorscheme and visual style. The system for defining color themes and portal skins supportsmultiple skins per theme, additional branding elements, navigation styles, and dynamic,browser-independent cascading style sheets.

Skins and themes can be applied to a page, not only to the overall portal. Different skinscan be applied individually to portlets as well, so that the appearance of a portal can be fine-tuned to meet any user need. By using a different theme for each page, a single portalinstallation can give the appearance of supporting many "virtual" portals.

Branding elements

All of the visual elements of WebSphere Portal, including the masthead, the navigationareas, graphics, portlet title areas, and style sheets, can be changed to give the portal acustom look. Standard file formats, such as JPEG, GIF, CSS, and JSP files, are used for

defining the look and layout of your portal.

The structure of the WebSphere Portal component installation folder contains foldersnamed "skin" and "theme", with folders "html", "wml", and "chtml". These folders containmost of the files that are used for defining the basic structure of the portal home page, itscolor schemes, and portlet decorations. Portal designers can copy these folders and modifytheir contents to create a custom look and feel. The theme administration portlet registersthe new files.

ersonalization

he WebSphere Portal content publishing personalization component selects content for users, based ormation in their profiles and on business logic. WebSphere Portal content publishing provides facilitat allow subject matter experts to select content that is suited to the needs and interests of each sitesitor. These Web-based tools help companies quickly and easily leverage content that is created bysiness and subject matter experts. WebSphere Portal content publishing involves three basic

ersonalization components:

q User Profile: information about users of the site, including user attributesq Content Model: defines attributes about content, such as product descriptions, articles, and othe

informationq Matching Technology: engines that match users to the right content; includes filtering, rules,

recommendation engines, or combinations of all three.

he WebSphere Portal content publishing and WebSphere Portal components share a common userofile and content model. The model is based on the WebSphere resource framework interfaces classhis means that personalization rules can easily be added to portlets to select portal content and targeWebSphere Portal registered users.

he basic steps involved in personalization involve classifying site visitors into segments and thenrgeting relevant content to each segment. Business experts create the rules for classifying users and

9


10/59

lecting content, using Web-based tools.

ebSphere Portal content publishing also includes a recommendation engine that provides collaboratering capabilities. Collaborative filtering uses statistical techniques to identify groups of users withmilar interests or behaviors. Inferences can be made about what a particular user might be interestedased on the interests of the other members of the group.

so included with WebSphere Portal content publishing are new campaign management tools.ampaigns are sets of business rules that work together to accomplish a business objective. For exam

HR manager might want to run a campaign to encourage employees to enroll in a stock purchase phe HR manager would define a set of rules shown to accomplish this business objective. Campaignsave start and stop dates and times and can be e-mail- and Web-page based. Several campaigns canmultaneously and can be prioritized.

plicit profiling services can collect real-time information about site visitor actions and then constructersonalization business rules using this data. To analyze the effectiveness of the site and itsersonalization strategies, the server provides reports for the business owner of the site. This helps thempany measure the effectiveness of the business rules and campaigns in achieving its objectives.

he WebSphere Personalization component selects content for users, based on information in theirofiles and on business logic. WebSphere Personalization provides facilities that allow subject matterperts to select content that is suited to the needs and interests of each site visitor. These Web-basedols help companies quickly and easily leverage content created by business and subject matter expeebSphere Personalization involves three basic components:

q User Profile: information about users of the site, including user attributesq Content Model: defines attributes about content, such as product descriptions, articles, and othe

informationq Matching Technology: engines that match users to the right content; includes filtering, rules,

recommendation engines, or combinations of all three.

he WebSphere Personalization and WebSphere Portal components share a common user profile andntent model. The model is based on the WebSphere resource framework interfaces classes. Thiseans that personalization rules can easily be added to portlets to select portal content and target it toebSphere Portal registered users.

he basic steps involved in personalization involve classifying site visitors into segments and thenrgeting relevant content to each segment. Business experts create the rules for classifying users andlecting content, using Web-based tools.

ebSphere Personalization also includes a recommendation engine that provides collaborative filterin

pabilities. Collaborative filtering uses statistical techniques to identify groups of users with similarerests or behaviors. Inferences can be made about what a particular user might be interested in, bas the interests of the other members of the group.

so included with WebSphere Personalization are new campaign management tools. Campaigns are business rules that work together to accomplish a business objective. For example, an HR managerght want to run a campaign to encourage employees to enroll in a stock purchase plan. The HRanager would define a set of rules shown to accomplish this business objective. Campaigns have stad stop dates and times and can be e-mail- and Web-page based. Several campaigns can run

multaneously and can be prioritized.

10


11/59

plicit profiling services can collect real-time information about site visitor actions and then constructersonalization business rules using this data. To analyze the effectiveness of the site and itsersonalization strategies, the server provides reports for the business owner of the site. This helps thempany measure the effectiveness of the business rules and campaigns in achieving its objectives.

niversal access

he system of page templates, themes, skins, and portlet rendering is fully enabled for internationaliza

d accessibility by people with disabilities. For globally accessible portals, WebSphere Portal searcher and selects the proper JSP pages, based on the target browser and its settings for language anduntry.

elated information

q Key features

11


12/59

ortlets

ortlets are a central part of WebSphere Portal. Portlets are small portal applications, usually depictedsmall box in the Web page. Portlets are developed, deployed, managed, and displayed independentldministrators and users compose personalized portal pages by choosing and arranging portlets, resucustomized Web pages.

ebSphere Portal ships a rich set of standard portlets. See Installed portlets, under Working with portlr a list of shipped portlets. Then, for the most up-to-date information on portlets, including the latestrtlets that are available for download, visit the IBM Workplace Solutions Catalog at the WebSphere

ortal Web site.


q Portlet applications

q Portlet API

q Portlet communications

q Discoverable services

q Related information

ortlet applications

ortlets are more than simple views of existing Web content. A portlet is a complete application, followstandard model-view-controller design. Portlets have multiple states and view modes, plus event andessaging capabilities.

ortlets run inside the portlet container of the WebSphere Portal component, similar to the way a servlns on an application server. The portlet container provides a run-time environment where portlets arestantiated, used, and finally destroyed. Portlets rely on the WebSphere Portal infrastructure to accesser profile information, participate in window and action events, communicate with other portlets, accemote content, look up credentials, and store persistent data.

enerally, portlets are administered more dynamically than servlets. For example, portlet applicationsnsisting of several portlets can be installed or removed while the WebSphere Portal component isnning. The settings and access rights of a portlet can be changed by an administrator while WebSphortal is running, even in a production environment.

ortlet modes allow a portlet to display a different user interface, depending on the task that is requirede portlet. A portlet has several modes of display that can be invoked by icons on the portlet title bar:ew, Help, and Edit.

portlet is initially displayed in its View mode. As the user interacts with the portlet, the portlet can dispsequence of view states, such as forms and responses, error messages, and other application-speciates. Help mode provides user assistance. Edit mode provides a page for users to change portletttings. For example, a weather portlet might provide an Edit page for users to specify location. Usersust be logged in to WebSphere Portal to access Edit mode.

12
http://www7b.software.ibm.com/wsdd/zones/portal/catalog/index.htmlhttp://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://www7b.software.ibm.com/wsdd/zones/portal/catalog/index.html


13/59

ach portlet mode can be displayed in normal, maximized, or minimized states. When a portlet isaximized, it is displayed in the entire body of a page, replacing the view of other portlets. When a porminimized, only the portlet title bar is displayed on the page.

ortlet API

ortlets are a special subclass of HttpServlet, with properties that allow them to easily plug in to ann in WebSphere Portal. Portlets are assembled into a larger page, with multiple instances of the sam

rtlet displaying different data for each user. Portlets rely on WebSphere Portal infrastructure to acceser profile information, participate in window and action events, communicate with other portlets, accemote content, look up credentials, and store persistent data. The Portlet API provides standarderfaces for these functions.

he portlet API defines a common base class and interfaces for portlets to cleanly separate the portletom WebSphere Portal infrastructure. In most respects, the portlet API is an extension of the servlet Acept that it restricts certain functions to a subset that makes sense for portlets running in the contextrtal. For example, unlike servlets, portlets cannot send errors or redirects as a response. This is donly by WebSphere Portal itself, which controls the overall response page.

sually, many portlets are invoked in the course of handling a single request, each one appending itsntent to the overall page. Some portlets can be rendered in parallel, so that WebSphere Portalsembles all the markup fragments when all the portlets finish or time out. Portlets that are notnsidered thread-safe are rendered sequentially.

he markup fragments that portlets produce can contain links, actions, and other content. The Portlet Aefines URL rewriting methods that allow portlets to transparently create links, without the portlet need

know how URLs are structured in the particular portal.

ortlet communications

ebSphere Portal provides a way for portlets to communicate with each other. In a production portal,rtlet communication could be used to copy common data between portlets. This saves redundant typ

r the user and makes WebSphere Portal easier to use. For example, one portlet might displayormation about accounts while a second portlet displays information about transactions that havecurred for one of the accounts over the last 30 days. To do this, the transactions portlet needs to obte corresponding account information when it displays the transaction details.

his is accomplished by communication between the two portlets, using portlet actions and portletessages. In this example, the account portlet creates a portlet action and encodes it into the URL thandered for displaying transactions. When the link is clicked, the action listener is called, which then

nds a portlet message to send the necessary data.

sing this event and message feature help unify portlet applications that access disparate back-endpplications. WebSphere Portal provides a feature called cooperative portletswhich dynamically bindsrtlets on a page for data exchange. See Cooperative portlets for more details.

scoverable services

he portlet API provides an interface to enable dynamic discovery of available services. Each service igistered in a portal configuration file and is accessed from the PortletContext.getService()

13
http://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wps/wpsc2a.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wps/wpsc2a.html


14/59

ethod, which looks up the factory for the service, creates the service, and returns it to the portlet. Thiakes services available to all portlets without having to package the service code with the portlet.

ebSphere Portal provides discoverable services for its credential vault, for managing persistent TCPnnections, and for managing the WebSphere Portal content repository. New services can beplemented by portal developers, such as search, location, notification, content access, or mail servic

ortlets can also be grouped together in a portlet application. Portlet applications are distributed andeployed using Web archive files (WAR). There are portlet-specific extensions to the standard Webpplication deployment descriptor.

ebSphere Studio Site Developer provides an excellent development, test, and debug environment fortlet applications. You can implement the Java classes for portlet classes and test and debug the Jade. WebSphere Studio Site Developer also provides tools for creating Java Server Pages, HTML paages, and other related portal resources. In WebSphere Studio Site Developer, the portlet can be

ackaged into a WAR file and easily deployed to the run-time server.

elated information

q Key features

14


15/59

ontent management

ontent management is an important part of WebSphere Portal. When companies deploy portals, theymarily focused on content aggregation, rapid and large-scale deployment, search, and delivery of

ersonalized content. WebSphere Portal meets content delivery needs by supporting syndicated conteintegration with Web content management systems, and by providing built-in content organizing

ortlets.


q Delivering syndicated Web content

q Managing Web content

q Document Manager

q WebSphere Portal content publishing

q Search

q Federated search

elivering syndicated Web content

yndicating content is about delivering fresh, personalized, and filtered content from multiple contenturces to users. Typically, this content is news, finance, and entertainment. WebSphere Portal partneth many popular content providers. Content syndication helps to automate the publishing of electronitalogs and other internal information and to make this information available to users through enterpr

ortals.

popular and useful format for syndicated news and entertainment is Rich Site Summary (RSS). Cont

n be published directly from the content management system into Rich Site Summary and Openontent Syndication (OCS) channels. The example portlet org.apache.jetspeed.portlets.RSSPortletows how this can be done. This self-syndication defines a procedure for editing, managing, andblishing sources of content.

anaging Web content

anaging Web content means creating, approving, and publishing Web content from content creators.he steps of this process include defining content types, roles, publication options, destinationecifications, and workflow processes. Although each of the content management products that are in

e marketplace today works differently, they are all designed to create, maintain, and publish collectiodocuments that can be made available to users through WebSphere Portal.

o illustrate how this can be done, WebSphere Portal includes integration kits that illustrate steps forblishing RSS content from several Web content management products. Content contribution and

pproval operations of the Web content management system can also be accessed through portlets the provided by their respective companies. These portlets provide a user interface for various aspectsntent management, such as content submission, workflow management, content approval, and stagpublishing.

15
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


16/59

ocument Manager

ebSphere Portal includes the Document Manager portlet application for contributing and sharing

cuments between users. Document Manager provides a simple method for storing, navigating, viewd searching documents and other content.

ocument Manager helps users organize the content they have seen, want to read, or want to share.ocuments are organized into folder hierarchies. Document Manager maintains properties and attribut

documents, handles conversion of documents to other formats, and serves as an organized repositor documents of any format. Documents that are maintained in Document Manager can be searched bing the Document Manager built-in search service. Authorized users can control document modificatrough a workflow process.

ebSphere Portal content publishing

sers can contribute content to a Web site on a regular or occasional basis. This includes business useating template-driven content such as press releases or product information and graphic artists cread editing artwork with their favorite tools. WebSphere Portal content publishing supports content

ntribution by means of templates (forms). It also supports the contribution of files such as images,TML, or JSPs that are created and edited using many editing tools.

ebSphere Portal content publishing provides a Web browser interface that enables users to contribuntent to a site in an easy-to-use, quick, and controlled manner. This allows large teams to workgether, collaborating where necessary, but with enough isolation that they are not constantly trippinger each other's changes. WebSphere Portal content publishing tools can be used to manage contenat is served through the Portal Content Organizer or other portlets within WebSphere Portal. It is alsossible to categorize content and to schedule importing syndicated content.

ebSphere Portal content publishing manages the task lists of each user, maintains access control ov

hat content each user can see or change, and coordinates the approval and publishing process whene content is ready. Lotus Workflow Architect is provided to graphically design one or more processesach step in the process is assigned to a specific user role. When the process is instantiated, a work itput on the work queue of each person in the specified role. One of the users claims that activity, andter that user completes the step, the work is put on the next work queue as defined in the workflow.

earch

ebSphere Portal provides integrated text search capabilities, including a search portlet, a crawler, anocument indexer. The search service can search the portal document repository and Internet content

he WebSphere Portal built-in search engine is optimized for full-text searching of small and medium-zed collections where precision is essential. It efficiently applies state-of-the-art search algorithmsoducing high-quality search results.

he search engine supports free-text queries, with query assistance and query word completion. Searceries use advanced query operators (+ or -) to indicate keywords that must be in the document orywords that must not be in the document. The search engine can search documents in any languaged supports synonyms and stop-word lists. Search results include document summarization and searsults clustering.

o prepare for searching, the search engine builds a full-text index in order to search documents that a16
http://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/pdm_info.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/cm_intr.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/cm_intr.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/pdm_info.html


17/59

ored in the local file system. The indexer supports multiword indexing for clarity and high precision. Tdex can be compressed, and lossy compression is allowed for situations where the size of the indexeeds to be limited. Administration portlets are provided for creating, updating, and managing the inde

ederated Search

ortlets using IBM Lotus Extended Search and IBM Enterprise Information Portal search can access agregate other search engines and indexes in a distributed fashion. Customers seeking support for la

cument collections or for searching a wide range of document types and data sources should considing Lotus Extended Search or EIP.

elated information

q Key features

17


18/59

pplication integration

portal provides access to content, data, and services that are located throughout the enterprise. Thervices not only include predefined connectors and portlets, but also tools for creating additionalnnectors and portlets.

nterprise resource planning (ERP) and customer relationship management (CRM) systems are excelndidates for portlets because efficient, personalized access to these functions provides measurableturn on your portal investment. IBM provides connectors to enterprise applications, using the Javaonnector Architecture (JCA). In addition, Application Portlet Builders are provided for building portletsat interact with other enterprise applications.


q Standard Java connectors

q Application Portlet Builders

andard Java connectors

CA is a standard architecture for integrating Java 2 Enterprise Edition (J2EE) applications with enterpormation systems that are not relational databases. Each of these systems provides native APIs forentifying a function to call, specifying its input data, and processing its output data. The goal of the JCto provide an independent API for coding these functions.

CA also defines a standard Service Provider Interface (SPI) for integrating the transaction, security, annection management facilities of an application server with those of a transactional resource manag

hus, JCA is a standards-based approach to managing connections, transactions, and secure access

terprise application systems. IBM JCA connectors provide access to systems such as SAP, PeopleSD. Edwards, Oracle, CICS, IMS, and Host-on-Demand. Leveraging its CrossWorlds acquisition, IBMans to develop and integrate JCA connectors to many other systems.

ebSphere Studio Site Developer provides a complete development and unit test environment forpplications that use JCA connectors, Web services, and microflows. WebSphere Studio Site Developols include support for Web Service Definition Language (WSDL), developer versions of the connecte Web Services Invocation Framework (WSIF), and the microflow engine.

pplication Portlet Builders

he Application Portlet Builder enables users to create portlets that can access and manipulate data interprise application without requiring programming knowledge of the system. By selecting business

bjects that are available from the enterprise application, users can specify which data fields should besplayed in your portlet. When the portlet is created, the portlet can be made available to portal users.

wo builders are included with this edition of WebSphere Portal, Domino Builder and SQL Builder. Forore information, go to the IBM Workplace Solutions Catalog.

elated information

18
http://www7b.software.ibm.com/wsdd/zones/portal/catalog/index.htmlhttp://www7b.software.ibm.com/wsdd/zones/portal/catalog/index.html


19/59

q Key features

19


20/59

obile portals

ext-generation portals will be accessible through more than desktop browsers. Access through mobilevices is becoming increasingly important. WebSphere Portal supports mobile devices by generatingages in any markup language. Three are officially supported: HTML, for desktop computers and someersonal digital assistants; WML, for WAP devices, which are typically mobile phones; and cHTML, for

obile devices in the NTT DoCoMo iMode network. Support for other markup languages is easy to add

sers can customize a unique home page for each device, selecting content and applications that areost useful on the device. When the home page is requested, the page is produced by detecting the tydevice that is making the request and then by assembling the portlets, each of which renders itsntents in the appropriate markup language.

hen a user customizes the home page for a device, the portlet selection list shows only the portlets tn produce markup that is appropriate for that device. Thus, the list of available portlets for each devi

epends on what the portlets can actually do.

ome portlets might be available for all supported devices, while others might be available only for angle device. The user interface design of each portlet also varies from device to device, so that theer's experience can be optimized on each device. Thus, the user's home page and each of the portleght appear very different on a mobile phone from how they appear in a desktop browser.

upporting new devices: content transformation

sing Transcoding Technology imbedded within this version of WebSphere Portal, portlets that normaoduce HTML content can be made to automatically render WML and cHTML as well. By defining the

anscoding PortletFilter on a portlet, the portlet HTML output can be converted to WML or cHTML,

epending on the device that is making the request. See the Transcoding Technology section for moreetails.

upporting new devices: clients and markups

he WebSphere Portal page aggregation subsystem supports several markup languages and recognizrtain browsers and mobile device user agent signatures, all out of the box. The framework is easy totend to support additional markups or new devices. To support new browsers and devices, add newarkup and clients using the corresponding administration portlets.

elated information

q Key features

20


21/59

ecurity

his topic highlights some of the security features that applications and portal administrators can exploetter protect the valuable information of the portal assets.

q Member services

q Administrationq Authentication

q Identifying the User

q Third Party Authentication Servers

q Single signon

q Credential Vault

q Persistent Connections

q Java Security

q Authorization

q Delegated Administrationq Related information

ember services

entralized administration of user identities, credentials, and permissions is desirable in manyvironments. The portal server includes facilities for defining portal users and managing user accesshts. The user and group subsystem includes Web pages where users can register and manage thei

wn account information, administration portlets for managing user accounts and group information, plpository that stores all the information about portal users. It provides services to create, read, update

d delete users or groups in the repository. User profile information includes general information suche name of the user and user ID, plus preference information such as news topics of interest, preferrenguage, and so on. A user might be a member of one or more groups, and groups can contain otheroups.

he default set of user profile attributes is based on the inetOrgPerson schema, which is supported byost LDAP directories. The user repository might consist of multiple data sources. By default, thepository consists of two data sources: it is a combination of a database and a directory server. The

atabase might be any of the databases that are supported by WebSphere Portal. Any one of severalDAP directory products are supported, including the Netscape (iPlanet) Directory Server, Microsoft Ac

rectory, Novell eDirectory, Lotus Domino, and IBM Directory Server.he mapping of user profile attributes to LDAP object classes is defined using in the file wms.xml. Thie specifies the names of the various data repositories and how they are navigated to retrieve user anoup information. These settings are configured differently for each supported LDAP directory; if you wtry using a directory that is not supported, these values would need to be set appropriately for that

rectory server.

he file attributeMap.xml specifies the details of how each attribute is mapped to the LDAP directodatabase. This mapping file also includes metadata about each attribute such as its data type, whets required, whether it can have multiple values, and so on.

21


22/59

dministration

dministration of users and groups can be performed by users themselves ("self care") or by portalministrators. The portal server includes forms for registering new users and administration portlets fo

pdating user and group information.

he registration and self-care forms are easily modified to accommodate new attributes. You can add

ata entry fields to the form, matching the field identifiers with the new attribute names. The enrollmenrvlet will automatically store the new data in the corresponding user attributes. The WebSphere Portformation Center includes more information about customizing the implementation of the user reposigistration and self-care pages, and data validation classes.

uthentication

uthentication is the process of establishing the identity of a user. Usually, the portal server uses thethentication services that are provided by WebSphere Application Server. Another option is to use ard-party authentication server (such as Tivoli Access Manager, WebSeal, or Netegrity SiteMinder) th

as a trusted association with the application server.

entifying the User

ebSphere Portal uses form-based authentication. Form-based authentication means that a user isompted through an HTML form for the user ID and password for authentication when trying to accesse portal. The portal server requests the application server to validate the authentication informationainst a Lightweight Directory Access Protocol (LDAP) user registry.

ebSphere Application Server uses Lightweight Third Party Authentication (LTPA) as the authenticatiechanism. A Common Object Request Broker Architecture (CORBA) credential is used to represent

thenticated users and their group memberships. When a user tries to access a protected resource, tpplication server intercepts the request and redirects the request to the login form. This form posts theer ID and password to the portal that requests the application server to authenticate the user. If the un be authenticated, a valid CORBA credential is created and an LTPA cookie is stored on the user'sachine.

hird-party Authentication Servers

your system uses another third-party authentication server, trust needs to be established between thoxy and WebSphere Application Server. This is done using a Trust Association Interceptor (TAI)

odule, which converts security information that is specific to the authentication proxy into a format than be handled by the application server. The supported authentication mechanism depends on thepabilities of the third-party product.

hen a user tries to access the portal, the third-party authentication proxy intercepts the request andallenges the user to authenticate. After a successful login, the original user request, along withditional security information in the request header, is passed to the application server. The format anntent of this information is vendor specific. WebSphere Application Server uses the TAI module (thatecific to the third-party product) to extract the necessary security information from the request heade

22


23/59

AI modules for IBM Tivoli Access Manager and Netegrity SiteMinder are packaged with the portal serl editions). The WebSphere Application Server InfoCenter includes information about creating custo

AI modules for other third-party reverse proxy servers.

ngle Sign-On

he portal server provides comprehensive single signon (SSO) support. Users want to be able to log oly once, and be known to the different parts of the portal server with the same consistent user

edentials. Users should not be asked to do multiple logons simply because they accessferent portal applications.

he portal server supports single signon realms using WebSphere Application Server and authenticatiooxies. This means that the user needs to log on only once to gain access to all enterprise applicationat are installed within the single signon realm.

he WebSphere Application Server uses Lightweight Third Party Authentication (LTPA) tokens to provngle signon. When a user is authenticated, the portal server creates an LTPA single signon cookientaining the authenticated user credential. This encrypted cookie conforms to the format that is usedebSphere Application Server and can be decrypted by all application servers in the shared domain,

ovided they all have the same cipher key. This cookie enables all servers in the cluster to access theer credentials without additional prompting, resulting in a seamless single signon experience for theer. To benefit from the LTPA method of single signon, the browser of the user must support cookies

ave its support for session cookies enabled.

redential Vault

any portlets need to access remote applications that require some form of user authentication. Forcessing applications outside the portal realm, portal server provides a credential vault service thatrtlets can use to store user ID and password (or other credentials) for a user login to an application.

ortlets can use these on behalf of the user to access remote systems. The credential vault supportsher local database storage or IBM Tivoli Access Manager for secure storage and retrieval of credent

ortlets obtain credentials by obtaining a CredentialVaultPortletService object and calling its getCredeethod. With the returned credential, there are two options:

1. Use passwords or keys from a passive credential, passing them in application-specific calls.Portlets that use passive credentials need to extract the secret out of the credential and do all thauthentication communication with the back-end application.

2. Call the authenticate method of an active credential. Active credential objects hide the credentiasecret from the portlet, with no way to extract it out of the credential. Active credentials provide

additional methods to perform the authentication.he latter case allows portlets to trigger authentication to remote servers using basic authorization, SSent authentication, digest authentication, or LTPA without knowing the credential values. Using activedentials means that the portal authenticates on behalf of the portlet, and the portlet can simply use tpen connection. While this might not be possible for all cases, it is the preferred technique. For secureansmission of data, portlets can request a secure session (HTTPS) for accessing Web applications.

ersistent Connections

23


24/59

ortlets that depend on remote connections require some way of maintaining that connection as usersavigate through the portal. The portal provides a persistent back-end connection service that maintainCP/IP connections across page changes. Some remote applications use forms-based logins and storokies during the login form processing. The HttpFormBasedCredential can be used for handling thesrm-based logins and will store all the cookies that are returned as a result. For subsequent calls, thertlet can then ask the credential for an authenticated connection. This gives an HTTP connection wit

ese cookies already set in the header. This way, portlets can maintain persistent, secure back-endnnections.

ava Security

he portal server implements the Java Authentication and Authorization Service (JAAS) architecture.AAS provides a means for authenticating subjects and for providing fine-grained access control. JAASart of the standard Java security model; it gives applications independence from the underlyingthentication and authorization mechanisms that are being used. JAAS performs login and logout

perations using a modular service provider interface. Credentials that are established through the porrver JAAS login modules include CORBA credentials, user and group distinguished names, user ID

assword, and LTPA tokens. In a distributed J2EE environment, portlets can use the JAAS API to acce

AAS-enabled back-end applications.

uthorization

ter determining the identity of the user, the portal server consults locally cached access control lists tetermine which pages and portlets a user has permission to access.

he portal server enforces access control to portal assets, including portlets, pages, and user groups. Tcess control lists are stored in the portal administration database. It is also possible to manage accentrol for specific resources in an external security manager, such as IBM Tivoli Access Manager or

etegrity SiteMinder.

ccess permissions are maintained using the Access Control administration portlet. Use this portlet tosign roles to individual users or to groups of users for specific portlets, pages, or documents. Roles a

ermission sets, such as the ability to view and update the corresponding item. Users can also delegate permissions they hold to other users. When a role is assigned to a user or a group on a containeruch as a page that contains portlets or other pages, or a folder that contains other folders orcuments), that role is inherited downward through the hierarchy unless it is specifically blocked. Thisakes managing access within a document library or an area of the portal easy.

ranting view access to a page or place means that other users will see pages and places when they

Granting view access to a portlet means that users can add it to their pages when they customize thortal experience. Granting edit access means that a user can set the portlet settings or change thentents of a page. Manage access means that a user can perform view and edit operations, and can

elete the portlet or page.

elegated Administration

ranting view access to administration portlets is an effective way of delegating certain administrativesks to other portal users. Those users can add the administration portlets to their personal pages, anen can perform whatever task the portlet is designed to do. This way, the user does not have to be g

24


25/59

administrative privileges or added to the portal administrator group. Their administrative abilities aremited to only those tasks that are covered by the authorized portlets.

elated information

q Key features

25


26/59

ollaboration

ollaboration features help people in your organization work together and share information online tohieve their business goals. A collaborative portal can improve the responsiveness, innovation,mpetencies, and efficiency of your organization. WebSphere Portal offers features from IBM Lotus

oftware that enhance collaboration for portal users:

q Lotus collaborative portlets

q Lotus Companion Products

q Lotus Collaborative Components

q Collaboration Center

otus collaborative portlets

ollaborative portlets from IBM Lotus Software provide access to a variety of collaborative applicationsat use Lotus Notes databases that are hosted on Domino servers: the Notes and Domino portlet offeail, Calendar, To Do, Notes View, TeamRoom, and Discussion, while the Domino Web Access (iNotertlet offers Mail, Calendar, To Do, Contacts, and Notebook. Other portlets from IBM Lotus Software

clude Quick Appointment, Quick e-Mail, and Web Page. Still others, such as Inline QuickPlace, offerditional features when you have chosen to integrate Lotus Companion Products in your portalvironment.

otus Companion Products

ou can enhance the collaborative features of WebSphere Portal and add features such as peoplewareness and information discovery to Lotus business portlets, by choosing to install and enable any

e following companion products for advanced collaboration from IBM Lotus Software:

q Lotus Sametime adds the online status indicator to people links and adds actions to people link

menus.q Lotus QuickPlace provides access, from a collaborative portlet, to the QuickPlace server and th

team workspaces that it hosts.q Lotus Discovery Server adds actions to people link menus and provides access to Knowledge M

components from collaborative portlets. The expertise location feature of Discovery Server isavailable from within the Discovery Server portlets and from the added people link actions.

tus Sametime features

hen Sametime is enabled in your portal configuration, portal users can work with the complete set ofeople awareness functionality, which includes instant messaging and application sharing through e-eetings. With Sametime enabled, people appear with a dynamic online status indicator, and their namppear as hyperlinks. People link menus include the following options:

q Chatq Add to Contact List

26
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


27/59

ou might choose not to enable Sametime in your portal configuration. If Sametime is not enabled, theeople awareness functionality will be restricted to the following features:

q People's names appear as hyperlinks, but with no people awareness icon next to each nameq People menus still appear when a user clicks a name shown as a hyperlink, but menu options a

limited to the following actions, which are native to WebSphere Portal (or to Lotus DiscoveryServer) and are not Sametime actions:

r Send E-mailr

Show Profile (if Lotus Discovery Server is installed)r Find Documents Authored By (if Lotus Discovery Server is installed)

tus QuickPlace features

he availability of QuickPlace portlets is not affected by the portal configuration option to enable or disuickPlace, because portlets launch applications and services that are independent of portalnfiguration. As long as a QuickPlace server is available for selection and you have installed andnfigured the QuickPlace portlet application, portal users can add instances of QuickPlace portlets tortal pages or use QuickPlace portlets in the portal pages where they participate.

tus Discovery Server features

hen Discovery Server is enabled in your portal configuration, portal users have access to the Knowleap of your enterprise content repositories and expertise profiles for the people in your enterprise.scovery Server extends the basic content and people awareness of WebSphere Portal to include thelowing features:

q People link menus include actions for getting additional information about people and documenr Show Profile (Discovery Server expertise locator and affinity generation component)

This action displays the person's profile of business card information, contact informatio

affinities, current job, and background.r Find Documents Authored By (Discovery Server Knowledge Map features)

This action launches Knowledge Map Search of all documents that the person has auth

q The WebSphere Portal navigation bar includes the Expertise Profile icon, which opens the peopprofiles that are generated and maintained by the Discovery Server.

q Discovery Server portlets are available for installation, configuration, and deployment:r Knowledge Map portletr Search Results portletr Mini-Search portlet

otus Collaborative Components

tus Collaborative Components are Java APIs that provide the building blocks for integrating thenctionality of Domino, Lotus Sametime, Lotus QuickPlace, and Lotus Discovery Server into portals anrtlets. Using Lotus Collaborative Components, application developers can design and implement useerface extensions in portals and portlets that extend the functionality of Lotus Software collaborationoducts.

he primary goal of Lotus Collaborative Components is to provide the data for the portlet user interfaced to allow developers to execute actions on installed Lotus products. Lotus Collaborative Componen

27


28/59

clude no platform-specific code, hide the configuration details of Lotus Software products that arestalled in the enterprise, and (except for the PeopleService tags) are user-interface neutral. Applicatioevelopers can add collaborative functionality to a portlet without having to know the details of servernfiguration and with total control of user interface design and implementation. These benefits maketus Collaborative Components effective for implementing mobile applications.

ollaboration Center

ollaboration Center comprises the following portlets, which offer integrated features to improve useroductivity, and can be deployed in WebSphere Portal in addition to Lotus Collaborative Components

otus collaborative portlets.

q People Finder portletq My Lotus Team Workplaces (QuickPlace) portletq Lotus Web Conferencing (Sametime) portletq Sametime Contact List portletq Sametime Who Is Here portlet

elated information

q Planning for collaboration

q People awareness

q Collaborative Components API

q Collaboration Center

q Key features

28
http://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksa_cfg_setupmgr_collab.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksu_pac_def.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksd_cs_api_intro.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ap_intro.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ap_intro.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksd_cs_api_intro.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksu_pac_def.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/collab/ksa_cfg_setupmgr_collab.html


29/59

omponents overview

his section describes each of the components that is shipped with WebSphere Portal and explains the each component plays in the overall solution.

ote: Consult the product license for specific terms of entitlement for the software components that are

ipped with your edition of WebSphere Portal. Usage restrictions apply for some software.

q Components and products included with WebSphere Portal Version 5.0.2r WebSphere Portal

r WebSphere Portal content publishing

r Lotus Collaborative Components

r Portal Toolkit

r IBM WebSphere Application Server, Enterprise Version 5.0 Fix Pack 2

r IBM Directory Server Version 5.1

r DB2 Enterprise Edition, Enterprise Server Edition Version 8.1 Fix Pack 1

r IBM WebSphere Studio Site Developer Version 5.1

r WebSphere Translation Server Version 5.0

q Additional products and components included with WebSphere Portal Extend Version 5.0.2r Collaboration Center Version 5.0

r IBM Lotus Domino Enterprise Server 5.0.12

r Instant messaging and online awareness, based on Lotus Sametime 3.0 technology

r Virtual teamrooms based on Lotus QuickPlace 3.0.1 technology

r IBM Tivoli Web Site Analyzer Version 4.5

r IBM Lotus Extended Search 4.0

q Additional products to use with WebSphere Portalr IBM Tivoli Access Manager for e-business Version 4.1

r IBM Content Manager

r Lotus Discovery Server

q Product and component matrix

roducts and components included with WebSphere Portal

his section provides information about the products and components that are included with WebSpheortal.

WebSphere Portal

WebSphere Portal is a J2EE(TM) application that runs on WebSphere Application Server.Its main function is to serve the WebSphere Portal framework to the desktops and mobile

29


30/59

devices of portal users. WebSphere Portal creates an environment that provides theconnectivity, administration, and presentation services required. WebSphere Portal includesseveral new functions and enhancements that make it easier to design, administer, anduse.

WebSphere Portal content publishing

WebSphere Portal content publishing (WPCP) provides a Web-content management

solution that gives nontechnical users greater control over content that is published toportals and Web sites. Users benefit from the combined power of having one place tomanage content for their Portal environment or other Web sites and an easy-to-use Webinterface. This interface puts content management back into the hands of nontechnicalbusiness users and provides them with tools such as personalization rules, templates,workflow, and versioning, that make the content creation process simple, yet controlled.WPCP decreases Web maintenance and administration costs, increases sales and profitsby deploying timely and personalized content, and improves efficiency by getting all contentthat is produced in an enterprise to the Web.

WPCP includes a variety of functions. The core part of WPCP involves the content creationprocess. The Web browser interface enables users to contribute content to a Web site withlittle training in a simple and controlled manner. The solution allows large teams to worktogether, jointly where necessary, but with enough isolation to manage content changes intheir respective work groups until they are ready to share them with the extendedcontribution team. Versions of changed content can be stored in the versioning repositoryfor later reuse. WPCP manages the task lists of each user, maintains access control overwhat content each user can see or change, and coordinates the approval and publishingprocess when content has been approved. This is all accomplished through a workflowprocess that can be customized to meet the needs of each individual customer.

WPCP includes two personalization technologies to dynamically tailor Web content to meetthe needs of different users and groups. These include rules-based filtering to displayselected content to targeted users and matching techniques that extract visitor behavior andtailor the content within individual portlets based on that behavior. This technology creates acustomized user experience for improved employee productivity and more effectiveconsumer messaging. To augment the personalization features, WPCP provides a reportingmechanism. This functionality assesses the effectiveness of business rules and buildsreports for the WPCP user to leverage when analyzing the impact of targeted content onconsumers. The reporting mechanism provides data to Web site managers to help themrevise targeting strategies based on user response to content they have received.

Lotus Collaborative Components

Lotus Collaborative Components are UI-neutral API methods and tag libraries that allowdevelopers who are writing portlets for WebSphere Portal to add Lotus Softwarecollaborative functionality to their portlets. Application developers who are usingCollaborative Components can design and implement UI extensions that leverage thefeatures of Domino, QuickPlace, Sametime, and Lotus Discovery Server.

Portal Toolkit30


31/59

Portal Toolkit provides the capabilities to customize and manage the enterprise portal andcreate, test, debug, and deploy individual portlets and Web content. Templates enabledevelopers to quickly and easily create their own portlets. Debugging and deployment toolsshorten the development cycle. Sample portlets that demonstrate best programmingpractices are also provided.

Portal Toolkit plugs into WebSphere Studio Site Developer or WebSphere Studio

Application Developer, which provides a comprehensive framework for the development ofe-business applications.

A copy of WebSphere Studio Site Developer is included, and it is licensed for use only withPortal Toolkit. Consult the product license for details.

IBM WebSphere Application Server Version 5.0 Fix Pack 2

IBM WebSphere Application Server is a Web application server that provides J2EE servicesfor the WebSphere Portal environment. It executes the Java portlets, JavaBeans,JavaServer(TM) Pages (JSP) files, and Enterprise JavaBeans (EJBs) that are used by

WebSphere Portal. This component is the platform on which WebSphere Portal runs.

Usage restrictions apply. Consult the product license for details.

IBM Directory Server Version 5.1

IBM Directory Server is a Lightweight Directory Access Protocol (LDAP) directory that runsas a stand-alone daemon. In the WebSphere Portal environment, it stores, updates, andretrieves user-specific data that is related to authentication, such as user IDs andpasswords.

DB2 Enterprise Edition, Enterprise Server Edition Version 8.1 Fix Pack 1

DB2 Enterprise Edition is a Web-enabled relational-database management system. In theWebSphere Portal environment, DB2 stores portal configuration data, and portal-specificdata, access-control data, and user data.

IBM WebSphere Studio Site Developer Version 5.1

IBM WebSphere Studio Site Developer is an integrated development environment (IDE) for

building, testing, and deploying J2EE applications. It provides integrated developmentsupport for building J2EE applications with HTML pages, servlets, JavaServer Pages, andEJBs. It also creates Web service applications with open standards, generates XMLdocuments from DTDs, and enables a collaborative team development environment. Itenables end-to-end local and remote testing and creates high-quality applications usingwizards, code generators, and best practices.

WebSphere Translation Server Version 5.0

Translation Server is a machine translation (MT) offering that helps you remove language

31


32/59

as a barrier to global communication and e-commerce. Translation Server enablesenterprises to provide Web pages, e-mail messages and chat conversations in multiplelanguages, in real time. Specifically designed for enterprise use, the Translation Serverallows companies to leverage their existing Web infrastructure to provide content to users intheir native language, at a fraction of the cost of professional translation.

Based on IBM machine translation technology, Translation Server is designed for scalabilityon multiple platforms. Translation Server can run on a dedicated server, using RMI and Java

(R) protocol to communicate with the WebSphere Application Server. Web page HTMLcontent can also be translation-enabled to support HTTP servers from Netscape, Apache,Microsoft, or IBM.

Translation Server consists of:

q MT engines for translating text from one language to another language (such asEnglish to Spanish)

q User Dictionary Manager tools that allow specific words to be added to a domain (forexample, tuning for a specific application or adding of slang or domain-specificphrases and terms)

q Support for WebSphere Application Server and HTTP servers from Microsoft,Netscape, Apache, and IBM

dditional products and components included with WebSphere Portal Extend

he following components are included with WebSphere Portal Extend.

Collaboration Center Version 5.0

WebSphere Portal featuring Collaboration Center capabilities offers an integrated

framework of e-workplace components for finding, connecting, and working with people:

q People Finder portletr Directory Connectorr Sample configuration

q My Lotus Team Workplaces (QuickPlace) portletq Lotus Web Conferencing (Sametime) portlet

Using these components, users have immediate access to a searchable directory of peoplethat is integrated with their workplaces and their e-meetings within the collaborative portal.

Users can find people in the directory, see their online status, and interact with them usinginstant messaging and other actions that are provided by people links. In addition to searchfeatures, the People Finder provides views of each person's directory record and his or herplace in the organizational context. People links are visible in workplaces and e-meetings tomake employee interaction fast and easy, improving personal and organizationalproductivity.

IBM Lotus Domino Enterprise Server 5.0.12

IBM Lotus Domino Enterprise Server and Notes is groupware software that provides

32


33/59

messaging and collaboration features. Notes is the e-mail, calendaring, group scheduling,Web access, and information management client. Domino is the integrated messaging andWeb application server.

Domino Directory can provide your primary corporate directory or the secondary LDAPservice that complements another LDAP service (for example, IBM Directory Server,Windows 2000 Active Directory, or Sun ONE) in your portal environment. As a secondaryLDAP service, Domino Directory provides user access to Notes-based information sources

for Collaborative Components and collaborative portlets.Usage restrictions apply. You are authorized to install and use Domino solely andexclusively in connection with your use of Sametime and QuickPlace. Consult the productlicense for details.

Instant messaging and online awareness, based on Lotus Sametime 3.0technology

Instant messaging and online awareness (also known as people awareness), are available.Using Sametime, portal users can discover if others are available to chat, receive e-mail,

share applications and other tools in an e-meeting or Web conference, and, if LotusDiscovery Server is enabled, find documents authored by others and display expertiseprofiles from the Knowledge Map.

Usage restrictions apply. For example, the e-meeting capabilites of Sametime are notlicensed for use. Consult the product license for details.

Virtual teamrooms based on Lotus QuickPlace 3.0.1 technology

A Web-based solution is available for creating team workspaces for collaboration. Using

QuickPlace, portal users can work securely with colleagues, suppliers, partners, andcustomers. QuickPlace provides teams with workspaces where they can reach consensusthrough discussions, collaborate on documents, and coordinate plans, tasks, and resources.

Usage restrictions apply. For example, you are authorized to install and use QuickPlacesolely and exclusively with WebSphere Portal. A separate license is required to accessQuickPlace from a source other than WebSphere Portal. Consult the product license fordetails.

IBM Tivoli Web Site Analyzer Version 4.5

IBM Tivoli Web Site Analyzer is a Web application that captures and analyzes Web sitedata to provide useful reports about visitor traffic, visitor behavior, site usage, site content,and site structure. You can build customized reports from predefined report elements or youcan build custom reports that collect information specific to your site. Installed as a Webapplication on WebSphere Application Server, Tivoli Web Site Analyzer allows you to createtrend reports that show Web site visitor traffic, site usage growth, and changes over time.

The new enhancements in Tivoli Web Site Analyzer include integrated support forWebSphere Portal. This support includes specific report elements that enable you toanalyze portal usage data, such as a ranking of the portal pages viewed by visitors and

33


34/59

portal login trends. Using this integration involves configuring the portal to generateapplication level logs, importing the logs to Tivoli Web Site Analyzer and creating reports.

IBM Lotus Extended Search 4.0

IBM Lotus Extended Search is a Web-based solution that supports searching acrossdistributed, heterogeneous, structured, and unstructured data sources through a singlepoint of access. Although it does not require you to create a central index for the sources

that you want to search, Lotus Extended Search serves as a complimentary solution toproducts that provide indexing services, such as Lotus Discovery Server.

By entering a single request from a Web browser, you can search potentially thousands ofdata repositories and the Internet and, at the same time, locate people with expertknowledge. Lotus Extended Search handles the logistics that are required to access manydiverse sources simultaneously without requiring you to know any details about the varioussearch interfaces. It also produces a single, ranked result set that contains responses frommultiple sources. Links in the result set enable you to go directly to documents of interest ordownload attachments.

Lotus Extended Search can search and retrieve documents from the following types ofsources:

q 18 popular Web search sites and News sitesq Lotus repositories such as Notes databases, Domino.Doc libraries, QuickPlace

places, and Lotus Discovery Server knowledge mapsq Mail systems such as those managed by Lotus Notes and Microsoft Exchangeq Instant messaging systems such as Sametimeq Relational databases such as DB2, Oracle, Sybase, MS SQL-Server, and other

ODBC-compliant databasesq Document management systems such as IBM DB2 Information Integrator for

Content (Enterprise Information Portal)q File systemsq LDAP-compliant directoriesq Full text indexes such as those created with WebSphere Portal, Domino Domain

Index, Microsoft Index Server, and Microsoft Site Server.

With the Lotus Extended Search C++ and Java application programming interface (API),you can extend support to other types of sources that you need to search, such asproprietary, commercial, or legacy databases in your enterprise that are not mentioned inthe preceding list.

dditional products to use with WebSphere Portal

he following products are not included with WebSphere Portal, but they can enhance the features andnctions provided.

IBM Tivoli Access Manager for e-business Version 4.1

IBM Tivoli Access Manager for e-business is an authorization and management solutionthat scales across the entire enterprise. A robust and secure policy management tool for e-34


35/59

business and distributed applications, it addresses the challenges of escalating securitycosts, growing complexity, and the need for uniform security policies across platforms. TivoliAccess Manager unites core security technologies around common security policies to helpreduce implementation time and management complexity, thereby lowering the total cost ofsecurity-enhanced computing.

IBM Content Manager Version 8.2

IBM Content Manager is an unstructured content management system that is optimized forlarge collections of large objects, from scanned images, facsimiles, and PC files to XML andrich multimedia and Web content. IBM Content Manager also provides folder managementand document workflow and provides the content infrastructure for applications from callcenters, high-volume claims processing, and accounts payable, to e-commerce cataloguesand e-learning.

Lotus Discovery Server

Lotus Discovery Server is a comprehensive knowledge server that lets portal users search

or browse for information and subject matter experts from multiple locations, collaboratewith colleagues instantly, increase knowledge sharing and decrease time spent looking forneeded resources - all from a Web browser.Lotus Discovery Server finds content, discovers relationships, locates expertise and returnsmore accurate results through automated collaborative filtering based upon usage. It doesthis on a backdrop of collaborative tools that instantly link people through awareness andinstant messaging.

q Search and find answers quickly while avoiding information overload.q Identify documents, people, and places with a single search across your entire

organization.q Capture and quickly catalog information and intellectual assets to avoid duplicate

work.q Identify the experts for collaboration - on demand - to improve decision cycle times

and to leverage skills across departmental and geographical boundaries.

roduct and component matrix

he following table shows the products and components that are packaged in each WebSphere Portalfering. You might have purchased only one of these offerings; however, all available WebSphere Porferings are shown for comparison purposes.

Product or component Express Express Plus Enable Extend

WebSphere Portal X X X X

M WebSphere Application Servernterprise Edition

X X X X

BM Directory Server X X X X

otus Collaborative Components X X X X

ortal Toolkit X X X X

M WebSphere Studio Site Developer X X X X35


36/59

B2 Enterprise Edition X X

BM Lotus Domino Enterprise Server X X X

otus QuickPlace * *

otus Sametime * *

ollaboration Center X X

WebSphere Portal content publishingncluding Personalization)

X X

WebSphere Translation Server X XBM Lotus Extended Search X

M Tivoli Web Site Analyzer X

Sametime and Quickplace are limited portal use only.

elated information

q What's new


q Key features





36


37/59

ccessibility features

ccessibility features help a user who has a physical disability, such as restricted mobility or limited visuse software products successfully.

hese are the major accessibility features in WebSphere Portal:

q You can use screen-reader software and a digital speech synthesizer to hear what is displayedthe screen.

q You can operate most features using the keyboard instead of the mouse.q When appropriate, the documentation for specific product features contains additional informati

about accessibility.

elated information

q What's new


q Key featuresq Components overview




37


38/59

bout this information

his Information Center is for planners, installers, administrators, developers, and others who plan tostall, configure, administer, and develop for WebSphere Portal.

ebSphere Portal provides a comprehensive solution for your business. The information in this

formation Center is designed to help you design and implement your portal solution. Because everyrtal deployment is unique, it is important to also refer to the the Additional resources section for links

her information about WebSphere Portal. There are links to IBM Redbooks, articles, and much more

ortal administrators should have experience supporting Internet servers running on UNIX-based orindows operating systems. In addition, installers and administrators should have skills in databaseftware, general networking, and firewalls. Portlet developers should have Java programming skills.

q Information Center change history

q Conventions

formation Center change history

Edition Date Updates

dition 12 March 2, 2005

Corrections to various topics including:q Managing documents > Document Manager >

Running Document Conversion Services on an AIXserver (new)

q Installing > Web Serverq Installing > Database > Configuring databasees > D

q removed Customizing Web Clipperq Customizing the portalq Using Active Directory and SSLq Securing your portal > LDAP > Setting up LDAP ov

SSLq Additional Resources > Resources and Supportq Troubleshooting Collaboration Centerq Creating a vertical cluster on a single machineq Installing WebSphere Portal in a cluster environmen

dition 11 January 4, 2004

Corrections to various topics including:q Administering > Portal Administration portletsq Troubleshooting Document Manager and Productiv

Componentsq Troubleshooting Administration

38
http://-/?-http://-/?-http://-/?-http://-/?-


39/59

dition 10 December 7, 2004

Corrections to various topics including:q Troubleshooting databasesq Configuration task referenceq Troubleshooting WebSphere Portal installationq Changing WebSphere Portal schema in the databaq added topic: Slow login when using Active Directory

as LDAPq Troubleshooting LDAP and Securityq Can Lotus Collaborative Environments share an LD

server?q Changing the WebSphere Portal URIq Searching multiple object classes in WebSphere Poq Managing Documents

dition 9 November 2, 2004

Corrections to various topics including:q Web clippingq Installing WebSphere Portal in a cluster environmenq Enabling Security > Configuring LDAPq Developing portlets > IBM Portlet API > Configurati

objects

dition 8 October 5, 2004

Corrections to various topics including:q Changing LDAP hostname in a clusterq Configuring Document Managerq Member Manager Configurationq Setting up SSL for WebSphere Portal

dition 7 September 3, 2004

Corrections to various topics including:q Changes to Struts Applicationq Deploying customized themes and skinsq Setting up SSL for WebSphere Portalq Hardware and software requirementsq Portlet API tag quick referenceq Tags used by the portal JSPs

dition 6 August 5, 2004

Corrections to various topics including:q Installing WebSphere Portal in a cluster environmenq Improving Performance

q Installingq Moving from a test to production server using the X

configuration interfaceq Configuring WebSphere Portal for Active Directoryq Using IBM Content Manager as a datastore for

Document Manager

39


40/59

dition 5 July 7, 2004

Corrections to various topics including:q Supported hardware and softwareq Installing WebSphere Portalq Configuring your Web serverq Tivoli Access Managerq Clusteringq Creating databases and users for DB2q Machine Translationq Configuring securityq Improving performanceq Packaging the JARS in your portlet WAR fileq Configuration property referenceq Migrating credential vault

dition 4 January 23, 2004

Update of the Information Center and provided translated othe Web.

Refer to the WebSphere Portal Version 5.0.2 release notesfor change history details.

dition 3 December 12, 2003

Update of the Information Center and provided translated othe Web.

Refer to the WebSphere Portal Version 5.0.2 release notesfor change history details.

dition 2 November 21, 2003

Update to the Information Center for WebSphere PortalVersion 5.0.2.Refer to the WebSphere Portal Version 5.0.2 release notesfor change history details.

dition 1 October 29, 2003Initial Information Center that was translated and included the WebSphere Portal Version 5.0.2 product CDs.

onventions

ollowing are some conventions that can help you interpret the information that is provided in thisformation Center:

q File names, directories, and commands appear in Courier font. For example:r File name: install.batr Directory: /opt/WebSphere/PortalServerr Command: startServer WebSphere_Portal

q Variables are either italicized, enclosed in brackets, or both. For example:r http:///wps/portal

q The following variables are used to indicate a root installation directory:r WebSphere Portal root installation directory: or wp_rootr WebSphere Application Server root installation directory: or was_root

q Directories are shown with forward slashes (/), unless operating-system specific information is

40
http://www.ibm.com/websphere/portal/libraryhttp://www.ibm.com/websphere/portal/libraryhttp://www.ibm.com/websphere/portal/libraryhttp://www.ibm.com/websphere/portal/library


41/59

provided. On Windows systems, you should use backward slashes (\) when typing at a commaline, unless otherwise noted.

q Operating-system specific information is provided. For example:r UNIX:./WPSconfig.sh backup-main-cfg-filer Windows: WPSconfig.bat backup-main-cfg-file

q Tips on how to use specific topics are marked with a green check. For example:

r

How to use this planning sectionq Most topics include a Related information section that links to other relevant topics. See the las

section for an example.q When the term UNIX is used, this implies all UNIX-based operating systems that are supported

Refer to Supported hardware and software for more information.

elated information

q What's new


q Key features





q Trademarks

41
http://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/inst_req.htmlhttp://pvcid.raleigh.ibm.com/wpf/ic/502/ent/en/InfoCenter/wpf/inst_req.html


42/59

esources and support

addition to the Information Center, you can locate product documentation on the WebSphere PortalDs or on a separate Information CD that is shipped with WebSphere Portal.

mportant: It is recommended that you use the installation program to install the software that is includ

th WebSphere Portal. For more information, see Installing. If you elect to use the installation programat are provided with a component, refer to this information to locate specific product documentation.

ebSphere Portal Enable includes the following products:

q WebSphere Portal

q IBM WebSphere Application Server

q IBM HTTP Server

q IBM Directory Server

q DB2 Enterprise Edition

q IBM Rational Application Developerq WebSphere Translation Server

ebSphere Portal Extend adds the following products:

q IBM Lotus Domino Enterprise Server

q Lotus Sametime

q Lotus QuickPlace

q IBM Tivoli Web Site Analyzer

q IBM Lotus Extended Search

WebSphere Portal Enable includes the following products:

ebSphere Portal

oduct documentation

ebSphere Portal product documentation is available to view and download from the Web. As updates

e received the product documentation on the Web is updated, therefore it is important to always chece Web for the most current information. In addition to this Information Center, online files supplementormation in this Information Center. Examine these files before you install WebSphere Portal. Theynt