Lotus Workplace. Version Upgrade Guide: Version 2.0 to G

Transcription

1 Lotus Workplace Version Upgrade Guide: Version 2.0 to G

2 Terms of Use Disclaimer THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONL. WHILE EFFORTS WERE MADE TO VERIF THE COMPLETENESS AND ACCURAC OF THE INFORMATION CONTAINED IN THIS DOCUMENTATION, IT IS PROVIDED AS IS WITHOUT WARRANT OF AN KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM S CURRENT PRODUCT PLANS AND STRATEG, WHICH ARE SUBJECT TO CHANGE B IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR AN DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENTATION OR AN OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS DOCUMENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING AN WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE. Licensed Materials - Property of IBM (C) Copyright IBM Corporation All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GS ADP Schedule Contract with IBM Corp. Lotus SoftwareIBM Software GroupOne Rogers StreetCambridge, MA List of Trademarks IBM, the IBM logo, AIX, Cloudscape, DB2, Lotus, WebSphere, and Workplace Messaging are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel is a trademark of Intel Corporation in the United States, other countries, or both. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

3 Contents Chapter 1. Upgrade Overview Lotus Workplace 2.0-to upgrades Upgrade roadmap Upgrade known issues Conventions Additional documentation Chapter 2. Performing Pre-upgrade Steps Performing pre-upgrade steps Step 1: Recording Administrative Console settings..5 Step 2a: Emptying the message queue Disabling inbound mail Reporting the status of the message queue...7 Expediting pending mail Removing dead messages Step 2b: Deleting orphaned mail accounts....8 Step 3: Preparing the database server Step 4: Preparing the Lotus Workplace server...10 Chapter 3. Performing the Upgrade.. 13 Performing the upgrade Step 1 Reading the release notes Step 2: Installing and setting up Lotus Workplace products Step 3: Verifying the Lotus Workplace functionality Step 4: Restoring the Lotus Workplace 2.0 data..14 Step 5: Configuring the Team Tasks, Chat, and Chat Room portlets Step 6: Re-creating Administrative Console settings 19 Administrative Console page reference Re-creating Lotus Workplace Server settings..23 Re-creating Additional Searchable Directories settings Re-creating user policy settings Re-creating mail cells Re-creating archive properties Re-creating outbound connections for the SIP proxy Reimporting client certificates Step 7: Upgrading the rich client software Upgrading the rich client provisioning page and portlets Uninstalling the version 2.0 rich client from desktops Installing the version rich client on desktops 28 Step 8: Verifying the upgrade iii

4 iv Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

5 Chapter 1. Upgrade Overview This chapter provides overview information on upgrading from IBM Lotus Workplace 2.0 products to Lotus Workplace products. Lotus Workplace 2.0-to upgrades To upgrade Lotus Workplace 2.0 products to version 2.0.1, you back up the version 2.0 data, uninstall version 2.0, (including the installed WebSphere Application Server and WebSphere Portal software), install Lotus Workplace version products using the same server deployments, configuration choices, and installation directories that you used for version 2.0, and then restore the version 2.0 data. Version of the Lotus Workplace products requires WebSphere Application Server and WebSphere Portal , a change from version 2.0. This software is provided with the Lotus Workplace installation kit. Other software requirements and the hardware requirements remain the same as in version 2.0. Refer to the Lotus Workplace Release Notes at for the list of requirements. Note the following upgrade requirements: v Only Lotus Workplace 2.0 deployments that use IBM DB2 as the database software are supported for upgrades to version 2.0.1; version 2.0 deployments that use, Cloudscape, Oracle, or Microsoft SQL Server are not supported for upgrades. The installation must continue to use the same DB2 server. v Only Lotus Workplace 2.0 single-server or two-server deployments are supported for upgrades to version 2.0.1; upgrading a network deployment is not supported. In addition, you must use the same type of deployment for that you did for 2.0; for example if you used a single-server deployment for 2.0, you must use that type for v The installation must use the same LDAP server and version and the same LDAP directory as the 2.0 installation. v The installation must use the same HTTP server and version as the 2.0 installation. v During the installation you must select the same licensed products that you selected for the 2.0 installation. v ou cannot upgrade Lotus Workplace to version 2.0.1; you must first upgrade Lotus Workplace to 2.0. The upgrade preserves most, but not all, of the version 2.0 data. The following table describes which data is preserved. Data Mail accounts es Mail messages es Contacts Preserved? es Calendar data es Team spaces es Documents es Web conferences es Courses and other Collaborative Learning data es Custom Workplace application policy settings in the WebSphere Administrative Console es. 1

6 Data Custom settings other than Workplace application policy settings in the WebSphere Administrative Console Custom configuration settings made through the file system Preserved? No, record and then re-create. No, record then re-create. Version of the Lotus Workplace products incorporates many fixes. For a list of these fixes, contact IBM Software Support. Upgrade roadmap To upgrade Lotus Workplace 2.0 products to version 2.0.1, complete the following steps. 1. Read this entire guide. 2. Perform these pre-upgrade steps described in the chapter Performing Pre-upgrade Steps: a. Record custom Administrative Console settings. b. Empty the message queue and delete orphaned mail accounts. c. Prepare the database server by backing up the version 2.0 databases and then dropping the databases from the server. d. Prepare the Lotus Workplace server by backing up the Lotus Workplace 2.0 files and then uninstalling Lotus Workplace and its related products. 3. Perform these upgrade steps described in the chapter Performing the Upgrade : a. Read the Lotus Workplace Release Notes. b. Install and set up Lotus Workplace products. c. Verify the Lotus Workplace functionality. d. Restore Lotus Workplace 2.0 data. Note: This step requires the C81H6ML.zip file, which is available from the Lotus Support Services Web site. This zip file is found in the document IBM Lotus Workplace 2.0 to upgrade V1 for Windows, IBM AIX, Linux at e. Configure the Team Tasks, Chat, and Chat Room portlets. f. Re-create custom Administrative Console settings. g. If you installed, or will ever install, the rich client provisioning server, upgrade the rich client software. h. Verify the upgrade. Upgrade known issues Collaborative Learning announcements do not function in Lotus Workplace after the upgrade. Conventions This guide uses the following conventions to denote root installation directories. Root installation directory Convention WebSphere Portal ( \WebSphere\PortalServer\, default) <wp_root> WebSphere Application Server (\WebSphere\AppServer\, default) <was_root> 2 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

7 Root installation directory Convention Lotus Workplace (\WebSphere\WorkplaceServer\, default) <lwp_root> Note: This guide sometimes shows path names with backward slashes (\) only, which is the Windows path name convention. If you use AIX or Linux, assume forward slashes instead (/). Additional documentation Refer to the following documentation in addition to this guide. Lotus Workplace Installation Guide This guide describes how to install Lotus Workplace products and is available on the Web at Lotus Workplace Information Center This information center provides information on configuring and administering Lotus Workplace products, and also includes all the information in the Lotus Workplace Installation Guide. It is available on the Web at Lotus Workplace Release Notes The release notes describe hardware and software requirements, and known issues and workarounds for client and server components. Before you begin the upgrade, it is important to read the release notes for information on known installation issues and their workarounds. The release notes are available on the Web at WebSphere Portal Information Center This information center describes how to install, configure, and administer WebSphere Portal and is available on the Web at Chapter 1. Upgrade Overview 3

8 4 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

9 Chapter 2. Performing Pre-upgrade Steps This chapter describes steps that you must take before you begin the upgrade process. Performing pre-upgrade steps Before you begin the upgrade process, perform the following pre-upgrade steps. 1. Record custom Administrative Console settings. 2. If you use Lotus Workplace Messaging : a. Empty the message queue. b. Delete orphaned mail accounts. 3. Prepare the database server. 4. Prepare the Lotus Workplace server. Step 1: Recording Administrative Console settings Follow these steps to record Administrative Console settings that you created for version 2.0, so that you can re-create the settings after the upgrade is complete. ou do not have to record Workplace application policy settings because the upgrade preserves these. Record a setting by writing it down or by creating a screen capture and saving the capture to a file. Note: The following steps describe how to record some of the more important settings in the console, for example, settings for user policies and for additional servers and directories that you may have configured. The steps do not describe how to record every setting however. 1. Start WebSphere Application Server, WebSphere Portal, and Lotus Workplace. 2. To start the WebSphere Administrative Console, open a browser and type the following Web address: 3. Click Servers Lotus Workplace Servers. If you edited the default settings Lotus Workplace Server (LotusWorkplace_Server): a. Click LotusWorkplace_Server. b. Record the custom property settings. c. If you customized settings for any of the services running on the server, open the appropriate service configuration pages and record the custom settings. d. If you created one or more new export tasks, click Task Scheduler Service and record the task names and current schedules listed. 4. If there are additional Lotus Workplace servers listed: a. Click the server link for an additional server. b. Click the Status tab, and record which services are listed for the server. This step will help you create the same type of server (using the same template) after the upgrade is complete. c. Record the server properties. d. Click the service configuration pages for the server and record their properties. e. If you created one or more new export tasks for the server, click Task Scheduler Service and record the task names and current schedules. f. Repeat Steps 4a through 4e for each additional server listed. 5. If you configured Additional Searchable Directories, click Lotus Workplace Directories Additional Searchable Directories, open the directory configuration page for each additional directory listed, and record its settings. By default, no additional directories are listed. 5

10 6. If you configured user policies: a. Click Lotus Workplace Users Manage User Policies. b. Open the configuration page for the Default User Policy and record the settings. c. If there are additional user policies listed, open each one and record the settings. 7. If you created mail cells, click Lotus Workplace Directories Directory Settings for Messaging Mail Cells, open each mail cell configuration page, and record the settings. By default, no mail cells are listed. 8. If you created custom archive properties, click Lotus Workplace Archive Custom Properties, open each property configuration page, and record the settings. The following properties are listed by default: DefaultZipMessageArchiveClass, DefaultZipMessageArchivePath, ServiceType1. 9. If you created outbound connections for the SIP proxy, click Lotus Workplace Workplace Applications Team Collaboration Cell-Wide Settings SIP Proxy Outbound Connections, open each connection configuration page, and record the settings. By default, no connections are listed. 10. If you imported new client certificates, click Lotus Workplace Workplace Applications Workplace Client Certificate Store, and then make backup copies of the certificate files so that you can import them again after the upgrade is complete. By default, 22 certificates are listed. 11. If you use Lotus Workplace Messaging, continue to the next procedure, Emptying the message queue. Otherwise, continue to the procedure Preparing the database server. The following XML files contain all the Administrative Console settings. ou will back up these files when you back up the Lotus Workplace 2.0 files, as described in the topic Preparing the Lotus Workplace server. <was_root>\config\cells\{cellname}\lwparchive.xml <was_root>\config\cells\{cellname}\lwpcertstore.xml <was_root>\config\cells\{cellname}\lwpdirsearch.xml <was_root>\config\cells\{cellname}\lwplicense.xml <was_root>\config\cells\{cellname}\lwpmailcell.xml <was_root>\config\cells\{cellname}\lwpspamfilter.xml <was_root>\config\cells\{cellname}\lwp-sync-collabcell.xml <was_root>\config\cells\{cellname}\messaging.xml <was_root>\config\cells\{cellname}\nodes\{nodename}\servers\lotusworkplace_server\lwpcf.xml <was_root>\config\cells\{cellname}\nodes\{nodename}\servers\lotusworkplace_server\lwpscheduler.xml <was_root>\config\cells\{cellname}\nodes\{nodename}\servers\lotusworkplace_server\lwpspamfilter.xml <was_root>\config\cells\{cellname}\nodes\{nodename}\servers\lotusworkplace_server\messaging.xml Step 2a: Emptying the message queue If you use Lotus Workplace Messaging, disable inbound mail and ensure the message queue is empty before you begin the upgrade process. To empty the message queue, first disable inbound mail from servers and clients. Then report the status of the queue and take any manual steps necessary to process pending messages. The message queue normally empties without intervention. Messages in the queue that are in the delivery states of Unprocessed, Delivered, Undeliverable, or Completed are processed and removed from the queue automatically. Messages in the delivery state of Ready are also removed from the queue automatically, except ones that remain in the message state Retry; these Retry messages usually indicate server unavailability and require intervention to resolve the problem. If the LDAP directory server configured for Lotus Workplace becomes unavailable, inbound mail is marked with the delivery state Handler Retry and the message state Unprocessed. Messages in the DeadEnd delivery state are processed and removed automatically if a valid Internet address has been configured on the messaging server to receive the dead messages. Otherwise, you must remove any dead messages manually. 6 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

11 Disabling inbound mail Use the following steps to disable inbound mail on the messaging server. 1. Type the following Web address in a browser to start the WebSphere Administrative Console: 2. Disable inbound mail from Lotus Workplace mail clients: a. Click Lotus Workplace Users Manage User Policies Default User Policy. b. Clear the Allow mail check box. c. Next to Allowed alternate mail clients, clear the POP3 and IMAP check boxes to prevent users from accessing their mail. d. Clear the Allow calendar check box, to prevent users from sending mail from the calendar. e. Next to Allow team spaces, clear the Use and Create check boxes to prevent users from sending mail using team spaces. f. Next to Allow Web conferencing, clear the Attend and Schedule check boxes to prevent users from sending mail from Web conferences. g. Click Apply, and then click OK. h. Repeat Steps 2a through 2g for any additional user policies. 3. Click Servers Lotus Workplace Servers LotusWorkplace_Server SMTP Inbound Service Initial State: Stopped to disable inbound mail from servers and from Internet mail clients. 4. Stop and restart the Lotus Workplace server so the user policy changes take effect. 5. Follow these steps to verify the configuration changes: a. Log in to the server from a browser client and verify that the mail portlet is not visible. b. Attempt a telnet connection to the server on port 25 and verify that the connection fails. 6. Proceed to the topic Reporting the status of the message queue. Reporting the status of the message queue After you disable inbound mail, perform the following steps to report the status of any messages in the message queue. ou can report the status to the server console or to a file; both methods report identical information. ou may want to report to a file if there are many messages in the queue. The two pieces of information most useful in initially evaluating the queue are a message s Message State (third item listed) and Delivery State (last item listed). 1. Start the WebSphere Application Server, WebSphere Portal, and Lotus Workplace. 2. From the <was_root>\bin directory, type one of the following commands to start the Lmadmin tool: Windows lmadmin -user <username> -password <password> -port 8882 AIX and Linux./lmAdmin.sh -user <username> -password <password> -port Confirm that you see a message indicating that the SOAP process is connected to the Lotus Workplace server. If the SOAP process is not connected, see the Lotus Workplace Information Center for more information on running Lmadmin. 4. Choose one of the following methods to generate the report: v To report the status of the message queue to the server console, type: lm mail /report All v To report the status of the message queue to a file created under <was_root>, type: lm querycell -qreport <filename> 5. Proceed to the step Expediting pending mail. Chapter 2. Performing Pre-upgrade Steps 7

12 Expediting pending mail If messages remain in the pending queue for a period of time, the cause is usually an unavailable local domain smart host server or relay server, or an unavailable LDAP directory server. Perform the following steps to identify messages such as these in a report of the message queue, to resolve the server problem, and to resend the pending messages. 1. Look for messages in the queue marked with the delivery state Ready and the message state Retry. 2. If you find messages in these states, look at the recipient lists to determine the recipient domain and the server that is unavailable, and resolve the server availability problem. For example, if a recipient is in the local domain, it is likely that the local domain smart host server is unavailable. 3. Look for messages marked with the delivery state Handler Retry and the message state Unprocessed, which indicate that the LDAP directory server configured for Lotus Workplace is unavailable. Resolve the server availability problem. 4. After all servers are available, wait for the next scheduled retry of the pending messages to send the messages and remove them from the queue. Or use the following steps to force a retry of each pending message: a. Type the following Lmadmin command to list the IDs of the pending messages: lm mail getpendingmessages b. Copy the ID of a pending message in the list to the clipboard. c. Type the following command to retry sending the pending message with the copied ID: lm mail sendpendingmessage <id> where <id> is the message ID pasted from the clipboard. d. Repeat Steps 4b and 4c for each pending message. 5. Proceed to the step Removing dead messages. Removing dead messages Dead messages are marked in the message queue with message state Dead and the delivery state DeadEnd. 1. Type the following command to delete any dead messages: lm mail /reapdeadmessages Proceed to the topic Deleting orphaned mail accounts. Step 2b: Deleting orphaned mail accounts Follow these steps to delete any orphaned mail accounts from the messaging database. An orphaned account is one that is missing a corresponding user entry in the LDAP directory. Large numbers of orphaned accounts may have an impact on the time required to back up the Lotus Workplace 2.0 databases. However, if you have difficulty deleting an orphaned account, you can leave it. 1. Type the following Lmadmin command to list any orphaned accounts and their associated external IDs: lm listaccounts /orphan 2. For each orphaned account listed: a. Copy its external ID from the list to the clipboard. b. Type the following command to delete the account: lm deleteaccounts -externalid <id> where <id> is the external ID pasted from the clipboard. For example: lm deleteaccounts -externalid F24F53BBCDE0D1CE323ALF Proceed to the topic, Preparing the database server. 8 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

13 Step 3: Preparing the database server After you have emptied the message queue and deleted orphaned accounts, follow these steps to prepare the database server. 1. Stop Lotus Workplace, WebSphere Portal, and WebSphere Application Server. 2. Log into the database server as db2admin. 3. Stop and then restart the database server and its services. For example, type these commands from a command window: db2 db2stop force db2 db2start 4. Verify that no application is connected to the database server. For example, type the following commands from a command window: db2 force applications all db2 terminate 5. Perform the following steps to ensure that the indexer is in a functional state so that it will work after the upgrade: a. Type the following command to connect to the wpcp50 database: db2 connect to wpcp50 b. Type the following command to determine the state of the indexer: db2 select state from cmjobs where projectid= 1 c. If the state that is output in the preceding step is 2, the indexer is functional. If the state that is output is any other value, the indexer is not functional and you must reset it. To reset the indexer, type the following command: db2 update cmjobs set state=2 where projectid= 1 6. Perform the following steps to ensure that there are no duplicate IDs in the indexer queue; duplicate IDs will prevent the indexer from working after the upgrade: a. Type the following command to list the projects in the indexer queue table by ID: db2 select id,projectid from projectsearchindex order by id b. Look for duplicate IDs in the list that is output. Duplicate IDs will be listed together. If you see a duplicate ID, type the following command to clear the indexer queue so that the indexer will work after the upgrade: db2 delete from projectsearchindex Note: Project data cleared from the indexer queue is not indexed until new data is added to the project and the queue. 7. Make backup copies of the WebSphere Portal databases (wps50 and wpcp50) and the Lotus Workplace databases (lwpcom, lwplds, lwplms, lwparc, and nagano). The lwplds and lwplms databases exist only if you installed Lotus Workplace Collaborative Learning. For example, enter these commands from a command window db2 backup database LWPARC to <path name> db2 backup database LWPLDS to <path name> db2 backup database LWPLMS to <path name> db2 backup database LWPCOM to <path name> db2 backup database NAGANO to <path name> db2 backup database WPCP50 to <path name> db2 backup database WPS50 to <path name> where <path name> Chapter 2. Performing Pre-upgrade Steps 9

14 is the path name for the database backups, for example: D:\db2backups\lwp20 Note: Also back up the fdbk50 database if it exists on your system. 8. Drop the original WebSphere Portal and Lotus Workplace 2.0 databases. For example, to drop the lwparc database, type these commands from a command window: db2 terminate db2 force applications all db2 drop database lwparc 9. Continue to the step, Preparing the Lotus Workplace server. Note: Do not uninstall DB2. Step 4: Preparing the Lotus Workplace server After you have completed the procedure Preparing the database server, follow these steps on the Lotus Workplace server to make backup copies of the Lotus Workplace 2.0 files, and then to uninstall Lotus Workplace and its related products. Note: Do not uninstall DB2. 1. Stop the HTTP server if it is running. 2. Back up all the folders in the <was_root>\wpcp\config\websphere_portal\author\indexes\ directory. The names of the folders are numbers, and they contain built search indexes for applications. After the upgrade is complete, you will need to copy all of these folders back to the same directory location on the server to ensure that users can search for applications. 3. Back up the following files so that you can refer to them as you install and set up version 2.0.1: v v <wp_root>\config\wpconfig.properties <lwp_root>\config\lwpprops.properties ou can refer to the wpconfig.properties file to determine which properties to specify when you enable directory security on the WebSphere Portal server. ou can refer to the lwpprops.properties file to determine properties to specify when you run Lotus Workplace configuration scripts. 4. Back up the WebSphere Application Server installation directory, for example, C:\WebSphere, and all of its subdirectories. 5. Back up the IBM HTTP Server directory, for example, C:\IBMHttpServer, and any subdirectories, if the IBM HTTP Server is installed 6. Back up the vpd.properties file, which is located in one of these directories: AIX /usr/lib/objrepos Linux The home directory of the root user: /root Windows c:\winnt 7. Back up the workplace.properties file, which is located in one of these directories: Note: The workplace.properties file may not exist on all deployments. AIX /usr/lib/objrepos Linux The home directory of the root user: /root 10 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

15 Windows c:\documents and Settings Note: The vpd.properties file and workplace.properties file identify installed components at the time of backup and are required should you need to restore the version 2.0 installation. 8. Record the path names for the WebSphere Application Server directory and subdirectories; when you install the Lotus Workplace product software, you must specify the same path names. 9. If you installed the rich client provisioning components on the server, uninstall them. See the Lotus Workplace Installation section of the Lotus Workplace Information Center for instructions. 10. Uninstall Lotus Workplace. See the Lotus Workplace Installation section of the Lotus Workplace Information Center for instructions. 11. Uninstall WebSphere Portal. Note: ou may receive a failure message at the end of the uninstall process. Continue to Step 11, regardless if you see this message. 12. Uninstall WebSphere Application Server. 13. Uninstall IBM HTTP Server, if it is installed. 14. Delete the following files, which are not automatically uninstalled: v The WebSphere Application Server installation directory, for example, C:\WebSphere. v The IBM HTTP Server directory, for example, C:\IBMHttpServer, if it exists. v The vpd.properties file. v Registry entries that contain the text WebSphere Portal or Lotus Workplace. 15. Continue to the chapter Performing the Upgrade. Chapter 2. Performing Pre-upgrade Steps 11

16 12 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

17 Chapter 3. Performing the Upgrade This chapter describes the steps you take to perform the upgrade. Performing the upgrade After you have completed the pre-upgrade steps described in the chapter Performing Pre-upgrade Steps, complete the following steps to perform the upgrade. 1. Read the Lotus Workplace Release Notes. 2. Install and set up Lotus Workplace products. 3. Verify the Lotus Workplace functionality. 4. Restore Lotus Workplace 2.0 data. 5. Configure the Team Tasks, Chat, and Chat Room portlets. 6. Re-create custom Administrative Console settings. 7. Upgrade the rich client software. 8. Verify the upgrade. Step 1 Reading the release notes Read the Lotus Workplace Release Notes to learn about important installation and configuration known issues and workarounds. These release notes are available on the Web at Step 2: Installing and setting up Lotus Workplace products After you have read the Lotus Workplace Release Notes, install and set up Lotus Workplace products. For instructions, see the installation section of the Lotus Workplace Information Center, available on the Web at Skip the steps that describe how to install DB2, which remains installed from the Lotus Workplace 2.0 deployment. However complete all other documented required installation and setup steps, including installing and configuring WebSphere Portal. Keep the following points in mind: v As part of the WebSphere Portal configuration done prior to the Lotus Workplace product installation, you must configure WebSphere Portal to use DB2. For more information, see the Database section of the WebSphere Portal Information Center at v Select the same installation directory path names for WebSphere Application Server, WebSphere Portal, and Lotus Workplace that you selected for Lotus Workplace 2.0. Also select the same Lotus Workplace data and backup directory path names. v Use the same DB2 server, LDAP server version and directory, and HTTP server that you used for Lotus Workplace 2.0. v Use the same type of deployment that you used for Lotus Workplace 2.0. If you used a single-server deployment for version 2.0, use that type for version 2.0.1; if you used a two-server pilot deployment for version 2.0, use that type for version v When you configure the LDAP directory and security for WebSphere Portal, you can refer to the backup copy of the version 2.0 wpconfig.properties file to determine values to specify. Similarly, when you edit the lwpprops.properties file to prepare to run Lotus Workplace configuration scripts, you can refer to the version 2.0 backup copy of that file. 13

18 Note: Do not use file replace to replace the newly installed versions of the wpconfig.properties and lwpprops.properties files with the 2.0 versions. Use the 2.0 versions as a reference only. v To install and configure the rich client provisioning server, follow the instructions in the Lotus Workplace Information Center after you have completed installation and configuration of the Lotus Workplace server. Do not install the rich client software at this point though. When you have finished installing and setting up the Lotus Workplace products, continue to the next step, Verifying the Lotus Workplace functionality. Step 3: Verifying the Lotus Workplace functionality After you have installed and set up Lotus Workplace 2.0.1, start all servers and verify that the installed components are working properly. Troubleshoot and fix any problems before continuing to the next step. Step 4: Restoring the Lotus Workplace 2.0 data After you verify the Lotus Workplace functionality, follow these steps to restore the Lotus Workplace 2.0 data. 1. Stop Lotus Workplace, WebSphere Portal, and WebSphere Application Server. 2. Log into the database server as db2admin. 3. Stop and then restart the database server and its services. For example, type these commands from a command window: db2 db2stop force db2 db2start 4. Verify that no application is connected to the database server. For example, type these commands from a command window: db2 force applications all db2 terminate 5. Make backup copies of the WebSphere Portal databases (wps50 and wpcp50) and the Lotus Workplace databases (lwpcom, lwplds, lwplms, lwparc, and nagano) created for Lotus Workplace Follow similar steps as the ones you followed in the chapter Performing Pre-upgrade Steps to back up the version 2.0 databases; be sure to specify a different backup location for the version databases. 6. Make backup copies of the Lotus Workplace installation directories and files, following steps similar to the ones you followed in the chapter Performing Pre-upgrade Steps to back up the version 2.0 installation directories. 7. Perform the following steps on the Lotus Workplace server to export data from the WEB_MOD table in the WPS50 database to the <wp_root>\config\ directory: a. Extract the contents of the C81H6ML.zip file to the <wp_root>\config directory. This file is available from the Lotus Support Services Web site, in document number titled IBM Lotus Workplace 2.0 to upgrade V1 for Windows, AIX, Linux at b. With a text editor, open one of the following files that have been extracted to the <wp_root>\config directory: Windows lwp_migrate.bat AIX or Linux: lwp_migrate.sh 14 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

19 c. Verify that the WAS_HOME and SQL_LIB path names in the lwp_migrate.bat file (Windows) or lwp_migrate.sh file (AIX or Linux) reflect the correct path names for your system. Make any necessary changes, and then save the file. Example path names are: Windows (lwp_migrate.bat) set WAS_HOME=c:\WebSphere\AppServer\ set SQL_LIB="c:\Program Files\IBM\SQLLIB\java\db2java.zip AIX (lwp_migrate.sh) export WAS_HOME= /usr/websphere/appserver export SQL_LIB= /home/db2admin/sqllib/java/db2java.zip Note: The default WAS_HOME path name specified in the lwp_migrate.sh file is the Linux default path name; for AIX, you must change the path name to conform to the AIX convention. Linux (lwp_migrate.sh) export WAS_HOME= /opt/websphere/appserver export SQL_LIB= /home/db2admin/sqllib/java/db2java.zip d. If the database server is remote, start the DB2 Administration Client. e. From the <wp_root>\config\ directory, enter the following command: Windows lwp_migrate.bat -export AIX and Linux./lwp_migrate.sh -export 8. Drop all of the version WebSphere Portal and Lotus Workplace databases. For example, to drop the lwparc database, type these commands from a command window: db2 terminate db2 force applications all db2 drop database lwparc 9. On the database server, type the following commands from a command window to stop and then restart the database server and its services: db2 db2stop force db2 db2start 10. On the database server, type the following commands from a command window to restore the Lotus Workplace 2.0 databases that you backed up prior to installing the Lotus Workplace products, and then stop and restart the database server. Note: Alternatively, use the DB2 Control Center to restore the databases. db2 restore database LWPARC from <path name> without rolling forward without prompting db2 restore database LWPLDS from <path name> without prompting db2 restore database LWPLMS from <path name> without prompting db2 restore database LWPCOM from <path name> without rolling forward without prompting db2 restore database NAGANO from <path name> without rolling forward without prompting db2 restore database WPCP50 from <path name> without prompting db2 restore database WPS50 from <path name> without prompting db2 db2stop force db2 db2start where <path name> is the path name for the Lotus Workplace 2.0 databases backed up previously, for example D:\db2backups\lwp20. Chapter 3. Performing the Upgrade 15

20 Note: Also restore the fdbk50 database if you backed it up previously. 11. On the Lotus Workplace server, enter the following commands from the <wp_root>\config\ directory to run Portal Data Management (PDM) update scripts. Windows wpsconfig action-add-search-index-table wpsconfig action-wpcp-add-id-lwp20 wpsconfig action-fix-psi wpsconfig action-delete-index-503 wpsconfig action-add-sidr-table-lwp20 wpsconfig action-add-wpcpguid wpsconfig action-update-wpcpguid AIX and Linux./WPSconfig.sh action-add-search-index-table./wpsconfig.sh action-wpcp-add-id-lwp20./wpsconfig.sh action-fix-psi./wpsconfig.sh action-delete-index-503./wpsconfig.sh action-add-sidr-table-lwp20./wpsconfig.sh action-add-wpcpguid./wpsconfig.sh action-update-wpcpguid 12. On the database server type the following commands from a command window to add the wpcpguid column to the schema of the DiscussionResource and TT_TASKS tables: db2 "connect to wpcp50" db2 "update command options using c OFF v ON" db2 "RENAME TABLE DISCUSSIONRESOURCE TO dr_noguid" db2 "create view dr_guid as select m.wpcpguid,dr.* from dr_noguid dr inner join DISCUSSIONRES_M m on (dr.uri=m.uri)" db2 "CREATE TABLE DISCUSSIONRESOURCE LIKE dr_guid NOT logged initially" db2 "INSERT INTO DISCUSSIONRESOURCE SELECT * FROM dr_guid" db2 "COMMIT" db2 "runstats on table db2admin.discussionresource with distribution and detailed indexes all" db2 "RENAME TABLE TT_TASKS TO tt_noguid" db2 "create view tt_guid as select m.wpcpguid,tt.* from tt_noguid tt inner join TT_TASKS_M m on (tt.tt_id=m.tt_id)" db2 "CREATE TABLE TT_TASKS LIKE tt_guid NOT logged initially" db2 "INSERT INTO TT_TASKS SELECT * FROM tt_guid" db2 "COMMIT" db2 "runstats on table db2admin.tt_tasks with distribution and detailed indexes all" 13. From the <wp_root>\config\ directory on the Lotus Workplaces server, enter the following command to use the data exported in Step 7 to update the WEB_MOD table in the WPS50 database: Windows lwp_migrate.bat -import AIX and Linux./lwp_migrate.sh -import 14. Perform the following steps on the Lotus Workplace server to fix the context root: a. Make a backup copy of the <wp_root>\config\actions\wps_cfg.xml file. b. With a text editor, open the <wp_root>\config\actions\wps_cfg.xml file. c. Find the target action-update-portlets and comment out the Update Portlets section, so that only Export Portlets remains enabled. The edited target should look like the following example. The comment section is enclosed by <!-- and -->. <target name="action-update-portlets" depends="stop-portal-server,start-portal-server"> 16 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

21 <!-- --> </target> <echo message=""/> <echo message="export Portlets"/> <xmlaccess user="${portaladminidshort}" password="${portaladminpwd}" url=" srcfile="${wpsinstalllocation}/config/work/exportallportlets.xml" destfile="${wpsinstalllocation}/config/work/allportlets.xml" /> <echo message=""/> <echo message="update Portlets"/> <xmlaccess user="${portaladminidshort}" password="${portaladminpwd}" url=" srcfile="${wpsinstalllocation}/config/work/allportlets.xml"/> <antcall target="action-update-wpcp-context-authorportlets"/> d. Save the edited wps_cfg.xml file. e. Enter one of the following commands: Windows wpsconfig.bat action-update-portlets AIX and Linux./WPSconfig.sh action-update-portlets f. Make a backup copy of the <wp_root>\config\work\allportlets.xml file. g. Use a text editor to open the <wp_root>\config\work\allportlets.xml file. h. Remove all <web-app> elements from the AllPortlets.xml file that contain the text installedapps in the <url> element. To remove a <web-app> element, select all text from <web-app> through </web-app> and delete the text. Each <web-app> element can span multiple screens, and there are many <web-app> elements. Here is an example of a <web-app> element that would be deleted; the example does not show all the lines in the element: <web-app action="update" active="true" objectid="_1_0830mmn6tf0eh60c_ch" removable="true" uid="dce:08e02e80-c5ae fe94b6010:1"> <url>file://localhost/$server_root$/installableapps//d:/websph~1/ APPSER~1/installedApps/pflpas/A_LWP_Infrastructure.ear/ lwppeoplefinder.war</url><access-control externalized="false" owner="undefined" private="false"/> </portlet-app> </web-app> Note: Complete this step carefully to avoid errors. Review the modified file before continuing to the next step. Chapter 3. Performing the Upgrade 17

22 Tip: Use an XML editor to help you select and delete elements. Search for the text installedapps to help locate the elements to be deleted. This text is found in the <url> element near the top of the <web-app> element.. i. Remove the <web_app> section that contains the text installableapps/spellcheckerservice.war in its <url> line to avoid an OutOfMemory exception. j. Save the edited AllPortlets.xml file. k. Use a text editor to open the file <wp_root>\config\actions\wps_cfg.xml. l. Find the target action-update-portlets, comment out the Export Portlets section, and leave only the Update Portlets section enabled. The edited target should look like the following example. The comment section is enclosed by <!-- and -->. <target name="action-update-portlets" depends="stop-portal-server,start-portal-server"> <!-- --> <echo message=""/> <echo message="export Portlets"/> <xmlaccess user="${portaladminidshort}" password="${portaladminpwd}" url=" srcfile="${wpsinstalllocation}/config/work/exportallportlets.xml" destfile="${wpsinstalllocation}/config/work/allportlets.xml" /> <echo message=""/> <echo message="update Portlets"/> <xmlaccess user="${portaladminidshort}" password="${portaladminpwd}" url=" srcfile="${wpsinstalllocation}/config/work/allportlets.xml"/> <antcall target="action-update-wpcp-context-authorportlets"/> </target> m. Save the edited wps_cfg.xml. n. Enter one of the following commands: Windows wpsconfig.bat action-update-portlets AIX and Linux./WPSconfig.sh action-update-portlets Note: If you see the following warning or a similar one after a BUILD SUCCESSFUL message, you can ignore the warning. com.ibm.wps.command.xml.xmlcommandexception: XMLC0060W: A user or group with ID cn=wpcpusers,o=default organization could not be retrieved from the portal datastore, possibly because it does not exist. Related access-control configuration data will not be updated. [portlet _3_0G0ALLBDVB0C1JIH_3K name=resource View] 15. On the Lotus Workplace server, stop any servers that are running, and then delete all the files in the <was_root>\wstemp\ directory to remove pre-compiled jsp files. Do not delete the directory, only the contents. 16. To ensure that users can search for applications, copy the version 2.0 search index folders that you backed up prior to the upgrade, to the 18 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

23 <was_root>\wpcp\config\websphere_portal\author\indexes\ directory of the version installation. Replace the versions of the folders with the 2.0 versions. 17. Start WebSphere Application Server, WebSphere Portal, and Lotus Workplace. 18. Start the HTTP server. 19. If you installed the rich client provisioning server, instruct users not to use the rich client yet. They should use the rich client only after uninstalling the 2.0 version of the rich client and then installing the version, as described later in this chapter. 20. Continue to the procedure Configuring the Team Tasks, Chat, and Chat Room portlets. Step 5: Configuring the Team Tasks, Chat, and Chat Room portlets After you have restored the Lotus Workplace 2.0 data, follow these steps to configure the Team Tasks, Chat, and Chat Room portlets to work with Lotus Workplace From a browser, sign in to the Lotus Workplace server using a name with administrative rights. 2. Click Administration at the top of the page to open the Lotus Workplace Administration page. 3. Click Portlets Manage Portlets. 4. Configure the Team Tasks portlet: a. In the Portlets box, drag the mouse to select Team Tasks, and then click Modify parameters. b. Click the check box next to FilterChain (which contains the value StrutsTranscoding), and then click the trash can icon to delete the parameter. c. Click Save. 5. Configure the Chat portlet: a. Click Portlets Manage Portlets b. In the Portlets box, drag the mouse to select Chat Portlet, and then click Modify parameters. c. Click the check box next to FilterChain (which contains the value StrutsTranscoding), and then click the trash can icon to delete the parameter. d. Click Save. Note: Ignore this step if you do not see the StrutsTranscoding parameter for the Chat portlet. 6. Configure the Chat Room portlet: a. Click Portlets Manage Portlets b. In the Portlets box, drag the mouse to select Chat Room, and then click Modify parameters. c. Click the check box next to FilterChain (which contains the value StrutsTranscoding), and then click the trash can icon to delete the parameter. d. Click Save. 7. Stop and then start the WebSphere Portal. 8. Continue to the procedure Re-creating custom Administrative Console Settings. Step 6: Re-creating Administrative Console settings Perform the following steps to re-create Lotus Workplace 2.0 Administrative Console settings that you recorded before the upgrade. 1. Start the newly installed WebSphere Application Server, WebSphere Portal Server, and Lotus Workplace server. 2. Type the following Web address in a browser to start the WebSphere Administrative Console: 3. Follow the steps in the topic Re-creating Lotus Workplace Server settings. 4. Follow the steps in the topic Re-creating Additional Searchable Directories settings. Chapter 3. Performing the Upgrade 19

24 5. Follow the steps in the topic Re-creating user policy settings. 6. Follow the steps in the topic Re-creating mail cells. 7. Follow the steps in the topic Re-creating archive properties. 8. Follow the steps in the topic Re-creating outbound connections for the SIP proxy. 9. Follow the steps in the topic Reimporting client certificates. 10. Re-create any other custom settings omitted from the preceding steps, clicking Save and Save again when done editing each. Refer to the Administrative Console XML files saved before the upgrade, and to the next topic Administrative Console page reference. 11. Click Logout to exit the Administrative Console. 12. Re-start the WebSphere Application Server, WebSphere Portal Server, Lotus Workplace server, and any additional Lotus Workplace servers you created, for the changes to take effect. Administrative Console page reference The following tables list the paths to each page in the Administrative Console in Lotus Workplace Administrative Console page Servers > Lotus Workplace Servers > Services tab N Servers > Lotus Workplace Servers > Servers tab N Servers > Lotus Workplace Servers > Servers tab > New (Step 1) Servers > Lotus Workplace Servers > Servers tab > New (Step 2) Servers > Lotus Workplace Servers > Servers tab > Delete N Servers > Lotus Workplace Servers > Servers tab > {server name} > Status tab N Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > General Mail Server > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > IMAP > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > IMAP > Runtime tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Message Handler > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > POP3 > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > POP3 > Runtime tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > SMTP Inbound > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > SMTP Inbound > Runtime tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > SMTP Outbound > Configuration tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > SMTP Outbound > Runtime tab Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler Contains configuration settings? N N N N N 20 Lotus Workplace Upgrade Guide: Version 2.0 to 2.0.1

25 Administrative Console page Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Configure Task Scheduler Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > New Export Task Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Administrator Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Archive Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Attachment Cleanup Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Compact Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Export Default Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > PKI Request Processor Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Quota Manager Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Reconcile Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Reconcile Archive Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Trash Collector Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Update Overdue Team Tasks Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Task Scheduler > Workplace Information Collector Servers > Lotus Workplace Servers > Servers tab > {server name} > Configuration tab > Team Collaboration > Configuration tab Contains configuration settings? Administrative console page Lotus Workplace > Licenses Lotus Workplace > Directories N Lotus Workplace > Directories > Directory Settings for Searching Lotus Workplace > Directories > Directory Settings for Messaging Lotus Workplace > Directories > Directory Settings for Messaging > Mail Cells N Lotus Workplace > Directories > Directory Settings for Messaging > Mail Cells > New Lotus Workplace > Directories > Directory Settings for Messaging > Mail Cells > Edit Lotus Workplace > Directories > Directory Settings for Messaging > Mail Cells > Delete N Lotus Workplace > Directories > Additional Searchable Directories N Lotus Workplace > Directories > Additional Searchable Directories > New Lotus Workplace > Directories > Additional Searchable Directories > Edit Contains configuration settings? Chapter 3. Performing the Upgrade 21