WebSphere Portal content publishing Installation Guide

Transcription

1 WebSphere Portal content publishing Installation Guide

2 Note! Before using this information and the software it supports, be sure to read the general information under Notices. First Edition (November 2002) This edition applies to the current version of WebSphere Portal content publishing and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the software. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Chapter 1. Installation Guide Terminology Prerequisites Chapter 2. Example installation scenarios Proof of concept scenario Production with Domino Workflow Production with Lite Workflow Chapter 3. Planning your installation.. 9 Migration Database installation WebSphere Application Server Workflow Management Version Control Development environment Authoring environment Runtime environment Considerations for LikeMinds Recommendation Engine Chapter 4. Preparing to install WebSphere Portal content publishing. 15 Uninstalling WebSphere Portal content publishing 15 Preparing databases and content stores Configuring an Oracle database Configuring a DB2 database Installing IBM Content Manager Preparing workflow management Setting up Lotus Workflow Preparing security/authentication Local operating system LDAP Lotus Domino Preparing version control Preparing to install LikeMinds Recommendation Engine Using an existing database for your LikeMinds installation Using a different table schema from the default tables Creating the database for Microsoft SQL Server 32 Configuring an ODBC DSN for Microsoft SQL Server Preparing for a LikeMinds Recommendation Engine installation on Oracle Preparing for a LikeMinds Recommendation Engine installation on IBM DB Using Movie Site, the LikeMinds Admin Center, or the LikeMinds SDK Chapter 5. Installing WebSphere Portal content publishing Installing the development environment WebSphere Studio WebSphere Portal content publishing wizards for WebSphere Studio Installing the authoring environment Installing the Authoring Server and Sample.. 39 Installing WebSphere Portal content publishing Desktop Integration Installing the runtime environment Installing a Production Server Verifying your installation Configuring the runtime environment Cloning the runtime environment Installing the documentation (custom location).. 54 Installing the documentation (custom location) 54 Verifying the installation and accessing the documentation Troubleshooting Text truncation in install panels on AIX and Linux Chapter 6. Accessing the Sample Starting WebSphere Portal content publishing Getting Started Tutorial (for use with the Authoring Server Sample) Chapter 7. Troubleshooting Chapter 8. Manually uninstalling WebSphere Portal content publishing. 63 Notices Programming interface information Trademarks and service marks Copyright IBM Corp iii

4 iv WebSphere Portal content publishing Installation Guide

5 Chapter 1. Installation Guide Terminology Prerequisites This guide is for those performing custom installations of WebSphere Portal content publishing and is not intended for use with the WebSphere Portal Setup Manager. Use of the Setup Manager is recommended if you are doing a full installation of WebSphere Portal content publishing. Setup Manager will install the prerequisites for 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: The following is a list of terms and definitions used throughout this installation guide. was_home Indicates the root directory where WebSphere Application Server (WAS) is installed. For example, on Windows platforms the WAS root directory could be C:\WebSphere\AppServer, on AIX platforms the WAS root directory could be /usr/websphere/appserver. oracle_home Indicates the root directory where Oracle is installed. For example, on Windows platforms the Oracle root directory could be C:\Oracle, on AIX platforms the Oracle root directory could be /u01/app/oracle. studio_root Indicates the root directory where WebSphere Studio is installed, for example, C:\Program Files\IBM\Application Developer on Microsoft Windows. In order to provide the most current information, the hardware and software prerequisites have been made available on the WebSphere Portal content publishing Web site: Copyright IBM Corp

6 2 WebSphere Portal content publishing Installation Guide

7 Chapter 2. Example installation scenarios Proof of concept scenario Generally, WebSphere Portal content publishing and its prerequisites can be divided into three functional environments: WebSphere Portal content publishing development environment One or more of the following: v One of the WebSphere Studio Family of Products v WebSphere Portal content publishing wizards for WebSphere Studio WebSphere Portal content publishing authoring environment One or more of the following: v WebSphere Portal content publishing Authoring Server (required) v WebSphere Portal content publishing Authoring Server Sample v 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 environment One or more of the following: v WebSphere Portal content publishing Production Server v WebSphere Portal content publishing Edge Server v WebSphere Portal content publishing Personalization Runtime v WebSphere Portal content publishing LikeMinds Recommendation Engine It is recommended that these environments be on different machines. Three example scenarios are provided that demonstrate different installation configurations and a basic concept of the development process. Note that these scenarios are only examples; these are not the only possible configurations. This example scenario, illustrated below, demonstrates one of the simpler installation configurations. Copyright IBM Corp

8 Here, all machines are running Microsoft Windows (specifically, Windows 2000). In the runtime environment are WebSphere Portal, WebSphere Portal content publishing Production Server, and the optional WebSphere Portal content publishing Personalization run-time environment for interpreting business rules and delivering dynamic, targeted content. Security and authentication for the run-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 Studio Family of Products (for example, WebSphere Studio Application Developer) with the WebSphere Portal content publishing wizards and WebSphere Portal toolkit. 4 WebSphere Portal content publishing Installation Guide

9 The developer generates and delivers content, Web pages (HTML/JSPs), servlets, portlets, application objects, resource classes, and content spots to both the Authoring and Production Servers. The business users and other content contributors can create and publish content to the Web site on the Production Server via the WebSphere Portal content publishing workspace. Because the Personalization runtime has been installed on the Production Server, business users can use the workspace to create rules and campaigns that govern dynamic content delivery and publish them to the run-time environment. Also, business users can use the workspace to analyze reports and charts about the logged activity in the Feedback database. Production with Domino Workflow In the configuration shown below, Lotus Domino, Lotus Workflow and Lotus Domino LDAP are installed with the WebSphere Portal content publishing Authoring Server. The LDAP Server provides security and authentication for both the Authoring and Production servers (both Sun Solaris). Lotus Domino Workflow is coupled with WebSphere Portal content publishing s versioning capabilities, with approved versions of content being published to a remote content store that is also accessed remotely from the run-time environment. Chapter 2. Example installation scenarios 5

10 Production with Lite Workflow The sample installation configuration shown here demonstrates integration with IBM Content Manager as a content and versioning store. In this example, IBM CM and IBM Enterprise Information Portal are located on the Production Server (AIX), and are accessible from the development and authoring environments (Microsoft Windows). 6 WebSphere Portal content publishing Installation Guide

11 Additionally, IBM Directory Server, located on the Production Server, provides LDAP authentication services for both the Authoring and Production Servers. Note that the LikeMinds Recommendation Engine is installed on the Production Server, enabling the use of recommendation-based personalization of dynamic content. Chapter 2. Example installation scenarios 7

12 8 WebSphere Portal content publishing Installation Guide

13 Chapter 3. Planning your installation Migration Database installation It is possible to migrate projects or configuration information from previous releases of WebSphere Personalization, LikeMinds, and Web Content Publisher for use with WebSphere Portal content publishing. Migration of configuration information must be performed before continuing with this installation. The migration utilities are provided on the WebSphere Portal installation CD 5 in the wpcp\migration directory. For instructions on using these utilities, refer to the WebSphere Portal content publishing Web site: Similarly to WebSphere Application Server, the WebSphere Portal content publishing Authoring Server and Production Server each require access to relational databases. Typically the database will be a local installation of IBM DB2 or Oracle, although it is possible to use databases on remote machines. For storage of content (files, images, digital media, and so on), you can use either of these repositories or an installation of IBM Content Manager and IBM Enterprise Information Portal (EIP). Regardless of your choice, the database must be installed and correctly configured before you install WebSphere Portal content publishing. WebSphere Application Server Workflow Management WebSphere Application Server must be installed and functioning correctly on each machine where you plan to install a WebSphere Portal content publishing Authoring Server or Production Server. Security may be enabled or disabled prior to beginning the installation. There are three options for implementing workflow for the WebSphere Portal content publishing authoring environment: no workflow; Lite workflow (a basic workflow process built into the WebSphere Portal content publishing Authoring Server software); and Lotus Workflow. No setup is necessary if you will not be using 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. Copyright IBM Corp

14 Version Control Development environment Authoring environment There are several options for implementing version control for the WebSphere Portal content publishing authoring environment: IBM Content Manager, Rational ClearCase, CVS, or the version control built into WebSphere Portal content publishing. The version control software that you plan to use should already be installed 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 content store and the version store. If IBM CM is used as the content store, it must also be used as the version store. v IBM Content Manager versions resources in a common namespace. Whereas other providers can scope different resources with the same name according to different 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 version store, resource metadata (such as project, workspace) are versioned along with the resource itself. If used as a standalone version provider, these attributes are not versioned. v Client software for the version control solution you plan to use should be installed on the machine where you will install the WebSphere Portal content publishing Authoring Server. Machines in the development environment must have access to the content store, the Authoring Server, and the version store, if applicable. It is recommended that these machines use one of the WebSphere Studio Family of Products for development. WebSphere Studio should already be installed on the development machine prior to installing the Wizards for WebSphere Studio (included in the WebSphere Portal content publishing installation). The authoring environment is the machine where the WebSphere Portal content publishing workspace is located. The following are required components: v A database management system v WebSphere Application Server v WebSphere Portal content publishing In addition, WebSphere Portal content publishing works with various library and repository management systems. It also enables you to add workflow management and versioning management. Most of these management systems can be installed locally or remotely to the Authoring Server. Notes: 1. Installing the sample is recommended. The sample makes it easy for you to verify your installation and get started quickly with WebSphere Portal content publishing. 2. If installing the Authoring Server on an AIX platform that uses a double-byte language, ensure the appropriate fonts are installed: v For ja_jp or Ja_JP: X11.fnt.ucs.ttf 10 WebSphere Portal content publishing Installation Guide

15 Runtime environment v For zh_cn or Zh_CN: X11.fnt.ucs.ttf_CN v For ko_kr: X11.fnt.ucs.ttf_KR v For zh_tw or Zh_TW: X11.fnt.ucs.ttf_TW 3. WebSphere Portal content publishing does not support log records that have double-byte characters, nor are double-byte or non-ascii characters in pattern matching parameters. The runtime environment is the production server that the Web site visitor interfaces with, and contains the engines required to deliver Web content, to personalize the Web content, and to record site metrics. The following are required components: v A database management system Personalization supports DB2, Oracle, Informix, Microsoft SQL Server, and Sybase Feedback supports DB2 and Oracle LikeMinds supports DB2, Oracle, Microsoft SQL Server, or any ODBC-compliant RDBMS v WebSphere Application Server v WebSphere Portal content publishing The Feedback (site analysis) engine allows site metrics to be viewed in the WebSphere Portal content publishing workspace. The rules-based Personalization engines and the LikeMinds Recommendation Engine are optional installations. If you 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 logging depends on the amount of traffic to the site, and the amount of data logged per logging-enabled page can vary. However, a rough guideline that you can use is 0.75 KB per record logged to the database. Therefore, a site that serves an average of 20,000 logging-enabled pages per day, with each page generating three log records (through rules, categories, and so on), will generate approximately 45 MB of logged data per day. Considerations for LikeMinds Recommendation Engine Before you begin the installation, consider where you will put the major parts of your LikeMinds Recommendation Engine installation: v v v If possible, install the LikeMinds database on a different machine from LikeMinds Personalization Server. Installing the database on a different machine from LikeMinds Personalization Server will increase LikeMinds performance. Ideally, you should use your fastest machine for the database. You also will need disk space for your database. The amount required will depend on your application and the number of users at your site. For guidelines on estimating the size of your database refer to the LikeMinds Recommendation Engine documentation of the WebSphere Portal content publishing Help System. If you plan to use the Movie Site application, you can install it and the Web server on the same machine as LikeMinds Personalization Server. If you serve large amounts of additional content from the same Web server, you may want to install the Web server on a separate machine from LikeMinds Chapter 3. Planning your installation 11

16 v Personalization Server. However, Movie Site or your application must be installed on the same machine as the Web server. They do not need to be on the same machine as LikeMinds Personalization Server. You must install the LikeMinds Admin Center onto any machine that has a Web server, but it does not need to be on the same machine as LikeMinds Personalization Server. The LikeMinds Admin Center is designed to be used remotely. The machine where LikeMinds Personalization Server is installed should have at least 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 the same local area network. Placing the machines on separate networks is possible, but slow communications between machines can degrade performance. Installing LikeMinds Recommendation Engine for a single-system For a single-system sites, install LikeMinds Recommendation Engine as follows: v v The RDBMS and LikeMinds Personalization Server should be on separate machines, but can be on a single machine. 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 multiple systems For multiple-system sites, install LikeMinds Recommendation Engine as follows: v Install the RDBMS onto its own machine, preferably the fastest. v v 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 each client machine as well. You do not need to install the LikeMinds Personalization Server server onto these client machines. For IBM DB2, make sure each client machine has the IBM DB2 Runtime Client installed. For Oracle, make sure each client machine has the following Oracle-specific components: Oracle Client (including Net8 and SQL*Plus) ORACLE_HOME environment variable set TNSNAME entry in tnsnames.ora Installing the LikeMinds Recommendation Engine utilities across multiple machines: You can install the LikeMinds Personalization Server utilities and LikeMinds servers across multiple machines for load balancing. In general, you need to install the LikeMinds Personalization Server itself, which includes its utilities, onto each machine, but have its service running on only one machine. You will also need to disable or enable the LikeMinds Personalization Server utilities on each 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 set this service to run. It also has the buildstats, buildvisit, sifter, and accumulator utilities, which need to be disabled as follows: 12 WebSphere Portal content publishing Installation Guide

17 buildstats and buildvisit: Inthe <LM_install_dir>\lrs\util\daily script, comment out the lines that refer to starting buildstats and buildvisit. sifter: Inthe <LM_install_dir>\lrs\server\prefetch script, comment out the line that refers to starting the sifter. accumulator: Do not run the accumulator on this machine. v On the remaining machines, you can install the utilities separately, each with its LikeMinds Personalization Server server disabled and with the appropriate utility enabled. To disable the LikeMinds Personalization Server, use the Control Panel Services applet. Machine 4: Has a LikeMinds Recommendation Engine that is not enabled, and an 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 the background, so configure this system to start the sifter at boot time. For very large sites, you may want to have a sifter on more than one machine. If you do use multiple sifters, be sure that each sifter is looking at a distinct group of users. (Multiple sifters should not be looking at the same user). Refer to the LikeMinds Recommendation Engine documentation of the WebSphere Portal content publishing Help System for information on using multiple sifters. The buildstats, buildvisit, and the accumulator utilities on this machine are automatically disabled as long as the LikeMinds Personalization Server on this machine is disabled. If you plan to use the LikeMinds Personalization Server on this system, you can disable buildstats and buildvisit by commenting out their start lines in the daily script. Chapter 3. Planning your installation 13

18 14 WebSphere Portal content publishing Installation Guide

19 Chapter 4. Preparing to install WebSphere Portal content publishing Uninstalling WebSphere Portal content publishing Note: Do not attempt to remove WebSphere Portal content publishing from your machine by simply deleting or removing the enterprise archives. You will not be able to reinstall WebSphere Portal content publishing. If this occurs, go to Chapter 8, Manually uninstalling WebSphere Portal content publishing on page 63. If WebSphere Portal content publishing is installed on your system, then you will need 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 new installation. If you have data in the WebSphere Portal content publishing that you want to preserve, backup the authoring environment databases. 2. Remove any Resource Collections using the Resource Console ( Click the Resource Collections tab, select a resource collection from the drop-down list and click Delete; repeat until all are removed. 3. For Windows, go to the C:\Program Files\IBM\wcp\uninst directory and run wcpuninstall.exe. (You can also uninstall the program from the Add/Remove Programs application in the Control Panel.) 4. For UNIX platforms, go to the /opt/ibm/wcp/uninst directory and execute the following 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_ .ear Personalization_Runtime.ear wcm.ear WCPDemo_Author.ear v Verify that the temporary directories for WebSphere Portal content publishing were 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 your uninstallation is complete. v pkginfo grep IBMWCP If the system returns WebSphere Portal content publishing registrations, then WebSphere Portal content publishing is not completely uninstalled. Copyright IBM Corp

20 v If WebSphere Portal content publishing registrations are returned, run the following command for each WebSphere Portal content publishing registration: pkgrm IBMWCPxxx v where IBMWCPxx is the name of the WebSphere Portal content publishing registration. Rerun pkginfo grep IBMWCP If you are using AIX, run the following command to ensure that your uninstallation is complete. v ODMDIR=/usr/lib/objrepos odmget vendor 2>&1 tee /tmp/vendor.file If the system returns WebSphere Portal content publishing registrations, then WebSphere Portal content publishing is not completely uninstalled. If you are using Linux, run the following command to ensure your uninstallation is complete. v rpm qa grep i wcp If any packages are returned, these must be removed before uninstallation is complete. If you encounter any problems during uninstallation or verification of uninstallation, refer to Chapter 8, Manually uninstalling WebSphere Portal content publishing on page 63. Preparing databases and content stores Configuring an Oracle database Oracle must be configured to work with WebSphere Application Server and WebSphere Portal content publishing. The database configuration must be done by a qualified Oracle database administrator. For instructions on configuring Oracle for the operating system where you have it installed, see the appropriate section. Configuring Oracle on Microsoft Windows 2000 Server To 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 one used by WebSphere Application Server. Ensure that: v The characterset is UTF-8 v The national language character set is UTF-8 v The database is configured for the number of concurrent users you need to support v The SID for the database must be the same as the name. 2. Define the WebSphere Portal content publishing IDs with database administration authority by creating the Oracle users PZNADMIN and EJB using the following commands. (Note: if you do not want them to 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 the second command, use PZNADMIN and EJB as the IDs. 16 WebSphere Portal content publishing Installation Guide

21 sqlplus create 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 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@xxx create 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 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 = Stop and restart the following Oracle services to pick up the changes to the initialization files v OracleServiceXXX v OracleServiceWCPDEMO v 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@xxx show parameter open_cursors When a message is displayed indicating that the connection was successful, type exit. Configuring Oracle on AIX To 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. Ensure that: v The characterset is UTF-8 v The national language character set is UTF-8 v The database is configured for the number of concurrent users you need to support v The SID for the database must be the same as the database name. 2. Define the WebSphere Portal content publishing IDs with database administration authority by creating the Oracle users PZNADMIN and EJB using the following commands. (Note: if you do not want PZNADMIN and EJB to have database administrator authority, skip to step 3). For values needed in Chapter 4. Preparing to install WebSphere Portal content publishing 17

22 the first command, enter system as the ID and manager as the password. For the second command, use PZNADMIN and EJB as the ID. sqlplus create 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 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@xxx create 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 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 initialization files, typically located at oracle_home/admin/xxx/pfile/initxxx.ora where xxx is your SID. 5. Modify the following line to the initialization files open_cursors = Stop and restart the Oracle databases and listener to pick up the changes to the initialization files. 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@xxx show parameter open_cursors When a message is displayed indicating that the connection was successful, type exit. Configuring Oracle on Solaris To 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. Ensure that: v The characterset is UTF-8 v The national language character set is UTF-8 v The database is configured for the number of concurrent users you need to support v The SID for the database must be the same as the database name 2. Define the WebSphere Portal content publishing IDs with database administration authority by creating the Oracle users PZNADMIN and EJB using the following commands. (Note: if you do not want PZNADMIN and EJB to 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 the second command, use PZNADMIN and EJB as the ID. 18 WebSphere Portal content publishing Installation Guide

23 sqlplus create 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 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@xxx create 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 symbol) without the domain. 4. Locate the WebSphere Portal content publishing and WCPDEMO database initialization files. Change to the Solaris Oracle user. Navigate to the initialization files, typically located at oracle_home/admin/xxx/pfile/initxxx.ora where xxx is your SID. 5. Modify the following line to the initialization files open_cursors = Stop and restart the Oracle databases and listener to pick up the changes to the initialization files. 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@xxx show parameter open_cursors When a message is displayed indicating that the connection was successful, type exit. Before you use WebSphere Portal content publishing, you must stop the OracleOraHome81HTTPServer service. Configuring Oracle on Linux To 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. Ensure that: v The characterset is UTF-8 v The national language character set is UTF-8 v The database is configured for the number of concurrent users you need to support v The SID for the database must be the same as the database name 2. Define the WebSphere Portal content publishing IDs with database administration authority by creating the Oracle users PZNADMIN and EJB using the following commands. (Note: if you do not want PZNADMIN and EJB to have database administrator authority, skip to step 3). For values needed in Chapter 4. Preparing to install WebSphere Portal content publishing 19

24 the first command, enter system as the ID and manager as the password. For the second command, use WCPADMIN as the ID. sqlplus create 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 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@xxx create 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 symbol) without the domain. 4. Locate the WebSphere Portal content publishing and WCPDEMO database initialization files. Change to the Linux Oracle user. Navigate to the initialization files, typically located at oracle_home/admin/xxx/pfile/initxxx.ora where xxx is your SID. 5. Modify the following line to the initialization files open_cursors = Stop and restart the Oracle databases and listener to pick up the changes to the initialization files. 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@xxx show parameter open_cursors When a message is displayed indicating that the connection was successful, type exit. Configuring a DB2 database IBM DB2 must be configured to work with WebSphere Portal content publishing. For instructions on configuring DB2, see the appropriate section. Enabling JDBC2.0 Before you can install WebSphere Portal content publishing, your installation of DB2 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 the Services panel. 20 WebSphere Portal content publishing Installation Guide

25 3. Open a DB2 command window, go to the \Program Files\SQLLIB\java12 directory, and run the following file: usejdbc2.bat 4. Start the DB2 services you stopped in Step 2 and WebSphere Application Server. To enable JDBC2.0 on UNIX, select the JDBC2.0 version of db2java.zip in the Driver Location field of the appropriate Database Configuration panels during the installation of WebSphere Portal content publishing: v Linux: /usr/ibmdb2/v7.1/java12/db2java.zip v AIX: /usr/lpp/db2_07_01/java12/db2java.zip v Solaris: /opt/ibmdb2/v7.1/java12/db2java.zip Creating and configuring a DB2 database for WebSphere Portal content publishing If you have an existing database, will be creating your own database, or will be using a remote database: 1. Open a DB2 Command Window and execute the following command: DB2 CREATE DB MY_DATABASE USING CODESET UTF-8 TERRITORY US COLLATE USING IDENTITY Where MY_DATABASE is the name of the database you are creating. Substitute your territory code if different from US. 2. Configure the database for WebSphere Portal content publishing by executing the following command: DB2 UPDATE DB CFG FOR MY_DATABASE USING APPLHEAPSZ 4096 LOGFILSIZ 3000 LOGPRIMARY 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 4096 LOGPRIMARY 4 LOGSECOND 25 Some additional parameters that are not necessary but can be used to improve performance the Feedback database include: v DBHEAP = 4096 v STMTHEAP = 4096 v CATALOGCACHE_SZ = 256 v LOCKLIST = 1024 v 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 Manager IBM Content Manager must be installed prior to installing WebSphere Portal content publishing. When installing IBM CM, two programs are required: Content Manager and IBM Enterprise Information Portal (EIP). Note the following: v 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. IBM EIP must be installed on the same machine as the WebSphere Portal content publishing Authoring Server. Chapter 4. Preparing to install WebSphere Portal content publishing 21

26 Installing and configuring IBM Content Manager To manage large collections of data or multimedia collections, you may want to use WebSphere Portal content publishing with IBM Content Manager. Before you install WebSphere Portal content publishing to work with IBM Content Manager, you must install IBM Content Manager and IBM Enterprise Information Portal and their prerequisites. Follow the installation instructions provided with each of these products. Verifying your IBM Content Manager installation: After you have installed IBM Content Manager, IBM Enterprise Information Portal and their prerequisite software, you should test your system and verify that IBM Content Manager (library server, resource manager, system administration client) and IBM Enterprise Information Portal (administration database, Content Manager connector) are working. You can do this by following the instructions on testing the server installation and configuration in the IBM Content Manager guide to Planning and Installing Your Content Management System. You can also verify that IBM Content Manager and IBM Enterprise Information Portal are working properly by compiling 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 type Resource 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 IBM Content Manager. If you encounter problems with importing, see the troubleshooting section in Planning 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 to provide the following information about your IBM Content Manager installation: Library server database name The name you type in the WebSphere Portal content publishing Installation Server field. Library server database administration ID The ID you type in the WebSphere Portal content publishing Installation User ID field. 22 WebSphere Portal content publishing Installation Guide

27 Password The password you use to administer the IBM Content Manager library database. Resource manager database name The name you type in the WebSphere Portal content publishing Installation Default Resource Manager Name field. You can use IBM Content Manager for storage and management of content as well as version control. For instructions on using IBM Content Manager for version control, see the section in the WebSphere Portal content publishing Administrator s Guide on version control. Preparing workflow management Setting up Lotus Workflow Instructions for installing Lotus Domino Server are provided below. Notes: 1. Do not install Lotus Domino Server on a machine where Lotus Notes or Lotus Domino are already installed. 2. You do not have to install Lotus Domino on the same machine where you installed WebSphere Application Server and WebSphere Portal content publishing. The installation and configuration of Lotus Domino Server consists of the following steps: v Installing Lotus Domino Server v Configuring Lotus Domino Administrator v Sample users and groups in Lotus Domino Administrator on page 24 v Configuring WebSphere Security and Domino SSO on page 27 v Configuring Single Sign-on (SSO) between Domino and WebSphere on page 27 Installing Lotus Domino Server To install Lotus Domino Server, use WebSphere Portal installation CD 8 and choose the installation file for your operating system. The installation will lead you through most of the necessary configuration steps. During installation of Lotus Domino Server, you will be prompted for the following information: v Domain Name v Certifier Organization v Certifier Password v Administrator user ID and password Ensure that the Domain Name and Certifier Organization match your LTPA Domain Name. You can accept default values in the other fields. During the Lotus Domino Server installation you will also be prompted to configure SSO in Lotus Domino. To do this task, you will need to enter the location of the keys file and password used to generate the LTPA key from your WebSphere Application Server installation. Configuring Lotus Domino Administrator The first time you use Lotus Domino Administrator you will be prompted to do the following configuration steps: Chapter 4. Preparing to install WebSphere Portal content publishing 23

28 1. Start the Lotus Domino Administrator. FromtheStart Menu, select Programs Lotus Applications Lotus Domino Administrator. The Lotus Notes Client Configuration 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 is Domino 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 to type 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 not available from the Workspace. You can ignore this error message and click OK. Sample users and groups in Lotus Domino Administrator You will need an ID for administering WebSphere Application Server Security and Lotus Domino Administrator. For additional information on what ID to use, refer to the WebSphere Portal documentation. There are four users identified with roles in the samples that are created during installation, as well. These roles are defined to the sample workflow processes. If you wish to use the samples or work through the Getting Started tutorial, you should create these users. For security purposes, we strongly recommend that you update these users with different passwords that adhere to standard password security guidelines. These user IDs and passwords should be treated as you would treat any other IDs and passwords because people using them will have all the server privileges you specify. Finally, to fully explore the sample workflows, you can use these instructions to create additional users. Installing the Lotus Workflow Process Designer s Guide If your team plans to design their own workflow processes, you will want to install the Process Designer s Guide. To install the Process Designer s Guide: 24 WebSphere Portal content publishing Installation Guide

29 1. From the WebSphere Portal installation CD 10, copy \lwfarchitect\lwf_process-designer_30_en.nsf to the data directory where you installed Lotus Workflow Architect. If you did a typical install, copy the file to \Lotus\Notes\data. 2. In the directory where you installed Lotus Workflow Architect, modify the workflow.ini file so that the HelpDBPath is set to reference the fully qualified path where you copied lwf_process-designer_30_en.nsf. If you did a typical install, 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 with LWF Application R3.0, LWF Process Definition R3.0, and LWF Organization 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. If not, 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. Chapter 4. Preparing to install WebSphere Portal content publishing 25

30 5) Detach the userid file to your Lotus/notes/data directory. In the File name 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, perform the 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 and select 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 notification in Lotus Domino Administrator for use with WebSphere Portal content publishing samples By default, notification for the sample users is not enabled. If you want the sample users to receive notification of workflow events, follow these steps to enable 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 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 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 select your Domino Server. 26 WebSphere Portal content publishing Installation Guide