websphere portal content publishing installation...

WebSphere Portal content publishingInstallation Guide

��

First Edition (November 2002)

This edition applies to the current version of WebSphere Portal content publishing and to all subsequent releasesand modifications until otherwise indicated in new editions. Make sure you are using the correct edition for thelevel of the software.

When you send information to IBM®, you grant IBM a nonexclusive right to use or distribute the information inany way it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 2002. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Note!Before using this information and the software it supports, be sure to read the generalinformation under Notices.

Contents

Chapter 1. Installation Guide . . . . . . 1Terminology . . . . . . . . . . . . . . 1Prerequisites . . . . . . . . . . . . . . 1

Chapter 2. Example installationscenarios . . . . . . . . . . . . . . 3″Proof of concept″ scenario . . . . . . . . . 3Production with Domino Workflow. . . . . . . 5Production with Lite Workflow . . . . . . . . 6

Chapter 3. Planning your installation . . 9Migration . . . . . . . . . . . . . . . 9Database installation. . . . . . . . . . . . 9WebSphere Application Server . . . . . . . . 9Workflow Management . . . . . . . . . . . 9Version Control . . . . . . . . . . . . . 10Development environment . . . . . . . . . 10Authoring environment . . . . . . . . . . 10Runtime environment . . . . . . . . . . . 11

Considerations for LikeMinds RecommendationEngine . . . . . . . . . . . . . . . 11

Chapter 4. Preparing to installWebSphere Portal content publishing . 15Uninstalling WebSphere Portal content publishing 15Preparing databases and content stores . . . . . 16

Configuring an Oracle database . . . . . . 16Configuring a DB2 database . . . . . . . . 20Installing IBM Content Manager . . . . . . 21

Preparing workflow management . . . . . . . 23Setting up Lotus Workflow . . . . . . . . 23

Preparing security/authentication . . . . . . . 30Local operating system . . . . . . . . . 30LDAP . . . . . . . . . . . . . . . 30Lotus Domino . . . . . . . . . . . . 31

Preparing version control . . . . . . . . . . 31Preparing to install LikeMinds RecommendationEngine . . . . . . . . . . . . . . . . 32

Using an existing database for your LikeMindsinstallation . . . . . . . . . . . . . 32Using a different table schema from the defaulttables . . . . . . . . . . . . . . . 32Creating the database for Microsoft SQL Server 32Configuring an ODBC DSN for Microsoft SQLServer . . . . . . . . . . . . . . . 33

Preparing for a LikeMinds RecommendationEngine installation on Oracle . . . . . . . 33Preparing for a LikeMinds RecommendationEngine installation on IBM DB2 . . . . . . 34Using Movie Site, the LikeMinds Admin Center,or the LikeMinds SDK. . . . . . . . . . 35

Chapter 5. Installing WebSphere Portalcontent publishing . . . . . . . . . 37Installing the development environment . . . . . 37

WebSphere Studio . . . . . . . . . . . 37WebSphere Portal content publishing wizards forWebSphere Studio . . . . . . . . . . . 37

Installing the authoring environment . . . . . . 39Installing the Authoring Server and Sample . . 39Installing WebSphere Portal content publishing— Desktop Integration . . . . . . . . . 43

Installing the runtime environment . . . . . . 44Installing a Production Server . . . . . . . 44Verifying your installation . . . . . . . . 47Configuring the runtime environment . . . . 49Cloning the runtime environment . . . . . . 52

Installing the documentation (custom location) . . 54Installing the documentation (custom location) 54Verifying the installation and accessing thedocumentation . . . . . . . . . . . . 54

Troubleshooting . . . . . . . . . . . . . 55Text truncation in install panels on AIX andLinux . . . . . . . . . . . . . . . 55

Chapter 6. Accessing the Sample . . . 57Starting WebSphere Portal content publishing . . . 57Getting Started Tutorial (for use with the AuthoringServer Sample) . . . . . . . . . . . . . 58

Chapter 7. Troubleshooting . . . . . . 59

Chapter 8. Manually uninstallingWebSphere Portal content publishing . 63

Notices . . . . . . . . . . . . . . 69Programming interface information . . . . . . 70Trademarks and service marks . . . . . . . . 71

© Copyright IBM Corp. 2002 iii

iv WebSphere Portal content publishing Installation Guide

Chapter 1. Installation Guide

This guide is for those performing custom installations of WebSphere Portalcontent publishing and is not intended for use with the WebSphere Portal SetupManager.

Use of the Setup Manager is recommended if you are doing a full installation ofWebSphere Portal content publishing. Setup Manager will install the prerequisitesfor you and prompt you to complete most of the necessary configuration steps.

For updates to this and other documents, see the WebSphere Portal Web site:http://www.ibm.com/websphere/portalfamily

TerminologyThe following is a list of terms and definitions used throughout this installationguide.

was_homeIndicates the root directory where WebSphere® Application Server (WAS) isinstalled. For example, on Windows® platforms the WAS root directorycould be C:\WebSphere\AppServer, on AIX® platforms the WAS rootdirectory could be /usr/WebSphere/AppServer.

oracle_homeIndicates the root directory where Oracle is installed. For example, onWindows platforms the Oracle root directory could be C:\Oracle, on AIXplatforms the Oracle root directory could be /u01/app/oracle.

studio_rootIndicates the root directory where WebSphere Studio is installed, forexample, C:\Program Files\IBM\Application Developer on MicrosoftWindows.

PrerequisitesIn order to provide the most current information, the hardware and softwareprerequisites have been made available on the WebSphere Portal contentpublishing Web site:http://www.ibm.com/software/webservers/portal/webcontentpublisher.html

© Copyright IBM Corp. 2002 1

http://www.ibm.com/websphere/portalfamily

2 WebSphere Portal content publishing Installation Guide

Chapter 2. Example installation scenarios

Generally, WebSphere Portal content publishing and its prerequisites can bedivided into three functional environments:

WebSphere Portal content publishing development environmentOne or more of the following:v One of the WebSphere Studio Family of Productsv WebSphere Portal content publishing wizards for WebSphere Studio

WebSphere Portal content publishing authoring environmentOne or more of the following:v WebSphere Portal content publishing Authoring Server (required)v WebSphere Portal content publishing Authoring Server Samplev Lotus Workflow Architect (if using Lotus Workflow)v IBM Enterprise Information Portal (if using IBM Content Manager for

repository)v IBM Content Manager (if using IBM CM)v A versioning system (for example, CVS or Rational ClearCase)

WebSphere Portal content publishing runtime environmentOne or more of the following:v WebSphere Portal content publishing Production Serverv WebSphere Portal content publishing — Edge Serverv WebSphere Portal content publishing — Personalization Runtimev WebSphere Portal content publishing — LikeMinds Recommendation

Engine

It is recommended that these environments be on different machines. Threeexample scenarios are provided that demonstrate different installationconfigurations and a basic concept of the development process. Note that thesescenarios are only examples; these are not the only possible configurations.

″Proof of concept″ scenarioThis example scenario, illustrated below, demonstrates one of the simplerinstallation configurations.


Here, all machines are running Microsoft Windows (specifically, Windows 2000). Inthe runtime environment are WebSphere Portal, WebSphere Portal contentpublishing Production Server, and the optional WebSphere Portal contentpublishing Personalization run-time environment for interpreting business rulesand delivering dynamic, targeted content. Security and authentication for therun-time and the authoring environments are provided by IBM Directory Server.The authoring environment has been set up with no workflow mechanisms.

The development environment is shown as having one of the WebSphere StudioFamily of Products (for example, WebSphere Studio Application Developer) withthe WebSphere Portal content publishing wizards and WebSphere Portal toolkit.


The developer generates and delivers content, Web pages (HTML/JSPs), servlets,portlets, application objects, resource classes, and content spots to both theAuthoring and Production Servers.

The business users and other content contributors can create and publish contentto the Web site on the Production Server via the WebSphere Portal contentpublishing workspace. Because the Personalization runtime has been installed onthe Production Server, business users can use the workspace to create rules andcampaigns that govern dynamic content delivery and publish them to the run-timeenvironment. Also, business users can use the workspace to analyze reports andcharts about the logged activity in the Feedback database.

Production with Domino WorkflowIn the configuration shown below, Lotus Domino, Lotus Workflow and LotusDomino LDAP are installed with the WebSphere Portal content publishingAuthoring Server. The LDAP Server provides security and authentication for boththe Authoring and Production servers (both Sun Solaris). Lotus Domino Workflowis coupled with WebSphere Portal content publishing’s versioning capabilities, withapproved versions of content being published to a remote content store that is alsoaccessed remotely from the run-time environment.

Chapter 2. Example installation scenarios 5

Production with Lite WorkflowThe sample installation configuration shown here demonstrates integration withIBM Content Manager as a content and versioning store. In this example, IBM CMand IBM Enterprise Information Portal are located on the Production Server (AIX),and are accessible from the development and authoring environments (MicrosoftWindows).


Additionally, IBM Directory Server, located on the Production Server, providesLDAP authentication services for both the Authoring and Production Servers.

Note that the LikeMinds Recommendation Engine is installed on the ProductionServer, enabling the use of recommendation-based personalization of dynamiccontent.

Chapter 2. Example installation scenarios 7

Chapter 3. Planning your installation

MigrationIt is possible to migrate projects or configuration information from previousreleases of WebSphere Personalization, LikeMinds, and Web Content Publisher foruse with WebSphere Portal content publishing. Migration of configurationinformation must be performed before continuing with this installation. Themigration utilities are provided on the WebSphere Portal installation CD 5 in thewpcp\migration directory. For instructions on using these utilities, refer to theWebSphere Portal content publishing Web site:http://www.ibm.com/software/webservers/portal/webcontentpublisher.html

Database installationSimilarly to WebSphere Application Server, the WebSphere Portal contentpublishing Authoring Server and Production Server each require access torelational databases. Typically the database will be a local installation of IBM DB2or Oracle, although it is possible to use databases on remote machines. For storageof content (files, images, digital media, and so on), you can use either of theserepositories or an installation of IBM Content Manager and IBM EnterpriseInformation Portal (EIP).

Regardless of your choice, the database must be installed and correctly configuredbefore you install WebSphere Portal content publishing.

WebSphere Application ServerWebSphere Application Server must be installed and functioning correctly on eachmachine where you plan to install a WebSphere Portal content publishingAuthoring Server or Production Server. Security may be enabled or disabled priorto beginning the installation.

Workflow ManagementThere are three options for implementing workflow for the WebSphere Portalcontent publishing authoring environment: no workflow; Lite workflow (a basicworkflow process built into the WebSphere Portal content publishing AuthoringServer software); and Lotus Workflow. No setup is necessary if you will not beusing workflow or if you will be using Lite Workflow modes.

Notes:

1. If you are using Lotus Domino Server, it should be dedicated to Lotus®

Workflow.2. If you choose Lotus Workflow, you will automatically be set up to use Lotus

Domino LDAP as the authentication mechanism for the Authoring Server.


Version ControlThere are several options for implementing version control for the WebSpherePortal content publishing authoring environment: IBM Content Manager, RationalClearCase, CVS, or the version control built into WebSphere Portal contentpublishing. The version control software that you plan to use should already beinstalled and configured before you install WebSphere Portal content publishing.

When deciding what version control system to use, consider the following:v IBM Content Manager can be used as a standalone version store with another

repository serving as the content store, or it can be used as both the contentstore and the version store. If IBM CM is used as the content store, it must alsobe used as the version store.

v IBM Content Manager versions resources in a common namespace. Whereasother providers can scope different resources with the same name according todifferent projects, IBM CM can version only one resource of a given name.

v When IBM Content Manager is used as both the content store and the versionstore, resource metadata (such as project, workspace) are versioned along withthe resource itself. If used as a standalone version provider, these attributes arenot versioned.

v Client software for the version control solution you plan to use should beinstalled on the machine where you will install the WebSphere Portal contentpublishing Authoring Server.

Development environmentMachines in the development environment must have access to the content store,the Authoring Server, and the version store, if applicable. It is recommended thatthese machines use one of the WebSphere Studio Family of Products fordevelopment. WebSphere Studio should already be installed on the developmentmachine prior to installing the Wizards for WebSphere Studio (included in theWebSphere Portal content publishing installation).

Authoring environmentThe authoring environment is the machine where the WebSphere Portal contentpublishing workspace is located. The following are required components:v A database management systemv WebSphere Application Serverv WebSphere Portal content publishing

In addition, WebSphere Portal content publishing works with various library andrepository management systems. It also enables you to add workflow managementand versioning management. Most of these management systems can be installedlocally or remotely to the Authoring Server.

Notes:

1. Installing the sample is recommended. The sample makes it easy for you toverify your installation and get started quickly with WebSphere Portal contentpublishing.

2. If installing the Authoring Server on an AIX platform that uses a double-bytelanguage, ensure the appropriate fonts are installed:v For ja_JP or Ja_JP: X11.fnt.ucs.ttf


v For zh_CN or Zh_CN: X11.fnt.ucs.ttf_CNv For ko_KR: X11.fnt.ucs.ttf_KRv For zh_TW or Zh_TW: X11.fnt.ucs.ttf_TW

3. WebSphere Portal content publishing does not support log records that havedouble-byte characters, nor are double-byte or non-ASCII characters in patternmatching parameters.

Runtime environmentThe runtime environment is the production server that the Web site visitorinterfaces with, and contains the engines required to deliver Web content, topersonalize the Web content, and to record site metrics. The following are requiredcomponents:v A database management system

– Personalization supports DB2, Oracle, Informix, Microsoft SQL Server, andSybase

– Feedback supports DB2 and Oracle– LikeMinds supports DB2, Oracle, Microsoft SQL Server, or any

ODBC-compliant RDBMSv WebSphere Application Serverv WebSphere Portal content publishing

The Feedback (site analysis) engine allows site metrics to be viewed in theWebSphere Portal content publishing workspace. The rules-based Personalizationengines and the LikeMinds Recommendation Engine are optional installations. Ifyou plan to install LikeMinds Recommendation Engine, review the section on“Considerations for LikeMinds Recommendation Engine”.

When considering the amount of storage space needed for the Feedback database,it is important to remember that the amount of database space required for loggingdepends on the amount of traffic to the site, and the amount of data logged perlogging-enabled page can vary. However, a rough guideline that you can use is0.75 KB per record logged to the database. Therefore, a site that serves an averageof 20,000 logging-enabled pages per day, with each page generating three logrecords (through rules, categories, and so on), will generate approximately 45 MBof logged data per day.

Considerations for LikeMinds Recommendation EngineBefore you begin the installation, consider where you will put the major parts ofyour LikeMinds Recommendation Engine installation:v If possible, install the LikeMinds database on a different machine from

LikeMinds Personalization Server.Installing the database on a different machine from LikeMinds PersonalizationServer will increase LikeMinds performance. Ideally, you should use your fastestmachine for the database. You also will need disk space for your database. Theamount required will depend on your application and the number of users atyour site. For guidelines on estimating the size of your database refer to theLikeMinds Recommendation Engine documentation of the WebSphere Portalcontent publishing Help System.

v If you plan to use the Movie Site application, you can install it and the Webserver on the same machine as LikeMinds Personalization Server.

v If you serve large amounts of additional content from the same Web server, youmay want to install the Web server on a separate machine from LikeMinds

Chapter 3. Planning your installation 11

Personalization Server. However, Movie Site or your application must beinstalled on the same machine as the Web server. They do not need to be on thesame machine as LikeMinds Personalization Server.

v You must install the LikeMinds Admin Center onto any machine that has a Webserver, but it does not need to be on the same machine as LikeMindsPersonalization Server. The LikeMinds Admin Center is designed to be usedremotely.

The machine where LikeMinds Personalization Server is installed should have atleast 1 GB of RAM. LikeMinds requires at least 1 GB of disk space.

All machines that are part of your run-time installation should be located on thesame local area network. Placing the machines on separate networks is possible,but slow communications between machines can degrade performance.

Installing LikeMinds Recommendation Engine for asingle-systemFor a single-system sites, install LikeMinds Recommendation Engine as follows:v The RDBMS and LikeMinds Personalization Server should be on separate

machines, but can be on a single machine.v Movie Site (or your custom application) and the LikeMinds Admin Center

should be on the same machine as the Web server.

Installing LikeMinds Recommendation Engine for multiplesystemsFor multiple-system sites, install LikeMinds Recommendation Engine as follows:v Install the RDBMS onto its own machine, preferably the fastest.v Install the LikeMinds SDK onto each Web server and application server on your

system. Optionally, you can install the Movie Site application files onto eachclient machine as well. You do not need to install the LikeMinds PersonalizationServer server onto these client machines.

v For IBM DB2, make sure each client machine has the IBM DB2 Runtime Clientinstalled.

v For Oracle, make sure each client machine has the following Oracle-specificcomponents:– Oracle Client (including Net8 and SQL*Plus)– ORACLE_HOME environment variable set– TNSNAME entry in tnsnames.ora

Installing the LikeMinds Recommendation Engine utilities across multiplemachines: You can install the LikeMinds Personalization Server utilities andLikeMinds servers across multiple machines for load balancing. In general, youneed to install the LikeMinds Personalization Server itself, which includes itsutilities, onto each machine, but have its service running on only one machine. Youwill also need to disable or enable the LikeMinds Personalization Server utilities oneach machine as appropriate.

The following setup for Machines 1-4 is an example configuration:v Machine 1: Has the LikeMinds Recommendation Engine database.v Machine 2: Has a LikeMinds Personalization Server that serves as the

LikeMinds Recommendation Engine. Use the Control Panel Services applet to setthis service to run. It also has the buildstats, buildvisit, sifter, andaccumulator utilities, which need to be disabled as follows:


– buildstats and buildvisit: In the <LM_install_dir>\lrs\util\daily script,comment out the lines that refer to starting buildstats and buildvisit.

– sifter: In the <LM_install_dir>\lrs\server\prefetch script, comment outthe line that refers to starting the sifter.

– accumulator: Do not run the accumulator on this machine.

On the remaining machines, you can install the utilities separately, each with itsLikeMinds Personalization Server server disabled and with the appropriateutility enabled. To disable the LikeMinds Personalization Server, use the ControlPanel Services applet.

v Machine 4: Has a LikeMinds Recommendation Engine that is not enabled, andan enabled sifter. Use this machine only if you are using the Clickstream,Purchase, or Preference engine. The sifter must be running all the times in thebackground, so configure this system to start the sifter at boot time. For verylarge sites, you may want to have a sifter on more than one machine. If you douse multiple sifters, be sure that each sifter is looking at a distinct group ofusers. (Multiple sifters should not be looking at the same user). Refer to theLikeMinds Recommendation Engine documentation of the WebSphere Portalcontent publishing Help System for information on using multiple sifters.The buildstats, buildvisit, and the accumulator utilities on this machine areautomatically disabled as long as the LikeMinds Personalization Server on thismachine is disabled. If you plan to use the LikeMinds Personalization Server onthis system, you can disable buildstats and buildvisit by commenting outtheir start lines in the daily script.

Chapter 3. Planning your installation 13

Chapter 4. Preparing to install WebSphere Portal contentpublishing

Uninstalling WebSphere Portal content publishingNote: Do not attempt to remove WebSphere Portal content publishing from yourmachine by simply deleting or removing the enterprise archives. You will not beable to reinstall WebSphere Portal content publishing. If this occurs, go toChapter 8, “Manually uninstalling WebSphere Portal content publishing” onpage 63.

If WebSphere Portal content publishing is installed on your system, then you willneed to uninstall it by completing the following steps:1. If you had a previous installation of WebSphere Portal content publishing or

Lotus Domino Server, you should uninstall both before starting a newinstallation. If you have data in the WebSphere Portal content publishing thatyou want to preserve, backup the authoring environment databases.

2. Remove any Resource Collections using the Resource Console(http://<fullyqualifiedhostname>/wps/PersAdmin/adminframe.jsp). Click theResource Collections tab, select a resource collection from the drop-down listand click Delete; repeat until all are removed.

3. For Windows, go to the C:\Program Files\IBM\wcp\uninst directory and runwcpuninstall.exe. (You can also uninstall the program from the Add/RemovePrograms application in the Control Panel.)

4. For UNIX platforms, go to the /opt/IBM/WCP/uninst directory and execute thefollowing command:was_home/java/bin/java -cp wcpuninstaller.jar run

To ensure that your uninstall is complete:v Verify that the following directories for the WebSphere Portal content publishing

Web applications were deleted from the was_home\installedApps directory:– LMAdminCenter.ear– MovieSite.ear– Personalization_Email.ear– Personalization_Runtime.ear– wcm.ear– WCPDemo_Author.ear

v Verify that the temporary directories for WebSphere Portal content publishingwere deleted from was_home\temp\hostname\appserverName.

v Verify that the was_home\wcp directory was deleted.v Verify that the directory containing install.properties) was deleted (Program

Files\IBM\wcp on Windows, /opt/IBM/WCP on UNIX).

If you are using Solaris, run the following commands to ensure that youruninstallation is complete.v pkginfo | grep IBMWCP

If the system returns WebSphere Portal content publishing registrations, thenWebSphere Portal content publishing is not completely uninstalled.


v If WebSphere Portal content publishing registrations are returned, run thefollowing command for each WebSphere Portal content publishing registration:pkgrm IBMWCPxxx

where IBMWCPxx is the name of the WebSphere Portal content publishingregistration.

v Rerun pkginfo | grep IBMWCP

If you are using AIX, run the following command to ensure that youruninstallation is complete.v ODMDIR=/usr/lib/objrepos odmget vendor 2>&1 | tee /tmp/vendor.file

If the system returns WebSphere Portal content publishing registrations, thenWebSphere Portal content publishing is not completely uninstalled.

If you are using Linux, run the following command to ensure your uninstallationis complete.v rpm —qa | grep —i wcp

If any packages are returned, these must be removed before uninstallation iscomplete.

If you encounter any problems during uninstallation or verification ofuninstallation, refer to Chapter 8, “Manually uninstalling WebSphere Portal contentpublishing” on page 63.

Preparing databases and content stores

Configuring an Oracle databaseOracle must be configured to work with WebSphere Application Server andWebSphere Portal content publishing. The database configuration must be done bya qualified Oracle database administrator. For instructions on configuring Oraclefor the operating system where you have it installed, see the appropriate section.

Configuring Oracle on Microsoft Windows 2000 ServerTo configure Oracle to work with WebSphere Portal content publishing:1. Create a database for use by WebSphere Portal content publishing. The name of

the database is your choice, but it must be a different database than the oneused by WebSphere Application Server. Ensure that:v The characterset is UTF-8v The national language character set is UTF-8v The database is configured for the number of concurrent users you need to

supportv The SID for the database must be the same as the name.

2. Define the WebSphere Portal content publishing IDs with databaseadministration authority by creating the Oracle users PZNADMIN and EJBusing the following commands. (Note: if you do not want them to havedatabase administrator authority, skip to step 3). For values needed in the firstcommand, enter system as the ID and manager as the password. For the secondcommand, use PZNADMIN and EJB as the IDs.


sqlplus system/manager@xxxcreate user PZNADMIN identified by PZNADMIN_password;create user EJB identified by EJB_password;grant connect, resource, dba to PZNADMIN, EJB;quit

Where xxx is the Net Service Name (after the @ symbol) without the domain.3. If you do not want PZNADMIN and EJB to have database administrator

authority, type the following commands:sqlplus system/manager@xxxcreate user PZNADMIN identified by PZNADMIN_password;create user EJB identified by EJB_password;grant connect, resource to PZNADMIN, EJB;quit

Where xxx is the Net Service Name (after the @ symbol) without the domain.4. Locate the initialization file. In a typical install, it is located at

<oracle_home>\Ora81\database\initxxx.ora

where xxx is your SID.5. Modify the following line to the initialization files

open_cursors = 2500

6. Stop and restart the following Oracle services to pick up the changes to theinitialization filesv OracleServiceXXXv OracleServiceWCPDEMOv OracleOraHome81TNSListener

where XXX is the SID for the WebSphere Portal content publishing database.7. Verify that the hostname and SID are mapped to the correct Net Service Name

in the tnsnames.ora file.8. Test access to the new database and verify changes to open_cursors using the

PZNADMIN user ID by typing:sqlplus pznadmin/PZNADMIN_password@xxxshow parameter open_cursors

When a message is displayed indicating that the connection was successful,type exit.

Configuring Oracle on AIXTo configure Oracle to work with WebSphere Portal content publishing:1. Create a database. The name of the database is your choice, but it must be a

different database than the one used by WebSphere Application Server. Ensurethat:v The characterset is UTF-8v The national language character set is UTF-8v The database is configured for the number of concurrent users you need to

supportv The SID for the database must be the same as the database name.

2. Define the WebSphere Portal content publishing IDs with databaseadministration authority by creating the Oracle users PZNADMIN and EJBusing the following commands. (Note: if you do not want PZNADMIN and EJBto have database administrator authority, skip to step 3). For values needed in

Chapter 4. Preparing to install WebSphere Portal content publishing 17

the first command, enter system as the ID and manager as the password. For thesecond command, use PZNADMIN and EJB as the ID.sqlplus system/manager@xxxcreate user PZNADMIN identified by PZNADMIN_password;create user EJB identified by EJB_password;grant connect, resource, dba to PZNADMIN, EJB;quit



Where xxx is the Net Service Name (after the @ symbol) without the domain.4. Locate the WebSphere Portal content publishing and WCPDEMO database

initialization files. Change to the AIX Oracle user. Navigate to the initializationfiles, typically located atoracle_home/admin/xxx/pfile/initxxx.ora


open_cursors = 2500

6. Stop and restart the Oracle databases and listener to pick up the changes to theinitialization files.

7. Verify that the hostname and SID are mapped to the correct Net Service Namein the tnsnames.ora file.

8. Test access to the new database and verify changes to open_cursors using thePZNADMIN user ID by typing:sqlplus pznadmin/PZNADMIN_password@xxxshow parameter open_cursors


Configuring Oracle on SolarisTo configure Oracle to work with WebSphere Portal content publishing:1. Create a database. The name of the database is your choice, but it must be a


supportv The SID for the database must be the same as the database name

2. Define the WebSphere Portal content publishing IDs with databaseadministration authority by creating the Oracle users PZNADMIN and EJBusing the following commands. (Note: if you do not want PZNADMIN and EJBto have database administrator authority, skip to step 3). For values needed inthe first command, enter system as the ID and manager as the password. For thesecond command, use PZNADMIN and EJB as the ID.


sqlplus system/manager@xxxcreate user PZNADMIN identified by PZNADMIN_password;create user EJB identified by EJB_password;grant connect, resource, dba to PZNADMIN, EJB;quit




initialization files. Change to the Solaris Oracle user. Navigate to theinitialization files, typically located atoracle_home/admin/xxx/pfile/initxxx.ora


open_cursors = 2500





Before you use WebSphere Portal content publishing, you must stop theOracleOraHome81HTTPServer service.

Configuring Oracle on LinuxTo configure Oracle to work with WebSphere Portal content publishing:1. Create a database. The name of the database is your choice, but it must be a


supportv The SID for the database must be the same as the database name

2. Define the WebSphere Portal content publishing IDs with databaseadministration authority by creating the Oracle users PZNADMIN and EJBusing the following commands. (Note: if you do not want PZNADMIN and EJBto have database administrator authority, skip to step 3). For values needed in


the first command, enter system as the ID and manager as the password. For thesecond command, use WCPADMIN as the ID.sqlplus system/manager@xxxcreate user PZNADMIN identified by PZNADMIN_password;create user EJB identified by EJB_password;grant connect, resource, dba to PZNADMIN, EJB;quit




initialization files. Change to the Linux Oracle user. Navigate to theinitialization files, typically located atoracle_home/admin/xxx/pfile/initxxx.ora


open_cursors = 2500





Configuring a DB2 databaseIBM DB2 must be configured to work with WebSphere Portal content publishing.For instructions on configuring DB2, see the appropriate section.

Enabling JDBC2.0Before you can install WebSphere Portal content publishing, your installation ofDB2 must be configured for JDBC2.0.

To enable JDBC2.0 on Microsoft Windows:1. From Windows’ Services panel, stop the WebSphere Application Server.2. Stop all DB2 processes. If any DB2 services fail to stop, open the DB2

Command Line Processor and type:force application all

This will drop all connections to DB2. You can now stop the DB2 services in theServices panel.


3. Open a DB2 command window, go to the \Program Files\SQLLIB\java12directory, and run the following file:usejdbc2.bat

4. Start the DB2 services you stopped in Step 2 and WebSphere ApplicationServer.

To enable JDBC2.0 on UNIX, select the JDBC2.0 version of db2java.zip in theDriver Location field of the appropriate Database Configuration panels during theinstallation of WebSphere Portal content publishing:v Linux: /usr/IBMdb2/V7.1/java12/db2java.zipv AIX: /usr/lpp/db2_07_01/java12/db2java.zipv Solaris: /opt/IBMdb2/V7.1/java12/db2java.zip

Creating and configuring a DB2 database for WebSphere Portalcontent publishingIf you have an existing database, will be creating your own database, or will beusing a remote database:1. Open a DB2 Command Window and execute the following command:

DB2 CREATE DB MY_DATABASE USING CODESET UTF-8 TERRITORY USCOLLATE USING IDENTITY

Where MY_DATABASE is the name of the database you are creating. Substituteyour territory code if different from US.

2. Configure the database for WebSphere Portal content publishing by executingthe following command:DB2 UPDATE DB CFG FOR MY_DATABASE USING APPLHEAPSZ 4096 LOGFILSIZ 3000LOGPRIMARY 25 LOGSECOND 25

If creating a database for Feedback, use instead the following command:DB2 UPDATE DB CFG FOR MY_DATABASE USING APPLHEAPSZ 4096 LOGFILSIZ 4096LOGPRIMARY 4 LOGSECOND 25

Some additional parameters that are not necessary but can be used to improveperformance the Feedback database include:v DBHEAP = 4096v STMTHEAP = 4096v CATALOGCACHE_SZ = 256v LOCKLIST = 1024v And, on the database manager: JAVA_HEAP_SZ = 4096

The database manager variable may be set with the following command:db2 update dbm cfg using JAVA_HEAP_SZ 4096

Installing IBM Content ManagerIBM Content Manager must be installed prior to installing WebSphere Portalcontent publishing. When installing IBM CM, two programs are required: ContentManager and IBM Enterprise Information Portal (EIP). Note the following:v The IBM CM databases can be on the same machine as the WebSphere Portal

content publishing Authoring Server, or on any number of machines.v IBM EIP must be installed on the same machine as the WebSphere Portal content

publishing Authoring Server.


Installing and configuring IBM Content ManagerTo manage large collections of data or multimedia collections, you may want touse WebSphere Portal content publishing with IBM Content Manager.

Before you install WebSphere Portal content publishing to work with IBM ContentManager, you must install IBM Content Manager and IBM Enterprise InformationPortal and their prerequisites. Follow the installation instructions provided witheach of these products.

Verifying your IBM Content Manager installation: After you have installed IBMContent Manager, IBM Enterprise Information Portal and their prerequisitesoftware, you should test your system and verify that IBM Content Manager(library server, resource manager, system administration client) and IBM EnterpriseInformation Portal (administration database, Content Manager connector) areworking. You can do this by following the instructions on testing the serverinstallation and configuration in the IBM Content Manager guide to Planning andInstalling Your Content Management System. You can also verify that IBM ContentManager and IBM Enterprise Information Portal are working properly bycompiling the samples in the %CMBROOT%\samples\java\beans directory.

To compile the IBM Content Manager samples:v Ensure that the IBM DB2 Text Information Extender has been started.v In the WebSphere Application Server Administration Console, ensure that your

icmrm server is started.v Start the EIP development environment.v Change directories to %CMBROOT%\samples\java\beans.v Run the following command javac *.java

v Using the IBM Content Manager user interface, create a new item type of typeResource Item. For example, create an item type called testitem.

v Use the TImport sample to create data from a file.v Use the TExport sample to export data to a file.

Tip: Use a valid extension like .txt or .htm for your test file. For example:TImport ICM icmnlsdb icmadmin password testitem readme.html testname=123

If TImport works, you are able to use the resource manager part of IBMContent Manager.

If you encounter problems with importing, see the troubleshooting section inPlanning and Installing Your Content Management System

Installing WebSphere Portal content publishing to use IBM Content Manager:When you install WebSphere Portal content publishing, you will be asked toprovide the following information about your IBM Content Manager installation:

Library server database nameThe name you type in the WebSphere Portal content publishing InstallationServer field.

Library server database administration IDThe ID you type in the WebSphere Portal content publishing InstallationUser ID field.


PasswordThe password you use to administer the IBM Content Manager librarydatabase.

Resource manager database nameThe name you type in the WebSphere Portal content publishing InstallationDefault Resource Manager Name field.

You can use IBM Content Manager for storage and management of content as wellas version control. For instructions on using IBM Content Manager for versioncontrol, see the section in the WebSphere Portal content publishing Administrator’sGuide on version control.

Preparing workflow management

Setting up Lotus WorkflowInstructions for installing Lotus Domino™ Server are provided below.

Notes:

1. Do not install Lotus Domino Server on a machine where Lotus Notes™ or LotusDomino are already installed.

2. You do not have to install Lotus Domino on the same machine where youinstalled WebSphere Application Server and WebSphere Portal contentpublishing.

The installation and configuration of Lotus Domino Server consists of thefollowing steps:v “Installing Lotus Domino Server”v “Configuring Lotus Domino Administrator”v “Sample users and groups in Lotus Domino Administrator” on page 24v “Configuring WebSphere Security and Domino SSO” on page 27v “Configuring Single Sign-on (SSO) between Domino and WebSphere” on page 27

Installing Lotus Domino ServerTo install Lotus Domino Server, use WebSphere Portal installation CD 8 and choosethe installation file for your operating system. The installation will lead youthrough most of the necessary configuration steps. During installation of LotusDomino Server, you will be prompted for the following information:v Domain Namev Certifier Organizationv Certifier Passwordv Administrator user ID and password

Ensure that the Domain Name and Certifier Organization match your LTPADomain Name. You can accept default values in the other fields.

During the Lotus Domino Server installation you will also be prompted toconfigure SSO in Lotus Domino. To do this task, you will need to enter the locationof the keys file and password used to generate the LTPA key from your WebSphereApplication Server installation.

Configuring Lotus Domino AdministratorThe first time you use Lotus Domino Administrator you will be prompted to dothe following configuration steps:


1. Start the Lotus Domino Administrator. From the Start Menu, select Programs→Lotus Applications → Lotus Domino Administrator. The Lotus Notes ClientConfiguration dialog will appear.

2. Click Next to bypass the introductory page.3. Select I want to connect to a Domino Server and click Next.4. Select Set up a connection to a local area network (LAN) and click Next.5. Type your Domino server name and click Next. The Domino server name is

your HostName/YourDomainName, for example host1/locale.ibm.com.6. Select Use My Name as Identification, type the ID for Domino Administrator

that you defined during installation as your User name, (the default isDomino Admin) and click Next.

7. Click Next to bypass the confirmation page.8. Click Next to bypass the Internet Mail Account page.9. Click Next to bypass the News Server page.

10. Click Next to bypass the Internet Directory Server page.11. On the Connect through a Proxy Server page, select the option that meets

your needs and click Next.

Note: If you do connect through a proxy, the next page will require you totype your proxy information.

12. Click Next to bypass the Internet Connection Type page.13. Click Finish.14. Type your Domino Administrator password, and click OK.

Note: You may receive the message ″Notes Error - Specified Command is notavailable from the Workspace″. You can ignore this error message andclick OK.

Sample users and groups in Lotus Domino AdministratorYou will need an ID for administering WebSphere Application Server Security andLotus Domino Administrator. For additional information on what ID to use, referto the WebSphere Portal documentation.

There are four users identified with roles in the samples that are created duringinstallation, as well. These roles are defined to the sample workflow processes. Ifyou wish to use the samples or work through the Getting Started tutorial, youshould create these users.

For security purposes, we strongly recommend that you update these users withdifferent passwords that adhere to standard password security guidelines. Theseuser IDs and passwords should be treated as you would treat any other IDs andpasswords because people using them will have all the server privileges youspecify.

Finally, to fully explore the sample workflows, you can use these instructions tocreate additional users.

Installing the Lotus Workflow Process Designer’s GuideIf your team plans to design their own workflow processes, you will want toinstall the Process Designer’s Guide.

To install the Process Designer’s Guide:


1. From the WebSphere Portal installation CD 10, copy\lwfarchitect\lwf_process-designer_30_en.nsf to the data directory whereyou installed Lotus Workflow Architect. If you did a typical install, copy thefile to \Lotus\Notes\data.

2. In the directory where you installed Lotus Workflow Architect, modify theworkflow.ini file so that the HelpDBPath is set to reference the fully qualifiedpath where you copied lwf_process-designer_30_en.nsf. If you did a typicalinstall, the workflow.ini file is in Lotus\Workflow\Architect.

Alternatively, you can use the PDF of the Process Designer’s Guide on CD 10:\lwfarchitect\lwf_process-designer_30_en.pdf.

Configuring Processes in Lotus Workflow Architect

Opening the workflow document with Lotus Workflow Architect:

1. Start Lotus Workflow Architect (Start Button → Programs → Lotus Workflow 3.0→ Lotus Workflow Architect)

2. Open the Domino databases:a. Select File → Open Databases.b. Create a new Profile Name.c. Under Data Source Type, select Design Repository and click Browse.d. Under the Server drop-down menu, select your server. If prompted to enter

your password, which is password.e. Under the database menu, select LWF Design Repository R3.0 and click

OK.f. Repeat the above process for the Application database, Process Definition

database, and Notes Organization Directory, which will match up withLWF Application R3.0, LWF Process Definition R3.0, and LWFOrganization R3.0 respectively.

g. Click OK.3. Import SimpleChangeProcess.lwf . Select File→ Import→Browse and select

SimpleChangeProcess.lwf.4. Select File →Save Process.5. Select File →Activate Process and click OK.

WebSphere Portal content publishing also provides two other workflow processes:v SimplerChangeProcess.lwf

v SimplestChangeProcess.lwf

You can import these processes using the same same instructions.

Configuring the process in Lotus Domino Administrator:

1. Start Lotus Domino Administrator and switch to the WCP Administrator ID.a. If you installed Lotus Domino Administrator and Lotus Domino Server on

different machines, you need to configure the WPCP Administrator ID. Ifnot, you can skip to 1b. To configure the WCP Administrator ID:1) Log in with the Lotus Domino Administrator ID.2) Click the Administration tab.3) Click the People and Groups tab.4) Click Administrator, WCP and click Edit Person.


5) Detach the userID file to your Lotus/notes/data directory. In the Filename field, type WCPAdmin.id to rename the file.

6) Close Lotus Domino Administrator and reopen it.b. If it is not already there, copy WCPAdmin.id from the Lotus/domino/data

directory to the Lotus/notes/data directory.c. On the password prompt window, click Cancel.d. From the Choose User ID to Switch to window, navigate to the

Lotus/notes/data directory and select WCPAdmin.id.If you need to switch back to using the Domino Administrator ID, performthe previous steps but navigate to Lotus\Notes\data and select user.id.

e. Click the Administration tab.2. Open the Lotus Workflow Application database with Lotus Domino

Administrator.a. Verify that the Server is your Lotus Domino Server is and not your Local

Server.

Note: If you are using your Local Server, select Files → Open Server andselect your Domino Server.

b. In Lotus Domino Administrator, click the Files tab.c. In the list of files on the right, double-click LWF Application R3.0.

Note: If you don’t see a list of files, click the refresh button.3. On the left frame, select Administration→ Cache .4. On the top frame, click Update Process Cache.

Note: If a message appears, click OK.5. Close the LWF Application R3.0 database.6. Open the LWF Application R3.0 database and close it again.

Enabling e-mail notification in Lotus Domino Administrator foruse with WebSphere Portal content publishing samplesBy default, e-mail notification for the sample users is not enabled. If you want thesample users to receive notification of workflow events, follow these steps toenable e-mail notification:1. Log in as the WCP Administrator.2. Click the Administration tab.3. Click the People and Groups tab.4. Select the person (Dave, Greg, Rob or Tara) you want to set e-mail notification

for and click Edit Person.5. Click the Mail tab.6. In the Domain field, enter your domain.7. Click Save and Close.8. Click File→Tools→Switch ID.9. Select the user ID you want to configure e-mail notification for (see Table 1 on

page 27) and click Open.10. In the login window, type the user’s password and click OK.11. Ensure that appropriate server is selected.

Note: If you are using your Local server, select Files→ Open Server and selectyour Domino Server.


12. Click the Files tab.13. Click the mail folder. If a database cover page is displayed, close it.14. Double-click the user you are configuring e-mail notification for to check their

mail.

You will need to repeat these steps to enable e-mail notification for each of thesample users.

Table 1. WebSphere Portal content publishing sample users and IDs

User ID

Dave DDev

Greg GContent

Rob RPro

Tara TWeb

Configuring WebSphere Security and Domino SSO

Configuring WebSphere Application Server security:

1. Start the Lotus Domino Server.2. Start the WebSphere Application Server.3. Open the WebSphere Advanced Administration Console.4. Select Console→ Security Center.5. Select the General tab, check Enable Security.6. Select the Authentication tab and fill in the following fields:

v Authentication Mechanism: select Lightweight Third Party Authentication(LTPA).

v Check Enable Single Sign On (SSO).v Domain: <yourdomainname>, for example: locale.ibm.com.v Verify that the LDAP radio button is selected.v Security Server ID: <ID specified during installation>, for example:

DAdmin.v Password: password.v Host: <hostname>.<domain> (where <hostname>.<domain> is your hostname

and domain name).v Directory Type: Domino 5.0v Leave all other fields set to default and click OK.v Type your LTPA password, which is password.

Note: The message ″The changes will not take effect until the admin serveris restarted″ will appear, click OK.

7. Stop and start the WebSphere Application Server.8. Open the WebSphere Advanced Administrative Console.9. Verify that the Administrative Console prompts you for a login. Use UserID

DAdmin and password.

Configuring Single Sign-on (SSO) between Domino and WebSphere: Toconfigure single sign-on you need to generate LTPA keys and enable singlesign-on.


Generating LTPA keys:

1. Open the WebSphere Advanced Administrative Console.2. Select Console→ Security Center.3. Select the Authentication tab.4. Click Generate Keys... and specify password as the LTPA password.5. Click Export Key....6. In the Export to File dialog, under File name, type WAS_HOME\wcp\DOMWAS.key.

For example on Windows systems typeC:\WebSphere\AppServer\wcp\DOMWAS.key. On UNIX® platforms, type the nameof a directory on the UNIX file system, for example /tmp/DOMWAS.key.

7. Click Save.8. Close the Administration Console.9. Stop and Start the WebSphere Application Server.

Enabling Single Sign-on: Enable Single Sign-on (SSO) in Domino. (Note: If you hadalready enabled WebSphere Application Server when you installed Lotus DominoServer and you specified the key files during the Lotus Domino Server installation,start the WebSphere Application Server and skip these enabling single sign-onsteps.)1. Open Lotus Domino Administrator.2. Select the Administration tab and Files tag.3. Verify that the Server is your Lotus Domino Server is and not your Local

Server.

Note: If you are using your Local Server, select Files → Open Server andselect your Domino Server.

4. Double-click names.nsf (the Address book for your domain).5. Select View→ Server→ Other → Server/Servers and click OK.6. On the top frame, select Web → Create Web SSO Configuration.7. For the Token Domain, type your domain.8. For the Domino Server Name use select your Domino server machine from

the drop-down list and click OK.

Note: You may need to change the top drop-down menu to your domain’sAddress Book.

9. Click Keys and select Import WebSphere LTPA Keys. For Windows, typeWAS_HOME\AppServer\wcp\DOMWAS.key, for exampleC:\WebSphere\AppServer\wcp\DOMWAS.key. For UNIX platforms, FTP the keyfile from the UNIX server to the Windows machine where the DominoAdministrator is installed and specify this location.

10. Type password, for the password and click OK.

Note: The Web SSO Configuration dialog will appear with the message″Successfully imported keys″. If you do not see this message, importthe key again making sure you enter in the correct path and password.

11. Verify that the LDAP Realm is <hostname>.<domain> (replacing hostname anddomain with your hostname and domain name, for examplehost1.locale.ibm.com).

12. Click Save and Close.13. Close the Address book.


14. Restart the Lotus Domino Server by typing the command restart server inthe Lotus Domino Server command window. Verify the following line showsup when the server restarts:HTTP: Successfully loaded Web SSO Configuration

15. If you have Lotus Domino installed on the same machine as WebSphereApplication Server and WebSphere Portal content publishing, copy the LotusDomino DIIOP file from your Lotus Domino directory (for example,C:\Lotus\Domino\Data\domino\html\diiop_ior.txt) to your IBM HTTP ServerRoot document directory (for example, C:\IBM HTTP Server\htdocs). To verifythe file, open a browser and, in the Location field, typehttp://hostname/diiop_ior.txt.

16. Start the WebSphere Application Server.

Verifying your installation

Verifying that the Java/COM Restrictions are set correctly in Lotus DominoServer: In Lotus Domino Administrator, select the Security tab and update theAgent Restrictions and Java/COM Restrictions, if necessary, as follows:v Run restricted LotusScript/Java agents: Domino Admin/ locale.domain.comv Run unrestricted LotusScript/Java agents: wcmtest2/locale.domain.com Domino

Admin locale.domain.comv Run restricted Java/Javascript/COM: Workflow Participants, WCP

Administrator/locale.domain.comv Run unrestricted Java/Javascript/COM: Domino Admin/ locale.domain.com

Verifying immediate backgrounder processing in Lotus Domino Server: Verifyimmediate backgrounder processing to Domino by checking for the following linesinc:\lotus\domino\notes.ini:v AMGR_DOCUPDATEAGENTMININTERVAL=0v AMGR_DOCUPDATEEVENTDELAY=0v AMGR_NEWMAILAGENTMININTERVAL=0v AMGR_NEWMAILEVENTDELAY=0

Changing servers: verifying your Lotus Workflow setup: If you change servers,you may want to go through these steps to ensure that WebSphere Portal contentpublishing is enabled for Lotus Workflow.1. Verify the WCM.properties file

(\WebSphere\AppServer\wcm\WCM.properties):a. Verify the value of wcm.workflow.ldaphost equals

<hostname>.<domain>(replacing <hostname> with your host name and<domain> with your host name and domain name), for examplehost1.ibm.com.

2. If you make changes to the WCM.properties file, stop and start the WebSphereApplication Server.

3. Open and log into the WebSphere Application Server Administrative Console.4. In the left frame, expand WebSphere Administrative Domain .5. Verify the that WebSphere Application Server where you have WebSphere

Portal content publishing installed has started.6. Expand Enterprise Applications.7. For each WCM application, right-click the application and select Start.


Preparing security/authentication

Local operating systemOn the machine where the Authoring Server will be installed, ensure that theindividuals who will be accessing the WebSphere Portal content publishingworkspace are identified as system users. In addition, if you want to use theWebSphere Portal content publishing sample, add the following users:

User ID Password

dave dave

greg greg

rob rob

tara tara

WCPAdmin password

These User IDs and passwords must also be added to the userInfo.properties fileafter installation of the WebSphere Portal content publishing Authoring Server iscomplete. See“Editing the userInfo.properties file” on page 41.

LDAPIf you have are using a new installation of IBM Directory Server as your LDAPserver, confirm that it is properly configured for WebSphere Portal contentpublishing:1. Confirm the distinguished name of the suffix:

a. Open the IBM Directory Server Administration Console (open a browserand enter the URL http://hostname/ldap). Login using a valid user ID andpassword.

b. Click Settings > Suffixes.c. Verify the distinguished name of the suffix you plan to use. For example, if

the computer name is hostname.locale.ibm.com, the suffix would bedc=ibm,dc=com. If you change the Suffix DN, click Update.

d. Restart the LDAP server.2. Import the WPSConfig.ldif file:

a. Copy the file WPSConfig.ldif to any folder on your LDAP server (forexample, C:\WPSConfig.ldif). This file is provided on the WebSphere Portalinstallation CD 8, in the wps folder.)

b. Using a text editor, edit the file so that the host suffixes match your hostsuffix. For example, change instances of dc=yourco,dc=com to dc=ibm,dc=com.

c. Save and close the file.d. In the IBM Directory Server Administration Console, stop the LDAP server.

(Click Current State > Start/Stop and then click Stop. Wait for the message″The current server is stopped.″)

e. Select Database > Import LDIF.f. Enter the path to the LDIF file (for example, C:\WPSConfig.ldif) and click

Import.3. Create users:

a. Open the IBM Directory Management tool (for example, click Start >Program > IBM Directory Server > Directory Management Tool).


b. Click Directory Tree > Browse Tree. Verify that the users wpsadmin andwpsbind, and the group wpsadmins, exist as a result of importing theWPSConfig.ldif file.

c. To add a user, click cn=users in the tree and then click Add.d. In the Add an LDAP Entry window, replace cn=newEntry with

uid=username (where username is the user ID of the user you want to add).e. Enter the password for the user.f. Click the Other tab and enter the user ID in the uid field.g. Click Add.h. If you plan to use the WebSphere Portal content publishing Authoring

Server Sample, create the following users:v uid=WCPAdmin,cn=users,cn=ibm,cn=com (password is password)v uid=dave,cn=users,cn=ibm,cn=com (password is dave)v uid=tara,cn=users,cn=ibm,cn=com (password is tara)v uid=rob,cn=users,cn=ibm,cn=com (password is rob)v uid=greg,cn=users,cn=ibm,cn=com (password is greg)

4. Create groups:a. To add a group, click cn=groups in the tree and click Add.b. In the Add an LDAP Entry window, select Group as the Entry Type.c. If you plan to use the WebSphere Portal content publishing Authoring

Server Sample, create the following groups:v cn=Content Contributor,cn=groups,dc=ibm,dc=com (add

uid=dave,cn=users,cn=ibm,cn=com anduid=greg,cn=users,cn=ibm,cn=comto its member field (member/groupmembers)

v cn=Project Lead,cn=groups,dc=ibm,dc=com (adduid=rob,cn=users,cn=ibm,cn=com anduid=WCPAdmin,cn=users,cn=ibm,cn=comto its member field(member/group members)

v cn=Content Publisher,cn=groups,dc=ibm,dc=com (adduid=tara,cn=users,cn=ibm,cn=com to its member field (member/groupmembers)

v cn=Domain Expert,cn=groups,dc=ibm,dc=com (adduid=rob,cn=users,cn=ibm,cn=com to its member field (member/groupmembers)

Lotus DominoIf you are using Lotus Domino for security but not for Lotus Workflow, thenperform the steps in “Configuring WebSphere Security and Domino SSO” onpage 27. If you have already configured Lotus Workflow, then you have alreadycompleted this step.

Preparing version controlYou have the option of using any of the following version control systems withWebSphere Portal content publishing: IBM Content Manager (if using IBM CM asyour content repository), CVS, ClearCase, or the version control system providedas part of WebSphere Portal content publishing.

The client software for the version control system that you plan to use must beinstalled on the machine where WebSphere Portal content publishing Authoring


Server will be installed. No further preparation or configuration is required priorto installing WebSphere Portal content publishing.

Preparing to install LikeMinds Recommendation EngineThis section describes how to prepare your system for a run-time installation. Itcovers the following topics:v “Using an existing database for your LikeMinds installation”v “Using a different table schema from the default tables”v “Creating the database for Microsoft SQL Server”v “Configuring an ODBC DSN for Microsoft SQL Server” on page 33v “Preparing for a LikeMinds Recommendation Engine installation on Oracle” on

page 33v “Preparing for a LikeMinds Recommendation Engine installation on IBM DB2”

on page 34v “Configuring a connection driver for Oracle” on page 33

Using an existing database for your LikeMinds installationIf you plan to use an existing database, including existing tablespaces and tables,go to Using Movie Site, the LikeMinds Admin Center, or the LikeMinds SDK forinformation on planning the installation of these features.

If you have existing tables that have the same structure as the LikeMinds tables,you can map them to the LikeMinds tables. For details about the tables or how toset up mappings for tables that use different names, refer to the LikeMindsRecommendation Engine documentation of the WebSphere Portal contentpublishing Help System.

Using a different table schema from the default tablesThe installer will create a default set of LikeMinds tables for your LikeMindsdatabase.

Creating the database for Microsoft SQL ServerYou or your database administrator must create the database that will contain theLikeMinds data before you install LikeMinds Recommendation Engine. You canuse an existing database. Before continuing, verify that your database is backed upregularly so that you do not risk losing your LikeMinds data.

The database you use for LikeMinds must have a separate transaction log device,which should be about the same size as your data device. By default, MicrosoftSQL Server 7.0 and SQL Server 2000 creates a separate transaction log device whenyou create the database; they are approximately 1MG each. When you create thedatabase and log device, be sure to enable the Automatically grow file option,since some LikeMinds tables can grow quite large. You can set the automaticgrowth to be by megabytes or percentage.

When you create the database, make sure the Select Info/Bulk Copy and TruncateLog on Checkpoint options are on. (They are on by default.) Leave the TruncateLog on Checkpoint option on while you load the database and set up yourapplication. Be sure to disable Truncate Log on Checkpoint before your sitebecomes active to allow recovery from damage to the database. We recommendthat you set up frequent full backups and daily transaction log dumps.


You will also need to create the database user and password which the LikeMindsRecommendation Engine will use to connect to the database. Make sure that thisuser has database table creation privileges.

For Microsoft SQL Server 7.0, tune the memory to half the size of the physicalmemory.

Configuring an ODBC DSN for Microsoft SQL ServerMicrosoft Windows NT and Microsoft Windows 2000 include an ODBC DSN forMicrosoft SQL Server. The LikeMinds installer allows you to configure the ODBCDSN during installation. You can configure it before installation, by using theODBC Data Sources utility in the Control Panel.

To determine which ODBC drivers are installed on your system, open the ControlPanel and double-click ODBC. Click the ODBC Drivers tab to see a list of drivers.

If you create a Data Source Name beforehand, be sure to record the Data SourceName you create. You will need to supply this name during the LikeMindsinstallation.

Note: If using Microsoft Windows NT, there is a problem creating the ODBCconnection to the database in order to load the configuration table duringinstallation. Refer to Chapter 7, “Troubleshooting” on page 59.

Preparing for a LikeMinds Recommendation Engineinstallation on Oracle

Perform the following tasks before installing the LikeMinds RecommendationEngine:1. Create the LikeMinds database.2. Configure a TNS service name for the LikeMinds database’s connection driver.3. Plan the installation for Movie Site and the LikeMinds SDK. (See Using Movie

Site, the LikeMinds Admin Center, or the LikeMinds SDK.)

Creating the database for OracleYou or your database administrator must create the database that will contain theLikeMinds data before you install LikeMinds Recommendation Engine. You canuse an existing database. Before continuing, verify that your database is backed upregularly so that you do not risk losing your LikeMinds data.

If you are installing Oracle (either Oracle 8 or 8i), perform a custom installation,installing all options. If you are installing Oracle 8, you do not need to install theMigration utility.

Be sure to include the following components on the Oracle server machine and oneach client machine:v Net8v SQL*Plusv The Oracle online documentation

Configuring a connection driver for OracleYou need to configure the Oracle native driver to connect LikeMinds with yourOracle database. This involves installing the Oracle client software and configuringa local TNS service name to connect to either the local or remote Oracle databaseinstance.


To create the TNS service name, use Net8 to create (TNS) entry for each SID. TheLikeMinds Recommendation Engine uses the TNS entry name to connect to eachremote Oracle client machine. We recommend that the TNS service name matchthe SID, since the SID is guaranteed to be unique for each database installed on themachine.

Configuring AIX systems using OracleBefore installing LikeMinds on an AIX system using Oracle, set the LIBPATH to:LIBPATH = /usr/lib:/lib:<ORACLE_HOME>/lib

Preparing for a LikeMinds Recommendation Engineinstallation on IBM DB2

You will need to perform the following tasks before you run the LikeMindsRecommendation Engine installer if your RDBMS is IBM DB2:1. Create the LikeMinds database.2. Create an ODBC DSN for your LikeMinds database.3. Plan the installation for Movie Site, the LikeMinds Admin Center, and the

LikeMinds SDK. (See Using Movie Site, the LikeMinds Admin Center, or theLikeMinds SDK.)

Creating the LikeMinds databaseCreate a database for LikeMinds, but do not populate it with any data. Theinstaller will overwrite this database during installation with a new database.

Be sure to record the database you create. You will need to supply this nameduring the LikeMinds installation.

Creating the LikeMinds tablesIf you want to bulk load item and user data, you can write scripts similar to theMicrosoft SQL Server table creation scripts.

If you have existing tables that have the same structure as the LikeMinds tables,you can map them to the LikeMinds tables.

For details about the tables or how to set up mappings for tables that use differentnames, refer to the LikeMinds Recommendation Engine documentation of theWebSphere Portal content publishing Help System.

Configuring an ODBC database driverYou need to configure the ODBC driver connection before installing LikeMinds. Todo so, use the ODBC Data Sources utility in the Control Panel. Microsoft WindowsNT supplies ODBC drivers you can use, or you can use one specific to yourRDBMS. You cannot configure the ODBC driver during the LikeMinds installation.

Be sure to record the Data Source Name you create. You will need to supply thisname during the LikeMinds installation.

Configuring AIX systems using DB2Before installing LikeMinds on an AIX system using DB2, set the LIBPATH to:LIBPATH = <DB2_install_dir>/install/sqllib/lib


Using Movie Site, the LikeMinds Admin Center, or theLikeMinds SDK

WebSphere Application Server requires the following before you begin theLikeMinds installation:v Plan to install the LikeMinds SDK, Movie Site, and the LikeMinds Admin Center

onto the same machine as WebSphere Application Server.v Make sure that the WebSphere Application Server JSP compiler is enabled.

Configuring your system for Movie SiteMovie Site Seed Data: The installer will add seed data for a Movie Site database.When a database is initially created using the seed data, for IBM DB2 and Oracle,the only user who can log in is likeminds, with the password likeminds. (For SQLServer, the login and password can be for any database user has access. For otherODBC databases, it depends on the RDBMS login and password.) You can, ofcourse, add new users.


Chapter 5. Installing WebSphere Portal content publishing

During the WebSphere Portal content publishing installation process, or after youhave started WebSphere Portal content publishing, if you encounter errors, see thesection on troubleshooting or the README file.

To install WebSphere Portal content publishing, use WebSphere Portal installationCD 5.

Note: Close the WebSphere Application Server Administrative Console before youuninstall or install WebSphere Portal content publishing.

Installing the development environment

WebSphere StudioInstallation of WebSphere Studio Application Developer is optional; however, ifyou are going to use the WebSphere Portal content publishing wizards forWebSphere Studio, you need to install WebSphere Studio Application Developer ifyou do not already have one of the WebSphere Studio Family of Products.

To install WebSphere Studio Application Developer:1. Load the CD containing WebSphere Studio Application Developer (WebSphere

Portal installation CD 7). If the Setup Manager starts, close it.2. On the CD, run the file wsad\win\setup.exe (or wsad\linux\install.sh for

Linux). The InstallShield wizard will start.3. Click Next.4. Read and accept the license agreement. Click Next.5. On the Destination Folder dialog, specify the destination directory for

WebSphere Studio Application Developer. Click Next.6. On the Primary User Role dialog, choose the role that best describes your

development needs. Click Next.7. On the Select Version Control Interface dialog, select the version control

interface that you want to use. Click Next and then Install.8. When the installation is complete, click Finish.

WebSphere Portal content publishing wizards for WebSphereStudio

Uninstalling earlier versions of the WebSphere Portal contentpublishing wizardsIf one of the WebSphere Studio Family of Products is already installed, you mustuninstall any earlier versions of the WebSphere Portal content publishing wizardsor the WebSphere Personalization wizards for WebSphere Studio. To uninstall thewizards:1. Close any open copies of WebSphere Studio on your machine.2. Click Start > Settings > Control Panel > Add/Remove Programs.


3. Select any of the following from the list of currently installed programs: IBMWebSphere Personalization wizards for WebSphere Studio Developer or IBMWebSphere Portal content publishing.

4. Click Change/Remove.5. Follow the instructions to remove the wizards.

Installing the WebSphere Portal content publishing wizardsTo install the WebSphere Portal content publishing wizards using the WebSpherePortal content publishing installer:1. On the machine with WebSphere Studio, load the CD that contains WebSphere

Portal content publishing (WebSphere Portal Server CD 5). If the SetupManager starts, close it.

2. Using Windows Explorer, run the file wpcp\wcpinstallwin.exe (or java —cpwcpinstall.jar run for Linux). The InstallShield wizard will start.

3. Click Next.4. On the Feature Selection panel, check Wizards for WebSphere Studio and

click Next.5. Confirm the location of WebSphere Studio. If no installation of WebSphere

Studio was found, you can type the location or browse for it. Click Next.6. Click Install. The wizards will be installed to the folder you specified in the

previous panel.7. When the installation is complete, click Finish.8. If necessary, restart WebSphere Studio.

You may manually install the wizards to WebSphere Studio. To manually installthe wizards:1. On the machine with WebSphere Studio, load the CD that contains WebSphere

Portal content publishing. If the Setup Manager appears, close it.2. Using Windows Explorer, locate the file iwcp_eclipsetools.zip in the

wpcp\eclipsetools folder on the CD.3. Use a file extraction utility to open the iwcp_eclipsetools.zip archive.4. Extract the contents of the archive to <studio_root>\plugins. Maintain the

directory structure of the files in the archive.5. If necessary, restart WebSphere Studio.

Verifying the installationTo verify the installation, ensure the following folders have been created:v <studio_root>\plugins\com.ibm.wcm.resource.wizards

v <studio_root>\plugins\com.ibm.wcm.resource.wizards.doc

Accessing the WebSphere Portal content publishing wizardswithin WebSphere StudioTo access the WebSphere Portal content publishing wizards within WebSphereStudio:1. Start WebSphere Studio.2. Click Help > Help Contents.3. In the navigation tree, click Tasks > Using WebSphere Portal content

publishing > Adding WebSphere Portal content publishing resource wizardsto a perspective and follow the instructions.


Browse WebSphere Studio’s help system for assistance on setting up WebSpherePortal content publishing projects, migrating Web Content Publisher andWebSphere Personalization projects, setting up publish servers, and using thewizards.

Installing the authoring environment

Installing the Authoring Server and Sample

Installing the WebSphere Portal content publishing AuthoringServer and SampleTo install the WebSphere Portal content publishing Authoring Server:1. Load the CD that contains WebSphere Portal content publishing (WebSphere

Portal Server CD 5). If the Setup Manager starts, close it.2. Run the file wpcp\wcpinstallwin.exe for Windows platforms (or unixinst.sh

for AIX, Solaris or Linux).v On Windows, the InstallShield wizard will launch.v On AIX, Solaris, or Linux, you will be prompted for the WebSphere

Application Server root directory and (if using DB2) the home directory ofyour DB2 instance owner; then the InstallShield wizard will launch.

3. Click Next.4. Check Authoring Server and click Next. (If WAS security is enabled, you will

be prompted for a user ID and password.)5. Check Authoring Server. If you want to install the optional Authoring Server

Sample, check it also. Click Next.6. In the first window of the panel, select the application server where the

Authoring Server will be installed. In the lower window, select the VirtualHost. Click Next.

7. On the Authoring Server Repository Panel, select the type of repositorywhere you have, or will have, your Web content stored. If you plan on usingOracle or DB2, select Database. If you already have content stored in IBMContent Manager, select IBM Content Manager. Click Next.

8. If you chose Database on the previous panel, enter the information to create aconnection to the Oracle or DB2 database.v Database Type: Select the appropriate setting for your configuration and

database type.v Database Name: Choose an arbitrary name for your database (if using a

local DB2 database) or the name of an existing database (if using Oracle ora remote DB2 database). Do not use the database name the WebSphereApplication Server uses (typically, WAS).

v Database User ID: Enter a user ID with administrator privileges for thedatabase.

v Password: Enter the password for the user ID.

Confirm that the default values for the other fields on the panel are acceptableand click Next.

9. If you chose IBM Content Manager on the Authoring Server RepositoryPanel, enter the configuration information for your IBM Content Managerinstallation.v Server: Enter the name of the IBM Content Manager server (for example:

icmnlsdb)

Chapter 5. Installing WebSphere Portal content publishing 39

v User ID: Enter a user ID with administrative privilegesv Password: Enter and verify the password for the user ID.v Default Resource Manager Name: Enter the default resource manager name

(for example: rmdb)

Click Next.10. In the Authoring Server Workflow Selection panel, select either Lite

Workflow, Lotus Workflow, or None. Click Next.11. If you chose Lotus Workflow in the previous panel, type the fully qualified

name of the Lotus Domino server (for example, servername.domain). ClickNext.

12. In the Authoring Server Authentication Selection panel, choose the methodby which users of the WebSphere Portal content publishing authoringenvironment will be authenticated (when logging into the WebSphere Portalcontent publishing workspace). (Note: if you have chosen to use LotusWorkflow, then you will not see this panel and will use Lotus Domino forauthentication.) Click Next.

13. If you chose Local operating system on the Authoring Server AuthenticationSelection panel, type the name of a user for the current machine.

14. If you chose LDAP Server on the Authoring Server Authentication Selectionpanel, enter the configuration information for your IBM Directory Serverinstallation.v LDAP Server: Enter the fully qualified name of the LDAP server (for

example, servername.domain.com).v Base Distinguished Name (suffix): Enter the appropriate setting for your

LDAP configuration. Lotus Domino uses the form ou=,o=,c= (for example,ou=locale,o=company,c=us). Another possible LDAP form iscn=group,dc=company,dc=com.

Click Next.15. If you chose Lotus Domino on the Authoring Server Authentication

Selection panel, type the name of the Lotus Domino server. Click Next.16. On the Precompile JSP Selection panel, indicate whether you want the JSPs

associated with the WebSphere Portal content publishing workspaceprecompiled during the installation. Choosing Yes will cause the time requiredto complete the installation to be longer, but the pages within the WebSpherePortal content publishing workspace will load quicker when first accessed.Click Next.

17. Confirm the components to be installed and click Install.Note: If you selected the Authoring Server Sample, it does not appear as aseparate item in this list.

18. To complete the wizard, click Finish. You may be directed to reboot themachine.

Configuring the Authoring Server

Configuring DB2 databases on UNIX: If you are using DB2 on a UNIX system,create a loopback connection:1. Setup a loopback alias for your node with the following command:

DB2 CATALOG TCPIP NODE LOCAL_NODE REMOTE 127.0.0.1 SERVER 50000

where LOCAL_NODE can be any name you wish to use to refer to your localsystem.


If your server port is different than 50000, use the server port defined for yoursystem. To determine the value, find the DB2cDB2 variable in the filewinnt/system32/drivers/etc/services (Windows) or /etc/services (UNIX).

2. Catalog your database to use the loopback alias with the following command:DB2 CATALOG DATABASE MY_DATABASE AS MY_DB_ALIAS AT NODE LOCAL_NODE

where MY_DATABASE is the database you created and MY_DB_ALIAS is your alias toyour database. The database name and alias can be any name you wish youuse.

3. Verify that the connection works using the following command:DB2 CONNECT TO MY_DB_ALIAS

4. Change your WebSphere Portal content publishing datasources to use theloopback alias.a. Open a WebSphere Application Server Administrative Console and expand

Resources, then JDBC Drivers. You will see up to three of the followingJDBC drivers: WCM DB Driver, Pers DB Driver, and Feedback DB Driver.

b. For each of these drivers, expand it and click Datasources. On the rightpanel, change the database name to be the loopback alias and click Apply.Click Test Connection to verify your connection is working.

c. Stop and restart your server.

Editing the userInfo.properties file: If you are using the local operating systemfor authentication, edit the userInfo.properties file located in thewas_home\wcp\author\ directory:# Properties File for the user and role information##wcm.users = dave, greg, rob, tara, db2admin

## Role information for each user#wcm.users.role.dave = Content Contributorwcm.users.role.greg = Content Contributorwcm.users.role.rob = Project Lead, Domain Expertwcm.users.role.tara = Content Publisherwcm.users.role.db2admin = Project Lead

## E-Mail information for each user##wcm.users.email.rob = [email protected]

The existing users are for use with the Authoring Server sample. If you do notwant to use the sample, you can delete these users.

Add a new line for each system user who will be using the Authoring Server. Eachuser must also be added to the list of wcm.users at the top of the file. Refer to theWebSphere Portal content publishing help system for more information about theauthorities and responsibilities of the different roles. You can edit this file at anytime as necessary to add, change or delete users. Save and close the file whenfinished.

Editing the WCM.properties file if using a different port: If the webserver isrunning on a different <hostname>:<port> than localhost:80, add the followinglines to the WCM.properties file:


wcm.webserver.host=<hostname>wcm.webserver.port=<port>

For example,wcm.webserver.host=locale.ibm.comwcm.webserver.port=8080

Adjusting the Java Heap Size in JVM settings: To adjust the JVM settings:1. Open the WebSphere Application Server Administrative Console.2. Click Nodes > node_name > Application Servers > server_name.3. Click the JVM Settings tab.4. Enter new values for Adjust the Initial Java Heap Size and the Maximum Java

Heap Size.The values to use depend on the amount of memory your computer has, aswell as other processes running on your system. Suggested starting values are128 MB for the Java Heap Size and 256 MB for the Maximum Java Heap Size.Adjust as necessary.

Configuring datasource connections for the authoring environment: Considerthe number of users who will be simultaneously logged into the authoringenvironment. By default, the maximum number of simultaneous connections to thedatasource is set to 25. You should multiply the number of simultaneous users youwill need to have by 3. If that number is greater than 25, you should change thisvalue. To change the maximum number of simultaneous users:1. In the WebSphere Application Server Administrative Console, expand

WebSphere Administrative Domain.2. Expand Resources and JDBC Drivers.3. Expand WCM DB Driver and click Data Sources.4. Click the Connection Pooling tab.5. In the Maximum pool size field, type the value you want to use.6. Click Apply and restart WebSphere Application Server.

Enabling Security on WebSphere Application Server when using local operatingsystem or LDAP authentication: To enable security in WebSphere ApplicationServer:1. In the WebSphere Application Server Administrative Console, open the Security

Center.2. Click the General tab and check Enable security.3. Click the Authentication tab and check the appropriate authentication method.

v For local operating system security, enter the user ID and password of a userwith administrative authority.

v For LDAP, enter the following information:– Security Server ID: Enter a user ID with administrative privileges. For

example: uid=wpsadmin,cn=users,dc=ibm,dc=com.– Security Server Password: Type the password for the user ID.– Directory Type: Select the appropriate setting for your LDAP server. If

using IBM Directory Server, choose SecureWay.– Host: Enter your fully qualified host name. For example:

hostname.locale.domain.– Base Distinguished Name: Enter your base distinguished name. For

example: dc=ibm,dc=com.


4. Click OK. If this is the first time you have enabled security in WebSphereApplication Server, you will be prompted for the target LTPA password.

5. Stop and restart the application server. Provide the user ID and password whenprompted.

Verifying your installationTo verify your installation:1. Check for activity in the WebSphere Application Server error logs

(was_home\logs\Default_Server_stderr.log andwas_home\logs\Default_Server_stdout.log) or the WebSphere Portal contentpublishing wcpinstall.log file:v AIX, Linux, or Solaris: /tmp/wcpinstall.logv Windows: %temp%\wcpinstall.log (where %temp% is defined as your temp

environment variable)2. In WAS Administrative Console, make sure the enterprise applications exist:

v Personalization Emailv Personalization Runtimev WCMv WCPDemo_Author (if the Authoring Server Sample was installed)

3. Make sure the Datasource connections exist:v Pers DB Driverv Feedback DB Driver

To start WebSphere Portal content publishing:v Go to http://<fullyqualifiedhostname>/wps/wcp/index.jsp in your Web

browser, where <fullyqualifiedhostname> includes the host name and domainname of the server where you installed the WebSphere Portal content publishingauthoring server.

v Click Start Web Content Publisher. A new window is displayed.v Type your User ID and Password.v Click Login.

Installing WebSphere Portal content publishing — DesktopIntegration

Uninstalling WebSphere Portal content publishing — DesktopIntegrationBefore installing, uninstall any existing copies of WebSphere Portal contentpublishing — Desktop Integration (if applicable):1. Close any open windows for WebSphere Portal content publishing — Desktop

Integration.2. Click Start > Settings > Control Panel > Add/Remove Programs.3. Select IBM WebSphere Portal content publishing — Desktop Integration.4. Click Change/Remove.5. Follow the instructions to remove the wizards.

Alternately, you can run dskint_uninstall.exe from the \ProgramFiles\IBM\wcp\DesktopIntegration\uninst directory (default location).


Installing WebSphere Portal content publishing — DesktopIntegrationTo install WebSphere Portal content publishing — Desktop Integration:1. Load WebSphere Portal installation CD 5 containing WebSphere Portal content

publishing. If the Setup Manager starts, close it.2. Using a file browser or command prompt, change to the dskint folder on the

CD and run dskint_installwin.exe. The InstallShield Wizard will start.3. Click Next.4. Type (or browse to) the location you want to install Desktop Integration and

click Next.5. Confirm the information and click Next.6. When the installation is complete, click Finish.

Verifying the installationTo verify your installation:1. Using your file browser or command prompt, change to the directory that you

indicated during the installation.2. Verify that the following directories exist (default location):

v \Program Files\IBM\wcp\DesktopIntegration

v \Program Files\IBM\wcp\DesktopIntegration\uninst

3. On your Windows desktop, open My Computer and verify that the WPCP iconexists.

Configuring WebSphere Portal content publishing DesktopIntegrationYou must install the WebSphere Portal content publishing Authoring Server andconfigure a project before proceeding.

Refer to the instructions on connecting to an authoring server within theWebSphere Portal content publishing help system’s Desktop Integration Guide.

Installing the runtime environmentDuring the WebSphere Portal content publishing installation process, or after youhave started WebSphere Portal content publishing, if you encounter errors, see thesection on troubleshooting in the README file.

Notes:

1. It is recommended that you install the WebSphere Portal content publishingauthoring environment on a different machine than the runtime environment.

2. If you plan to install LikeMinds:v For Microsoft SQL Server, Oracle, or IBM DB2 systems (but not other

ODBC-compliant databases), you can install it onto a system that has adatabase created, but no tablespaces or tables.

v If you are installing LikeMinds using Microsoft SQL Server or Oracle, makesure you have started the LikeMinds database.

Note: Close the WebSphere Application Server Administrative Console before youuninstall or install WebSphere Portal content publishing.

Installing a Production ServerTo install a WebSphere Portal content publishing Production Server:


1. Load the CD that contains WebSphere Portal content publishing (WebSpherePortal installation CD 5). If the Setup Manager starts, close it.

2. Run the file wpcp\wcpinstallwin.exe for Windows platforms (or unixinst.shfor AIX, Solaris or Linux).v On Windows, the InstallShield wizard will launch.v On AIX, Solaris, or Linux, you will be prompted for the WebSphere

Application Server root directory and (if using DB2) the home directory ofyour DB2 instance owner; the InstallShield wizard will then launch.

3. Click Next.4. Check Production Server.

v To enable recommendation-based personalization of your Web site, checkLikeMinds Recommendation Engine.

v To enable rules-based personalization of your Web site, checkPersonalization.

5. Click Next. If WAS security is enabled, you will be prompted for a user IDand password.

6. Check Runtime Server. (Optionally, check Edge Publish if you are installingto WebSphere Edge Server; you must also check Runtime Server). Click Next.

7. In the first window of the panel, select the application server where theRuntime Server will be installed. In the lower window, select the Virtual Host.Click Next.

8. (LikeMinds only) Select the features that you want to install on theLikeMinds Production Server Selection panel.v LikeMinds Recommendation Server: Installs the server that calculates and

delivers recommendations.v LikeMinds Recommendation Server Utilities: Installs the LikeMinds utilities

(sifter, accumulator, buildstats, buildvisit, and others). You must select thisoption if you select LikeMinds Recommendation Server.

v LikeMinds Admin Center: Installs the Admin Center; may be installed on aseparate machine from the Recommendation Server that has WebSphereApplication Server installed.

v LikeMinds Sample Applications: Installs a sample Web site (Movie Site);may be installed on a separate machine from the Recommendation Server.

v LikeMinds Software Development Kit (SDK): Installs the LikeMinds SDK.

Click Next.9. (LikeMinds only) Enter the following configuration information on the

LikeMinds Production Server Configuration panel:v Installation location:v LikeMinds Recommendation Server Hostname:v LikeMinds Recommendation Server Port:v LikeMinds LPS Service/Daemon Name:

10. (LikeMinds only) Select the application server and virtual host on theproduction server where LikeMinds will be installed.

11. (LikeMinds only) Enter the information to create a connection to thePersonalization database on the LikeMinds Production Server DatabaseConfiguration panel.v Database Type: Select the appropriate setting for your configuration and

database type.


v Database Name: Choose an arbitrary name for your database or enter thename of the existing LikeMinds database. Do not use the database name theWebSphere Application Server uses (typically, WAS).




12. If you chose Local operating system on the Authoring Server AuthenticationSelection panel, type the name of a user with administrator privileges for thecurrent machine.

13. (Personalization only) Enter the information to create a connection to thePersonalization database on the Personalization Production Server DatabaseConfiguration panel.v Database Type: Select the appropriate setting for your configuration and





Note: If installing to an Informix database, you must complete the URL in thejdbcURL field on the database panels by typing the value of the InformixServer Name.Confirm that the default values for the other fields on the panelare acceptable and click Next.

14. On the Feedback Production Server Database Configuration panel, enter theinformation to create a connection to the Oracle or DB2 database that will beused to store site statistical data for feedback and reporting.v Database Type: Select the appropriate setting for your configuration and






15. Confirm the components to be installed and click Install.16. To complete the wizard, click Finish. You may be directed to reboot the

machine.

Adjusting JVM settingsTo adjust the JVM settings:1. Open the WebSphere Application Server Administrative Console.2. Click Nodes > node_name > Application Servers > server_name.3. Click the JVM Settings tab.


4. Enter new values for Adjust the Initial Java Heap Size and the Maximum JavaHeap Size.The values to use depend on the amount of memory your computer has, aswell as other processes running on your system. Suggested starting values are128 MB for the Java Heap Size and 256 MB for the Maximum Java Heap Size.Adjust as necessary.

Configuring DB2 on UNIXIf you are using DB2 on a UNIX system, perform the same steps to configure aloop back connection as for the Authoring Server. Refer to the instructions in“Configuring DB2 databases on UNIX” on page 40.

Verifying your installationTo verify your installation:1. Check for activity in the WebSphere Application Server error logs

(was_home\logs\Default_Server_stderr.log andwas_home\logs\Default_Server_stdout.log) or the WebSphere Portal contentpublishing wcpinstall.log file:v AIX, Linux, or Solaris: /tmp/wcpinstall.logv Windows: %temp%\wcpinstall.log (where %temp% is defined as your temp

environment variable)2. In WAS Administrative Console, make sure the enterprise applications exist:

v Personalization Emailv Personalization Runtimev LMAdminCenter (if you installed LikeMinds)v MovieSite (if you installed the LikeMinds sample)

3. Make sure the Datasource connections exist:v Pers DB Driverv Feedback DB Driver

4. Open a browser and in the Location field typehttp://<fullyqualifiedhostname>/wps/PersAdmin/adminframe.jsp

5. If WebSphere security is enabled, login with a valid user ID and password.(The first time you start the Resource Console, the UI may load slowly whileJSPs are compiled, if the JSPs were not precompiled during installation.)

6. Verify there are no errors when you log in. If you receive any errors, check thewas_home\logs\Default_Server_stdout.log.

7. If you installed the Production Server on a machine with IBM Content Managerinstalled, verify that the JVM settings were adjusted:a. Open the WebSphere Application Server Administrative Console.b. Click Nodes > node_name > Application Servers > server_name.c. Click the JVM Settings tab.d. Under System Properties, select ws.ext.dirs. In the Value column, you

should see the following in the list:v Windows: C:\Program Files\IBM\cmgmt;C:\cmbroot\lib

v Solaris: :/opt/IBMcmb/lib:/opt/IBMcmb/cmgmtv AIX: :/usr/lpp/cmb/lib:/usr/lpp/cmb/cmgmt

Verifying your LikeMinds Recommendation Engine installationThis chapter covers the following topics:v Verifying the LikeMinds Admin Center is functioning


v Running the test scriptv Starting and stopping LikeMinds Recommendation Enginev Verifying that Movie Site is functioning

Verifying the LikeMinds Admin Center: To verify the LikeMinds Admin Centeris working:1. Start the WebSphere Application Server Console.2. In a browser, open the LikeMinds Admin Center, for example:

http://<fullyqualifiedhostname>/LMAdminCenter.3. Log into the LikeMinds Admin Center. The default login is admin and the

default password is admin.

Running the test script: The LikeMinds distribution includes a test script whichverifies that LikeMinds Recommendation Engine is properly installed. You mustpopulate your database with seed data before running the test script.

To run the test script, navigate to the lrs\util subdirectory of the LikeMindsRecommendation Engine installation directory and execute test.cmd.

Starting and stopping LikeMinds Personalization Server: The installer installsLikeMinds as a Microsoft Windows NT service and configures it to startautomatically when the system boots.

Manually starting and stopping LikeMinds Personalization Server: To start theLikeMinds Personalization Server:1. Make sure your RDBMS is running.2. Open the control panel and double-click Services.3. Select LikeMinds Personalization Server (LPS Service Name).4. Click Start.

To stop the LikeMinds Personalization Server:1. Open the control panel and double-click Services.2. Select LikeMinds Personalization Server (LPS Service Name).3. Click Stop.4. Stop the sifter: in the <LM_install_dir>\lrs\util directory, run the

stopsifter script.

Note: The sifter may continue to run for a few seconds after you runstopsifter.

Automatically starting LikeMinds Personalization Server: To configure LikeMinds tostart automatically when the system starts:1. Make sure your RDBMS is running.2. Open the control panel and double-click Services.3. Select LikeMinds Personalization Server (LPS Service Name) and select

Properties.4. From the Startup type list, select Automatic.

Starting LikeMinds Personalization Server on the Same Machine as Microsoft SQLServer: If your RDBMS is Microsoft SQL Server, and it is located on a separatemachine from the LikeMinds Personalization Server, you must start it each timeyou plan to use LikeMinds. If Microsoft SQL Server is on the same machine as


LikeMinds Personalization Server, you can configure LikeMinds PersonalizationServer to start automatically whenever Microsoft SQL Server is started. To do so,you need to run the svcdepend.reg script, which updates your registry.

To run the svcdepend.reg script:1. Go to the <LM_install_dir>\lrs\server directory.2. Double-click the svcdepend.reg script.3. In the confirmation dialog box, click OK.

Verifying Movie Site is functioning: After you have started the sifter, verifythat the Movie Site Web interface is working:1. In a browser, open Movie Site, for example:

http://<fullyqualifiedhostname>/MovieSite. The Movie Site signon.jsp pageis displayed with a form for a user name and password, and a link to become amember.

2. Click on the Become a member link and attempt to add a new user, or attemptto log in.For IBM DB2 and Oracle, the default login is likeminds, with the passwordlikeminds. For Microsoft SQL Server, the login and password can be for anydatabase user has access. For other ODBC databases, it depends on the RDBMSlogin/password as the user likeminds with the password likeminds.

Configuring the runtime environment

Configuring LikeMinds Recommendation EngineUnless you specified that some components should be installed elsewhere, theLikeMinds Recommendation Engine installation directory and its subdirectoriescontain all the LikeMinds Recommendation Engine files, except for the someMovie Site and LikeMinds Admin Center files.

The conf subdirectory: This subdirectory of the LikeMinds installation directorycontains all configuration files used by LikeMinds. You can change the behavior ofLikeMinds by modifying the parameters in these files. The exact files in yourinstallation may be different from those shown if you have multiple handlers oryou have chosen to give some files different names.

File Description

all.conf Records the installation settings as you run the installer. Do notchange this file; it is for installation record-keeping purposes only.

lps.conf Basic configuration settings for the LikeMinds RecommendationEngine. It contains information such as the LikeMinds homedirectory, log file name, name of the LikeMinds server, portnumber, names of handlers, and the name of the Lps_Cfgconfiguration table.

The logs subdirectory: This directory contains log files created by LikeMinds andMovie Site. It may be empty if you have not yet started the LikeMindsPersonalization Server.

The LikeMinds Personalization Server directory: Unless you specified otherwise,this directory is the lrs subdirectory of the LPS installation directory.

This directory tree contains the LikeMinds server and utility executable files andscripts used with them.


lrs\bin: This directory contains various LikeMinds Personalization Server utilities:

Table 2. lrs\bin directory

File or directory Description

db directory Executable files for running the LikeMinds databases.

engine directory Executable files for running the LikeMinds engines

filters directory Directory that contains the sample filters for rating andtransaction sets.

buildstats Utility that updates database statistics.

dsncreate.exe Creates ODBC DataSource Name for IBM DB2 or Microsoft SQLServer.

lpsConfig Utility that allows you to add or modify configurationparameters.

pplsrvadmin Command-line administration tool that lets you check the statusof the LikeMinds Recommendation Engine and perform basicadministration tasks.

prefetchMentors For internal use only.

psadmin Utility that compiles the visit list for buildvisit.

sifter.exe Utility to launch the sifter.

testInstall Utility to test the LikeMinds Personalization Server installation.

trxBlkLoad Bulk loader utility for ratings and transactions.

lmpplserver.exe Executable for running LikeMinds Recommendation Engine.

lrs\server: This directory contains scripts that start and stop the server and invokeserver administration tools:

Table 3. lrs\server directory

Script Description

admin.cmd Command-line server administration tool.

prefetch.cmd Script that loads mentors into the cache when a new handler isinitialized.

reinitserver.cmd Script to reinitialize all handlers.

startserver.cmd Script to start the LikeMinds Personalization Server.

status.cmd Script which displays LikeMinds Personalization Server status.

stopserver.cmd Script to stop the LikeMinds Personalization Server.

lrs\util: This directory contains scripts to invoke the LikeMinds utilities:

Table 4. lrs\util directory

Script Description

buildstats.cmd Script that starts the buildstats utility.

buildvisit.cmd Script that starts the buildvisit utility.

lpsIAA.cmd Script that starts the lpsIAA (accumulator) utility.

daily.cmd Script that runs the buildstats utility, then runs buildvisit oncebuildstats has finished.

lpsconfig.cmd Script that invokes the lpsconfig utility, which allows you tochange LikeMinds Personalization Server configuration settings.


Table 4. lrs\util directory (continued)

Script Description

sifter.cmd Script that starts the sifter.com script.

startsifter.cmd Script that starts the sifter.

stopsifter.cmd Script that stops the sifter.

test.cmd Installation test script.

The Software Developer’s Kit (SDK) directory: Unless you specified otherwise, theSoftware Developer’s Kit is in the sdk subdirectory of the LikeMinds installationdirectory.

sdk\java: This directory tree contains the LikeMinds Software Developer’s Kit forJava.

Table 5. sdk\java directory

Directory Description

apiTest.dsp , Makefile.msw Files used to test the Java APIs.

com Contains the andromedia directory, which stores wrapper files.

LMRecommender.jar Contains Java code.

sdk\java\com\andromedia\lmrpc: Classes for the internal use of LikeMinds.

LMAdminServlet.jar and lmhost.properties

sdk\java\com\andromedia\recommender: This directory contains the classes of theJava API and the LikeMinds beans.

sdk\java\com\andromedia\recommender\test: This directory contains code that teststhe Java APIs. The apiTest.java exercises all methods in the API. You can use thisprogram as an example of programming for the Java API.

LikeMinds Admin Center and Movie Site: The directories for the LikeMinds Admincenter and Movie Site are:v /WebSphere/AppServer/installableApps/lmadmin.ear

v /WebSphere/AppServer/installableApps/moviesite.ear

Configuring LikeMinds Admin Center to administer multiple LikeMinds servers: It ispossible to configure a single installation of the LikeMinds Admin Center toadminister multiple LikeMinds Recommendation servers. Therefore, it is notnecessary to install a separate copy of the Admin Center for every LikeMindsRecommendation server.

To configure the Admin Center, use a text editor to open the filelmhosts.properties located inwas_home\installedApps\LMAdminCenter\lmservlet.war. For each additional hostthat you want to administer, add a new line in the formathost<#>:<domain>,<port>

where <#> is a unique integer, <domain> is the domain or IP number of theLikeMinds Recommendation Server, and <port> is the port number used tocommunication with the LikeMinds Recommendation Server. For example:


host1:sunsrv07,2620host2:sunsrv03,2620

Cloning the runtime environmentYou can clone the runtime environment to application servers in a server group.However, neither the Authoring Server nor the Production LikeMinds Server canbe cloned.

Before attempting to clone servers, note that:v All nodes in the WAS domain must share the same runtime database.v If you are using Oracle, PZNADMIN and EJB user IDs must be set up prior to

install (refer to “Configuring an Oracle database” on page 16).

The following steps demonstrate how to create a clone of the Production RuntimeServer. The scenario assumes a WebSphere Application Server domain with 2nodes, A and B. For a domain with more than 2 machines, set up the additionalmachines similarly to B.1. Complete the installation of Runtime Server on Node A.2. Copy was_home/installedApps/Personalization_Email.ear and

was_home/installedApps/Personalization_Runtime.ear to the same locationson Node B

3. Move was_home/temp/<node_B_name>/<clone_name>/Personalization_Runtime toNode B.(If was_home/temp/<node_B_name> does not exist, copywas_home/temp/<node_A_name>/<app_server_name> to Node B and rename the<node_A_name> directory to the name of Node B, and rename the<app_server_name> directory to the name of the clone on Node B.)

4. Copy was_home/wcp directory to node B.5. Copy was_home/lib/brbClient.jar and brbServer.jar to Node B.6. Edit was_home/properties/com/ibm/websphere/product.xml on Node B and add

the lines between <extensions> and </extensions>:<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE websphere SYSTEM "product.dtd">

<websphere><appserver><name>IBM WebSphere Application Server</name><edition><value>AE</value><name>Advanced Edition for Multiplatforms</name></edition><version>4.0.4</version><build><number>ptf40230.02</number><date>08/01/2002</date></build><extensions><extensionname="Personalization Server"><version>4.0.1</version><BuildDate>04/26/2002</BuildDate></extension><extensionname="Rules Runtime"><ext><name>Rules Runtime</name><build>


<number>ptf20202.06</number><date>1-30-2002</date></build></ext></extension><extension name="Personalization Common"><BuildDate>04/26/2002</BuildDate></extension></extensions></history></appserver></websphere>

To configure the clone:1. Install the JDBC drivers for Pers DB Driver and Feedback DB Driver on Node

B:a. On Node A, open the WAS Admin Consoleb. Expand Resources > JDBC Drivers.c. Highlight Pers DB Driver and in the right panel, select the Nodes tab.d. Select Install New.e. Highlight Node 2 and select Specify Driver.f. Select Add Driver.g. Locate the database driver file (db2java.zip for DB2, or classes12.zip for

Oracle) on Node B.h. Select Set.i. Select Install.j. Click Apply.k. Repeat these steps for Feedback DB Driver.

2. In the WAS Admin Console, regenerate the webserver plugin for both nodes.3. Stop and restart the server group.

Tips for using Production runtime in a cloned environment

Importing resource collections: Importing a .hrf file requires that you provide thelocation of the .hrf file on the import panel. However, in a cloned environment,only the clone running on the system with the .hrf file can find the .hrf file to dothe import. To avoid this problem, you can do one of the following:v Perform the import using the internal WAS port on the system containing the

.hrf file. That is, usehttp://<server_name>:<port>/wps/PersAdmin/adminframe.jsp

(where <server_name> is the system and <port> is the internal server port*.)v Place the .hrf file on each cloned machine, in the same directory as the original

(Node A).

*To find the port number for your application server:1. Open the WebSphere Application Server Administrative Console.2. Click Nodes > node_name > Application Servers > server_name.3. Click the Services tab.4. Click Web Container Service.5. Click Edit Properties.6. In the Web Container Service panel, click the Transport tab. The port number

is displayed for the host.


Installing the documentation (custom location)The suite of documentation for WebSphere Portal content publishing consists of:v README file (located in the installation root)v Installation Guide (located in the installation root)v Help system (a Web site containing all of the help, installation and migration

instructions, and Javadoc for WebSphere Portal content publishing)

The Help System is automatically installed with the WebSphere Portal contentpublishing Authoring Server as part of the WCM enterprise application (wcm.ear),and is accessible by hyperlinks in the WebSphere Portal content publishingworkspace UI. However, it is possible to install the Help System to a separatelocation (for example, for offline access).

Installing the documentation (custom location)To install the WebSphere Portal content publishing help system to a customlocation :1. Load the CD that contains WebSphere Portal content publishing (WebSphere

Portal Server CD 5). If the Setup Manager starts, close it.2. Run the file wpcp\wcpinstallwin.exe for Windows platforms (or execute java

-cp wcpinstall.jar run for AIX, Solaris or Linux). The InstallShield wizardwill launch.

3. Click Next.4. Check Documentation (custom location) and click Next.5. Type (or browse to) the location you want to install the documentation. Click

Next.6. Click Install.7. When installation is complete, click Finish.

Verifying the installation and accessing the documentationTo verify your installation:1. In the location you specified during the installation, verify that the following

directories exist:v wcp\helpsystem\<language code>

v wcp\helpsystem\<language code>\images

v wcp\helpsystem\<language code>\search

2. Open a browser.v If you installed to an HTTP server, type the following in the Location field:

http://<host_name>/wps/wcp/helpsystem/<language_code>/index.html (ordocFrameset.html)

v If you did not install to an HTTP server, click File > Open and browse thefollowing file, relative to the location you indicated during the installation:<install_dir>\wcp\helpsystem\<language_code>\index.html (ordocFrameset.html)

Note: <language_code> is the two- or four-letter code for your country or region:

Code Code

de German ja Japanese

en English ko Korean


es Spanish pt_BR Brazilian Portuguese

fr French zh Simplified Chinese

it Italian zh_TW Traditional Chinese

Troubleshooting

Text truncation in install panels on AIX and LinuxOn AIX and Linux, text on some install panels may be truncated. Resizing thewindow may help to show the complete text. To prevent the problem, beforerunning install, set the JAVA2D_USEAWTFONTS environment variable to 0, usingthe following command:export JAVA2D_USEAWTFONTS=0


Chapter 6. Accessing the Sample

Before you can work with the samples you need must install WebSphere Portalcontent publishing and the WPCP Authoring Server Sample. You must then startWebSphere Portal content publishing.

Starting WebSphere Portal content publishingTo run WebSphere Portal content publishing, you need to:1. If using Lotus Workflow, start Lotus Domino Server.

v If you installed Lotus Domino Server on Microsoft Windows 2000, you canstart Lotus Domino Server from the Start menu.

v If you installed Lotus Domino Server on one of the UNIX platforms, you canstart Lotus Domino Server using the command /opt/lotus/bin/server. Note:You must run this command as the user you specified when you installedLotus Domino Server.

2. Start WebSphere Application Server.v If you installed WebSphere Application Server on Microsoft Windows 2000,

you can start WebSphere Application Server from the Start menu.v If you installed WebSphere Application Server on one of the UNIX platforms,

you can start WebSphere Application Server using the command by changingdirectories to <was_home>/bin and running the following command run./startupServer.sh &.

3. Start the appropriate application server.Depending on your settings, the appropriate application server may or may notbe started when you start WebSphere Application Server. If it has not beenstarted, you will not be able to start WebSphere Portal content publishing. Toensure that it is started, open the WebSphere Application Server AdministrativeConsole, expand Nodes and Application Servers. If you did a typical install, theapplication server that must be running will be called WebSphere Portal.

4.

To start WebSphere Portal content publishing:v Go to http://<fullyqualifiedhostname>/wps/wcp/index.jsp in your Web

browser, where <fullyqualifiedhostname> includes the host name anddomain name of the server where you installed the WebSphere Portal contentpublishing authoring server.

v Click Start Web Content Publisher. A new window is displayed.v Type your User ID and Password.v Click Login.

Four named users (dave, greg, rob and tara) are defined to WebSphere Portalcontent publishing. Their user IDs and passwords are the same as their names. Inaddition, an administrative user ID (either WCPAdmin, password: password, orthe system administrator’s user ID and password if using local operating systemsecurity) has been defined for you. Functions available to users vary based on theirassigned roles. WCPAdmin enables you to look at and experiment with all productfunctions.


Note: If you experience errors (for example, JSP errors or connection problems)running the samples, you should restart your machine and make sure theWebSphere Application Server Admin Server is running.

When you start working with WebSphere Portal content publishing, you will needto set access control for different users. See the online help for creating users andchanging users’ access.

For more information on working with the sample and publishing it to a runtimeenvironment, refer to the Getting Started tutorial in the WebSphere Portal contentpublishing help system (see “Getting Started Tutorial (for use with the AuthoringServer Sample)”).

Getting Started Tutorial (for use with the Authoring Server Sample)The section on Getting Started in theWebSphere Portal content publishing helpsystem will introduce you to some of the features of WebSphere Portal contentpublishing. The Tutorial section of Getting Started provides you with step-by-stepinstructions for developing a Web content management solution based on thesample installed with WebSphere Portal content publishing.

To start the help system, launch WebSphere Portal content publishing(http://<fullyqualifiedhostname>/wps/wcp/index.jsp) and click Help System.You can also access the help system from within the workspace by clicking Help inthe lower left corner of the main window. A link to the Getting Started Tutorial isdisplayed in the left frame.

If you want to work through the section on creating resources using the wizardsfor WebSphere Studio, you will need to install WebSphere Studio ApplicationDeveloper from the CD provided with WebSphere Portal content publishing andinstall the WebSphere Portal content publishing wizards into the WebSphere StudioApplication Developer plugins directory.


Chapter 7. Troubleshooting

Problem: Database connection error message: Invalid Database object

Correction: Confirm that the Data Source Name (DSN), database user name, anddatabase password settings in lps.conf are the correct settings for your database.Check that this information has been properly configured using the ODBC controlpanel applet.

Problem: Database connection error message: tmpdb full:

Correction: If you use Microsoft SQL Server, verify that the driver associated withthe DSN is configured to drop procedures ″when you disconnect and asappropriate while you are connected″.

Problem: Uninstallation was not successful, some files remain.

Correction: Follow the instructions for Chapter 8, “Manually uninstallingWebSphere Portal content publishing” on page 63.

Problem: Cannot install WebSphere Portal content publishing after uninstalling.

Correction: If WebSphere Portal content publishing’s install.properties fileremains after uninstallation, or the vpd.properties file is not properly updated bythe uninstaller, it may not be possible to reinstall WebSphere Portal contentpublishing. Follow the instructions for Chapter 8, “Manually uninstallingWebSphere Portal content publishing” on page 63.

Problem: Database tables were not created for the Authoring Server or ProductionServer during installation.

Correction: You can manually create the database tables for WebSphere Portalcontent publishing by running DDL scripts contained on WebSphere Portalinstallation CD 5. The DDLs must be run in the order shown. Run only the DDLfrom each list needed for your database. For instructions on how to run DDLs,consult the operating manual for your database.1. For a Production Server or Authoring Server, run the appropriate DDL from the

list below. They are located in the wcp\runtime\config\database directory andare installed in the was_home\wcp\runtime\config\database directory. TheseDDLs create the tables necessary for configuring the rules engine and resourceengine and must be run first.v TableDB271.ddl

v TableOracle.ddl

v TableInformix.ddl

v TableSybase.ddl

v TableMSSQL.ddl

2. The following DDLs are required for the Authoring Server and must be runafter those in step 1. The wcmTable* DDLs create the Authoring Serverconfiguration tables and must be run before the wcmData* DDLs. ThewcmData* DDLs configure the default project and its associated data (users,


roles, authorities, etc.). These DDLs are located in thewpcp\wcp\author\config\database directory and are installed in thewas_home\wcp\author\bin directory.In order to login to WebSphere Portal content publishing and administer theenvironment, create an LDAP user or a local operating system user (dependingon your authentication method) that has the same name as the ’InitialAdministrator’ in the CMUSER table.v wcmTableDB2.ddl

v wcmTableOracle.ddl

v wcmDataDB2.ddl

v wcmDataOracle.ddl

3. If you installed the Authoring Server Sample, the following DDLs are requiredand must be run after those in step 2. The wcmdemoTable* DDLs create thetables that configure the sample at authoring time and must be run before thewcmdemoData* DDLs. The wcmdemoData* DDLs configure theWCPDemo_Author project and its associated data (users, roles, authorities, andso on). These DDLs are installed in the was_home\wcp\author\bin directory.v wcmdemoTableDB2.ddl

v wcmdemoTableOracle.ddl

v wcmdemoDataDB2.ddl

v wcmdemoDataOracle.ddl

4. For the Production Server, create the Feedback database tables using thecreateFeedbackTables.bat file (Windows) or createFeedbackTables.sh (UNIX).Before running the file, edit it and modify the environment variables (such asJAVA_HOME, where Java can be found) and the database URL, user ID, andpassword for both the target database.

5. For the Production Server, if you installed LikeMinds, first create the databaseand tablespaces. For a DB2 database the tablespace needs to be namedlmtablespace; for an Oracle database two tablespaces must be created, namedlmdata and lmindex. Create the LikeMinds database tables using thecreateLikeMindsTables.bat file (for Windows) or createLikeMindsTables.sh(UNIX). Before running the file, edit it and modify the environment variablesand the database URL, user ID, and password for both the target database.After running the scripts, you must also run the lpsconfig program asdescribed in the next troubleshooting section.

Problem: The installer fails to load your configuration settings to the LikeMindsdatabase.

Correction:v Fix the problem that inhibited the loading process.

This may be due to an incorrectly set environment variable, the database servernot running, or a connection problem.

v Run a short test to verify that you can run the load program successfully:<LM_install_dir>\lrs\util\lpsconfig -verify

v If the output from the test is successful, run the load program again with thecorrect input file:<LM_install_dir>\lrs\util\lpsconfig -load ..\..\conf\all.conf


Problem: When installing LikeMinds on Windows NT, there is a problem creatingthe ODBC connection to the database in order to load the configuration tableduring installation. You will receive an error when starting LikeMinds Server fromWindows’ Services panel.

Correction:1. After installation, go to the directory <LM_install_dir>/lrs/bin and run the

program dsncreate:dsncreate <database name> <database type (sql/db2)><Action (create/remote)> <hostname>

(Type only dnscreate to see more documentation about these parameters)2. Go to the ODBC Datasource in your Control Panel and check that you have a

connection to the DB.3. Load the configuration table for LikeMinds manually running the following

command in the <LM_install_dir>/lrs/util directory:lpsconfig -conf ..\..\conf\lps.conf -load ..\..\conf\all.conf

4. Restart the LikeMinds Service.

Problem: Error running the LikeMinds daily.cmd script in Windows:

Correction: The script is trying to write logs to a missing directory. Create a logsdirectory in the LikeMinds installation directory (<LM_install_dir>\logs), or editthe lrs\utils\daily.cmd script and change the directory where the log files shouldbe created.

Problem: While running WebSphere Portal content publishing on a UNIX systemwith DB2, the following error occurs:CONM6009E: Failed to get connection to the database from datasource

(Serious Event Reader).CONM7007I: Mapping the following SQLException, with ErrorCode -1,224 and

SQLState 08001, to a StaleConnectionException:COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver]SQL1224N A database agent could not be started to service arequest, or was terminated as a result of a database systemshutdown or a force command. SQLSTATE=55032

Correction: Change your DB2 access to use a TCP/IP loopback alias.1. Create and configure the DB2 database as shown in “Configuring a DB2

database” on page 20.2. Setup a loopback alias for your node with the following command:

DB2 CATALOG TCPIP NODE LOCAL_NODE REMOTE 127.0.0.1 SERVER 50000

where LOCAL_NODE can be any name you wish to use to refer to your localsystem.

If your server port is different than 50000, use the server port defined for yoursystem. To determine the value, find the DB2cDB2 variable in the filewinnt/system32/drivers/etc/services (Windows) or /etc/services (UNIX).

3. Catalog your database to use the loopback alias with the following command:DB2 CATALOG DATABASE MY_DATABASE AS MY_DB_ALIAS AT NODE LOCAL_NODE

where MY_DATABASE is the database you created and MY_DB_ALIAS is your alias toyour database. The database name and alias can be any name you wish youuse.

Chapter 7. Troubleshooting 61

4. Verify that the connection works using the following command:DB2 CONNECT TO MY_DB_ALIAS

5. Change your WebSphere Portal content publishing datasources to use theloopback alias.a. Open a WebSphere Application Server Administrative Console and expand

Resources, then JDBC Drivers. You will see up to three of the followingJDBC drivers: WCM DB Driver, Pers DB Driver, and Feedback DB Driver.

b. For each of these drivers, expand it and click Datasources. On the rightpanel, change the database name to be the loopback alias and click Apply.Click Test Connection to verify your connection is working.

c. Stop and restart your server.

Note to AIX users: an alternative to using the DB2 loopback alias for AIX is to setthe DB2 environment variable EXTSHM=ON with the commands:EXTSHM=ONexport EXTSHMdb2set DB2ENVLIST=EXTSHM

Then stop and restart DB2.

For more information on TCP/IP loopback, search the DB2 Knowledge Base atwww.ibm.com.


Chapter 8. Manually uninstalling WebSphere Portal contentpublishing

To uninstall WebSphere Portal content publishing manually:1. Remove the enterprise applications from WebSphere Application Server (WAS)

a. Start the WAS Admin Serverb. Launch the WAS Administrative Consolec. Navigate to Enterprise Applications. Stop and remove any of the following

applications that are present.v Personalization Runtimev Personalization Emailv WCM Edge Publishv LMAdminCenterv MovieSitev WCMv WCPDemo Author

d. In the Resources section, open JDBC Providers and look for the items listedbelow. For each one that exists, expand it, highlight Data Sources, andremove the data source; then, remove the JDBC Provider name.v Pers DB Driverv Feedback DB Driverv WCM DB Driver

e. In the Resources section, open JavaMail Sessions. If pznMail is listed,remove it.

f. In the Nodes section, open the subsection for the node on which youinstalled WebSphere Portal content publishing and click on ApplicationServers. Click on the JVM Settings tab. In the System Properties area,remove any of the following that are present. When finished, click Apply.v pzn.ispreviewserverv wcm.root.dirv pzn.root.dir

Edit ws.ext.dirs and delete any entries associated with WebSphere Portalcontent publishing, such as was_home\wcp\author\lib andwas_home\wcp\runtime\lib.

g. Close the WAS Administrative Console.h. Using a file explorer or console window change to the

<was_root>\properties\com\ibm\websphere directory. Make a backup copyof the product.xml file and then open it with a text editor. In the file, youshould find the following two sections of text:<extension name="Personalization Server"><version>4.2</version><BuildDate>xx/xx/xx</BuildDate></extension>

and


<extension name="Personalization Common"><version>4.2</version><BuildDate>xx/xx/xx</BuildDate></extension>

Note that the BuildDate tags will include an actual date, not x’s. Delete allthese lines (and no others) and save the file. Depending on your editor,additional text may appear on the same line before or after these strings,but you should remove only the text between and including the<extension> and </extension> tags.

i. Navigate to <was_root>\temp directory. Change into the directory named foryour node, then into the directory named for the application server ontowhich you installed WebSphere Portal content publishing (for example,<was_root>\temp\nodename\appservername). If any of the followingsubdirectories are listed here, delete them and all their contents:v Personalization_Runtimev Personalization_Emailv LMAdminCenterv MovieSitev WCMv WCPDemo_Authorv WCM_Edge_Publish

The WebSphere Portal content publishing enterprise applications are nowremoved.

2. (Optional) Remove Business Rules BeansWebSphere Portal content publishing will also install some shared beans if theyare not already present. Since they are shared, the uninstall program does notremove them, nor is it necessary to do so. If you want to remove them, followthese steps:a. Stop the WAS Admin Server.b. In a file explorer or console window, change to <was_root>\lib directory.

Delete brbClient.jar and brbServer.jar.c. In a file explorer or console window, change to

<was_root>\properties\com\ibm\websphere directory. Make a backup copyof product.xml and then edit it. In the file, locate the following text:<extension name="Rules Runtime"><ext><name>Rules Runtime</name><build><number>ptf20202.06</number><date>1-30-2002</date></build></ext></extension>

Delete all of these lines, beginning with <extension... and ending with</extension>. Save the file.

d. Restart the WAS Admin Server. Business Rules Beans are now removed.3. (Optional) Drop database tables

During the installation of WebSphere Portal content publishing, severaldatabase tables may have been created. The uninstall program does not dropthese database tables, nor is it necessary to do so. If you wish to drop the tables


for Authoring, Runtime, Feedback, and LikeMinds, you may do so. Thisprocedure will vary depending on your database software.

4. Removing product filesWebSphere Portal content publishing installs files in several locations,depending on which features you selected to install. To completely uninstall theproduct, remove the following files and directories:a. Enterprise application files

In the <was_root> directory, delete the wcp directory and all of its contents.In <was_root>\installedApps, delete and folders for WebSphere Portalcontent publishing enterprise applications that may not have been removed.

b. Remove LikeMinds filesLikeMinds files are installed to the following directories by default, thoughyou may have specified an alternative directory during the installation.Delete the directory and its contents.v Windows default: C:\Program Files\LikeMinds

v AIX default: /opt/LikeMindsv Solaris default: /opt/LikeMinds

c. Remove WebSphere Portal content publishing wizards from WebSphereStudioTo manually remove the WebSphere Portal content publishing wizards forWebSphere Studio, delete the following two directories and their contentsfrom <studio_root>\plugins:v com.ibm.wcm.resource.wizardsv com.ibm.wcm.resource.wizards.doc

If necessary, restart WebSphere Studio.d. Remove documentation files

Documentation files are installed to the following directories by default,though you may have specified an alternative directory during theinstallation. Delete the directory and its contents.v Windows default: C:\Program Files\wcp

v AIX default: /opt/wcpv Solaris default: /opt/wcpv Linux default: /opt/wcp

e. Remove installation files1) Product installation files are installed to the following directories by

default. Delete the directory and its contents.v Windows: C:\Program Files\IBM\wcp

v AIX: /opt/IBM/wcpv Solaris: /opt/IBM/wcpv Linux: /opt/IBM/wcp

2) (AIX and Windows only)Open vpd.properties with a text editor.v Windows: C:\WINNTv AIX: /usr/lib/objrepos

Before editing it, create a backup copy of the file. Delete every line thatbegins with one of these keys and then save the file.

Chapter 8. Manually uninstalling WebSphere Portal content publishing 65

iwcpiwcp.auth.backupiwcp.authoring.biniwcp.authoring.db2iwcp.authoring.dbanalyze.windowsiwcp.authoring.dbcreateiwcp.authoring.dbcreate.unixiwcp.authoring.dbcreate.windowsiwcp.authoring.earsiwcp.authoring.libiwcp.authoring.oracleiwcp.authoring.wcmiwcp.authoringsamplesiwcp.authoringsamples.cmiwcp.authoringsamples.dbiwcp.authoringsamples.dbloadiwcp.authoringsamples.eariwcp.authoringsamples.filesiwcp.authoringserveriwcp.authortimeiwcp.dev.backupiwcp.developmentiwcp.documentationiwcp.likemindsiwcp.lm.backupiwcp.lmadmincenteriwcp.lmsamplesiwcp.lmsdkiwcp.lmserveriwcp.lmserverutilitiesiwcp.personalizationiwcp.pzn.backupiwcp.runtimeiwcp.runtime.createdb.windowsiwcp.runtimeedgepublishiwcp.runtimeedgepublish.wcpedgepublisheariwcp.runtimesamplesiwcp.runtimesamples.pznsampleeariwcp.runtimeserveriwcp.runtimeserver.businessrulebeansiwcp.runtimeserver.databaseiwcp.runtimeserver.pzncommoniwcp.runtimeserver.pzncommonjarsiwcp.runtimeserver.pzndeployedbeansiwcp.runtimeserver.pznservereariwcp.runtimeserver.pznupdateproductxmliwcpRegistrypzn.common.configpzn.update.persruntime.xml08a957a6729a6a6fa888da0208472c110911065e2bf83e4fcb9f24869407cbf30c1e412b2c1da23675c2325cc62818cf0c4ed52c741162356db96c682d11311c0c4ed52c741162356db96c682d11311c0c4ed52c741162356db96c682d11311c0dbfb1ca662c5ba0aeb245c650220dcd112bb0bb662ccb613a5ad36f2ab0084c13f7f58bf4dfa9b4f5891b588af6df1513f7f58bf4dfa9b4f5891b588af6df1518bf15b8a7dafd1cdcc1641b8985dfc4226a9862b863f7688da577b9483f727a25964940066b123fc2864d548ef0ca5828265118e6f83ffb648e3f76494bf1272b3578953e68cb53a0a2a79f0db2d93b362efde90515509fe056bf0f32c848e63a948ff9b858277fe2d1e1feedf210fc3c62d77ee0b55e77c866f90f481ddc09


4a7639d83df591d3dfc7d6278ab740ff4d5eda82f9adc8d2af947da836db1aad4e070f83492f036b8e1ea2ced25fd7a84e070f83492f036b8e1ea2ced25fd7a84ea3e061738dde56df8ee334b1fb160b4f712937c0536a15699fa4e59df0313e5ebbc091082aeda0733a5f54d3cfc4e76002a808ef1f9d4929197e9e4497a90a66946cae10f67c49c2139dbd61fa60ea68efe3ad81ee14d4d19992b45cac768468efe3ad81ee14d4d19992b45cac76846958dc50e199f8ebeae8e1d1669e19e76d0a6cde2cd2041a221aaffefe7392566f30a3d4132bf82b52a68e10c6174a5b6f8f3b7afb34fee5a5a5c719b95632f26fbe666ec492909a4448d24046d460b26fbe666ec492909a4448d24046d460b273b545cbbff269dbb94079480315f29f7616785779c27dbf454394325ed5b82f76f55fb08a01d0a6ece8dbcdf5e4a4f97c87da68ba7d81dade465b257205be047d91df66f4e0d3af6ea216b4ce841a5f7dc8de1e6fa799a664e3c6673b7527b17dd85f02b5f3fc3dfd1ed9bd9db9a29482ee9a7b7b84fa4859e4db61ca06455c84f4106159aeb466949e5939d5cb40b985ebd25aad800dbb6a555871901bbeb78b7a77ca8823d797a7be3c4adc6fd9e78ca0ec3e82831d7b958a8fc6d80201fb9408a63720644d46b8c9478d05bf544094970fcbe861596f66d73107e75ed4b49ae15d3c95fc8b5b6d273d2df5f298cc9ae15d3c95fc8b5b6d273d2df5f298cc9ae15d3c95fc8b5b6d273d2df5f298cc9b18850ad0c6b8bf40013697c14bd93aa036a1747ce720c93004d47d7c6e05bda09b0ca8b8ece82645608db51e391d3aa1576546e2c9e763c6ec79a7d10cf3d9ab866462247b9644f93e84db4f5b4ef3b18b5db7a617c035edda14ee30822cffb9173d1d117bdbdd8ed369ca295e434bb933aab1f422e8dbfaeab209ca883bfcb933aab1f422e8dbfaeab209ca883bfcb95c166cc91c12ee50f0ee306af506efb95c166cc91c12ee50f0ee306af506efba03835cf09abe570aad3a0a589e58e4ba03835cf09abe570aad3a0a589e58e4bab9b362794997bc2c513a071c98a214bcfca3d45bd150cfdec055b099093501bf2f4dcbba6b8ecb4d3e3441d311f455bf2f4dcbba6b8ecb4d3e3441d311f455bf2f4dcbba6b8ecb4d3e3441d311f455c110d414f1ec3c9b801a51ee74059f68c110d414f1ec3c9b801a51ee74059f68c561c9e8127e9cf430903e51e5022e6ec561c9e8127e9cf430903e51e5022e6ec561c9e8127e9cf430903e51e5022e6ec5a26768cc5c36a8da8c997c89e3e7c2c5a26768cc5c36a8da8c997c89e3e7c2c8bdc30221683fd45ec9d63fd8426ef5cf3bb3f9f271f08837b4d772a924d400d17be9c2a33238a69035b0cdb8507484d90dc52b3937196d71b14dc865bc3cb7d90dc52b3937196d71b14dc865bc3cb7d92bc8111341d9a504a4de0c62a3219ddbd8aea9a0ab958bbe4927044cd573b4dbd8aea9a0ab958bbe4927044cd573b4

Chapter 8. Manually uninstalling WebSphere Portal content publishing 67

dbd8aea9a0ab958bbe4927044cd573b4dcd4b9438c1c244ea6a9a1a449d53804e14298b2d86ff2a3155654f64506f74ee14298b2d86ff2a3155654f64506f74ee1bf4d940f9218345fb6a1327d67812ae45269825d97c95f476d847219ced365e7849b3f92d6841c77773c9ae43bb32fecf8b7dce12e93d7216a3de04ce0f283ecf8b7dce12e93d7216a3de04ce0f283ecf8b7dce12e93d7216a3de04ce0f283ed1999352554dd8d6d35b99e2dacfb5bed8cad6bacc8270ddbe69ce5d61e6de7edd1fce0be736b1ee31c6479234f54aaee6762ad9265a004e37fb3295c890b50f7858cb44632be05a6ac995ae13df510f8bbd8598fed2d31cfff976a3dc6deb0f8bbd8598fed2d31cfff976a3dc6deb0f8d47f7928a8d1b8d36e55fa94bdf221fb7a83a860e6626205d1abdd8c704ae6Fdb4fd61725002f975d2cd22b42bf103

3) (Windows only) Open the Windows registry editor and remove thefollowing entries, including any subkeys:v [HKEY_LOCAL_MACHINE] Software\IBM\Web Content Publisherv [HKEY_LOCAL_MACHINE]

Software\Microsoft\Windows\CurrentVersion\Uninstall\iwcp


Notices

Note to U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in thisDocumentation in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or implythat only that IBM product, program, or service may be used. Any functionallyequivalent product, program, or service that does not infringe any IBM intellectualproperty right may be used instead. However, it is the user’s responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this Documentation. The furnishing of this Documentation does notgive you any license to these patents.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OR CONDITIONS OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some statesdo not allow disclaimer of express or implied warranties in certain transactions,therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.


The licensed program described in this Documentation and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples may includethe names of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrates programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. (C) Copyright IBM Corp. 2002. All rights reserved.

Programming interface informationProgramming interface information is intended to help you create applicationsoftware using this program.

General-use programming interfaces allow you to write application software thatobtain the services of this program’s tools.

However, this information may also contain diagnosis, modification, and tuninginformation. Diagnosis, modification and tuning information is provided to helpyou debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as aprogramming interface because it is subject to change.


Trademarks and service marksThe following terms are trademarks or registered trademarks of InternationalBusiness Machines Corporation in the United States, or other countries, or both:v DB2®

v DB2 Universal Database™

v IBMv WebSphere

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and other countries.

ActiveX, Microsoft®, Windows, Windows NT®, and the Windows logo aretrademarks or registered trademarks of Microsoft Corporation in the United States,or other countries, or both.

UNIX is a registered trademark of The Open Group.

Linux is a registered trademark of Linus Torvalds.

Other company, product, and service names, which may be denoted by a doubleasterisk(**), may be trademarks or service marks of others.

Notices 71

websphere portal content publishing installation...

Documents