Installation and Upgrade Guide

Installation and Upgrade Guide
IBM Workplace Collaboration Services
Installation and Upgrade Guide
Version 2.5
G210-1961-00
IBM Workplace Collaboration Services
Installation and Upgrade Guide
Version 2.5
G210-1961-00
Note
Before using this information and the product it supports, read the information in “Notices” on page 417.
First Edition (May 16, 2005)
This edition applies to version 2.5 of IBM Workplace Collaboration Services (product number L-KBIM-64NQA7) and
to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2002, 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1 Planning a deployment. . . . 1
Installation and upgrade . . . . . . . . . . 1
Phase 1: Planning an IBM Workplace deployment . . 1
Release Notes available . . . . . . . . . . 2
Requirements for AIX, Linux, Solaris, and
Windows . . . . . . . . . . . . . . 2
Requirements for i5/OS . . . . . . . . . 9
Installation overview . . . . . . . . . . 16
Administrator names and passwords worksheet 22
Pre-installation checklist . . . . . . . . . 29
Installation scenarios . . . . . . . . . . 30
Chapter 2 Preparing the Environment
45
Setting up a Network Deployment environment .
Setting up a Network Deployment environment
Setting up an i5/OS environment . . . . .
Setting up a Database Management System . .
Preparing an external HTTP server . . . .
. 45
45
. 54
. 57
. 65
Chapter 3 Installing IBM Workplace
Collaboration Services . . . . . . . . 71
Phase 3: Installing IBM Workplace Collaboration
Services . . . . . . . . . . . . . .
Preparing to run the installation program . .
Installing on a single server . . . . . . .
Installing on network nodes . . . . . . .
Installing on the Deployment Manager . . .
Other ways to install IBM Workplace
Collaboration Services . . . . . . . .
Configuring IBM Workplace Collaboration
Services . . . . . . . . . . . . .
Starting and stopping IBM Workplace
Collaboration Services servers . . . . . .
Uninstalling IBM Workplace Collaboration
Services . . . . . . . . . . . . .
. 71
. 71
. 72
. 90
. 101
. 206
. 245
Chapter 6 Completing Setup of an
External HTTP Server . . . . . . . . 261
Phase 6: Completing setup of an external HTTP
server . . . . . . . . . . . . . . .
External HTTP server checklist . . . . .
Accessing IBM Workplace Collaboration
Services through an external HTTP server . .
. 261
. 261
. 283
Chapter 7 Completing IBM Workplace
Collaborative Learning Setup . . . . 285
Phase 7: Completing IBM Workplace Collaborative
Learning Setup . . . . . . . . . . . . .
Granting Learning access to the WebSphere
Portal administrator . . . . . . . . . .
Connecting Learning portlets to a remote
Learning Server . . . . . . . . . . .
Setting up access control for IBM Workplace
Collaborative Learning portlets . . . . . .
Enabling reporting on AIX, Linux, Solaris, and
i5/OS . . . . . . . . . . . . . . .
Configuring Learning administrator help on
AIX, Linux, Solaris, and Windows . . . . .
Configuring Learning administrator help on
i5/OS . . . . . . . . . . . . . . .
285
286
286
287
288
292
292
. 123
. 130
. 137
. 138
Chapter 4 Connecting to an LDAP
Directory Server . . . . . . . . . . 141
Phase 4: Connecting to an LDAP directory server
Connecting to an LDAP directory in a Network
Deployment . . . . . . . . . . . . .
Connecting to IBM Tivoli Directory Server . .
Connecting to Domino Directory . . . . . .
Connecting to Active Directory . . . . . .
Connecting to Sun Java System Directory Server
Connecting to Novell eDirectory . . . . . .
141
142
142
153
167
178
188
Chapter 5 Connecting to a DBMS
Server . . . . . . . . . . . . . . 201
Phase 5: Connecting to a DBMS server . . . . . 201
About the Workplace Collaboration Services
database . . . . . . . . . . . . . . 201
Creating the Workplace Collaboration Services
database . . . . . . . . . . . . . . 202
© Copyright IBM Corp. 2002, 2005
Transferring data to another DBMS . . . .
Connecting Network Deployment nodes to a
remote database . . . . . . . . . .
Chapter 8 Rich Client Installation and
Configuration . . . . . . . . . . . 295
Phase 8: Rich client installation and configuration
IBM Workplace rich client installation and
configuration checklist . . . . . . . . .
Installing and configuring the provisioning
server . . . . . . . . . . . . . . .
Configuring for optimal rich client performance
Setting rich client installation program defaults
Installing the IBM Workplace rich client . . .
Upgrading rich client capabilities . . . . . .
Updating IBM Workplace rich clients using IBM
WebSphere Everyplace Device Manager . . .
Uninstalling the rich client on the user desktop
Uninstalling the rich client provisioning server
Changing the search bar appearance. . . . .
295
295
298
313
323
326
328
329
332
333
335
Chapter 9 Completing the Network
Deployment Setup . . . . . . . . . 337
Phase 9: Completing Network Deployment setup
Updating the WebSphere Portal EAR file for
Network Deployment . . . . . . . . .
Federating and clustering network nodes . . .
Configuring load balancing for SIP services and
HTTP . . . . . . . . . . . . . . .
337
337
340
350
iii
Updating rich client configuration files for
Network Deployment . . . . . . . . .
Enabling dynamic caching . . . . . . . .
Enabling Search in the cluster . . . . . . .
Enabling Messaging in the cluster . . . . .
Editing WebSphere settings for a Network
Deployment . . . . . . . . . . . . .
Applying fix packs to the Network Deployment
servers . . . . . . . . . . . . . .
354
356
357
358
359
360
Appendix A Upgrading from Lotus
Workplace 2.01. . . . . . . . . . . 361
Lotus Workplace 2.0.1 upgrade . . . . . . .
Lotus Workplace 2.0.1 data migration . . . .
Upgrading to IBM Workplace Collaboration
Services (single server) . . . . . . . . . .
Preparing to upgrade . . . . . . . . . .
Running the installation program for a
single-server deployment . . . . . . . .
Completing an upgrade . . . . . . . . .
Upgrading a Network Deployment . . . . . .
Creating shared directories for a Network
Deployment upgrade . . . . . . . . . .
Installing a new Deployment Manager . . . .
Installing the HTTP server . . . . . . . .
Upgrading the first node (Node 1) . . . . .
Copying Node 1 cell level configuration to the
Deployment Manager . . . . . . . . .
Creating a new IBM WebSphere Portal cluster
Updating the Deployment Manager with cluster
information . . . . . . . . . . . . .
Installing IBM Workplace Collaboration Services
on an additional node . . . . . . . . .
Configuring the HTTP server . . . . . . .
iv
Installation and Upgrade Guide
361
362
365
365
374
375
376
377
378
384
385
386
387
388
389
394
Enabling dynamic caching . . . . . . . .
Distributing Embedded Messaging files . . .
Modifying properties files . . . . . . . .
Removing JDBC provider configuration from
node configuration . . . . . . . . . .
Modifying the messaging queue file store
location . . . . . . . . . . . . . .
Modifying cell-level URL providers to point to
the remote HTTP server . . . . . . . . .
Mapping the Mail module to Mail servers . . .
Applying fix packs to the Network Deployment
servers . . . . . . . . . . . . . .
395
396
396
397
397
397
398
398
Appendix B Completing Optional
Post-installation Tasks . . . . . . . 399
Optional post-installation tasks . . . . . .
Customizing attributes . . . . . . . .
Multiple LDAP directories . . . . . . .
Changing the LDAP host name or port number
after configuration . . . . . . . . . .
Changing the installed context root . . . .
Appendix C Reference Information
Reference information . . . .
Root installation directories . .
Installation logs . . . . .
Installed folders . . . . .
Port assignments on IBM i5/OS
Related product information .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 399
. 399
. 403
. 403
. 404
407
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
407
407
408
409
411
413
Notices . . . . . . . . . . . . . . 417
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 418
Chapter 1 Planning a deployment
This chapter provides information for planning the installation of IBM®
Workplace™ Collaboration Services.
Installation and upgrade
To prepare for installation, read this topic and its related topics before you start the
installation program. Also review the requirements for information on hardware
and software requirements, supported hardware and software versions, and
capacity planning.
Use the installation program to install the IBM Workplace Collaboration Services
products. The installation program also installs some of the other required software
components; others you must install separately, using the vendor’s documentation.
Also use the installation program to upgrade from a previous release.
For more information about upgrading, see ″Appendix A: Alternative installation
methods.″
Use the IBM Workplace Collaboration Services rich client provisioning server
installation program to install a downloadable copy of the rich client where users
can access it.
Related concepts
Requirements for AIX, Linux, Solaris, and Windows
Requirements for i5/OS
Phase 1: Planning the installation
Upgrading from Lotus Workplace 2.0.1
Related tasks
Installing and configuring the provisioning server
Phase 1: Planning an IBM Workplace deployment
Planning is crucial. The decisions you make when initially installing IBM
Workplace Collaboration Services might be difficult, or impossible, to change after
the system is in use. It is important to understand what is involved in deploying
Workplace Collaboration Services might and its related components, and to
complete installation tasks in the proper sequence.
Before you install Workplace Collaboration Services, consider the number of people
who will use it, the amount of data you expect to manage, the types of servers you
will be hosting the product on, and the third-party components you plan to use
with Workplace Collaboration Services. You must make a series of decisions
regarding components and configuration, including (but not limited to):
v Will this be a pilot installation, or will it be used in a networked environment?
v Will you use an LDAP directory to store user records?
v Which DBMS will you use for storing Workplace Collaboration Services data?
v Will you use an external HTTP server rather than the built-in one that comes
with Workplace Collaboration Services?
© Copyright IBM Corp. 2002, 2005
1
Sometimes, the answer to one question affects the answer to another. For example,
while the default Cloudscape™ database management system (DBMS) may be a
good choice for a demonstration server, it is not sufficiently robust for use in a
production environment. If you answer the first question with ″networked
environment,″ you should not answer the third question with ″Cloudscape.″
The topics in this section provide an overview of Workplace Collaboration Services
installation that explains the sequence of operations, describes the tasks you will
need to perform, and supplies a worksheet and a checklist to help you prepare for
installation.
Release Notes available
For the latest information on installing and configuring IBM Workplace
Collaboration Services, see the Release Notes. You can access the Release Notes by
pointing your browser at the following Web address and clicking the appropriate
link for Product documentation by version:
http://www-10.lotus.com/ldd/notesua.nsf/find/workplace
Requirements for AIX, Linux, Solaris, and Windows
This topic describes requirements for running IBM Workplace Collaboration
Services on IBM AIX®, Linux®, Sun Solaris, and Microsoft® Windows® servers.
Unless specified otherwise, the requirements in this topic also apply to the
individual IBM Workplace collaboration products, including IBM Workplace
Messaging™, IBM Workplace Team Collaboration, IBM Workplace Documents, and
IBM Workplace Collaborative Learning. Also note:
v Any information that specifically addresses the messaging capabilities of IBM
Workplace Collaboration Services also applies to IBM Workplace Messaging.
v Any information that specifically addresses the collaborative learning capabilities
of IBM Workplace Collaboration Services also applies to IBM Workplace
Collaborative Learning.
v Any information that specifically addresses the web content management
capabilities of IBM Workplace Collaboration Services also applies to IBM
Workplace Web Content Management.
This topic contains the following requirements:
v Installation program
v Server hardware
v Network connectivity
v Server software and operating system
v Rich client hardware and software
v Client software and operating system
This requirements information may be updated periodically on the Web. For the
latest information, see the Release Notes for Workplace Collaboration Services at
http://www.lotus.com/ldd/notesua.nsf.
Note: For the system requirements for the web content management capabilities of
IBM Workplace Collaboration Services, see ″System Requirements: IBM
Workplace Web Content Management″ at
http://www.lotus.com/products/product5.nsf/wdocs/lwwcmsysreq.
2
Installation and Upgrade Guide
Installation program requirements
(AIX and Solaris) The Workplace Collaboration Services installation program uses
the GNU tar archiver to extract files during installation. Before running the
installation program on AIX or Solaris, you must install GNU tar, version 1.14 or
later. The GNU tar can be downloaded from the Free Software Directory on
www.gnu.org. It must be installed as the default tar utility on the path (the default
install location for GNU tar is /usr/local/bin). To verify the version number of the
default tar utility, use the command ″tar --version″ (typed with two hyphens, not a
dash). If the default tar utility is not the latest version, upgrade to version 1.14 or
later.
Server hardware requirements
This section describes the server hardware requirements.
Server processor and memory requirements
The following table lists the minimum server processor and memory requirements.
The requirements provided are for the default configuration where no external
LDAP directories and databases are being used. Contact your IBM representative
to determine capacity requirements for your organization’s deployment.
Server platform
Minimum processor
Minimum RAM
™
IBM AIX
1.2 GHz IBM POWER4+
higher processor
or 4 GB
Linux
2.0 GHz Intel® Pentium® 4
or equivalent processor
4 GB
Solaris
1.28 GHz UltraSparc IIIi or
equivalent processor
4 GB
Microsoft Windows
2.0 GHz Intel Pentium 4 or
equivalent processor
4 GB
Using the NTFS file system is recommended for Windows systems.
Server disk space requirements
Installing Workplace Collaboration Services requires a minimum of 10 GB of free
disk space. This amount does not include the disk space required to install
database software if you use an external database server. Installation of the rich
client provisioning server requires an additional 1.5 GB.
If you use a two-server deployment or a multiple-server Network Deployment, the
Workplace server requires a minimum of 17 GB of free disk space. If you also
install the rich client provisioning server on the same machine, the server needs
18.5 GB of free disk space.
Note: For AIX installations, the /usr directory and /tmp directory each require a
minimum of 2 GB of free disk space. For Linux or Solaris installation, the
/opt directory and /tmp directory each require a minimum of 2 GB of free
disk space.
Chapter 1 Planning a deployment
3
Estimating disk space requirements for the messaging
capabilities of Workplace Collaboration Services
Before you install the messaging capabilities of Workplace Collaboration Services,
refer to the following table to estimate the disk space needed for the mail data. For
example, if you have 1000 users and each user uses the default disk space of 60
MB, you need approximately 73 GB of disk space. The numbers in the table are
based on an average message size of 50 KB and 90 day message stub retention. It
is also important to note that these estimates are for messaging only. Additional
database storage is required for archiving, if you implement an archiving solution.
Maximum storage per user (MB)
Number
of
10
Users
50
5
10
15
20
25
30
35
40
45
50
55
60
0.49
0.51
0.53
0.55
0.58
0.60
0.62
0.64
0.67
0.69
0.71
0.73
2.44
2.55
2.66
2.77
2.89
3.00
3.11
3.22
3.34
3.45
3.56
3.67
100
4.87
5.1
5.32
5.55
5.77
6.00
6.22
6.45
6.67
6.90
7.12
7.35
500
24.37 25.49 26.62 27.74 28.87 30.00 31.12 32.24 33.37 34.50 35.62 36.75
1000 48.73 50.98 53.23 55.48 57.74 60.00 62.24 64.49 66.74 68.99 71.24 73.49
5000 243.66 254.91 266.17 277.42 288.68 30.00 311.19 322.44 333.70 344.95 356.21 367.46
10000 487.32 509.83 532.34 554.85 577.35 600.00
Estimating disk space requirements for the collaborative learning
capabilities of Workplace Collaboration Services
Before you install the collaborative learning capabilities of Workplace Collaboration
Services, refer to the following information to estimate the amount of disk space
required for the learning data and indexes. The amount depends on the following
factors:
v Number of courses
v Number of registered users
v Average courses per user
v Average nodes (course elements) per course
Use the following formulas to estimate the size of the learning data and indexes:
To estimate the data size (in kilobytes), use this formula:
number_of_courses *(57 + average_nodes_per_course * 30.4) +
number_of_users *(10 + average_courses_per_user * (3.8 + average_nodes_per_course * 1.1))
To estimate the index size (in kilobytes), use this formula:
number_of_courses * (12.3 + average_nodes_per_course * 1.4) +
number_of_users * (1.5 + average_courses_per_user *(1.6 + average_nodes_per_course * 0.14))
To calculate the required disk space, add the data size to the index size. Multiply
the result of this calculation by 2 to determine the required disk space.
Network connectivity requirements
The network connectivity requirements for a Workplace server are as follows:
v Network adapter and connection to a physical network that can carry IP packets.
For example, Ethernet, token ring, ATM, and so on.
4
Installation and Upgrade Guide
v Static IP address with an entry in DNS.
v Configured fully qualified host name. Workplace Collaboration Services must be
able to resolve an IP address from its fully qualified host name.
To ensure that the host name is correctly configured in DNS, type one of these
commands at the command line of another server on the network:
v ping hostname.yourco.com
v (Windows) nslookup hostname.yourco.com
v (Linux) dig hostname.yourco.com
Server software and operating system requirements
This section describes the server software and operating system requirements.
Supported server operating systems
One of the following operating systems is required on the server where Workplace
Collaboration Services will be installed:
v IBM AIX 5.2 with Maintenance Level 4
v IBM AIX 5.3
v
v
v
v
v
Microsoft Windows 2000 Server with Service Pack 4
Microsoft Windows 2000 Advanced Server with Service Pack 4
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows Server 2003 Enterprise Edition
Red Hat Enterprise AS for Linuz (x89) 2.1 (both clustered and non-clustered
configurations), 3.0 (non-clustered configurations only)
v SuSE Linux Enterprise Server 8, 2.4 Kernel for Intel x86
v Sun Solaris 9 Fix Level 12-2002; Fix Level 112951-08
Components of WebSphere Application Server Enterprise 5.0.2.6 and WebSphere
Portal Enable for Multiplatforms 5.0.2.2 are installed automatically with Workplace
Collaboration Services. It is not possible to install Workplace Collaboration Services
on top of an existing WebSphere Application Server or WebSphere Portal
installation.
Supported databases
Workplace Collaboration Services installs Cloudscape by default; any of the
supported databases can then be substituted to Cloudscape. The following
databases are supported:
v +IBM Cloudscape 5.1
v +IBM DB2 Universal Database™ Enterprise Server Edition 8.1 (all platforms)
FixPak 4a and the hot fix for FixPak 7a are included for Windows servers.
FixPak 7a is available from http://www306.ibm.com/software/data/db2/udb/support/downloadv8.html
v IBM DB2 Universal Database Workgroup Server Edition 8.1 with FixPak 7a
v Microsoft SQL Server 2000 with Service Pack 3 and Service Pack 3a
v Oracle Enterprise Edition 9i Release 2 (9.2.0.4)
+Software marked with a plus sign (+) is shipped with Workplace Collaboration
Services and is only licensed for use with Workplace Collaboration Services.
Chapter 1 Planning a deployment
5
Supported HTTP servers
Workplace Collaboration Services comes with an internal HTTP server provided
with WebSphere Application Server, but using an optional separate HTTP server
can improve performance. An external HTTP server is also required for the rich
client provisioning server. Workplace Collaboration Services does not include an
external HTTP server, but the following HTTP servers are supported:
v Apache HTTP Server 1.3.26 and 1.3.28
v IBM HTTP Server 1.3.26.1 and 1.3.26.2
v IBM HTTP Server 2.0.42.1 and 2.0.42.2
v IBM Lotus® Domino® Enterprise Server (as Web server) 5.0.9a
v Microsoft IIS 5.0
v Sun ONE Web Server (formerly iPlanet), Enterprise Edition 6.0 with Service Pack
4
Supported LDAP directory servers
Workplace Collaboration Services installs with a default WebSphere Member
Manager user directory, but can be configured to run with the following LDAP
directory servers:
v
v
v
v
v
v
+IBM Tivoli Directory Server 5.2
IBM Lotus Domino Enterprise Server (as LDAP server) 6.5.1
Microsoft Active Directory 2000
Microsoft Active Directory 2003
Novell eDirectory 8.7
Sun Java™ System Directory Server 5.2 with Fix Pack 3
Note: If the LDAP server is Lotus Domino 6.5.1, Workplace Collaboration Services
supports searches of secondary Domino directories that are designated as
″Domain type: Notes″ in a directory assistance database on the server.
+Software marked with a plus sign (+) is shipped with Workplace Collaboration
Services and is only licensed for use with Workplace Collaboration Services.
Supported directory integration product
The following application supports the import of users from other mail systems
and provides directory integration for Workplace Collaboration Services:
v +IBM Tivoli® Directory Integrator 5.2
+Software marked with a plus sign (+) is shipped with Workplace Collaboration
Services and is only licensed for use with Workplace Collaboration Services.
Supported server Java Development Kits
v JDK 1.3.1
v JDK 1.4.2 (non-programmable embedded components)
Supported third-party single sign-on (SSO) products for the
browser client
v IBM Tivoli Access Manager 4.1
v IBM Tivoli Access Manager 5.1
6
Installation and Upgrade Guide
v Netegrity Policy Server 5.5
Attention: The rich client and provisioning server cannot be used in an
environment that uses Netegrity Policy Server because of limitations
with Netegrity Policy Server authentication protocols. However,
Netegrity Policy Server can be used by browser clients who use
Workplace Collaboration Services.
Supported public key infrastructure (PKI) products
v IBM Lotus Domino 6.5.2
v Microsoft Certificate Services provided with Windows 2000 server
v VeriSign 6.0
Supported proxy servers
v IBM WebSphere Application Server 6.0, Edge Components (awaiting
confirmation at publication time)
v IBM WebSphere Edge Server 2.0.2 with eFix 49, PTF-1
v Sun One Portal Server 6.2 (Reverse proxy not supported. Regular proxy is
supported.)
v Tivoli Access Manager 5.1
Additional requirements for the collaborative learning
capabilities of Workplace Collaboration Services
To support complete functionality for live classroom sessions, you need to install
IBM Lotus Virtual Classroom 1.1.1 or later.
Rich client hardware and software requirements
The minimum rich client processor and memory requirements are as follows:
v Intel Pentium 3 processor, 800 MHz
v 512 MB RAM
To reduce client startup time, you can use an Intel Pentium 4 processor and
increase the amount of memory to, for example, 1 GB. This increase in processor
speed and memory does not provide significant performance gains after startup.
Disk space recommendations for the rich client are described in the following table.
Installation scenario
Recommended disk space
IBM productivity tools not installed
350 MB
IBM productivity tools installed without
language pack
600 MB
IBM productivity tools installed with
language pack
700 MB
Supported operating systems for the rich client
The following operating systems are supported for the rich client:
v Microsoft Windows Mobile 2003
v Microsoft Windows 2000 Professional with Service Pack 2
Chapter 1 Planning a deployment
7
v Microsoft Windows XP with Service Pack 1
v Red Hat Enterprise Linux WS 3.0 with Update 3; Kernel: 2.4.2.21-27.0.2″;
Compiler: gcc 3.2, glibc 2.3.2; desktop environment: GNOME
Client software and operating system requirements
This section describes the client software and operating system requirements for
this release.
Supported operating systems for the browser client
The following operating systems are supported for browser clients:
v Mac 8.0 (to access the collaborative learning capabilities only through the
non-Portal-based interface)
v Microsoft Windows 2000 Professional with Service Pack 2
v Microsoft Windows XP with Service Pack 1
v Red Hat Enterprise Linux WS 3.0 with Update 3
v SuSE Linux Desktop 1.0
Note: The Learning Authoring Tool and Offline Learning client support Windows
2000 and Windows XP only.
Supported browsers
The following browsers are supported:
v Microsoft Internet Explorer 6.0 with Service Pack 1 on Windows 2000 and
Windows XP with the Sun Java Runtime Environment (JRE) 1.4.2 or with
Microsoft Java Virtual Machine (JVM) 1.1
v Mozilla 1.4 on Linux with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla 1.4 on Windows with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla Firefox 1.0 on Windows with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla Firefox 1.0 on Linux with Sun Java Runtime Environment (JRE) 1.4.2
v Netscape 6.2 (collaborative learning only)
Supported mail clients
In addition to the browser client and rich client, the messaging capabilities of
Workplace Collaboration Services support the following mail clients.
POP3 clients on Microsoft Windows 2000 and Microsoft Windows
XP
The messaging capabilities of Workplace Collaboration Services support the
following POP3 clients:
v IBM Lotus Notes 6.5
v Microsoft Outlook Express 6
v Microsoft Outlook for Windows XP and Windows 2003
v WebSphere Portal Internet Mailbox 5.0
8
Installation and Upgrade Guide
IMAP clients on Microsoft Windows 2000 and Microsoft Windows
XP
The messaging capabilities of Workplace Collaboration Services support the
following IMAP clients:
v IBM Lotus Notes 6.5
v Microsoft Outlook Express 6
v Microsoft Outlook on Windows XP and Windows 2003
Supported client Java Development Kit (JDK)
JDK 1.4.2
Related concepts
Requirements for IBM i5/OS
Installation
Requirements for i5/OS
This topic describes requirements for running IBM Workplace Collaboration
Services on IBM i5/OS™.
Unless specified otherwise, the requirements in this topic also apply to the
individual IBM Workplace collaboration products, including IBM Workplace
Messaging, IBM Workplace Team Collaboration, IBM Workplace Documents, and
IBM Workplace Collaborative Learning. Also note:
v Any information that specifically addresses the messaging capabilities of IBM
Workplace Collaboration Services also applies to IBM Workplace Messaging.
v Any information that specifically addresses the collaborative learning capabilities
of IBM Workplace Collaboration Services also applies to IBM Workplace
Collaborative Learning.
v Any information that specifically addresses the web content management
capabilities of IBM Workplace Collaboration Services also applies to IBM
Workplace Web Content Management.
This topic contains the following requirements:
v Hardware requirements
v Required software products
v Required Program Temporary Fixes (PTFs)
v Server software and operating system requirements
v Rich client hardware and software requirements
v Client software and operating system requirements
This requirements information may be updated periodically on the Web. For the
latest information see the Workplace Collaboration Services Release Notes® at
http://www.lotus.com/ldd/notesua.nsf.
Note: For the system requirements for the web content management capabilities of
IBM Workplace Collaboration Services, see
http://www.lotus.com/products/product5.nsf/wdocs/lwwcmsysreq.
Chapter 1 Planning a deployment
9
Hardware requirements for i5/OS
This section describes the server hardware requirements.
Server hardware
The following are the minimum server processor and memory requirements for
new IBM eServer™ i5™ systems. For existing systems, contact your IBM
representative to determine capacity requirements for your organization’s
deployment.
v IBM eServer i5 520 1-way (2400 CPW)
v 4 GB main storage
v 15 GB of disk space for installation of Workplace Collaboration Services and
WebSphere® Application Server V5.0.2 Enterprise Enablement
v 4 GB of disk space for each WebSphere Application Server instance configured
for use with Workplace Collaboration Services
Estimating disk space requirements for the messaging capabilities of Workplace
Collaboration Services
Before you install the messaging capabilities of Workplace Collaboration Services,
refer to the following table to estimate the disk space needed for the mail data. For
example, if you have 1000 users and each user uses the default disk space of 60
MB, you need approximately 73 GB of disk space. The numbers in the table are
based on an average message size of 50 KB and 90 day message stub retention. It
is also important to note that these estimates are for Messaging only. Additional
database storage is required for archiving, if you implement an archiving solution.
Maximum storage per user (MB)
Number
of
10
Users
50
5
10
15
20
25
30
35
40
45
50
55
60
0.49
0.51
0.53
0.55
0.58
0.60
0.62
0.64
0.67
0.69
0.71
0.73
2.44
2.55
2.66
2.77
2.89
3.00
3.11
3.22
3.34
3.45
3.56
3.67
100
4.87
5.1
5.32
5.55
5.77
6.00
6.22
6.45
6.67
6.90
7.12
7.35
500
24.37 25.49 26.62 27.74 28.87 30.00 31.12 32.24 33.37 34.50 35.62 36.75
1000 48.73 50.98 53.23 55.48 57.74 60.00 62.24 64.49 66.74 68.99 71.24 73.49
5000 243.66 254.91 266.17 277.42 288.68 30.00 311.19 322.44 333.70 344.95 356.21 367.46
10000 487.32 509.83 532.34 554.85 577.35 600.00
Note: IBM DB2 Universal Database for iSeries has a size limit of 1.7 TB per table.
Network connectivity requirements
The network connectivity requirements for a Workplace server are as follows:
v Network adapter and connection to a physical network that can carry IP packets.
For example, Ethernet, token ring, ATM, and so on.
v Static IP address with an entry in DNS.
v Configured fully qualified host name. Workplace Collaboration Services must be
able to resolve an IP address from its fully qualified host name.
To ensure that the host name is correctly configured in DNS, enter the following
command at the command line of another server on the network:
10
Installation and Upgrade Guide
ping hostname.yourco.com
i5/OS user profiles
To install and configure Workplace Collaboration Services on i5/OS, you must
have a user profile with the following special authorities:
v *ALLOBJ
v *IOSYSCFG
v *JOBCTL
Setting the time on i5/OS
Before installing the IBM Workplace Collaboration Services software, ensure that
the UTC offset system value is set correctly by running the following command
from an i5/OS command line (example below is for Central Standard Time):
CHGSYSVAL SYSVAL(QTIMZON) VALUE(QN0600CST)
Workstation requirements for remote installation
In order to install the IBM Workplace Collaboration Services software using the
graphical interface, you must be connected to your i5 server from a remote
workstation. The requirements for that workstation are as follows:
v Windows 2000 or Windows XP
v DVD-ROM drive
Required i5/OS software products
The following software products are required for Workplace Collaboration Services
on i5/OS:
Program
Option
5722SS1
Description
i5/OS V5R3
5722SS1
12
Host Servers
5722SS1
30
QShell Interpreter
5722SS1
33
Portable Application Solution
Environment (PASE)
5722AC3
Crypto Access Provider
128-bit
5722DG1
IBM HTTP Server
5722JV1
*BASE
IBM Developer Kit for Java
5722JV1
5
Dev Toolkit for Java (Version
1.3)
5722JV1
6
Dev Toolkit for Java (Version
1.4)
5722TC1
TCP/IP Utilities
5733WS5
*BASE
WebSphere Application
Server V5.0
5733WS5
1
WAS V5.0 Client
development and runtime
Chapter 1 Planning a deployment
11
5733WS5
2
WAS V5.0 Application server
runtime
5733WS5
10
WAS V5.0 Enterprise
Enablement1
5799PTL
iSeries Tools for Developers
PRPQ
1
For information on installing WebSphere Application Server V5.0 Enterprise
Enablement, see ″Installing WebSphere Application Server V5.0 Enterprise
Enablement (i5/OS only)″ in the IBM Workplace Collaboration Services
Information Center.
To determine which software is installed on your system, enter DSPSFWRSC on an
i5/OS command line. The Display Software Resources screen shows all installed
software.
Required i5/OS PTFs
This section describes the group and individual program temporary fixes (PTFs)
that must be installed on your system prior to Workplace Collaboration Services
installation. For instructions on ordering PTFs, go to http://www912.ibm.com/supporthome.nsf/document/10000069.
Group PTFs
Ensure that the following group PTFs are installed. Apply these PTFs after
installing all required software, and before applying the individual PTFs.
Group Number
Description
Minimum Level
SF99530
Cumulative PTF package
5102
SF99503
DB2 UDB for iSeries
4
SF99287
WebSphere App Server V5.0
(Base Edition)
7
SF99269
Java
5
SF99099
IBM HTTP Server
5
SF99282
WebSphere Portal
3
Express/Express Plus Service
Pack
Verifying which group PTFs are installed
To determine if the correct group PTF packages are installed, perform the
following steps:
1. Sign on to your server.
2. Enter the Work with PTF Groups command on an i5/OS command line:
WRKPTFGRP
The Work with PTF Groups status screen lists the PTF group level and what
group PTFs have been applied to your server.
Individual PTFs
12
Installation and Upgrade Guide
After installing all required group PTFs, ensure that the following individual PTFs
are installed:
PTF Number
Product
Description
SI09622
5799PTL
OSP-INCORROUT vnc does
not start
SI17277
5722SS1
OSP-DB-MSGSQL0514
PREPARED STMT NOT
USED FOR 2ND OPEN
SI17314
5722SS1
OSP-DB-MSGSQL0501
switching between NTS
transactions
SI17480
5722SS1
OSP-DB msgCPD0013
f/QCANPARS t/QDBOPEN
per msgCPF32A4
SI17274
5722SS1
OSP-DB-MSGSQL0514
PREPARED STMT NOT
USED FOR 2ND OPEN
SI17551
5722SS1
Database fix
Verifying which individual PTFs are installed
To determine whether the correct individual PTF packages are installed, perform
the following steps:
1. Sign on to your server.
2. Enter the Display PTF Status command on an i5/OS command line.
DSPPTF LICPGM(product)
The Display PTF Status screen is displayed. This screen lists the PTFs that have
been applied to your server.
Supported databases
Workplace Collaboration Services runs on i5/OS with the following DBMS server:
v IBM DB2 Universal Database for iSeries V5R3
Supported HTTP servers
A separate, external HTTP server is required for instant messaging, presence, and
Web conferencing activities and for the rich client provisioning server. Workplace
Collaboration Services comes with an internal HTTP server provided with
WebSphere Application Server, but using an external HTTP server can improve
performance.
Workplace Collaboration Services runs on i5/OS with the following local or remote
HTTP servers:
v IBM HTTP Server for iSeries 2.0.49
v IBM Lotus Domino Server for iSeries Release 5.0.12 or later
Workplace Collaboration Services also runs with the following remote HTTP
servers:
v Apache HTTP Server 1.3.26 and 1.3.28
v IBM HTTP Server 1.3.26.1 and 1.3.26.2
Chapter 1 Planning a deployment
13
v
v
v
v
IBM HTTP Server 2.0.42.1 and 2.0.42.2
IBM Lotus Domino Enterprise Server (as Web server) 5.0.9a
Microsoft IIS 5.0
Sun ONE Web Server (formerly iPlanet), Enterprise Edition 6.0 with Service Pack
4
Supported LDAP directory servers
Workplace Collaboration Services installs with a default WebSphere Member
Manager user directory, but can be configured to run with the following LDAP
directory servers:
v IBM Tivoli Directory Server for iSeries 5.1 (with i5/OS V5R3)
v IBM Tivoli Directory Server 5.2
v IBM Lotus Domino Enterprise Server (as LDAP server) 6.5.1
v Microsoft Active Directory 2000
v Microsoft Active Directory 2003
v Novell eDirectory 8.7
v Sun Java System Directory Server 5.2 with Fix Pack 3
Supported directory integration product
The following application supports the import of users from other mail systems
and provides directory integration for Workplace Collaboration Services:
v +IBM Tivoli Directory Integrator 5.2
+Software marked with a plus sign (+) is shipped with Workplace Collaboration
Services and is only licensed for use with Workplace Collaboration Services.
Supported third-party single sign-on products for the browser
client
v IBM Tivoli Access Manager 4.1
v IBM Tivoli Access Manager 5.1
v Netegrity Policy Server 5.5
Supported third-party public key infrastructure products
v VeriSign 6.0
Supported proxy servers
v IBM WebSphere Application Server 6.0, Edge Components (awaiting
confirmation at publication time)
v IBM WebSphere Edge Server 2.0.2 with eFix 49, PTF-1
v Sun One Portal Server 6.2 (Reverse proxy not supported. Regular proxy is
supported.)
v Tivoli Access Manager 5.1
Rich client hardware and software requirements
The minimum rich client processor and memory requirements are as follows:
v Intel Pentium 3 processor, 800 MHz
v 512 MB RAM
14
Installation and Upgrade Guide
To reduce client startup time, you can use an Intel Pentium 4 processor and
increase the amount of memory to, for example, 1 GB. This increase in processor
speed and memory does not provide significant performance gains after startup.
Disk space recommendations for the rich client are described in the following table.
Installation scenario
Recommended disk space
IBM productivity tools not installed
350 MB
IBM productivity tools installed without
language pack
600 MB
IBM productivity tools installed with
language pack
700 MB
Supported operating systems for the rich client
The following operating systems are supported for the rich client:
v Microsoft Windows Mobile 2003
v Microsoft Windows 2000 Professional with Service Pack 2
v Microsoft Windows XP with Service Pack 1
v Red Hat Enterprise Linux WS 3.0 with Update 3; Kernel: 2.4.2.21-27.0.2″;
Compiler: gcc 3.2, glibc 2.3.2; desktop environment: GNOME
Client software and operating system requirements
This section describes the client software and operating system requirements for
this release.
Supported operating systems for the browser client
The following operating systems are supported for browser clients:
v Mac 8.0 ((to access the collaborative learning capabilities only through the
non-Portal-based interface)
v Microsoft Windows 2000 Professional with Service Pack 2
v Microsoft Windows XP with Service Pack 1
v Red Hat Enterprise Linux WS 3.0 with Update 3
v SuSE Linux Desktop 1.0
Note: The Learning Authoring Tool and Offline Learning client support Windows
2000 and Windows XP only.
Supported browsers
The following browsers are supported:
v Microsoft Internet Explorer 6.0 with Service Pack 1 on Windows 2000 and
Windows XP with the Sun Java Runtime Environment (JRE) 1.4.2 or with
Microsoft Java Virtual Machine (JVM) 1.1
v Mozilla 1.4 on Linux with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla 1.4 on Windows with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla Firefox 1.0 on Windows with Sun Java Runtime Environment (JRE) 1.4.2
v Mozilla Firefox 1.0 on Linux with Sun Java Runtime Environment (JRE) 1.4.2
v Netscape 6.2 (Collaborative Learning only)
Chapter 1 Planning a deployment
15
Supported mail clients
In addition to the browser client and rich client, the messaging capabilities of
Workplace Collaboration Services support the following mail clients.
POP3 clients on Microsoft Windows 2000 and Microsoft Windows
XP
The messaging capabilities of Workplace Collaboration Services support the
following POP3 clients:
v IBM Lotus Notes® 6.5
v Microsoft Outlook Express 6
v Microsoft Outlook for Windows XP and Windows 2003
v WebSphere Portal Internet Mailbox 5.0
IMAP clients on Microsoft Windows 2000 and Microsoft Windows
XP
The messaging capabilities of Workplace Collaboration Services support the
following IMAP clients:
v IBM Lotus Notes 6.5
v Microsoft Outlook Express 6
v Microsoft Outlook on Windows XP and Windows 2003
Supported client Java Development Kit (JDK)
JDK 1.4.2
Related concepts
Requirements for AIX, Linux, Solaris, and Windows
Installation overview
In a production environment, you install IBM Workplace Collaboration Services in
phases; each phase consists of one or more tasks.
A demo installation does not require a phased installation.
Planning a Workplace Collaboration Services deployment
Before installing anything, read through all the planning topics and make sure that
you understand what software you will install on various servers, and how you
will configure your Workplace Collaboration Services deployment. Completing the
Administrative names and passwords worksheet helps you to collect information
about the different user accounts that you will use while installing Workplace
Collaboration Services and related software. The Pre-installation checklist, which
you fill out at the end of Phase 1, ensures that you complete preliminary tasks in
the proper order before you install Workplace Collaboration Services products.
This phase is described in ″Planning a deployment.″
Preparing the Workplace Collaboration Services environment
For a WebSphere Application Server Network Deployment on AIX, Linux, Solaris,
or Microsoft Windows, you must install some additional components before you
16
Installation and Upgrade Guide
can set up the actual Network Deployment and federate Workplace Collaboration
Services servers to it. Begin by creating shared directories that will be accessed by
all Workplace Collaboration Services servers in the deployment, then install and set
up the Deployment Manager. At this time, you also install the WebSphere
Application Server Edge components to set up load balancing for the deployment.
In an i5/OS environment, install WAS V5.0 Enterprise Enablement before installing
Workplace Collaboration Services. Also, if you are setting up a rich client
provisioning server and intend to use the Create IBM Workplace Collaboration
Services wizard to configure it (recommended), copy the rich client installation files
to your system.
In any environment where a remote DBMS server will be used, install the DBMS
server software on the DBMS server and install a DBMS client on the Workplace
server. The Workplace Collaboration Services installation program always installs
with Cloudscape as its default DBMS product, and immediately creates its own
databases. Although Cloudscape is sufficient for a demonstration, you should
connect Workplace Collaboration Services to a more robust DBMS product for
production use, even if you are working with a single-server configuration.
In any environment where a remote HTTP server will be used, install the HTTP
server plug-in and perform other tasks to prepare for Workplace Collaboration
Services installation.
This phase is described in ″Preparing the environment.″
Installing Workplace Collaboration Services
After the basic requirements have been met and preparations are made, you can
install the Workplace Collaboration Services software, selecting the licensed
products you need.
If you are setting up a Network Deployment and intend to use the rich client
provisioning server, you must also install the provisioning server at this time -before federating the node, as explained in the Network Deployment installation
and configuration road map.
If you are installing on IBM i5/OS, it is recommended that you use the Create IBM
Workplace Collaboration Services wizard immediately after installation to
configure your Workplace Collaboration Services deployment. The Create IBM
Workplace Collaboration Services wizard performs Virtual Network Computing,
DBMS, LDAP, HTTP, and Learning, and rich client setup through a single,
Web-based interface, allowing you to skip Phases 4 through 8.
If you are installing on i5/OS and choose not to use the Create IBM Workplace
Collaboration Services wizard, you must configure Virtual Network Computing
(VNC) before proceeding to the next phase.
This phase is described in ″Installing IBM Workplace Collaboration Services.″
Connecting to an LDAP directory
The Workplace Collaboration Services installation program sets up WebSphere
Member Manager as the default user directory. If you prefer to connect to an
LDAP directory, you first establish mappings between the LDAP directory and
Workplace Collaboration Services to ensure both proper access for users and
Chapter 1 Planning a deployment
17
proper security levels to protect data. In addition, you must create LDAP
administrator accounts for use with Workplace Collaboration Services. Then run
the Configuration Wizard to connect to the LDAP directory.
This phase is described in ″Connecting to an LDAP directory.″
Connecting to a DBMS server
After installing Workplace Collaboration Services, run the Configuration Wizard to
create and configure the Workplace Collaboration Services database before
transferring data to it.
This phase is described in ″Connecting to a DBMS server.″
Connecting to an external HTTP server
After installation, you may install and set up an external HTTP server for the rich
client provisioning server or for a Network Deployment. To improve performance,
you may also use a separate HTTP server with Workplace Collaborative Learning
and the other Workplace Collaboration Services products.
Note: If you set up an HTTP server on a separate machine, the remote HTTP
server must be in the same Internet DNS domain as the Workplace server.
This phase is described in ″Connecting to an external HTTP server.″
Setting Up IBM Workplace Collaborative Learning
After installation, a final set of tasks ensures that all of the Workplace
Collaborative Learning components can communicate.
This phase is described in ″Setting up IBM Workplace Collaborative Learning.″
Installing and distributing the Workplace Collaboration Services
rich client
The provisioning server provides the Workplace Collaboration Services rich client
applications to the user workstation during managed client desktop installation.
Every time a user logs in to the client, the system checks the provisioning server to
determine if there are updates or new components available. If there are, the user
is prompted to update the Workplace Collaboration Services rich client.
Note: If you are setting up a Network Deployment, you install the provisioning
server earlier in the overall task sequence before federating network nodes,
as explained in the Network Deployment installation and configuration road
map.
Customers or business partners who are interested in the Workplace Collaboration
Services Client technology should contact their IBM representative for more details.
This phase is described in ″Rich client installation and configuration.″
Completing Network Deployment setup
If you are installing Workplace Collaboration Services using a Network
Deployment, you must complete the Network Deployment before anyone starts
18
Installation and Upgrade Guide
using Workplace Collaboration Services. Tasks include updating rich client files,
federating nodes and adding them to a cluster, setting up dynamic caching and
messaging, distributing various files to ensure that all nodes have a copy, installing
fix packs, and setting up load balancing for instant messaging and Web
conferences.
This phase is described in ″Completing Network Deployment setup.″
Related concepts
Workplace Collaboration Services software components
“Installation scenarios” on page 30
Requirements for AIX, Linux, Solaris, and Windows
Requirements for i5/OS
Optional post-installation tasks
Reference information
Workplace Collaboration Services software components
The following components are part of an IBM Workplace Collaboration Services
environment. The Workplace Collaboration Services installation program installs
some of these components; others you must install separately, using the vendor’s
documentation.
For details on specific versions of support products, see the topic, ″Requirements.″
HTTP server
An HTTP server handles client HTTP requests across an intranet or the
Internet. Workplace Collaboration Services uses an internal HTTP server
built into IBM WebSphere Application Server. However, you may need to,
or want to, install an external HTTP server and configure it to handle
Workplace Collaboration Services client requests. For example, an external
HTTP server is required for IBM Workplace SIP services (used for instant
messaging, awareness, and Web conference activity). It is also required for
the rich client provisioning server. Also, for busy production environments,
setting up an external HTTP server provides optimal performance for IBM
Workplace Collaborative Learning and other Workplace Collaboration
Services products.
Workplace Collaboration Services supports many HTTP servers, including:
Apache HTTP Server, IBM HTTP Server, Lotus Domino Enterprise Server,
Microsoft IIS, and Sun ONE Web Server.
Database Management System
A database management system (DBMS) hosts the database that stores
Workplace Collaboration Services data and manages access to them.
By default, Workplace Collaboration Services uses a local IBM Cloudscape
database to store data. For better performance, you can configure
Workplace Collaboration Services to use IBM DB2 Universal Database,
Oracle, or Microsoft SQL Server. If you prefer to use one of these DBMS
servers instead, use the Configuration Wizard after installation to transfer
Workplace Collaboration Services data from the Cloudscape database to
the preferred DBMS server.
If the DBMS server is not installed on the Workplace server, you must
install the appropriate DBMS client software on the Workplace server to
ensure that it can access the databases.
Chapter 1 Planning a deployment
19
Cloudscape Network Server Edition and DB2 Universal Database
Enterprise Server Version 8.1 with FixPak 7a are included with Workplace
Collaboration Services; however, you can only use Cloudscape when the
DBMS is hosted directly on the Workplace server.
LDAP directory
An LDAP directory stores user account information, which is used by
Workplace Collaboration Servicesfor authentication. By default, Workplace
Collaboration Services uses WebSphere Member Manager to store user
account information. If you prefer to use an existing LDAP directory
instead, use the Configuration Wizard after installation to set up an LDAP
directory.
Workplace Collaboration Services supports a variety of LDAP directories,
including IBM Directory Server, Lotus Domino Enterprise Server, Microsoft
Active Directory, Novell eDirectory, and Sun ONE Directory Server.
If your company already uses a supported LDAP directory, you can use it
instead of setting up a new one.
IBM Directory Server 5.2 is included with Workplace Collaboration
Services.
IBM WebSphere Application Server
WebSphere Application Server is installed automatically with Workplace
Collaboration Services. WebSphere Application Server Enterprise Version
provides the WebSphere Administrative Console, from which you can
configure and administer the WebSphere Application Server and Workplace
Collaboration Services products. WebSphere Application Server also
provides the technology for Workplace Collaboration Services to be
installed as part of a distributed Network Deployment.
IBM WebSphere Portal
WebSphere Portal is automatically installed with Workplace Collaboration
Services and provides the infrastructure for its products.
The Workplace Collaboration Services installation also includes the
following software as appropriate for your configuration: Lotus
Collaborative component Version 5.0, Odyssey browser framework,
WebSphere Member Manager (WMM) Version 5.0, IBM Cloudscape Version
5.1.3.6, IBM WebSphere Studio Site Developer Version 5.1.1, and IBM
WebSphere Portal Content Publishing Version 5.0.
IBM Workplace Collaborative Learning Servers
Collaborative Learning requires three servers: a Learning Server, a
Learning Delivery Server, and a course content server.
A Learning Server contains the functions and capabilities for configuring
and coordinating the other Collaborative Learning features. It is installed
automatically with the Workplace Collaborative Learning product.
A Learning Delivery Server is a Workplace Collaborative Learning feature
that launches course content, provides course navigation features, tracks
student progress, and sends tracking information to the Learning Server. It
is installed automatically with the Workplace Collaborative Learning
product.
A course content server is any file server (usually an HTTP server) that
contains content for Workplace Collaborative Learning courses. The
Learning Delivery Server accesses the course content from the course
content server. Before installing WorkplaceCollaborative Learning, you
20
Installation and Upgrade Guide
must know which protocol (usually FTP) the Learning Delivery Server will
use to access the course content server. You must also configure the course
content server to use the protocol you have chosen. You can populate the
course content server at any time before or after installing Workplace
Collaborative Learning. Depending on your environment, you can
maintain a course content server on its own computer, or install it on a
computer that hosts other features and products.
Mail Service
The Mail Service allows browser and rich client access to mail on an
Workplace server. The Mail Service also supports Internet Message Access
Protocol (IMAP), and Post Office Protocol version 3 (POP3) clients from
other mail systems, and includes the following services:
v Simple Mail Transfer Protocol (SMTP) Inbound
v SMTP Outbound/Local Delivery
v Message Handler
v POP3
v IMAP
The Mail Service works with the message queue, the queue directory, and
the message store to receive, process, and send e-mail. Depending on your
environment, you can install the Mail Service on its own computer, or
install it on a computer with other Workplace Collaboration Services
products.
You must use the Mail Service installed by the Workplace Collaboration
Services installation program, but you can use other SMTP servers within a
deployed infrastructure as routing or relay hubs.
The Mail Service is required if you are installing IBM Workplace
Messaging. The POP3 and IMAP services are not required.
IBM Workplace Rich Client
The IBM Workplace Rich Client is a desktop environment that lets users
work with IBM Workplace Messaging and IBM Workplace Documents. The
client installation comprises two procedures: the administrator installs a
provisioning server for use with Workplace Collaboration Services, and
users install the client on their desktops from the provisioning server.
IBM Workplace client provisioning server
The provisioning server provides the Workplace Collaboration Services
client applications to the user workstation during client desktop
installation. It also provides updates. Every time a user logs in to the
client, the system checks the provisioning server to determine if there are
updates or new components available. If there are, the user is prompted to
update the rich client.
Customers or business partners who are interested in the IBM Workplace
Client technology should contact their IBM representative for more details.
Licensing IBM Workplace products
You must purchase a license for Workplace Collaboration Services products before
you install them. To purchase product licenses, contact your IBM representative or
point your browser at www.ibm.com.
Chapter 1 Planning a deployment
21
After installation, click Workplace → Licenses in the WebSphere Administrative
Console to access the Licenses page, which displays the licenses you purchased.
To enable a license for an additional Workplace Collaboration Services product, or
to disable a product’s license, be sure to contact your IBM representative first to
make the appropriate business arrangements, and then use the Licenses page to
enable (License) or disable (Unlicense) the product.
Related concepts
Installation overview
Requirements for AIX, Linux, Solaris, and Windows
Requirements for i5/OS
Setting up an HTTP server
Types of external HTTP servers: This section describes the use of external HTTP
servers that are either local or remote:
v A local HTTP server is located on the same machine as IBM Workplace
Collaboration Services or the provisioning server.
This option is a good choice for i5/OS systems. For IBM AIX, Linux, Sun Solaris,
and Microsoft Windows servers, this option is only recommended when
performance is not a major concern. It ensures that all network traffic flows over
port 80, which is often a requirement when clients need to reach servers
protected by a firewall, but performance is slower than it is with a remote HTTP
server.
v A remote HTTP server resides on a separate machine from Workplace
Collaboration Services or the provisioning server.
This option is required for a Network Deployment and is recommended for
most production deployments because it provides better performance and load
balancing. It is also recommended for a single-server environment that runs IBM
Workplace Collaborative Learning.
Types of HTTP services
External HTTP servers provide HTTP transport services for:
v Workplace Collaboration Services products, including Workplace Collaborative
Learning and products that use SIP services.
v The Workplace Collaborative Learning content server (where courses are stored).
v The rich client provisioning server.
The instructions in this section use the term ″HTTP server″ to refer to any of these
uses. You may use one machine as the external HTTP server for all these functions
or maintain separate machines to distribute the server load.
Related concepts
Phase 6: Setting up an external HTTP server
Related tasks
Setting up an external HTTP server
Administrator names and passwords worksheet
To prepare for IBM Workplace Collaboration Services installation and
configuration, fill in this worksheet with the names and passwords for the
administrator users or groups at your site.
22
Installation and Upgrade Guide
Information needed
Description
Name and password
for your site
Before installing
Workplace
Collaboration
Services
1
IBM AIX, Linux, or
Sun Solaris
administrator
Create a user with
administrative
privileges who can
install software on
this server. Log in as
this user when you
are ready to install
Workplace
Collaboration
Services.
2
Microsoft Windows
administrator
Create a user with
administrative
privileges who can
install software on
this server. Log in as
this user when you
are ready to install
Workplace
Collaboration
Services.
3
IBM i5/OS
administrator
Create a user with
administrative
privileges who can
install software on
this server. The user
must have at least
*ALLOBJ,
*IOSYSCFG, and
*JOBCTL special
authorities. Log in as
this user when you
are ready to install
Workplace
Collaboration
Services.
Chapter 1 Planning a deployment
23
4
Information needed
Description
Workplace
Collaboration
Services
administrator
Decide on a name
and password for the
Workplace
Collaboration
Services
administrator. If you
will connect
Workplace
Collaboration
Services to an
existing LDAP
directory, this user
name and password
must already exist in
your user directory.
You will be
prompted for this
administrator name
during Workplace
Collaboration
Services installation.
This user is the same
name that you will
specify for User #13.
Before connecting a
DBMS to Workplace
Collaboration
Services
24
Installation and Upgrade Guide
Name and password
for your site
5
Information needed
Description
Database
administrator
A user name and
password with
administrator access
to the DBMS server;
typically you will use
the account created
during DBMS server
installation.
Name and password
for your site
In DB2 Universal
Database, the
standard database
administrator account
is called db2admin
in Windows and
db2inst1 in AIX,
Linux, and Solaris. In
Oracle it is called
system and in SQL
Server it is called SA.
Any account with
administrative
privileges can be
used.
Attention: The
database
administrator user
name cannot be
changed after
installation. For this
reason, it is
recommended that
you use an ID
associated with the
role of database
administrator, and
not one associated
with a specific user.
6
Database client
A user name and
password with
authority to
administer remote
databases on the
DBMS server;
normally you will
use the account
created during client
installation (typically
this account receives
the same name as is
used on the DBMS
server).
This user does not
have to be listed in
the LDAP directory.
Chapter 1 Planning a deployment
25
7
Information needed
Description
Workplace
Collaboration
Services application
data source user
DB2 Universal
Database only
If you do not want
Workplace
Collaboration
Services using the
DB2® database
administrator
(db2admin) account
to access the data
source, create a
separate DB2 user
account for this
purpose.
This user is not
needed for Oracle
and SQL Server
because
authentication is
handled differently.
8
IBM WebSphere
Portal database user
The user ID and
password for the
administrator of the
WebSphere Portal
wps50 database.
For DB2 Universal
Database, this can be
the DB2
administrator or
another user. For
Oracle and Microsoft
SQL Server, create a
user with the name
WPSDBUSR and
assign a password.
9
WMM WebSphere
Portal database user
The additional user
ID and password for
the administrator of
the WebSphere Portal
database.
For DB2 Universal
Database, this should
be the same as User
#8. For Oracle and
SQL Server, create a
user with the name
WMMDBUSR and
assign a password.
26
Installation and Upgrade Guide
Name and password
for your site
10
Information needed
Description
WebSphere Portal
content publishing
database user
The user ID and
password for the
administrator of the
WebSphere Portal
wpcp50 database.
Name and password
for your site
For DB2 Universal
Database, this should
be the same as User
#8.
For Oracle and SQL
Server, create three
users with the
following names and
assign a password to
each (you may want
to assign the same
password to all of
them):
v EJB
v PZNADMIN
v WCMDBADM
11
WebSphere Portal
feedback database
user
The user ID and
password for the
administrator of the
WebSphere Portal
fdbk50 database.
For DB2 Universal
Database, this should
be the same as User
#8. For Oracle and
SQL Server, the
recommended user
name is FEEDBACK.
Before connecting an
LDAP directory to
Workplace
Collaboration
Services
Chapter 1 Planning a deployment
27
Information needed
Description
12
IBM WebSphere
Application Server
administrator
Create a user name
and password to
allow access to
WebSphere
Application Server
with administrator
authority. You must
create, or already
have, a record for
this user in the user
directory, and the
user must be a
member of the
WebSphere Portal
administrators group.
This administrator is
likely to be the same
as User #13.
13
WebSphere Portal
administrator
Create a user name
and password to
allow access to
WebSphere Portal
with administrator
authority. You must
create, or already
have, a record for
this user in the user
directory, and the
user must be a
member of the
administrators group.
This user name is
used for WebSphere
Portal access and is
not related to any
users who have
access to the
operating system
itself.
This administrator is
the same as User #4
and is likely to be the
same as User #12.
14
28
Installation and Upgrade Guide
WebSphere Portal
administrator group
This group must
include the name of
the WebSphere Portal
administrator you
created for User #4
and #13.
Name and password
for your site
Information needed
Description
15
LDAP Administrator
Name that Member
Manager uses to
access the LDAP
directory. If you want
Member Manager to
have only read access
to the directory, give
this account only
read access.
16
LDAP Bind ID
Name used to bind
to the LDAP
directory in order to
look up Users #13,
#14, and #15.
Name and password
for your site
Before connecting an
HTTP Server to IBM
Workplace
Collaborative
Learning
17
Content Server FTP
user
If you want to use
the FTP method of
content delivery,
create a user name
and password with
sufficient rights to
access the FTP server
and upload content.
Testing Workplace
Collaboration
Services
18
Workplace
Collaboration
Services user name
To test the Workplace
Collaboration
Services installation,
log in as the
Workplace
Collaboration
Services
administrator.
Pre-installation checklist
Before installing and configuring IBM Workplace Collaboration Services, use this
checklist to ensure that you have completed all necessary preparations.
Complete
Pre-installation tasks
Make sure that you have purchased licenses
for any Workplace Collaboration Services
products you plan to install. To purchase
product licenses, contact your IBM
representative or point your browser at
www.ibm.com.
Chapter 1 Planning a deployment
29
Complete
Pre-installation tasks
Decide how many servers will be used for
your deployment. Read the topic ″Phase 1:
Planning a deployment″ for guidelines.
Choose whether you will use keep the
default IBM Cloudscape database or transfer
data to IBM DB2 Universal Database, IBM
DB2 Universal Database for iSeries, Oracle,
or Microsoft SQL Server.
Decide whether you will use an LDAP
directory as the user directory rather than
the IBM WebSphere Member Manager
directory that is provided for you.
Determine if your environment needs an
external HTTP server.
If you are installing IBM Workplace
Collaborative Learning, determine where
you will store course content and which
method (FTP or local file system) the
Learning Delivery Server will use to access
the content.
Verify that you have the necessary hardware
and software and their required versions.
If you are installing IBM Workplace
Messaging, disable any mail server that is
already running, as described in the mail
server’s documentation.
Fill out the ″Administrator names and
passwords worksheet″ and have the
information available during installation.
Verify that the administrators exist in the
user directory and that they are members of
the appropriate administrator groups.
Read the Workplace Collaboration Services
Release Notes for the latest information on
installation issues and workarounds. The
release notes are available on the Web at
http://www.lotus.com/doc.
If you will be configuring Workplace
Collaboration Services in a IBM WebSphere
Application Server Network Deployment,
complete preparations for the deployment.
If you will be configuring Workplace
Collaboration Services in an IBM i5/OS
environment, install IBM WebSphere
Application Server V5.0 Enterprise
Enablement.
Installation scenarios
There are two types of configurations for production use:
v Single-server production deployment
This deployment runs on IBM AIX, Linux, Sun Solaris, and Microsoft Windows
platforms. For IBM i5/OS environments, this is the only supported deployment.
30
Installation and Upgrade Guide
v A multiple-server cluster, known as a Network Deployment environment.
Sites with many users or a large amount of data should strongly consider
deploying a multiple-server cluster because it offers better performance and load
balancing. This deployment runs on AIX, Linux, Solaris, and Windows
platforms.
You may also install a demo server which is a single-server installation that uses
the internal database and user directory that come with IBM Workplace
Collaboration Services.
Related concepts
Phase 1: Planning a deployment
Installing a demo server
The following figure illustrates how IBM Workplace Collaboration Services
components are hosted on a single server. An all-in-one deployment such as this is
suitable only for demonstrations because it taxes the server’s resources. This type
of deployment is not supported on IBM i5/OS.
A demo deployment uses the default IBM Cloudscape database as the repository
for Workplace Collaboration Services data and IBM WebSphere Member Manager
(WMM) as the user directory. If you install the IBM Workplace Collaborative
Learning component, then the Learning Server, the Learning Delivery Server, and
the course content server are also installed on this computer. And if you install
IBM Workplace Messaging, then the SMTP, and the IMAP or POP3, servers are
installed on the computer as well.
To install a demo server, choose single-server as the installation type when you run
the installation program; the installation program places everything on one
machine.
Related tasks
Installing on a single server
Single-server production deployment
In this deployment, all core components reside on a single server. Supporting
functions such as DBMS, LDAP, and HTTP may be hosted on separate servers.
Unlike a demo installation, this deployment features a DBMS server, a
production-level LDAP directory, and an external HTTP server. The Workplace
server hosts IBM Workplace Collaboration Services products and any supplemental
servers needed for IBM Workplace Collaborative Learning and IBM Workplace
Messaging components. In such a deployment, you install all prerequisite software,
install the Workplace Collaboration Services software itself, and then configure the
Chapter 1 Planning a deployment
31
servers for production use. An external HTTP server directs HTTP requests as
needed from clients and acts as a rich client provisioning server and Learning
content server. In this deployment, the remote HTTP servers must be in the same
Internet DNS domain as the Workplace server.
The following figure illustrates how software could be distributed in a
single-server production deployment. Variations to this configuration include:
v Hosting DBMS, LDAP and/or HTTP servers on the same server with Workplace
Collaboration Services (suitable for an i5/OS environment or a single-server
environment).
v Hosting the DBMS server and LDAP directory on the same server to reduce the
number of machines needed.
Related concepts
Installation scenarios
Related tasks
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows
Sequence of operations for i5/OS
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows:
In a single-server installation, you install IBM Workplace Collaboration Services
and then configure the product to work with external servers.
Follow these steps to install a single Workplace server and, optionally, to configure
it to work with a DBMS, LDAP, or HTTP server.
1. Verify that you have planned your installation.
Refer to the Administrator Names and Passwords worksheet if you filled it
out.
2. (Optional) To use an external DBMS server, do the following. Otherwise,
proceed to the next step.
a. Install the DBMS server (IBM DB2, SQL, or Oracle).
32
Installation and Upgrade Guide
b. Install the DBMS client.
3. (Optional) To use an external HTTP server, install the HTTP server.
4. Prepare to run the installation program.
5. Install Workplace Collaboration Services from a DVD (recommended), CDs, or
downloadable e-images. Choose Single-server as the installation type.
Note: The server must be in the same Internet DNS domain as the external
HTTP server if you plan to use an external HTTP server.
6. (Optional) To use an LDAP directory, configure the Workplace server to work
with an LDAP directory. Otherwise, proceed to the next step.
7. (Optional) To use an external DBMS server, do the following. Otherwise,
proceed to the next step.
a. Create the Workplace Collaboration Services database
b. Transfer data from IBM Cloudscape to a new database by running the
Configuration Wizard for each of these operations:
v IBM Workplace Setup Database
v Transfer Data to another database
v IBM Workplace Database Transfer
8. (Optional) To use an external HTTP server, connect Workplace Collaboration
Services to a remote HTTP server. Otherwise, proceed to the next step.
9. If you installed IBM Workplace Collaborative Learning, finish setting it up.
10. (Optional) To use your server as a rich client provisioning server, install and
configure the IBM Workplace Collaboration Services rich client provisioning
server.
Related concepts
Single-server production deployment
Optional post-installation tasks
Sequence of operations for i5/OS:
In a single-server installation, you install IBM Workplace Collaboration Services
and then configure the product to work with external servers.
Follow these steps to install a Workplace server for i5/OS and configure it to work
with a DBMS, LDAP, and HTTP server.
1. Verify that you have planned your installation.
Refer to the Administrator Names and Passwords worksheet if you filled it
out.
2. Install WAS V5.0 Enterprise Enablement.
3. If you are installing the rich client and plan to use the Create IBM Workplace
Collaboration Services wizard (recommended), prepare your system for rich
client installation.
4. Install Workplace Collaboration Services from a DVD (recommended), CDs, or
downloadable e-images. Choose Single-server as the installation type.
Note: The server must be in the same Internet DNS domain as the external
HTTP server if you plan to use an external HTTP server.
5. Configure Workplace Collaboration Services in one of these ways:
v (Recommended) Run the Create IBM Workplace wizard to configure some,
or all, components.
Chapter 1 Planning a deployment
33
The Create IBM Workplace Collaboration Services wizard configures a DB2
server and a local HTTP server automatically. If you use the Create
Workplace Collaboration Services wizard to configure all components, skip
the remaining steps.
v Configure Workplace Collaboration Services manually.
Proceed to Steps 6-11 to configure Workplace Collaboration Services
manually.
6. Configure Virtual Network Computing.
7. To use an LDAP directory, configure the Workplace server to work with an
LDAP directory. Otherwise, proceed to the next step.
8. Transfer data from Cloudscape to DB2 for iSseries by running the
Configuration Wizard for each of these operations:
v IBM Workplace Setup Database
v Transfer Data to another database
v IBM Workplace Database Transfer
9. To use an external HTTP server, connect Workplace Collaboration Services to a
remote HTTP server. Otherwise, proceed to the next step.
10. If you installed IBM Workplace Collaborative Learning, finish setting it up.
11. To use your server as a rich client provisioning server, install and configure
the IBM Workplace Collaboration Services rich client provisioning server.
Related concepts
Single-server production deployment
Optional post-installation tasks
Network Deployment
The IBM WebSphere Application Server Network Deployment is the only
configuration suitable for an enterprise environment running on AIX, Linux,
Windows, or Solaris platforms, because it is scalable and eliminates single points of
failure. It is not supported in an i5/OS environment.
The Network Deployment is comprised of multiple WebSphere Application Servers
managed as a single domain, called a cell. Cells are managed by the Deployment
Manager, which usually resides on its own server. In this deployment, you install
the various software components required for Workplace Collaboration Services on
separate servers, and use WebSphere Application Server Network Deployment
technology to group and manage the Workplace servers. External HTTP servers
direct HTTP requests as needed from clients and act as rich client provisioning
servers and Learning content servers. A Network Dispatcher Edge Server is
required for balancing HTTP requests and SIP services (used for instant messaging
and Web conferences) among the nodes.
The following figure illustrates how software could be distributed in a Network
Deployment.
Note: In this deployment, the remote HTTP servers must be in the same Internet
DNS domain as the Workplace server. In addition, for effective load
balancing, the nodes, the HTTP servers, the Network Dispatcher, and the
Deployment Manager must all be in the same subnet.
34
Installation and Upgrade Guide
Related concepts
Installation scenarios
Related tasks
Network Deployment installation and configuration road map
Network Deployment installation and configuration road map:
In a Network Deployment on IBM AIX, Linux, Sun Solaris, or Microsoft Windows,
you run the IBM Workplace Collaboration Services installation program on every
server in the deployment except on the LDAP server, the DBMS server, and the
external HTTP server. You then join each Workplace server to the deployment node
and create a cluster of Workplace servers. The instructions assume that you are
setting up the recommended configuration that connects Workplace Collaboration
Services to separate DBMS, LDAP, and HTTP servers.
IBM i5/OS does not offer a Network Deployment environment.
You cannot install Workplace Collaboration Services on a WebSphere node that is
already part of a Network Deployment. You must instead install and configure
Workplace Collaboration Services on multiple standalone servers, and then add (or
″federate″) each of these servers to the Network Deployment environment.
Preparation:
Verify that you have completed these steps before proceeding.
1. Verify that you have planned your installation (Phase 1).
2. Verify that you have filled out the Administrator Names and Passwords
worksheet.
Sequence of operations:
The rest of this topic shows you the tasks needed for each server in the Network
Deployment. Follow the steps shown below for each of the servers, rather than
following the numbered phases. Pay close attention to the order in which to
complete each task and ensure that you have fulfilled any prerequisite tasks on
Chapter 1 Planning a deployment
35
another server before continuing. You may also want to use the Network
Deployment installation checklist to track your progress.
For more information, see the sections that follow for each type of server in the
Network Deployment environment:
v Network Dispatcher
v Deployment Manager
v DBMS server
v LDAP Directory server
v HTTP server
v Node 1
v Node 2 and all subsequent nodes
Network Dispatcher:
Perform these steps on the Network Dispatcher to set up load balancing for SIP
services and HTTP.
1. Install the WebSphere Application Server Edge components (Phase 2).
2. Set up the HTTP server, the rich client provisioning server, the DBMS server,
the LDAP server, and all nodes before continuing. For more information about
these tasks, see other sections in this topic.
3. As part of completing Network Deployment setup, configure load balancing for
SIP services and HTTP (Phase 9).
Deployment Manager:
Perform these steps on the Deployment Manager.
1. On the server that will be the Deployment Manager or on a separate file
server create shared directories for Workplace servers to use (Phase 2).
2. Install the Deployment Manager software (Phase 2).
3. Before continuing work on the Deployment Manager, install and set up the
back-end systems (HTTP, DBMS, LDAP). Then install Workplace Collaboration
Services on Node 1 and connect it to the external servers. For more
information, see other sections in this topic.
4. Install the DBMS client.
5. Enable LDAP security on the Deployment Manager by copying values from
Node 1 (Phase 3).
6. Prepare to run the installation program and then install Workplace
Collaboration Services from a DVD (recommended), CDs, or downloadable
e-images. Choose Network Deployment as the installation type and
Deployment Manager as the server type (Phase 3).
7. Federate Node 1 to the Network Deployment cell.
8. Create the Workplace Collaboration Services cluster and add Node 1 to the
cluster. Save the cluster information (Phase 3).
9. Update the Deployment Manager with node information (Phase 3).
10. On the Deployment Manager, define URLs for downloading and provisioning
the rich client using an external HTTP Server.
Perform this step after federating the first node and creating the cluster.
11. Federate Node 2.
12. Update the Deployment Manager with cluster information (Phase 3).
36
Installation and Upgrade Guide
13. Complete setup of Workplace Collaborative Learning on the nodes before
continuing.
14. Complete setup of the Network Deployment environment on the Deployment
Manager:
v Enable dynamic caching for the nodes.
v Distribute embedded messaging files.
v Apply fix packs to the Network Deployment servers.
LDAP Directory server:
Prepare the LDAP directory and then connect the nodes. Instructions differ for
each type of LDAP directory:
v IBM Tivoli Directory Server
v Domino Directory
v Microsoft Active Directory
v Sun Java System Directory Server
v Novell eDirectory
DBMS server:
Prepare the DBMS server (described in Phase 2).
Install the DBMS server (DB2, SQL, or Oracle).
HTTP server:
Set up a remote HTTP server or servers.
Note: The Network Deployment nodes must be in the same Internet DNS domain
as the external HTTP server.
1. Complete Steps 1 and 2 on the Deployment Manager before starting.
2. Install the HTTP server (described in Phase 2).
3. Complete installation and setup of the Deployment Manager and nodes before
continuing.
4. Set up the external HTTP server for use with Workplace Collaboration Services
and the rich client provisioning server (described in Phase 6). When you install
the rich client provisioning server on the HTTP server, use a custom installation
and select Update bundles and Installation files to be installed. Then when
you install the rich client provisioning server on Node 1, deselect Update
bundles and Installation files .
5. Configure help for the Collaborative Learning administrator interface for AIX,
Linux, Solaris, or Microsoft Windows or i5/OS.
6. Complete setup of the Network Deployment and verify that the Workplace
server cluster is operational before continuing.
7. After you have federated the nodes and created a cluster, update rich client
configuration files for Network Deployment.
Node 1:
Perform these steps on Node 1. Follow this sequence of steps, rather than
following the numbered phases, to install Workplace Collaboration Services in a
Chapter 1 Planning a deployment
37
Network Deployment environment. The steps assume the recommended
configuration that connects Workplace Collaboration Services to separate DBMS,
LDAP, and HTTP servers.
Note: In a Network Deployment environment, you must install the rich client
provisioning server on Node 1 in the middle of Phase 3 (Installing IBM
Workplace Collaboration Services) as shown in the following procedure. Do
not wait until Phase 8 to perform this step. Provisioning server installation
must be performed prior to federating. The provisioning server cannot be
installed on any other node in the cluster, only on the first node (Node 1) to
be federated.
Note: The Network Deployment nodes must be in the same Internet DNS domain
as the external HTTP server.
1. Before starting, you must have done the following:
v Completed Steps 1 and 2 on the Deployment Manager (create shared
directories and install the Deployment Manager software).
v Prepared the DBMS server.
v Prepared the Network Dispatcher.
2. Install the DBMS client (Phase 2).
3. Prepare to run the installation program, then install Workplace Collaboration
Services from a DVD (recommended), CDs, or downloadable e-images.
Choose Network Deployment as the installation type and Node as the server
type (Phase 3).
4. Configure Node 1 to work with an LDAP directory (Phase 4).
5. (Oracle) Add WebSphere Portal users to the Oracle database.
6. Transfer data from IBM Cloudscape to a new database by running each of
these Configuration Wizard operations in turn (Phase 5):
v IBM Workplace Setup Database
v Transfer data to another database
v IBM Workplace database transfer
7. Before continuing, install the rich client provisioning server on this server and
on the HTTP server. On Node 1, use a custom installation and deselect
Update bundles and Installation files. When you install the rich client
provisioning server on the HTTP server, select Update bundles and
Installation files to be installed on the HTTP server.
8. Connect the node to the external HTTP server.
Perform this step on Node 1 before federating the node.
9. Connect the Learning servers to the external HTTP server.
Perform this step on Node 1 before federating the node.
10.
v Update the WebSphere Portal EAR file.
v On the Deployment Manager, federate the node and add it to the cluster
before continuing.
v Grant Learning access to the WebSphere Portal administrator.
v Connect Collaborative Learning portlets to a remote Learning Server.
v Set up access control for Collaborative Learning portlets.
v Enable reporting on IBM AIX, Linux, Sun Solaris, and i5/OS.
In a Network Deployment environment, do this on Node 1 and all
subsequent nodes.
38
Installation and Upgrade Guide
11. Complete setup of the Network Deployment environment on Node 1:
v Enable Search in the cluster.
v Distribute embedded messaging files.
v Edit WebSphere settings for a Network Deployment.
v Apply fix packs to the Network Deployment servers.
Node 2 and all subsequent nodes:
Perform these steps on Node 2 and all subsequent nodes. Follow this sequence of
steps, rather than following the numbered phases, to install Workplace
Collaboration Services in a Network Deployment environment. The steps assume
the recommended configuration that connects Workplace Collaboration Services to
separate DBMS, LDAP, and HTTP servers.
1. Install the DBMS client (Phase 2).
2. Prepare to run the installation program, then install Workplace Collaboration
Services from a DVD (recommended), CDs, or downloadable e-images.
Choose Network Deployment as the installation type and Node as the server
type (Phase 3).
3. Before continuing, enable LDAP security on the Deployment Manager.
4. Configure Node 2 to work with an LDAP directory (Phase 4).
5. Connect Node 2 to the remote database each of these Configuration Wizard
operations in turn (Phase 5):
v Connect to a database
v IBM Workplace Connection to database
6. Copy files and directories from Node 1 to the new node.
7. Connect Workplace and Learning servers to the external HTTP server.
Perform this step on Node 2 before federating the node.
8. On the Deployment Manager, federate the node to the cell and add it to the
cluster before continuing.
9. Complete setup of Workplace Collaborative Learning on Node 2:
v Enable reporting on IBM AIX, Linux, Sun Solaris, and i5/OS.
10. Complete setup of the Network Deployment environment on Node 2:
v Enable Search in the cluster.
v Distribute embedded messaging files.
v Edit WebSphere settings for a Network Deployment.
v Apply fix packs to the Network Deployment servers.
Related concepts
Network Deployment scenario
Related tasks
Network Deployment installation checklist
Related reference
Root installation directories
Network Deployment installation checklist:
Use the following table to help you track your work as you set up IBM Workplace
Collaboration Services in a Network Deployment environment. The order in which
you complete tasks in a Network Deployment environment is critical. Complete all
Chapter 1 Planning a deployment
39
items in a row before working on items in a subsequent row. Tasks on the same
row can be done simultaneously for faster setup. Time estimates are based on an
AIX deployment.
Other servers (such as DBMS, HTTP, LDAP and Network Dispatcher servers) also
comprise a Network Deployment environment. For more information, see the
Network Deployment installation and configuration road map.
Task
Deployment
Manager
Node 1
Baseline Install DM and Install
necessary
operating
patches
system and
necessary
patches
Node 2
Node 3
Node 4
Install
operating
system and
necessary
patches
Install
operating
system and
necessary
patches
Install
operating
system and
necessary
patches
Install
DBMS
client
(nodes)
Install DBMS
client
Install DBMS
client
Install DBMS
client
Install DBMS
client
Install
Workplace
Collaboration
Services
(~ 2 hours)
Install
Workplace
Collaboration
Services
(~ 2 hours)
Install
Workplace
Collaboration
Services
(~ 2 hours)
Install
Workplace
Collaboration
Services
(~ 2 hours)
Install
Workplace
Collaboration
Services
Perform Perform
backup backup
Perform
backup
Perform
backup
Perform
backup
Perform
backup
Disable
security
(~ 40 minutes)
Disable LDAP
security
(~ 40 minutes)
Disable LDAP
security
(~ 40 minutes)
Disable LDAP
security
(~ 40 minutes)
Disable LDAP
security
Enable
LDAP
security
(nodes)
(~ 1 hour)
Enable LDAP
security
(~ 1 hour)
Enable LDAP
security
(~ 1 hour)
Enable LDAP
security
(~ 1 hour)
Enable LDAP
security
(~ 45 minutes)
Connect to
database
(~ 45 minutes)
Connect to
database
Enable Enable LDAP
LDAP
security
security
(DM)
Perform
database
transfer
(Node
1)
(~ 1 hour, 30
minutes)
Perform
database
transfer
Connect
to
database
(Nodes
2 and
above)
DO NOT
(~ 45 minutes)
TOUCH until Connect to
specified since database
you could
cause database
corruption
Install
DBMS
client
(DM)
40
Installation and Upgrade Guide
Install DBMS
client
Task
Deployment
Manager
Node 1
Product Install
installation
Workplace
on DM Collaboration
Services.
(Choose
Deployment
Manager
option. This
also connects
to database.)
At this
point
DO
NOT
TOUCH
ANY
NODE
BUT
NODE
1
Node 2
Node 3
Node 4
DO NOT
TOUCH until
specified since
you could
cause database
corruption
DO NOT
TOUCH until
specified since
you could
cause database
corruption
DO NOT
TOUCH until
specified since
you could
cause database
corruption
Connect to
HTTP server
Connect to
HTTP server
Connect to
HTTP server
DO NOT
TOUCH until
specified since
you could
cause database
corruption
Configure
HTTP
Configure
HTTP for
plug-in and
verify product
installation
Test
(optional)
Test HTTP
plug-in
Install
rich
client
provisioning
server
(~ 1 hour)
Install and
configure the
provisioning
server
Connect
nodes
to
external
HTTP
server
Connect to
HTTP server
Complete
Workplace
Collaborative
Learning
setup
Complete
Workplace
Collaborative
Learning setup
(if installed)
Configure
policies
Configure
policies to
determine who
has access to
server
Configure
mail
Determine
domains for
mail routing.
Chapter 1 Planning a deployment
41
Task
Deployment
Manager
Node 1
Node 2
Node 3
Node 4
Perform
backup
Perform
backup
Perform
backup
Copy
files
from
Node 1
Copy files
from Node 1
Copy files
from Node 1
Copy files
from Node 1
Federate
Federate Node
2
Deploy
themes
and
skins
for rich
client
Update
WebSphere
Portal EAR file
Test
(recommended)
At this point,
you should be
able to log in
and use all
features.
Debug any
problems
before moving
on.
Perform Perform
backup backup
Perform
backup
Federate
Federate Node
1
Create
cluster
Add Node 1 to
cluster
Test
Start Node 1
(optional)
Add to
cluster
Start Node
Agent
Add Node 2 to
cluster
Test
Stop Node 1
Stop Node
(optional)and start Node Agent
2
Start Node
Agent
Test
Start all nodes
(optional)
Start Node
Agent
Start Node
Agent
Federate Node
3
Federate
Add to
cluster
Add Node 3 to
cluster
Test
Stop Nodes 1
(optional)and 2; start
Node 3
Stop Node
Agent
Stop Node
Agent
Start Node
Agent
Test
Start all nodes
(optional)
Start Node
Agent
Start Node
Agent
Start Node
Agent
Federate Node
4
Federate
Add to
cluster
42
Installation and Upgrade Guide
Add Node 4 to
cluster
Task
Deployment
Manager
Node 1
Node 2
Node 3
Node 4
Test
Stop Nodes 1,
(optional)2, and 3; start
Node 4
Stop Node
Agent
Stop Node
Agent
Stop Node
Agent
Start Node
Agent
Test
Start all nodes
(optional)
Start Node
Agent
Start Node
Agent
Start Node
Agent
Start Node
Agent
Enable Enable
dynamic dynamic
caching caching
Enable
dynamic
caching
Enable
dynamic
caching
Enable
dynamic
caching
Enable
dynamic
caching
Enable Search
Enable Search
Enable Search
Enable Search
Enable Enable
MessagingMessaging
Enable
Messaging
Enable
Messaging
Enable
Messaging
Enable
Messaging
Edit
Edit
WebSphere
WebSphere
settings settings
Edit
WebSphere
settings
Edit
WebSphere
settings
Edit
WebSphere
settings
Edit
WebSphere
settings
Apply fix
packs
Apply fix
packs
Apply fix
packs
Apply fix
packs
Enable
Search
Apply
fix
packs
Enable Search
Apply fix
packs
Related tasks
Network Deployment installation and configuration road map
Chapter 1 Planning a deployment
43
44
Installation and Upgrade Guide
Chapter 2 Preparing the Environment
This chapter describes how to set up prerequisite software and servers needed for
the IBM Workplace Collaboration Services installation.
Setting up a Network Deployment environment
In a Network Deployment environment, make these preparations before installing
IBM Workplace Collaboration Services:
v Create shared Workplace Collaboration Services directories.
v Install the Deployment Manager.
v Install WebSphere Application Server Edge components.
A Network Deployment environment also uses a Database Management System
and an external HTTP server.
Related concepts
Setting up the environment
Setting up a Network Deployment environment
In a Network Deployment environment, make these preparations before installing
IBM Workplace Collaboration Services:
v Create shared Workplace Collaboration Services directories.
v Install the Deployment Manager.
v Install WebSphere Application Server Edge components.
A Network Deployment environment also uses a Database Management System
and an external HTTP server.
Related concepts
Setting up the environment
Creating shared directories for a Network Deployment
To allow IBM Workplace Collaboration Services to function properly, several
directories must be accessible to all nodes in the deployment. These directories
may be created on the Deployment Manager or a separate file server that all nodes
can access.
1. Create the main shared directory, for example, q:\NDShares.
2. Create the following directories under the main shared directory:
v qfilestore
v lms_courses
v lms_juru
v content (required for IBM Workplace Collaborative Learning if you do not
use the FTP method for course transfer)
v WPCPIndex
Next, continue preparing the Network Deployment environment by installing the
Deployment Manager software.
© Copyright IBM Corp. 2002, 2005
45
Related tasks
Installing the Deployment Manager
Related reference
Learning settings in the dbbuild.properties file
Installing the Deployment Manager
A Network Deployment cell is a group of servers (known as nodes) that are
managed by a special WebSphere Application Server called the Deployment
Manager. Unlike the nodes in an IBM Workplace server installation, the
Deployment Manager does not use WebSphere Portal software.
In a Network Deployment, you designate one server as the Deployment Manager,
which should be a dedicated system. It hosts the WebSphere Administrative
Console and provides a single point of administrative control for all elements in
the WebSphere Application Server cell.
This section describes how to install the prerequisite Deployment Manager
software on the following platforms:
v IBM AIX
v Linux
v Sun Solaris
v Microsoft Windows
Related tasks
Setting up a Network Deployment environment
Installing the Deployment Manager on IBM AIX:
This topic describes how to install the Deployment Manager software on IBM AIX
by following these steps:
1. Install the base version of Deployment Manager.
2. Install the enterprise version of Deployment Manager.
3. Apply fix packs to the Deployment Manager.
4. Verify installation.
CD list:
The following table lists the CDs needed for the Deployment Manager installation.
IBM AIX
Base version 5.0
CD 1-17
Enterprise version 5.0
CD 1-5
Base version 5.0.2 fix pack
CD 1-18
Enterprise version 5.0.2 fix pack
CD 1-10
Base version 5.0.2.6 fix pack
CD 1-18
Enterprise version 5.0.2.6 fix pack
Cumulative Fix 6 CD
Installing the base version of Deployment Manager:
To install the base version of WebSphere Application Server Deployment Manager,
perform the following steps.
46
Installation and Upgrade Guide
For more information about installing the WebSphere Application Server
Deployment Manager in a WebSphere Portal cluster, see the WebSphere Portal
Information Center on the Web at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
1. Log in to the server as a user with administrative privileges.
2. Locate CD 1-17 for WebSphere Application Server Deployment Manager.
3. Run the installation program.
./<cd_root>/wasnd/<operating_system>/<platform>/install
where:
<cd_root> is the root directory of the CD.
4. When selecting the features for the ″IBM WebSphere Application Server
Network Deployment Version 5,″ select Deployment Manager.
5. When typing the node, host, and cell names, the host name is the name of the
server on which you are installing the Network Deployment Edition. To form
the node and cell names, append the words ″Manager″ and ″Network″
respectively, to the host name. For example:
Node name: acmeManager
Host name: acme
Cell name: acmeNetwork
6. Complete the installation as directed.
Installing the enterprise version of Deployment Manager:
To install the enterprise version of WebSphere Application Server Deployment
Manager, perform the following steps.
1. Locate CD 1-5 for WebSphere Application Server Version 5.0 Enterprise Edition.
2. Run the installation program.
./<cd_root>/was/<operating_system>/<platform>/install
The WebSphere Application Server Enterprise installation program
automatically detects the existing Network Deployment installation and
provides the option to extend it with the Enterprise extensions.
3. Complete the installation as directed.
4. Make a “backup” image of your system at this point so you can revert to it if
needed during the fix packs’ installation.
Applying fix packs to the Deployment Manager:
After installing the base version of the Deployment Manager software, use the
update wizard to apply the following fix packs in turn to bring the software to the
level required for IBM Workplace Collaboration Services installation.
Network Deployment fix packs for AIX:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-18
v Enterprise second fix pack level (Version 5.0.2), CD 1-10
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-18
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6), WebSphere
Application Server Enterprise Enablement Cumulative Fix 6 CD
Verifying installation:
Chapter 2 Preparing the Environment
47
When you are done, verify that you can open the WebSphere Administrative
console, then make a “backup” image of your system at this point so you can
revert to it if needed.
Refer to the Network Deployment installation and configuration road map for
information about your next step.
Related tasks
Opening the WebSphere Administrative Console
Network Deployment installation and configuration road map
Installing the Deployment Manager
Setting up a Network Deployment environment
Installing the Deployment Manager on Linux:
This topic describes how to install the Deployment Manager software on Linux by
following these steps:
1. Install the base version of Deployment Manager.
2. Install the enterprise version of Deployment Manager.
3. Apply fix packs to the Deployment Manager.
4. Verify installation.
CD list:
The following table lists the CDs needed for the Deployment Manager installation.
Linux
Base version 5.0
CD 1-14
Enterprise version 5.0
CD 1-3
Base version 5.0.2 fix pack
CD 1-19
Enterprise version 5.0.2 fix pack
CD 1-8
Base version 5.0.2.6 fix pack
CD 1-19
Enterprise version 5.0.2.6 fix pack
Cumulative Fix 6 CD
Installing the base version of Deployment Manager:
To install the base version of WebSphere Application Server Deployment Manager,
perform the following steps.
For more information about installing the WebSphere Application Server
Deployment Manager in a WebSphere Portal cluster, see the WebSphere Portal
Information Center on the Web at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
1. Log in to the server as a user with administrative privileges.
2. Locate CD 1-14 for WebSphere Application Server Deployment Manager.
3. Run the installation program.
./<cd_root>/wasnd/<operating_system>/<platform>/install
where:
<cd_root> is the root directory of the CD.
4. When selecting the features for the ″IBM WebSphere Application Server
Network Deployment Version 5,″ select Deployment Manager.
48
Installation and Upgrade Guide
5. When typing the node, host, and cell names, the host name is the name of the
server on which you are installing the Network Deployment Edition. To form
the node and cell names, append the words ″Manager″ and ″Network″
respectively, to the host name. For example:
Node name: acmeManager
Host name: acme
Cell name: acmeNetwork
6. Complete the installation as directed.
Installing the enterprise version of Deployment Manager:
To install the enterprise version of WebSphere Application Server Deployment
Manager, perform the following steps.
1. Locate CD 1-5 for WebSphere Application Server Version 5.0 Enterprise Edition.
2. Run the installation program.
./<cd_root>/was/<operating_system>/<platform>/install
The WebSphere Application Server Enterprise installation program
automatically detects the existing Network Deployment installation and
provides the option to extend it with the Enterprise extensions.
3. Complete the installation as directed.
4. Make a “backup” image of your system at this point so you can revert to it if
needed during the fix packs’ installation.
Applying fix packs to the Deployment Manager:
After installing the base version of the Deployment Manager software, use the
update wizard to apply the following fix packs in turn to bring the software to the
level required for IBM Workplace Collaboration Services installation.
Network Deployment fix packs for Linux:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-19
v Enterprise second fix pack level (Version 5.0.2), CD 1-8
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-19
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6), WebSphere
Application Server Enterprise Enablement Cumulative Fix 6 CD
Verifying installation:
When you are done, verify that you can open the WebSphere Administrative
console, then make a “backup” image of your system at this point so you can
revert to it if needed.
Next, set up the LDAP, DBMS, HTTP servers and install Workplace Collaboration
Services on the first node. You will then enable LDAP security on the Deployment
Manager before installing Workplace Collaboration Services on the Deployment
Manager.
Related tasks
Opening the WebSphere Administrative Console
Network Deployment installation and configuration road map
Installing the Deployment Manager
Setting up a Network Deployment environment
Installing the Deployment Manager on Sun Solaris:
Chapter 2 Preparing the Environment
49
This topic describes how to install the Deployment Manager software on Sun
Solaris by following these steps:
1. Install the base version of Deployment Manager.
2. Install the enterprise version of Deployment Manager.
3. Apply fix packs to the Deployment Manager.
4. Verify installation.
CD list:
The following table lists the CDs needed for the Deployment Manager installation.
Sun Solaris
Base version 5.0
CD 1-12
Enterprise version 5.0
CD 1-6
Base version 5.0.2 fix pack
CD 1-18
Enterprise version 5.0.2 fix pack
CD 1-11
Base version 5.0.2.6 fix pack
CD 1-18
Enterprise version 5.0.2.6 fix pack
Cumulative Fix 6 CD
Installing the base version of Deployment Manager:
To install the base version of WebSphere Application Server Deployment Manager,
perform the following steps.
For more information about installing the WebSphere Application Server
Deployment Manager in a WebSphere Portal cluster, see the WebSphere Portal
Information Center on the Web at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
1. Log in to the server as a user with administrative privileges.
2. Locate CD 1-12 for WebSphere Application Server Deployment Manager.
3. Run the installation program.
./<cd_root>/wasnd/<operating_system>/<platform>/install
where:
<cd_root> is the root directory of the CD.
4. When selecting the features for the ″IBM WebSphere Application Server
Network Deployment Version 5,″ select Deployment Manager.
5. When typing the node, host, and cell names, the host name is the name of the
server on which you are installing the Network Deployment Edition. To form
the node and cell names, append the words ″Manager″ and ″Network″
respectively, to the host name. For example:
Node name: acmeManager
Host name: acme
Cell name: acmeNetwork
6. Complete the installation as directed.
Installing the enterprise version of Deployment Manager:
To install the enterprise version of WebSphere Application Server Deployment
Manager, perform the following steps.
1. Locate CD 1-6 for WebSphere Application Server Version 5.0 Enterprise Edition.
50
Installation and Upgrade Guide
2. Run the installation program.
./<cd_root>/was/<operating_system>/<platform>/install
The WebSphere Application Server Enterprise installation program
automatically detects the existing Network Deployment installation and
provides the option to extend it with the Enterprise extensions.
3. Complete the installation as directed.
4. Make a “backup” image of your system at this point so you can revert to it if
needed during the fix packs’ installation.
Applying fix packs to the Deployment Manager:
After installing the base version of the Deployment Manager software, use the
update wizard to apply the following fix packs in turn to bring the software to the
level required for IBM Workplace Collaboration Services installation.
Network Deployment fix packs for Solaris:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-18
v Enterprise second fix pack level (Version 5.0.2), CD 1-11
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-18
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6), WebSphere
Application Server Enterprise Enablement Cumulative Fix 6 CD
Verifying installation:
When you are done, verify that you can open the WebSphere Administrative
console, then make a “backup” image of your system at this point so you can
revert to it if needed.
Next, set up the LDAP, DBMS, HTTP servers and install Workplace Collaboration
Services on the first node. You will then enable LDAP security on the Deployment
Manager before installing Workplace Collaboration Services on the Deployment
Manager.
Related tasks
Opening the WebSphere Administrative Console
Network Deployment installation and configuration road map
Installing the Deployment Manager
Setting up a Network Deployment environment
Installing the Deployment Manager on Microsoft Windows:
This topic describes how to install the Deployment Manager software on Microsoft
Windows by following these steps:
1. Install the base version of Deployment Manager.
2. Install the enterprise version of Deployment Manager.
3. Apply fix packs to the Deployment Manager.
4. Verify installation.
CD list:
Chapter 2 Preparing the Environment
51
The following table lists the CDs needed for the Deployment Manager installation.
Windows 2000
Windows 2003
Base version 5.0
CD 1-13
CD 1-15
Enterprise version 5.0
CD 1-1
CD 1-2
Base version 5.0.2 fix pack
CD 1-19
CD 1-19
Enterprise version 5.0.2 fix
pack
CD 1-19
CD 1-19
Base version 5.0.2.6 fix pack
CD 1-7
CD 1-7
Enterprise version 5.0.2.6 fix
pack
Cumulative Fix 6 CD
Cumulative Fix 6 CD
Installing the base version of Deployment Manager:
To install the base version of WebSphere Application Server Deployment Manager,
perform the following steps.
For more information about installing the WebSphere Application Server
Deployment Manager in a WebSphere Portal cluster, see the WebSphere Portal
Information Center on the Web at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
1. Log in to the server as a user with administrative privileges.
2. Locate the CD for WebSphere Application Server Deployment Manager.
Windows 2000
CD 1-13 (Version 5.0)
Windows 2003
CD 1-15 (Version 5.0.2)
3. Run the installation program.
Windows
<cd_root>\wasnd\win\nt\launchpad.bat
where:
<cd_root> is the root directory of the CD.
4. When selecting the features for the ″IBM WebSphere Application Server
Network Deployment Version 5,″ select Deployment Manager.
5. When typing the node, host, and cell names, the host name is the name of the
server on which you are installing the Network Deployment Edition. To form
the node and cell names, append the words ″Manager″ and ″Network″
respectively, to the host name. For example:
Node name: acmeManager
Host name: acme
Cell name: acmeNetwork
6. Complete the installation as directed.
Installing the enterprise version of Deployment Manager:
To install the enterprise version of WebSphere Application Server Deployment
Manager, perform the following steps.
1. Locate the CD for WebSphere Application Server Version 5.0 Enterprise Edition.
Windows 2000
CD 1-1 (Version 5.0)
52
Installation and Upgrade Guide
Windows 2003
CD 1-2 (Version 5.0.2)
2. Run the installation program.
Windows
<cd_root>\was\win\install.bat
The WebSphere Application Server Enterprise installation program
automatically detects the existing Network Deployment installation and
provides the option to extend it with the Enterprise extensions.
3. Complete the installation as directed.
4. Make a “backup” image of your system at this point so you can revert to it if
needed during the fix packs’ installation.
Applying fix packs to the Deployment Manager:
After installing the base version of the Deployment Manager software, use the
update wizard to apply the following fix packs in turn to bring the software to the
level required for IBM Workplace Collaboration Services installation.
Network Deployment fix packs for Windows:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-19
v Enterprise second fix pack level (Version 5.0.2), CD 1-7
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-19
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6), WebSphere
Application Server Enterprise Enablement Cumulative Fix 6 CD
Verifying installation:
When you are done, verify that you can open the WebSphere Administrative
console, then make a “backup” image of your system at this point so you can
revert to it if needed.
Next, set up the LDAP, DBMS, HTTP servers and install Workplace Collaboration
Services on the first node. You will then enable LDAP security on the Deployment
Manager before installing Workplace Collaboration Services on the Deployment
Manager.
Related tasks
Opening the WebSphere Administrative Console
Network Deployment installation and configuration road map
Installing the Deployment Manager
Setting up a Network Deployment environment
Installing WebSphere Application Server Edge components
In a Network Deployment environment, you must install WebSphere Application
Server Edge components to set up load balancing for instant messaging and Web
conferences. The standalone machine you use as the load balancer is called a
Network Dispatcher. You should also use the Network Dispatcher to load-balance
HTTP requests across the network.
Prerequisites:
Keep the following prerequisites in mind:
Chapter 2 Preparing the Environment
53
v Network nodes must be on the same subnet as the Network Dispatcher.
v To load balance HTTP requests, the HTTP server must also be on the same
subnet.
v (Recommended) Install the same operating system version and patches on all
nodes in the cluster.
v The nodes that are being balanced must be configured with a loopback adapter.
Refer to the Edge server documentation at http://www306.ibm.com/software/webservers/appserv/ecinfocenter.html for instructions
pertinent to your operating system.
Installing Edge components:
Workplace Collaboration Services comes with the Microsoft Windows 2003 version
of Edge components on CDs 1-21 and 1-22. For more information about the
installation and configuration of Edge components, see the Edge components
Information Center at http://www306.ibm.com/software/webservers/appserv/ecinfocenter.html. Refer to the Load
Balancer Administration Guide for detailed installation instructions.
Applying a fix pack to the base 5.0 installation:
If you have version 5.0 of the WebSphere Application Server Edge Components,
upgrade to version 5.0.2, using the appropriate Edge Components fix pack CD
provided with Workplace Collaboration Services.
IBM AIX
Linux
Sun Solaris
Microsoft Windows
CD 1-26
CD 1-25
CD 1-27
CD 1-25
Related concepts
Network Deployment scenario
Related tasks
Network Deployment installation and configuration road map
Phase 2: Setting up the environment
Configuring load balancing for instant messaging and Web conferences
Setting up an i5/OS environment
In an IBM i5/OS environment, make these preparations before installing
Workplace Collaboration Services:
v Install WAS V5.0 Enterprise Enablement.
v If you are installing the rich client and plan to use the Create IBM Workplace
Collaboration Services wizard (recommended), prepare your system for rich
client setup.
Related concepts
Phase 2: Setting up the environment
Installing WebSphere Application Server V5.0 Enterprise
Enablement (i5/OS only)
IBM Workplace Collaboration Services requires functionality that is not available
with standard versions of WebSphere Application Server on IBM i5/OS. To add
this functionality, you must install IBM Enterprise Enablement for WebSphere
Application Server for iSeries (WebSphere Application Server V5.0 Enterprise
Enablement).
54
Installation and Upgrade Guide
Before installing WebSphere Application Server V5.0 Enterprise Enablement, you
must have the following software installed:
Program
Option
5722SS1
Description
i5/OS V5R3
5733WS5
*BASE
WebSphere Application Server V5.0
5733WS5
2
WebSphere Application Server V5.0
Application server runtime
To install WebSphere Application Server V5.0 Enterprise Enablement from a
workstation connected to your server:
1. If your WebSphere Application Server subsystem is running, end it by entering
the following command on an i5/OS command line: ENDSBS SBS(QEJBAS5)
2. Insert the WebSphere Application Server V5.0 Enterprise Enablement CD into
your workstation’s CD-ROM drive. The WebSphere Application Server V5.0
Enterprise Enablement installation program will start automatically.
3. A signon screen will prompt you to enter your server name, ID, and password.
When you have entered that information, click OK.
4. Select the language for the install and click Next.
5. The WebSphere Application Server V5.0 Enterprise Enablement welcome screen
should appear. Click Next.
6. Review the license agreement. Select I accept the terms of the licensing
agreement and click Next.
7. The following screen asks which version of WebSphere Application Server V5.0
Enterprise Enablement you wish to install. Select WebSphere Application
Server V5.0 Enterprise Enablement to install the Base Edition, and click Next.
8. View the install summary information and click Next.
9. When WebSphere Application Server V5.0 Enterprise Enablement finishes
installing, the installation program will display a confirmation panel. Click
Finish.
PTF SF99282:
After you have successfully installed WAS Application Server V5.0 Enterprise
Enablement, apply the following group PTF:
Group Number
Description
Minimum Level
SF99282
WebSphere Portal
3
Express/Express Plus Service
Pack
See the following Web page on the IBM eServer iSeries Support site for instructions
on ordering PTFs:
http://www-912.ibm.com/supporthome.nsf/document/10000069
Related tasks
Phase 2: Preparing the environment
Preparing for rich client setup (i5/OS)
If you are setting up a rich client provisioning server on i5/OS, the Create IBM
Workplace Collaboration Services wizard can install and configure the rich client
Chapter 2 Preparing the Environment
55
for you. Follow these steps to enable the Create IBM Workplace Collaboration
Services wizard to install and configure the rich client.
Note: You can perform these steps at any time before using the Create IBM
Workplace Collaboration Services wizard. However, because you can launch
the wizard directly from the Workplace Collaboration Services installation
program, you may find it more convenient to perform the steps before
installing Workplace Collaboration Services.
To prepare for rich client setup with the Create IBM Workplace Collaboration
Services wizard, follow these steps:
1. Sign on to your system with a user profile that has *ALLJOB authority.
2. Start the QShell Interpreter by entering the following on an i5/OS command
line:
STRQSH
3. Create a directory to hold rich client setup files by entering the following:
mkdir -p /QIBM/ProdData/Workplace/WCT25/
4. Copy the installation directories on both rich client installation CDs to the
newly created directory:
a. Insert the first rich client CD into your system’s optical drive.
b. Change to the root directory of the optical drive by entering the following:
cd /qopt
c. Copy the first installation directory from the CD to your system by entering
the following:
cp -R WorkplaceSCI1 /QIBM/ProdData/Workplace/WCT25
d. Enter the following:
cd /qopt
e. Insert the second rich client CD into your system’s optical drive.
f. Change to the root directory of the optical drive by entering the following:
cd /qopt
g. Copy the second installation directory from the CD to your system by
entering the following:
cp -R WorkplaceSCI2 /QIBM/ProdData/Workplace/WCT25
5. Authorize the Create IBM Workplace Collaboration Services wizard to access
the setup files:
a. Change to the Workplace Collaboration Services product directory by
entering the following:
cd /QIBM/ProdData/Workplace
b. Authorize the wizard to access setup files by entering the following:
chown -R QSYS /QIBM/ProdData/Workplace/WCT25
6. Confirm that the files are in the correct location by ensuring that the following
files exist:
v /QIBM/ProdData/Workplace/WCT25/WorkplaceSCI1/data.jar
v /QIBM/ProdData/Workplace/WCT25/WorkplaceSCI2/media.inf
You can now install and configure the rich client using the Create IBM Workplace
Collaboration Services wizard, providing you are licensed to use the rich client and
selected the rich client offering during installation of Workplace Collaboration
Services.
Related tasks
56
Installation and Upgrade Guide
Starting the Create IBM Workplace Collaboration Services wizard
IBM Web Administration for IBM i5/OS includes a Create IBM Workplace
Collaboration Services wizard to help you configure all components in a
production-level environment. When you install IBM Workplace Collaboration
Services using the IBM Workplace setup wizard for i5/OS option, the final
screen of the installation program gives you the option of starting the wizard. If
starting the wizard immediately after installing Workplace Collaboration
Services is not convenient, you can also manually start it by following the
instructions below.
Setting up a Database Management System
Before you can host the IBM Workplace Collaboration Services database on a
server, you must install a supported database management system (DBMS), which
stores and manages the data.
Note: IBM DB2 Universal Database is integrated with the IBM i5/OS platform. If
you are installing IBM Workplace Collaboration Services on i5/OS, skip this
section.
Workplace Collaboration Services installs with IBM Cloudscape as its default
database. While Cloudscape is sufficient for a demo installation, you should
transfer data to a more robust database management system (DBMS) before
putting Workplace Collaboration Services into production mode.
In addition to Cloudscape, Workplace Collaboration Services supports the
following DBMS products:
v IBM DB2 Universal Database
v Oracle
v Microsoft SQL Server
Refer to the topic, ″Requirements for AIX, Linux, Solaris, and Windows,″ for
information on supported releases of these products.
You can install the DBMS server directly on the Workplace Collaboration Services
computer. If you install the DBMS on a separate computer, you must install the
associated DBMS client software on every Workplace Collaboration Services
computer to enable them to access the database as needed.
Decide which DBMS product you will use, and proceed to the topic, ″Installing the
DBMS server″.
Installing the DBMS server
You can install the database management system (DBMS) server software on the
same computer that will host IBM Workplace Collaboration Services (the database
is local), or on a separate computer (the database is remote). In a large-scale
environment, using a remote database reduces the resource usage on the server by
directing database queries to another computer. Using a separate computer for
hosting the database also allows more storage space for the data required by
Workplace Collaboration Services.
If you use the same DBMS instance with another product, make sure you create a
separate database container for use with Workplace Collaboration Services.
Before you install the DBMS server software, review one of the following topics:
v ″Installing the DB2 Universal Database server″
Chapter 2 Preparing the Environment
57
v ″Installing the Oracle server″
v ″Installing SQL Server″
Installing the DB2 Universal Database server: Install the IBM DB2 Universal
Database server software on the server that will host the IBM Workplace
Collaboration Services database. After you install the server software, be sure to
install the required fix pack.
Procedures for installing DB2 Universal Database varies by platform; see the
appropriate topic for your platform:
v Installing DB2 Universal Database in AIX, Linux, and Solaris
v Installing DB2 Universal Database in Windows
Note: The instructions for installing DB2 Universal Database do not apply to the
IBM i5/OS platform, which comes with IBM DB2 Universal Database for
iSeries already installed.
Installing DB2 Universal Database in AIX, Linux, and Solaris:
Install the IBM DB2 Universal Database server on IBM AIX, Linux, or Sun Solaris.
Complete this procedure on the computer where you will host the IBM Workplace
Collaboration Services database.
1. Log in to the server as a DB2 administrator.
2. Insert one of the following CDs:
v The CD containing the DB2 Universal Database Enterprise Server Edition
for Linux.
v The CD containing the DB2 Universal Database Enterprise Server Edition
for AIX Single-Byte Character Set (SBCS).
v The CD containing the DB2 Universal Database Enterprise Server Edition
for AIX Double-Byte Character Set (DBCS).
v The CD containing the DB2 Universal Database Enterprise Server Edition
for Solaris.
3. Start the launch pad by typing the following command:
./db2setup
4. Click Installation Prerequisites to review the system requirements.
5. Click Install Products.
6. Make sure that DB2 UDB Enterprise Server Edition is selected, and then click
Next.
7. Read the ″Welcome″ panel text, and then click Next.
8. Read the License Agreement, select I accept the terms in the license
agreement, and then click Next.
9. In the ″Select Installation Type″ panel, select Typical (do not select Data
warehousing or Satellite administration capability), and then click Next.
If you are prompted with a warning about using APPC to connect to remote
servers, click OK.
10. In the ″Select the Installation Action″ panel, make sure that Install DB2 UDB
Enterprise Server Edition on this computer is selected. (do not select Save
your settings in a response file), and then click Next.
11. In the ″Set user information for the DB2 Administration Server″ panel, do the
following steps, and then click Next:
58
Installation and Upgrade Guide
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
a. Accept the default user name.
This user will also be granted administrative privileges in DB2.
b. Type the group name that this user belongs to, for example: db2grp.
c. Type and confirm a password.
d. Accept the default directory, or type one; for example:
/home/<db2_admin>.
Do one of the following steps, and then click Next.
v (AIX) Accept the default Create a DB2 instance -32 bit (if your system is 32
bit option this will not display).
v (Linux) Accept the default Create a DB2 instance.
Select how the instance will be used: accept the default Single-partition
instance, and then click Next.
To set user information for the DB2 instance owner, do the following steps,
and then click Next:
a. Type the DB2 instance owner’s name; for example, db2inst. This name
must not be the same as that used in Step 11 (administrative user).
b. Type the group name that this user belongs to, for example: db2grp.
c. Type and confirm a password.
d. Accept the default directory, or type one; for example:
/home/<db2_instance>. This path must not be the same as that used in
Step 11 (administrative user).
To set user information for the fenced user, do the following steps, and then
click Next:
a. Accept the default user name. This value must not be the same as the
name used in Step 11 (administrative user) or Step 14 (instance owner).
b. Type the group name; for example: db2grp.
c. Type and confirm a password.
d. Type the user’s home directory; for example: /home/<db2_fenced>. This
path must not be the same as those used in Step 11 (administrative user)
or Step 14 (instance owner).
In the ″Prepare the DB2 tools catalog″ panel, select Prepare the DB2 tool
catalog in a local database, and then click Next.
In the ″Specify a local database to store the DB2 tools catalog″ panel, accept
the defaults, and then click Next.
If you are prompted with a warning about SMTP, click OK.
In the ″Set up the administration contact list″ panel, select Local - create a
contact list on this system, and then click Next.
In the ″Specify a contact for health monitor notification″ panel, select Defer
the task after installation is complete, and then click Next.
In the ″Start copying files″ panel, review the list, and then click Install.
Restart the server.
Before you can use DB2 Universal Database, you must install FixPak 7a as
described in the following procedure.
Installing DB2 FixPak 7a:
FixPak 7a for DB2 is posted on the DB2 Web site, and can be accessed using the
following steps:
1. Log in to the DB2 database server as db2admin.
Chapter 2 Preparing the Environment
59
2. Navigate to the following Web address and download the FixPak to your DB2
server:
http://www-306.ibm.com/software/data/db2/udb/support/downloadv8.html
This address contains tables of FixPaks and documentation for all supported
platforms.
If you will be hosting the Workplace Collaboration Services database directly on
the DB2 server, proceed to the Phase 3, ″Installing Workplace Collaboration
Services″. If you will be hosting the database on a DB2 client computer, proceed to
the topic, ″Installing the DB2 Universal Database client″.
Installing DB2 Universal Database in Windows:
Install the IBM DB2 Universal Database server in Microsoft Windows.
Complete this procedure on the computer where you will host the IBM Workplace
Collaboration Services database.
1. Log in to the Windows server as a DB2 administrator.
2. Insert the CD containing the DB2 Universal Database Enterprise Endition
Server for Windows.
The auto-run feature automatically opens the DB2 launch pad in the DB2
Setup wizard.
3. Click Installation Prerequisites to review the system requirements.
4. Click Install Products.
5. Make sure that ″DB2 UDB Enterprise Server Edition″ is selected, and then
click Next.
6. Read the ″Welcome″ panel text, and then click Next.
7. Read the License Agreement, select I accept the terms in the license
agreement, and then click Next.
8. In the ″Select Installation Type″ panel, select Typical (do not select ″Data
warehousing″ or ″Satellite administration capability″), and then click Next.
If you are prompted with a warning about using APPC to connect to remote
servers, click OK.
9. In the ″Select the Installation Action″ panel, make sure that Install DB2 UDB
Enterprise Server Edition on this computer is selected (do not select Save
your settings in a response file), and then click Next.
10. Choose a drive and directory on which to install the DB2 server, and then
click Next.
Do not use the default C:\Program Files\SQLLIB, and do not include spaces
in the path name. For example, use C:\IBM\SQLLIB.
11. In the ″Set user information for the DB2 Administration Server″ panel, type
the DB2 administrator’s name.
In this step, you are ensuring that the DB2 administrator now has all of the
necessary privileges in both DB2 and Windows.
12. Type the password for that account and confirm it. Leave Use the same user
name and password for the remaining DB2 services checked, and then click
Next.
13. In the ″Set up the administration contact list″ panel, select Local - create a
contact list on this system, and then click Next.
14. In the Configure DB2 instances panel, click Next.
60
Installation and Upgrade Guide
15. In the ″Prepare the DB2 tools catalog″ panel select Prepare the DB2 tool
catalog in a local database, and then click Next.
16. In the ″Specify a local database to store the DB2 tools catalog″ panel, accept
the defaults and then click Next.
If a warning about SMTP displays, click OK.
17. In the ″Specify a contact for health monitor notification″ panel, select Defer
the task after installation is complete, and then click Next.
18. In the ″Start copying files″ panel, review the list, and then click Install.
19. Restart the server.
Before you can use DB2, you must install FixPak 7a as described in the following
procedure.
Installing DB2 FixPak 7a:
FixPak 7a for DB2 is posted on the DB2 Web site, and can be accessed using the
following steps:
1. Log in to the DB2 database server as a DB2 administrator.
2. Navigate to the following Web address and download the FixPak to your DB2
server:
http://www-306.ibm.com/software/data/db2/udb/support/downloadv8.html
This address contains tables of FixPaks and documentation for all supported
platforms.
If you will be hosting the IBM Workplace Collaboration Services database directly
on the DB2 server, proceed to Phase 3, ″Installing Workplace Collaboration
Services″. If you will be hosting the database on a DB2 client computer, proceed to
the topic, ″Installing the DB2 Universal Database client″.
Installing the Oracle server:
Setting up the Oracle server involves installing the Oracle database server software
and creating a database instance for use with IBM Workplace Collaboration
Services, as described in this topic. If you have previously installed Oracle 9i and
used it with earlier releases of Workplace Collaboration Services, you must update
the Oracle installation with patch 9.2.0.4.0 and then create a new database for
Workplace Collaboration Services as described in the topic, ″Creating a new Oracle
database for IBM Workplace Collaboration Services″.
Installing the Oracle server software:
For instructions on installing the Oracle DBMS server software, consult your Oracle
documentation. When installing the Oracle server software, complete the Database
Instance and Service naming task (described in this topic) to ensure proper access
to databases from Workplace Collaboration Services.
Note: As part of the Oracle server software installation, install Oracle 9i patch
9.2.0.4.0; this patch is required to ensure that Workplace Collaboration
Services data transfer operations are successful.
After the server software has been installed, proceed to the next section, ″Setting
the database instance and service names.″
Setting the database instance and service names:
Chapter 2 Preparing the Environment
61
Perform this task on the computer hosting the Oracle database.
1. Log in to the server as a user with administrative privileges.
2. While installing the Oracle server software, create a database instance called
wps50 using the Unicode and UTF-8 options.
This database instance will contain the schemas used by Workplace, and must
be created using the UTF-8 character set to ensure accessibility in all languages.
Tip: If you omit this step during installation, you can create the database
instance later using the Oracle Database Configuration Assistant tool.
3. Edit the Oracle\Ora9\network\admin\tnsnames.ora file, and set the
SERVICE_NAME parameter to wps50 to match the database instance name
created in Step 2.
In the example that follows, the SERVICE_NAME (shown italicized) matches
the ″tns″ entry in which it is included; this match between names is required
for Workplace Collaboration Services. The examples in this documentation use
wps50 as the database name (and thus, the service name).
wps50 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = workplaceserver.acme.com)
(PORT = 1521)
)
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = wps50)
)
)
The PORT indicates the port that the Oracle server and client use for
communicating (they must use the same port).
4. Save and close the tnsnames.ora file.
After the Oracle server has been installed and the database instance has been
created, proceed to the topic ″Adding WebSphere Portal Server users to the Oracle
database.″
Installing SQL Server: IBM Workplace Collaboration Services supports Microsoft
SQL Server as a database management product. For instructions on installing the
SQL Server software, consult the SQL Server documentation.
After you have installed the SQL Server software, install the associated SQL Server
client software on all computers that will host Workplace Collaboration Services
(except for the computer hosting the SQL Server database server). For more
information, see the topic, ″Installing the SQL Server client″.
Installing the DBMS client
The IBM Workplace Collaboration Services databases are stored on the DBMS
server. If the DBMS server is not hosted on the same server as Workplace
62
Installation and Upgrade Guide
Collaboration Services (you are using a remote database), you must install the
appropriate DBMS client application on the Workplace server, to ensure access to
the database.
In a Network Deployment environment, install the DBMS client on the
Deployment Manager and all nodes.
Before you install the DBMS client software, review one of the following topics:
v ″Installing the DB2 Universal Database DBMS client″
v ″Installing the Oracle DBMS client″
v ″Installing the SQL Server DBMS client″
Installing the DB2 Universal Database client:
Install the IBM DB2 Universal Database Administration Client.
Complete this procedure on each computer hosting IBM Workplace Collaboration
Services.
1. Log in to the server using an account with administrator privileges..
2. Download the DB2 Administration Client and fix pack appropriate to your
operating system from the following Web address:
http://www-306.ibm.com/software/data/db2/udb/support/
3. Source the db2profile file in the login profile of your IBM WebSphere
Application Server V5 instance owner, as described in the topic, ″Configuring
WebSphere Application Server for DB2 access,″ in the WebSphere Application
Server Enterprise information center.
If you are prompted for the DB2 administrator account during client installation,
provide the name of a user account that has DB2 administrator privileges on the
DB2 server.
Note: The DB2 client must always use the same connection port as the DB2 server,
to ensure that the two can communicate. The DB2 server usually defaults to
port 50000 for connections and port 50001 for interrupts. On SuSE Linux,
port 50000 may already be reserved for another use; if so, DB2 automatically
increments the port numbers by one.
To check which ports have been assigned to DB2 on the server, look at the
/etc/services file (available on IBM AIX, Linux, Sun Solaris, and Microsoft
Windows). This file contains two entries: the entry prefixed with db2c represents
the connection port, and the entry prefixed with db2i represents the interrupt port.
For example, if the owner of the first DB2 instance installed on the server is
″db2inst1,″ the /etc/services file contains entries like these:
db2cdb2inst1 50000/tcp
#Connection port for DB2 instance db2inst1
db2idb2inst1 50001/tcp
#Interrupt port for DB2 instance db2inst1
In addition to using the same connection port for the DB2 server and client, you
must configure TCP/IP to work between them.
After you complete the DB2 client installation, proceed to Phase 5, ″Connecting to
a DBMS server.″
Installing the Oracle client: For instructions on installing the Oracle client, refer
to the Oracle documentation. When installing the client software, be sure to install
Chapter 2 Preparing the Environment
63
Oracle 9i patch 9.2.0.4.0, which is required to ensure that IBM Workplace
Collaboration Services data transfers are successful.
Note: Be sure to install the client using the same port that the database server
uses, so that they can communicate properly. In addition, make that the
client uses a UTF-8 codepage (any language).
Upgrading the client’s JDBC driver
On IBM AIX, Linux, and Sun Solaris platforms, installing the Oracle 9i patch
9.2.0.4.0 patch may install the (incorrect) 9.2.0.3.0 JDBC driver rather than the
required 9.2.0.4.0 JDBC driver.
To check to see if you need to upgrade your driver, look in your Portal system.out
log for this entry:
[3/8/05 18:15:39:041 GMT] 34d14c25 WSRdbDataSour W DSRA7011W: A Oracle JDBC provider
property (TransactionBranchesLooselyCoupled) has been set. Oracle patch 2511780 must be
applied before setting this property.
[3/8/05 18:15:39:513 GMT] 34d14c25 WSRdbDataSour u Database version is Oracle9i
Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining optionsJServer
Release 9.2.0.4.0 - Production
[3/8/05 18:15:39:514 GMT] 34d14c25 WSRdbDataSour u JDBC Driver
version is 9.2.0.3.0
If the log entry indicates that you have the 9.2.0.3.0 JDBC driver (as highlighted in
the example), you will need to upgrade the driver by downloading it from the
following Web address:
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Finalizing the Oracle client installation
After you install the Oracle client, copy the following files from the Oracle server
to the client:
v tsnames.ora
v classes12.zip
Edit the tnsnames.ora file and add a reference to the Oracle database server, and
verify that it specifies the port used by the Oracle server and client.
After you complete the Oracle client installation, proceed to Phase 5, ″Connecting
to a DBMS server.″
Installing the SQL Server client:
Every computer hosting IBM Workplace Collaboration Services needs a copy of the
Microsoft SQL Server client (except for the computer hosting the SQL Server
database-server software).
To download the SQL Server client software, point your browser at:
http://www.microsoft.com/sql/downloads/default.asp
64
Installation and Upgrade Guide
On that page, click Most Popular Dowloads → SQL Server 2000 Driver for JDBC
Service Pack 3; then you can download the client driver directly to your computer.
Instructions for the download are located on the same page.
Attention: Be sure to install the client driver using the same port that the SQL
Server database-server software uses, so that they can communicate properly.
After you complete the SQL Server client installation, proceed to Phase 5,
″Connecting to a DBMS server.″
Preparing an external HTTP server
If you plan to use an external HTTP server (either remote or local), make these
preparations before installing Workplace Collaboration Services. In a Network
Deployment environment, you must also install WebSphere® Application Server
Edge components on another server to set up load balancing for instant messaging
and Web conferences.
By default IBM Workplace Collaboration Services uses the internal HTTP transport
within WebSphere Application Server. The default is sufficient for pilot installations
or small-business environments, but for a Network Deployment, you must set up
an external HTTP server.
In addition, an external HTTP server provides optimal performance for IBM
Workplace Collaborative Learning and its course content server and IBM
Workplace SIP services (used for instant messaging, awareness, and Web
conference activity). An external HTTP server also improves performance when
used with the rich client provisioning server.
1. Install the HTTP server.
(i5/OS only) This step also includes creating a new IBM HTTP Server instance.
2. If you are installing in a Network Deployment environment, create aliases for
the shared directories.
3. If Workplace Collaboration Services will not be installed on the external HTTP
server machine, install one of the following:
v AIX, Linux, Solaris, and Windows
Install the WebSphere Application Server plug-in.
v i5/OS
Install the *BASE version of WebSphere Application Server.
4. To test the installation, start the HTTP server.
Related concepts
Types of external HTTP servers
Setting up the environment
Related tasks
“Installing WebSphere Application Server Edge components” on page 53
Installing the HTTP server
Follow these instructions to install IBM HTTP Server on IBM AIX, Linux, Sun
Solaris, or Microsoft Windows.
IBM HTTP Server is a licensed program on IBM i5/OS. For instructions on
installing IBM HTTP Server on i5/OS, see the IBM eServer iSeries Information
Center at
Chapter 2 Preparing the Environment
65
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/rzaie/rzaieinstalling.htm
For instructions on installing other supported Web servers, refer to the vendor’s
Web server documentation for more information.
1. If you are setting up a remote HTTP server, ensure that the machines that
will host Workplace Collaboration Services or the provisioning server and the
HTTP server are in the same Internet DNS domain.
2. Download the IBM HTTP Server version that corresponds to the operating
system of your server from the IBM Web site. Ensure you have the IBM
Developer Kit, Java Technology Edition Version 1.3 or higher, installed on
your machine. This Developer Kit ships with the WebSphere Application
Server on the CD and is available from the following Web site:
http://www-130.ibm.com/developerworks/java.
3. Follow the instructions to download the appropriate file to a temporary
directory.
4. Extract the files from the .tar or .zip file to another temporary directory.
For example, for IBM HTTP Server 2.0.42.2 for Linux, use the following
command:
tar -xf HTTPServer.linux.20422.tar
5. Open a command prompt window and enter the following command:
IBM AIX, Linux, and Sun Solaris
From the <install_root>/AppServer/bin directory, enter:
./setupCmdLine.sh
Microsoft Windows
From the <install_root>\AppServer\bin directory, enter:
setupCmdLine.bat
6. Change to the temporary directory in which the extracted files are stored.
7. Enter the following command to start the installation program:
AIX
java -jar setup.jar -console
Linux
java -jar setup.jar
Solaris
java -jar setup.jar -console
Windows
java -jar setup.jar
8. Select the language in which to run the installation and click Next.
9. Accept the license agreement and click Next.
10. Select the installation directory; for example, “/opt1/IBMHttpServer” for
Linux or “C:\IBMHttpServer” for Windows. Then click Next.
11. Select Typical and click Next.
12. Type a valid administrative user name and password, confirm the password,
and click Next.
13. At the Summary panel, click Next.
14. At the Installation Complete panel, click Finish.
Now you are ready to download any of the following software patches that are
appropriate for your site.
66
Installation and Upgrade Guide
Download PQ92124 for IBM HTTP Server Version 2.0.42.2:
If you are using IBM HTTP Server Version 2.0.42.2 for Windows, follow these
steps.
1. Download PQ92124 from this site:
http://www-1.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&
q1=PQ92124&uid=swg24008098& loc=en_US&cs=utf-8&lang=en
The patch is labeled for HTTP Server Version 2.0.47.1, but also works with
Version 2.0.42.2.
2. Apply the fix by replacing the afpa.sys file with the newer version provided by
the patch.
3. Restart the server.
Download a WebSphere Application Server fix for remote HTTP servers:
If you are setting up an HTTP server that will connect remotely, download an
updated plug-in and copy it to your HTTP server. Perform these steps on the
server that has the WebSphere Application Server plug-in.
1. Stop all Web services.
2. Go to the IBM support site:
3.
4.
5.
6.
http://www-1.ibm.com/support/docview.wss?uid=swg24007265
Download the plug-in zip file that is appropriate for your platform.
Unzip the plug-in zip file.
Back up the plug-in modules currently being used.
Copy the updated plugin-cfg.xml file from the WebSphere Application Server to
the local or remote HTTP server directory.
7. (AIX) Run the slibclean command after stopping the Web server to clean up
any shared libraries in use.
8. Restart all Web services.
Verify that the plug-in build date has changed within the plug-in log file by
looking at the Bld version and Bld date recorded in the http_plugin.log file when
the HTTP server starts.
For example, the information on a Windows system might look something like
this:
--------------------System Information-------------PLUGIN: Bld version: 5.0.0
PLUGIN: Bld date: Dec 3 2004, 10:48:06
PLUGIN: Webserver: IBM_HTTP_SERVER/1.3.26.2
Apache/1.3.26 (Win32)
PLUGIN: Hostname = www.mycompany.com
PLUGIN: OS version 5.1, build 2600, ‘Service Pack 1
PLUGIN: -------------------------------------------
Related concepts
Phase 6: Connecting to an external HTTP server
Related tasks
Creating a new IBM HTTP Server instance on i5/OS
Installing the WebSphere Application Server plug-in
Setting up an external HTTP server
Chapter 2 Preparing the Environment
67
Creating a new IBM HTTP Server instance on i5/OS:
IBM Web Administration for i5/OS includes a Web-based interface for creating and
configuring a new IBM HTTP Server instance. The Create HTTP Server wizard
collects may of the required values from your server. The following steps describe
how to create a new HTTP server instance using the Create HTTP Server wizard.
1. Start the administrative HTTP server by entering the following on an i5/OS
command line:
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
2. Type the following address in the Address field of a Web browser and press
Enter:
http://hostname:2001
where hostname is the fully qualified host name of the server.
3. Type the system name, user ID and password for the server and click OK. The
user ID must have *ALLOBJ, *IOSYSCFG, and *JOBCTL special authorities.
4. Click IBM Web Administration for i5/OS.
5. Under Common Tasks and Wizards, click Create HTTP Server.
6. Follow each step in the wizard to create a new HTTP Server for use with IBM
Workplace Collaboration Services.
Note: On the ″IP Address″ screen, select the specific IP address you set aside
for use with Workplace Collaboration Services (do not select All
Addresses).
Related tasks
Setting up an external HTTP server
Creating aliases for Network Deployment shared directories
The next step is to create an alias for the Learning content directory. In a Network
Deployment environment, the Collaborative Learning shared content folder is on a
network drive when you use File System as the course transport method. This step
isn’t necessary in other environments, where the content folder exists in the default
document root of the HTTP server (for example,
\IBMHttpServer\htdocs\en_US\content).
You must also map the URL to the shared folder to prevent the content URL
(http://<servername>/content) from loading from the default document root.
1. On the HTTP server, find the httpd.conf file, located in the <ihs_root>\conf
directory and make a backup copy of the file.
2. Open the original httpd.conf file in a text editor.
3. Redirect the /content/ to the share by creating a Directory directive entry:
#</Directory><Directory "//Deployment_Manager_Name/NDShare_name">
Options Indexes
AllowOverride None
Order allow,deny
Allow from all
</Directory>
4. Add an alias entry for Learning content.
Alias /content/ "//Deployment_Manager_Name/NDShare_name/content/"
5. Save your changes and close the file.
Related concepts
Configuring the HTTP server
68
Installation and Upgrade Guide
Phase 6: Connecting to an external HTTP server
Related tasks
Creating shared directories for a Network Deployment
Installing the WebSphere Application Server plug-in
Installing the WebSphere Application Server plug-in
If your HTTP server is running on IBM i5/OS, you will need to create and
configure a new remote HTTP server instance. For details, see the WebSphere
Application Server for iSeries Information Center at
http://publib.boulder.ibm.com/iseries/v1r1m0/websphere/
ic2924/info/rzaiz50/admin/rmthttp.htm
For all other platforms, follow the instructions in this topic to install the
WebSphere Application Server plug-in if you are setting up a remote HTTP server.
Installing the plug-in:
Follow these steps to install the plug-in.
1. Stop the HTTP server if it is running.
2. Start the WebSphere Application Server installation program.
The installation program is located in the
<was_cd_root>\was\<operating_system>\WAS50 directory, where was_cd_root is
the root directory of the CD containing the WebSphere Application Server
component and operating_system indicates the operating system of the machine
where you are installing the plug-in.
3. Select the language you want to use for the installation, and click OK.
4. Click Next on the Welcome panel, accept the license agreement, and click Next.
5. Select Custom.
6. On the features panel, deselect all features except Web Server Plugins and the
entry for the specific Web server for which you are installing the plug-in, such
as IBM HTTP Server.
Note: You must select both Web Server Plugins and the entry for the Web
server.
7. Click Next.
8. Specify the directory path where you want to install the WebSphere Application
Server files, and then click Next.
9. Specify the location of the HTTP server configuration file (usually httpd.conf)
or other required files, as appropriate, and then click Next to complete the
installation.
Updating the plug-in:
1. In the <install_root>\AppServer directory, create a new folder called update.
2. Download the latest update wizard utility from http://www1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg2400190.
3. Extract the contents of the wizard zip file into the <install_root>\AppServer
\update directory, selecting the option to maintain the folder structure while
extracting.
4. Download the appropriate fixes to update the plug-in to work with WebSphere
Application Server 5.0.2.6 and WebSphere Application Server PME 5.0.2.6.
Chapter 2 Preparing the Environment
69
5. Create a subdirectory under <install_root>\AppServer\update called fixpacks.
Extract the respective jar files within the downloaded zip files into the fixpacks
directory.
Related tasks
Creating a new IBM HTTP Server instance on i5/OS
External HTTP server checklist
Starting and stopping the HTTP server
This section describes how to stop and start the IBM HTTP server. The notation
<ihs_root> represents the HTTP server installation directory.
Starting the HTTP server:
Enter the following commands to start the HTTP server.
IBM AIX, Linux, and Sun Solaris
cd /<ihs_root>/bin/
./apachectl start
Microsoft Windows
cd \<ihs_root>\bin\
c:\apache -k start
IBM i5/OS
Use the graphical user interface for HTTP or from the IBM OS400 command line,
enter the following command:
STRTCPSVR SERVER(*HTTP) HTTPSVR(<http instance name>)
Stopping the HTTP server:
Enter the following commands, where <ihs_root> is the HTTP server installation
directory:
AIX, Linux, and Solaris
cd /<ihs_root>/bin/
./apachectl stop
Windows
cd \<ihs_root>\bin\
c:\apache -k stop
i5/OS
Use the graphical user interface for HTTP or from the OS400 command line, enter
the following command:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(<http instance name>)
Related concepts
Phase 6: Setting up an external HTTP server
70
Installation and Upgrade Guide
Chapter 3 Installing IBM Workplace Collaboration Services
This chapter describes how to install IBM Workplace Collaboration Services in a
variety of scenarios.
Phase 3: Installing IBM Workplace Collaboration Services
Use this section to perform the following installation-related tasks:
1. In a Network Deployment environment, enable LDAP security on the
Deployment Manager.
2. Prepare to run the installation program.
3. Install on a single server, network nodes, or the Deployment Manager.
4. Configure IBM Workplace Collaboration Services.
5. Start and stop IBM Workplace Collaboration Services.
Related tasks
(Single server) Sequence of operations for AIX, Linux, Solaris, and Windows
(Single server) Sequence of operations for i5/OS
Network Deployment installation and configuration road map
Uninstalling IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Preparing to run the installation program
Follow these steps before installing IBM Workplace Collaboration Services.
1. Complete the steps in the pre-installation checklist and have the Administrator
Names and Passwords worksheet at hand.
2. (i5/OS) If host servers are not started on your server, start them by entering the
following on an i5/OS command line:
STRHOSTSVR SERVER(*ALL)
Starting host servers also requires the QUSRWRK, QSYSWRK, and QSERVER
subsystems to be running. To start a subsystem, enter the following on an
i5/OS command line:
STRSBS SBSD(<SUBSYSTEM>)
3. If you are installing on IBM AIX or Sun Solaris, meet these additional
installation program requirements.
v (AIX and Solaris) The installation program uses the GNU tar archiver to
extract files during installation. Before running the installation program on
AIX or Solaris, you must install GNU tar, version 1.14 or later. The GNU tar
can be downloaded from the Free Software Directory on www.gnu.org. It
must be installed as the default tar utility on the path. (The default install
location for GNU tar is /usr/local/bin.) To verify the version number of the
default tar utility, use the command ″tar --version″ (typed with two hyphens,
not a dash). If the default tar utility is not the latest version, upgrade to
version 1.14 or later.
v (AIX only) Increase the ulimit to a number larger than the size of
LWP_WPS_Common1.tar.gz with the following command:
ULIMIT 99999999999999999; export ULIMIT
© Copyright IBM Corp. 2002, 2005
71
4. If you expect to set up an HTTP server on a separate machine, ensure that the
Workplace server and the planned HTTP server are in the same Internet DNS
domain.
5. Deactivate any screen savers, because they may interfere with the operation of
the installation program.
6. Disable all firewalls until Workplace Collaboration Services is installed and
configured because they may interfere with the operation of the installation
program and Configuration Wizard.
Related tasks
Single-server installation and configuration road map
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
Installing on a single server
If you are installing IBM Workplace Collaboration Services on a single server,
follow the instructions appropriate to the media and operating system you have.
DVD
CD-ROM
Downloadable
e-image
IBM AIX
Install
Install
Install
Linux
Install
Install
Install
Sun Solaris
Install
Install
Install
Microsoft Windows
Install
Install
Install
IBM i5/OS
Install
Install
Install
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
Related tasks
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows
Sequence of operations for i5/OS
Other ways to install IBM Workplace Collaboration Services
Installing on a single server from a DVD
If you are installing IBM Workplace Collaboration Services on a single server,
follow the steps appropriate to your operating system.
If you are installing in a Network Deployment, follow the instructions in
″Installing in a Network Deployment″ instead.
Installing on a single server on AIX, Linux, and Solaris from a DVD:
Follow these steps to install Workplace Collaboration Services on a single server on
IBM AIX, Linux, and Sun Solaris. The process takes about an hour to complete.
1. Prepare to run the installation program.
72
Installation and Upgrade Guide
2. Log in to the server as a user with administrative privileges.
3. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
4. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
5. Enter the command to start installation.
./install.sh
6. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
7. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
8. When you are ready to proceed with the installation, click Next at the
Welcome panel.
9. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
10. At the License Agreement, click I accept the terms, and click Next.
11. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (for example, /opt/IBM/Workplace), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
12. At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
13. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
14. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
15. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
16. The installer displays the final screen, which shows the location of the
installation logs.
17. Click Finish to complete the installation.
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server on Windows from a DVD:
Follow these steps to install Workplace Collaboration Services on a single server on
Microsoft Windows. The process takes about an hour to complete.
Chapter 3 Installing IBM Workplace Collaboration Services
73
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
4. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
5. Enter the appropriate command to start installation.
install.bat
6. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
7. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
8. When you are ready to proceed with the installation, click Next at the
Welcome panel.
9. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
10. At the License Agreement, click I accept the terms, and click Next.
11. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (for example, c:\Program Files\IBM\Workplace), and
then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
12. At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
13. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
14. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
15. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
16. The installer displays the final screen, which shows the location of the
installation logs.
17. Click Finish to complete the installation.
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server on i5/OS from a DVD:
74
Installation and Upgrade Guide
Follow these steps to install Workplace Collaboration Services on a single server on
IBM i5/OS.
Note: These instructions are for installing Workplace Collaboration Services
remotely from a workstation connected to your server. For local installation,
copy the install files directly to your server and install using the install.sh
command from a QShell session. This will launch the installation program in
console mode.
For other installation methods, see the section ″Other ways to install Workplace
Collaboration Services.″
1. Prepare to run the installation program.
2. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
3. From a command prompt, change to the LWPServer directory of the
installation DVD (Example: cd D:\LWPServer).
4. Start the installation program by entering the following:
install400.bat
5. Sign on to your server with a user profile that has *ALLOBJ, *IOSYSCFG, and
*JOBCTL authorities.
6. At the panel ″Select a language to be used,″ select the language for the
installation program, and click OK.
7. When you are ready to proceed with the installation, click Next at the
Welcome panel.
8. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
9. At the ″License Agreement,″ click I accept the terms in the license agreement,
and click Next.
10. View the summary information on the next panel and click Next when you
are ready to begin installation. Note that Workplace Collaboration Services
product files are installed to /QIBM/ProdData/Workplace/WCS25/.
Note: Installation of Workplace Collaboration Services may take 30 minutes or
more to complete.
11. After Workplace Collaboration Services has been installed, a screen will be
displayed asking if you wish to configure Workplace Collaboration Services.
Click Next to continue with configuration or Cancel to exit the installation
program.
12. At the panel ″Configuration options,″ select a method for configuring
Workplace Collaboration Services and click Next.
Select IBM Workplace setup wizard for i5/OS if you want to use the Create
IBM Workplace Collaboration Services wizard to configure Workplace
Collaboration Services. This is the recommended method for configuring
Workplace Collaboration Services on i5/OS, as it performs HTTP, database,
and LDAP setup through a single Web-based interface.
Select Custom configuration if you want to configure Workplace
Collaboration Services using the installation program and the Workplace
Configuration Wizard. This method involves additional manual steps, but may
be suitable for advanced users and those attempting non-standard
deployments.
Chapter 3 Installing IBM Workplace Collaboration Services
75
13. If you selected IBM Workplace setup wizard for i5/OS on the previous panel,
the next panel will indicate whether the installation program was able to
detect and start the IBM HTTP Server administrative server.
If the IBM HTTP Server administrative server is started, you can select
Launch the i5/OS setup wizard for IBM Workplace and then Finish to exit
the installation program and immediately begin configuration of Workplace
Collaboration Services.
If the installation program indicates it was unable to start the IBM HTTP
Server administrative server, or if you do not wish to begin configuration
immediately, click Finish to exit the installation program. To configure
Workplace Collaboration Services, you will need to manually start IBM HTTP
Server and the Create IBM Workplace Collaboration Services wizard.
Skip the remaining steps in this procedure. These steps are only necessary if
you chose Custom configuration on the previous panel.
14. The panel ″IBM Workplace instance name″ is displayed only if you selected
Custom configuration on the previous panel. Enter your Instance Name and
click Next. The Instance Name is a unique name for the WebSphere
Application Server instance to be used for Workplace Collaboration Services
(this instance may also be referred to as the ″Workplace Collaboration Services
instance″).
Note: You are required to enter your Workplace Collaboration Services
instance name for various configuration steps following installation. At
this point, you may wish to make a note of the instance name for
future reference.
15. At the panel ″Specify internal ports used by the WebSphere Application
Server,″ enter the first of 50 consecutive ports to be used for IBM Workplace
and click Next.
Note: You will need to know the port block used by Workplace Collaboration
Services for later configuration steps, so you may wish to make a note
of this value.
16. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full host name) for the Workplace
Collaboration Services installation. This is the host name associated with the
TCP/IP address you set aside for use with Workplace Collaboration Services.
Click Next.
17. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace Collaboration Services
administrator.
Click Next.
18. View the configuration summary information and click Next to start
configuration.
Note: Configuration of Workplace Collaboration Services may take an hour or
more to complete.
19. When configuration is complete, the installation program displays a screen
indicating that configuration was successful. Click Finish to exit the
installation program.
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
76
Installation and Upgrade Guide
Related tasks
Installing on a single server from CD-ROM
Installing on a snigle server from an e-image
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows
Sequence of operations for i5/OS
Installing on a single server from CD-ROM
This topic provides a CD-based alternative method for installing IBM Workplace
Collaboration Services. If you are installing IBM Workplace Collaboration Services
on a single server, follow the steps appropriate to your operating system:
v IBM AIX, Linux, Sun Solaris
v Microsoft Windows
v IBM i5/OS
If you are installing in a Network Deployment, follow the instructions in
″Installing in a Network Deployment″ instead.
Installing on a single server from CD-ROM (AIX, Linux, Solaris):
Follow these steps to install Workplace Collaboration Services on a single server
from CDs . You must copy the contents of the CDs to the local drive; you cannot
install directly from CDs. The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
4. Create a downloads directory on your hard drive, for example,
/opt/downloads.
5. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
6. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
AIX
/LWPArchives/WAS_Archive_AIX.tar.gz
/LWPArchives/WPS_Archive_AIX.tar.gz
Linux
/LWPArchives/WAS_Archive_Linux.tar.gz
/LWPArchives/WPS_Archive_Linux.tar.gz
Chapter 3 Installing IBM Workplace Collaboration Services
77
Solaris
/LWPArchives/WAS_Archive_Solaris.tar.gz
/LWPArchives/WPS_Archive_Solaris.tar.gz
7. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
8. Change to the local LWPServer directory.
9. Enter the command to start installation.
./install.sh
10. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
11. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
12. When you are ready to proceed with the installation, click Next at the
Welcome panel.
13. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
14. At the License Agreement, click I accept the terms, and click Next.
15. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
16. At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
17. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
18. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
19. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
20. The installer displays the final screen, which shows the location of the
installation logs.
21. Click Finish to complete the installation.
78
Installation and Upgrade Guide
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server from CD-ROM (Windows):
Follow these steps to install Workplace Collaboration Services on a single server
from CDs. You must copy the contents of the CDs to the local drive; you cannot
install directly from CDs. The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
4. Create a downloads directory on your hard drive, for example, C:\downloads.
5. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
6. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
\LWPArchives\WAS_Archive_Windows.tar.gz
\LWPArchives\WPS_Archive_Windows.tar.gz
7. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
8. Change to the local LWPServer directory.
9. Enter the command to start installation.
install.bat
10. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
11. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
12. When you are ready to proceed with the installation, click Next at the
Welcome panel.
13. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
Chapter 3 Installing IBM Workplace Collaboration Services
79
14. At the License Agreement, click I accept the terms, and click Next.
15. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
16. At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
17. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
18. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
19. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
20. The installer displays the final screen, which shows the location of the
installation logs.
21. Click Finish to complete the installation.
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server from CD-ROM (i5/OS):
Follow these steps to install Workplace Collaboration Services on a single server on
IBM i5/OS.
Note: These instructions are for installing Workplace Collaboration Services
remotely from a workstation connected to your server. For local installation,
copy the install files directly to your server and install using the install.sh
command from a QShell session. This will launch the installation program in
console mode.
For other installation methods, see the section ″Other ways to install Workplace
Collaboration Services.″
1. Prepare to run the installation program.
2. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
3. Create a downloads directory on your hard drive.
80
Installation and Upgrade Guide
4. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
5. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
/LWPArchives/WAS_Archive_i5OS.tar.gz
/LWPArchives/WPS_Archive_i5OS.tar.gz
6. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
7. From a QShell prompt or command prompt, change to the local LWPServer
directory.
8. Start the installation program by entering the following:
From i5/OS:
./install.sh
From a remote Windows server:
install400.bat
9. Sign on to your server with a user profile that has *ALLOBJ, *IOSYSCFG, and
*JOBCTL authorities.
10. At the panel ″Select a language to be used,″ select the language for the
installation program, and click OK.
11. When you are ready to proceed with the installation, click Next at the
Welcome panel.
12. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
13. At the ″License Agreement,″ click I accept the terms in the license agreement,
and click Next.
14. View the summary information on the next panel and click Next when you
are ready to begin installation. Note that Workplace Collaboration Services
product files are installed to /QIBM/ProdData/Workplace/WCS25/.
Note: Installation of Workplace Collaboration Services may take 30 minutes or
more to complete.
15. After Workplace Collaboration Services has been installed, a screen will be
displayed asking if you wish to configure Workplace Collaboration Services.
Click Next to continue with configuration or Cancel to exit the installation
program.
16. At the panel ″Configuration options,″ select a method for configuring
Workplace Collaboration Services and click Next.
Select IBM Workplace setup wizard for i5/OS if you want to use the Create
IBM Workplace Collaboration Services wizard to configure Workplace
Collaboration Services. This is the recommended method for configuring
Workplace Collaboration Services on i5/OS, as it performs HTTP, database,
and LDAP setup through a single Web-based interface.
Select Custom configuration if you want to configure Workplace
Collaboration Services using the installation program and the Workplace
Configuration Wizard. This method involves additional manual steps, but may
be suitable for advanced users and those attempting non-standard
deployments.
Chapter 3 Installing IBM Workplace Collaboration Services
81
17. If you selected IBM Workplace setup wizard for i5/OS on the previous panel,
the next panel will indicate whether the installation program was able to
detect and start the IBM HTTP Server administrative server.
If the IBM HTTP Server administrative server is started, you can select
Launch the i5/OS setup wizard for IBM Workplace and then Finish to exit
the installation program and immediately begin configuration of Workplace
Collaboration Services.
If the installation program indicates it was unable to start the IBM HTTP
Server administrative server, or if you do not wish to begin configuration
immediately, click Finish to exit the installation program. To configure
Workplace Collaboration Services, you will need to manually start IBM HTTP
Server and the Create IBM Workplace Collaboration Services wizard.
Skip the remaining steps in this procedure. These steps are only necessary if
you chose Custom configuration on the previous panel.
18. The panel ″IBM Workplace instance name″ is displayed only if you selected
Custom configuration on the previous panel. Enter your Instance Name and
click Next. The Instance Name is a unique name for the WebSphere
Application Server instance to be used for Workplace Collaboration Services
(this instance may also be referred to as the ″Workplace Collaboration Services
instance″).
Note: You are required to enter your Workplace Collaboration Services
instance name for various configuration steps following installation. At
this point, you may wish to make a note of the instance name for
future reference.
19. At the panel ″Specify internal ports used by the WebSphere Application
Server,″ enter the first of 50 consecutive ports to be used for IBM Workplace
and click Next.
Note: You will need to know the port block used by Workplace Collaboration
Services for later configuration steps, so you may wish to make a note
of this value.
20. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full host name) for the Workplace
Collaboration Services installation. This is the host name associated with the
TCP/IP address you set aside for use with Workplace Collaboration Services.
Click Next.
21. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace Collaboration Services
administrator.
Click Next.
22. View the configuration summary information and click Next to start
configuration.
Note: Configuration of Workplace Collaboration Services may take an hour or
more to complete.
23. When configuration is complete, the installation program displays a screen
indicating that configuration was successful. Click Finish to exit the
installation program.
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
82
Installation and Upgrade Guide
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows
Sequence of operations for i5/OS
Installing on a single server from an e-image
This topic provides an e-image alternative method for installing IBM Workplace
Collaboration Services from the Internet. To download from the Web, go to
http://www-306.ibm.com/software/howtobuy/passportadvantage/.
If you are installing on a single server, follow the steps for IBM AIX, Linux and
Sun Solaris, Microsoft Windows, or IBM i5/OS.
If you are installing in a Network Deployment, follow the instructions in
″Installing in a Network Deployment″ instead.
Installing on a single server from an e-image (AIX, Linux, and Solaris):
Follow these steps to install Workplace Collaboration Services from an e-image.
The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Create directories on your hard drive.
a. Create a downloads directory, for example, /opt/downloads.
b. Create an install directory, for example, /opt/install.
c. Create a directory called LWPArchives under the install directory, for
example, /opt/install/LWPArchives.
4. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
v C82MJML.tar.gz
v C83CCML.tar.gz
v C83XQML.tar.gz
5. Download the following platform-specific files to the downloads directory.
AIX
v C82MDML.tar
v C82MEML.tar
v C82MNML.tar.gz
v C83XTML.tar.gz
Linux
v C82MDML.tar
v C82MEML.tar
v C82MLML.tar.gz
v C83XRML.tar.gz
Chapter 3 Installing IBM Workplace Collaboration Services
83
Solaris
v C82MDML.tar
v C82MEML.tar
v C82MMML.tar.gz
v C83XSML.tar.gz
6. Move or copy the files from the downloads directory to the LWPArchives
directory.
7. Rename the files in the LWPArchives directory as shown in the following
table. The images can be renamed without making separate copies of the files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
8. Rename the following platform-specific files in the LWPArchives directory as
shown in the table.
AIX
Download image
Renamed file
C82MNML.tar.gz
WAS_Archive_AIX.tar.gz
C83XTML.tar.gz
WPS_Archive_AIX.tar.gz
Linux
Download image
Renamed file
C82MLML.tar.gz
WAS_Archive_Linux.tar.gz
C83XRML.tar.gz
WPS_Archive_Linux.tar.gz
Solaris
Download image
Renamed file
C82MMML.tar.gz
WAS_Archive_Solaris.tar.gz
C83XSML.tar.gz
WPS_Archive_Solaris.tar.gz
9. Extract the following files to the install directory, preserving the directory
structure.
v C82MDML.tar
v C82MEML.tar
10. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
84
Installation and Upgrade Guide
<download_directory>/DB2/PMR36414
11. Change to the local LWPServer directory.
12. Enter the command to start installation.
./install.sh
13. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
14. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
15. When you are ready to proceed with the installation, click Next at the
Welcome panel.
16. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
17. At the License Agreement, click I accept the terms, and click Next.
18. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
19. At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
20. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
21. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
22. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
23. The installer displays the final screen, which shows the location of the
installation logs.
24. Click Finish to complete the installation.
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server from an e-image (Windows):
Follow these steps to install Workplace Collaboration Services from an e-image.
The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
Chapter 3 Installing IBM Workplace Collaboration Services
85
3. Create directories on your hard drive.
a. Create a downloads directory, for example, D:\downloads.
b. Create an install directory, for example, D:\install.
c. Create a directory called LWPArchives under the install directory, for
example, D:\install\LWPArchives.
4. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
v C82MJML.tar.gz
v C82MKML.tar.gz
v C83CAML.exe
v C83CBML.exe
v C83CCML.tar.gz
v C83XQML.tar.gz
v C83XUML.tar.gz
5. Move or copy the files from the downloads directory to the LWPArchives
directory.
6. Rename the files in the LWPArchives directory as shown in the following
table. The images can be renamed without making separate copies of the files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C82MKML.tar.gz
WAS_Archive_Windows.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
C83XUML.tar.gz
WPS_Archive_Windows.tar.gz
7. Extract the following files to the install directory, preserving the directory
structure.
v C83CAML.exe
v C83CBML.exe
8. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
<download_directory>\DB2\PMR36414
9. Change to the local LWPServer directory.
10. Enter the command to start installation.
install.bat
86
Installation and Upgrade Guide
11. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
12. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
13.
14.
15.
16.
17.
18.
19.
For more information, see Appendix A.
When you are ready to proceed with the installation, click Next at the
Welcome panel.
At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
At the License Agreement, click I accept the terms, and click Next.
At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
At the panel ″IBM Workplace supports different deployment topologies,″
select Single-server, and then click Next.
At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the IBM Workplace
installation. Then click Next.
At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
20. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
21. The installer displays the final screen, which shows the location of the
installation logs.
22. Click Finish to complete the installation.
If you are setting up a pilot deployment with a remote database server or an
LDAP directory, you will now run the Configuration Wizard to finish setting up
Workplace Collaboration Services. Otherwise, proceed to the instructions for
starting the Workplace server.
Installing on a single server on i5/OS from an e-image:
Follow these steps to install Workplace Collaboration Services on a single server on
IBM i5/OS from an e-image.
Note: These instructions are for installing Workplace Collaboration Services
remotely from a workstation connected to your server. For local installation,
copy the install files directly to your server and install using the install.sh
command from a QShell session. This will launch the installation program in
console mode.
Chapter 3 Installing IBM Workplace Collaboration Services
87
For other installation methods, see the section ″Other ways to install Workplace
Collaboration Services.″
1. Prepare to run the installation program.
2. Create directories on your hard drive.
If running from Windows:
a. Create a downloads directory, for example, D:\downloads.
b. Create an install directory, for example, D:\install.
c. Create a directory called LWPArchives under the install directory, for
example, D:\install\LWPArchives.
3. Download the following files to the downloads directory:
v C82MDML.tar
v C82MEML.tar
v C82MPML.tar
v C82MQML.tar
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
v C82MJML.tar.gz
v C83CCML.tar.gz
v C83XQML.tar.gz
4. Move or copy the files from the downloads directory to the LWPArchives
directory.
5. Rename the following tar.gz images in the LWPArchives directory as shown in
the table. The images can be renamed without making separate copies of the
files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
6. Extract the following files to the install directory, preserving the directory
structure.
v C82MDML.tar
v C82MEML.tar
v C82MPML.tar
v C82MQML.tar
7. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
88
Installation and Upgrade Guide
8.
9.
10.
11.
12.
13.
<download_directory>\LWPUserMigration
<download_directory>\DB2/PMR36414
From a command prompt, change to the local LWPServer directory.
Start the installation program by entering the following:
install400.bat
Sign on to your server with a user profile that has *ALLOBJ, *IOSYSCFG, and
*JOBCTL authorities.
At the panel ″Select a language to be used,″ select the language for the
installation program, and click OK.
When you are ready to proceed with the installation, click Next at the
Welcome panel.
At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
14. At the ″License Agreement,″ click I accept the terms in the license agreement,
and click Next.
15. View the summary information on the next panel and click Next when you
are ready to begin installation. Note that Workplace Collaboration Services
product files are installed to /QIBM/ProdData/Workplace/WCS25/.
Note: Installation of Workplace Collaboration Services may take 30 minutes or
more to complete.
16. After Workplace Collaboration Services has been installed, a screen will be
displayed asking if you wish to configure Workplace Collaboration Services.
Click Next to continue with configuration or Cancel to exit the installation
program.
17. At the panel ″Configuration options,″ select a method for configuring
Workplace Collaboration Services and click Next.
Select IBM Workplace setup wizard for i5/OS if you want to use the Create
IBM Workplace Collaboration Services wizard to configure Workplace
Collaboration Services. This is the recommended method for configuring
Workplace Collaboration Services on i5/OS, as it performs HTTP, database,
and LDAP setup through a single Web-based interface.
Select Custom configuration if you want to configure Workplace
Collaboration Services using the installation program and the Workplace
Configuration Wizard. This method involves additional manual steps, but may
be suitable for advanced users and those attempting non-standard
deployments.
18. If you selected IBM Workplace setup wizard for i5/OS on the previous panel,
the next panel will indicate whether the installation program was able to
detect and start the IBM HTTP Server administrative server.
If the IBM HTTP Server administrative server is started, you can select
Launch the i5/OS setup wizard for IBM Workplace and then Finish to exit
the installation program and immediately begin configuration of Workplace
Collaboration Services.
If the installation program indicates it was unable to start the IBM HTTP
Server administrative server, or if you do not wish to begin configuration
immediately, click Finish to exit the installation program. To configure
Workplace Collaboration Services, you will need to manually start IBM HTTP
Server and the Create IBM Workplace Collaboration Services wizard.
Skip the remaining steps in this procedure. These steps are only necessary if
you chose Custom configuration on the previous panel.
Chapter 3 Installing IBM Workplace Collaboration Services
89
19. The panel ″IBM Workplace instance name″ is displayed only if you selected
Custom configuration on the previous panel. Enter your Instance Name and
click Next. The Instance Name is a unique name for the WebSphere
Application Server instance to be used for Workplace Collaboration Services
(this instance may also be referred to as the ″Workplace Collaboration Services
instance″).
Note: You are required to enter your Workplace Collaboration Services
instance name for various configuration steps following installation. At
this point, you may wish to make a note of the instance name for
future reference.
20. At the panel ″Specify internal ports used by the WebSphere Application
Server,″ enter the first of 50 consecutive ports to be used for IBM Workplace
and click Next.
Note: You will need to know the port block used by Workplace Collaboration
Services for later configuration steps, so you may wish to make a note
of this value.
21. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full host name) for the Workplace
Collaboration Services installation. This is the host name associated with the
TCP/IP address you set aside for use with Workplace Collaboration Services.
Click Next.
22. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace Collaboration Services
administrator.
Click Next.
23. View the configuration summary information and click Next to start
configuration.
Note: Configuration of Workplace Collaboration Services may take an hour or
more to complete.
24. When configuration is complete, the installation program displays a screen
indicating that configuration was successful. Click Finish to exit the
installation program.
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Sequence of operations for IBM AIX, Linux, Sun Solaris, and Microsoft
Windows
Sequence of operations for i5/OS
Installing on network nodes
If you are installing IBM Workplace Collaboration Services on a node in a Network
Deployment environment, follow the instructions appropriate to the media and
operating system you have.
90
Installation and Upgrade Guide
DVD
CD-ROM
Downloadable
e-image
IBM AIX
Install
Install
Install
Linux
Install
Install
Install
Sun Solaris
Install
Install
Install
Microsoft Windows
Install
Install
Install
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
Related tasks
Network Deployment installation and configuration road map
Installing on the Deployment Manager
Other ways to install IBM Workplace Collaboration Services
Installing on network nodes from a DVD
If you are installing IBM Workplace Collaboration Services on a node in a Network
Deployment, follow the steps for IBM AIX, Linux, Sun Solaris, or Microsoft
Windows platforms. This type of installation is not available on IBM i5/OS.
Installing Workplace Collaboration Services from a DVD:
Follow these steps to install Workplace Collaboration Services on a Network
Deployment node. The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
4. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
5. Enter the appropriate command to start installation.
AIX, Linux, and Solaris
./install.sh
Windows
install.bat
6. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
7. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
8. When you are ready to proceed with the installation, click Next at the
Welcome panel.
9. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
Chapter 3 Installing IBM Workplace Collaboration Services
91
10. At the License Agreement, click I accept the terms, and click Next.
11. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (recommended examples are shown below), and then
click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
AIX
/opt/IBM/Workplace
Linux
/opt/IBM/Workplace
Solaris
/opt/IBM/Workplace
Windows
c:\Program Files\IBM\Workplace
12. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
13. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
14. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
15. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
16. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
17. The installer displays the final screen, which shows the location of the
installation logs.
18. Click Finish to complete the installation.
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Related concepts
Lotus Workplace 2.0.1 upgrade
Related tasks
Installing on network nodes from CD-ROM
Installing on network nodes from an e-image
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
92
Installation and Upgrade Guide
Installing on network nodes from CD-ROM
This topic provides a CD-based alternative method for installing IBM Workplace
Collaboration Services. If you are installing on a node in a Network Deployment,
follow the steps for IBM AIX, Linux, and Sun Solaris or Microsoft Windows. This
type of installation is not available on IBM i5/OS.
Installing Workplace Collaboration Services from CDs (AIX, Linux, and
Solaris):
Follow these steps to install Workplace Collaboration Services on a Network
Deployment node from CDs. You must copy the contents of the CDs to the local
drive; you cannot install directly from CDs. The process takes about an hour to
complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
4. Create a downloads directory on your hard drive, for example,
/opt/downloads.
5. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
6. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
AIX
/LWPArchives/WAS_Archive_AIX.tar.gz
/LWPArchives/WPS_Archive_AIX.tar.gz
Linux
/LWPArchives/WAS_Archive_Linux.tar.gz
/LWPArchives/WPS_Archive_Linux.tar.gz
Solaris
/LWPArchives/WAS_Archive_Solaris.tar.gz
/LWPArchives/WPS_Archive_Solaris.tar.gz
7. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
8. Change to the local LWPServer directory.
9. Enter the command to start installation.
./install.sh
Chapter 3 Installing IBM Workplace Collaboration Services
93
10. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
11. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
12.
13.
14.
15.
16.
17.
18.
For more information, see Appendix A.
When you are ready to proceed with the installation, click Next at the
Welcome panel.
At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
At the License Agreement, click I accept the terms, and click Next.
At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
19. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
20. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
21. The installer displays the final screen, which shows the location of the
installation logs.
22. Click Finish to complete the installation.
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Installing Workplace Collaboration Services from CDs (Windows):
Follow these steps to install Workplace Collaboration Services on a Network
Deployment node from CDs. You must copy the contents of the CDs to the local
drive; you cannot install directly from CDs. The process takes about an hour to
complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
94
Installation and Upgrade Guide
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
4. Create a downloads directory on your hard drive, for example, C:\downloads.
5. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
6. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
\LWPArchives\WAS_Archive_Windows.tar.gz
\LWPArchives\WPS_Archive_Windows.tar.gz
7. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
8. Change to the local LWPServer directory.
9. Enter the command to start installation.
install.bat
10. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
11. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
12. When you are ready to proceed with the installation, click Next at the
Welcome panel.
13. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
14. At the License Agreement, click I accept the terms, and click Next.
15. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
16. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
17. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
18. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
Chapter 3 Installing IBM Workplace Collaboration Services
95
19. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
20. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
21. The installer displays the final screen, which shows the location of the
installation logs.
22. Click Finish to complete the installation.
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Related concepts
Lotus Workplace 2.0.1 upgrade
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
Installing on network nodes from an e-image
This topic provides an e-image alternative method for installing IBM Workplace
Collaboration Services from the Internet. To download from the Web, go to
http://www-306.ibm.com/software/howtobuy/passportadvantage/.
If you are installing on a node in a Network Deployment, follow the steps for IBM
AIX, Linux and Sun Solaris or Microsoft Windows platforms. This type of
installation is not available on IBM i5/OS.
Installing Workplace Collaboration Services from an e-image (AIX, Linux, and
Solaris):
Follow these steps to install Workplace Collaboration Services on a Network
Deployment node from an e-image. The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Create directories on your hard drive.
a. Create a downloads directory, for example, /opt/downloads.
b. Create an install directory, for example, /opt/install.
c. Create a directory called LWPArchives under the install directory, for
example, /opt/install/LWPArchives.
4. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
96
Installation and Upgrade Guide
v C82MJML.tar.gz
v C83CCML.tar.gz
v C83XQML.tar.gz
5. Download the following platform-specific files to the downloads directory.
AIX
v C82MDML.tar
v C82MEML.tar
v C82MNML.tar.gz
v C83XTML.tar.gz
Linux
v C82MDML.tar
v C82MEML.tar
v C82MLML.tar.gz
v C83XRML.tar.gz
Solaris
v C82MDML.tar
v C82MEML.tar
v C82MMML.tar.gz
v C83XSML.tar.gz
6. Move or copy the files from the downloads directory to the LWPArchives
directory.
7. Rename the following tar.gz images in the LWPArchives directory as shown in
the table. The images can be renamed without making separate copies of the
files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
8. Rename the following platform-specific files in the LWPArchives directory as
shown in the table.
AIX
Download image
Renamed file
C82MNML.tar.gz
WAS_Archive_AIX.tar.gz
C83XTML.tar.gz
WPS_Archive_AIX.tar.gz
Linux
Download image
Renamed file
C82MLML.tar.gz
WAS_Archive_Linux.tar.gz
C83XRML.tar.gz
WPS_Archive_Linux.tar.gz
Chapter 3 Installing IBM Workplace Collaboration Services
97
Solaris
Download image
Renamed file
C82MMML.tar.gz
WAS_Archive_Solaris.tar.gz
C83XSML.tar.gz
WPS_Archive_Solaris.tar.gz
9. Extract the following files to the install directory, preserving the directory
structure.
v C82MDML.tar
v C82MEML.tar
10. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
<download_directory>/DB2/PMR36414
11. Change to the local LWPServer directory.
12. Enter the command to start installation.
./install.sh
13. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
14. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
15. When you are ready to proceed with the installation, click Next at the
Welcome panel.
16. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
17. At the License Agreement, click I accept the terms, and click Next.
18. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
19. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
20. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
21. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
22. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
98
Installation and Upgrade Guide
23. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
24. The installer displays the final screen, which shows the location of the
installation logs.
25. Click Finish to complete the installation.
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Installing Workplace Collaboration Services from an e-image (Windows):
Follow these steps to install Workplace Collaboration Services on a Network
Deployment node from an e-image. The process takes about an hour to complete.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Create directories on your hard drive.
a. Create a downloads directory, for example, D:\downloads.
b. Create an install directory, for example, D:\install.
c. Create a directory called LWPArchives under the install directory, for
example, D:\install\LWPArchives.
4. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
v C82MJML.tar.gz
v C82MKML.tar.gz
v C83CAML.exe
v C83CBML.exe
v C83CCML.tar.gz
v C83XQML.tar.gz
v C83XUML.tar.gz
5. Move or copy the files from the downloads directory to the LWPArchives
directory.
6. Rename the following tar.gz images in the LWPArchives directory as shown in
the table. The images can be renamed without making separate copies of the
files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C82MKML.tar.gz
WAS_Archive_Windows.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
Chapter 3 Installing IBM Workplace Collaboration Services
99
Download image
Renamed file
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
C83XUML.tar.gz
WPS_Archive_Windows.tar.gz
7. Extract the following files to the install directory, preserving the directory
structure.
v C83CAML.exe
v C83CBML.exe
8. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
<download_directory>\DB2\PMR36414
9. Change to the local LWPServer directory.
10. Enter the command to start installation.
install.bat
11. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
12. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
If you are upgrading from a previous version of Workplace, read the section
entitled ″Lotus Workplace 2.0.1 upgrade.″ There are steps to take before
performing an upgrade.
For more information, see Appendix A.
13. When you are ready to proceed with the installation, click Next at the
Welcome panel.
14. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
15. At the License Agreement, click I accept the terms, and click Next.
16. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
17. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
18. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
19. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
20. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
21. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
100
Installation and Upgrade Guide
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
22. The installer displays the final screen, which shows the location of the
installation logs.
23. Click Finish to complete the installation.
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Related concepts
Lotus Workplace 2.0.1 upgrade
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
Installing on the Deployment Manager
If you are installing IBM Workplace Collaboration Services on a node in a Network
Deployment environment, follow the instructions appropriate to the media and
operating system you have.
DVD
CD-ROM
Downloadable
e-image
IBM AIX
Install
Install
Install
Linux
Install
Install
Install
Sun Solaris
Install
Install
Install
Microsoft Windows
Install
Install
Install
Related concepts
Lotus Workplace 2.0.1 upgrade
Configuring IBM Workplace Collaboration Services
Related tasks
Network Deployment installation and configuration road map
Installing on network nodes
Other ways to install IBM Workplace Collaboration Services
Enabling LDAP security on the Deployment Manager
If you already enabled LDAP security as part of WebSphere Application Server
setup, skip this step and proceed to the next step outlined in the ″Network
Deployment installation and configuration road map.″
If LDAP security is not enabled, after you set up Node 1 and connect it to an
LDAP directory, copy the security values to the Deployment Manager by following
these steps.
1. Open the WebSphere Application Server administrative console for Node 1 by
typing the following URL from a browser window:
Chapter 3 Installing IBM Workplace Collaboration Services
101
http://nodename:9091/admin
where nodename is the fully qualified DNS name of Node 1.
2. Click Security → User Registries → LDAP.
3. In another window, open the WebSphere Application Server administrative
console for the Deployment Manager by typing the following URL from a
browser window:
http://dmname:9090/admin
where dmname is the fully qualified DNS name of the Deployment Manager.
4. Click Security → User Registries → LDAP.
5. Copy the values in the fields listed below from the Node console to the
Deployment Manager console:
Property
Description
Server User ID
The common name of the WebSphere Portal administrator; for
example: uid=wpsadmin,cn=Users,l=Nashville,st=Tennessee,c=US,
ou=SE,o=Sales,dc=acme,dc=com
Server User Password
The password of the user specified in the previous field.
Type
The type of LDAP directory to be used; for example:
IBM_Directory_Server
Host
The fully qualified host name of the LDAP server; for example:
ids51ldap.acme.com
Base Distinguished
Name
The base distinguished name of the directory service, indicating
the starting point for LDAP searches of the directory service; for
example:
l=Nashville,st=Tennessee,c=US,ou=SE,o=Sales,dc=acme,dc=com
Bind Distinguished
Name
The fully qualified distinguished name that the application server
must use to bind to the LDAP directory; for example:
uid=wpsbind,cn=Users,l=Nashville,st=Tennessee,c=US,
ou=SE,o=Sales,dc=acme,dc=com
Bind Password
The password of the user specified in the previous field.
Reuse Connection
Select the check box.
Ignore Case
Select the check box.
SSL
Clear the check box.
6. Click Apply.
7. In both administrative console windows, click Advanced LDAP Settings.
8. Copy the values in the fields listed below from the Node console to the
Deployment Manager console:
Property
Description
User Filter
Add the mail attribute; for example:
(&(|(uid=%v)(mail=%v))(objectclass=inetOrgPerson))
Group Filter
Add the group attribute; for example:
(&(cn=%v)(objectclass=groupOfUniqueNames))
User ID Map
Add the entry *:uid.
Group ID Map
Add the entry *:cn
Group Member ID
Map
Add the group mapping attribute; for example:
groupOfUniqueNames:uniqueMember
9. Click OK.
102
Installation and Upgrade Guide
10. In both administrative console windows, click Security → Authentication
Mechanisms → LTPA.
11. Copy the values in the fields listed below from the Node console to the
Deployment Manager console:
Property
Description
Password
Supply the password.
Confirm Password
Confirm the password.
12. Click Apply.
13. In both administrative console windows, click Single Signon (SSO).
14. Copy the values in the fields listed below from the Node console to the
Deployment Manager console:
Property
Description
Enabled
Select the check box.
Requires SSL
Clear the check box unless you are using SSL at your site.
Domain Name
The domain name; for example, .acme.com. (The period before the
domain name is required.)
15.
16.
17.
18.
Click OK.
Save your changes.
In both administrative console windows, click Security → Global Security.
Copy the values in the fields listed below from the Node console to the
Deployment Manager console:
Property
Description
Enabled
Select the check box.
Enforce Java 2 Security Clear the check box.
Active User Registry
19.
20.
21.
22.
Choose LDAP.
Click OK.
Save your changes.
Log out and close both browser windows.
Shut down the Deployment Manager and restart it.
You have now enabled security on the Deployment Manager. In the future,
you will be prompted for the administrative name and password when you
stop and start the Deployment Manager.
Now perform the next steps covered in ″Network Deployment installation and
configuration road map.″
Related tasks
Network Deployment installation and configuration road map
Installing on the Deployment Manager
Installing on the Deployment Manager from a DVD
If you are installing IBM Workplace Collaboration Services on the Deployment
Manager in a Network Deployment, follow the steps for IBM AIX, Linux, Sun
Solaris, or Microsoft Windows platforms. This type of installation is not available
on IBM i5/OS.
Chapter 3 Installing IBM Workplace Collaboration Services
103
Before you install Workplace Collaboration Services, enable LDAP security on the
Deployment Manager.
Copying SQL Server files from Node 1:
If you are setting up a DBMS server running on SQL Server, you must copy files
from Node 1 to the Deployment Manager after the SQL Server software is
installed. Perform this task before you install Workplace Collaboration Services.
Copy the following files from the <was_root>\lib directory on Node 1 after
Workplace Collaboration Services has been installed. Copy them to the
Deployment Manager’s \WebSphere\DeploymentManager\lib directory:
v sqlserver.jar
v base.jar
v util.jar
Now perform the next steps covered in the ″Network Deployment installation and
configuration road map.″
Installing Workplace Collaboration Services from a DVD:
Follow these steps to install Workplace Collaboration Services on the Deployment
Manager.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. In a command prompt window, navigate to the
<drive>:\WebSphere\DeploymentManager\bin directory and stop the
Deployment Manager using the command:
stopmanager -user admin_name -password admin_password
4. (AIX, Linux, and Solaris) Source the setupCmdLine.sh located under the
<install_directory>/WebSphere/DeploymentManager/bin directory:
# . ./setupCmdLine.sh
5. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
6. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
7. Enter the appropriate command to start installation.
AIX, Linux, and Solaris
./install.sh
Windows
install.bat
8. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
9. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
10. When you are ready to proceed with the installation, click Next at the
Welcome panel.
11. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
12. At the License Agreement, click I accept the terms, and click Next.
104
Installation and Upgrade Guide
13. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (recommended examples are shown below), and then
click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
AIX
/opt/IBM/Workplace
Linux
/opt/IBM/Workplace
Solaris
/opt/IBM/Workplace
Windows
c:\Program Files\IBM\Workplace
14. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
15. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
16. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
17. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
18.
19.
20.
21.
22.
23.
Confirm the password, and then click Next.
At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
If you don’t know the node and cell name, navigate to the WebSphere
\config\cells directory and look for the following names:
v The cell name is shown in <was_root>\config\cells\<cellname>
v The node name is shown in
<was_root>\config\cells\<cellname>\nodes\<nodeName>.
At the panel ″Select the database type,″ select the type of DBMS system you
installed in Phase 2, and then click Next.
At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database application user on this server. Then
click Next.
At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Chapter 3 Installing IBM Workplace Collaboration Services
105
Field
LWPDBDriver
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database. For example:
DB2
COM.ibm.db2.jdbc.app.DB2Driver
Oracle
oracle.jdbc.driver.OracleDriver
SQL Server
LWPDbLibrary
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
Specify the database driver class and enter
the location of the zip file that has the
database driver class. For example:
DB2
D:/IBM/SQLLIB/java/db2java.zip
Oracle
C:/oracle/ora92/jdbc/lib/classes12.zip
SQL Server
c:\WebSphere\DeploymentManager\lib\sqlserver.jar,
c:\WebSphere\DeploymentManager\lib\base.jar,
LWPDBName
LWPDBUrl
c:\WebSphere\DeploymentManager\lib\util.jar
Enter the database name (for example,
wps50).
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>, where
<database_name> is the value of
LWPDBName. For example:
DB2
jdbc:db2:wps50
Oracle
jdbc:oracle:oci:@<tns entry alias>
SQL Server
jdbc:microsoft:sqlserver://<SqlServer
Name>:1433;DatabaseName=wps50
24. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
25. The installer displays the final screen, which shows the location of the
installation logs.
106
Installation and Upgrade Guide
26. Click Finish to complete the installation.
Completing the data source setup for SQL Server:
If you are using a SQL Server database, follow these steps after installing
Workplace Collaboration Services to create one of the custom properties on the
data source required by the database.
1. In the WebSphere Administrative Console, navigate to Resources → JDBC
Providers.
2. Select the node name for the deployment manager (typically
<servername>Manager) and click ″apply″.
3. From the list of available jdbc providers (there should be only one), select
″lwp25jdbc″. This opens a new page.
4. Scroll to the bottom and select Data Sources.
5. Select ″lwpApp″ from the list of data sources (there should be only one). This
opens a new page.
6. Scroll to the bottom and select Custom Properties, then click New.
7. In the page that opens, enter ″serverName″ for Name.
8. For Value, enter the full DNS for the database server machine.
9. Click OK and save all changes, selecting the option to synchronize with nodes
if there is an existing cell.
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Installing on the Deployment Manager from CD-ROM
Installing on the Deployment Manager from an e-image
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
Root installation directories
Installing on the Deployment Manager from CD-ROM
This topic provides a CD-based alternative method for installing IBM Workplace
Collaboration Services. Installation in a Network Deployment is not available on
IBM i5/OS.
Before you install Workplace Collaboration Services, enable LDAP security on the
Deployment Manager.
If you are installing on the Deployment Manager on other platforms, follow the
steps in this topic to:
v Copy SQL Server files (if appropriate for your site)
v Install Workplace Collaboration Services on IBM AIX, Linux, and Sun Solaris or
Microsoft Windows platforms.
v Complete data source setup for SQL Server (if appropriate for your site)
Copying SQL Server files from Node 1:
Chapter 3 Installing IBM Workplace Collaboration Services
107
If you are setting up a DBMS server running on SQL Server, you must copy files
from Node 1 to the Deployment Manager after the SQL Server software is
installed. Perform this task before you install Workplace Collaboration Services.
Copy the following files from the <was_root>\lib directory on Node 1 after
Workplace Collaboration Services has been installed. Copy them to the
Deployment Manager’s \WebSphere\DeploymentManager\lib directory:
v sqlserver.jar
v base.jar
v util.jar
Now perform the next steps covered in the ″Network Deployment installation and
configuration road map.″
Installing Workplace Collaboration Services from CDs (AIX, Linux, and
Solaris):
Follow these steps to install Workplace Collaboration Services on the Deployment
Manager from CDs. You must copy the contents of the CDs to the local drive; you
cannot install directly from CDs.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. In a command prompt window, navigate to the
/WebSphere/DeploymentManager/bin directory and stop the Deployment
Manager using the command:
stopmanager -user admin_name -password admin_password
4. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
5. Create a downloads directory on your hard drive, for example,
/opt/downloads).
6. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
7. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
AIX
/LWPArchives/WAS_Archive_AIX.tar.gz
/LWPArchives/WPS_Archive_AIX.tar.gz
Linux
/LWPArchives/WAS_Archive_Linux.tar.gz
/LWPArchives/WPS_Archive_Linux.tar.gz
Solaris
/LWPArchives/WAS_Archive_Solaris.tar.gz
108
Installation and Upgrade Guide
/LWPArchives/WPS_Archive_Solaris.tar.gz
8. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
9. Change to the local LWPServer directory.
10. Source the setupCmdLine.sh located under the
<install_directory>/WebSphere/DeploymentManager/bin directory:
# . ./setupCmdLine.sh
11. Change to the local LWPServer directory.
12. Enter the command to start installation.
./install.sh
13. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
14. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
15. When you are ready to proceed with the installation, click Next at the
Welcome panel.
16. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
17. At the License Agreement, click I accept the terms, and click Next.
18. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
19. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
20. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
21. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
22. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
23. At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
24. At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
25. At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
If you don’t know the node and cell name, navigate to the WebSphere
\config\cells directory and look for the following names:
v The cell name is shown in <was_root>/config/cells/<cellname>
Chapter 3 Installing IBM Workplace Collaboration Services
109
v The node name is shown in
<was_root>/config/cells/<cellname>/nodes/<nodeName>.
26. At the panel ″Select the database type,″ select the type of DBMS system you
installed in Phase 2, and then click Next.
27. At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database application user on this server. Then
click Next.
28. At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Field
LWPDBDriver
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database. For example:
DB2
COM.ibm.db2.jdbc.app.DB2Driver
Oracle
oracle.jdbc.driver.OracleDriver
SQL Server
LWPDbLibrary
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
Specify the database driver class and enter
the location of the zip file that has the
database driver class. For example:
DB2
/IBM/SQLLIB/java/db2java.zip
Oracle
/oracle/ora92/jdbc/lib/classes12.zip
SQL Server
/WebSphere/DeploymentManager/lib/sqlserver.jar,
/WebSphere/DeploymentManager/lib/base.jar,
LWPDBName
110
Installation and Upgrade Guide
/WebSphere/DeploymentManager/lib/util.jar
Enter the database name (for example,
wps50).
Field
LWPDBUrl
Description
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>, where
<database_name> is the value of
LWPDBName. For example:
DB2
jdbc:db2:wps50
Oracle
jdbc:oracle:oci:@<tns entry alias>
SQL Server
jdbc:microsoft:sqlserver://<SqlServer
Name>:1433;DatabaseName=wps50
29. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
30. The installer displays the final screen, which shows the location of the
installation logs.
31. Click Finish to complete the installation.
Installing Workplace Collaboration Services from CDs (Windows):
Follow these steps to install Workplace Collaboration Services on the Deployment
Manager from CDs. You must copy the contents of the CDs to the local drive; you
cannot install directly from CDs.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. In a command prompt window, navigate to the
<drive>:\WebSphere\DeploymentManager\bin directory and stop the
Deployment Manager using the command:
stopmanager -user admin_name -password admin_password
4. Gather the following CDs:
v Server Install and Migration Tools
v Learning Client Tools
v Server Archive Install 1 of 6
v Server Archive Install 2 of 6
v Server Archive Install 3 of 6
v Server Archive Install 4 of 6
v Server Archive Install 5 of 6
v Server Archive Install 6 of 6
5. Create a downloads directory on your hard drive, for example, C:\downloads.
6. Copy the contents of all CDs except the Service Archive Install 6 CD into the
downloads directory.
7. Copy the following files from the Server Archive Install 6 CD into the
downloads directory.
Chapter 3 Installing IBM Workplace Collaboration Services
111
\LWPArchives\WAS_Archive_Windows.tar.gz
\LWPArchives\WPS_Archive_Windows.tar.gz
8. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
9. Change to the local LWPServer directory.
10. Change to the local LWPServer directory.
11. Enter the command to start installation.
install.bat
12. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
13. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
14. When you are ready to proceed with the installation, click Next at the
Welcome panel.
15. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
16. At the License Agreement, click I accept the terms, and click Next.
17. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
18. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
19. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
20. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
21. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
22. At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
23. At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
24. At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
If you don’t know the node and cell name, navigate to the WebSphere
\config\cells directory and look for the following names:
v The cell name is shown in <was_root>\config\cells\<cellname>
v The node name is shown in
<was_root>\config\cells\<cellname>\nodes\<nodeName>.
112
Installation and Upgrade Guide
25. At the panel ″Select the database type,″ select the type of DBMS system you
installed in Phase 2, and then click Next.
26. At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database application user on this server. Then
click Next.
27. At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Field
LWPDBDriver
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database. For example:
DB2
COM.ibm.db2.jdbc.app.DB2Driver
Oracle
oracle.jdbc.driver.OracleDriver
SQL Server
LWPDbLibrary
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
Specify the database driver class and enter
the location of the zip file that has the
database driver class. For example:
DB2
D:/IBM/SQLLIB/java/db2java.zip
Oracle
C:/oracle/ora92/jdbc/lib/classes12.zip
SQL Server
c:\WebSphere\DeploymentManager\lib\sqlserver.jar,
c:\WebSphere\DeploymentManager\lib\base.jar,
LWPDBName
c:\WebSphere\DeploymentManager\lib\util.jar
Enter the database name (for example,
wps50).
Chapter 3 Installing IBM Workplace Collaboration Services
113
Field
LWPDBUrl
Description
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>, where
<database_name> is the value of
LWPDBName. For example:
DB2
jdbc:db2:wps50
Oracle
jdbc:oracle:oci:@<tns entry alias>
SQL Server
jdbc:microsoft:sqlserver://<SqlServer
Name>:1433;DatabaseName=wps50
28. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
29. The installer displays the final screen, which shows the location of the
installation logs.
30. Click Finish to complete the installation.
Completing the data source setup for SQL Server:
If you are using a SQL Server database, follow these steps after installing
Workplace Collaboration Services to create one of the custom properties on the
data source required by the database.
1. In the WebSphere Administrative Console, navigate to Resources → JDBC
Providers.
2. Select the node name for the deployment manager (typically
<servername>Manager) and click ″apply″.
3. From the list of available jdbc providers (there should be only one), select
″lwp25jdbc″. This opens a new page.
4. Scroll to the bottom and select Data Sources.
5. Select ″lwpApp″ from the list of data sources (there should be only one). This
opens a new page.
6. Scroll to the bottom and select Custom Properties, then click New.
7. In the page that opens, enter ″serverName″ for Name.
8. For Value, enter the full DNS for the database server machine.
9. Click OK and save all changes, selecting the option to synchronize with nodes
if there is an existing cell.
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
114
Installation and Upgrade Guide
Administrator names and passwords worksheet
Root installation directories
Installing on the Deployment Manager from an e-image
This topic provides an e-image alternative for installing IBM Workplace
Collaboration Services. Installation in a Network Deployment is not available on
IBM i5/OS.
To download from the Web, go to http://www306.ibm.com/software/howtobuy/passportadvantage/.
Before you install Workplace Collaboration Services, enable LDAP security on the
Deployment Manager.
If you are installing on the Deployment Manager on other platforms, follow the
steps in this topic to:
v Copy SQL Server files (if appropriate for your site)
v Install Workplace Collaboration Services on IBM AIX, Linux, and Sun Solaris or
Microsoft Windows platforms.
v Complete data source setup for SQL Server (if appropriate for your site)
Copying SQL Server files from Node 1:
If you are setting up a DBMS server running on SQL Server, you must copy files
from Node 1 to the Deployment Manager after the SQL Server software is
installed. Perform this task before you install Workplace Collaboration Services.
Copy the following files from the <was_root>\lib directory on Node 1 after
Workplace Collaboration Services has been installed. Copy them to the
Deployment Manager’s \WebSphere\DeploymentManager\lib directory:
v sqlserver.jar
v base.jar
v util.jar
Now perform the next steps covered in the ″Network Deployment installation and
configuration road map.″
Installing Workplace Collaboration Services from an e-image (AIX, Linux, and
Solaris):
Follow these steps to install Workplace Collaboration Services on the Deployment
Manager from an e-image.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. In a command prompt window, navigate to the
/WebSphere/DeploymentManager/bin directory and stop the Deployment
Manager using the command:
stopmanager -user admin_name -password admin_password
4. Source the setupCmdLine.sh located under the
<install_directory>/WebSphere/DeploymentManager/bin directory:
# . ./setupCmdLine.sh
5. Create directories on your hard drive.
Chapter 3 Installing IBM Workplace Collaboration Services
115
a. Create a downloads directory, for example, /opt/downloads.
b. Create an install directory, for example, /opt/install.
c. Create a directory called LWPArchives under the install directory, for
example, /opt/install/LWPArchives.
6. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v C82MGML.tar.gz
v C82MHML.tar.gz
v C82MIML.tar.gz
v C82MJML.tar.gz
v C83CCML.tar.gz
v C83XQML.tar.gz
7. Download the following platform-specific files to the downloads directory.
AIX
v C82MDML.tar
v C82MEML.tar
v C82MNML.tar.gz
v C83XTML.tar.gz
Linux
v C82MDML.tar
v C82MEML.tar
v C82MLML.tar.gz
v C83XRML.tar.gz
Solaris
v C82MDML.tar
v C82MEML.tar
v C82MMML.tar.gz
v C83XSML.tar.gz
8. Move or copy the files from the downloads directory to the LWPArchives
directory.
9. Rename the files in the LWPArchives directory as shown in the following
table. The images can be renamed without making separate copies of the files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
10. Rename the following platform-specific files in the LWPArchives directory as
shown in the table.
AIX
116
Installation and Upgrade Guide
Download image
Renamed file
C82MNML.tar.gz
WAS_Archive_AIX.tar.gz
C83XTML.tar.gz
WPS_Archive_AIX.tar.gz
Linux
Download image
Renamed file
C82MLML.tar.gz
WAS_Archive_Linux.tar.gz
C83XRML.tar.gz
WPS_Archive_Linux.tar.gz
Solaris
Download image
Renamed file
C82MMML.tar.gz
WAS_Archive_Solaris.tar.gz
C83XSML.tar.gz
WPS_Archive_Solaris.tar.gz
11. Extract the following files to the install directory, preserving the directory
structure.
v C82MDML.tar
v C82MEML.tar
12. Verify that you have the following directory structure on your hard drive.
<download_directory>/LMSClient
<download_directory>/LWPArchives
<download_directory>/LWPServer
<download_directory>/LWPUserMigration
<download_directory>/DB2/PMR36414
13. Change to the local LWPServer directory.
14. Enter the command to start installation.
./install.sh
15. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
16. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
17. When you are ready to proceed with the installation, click Next at the
Welcome panel.
18. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
19. At the License Agreement, click I accept the terms, and click Next.
20. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (/opt/IBM/Workplace is recommended), and then click
Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
21. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
22. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
Chapter 3 Installing IBM Workplace Collaboration Services
117
23. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
24. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
25. At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
26. At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
27. At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
If you don’t know the node and cell name, navigate to the WebSphere
/config/cells directory and look for the following names:
v The cell name is shown in <was_root>/config/cells/<cellname>
v The node name is shown in
<was_root>/config/cells/<cellname>/nodes/<nodeName>.
28. At the panel ″Select the database type,″ select the type of DBMS system you
installed in Phase 2, and then click Next.
29. At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database application user on this server. Then
click Next.
30. At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Field
LWPDBDriver
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database. For example:
DB2
COM.ibm.db2.jdbc.app.DB2Driver
Oracle
oracle.jdbc.driver.OracleDriver
SQL Server
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
118
Installation and Upgrade Guide
Field
LWPDbLibrary
Description
Specify the database driver class and enter
the location of the zip file that has the
database driver class. For example:
DB2
/IBM/SQLLIB/java/db2java.zip
Oracle
/oracle/ora92/jdbc/lib/classes12.zip
SQL Server
/WebSphere/DeploymentManager/lib/sqlserver.jar,
/WebSphere/DeploymentManager/lib/base.jar,
LWPDBName
LWPDBUrl
/WebSphere/DeploymentManager/lib/util.jar
Enter the database name (for example,
wps50).
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>, where
<database_name> is the value of
LWPDBName. For example:
DB2
jdbc:db2:wps50
Oracle
jdbc:oracle:oci:@<tns entry alias>
SQL Server
jdbc:microsoft:sqlserver://<SqlServer
Name>:1433;DatabaseName=wps50
31. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
32. The installer displays the final screen, which shows the location of the
installation logs.
33. Click Finish to complete the installation.
Installing Workplace Collaboration Services from an e-image (Windows):
Follow these steps to install Workplace Collaboration Services on the Deployment
Manager from an e-image.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. In a command prompt window, navigate to the
<drive>:\WebSphere\DeploymentManager\bin directory and stop the
Deployment Manager using the command:
Chapter 3 Installing IBM Workplace Collaboration Services
119
stopmanager -user admin_name -password admin_password
4. Create directories on your hard drive.
a. Create a downloads directory, for example, D:\downloads.
b. Create an install directory, for example, D:\install.
c. Create a directory called LWPArchives under the install directory, for
example, D:\install\LWPArchives.
5. Download the following tar.gz images to the downloads directory:
v C82MFML.tar.gz
v
v
v
v
v
C82MGML.tar.gz
C82MHML.tar.gz
C82MIML.tar.gz
C82MJML.tar.gz
C82MKML.tar.gz
v C83CAML.exe
v C83CBML.exe
v C83CCML.tar.gz
v C83XQML.tar.gz
v C83XUML.tar.gz
6. Move or copy the files from the downloads directory to the LWPArchives
directory.
7. Rename the files in the LWPArchives directory as shown in the following
table. The images can be renamed without making separate copies of the files.
Download image
Renamed file
C82MFML.tar.gz
LWP_Archive_Common1.tar.gz
C82MGML.tar.gz
LWP_WAS_Archive_Common1.tar.gz
C82MHML.tar.gz
LWP_WAS_Archive_Common2.tar.gz
C82MIML.tar.gz
LWP_WPS_Archive_Common1.tar.gz
C82MJML.tar.gz
WAS_Archive_Common1.tar.gz
C82MKML.tar.gz
WAS_Archive_Windows.tar.gz
C83CCML.tar.gz
LWP_Upgrade_Archive_Common1.tar.gz
C83XQML.tar.gz
WPS_Archive_Common1.tar.gz
C83XUML.tar.gz
WPS_Archive_Windows.tar.gz
8. Extract the following files to the install directory, preserving the directory
structure.
v C83CAML.exe
v C83CBML.exe
9. Verify that you have the following directory structure on your hard drive.
<download_directory>\LMSClient
<download_directory>\LWPArchives
<download_directory>\LWPServer
<download_directory>\LWPUserMigration
<download_directory>\DB2\PMR36414
10. Change to the local LWPServer directory.
11. Enter the command to start installation.
120
Installation and Upgrade Guide
install.bat
12. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
13. Optional: At the panel “Welcome to the IBM Workplace Installation,” click
Launch Getting Started to access information about planning, hardware and
software requirements, installation procedures, and configuration tasks.
14. When you are ready to proceed with the installation, click Next at the
Welcome panel.
15. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
16. At the License Agreement, click I accept the terms, and click Next.
17. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (c:\Program Files\IBM\Workplace is recommended),
and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
18. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
19. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
20. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
21. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace administrator.
Confirm the password, and then click Next.
22. At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
23. At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
24. At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
If you don’t know the node and cell name, navigate to the WebSphere
\config\cells directory and look for the following names:
v The cell name is shown in <was_root>\config\cells\<cellname>
v The node name is shown in
<was_root>\config\cells\<cellname>\nodes\<nodeName>.
25. At the panel ″Select the database type,″ select the type of DBMS system you
installed in Phase 2, and then click Next.
26. At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database application user on this server. Then
click Next.
27. At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Chapter 3 Installing IBM Workplace Collaboration Services
121
Field
LWPDBDriver
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database. For example:
DB2
COM.ibm.db2.jdbc.app.DB2Driver
Oracle
oracle.jdbc.driver.OracleDriver
SQL Server
LWPDbLibrary
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
Specify the database driver class and enter
the location of the zip file that has the
database driver class. For example:
DB2
D:/IBM/SQLLIB/java/db2java.zip
Oracle
C:/oracle/ora92/jdbc/lib/classes12.zip
SQL Server
c:\WebSphere\DeploymentManager\lib\sqlserver.jar,
c:\WebSphere\DeploymentManager\lib\base.jar,
LWPDBName
LWPDBUrl
c:\WebSphere\DeploymentManager\lib\util.jar
Enter the database name (for example,
wps50).
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>, where
<database_name> is the value of
LWPDBName. For example:
DB2
jdbc:db2:wps50
Oracle
jdbc:oracle:oci:@<tns entry alias>
SQL Server
jdbc:microsoft:sqlserver://<SqlServer
Name>:1433;DatabaseName=wps50
28. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
29. The installer displays the final screen, which shows the location of the
installation logs.
122
Installation and Upgrade Guide
30. Click Finish to complete the installation.
Completing the data source setup for SQL Server:
If you are using a SQL Server database, follow these steps after installing
Workplace Collaboration Services to create one of the custom properties on the
data source required by the database.
1. In the WebSphere Administrative Console, navigate to Resources → JDBC
Providers.
2. Select the node name for the deployment manager (typically
<servername>Manager) and click ″apply″.
3. From the list of available jdbc providers (there should be only one), select
″lwp25jdbc″. This opens a new page.
4. Scroll to the bottom and select Data Sources.
5. Select ″lwpApp″ from the list of data sources (there should be only one). This
opens a new page.
6. Scroll to the bottom and select Custom Properties, then click New.
7. In the page that opens, enter ″serverName″ for Name.
8. For Value, enter the full DNS for the database server machine.
9. Click OK and save all changes, selecting the option to synchronize with nodes
if there is an existing cell.
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Other ways to install IBM Workplace Collaboration Services
Network Deployment installation and configuration road map
Related reference
Pre-installation checklist
Administrator names and passwords worksheet
Root installation directories
Other ways to install IBM Workplace Collaboration Services
You can install IBM Workplace Collaboration Services in these other ways:
v Installing from the console
This method allows you to install from a command prompt.
v Installing with a response file
This method allows you to run an unattended installation.
Related tasks
Phase 3: Installing IBM Workplace Collaboration Services
Installing from a response file
IBM Workplace Collaboration Services can be installed from a command prompt
with a response file. This method makes displaying the graphical interface and
waiting for user input unnecessary; it is useful when you want to install Workplace
Collaboration Services on multiple servers using a similar configuration, or when it
is impractical to manually enter responses during installation.
Running the installation program on IBM AIX, Linux, Sun Solaris, and
Microsoft Windows:
Chapter 3 Installing IBM Workplace Collaboration Services
123
Create a response file and enter the parameters for the installation you want to
create. Then follow these steps to install Workplace Collaboration Services with the
response file on AIX, Linux, Solaris or Windows.
1. Prepare to run the installation program. For more information, see Chapter 3.
2. Log in to the server as a user with administrative privileges.
3. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
4. Navigate to the folder called LWPServer on the installation DVD and enter the
appropriate command to start installation.
Provide the full path name and file name for the response file you created.
IBM AIX
./usr/LWPServer/install.sh -options /path/response_file
Linux
./opt/LWPServer/install.sh -options /path/response_file
Sun Solaris
./opt/LWPServer/install.sh -options /path/response_file
Microsoft Windows
install.bat -options path\response_file
After installation, you can configure Workplace Collaboration Services as needed
for your site.
Running the installation program on IBM i5/OS:
Follow these steps to install using a response file on IBM i5/OS.
Note: Installation with a response file can be performed remotely from a
Windows-based workstation or locally on the IBM eServer i5 server. These
instructions are for a local install. To install remotely from a Windows
workstation, follow the previous instructions for Windows using the
command install400.bat instead of install.bat.
1. Prepare to run the installation program. For more information, see Chapter 3.
2. Insert the Workplace Collaboration Services installation DVD into the optical
drive of your server.
3. Fill in the response file with information appropriate for your environment and
save it to a location on your server.
4. Start the QShell Interpreter by entering the following:
STRQSH
5. Change to the system root directory by entering the following:
cd /
6. Start installation of Workplace Collaboration Services by entering the following:
/qopt/C83ZEML/LWPServer/install.sh -options path/response_file
where path/response_file is the directory path and file name of your response file.
After installation, you can configure Workplace Collaboration Services as needed
for your site.
Related concepts
Configuring IBM Workplace Collaboration Services
Related reference
Pre-installation checklist
124
Installation and Upgrade Guide
Response file parameters for an unattended installation
Response file parameters for an unattended installation:
The response file contains the information you provide directly when you install
IBM Workplace Collaboration Services, through either the installation screens or
the command console. When you install with a response file, the installation
program determines your installation choices from the response file.
You must supply the parameters in the following table in your response file. The
first column shows each parameter with its default value. The second column
describes the parameter and provides possible values for it. All values must be
enclosed in double quotes ( ″″ ). Note that if a required parameter is not specified
in this response file, an error message displays.
Parameter
Description
-silent
Unattended installation choice
This parameter runs the installation without the graphical
interface.
If you want to use a response file and continue to show
the graphical interface and user input prompts, comment
out this parameter.
-W offeringsPanel.offerings=
″<value>″
Product offering selection
Specify the products that you have licensed. This option
accepts a comma-delimited list of offering IDs:
learning - IBM Workplace Collaborative Learning
docmgt - IBM Workplace Documents
msg - IBM Workplace Messaging
team - IBM Workplace Team Collaboration
all - IBM Workplace Collaboration Services
mgdclient - IBM Workplace Managed Client
wccm - Software prerequisites for IBM Workplace Web
Content Management
Examples:
-W offeringsPanel.offerings=learning,msg,team
-W offeringsPanel.offerings=learning,docmgt,msg,team,all,
mgdclient,wccm
Chapter 3 Installing IBM Workplace Collaboration Services
125
Parameter
Description
-W product.location=″<value>″
Installation directory (for IBM AIX, Linux, Sun Solaris,
and Microsoft Windows)
Specify the directory where you want to install Workplace
Collaboration Services, following the convention for
specifying path information on your platform.
If you are installing on IBM i5/OS, leave this value blank.
On i5/OS, product files are always installed to the
directory QIBM/Lotus/WorkplaceServer/WCS25.
Examples:
AIX
-W product.location=″/usr/IBM/Workplace″
Linux and Solaris
-W product.location=″/opt/IBM/Workplace″
Windows
-W product.location=″c:\Program Files\IBM\Workplace″
-W singleOrNdPanel.choice=
″<value>″
Installation type
Specify whether this installation is a single-server or a
Network Deployment using the following choices:
single - Single-server installation
nd - Network Deployment installation
-W
nodeOrDmPanel.nodeOrDm
=″″value>″
Network Deployment Installation Type
If you selected a Network Deployment installation type,
specify whether this installation is for the Deployment
Manager server or one of the Network Deployment
nodes.
dm - the Deployment Manager server
node - a Network Deployment node
-W node.hostName=″<value>″
Workplace server host name
Specify the fully qualified host name or IP address of the
computer running Workplace Collaboration Services; for
example, ″workplace.acme.com.″
-W admin.user=″<value>″
-W admin.password=″<value>″
-W admin.passwordConfirm=
″<value>″
126
Installation and Upgrade Guide
Workplace Collaboration Services administrator name and
password
Provide a name for the administrator and then provide a
password and confirm the password. If you plan to
connect to an existing LDAP directory, this user name and
password must already exist in your user directory.
Parameter
Description
-W cd11MediaPanel.cdPath=″<value>″
Install disc source (AIX, Linux, Solaris, Windows)
Specify the directory path to the LWP Archive Disc.
Although this can be to a CD-ROM drive, for unattended
installations, this location is more likely to be a directory
where electronic product images are stored, such as on a
network drive. Follow the convention for specifying path
information on your platform.
Example:
/LWPDVD/LWPArchives
-W
Workplace Collaboration Services install media location
i5InstallMedia.cdPath=″<value>″ (i5/OS ONLY)
Specify the directory path to Workplace Collaboration
Services media. For i5/OS remote install, this is the path
to the CD-ROM drive on the Windows system (for
example, D:\).
Example:
/qopt/<cd-root>/LWPMedia
-W
instance.instname=″<value>″
Workplace Collaboration Services instance name (for
i5/OS)
Specify the name of the Workplace Collaboration Services
instance to be created.
Example:
-W instance.instname=″myinstance″
-W port.enterports=″<value>″
Workplace Collaboration Services instance port range (for
i5/OS)
Specify the first of 50 consecutive ports to be used by the
Workplace server.
Example:
-W port.enterports=″30501″
(In this example, ports 30501-30550 would be used.)
Chapter 3 Installing IBM Workplace Collaboration Services
127
Parameter
Description
-W dmAdminPanel.user=
″<value>″
Deployment Manager installation settings
-W dmAdminPanel.password=
″<value>″
-W dmAdminPanel.password
Confirm =″<value>″
If you are installing on a Deployment Manager server in a
Network Deployment, specify the Deployment Manager
administrator credentials, Deployment Manager location,
node name, cell name, and location of Workplace
installation files and Deployment Manager installation
files.
-W
Example:
dmLocationPanel.dmLocation=
″<value>″
-W dmAdminPanel.user=″dmAdmin″
-W dmInfoPanel.nodename=
″<value>″
-W dmInfoPanel.cellname=
″<value>″
-W cd11MediaPanelDM.cdPath
=″<value>″
-W dmAdminPanel.password=″dmAdminPassword″
-W
dmAdminPanel.passwordConfirm=″dmAdminPassword″
-W dmLocationPanel.dmLocation
=″/opt/WebSphere/DeploymentManager″
-W dmInfoPanel.nodename=″nodeManager″
-W dmInfoPanel.cellname=″cellNetwork″
-W cd11MediaPanelDM.cdPath=″/LWPDVD/LWPArchives″
-W
dmDbChoicePanel.dbChoice=
″<value>″
-W
dmDbAppUserPanel.username
= ″<value>″
Deployment Manager database settings
If you are installing on a Deployment Manager server in a
Network Deployment, specify the following database
properties according to your Deployment Manager (DM)
installation.
Valid dbChoice values are:
-W
dmDbAppUserPanel.password
=″<value>″
db2, db2iSeries, oracle, mssql
-W dmDbAppUserPanel.
confirmpassword =″<value>″
-W dmDbChoicePanel.dbChoice=″db2″
-W dmDbConnInfoPanel.
driverclass =″<value>″
-W dmDbConnInfoPanel.
driverlibrary =″<value>″
-W
dmDbConnInfoPanel.dbname
=″<value>″
-W dmDbConnInfoPanel.
jdbcurl =″<value>″
Examples:
-W dmDbAppUserPanel.username=″dbAdmin″
-W dmDbAppUserPanel.password= ″dbAdminPassword″
-W dmDbAppUserPanel.confirmpassword=
″dbAdminPassword″
-W dmDbConnInfoPanel.driverclass=
″COM.ibm.db2.jdbc.app.DB2Driver″
-W dmDbConnInfoPanel.driverlibrary=
″D:/IBM/SQLLIB/java/db2java.zip″
-W dmDbConnInfoPanel.dbname=″wps50″
-W dmDbConnInfoPanel.jdbcurl=″jdbc:db2:wps50″
128
Installation and Upgrade Guide
Parameter
Description
-W foundOldLwp.
IBM Lotus Workplace 2.0.1 Upgrade/New installation
existingLwpChoice = ″<value>″ options
Setup will detect if you already have an older installation.
Specify which type of installation you want to perform:
new - install a new, separate installation of Workplace
Collaboration Services 2.5.
upgrade - upgrade the existing installation to Workplace
Collaboration Services 2.5.
-W foundLwp25.
Workplace Collaboration Services 2.5 Upgrade/New
existingLwpChoice = ″<value>″ installation options
Setup will detect if you have an existing installation.
Specify a new installation with the following value:
new - install a new, separate Workplace Collaboration
Services 2.5 installation.
If you leave this value blank, Workplace Collaboration
Services will be installed over the existing installation.
CAUTION:
You should not store actual user names and passwords in the response file. The
response file is not encrypted, so it can be read by anyone who can access this
file. When you want to run an installation using the file, insert the correct
values for all user names and passwords. After the installation is complete,
remove the user names and passwords.
Related tasks
Installing with a response file
Installing using the console interface
The IBM Workplace Collaboration Services installation program provides a console
interface, which enables you to perform an interactive installation from a command
prompt. The console interface presents the same content as the graphical interface,
but in a textual form. Prompts at the bottom of each screen tell you how to enter
numbers to make your selections and proceed to the next screen.
Installing Workplace Collaboration Services on AIX, Linux, Solaris, and
Windows:
Follow these steps to install Workplace Collaboration Services using the console
interface on AIX, Linux, Solaris or Windows.
1. Prepare to run the installation program.
2. Log in to the server as a user with administrative privileges.
3. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
4. Navigate to the folder called LWPServer on the installation DVD and enter the
appropriate command to start installation.
AIX
./usr/LWPServer/install.sh -console
Linux
Chapter 3 Installing IBM Workplace Collaboration Services
129
./opt/LWPServer/install.sh -console
Solaris
./opt/LWPServer/install.sh -console
Windows
c:\LWPServer\install.bat -console
After installation, you can configure Workplace Collaboration Services as needed
for your site.
Installing Workplace Collaboration Services on IBM i5/OS:
Follow these steps to install Workplace Collaboration Services using the console
interface on i5/OS.
1. Prepare to run the installation program.
2. Insert the Workplace Collaboration Services installation DVD into the optical
drive of your IBM eServer i5 server.
3. Start the QShell Interpreter by entering the following:
STRQSH
4. Change to the system root directory by entering the following:
cd /
5. Start installation of Workplace Collaboration Services by entering the following:
/qopt/C83ZEML/LWPServer/install.sh
After installation, you can configure Workplace Collaboration Services as needed
for your site.
Related concepts
Configuring IBM Workplace Collaboration Services
Related reference
Pre-installation checklist
Configuring IBM Workplace Collaboration Services
After you install IBM Workplace Collaboration Services, finish setting it up by
performing all of the tasks that apply to your site.
Configuring on AIX, Linux, Solaris, and Windows
Configure Workplace Collaboration Services on IBM AIX, Linux, Sun Solaris, and
Microsoft Windows as needed for your site:
v Connect to an LDAP Directory if you plan to use an existing LDAP directory.
v Connect to a DBMS server if you installed a remote database server.
v Connect to an external HTTP Server if you plan to bypass the internal HTTP
mechanism supplied with the product.
v Set up IBM Workplace Collaborative Learning if you installed Workplace
Collaborative Learning.
v Install the rich client provisioning server to distribute the rich client to users.
v Complete the Network Deployment Setup if you installed in a Network
Deployment.
Configuring on i5/OS
Configure Workplace Collaboration Services on IBM i5/OS in one of these ways:
130
Installation and Upgrade Guide
v Start the Create IBM Workplace Collaboration Services wizard to configure
Virtual Network Computing, an IBM DB2 server, and an HTTP server
automatically, and optionally, an LDAP server and Workplace Collaborative
Learning.
v Configure components separately:
– Configure Virtual Network Computing.
– Connect to an LDAP Directory if you plan to use an existing LDAP directory.
– Connect to a DBMS server if you plan to use a remote database server.
– Connect to an external HTTP Server if you plan to bypass the internal HTTP
mechanism supplied with the product.
– Set up Collaborative Learning if you installed IBM Workplace Collaborative
Learning.
– Install the rich client provisioning server to distribute the rich client to users.
Related tasks
Phase 3: Installing IBM Workplace Collaboration Services
Starting the Create IBM Workplace Collaboration Services wizard
(i5/OS only)
IBM Web Administration for IBM i5/OS includes a Create IBM Workplace
Collaboration Services wizard to help you configure all components in a
production-level environment. When you install IBM Workplace Collaboration
Services using the IBM Workplace setup wizard for i5/OS option, the final screen
of the installation program gives you the option of starting the wizard. If starting
the wizard immediately after installing Workplace Collaboration Services is not
convenient, you can also manually start it by following the instructions below.
The Create IBM Workplace Collaboration Services wizard is only available for
i5/OS. Before starting the wizard, you should have installed using the IBM
Workplace setup wizard for i5/OS option. In addition, if you are configuring a
rich client provisioning server, complete the steps in the topic ″Preparing for rich
client setup (i5/OS)″ before starting the Create IBM Workplace Collaboration
Services wizard.
Note: Allow at least 30 minutes to fill in the information required by the wizard.
Once you have filled in the information, the wizard may take several hours
or more to complete the configuration.
To start the Create IBM Workplace Collaboration Services wizard:
1. Start the administrative HTTP server on the server hosting Workplace
Collaboration Services by entering the following on an i5/OS command line:
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
2. From a workstation connected to your server, enter the following into the
address bar of a Web browser:
http://hostname.yourco.com:2001/HTTPAdmin
where hostname.yourco.com is the fully qualified host name of your server.
3. Sign on to the server with an ID that has at least *ALLOBJ, *IOSYSCFG, and
*JOBCTL special authorities.
Note: To use the wizard to create a new database user profile, you will also
need *SECADM authority.
4. On the Setup tab, click Create IBM Workplace.
Chapter 3 Installing IBM Workplace Collaboration Services
131
Fill out each wizard screen with information appropriate for your deployment.
Related concepts
Configuring IBM Workplace Collaboration Services
Related tasks
Single-server installation and configuration road map
Preparing for rich client setup (i5/OS)
If you are setting up a rich client provisioning server on i5/OS, the Create IBM
Workplace Collaboration Services wizard can install and configure the rich
client for you. Follow these steps to enable the Create IBM Workplace
Collaboration Services wizard to install and configure the rich client.
Configuring Virtual Network Computing (i5/OS only)
In order to enable the Learning and PDM functionality of IBM Workplace
Collaboration Services on IBM i5/OS, you must set up an AT&T Virtual Network
Computing (VNC) server to work with your Workplace Collaboration Services
instance. Since i5/OS does not contain native graphics support, a VNC server is
required to perform the document conversion required by these functions.
The following steps only need to be performed if you are installing Workplace
Collaboration Services on i5/OS, and only if you are not using IBM Web
Administration for i5/OS to configure your environment. IBM Web Administration
for i5/OS performs these steps automatically through the Create IBM Workplace
Collaboration Services wizard.
Before following these instructions, you should have installed both Workplace
Collaboration Services and iSeries Tools for Developers PRPQ (5799PTL). You will
need to know the name of your Workplace Collaboration Services instance.
Note: The VNC server you associate with your Workplace Collaboration Services
instance should only be used for IBM Workplace. Using the VNC server
with other applications may cause problems.
To set up VNC access, follow these steps:
1. Make the directory to store the password for the VNC server by entering the
following commands on an i5/OS command line:
MKDIR DIR(’/home/QEJBSVR’)
MKDIR DIR(’/home/QEJBSVR/.vnc’)
2. Create the password file required by the VNC server by entering the following
command (note that you will be prompted for a password that will be stored
for the VNC server to use at startup):
QAPTL/VNCPASSWD USEHOME(*NO) PWDFILE(’/home/QEJBSVR/.vnc/passwd’)
3. Run the following command to assign the appropriate permissions to the
/home/QEJBSVR directory tree:
STRQSH CMD(’chown -R QEJBSVR /home/QEJBSVR’)
Selecting a display number for the VNC server:
To select a display number for the VNC server, follow these steps:
1. If the QShell Interpreter is running, stop it by doing the following:
a. On an i5/OS command line, enter QSH
b. Press F3
2. Start the PASE console by entering the following on an i5/OS command line:
132
Installation and Upgrade Guide
CALL QP2TERM
3. Enter the following to list the active VNC servers:
ps gaxuw | grep Xvnc
If other VNC servers are already active, you may see output such as this (the
numbers following the colons are the display numbers already in use):
v2kea554 40571 0.0
0.0 12484 0 - A Jul 13 4:08
/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/Xvnc :6 -desktop X -httpd
v2kea512 13027 0.0
0.0 11912 0 - A Jun 25 14:05
/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/Xvnc :1 -desktop X -httpd
qejbsvr 21707
0.0
0.0 11928 0 - A Jun 30 7:01
/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/Xvnc :33 -desktop X -httpd
v2kea554 40297
0.0
0.0 12232 0 - A Jul 12 2:31
/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/Xvnc :3 -desktop X -httpd
4. Select any number from 1 to 99 that is not in use.
5. Start the VNC Server by entering the following command on an i5/OS
command line (enter on one line):
SBMJOB CMD(CALL PGM(QP2SHELL) PARM(’/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/
vncserver_java’ ’:N’)) USER(QEJBSVR) JOBQ(QSYSNOMAX)
where N is the display number.
6. Verify that the VNC server is started by repeating steps 2-3 and confirming that
a VNC server with your display number is in the list.
Associating the VNC server with the Workplace Collaboration Services
instance:
Follow these steps to associate the VNC server with your Workplace Collaboration
Services instance:
1. Start the WebSphere Application Server administrative console by entering the
following in the location bar of a Web browser:
http://SYSTEM_NAME.COM:ADMIN_PORT/admin
where SYSTEM_NAME.COM is the name of your iSeries server, and
ADMIN_PORT is the port assigned to the administrative console of the server1
server. The port number for this port is the first internal TCP port used for the
instance, plus 24. For example, when you installed Workplace Collaboration
Services, if you entered port 39900 as the first port to be used, then you would
enter 39924 for this command.
2. Click Servers → Application Servers → WebSphere_Portal → Process Definition
→ Environment entries → New.
3. In the Name field, type DISPLAY.
4. In the Value field, type HOSTNAME:N where HOSTNAME is the TCP/IP host
name of your system and N is the display number (Example:
mysystem.rchland.ibm.com:1).
5. Click OK.
6. Save your changes to the master WAS configuration file.
Related tasks
Phase 3: Installing IBM Workplace Collaboration Services
Running the Configuration Wizard after installation
After IBM Workplace Collaboration Services is installed, run the Configuration
Wizard as many times as needed to set up a remote database server or an LDAP
Chapter 3 Installing IBM Workplace Collaboration Services
133
directory for use in a production environment. This step is not needed for a demo
server. It is also unnecessary on IBM i5/OS if you used the Create IBM Workplace
Collaboration Services wizard to configure all components.
Starting the Configuration Wizard in AIX, Linux, Solaris, and Windows:
To start the Configuration Wizard, follow these steps:
1. Log in to the Workplace server machine as a user with administrative
privileges.
2. Depending on the configuration task you are performing, servers that run
Workplace Collaboration Services may need to be stopped or started. For more
information, see instructions for each configuration task and the topic ″Starting
and stopping IBM Workplace Collaboration Services.″
3. Type the command for the mode in which you want the wizard to run.
Note: Online help is not available in console mode.
AIX, Linux, and Solaris
To run the wizard with the graphical user interface:
./configwizard.sh
To run the wizard in console mode (without the graphical user interface):
./configwizard.sh -console
Windows
To run the wizard with the graphical user interface:
configwizard.bat
To run the wizard in console mode (without the graphical user interface):
configwizard.bat -console
4. At the Welcome screen, click Next to start the wizard.
5. At the panel ″Select a language to be used,″ select the language you want to
see when running this wizard, and then click OK.
6. At the ″Ready to Start″ panel, click Next.
Tip: Each time the Configuration Wizard runs, it creates log files (configwizard.log
and configwizardlog.txt) in the <install_root>\PortalServer\log directory.
Review these logs to check for errors. To save them for later viewing, assign
them names that describe the type of configuration you chose.
Starting the Configuration Wizard on i5/OS:
To start the Configuration Wizard for an i5/OS deployment, follow these steps:
1. Start the QShell Interpreter by entering the following on an i5/OS command
line:
STRQSH
2. Change to the WebSphere Portal rootscripts directory by entering the
following:
cd <install_root>/PortalServer/rootscripts
where <install_root> is the Workplace Collaboration Services root installation
directory.
3. Stop Workplace Collaboration Services with the following case-sensitive
command.
stopWorkplaceServices.sh
134
Installation and Upgrade Guide
4. Ensure that the QEJBAS5 subsystem is running. If the subsystem is not
running, start it by entering the following on an i5/OS command line:
STRSBS QEJBAS5/QEJBAS5
5. Return to the QShell session and change to the WebSphere Portal
rootscripts/subtasks directory by entering the following:
cd <install_root>/PortalServer/rootscripts/subtasks
6. Restart the Cloudscape Network Server by entering the following:
startNetworkServer.sh
7. Change to the WebSphere Application Server bin directory by entering the
following:
cd <install_root>/AppServer/bin
8. Restart the WebSphere Application Server by entering the following:
startServer -instance instance server1
where instance is the name of your Workplace Collaboration Services instance.
9. Copy the cfgwiz.exe executable file from your server to your workstation. This
file is in the following directory:
<install_root>/PortalServer/config/wizard/cfgwiz.exe
Note: You can copy the file using IBM iSeries Navigator or FTP. Alternatively,
you can map a network drive to your server.
10. Double-click the cfgwiz.exe file on your workstation to start the Configuration
Wizard.
11. A small server signon dialog box will appear. Sign on to your server by typing
the host name, user ID and password, and clicking OK.
Note: If you do not see the server signon box right away, it may be behind
another window on your workstation.
12. At the panel ″Select a language to be used,″ select the language you want to
see when running this wizard, and then click OK.
13. Select the Workplace Collaboration Services instance you want to configure,
and click Next.
Related tasks
“Starting and stopping IBM Workplace Collaboration Services servers” on page
137
Root installation directories
Phase 4: Connecting to an LDAP directory
Phase 5: Connecting to a DBMS server
Configuring IBM Workplace Collaboration Services
Removing an IBM Workplace Collaboration Services instance
(i5/OS only)
Follow the instructions in this topic to remove an IBM Workplace Collaboration
Services instance on IBM i5/OS. You may wish to do this if the instance is no
longer used, such as when you are planning to uninstall Workplace Collaboration
Services, or if you have configured a new Workplace Collaboration Services
instance for your production environment.
Note: Removing a Workplace Collaboration Services instance does not delete any
of the database schemas associated with that instance. To delete a database
schema, enter the following command on an i5/OS command line:
Chapter 3 Installing IBM Workplace Collaboration Services
135
DLTLIB schema
where schema is the name of the Workplace Collaboration Services schema.
To remove a Workplace Collaboration Services instance on i5/OS, complete the
following steps:
1. If you installed the rich client provisioning server on the instance, uninstall it
before removing the instance. For more information, see ″Uninstalling the
provisioning server from i5/OS.″
2. If IBM Workplace Web Content Management is running on the instance,
remove it before removing the instance.
3. Start the QShell Interpreter by entering the following on an i5/OS command
line:
STRQSH
4. Change to the Workplace Collaboration Services product root directory by
entering the following:
cd /QIBM/ProdData/Workplace/WCS25
5. Enter the following for each Workplace Collaboration Services instance you
wish to remove:
rmvwcsinst.sh -instance <instance_name> -username <wasAdminUserId>
-password <wasAdminPassword>
where instance_name is the name of the Workplace Collaboration Services
instance, wasAdminUserId is the User ID for the WebSphere Application Server
instance, and wasAdminPassword is the password for the WebSphere Application
Server instance.
Related concepts
Configuring IBM Workplace Collaboration Services
Related tasks
Uninstalling the provisioning server from i5/OS
Uninstalling IBM Workplace Collaboration Services
Opening the WebSphere Administrative Console
To access the IBM WebSphere Administrative Console, you must start it and then
log in. After you finish working in the console, save your work and log out.
1. Start IBM Workplace Collaboration Services.
2. Enable cookies in the Web browser that you use to access the WebSphere
Administrative Console.
3. In the same Web browser, type http://yourWASServer:admin_port/admin where
yourWASServer is the fully qualified DNS name of the WebSphere Application
Server, and admin_port is the port assigned to the WebSphere Administrative
Console. The port varies depending on the operating system and the
environment. The port number is 9091 for a single-server deployment of IBM
AIX, Linux, Sun Solaris, or Microsoft Windows. The port number is 9090 for a
network deployment of AIX, Linux, Solaris, or Windows. For i5/OS, the port
number is the base port number for the instance, plus 10. For example, if you
specified 30000 as your base port number, the WebSphere Administrative
Console would be port 30010. For example, the URL would look like this for a
single-server deployment of Windows:
http://server1.acme.com:9091/admin
4. Wait for the console to load in the Web browser window. If you cannot start the
WebSphere Administrative Console because the console port conflicts with an
136
Installation and Upgrade Guide
application that is already running on the machine, change the port number in
the two files that follow and then restart the WebSphere Application Server.
<was_root>/config/cells/cell_name/nodes/node_name/servers/server_name/server.xml
<was_root>/config/cells/cell_name/virtualhosts.xml
5. When the login page displays, type your user ID and password to log into the
console. Changes made to server configurations are saved to the user ID. Server
configurations also are saved to the user ID if there is a session timeout. A user
ID lasts for the duration of the session for which it was used to log in. If you
enter an ID that is already in use (and in session), perform one of these actions:
v Force the existing user ID out of session. The configuration file used by the
existing user ID is saved in the temporary area.
v Wait for the existing user ID to log out or time out of the session.
v Type a different user ID and password.
6. Click OK.
Starting and stopping IBM Workplace Collaboration Services
servers
This topic describes how to start and stop the servers that run IBM Workplace
Collaboration Services. It also describes how to check the status of those servers.
Note: Commands for IBM AIX, Linux, Sun Solaris, and IBM i5/OS are case
sensitive.
Checking the status of servers
To determine which servers are running, use the serverstatus command.
1. Open a command prompt (QShell session on IBM i5/OS).
2. Navigate to the <install_root>\AppServer\bin directory, where <install_root> is
the root Workplace Collaboration Services installation directory.
3. Check the status of all servers with the following command:
serverStatus -all
These are the servers that run with Workplace Collaboration Services:
v Network Server (Cloudscape)
v Mail_Server_1
v server_1 (WebSphere Application Server)
v WebSphere_Portal
Starting and stopping all servers that run Workplace
Collaboration Services
Follow these instructions to start and stop all servers that run Workplace
Collaboration Services. If you are using a remote DBMS server, start the DBMS
server before starting Workplace Collaboration Services. Stop the DBMS server
after stopping Workplace Collaboration Services.
1. Log in to the server machine as a user with administrative privileges.
2. Open a command prompt (QShell session on IBM i5/OS).
3. Navigate to the <install_root>\PortalServer\rootscripts directory, where
<install_root> is the root Workplace Collaboration Services installation directory.
Chapter 3 Installing IBM Workplace Collaboration Services
137
4. Start Workplace Collaboration Services with the following command. This
command starts WebSphere_Portal, server_1, Mail_Server_1, and Cloudscape
Network Server.
IBM AIX, Linux, and Sun Solaris
./startWorkplaceServices.sh
Microsoft Windows
startWorkplaceServices.bat
i5/OS
startWorkplaceServices.sh
5. To see the Workplace Collaboration Services user interface, type the following
URL from a browser window:
http://servername.yourcompany.com:9081/lwp/workplace
6. Stop Workplace Collaboration Services with the following command.
AIX, Linux, and Solaris
./stopWorkplaceServices.sh
Windows
stopWorkplaceServices.bat
i5/OS
stopWorkplaceServices.sh
Starting and stopping individual servers
Follow these instructions to start and stop individual servers. The batch files are
located in the the <install_root>\PortalServer\rootscripts\tasks directory.
Server Name
AIX, Linux, and
Solaris
Windows
i5/OS
Cloudscape Network
Server
./startNetworkServer.shstartNetworkServer.bat startNetworkServer.sh
Mail_Server_1
./startMailServer.sh
startMailServer.bat
startMailServer.sh
./stopMailServer.sh
stopMailServer.bat
stopMailServer.sh
./startPortalServer.sh
startPortalServer.bat
startPortalServer.sh
./stopPortalServer.sh
stopPortalServer.bat
stopPortalServer.sh
WebSphere_Portal
and server_1
./stopNetworkServer.shstopNetworkServer.bat startNetworkServer.sh
Related tasks
Opening the WebSphere Administrative Console
Phase 3: Installing IBM Workplace Collaboration Services
Uninstalling IBM Workplace Collaboration Services
To uninstall IBM Workplace Collaboration Services, complete the following steps
for your operating system.
Uninstalling on AIX, Linux, Solaris, and Windows
To uninstall Workplace Collaboration Services on IBM AIX, Linux, Sun Solaris or
Microsoft Windows, complete the following steps:
1. Log in to the server as a user with administrative privileges.
2. Stop Workplace Collaboration Services.
138
Installation and Upgrade Guide
3. Open a command prompt and enter the appropriate command to start the
Uninstall Wizard.
All commands accept the -console argument to run the uninstallation program
from a command prompt. The console interface presents the same content as
the graphical interface, but in a textual form. Prompts at the bottom of each
screen tell you how to enter numbers to make your selections and proceed to
the next screen.
AIX
<install_root>/WorkplaceServer/uninstall/aixwpuninstall
Linux
<install_root>/WorkplaceServer/uninstall/linwpuninstall
Solaris
<install_root>/WorkplaceServer/uninstall/sunwpuninstall
Windows
<install_root>\WorkplaceServer\uninstall\winwpuninstall.exe
4.
5.
6.
7.
You can also invoke the uninstallation from Add / Remove Programs in the
Control Panel.
At the panel ″Select a language to be used,″ select the language for the wizard,
and then click Next.
Optional: At the panel ″Welcome to the Uninstall Wizard,″ click Next.
At the panel ″Ready to Uninstall,″ click Next .
At the panel ″Uninstallation is successful,″ click Finish.
Uninstalling on i5/OS
To uninstall Workplace Collaboration Services on IBM i5/OS, complete the
following steps:
1. Remove each Workplace Collaboration Services instance you have configured.
For more information, see ″Removing an IBM Workplace Collaboration Services
instance (i5/OS).″
2. Start the QShell Interpreter by entering the following on an i5/OS command
line:
STRQSH
3. Change to the system root directory by entering the following:
cd /
4. Begin uninstalling Workplace Collaboration Services by entering the following
command:
/QIBM/ProdData/Workplace/WCS25/WorkplaceServer/uninstall/uninstall.sh -silent
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Removing an IBM Workplace Collaboration Services instance (i5/OS)
Phase 3: Installing IBM Workplace Collaboration Services
Chapter 3 Installing IBM Workplace Collaboration Services
139
140
Installation and Upgrade Guide
Chapter 4 Connecting to an LDAP Directory Server
This chapter provides information on connecting IBM Workplace Collaboration
Services to an LDAP directory server.
Phase 4: Connecting to an LDAP directory server
Skip this phase if you are deploying on i5/OS and used the i5/OS Create IBM
Workplace Collaboration Services wizard after installation to enable LDAP security.
These steps were done for you automatically.
By default IBM Workplace Collaboration Services stores user account information
in a custom user registry database. You can configure Workplace Collaboration
Services to use a directory on a Lightweight Directory Access Protocol (LDAP)
server instead. Using this configuration, common attributes such as names, e-mail
addresses, telephone numbers, and authentication credentials are stored in the
LDAP directory, while other attributes that are particular to Workplace
Collaboration Services are stored in a lookaside database. WebSphere Member
Manager manages the user and group lookups to the LDAP directory and
lookaside database.
Configuring Workplace Collaboration Services to use an LDAP directory is referred
to as enabling LDAP security, and you use the ″Enable LDAP Security″ option
provided with the Configuration Wizard to complete this task. The wizard requires
a supported and functioning LDAP directory server. Only someone with advanced
knowledge of LDAP concepts and administration who is familiar with your
directory environment should enable LDAP security.
An LDAP directory can work with any supported database management server. If
you plan to transfer from IBM Cloudscape to another database management server
(required for IBM i5/OS), and to enable LDAP security, enable LDAP security first.
When you switch from a custom user registry configuration to an LDAP directory
configuration, the external IDs that uniquely identify users change, so that any
data users create while a custom user registry is in place is no longer available. For
this reason, if you want to enable LDAP security, it is important to do so before
users begin using Workplace Collaboration Services products.
Note: The ″Enable LDAP Security″ option in the Configuration Wizard automates
the mapping of the WebSphere Member Manager extID attribute to an
attribute in the LDAP directory. This mapping is required to uniquely
identify users. If you use the IBM Lotus Domino Directory, you must add
the dominoUNID attribute, used for the mapping, to the schema before
enabling LDAP security.
Related concepts
Requirements for AIX, Linux, Solaris, and Windows
Requirements for i5/OS
“Optional post-installation tasks” on page 399
Related tasks
Connecting to an LDAP directory in a Network Deployment
Connecting to IBM Tivoli Directory Server
© Copyright IBM Corp. 2002, 2005
141
Connecting
Connecting
Connecting
Connecting
to
to
to
to
Domino Directory
Microsoft Active Directory
Sun Java System Directory Server
Novell eDirectory
Connecting to an LDAP directory in a Network Deployment
If you use a Network Deployment, follow these steps to connect to an LDAP
directory:
1. Connect Node 1 to an LDAP directory, using one of these procedures:
v Connect to IBM Tivoli Directory Server.
v Connect to Domino Directory.
v Connect to Microsoft Active Directory.
v Connect to Sun Java System Directory Server.
v Connect to Novell eDirectory.
2. Enable LDAP security on the Deployment Manager.
For more information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
3. Connect Node 2 and additional nodes to the LDAP directory, as described in
Step 1.
Related concepts
Phase 4: Connecting to an LDAP directory server
Connecting to IBM Tivoli Directory Server
Perform the following steps to configure IBM Workplace Collaboration Services to
use IBM Tivoli Directory Server:
1. Create required administrative accounts.
2. Index the IBM Tivoli Directory Server LDAP database.
3. Edit the helper file.
4. Use the Configuration Wizard to enable LDAP security.
5. Optional: Configure read-only directory access.
6. Verify the LDAP configuration.
Related concepts
Phase 4: Connecting to an LDAP directory server
Related tasks
Connecting to an LDAP directory in a Network Deployment environment
Creating administrative accounts for IBM Tivoli Directory Server
Create the following required administrative accounts in the LDAP directory before
you enable LDAP security. For instructions, see the IBM Tivoli Directory Server
documentation. Each account corresponds to properties that you specify in the
helper file and in the wizard.
LDAP account
IBM WebSphere Application Server
administrator. This can be the same as the
IBM WebSphere Portal Server administrator.
142
Installation and Upgrade Guide
Related properties in helper file and
wizard
WasUserid
WasPassword
LDAP account
Related properties in helper file and
wizard
WebSphere Portal Server administrator.
PortalAdminId
Note: This account must include a value for PortalAdminIdShort
the mail attribute. If the account does not
have a value for the mail attribute, enabling PortalAdminPwd
LDAP security will fail.
Do not use the following characters in the
password (PortalAdminPwd) because they
can cause authentication failures:
!()@#$%
WebSphere Portal Server administrator
PortalAdminGroupId
group. This group must include the name of
PortalAdminGroupIdShort
the WebSphere Portal Server administrator.
The group must define its user and group
members using the members’ distinguished
names.
Name that WebSphere Portal Server and
LDAPAdminUId
IBM WebSphere Member Manager use to
bind to the LDAP directory. The access level LDAPAdminPwd
given this name controls the access that IBM
Workplace Collaboration Services has to the
directory.
Note: Give this account read-only access if
you want to prevent users from using the
Sign-up link to register accounts in the
directory, and from using the Edit My
Profile link to change attributes in the
directory, such as their e-mail addresses.
Name that WebSphere Application Server
uses to bind to the LDAP directory.
LDAPBindID
LDAPBindPassword
Related tasks
Editing the helper file for IBM Tivoli Directory Server
Connecting to IBM Tivoli Directory Server
Indexing the IBM Tivoli Directory Server LDAP database
Perform the following required steps to index the mail table in the IBM DB2
database used by IBM Tivoli Directory Server. Adding this index to the mail table
improves Address Book look up features in IBM Workplace Collaboration Services
products.
1. Log in as the LDAP database owner:
a. Make sure that the $DB2INSTANCE variable (IBM AIX, Linux, Solaris) or
the %DB2INSTANCE% variable (Windows) is set to your LDAP database
instance.
Tip: If you are not sure which DB2 instance is set to your LDAP database
instance, use the db2 db2ilist command to list the instances.
b. Use the LDAP database owner login account to log in as the LDAP
database owner. Alternatively, on AIX, Solaris, or Linux, type the following
command:
su - <dbowner>
Chapter 4 Connecting to an LDAP Directory Server
143
where <dbowner> is the database owner, for example, ldapdb2.
2. Type the following command to connect to the LDAP database:
db2 "connect to <ldapdatabase>"
where <ldapdatabase> is the name of the database, for example ldapdb2.
3. Type the following command to index the mail table:
db2 "create index maili2 on mail(mail_t,eid)"
Related tasks
“Editing the helper file for IBM Tivoli Directory Server”
Connecting to IBM Tivoli Directory Server
Editing the helper file for IBM Tivoli Directory Server
You use a helper file to aid in enabling LDAP security. You make a copy of the
helper file, then edit the copy, providing values for directory properties that are
appropriate for your LDAP directory environment. When you run the
Configuration Wizard to enable LDAP security, the wizard displays the values you
specified in the helper file, which you can then verify.
Note: Only someone with advanced knowledge of LDAP concepts and
administration who is familiar with your directory environment should edit
the helper file.
1. Make a backup copy of the IBM Tivoli Directory Server helper file,
<wp_root>\config\helpers\security_ibm_dir_server.properties.
2. With a text editor, open the security_ibm_dir_server.properties file, specify
values for properties, and then save and close the file.
v The helper file and the following table provide example values for some
directory properties. Do not assume the example values are correct for your
environment; you must evaluate each property to determine the appropriate
value for your environment.
v Type distinguished names in lowercase characters.
v Ignore any properties in the helper file that are not described in the
following table.
Property
Description
IBM WebSphere Application
Server properties
WasUserid
The distinguished name in the LDAP directory for the
WebSphere Application Server administrator. This can
be the same name as the IBM WebSphere Portal Server
administrator (PortalAdminId).
Example: uid=wasadmin,cn=users,dc=acme,dc=com
WasPassword
The password for the WasUserid name. As a security
measure, do not type the password in the helper file.
Type the password when you run the wizard.
WpsHostName
The host name for the WebSphere Portal Server.
Type localhost.
WebSphere Portal Server
configuration properties
144
Installation and Upgrade Guide
Property
Description
PortalAdminId
The distinguished name of the WebSphere Portal
Server administrator in the LDAP directory. This name
must be a member of the WebSphere Portal Server
administrators group defined by the
PortalAdminGroupId property.
Note: This account must include a value for the mail
attribute. If the account does not have a value for the
mail attribute, enabling LDAP security will fail.
Example: uid=portaladmin,cn=users,dc=acme,dc=com
PortalAdminIdShort
The short form of the WebSphere Portal Server
administrator name.
Example: portaladmin
PortalAdminPwd
Password for the WebSphere Portal Server
administrator. As a security measure, do not type the
password in the helper file. Type the password when
you run the wizard.
Note: Do not include the following characters in the
password because they can cause authentication
failures:
[email protected]()#$%
PortalAdminGroupId
The distinguished name of the WebSphere Portal
Server administrators group in the LDAP directory to
which the WebSphere Portal Server administrator
belongs. This group must define its user and group
members using the members’ distinguished names.
Example:
cn=portaladmins,cn=groups,dc=acme,dc=com
PortalAdminGroupIdShort
The short form of the WebSphere Portal Server
administrators group name.
Example: portaladmins
WebSphere Portal Server security
properties
LTPAPassword
The password used to encrypt and decrypt the LTPA
keys. As a security measure, do not type the password
in the helper file. Type the password when you run
the wizard.
LTPATimeout
Time period in minutes at which an LTPA token
expires.
Example: 120
SSOEnabled
Indicates whether single sign-on is enabled (true or
false).
SSORequiresSSL
Indicates whether single sign-on is enabled only for
HTTPS Secure Socket Layer (SSL) connections.
Type false. If you want to configure SSL, do so only
after you have enabled LDAP security and verified the
LDAP directory configuration.
Chapter 4 Connecting to an LDAP Directory Server
145
Property
Description
SSODomainName
The domain name for all single sign-on hosts.
Example: acme.com
Do not type a leading ″.″ For example, type acme.com,
and not .acme.com.
General global security properties
useDomainQualifiedUserNames
Indicates whether to qualify user names with the
security domain within which they reside (true or
false).
The default value (false) is recommended for most
environments.
cacheTimeout
Timeout for the security cache.
The default value (600) is recommended for most
environments.
issuePermissionWarnings
Indicates whether during application deployment and
application start, the security run time emits a
warning if applications are granted any custom
permissions (true or false).
The default value (true) is recommended for most
environments.
activeProtocol
The authentication protocol for RMI/IIOP requests
when security is enabled.
The default value (BOTH) is recommended for most
environments.
activeAuthmechanism
The authentication mechanism when security is
enabled.
The default value (LTPA) is recommended for most
environments.
LDAP properties
LDAPHostName
The host name for your LDAP server.
Example: idsldap.acme.com
LDAPPort
The LDAP server port number. Typically you type 389.
Do not type 636, the port typically used for SSL
connections. If you want to configure an SSL port for
LDAP, do so after you have enabled LDAP security
and verified the LDAP directory configuration.
146
Installation and Upgrade Guide
Property
Description
LDAPAdminUId
The distinguished name in the LDAP directory that
IBM WebSphere Portal Server and IBM WebSphere
Member Manager use to bind to the directory. The
level of access given this name determines the level of
access that IBM Workplace Collaboration Services has
to the directory. This name does not have to contain a
uid attribute.
Note: Give this account read-only access to prevent
users from using the Sign-up link to register accounts
in the directory, and from using the Edit My Profile
link to change attributes in the directory, such as their
e-mail addresses.
Example: uid=ldapadmin,cn=users,dc=acme,dc=com
LDAPAdminPwd
The password for the name assigned to the
LDAPAdminUId property. As a security measure, do
not type the password in the helper file. Type the
password when you run the wizard.
LDAPServerType
Do not change, leave as IBM_DIRECTORY_SERVER.
LDAPBindID
Distinguished name that WebSphere Application
Server uses to bind to the directory.
Example: uid=wpsbind,cn=users,dc=acme,dc=com
LDAPBindPassword
The password for the LDAPBindID name. As a
security measure, do not type the password in the
helper file. Type the password when you run the
wizard.
Advanced LDAP properties
LDAPSuffix
The LDAP suffix for your directory server. This
property determines the naming context at which to
begin directory searches for users and groups.
Example: dc=acme,dc=com
LDAPUserPrefix
The leftmost attribute of user names in the directory.
Type the value in lowercase characters.
Example: uid
LDAPUserSuffix
The naming context at which to begin searches for
user names in the directory.
Example: cn=users
Do not include the LDAPSuffix value as part of this
value. For example, do not type
cn=users,dc=acme,dc=com.
LDAPGroupPrefix
The leftmost attribute of group names in the directory.
Type the value in lowercase characters.
Example: cn
Chapter 4 Connecting to an LDAP Directory Server
147
Property
Description
LDAPGroupSuffix
The naming context at which to begin searches for
group names in the directory.
Example: cn=groups
Do not include the LDAPSuffix value as part of this
value. For example, do not type
cn=groups,dc=acme,dc=com.
LDAPUserObjectClass
The object class used for users.
Example: inetOrgPerson
LDAPGroupObjectClass
The object class used for groups.
Example: groupOfUniqueNames
LDAPGroupMember
The attribute used for the members of groups.
Example: uniqueMember
LDAPUserFilter
The filter used to search for user accounts. The filter
must include the following text:
(&(|(<userprefix>=%v)(mail=%v))(objectclass=
<userobjectclass>))
where <userprefix> is the value specified for the
LDAPUserPrefix property and <userobjectclass> is the
value specified for the LDAPUserObjectClass property.
Example:
(&(|(uid=%v)(mail=%v))(objectclass=inetOrgPerson))
LDAPGroupFilter
The filter used to search for groups accounts. The filter
must include the following text:
(&(<groupprefix>=%v)(objectclass=<groupobjectclass>))
where <groupprefix> is the value specified for the
LDAPGroupPrefix property and <groupobjectclass> is
the value specified for the LDAPGroupObjectClass
property.
Example:
(&(cn=%v)(objectclass=groupOfUniqueNames))
LDAPGroupMinimumAttributes
Attributes loaded for group searches and related to
performance. Leave this property blank.
LDAPUserBaseAttributes
Attributes loaded for user login related to
performance. Type givenName,sn,preferredLanguage.
Also type the following values to allow users, for
example calendar users, to set international time and
date preferences in the Edit My Profile page:
,ibm-regionalLocale,ibm-timeZone,
ibm-preferredCalendar,ibm-firstDayOfWeek,
ibm-firstWorkDayOfWeek
LDAPUserMinimumAttributes
148
Installation and Upgrade Guide
Attributes loaded for user searches and related to
performance. Leave this property blank.
Property
Description
LDAPsearchTimeout
Value in seconds for the amount of time the LDAP
server has to respond before canceling a request.
Example: 120
LDAPreuseConnection
Indicates whether LDAP connections are reused (true
or false). If your environment uses a frontend server to
spray requests to multiple backend LDAP directory
servers, type false. If your environment does not use
an intermediate server but instead authenticates
directly with the LDAP directory server, type true.
LDAPIgnoreCase
Indicates whether LDAP searches are case-sensitive
(true or false).
Related tasks
Enabling LDAP security for IBM Tivoli Directory Server
Connecting to IBM Tivoli Directory Server
Related reference
Root installation directories
Enabling LDAP security for IBM Tivoli Directory Server
Perform the following steps to disable security, and then to enable LDAP security
for IBM Tivoli Directory Server. These steps assume you are running the
Configuration Wizard using the graphical user interface. If you are using the
console interface, to advance in the wizard, type the number the wizard indicates
rather than click Next. Online help is not available in console mode.
If you have already enabled LDAP security, you can follow these steps to change
LDAP configuration properties. However, you should not change to a different
LDAP directory that is not a replica of the directory currently configured. If you do
so, users’ unique identifiers are lost and users will be unable to authenticate or
access data created previously.
1. Make sure you have made a backup copy of the
security_ibm_dir_server.properties helper file, and have edited the helper file
to accommodate your directory environment.
Note: Make sure the account specified for the PortalAdminId property
includes a value for the mail attribute. If the account does not have a
value for the mail attribute, enabling LDAP security will fail.
2. Start your LDAP directory server.
3. Start the Configuration Wizard. Make sure that Cloudscape and server1 are
running, and that WebSphere_Portal and Mail_Server_1 are stopped before
doing so.
For more information, see the chapter ″Installing IBM Workplace
Collaboration Services.″
4. Disable WebSphere Application Server global security:
a. At the Select the configuration task that you want to perform dialog box
in the Configuration Wizard, click Disable security, and then click Next.
b. At the WebSphere Application Server global security is enabled. Enter
the user ID and password to be used for Websphere Application Server
Chapter 4 Connecting to an LDAP Directory Server
149
administration dialog box, type the administrator name and password
specified during IBM Workplace Collaboration Services installation, and
then click Next.
Note: If LDAP security is already enabled, and you are preparing to
re-enable LDAP security in order to change the LDAP directory
configuration, type the name of the current WebSphere Application
Server administrator name and password in the LDAP directory
instead.
c. At the Please enter an appropriate properties file location dialog box,
type the path and filename for the wpconfig.properties file, located in the
<wp_root>/config directory, where <wp_root> is the root WebSphere Portal
Server installation directory. For example, type
/opt/IBM/Workplace/PortalServer/config/wpconfig.properties.
d. Verify that the next dialog box contains the required values indicated in
the following table, then click Next. Do not leave any of the properties
blank.
Property
Action
PortalAdminID
Verify that the value is uid=wpsadmin,o=default organization. Or
if LDAP security is enabled, verify that the value is the
distinguished name of the current WebSphere Portal Server
administrator in the LDAP directory.
PortalAdminIdShort
Verify that the value is wpsadmin. Or if LDAP security is
enabled, verify that the value is the short form of the current
WebSphere Portal Server administrator in the LDAP directory.
PortalAdminPwd
Type the administrator password that you specified during IBM
Workplace Collaboration Services installation. Or if LDAP security
is enabled, type the password for the current Websphere Portal
Server administrator in the LDAP directory.
PortalAdminGroupId
Verify that the value is cn=wpsadmins,o=default organization. Or
if LDAP security is enabled, type the distinguished name of the
current WebSphere Portal Server administrators group.
DbPassword
Accept the default hidden password value.
WmmDbPassword
Accept the default hidden password value.
5.
6.
7.
8.
9.
150
e. At the The Configuration Wizard is ready to run the following
configuration: Disable security dialog box, click Next to disable security.
See the progress bar and wait for the wizard to finish.
f. At the The following configuration has completed successfully: Disable
security dialog box, click Finish.
Click Run Wizard Again.
At the Select the configuration task that you want to perform dialog box,
click Enable LDAP security, and then click Next.
At the Select the LDAP type to use for authentication dialog box, click IBM
Directory Server, and then click Next.
At the Please enter an appropriate properties file location dialog box, type
<wp_root>/config/helpers/security_ibm_dir_server.properties, and then click
Next.
Advance through the wizard.
v Verify at each stage that the values the wizard reads from the helper file are
correct. Accurate values are essential for proper LDAP directory
configuration.
Installation and Upgrade Guide
v Remember to type the required passwords, because you did not type them
in the helper file.
v The wizard may not read the domain name specified for the
SSODomainName property from the helper file. In this case, be sure to type
the SSO domain name again in the wizard.
v If you change a distinguished name, the LdapUserPrefix, or the
LdapGroupPrefix, remember to use lowercase characters.
10. Near the end of the wizard, type values for the following properties, and then
click Next. These properties are not included in the helper file.
Property
Action
WmmDbPassword
Type any text but do not leave the property blank.
DbPassword
Type any text but do not leave the property blank.
LWPDBAdminPassword
Type any text but do not leave the property blank.
11. At the The Configuration Wizard is ready to run the following
configuration: Enable LDAP security dialog box, click Next to run the
wizard. See the progress bar and wait for the wizard to finish.
12. If you see the dialog box that says The following configuration has
completed successfully: Enable LDAP security, click Finish to exit the
wizard, then continue to Step 13. If the wizard finishes with errors, perform
the following steps:
a. Click Finish.
b. Open the configwizard.log and configwizardlog.txt files to help you
troubleshoot errors and determine the correct values:
v <wp_root>/log/configwizard.log
v <wp_root>/log/configwizardlog.txt
Tip: Rename the two log files to reflect the configuration task chosen, so
you can find them easily if you need them in the future.
c. Correct any incorrect values in your helper file.
d. Repeat Step 1 through Step 12.
13. To allow IBM WebSphere Portal Server to follow LDAP referrals when
communicating with a server in front of multiple LDAP directory servers,
complete the following manual steps:
a. With a text editor, open the <wp_root>\shared\app\wmm\wmm.xml file.
b. Add the following line to the <ldapRepository name=″wmmLDAP″> tag,
directly after the ldapPort= line:
java.naming.referral="follow"
c. Save the file.
Related tasks
Configuring read-only access to IBM Tivoli Directory Server
Editing the helper file for IBM Tivoli Directory Server
Connecting to IBM Tivoli Directory Server
Related reference
Root installation directories
Chapter 4 Connecting to an LDAP Directory Server
151
Configuring read-only access to IBM Tivoli Directory Server
Perform the following optional steps to configure read-only access to IBM Tivoli
Directory Server. Read-only access prevents users from using the Sign-up and Edit
My Profile links in the IBM WebSphere Portal Server page to register themselves in
the directory and to change personal attributes in the directory, such as e-mail
addresses.
If you use IBM Tivoli Directory Server with IBM WebSphere Edge Server, use of
the Sign-up link can cause authentication problems. For this environment,
configure read-only directory access.
1. Make sure that the account name you specified for the LDAPAdminUId
property when you enabled LDAP security has read-only access to the
directory.
2. Stop the WebSphere Portal Server.
3. Remove the Sign-up and Edit My Profile links from the WebSphere Portal
Server page:
a. Change to the <wp_root>\config directory.
b. Type the following command:
Microsoft Windows
WPSconfig action-fixup-signup-link
IBM AIX, Linux, Solaris, IBM i5/OS
./WPSconfig.sh action-fixup-signup-link
Related tasks
“Verifying the IBM Tivoli Directory Server configuration”
Connecting to IBM Tivoli Directory Server
Related reference
Root installation directories
Verifying the IBM Tivoli Directory Server configuration
Perform the following steps to verify the IBM Tivoli Directory Server configuration.
1. Stop and restart the database server.
2. Start IBM WebSphere Portal Server and IBM Workplace Collaboration Services
servers:
Microsoft Windows
Navigate to the <was_root>\bin directory and type the following commands:
startServer.bat WebSphere_Portal
startServer.bat Mail_Server_1
IBM AIX, Linux, Solaris
Navigate to the <was_root>/bin directory and type the following commands:
./startServer.sh WebSphere_Portal
./startServer.sh Mail_Server_1
IBM i5/OS
Start the QShell Interpreter by entering STRQSH on an i5/OS command line,
and type the following command: :
/qibm/proddata/webas5/pme/bin/startServer WebSphere_Portal -instance <instance>
where <instance> is the name of the Workplace Collaboration Services instance.
152
Installation and Upgrade Guide
3. Type the following URL in a Web browser to start the IBM WebSphere
Administrative Console:
AIX, Linux, Solaris, Windows
http://<hostname>:9091/admin
where <hostname> is the fully qualified name of the server.
IBM i5/OS
http://<hostname>:<admin_port>/admin
where <hostname> is the fully qualified name of the server and <admin_port> is
the base port number for the instance plus10.
4. Test that you can log in as the IBM WebSphere Application Server
administrator.
5. If you have just enabled security on Node 1 of a Network Deployment, you
should now enable security on the Deployment Manager.
For information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
For information on configuring Secure Sockets Layer (SSL) over LDAP, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related concepts
“Optional post-installation tasks” on page 399
Related tasks
“Enabling LDAP security on the Deployment Manager” on page 101
Connecting to IBM Tivoli Directory Server
Related reference
Root installation directories
Connecting to Domino Directory
Perform the following steps to configure IBM Workplace Collaboration Services to
use Domino Directory:
1. Add dominoUNID to the Domino Directory schema.
2. Create required administrative accounts.
3. Configure e-mail addresses for groups.
4. Optional: Configure write access to the Domino Directory.
5. Optional: Configure directory assistance.
6. Create a full-text index for the Domino Directory.
7. Edit the helper file.
8. Use the Configuration Wizard to enable LDAP security.
9. Optional: Configure read-only access to the directory.
10. Verify the LDAP directory configuration.
Related concepts
Phase 4: Connecting to an LDAP directory server
Related tasks
Connecting to an LDAP directory in a Network Deployment environment
Chapter 4 Connecting to an LDAP Directory Server
153
Adding dominoUNID to the Domino Directory schema
IBM WebSphere Member Manager requires unique IDs in the LDAP directory to
identify users and groups. Unlike the schemas of the other supported LDAP
directories, the default schema for the Domino Directory does not provide a
suitable attribute for the unique IDs. Perform the following steps to add the
hidden field dominoUNID to the directory schema. Then, after you use the
Configuration Wizard to enable security for Domino Directory, WebSphere Member
Manager uses dominoUNID as the unique ID attribute.
This procedure assumes you have an understanding of customizing the Domino
Directory and of extending the LDAP schema. See Domino Administrator Help for
more information on these tasks. The recommended method for customizing the
Domino Directory is making changes in a copy of the Domino Directory template
and then applying the changes to the Domino Directory database.
1. Log in to Domino Designer® using the name and password of a server
administrator.
2. Add a field named dominoUNID to the Person, Group, and Server\Certifier
forms in the Domino Directory. Specify the Type as Text and Computed when
Composed. Do not select the Allow multiple values property. Specify the
following formula for the field:
@If(dominoUNID != ""; dominoUNID; @Text(@DocumentUniqueID))
3. To add the dominoUNID field to the schema, type the following command
from the IBM Lotus Domino server console:
tell ldap reloadschema
4. Domino automatically populates the dominoUNID attribute in new Person,
Group, and Server\Certifier documents. To create a Domino agent that
populates the attribute in existing Person, Group, and Server\Certifier
documents, follow these steps:
a. Open the Domino Directory database (NAMES.NSF).
b. Click Create → Design → Agent.
c. Type a name for the agent.
d. In the Runtime box, select the following options: On event, Action menu
selection, and Target All selected documents.
e. Close the properties box.
f. In the Objects pane, click Action.
g. From the list, select Formula and type the following formula:
FIELD dominoUNID := @If(dominoUNID != ""; dominoUNID;
@Text(@DocumentUniqueID));
h. In the Objects pane, click Document Selection.
i. Click Add Condition, select By Form as the condition, select the Group,
Person, and Server\Certifiers forms, and then click Add.
j. Save the agent.
k. Right-click the agent in the agent view, click Design Properties, click the
third tab, and click Prohibit design refresh or replace to modify.
l. To run the agent, select Actions from the IBM Lotus Notes menu.
5. Repeat Step 1 through Step 4 for any additional Domino Directories configured
through directory assistance.
Related tasks
Creating administrative accounts for Domino Directory
Connecting to Domino Directory
154
Installation and Upgrade Guide
Creating administrative accounts for Domino Directory
Create the following required administrative accounts in the IBM Lotus Domino
Directory before you enable LDAP security. For instructions, see Domino
Administrator Help. Each account corresponds to properties that you specify in the
helper file and in the wizard.
Related properties in helper file and
wizard
LDAP account
IBM WebSphere Application Server
administrator. This can be the same as the
IBM WebSphere Portal Server administrator.
WasUserid
WebSphere Portal Server administrator.
PortalAdminId
WasPassword
Note: This account must include a value for PortalAdminIdShort
the mail attribute. If the account does not
have a value for the mail attribute, enabling PortalAdminPwd
LDAP security will fail.
Do not use the following characters in the
password (PortalAdminPwd) because they
can cause authentication failures:
!()@#$%
WebSphere Portal Server administrator
PortalAdminGroupId
group. This group must include the name of
PortalAdminGroupIdShort
the WebSphere Portal Server administrator.
The group must define its user and group
members using the members’ distinguished
names.
Name that WebSphere Portal Server and
LDAPAdminUId
IBM WebSphere Member Manager use to
bind to the LDAP directory. The access level LDAPAdminPwd
given this name controls the access that IBM
Workplace Collaboration Services has to the
directory.
Note: Give this account read-only access if
you want to prevent users from using the
Sign-up link to register accounts in the
directory, and from using the Edit My
Profile link to change attributes in the
directory, such as their e-mail addresses.
Name that WebSphere Application Server
uses to bind to the LDAP directory.
LDAPBindID
LDAPBindPassword
Related tasks
“Configuring e-mail addresses for Domino Directory groups”
Connecting to Domino Directory
Configuring e-mail addresses for Domino Directory groups
If Group documents in the Domino Directory do not contain Internet addresses,
create a Global Domain Document in the Domino Directory to ensure that the
messaging server can send mail to groups:
1. From the Domino Administrator, click Configuration, and then click
Messaging.
2. Click Domains, and then click Add Domain.
Chapter 4 Connecting to an LDAP Directory Server
155
3. Click Basics, and then complete the following fields:
Field
Action
Domain type
Click Global Domain.
Global domain name (Optional)
Type a word or phrase that describes the
domain.
Global domain role
Click R5 Internet Domain or R4.x SMTP
MTA.
4. Click Conversions and complete the following fields:
Field
Action
Local primary Internet domain
Type the name of the primary Internet
domain your organization uses for external
communication.
Alternate Internet domain aliases
Type the names of any additional domains
your organization uses. Separate names with
commas.
Local part formed from
Click Common name
5. At the server console, type restart server to put the changes into effect.
For additional information on Global Domain documents, see Domino
Administrator Help.
Related tasks
Configuring write access to the Domino Directory
Connecting to Domino Directory
Configuring write access to the Domino Directory
Consider carefully whether to allow write access to the Domino Directory. Write
access allows users to use the IBM WebSphere Portal Server page Sign-up and Edit
My Profile links to register accounts for themselves in the LDAP directory and to
change personal attributes in the directory, such as e-mail addresses. Perform the
following steps to allow write access to the Domino Directory.
1. Configure Domino Directory access control:
a. Open the Domino Directory from the IBM Lotus Notes client.
b. Click File → Database → Access Control to open the access control list
(ACL).
c. Add an entry in the ACL for the LDAP administrator. This is the
distinguished name in the LDAP directory that IBM WebSphere Member
Manager uses to access the directory, for example, ldapadmin/acme. This
entry corresponds to the name you specify for the LDAPAdminUId
property when you enable LDAP security.
d. Assign access and roles to the LDAP administrator as follows:
v Assign the entry Editor access.
v Add the administrator to the following roles: GroupCreator,
GroupModifier, UserCreator, and UserModifier.
e. Open the Domino Directory and switch to the Server → Configurations
view.
f. Click Add Configuration.
156
Installation and Upgrade Guide
g. In the new document, click Yes for Use these settings as the default
settings for all servers. Click the LDAP tab. Scroll down and change Allow
LDAP users write access to Yes.
h. Save and close the document.
2. Edit a WebSphere Portal file:
a. With a text editor, open the
<wp_root>\shared\app\config\services\PumaService.Properties file.
b. Remove the number sign (#) from the user.sync.remove.attributes property,
and type the following values for it:
user.sync.remove.attributes=cn,CN,cN,Cn
Note: This step assumes that cn is the attribute used for the leftmost part of
users’ distinguished names. This attribute is configured through the
LdapUserPrefix property when you enable LDAP security.
c. Save the file.
Related tasks
Creating a full-text index on the Domino Directory
Connecting to Domino Directory
Creating a full-text index on the Domino Directory
Create a full-text index on the Domino Directory to reduce the time required for
login and authentication:
1. From the Domino Administrator client, open the Server document of a server
that runs the LDAP service, or of a server in the same domain as one that runs
the LDAP service.
2. In the left pane, click Directory → LDAP → Settings.
3. Perform one of these steps:
v If you see the prompt Unable to locate a Server Configuration document
for this domain. Would you like to create one now? click Yes, and then
click the LDAP tab on the document.
v If you do not see the prompt, click Edit LDAP Settings.
4. Next to Automatically Full Text Index Domino Directory? click Yes to enable
the LDAP service to create and update full-text indexes automatically.
5. Click Save & Close.
Related tasks
Configuring directory assistance
Connecting to Domino Directory
Configuring directory assistance
Use the following guidelines when configuring the IBM Lotus Domino server to
use directory assistance to search a secondary Domino Directory. For detailed
instructions on configuring directory assistance, see Domino Administrator Help.
1. Add the IBM WebSphere Portal Server administrator account name to the ACL
of the primary Domino Directory and give the name Manager access. The
primary Domino Directory is the NAMES.NSF database on the Domino server
to which IBM Workplace Collaboration Services will connect.
2. Add the name of the Domino server to which Workplace Collaboration Services
will connect to the ACL of each secondary Domino Directory and give the
Chapter 4 Connecting to an LDAP Directory Server
157
server name Manager access. A secondary Domino Directory is a Domino
Directory that has a document in the directory assistance database.
3. To search a secondary Domino Directory, enable one or more naming contexts
(rules) in the Directory Assistance document for the directory that match the
naming context for searches. Set Trusted for Credentials to True in each
naming context. Usually one, all-asterisk naming context is used:
*/*/*/*/*/*
Related tasks
Editing the helper file for Domino Directory
Connecting to Domino Directory
Editing the helper file for Domino Directory
You use a helper file to aid in enabling LDAP security. You make a copy of the
helper file, then edit the copy, providing values for directory properties that are
appropriate for your LDAP directory environment. When you run the
Configuration Wizard to enable LDAP security, the wizard displays the values you
specified in the helper file, which you can then verify.
Note: Only someone with advanced knowledge of LDAP concepts and
administration who is familiar with your directory environment should edit
the helper file.
1. Make a backup copy of the Domino Directory helper file,
<wp_root>\config\helpers\security_domino.properties.
2. With a text editor, open the security_domino.properties file, specify values for
properties, and then save and close the file.
v The helper file and the following table provide example values for some
directory properties. Do not assume the example values are correct for your
environment; you must evaluate each property to determine the appropriate
value for your environment.
v Type distinguished names in lowercase characters.
v Ignore any properties in the helper file that are not described in the
following table.
Property
Description
IBM WebSphere Application
Server properties
WasUserid
The distinguished name in the LDAP directory for the
WebSphere Application Server administrator. This can
be the same name as the IBMWebSphere Portal Server
administrator (PortalAdminId).
Example: cn=wasadmin,o=acme
WasPassword
The password for the WasUserid name. As a security
measure, do not type the password in the helper file.
Type the password when you run the wizard.
WpsHostName
The host name for the WebSphere Portal Server.
Type localhost.
WebSphere Portal Server
configuration properties
158
Installation and Upgrade Guide
Property
Description
PortalAdminId
The distinguished name of the WebSphere Portal
Server administrator in the LDAP directory. This name
must be a member of the WebSphere Portal Server
administrators group defined by the
PortalAdminGroupId property.
Note: This account must include a value for the mail
attribute. If the account does not have a value for the
mail attribute, enabling LDAP security will fail.
Example: cn=portaladmin,o=acme
PortalAdminIdShort
The short form of the WebSphere Portal Server
administrator name.
Example: portaladmin
PortalAdminPwd
Password for the WebSphere Portal Server
administrator. As a security measure, do not type the
password in the helper file. Type the password when
you run the wizard.
Note: Do not include the following characters in the
password because they can cause authentication
failures:
[email protected]()#$%
PortalAdminGroupId
The distinguished name of the WebSphere Portal
administrators group in the LDAP directory to which
the WebSphere Portal Server administrator belongs.
This group must define its user and group members
using the members’ distinguished names.
Example: cn=portaladmins,o=acme
PortalAdminGroupIdShort
The short form of the WebSphere Portal Server
administrators group name.
Example: portaladmins
WebSphere Portal Server security
properties
LTPAPassword
The password used to encrypt and decrypt the LTPA
keys. As a security measure, do not type the password
in the helper file. Type the password when you run
the wizard.
LTPATimeout
Time period in minutes at which an LTPA token
expires.
Example: 120
SSOEnabled
Indicates whether single sign-on is enabled (true or
false).
SSORequiresSSL
Indicates whether single sign-on is enabled only for
HTTPS Secure Socket Layer (SSL) connections.
Type false. If you want to configure SSL, do so only
after you have enabled LDAP security and verified the
LDAP directory configuration.
Chapter 4 Connecting to an LDAP Directory Server
159
Property
Description
SSODomainName
The domain name for all single sign-on hosts.
Example: acme.com
Do not type a leading ″.″ For example, type acme.com,
and not .acme.com.
General global security properties
useDomainQualifiedUserNames
Indicates whether to qualify user names with the
security domain within which they reside (true or
false).
The default value (false) is recommended for most
environments.
cacheTimeout
Timeout for the security cache.
The default value (600) is recommended for most
environments.
issuePermissionWarnings
Indicates whether during application deployment and
application start, the security run time emits a
warning if applications are granted any custom
permissions (true or false).
The default value (true) is recommended for most
environments.
activeProtocol
The authentication protocol for RMI/IIOP requests
when security is enabled.
The default value (BOTH) is recommended for most
environments.
activeAuthmechanism
The authentication mechanism when security is
enabled.
The default value (LTPA) is recommended for most
environments.
LDAP properties
LDAPHostName
The host name for your LDAP server.
Example: domldap.acme.com
LDAPPort
The LDAP server port number. Typically you type 389.
Do not type 636, the port typically used for SSL
connections. If you want to configure an SSL port for
LDAP, do so after you have enabled LDAP security
and verified the LDAP directory configuration.
160
Installation and Upgrade Guide
Property
Description
LDAPAdminUId
The distinguished name in the LDAP directory that
WebSphere Portal Server and IBM WebSphere Member
Manager use to bind to the directory. The level of
access given this name determines the level of access
that IBM Workplace Collaboration Services has to the
directory. This name does not have to contain a uid
attribute.
Note: Give this account read-only access to prevent
users from using the Sign-up link to register accounts
in the directory, and from using the Edit My Profile
link to change attributes in the directory, such as their
e-mail addresses.
Example: cn=ldapadmin,o=acme
LDAPAdminPwd
The password for the name assigned to the
LDAPAdminUId property. As a security measure, do
not type the password in the helper file. Type the
password when you run the wizard.
LDAPServerType
Do not change, leave as DOMINO502.
LDAPBindID
Distinguished name that WebSphere Application
Server uses to bind to the directory.
Example: cn=wpsbind,o=acme
LDAPBindPassword
The password for the LDAPBindID name. As a
security measure, do not type the password in the
helper file. Type the password when you run the
wizard.
Advanced LDAP properties
LDAPSuffix
The LDAP suffix for your directory server. Domino
Directory does not require a value for this property,
and it is typically left blank.
If you type a value for LDAPSuffix, for example
o=acme, you must change any non-distinguished (flat)
group names to distinguished names containing the
suffix. This step allows group names to be found. For
example, if you type o=acme as the LDAPSuffix, then
groups names must include the suffix, for example,
cn=portaladmins,o=acme.
LDAPUserPrefix
The leftmost attribute of user names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPUserSuffix
The naming context at which to begin searches for
user names in the directory. Domino Directory does
not require a value for this property, and it is typically
left blank.
LDAPGroupPrefix
The leftmost attribute of group names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPGroupSuffix
The naming context at which to begin searches for
group names in the directory. Domino Directory does
not require a value for this property, and it is typically
left blank.
Chapter 4 Connecting to an LDAP Directory Server
161
Property
Description
LDAPUserObjectClass
The object class used for users.
Example: dominoPerson
LDAPGroupObjectClass
The object class used for groups.
Example: dominoGroup
LDAPGroupMember
The attribute used for the members of groups.
Example: member
LDAPUserFilter
The filter used to search for user accounts. The filter
must include the following text:
(&(|(<userprefix>=%v)(mail=%v))(objectclass=
<userobjectclass>))
where <userprefix> is the value specified for the
LDAPUserPrefix property and <userobjectclass> is the
value specified for the LDAPUserObjectClass property.
Example:
(&(|(cn=%v)(uid=%v)(mail=%v))(objectclass=
dominoPerson))
LDAPGroupFilter
The filter used to search for groups accounts. The filter
must include the following text:
(&(<groupprefix>=%v)(objectclass=
<groupobjectclass>))
where <groupprefix> is the value specified for the
LDAPGroupPrefix property and <groupobjectclass> is
the value specified for the LDAPGroupObjectClass
property.
Example: (&(cn=%v)(objectclass=dominoGroup))
LDAPGroupMinimumAttributes
Attributes loaded for group searches and related to
performance. Leave this property blank.
LDAPUserBaseAttributes
Attributes loaded for user login related to
performance. Type givenName,sn,preferredLanguage.
Also type the following values to allow users, for
example calendar users, to set international time and
date preferences in the Edit My Profile page:
,ibm-regionalLocale,ibm-timeZone,
ibm-preferredCalendar,ibm-firstDayOfWeek,
ibm-firstWorkDayOfWeek
LDAPUserMinimumAttributes
Attributes loaded for user searches and related to
performance. Leave this property blank.
LDAPsearchTimeout
Value in seconds for the amount of time the LDAP
server has to respond before canceling a request.
Example: 120
LDAPreuseConnection
162
Installation and Upgrade Guide
Indicates whether LDAP connections are reused (true
or false). If your environment uses a frontend server to
spray requests to multiple backend LDAP directory
servers, type false. If your environment does not use
an intermediate server but instead authenticates
directly with the LDAP directory server, type true.
Property
Description
LDAPIgnoreCase
Indicates whether LDAP searches are case-sensitive
(true or false).
Related tasks
Enabling LDAP security for Domino Directory
Connecting to Domino Directory
Related reference
Root installation directories
Enabling LDAP security for Domino Directory
Perform the following steps to disable security, and then to enable LDAP security
for IBM Lotus Domino Directory. These steps assume you are running the
Configuration Wizard using the graphical user interface. If you are using the
console interface, to advance in the wizard, type the number the wizard indicates
rather than click Next. Online help is not available in console mode.
If you have already enabled LDAP security, you can follow these steps to change
LDAP configuration properties. However, you should not change to a different
LDAP directory that is not a replica of the directory currently configured. If you do
so, users’ unique identifiers are lost and users will be unable to authenticate or
access data created previously.
1. Make sure you have made a backup copy of the security_domino.properties
helper file, and have edited the helper file to accommodate your directory
environment.
Note: Make sure the account specified for the PortalAdminId property
includes a value for the mail attribute. If the account does not have a
value for the mail attribute, enabling LDAP security will fail.
2. Start your LDAP directory server.
3. Start the Configuration Wizard. Make sure that Cloudscape and server1 are
running, and that WebSphere_Portal and Mail_Server_1 are stopped before
doing so.
For more information, see the chapter ″Installing IBM Workplace
Collaboration Services.″
4. Disable WebSphere Application Server global security:
a. At the Select the configuration task that you want to perform dialog box
in the Configuration Wizard, click Disable security, and then click Next.
b. At the WebSphere Application Server global security is enabled. Enter
the user ID and password to be used for Websphere Application Server
administration dialog box, type the administrator name and password
specified during IBM Workplace Collaboration Services installation, and
then click Next.
Note: If LDAP security is already enabled, and you are preparing to
re-enable LDAP security in order to change the LDAP directory
configuration, type the name of the current WebSphere Application
Server administrator name and password in the LDAP directory
instead.
c. At the Please enter an appropriate properties file location dialog box,
type the path and filename for the wpconfig.properties file, located in the
<wp_root>/config directory, where <wp_root> is the root WebSphere Portal
Chapter 4 Connecting to an LDAP Directory Server
163
Server installation directory. For example, type
/opt/IBM/Workplace/PortalServer/config/wpconfig.properties.
d. Verify that the next dialog box contains the required values indicated in
the following table, then click Next. Do not leave any of the properties
blank.
Property
Action
PortalAdminID
Verify that the value is uid=wpsadmin,o=default organization. Or
if LDAP security is enabled, verify that the value is the
distinguished name of the current WebSphere Portal Server
administrator in the LDAP directory.
PortalAdminIdShort
Verify that the value is wpsadmin. Or if LDAP security is
enabled, verify that the value is the short form of the current
WebSphere Portal Server administrator in the LDAP directory.
PortalAdminPwd
Type the administrator password that you specified during IBM
Workplace Collaboration Services installation. Or if LDAP security
is enabled, type the password for the current Websphere Portal
Server administrator in the LDAP directory.
PortalAdminGroupId
Verify that the value is cn=wpsadmins,o=default organization. Or
if LDAP security is enabled, type the distinguished name of the
current WebSphere Portal Server administrators group.
DbPassword
Accept the default hidden password value.
WmmDbPassword
Accept the default hidden password value.
5.
6.
7.
8.
9.
e. At the The Configuration Wizard is ready to run the following
configuration: Disable security dialog box, click Next to disable security.
See the progress bar and wait for the wizard to finish.
f. At the The following configuration has completed successfully: Disable
security dialog box, click Finish.
Click Run Wizard Again.
At the Select the configuration task that you want to perform dialog box,
click Enable LDAP security, and then click Next.
At the Select the LDAP type to use for authentication dialog box, click IBM
Lotus Domino Enterprise Server, and then click Next.
At the Please enter an appropriate properties file location dialog box, type
<wp_root>/config/helpers/security_domino.properties. and then click Next.
Advance through the wizard.
v Verify at each stage that the values the wizard reads from the helper file are
correct. Accurate values are essential for proper LDAP directory
configuration.
v Make sure the LDAP account assigned to the PortalAdminId property
includes a value for the mail attribute, otherwise enabling LDAP security
will fail.
v Remember to type the required passwords, because you did not type them
in the helper file.
v The wizard may not read the domain name specified for the
SSODomainName property from the helper file. In this case, be sure to type
the SSO domain name again in the wizard.
v If you change a distinguished name, the LdapUserPrefix, or the
LdapGroupPrefix, remember to use lowercase characters.
10. Near the end of the wizard, type values for the following properties, and then
click Next. These properties are not included in the helper file.
164
Installation and Upgrade Guide
Property
Action
WmmDbPassword
Type any text but do not leave the property blank.
DbPassword
Type any text but do not leave the property blank.
LWPDBAdminPassword
Type any text but do not leave the property blank.
11. At the The Configuration Wizard is ready to run the following
configuration: Enable LDAP security dialog box, click Next to run the
wizard. See the progress bar and wait for the wizard to finish.
12. If you see the dialog box that says The following configuration has
completed successfully: Enable LDAP security, click Finish to exit the
wizard, then continue to Step 13. If the wizard finishes with errors, perform
the following steps:
a. Click Finish.
b. Open the configwizard.log and configwizardlog.txt files to help you
troubleshoot errors and determine the correct values:
v <wp_root>/log/configwizard.log
v <wp_root>/log/configwizardlog.txt
Tip: Rename the two log files to reflect the configuration task chosen, so
you can find them easily if you need them in the future.
c. Correct any incorrect values in your helper file.
d. Repeat Step 1 through Step 12.
13. To allow IBM WebSphere Portal Server to follow LDAP referrals when
communicating with a server in front of multiple LDAP directory servers,
complete the following manual steps:
a. With a text editor, open the <wp_root>\shared\app\wmm\wmm.xml file.
b. Add the following line to the <ldapRepository name=″wmmLDAP″> tag,
directly after the ldapPort= line:
java.naming.referral="follow"
c. Save the file.
Related tasks
“Configuring read-only access to Domino Directory”
Connecting to Domino Directory
Related reference
Root installation directories
Configuring read-only access to Domino Directory
Perform the following optional steps to configure read-only access to the IBM
Lotus Domino Directory. Read-only access prevents users from using the Sign-up
and Edit My Profile links in the IBM WebSphere Portal Server page to register
themselves in the directory and to change personal attributes in the directory, such
as e-mail addresses.
1. Make sure that the account name you specified for the LDAPAdminUId
property when you enabled LDAP security has read-only access to the
directory.
2. Stop the WebSphere Portal Server.
3. Remove the Sign-up and Edit My Profile links from the WebSphere Portal
Server page:
a. Change to the <wp_root>\config directory.
Chapter 4 Connecting to an LDAP Directory Server
165
b. Type the following command:
Microsoft Windows
WPSconfig action-fixup-signup-link
IBM AIX, Linux, Solaris, IBM i5/OS
./WPSconfig.sh action-fixup-signup-link
Related tasks
Verifying the Domino Directory configuration
Connecting to Domino Directory
Related reference
Root installation directories
Verifying the Domino Directory configuration
Perform the following steps to verify the IBM Lotus Domino Directory
configuration.
1. Stop and restart the database server.
2. Start IBM WebSphere Portal Server and IBM Workplace Collaboration Services
servers:
Microsoft Windows
Navigate to the <was_root>\bin directory and type the following commands:
startServer.bat WebSphere_Portal
startServer.bat Mail_Server_1
IBM AIX, Linux, Solaris
Navigate to the <was_root>/bin directory and type the following commands:
./startServer.sh WebSphere_Portal
./startServer.sh Mail_Server_1
IBM i5/OS
Start the QShell Interpreter by entering STRQSH on an i5/OS command line,
and then type the following command: :
/qibm/proddata/webas5/pme/bin/startServer WebSphere_Portal -instance <instance>
where <instance> is the name of the Workplace Collaboration Services instance.
3. Type the following URL in a Web browser to start the IBM WebSphere
Administrative Console:
AIX, Linux, Solaris, Windows
http://<hostname>:9091/admin
where <hostname> is the fully qualified name of the server.
IBM i5/OS
http://<hostname>:<admin_port>/admin
where <hostname> is the fully qualified name of the server and <admin_port> is
the base port number for the instance plus10.
4. Test that you can log in as the IBM WebSphere Application Server
administrator.
5. If you have just enabled security on Node 1 of a Network Deployment, you
should now enable security on the Deployment Manager.
For information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
166
Installation and Upgrade Guide
For information on configuring Secure Sockets Layer (SSL) over LDAP, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related concepts
“Optional post-installation tasks” on page 399
Related tasks
“Enabling LDAP security on the Deployment Manager” on page 101
Connecting to Domino Directory
Related reference
Root installation directories
Connecting to Active Directory
Perform the following steps to configure IBM Workplace Collaboration Services to
use Microsoft Active Directory:
1. Create required administrative accounts.
2.
3.
4.
5.
6.
7.
Add required user attributes to the Active Directory schema.
Index attributes.
Edit the helper file.
Use the Configuration Wizard to enable LDAP security.
(Optional) Configure read-only directory access.
Verify the LDAP configuration.
Related concepts
“Phase 4: Connecting to an LDAP directory server” on page 141
Related tasks
“Connecting to an LDAP directory in a Network Deployment” on page 142
Creating administrative accounts for Active Directory
Create the following required administrative accounts in the LDAP directory before
you enable LDAP security. For instructions, see the Microsoft Active Directory
documentation. Each account corresponds to properties that you specify in the
helper file and in the wizard.
Related properties in helper file and
wizard
LDAP account
IBM WebSphere Application Server
administrator. This can be the same as the
IBM WebSphere Portal Server administrator.
WasUserid
WebSphere Portal Server administrator.
PortalAdminId
WasPassword
Note: This account must include a value for PortalAdminIdShort
the mail attribute. If the account does not
have a value for the mail attribute, enabling PortalAdminPwd
LDAP security will fail.
Do not use the following characters in the
password (PortalAdminPwd) because they
can cause authentication failures:
!()@#$%
Chapter 4 Connecting to an LDAP Directory Server
167
LDAP account
Related properties in helper file and
wizard
WebSphere Portal Server administrator
PortalAdminGroupId
group. This group must include the name of
PortalAdminGroupIdShort
the WebSphere Portal Server administrator.
The group must define its user and group
members using the members’ distinguished
names.
Name that WebSphere Portal Server and
LDAPAdminUId
IBM WebSphere Member Manager use to
bind to the LDAP directory. The access level LDAPAdminPwd
given this name controls the access that IBM
Workplace Collaboration Services has to the
directory.
Note: Give this account read-only access if
you want to prevent users from using the
Sign-up link to register accounts in the
directory, and from using the Edit My
Profile link to change attributes in the
directory, such as their e-mail addresses.
Name that WebSphere Application Server
uses to bind to the LDAP directory.
LDAPBindID
LDAPBindPassword
Related tasks
“Adding required user attributes to the Active Directory schema”
“Connecting to Active Directory” on page 167
Adding required user attributes to the Active Directory schema
IBM Workplace Collaboration Services requires that the following attributes be
defined in the schema for the user object class. You must add these attributes to
the user object class in the Microsoft Active Directory schema if they are not
already defined for it. The user object class is typically ″user.″
v businessCategory
v departmentNumber
v description
v displayName
v
v
v
v
employeeNumber
employeeType
preferredLanguage
roomNumber
For information on adding attributes to the schema, see the Active Directory
documentation.
Related tasks
“Indexing attributes for Active Directory”
“Connecting to Active Directory” on page 167
Indexing attributes for Active Directory
You must index specific attributes in the directory. This step is required.
Index the following attributes in user accounts:
168
Installation and Upgrade Guide
v mail
v the additional attribute or attributes specified for the LDAPUserFilter property
in the helper file; for example, cn and samAccountName.
Refer to the Microsoft Active Directory documentation for instructions on indexing.
Related tasks
“Editing the helper file for Active Directory”
“Connecting to Active Directory” on page 167
Editing the helper file for Active Directory
You use a helper file to aid in enabling LDAP security. You make a copy of the
helper file, then edit the copy, providing values for directory properties that are
appropriate for your LDAP directory environment. When you run the
Configuration Wizard to enable LDAP security, the wizard displays the values you
specified in the helper file, which you can then verify.
Note: Only someone with advanced knowledge of LDAP concepts and
administration who is familiar with your directory environment should edit
the helper file.
1. Make a backup copy of the Microsoft Active Directory helper file,
<wp_root>\config\helpers\security_active_directory.properties.
2. With a text editor, open the security_active_directory.properties file, specify
values for properties, and then save and close the file.
v The helper file and the following table provide example values for some
directory properties. Do not assume the example values are correct for your
environment; you must evaluate each property to determine the appropriate
value for your environment.
v Type distinguished names in lowercase characters.
v Ignore any properties in the helper file that are not described in the
following table.
Property
Description
IBM WebSphere Application
Server properties
WasUserid
The distinguished name in the LDAP directory for the
WebSphere Application Server administrator. This can
be the same name as the IBM WebSphere Portal Server
administrator (PortalAdminId).
Example: cn=wasadmin,cn=users,dc=acme,dc=com
WasPassword
The password for the WasUserid name. As a security
measure, do not type the password in the helper file.
Type the password when you run the wizard.
WpsHostName
The host name for the WebSphere Portal Server.
Type localhost.
WebSphere Portal Server
configuration properties
Chapter 4 Connecting to an LDAP Directory Server
169
Property
Description
PortalAdminId
The distinguished name of the WebSphere Portal
Server administrator in the LDAP directory. This name
must be a member of the WebSphere Portal Server
administrators group defined by the
PortalAdminGroupId property.
Note: This account must include a value for the mail
attribute. If the account does not have a value for the
mail attribute, enabling LDAP security will fail.
Example: cn=portaladmin,cn=users,dc=acme,dc=com
PortalAdminIdShort
The short form of the WebSphere Portal Server
administrator name.
Example: portaladmin
PortalAdminPwd
Password for the WebSphere Portal Server
administrator. As a security measure, do not type the
password in the helper file. Type the password when
you run the wizard.
Note: Do not include the following characters in the
password because they can cause authentication
failures:
[email protected]()#$%
PortalAdminGroupId
The distinguished name of the WebSphere Portal
Server administrators group in the LDAP directory to
which the WebSphere Portal Server administrator
belongs. This group must define its user and group
members using the members’ distinguished names.
Example:
cn=portaladmins,cn=groups,dc=acme,dc=com
PortalAdminGroupIdShort
The short form of the WebSphere Portal Server
administrators group name.
Example: portaladmins
WebSphere Portal Server security
properties
LTPAPassword
The password used to encrypt and decrypt the LTPA
keys. As a security measure, do not type the password
in the helper file. Type the password when you run
the wizard.
LTPATimeout
Time period in minutes at which an LTPA token
expires.
Example: 120
SSOEnabled
Indicates whether single sign-on is enabled (true or
false).
SSORequiresSSL
Indicates whether single sign-on is enabled only for
HTTPS Secure Socket Layer (SSL) connections.
Type false. If you want to configure SSL, do so only
after you have enabled LDAP security and verified the
LDAP directory configuration.
170
Installation and Upgrade Guide
Property
Description
SSODomainName
The domain name for all single sign-on hosts.
Example: acme.com
Do not type a leading ″.″ For example, type acme.com,
and not .acme.com.
General global security properties
useDomainQualifiedUserNames
Indicates whether to qualify user names with the
security domain within which they reside (true or
false).
The default value (false) is recommended for most
environments.
cacheTimeout
Timeout for the security cache.
The default value (600) is recommended for most
environments.
issuePermissionWarnings
Indicates whether during application deployment and
application start, the security run time emits a
warning if applications are granted any custom
permissions (true or false).
The default value (true) is recommended for most
environments.
activeProtocol
The authentication protocol for RMI/IIOP requests
when security is enabled.
The default value (BOTH) is recommended for most
environments.
activeAuthmechanism
The authentication mechanism when security is
enabled.
The default value (LTPA) is recommended for most
environments.
LDAP properties
LDAPHostName
The host name for your LDAP server.
Example: adldap.acme.com
LDAPPort
The LDAP server port number. Typically you type 389.
Do not type 636, the port typically used for SSL
connections. If you want to configure an SSL port for
LDAP, do so after you have enabled LDAP security
and verified the LDAP directory configuration.
Chapter 4 Connecting to an LDAP Directory Server
171
Property
Description
LDAPAdminUId
The distinguished name in the LDAP directory that
WebSphere Portal Server and IBM WebSphere Member
Manager use to bind to the directory. The level of
access given this name determines the level of access
that IBM Workplace Collaboration Services has to the
directory. This name does not have to contain a uid
attribute.
Note: Give this account read-only access to prevent
users from using the Sign-up link to register accounts
in the directory, and from using the Edit My Profile
link to change attributes in the directory, such as their
e-mail addresses.
Example: cn=ldapadmin,cn=users,dc=acme,dc=com
LDAPAdminPwd
The password for the name assigned to the
LDAPAdminUId property. As a security measure, do
not type the password in the helper file. Type the
password when you run the wizard.
LDAPServerType
Do not change, leave as ACTIVE_DIRECTORY.
LDAPBindID
Distinguished name that WebSphere Application
Server uses to bind to the directory.
Example: cn=wpsbind,cn=users,dc=acme,dc=com
LDAPBindPassword
The password for the LDAPBindID name. As a
security measure, do not type the password in the
helper file. Type the password when you run the
wizard.
Advanced LDAP properties
LDAPSuffix
The LDAP suffix for your directory server. This
property determines the naming context at which to
begin directory searches for users and groups.
Example: dc=acme,dc=com
LDAPUserPrefix
The leftmost attribute of user names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPUserSuffix
The naming context at which to begin searches for
user names in the directory.
Example: cn=users
Do not include the LDAPSuffix value as part of this
value. For example, do not type
cn=users,dc=acme,dc=com.
LDAPGroupPrefix
The leftmost attribute of group names in the directory.
Type the value in lowercase characters.
Example: cn
172
Installation and Upgrade Guide
Property
Description
LDAPGroupSuffix
The naming context at which to begin searches for
group names in the directory.
Example: cn=groups
Do not include the LDAPSuffix value as part of this
value. For example, do not type
cn=groups,dc=acme,dc=com.
LDAPUserObjectClass
The object class used for users.
Example: user
LDAPGroupObjectClass
The object class used for groups.
Example: group
LDAPGroupMember
The attribute used for the members of groups.
Example: member
LDAPUserFilter
The filter used to search for user accounts. The filter
must include the following text:
(&(|(<userprefix>=%v)(mail=%v))(objectclass=
<userobjectclass>))
where <userprefix> is the value specified for the
LDAPUserPrefix property and <userobjectclass> is the
value specified for the LDAPUserObjectClass property.
Example:
(&(|(cn=%v)(samAccountName=%v)(mail=%v)
(objectclass=user))
LDAPGroupFilter
The filter used to search for groups accounts. The filter
must include the following text:
(&(<groupprefix>=%v)(objectclass=
<groupobjectclass>))
where <groupprefix> is the value specified for the
LDAPGroupPrefix property and <groupobjectclass> is
the value specified for the LDAPGroupObjectClass
property.
Example: (&(cn=%v)(objectclass=group))
LDAPGroupMinimumAttributes
Attributes loaded for group searches and related to
performance. Leave this property blank.
LDAPUserBaseAttributes
Attributes loaded for user login related to
performance. Type givenName,sn,preferredLanguage.
Also type the following values to allow users, for
example calendar users, to set international time and
date preferences in the Edit My Profile page:
,ibm-regionalLocale,ibm-timeZone,
ibm-preferredCalendar,ibm-firstDayOfWeek,
ibm-firstWorkDayOfWeek
LDAPUserMinimumAttributes
Attributes loaded for user searches and related to
performance. Leave this property blank.
Chapter 4 Connecting to an LDAP Directory Server
173
Property
Description
LDAPsearchTimeout
Value in seconds for the amount of time the LDAP
server has to respond before canceling a request.
Example: 120
LDAPreuseConnection
Indicates whether LDAP connections are reused (true
or false). If your environment uses a frontend server to
spray requests to multiple backend LDAP directory
servers, type false. If your environment does not use
an intermediate server but instead authenticates
directly with the LDAP directory server, type true.
LDAPIgnoreCase
Indicates whether LDAP searches are case-sensitive
(true or false).
Related tasks
“Enabling LDAP security for Active Directory”
“Connecting to Active Directory” on page 167
Related reference
“Root installation directories” on page 407
Enabling LDAP security for Active Directory
Perform the following steps to disable security, and then to enable LDAP security
for Microsoft Active Directory. These steps assume you are running the
Configuration Wizard using the graphical user interface. If you are using the
console interface, to advance in the wizard, type the number the wizard indicates
rather than click Next. Online help is not available in console mode.
If you have already enabled LDAP security, you can follow these steps to change
LDAP configuration properties. However, you should not change to a different
LDAP directory that is not a replica of the directory currently configured. If you do
so, users’ unique identifiers are lost and users will be unable to authenticate or
access data created previously.
1. Make sure you have made a backup copy of the
security_active_directory.properties helper file, and have edited the helper file
to accommodate your directory environment.
Note: Make sure the account specified for the PortalAdminId property
includes a value for the mail attribute. If the account does not have a
value for the mail attribute, enabling LDAP security will fail.
2. Start your LDAP directory server.
3. Start the Configuration Wizard. Make sure th Cloudscape and server1 are
running, and that WebSphere_Portal and Mail_Server_1 are stopped before
doing so.
For more information, see the chapter ″Installing IBM Workplace
Collaboration Services.″
4. Disable WebSphere Application Server global security:
a. At the Select the configuration task that you want to perform dialog box
in the Configuration Wizard, click Disable security, and then click Next.
b. At the WebSphere Application Server global security is enabled. Enter
the user ID and password to be used for Websphere Application Server
174
Installation and Upgrade Guide
administration dialog box, type the administrator name and password
specified during IBM Workplace Collaboration Services installation, and
then click Next.
Note: If LDAP security is already enabled, and you are preparing to
re-enable LDAP security in order to change the LDAP directory
configuration, type the name of the current WebSphere Application
Server administrator name and password in the LDAP directory
instead.
c. At the Please enter an appropriate properties file location dialog box,
type the path and filename for the wpconfig.properties file, located in the
<wp_root>/config directory, where <wp_root> is the root WebSphere Portal
Server installation directory. For example, type
/opt/IBM/Workplace/PortalServer/config/wpconfig.properties.
d. Verify that the next dialog box contains the required values indicated in
the following table, then click Next. Do not leave any of the properties
blank.
Property
Action
PortalAdminID
Verify that the value is uid=wpsadmin,o=default organization. Or
if LDAP security is enabled, verify that the value is the
distinguished name of the current WebSphere Portal Server
administrator in the LDAP directory.
PortalAdminIdShort
Verify that the value is wpsadmin. Or if LDAP security is
enabled, verify that the value is the short form of the current
WebSphere Portal Server administrator in the LDAP directory.
PortalAdminPwd
Type the administrator password that you specified during IBM
Workplace Collaboration Services installation. Or if LDAP security
is enabled, type the password for the current Websphere Portal
Server administrator in the LDAP directory.
PortalAdminGroupId
Verify that the value is cn=wpsadmins,o=default organization. Or
if LDAP security is enabled, type the distinguished name of the
current WebSphere Portal Server administrators group.
DbPassword
Accept the default hidden password value.
WmmDbPassword
Accept the default hidden password value.
5.
6.
7.
8.
9.
e. At the The Configuration Wizard is ready to run the following
configuration: Disable security dialog box, click Next to disable security.
See the progress bar and wait for the wizard to finish.
f. At the The following configuration has completed successfully: Disable
security dialog box, click Finish.
Click Run Wizard Again.
At the Select the configuration task that you want to perform dialog box,
click Enable LDAP security, and then click Next.
At the Select the LDAP type to use for authentication dialog box, click
Microsoft Active Directory, and then click Next.
At the Please enter an appropriate properties file location dialog box, type
<wp_root>/config/helpers/security_active_directory.properties, and then click
Next.
Advance through the wizard.
v Verify at each stage that the values the wizard reads from the helper file are
correct. Accurate values are essential for proper LDAP directory
configuration.
Chapter 4 Connecting to an LDAP Directory Server
175
v Remember to type the required passwords, because you did not type them
in the helper file.
v The wizard may not read the domain name specified for the
SSODomainName property from the helper file. In this case, be sure to type
the SSO domain name again in the wizard.
v If you change a distinguished name, the LdapUserPrefix, or the
LdapGroupPrefix, remember to use lowercase characters.
10. Near the end of the wizard, type values for the following properties, and then
click Next. These properties are not included in the helper file.
Property
Action
WmmDbPassword
Type any text but do not leave the property blank.
DbPassword
Type any text but do not leave the property blank.
LWPDBAdminPassword
Type any text but do not leave the property blank.
11. At the The Configuration Wizard is ready to run the following
configuration: Enable LDAP security dialog box, click Next to run the
wizard. See the progress bar and wait for the wizard to finish.
12. If you see the dialog box that says The following configuration has
completed successfully: Enable LDAP security, click Finish to exit the
wizard, then continue to Step 13. If the wizard finishes with errors, perform
the following steps:
a. Click Finish.
b. Open the configwizard.log and configwizardlog.txt files to help you
troubleshoot errors and determine the correct values:
v <wp_root>/log/configwizard.log
v <wp_root>/log/configwizardlog.txt
Tip: Rename the two log files to reflect the configuration task chosen, so
you can find them easily if you need them in the future.
c. Correct any incorrect values in your helper file.
d. Repeat Step 1 through Step 12.
13. To allow IBM WebSphere Portal Server to follow LDAP referrals when
communicating with a server in front of multiple LDAP directory servers,
complete the following manual steps:
a. With a text editor, open the <wp_root>\shared\app\wmm\wmm.xml file.
b. Add the following line to the <ldapRepository name=″wmmLDAP″> tag,
directly after the ldapPort= line:
java.naming.referral="follow"
c. Save the file.
Related tasks
“Configuring read-only access to Active Directory” on page 177
“Editing the helper file for Active Directory” on page 169
“Connecting to Active Directory” on page 167
Related reference
“Root installation directories” on page 407
176
Installation and Upgrade Guide
Configuring read-only access to Active Directory
Perform the following optional steps to configure read-only access to Microsoft
Active Directory. Read-only access prevents users from using the Sign-up and Edit
My Profile links in the IBM WebSphere Portal Server page to register themselves in
the directory and to change personal attributes in the directory, such as e-mail
addresses.
1. Make sure that the account name you specified for the LDAPAdminUId
property when you enabled LDAP security has read-only access to the
directory.
2. Stop the WebSphere Portal Server.
3. Remove the Sign-up and Edit My Profile links from the WebSphere Portal
Server page:
a. Change to the <wp_root>\config directory.
b. Type the following command:
Microsoft Windows
WPSconfig action-fixup-signup-link
IBM AIX, Linux, Solaris, IBM i5/OS
./WPSconfig.sh action-fixup-signup-link
Related tasks
Verifying the Microsoft Active Directory configuration
Connecting to Microsoft Active Directory
Related reference
Root installation directories
Verifying the Active Directory configuration
Perform the following steps to verify the Microsoft Active Directory configuration.
1. Stop and restart the database server.
2. Start IBM WebSphere Portal Server and IBM Workplace Collaboration Services
servers:
Microsoft Windows
Navigate to the <was_root>\bin directory and type the following commands:
startServer.bat WebSphere_Portal
startServer.bat Mail_Server_1
IBM AIX, Linux, Solaris
Navigate to the <was_root>/bin directory and type the following commands:
./startServer.sh WebSphere_Portal
./startServer.sh Mail_Server_1
IBM i5/OS
Start the QShell Interpreter by entering STRQSH on an i5/OS command line,
and then type the following command:
/qibm/proddata/webas5/pme/bin/startServer WebSphere_Portal -instance <instance>
where <instance> is the name of the Workplace Collaboration Services instance.
3. Type the following URL in a Web browser to start the IBM WebSphere
Administrative Console:
AIX, Linux, Solaris, Windows
http://<hostname>:9091/admin
Chapter 4 Connecting to an LDAP Directory Server
177
where <hostname> is the fully qualified name of the server.
IBM i5/OS
http://<hostname>:<admin_port>/admin
where <hostname> is the fully qualified name of the server and <admin_port> is
the base port number for the instance plus10.
4. Test that you can log in as the IBM WebSphere Application Server
administrator.
5. If you have just enabled security on Node 1 of a Network Deployment, you
should now enable security on the Deployment Manager.
For information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
For information on configuring Secure Sockets Layer (SSL) over LDAP, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related concepts
“Optional post-installation tasks” on page 399
Related tasks
“Enabling LDAP security on the Deployment Manager” on page 101
“Connecting to Active Directory” on page 167
Related reference
“Root installation directories” on page 407
Connecting to Sun Java System Directory Server
Perform the following steps to configure IBM Workplace Collaboration Services to
use Sun Java System Directory Server:
1. Create required administrative accounts.
2. Index specific attributes.
3. Edit the helper file.
4. Use the Configuration Wizard to enable LDAP security.
5. Optional: Configure read-only directory access.
6. Verify the LDAP configuration.
Related concepts
Phase 4: Connecting to an LDAP directory server
Related tasks
Connecting to an LDAP directory in a Network Deployment environment
Creating administrative accounts for Sun Java System Directory
Server
Create the following required administrative accounts in the LDAP directory before
you enable LDAP security. For instructions, see the Sun Java System Directory
Server documentation. Each account corresponds to properties that you specify in
the helper file and in the wizard.
178
Installation and Upgrade Guide
Related properties in helper file and
wizard
LDAP account
IBM WebSphere Application Server
administrator. This can be the same as the
IBM WebSphere Portal Server administrator.
WasUserid
WebSphere Portal Server administrator.
PortalAdminId
WasPassword
Note: This account must include a value for PortalAdminIdShort
the mail attribute. If the account does not
have a value for the mail attribute, enabling PortalAdminPwd
LDAP security will fail.
Do not use the following characters in the
password (PortalAdminPwd) because they
can cause authentication failures:
!()@#$%
WebSphere Portal Server administrator
PortalAdminGroupId
group. This group must include the name of
PortalAdminGroupIdShort
the WebSphere Portal Server administrator.
The group must define its user and group
members using the members’ distinguished
names.
Name that WebSphere Portal Server and
LDAPAdminUId
IBM WebSphere Member Manager use to
bind to the LDAP directory. The access level LDAPAdminPwd
given this name controls the access that IBM
Workplace Collaboration Services has to the
directory.
Note: Give this account read-only access if
you want to prevent users from using the
Sign-up link to register accounts in the
directory, and from using the Edit My
Profile link to change attributes in the
directory, such as their e-mail addresses.
Name that WebSphere Application Server
uses to bind to the LDAP directory.
LDAPBindID
LDAPBindPassword
Related tasks
“Indexing attributes for Sun Java System Directory Server”
“Connecting to Sun Java System Directory Server” on page 178
Indexing attributes for Sun Java System Directory Server
You must index specific attributes in the directory. This step is required.
Index the following attributes in user accounts:
v mail
v the user attribute or attributes specified for the LDAPUserFilter property in the
helper file; for example, uid.
v displayName
Refer to the Sun Java System Directory Server documentation for instructions on
indexing.
Related tasks
“Editing the helper file for Sun Java System Directory Server” on page 180
Chapter 4 Connecting to an LDAP Directory Server
179
“Connecting to Sun Java System Directory Server” on page 178
Editing the helper file for Sun Java System Directory Server
You use a helper file to aid in enabling LDAP security. You make a copy of the
helper file, then edit the copy, providing values for directory properties that are
appropriate for your LDAP directory environment. When you run the
Configuration Wizard to enable LDAP security, the wizard displays the values you
specified in the helper file, which you can then verify.
Note: Only someone with advanced knowledge of LDAP concepts and
administration who is familiar with your directory environment should edit
the helper file.
1. Make a backup copy of the Sun Java System Directory Server helper file,
<wp_root>\config\helpers\security_sun_one.properties.
2. With a text editor, open the security_sun_one.properties file, specify values for
properties, and then save and close the file.
v The helper file and the following table provide example values for some
directory properties. Do not assume the example values are correct for your
environment; you must evaluate each property to determine the appropriate
value for your environment.
v Type distinguished names in lowercase characters.
v Ignore any properties in the helper file that are not described in the
following table.
Property
Description
IBM WebSphere Application
Server properties
WasUserid
The distinguished name in the LDAP directory for the
IBM WebSphere Application Server administrator. This
can be the same name as the IBM WebSphere Portal
Server administrator (PortalAdminId).
Example: uid=wasadmin,ou=people,o=acme.com
WasPassword
The password for the WasUserid name. As a security
measure, do not type the password in the helper file.
Type the password when you run the wizard.
WpsHostName
The host name for the WebSphere Portal Server.
Type localhost.
WebSphere Portal Server
configuration properties
PortalAdminId
The distinguished name of the WebSphere Portal
Server administrator in the LDAP directory. This name
must be a member of the WebSphere Portal Server
administrators group defined by the
PortalAdminGroupId property.
Note: This account must include a value for the mail
attribute. If the account does not have a value for the
mail attribute, enabling LDAP security will fail.
Example: uid=portaladmin,ou=people,o=acme.com
180
Installation and Upgrade Guide
Property
Description
PortalAdminIdShort
The short form of the WebSphere Portal Server
administrator name.
Example: portaladmin
PortalAdminPwd
Password for the WebSphere Portal Server
administrator. As a security measure, do not type the
password in the helper file. Type the password when
you run the wizard.
Note: Do not include the following characters in the
password because they can cause authentication
failures:
[email protected]()#$%
PortalAdminGroupId
The distinguished name of the WebSphere Portal
Server administrators group in the LDAP directory to
which the WebSphere Portal Server administrator
belongs. This group must define its user and group
members using the members’ distinguished names.
Example: cn=portaladmins,ou=people,o=acme.com
PortalAdminGroupIdShort
The short form of the WebSphere Portal Server
administrators group name.
Example: portaladmins
WebSphere Portal Server security
properties
LTPAPassword
The password used to encrypt and decrypt the LTPA
keys. As a security measure, do not type the password
in the helper file. Type the password when you run
the wizard.
LTPATimeout
Time period in minutes at which an LTPA token
expires.
Example: 120
SSOEnabled
Indicates whether single sign-on is enabled (true or
false).
SSORequiresSSL
Indicates whether single sign-on is enabled only for
HTTPS Secure Socket Layer (SSL) connections.
Type false. If you want to configure SSL, do so only
after you have enabled LDAP security and verified the
LDAP directory configuration.
SSODomainName
The domain name for all single sign-on hosts.
Example: acme.com
Do not type a leading ″.″ For example, type acme.com,
and not .acme.com.
General global security properties
useDomainQualifiedUserNames
Indicates whether to qualify user names with the
security domain within which they reside (true or
false).
The default value (false) is recommended for most
environments.
Chapter 4 Connecting to an LDAP Directory Server
181
Property
Description
cacheTimeout
Timeout for the security cache.
The default value (600) is recommended for most
environments.
issuePermissionWarnings
Indicates whether during application deployment and
application start, the security run time emits a
warning if applications are granted any custom
permissions (true or false).
The default value (true) is recommended for most
environments.
activeProtocol
The authentication protocol for RMI/IIOP requests
when security is enabled.
The default value (BOTH) is recommended for most
environments.
activeAuthmechanism
The authentication mechanism when security is
enabled.
The default value (LTPA) is recommended for most
environments.
LDAP properties
LDAPHostName
The host name for your LDAP server.
Example: sunldap.acme.com
LDAPPort
The LDAP server port number. Typically you type 389.
Do not type 636, the port typically used for SSL
connections. If you want to configure an SSL port for
LDAP, do so after you have enabled LDAP security
and verified the LDAP directory configuration.
LDAPAdminUId
The distinguished name in the LDAP directory that
WebSphere Portal Server and IBM WebSphere Member
Manager use to bind to the directory. The level of
access given this name determines the level of access
that IBM Workplace Collaboration Services has to the
directory. This name does not have to contain a uid
attribute.
Note: Give this account read-only access to prevent
users from using the Sign-up link to register accounts
in the directory, and from using the Edit My Profile
link to change attributes in the directory, such as their
e-mail addresses.
Example: uid=ldapadmin,ou=people,o=acme.com
LDAPAdminPwd
The password for the name assigned to the
LDAPAdminUId property. As a security measure, do
not type the password in the helper file. Type the
password when you run the wizard.
LDAPServerType
Do not change, leave as IPLANET.
LDAPBindID
Distinguished name that WebSphere Application
Server uses to bind to the directory.
Example: uid=wpsbind,ou=people,o=acme.com
182
Installation and Upgrade Guide
Property
Description
LDAPBindPassword
The password for the LDAPBindID name. As a
security measure, do not type the password in the
helper file. Type the password when you run the
wizard.
Advanced LDAP properties
LDAPSuffix
The LDAP suffix for your directory server. This
property determines the naming context at which to
begin directory searches for users and groups.
Example: o=acme.com
LDAPUserPrefix
The leftmost attribute of user names in the directory.
Type the value in lowercase characters.
Example: uid
LDAPUserSuffix
The naming context at which to begin searches for
user names in the directory.
Example: ou=people
Do not include the LDAPSuffix value as part of this
value. For example, do not type
ou=people,o=acme.com
LDAPGroupPrefix
The leftmost attribute of group names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPGroupSuffix
The naming context at which to begin searches for
group names in the directory.
Example: ou=people
Do not include the LDAPSuffix value as part of this
value. For example, do not type
ou=people,o=acme.com
LDAPUserObjectClass
The object class used for users.
Example: inetOrgPerson
LDAPGroupObjectClass
The object class used for groups.
Example: groupOfUniqueNames
LDAPGroupMember
The attribute used for the members of groups.
Example: uniqueMember
LDAPUserFilter
The filter used to search for user accounts. The filter
must include the following text:
(&(|(<userprefix>=%v)(mail=%v))(objectclass=
<userobjectclass>))
where <userprefix> is the value specified for the
LDAPUserPrefix property and <userobjectclass> is the
value specified for the LDAPUserObjectClass property.
Example:
(&(|(uid=%v)(mail=%v))(objectclass=inetOrgPerson))
Chapter 4 Connecting to an LDAP Directory Server
183
Property
Description
LDAPGroupFilter
The filter used to search for groups accounts. The filter
must include the following text:
(&(<groupprefix>=%v)(objectclass=
<groupobjectclass>))
where <groupprefix> is the value specified for the
LDAPGroupPrefix property and <groupobjectclass> is
the value specified for the LDAPGroupObjectClass
property.
Example:
(&(cn=%v)(objectclass=groupOfUniqueNames))
LDAPGroupMinimumAttributes
Attributes loaded for group searches and related to
performance. Leave this property blank.
LDAPUserBaseAttributes
Attributes loaded for user login related to
performance. Type givenName,sn,preferredLanguage.
Also type the following values to allow users, for
example calendar users, to set international time and
date preferences in the Edit My Profile page:
,ibm-regionalLocale,ibm-timeZone,
ibm-preferredCalendar,ibm-firstDayOfWeek,
ibm-firstWorkDayOfWeek
LDAPUserMinimumAttributes
Attributes loaded for user searches and related to
performance. Leave this property blank.
LDAPsearchTimeout
Value in seconds for the amount of time the LDAP
server has to respond before canceling a request.
Example: 120
LDAPreuseConnection
Indicates whether LDAP connections are reused (true
or false). If your environment uses a frontend server to
spray requests to multiple backend LDAP directory
servers, type false. If your environment does not use
an intermediate server but instead authenticates
directly with the LDAP directory server, type true.
LDAPIgnoreCase
Indicates whether LDAP searches are case-sensitive
(true or false).
Related tasks
Enabling LDAP security for Sun Java System Directory Server
Connecting to Sun Java System Directory Server
Related reference
Root installation directories
Enabling LDAP security for Sun Java System Directory Server
Perform the following steps to disable IBM WebSphere Application Server global
security, and then to enable LDAP security for Sun Java System Directory Server.
These steps assume you are running the Configuration Wizard using the graphical
user interface. If you are using the console interface, to advance in the wizard, type
the number the wizard indicates rather than click. Next. Online help is not
available in console mode.
184
Installation and Upgrade Guide
If you have already enabled LDAP security, you can follow these steps to change
LDAP configuration properties. However, you should not change to a different
LDAP directory that is not a replica of the directory currently configured. If you do
so, users’ unique identifiers are lost and users will be unable to authenticate or
access data created previously.
1. Make sure you have made a backup copy of the security_sun_one.properties
helper file, and have edited the helper file to accommodate your directory
environment.
Note: Make sure the account specified for the PortalAdminId property
includes a value for the mail attribute. If the account does not have a
value for the mail attribute, enabling LDAP security will fail.
2. Start your LDAP directory server.
3. Start the Configuration Wizard. Make sure that Cloudscape and server1 are
running, and that WebSphere_Portal and Mail_Server_1 are stopped before
doing so.
For more information, see the chapter ″Installing Workplace Collaboration
Services.″
4. Disable WebSphere Application Server global security:
a. At the Select the configuration task that you want to perform dialog box
in the Configuration Wizard, click Disable security, and then click Next.
b. At the WebSphere Application Server global security is enabled. Enter
the user ID and password to be used for Websphere Application Server
administration dialog box, type the administrator name and password
specified during IBM Workplace Collaboration Services installation, and
then click Next.
Note: If LDAP security is already enabled, and you are preparing to
re-enable LDAP security in order to change the LDAP directory
configuration, type the name of the current WebSphere Application
Server administrator name and password in the LDAP directory
instead.
c. At the Please enter an appropriate properties file location dialog box,
type the path and filename for the wpconfig.properties file, located in the
<wp_root>/config directory, where <wp_root> is the root WebSphere Portal
Server installation directory. For example, type
/opt/IBM/Workplace/PortalServer/config/wpconfig.properties.
d. Verify that the next dialog box contains the required values indicated in
the following table, then click Next. Do not leave any of the properties
blank.
Property
Action
PortalAdminID
Verify that the value is uid=wpsadmin,o=default organization. Or
if LDAP security is enabled, verify that the value is the
distinguished name of the current WebSphere Portal Server
administrator in the LDAP directory.
PortalAdminIdShort
Verify that the value is wpsadmin. Or if LDAP security is
enabled, verify that the value is the short form of the current
WebSphere Portal Server administrator in the LDAP directory.
PortalAdminPwd
Type the administrator password that you specified during IBM
Workplace Collaboration Services installation. Or if LDAP security
is enabled, type the password for the current Websphere Portal
Server administrator in the LDAP directory.
Chapter 4 Connecting to an LDAP Directory Server
185
Property
Action
PortalAdminGroupId
Verify that the value is cn=wpsadmins,o=default organization. Or
if LDAP security is enabled, type the distinguished name of the
current WebSphere Portal Server administrators group.
DbPassword
Accept the default hidden password value.
WmmDbPassword
Accept the default hidden password value.
e. At the The Configuration Wizard is ready to run the following
configuration: Disable security dialog box, click Next to disable security.
See the progress bar and wait for the wizard to finish.
f. At the The following configuration has completed successfully: Disable
security dialog box, click Finish.
5. Click Run Wizard Again.
6. At the Select the configuration task that you want to perform dialog box,
click Enable LDAP security, and then click Next.
7. At the Select the LDAP type to use for authentication dialog box, click Sun
ONE Directory Server, and then click Next.
8. At the Please enter an appropriate properties file location dialog box, type
<wp_root>/config/helpers/security_sun_one.properties, and then click Next.
9. Advance through the wizard.
v Verify at each stage that the values the wizard reads from the helper file are
correct. Accurate values are essential for proper LDAP directory
configuration.
v Remember to type the required passwords, because you did not type them
in the helper file.
v The wizard may not read the domain name specified for the
SSODomainName property from the helper file. In this case, be sure to type
the SSO domain name again in the wizard.
v If you change a distinguished name, the LdapUserPrefix, or the
LdapGroupPrefix, remember to use lowercase characters.
10. Near the end of the wizard, type values for the following properties, and then
click Next. These properties are not included in the helper file.
Property
Action
WmmDbPassword
Type any text but do not leave the property blank.
DbPassword
Type any text but do not leave the property blank.
LWPDBAdminPassword
Type any text but do not leave the property blank.
11. At the The Configuration Wizard is ready to run the following
configuration: Enable LDAP security dialog box, click Next to run the
wizard. See the progress bar and wait for the wizard to finish.
12. If you see the dialog box that says The following configuration has
completed successfully: Enable LDAP security, click Finish to exit the
wizard, then continue to Step 13. If the wizard finishes with errors, perform
the following steps:
a. Click Finish.
b. Open the configwizard.log and configwizardlog.txt files to help you
troubleshoot errors and determine the correct values:
v <wp_root>/log/configwizard.log
v <wp_root>/log/configwizardlog.txt
186
Installation and Upgrade Guide
Tip: Rename the two log files to reflect the configuration task chosen, so
you can find them easily if you need them in the future.
c. Correct any incorrect values in your helper file.
d. Repeat Step 1 through Step 12.
13. To allow IBM WebSphere Portal Server to follow LDAP referrals when
communicating with a server in front of multiple LDAP directory servers,
complete the following manual steps:
a. With a text editor, open the <wp_root>\shared\app\wmm\wmm.xml file.
b. Add the following line to the <ldapRepository name=″wmmLDAP″> tag,
directly after the ldapPort= line:
java.naming.referral="follow"
c. Save the file.
Related tasks
“Configuring read-only access to Sun Java System Directory Server”
Connecting to Sun Java System Directory Server
Related reference
Root installation directories
Configuring read-only access to Sun Java System Directory
Server
Perform the following optional steps to configure read-only access to Sun Java
System Directory Server. Read-only access prevents users from using the Sign-up
and Edit My Profile links in the IBM WebSphere Portal Server page to register
themselves in the directory and to change personal attributes in the directory, such
as e-mail addresses.
1. Make sure that the account name you specified for the LDAPAdminUId
property when you enabled LDAP security has read-only access to the
directory.
2. Stop the WebSphere Portal Server.
3. Remove the Sign-up and Edit My Profile links from the WebSphere Portal
Server page:
a. Change to the <wp_root>\config directory.
b. Type the following command:
Microsoft Windows
WPSconfig action-fixup-signup-link
IBM AIX, Linux, Solaris, IBM i5/OS
./WPSconfig.sh action-fixup-signup-link
Related tasks
“Verifying the Sun Java System Directory Server configuration”
“Connecting to Sun Java System Directory Server” on page 178
Related reference
Root installation directories
Verifying the Sun Java System Directory Server configuration
Perform the following steps to verify the Sun Java System Directory Server
configuration.
1. Stop and restart the database server.
Chapter 4 Connecting to an LDAP Directory Server
187
2. Start IBM WebSphere Portal Server and IBM Workplace Collaboration Services
servers:
Microsoft Windows
Navigate to the <was_root>\bin directory and type the following commands:
startServer.bat WebSphere_Portal
startServer.bat Mail_Server_1
IBM AIX, Linux, Solaris
Navigate to the <was_root>/bin directory and type the following commands:
./startServer.sh WebSphere_Portal
./startServer.sh Mail_Server_1
IBM i5/OS
Start the QShell Interpreter by entering STRQSH on an i5/OS command line,
and then type the following command:
/qibm/proddata/webas5/pme/bin/startServer WebSphere_Portal -instance <instance>
where <instance> is the name of the Workplace Collaboration Services instance.
3. Type the following URL in a Web browser to start the IBM WebSphere
Administrative Console:
AIX, Linux, Solaris, Windows
http://<hostname>:9091/admin
where <hostname> is the fully qualified name of the server.
IBM i5/OS
http://<hostname>:<admin_port>/admin
where <hostname> is the fully qualified name of the server and <admin_port> is
the base port number for the instance plus10.
4. Test that you can log in as the IBM WebSphere Application Server
administrator.
5. If you have just enabled security on Node 1 of a Network Deployment, you
should now enable security on the Deployment Manager.
For information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
For information on configuring Secure Sockets Layer (SSL) over LDAP, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related concepts
“Optional post-installation tasks” on page 399
Related tasks
“Enabling LDAP security on the Deployment Manager” on page 101
Connecting to Sun Java System Directory Server
Related reference
Root installation directories
Connecting to Novell eDirectory
Perform the following steps to configure IBM Workplace Collaboration Services to
use Novell eDirectory:
188
Installation and Upgrade Guide
1.
2.
3.
4.
5.
6.
Create required administrative accounts.
Index attributes.
Edit the helper file.
Use the Configuration Wizard to enable LDAP security.
Optional: Configure read-only directory access.
Verify the LDAP configuration.
Related concepts
“Phase 4: Connecting to an LDAP directory server” on page 141
Related tasks
“Connecting to an LDAP directory in a Network Deployment” on page 142
Creating administrative accounts for Novell eDirectory
Create the following required administrative accounts in the LDAP directory before
you enable LDAP security. For instructions, see the Novell eDirectory
documentation. Each account corresponds to properties that you specify in the
helper file and in the wizard.
Related properties in helper file and
wizard
LDAP account
IBM WebSphere Application Server
administrator. This can be the same as the
IBM WebSphere Portal Server administrator.
WasUserid
WebSphere Portal Server administrator.
PortalAdminId
WasPassword
Note: This account must include a value for PortalAdminIdShort
the mail attribute. If the account does not
have a value for the mail attribute, enabling PortalAdminPwd
LDAP security will fail.
Do not use the following characters in the
password (PortalAdminPwd) because they
can cause authentication failures:
!()@#$%
WebSphere Portal Server administrator
PortalAdminGroupId
group. This group must include the name of
PortalAdminGroupIdShort
the WebSphere Portal Server administrator.
The group must define its user and group
members using the members’ distinguished
names.
Name that WebSphere Portal Server and
LDAPAdminUId
IBM WebSphere Member Manager use to
bind to the LDAP directory. The access level LDAPAdminPwd
given this name controls the access that IBM
Workplace Collaboration Services has to the
directory.
Note: Give this account read-only access if
you want to prevent users from using the
Sign-up link to register accounts in the
directory, and from using the Edit My
Profile link to change attributes in the
directory, such as their e-mail addresses.
Name that WebSphere Application Server
uses to bind to the LDAP directory.
LDAPBindID
LDAPBindPassword
Related tasks
Chapter 4 Connecting to an LDAP Directory Server
189
“Indexing attributes for Novell eDirectory”
“Connecting to Novell eDirectory” on page 188
Indexing attributes for Novell eDirectory
You must index specific attributes in the directory. This step is required.
Index the following attributes in user accounts:
v mail
v the additional attribute or attributes specified for the LDAPUserFilter property
in the helper file; for example, uid.
Refer to the Novell eDirectory documentation for instructions on indexing.
Related tasks
“Editing the helper file for Novell eDirectory”
“Connecting to Novell eDirectory” on page 188
Editing the helper file for Novell eDirectory
You use a helper file to aid in enabling LDAP security. You make a copy of the
helper file, then edit the copy, providing values for directory properties that are
appropriate for your LDAP directory environment. When you run the
Configuration Wizard to enable LDAP security, the wizard displays the values you
specified in the helper file, which you can then verify.
Note: Only someone with advanced knowledge of LDAP concepts and
administration who is familiar with your directory environment should edit
the helper file.
1. Make a backup copy of the Novell eDirectory helper file,
<wp_root>\config\helpers\security_edir_server.properties.
2. With a text editor, open the security_edir_server.properties. file, specify values
for properties, and then save and close the file.
v The helper file and the following table provide example values for some
directory properties. Do not assume the example values are correct for your
environment; you must evaluate each property to determine the appropriate
value for your environment.
v Type distinguished names in lowercase characters.
v Ignore any properties in the helper file that are not described in the
following table.
Property
Description
WebSphere Application Server
properties
WasUserid
The distinguished name in the LDAP directory for the
IBM WebSphere Application Server administrator. This
can be the same name as the IBM WebSphere Portal
Server administrator (PortalAdminId).
Example: cn=wasadmin,ou=users,o=acme.com
WasPassword
190
Installation and Upgrade Guide
The password for the WasUserid name. As a security
measure, do not type the password in the helper file.
Type the password when you run the wizard.
Property
Description
WpsHostName
The host name for the WebSphere Portal Server.
Type localhost.
WebSphere Portal Server
configuration properties
PortalAdminId
The distinguished name of the WebSphere Portal
Server administrator in the LDAP directory. This name
must be a member of the WebSphere Portal Server
administrators group defined by the
PortalAdminGroupId property.
Note: This account must include a value for the mail
attribute. If the account does not have a value for the
mail attribute, enabling LDAP security will fail.
Example: cn=portaladmin,ou=users,o=acme.com
PortalAdminIdShort
The short form of the WebSphere Portal Server
administrator name.
Example: portaladmin
PortalAdminPwd
Password for the WebSphere Portal Server
administrator. As a security measure, do not type the
password in the helper file. Type the password when
you run the wizard.
Note: Do not include the following characters in the
password because they can cause authentication
failures:
[email protected]()#$%
PortalAdminGroupId
The distinguished name of the WebSphere Portal
Server administrators group in the LDAP directory to
which the WebSphere Portal Server administrator
belongs. This group must define its user and group
members using the members’ distinguished names.
Example: cn=portaladmins,ou=groups,o=acme.com
PortalAdminGroupIdShort
The short form of the WebSphere Portal Server
administrators group name.
Example: portaladmins
WebSphere Portal Server security
properties
LTPAPassword
The password used to encrypt and decrypt the LTPA
keys. As a security measure, do not type the password
in the helper file. Type the password when you run
the wizard.
LTPATimeout
Time period in minutes at which an LTPA token
expires.
Example: 120
SSOEnabled
Indicates whether single sign-on is enabled (true or
false).
Chapter 4 Connecting to an LDAP Directory Server
191
Property
Description
SSORequiresSSL
Indicates whether single sign-on is enabled only for
HTTPS Secure Socket Layer (SSL) connections.
Type false. If you want to configure SSL, do so only
after you have enabled LDAP security and verified the
LDAP directory configuration.
SSODomainName
The domain name for all single sign-on hosts.
Example: acme.com
Do not type a leading ″.″ For example, type acme.com,
and not .acme.com.
General global security properties
useDomainQualifiedUserNames
Indicates whether to qualify user names with the
security domain within which they reside (true or
false).
The default value (false) is recommended for most
environments.
cacheTimeout
Timeout for the security cache.
The default value (600) is recommended for most
environments.
issuePermissionWarnings
Indicates whether during application deployment and
application start, the security run time emits a
warning if applications are granted any custom
permissions (true or false).
The default value (true) is recommended for most
environments.
activeProtocol
The authentication protocol for RMI/IIOP requests
when security is enabled.
The default value (BOTH) is recommended for most
environments.
activeAuthmechanism
The authentication mechanism when security is
enabled.
The default value (LTPA) is recommended for most
environments.
LDAP properties
LDAPHostName
The host name for your LDAP server.
Example: neldap.acme.com
LDAPPort
The LDAP server port number. Typically you type 389.
Do not type 636, the port typically used for SSL
connections. If you want to configure an SSL port for
LDAP, do so after you have enabled LDAP security
and verified the LDAP directory configuration.
192
Installation and Upgrade Guide
Property
Description
LDAPAdminUId
The distinguished name in the LDAP directory that
WebSphere Portal Server and IBM WebSphere Member
Manager use to bind to the directory. The level of
access given this name determines the level of access
that IBM Workplace Collaboration Services has to the
directory. This name does not have to contain a uid
attribute.
Note: Give this account read-only access to prevent
users from using the Sign-up link to register accounts
in the directory, and from using the Edit My Profile
link to change attributes in the directory, such as their
e-mail addresses.
Example: cn=ldapadmin,ou=users,o=acme.com
LDAPAdminPwd
The password for the name assigned to the
LDAPAdminUId property. As a security measure, do
not type the password in the helper file. Type the
password when you run the wizard.
LDAPServerType
Do not change, leave as NDS.
LDAPBindID
Distinguished name that WebSphere Application
Server uses to bind to the directory.
Example: uid=wpsbind,ou=users,o=acme.com
LDAPBindPassword
The password for the LDAPBindID name. As a
security measure, do not type the password in the
helper file. Type the password when you run the
wizard.
Advanced LDAP properties
LDAPSuffix
The LDAP suffix for your directory server. This
property determines the naming context at which to
begin directory searches for users and groups.
Example: o=acme.com
LdapUserPrefix
The leftmost attribute of user names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPUserSuffix
The naming context at which to begin searches for
user names in the directory.
Example:ou=users
Do not include the LDAPSuffix value as part of this
value. For example, do not type ou=users,o=acme.com
LdapGroupPrefix
The leftmost attribute of group names in the directory.
Type the value in lowercase characters.
Example: cn
LDAPGroupSuffix
The naming context at which to begin searches for
group names in the directory.
Example: ou=groups
Do not include the LDAPSuffix value as part of this
value. For example, do not type
ou=groups,o=acme.com
Chapter 4 Connecting to an LDAP Directory Server
193
Property
Description
LDAPUserObjectClass
The object class used for users.
Example: inetOrgPerson
LDAPGroupObjectClass
The object class used for groups.
Example: groupOfNames
LDAPGroupMember
The attribute used for the members of groups.
Example: member
LDAPUserFilter
The filter used to search for user accounts. The filter
must include the following text:
(&(|(<userprefix>=%v)(mail=%v))(objectclass=
<userobjectclass>))
where <userprefix> is the value specified for the
LDAPUserPrefix property and <userobjectclass> is the
value specified for the LDAPUserObjectClass property.
Example:
(&(|(cn=%v)(mail=%v))(objectclass=inetOrgPerson))
LDAPGroupFilter
The filter used to search for groups accounts. The filter
must include the following text:
(&(<groupprefix>=%v)(objectclass=
<groupobjectclass>))
where <groupprefix> is the value specified for the
LDAPGroupPrefix property and <groupobjectclass> is
the value specified for the LDAPGroupObjectClass
property.
Example: (&(cn=%v)(objectclass=groupOfNames))
LDAPGroupMinimumAttributes
Attributes loaded for group searches and related to
performance. Leave this property blank.
LDAPUserBaseAttributes
Attributes loaded for user login related to
performance. Type givenName,sn,preferredLanguage.
Also type the following values to allow users, for
example calendar users, to set international time and
date preferences in the Edit My Profile page:
,ibm-regionalLocale,ibm-timeZone,
ibm-preferredCalendar,ibm-firstDayOfWeek,
ibm-firstWorkDayOfWeek
LDAPUserMinimumAttributes
Attributes loaded for user searches and related to
performance. Leave this property blank.
LDAPsearchTimeout
Value in seconds for the amount of time the LDAP
server has to respond before canceling a request.
Example: 120
LDAPreuseConnection
194
Installation and Upgrade Guide
Indicates whether LDAP connections are reused (true
or false). If your environment uses a frontend server to
spray requests to multiple backend LDAP directory
servers, type false. If your environment does not use
an intermediate server but instead authenticates
directly with the LDAP directory server, type true.
Property
Description
LDAPIgnoreCase
Indicates whether LDAP searches are case-sensitive
(true or false).
Related tasks
“Enabling LDAP security for Novell eDirectory”
“Connecting to Novell eDirectory” on page 188
Related reference
“Root installation directories” on page 407
Enabling LDAP security for Novell eDirectory
Perform the following steps to disable IBM WebSphere Application Server global
security, and then to enable LDAP security for Novell eDirectory. These steps
assume you are running the Configuration Wizard using the graphical user
interface. If you are using the console interface, to advance in the wizard, type the
number the wizard indicates rather than click Next. Online help is not available in
console mode.
If you have already enabled LDAP security, you can follow these steps to change
LDAP configuration properties. However, you should not change to a different
LDAP directory that is not a replica of the directory currently configured. If you do
so, users’ unique identifiers are lost and users will be unable to authenticate or
access data created previously.
1. Make sure you have made a backup copy of the
security_edir_server.properties helper file, and have edited the helper file to
accommodate your directory environment.
Note: Make sure the account specified for the PortalAdminId property
includes a value for the mail attribute. If the account does not have a
value for the mail attribute, enabling LDAP security will fail.
2. Start your LDAP directory server.
3. Start the Configuration Wizard. Make sure that Cloudscape and server1 are
running, and that WebSphere_Portal and Mail_Server_1 are stopped before
doing so.
For more information, see the chapter ″Installing IBM Workplace
Collaboration Services.″
4. Disable WebSphere Application Server global security:
a. At the Select the configuration task that you want to perform dialog box
in the Configuration Wizard, click Disable security, and then click Next.
b. At the WebSphere Application Server global security is enabled. Enter
the user ID and password to be used for Websphere Application Server
administration dialog box, type the administrator name and password
specified during IBM Workplace Collaboration Services installation, and
then click Next.
Note: If LDAP security is already enabled, and you are preparing to
re-enable LDAP security in order to change the LDAP directory
configuration, type the name of the current WebSphere Application
Server administrator name and password in the LDAP directory
instead.
c. At the Please enter an appropriate properties file location dialog box,
type the path and filename for the wpconfig.properties file, located in the
Chapter 4 Connecting to an LDAP Directory Server
195
<wp_root>/config directory, where <wp_root> is the root WebSphere Portal
Server installation directory. For example, type
/opt/IBM/Workplace/PortalServer/config/wpconfig.properties.
d. Verify that the next dialog box contains the required values indicated in
the following table, then click Next. Do not leave any of the properties
blank.
Property
Action
PortalAdminID
Verify that the value is uid=wpsadmin,o=default organization. Or
if LDAP security is enabled, verify that the value is the
distinguished name of the current WebSphere Portal Server
administrator in the LDAP directory.
PortalAdminIdShort
Verify that the value is wpsadmin. Or if LDAP security is
enabled, verify that the value is the short form of the current
WebSphere Portal Server administrator in the LDAP directory.
PortalAdminPwd
Type the administrator password that you specified during IBM
Workplace Collaboration Services installation. Or if LDAP security
is enabled, type the password for the current Websphere Portal
Server administrator in the LDAP directory.
PortalAdminGroupId
Verify that the value is cn=wpsadmins,o=default organization. Or
if LDAP security is enabled, type the distinguished name of the
current WebSphere Portal Server administrators group.
DbPassword
Accept the default hidden password value.
WmmDbPassword
Accept the default hidden password value.
5.
6.
7.
8.
9.
e. At the The Configuration Wizard is ready to run the following
configuration: Disable security dialog box, click Next to disable security.
See the progress bar and wait for the wizard to finish.
f. At the The following configuration has completed successfully: Disable
security dialog box, click Finish.
Click Run Wizard Again.
At the Select the configuration task that you want to perform dialog box,
click Enable LDAP security, and then click Next.
At the Select the LDAP type to use for authentication dialog box, click the
Novell eDirectory, and then click Next.
At the Please enter an appropriate properties file location dialog box, type
<wp_root>/config/helpers/security_edir_server.properties, and then click
Next.
Advance through the wizard.
v Verify at each stage that the values the wizard reads from the helper file are
correct. Accurate values are essential for proper LDAP directory
configuration.
v Remember to type the required passwords, because you did not type them
in the helper file.
v The wizard may not read the domain name specified for the
SSODomainName property from the helper file. In this case, be sure to type
the SSO domain name again in the wizard.
v If you change a distinguished name, the LdapUserPrefix, or the
LdapGroupPrefix, remember to use lowercase characters.
10. Near the end of the wizard, type values for the following properties, and then
click Next. These properties are not included in the helper file.
196
Installation and Upgrade Guide
Property
Action
WmmDbPassword
Type any text but do not leave the property blank.
DbPassword
Type any text but do not leave the property blank.
LWPDBAdminPassword
Type any text but do not leave the property blank.
11. At the The Configuration Wizard is ready to run the following
configuration: Enable LDAP security dialog box, click Next to run the
wizard. See the progress bar and wait for the wizard to finish.
12. If you see the dialog box that says The following configuration has
completed successfully: Enable LDAP security, click Finish to exit the
wizard, then continue to Step 13. If the wizard finishes with errors, perform
the following steps:
a. Click Finish.
b. Open the configwizard.log and configwizardlog.txt files to help you
troubleshoot errors and determine the correct values:
v <wp_root>/log/configwizard.log
v <wp_root>/log/configwizardlog.txt
Tip: Rename the two log files to reflect the configuration task chosen, so
you can find them easily if you need them in the future.
c. Correct any incorrect values in your helper file.
d. Repeat Step 1 through Step 12.
13. To allow IBM WebSphere Portal Server to follow LDAP referrals when
communicating with a server in front of multiple LDAP directory servers,
complete the following manual steps:
a. With a text editor, open the <wp_root>\shared\app\wmm\wmm.xml file.
b. Add the following line to the <ldapRepository name=″wmmLDAP″> tag,
directly after the ldapPort= line:
java.naming.referral="follow"
c. Save the file.
Related tasks
“Configuring read-only access to Novell eDirectory”
“Editing the helper file for Novell eDirectory” on page 190
“Connecting to Novell eDirectory” on page 188
Related reference
“Root installation directories” on page 407
Configuring read-only access to Novell eDirectory
Perform the following optional steps to configure read-only access to Novell
eDirectory. Read-only access prevents users from using the Sign-up and Edit My
Profile links in the IBM WebSphere Portal Server page to register themselves in the
directory and to change personal attributes in the directory, such as e-mail
addresses.
1. Make sure that the account name you specified for the LDAPAdminUId
property when you enabled LDAP security has read-only access to the
directory.
2. Stop the WebSphere Portal Server.
3. Remove the Sign-up and Edit My Profile links from the WebSphere Portal
Server page:
Chapter 4 Connecting to an LDAP Directory Server
197
a. Change to the <wp_root>\config directory.
b. Type the following command:
Microsoft Windows
WPSconfig action-fixup-signup-link
IBM AIX, Linux, Solaris, IBM i5/OS
./WPSconfig.sh action-fixup-signup-link
Related tasks
“Verifying the Novell eDirectory configuration”
“Connecting to Novell eDirectory” on page 188
Related reference
“Root installation directories” on page 407
Verifying the Novell eDirectory configuration
Perform the following steps to verify the Novell eDirectory configuration.
1. Stop and restart the database server.
2. Start IBM WebSphere Portal Server and IBM Workplace Collaboration Services
servers:
Microsoft Windows
Navigate to the <was_root>\bin directory and type the following commands:
startServer.bat WebSphere_Portal
startServer.bat Mail_Server_1
IBM AIX, Linux, Solaris
Navigate to the <was_root>/bin directory and type the following commands:
./startServer.sh WebSphere_Portal
./startServer.sh Mail_Server_1
IBM i5/OS
Start the QShell Interpreter by entering STRQSH on an i5/OS command line,
and the type the following command:
/qibm/proddata/webas5/pme/bin/startServer WebSphere_Portal -instance <instance>
where <instance> is the name of the Workplace Collaboration Services instance.
3. Type the following URL in a Web browser to start the IBM WebSphere
Administrative Console:
AIX, Linux, Solaris, Windows
http://<hostname>:9091/admin
where <hostname> is the fully qualified name of the server.
IBM i5/OS
http://<hostname>:<admin_port>/admin
where <hostname> is the fully qualified name of the server and <admin_port> is
the base port number for the instance plus10.
4. Test that you can log in as the IBM WebSphere Application Server
administrator.
5. If you have just enabled security on Node 1 of a Network Deployment, you
should now enable security on the Deployment Manager.
For information, see the chapter ″Installing IBM Workplace Collaboration
Services.″
198
Installation and Upgrade Guide
For information on configuring Secure Sockets Layer (SSL) over LDAP, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related concepts
“Optional post-installation tasks” on page 399
Related tasks
“Enabling LDAP security on the Deployment Manager” on page 101
“Connecting to Novell eDirectory” on page 188
Related reference
“Root installation directories” on page 407
Chapter 4 Connecting to an LDAP Directory Server
199
200
Installation and Upgrade Guide
Chapter 5 Connecting to a DBMS Server
This chapter provides information about setting up IBM Workplace Collaboration
Services to work with an external DBMS server.
Phase 5: Connecting to a DBMS server
If you do not use the IBM Cloudscape server to host your IBM Workplace
Collaboration Services data, you must connect all Workplace servers to an external
DBMS server. If you will be using the default Cloudscape DBMS server, skip this
entire section.
Connecting Workplace Collaboration Services to an external DBMS server involves
several tasks, which must be performed in the sequence shown:
1. Install the DBMS server software as described in Phase 2, ″Setting up the
environment.″
2. Create a database container for use with Workplace Collaboration Services as
described in the topic, ″Creating the Workplace Collaboration Services
database.″
3. Use the Configuration Wizard to establish database schemas and transfer data
from Cloudscape to the new database as described in the topic, ″Transferring
data to another DBMS.″
4. If you are configuring a Network Deployment, you will additionally need to
connect nodes within the deployment to the external DBMS server as described
in the topic, ″Connecting Network Deployment nodes to a remote database.″
Attention: If you want to change the context root of your Workplace Collaboration
Services installation, you must do that before you transfer data from
Cloudscape to another DBMS product.
“Changing the installed context root” on page 404
About the Workplace Collaboration Services database
IBM Workplace Collaboration Services uses a single database container.
By default, the database is created on the Workplace server, using the IBM
Cloudscape DBMS; however, you may choose to transfer the data to a more robust
DBMS product. The new database is created and configured with the
Configuration Wizard; you also use the wizard to transfer data from Cloudscape to
the new database.
For IBM DB2 Universal Database and Microsoft SQL Server, the data for Workplace
Collaboration Services and IBM WebSphere Portal are combined in a single
database, referred to in this documentation as wps50.
For Oracle, the database is created during DBMS software installation, and
schemas for both WebSphere Portal and Workplace Collaboration Services are
added to a single instance of Oracle. In Oracle, the default instance name is ORCL,
but this name is configurable; for consistency with the other supported DBMS
product, examples in the installation documentation use wps50 as the instance
name.
© Copyright IBM Corp. 2002, 2005
201
The Workplace Collaboration Services database hosts multiple schemas, described
in the following table.
Schema Name
Description
<database_owner>
This WebSphere Portal schema stores
configuration information for pages, portlets,
users and other portal administrative objects.
Instant messaging contact lists are stored in
this schema. This schema also stores
WebSphere Portal content for publishing,
documents created by IBM Workplace
Documents, and other documents and
discussions created by Workplace
Collaboration Services capabilities.
This schema is named using the uppercase
version of the database instance owner’s
user name.
FEEDBACK
This schema contains the information logged
by WebSphere Portal for generating reports
for analysis of site activity including
information about campaigns and
personalized resources.
LWPCOMM
This schema contains administrative data,
mail services data, and team collaboration
data. The schema is also used as the
messaging archive schema to track archived
mail messages. The schema contains links to
archived content that is stored on the file
system.
LWPLMS
This schema contains the IBM Workplace
Collaborative Learning information,
including the learning course catalog,
enrollments, and consolidated progress
records.
LWPLDS
This Workplace Collaborative Learning
delivery schema stores progress data
recorded from student actions. This data is
subsequently transmitted to the Learning
Management application and database.
EJB
This schema is used for business rule beans.
PZNADMIN
This schema used for personalization data.
If you plan to transfer data from Cloudscape to another DBMS product, begin by
reading the topic, ″Creating the Workplace Collaboration Services database,″ and
deciding whether you need to create the database yourself or can have it created
for you during the Database Setup task.
Creating the Workplace Collaboration Services database
If you want to transfer the IBMWorkplace Collaboration Services data from its
default database (stored in IBM Cloudspace) to another DBMS product, you must
create a database container. How and where you create the database depends on
several factors, including:
v The DBMS product hosting the databases
202
Installation and Upgrade Guide
v Whether you want to create the database yourself or have the Configuration
Wizard create it for you
v Whether you have created databases for a previous release of Workplace
Collaboration Services
If you use IBM DB2 Universal Database as your DBMS product, you can let the
Configuration Wizard create and configure a local database (hosted on the
Workplace server) for you by setting the run.db2.create option to True during the
Database Setup task. If you want to use a remote database (hosted on a separate
computer), you must create it yourself on the DBMS server, and then run the
Configuration Wizard on the Workplace server to configure it.
If you use Oracle as your DBMS product, the database is created automatically as
part of the server installation. The Configuration Wizard then creates the schemas
needed for hosting Workplace Collaboration Services data.
If you use Microsoft SQL Server as your DBMS product, you can let the
Configuration Wizard create and configure either a local (hosted on the Workplace
server) database or a remote (hosted on a separate computer) database for you by
setting the ″Run database creation″ option to True during the Database Setup task.
In both cases, the Configuration Wizard creates both the database container and
the schemas needed for hosting Workplace Collaboration Services data.
Unless you have a specific reason for creating the database yourself, the process is
most straightforward when you allow the Configuration Wizard to create it for
you.
If you decide to create the database yourself, follow the database-creation
instructions in the topic that corresponds to the DBMS product you will be using.
If you want the Configuration Wizard to create the database for you, skip this
section and proceed directly to the topic, ″Transferring data fromCloudscape to
another DBMS.″
Related tasks
“Creating the DB2 Universal Database”
“Creating the Oracle database”
“Creating the database in SQL Server” on page 205
Creating the DB2 Universal Database
Create a database container in IBM DB2 Universal Database for storing IBM
Workplace Collaboration Services data.
With DB2, the database is always created during the ″Setting up the database″ task.
If you will use a local database (stored on the same computer), you can choose to
have it created for you. If you will use a remote database (stored on another
computer), you will create the database yourself (instructions are provided at the
point in the process where you actually create the database).
Proceed to the topic, ″Transferring data to another DBMS.″
Creating the Oracle database
Create a database container in Oracle for storing IBM Workplace Collaboration
Services data.
Chapter 5 Connecting to a DBMS Server
203
Before creating the new database instance, update your Oracle 9i installation with
patch 9.2.0.4.0.
When you install the Oracle server software, a single database instance is created.
If you will be using that database instance with Workplace Collaboration Services,
skip the rest of this topic and proceed to the topic, ″Adding WebSphere Portal
users to the Oracle database.″
Note: It is recommended that you create only one Oracle instance on a computer.
One database instance can host schemas used with multiple applications,
although it can host only one set of Workplace Collaboration Services
schemas. If you must create multiple database instances on one computer, be
sure to set buffer sizes to values that do not cause memory swapping. In
addition, tablespace location names must either be unique, or stored in
different locations to prevent ambiguity.
Create the database instance on the Oracle server by following these instructions.
1. Log in to the Oracle server as a user with administrative privileges.
2. Start the Oracle Database Configuration Assistant.
3. Create a new database called wps50, using the Unicode and UTF-8 options.
This database instance will contain the schemas used by Workplace
Collaboration Services, and must be created using the UTF-8 character set to
ensure accessibility in all supported languages.
4. Create passwords for the SYS and SYSTEM accounts. You will use the SYSTEM
account and password later, during database configuration.
5. Edit the Oracle\Ora9\network\admin\tnsnames.ora file, and set the
SERVICE_NAME parameter to wps50 to match the database instance name
created in Step 4.
In the example that follows, the SERVICE_NAME (shown italicized) matches
the ″tns″ entry in which it is included; this match between names is required
for Workplace Collaboration Services. The examples in this documentation use
wps50 as the database name (and thus, the service name).
wps50 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = workplaceserver.your_company.com)
(PORT = 1521)
)
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = wps50)
)
)
The PORT value indicates the port that the Oracle server and client computers
use for communicating (they must use the same port).
6. Save and close the tnsnames.ora file.
204
Installation and Upgrade Guide
After the Oracle database has been created, proceed to the topic ″Adding
WebSphere Portal users to the Oracle database. ″
Adding WebSphere Portal users to the Oracle database:
To ensure that the IBM WebSphere Portal has appropriate access to the Oracle
database, add the associated users now.
Complete this task on the Oracle database server.
1. Connect to the Oracle SQL Plus utility.
2. Run the following commands, substituting the appropriate passwords where
needed.
create user WPSDBUSR identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user WMMDBUSR identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to WPSDBUSR;
grant connect, resource to WMMDBUSR;
create user PZNADMIN identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user EJB identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user WCMDBADM identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to PZNADMIN;
grant connect, resource to EJB;
grant connect, resource to WCMDBADM;
create user FEEDBACK identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to FEEDBACK;
3. Exit the SQL Plus utility.
After you have added the WebSphere Portal users to the Oracle database, proceed
to the topic, ″Setting up the Oracle database.″
Creating the database in SQL Server
Create a database container in Microsoft SQL Server for storing IBM Workplace
Collaboration Services data.
Generally, it is recommended that you allow the Configuration Wizard to create
the database for you during the Database Setup task. The Configuration Wizard
can create either a local database (stored on the same computer) or a remote
database (stored on another computer). If you want the Configuration Wizard to
create the database for you, skip this task and proceed to the topic, ″ Transferring
data to another DBMS.″
If there is a reason why you need to create the database yourself, use the
instructions that follow.
Create the database directly on the computer hosting the Microsoft SQL Server
DBMS software, using the SQL Server Enterprise Manager.
Chapter 5 Connecting to a DBMS Server
205
Note: To prevent schema collisions, it is recommended that you create a separate
database for use with Workplace Collaboration Services rather than share a
database with another product, although you can share the SQL Server
instance itself.
1. Start the SQL Server Enterprise Manager.
2. In the main window, expand the nodes until you see Databases → New
Database.
3. Type a name for the new database. The examples in this documentation use
wps50 as the database name.
4. Set the Collation Name according to your environment, making sure that it is
case sensitive. For example, on an English system, use the collation
SQL_Latin1_General_CP1_CS_AS (instead of SQL_Latin1_General_CP1_CI_AS
or Default).
Note: A case-sensitive collation can be identified by the _CS in the collation
name; a case-insensitive collation uses _CI instead.
5. Click OK to save the new database.
6. Leave the Enterprise Manager open for the next task.
Proceed to the topic, ″Enabling authentication and distributed transactions in SQL
Server.″
Transferring data to another DBMS
By default, IBM Workplace Collaboration Services is installed with some
predefined data stored in the IBM Cloudscape database management system,
which is hosted on the Workplace server. Data for IBM WebSphere Portal (installed
along with Workplace Collaboration Services) is also stored in Cloudscape.
Cloudscape is sufficient for use in demo installations; however, for a production
environment, it is recommended that you use a more robust DBMS product for
storing Workplace Collaboration Services data. See the ″Requirements″ topics for a
list of supported DBMS products.
Complete the database transfer tasks in the following sequence:
Single-server deployment or Node 1 in a Network Deployment
1. IBM Workplace Setup Database (creates the database and establishes the
necessary schemas).
2. Transfer data to another database (transfers WebSphere Portal Server data to
the new DBMS).
3. IBM Workplace Database Transfer (transfers Workplace Collaboration Services
data to the new DBMS).
Nodes 2+ in a Network Deployment
1. Connect to a Database (connects the new node to the existing database).
2. IBM Workplace Connection to Database (transfers default data from the new
node to the database).
Note: The database transfer procedure can migrate user-created data as well as the
data created during product installation; however, migrating additional data
takes longer and leaves the process more prone to errors. For best results,
complete the database transfer before users begin working with Workplace
Collaboration Services.
206
Installation and Upgrade Guide
To transfer data from Cloudscape to another database product, proceed to one of
the following topics:
v Transferring data to DB2 Universal Database
v Transferring data to Oracle
v Transferring data to SQL Server
Related concepts
Requirements for AIX, Linux, Solaris, and Windows
Requirements for i5/OS
“Connecting Network Deployment nodes to a remote database” on page 245
Transferring data to DB2 Universal Database
By default, IBM WebSphere Portal and IBM Workplace Collaboration Services
install with some predefined data stored in the IBM Cloudscape database
management system, hosted on the Workplace server. Cloudscape is sufficiently
robust for use in demo installations; however, for a production environment, it is
recommended that you transfer data to a more robust DBMS product.
Transferring data to IBM DB2 Universal Database involves the following tasks,
which must be completed in the sequence shown:
1.
2.
3.
4.
Create the DB2 Universal Database and set up its schemas.
Transfer WebSphere Portal data to DB2 Universal Database.
Transfer Workplace Collaboration Services data to DB2 Universal Database.
Update the DB2 Universal Database settings.
Begin the process by setting up the DB2 database schemas as described in the
topic, ″Setting up the DB2 Universal Database.″
Setting up the DB2 Universal Database:
Perform this task on the computer hosting IBM Workplace Collaboration Services.
1. (RedHat 3.0 Linux only) Locate the etc/ant.conf file and rename it to
ant.conf.BAK. The database transfer task will install a file with the same
name, so renaming your original file will prevent it from being overwritten in
case you want to use it at a later date.
2. Start the Configuration Wizard as described in the topic, ″Starting the
Configuration Wizard.″
3. In the Select the configuration task that you want to perform dialog box,
click IBM Workplace Setup Database, and then click Next.
4. In the Select the database type... dialog box, select IBM DB2 Universal
Database, and then click Next.
5. In the LWPDBDriver: dialog box, type the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for each field in the dialog box, assuming a Windows
server.
File
Example Path
LWPDBDriver
COM.ibm.db2.jdbc.app.DB2Driver
LWPDbLibrary
D:/IBM/SQLLIB/java/db2java.zip
6. In the LWPDBName: dialog box, fill in information about the new database,
including its associated user names and passwords, and then click Next. The
Chapter 5 Connecting to a DBMS Server
207
following table includes examples of appropriate values for each field in the
dialog box, assuming a Windows server.
Field
Example Values
Comments
LWPDBNAME
wps50
If this is preset to WRKPLC,
change it to wps50.
LWPDBUrl
jdbc:db2:wps50
LWPDBAdminUser
db2admin
This name is case sensitive.
LWPDBAdminPassword
<db2admin_password>
Always type the password
yourself as the default value
may not be correct.
LWPDBAppUser
db2admin
Application User’s name.
LWPDBAppPassword
<db2admin_password>
Application User’s
password. Always type the
password yourself as the
default value may not be
correct.
7. In the You will be able to choose to create a local DB2 database dialog box,
fill in the fields and then click Next. The following table includes examples of
appropriate values for each field in the dialog box, assuming a Windows
server.
Field
Example Value
Comment
Run database
creation
False
If you want the database created locally, set
this value to True. Use False for a remote
database or for a local database that already
exists. Always set this value to False if your
Workplace server is running on an AIX, Linux,
or Solaris platform.
LWPDBHome
D:/IBM/SQLLIB
Tablespace is created in the default directory
for DB2. You can change this (for example, to
improve performance) by specifying a different
location here; for example:
AIX, Linux, Solaris
/data1/lwpdata/LWPCOMMREG
Windows
F:/lwpdata/LWPCOMMREG
8. In the IBM Workplace common settings dialog box, fill in the schema and
tablespace information for the LWPCOMM schema, and then click Next. The
following table includes examples of appropriate values for each field in the
dialog box, assuming a Windows server.
208
Field
Example Value
Comment
LWPComSchema
LWPCOMM
The user name of the Com (Common)
schema’s owner.
db.lwp.comm.data
.tablespace.name
LWPCOMMREG
The data tablespace name for the Com
schema
db.lwp.comm.data
.container.list
LWPCOMMREG
The data tablespace location for the Com
schema.
Installation and Upgrade Guide
9. In the Learning Management Settings dialog box, fill in the schema and
tablespace information for the LWPLMS schema, and then click Next. The
following table includes examples of appropriate values for each field in the
dialog box, assuming a Windows server.
Field
Example Value
Comment
LWPLMSSchema
LWPLMS
The user name of the LMS (Learning)
schema’s owner.
db.lwp.lms.data
.tablespace.name
LWPLMSDATA
The data tablespace name for the LMS
schema
db.lwp.lms.data
.container.list
LWPLMSDATA
The data tablespace location for the LMS
schema.
10. In the Learning Delivery Settings dialog box, fill in the schema and
tablespace information for the LWPLDS schema, and then click Next. The
following table includes examples of appropriate values for each field in the
dialog box, assuming a Windows server.
Field
Example Value
Comment
LWPLDSSchema
LWPLDS
The user name of the LDS (Learning
Delivery) schema’s owner.
db.lwp.lds.data
.tablespace.name
LWPLDSDATA
The data tablespace name for the LDS
schema.
db.lwp.lds.data
.container.list
LWPLDSDATA
The data tablespace location for the
LDS schema.
11. In the Messaging Settings dialog box, fill in the schema and tablespace
information for the LWPMSG schema, and then click Next. The following table
includes examples of appropriate values for each field in the dialog box,
assuming a Windows server.
Field
Example Value
Comment
LWPMsgSchema
LWPMSG
The user name of the Msg (Messaging)
schema’s owner.
db.num.partitions
3
The number of partitions to create within the
Msg schema.
db.lwp.msg.data
.tablespace.name
LWPMSGDATA
The data tablespace name for the Msg schema
db.lwp.msg.data
.container.list
LWPMSGDATA
The data tablespace location for the Msg
schema.
db.lwp.msg.ptn
.tablespace.name
LWPMSGPTN
The tablespace partition name base for the Msg
schema.
db.lwp.msg.ptn
.container.list
LWPMSGPTN
The tablespace partition location base for the
Msg schema.
db.lwp.msg.mta
.tablespace.name
LWPMSGMTA
The MTA tablespace name for the Msg schema.
db.lwp.msg.mta
.container.list
LWPMSGMTA
The MTA tablespace location for the Msg
schema
db.lwp.msg.file
.tablespace.name
LWPMSGFILE
The file tablespace name for the Msg schema
db.lwp.msg.file
.container.list
LWPMSGFILE
The file tablespace location for the Msg
schema.
Chapter 5 Connecting to a DBMS Server
209
12. In the Messaging Archive Settings dialog box, fill in the schema and
tablespace information for the LWPARC schema, and then click Next. The
following table includes examples of appropriate values for each field in the
dialog box, assuming a Windows server.
Field
Example Value
Comment
LWPArcSchema
LWPARC
The password for the Arc schema
owner account. Always type the
password yourself as the default value
may not be correct.
db.lwp.arc.data
.tablespace.name
LWPARCDATA
The data tablespace name for the Arc
schema.
db.lwp.arc.data
.container.list
LWPARCDATA
The data tablespace location for the Arc
schema.
13. If you are using a local database (hosted directly on the Workplace server) on
a Microsoft Windows operating system, skip to Step 14. If you are using a
remote database (hosted on a separate computer) on any operating system, or
are using a local database on an IBM AIX, Linux, or Sun Solaris operating
system, proceed with Step 13.
14. Perform the following steps to create the DB2 database on the AIX, Linux,
Solaris, or remote Windows server:
a. Leave the Configuration Wizard open, and open a command prompt
window.
b. Transfer the following files from
$WCS_HOME/config/database/work/common.db/DB2 to a temporary
directory on the database server:
v createDb.run
v configureDb.run
c. On the remote DB2 server, log on with your DB2 administrator account
and set up the DB2 environment.
d. Navigate to the temporary directory where you copied the files in substep
b, and then run the following commands to create the database:
> db2 -tvf createDb.run
> db2 -tvf configureDb.run
Note: To prevent schema collisions, it is recommended that you create a
separate database for use with Workplace Collaboration Services
rather than share a database with another product, although you
can share the DB2 instance itself.
e. Return to the Workplace server and catalog the remote database, using the
same alias as the database name; for example:
catalog tcpip node <node_name> remote <server_dns_name> server <server_port>
catalog database wps50 as wps50 at node <node_name>
where:
v node_name is any eight-character name you want to assign to the node,
as in myDB2svr.
v server_dns_name is the fully qualified domain name of the remote
database server, as in db2server.acme.com.
v server_port is the port on which DB2 is installed; this is normally port
50000.
210
Installation and Upgrade Guide
The new database is ready to be configured in Step 16.
15. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database configuration by clickingNext. If you are using a local
database on a Windows operating system and set Run database creation to
True in Step 6, the database is created for you during this step.
16. Review the logs from the database configuration to ensure all is well before
proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
Note: If you have successfully completed a database transfer and you are
running it again, the database schema are already in place and are not
affected by the Database Setup task. The logs will note warnings to this
effect.
17. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
After you have set up the DB2 Universal Database schemas, proceed to the topic,
″Transferring WebSphere Portal data to DB2 Universal Database.″
Transferring WebSphere Portal data to DB2 Universal Database:
Both the IBM Cloudscape server and the IBM DB2 Universal Database server must
to be running to support the data transfer.
Perform this task on the computer hosting Workplace Collaboration Services.
1. Start the Cloudscape Network Server, start the WebSphere Application Server,
and stop the WebSphere Portal server, by running the following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Start the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./startNetworkServer.sh
Microsoft Windows
startNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh server1
Windows
startServer.bat server1
f. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
Chapter 5 Connecting to a DBMS Server
211
2.
3.
4.
5.
6.
g. Close the command prompt window and return to the Configuration
Wizard.
In the Select the configuration task that you want to perform dialog box,
click Transfer Data to Another Database, and then click Next.
If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
In the Select the database type... dialog box, select IBM DB2 Universal
Database, and then click Next.
In the Please enter an appropriate properties file location... dialog box,
browse to or type the path to the DB2 transfer helper file, and then click Next.
This file is usually stored in the following location:
<wp_root>\config\helpers\transfer_db2.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, c:\WebSphere\PortalServer.
7. In the DbDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values for a Windows
server.
File
Example path
DBDriver
COM.ibm.db2.jdbc.app.DB2Driver
DBDriverDs
COM.ibm.db2.jdbc
.DB2XADataSource
DBLibrary
D:\IBM\SQLLIB\java
\db2java.zip
Comments
For Windows, use a single
backslash between directories; use
a single forward slash for AIX,
Linux, or Solaris.
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpsDbName
wps50
For a remote database, use the
name of the alias you used
when cataloging the database.
DbUser
db2admin
This value is case sensitive.
DbPassword
<db2admin_password>
Always type the password
yourself as the default value
may not be correct.
DbUrl
jdbc:db2:wps50
WpsDbNode
wpsNode
For a remote database, use the
name of the node you
cataloged after creating the
database.
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
212
Installation and Upgrade Guide
Field
Example Value
Comments
WmmDbName
wps50
For a remote database, use the
name of the alias you used
when cataloging the database.
WmmDbUser
db2admin
This value is case sensitive.
WmmDbPassword
<db2admin_password>
Always type the password
yourself as the default value
may not be correct.
WmmDbUrl
jdbc:db2:wps50
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpcpDb
Name
wps50
For a remote database, use the name
of the alias you used when
cataloging the database.
WpcpDbUser db2admin
This value is case sensitive.
WpcpDb
Password
<db2admin_password>
Always type the password yourself
as the default value may not be
correct.
WpcpDbUrl
jdbc:db2:wps50
WpcpXDb
Name
If this property appears, leave the
value alone.
WpcpDb
Node
If this property appears, use the
following value: wcmNode
For a remote database, use the name
of the node you cataloged after
creating the database.
Wpcp
ResourceUrl
D:\WebSphere\PortalServer\wpcp
\v5.0\runtime\lib
For Windows, use a single backslash
between directories; use a single
forward slash for AIX, Linux, or
Solaris.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values for a Windows server.
Field
Example Value
Comments
FeedbackDbName wps50
FeedbackDbUser
db2admin
This value is case sensitive.
FeedbackDb
Password
<db2admin_password>
Always type the password yourself
as the default value may not be
correct.
FeedbackDbUrl
jdbc:db2:wps50
12. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
13. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Chapter 5 Connecting to a DBMS Server
213
Tip: Review the logs from the database configuration to ensure all is well
before proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
After you have successfully transferred the WebSphere Portal data to DB2
Universal Database, proceed to the topic, ″Transferring Workplace Collaboration
Services data to DB2 Universal Database.″
Transferring Workplace Collaboration Services data to DB2 Universal Database:
Perform this task on the computer hosting IBM Workplace Collaboration Services.
1. Stop the IBM Cloudscape Network Server, the IBM WebSphere Portal Server,
and the IBM WebSphere Application Server by running the following
commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./stopNetworkServer.sh
Microsoft Windows
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./stopServer.sh server1
Windows
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
2. In the Select the configuration task that you want to perform dialog box, click
IBM Workplace Database Transfer, and then click Next.
3. In the Select the database type dialog box, select IBM DB2 Universal
Database, and then click Next.
4. In the LWPDriver: dialog box, enter the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for a Microsoft Windows server.
214
Installation and Upgrade Guide
File
Example Path
LWPDBDriver
COM.ibm.db2.jdbc
.app.DB2Driver
LWPDbLibrary
D:\IBM\SQLLIB\java
\db2java.zip
Comments
For Windows, use a single backslash
between directories; use a single forward
slash for IBM AIX, Linux, or Sun Solaris.
5. In the LWPDBNAME: dialog box, enter information about the new database
and associated user names and passwords, click Debug Mode in case errors
occur during the data transfer, and then click Next. The following table
includes examples of appropriate values for a Windows server.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:db2:wps50
LWPDBAdminUser
db2admin
This value is case sensitive.
LWPDBAdminPassword
<db2admin_password>
Always type the password
yourself as the default value
may not be correct.
LWPDBAppUser
db2admin
Application User’s name.
This value is case sensitive.
LWPDBAppPassword
<db2admin_password>
Application User’s
password. Always type the
password yourself as the
default value may not be
correct.
BackEndId
DB2UDBNT_V8_1
6. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
7. Click Finish to close the Configuration Wizard.
8. Review the logs from the data transfer operation to ensure all is well before
proceeding to the next step. These logs are stored in the
\WebSphere\PortalServer\log directory.
9. Start WebSphere Portal Server and Workplace Collaboration Services by
running the following commands.
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start WebSphere Portal Server with the following case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
c. Start Workplace Collaboration Services with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh Mail_Server_1
Windows
startServer.bat Mail_Server_1
Chapter 5 Connecting to a DBMS Server
215
d. Close the command prompt window.
Note: If your database transfer was successful, all passwords are automatically
deleted from properties and helper files, If you need to re-run the data
transfer in the future, you must first run the Database Setup again and
allow it to populate files with passwords before you run the data transfer.
After you have successfully transferred Workplace Collaboration Services data to
the DB2 database, proceed to the topic, ″Updating the DB2 Universal Database
settings.″
Updating the DB2 Universal Database settings:
Update the IBM DB2 Universal Database settings to establish the configuration
settings for IBM Workplace Collaboration Services.
Run the following commands on either the DB2 server or any DB2 client while
logged in as a DB2 administrator:
db2
connect to wps50 user <db2_admin> using <password>
reorgchk update statistics on table all
terminate
db2rbind <database_name> -l db2rbind.out -u <db2_admin> -p <password>
After you have finished transferring data from Cloudscape to DB2, proceed to
Phase 6, ″Connecting to an external HTTP server.″
Transferring data to DB2 Universal Database for iSeries
Follow the instructions in this section to transfer data from IBM Cloudscape to
IBM DB2 Universal Database for iSeries using the Configuration Wizard. Do not
perform these steps if you are using the Create IBM Workplace Collaboration
Services wizard to configure Workplace Collaboration Services. The Create IBM
Workplace Collaboration Services wizard performs these steps automatically.
Note that the steps for transferring data to DB2 for iSeries are different than the
steps for transferring data to DB2 on other platforms.
For instructions on transferring data to DB2 on other platforms, see the topic
″Transferring data from Cloudscape to IBM DB2 Universal Database.″
Before transferring data, you will need to have a database administrator profile,
referred to as db2admin throughout the IBM Workplace Collaboration Services
help topics. Because you cannot change the Workplace Collaboration Services
database administrator once your environment has been configured, it is
recommended that you create a new profile for this purpose rather than use an
existing profile associated with a specific user. The database administrator profile
should have the following authorities:
v *USER authority
v Maximum Storage of *NOMAX
Note: To change this value, enter the following on an i5/OS command line:
CHGUSRPRF USRPRF(DB2ADMIN) MAXSTG(*NOMAX)
where DB2ADMIN is the database administrator profile.
216
Installation and Upgrade Guide
To transfer data from Cloudscape to DB2 for iSeries, follow the instructions for
each of the following tasks:
v Set up the DB2 Universal Database for iSeries database schemas.
v Transfer WebSphere Portal data to DB2 Universal Database for iSeries.
v Transfer IBM Workplace Collaboration Services data to DB2 Universal Database
for iSeries.
Related tasks
Transferring data from Cloudscape to DB2 Universal Database
Setting up the DB2 Universal Database for iSeries schemas:
Use the Configuration Wizard to create the schemas needed for the IBM
WebSphere Portal and IBM Workplace Collaboration Services databases.
Note: The native JDBC driver values are specified by default in the Configuration
Wizard. Use the native JDBC driver if Workplace Collaboration Services is
on the same system as the database files. Use the IBM Toolbox JDBC driver
if Workplace Collaboration Services is on a different system than the
database files. Note that the driver you use should be the same for all
database transfer tasks.
1. Start the Configuration Wizard as described in the topic, ″Starting the
Configuration Wizard.″
2. At the Select the configuration task that you want to perform dialog box,
click IBM Workplace Setup Database, and then click Next.
3. If global security is enabled, you will be prompted to enter an IBM
WebSphere Application Server administrative user name and password in the
WebSphere Application Server global security is enabled... dialog box. Type
the user name and password in the appropriate fields, and then click Next.
4. If you transferred your LDAP directory from Cloudscape to another product,
you will be prompted to authenticate against your LDAP directory in the
Enter the LDAPAdminUID and password dialog box. Type the LDAP
administrator account’s user name and password in the appropriate fields,
and then click Next.
5. At the Select the database type... dialog box, select IBM DB2 for iSeries, and
then click Next.
6. At the LWPDBDriver: ... dialog box, type the appropriate paths to the relevant
database files, and then click Next. The following table includes the
appropriate values for each field in the dialog box.
File
Path
LWPDBDriver
Native JDBC:
com.ibm.db2.jdbc.app.DB2Driver
Toolbox JDBC driver:
com.ibm.as400.access.AS400JDBCDriver
Chapter 5 Connecting to a DBMS Server
217
File
Path
LWPDbLibrary
Native JDBC:
/QIBM/ProdData/Java400/ext/db2_classes.jar
Toolbox JDBC driver:
/QIBM/UserData/WebAS5/Base/
instance/PortalServer/shared/
app/jt400.jar
7. At the LWPDBUrl: ... dialog box, fill in information about the new database,
including its associated user names and passwords, and then click Next. The
following table includes appropriate values for each field in the dialog box.
Field
Value
LWPDBUrl
Native JDBC:
jdbc:db2:*LOCAL
Toolbox JDBC driver:
jdbc:as400:hostname
LWPDBAdminUser
<db2admin>
LWPDBAdminPasswor
<db2admin_password>
LWPDBAppUser
<user_profile>
LWPDBAppPassword
<user_profile_password>
8. On the LWPDBSuffix... dialog box, enter a unique suffix of up to 4 characters
to add to the IBM Workplace Collaboration Services schema name and then
click Next.
The following schemas will be created, where <XXXX> is the specified suffix:
v LWPMSG<XXXX>
v LWPLMS<XXXX>
v LWPLDS<XXXX>
v LWPCOM<XXXX>
v LWPARC<XXXX>
Note: You can ensure the schemas being created have unique names by
viewing the existing Workplace Collaboration Services libraries. To view
existing libraries, enter the following on an i5/OS command line:
WRKOBJ OBJ(*ALL/LWP*) OBJTYPE(*LIB)
9. At the IBM Workplace Setup database dialog box, select Do you wish the
setup wizard to run these scripts now?, then start the database configuration
by clicking Next.
10. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Tip: Review the logs from the database configuration (configwizard.log and
configwizardlog.txt) to ensure all is well before proceeding to the next
task. These logs are stored in the <wp_root> /log directory, where
<wp_root> is the root WebSphere Portal directory.
218
Installation and Upgrade Guide
After you have set up the DB2 database schemas, proceed to the topic,
″Transferring WebSphere Portal data to IBM DB2 Universal Database for iSeries.″
Related concepts
Transferring data from Cloudscape to IBM DB2 Universal Database for iSeries
Related tasks
Running the Configuration Wizard after installation
Transferring WebSphere Portal data to DB2 Universal Database for iSeries:
Use the Configuration Wizard to transfer IBM WebSphere Portal data from the
default IBM Cloudscape database to IBM DB2 Universal Database for iSeries.
This process creates one or more WebSphere Portal schemas for use with
Workplace Collaboration Services. To ensure that the wizard completes
successfully, make sure any schema names you specify in the Configuration
Wizard do not already exist on the system. For convenience, it is recommended
that you use the same schema name for all database schema fields (WpsDBSchema,
WmmDbSchema, WpcpDbSchema, and FeedbackSchema). You may wish to make
a note of this schema name for future reference.
In addition, it is recommended that you specify a single user profile for all
database user fields. Any database users specified must already exist on the system
at the time you run the Configuration Wizard.
Note: The native JDBC driver values are specified by default in the Configuration
Wizard. Use the native JDBC driver if Workplace Collaboration Services is
on the same system as the database files. Use the IBM Toolbox JDBC driver
if Workplace Collaboration Services is on a different system than the
database files. Note that the driver you use should be the same for all
database transfer tasks.
The Cloudscape server and the database host system must be running to support
the data transfer.
1. Stop the WebSphere Portal server by running the following commands.
a. Leave the Configuration Wizard running, and start the QShell Interpreter
by entering the following on an i5/OS command line.
STRQSH
b. Change to the <wp_root>/rootscripts directory by entering the following:
cd wp_root/rootscripts
where <wp_root> is the root directory for WebSphere Portal.
c. Stop WebSphere Portal and the Mail Server by entering one of the
following commands:
Security configured:
stopWorkplaceServices.sh -username <was_user_name> password <password>
Security not configured:
stopWorkplaceServices.sh
d. If security is configured, start the WebSphere Application Server by
entering the following command:
was_root/bin/startServer -instance instance server1
where was_root is the WebSphere Application Server root directory and
instance is the name of your Workplace Collaboration Services instance.
Chapter 5 Connecting to a DBMS Server
219
e. Change to the <wp_root>/rootscripts/subtasks directory by entering the
following:
cd wp_root/rootscripts/subtasks
f. Start the Cloudscape Network Server by entering the following:
startNetworkServer.sh
g. Exit the QShell session and return to the Configuration Wizard.
2. At the Select the configuration task that you want to perform dialog box,
select Transfer Data to Another Database, and then click Next.
3. If global security is enabled, you will be prompted to enter an IBM
WebSphere Application Server administrative user name and password in the
WebSphere Application Server global security is enabled... dialog box. Type
the user name and password in the appropriate fields, and then click Next.
4. If you transferred your LDAP directory from Cloudscape to another product,
you will be prompted to authenticate against your LDAP directory in the
Enter the LDAPAdminUID and password dialog box. Type the LDAP
administrator account’s user name and password in the appropriate fields,
and then click Next.
5. At the Select the database type... dialog box, select IBM DB2 for iSeries, and
then click Next.
6. On the next dialog box, indicate the location of the helper file you wish to use
for the wizard by typing the path or clicking the Browse button and browsing
for it, and then click Next.
7. In the next dialog box, type appropriate paths for the requested files, and then
click Next. The following table shows appropriate values for these fields.
File
Path
DBDriver
Native JDBC:
com.ibm.db2.jdbc.app.DB2Driver
Toolbox JDBC:
com.ibm.as400.access.AS400JDBCDriver
DBDriverDs
Native JDBC:
COM.ibm.db2.jdbc.app.DB2XADataSource
Toolbox JDBC:
com.ibm.as400.access.AS400JDBCXADataSource
DBLibrary
Native JDBC:
/QIBM/ProdData/Java400/ext/db2_classes.jar
Toolbox JDBC:
/QIBM/UserData/WebAS5/Base/<instance>/
PortalServer5/shared/app/jt400.jar
8. In the next dialog box, type appropriate values for the requested information,
and then click Next. The following table shows appropriate values for these
fields.
220
Field
Value
WpsDBSchema
<wps_schema>
Installation and Upgrade Guide
Field
Value
WpsDbName
Native JDBC:
*LOCAL/<wps_schema>
Toolbox JDBC:
<hostname>/<wps_schema>
DbUser
<user_profile>
DbPassword
<user_profile_password>
DbUrl
Native JDBC:
jdbc:db2:*LOCAL/<wps_schema>
Toolbox JDBC:
jdbc:as400:<hostname>/<wps_schema>
9. In the next dialog box, type appropriate values for the requested information,
and then click Next. The following table shows example values for a Windows
server.
Field
Value
WmmDbSchema
<wmm_schema>
WmmDbName
Native JDBC:
*LOCAL/<wmm_schema>
Toolbox JDBC:
<hostname>/<wmm_schema>
WmmDbUser
<user_profile>
WmmDbPassword
<user_profile_password>
WmmDbUrl
Native JDBC:
jdbc:db2:*LOCAL/<wmm_schema>
Toolbox JDBC:
jdbc:as400:<hostname>/<wmm_schema>
10. In the next dialog box, type appropriate values for the requested information,
and then click Next. The following table shows appropriate values for these
fields.
Field
Value
WpcpDbSchema
<wpcp_schema>
WpcpDbName
Native JDBC:
*LOCAL/<wpcp_schema>
Toolbox JDBC:
<hostname>/<wpcp_schema>
WpcpDbUser
<user_profile>
WpcpDbPassword
<user_profile_password>
Chapter 5 Connecting to a DBMS Server
221
Field
Value
WpcpDbUrl
Native JDBC:
jdbc:db2:*LOCAL/<wpcp_schema>
Toolbox JDBC:
jdbc:as400:<hostname>/<wpcp_schema>
11. In the next dialog box, type appropriate values for the requested information,
and then click Next. The following table shows appropriate values for these
fields.
Field
Example Value
FeedbackSchema
<feedback_schema>
FeedbackDbName
*LOCAL/<feedback_schema>
FeedbackDbUser
<user_profile>
FeedbackDbPassword
<user_profile_password>
FeedbackDbUrl
Native JDBC:
jdbc:db2:*LOCAL/<feedback_schema>
Toolbox JDBC:
jdbc:as400:<hostname>/<feedback_schema>
12. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
13. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Tip: Review the logs from the database configuration to ensure all is well
before proceeding to the next task. These logs are stored in the wp_root
/log directory, where wp_root is the WebSphere Portal root directory.
After you have successfully transferred the WebSphere Portal data to DB2, transfer
Workplace Collaboration Services data to DB2.
For more information, see ″Transferring IBM Workplace Collaboration Services data
to DB2 Universal Database for iSeries.″
Related concepts
Transferring data from Cloudscape to DB2 Universal Database for iSeries
Related tasks
Transferring IBM Workplace Collaboration Services data to DB2 Universal
Database for iSeries
Use the Configuration Wizard to transfer IBM Workplace Collaboration Services
data from IBM Cloudscape to the IBM DB2 for iSeries database.
Transferring Workplace Collaboration Services data to DB2 Universal Database
for iSeries:
Use the Configuration Wizard to transfer IBM Workplace Collaboration Services
data from IBM Cloudscape to the IBM DB2 for iSeries database.
222
Installation and Upgrade Guide
Note: The native JDBC driver values are specified by default in the Configuration
Wizard. Use the native JDBC driver if Workplace Collaboration Services is
on the same system as the database files. Use the IBM Toolbox JDBC driver
if Workplace Collaboration Services is on a different system than the
database files. Note that the driver you use should be the same for all
database transfer tasks.
Both the Cloudscape server and the database host system must to be running to
support the data transfer.
1. At the Select the configuration task that you want to perform dialog box,
click IBM Workplace Database Transfer, and then click Next.
2. If global security is enabled, you will be prompted to enter an IBM
WebSphere Application Server administrative user name and password in the
WebSphere Application Server global security is enabled... dialog box. Type
the user name and password in the appropriate fields, and then click Next.
3. If you transferred your LDAP directory from Cloudscape to another product,
you will be prompted to authenticate against your LDAP directory in the
Enter the LDAPAdminUID and password dialog box. Type the LDAP
administrator account’s user name and password in the appropriate fields,
and then click Next.
4. At the Select the database type dialog box, select IBM DB2 for iSeries, and
then click Next.
5. At the dialog box whose first field starts with ″LWPDBDriver,″ enter the
appropriate paths to the relevant database files, and then click Next. The
following table includes appropriate values for these fields.
File
Path
LWPDBDriver
Native JDBC:
com.ibm.db2.jdbc.app.DB2Driver
Toolbox JDBC:
com.ibm.as400.access.AS400JDBCDriver
LWPDbLibrary
Native JDBC:
/QIBM/ProdData/Java400/ext/db2_classes.jar
Toolbox JDBC:
/qibm/userdata/webas5/base/<instance>
/PortalServer/shared/app/jt400.jar
6. In the dialog box that starts with ″LWPDBUrl,″ enter information about the
new database and associated user names and passwords, click Debug Mode
in case errors occur during the data transfer, and then click Next. The
following table includes appropriate values for these fields.
Field
Value
LWPDBUrl
Native JDBC:
jdbc:db2:*LOCAL
Toolbox JDBC:
jdbc:as400:<hostname>
Chapter 5 Connecting to a DBMS Server
223
Field
Value
LWPDBAdminUser
<admin_user>
LWPDBAdminPassword
<admin_user_password>
LWPDBAppUser
<app_user_profile>
LWPDBAppPassword
<app_user_profile_password>
BackEndId
DB2UDBAS400_V5_1
7. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
8. Click Finish to close the Configuration Wizard.
9. Review the logs from the data transfer operation to ensure all is well before
proceeding to the next step. Logs are stored in the wp_root /log directory,
where wp_root is the WebSphere Portal root directory.
10. Start the WebSphere Portal server by running the following commands.
a. Start the QShell Interpreter by entering the following on an i5/OS
command line:
STRQSH
b. Change to the <wp_root>/rootscripts directory by entering the following:
cd wp_root/rootscripts
where <wp_root> is the root directory for WebSphere Portal.
c. Start WebSphere Portal by entering the following:
startServer.sh WebSphere_Portal
d. Start the Mail Server by entering the following:
startServer.sh Mail_Server_1
Related concepts
Transferring data from Cloudscape to DB2 Universal Database for iSeries
Transferring data to Oracle
By default, IBM WebSphere Portal and IBM Workplace Collaboration Services
install with some predefined data stored in the IBM Cloudscape database
management system, hosted on the Workplace server. Cloudscape is sufficiently
robust for use in demo installations; however, for a production environment, it is
recommended that you transfer data to a more robust DBMS product.
Before you can transfer data to Oracle, you must have created an Oracle database
and assigned users to it. For more information, see the topic, ″Creating the Oracle
database.″
Transferring data to Oracle involves the following tasks, which must be completed
in the sequence shown:
1. Verify that Oracle 9i patch 9.2.0.4.0 has been installed on the Oracle server.
Note: The data transfer operation will not work unless this patch has been
installed.
2. Set up the Oracle database schemas.
3. Transfer WebSphere Portal data to Oracle.
4. Transfer Workplace Collaboration Services data to Oracle.
224
Installation and Upgrade Guide
Begin the process by setting up the Oracle database schemas as described in the
topic, ″Setting up the Oracle database.″
Setting up the Oracle database:
You must have already created the database instance on the Oracle database server.
A database instance is created automatically during Oracle installation; if you are
using an existing installation you may need to drop the existing database and
create a new one.
Note: If you have already run a database transfer (whether or not it was
successful) and plan to run another transfer using the same Oracle database,
it is recommended that you use the Oracle Enterprise Console Manager to
drop all IBM Workplace Collaboration Services (LWPCOMM, LWPApp, and
so on) and IBM WebSphere Portal Server-related users (FEEDBACK,
WMMDBUSR, and so on) with CASCADE. You should also drop all LWP*
named tablespaces as well.
Perform this task on the computer hosting Workplace Collaboration Services.
1. (IBM AIX, Linux, and Sun Solaris only) Set up the .profile (or .bash_profile)
for both root and oracle users:
a. Verify that the following variables are set in the profile:
ORACLE_BASE=/opt/oracle (or equivalent for your environment)
ORACLE_HOME=$ORACLE_BASE/product/9ir2 (or equivalent for your environment)
TNS_ADMIN=$ORACLE_HOME/network/admin
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
NLS_LANG=(See information below)
PATH=$PATH:$ORACLE_HOME/bin
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME
/jlib:$ORACLE_HOME/rdbms/jlib:$ORACLE_HOME/network
/jlib export ORACLE_BASE ORACLE_HOME ORA_NLS33 NLS_LANG
PATH LD_LIBRARY_PATH CLASSPATH TNS_ADMIN
b. Verify that the library path is correct:
AIX
LIBPATH=[ORACLE_HOME]/lib:[ORACLE_HOME]/lib32:[ORACLE_HOME]
/jdbc/lib
Linux and Solaris
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$ORACLE_HOME
/ctx/lib:$ORACLE_HOME/jdbc/lib
c. Verify that the $NLS_LANG variable is correct by running the following
command:
echo $NLS_LANG
The response should end with ″UTF8″ as in ″American_America.UTF8″.
This is the environment variable that contains the codepage. It is in three
parts: language, territory, and character set (also known as codepage). The
$NLS_LANG env variable is used by Oracle to determine what character
set you are using on the client side to ensure proper conversion. (Both
your Oracle database and your client software must use UTF-8 as the
codepage).
2. (RedHat 3.0 Linux only) Locate the etc/ant.conf file and rename it to
ant.conf.BAK. The database transfer task will install a file with the same
name, so renaming your original file will prevent it from being overwritten in
case you want to use it at a later date.
Chapter 5 Connecting to a DBMS Server
225
3. (Microsoft Windows only) Verify that you are using the UTF-8 codepage:
a. Open the Windows registry (run regedit).
b. Locate the section,
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME<id>\NLS_LANG,
where <id> is the unique number identifying the Oracle home (for
example, HOME0).
c. Within that section, locate the NLS_LANG parameter. The key is in three
parts: language, territory, and character set (also known as codepage).
d. Verify that the key ends with ″UTF8″ as in ″American_America.UTF8″; if
necessary, fix the key. You must use the UTF-8 codepage.
e. Close the registry.
4. Stop the IBM Cloudscape Network Server and the IBM WebSphere Portal
server by running the following commands.
a. Open a command prompt window.
b. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
c. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
d. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
e. Stop the Cloudscape Network Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopNetworkServer.sh
Windows
stopNetworkServer.bat
5.
6.
7.
8.
f. Close the command prompt window and return to the Configuration
Wizard.
Start the Configuration Wizard as described in the topic, ″Starting the
Configuration Wizard.″
In theSelect the configuration task you want to perform dialog box, click
IBM Workplace Setup database, and then click Next.
In the Select the database type... dialog box, click Oracle Enterprise Edition,
and then click Next.
In the LWPDBDriver: dialog box, type the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for a Windows server.
File
Example Path
LWPDBDriver
oracle.jdbc.diver.OracleDriver
LWPDbLibrary
C:/oracle/ora92/jdbc/lib/classes12.zip
9. In the LWPDBNAME: dialog box, fill in the information about the new
database, including its associated user names and passwords, and then click
Next. The following table includes examples of appropriate values for a
Windows server.
226
Installation and Upgrade Guide
Field
Example Values
LWPDBNAME
wps50
LWPDBUrl
jdbc:oracle:oci:
@<tnsnames_entry_alias>
LWPDBAdminUser
ora92dmin
LWPDBAdmin
Password
<ora92dmin_password>
Always type the password
yourself as the default value may
not be correct.
LWPDBAppUser
LWPApp
Application User’sname.
LWPDBAppPassword <LWPApp_password>
Comments
Use the alias specified for this
database in the tnsnames.ora file.
This is usually the name of the
database; in this documentation
the database name and the tns
alias are both wps50.
Application User’s password.
Always type the password
yourself as the default value may
not be correct.
10. In the IBM Workplace Common Settings dialog box, fill in information about
the Common schema names and tablespaces in the appropriate fields. Steps 10
through 14 present tables showing examples (for a Windows server) of
appropriate values for the fields in the each dialog box. Notice that
tablespaces are created in the default Oracle directory. If you want to change
this (for example, for performance or backup reasons), specify a different
location in this dialog box. For example, you might change the location of the
Common table space from ″LWPCOMMREG″ to one of the following
locations:
AIX, Linux, and Solaris
/data1/lwpdata/LWPCOMMREG
Windows
F:/lwpdata/LWPCOMMREG
Field
Example Values
Comments
LWPComSchema
LWPCOMM
The user name of the Com
(Common) schema’s owner.
LWPComSchemaPW
<LWPCOMM
_password>
The password for the Com schema
owner account. Always type the
password yourself as the default
value may not be correct.
db.lwp.comm.data
.tablespace.name
LWPCOMMREG
The data tablespace name for the
Com schema
db.lwp.comm.data
.container.list
LWPCOMMREG
The data tablespace location for the
Com schema.
db.lwp.comm.idx
.tablespace.name
LWPCOMMIDX
The index tablespace name for the
Com schema
db.lwp.comm.idx
.container.list
LWPCOMMIDX
The index tablespace location for the
Com schema.
11. In the Learning Management Settings dialog box, fill in information about the
Learning Management schema names and tablespaces in the appropriate
fields.
Chapter 5 Connecting to a DBMS Server
227
Field
Example Values
Comments
LWPLMSSchema
LWPLMS
The user name of the LMS (Learning)
schema’s owner.
LWPLMSSchemaPW
<LWPLMS
_password>
The password for the LMS schema owner
account. Always type the password
yourself as the default value may not be
correct.
db.lwp.lms.data
.tablespace.name
LWPLMSDATA
The data tablespace name for the LMS
schema
db.lwp.lms.data
.container.list
LWPLMSDATA
The data tablespace location for the LMS
schema.
db.lwp.lms.id
.tablespace.name
LWPLMSIDX
The index tablespace name for the LMS
schema
db.lwp.lms.idx
.container.list
LWPLMSIDX
The index tablespace location for the LMS
schema.
12. In the Learning Delivery Settings dialog box, fill in information about the
Learning Delivery schema names and tablespaces in the appropriate fields.
Field
Example Values
Comments
LWPLDSSchema
LWPLDS
The user name of the LDS (Learning
Delivery) schema’s owner.
LWPLDSSchemaPW
<LWPLDS
_password>
The password for the LDS schema
owner account. Always type the
password yourself as the default value
may not be correct.
db.lwp.lds.data
.tablespace.name
LWPLDSDATA
The data tablespace name for the LDS
schema.
db.lwp.lds.data
.container.list
LWPLDSDATA
The data tablespace location for the
LDS schema.
db.lwp.lds.idx
.tablespace.name
LWPLDSIDX
The index tablespace name for the LDS
schema
db.lwp.lds.idx .container.list LWPLDSIDX
The index tablespace location for the
LDS schema.
13. In the Messaging Settings dialog box, fill in information about the Messaging
schema names and tablespaces in the appropriate fields.
228
Field
Example Value
Comment
LWPMsgSchema
LWPCOMM
The user name of the Msg (Messaging)
schema’s owner.
db.num.partitions
3
Number of partitions to create in the
Messaging schema.
LWPMsgSchemaPW
<LWPCOMM
_password>
The password for the Msg schema owner
account. Always type the password
yourself as the default value may not be
correct.
db.lwp.msg.data
.tablespace.name
LWPMSGDATA
The data tablespace name for the Msg
schema.
db.lwp.msg.data
.container.list
LWPMSGDATA
The data tablespace location for the Msg
schema.
Installation and Upgrade Guide
Field
Example Value
Comment
db.lwp.msg.id
x.tablespace.name
LWPMSGIDX
The index tablespace name for the Msg
schema.
db.lwp.msg.idx
.container.list
LWPMSGIDX
The index tablespace location for the Msg
schema.
db.lwp.msg.lob
.tablespace.name
LWPMSGLOB
The large object tablespace name for the
Msg schema.
db.lwp.msg.lob
.container.list
LWPMSGLOB
The large object tablespace location for the
Msg schema.
db.lwp.msg.ptn
.tablespace.name
LWPMSGPTN
The tablespace partition name base for the
Msg schema.
db.lwp.msg.ptn
.container.list
LWPMSGPTN
The tablespace partition location base for
the Msg schema.
db.lwp.msg.map
.tablespace.name
LWPMSGMAP
The map tablespace name for the Msg
schema.
db.lwp.msg.ma
.container.list
LWPMSGMAP
The map tablespace location for the Msg
schema.
db.lwp.msg.mta
.tablespace.name
LWPMSGMTA
The MTA tablespace name for the Msg
schema.
db.lwp.msg.mta
.container.list
LWPMSGMTA
The MTA tablespace location for the Msg
schema.
db.lwp.msg.file
.tablespace.name
LWPMSGFILE
The file tablespace name for the Msg
schema.
db.lwp.msg.file
.container.list
LWPMSGFILE
The file tablespace location for the Msg
schema.
14. In the Messaging Archive Settings dialog box, fill in information about the
Messaging schema names and tablespaces in the appropriate fields.
Field
Example Values
Comments
LWPArcSchema
LWPCOMM
The user name of the Arc (Archive)
schema’s owner; in this example, the
same account owns the Com, Msg,
and Arc schemas to simplify access.
LWPArcSchemaPW
<LWPCOMM
_password>
The password for the Arc schema
owner account. Always type the
password yourself as the default
value may not be correct.
db.lwp.arc.data
.tablespace.name
LWPARCDATA
The data tablespace name for the Arc
schema.
db.lwp.arc.data
.container.list
LWPARCDATA
The data tablespace location for the
Arc schema.
db.lwp.arc.idx
.tablespace.name
LWPARCIDX
The index tablespace name for the
Arc schema.
db.lwp.arc.idx
.container.list
LWPARCIDX
The index tablespace location for the
Arc schema.
15. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database configuration by clicking Next.
Chapter 5 Connecting to a DBMS Server
229
16. Review the logs from the database configuration to ensure all is well before
proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
Note: If you have successfully completed a database transfer and you are
running it again, the database schemas are already in place and are not
affected by the Database Setup task. The logs will note warnings to this
effect.
17. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
After you have set up the Oracle database schemas, proceed to the topic,
″Transferring WebSphere Portal data to Oracle.″
Transferring WebSphere Portal Server data to Oracle:
Make sure the Oracle server is running. If the Oracle database is not hosted on the
IBM Workplace server, install the Oracle client on the Workplace server before
proceeding.
Perform this task on the Workplace server.
1. Start the IBM Cloudscape Network Server, start the IBM WebSphere
Application Server, and stop the IBM WebSphere Portal server, by running the
following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Start the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./startNetworkServer.sh
Microsoft Windows
startNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Start the IBM WebSphere Application Server with the following
case-sensitive command:
IBM AIX, Linux, and Sun Solaris
./startServer.sh server1
Microsoft Windows
startServer.bat server1
f. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
g. Close the command prompt window and return to the Configuration
Wizard.
230
Installation and Upgrade Guide
2. In the Select the configuration task that you want to perform dialog box,
click Transfer Data to Another Database, and then click Next.
3. If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
4. If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
5. In the Select the database type... dialog box, select Oracle Enterprise Edition,
and then click Next.
6. In the Please enter an appropriate properties file location... dialog box,
browse or type the path to the Oracle transfer helper file, and then click Next.
This file is usually stored in the following location:
<wp_root>config\helper\transfer_oracle.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, C:\WebSphere\PortalServer\config.
7. In the DbDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values for a Windows
server.
File
Example path
DBDriver
oracle.jdbc.driver.OracleDriver
DBDriverDs
oracle.jdbc.xa.client.OracleXADataSource
DBLibrary
C:/oracle/ora92/jdbc/lib/classes12.zip
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpsDbName wps50
DbUser
WPSDBUSR
DbPassword <WPSDBUSR
_password>
Always type the password yourself as the default value
may not be correct.
DbUrl
Use the alias specified for this database in the
tnsnames.ora file. This is usually the name of the
database; in this documentation the database name and
the tns alias are both wps50.
jdbc:oracle:thin:
@<dns_server>:
1521:wps50
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
WmmDbName
wps50
WmmDbUser
WMMDBUSR
WmmDbPassword <WMMDBUSR
_password>
Comments
Always type the password yourself as the default
value may not be correct.
Chapter 5 Connecting to a DBMS Server
231
Field
Example Value
Comments
WmmDbUrl
jdbc:oracle:thin:
@<dns_server>:
1521:wps50
Use the alias specified for this database in the
tnsnames.ora file. This is usually the name of the
database; in this documentation the database
name and the tns alias are both wps50.
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
WpcpDbName
wps50
WpcpDbUser
WCMDBADM
Comments
WpcpDbPassword<WCMDBADM
_password>
Always type the password yourself as the default
value may not be correct.
WpcpDbUrl
jdbc:oracle:thin:
@<dns_server>:
1521:wps50
Use the alias specified for this database in the
tnsnames.ora file. This is usually the name of the
database; in this documentation the database
name and the tns alias are both wps50.
WpcpDb
EjbPassword
<WpcpDbEjb
_password>
Always type the password yourself as the default
value may not be correct; use the password
assigned to this WebSphere Portal Server user
account.
WpcpDb
Pznadmin
Password
<WpcpDb_
Always type the password yourself as the default
Pznadmin_password> value may not be correct use the password
assigned to this WebSphere Portal Server user
account.
Wpcp
ResourceUrl
D:\WebSphere
\PortalServer\wpcp
\v5.0\runtime\lib
For Windows, use a single backslash between
directories; for AIX, Linux, or Solaris, use a single
forward slash.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values for a Windows server.
Field
Example Value
Feedback
DbName
wps50
Feedback
DbUser
FEEDBACK
Comments
Feedback
<FeedbackDb
DbPassword _password>
Always type the password yourself as the default
value may not be correct.
Feedback
DbUrl
Type this as a single entry. Use the alias specified for
this database in the tnsnames.ora file. This is usually
the name of the database; in this documentation the
database name and the tns alias are both wps50.
jdbc:oracle:thin:
@<dns_server>:
1521:wps50
12. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
13. Review the logs from the Workplace Collaboration Services data transfer to
ensure all is well before proceeding to the next step; the logs are stored in the
\WebSphere\PortalServer\log directory.
232
Installation and Upgrade Guide
14. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
After you have successfully transferred the WebSphere Portal data to Oracle,
proceed to the topic, ″Transferring Workplace Collaboration Services data to
Oracle.″
Transferring Workplace Collaboration Services data to Oracle:
Perform this task on the computer hosting Workplace Collaboration Services.
1. Stop the IBM Cloudscape Network Server, the WebSphere Portal Server, and
the WebSphere Application Server by running the following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./stopNetworkServer.sh
Microsoft Windows
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./stopServer.sh server1
Windows
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
2. At the Select the configuration task that you want to perform dialog box,
click IBM Workplace Database Transfer, and then click Next.
3. At the Select the database type dialog box, select Oracle Enterprise Edition,
and then click Next.
4. At the Please enter an appropriate properties file location... dialog box,
verify the path for the dbbuild.properties file, correct it if needed, and then
click Next.
5. At the LWPDBDriver:dialog box, enter the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for a Microsoft Windows server.
Chapter 5 Connecting to a DBMS Server
233
File
Example Path
Comments
LWPDBDriver oracle.jdbc.driver.
OracleDriver
LWPDbLibrary C:\oracle\ora92\
jdbc\lib\
classes12.zip
For Windows, use a single backslash between
directories; use a single forward slash for IBM AIX,
Linux, or Sun Solaris.
6. In the LWPDBName:dialog box, enter information about the new database
and associated user names and passwords, click Debug Mode in case errors
occur during the data transfer, and then click Next. The following table
includes examples of appropriate values for a Windows server.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:oracle:oci:
@<tnsnames_entry_alias>
LWPDBAdmin
User
ora92admin
LWPDBAdmin
Password
<ora92admin _password>
Always type the password yourself as the
default value may not be correct.
LWPDBAppUser
<Application
_User_Name>
Application User’s name. This value is case
sensitive.
LWPDBApp
Password
<Application
_User_password>
Application User’s password. Always type
the password yourself as the default value
may not be correct.
BackEndId
ORACLE_V9_1
Although you are using Oracle 9.2, this
setting refers to Oracle 9.1.
Use the alias specified for this database in
the tnsnames.ora file. This is usually the
name of the database; in this
documentation the database name and the
tns alias are both wps50.
7. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
8. Click Finish to close the Configuration Wizard.
9. Review the logs from the Workplace Collaboration Services data transfer to
ensure all is well before proceeding to the next step; the logs are stored in the
\WebSphere\PortalServer\log directory.
10. Update Oracle database settings by running the following SQL Plus
commands on the Oracle server:
grant ALTER on
EJB.BRBeans_Rule to PZNADMIN;
grant DELETE on EJB.BRBeans_Rule to PZNADMIN;
grant INSERT on EJB.BRBeans_Rule to PZNADMIN;
grant SELECT on EJB.BRBeans_Rule to PZNADMIN;
grant UPDATE on EJB.BRBeans_Rule to PZNADMIN;
grant ALTER on EJB.BRBeans_RuleFolder to PZNADMIN;
grant DELETE on EJB.BRBeans_RuleFolder to PZNADMIN;
grant INSERT on EJB.BRBeans_RuleFolder to PZNADMIN;
grant SELECT on EJB.BRBeans_RuleFolder to PZNADMIN;
grant UPDATE on EJB.BRBeans_RuleFolder to PZNADMIN;
conn sys/<password>@<connect string> as sysdba;
234
Installation and Upgrade Guide
grant SELECT on DBA_PENDING_TRANSACTIONS to PUBLIC;
11. (Solaris only) If your Oracle database is hosted locally (on the Workplace
server), change the port used by Instant Messaging to avoid a conflict with
Oracle:
a. Open the WAS Administrator Console.
b. Navigate to Server → ApplicationServer → WebSphere_Portal → Workplace
SIP Service
c. Change TCPLiteProtocolChannel from 8080/8081 to 8060/8061, or another
non-conflicting port.
12. Only if your transfers were successful:
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
c. Navigate to C:\WAS_HOME\TRANLOG and delete all the subdirectories
in it.
13. Start WebSphere Portal Server and Workplace Collaboration Services by
running the following commands.
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start WebSphere Portal Server with the following case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
c. Start Workplace Collaboration Services with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh Mail_Server_1
Windows
startServer.bat Mail_Server_1
d. Close the command prompt window.
Note: If your database transfer was successful, all passwords are automatically
deleted from properties and helper files, If you need to re-run the data
transfer in the future, you must first run the Database Setup again and
allow it to populate files with passwords before you run the data transfer.
After you have finished transferring data from Cloudscape to Oracle, proceed to
Phase 6, ″Connecting to an external HTTP server.″
Transferring data to SQL Server
By default, IBM WebSphere Portal and IBM Workplace install with some
predefined data stored in the IBM Cloudscape database management system,
hosted on the Workplace server. Cloudscape is sufficiently robust for use in demo
Chapter 5 Connecting to a DBMS Server
235
installations; however, for a production environment, it is recommended that you
transfer data to a more robust DBMS product.
If you intend to create the Microsoft SQL Server database yourself, you must do so
before you begin the database transfer. For information on creating the SQL Server
database, see the topic, ″Creating the SQL Server database.″ Otherwise, the
Configuration Wizard will create the database for you during the Database Setup
task.
Transferring data to SQL Server involves the following tasks, which must be
completed in the sequence shown
1. Create the SQL Server database and set up its schemas.
2. Create database users.
3. Enable authentication and distributed transactions in SQL Server.
4. Add stored XA procedures to SQL Server.
5. Transfer WebSphere Portal data to SQL Server.
6. Transfer Workplace Collaboration Services data to SQL Server.
Begin the process by setting up the SQL Server database schemas as described in
the topic, ″Setting up the SQL Server database.″
Setting up the SQL Server database:
Before beginning this task, there are several prerequisites to complete. First, create
the following directories on the server hosting the database used for IBM
Workplace Collaboration Services:
v Data directory, used for storing Microsoft SQL Server data (.dbf files); for
example:
C:\wpdatadir
v Log directory, used for storing logs (.log files); for example:
C:\wplogdir
For performance reasons, you may want to use store these directories on different
devices, but this is not a requirement. The examples show the two directories
existing on the same drive.
Next, download the SQL Server Driver for JDBC Service Pack 3 from the following
Web address:
http://www.microsoft.com/sql/downloads/default.asp
On that page, click Most Popular Downloads → SQL Server 2000 Driver for JDBC
Service Pack 3; download the driver directly to your computer. Instructions for the
download are located on the same page. This driver is required for the Database
Setup task.
Finally, if you will not host the database on the Workplace server, you must create
the database before running this Database Setup task. For instructions on creating
the database, see the topic, ″Creating the SQL Server database.″
Perform this task on the computer hosting Workplace Collaboration Services.
1. Start the Configuration Wizard as described in the topic, ″Starting the
Configuration Wizard.″
236
Installation and Upgrade Guide
2. In the Select the configuration task that you want to perform dialog box,
click IBM Workplace Setup Database, and then click Next.
3. In the Select the database type... dialog box, select Microsoft SQL Server
Enterprise, and then click Next.
4. In the LWPDBDriver: dialog box, type the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values.
File
Example Path
Comments
LWPDBDriver com.microsoft.jdbc.sqlserver
.SQLServerDriver
LWPDbLibrary C:/MicrosoftSQLServer/lib
Type all three paths into the field, separating
/msbase.jar;
them with semi colons. Use a forward slash
C:/MicrosoftSQLServer/lib
between directories.
/mssqlserver.jar;
C:/MicrosoftSQLServer/lib
/msutil.jar
5. In the LWPDBName: dialog box, enter information about the new database
and associated user names and passwords, and then click Next. The following
table includes examples of appropriate values.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:MicrosoftSQLServer//The database name specified above in the
<server_DNS>:1433
LWPDBNAME field will be appended
automatically to the URL.
LWPDBAdminUser sqlserveradmin
SQL Server administrator’s user name.
LWPDBAdmin
Password
<sqlserveradmin
_password>
SQL Server administrator’s password.
Always type the password yourself as the
default value may not be correct.
LWPDBAppUser
LWPCOMM
Application User’s name; for SQL Server this
must be the name of the LWPCOMM
schema owner.
LWPDBApp
Password
<appUser_password>
Application User’s password. Always type
the password yourself as the default value
may not be correct.
6. In the SQL Database Setup dialog box, fill in the information needed to
establish the Workplace Collaboration Services schemas (schema owners,
tablespaces, container lists, and so on) in the new database, and then click
Next. The following table includes examples of appropriate values.
Field
Example Value
Comment
Run database creation
True
If you have already created
the database manually, set
the value to False.
db.lwp.data.container.list
C:\wpdatadir
Data tablespace location.
The directory must already
exist, it cannot be created
at run-time.
Chapter 5 Connecting to a DBMS Server
237
Field
Example Value
Comment
db.lwp.logdir.container.list
C:\wplogdir
Log directory location; if
stored on the database
server, provide the full
path. The directory must
already exist, it cannot be
created at run-time.
7. In the IBM Workplace common settings dialog box, fill in the user name and
password for the LWPCOMM schema owner account, and then click Next.
8. In the Learning Management Settings dialog box, fill in the user name and
password for the LWPLMS schema owner account, and then click Next.
9. In the Learning Delivery Settings dialog box, fill in the user name and
password for the LWPLDS schema owner account, and then click Next.
10. In the Messaging Settings dialog box, fill in the user name and password for
the LWPMSG schema owner account, and then click Next.
11. In the Messaging Archive Settings dialog box, fill in the user name and
password for the LWPARC schema owner account, and then click Next.
12. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database configuration by clicking Next.
Note: The database-setup scripts are stored in
<iwp_root>\config\database\work, where <iwp_root> represents the
IBM Workplace Collaboration Services root installation directory. If you
choose not to actually run the scripts now through the Configuration
Wizard, you can run them manually later. If necessary, you can
manually edit the scripts to make additional changes before running
them.
13. Review the logs from the database configuration to ensure all is well before
proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
Note: If you have successfully completed a database transfer and you are
running it again, the database schema are already in place and are not
affected by the Database Setup task. The logs will note warnings to this
effect.
14. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
After you have set up the SQL Server database schemas, proceed to the topic,
″Creating SQL Server database users.″
Creating SQL Server database users:
Add users to the new database to ensure proper access for components of IBM
Workplace Collaboration Services.
Perform this task on the computer hosting the Microsoft SQL Server database,
using the SQL Server Enterprise Manager.
1. Start the SQL Server Enterprise Manager if it is not already running.
2. Expand the nodes until you see Security → Login → New Logins.
3. Add logins for the following users, using uppercase letters for each name:
v EJB
238
Installation and Upgrade Guide
4.
5.
6.
7.
8.
v FEEDBACK
v PZNADMIN
v WCMDBADM
v WMMDBUSR
v WPSDBUSR
For each new login, select SQL Server Authentication and assign the password
that you plan to use when configuring the database.
Attention: For this release, make the passwords match the login names.
Use the same database name that you assigned when you created the database.
In this documentation, the examples use wps50 as the database name.
Now expand the nodes until you see Databases → wps50 → Users → New
Database User.
Add a user for each of the new logins, using uppercase letters for each name
and setting the Database Role Membership to public and db owner for each
user:
v EJB
v FEEDBACK
v PZNADMIN
v WCMDBADM
v WMMDBUSR
v WPSDBUSR
Leave the SQL Server Enterprise Manager open for the next task.
After you have added the appropriate users to the database, proceed to the topic,
″Enabling authentication and distributed transactions in SQL Server.″
Enabling authentication and distributed transactions in SQL Server:
Enable authentication and distributed transactions for Microsoft SQL Server.
Perform this task on the computer hosting the SQL Server database, using the SQL
Server Enterprise Manager.
1. Start the SQL Server Enterprise Manager.
2. In the SQL Server Enterprise Manager, right click on your Server Group, which
may be (local).
3. Set the authentication mode by clicking Security → Authentication: SQL Server
and Windows.
4. Enable distributed transactions by clicking General → Autostart MSDTC.
5. Close the SQL Server Enterprise Manager.
Proceed to the topic, ″Adding stored XA procedures to SQL Server.″
Adding stored XA procedures to SQL Server:
Add stored XA command procedures to Microsoft SQL Server, to enable database
operations required by the Configuration Wizard.
Attention:
Omitting this task may result in an improperly configured database.
In this task, you copy files from the IBM Workplace Collaboration Services
computer to the computer hosting the SQL Server DBMS.
Chapter 5 Connecting to a DBMS Server
239
1. On the Workplace server, navigate to the following directory:
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\SQLServer JTA
2. Copy the sqljdbc.dll and instjdbc.sql files, and paste them to a location where
they can be accessed from the SQL Server host computer.
3. On the SQL Server host computer, copy the two files to the following directory
(or equivalent):
C:\MicrosoftSQLServer\SQLServer\Binn
4. Use the OSQL program to apply the instjdbc.sql file to the SQL Server Master
database by running the following command:
osql -E -i instjdbc.sql -o instjdbc1515.log
After you have added the XA procedures to SQL Server, proceed to the topic,
″Transferring WebSphere Portal data to SQL Server.″
Transferring WebSphere Portal data to SQL Server:
Both the IBM Cloudscape server and the Microsoft SQL Server database server
must to be running to support the data transfer.
Perform this task on the computer hosting IBM Workplace Collaboration Services.
1. Start the Cloudscape Network Server, start the IBM WebSphere Application
Server, and stop the IBM WebSphere Portal server, by running the following
commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Start the Cloudscape Network Server with the following case-sensitive
command:
startNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Start the IBM WebSphere Application Server with the following
case-sensitive command:
startServer.bat server1
f. Stop the WebSphere Portal Server with the following case-sensitive
command:
stopServer.bat WebSphere_Portal
2.
3.
4.
5.
240
g. Close the command prompt window and return to the Configuration
Wizard.
In the Select the configuration task that you want to perform dialog box,
click Transfer Data to Another Database, and then click Next.
If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
In the Select the database type... dialog box, select Microsoft SQL Server
Enterprise, and then click Next.
Installation and Upgrade Guide
6. In the Please enter an appropriate properties file location... dialog box,
browse or type the path to the SQL Server transfer helper file, and then click
Next. This file is usually stored in the following location:
<wp_root>\config\helpers\transfer_sqlserver.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, c:\WebSphere\PortalServer.
7. In the DBDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values.
File
Example path
Comments
DBDriver
com.microsoft.jdbc.sqlserver
.SQLServerDriver
DBDriverDs
com.microsoft.jdbcx.sqlserver
.SQLServerDataSource
DBLibrary
C:/MicrosoftSQLServer/libType all three paths into the field, separating
/msbase.jar;
them with semi colons. Use a forward slash
C:/MicrosoftSQLServer/libbetween directories.
/mssqlserver.jar;
C:/MicrosoftSQLServer/lib
/msutil.jar
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
Comments
WpsDbName
wps50
DbUser
WPSDBUSR
DbPassword
<WPSDBUSR _password>
DbUrl
jdbc:microsoft:sqlserver:/
Type the URL as a single entry; make sure
/<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
Always type the password yourself, as the
default value may not be correct.
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
Comments
WmmDbName
wps50
WmmDbUser
WMMDBUSR
WmmDb
Password
<WMMDBUSR
_password>
WmmDbUrl
jdbc:microsoft:sqlserver:// Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
Always type the password yourself, as the
default value may not be correct.
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
WpcpDbName
wps50
WpcpDbUser
WCMDBADM
Comments
Chapter 5 Connecting to a DBMS Server
241
Field
Example Value
WpcpDb Password <WCMDBADM
_password>
Comments
Always type the password yourself, as
the default value may not be correct.
WpcpDbUrl
jdbc:microsoft:sqlserver:// Type the URL as a single entry; make
server_DNS>:1433;DatabaseName=wps50
sure the ″DatabaseName″ setting
appears only once and has a semi colon
(;) before it.
WpcpDb
EjbPassword
<password as set in SQL
Server login>
Always type the password yourself as
the default value may not be correct.
WpcpDb
<password as set in SQL
PznadminPassword Server login>
Always type the password yourself as
the default value may not be correct.
WpcpDb
HostName
<your server DNS>
Wpcp ResourceUrl
c:\WebSphere\PortalServer\ Use a single backslash between
wpcp\v5.0\runtime\lib
directories.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values.
Field
Example Value
Comments
FeedbackDb
Name
wps50
FeedbackDb
User
FEEDBACK
FeedbackDb
assword
<FEEDBACK _password>
FeedbackDb
Url
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
FeedbackDb
HostName
<server_DNS>
Always type the password yourself, as the
default value may not be correct.
12. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
13. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Tip: Review the logs from the database configuration to ensure all is well
before proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
After you have successfully transferred the WebSphere Portal data to SQL Server,
proceed to the topic, ″Transferring Workplace Collaboration Services data to SQL
Server.″
Transferring Workplace Collaboration Services data to SQL Server:
Perform this task on the computer hosting IBM Workplace Collaboration Services.
1. Stop the IBM Cloudscape Network Server, the IBM WebSphere Portal Server,
and the IBM WebSphere Application Server by running the following
commands.
242
Installation and Upgrade Guide
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
2. In the Select the configuration task that you want to perform dialog box,
click IBM Workplace Database Transfer, and then click Next.
3. In the Select the database type dialog box, select Microsoft SQL Server
Enterprise, and then click Next.
4. In the LWPDBDriver: dialog box, type enter the appropriate paths to the
relevant database files, and then click Next. The following table includes
examples of appropriate values for each field in the dialog box.
File
Example Path
Comments
LWPDBDriver
com.microsoft.jdbc.sqlserver
.SQLServerDriver
LWPDbLibrary
C:/MicrosoftSQLServer/lib Type all three paths into the field, separating
/msbase.jar;
them with semi colons. Use a forward slash
C:/MicrosoftSQLServer/lib between directories.
/mssqlserver.jar;
C:/MicrosoftSQLServer/lib
/msutil.jar
5. In the LWPDBNAME: dialog box, type the information about the new
database and associated user names and passwords, click Debug Mode in
case errors occur during the data transfer, and then click Next. The following
table includes examples of appropriate values for each field in the dialog box.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
LWPDBAdmin
User
SQLSVRADMIN
LWPDBAdmin
Password
<SQLSVRADMIN
_password>
LWPDBApp
User
LWPCOMM
Always type the password yourself, as the
default value may not be correct.
Chapter 5 Connecting to a DBMS Server
243
Field
Example Values
Comments
LWPDBApp
Password
<LWPCOMM _password>
Always type the password yourself, as the
default value may not be correct.
BackEndId
MSSQLSERVER_V7_1
6. In the The WebSphere Portal Configuration Wizard is ready to run the
following configuration dialog box, start the database transfer by clicking
Next.
7. Click Finish to close the Configuration Wizard.
8. Review the logs from the data transfer operation to ensure all is well before
proceeding to the next step. These logs are stored in the
\WebSphere\PortalServer\log directory.
9. Use the OSQL utility to run the following scripts, which correct installation
problems in the SQL Server database.
-- osql -E -d wps50 -i concat_caltext.sql -o concat_caltext.log
-- osql -E -d wps50 -i concat_msgtext.sql -o concat_msgtext.log
These files are normally located in
<iwp_root>\config\database\msg.db\sqlserver, where <iwp_root> is the root
installation directory for Workplace Collaboration Services.
10. Use the ISQL utiity to grant database permissions for the LWPLDS schema:
isql -U sa -d wp50
GRANT SELECT, INSERT, UPDATE, DELETE ON LWPLDS.LRNPARTITION TO LWPCOMM -U;
go
GRANT SELECT, INSERT, UPDATE, DELETE ON LWPLDS.LRNUSER_PARTITION TO LWPCOMM;
go
11. If you used the default port of 1433 for your SQL Server installation, skip this
step and go directly to Step 11. If you used a custom port, complete this step
before proceeding to Step 11.
a. Open the WAS Administrator Console.
Click Resources.
Under Additional Properties, click WPCP50 JDBC.
Click Data Sources Version 4.
For each datasource listed (feedbackDS, persDS, and wcmDS), click
Custom Properties under the additional properties section:
v Click New to add a custom property.
v Add a property called portNumber, and type the non-zero standard port
number in use for SQL Server.
f. Save the entries and close the Administrative Console.
12. Start WebSphere Portal Server and Workplace Collaboration Services by
running the following commands.
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start WebSphere Portal Server with the following case-sensitive command:
AIX, Linux, and Solaris
b.
c.
d.
e.
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
244
Installation and Upgrade Guide
c. Start Workplace Collaboration Services with the following case-sensitive
command:
startServer.bat Mail_Server_1
d. Close the command prompt window.
Note: If your database transfer was successful, all passwords are automatically
deleted from properties and helper files, If you need to re-run the data
transfer in the future, you must first run the Database Setup again and
allow it to populate files with passwords before you run the data transfer.
After you have successfully transferred Workplace Collaboration Services data to
the SQL Server database, proceed to Phase 6, ″Connecting to an external HTTP
server.″
Connecting Network Deployment nodes to a remote database
Each time you install IBM Workplace Collaboration Services onto a server, a copy
of IBM WebSphere Portal Server is installed with it. In addition, each Workplace
server gets a separate, standalone version of IBM Cloudscape installed. The
Cloudscape installation hosts a database, which is initially populated with data
specific to the local Workplace Collaboration Services and WebSphere Portal Server
installations.
When you federate multiple Workplace servers as nodes within a Network
Deployment, they all share a common database server, which is hosted remotely.
For the first node in the deployment, you set up the database and transfer installed
data as you would for a standalone Workplace server that is using a remote
database.
For subsequent nodes in the deployment, you connect to the existing database and
transfer data from the node to the database, working first with WebSphere Portal
Server data and then with Workplace Collaboration Services data.
Attention: At this stage, do not access WebSphere Portal and do not log in to
WebSphere Portal as any user, because it could result in database
corruption.
Proceed to the topic that describes how to connect to the database product you are
using:
v Connecting to DB2 UDB
v Connecting to Oracle
v Connecting to SQL Server
“Transferring data to another DBMS” on page 206
Connecting to DB2 UDB
By default, each node in a Network Deployment installs with its own IBM
Cloudscape database. Because all the nodes in the Network Deployment need to
share a common data store, you must connect the node to a remote database
instead. This section explains how to connect the node to a remote IBM DB2
Universal Database server and transfer locally hosted data from Cloudscape to the
DB2 UDB database.
Before you begin this task, make sure that you have installed the DB2 client on the
current node so it can communicate with the DB2 database server.
Chapter 5 Connecting to a DBMS Server
245
You must connect to DB2 and transfer two sets of data: IBM WebSphere Portal
Server data, and IBM Workplace Collaboration Services data. Complete these tasks
in the sequence shown:
1. Connect to DB2 UDB for WebSphere Portal Server.
2. Connect to DB2 UDB for Workplace Collaboration Services.
Connecting to DB2 UDB for WebSphere Portal Server:
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. Start the Cloudscape Network Server, start the WebSphere Application Server,
and start the WebSphere Portal server, by running the following commands.
a. Open a command window and navigate to the
<wp_root>\rootscripts\subtasks directory, where <wp_root> is the root
installation directory for WebSphere Portal.
b. Start the Cloudscape Network Server with the following case-sensitive
command:
IBMAIX, Linux, and Sun Solaris
./startNetworkServer.sh
Microsoft Windows
startNetworkServer.bat
c. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
d. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh server1
Windows
startServer.bat server1
e. Start the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
2.
3.
4.
5.
6.
246
f. Close the command prompt window and return to the Configuration
Wizard.
In the Select the configuration task that you want to perform dialog box,
click Connect to a Database, and then click Next.
If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
In the Select the database type... dialog box, select IBM DB2 Universal
Database, and then click Next.
In the Please enter an appropriate properties file location... dialog box,
browse to or type the path to the DB2 transfer helper file, and then click Next.
This file is usually stored in the following location:
Installation and Upgrade Guide
<wp_root>\config\helpers\transfer_db2.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, c:\WebSphere\PortalServer.
7. In the DbDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values for a Windows
server.
File
Example path
DBDriver
COM.ibm.db2.jdbc.app.DB2Driver
DBDriverDs
COM.ibm.db2.jdbc.DB2XADataSource
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpsDbName
wps50
For a remote database, use the name of the alias
you used when cataloging the database.
DbUser
db2admin
This value is case sensitive. This user must have
database administrator privileges.
DbPassword
<db2admin
_password>
Always type the password yourself, as the
default value may not be correct.
DbUrl
jdbc:db2:wps50
WpsDbNode
wpsNode
For a remote database, use the name of the node
you cataloged after creating the database.
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WmmDb
Name
wps50
For a remote database, use the name of the alias
you used when cataloging the database.
WmmDb
User
db2admin
This value is case sensitive.
WmmDb
Password
<db2admin
_password>
Always type the password yourself, as the default
value may not be correct.
WmmDb Url
jdbc:db2:wps50
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpcpDb
Name
wps50
For a remote database, use the name of the alias you
used when cataloging the database. This value may
default to ″wpcp50″; be sure to change it to the
correct name.
WpcpDb User db2admin
This value is case sensitive.
WpcpDb
Password
Always type the password yourself, as the default
value may not be correct.
<db2admin
_password>
Chapter 5 Connecting to a DBMS Server
247
Field
Example Value
Comments
WpcpDb Url
jdbc:db2:wps50
Wpcp
ResourceUrl
D:\WebSphere\
For Windows, use a single backslash between
PortalServer\wpcp\ directories; use a single forward slash for AIX, Linux,
5.0\runtime\lib
or Solaris.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values for a Windows server.
Field
Example Value
FeedbackDb
Name
wps50
Comments
FeedbackDb User db2admin
This value is case sensitive.
FeedbackDb
Password
<db2admin
_password>
Always type the password yourself, as the
default value may not be correct.
FeedbackDb Url
jdbc:db2:wps50
12. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database connection and transfer by clicking Next.
13. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Tip: Review the logs from the database configuration to ensure all is well
before proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
Important: Now that the WebSphere Portal database connection is completed, do
not access WebSphere Portal and do not log on to WebSphere Portal as
any user from this node, as it could result in database corruption.
After you have successfully connected to DB2 and transferred the WebSphere
Portal data, proceed to the topic, ″Connecting to DB2 UDB for Workplace
Collaboration Services.″
Connecting to DB2 UDB for Workplace Collaboration Services:
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. In the Select the configuration task that you want to perform dialog box,
click IBM Workplace Connection to Database, and then click Next.
2. In the Select the database type dialog box, select IBM DB2 Universal
Database, and then click Next.
3. In the LWPDriver: dialog box, enter the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for a Microsoft Windows server.
248
File
Example Path
LWPDBDriver
COM.ibm.db2.jdbc.app.DB2Driver
LWPDbLibrary
D:\IBM\SQLLIB\java\db2java.zip
Installation and Upgrade Guide
4. In the LWPDBNAME: dialog box, enter information about the new database
and associated user names and passwords, click Debug Mode in case errors
occur during the data transfer, and then click Next. The following table
includes examples of appropriate values for a Windows server.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:db2:wps50
LWPDBAdmin
User
db2admin
This value is case sensitive.
LWPDBAdmin
Password
<db2admin
_password>
Always type the password yourself, as the
default value may not be correct.
LWPDBApp User
<application _user>
Application User’s name. This value is case
sensitive.
LWPDBApp
Password
<application
_user_password>
Application User’s password. Always type
the password yourself, as the default value
may not be correct.
BackEndId
DB2UDBNT_V8_1
5. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database transfer by clicking Next.
6. Click Finish to close the Configuration Wizard.
7. Review the logs from the data transfer operation to ensure all is well before
proceeding to the next step. These logs are stored in the
\WebSphere\PortalServer\log directory.
8. Stop the Cloudscape Network Server, the WebSphere Portal Server, and the
WebSphere Application Server by running the following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./stopNetworkServer.sh
Microsoft Windows
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./stopServer.sh server1
Windows
Chapter 5 Connecting to a DBMS Server
249
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
9. Validate that the transfer was successful by starting the WebSphere Portal
server without starting the Cloudscape server:
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
c. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh Mail_Server_1
Windows
startServer.bat Mail_Server_1
d. Close the command prompt window.
10. Point your browser to the following Web address to verify that you can
connect to the remote DB2 server:
http://<dns_name>:9090/admin
Important: Now that the database connection is completed, do not access
WebSphere Portal and do not log on to WebSphere Portal as any user
from this node, as it could result in database corruption.
After you have successfully transferred Workplace Collaboration Services data to
the SQL Server database, proceed to Phase 6, ″Connecting to an external HTTP
server.″
Connecting to Oracle
By default, each node in a Network Deployment installs with its own IBM
Cloudscape database. Because all the nodes in the Network Deployment need to
share a common data store, you must connect the node to a remote database
instead. This section explains how to connect the node to a remote Oracle database
and transfer locally hosted data from Cloudscape to Oracle.
Before you begin this task, make sure that you have installed the Oracle client on
the current node so it can communicate with the Oracle database server.
You must connect to Oracle and transfer two sets of data: IBM WebSphere Portal
Server data, and IBM Workplace Collaboration Services data. Complete these tasks
in the sequence shown:
1. Connect to Oracle for WebSphere Portal Server.
2. Connect to Oracle for Workplace Collaboration Services.
Connecting to Oracle for WebSphere Portal Server:
250
Installation and Upgrade Guide
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. Start the Cloudscape Network Server, start the WebSphere Application Server,
and start the WebSphere Portal server, by running the following commands.
a. Open a command window and navigate to the
<wp_root>\rootscripts\subtasks directory, where <wp_root> is the root
installation directory for WebSphere Portal.
b. Start the Cloudscape Network Server with the following case-sensitive
command:
IBMAIX, Linux, and Sun Solaris
./startNetworkServer.sh
Microsoft Windows
startNetworkServer.bat
c. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
d. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh server1
Windows
startServer.bat server1
e. Start the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
2.
3.
4.
5.
6.
f. Close the command prompt window and return to the Configuration
Wizard.
In the Select the configuration task that you want to perform dialog box,
click Connect to a Database, and then click Next.
If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
In the Select the database type... dialog box, select Oracle Enterprise Edition,
and then click Next.
In the Please enter an appropriate properties file location... dialog box,
browse or type the path to the Oracle transfer helper file, and then click Next.
This file is usually stored in the following location:
<wp_root>config\helper\transfer_oracle.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, C:\WebSphere\PortalServer\config.
7. In the DbDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values for a Windows
server.
Chapter 5 Connecting to a DBMS Server
251
File
Example path
DBDriver
oracle.jdbc.driver .OracleDriver
DBDriverDs
oracle.jdbc.xa.client. OracleXADataSource
DBLibrary
C:/oracle/ora92/jdbc/ lib/classes12.zip
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WpsDbName
wps50
DbUser
WPSDBUSR
DbPassword
<WPSDBUSR
_password>
Always type the password yourself, as the
default value may not be correct.
DbUrl
jdbc:oracle:thin:
@<dns_server_name>:
1521:wps50
Use the alias specified for this database in the
tnsnames.ora file. This is usually the name of the
database; in this documentation the database
name and the tns alias are both wps50.
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
Comments
WmmDb
Name
wps50
WmmDb
User
WMMDBUSR
WmmDb
Password
<WMMDBUSR
_password>
Always type the password yourself, as the
default value may not be correct.
WmmDb
Url
jdbc:oracle:thin:
@<dns_server_name>:
1521:wps50
Use the alias specified for this database in the
tnsnames.ora file. This is usually the name of
the database; in this documentation the
database name and the tns alias are both
wps50.
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values
for a Windows server.
Field
Example Value
WpcpDb
Name
wps50
WpcpDb
User
WCMDBADM
WpcpDb
Password
<WCMDBADM
_password>
Comments
Always type the password yourself, as the default
value may not be correct.
WpcpDb Url jdbc:oracle:thin:
Use the alias specified for this database in the
@<dns_server_name>: tnsnames.ora file. This is usually the name of the
1521:wps50
database; in this documentation the database name
and the tns alias are both wps50.
252
Installation and Upgrade Guide
Field
Example Value
WpcpDb
<WpcpDbEjb
EjbPassword _password>
Comments
Always type the password yourself, as the default
value may not be correct. Use the password assigned
to this WebSphere Portal Server account.
WpcpDb
Pznadmin
Password
<WpcpDb_ Pznadmin Always type the password yourself.a s the default
_password>
value may not be correct. Use the password assigned
to this WebSphere Portal Server account.
Wpcp
ResourceUrl
D:\WebSphere\
PortalServer\wpcp\
v5.0\runtime\lib
For Windows, use a single backslash between
directories; for AIX, Linux, or Solaris, use a single
forward slash.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values for a Windows server.
Field
Example Value
Comments
FeedbackDb wps50
Name
FeedbackDb FEEDBACK
User
FeedbackDb <FEEDBACK
Password
_password>
Always type the password yourself, as the default
value may not be correct.
FeedbackDb jdbc:oracle:thin:
Use the alias specified for this database in the
Url
@<dns_server_name>: tnsnames.ora file. This is usually the name of the
1521:wps50
database; in this documentation he database name
and the tns alias are both wps50.
12. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database connection and transfer by clicking Next.
13. Review the logs from the Workplace Collaboration Services data transfer to
ensure all is well before proceeding to the next step; the logs are stored in the
\WebSphere\PortalServer\log directory.
14. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
After you have successfully transferred the WebSphere Portal data to Oracle,
proceed to the topic, ″Connecting to Oracle for Workplace Collaboration Services.″
Connecting to Oracle for Workplace Collaboration Services:
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. At the Select the configuration task that you want to perform dialog box,
click IBM Workplace Connection to Database, and then click Next.
2. At the Select the database type dialog box, select Oracle Enterprise Edition,
and then click Next.
3. At the Please enter an appropriate properties file location... dialog box,
verify the path for the dbbuild.properties file, correct it if needed, and then
click Next.
4. At the LWPDBDriver:dialog box, enter the appropriate paths to the relevant
database files, and then click Next. The following table includes examples of
appropriate values for a Microsoft Windows server.
Chapter 5 Connecting to a DBMS Server
253
File
Example Path
Comments
LWPDBDriver oracle.jdbc.driver
.OracleDriver
LWPDbLibraryC:\oracle\ora92\jdbc\lib\
For Windows, use a single backslash between
classes12.zip
directories; use a single forward slash for IBM AIX,
Linux, or Sun Solaris.
5. In the LWPDBName:dialog box, enter information about the new database
and associated user names and passwords, click Debug Mode in case errors
occur during the data transfer, and then click Next. The following table
includes examples of appropriate values for a Windows server.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:oracle:oci:
Use the alias specified for this database in the
@<tnsnames_entry_alias> tnsnames.ora file. This is usually the name of
the database; in this documentation the
database name and the tns alias are both
wps50.
LWPDBAdmin
User
ora92admin
LWPDBAdmin
Password
<ora92admin
_password>
Always type the password yourself, as the
default value may not be correct.
LWPDBApp
User
<Application
_User_Name>
Application user’s name. This value is case
sensitive.
LWPDBApp
Password
<Application
_User_Password>
Application user’s password. lways type the
password yourself, as the default value may
not be correct.
BackEndId
ORACLE_V9_1
Although you are using Oracle 9.2, this setting
refers to Oracle 9.1.
6. At the Do you wish the setup wizard to run these scripts now? dialog box,
start the database connection and transfer by clicking Next.
7. Click Finish to close the Configuration Wizard.
8. Review the logs from the Workplace Collaboration Services data transfer to
ensure all is well before proceeding to the next step; the logs are stored in the
\WebSphere\PortalServer\log directory.
9. Stop the Cloudscape Network Server, the WebSphere Portal Server, and the
WebSphere Application Server by running the following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./stopNetworkServer.sh
Microsoft Windows
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
254
Installation and Upgrade Guide
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./stopServer.sh server1
Windows
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
10. Validate that the transfer was successful by starting the WebSphere Portal
server without starting the Cloudscape server:
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
c. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh Mail_Server_1
Windows
startServer.bat Mail_Server_1
d. Close the command prompt window.
After you have successfully transferred Workplace Collaboration Services data to
the SQL Server database, proceed to Phase 6, ″Connecting to an external HTTP
server.″
Connecting to SQL Server
By default, each node in a Network Deployment installs with its own IBM
Cloudscape database. Because all the nodes in the Network Deployment need to
share a common data store, you must connect the node to a remote database
instead. This section explains how to connect the node to a remote Microsoft SQL
Server database and transfer locally hosted data from Cloudscape to SQL Server.
Before you begin this task, make sure that you have installed the SQL Server client
on the current node so it can communicate with the SQL Server database server.
You must connect to SQL Server and transfer two sets of data: IBM WebSphere
Portal Server data, and IBM Workplace Collaboration Services data. Complete these
tasks in the sequence shown:
1. Connect to SQL Server for WebSphere Portal Server.
Chapter 5 Connecting to a DBMS Server
255
2. Connect to SQL Server for Workplace Collaboration Services.
Connecting to SQL Server for WebSphere Portal Server:
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. Start the Cloudscape Network Server, start the WebSphere Application Server,
and start the WebSphere Portal server, by running the following commands.
a. Open a command window and navigate to the
<wp_root>\rootscripts\subtasks directory, where <wp_root> is the root
installation directory for WebSphere Portal.
b. Start the Cloudscape Network Server with the following case-sensitive
command:
startNetworkServer.bat
c. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
d. Start the IBM WebSphere Application Server with the following
case-sensitive command:
startServer.bat server1
e. Start the WebSphere Portal Server with the following case-sensitive
command:
startServer.bat WebSphere_Portal
2.
3.
4.
5.
6.
f. Close the command prompt window and return to the Configuration
Wizard.
In the Select the configuration task that you want to perform dialog box,
click Connect to a Database, and then click Next.
If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
If the Enter the LDAPAdminUID and password dialog box appears, type the
LDAP administrator account’s user name and password in the appropriate
fields, and then click Next.
In the Select the database type... dialog box, select Microsoft SQL Server
Enterprise, and then click Next.
In the Please enter an appropriate properties file location... dialog box,
browse or type the path to the SQL Server transfer helper file, and then click
Next. This file is usually stored in the following location:
<wp_root>\config\helpers\transfer_sqlserver.properties
where <wp_root> is the root WebSphere Portal installation directory; for
example, c:\WebSphere\PortalServer.
7. In the DBDriver: dialog box, type appropriate paths for the requested files,
and then click Next. The following table shows example values.
256
File
Example path
DBDriver
com.microsoft.jdbc
.sqlserver.SQLServerDriver
DBDriverDs
com.microsoft.jdbcx
.sqlserver.SQLServerDataSource
Installation and Upgrade Guide
Comments
File
Example path
Comments
DBLibrary
C:/MicrosoftSQLServer/lib
/msbase.jar;
C:/MicrosoftSQLServer/lib
/mssqlserver.jar;
C:/MicrosoftSQLServer/lib
/msutil.jar
Type all three paths into the field,
separating them with semi colons. Use a
forward slash between directories.
8. In the WpsDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
Comments
WpsDbName
wps50
DbUser
WPSDBUSER
DbPassword
<WPSDBUSER _password>
DbUrl
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
Always type the password yourself, as the
default value may not be correct.
9. In the WmmDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
Comments
WmmDb
Name
wps50
WmmDb
User
WMMDBUSER
WmmDb
Password
<WMMDBUSER _password>
WmmDb
Url
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure he
<server_DNS>:1433;DatabaseName=wps50
″DatabaseName″ setting appears only once
and has a semi colon (;) before it.
Always type the password yourself, as the
default value may not be correct.
10. In the WpcpDbName: dialog box, type appropriate values for the requested
information, and then click Next. The following table shows example values.
Field
Example Value
Comments
WpcpDb
Name
wps50
WpcpDb User
WCMDBADMIN
WpcpDb
Password
<WCMDBADMIN
_password>
WpcpDb Url
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
WpcpDb
EjbPassword
<password as set in SQL
Server login>
Always type the password yourself, as the
default value may not be correct.
WpcpDb
Pznadmin
Password
<password as set in SQL
Server login>
Always type the password yourself, as the
default value may not be correct.
Always type the password yourself, as the
default value may not be correct.
Chapter 5 Connecting to a DBMS Server
257
Field
Example Value
WpcpDb
HostName
<your server DNS>
Wpcp
ResourceUrl
WebSphere\
PortalServer\wpcp\
v5.0\runtime\lib
Comments
Use a single backslash between directories.
11. In the FeedbackDbName: dialog box, type appropriate values for the
requested information, and then click Next. The following table shows
example values.
Field
Example Value
Comments
FeedbackDb
Name
wps50
FeedbackDb
User
FEEDBACK
FeedbackDb
Password
<FEEDBACK _password>
FeedbackDb
Url
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
FeedbackDb
HostName
<server_DNS>
Always type the password yourself, as the
default value may not be correct.
12. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database transfer by clicking Next.
13. Return to the task selection dialog box (for the next task) by clicking Run
Wizard Again.
Tip: Review the logs from the database configuration to ensure all is well
before proceeding to the next task; the logs are stored in the
\WebSphere\PortalServer\log directory.
After you have successfully transferred the WebSphere Portal data to SQL Server,
proceed to the topic, ″Connecting to SQL Server for Workplace Collaboration
Services.″
Connecting to SQL Server for Workplace Collaboration Services:
Perform this task on the new Network Deployment node (which is hosting
Workplace Collaboration Services).
1. In the Select the configuration task that you want to perform dialog box,
click IBM Workplace Connect to Database, and then click Next.
2. In the Select the database type dialog box, select Microsoft SQL Server
Enterprise, and then click Next.
3. In the LWPDBDriver: dialog box, type enter the appropriate paths to the
relevant database files, and then click Next. The following table includes
examples of appropriate values for each field in the dialog box.
258
File
Example Path
LWPDBDriver
com.microsoft.jdbc
.sqlserver.SQLServerDriver
Installation and Upgrade Guide
Comments
File
Example Path
Comments
LWPDbLibrary
C:/MicrosoftSQLServer/lib
/msbase.jar;
C:/MicrosoftSQLServer/lib
/mssqlserver.jar;
C:/MicrosoftSQLServer/lib
/msutil.jar
Type all three paths into the field,
separating them with semi colons. Use a
forward slash between directories.
4. In the LWPDBNAME: dialog box, type the information about the new
database and associated user names and passwords, click Debug Mode in
case errors occur during the data transfer, and then click Next. The following
table includes examples of appropriate values for each field in the dialog box.
Field
Example Values
Comments
LWPDBNAME
wps50
LWPDBUrl
jdbc:microsoft:sqlserver://
Type the URL as a single entry; make sure
<server_DNS>:1433;DatabaseName=wps50
the ″DatabaseName″ setting appears only
once and has a semi colon (;) before it.
LWPDBAdmin
User
SQLSVRADMIN
LWPDBAdmin
Password
<SQLSVRADMIN
_password>
LWPDBApp
User
LWPCOMM
LWPDBApp
Password
<LWPCOMM _password>
BackEndId
MSSQLSERVER_V7_1
Always type the password yourself, as the
default value may not be correct.
Always type the password yourself, as the
default value may not be correct.
5. In the Do you wish the setup wizard to run these scripts now? dialog box,
start the database transfer by clicking Next.
6. Click Finish to close the Configuration Wizard.
7. Review the logs from the data transfer operation to ensure all is well before
proceeding to the next step. These logs are stored in the
\WebSphere\PortalServer\log directory.
8. If you used the default port of 1433 for your SQL Server database server
installation, skip this step and go directly to Step 10. If you used a custom
port, complete this step before proceeding to Step 10.
a. Open the WAS Administrator Console.
b. Click Resources.
c. Under Additional Properties, click WPCP50 JDBC.
d. Click Data Sources Version 4.
e. For each datasource listed (feedbackDS, persDS, and wcmDS), click
Custom Properties under the additional properties section:
v Click New to add a custom property.
v Add a property called portNumber, and type the non-zero standard port
number in use for SQL Server.
f. Save the entries and close the Administrative Console.
9. Stop the Cloudscape Network Server, the WebSphere Portal Server, and the
WebSphere Application Server by running the following commands.
a. Leave the Configuration Wizard running, and open a command prompt
window.
Chapter 5 Connecting to a DBMS Server
259
b. Navigate to the <wp_root>\rootscripts\subtasks directory, where <wp_root>
is the root installation directory for WebSphere Portal.
c. Stop the Cloudscape Network Server with the following case-sensitive
command:
IBM AIX, Linux, and Sun Solaris
./stopNetworkServer.sh
Microsoft Windows
stopNetworkServer.bat
d. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
e. Stop the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./stopServer.sh WebSphere_Portal
Windows
stopServer.bat WebSphere_Portal
f. Stop the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./stopServer.sh server1
Windows
stopServer.bat server1
g. Close the command prompt window and return to the Configuration
Wizard.
10. Validate that the transfer was successful by starting the WebSphere Portal
server without starting the Cloudscape server:
a. Navigate to the <iwp_root>\AppServer\bin directory, where <iwp_root> is
the root installation directory for Workplace Collaboration Services.
b. Start the WebSphere Portal Server with the following case-sensitive
command:
AIX, Linux, and Solaris
./startServer.sh WebSphere_Portal
Windows
startServer.bat WebSphere_Portal
c. Start the IBM WebSphere Application Server with the following
case-sensitive command:
AIX, Linux, and Solaris
./startServer.sh Mail_Server_1
Windows
startServer.bat Mail_Server_1
d. Close the command prompt window.
After you have successfully transferred Workplace Collaboration Services data to
the SQL Server database, proceed to Phase 6, ″Connecting to an external HTTP
server.″
260
Installation and Upgrade Guide
Chapter 6 Completing Setup of an External HTTP Server
This chapter describes how to configure IBM Workplace Collaboration Services and
the rich client provisioning server to run with a separate HTTP server rather than
using the internal HTTP server that comes with the product.
Phase 6: Completing setup of an external HTTP server
If you are deploying on IBM i5/OS and used the Create IBM Workplace
Collaboration Services wizard after installation, you have already created a local
external HTTP server. Only follow the instructions in this section if you did not
use the wizard after installation or if you now want to configure a remote external
HTTP server.
This section assumes that you have already performed the initial setup steps for
the HTTP server, as described in Phase 2.
Related concepts
Types of external HTTP servers
Setting up an external HTTP server
Related tasks
External HTTP server checklist
Starting and stopping the HTTP server
Accessing IBM Workplace Collaboration Services through an external HTTP
server
External HTTP server checklist
The following steps explain how to set up the HTTP server for IBM Workplace
Collaboration Services products or the provisioning server. Skip any steps that do
not apply to the type of HTTP server you are setting up. Each of these steps is
described in more detail in other topics. This assumes that you have already
installed and prepared the HTTP server, as described in Phase 2, ″Setting up an
external HTTP server.″
1. (Network Deployment) To load balance an HTTP server cluster, install
WebSphere Application Server Edge components on a separate machine.
2. Configure the HTTP server.
3. If this server will not be a provisioning server, proceed to the next step.
To set up a provisioning server, perform the following steps in the order
shown:
v Update the WebSphere Application Server plug-in if it hasn’t already been
done.
v Install the rich client provisioning server.
v Connect HTTP and SIP services on the provisioning server.
4. Connect Workplace servers to the external HTTP server.
In a Network Deployment environment, perform this step on Node 1 before
federating the node.
5. Connect Learning servers to the external HTTP server.
© Copyright IBM Corp. 2002, 2005
261
In a Network Deployment environment, perform this step on Node 1 before
federating the node.
6. Edit the URL resources for Workplace Collaborative Learning and the rich
client servers. In a Network Deployment environment, perform this step on
the Deployment Manager after federating the node.
7. Update the WebSphere Application Server plug-in to apply the configuration
changes and copy it to the HTTP server.
8. Restart the HTTP server.
9. (Network Deployment) Configure load balancing for SIP services and HTTP.
10. (Network Deployment) Update rich client configuration files.
Related concepts
“Preparing an external HTTP server” on page 65
Phase 6: Connecting to an external HTTP server
Types of external HTTP servers
Related tasks
Installing and configuring the provisioning server
Rich client installation and configuration checklist
Starting and stopping the HTTP server
Configuring the HTTP server
An HTTP server requires some custom settings when you set it up for IBM
Workplace Collaboration Services or the provisioning server. Follow the steps for
the HTTP server you installed.
Related tasks
Configuring IBM HTTP Server and Apache HTTP Server
Configuring Domino Enterprise Server
Configuring Microsoft Internet Information Services
Configuring Sun Java System Web Server
Configuring the Domino and Sun ONE Web Server for rich client download
External HTTP server checklist
Configuring IBM HTTP Server and Apache HTTP Server:
Follow these instructions to configure the httpd.conf file for IBM HTTP Server and
Apache HTTP Server.
1. Find the httpd.conf file, located in the <ihs_root>\conf directory and make a
backup copy of the file.
2. Open the original httpd.conf file for editing.
IBM AIX, Linux, Sun Solaris, and Microsoft Windows
Open the httpd.conf file in a text editor.
IBM i5/OS
Enter the following on an i5/OS command line:
EDTF ’<ihs_root>/conf/httpd.conf’
3. Add the following line to the file:
AddType application/zip zip jar
4. At the end of the file, add the lines that are appropriate for the HTTP Server
version you installed and for the platform on which it is running. <was_root> is
the WebSphere Application Server installation directory.
IBM HTTP Server 2.0.42.2 and 2.0.42.1 AIX, Linux, and Solaris
262
Installation and Upgrade Guide
LoadModule was_ap20_module
/<was_root>/bin/mod_was_ap20_http.so
WebSpherePluginConfig <was_root>/config/cells/plugin-cfg.xml
Windows
LoadModule was_ap20_module
"<drive>:\<was_root>\bin\mod_was_ap20_http.dll"
WebSpherePluginConfig "<drive>:\<was_root>\config\
cells\plugin-cfg.xml"
IBM HTTP Server 1.3.26.2 and 1.3.26.1
AIX, Linux, and Solaris
LoadModule ibm_app_server_http_module
/<was_root>/bin/mod_ibm_app_server_http.so
WebSpherePluginConfig <was_root>/config/cells/plugin-cfg.xml
Windows
LoadModule ibm_app_server_http_module
"<drive>:\<was_root>\bin\mod_ibm_app_server_http.dll"
WebSpherePluginConfig "<drive>:\<was_root>\config\
cells\plugin-cfg.xml"
IBM HTTP Server 2.0.49
IBM i5/OS
WebSpherePluginConfig <was_root>/config/cells/plugin-cfg.xml
LoadModule ibm_app_server_http_module
/QSYS.LIB/QEJBAS5.LIB/QSVTIHSAH.SRVPGM
Apache Versions 1.3.28 and 1.3.26
AIX, Linux, and Solaris
LoadModule app_server_http_module
/<was_root>/bin/mod_app_server_http.so
WebSpherePluginConfig <was_root>/config/
cells/plugin-cfg.xml
Windows
LoadModule app_server_http_module
"<drive>:\<was_root>\bin\mod_app_server_http.dll"
WebSpherePluginConfig "<drive>:\<was_root>\config\cells\
plugin-cfg.xml"
5. Save your changes and close the file.
Related tasks
Setting up an external HTTP server
Related reference
Root installation directories
Configuring Domino Enterprise Server:
Follow these instructions to enable the HTTP server to work with IBM Lotus
Domino Enterprise Server.
Note: The Domino Web Administrator interface may vary slightly depending on
which version of Domino you are using.
1. Start the Domino server.
Chapter 6 Completing Setup of an External HTTP Server
263
2. Start the Domino Web Administrator interface by accessing the file
/webadmin.nsf using a Web browser (for example,
http://hostname.yourco.com/webadmin.nsf). Type the short name for the
administrator and the administrator password when prompted.
3. Select the Configuration tab.
4. Select All Server Documents.
5. Double-click the server that you want to use with IBM Workplace
Collaboration Services.
6. Click Edit Server on the top-left of the center window.
7. Select the Internet Protocols tab.
8. Under DSAPI in the middle-right of the page, add the Domino Web Server
Application Programming Interface (DSAPI) filter file.
Note: If there are already DSAPI filter files specified, use a space to separate
the files.
IBM AIX, Linux, Sun Solaris, and Microsoft Windows
Add the path name to the Domino plug-in, which is installed in the
WebSphere Application Server bin directory.
IBM i5/OS
Add the following path:
/QSYS.LIB/QEJBAS5.LIB/LIBDOMINOH.SRVPGM
9. Click Save and Close on the upper-left of the center window.
10. Define the location of the plugin-cfg.xml configuration file.
IBM AIX, Linux, and Sun Solaris
Set the WAS_HOME environment variable to point to the WebSphere
Application Server installation root directory.
Microsoft Windows
Add the variable Plugin Config to the registry under the path name
HKEY_LOCAL_MACHINE → SOFTWARE → IBM → WebSphere Application
Server → 5.0.0.0. Set the value for this variable to the location of the
plugin-cfg.xml file, which is <was_root>\config\cells\plugin-cfg.xml.
IBM i5/OS
Define the location of the plugin-cfg.xml file in the NOTES.INI file. To edit the
NOTES.INI file, enter WRKDOMSVR on an i5/OS command line and enter 13
next to the server you want to work with. Add the following line at the end
of the file:
WebSphereInit=<was_root>/config/cells/plugin-cfg.xml
11. Restart the Domino server. When the server starts, information similar to the
following appears:
02/12/2005 03:05:09 PM JVM: Java virtual machine initialized
WebSphere Application Server DSAPI filter loaded
02/12/2005 03:05:10 PM HTTP Web Server started
Related tasks
Setting up an external HTTP server
Configuring Microsoft Internet Information Services:
Follow these instructions to configure Microsoft Internet Information Services (IIS).
1. Start the IIS application in Program → Admin tools → Internet Service Manager.
264
Installation and Upgrade Guide
2. Expand the tree on the left until you see Default Web Site.
3. Right-click Default Web Site and select New → Virtual Directory.
4. Using the wizard for adding a virtual directory, do the following:
a. In the Alias to be used to Access Virtual Directory field, type:
sePlugins
b. Browse to the WebSphere Application Server bin directory in the ″Enter the
physical path of the directory containing the content you want to publish″
field.
c. Check Allow Execute Access in the What access permissions do you want
to set for this directory field.
d. Click Finish to add the sePlugins virtual directory to your default Web site.
5. Right-click the host name in the tree on the left and click Properties.
6. Click the Internet Information Services tab, and then do the following steps:
a. Click WWW Service in the Master Properties window.
b. Click Edit to open the WWW Service Master Properties window.
c. Click ISAPI Filters → Add to open the Filter Properties window.
d. Type iisWASPlugin in the Filter Name field.
e. Click Browse in the Executable field.
f. Browse to the <was_root>\bin directory.
g. Click the iisWASPlugin_http.dll file.
h. Click OK until all open windows close.
7. Add the variable Plugin Config to the registry under the path
HKEY_LOCAL_MACHINE → SOFTWARE → IBM → WebSphere Application
Server → 5.0.0.0.
Set the value to the location of the configuration file, which is
<install_root>\config\cells\plugin-cfg.xml.
Related tasks
Setting up an external HTTP server
Configuring Sun ONE Web Server:
Follow these instructions to configure entries in the Sun ONE Web Server obj.conf
and magnus.conf configuration files for Version 6.0 and later of Sun ONE Web
Server.
1. Find the obj.conf file and make a backup copy of the file.
2. Use a text editor to open the original obj.conf file.
3. Add two directives to the obj.conf file after the <Object name=default> tag:
Service fn="as_handler"
AddLog fn="as_term"
4. Close and save the file.
5. Find the magnus.conf file and make a backup copy of the file.
6. Add the load-modules directive to the end of the file.
Init fn="load-modules"
funcs="as_init,as_handler,as_term"
shlib="<drive>:\WebSphere\AppServer\bin\libns41_http.dll"
7. Add the bootstrap.properties directive to the end of the file.
The location for the bootstrap.properties directive varies, depending on how
you have configured your system. For example:
Chapter 6 Completing Setup of an External HTTP Server
265
Local HTTP server
Init fn="as_init"
bootstrap.properties="/opt/IBM/WebSphere/AppServer/profiles/default/
config/cells/sa_cell/nodes/webserver1_node/servers/webserver1/
plugin-cfg.xml"
Remote HTTP Server
Init fn="as_init"
bootstrap.properties="/opt/IBM/WebSphere/Plugins/config
/webserver1/plugin-cfg.xml"
8. Close and save the file.
Related tasks
Setting up an external HTTP server
Configuring the Domino and Sun ONE Web server to enable rich client
download:
If you are using either a Domino Web server or Sun ONE Web server, you must
perform additional setup tasks to enable rich client users to download the rich
client installation program. By default, the HTTP server is configured for the IBM
HTTP server and Apache HTTP server. Other HTTP servers must be configured
properly to permit the user to download .exe, .bin and .jar file extensions. This
page describes the HTTP server configuration unique to Domino Web Server 5.0.9a
and Sun ONE Web Server Enterprise Edition 6.0 SP4.
To configure the Domino Web Server 5.0.9a, set the content root to <Domino
Install>:\Data\domino\html.
To configure the Sun ONE Web Server Enterprise Edition 6.0 SP4, set the content
root to <drive-name>:\iPlanet\Servers\docs and then add the following lines to the
<drive-name>:\iPlanet\Servers\https-<servername>\config\mime.types file:
type=application/octet-stream exts=bin,exe
type=application/java-serialized-object exts=ser
type=application/java-vm exts=class
type=application/msword exts=doc,dot,wiz,rtf
type=application/pdf exts=pdf
type=application/postscript exts=ai,eps,ps
type=application/vnd.ms-excel exts=xls,xlw,xla,xlc,xlm,xlt
type=application/vnd.ms-powerpoint exts=ppt,pps,pot
type=application/vnd.ms-project exts=mpp
type=application/winhlp exts=hlp
type=magnus-internal/cgi exts=cgi,bat
Related tasks
266
Installation and Upgrade Guide
Rich client installation and configuration checklist
Connecting HTTP and SIP services on the rich client
provisioning server
After you have installed the rich client provisioning server, make the following
changes to properties files on the provisioning server. If you are installing in a
Network Deployment environment, you only need to make the changes on the
HTTP server that serves as the provisioning server, not on the node servers.
For a Network Deployment environment, also see Updating rich client
configuration files for a Network Deployment environment.
1. In a text editor, open the pluginvalues.props file.
The file is located in the
<install_root>\AppServer\installedApps\yourNode\wctInstall.ear\wctinstall.war
directory; for example:
c:\WebSphere\AppServer\installedApps\node1\wctInstall.ear\wctinstall.war\pluginvalues.props
Note: For additional settings relative to rich client provisioning, see Setting
rich client installation program defaults.
2. Add the following parameter to activate IBM Workplace SIP services.
plugin_customization.SIPSERVER=yourAppServer
where yourAppServer is the fully qualified DNS name of the Workplace server
where SIP services have been installed. In a Network Deployment
environment, this is the fully qualified DNS name of the node.
3. Specify the HTTP port (if it is not a standard port) for the following line:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.port=port
where port is the non-standard port through which the HTTP server
communicates; for example:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.port=9809
In a Network Deployment environment, this is the HTTP port on the
Deployment Manager.
4. If you are editing the file on a Network Deployment node, replace the host
name with the fully qualified DNS name of the Deployment Manager for the
following line:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=
Deployment_Manager_DNS_name
5. Close and save the file.
6. Open the token-values.props file, which is located in the same directory as the
pluginvalues.props file.
Note: For additional settings relative to rich client provisioning, see “Setting
rich client installation program defaults” on page 323.
7. Change the value of host to be your HTTP server name, prefaced with the
protocol.
host=http://yourHTTPServer:port
where yourHTTPServer is the fully qualified DNS name of the external HTTP
server; for example, host=http://web1.acme.com. If you defined a port other
than 80 for the HTTP server, include the port number in the value.
Note: If you are working in an SSL-secured environment, change the value of
host to be your HTTPS server name, prefaced with the protocol.
Chapter 6 Completing Setup of an External HTTP Server
267
host=https://yourHTTPSServer:port
8. Change the value of host-name to be your WebSphere Application Server
name.
host-name=yourWASServer
9.
10.
11.
12.
where yourWASServer is the fully qualified DNS name of the WebSphere
Application Server that has the provisioning server software; for example,
host-name=provisioning.acme.com. In a Network Deployment environment,
this value is the fully qualified DNS name of the Deployment Manager.
Close and save the file.
Create a directory called wctprops under the http directory (for example,
c:\IBMHTTPServer\htdocs\en_US\wctprops).
Copy the fileList.props, pluginvalues.props and token-values.props files to the
wctprops directory.
Stop the IBM HTTP server.
13. Set the following values in the httpd.conf file:
v KeepAlive = On
v KeepAliveTimeout = 5
v MaxKeepAliveRequests = 0
v MaxRequestsPerChild = 0
14. Turn off HTTP access logging by commenting out the logs/access.log line as
shown below:
# The location of the access log file (Common Logfile Format).
# If this does not start with /, ServerRoot is prepended to it.
# Comment out the below line:
# CustomLog logs/access.log common
15. Close and save the file.
16. Restart the IBM HTTP server.
Related tasks
External HTTP Server checklist
Rich client installation and configuration checklist
Installing and configuring the provisioning server
Updating the WebSphere Portal EAR file for Network Deployment
Connecting Workplace servers to an external HTTP server
Workplace server settings need to be updated to connect to an external HTTP
server.
Follow the instructions for the type of server you are setting up:
v Single server
v Node 1
v Node 2 and subsequent nodes
Related tasks
External HTTP server checklist
Connecting a single Workplace server to an external HTTP server:
Workplace server settings need to be updated to connect to an external HTTP
server. Follow the instructions for the platform you are running on.
268
Installation and Upgrade Guide
Note: If you are deploying on IBM i5/OS and used the Create IBM Workplace
Collaboration Services wizard after installation, these steps were done for
you for a local external HTTP server. Only follow the instructions in this
section if you did not use the wizard after installation or if you now want to
configure a remote external HTTP server.
Single Workplace server (AIX, Linux, Solaris):
Change settings by editing the wpconfig.properties and then running a
configuration script to update the IBM Workplace Collaboration Services database
with the new settings.
1. Make a backup copy of the following files:
v <install_root>/AppServer/config/cells/<CellName>/resources.xml
v <install_root>/PortalServer/config/wpconfig.properties
v All files in <install_root>/WorkplaceServer/properties
2. Using a text editor, update the original wpconfig.properties file as follows.
Property
Description
WpsHostName
If you are using a local HTTP server, this value is the host name
of the Workplace Collaboration Services machine. If you are using
a remote HTTP server, this value is the host name of the machine
where you installed the HTTP server; for example,
web1.acme.com.
WpsHostPort
This is the port number that your HTTP server uses to listen for
HTTP traffic. For an external HTTP server, change this from the
default 9081 to 80, unless you have set up a port other than 80 for
HTTP traffic.
3. Verify that other settings in the wpconfig.properties file are correct, then save
the file.
4. Run the WPSconfig script to read the values in the wpconfig.properties file and
perform configuration functions based on these values.
a. Verify that the HTTP server is running.
b. Shut down Workplace Collaboration Services.
c. Run the appropriate command for your operating system.
From the <install_root>/AppServer/bin directory, enter:
./setupCmdLine.sh
d. Change to the <install_root>/PortalServer/config directory and enter the
following command on one line:
./WPSconfig.sh lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password>
>httpsettings.log
where
v DLWPDBAdminUser and DLWPDBAdminPassword are the name and
password of the database administrator. If you are using the default IBM
Cloudscape database, use ″lwpadmin″ for both values.
v DLWPDBAppUser and DLWPDBAppPassword are the name and password
of the administrator of the WebSphere Portal wps50 database.
e. Check the log file httpsettings.log to make sure the update completed
successfully.
Single Workplace server (Windows):
Chapter 6 Completing Setup of an External HTTP Server
269
Change settings by editing the wpconfig.properties and then running a
configuration script to update the IBM Workplace Collaboration Services database
with the new settings.
1. Make a backup copy of the following files:
v <install_root>\AppServer\config\cells\<CellName>/resources.xml
v <install_root>\PortalServer\config\wpconfig.properties
v All files in <install_root>\WorkplaceServer\properties
2. Using a text editor, update the original wpconfig.properties file as follows, then
save the file.
Property
Description
WpsHostName
If you are using a local HTTP server, this value is the host name
of the Workplace Collaboration Services machine. If you are using
a remote HTTP server, this value is the host name of the machine
where you installed the HTTP server; for example,
web1.acme.com.
WpsHostPort
This is the port number that your HTTP server uses to listen for
HTTP traffic. For an external HTTP server, change this from the
default 9081 to 80, unless you have set up a port other than 80 for
HTTP traffic.
3. Verify that other settings in the wpconfig.properties file are correct, then save
the file.
4. Run the WPSconfig script to read the values in the wpconfig.properties file and
perform configuration functions based on these values.
a. Verify that the HTTP server is running.
b. Shut down Workplace Collaboration Services.
c. From the <install_root>\AppServer\bin directory, enter:
setupCmdLine.bat
d. Change to the <install_root>\PortalServer\config directory and enter the
following command on one line:
WPSconfig.bat lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password>
>httpsettings.log
i5/OS
WPSconfig.sh lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password> >httpsettings.log
where
v DLWPDBAdminUser and DLWPDBAdminPassword are the name and
password of the database administrator. If you are using the default IBM
Cloudscape database, use ″lwpadmin″ for both values.
v DLWPDBAppUser and DLWPDBAppPassword are the name and password
of the administrator of the WebSphere Portal wps50 database.
e. Check the log file httpsettings.log to make sure the update completed
successfully.
Single Workplace server (i5/OS):
270
Installation and Upgrade Guide
Change settings by editing the wpconfig.properties and then running a
configuration script to update the IBM Workplace Collaboration Services database
with the new settings.
1. Make a backup copy of the following files:
v <install_root>/AppServer/config/cells/<CellName>/resources.xml
v <install_root>/PortalServer/config/wpconfig.properties
v All files in <install_root>/WorkplaceServer/properties
2. Using a text editor, update the original wpconfig.properties file as follows, then
save the file.
Property
Description
WpsHostName
If you are using a local HTTP server, this value is the host name
of the Workplace Collaboration Services machine. If you are using
a remote HTTP server, this value is the host name of the machine
where you installed the HTTP server; for example,
web1.acme.com.
WpsHostPort
This is the port number that your HTTP server uses to listen for
HTTP traffic. For an external HTTP server, change this from the
default 9081 to 80, unless you have set up a port other than 80 for
HTTP traffic.
3. Run the WPSconfig script to read the values in the wpconfig.properties file and
perform configuration functions based on these values.
a. Verify that the HTTP server is running.
b. Shut down Workplace Collaboration Services.
c. tart the QShell interpreter by entering the following on an i5/OS command
line:
STRQSH
d. Change to the <install_root>/PortalServer/config directory and enter the
following command on one line:
WPSconfig.sh lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password> >httpsettings.log
where
v DLWPDBAdminUser and DLWPDBAdminPassword are the name and
password of the database administrator. If you are using the default IBM
Cloudscape database, use ″lwpadmin″ for both values.
v DLWPDBAppUser and DLWPDBAppPassword are the name and password
of the administrator of the WebSphere Portal wps50 database.
e. Check the log file httpsettings.log to make sure the update completed
successfully.
Related tasks
Connecting Workplace servers to an external HTTP server
Related reference
Root installation directories
Connecting Node 1 to an external HTTP server:
Workplace server settings need to be updated to connect to an external HTTP
server. Follow these instructions to connect Node 1 in a Network Deployment to
an external HTTP server.
Chapter 6 Completing Setup of an External HTTP Server
271
Change settings by editing the wpconfig.properties and lwpae.properties files and
then running a configuration script to update the IBM Workplace Collaboration
Services database with the new settings. Make these changes before federating the
node.
1. Make a backup copy of the following files:
v <install_root>\AppServer\config\cells\<CellName>\resources.xml
v <install_root>\PortalServer\config\wpconfig.properties
v All files in <install_root>\WorkplaceServer\properties
2. Using a text editor, update the original wpconfig.properties file as follows.
Property
Description
WpsHostName
If you are using a local HTTP server, this value is the host name
of the Workplace Collaboration Services machine. If you are using
a remote HTTP server, this value is the host name of the machine
where you installed the HTTP server; for example,
web1.acme.com.
WpsHostPort
This is the port number that your HTTP server uses to listen for
HTTP traffic. For an external HTTP server, change this from the
default 9081 to 80, unless you have set up a port other than 80 for
HTTP traffic.
3. Verify that other settings in the wpconfig.properties file are correct, then save
the file.
4. Activity Explorer uses the WebSphere Portal Content Publisher (WPCP)
document library to store shared files. By default, the Workplace server is
configured to receive messages for WPCP on port 9081. If a firewall blocks
communications that are destined for port 9081, Activity Explorer cannot create
shared files without the modifications to the lwpae.properties file described
below.
Using a text editor, open the
<install_root>\WorkplaceServer\properties\lwpae.properties file,delete the port
number from the wpcp.serverUrl property, then save the file.
For example, change:
wpcp.serverUrl=http://server.yourco.com:9081/lwp/wcp
to
wpcp.serverUrl=http://server.yourco.com/lwp/wcp
5. Run the WPSconfig script to read the values in the wpconfig.properties file and
perform configuration functions based on these values.
a. Verify that the HTTP server is running.
b. Shut down Workplace Collaboration Services.
c. Run the appropriate command for your operating system.
IBM AIX, Linux, and Sun Solaris
From the <install_root>/AppServer/bin directory, enter:
./setupCmdLine.sh
Windows
From the <install_root>\AppServer\bin directory, enter:
setupCmdLine.bat
d. Change to the <install_root>\PortalServer\config directory and enter the
following command on one line:
AIX, Linux, and Solaris
272
Installation and Upgrade Guide
./WPSconfig.sh lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password>
>httpsettings.log
Windows
WPSconfig.bat lwp-httpserver-config -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPDBAppUser=<db_app_user>
-DLWPDBAppPassword=<db_app_user_password>
>httpsettings.log
e. Check the log file httpsettings.log to make sure the update completed
successfully.
Related tasks
Connecting Learning servers to an external HTTP server
Updating the WebSphere Application Server plug-in
Connecting Workplace servers to an external HTTP server
Related reference
Root installation directories
Connecting Node 2 and subsequent nodes to an external HTTP server:
Workplace server settings need to be updated to connect to an external HTTP
server. Follow these instructions to connect Node 2 and subsequent nodes in a
Network Deployment to an external HTTP server.
Change settings by updating the Workplace properties files. Make these changes
before federating the node.
1. Open the following files in a text editor. They are located in the
<install_root>\WorkplaceServer\properties directory.
Note: Use an editor other than the UNIX® editor vi to edit these files. When a
line exceeds the maximum buffer size of 2048 characters (as it does in
the lwptaistorage.properties file), your changes will be saved in a
truncated and incorrect form.
v lwpae.properties
v lwpagenda.properties
v lwpchatroom.properties
v lwpformsstorage.properties
v lwplistadapter.properties
v lwppdmadapter.properties
v lwptaistorage.properties
v lwpteamtasklist.properties
v lwpworkplaceurl.properties
2. For each http value, replace the <node host name> with the <HTTP server host
name>, then save each file.
If you are using a local HTTP server, this value is the host name of the
Workplace Collaboration Services machine. If you are using a remote HTTP
server, this value is the host name of the machine where you installed the
HTTP server; for example, web1.acme.com. For an external HTTP server,
specify a port of 80 (from the default 9081), unless you have set up a port other
than 80 for HTTP traffic. For example, web1.acme.com:80.
3. Activity Explorer uses the WebSphere Portal Content Publisher (WPCP)
document library to store shared files. By default, the Workplace server is
Chapter 6 Completing Setup of an External HTTP Server
273
configured to receive messages for WPCP on port 9081. If a firewall blocks
communications that are destined for port 9081, Activity Explorer cannot create
shared files without the modifications to the lwpae.properties file described
below.
Using a text editor, open the
<install_root>/WorkplaceServer/properties/lwpae.properties file,delete the port
number from the wpcp.serverUrl property, then save the file.
For example, change:
wpcp.serverUrl=http://server.yourco.com:9081/lwp/wcp
to
wpcp.serverUrl=http://server.yourco.com/lwp/wcp
Related tasks
Connecting Workplace servers to an external HTTP server
Related reference
Root installation directories
Connecting Learning servers to an external HTTP server
Take the following steps to ensure that course content is available to users and that
IBM Workplace Collaborative Learning connects to the external HTTP server.
v Create a course directory on the content server.
v Add the content server to the dbbuild.properties file.
v Run the updateSettings script to update the Workplace Collaboration Services
database.
Note: If you used the Create IBM Workplace Collaboration Services wizard to
configure Collaborative Learning on i5/OS, these settings are automatically
updated for your deployment. In most cases, you do not have to update the
settings manually.
The wizard is described in Chapter 3.
Before performing these steps, you should have completed the steps in
″Connecting Workplace servers to an external HTTP server.″
Creating a course directory on the content server:
If the external HTTP server will be a course content server for Workplace
Collaborative Learning, set up the following directory structure.
1. Create a content directory off the HTTP server default content directory, for
example:
<ihs_root>\htdocs\en_US\content\
2. Copy any course content you already have to the new content directory.
For example, if you previously used the built-in internal HTTP server for
Workplace Collaborative Learning, existing content would be located in:
<install_root>\AppServer\installedApps\cell_name\LWP_LMS_DS.ear\dsWeb.war\content
Adding the content server to the dbbuild.properties file:
The dbbuild.properties file on the Workplace server is used to populate the IBM
Workplace Collaboration Services database. Follow these steps to add information
about the content servers and to change any default installation values that are not
274
Installation and Upgrade Guide
correct for your site. In a Network Deployment environment, perform this step
only on Node 1; do so before federating the node.
Syntax rules
v Do not enclose any value in quotation marks.
v Microsoft Windows path names can use either forward slashes (/) or double
back slashes (\\).
v Windows long path names (directory names and file name containing more than
8 characters) are acceptable.
Editing the file
1. Use a text editor to open the dbbuild.properties file, which is located in the
<install_root>\WorkplaceServer\config\database directory.
2. Make a backup copy of the installed version of the dbbuild.properties file and
name it dbbuild.old.
You can revert to this version if necessary.
3. Edit or add the lmscontent_serversnn setting. Appropriate values are described
in ″Learning settings in the dbbuild.properties file.″
Remove ″/lms-ds″ from the value; for example:
lmscontent_servers0=CS00,1,/<ihs_root>/htdocs/content
4. Update the lmscontent_base_url setting to match the content server URL.
lmscontent_base_url=http://contentserverURL/content
Note: If you have multiple content servers, set them up to be accessed through
this single URL.
5. Update any other Learning settings to be accurate for your deployment.
For more information, see ″Learning settings in the dbbuild.properties file.″
6. Save the revised version of the file.
Running the updateSettings script to update the Workplace Collaboration
Services database:
Verify that the properties in the dbbuild.properties are correct, then follow these
steps to run the LWPdbconfig configuration script.The script reads the values of
properties in the dbbuild.properties file and performs configuration functions
based on those values. In a Network Deployment environment, perform this step
only on Node 1; do so before federating the node.
1. Shut down the Workplace server and, if applicable, Cloudscape.
2. Run the appropriate command for your operating system.
IBM AIX, Linux, and Sun Solaris
From the <install_root>/AppServer/bin directory, enter:
./setupCmdLine.sh
Microsoft Windows
From the <install_root>\AppServer\bin directory, enter:
setupCmdLine.bat
IBM i5/OS
Start the QShell interpreter by entering the following on an i5/OS command
line:
STRQSH
Chapter 6 Completing Setup of an External HTTP Server
275
3. Change to the <install_root>\WorkplaceServer\config directory and enter the
following command on one line:
IBM AIX, Linux, and Sun Solaris
./LWPdbconfig.sh updateSettings -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPAppUser=<db_app_user>
-DLWPAppPassword=<db_app_user_password> >updatesettings.log
Microsoft Windows
LWPdbconfig.bat updateSettings -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPAppUser=<db_app_user>
-DLWPAppPassword=<db_app_user_password> >updatesettings.log
IBM i5/OS
LWPdbconfig.sh updateSettings -DLWPDBAdminUser=<admin_user>
-DLWPDBAdminPassword=<password> -DLWPAppUser=<db_app_user>
-DLWPAppPassword=<db_app_user_password> >updateSettings.log
where
v DLWPDBAdminUser and DLWPDBAdminPassword are the name and password
of the database administrator. If you are using the default IBM Cloudscape
database, use ″lwpadmin″ for both values.
v DLWPAppUser and DLWPAppPassword are the name and password of the
administrator of the WebSphere Portal wps50 database.
4. Check the log file updatesettings.log to make sure the update completed
successfully.
Connecting Workplace servers to an external HTTP server
Learning settings in the dbbuild.properties file
External HTTP server checklist
Learning settings in the dbbuild properties file:
The following table of IBM Workplace Collaborative Learning properties shows the
default values set by the installation program and indicates which settings need to
be changed if you set up an external HTTP server. It uses the following
abbreviations:
Abbreviation
Description
<WpsHost>
Fully qualified name of the Workplace
server (for example, workplace.acme.com).
<Port>
The port to be used. The Workplace server
default port is usually 9081 and the HTTP
server default port is usually 80.
<WasHome>
WebSphere Home directory (for example,
C:/WebSphere/AppServer).
<CellName>
WebSphere cell name (usually same as host
name; for example, mylwpserver).
Learning Property
Default Value
lmmserver_admin_name wpsadmin
276
Installation and Upgrade Guide
Comments
The Collaborative Learning
administrator name. Change if you
want to use another administrator
name.
Learning Property
Default Value
lmmserver_url
Comments
To set up an external HTTP server, this
value must be changed to:
lmmserver_url=
http://<Http_Server_Host_Name>:<Port>
The change is made automatically if
you follow the procedure described in
Phase 6, ″Connecting Workplace
servers to an external HTTP server.″
If you configure Collaborative
Learning to use SSL, change the
protocol from ″http″ to ″https.″
lmmserver_context_root lms-lmm
The Learning Server context root.
lmmserver_description
Learning LMS Server
A description of the Learning Server,
such as its name, location or IP address
(optional).
lmmserver_username
lwplms
The name used by the Learning Server
to authenticate with Delivery Servers
for Web services. This name does not
need to exist in any user directory.
lmmserver_password
lwplms
The password used by the Learning
Server to authenticate with Delivery
Servers for Web services.
lmmserver_course
Packages_dir
On a Microsoft
Windows server, the
default is:
Path where imported course packages
should be stored.
c:/WebSphere/
WorkplaceServer/
Learning/lms_courses
Note If you are installing in a Network
Deployment, specify the mapped drive
and path name to the shared directory
called ″lms_courses″ that you created
before installation; for example:
G:\lms_courses.
lmmserver_content
Manager_ email
text/plain
E-mail format used by Content
Manager to send e-mail notifications
regarding imported course packages.
The possible values are ″text/plain″
and ″text/html.″
lmmserver_juru_path
On a Windows server,
the default is:
Juru search index directory
c:/WebSphere/
WorkplaceServer
/Learning/lms_juru
Note If you are installing in a Network
Deployment, specify the mapped drive
and path name to the shared directory
called ″lms_juru″ that you created
before installation; for example:
G:/lms_juru.
Chapter 6 Completing Setup of an External HTTP Server
277
Learning Property
Default Value
Comments
lmscontent_base_url
The default is:
The Web address where the Delivery
Server looks for content when it opens
a course; for example,
http://contentserver.acme.com/content.
http://<WpsHost>
:<Port>/lms-ds/
content
By default after installation,
Collaborative Learning uses the
WebSphere Application Server internal
HTTP server as a content server, but
you should set up an external HTTP
server for better performance.
The external HTTP server to be used
as a content server may be located on
the same machine as the Workplace
server or it can be on a separate
machine. There is no requirement that
the external HTTP server used as a
content server be the same HTTP
server as the one used by Workplace
Collaboration Services products, but
usually it is the same.
To set up an external HTTP server,
remove ″/lms-ds″ from the value; for
example:
http://web1.acme.com/content.
If you configure Collaborative
Learning to use SSL, change the
protocol from ″http″ to ″https.″
dsserver_url
To set up an external HTTP server, this
value must be changed to:
dsserver_url=
http://<Http_Server_Host_Name>:<Port>
The change is made automatically if
you follow the procedure described in
Phase 6, ″Connecting Workplace
servers to an external HTTP server.″
If you configure Collaborative
Learning to use SSL, change the
protocol from ″http″ to ″https.″
278
dsserver_context_root
lms-ds
The Delivery Server context root.
dsserver_id
DS1
A text string that identifies this
Delivery Server when you deploy
courses or manage servers using the
Learning Server user interface.
dsserver_description
Learning Delivery
Server 1
A description of the Delivery Server,
such as its name, location or IP address
(optional).
dsserver_username
lwplds
The name used by the Delivery Server
to authenticate with the Learning
Server. This name does not need to
exist in any user directory.
Installation and Upgrade Guide
Learning Property
Default Value
Comments
dsserver_password
lwplds
The password used by the Delivery
Server to authenticate with the
Learning Server.
dsserver_admin_emailTo There is no default
value, but notifications
can be sent to the
administrator without
one.
System administrator e-mail to
address. System e-mail notifications are
sent to the ″to″ address.
dsserver_admin_
emailFrom
There is no default
value, but notifications
can be sent from the
administrator without
one.
System administrator e-mail from
address. System e-mail notifications
show the ″from″ address as the sender.
dsserver_admin_
emailType
text/plain
E-mail format used by Delivery Server
to send e-mail notifications. The
possible values are ″text/plain″ and
″text/html.’
Chapter 6 Completing Setup of an External HTTP Server
279
Learning Property
Default Value
Comments
lmscontent_servers0
The default is:
Specifies the transport method and
location for courses delivered from the
content server to the Delivery Server:
the local file system or FTP. All content
servers must be accessible through the
single URL specified by
lmscontent_base_url. Verify that the
value is complete and correct before
running the lwp-http-config or
LWPdbconfig updatesettings scripts.
CS00,1,<WasHome>
/installedApps/
<CellName>
/LWP_LMS_DS.ear/
dsWeb.war/content
″1″ as the second argument indicates
File System. This method is
recommended if the HTTP server is
local (meaning it is installed on the
same machine as IBM Workplace
Collaboration Services) using either the
internal HTTP transport or an external,
local HTTP server.
For example:
lmscontent_servers0=CS00,1,
C:/IBM HTTP Server2.0/
htdocs/en_US/content
″0″ as the second argument indicates
FTP. This method is recommended
when the content server is remote (on
a separate machine from Workplace
Collaboration Services). However, this
method can also be used if the content
server is local. Each server’s property
must contain the appropriate FTP user
name and password for that server.
Examples:
First or only content server
lmscontent_servers0=CS00,0,,
ftp://content1.acme.com,
ftpadmin,ftppassword.
Additional content servers (up to 100):
lmscontent_servers1=CS00,0,,
ftp://content2.acme.com,
ftpadmin2,ftppassword2.
...
lmscontent_servers99=CS00,0,,
ftp://content100.acme.com,
ftpadmin100,ftppassword100.
For more information about configuring Collaborative Learning to use SSL, see the
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related tasks
280
Installation and Upgrade Guide
Connecting Learning servers to an external HTTP server
Editing Learning and rich client URL resources
Use the WebSphere Administrative Console to update the URL resources for IBM
Workplace Collaborative Learning and the rich client servers.
Editing URL resources for Workplace Collaborative Learning:
Make these changes in the URL resources on the Workplace server. In a Network
Deployment, make these changes on the Deployment Manager after federating
nodes to the cluster.
1. From the WebSphere Administrative Console, click Resources → URL Providers.
2. Switch to the cell level and click Default URL Provider → URLs.
3. Click LMS_URL.
4. Update the URL to use the value of your HTTP server (for example,
http://web1.acme.com/lms-lmm).
Note: Removing the port number (9081) from the URL assumes that the
external HTTP server uses port 80. If the HTTP server uses a different
port number, you should replace :9081 with the specific port number.
5. Save your changes.
Editing URL resources for the provisioning server:
Make these changes in the URL resources on the provisioning server. In a Network
Deployment, make these changes on the Deployment Manager after federating
nodes to the cluster.
1. From the WebSphere Administrative Console, click Resources → URL Providers.
2. Clear the node value, and click Apply.
3. Click Default URL Provider.
4. Click Additional Properties → URLs.
5. Click Workplace Client Installer Download Server and update the URL to use
the value of your HTTP server (for example, http://web1.acme.com)
6. Click OK.
7. From the Additional Properties - URL page, click Workplace Client
Provisioning Server.
8. Change the specification value to be the URL of your HTTP server (for
example, http://web1.acme.com/lwpupdate/wct).
9. Save your changes.
Related concepts
Setting up an external HTTP server
Related tasks
Opening the WebSphere Administrative Console
“Phase 9: Completing Network Deployment setup” on page 337
Updating the WebSphere Application Server plug-in
This section describes how to regenerate the WebSphere Application Server plug-in
to provide the HTTP server with the latest settings. Do this step before you install
a rich client provisioning server or when you have completed making changes to
Chapter 6 Completing Setup of an External HTTP Server
281
the HTTP configuration file (including any optional ones you made to improve
performance for the provisioning server). Follow the instructions that apply to the
type of deployment you have.
Updating the plug-in for a single Workplace server or the provisioning server:
If you are setting up an HTTP server for use in a single-server or IBM i5/OS
deployment or for use with the rich client provisioning server, follow these steps.
1. On the machine on which IBM Workplace Collaboration Services or the
provisioning server is installed, start WebSphere Application Server.
2. Open the WebSphere Application Server Administrative Console.
3. Choose Environment → Update Web Server Plugin, then click OK.
4. (Remote HTTP server) Copy the updated HTTP plug-in (plugin-cfg.xml) from
the WebSphere Application Server to the remote HTTP server directory.
Updating and distributing the plugin-cfg.xml file in a Network Deployment:
You must place an updated version of the Deployment Manager plugin-cfg.xml file
on the remote HTTP server and on all nodes in the Network Deployment. Follow
these steps to create the plugin-cfg.xml file, and then distribute it. Perform this
step as part of completing Network Deployment setup, after you have federated
and clustered the nodes.
1. On the Deployment Manager, open a command prompt window and navigate
to the <wp_root>\bin directory.
2. Type the following command to create the plugin-cfg.xml file:
IBM AIX, Linux, and Sun Solaris
./lwpGenPluginCfg.sh >lwpgenplugin.log
Microsoft Windows
lwpGenPluginCfg.bat >lwpgenplugin.log
3. Find the plugin-cfg.xml file on the Deployment Manager in one of the
following locations:
AIX, Linux, and Solaris
/opt/WebSphere/DeploymentManager/config/cells/plugin-cfg.xml
Windows
c:\WebSphere\DeploymentManager\config\cells\plugin-cfg.xml
4. Copy the plugin-cfg.xml file to the remote HTTP server’s
<was_root>\config\cells directory.
5. Open the plugin-cfg.xml file with a text editor.
6. Replace all instances of ″DeploymentManager″ with ″AppServer.″
7. Save the file.
8. Copy the updated plugin-cfg.xml file from the remote HTTP server to Node 1.
9. Repeat the previous step for all other nodes in the environment.
10. Stop and restart the HTTP server.
For example, if you are using IBM HTTP Server, use one of the following
commands:
AIX, Linux, and Solaris
/<ihs_root>/bin/apachectl start
Windows
c:\<ihs_root>\apache -k start
282
Installation and Upgrade Guide
11. From the Deployment Manager Administrative Console, click Servers →
Clusters → Server Cluster and start the cluster you defined for Workplace
Collaboration Services.
Related concepts
Setting up an external HTTP server
Related tasks
Opening the WebSphere Administrative Console
Accessing IBM Workplace Collaboration Services through an
external HTTP server
With an external HTTP server connection, the port for accessing IBM Workplace
Collaboration Services changes from 9081 to the default port of 80. Unless you’ve
defined a port other than 80 for the HTTP server, the URL does not need to specify
a port.
1. To access Workplace Collaboration Services, type the following URL:
http://servername.yourcompany.com/lwp/workplace
2. To access the IBM Workplace Collaborative Learning administrator interface,
type the following URL:
http://servername.yourcompany.com/lms-lmm
Related concepts
Phase 6: Setting up an external HTTP server
Chapter 6 Completing Setup of an External HTTP Server
283
284
Installation and Upgrade Guide
Chapter 7 Completing IBM Workplace Collaborative Learning
Setup
This chapter describes how finish setting up IBM Workplace Collaborative
Learning after you have installed and configured IBM Workplace Collaboration
Services and, optionally, configured an external HTTP server.
Phase 7: Completing IBM Workplace Collaborative Learning Setup
For IBM i5/OS deployments, skip this phase if you used the Create IBM
Workplace Collaboration Services wizard to configure IBM Workplace
Collaborative Learning. If you did not use the wizard, or if you wish to change
your Learning settings, install and configure Virtual Network Computing on your
system before performing the following tasks.
For more information, see ″Configuring IBM Workplace Collaboration Services″ in
Chapter 3.
For all other platforms, finish setting up Collaborative Learning by performing the
following tasks:
v Update Learning settings in the dbbuild.properties file.
In a Network Deployment environment, do this on Node 1.
v Grant Learning access to the WebSphere Portal administrator.
In a Network Deployment environment, do this on Node 1.
v Connect Collaborative Learning portlets to a remote Learning Server.
In a Network Deployment environment, do this on Node 1.
v Set up access control for Collaborative Learning portlets.
In a Network Deployment environment, do this on Node 1.
v Enable reporting on IBM AIX, Linux, Sun Solaris, and i5/OS.
In a Network Deployment environment, do this on Node 1 and all subsequent
nodes.
v Configure help for the Collaborative Learning administrator interface for AIX,
Linux, Solaris, or Microsoft Windows or i5/OS.
In a Network Deployment environment, perform these steps after you have
finished setting up the Network Deployment and the Workplace server cluster is
operational.
For more information about managing Collaborative Learning, see the IBM
Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Related tasks
Configuring Virtual Network Computing (i5/OS only)
© Copyright IBM Corp. 2002, 2005
285
Granting Learning access to the WebSphere Portal
administrator
When you install IBM Workplace Collaborative Learning, the WebSphere Portal
″wpsRunAsAdmin″ administrator role is automatically set to the user name
″wpsadmin.″ As a result, if a course uses a Discussion database, only the course
creator can enroll.
Complete the following steps to grant Learning access to any WebSphere Portal
administrator. In a Network Deployment environment, do this on Node 1.
1. Log in to the WebSphere Administrative Console.
2. Click Applications → Enterprise Applications → LWP_LMS_LMM.
3. Click Map RunAs roles to users.
4. Select the check box near wpsRunAsAdmin, and then click Remove to delete
″wpsadmin″ as the user value.
5. Click OK, then click Save, and then click Save again when you are prompted
to confirm.
6. Click Applications → Enterprise Applications → LWP_LMS_LMM.
7. Click Map security roles to users/groups.
8. Select the check box near wpsRunAsAdmin, and then click the Lookup users
button.
9. Locate the WebSphere Portal administrator user name and add it to the
wpsRunAsAdmin role.
10. Click OK, click OK again, click Save, and then click Save again when you are
prompted to confirm.
11. Select Applications → Enterprise Applications → LWP_LMS_LMM.
12. Click Map RunAs roles to users.
13. Select the check box near wpsRunAsAdmin, and then type the WebSphere
Portal administrator’s user name and password in the appropriate fields.
14. Click Apply.
15. Click OK, then click Save, and then click Save again when you are prompted
to confirm.
16. Restart the server.
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Related tasks
Opening the WebSphere Administrative Console
Connecting Learning portlets to a remote Learning Server
If you installed IBM Workplace Collaborative Learning on a different node from
the Learning server, add a Web address on the portlet server to allow the
Collaborative Learning portlets to communicate with the Learning Server through
Web services. In a Network Deployment environment, do this on Node 1.
1. On the server where the Collaborative Learning portlets are installed, open the
WebSphere Administrative Console.
2. Open the URLs list (Resources → URL Providers → Switch to cell level →
Default URL Provider → URLs).
286
Installation and Upgrade Guide
3. Change the specification value of LMS_URL to be the Web address of the
Learning Server (for example, http://http.ibm.com/lms-lmm).
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Related tasks
Opening the WebSphere Administrative Console
Setting up access control for IBM Workplace Collaborative
Learning portlets
To give certain users access to the Configure Mode of Collaborative Learning
portlets, you can assign them administrator access. In a Network Deployment
environment, do this on Node 1.
Use the following procedure to set up access to the Collaborative Learning portlets:
1. In the WebSphere Portal Administration area, go to the User and Group
Permissions selection.
2. Select Users to set access control for an individual user or select User Groups
to set access control for entire groups.
3. Find the users or groups whose access you want to modify and click Select
Resource Type to display a list of resources. You must modify the Pages and
Portlet Applications entries.
4. Select Pages and browse the page hierarchy until you see the Learning page.
5. At the Learning page entry, click Assign Access.
For students, select Privileged User access. Anything above Privileged User in
the list corresponds to higher access. Make sure that no higher level access is
granted to student. The value set here can be inherited from pages up higher in
the hierarchy, meaning that you can set Student access at the My Portal level
and have it filter down. Make sure that no higher level access is granted, either
explicitly or as inherited.
For administrators, choose Administrator.
6. Click OK, and then click Done to return to the list of resources.
7. Select Portlet Applications and search for ″Learning″ to include the Learning
application in your results.
8. At the Learning application page entry, click Assign Access and give the same
access rights as you just did for students and administrators in Step 5. Make
sure that no higher level access is granted to students than Privileged User,
either explicitly or as inherited. For administrators, choose Administrator.
9. Click OK, and then click Done to return to the list of resources.
When you finish, users logged in as Students should see the following options in
their portlet title bars:
v My Learning - Help Mode, Minimize, Maximize
v Announcements - Minimize, Maximize
v My Competencies - Help mode, Minimize, Maximize
Administrators should have an additional Configure mode option for the My
Learning portlet.
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Chapter 7 Completing IBM Workplace Collaborative Learning Setup
287
Enabling reporting on AIX, Linux, Solaris, and i5/OS
If you are running IBM Workplace Collaborative Learning on IBM i5/OS and you
did not use the Create IBM Workplace Collaboration Services wizard, you must
install and configure Virtual Network Computing to enable Collaborative Learning
reporting.
For more information, see ″Configuring IBM Workplace Collaboration Services″ in
Chapter 3.
If you are running Collaborative Learning on IBM AIX, Linux, or Sun Solaris, you
must install Xvfb (Xserver virtual frame buffer) on the Workplace server to enable
Collaborative Learning reporting. Xvfb provides a virtual Xserver that runs
without a head or graphics card, so that you do not have to run a real Xserver.
Refer to the following Xvfb installation and configuration instructions for your
operating system. In a Network Deployment environment, perform these steps on
Node 1 and all subsequent nodes.
Installing Xvfb on AIX
Use the following procedure to install Xvfb on AIX. For complete instructions, refer
to the AIX Windows Programming Guide at
http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/aixwnpgd/xvfb.htm#xvfb.
1. Log in to the server as a user with administrative privileges.
2. Add the following line to /etc/initab:
xvfb:2:respawn:/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :1 > /dev/null
3. Set DISPLAY by adding the following line to .profile:
DISPLAY=`hostname`:1.0
export DISPLAY
4. Save the changes.
5. Restart the server.
6. Disable JIT on application servers.
Installing Xvfb on Linux and Solaris
Use the following procedure to install Xvfb on Linux and Sun Solaris.
Before you begin
On Linux, the binary is called ’Xvfb’ and may or may not be included with your
distribution. If you do not have Xvfb with your distribution, it may be available
from your Linux vendor; otherwise, it is available from x.org at the following URL:
ftp://ftp.xfree86.org/pub/XFree86/4.2.0/binaries/Linux-ix86-glibc22/
Once obtained, follow the instructions provided with the package to unpack and
install it.
On a standard Solaris 9 O/S, the software should already be installed. It resides
under /usr/openwin/bin and the binary is called ’Xsun’. It is started by a shell
script called Xvfb, which passes it some command line arguments in addition to
what the user specifies.
Installation
288
Installation and Upgrade Guide
The following steps should be carried out as an administrative user; for example,
root. If you are installing on Linux, skip Steps 1 - 4.
Note: This procedure assumes you use :1 as the display number for Xvfb. To use a
different number, see the instructions that follow for ″Changing the display
number from 1.″
1. (Solaris) Perform the following steps to remove the setgid bit, if it is set, on
the Xvfb script.
a. Check to see if the Xvfb script has setgid permissions. The ″s″ in the
middle set of permissions denotes that the script has setgid permissions.
bash-2.05# ls -l /usr/openwin/bin/Xvfb
-rwxr-sr-x 1 root root 162 Nov 30 18:34 /usr/openwin/bin/Xvfb
b. Issue the following command to remove the setgid bit if it is set:
bash-2.05# chmod g-s /usr/openwin/bin/Xvfb
2. (Solaris) Make a backup copy of the Xvfb script.
3. (Solaris) In a text editor, open the original Xvfb script and change the
following line:
Xsun $* +nkeyboard +nmouse -dev vfb
to
/usr/openwin/bin/Xsun $* +nkeyboard +nmouse -dev vfb
Save the file without closing it.
4. (Solaris) With the Xvfb script still open, determine if the script contains these
lines:
ServerNumber=`echo $1 |grep ":"`
if [ "$ServerNumber" ]
then
shift
fi
These lines, if present, force Xvfb to run on the default display :0. To run on
:1, as described in this procedure, or any other number besides 0, comment
out these lines, then save and close the file.
5. Generate a script file named /etc/init.d/xvfb containing the following:
#!/bin/sh
XVFB_DISPLAY=":1"
case "`uname`" in
"Linux")
XVFB_BINARY=/usr/X11R6/bin/Xvfb
;;
"SunOS"|"Solaris")
XVFB_BINARY=/usr/openwin/bin/Xsun
;;
*)
XVFB_BINARY=
;;
esac
if [ ! -z "$XVFB_BINARY" ]; then
case "$1" in
"start")
if [ -f "$XVFB_BINARY" ]; then
XVFB_PID="`pgrep -f "$XVFB_BINARY $XVFB_DISPLAY"`"
if [ -z "$XVFB_PID" ]; then
echo "xvfb: Starting Xvfb on $XVFB_DISPLAY"
`dirname $XVFB_BINARY`/Xvfb $XVFB_DISPLAY &
else
echo "xvfb: ERROR: Xvfb is running on $XVFB_DISPLAY"
Chapter 7 Completing IBM Workplace Collaborative Learning Setup
289
exit
fi
else
echo "xvfb: ERROR: $XVFB_BINARY not found"
exit 1
fi
;;
"stop")
XVFB_PID="`pgrep -f "$XVFB_BINARY $XVFB_DISPLAY"`"
if [ ! -z "$XVFB_PID" ]; then
echo "xvfb: Stopping Xvfb on $XVFB_DISPLAY"
kill -9 $XVFB_PID
else
echo "xvfb: ERROR: Xvfb is not running on $XVFB_DISPLAY"
exit 1
fi
;;
"status")
XVFB_PID="`pgrep -f "$XVFB_BINARY $XVFB_DISPLAY"`"
if [ -z "$XVFB_PID" ]; then
echo "xvfb: Xvfb is not running on $XVFB_DISPLAY"
else
echo "xvfb: Xvfb is running on $XVFB_DISPLAY"
fi
;;
*)
echo " Usage: "
echo " $0 start (start Xvfb)"
echo " $0 stop (stop Xvfb)"
echo " $0 status (check if Xvfb is running)"
exit 1
;;
esac
else
echo "xvfb: ERROR: Could not determine platform"
exit 1
fi
exit 0
6. Make the script file executable with the following command:
chmod +x /etc/init.d/xvfb
7. Determine the run-level into which the system starts with the following
command:
grep initdefault: /etc/inittab
The number in the resulting line indicates the default system run-level. In
these examples, ″3″ is the system run-level:
Linux
id:3:initdefault
Solaris
is:3:initdefault
To use a different run-level, change the line in /etc/inittab to specify a
different number.
8. Create a soft link in the appropriate run-level with the following command:
ln -s /etc/init.d/xvfb /etc/rc3.d/S99xvfb
This example uses run-level 3 (identified by ″rc3.d″). If you intend to use Xvfb
in a different run-level, set up the soft link to the appropriate /etc/rcX.d
directory.
Also, note the use of the number 99 (S99xvfb). This number indicates the
order in which the services for your run-level start up. The higher the number,
290
Installation and Upgrade Guide
the later the service starts in relation to all the others. You do not have to use
99 but you should make it reasonably high so that other services on which
this may depend will be started first.
9. Restart the machine.
10. Verify that Xvfb is running using the following command:
/etc/init.d/xvfb status
11. Set and export the DISPLAY environment variable using the following
command:
export DISPLAY=`hostname`:1.0
This command can also be added to the shell profile you use; for example,
.bash_profile.
12. Start Application Servers.
Note: Changes in scripts supplied by the operating system supply workarounds
for problems encountered with Xvfb on that platform. IBM accepts no
responsibility for any harm caused to your system by making these changes
and any queries regarding the suitability of such changes should be directed
to the operating system vendor.
Changing the display number from 1:
The display number argument to Xvfb (:1 in the above examples) is what isolates
Xvfb from any other running X servers. This number can be any number that is
not already in use, but you must set your DISPLAY environment variable to the
number you are actually using.
AIX
Make the following changes to /etc/initab, save the changes, and restart the
server.
1. Change GLX :1 to the new display number in the following line:
xvfb:2:respawn:/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :<your_new_number >/dev/null
where <your_new_number> represents the new display number.
2. Change DISPLAY=`hostname`:1.0 to the new display number:
DISPLAY=`hostname`:<your_new_number>.0
export DISPLAY
Linux and Solaris
Make the following changes and restart the server.
1. In /etc/init.d/xvfb, change XVFB_DISPLAY=″:1″ to the new display number,
then save the changes:
XVFB_DISPLAY=″:<your_new_number>″
where <your_new_number> represents the new display number.
2. Set and export the DISPLAY environment variable using the following
command:
export DISPLAY=`hostname`:<your_new_number>.0
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Related tasks
Configuring Virtual Network Computing (i5/OS only)
Chapter 7 Completing IBM Workplace Collaborative Learning Setup
291
Configuring Learning administrator help on AIX, Linux,
Solaris, and Windows
Most IBM Workplace Collaborative Learning administration is performed through
the separate Collaborative Learning administrator interface. You access the
interface with a Web address such as http://www.servername.com/lms-lmm. To
access help and online documentation while you are using the administrator
interface, configure the help system by following these steps. In a Network
Deployment environment, perform these steps after you have finished setting up
the Network Deployment and the Workplace server cluster is operational.
1. Log in to the server as a user with administrative privileges.
2. If you have not already done so, create a directory in the HTTP Server
document root to store the help files.
IBM AIX, Linux, and Sun Solaris users must have root privileges to create
directories. Do not include spaces when creating directory names.
AIX
/usr/IBMHttpServer/htdocs/en_US
Linux
/opt/IBMHttpServer/htdocs/en_US
Solaris
/opt/IBMHttpServer/htdocs/en_US
Microsoft Windows
c:\IBMHttpServer\htdocs\en_US
3. Copy the lms-help.zip file from the
<install_root>\WorkplaceServer\Learning\help directory to the new local
directory.
4. Unzip the files from lms-help.zip into the new local directory.
5. With a browser, access the Learning Server start page as an Administrator and
navigate to Settings → LMM Server → General Settings → General tab.
6. In the ″URL″ field for the Help System on the General settings page, type:
http://$LMM_HOSTNAME /$HELP_DIR/
where $HELP_DIR is the help directory created previously within the HTTP
server’s document root.
For example:
http://xyz.acme.com/help_dir/
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Related tasks
Configuring Learning administrator help on i5/OS
Configuring Learning administrator help on i5/OS
To configure the help system for the IBM Workplace Collaborative Learning
administrator interface on IBM i5/OS, follow these steps.
Note: If you used the Create IBM Workplace Collaboration Services wizard to
configure Collaborative Learning, these steps were performed for you.
1. Start the QShell Interpreter by entering the following on an i5/OS command
line:
292
Installation and Upgrade Guide
STRQSH
2. Create a new help directory in the directory structure of your external HTTP
server by entering the following:
mkdir /www/http_instance/htdocs/lms_help
where http_instance is the name of your HTTP server instance. In most cases,
this will be the same as the name of your IBM Workplace instance.
3. Copy the lms-help.zip file to the new help directory by entering the following
on one line:
cp /qibm/userdata/webas5/base/iwp_instance/workplaceserver/
Learning/help/lms-help.zip /www/http_instance/htdocs/lms_help
where iwp_instance is the name of your IBM Workplace Collaboration Services
instance, and http_instance is the name of your HTTP server instance.
4. Change to the new help directory:
cd /www/http_instance/htdocs/lms_help
5. Unzip the lms-help.zip file by entering the following:
jar -xvf lms-help.zip
6. Once the lms-help.zip file has been unzipped, you can remove it by entering
the following:
rm lms-help.zip
7. Change to the htdocs directory (one level up) by entering the following:
cd ..
8. Create the appropriate permissions for all files in the new help directory by
entering the following:
chmod -R o+rx lms_help
9. With a browser, access the Learning Server start page as an Administrator and
navigate to Settings → LMM Server → General Settings → General tab.
10. In the ″URL″ field for the Help System on the General settings page, type:
http://hostname/lms_help/
where hostname is the full host name of the server hosting Collaborative
Learning.
Related concepts
Phase 7: Setting up IBM Workplace Collaborative Learning
Chapter 7 Completing IBM Workplace Collaborative Learning Setup
293
294
Installation and Upgrade Guide
Chapter 8 Rich Client Installation and Configuration
This chapter provides information about installing the IBM Workplace
Collaboration Services provisioning server and downloading the IBM Workplace
rich client to user workstations.
Phase 8: Rich client installation and configuration
The IBM Workplace Collaboration Services rich client is a desktop environment
that lets users work with IBM Workplace Messaging, IBM Workplace Documents,
and other applications such as Lotus Notes. Users install the rich client on their
desktops after the IBM Workplace administrator has performed several preliminary
tasks. The administrator creates a provisioning server by installing provisioning
components on the IBM Workplace server or IBM WebSphere Portal server. The
administrator then performs such tasks as configuring user policy using the IBM
WebSphere Administrative Console. Users should be instructed to download and
install the rich client only after all system administration tasks have been
performed.
The rich client user environment is controlled by user policy (set by the
administrator) and user preferences (set by the user). User policy determines which
applications the user can install. The user starts desktop installation using the My
Work → IBM Workplace rich client → Start Download sequence, which is available
if the user policy setting Allowed clients has been set to Rich client using the
WebSphere Administrative Console.
The rich client installation program and the subsequent configuration process
provision the user’s rich client with only those capabilities he has been granted
access to through user policy. If any capabilities have been added or changed on
the provisioning server since the last login, the user will be notified.
User policy settings are held in an RCPML file that is accessed each time a user
logs in to the rich client. The relationship between the WebSphere Administrative
Console settings, the user’s RCPML file, and the rich client provisioning server is
closely linked to ensure that the user always has access to the correct rich client
capabilities.
To download the most up-to-date information center, go to
http://www.lotus.com/ldd/notesua.nsf/find/workplace.
Related tasks
Rich client installation and configuration checklist
Installing the provisioning server
Installing the rich client
IBM Workplace rich client installation and configuration
checklist
This topic lists in sequence the tasks administrators must perform before users can
install the IBM Workplace rich client on their desktops. It includes the tasks users
must perform to install the rich client on their desktops.
© Copyright IBM Corp. 2002, 2005
295
Note: The administrator can update the rich client using either Eclipse or IBM
WebSphere Everyplace® Device Manager (WEDM).
Note:
To download the most up-to-date information center, go to
http://www.lotus.com/ldd/notesua.nsf/find/workplace.
The administrator performs the following steps to enable users to install the IBM
Workplace rich client.
1. Review the preinstallation checklist and then install and configure the IBM
Workplace server.
2. Review the fix pack requirements for this release.
3. Install a local HTTP server or a remote HTTP server.
4. If you are using a Sun ONE or Domino Web server, configure it to enable rich
client installation program download.
5. (Optional) Configure Secure Socket Layer (SSL) for the HTTP server to later
facilitate rich client synchronization and replication and enable SSL
provisioning of the rich client components.
6. Review security and authentication access information in preparation of
subsequent steps in this checklist.
7. (IBM i5/OS only) Check that 5722JV1 Option *BASE and Option 6 are
installed on the system before installing the provisioning server. The 5722JV1
product can be found on the system CDs.
8. Install the rich client provisioning server using the standard graphical user
interface tools.
Note: If you are installing the provisioning server in a Network Deployment
environment, see Network Deployment installation and configuration
roadmap and Updating the WebSphere Portal EAR file for Network
Deployment.
Note: Rich client provisioning is supported using the IBM Workplace server
with Cloudscape and the IBM WebSphere Member Manager. You don’t
need IBM DB2 or IBM Directory Server for rich client provisioning.
Note: Alternatively, you can choose to install the provisioning server using a
response file or using the console. You can also install from either a CD
or an e-image.
9. Establish the user policy setting to enable users to install the rich client using
the IBM WebSphere Administrative Console. To ensure that the user can
install the rich client, click Lotus Workplace → Users → Manage User Policies →
Default (or specific user policy name). Scroll down to Allowed clients and
check Rich client. Without this setting, the user cannot install the rich client.
10. Create a site certificates file. This provides the credential store with a trusted
certificates file and suppresses the Trust Certificates dialog during rich client
installation.
11. Adjust existing system settings to enhance rich client performance.
12. Set rich client installation program defaults.
13. Establish security settings of your choice for the rich client certificate store
using the IBM WebSphere Administrative Console.
296
Installation and Upgrade Guide
14. Establish user policy settings to enable user access to specific rich client
capabilities using the IBM WebSphere Administrative Console.
a. Establish user policy settings for rich client General access.
b. Establish user policy settings for rich client Credentials access.
c. Establish user policy settings for rich client Security access.
Note: As stated in the Lotus Workplace → Users → Manage User Policies
help for the IBM WebSphere Administrative Console option Allow
Notes application plug-in, IBM Notes 7 and IBM Domino 7 are
required for Notes applications to operate in the rich client. See the
IBM Lotus Domino 7 Administration technical documentation at
http://www.lotus.com/doc for details.
15. (Optional) Configure the provisioning server for secure installation and
update with SSL.
16. Ensure that the rich client desktops meet the prerequisites of operating system
version, capacity, and so on.
17. (Optional) Configure operating system single sign-on for the user.
18. Provide rich client users with user name, password, and the Web address of
the provisioning server.
19. The rich client user logs in to IBM Workplace, opens the My Work welcome
page, and downloads and installs rich client software to the desktop.
20. The rich client user logs in to rich client and begins work. She can configure
the desktop using Preferences as described in the online help available in the
client. She can also modify the Search bar graphic to customize it for her
organization.
21. The administrator updates the provisioning server with new rich client
components as they become available.
Note: The administrator can optionally configure the provisioning server to
use IBM WebSphere Everyplace Device Manager (WEDM) and then
push provisioning server updates to rich client users using WEDM.
Note: See the system upgrade overview and roadmap for details.
If needed later, the user uninstalls the rich client from her desktop.
If needed later, the administrator uninstalls the provisioning server.
Related concepts
Rich client policy and preference overview
HTTP server overview
Related tasks
Network deployment installation
“Connecting HTTP and SIP services on the rich client provisioning server” on
page 267
“Updating the WebSphere Portal EAR file for Network Deployment” on page
337
Setting rich client installation program defaults
Provisioning server installation using console mode
Installing the provisioning server on i5/OS graphically
“Preparing for rich client setup (i5/OS)” on page 55
If you are setting up a rich client provisioning server on i5/OS, the Create IBM
Chapter 8 Rich Client Installation and Configuration
297
Workplace Collaboration Services wizard can install and configure the rich
client for you. Follow these steps to enable the Create IBM Workplace
Collaboration Services wizard to install and configure the rich client.
Additional HTTP server settings for provisioning
“Updating rich client configuration files for Network Deployment” on page 354
Installing and configuring the provisioning server
Before IBM Workplace rich client users can install the rich client, the administrator
must install the rich client provisioning server on the IBM Workplace server. IBM
Workplace Collaboration Services capabilities are provided to the user from this
provisioning server when he installs the rich client on his desktop. Updates to
these capabilities are available each time the user logs in or switches from one
capability to another while working in the rich client user interface.When updates
are available, the user is notified.
Read the rich client installation and configuration checklist before continuing.
If you are installing the provisioning server in a Network Deployment (clustered)
environment, read Network Deployment installation and configuration road map
and Configuring the wps.ear file in a Network Deployment environment before
continuing. If you are installing the provisioning server in a Network Deployment
environment, you MUST install on the first node (Node 1) that is going to be
federated into the cluster. Provisioning server installation must be performed prior
to federating. The provisioning server cannot be installed on any other node in the
cluster, only on the first node (Node 1) to be federated.
When running this installation program, you must be logged in as a system
administrator (for Microsoft Windows) or root (for UNIX and IBM i5/OS).
For i5/OS administrators -- These steps describe a local console installation on
i5/OS. For instructions on installing remotely on i5/OS using the graphical
installation program, see Installing the provisioning server on i5/OS with the
graphical installation program.
To install and configure the provisioning server, complete the following steps:
1. Ensure that the IBM HTTP server, Cloudscape or IBM DB2 server, and the
IBM WebSphere Portal Server that you will be using for this procedure are
installed and running on the IBM Workplace server.
Note: An external HTTP server configuration doesn’t require a local HTTP
server be installed but it does require additional steps to install and link
the content on the HTTP server. If you are using an external HTTP
server, read this procedure.
2. If you already have a provisioning server installed on this Workplace server,
uninstall it before continuing.
Note: If you are not sure if there is a provisioning server already installed,
look for ″IBM Workplace rich client provisioning components″ in
Add/Remove programs (for Microsoft Windows) or installed package
names starting with IBM_LWP_S_MC (for UNIX).
3. On the Workplace server, start the platform-specific rich client provisioning
setup program. The installation startup files, listed below, are on the first
CD-ROM.
298
Installation and Upgrade Guide
For Windows, use setupWin32.exe.
For Linux, use setupLinux.bin.
For AIX, use setupAix.bin.
For Solaris, use setupSolaris.bin.
For i5/OS, use setupi5OS.sh from a QShell session (enter STRQSH on an
i5/OS command line to start the QShell Interpreter).
4. When prompted, specify the language in which to display the screen text and
click OK to continue. This affects the language for the installation program
and does not affect which languages will be installed. All languages are made
available to users regardless of your selection here.
5. Read the Welcome screen and click Next to continue.
v
v
v
v
v
6. Read the license agreement screen, accept the terms, and click Next to
continue.
Note: If you are installing on i5/OS, skip ahead to Step 8.
7. Specify a directory in which to install the provisioning server and click Next
to continue.
8. Select a Typical or Custom installation and click Next to continue.
Note: Select Custom to install Update bundles and Installation files to a
remote HTTP server. For example, when running the installation
program on the remote HTTP server, you can de-select all custom
choices that do not say HTTP server in parentheses; when running the
installation program on the Workplace server associated with the
remote HTTP server, you can turn the HTTP server content off.
Note: If you are using a remote HTTP server, do not install the HTTP content
on the Workplace server. Instead, use the Custom install mode,
un-check the HTTP content boxes when installing to Workplace, run the
provisioning server installation program again on the remote server,
and select only HTTP content.
Note: If you are installing in a Network Deployment environment, you must
use the Custom option for Node 1.
9. If you selected Custom, select the features you want to install and click Next
to continue. The Custom features are listed below:
v Update bundles (install on HTTP server)
v WebSphere Portal content (install on WebSphere Portal Server)
v IBM WebSphere Everyplace Device Manager (WEDM) extensions (install in
selected root)
v IBM Workplace Collaboration Services contents
v Installation files (install on HTTP server)
Note: If you are installing in a Network Deployment environment, uncheck
Update bundles (install on HTTP server) and Installation files
(installed on HTTP server) if your HTTP server is located on a
different server. If the HTTP server is on the same system as the
Workplace server, all of these should be checked.
10. Specify the following IBM WebSphere Portal Server information and click
Next to continue.
Chapter 8 Rich Client Installation and Configuration
299
Note: (i5/OS only) Select your WebSphere Portal instance and enter your
WebSphere Portal administrator user ID and password. If unsure of the
WebSphere Portal instance, use the default value of WebSphere_Portal.
Click Next to continue.
Note: Ensure that the WebSphere Portal server is running and able to install
setup scripts before clicking Next to continue.
v Portal server directory -- Specify the directory in which the WebSphere
Portal Server is installed. A typical setting is WebSphere_Portal.
Note: On i5/OS, the administrator does not need to specify a portal server
directory.
v Portal Server configuration URL -- Accept the default address or specify a
different URL, such as http://lwpsvrabx.pic.ibm.com:9081/lwp/config.
v Portal administrator User ID -- Enter your user ID.
v Portal administrator password (with password confirmation) -- Enter and
confirm your password. This password is not saved to a local registry.
11. Continue to specify information on this screen for the WebSphere Portal Server
selected in the previous screen. Specify the following WebSphere Application
Server information and then click Next to continue.
v WebSphere Application Server (WAS) application server (AppServer)
directory -- Specify an AppServer directory or accept the default.
v WAS server name -- Specify the WebSphere Application Server name, such
as WebSphere_Portal.
v WAS cell name, located in the installedApps directory for wps.ear -- Specify
the cell name. To determine the cell name check
c:\<installeddir>\AppServer\config\cells. This can be found by navigating
to the WebSphere installedApps directory and searching for wps.ear
associated with the WebSphere Portal instance you are installing to, and
providing its parent directory name.
Note: If you are installing in a Network Deployment environment, use a
wps.ear file that has been updated to contain the needed themes,
screens, skins, and images as specified in the topic entitled ″Updating
the WebSphere Portal EAR file for Network Deployment″.
v WAS server bootstrap address -- Accept the default bootstrap address or
specify a different value.
v WAS server SOAP connector port -- Accept the default SOAP connector port
or specify a different value.
Note: The BOOTSTRAP_ADDRESS and SOAP values are typically set in the
WebSphere Application Server Administrative Console and also found
in the serverindex.xml file. A sample i5/OS path to serverindex.xml is
as below:
/QIBM/UserData/WebAS5/base/<instanceName>/config/cells/<cellName>/
nodes/<nodeName>
For i5/OS, there may not be a default port value specified so you must
retrieve the port value from the WebSphere Administrative Console
bootstrap address. To simplify the process of obtaining your
BOOTSTRAP_ADDRESS and SOAP_CONNECTOR_ADDRESS, use the
grep command on the serverindex.xml. Sample command syntax to find
300
Installation and Upgrade Guide
the BOOTSTRAP port number and SOAP connector port number
associated with the WebSphere_Portal server for the i5/OS platform is
shown below:
/qibm/proddata/webas5/pme/bin/dspwasinst -instance <instance_name>
-server WebSphere_Portal | grep ’Name service port’
/qibm/proddata/webas5/pme/bin/dspwasinst -instance <instance_name>
-server WebSphere_Portal | grep ’Soap port’
Note: The Server name specified in the user’s login screen (and on the
Connectivity screens available to users) is used to supply rich client
updates to the rich client workstation. It is also used to synchronize rich
client libraries and other data on user workstations with data on the
server. Specifying a different server name may result in lost libraries
and malfunctions with mail, calendar, and address book features.
Changing the server value is only supported if the server is known to
be in a clustered environment sharing the same data store. The Port
value corresponds to the setting on the WebSphere Portal Server to
which the client is connecting. To reduce the risk of entering an
erroneous port number, use the WebSphere Administrative Console to
retrieve these values. The default Host (Server name) and Port is
specified by the administrator in the WebSphere Administrative Console
using Servers → Application Servers → <server name> → End Points →
BOOTSTRAP_ADDRESS.
12. Specify the HTTP server document root, installed on this Workplace server, to
use for provisioning rich client updates to the desktop. A sample path might
be C:\HttpServer\htdocs\en_US.
The HTTP server document root is the directory location that maps to ″/″ on
the HTTP site that the server provides. The directory that the HTTP server
uses is part of the HTTP server’s configuration. For the IBM HTTP server, the
default relative path is htdocs/en_US.
For i5OS, select the HTTP server associated with the Workplace server.
Note: If you are using a remote HTTP server (not on the same machine as the
Workplace server), you would not install the HTTP content on the
Workplace server. Instead, you must use the Custom install mode (see
step 9), un-check the HTTP content boxes when installing to Workplace,
run the provisioning server installation program again on the remote
server, and select only HTTP content.
13. Click Next to continue.
14. Read the summary screen and then click Next to install the rich client
provisioning server uninstall program and regenerate the HTTP server’s
plugin configuration file.
15. If prompted, insert the second CD and click OK to continue.
Note: On UNIX platforms, it may be necessary to unmount CD 1 before
ejecting and then remount CD 2 after inserting. On i5/OS, you may be
prompted to enter the path for the second directory, for example
/tmp/WorkplaceSCI2.
16. Read the on-screen instructions about restarting the WebSphere Portal server,
restart it now, and click Next to continue.
17. Read the on-screen instructions regarding the location of installation logs and
record log location. Click Finish to complete the provisioning server
installation. The IBM Workplace rich client provisioning directory will contain
several .txt files and the _jvm, _uninst, license, and log subdirectories.
Chapter 8 Rich Client Installation and Configuration
301
18. Click Finish.
Note: If the installation program reports deployment errors, read through the
log files and determine possible causes and consequences for the errors.
Check the masterInstallLog.txt and masterInstallWizardLog.txt files if
there are errors.
Note: Before users can install the rich client, you must establish appropriate
user policy settings. The IBM Workplace rich client installation option is
only available to the user, in the Downloads area of the My Work page,
if you enabled the option in the Allowed client field for that user
policy.
19. If you are using an external HTTP server complete the external HTTP
checklist now.
Related concepts
HTTP server overview
System settings for optimal performance
“Lotus Workplace 2.0.1 upgrade” on page 361
Related tasks
Synchronizing and replicating rich client data through the HTTP server
Rich client installation and configuration checklist
Installing the provisioning server on i5/OS graphically
Provisioning server installation using console mode
Network deployment installation
“Updating the WebSphere Portal EAR file for Network Deployment” on page
337
Provisioning server updates
Configuring the provisioning server to use WEDM
Updating the rich client using WEDM
Uninstalling the provisioning server
Additional HTTP server settings for provisioning
“Updating rich client configuration files for Network Deployment” on page 354
Installing the rich client provisioning server using a response file
The administrator can optionally install the IBM Workplace rich client provisioning
server from a command prompt window using a response file, instead of using the
graphical user interface. This can be useful when you want to install provisioning
capabilities on multiple servers using a similar configuration.
Note: Instructions for installation on IBM i5/OS appear at the end of this topic.
1. Create a baseline response file called optionsFile.txt.
a. Open a command prompt window and run the installation program with
the command line option -options-record <optional-path/>optionsFile.txt.
For example, type run setupWin32.exe -options-record c:\optionsfile.txt.
b. Run through the entire installation program to the end. This will record all
of your responses, allowing you to accept the defaults provided by the
installation program where appropriate.
Note: The response file will only be created if you run the installation program
all the way through to completion and click the Finish option.
302
Installation and Upgrade Guide
Note: Response files will contain the same properties for all platforms, but the
default values and file path formats will be different. It is best to
perform this step for every operating system on which you will use a
response file to install.
2. After completing the installation, edit the optionsFile.txt response file to
customize it to your needs. For example, for security reasons, you may wish to
remove the stored IBM WebSphere Portal server administrator password line
-W selectWpsServer.wpsAdminPassword=″wpsadmin″, or change the password
to a placeholder such as ″″ or ″password″ instead of the actual password.
3. Copy the contents of the two IBM Workplace rich client provisioning server
CD-ROMs to a temporary location on the server’s hard drive, into directories
named disk1 and disk2, respectively.
Note: Use the ″disk1″ and ″disk2″ names specifically or the installation will
fail. You can create disk1 and disk2 as subdirectories of a directory with
a more descriptive name.
4. Copy the response file, optionsFile.txt, into the disk1 directory.
5. Open a command prompt window and change to the disk1 directory.
6. Run the installation program for your platform with the command line options
-options optionsFile.txt -silent.
Note: If you removed -W selectWpsServer.wpsAdminPassword=″password″
and -W selectWpsServer.wpsAdminPasswordVerification=″password″
from the response file, or if you replaced the value with a placeholder
value, add that line as a command line option. For example, on a
Windows system where you have replaced the password with ″″, the
command is setupWin32.exe -options optionsFile.txt -silent -W
selectWpsServer.wpsAdminPassword=″TheRealPassword″.
Note: The install command starts asynchronously, meaning the command
window will be immediately available for more input after you start the
installation program. The best way to determine when installation is
complete is to watch for a decrease in server hard drive activity. You can
monitor the state of the master InstallLog.txt file in the logs directory in
the product root install location you specified.
Instruction for installing the provisioning server using a response file on i5/OS
are as below.
Note: Names are case-sensitive and italicized text should be replaced with
appropriate values.
a. Open a QShell session on the i5/OS system and create a directory using the
following commands:
v On the i5/OS screen type QSH and press enter.
v From the QShell session, enter mkdir -p
/QIBM/ProdData/Workplace/WCT25/ and press enter.
b. Copy the WorkplaceSCI1 and WorkplaceSCI2 directories from the
installation media to /QIBM/ProdData/Workplace/WCT25/ created on the
i5OS system.
c. Edit the wctResponse file located in the
/QIBM/ProdData/Workplace/WCT25/WorkplaceSCI1 directory by
updating the following properties:
v -W wasInstancePanel.instanceName=″<value>″
v -W wasInstancePanel.wpsAdminUsername=″<value>″
Chapter 8 Rich Client Installation and Configuration
303
-W wasInstancePanel.wpsAdminPassword=″<value>″
-W wasInstancePanel.wpsAdminPasswordVerification=″<value>″
-W wpsPropsPanel.wpsServerName=″<value>″
-W wpsPropsPanel.wasBootstrapPort=″<value>″
-W wpsPropsPanel.wasSoapConnectorPort=″<value>″
-W httpInstancePanel.httpInstance=″<value>″
-media 1=/<PathToWorkplaceSCI>/WorkplaceSCI1
2=/<PathToWorkplaceSCI>/WorkplaceSCI2
d. Run the following command from QShell in the directory where the
response file is located: setupi5OS.sh -options wctResponse.txt -silent
Related tasks
Provisioning server installation
Rich client installation and configuration checklist
Related reference
Sample options.txt file
v
v
v
v
v
v
v
Sample optionsFile.txt:
The IBM Workplace rich client provisioning server can be installed from a
command prompt using a response file. This can be useful when you want to
install the IBM Workplace rich client provisioning server on multiple servers using
a similar configuration.
When you use a response file to install, you use a baseline response file called
optionsFile.txt. The contents of a sample optionsFile.txt response file for use with
Microsoft Windows is shown below.
################################
# InstallShield Options File
# Wizard name: Install
# Wizard source: data.jar
# Created on: Fri Dec 10 13:23:24 EST 2004
# Created by: InstallShield Options File Generator
#
# This file contains values that were specified during a recent execution of
# Install. It can be used to configure Install with the options specified below
# when the wizard is run with the "-options" command line option. Read each
# setting’s documentation for information on how to change its value.
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, use the following command line arguments when running the wizard:
#
#
-options "c:\optionsfile.txt" -silent
#
################################
# IBM Workplace rich client provisioning components Install Location
# The install location of the product. Specify a valid directory into which the
# product should be installed. If the directory contains spaces, enclose it in
# double-quotes. For example, to install the product to C:\Program Files\My
304
Installation and Upgrade Guide
# Product, use
#
-P installLocation="C:\Program Files\My Product"
-P installLocation="D:\websphere\WCT"
################################
# Setup Type
# The setup type to be used when installing the product. Legal values are:
#
typical - Typical: The program will be installed with the suggested
#
#
configuration. Recommended for most users.
custom
#
- Custom: The program will be installed with the features you
choose. Recommended for advanced users.
#
# For example, to specify that the "Typical" setup type is selected, use
#
-W setupTypes.selectedSetupTypeId=typical
# You may also set the setup type to nothing by using
#
-W setupTypes.selectedSetypTypeId=
# This clears the current setup type and prevents any changes to the set of
# selected features. Use this option whenever you set feature active states in
# this options file. If you do not clear the selected setup type, the setup type
# panel will override any changes you make to feature active states using this
# file.
-W setupTypes.selectedSetupTypeId=typical
################################
# "License files (installed in selected root)" Feature
# The selection state of the "License files (installed in selected root)"
# feature. Legal values are:
#
true
#
false - Indicates that the feature is not selected for installation
- Indicates that the feature is selected for installation
# For example, to select "License files (installed in selected root)" for
# installation, use
#
-P licensefiles.active=true
-P licensefiles.active=true
################################
# "Update bundles (installed on HTTP server)" Feature
# The selection state of the "Update bundles (installed on HTTP server)"
# feature. Legal values are:
#
true
#
false - Indicates that the feature is not selected for installation
- Indicates that the feature is selected for installation
# For example, to select "Update bundles (installed on HTTP server)" for
# installation, use
#
-P updateBundlesFeature.active=true
-P updateBundlesFeature.active=true
################################
# "WebSphere Portal content (deployed to WebSphere Portal server)" Feature
# The selection state of the "WebSphere Portal content (deployed to WebSphere
# Portal server)" feature. Legal values are:
#
true
#
false - Indicates that the feature is not selected for installation
- Indicates that the feature is selected for installation
# For example, to select "WebSphere Portal content (deployed to WebSphere Portal
Chapter 8 Rich Client Installation and Configuration
305
# server)" for installation, use
#
-P wpsContentFeature.active=true
-P wpsContentFeature.active=true
################################
#
Feature
# The selection state of the "WebSphere Everyplace Device Manager extensions
# (installed in selected root)" feature. Legal values are:
#
true
#
false - Indicates that the feature is not selected for installation
- Indicates that the feature is selected for installation
# For example, to select "WebSphere Everyplace Device Manager extensions
# (installed in selected root)" for installation, use
#
-P wedmExtensionsFeature.active=true
-P wedmExtensionsFeature.active=true
################################
# "IBM Workplace content" Feature
# The selection state of the "IBM Workplace content" feature. Legal values are:
#
true
- Indicates that the feature is selected for installation
#
false - Indicates that the feature is not selected for installation
# For example, to select "IBM Workplace content" for installation, use
#
-P lwpContentFeature.active=true
-P lwpContentFeature.active=true
################################
# "Installation files (installed on HTTP server)" Feature
# The selection state of the "Installation files (installed on HTTP server)"
# feature. Legal values are:
#
true
#
false - Indicates that the feature is not selected for installation
- Indicates that the feature is selected for installation
# For example, to select "Installation files (installed on HTTP server)" for
# installation, use
#
-P installationFilesFeature.active=true
-P installationFilesFeature.active=true
################################
# User Input Field - wpsDirectory
-W selectWpsServer.wpsDirectory="D:\websphere\PortalServer"
################################
# User Input Field - wpsConfigUrl
-W selectWpsServer.wpsConfigUrl="http://localhost:9081/lwp/config"
################################
# User Input Field - wpsAdminUsername
-W selectWpsServer.wpsAdminUsername="wpsadmin"
################################
# User Input Field - wpsAdminPassword
-W selectWpsServer.wpsAdminPassword="wpsadmin"
################################
# User Input Field - wpsAdminPasswordVerification
-W selectWpsServer.wpsAdminPasswordVerification="wpsadmin"
################################
# User Input Field - wasAppServerDirectory
306
Installation and Upgrade Guide
-W selectWasServer.wasAppServerDirectory="D:\websphere\AppServer"
################################
# User Input Field - wasServerName
-W selectWasServer.wasServerName="WebSphere_Portal"
################################
# User Input Field - wasCell
-W selectWasServer.wasCell="krishna"
################################
# User Input Field - wasBootstrapPort
-W selectWasServer.wasBootstrapPort="2810"
################################
# User Input Field - wasSoapConnectorPort
-W selectWasServer.wasSoapConnectorPort="8881"
################################
# User Input Field - httpServerDocumentRoot
-W selectHttpServer.httpServerDocumentRoot="D:\IBMHTTPServer\htdocs\en_US"
################################
# User Input Field - instanceName
-W wasInstancePanel.instanceName=""
################################
# User Input Field - wpsAdminUsername
-W wasInstancePanel.wpsAdminUsername=""
################################
# User Input Field - wpsAdminPassword
-W wasInstancePanel.wpsAdminPassword=""
################################
# User Input Field - wpsServerName
-W wpsPropsPanel.wpsServerName="WebSphere_Portal"
################################
# User Input Field - httpInstance
-W httpInstancePanel.httpInstance=""
################################
Related tasks
Installing the provisioning server using a response file
Installing the provisioning server using the console interface for
Windows
The IBM Workplace rich client provisioning server installation program provides a
console interface, which enables you to perform an interactive installation from a
command prompt. The console interface for Windows presents the same content as
the graphical interface, but in a textual form. Prompts at the bottom of each screen
tell you how to enter numbers to make your selections and proceed to the next
screen.
1. Copy the WorkplaceSCI1 and WorkplaceSCI2 directories from the installation
media to your local Windows server.
2. Navigate to your local WorkplaceSCI1 directory.
3. Start the installation by typing the following command and then press Enter:
setupWin32.exe -console
Chapter 8 Rich Client Installation and Configuration
307
4. Enter a number to correspond to the desired installation program language
and press Enter.
5. Read the license agreement panel and press Enter to continue.
6. Read the rest of the license agreement, press 1 to accept the terms, and press
Enter to continue.
7. Specify a directory in which to install the provisioning components and press
Enter or just press Enter to accept the default installation directory.
8. Press 1 and Enter to specify Typical installation or press 2 and Enter to specify
Custom installation. For information on Custom installation and subsequent
options, see “Installing and configuring the provisioning server” on page 298.
9. Enter the Portal server information as below and then press Enter.
a. Enter the Portal server directory or accept the default Portal server.
b. Enter the Portal server configuration URL or accept the default Portal
server. configuration URL.
c. Enter the Portal administrator user ID.
d. Enter the Portal administrator password.
e. Confirm the Portal administrator password.
10. Enter the WebSphere Application Server information as below and then press
Enter.
a. Enter the WebSphere Application Server (WAS) server name, for example
WebSphere_Portal.
b. Enter the WAS cell name, located in the installedApps directory) for
wps.ear. To determine the cell name check
c:\<installeddir>\AppServer\config\cells. This can be found by
navigating to the WebSphere installedApps directory and searching for
wps.ear associated with the WebSphere Portal instance you are installing
to, and providing its parent directory name.
c. Enter the BOOTSTAP_ADDRESS.
d. Enter the SOAP connector port.
Note: The BOOTSTRAP_ADDRESS and SOAP values are typically set in
the WebSphere Application Server Administrative Console and also
found in the serverindex.xml file. A sample Windows path to
serverindex.xml is C:\Program
Files\WebSphere\AppServer\config\cells\aria\nodes\abx. To
simplify the process of obtaining your BOOTSTRAP_ADDRESS and
SOAP_CONNECTOR_ADDRESS, use the grep command on the
serverindex.xml file.
11. Specify the HTTP server document root, associated with the chosen IBM
Workplace server, to use for provisioning rich client updates to the desktop. A
sample path might be C:\httpserver\htdocs\en_US. Press Enter to continue.
12. Read the summary panel and press Enter to continue.
13. When prompted to insert the second CD, enter the path to the local
WorkplaceSCI2 directory and then press Enter to continue.
14. Note the statement informing you that you must manually restart the
WebSphere Portal server and then press Enter to continue.
15. Note the statement informing you that the server components are now
available and also the location of the log files. Press 3 and Enter to complete
the installation program.
16. Review the rich client installation and configuration checklist.
308
Installation and Upgrade Guide
Related tasks
Installing the provisioning server
Rich client installation and configuration checklist
Installing the provisioning server from CD-ROM
This topic provides a CD-based alternative method for installing the provisioning
server. Provisioning server installation is dependent on other installation and
configuration procedures. Read Installing and configuring the provisioning server
before initiating the steps described on this page.
You can either install directly from the CD or download the contents of the CDs to
your hard drive and run the installation program from your hard drive.
To install Workplace Client Technology from the CD, insert CD 1 and run the
following platform-specific installation program. Refer to Installing and configuring
the provisioning server for help in responding to prompts.
v Windows (Example: E:) -- E:\setupWin32.exe
v Linux -- /opt/<mount point>/setupLinux.bin
v AIX -- /opt/<mount point>/setupAix.bin
v Solaris -- /opt/<mount point>/setupSolaris.bin
v i5/OS -- /opt/mount point/setupi5OS.sh if running from Linux or
E:\setupi5OS.bat if running from Windows
Note: The installation program requires that you use both CDs. For Linux, AIX,
and Solaris run the installation program, resident on CD 1, one level higher
than the mount point. For example, if the mount point is /install, run the
installation program from /opt/install/setupLinux.bin.
To install Workplace Client Technology by downloading from the CD and
installing from the hard drive, complete the following steps:
1. Create a downloads directory on your hard drive for both of the CDs, for
example D:\downloads\WorkplaceSCI1 and D:\downloads\WorkplaceSCI2
(Windows) or /opt/downloads/WorkplaceSCI1 and
/opt/downloads/WorkplaceSCI2 (Linux, AIX, Solaris, and i5/OS).
2. Insert CD 1 in the CD-ROM drive.
3. Copy the contents of CD1 to the downloads directory created in step 1 on your
hard drive.
Windows:
D:\downloads\WorkplaceSCI1
Linux, AIX, Solaris, and i5/OS:
/opt/downloads/WorkplaceSCI1
4. Insert CD 2 in the CD-ROM drive.
5. Copy the contents of CD 2 to the downloads directory created in step 1 on
your hard drive.
Windows:
D:\downloads\WorkplaceSCI2
Linux:
/opt/downloads/WorkplaceSCI2
6. Run the platform-specific installation program.
v Windows -- D:\downloads\WorkplaceSCI1\setupWin32.exe
Chapter 8 Rich Client Installation and Configuration
309
Linux -- /opt/downloads/WorkplaceSCI1/setupLinux.bin
AIX -- /opt/downloads/WorkplaceSCI1/setupAix.bin
Solaris -- /opt/downloads/v/setupSolaris.bin
i5/OS -- /opt/downloads/WorkplaceSCI1/setupi5OS.sh if running from
Linux or D:\downloads\WorkplaceSCI1\setupi5OS.bat if running from
Windows
7. Refer to Installing and configuring the provisioning server for help in
responding to prompts.
Related tasks
Rich client installation and configuration checklist
“Installing and configuring the provisioning server” on page 298
v
v
v
v
Installing the provisioning server from an e-image
This topic provides an e-image alternative method for installing the provisioning
server. Provisioning server installation is dependent on other installation and
configuration procedures. Read Installing and configuring the provisioning server
before initiating the steps described on this page.
To install Workplace Client Technology from an e-image, complete the following
steps:
1. Create a downloads directory and an install directory on your hard drive.
Windows:
a. Create a downloads directory, for example D:\downloads.
b. Create an install directory in which to extract the download images, for
example D:\install.
Linux, Solaris, AIX, and i5/OS:
a. Create a downloads directory under /opt or /tmp, for example
/opt/downloads or /tmp/downloads.
b. Create an install directory under /opt or /tmp, for example /opt/install or
/tmp/install.
2. Copy the e-image contents to the downloads directory created in step 1 using
the following platform-specific procedure.
Windows:
a. Download the abx001.exe and abx002.exe self-extracting images to the
downloads directory created in step 1.
b. Preserving the folder structure, extract the .exe images to the install
directory created in step 1.
The following directory structure should now exist in the install directory
on your hard drive:
D:\install\WorkplaceSCI1
D:\install\WorkplaceSCI2
Linux, Solaris, AIX, and i5/OS:
a. Download the C82MBML.tar and C82MCML.tar images to the downloads
directory created in step 1.
b. Preserving the folder structure, extract the tar images to the install directory
created in step 1.
The following directory structure should now exist in the install directory
on your hard drive:
/opt/install/WorkplaceSCI1
310
Installation and Upgrade Guide
/opt/install/WorkplaceSCI2
3. Run the platform-specific installation program.
v Windows -- D:\install\WorkplaceSCI1\setupWin32.exe
v Linux -- /opt/install/WorkplaceSCI1/setupLinux.bin
v AIX -- /opt/install/WorkplaceSCI1/setupAix.bin
v Solaris -- /opt/install/WorkplaceSCI1/setupSolaris.bin
v i5/OS -- /opt/install/WorkplaceSCI1/setupi5OS.sh if running from Linux or
D:\install\WorkplaceSCI1\setupi5OS.bat if running from Windows
4. Refer to Installing and configuring the provisioning server for help in
responding to prompts.
Related tasks
Rich client installation and configuration checklist
“Installing and configuring the provisioning server” on page 298
Installing the provisioning server on i5/OS with the graphical
installation program
You can install the IBM Workplace rich client provisioning server using the
graphical installation program from a remote workstation connected to your server.
Note: These instructions refer to the D: drive as the CD drive letter on the local
PC.
1. Insert disk 1 in the CD-ROM drive of the PC.
2. Open Windows Explorer and navigate to the D: drive.
3. Navigate to the <WorkplaceSCI1> directory and start the graphical installation
program by double-clicking setupi5OS.bat.
4. Enter the System name, User ID, and Password and click OK.
5. Select the language to be used by the graphical installation program and click
OK.
6. Read the Welcome panel and click OK.
7. Accept the license agreement terms and click OK.
8. Select the Typical or Custom installation method and click OK.
Note: For details on Custom installation, as well as details on subsequent
steps in this installation process, see “Installing and configuring the
provisioning server” on page 298.
9. Select the IBM Workplace Collaboration Services instance on which to install
the provisioning server. Enter the WebSphere Application Server
administrative user ID, password, and password confirmation and click Next.
Note: Ensure that the WebSphere Portal server is running and able to install
setup scripts before clicking Next to continue.
10. Continue to specify information on this screen for the Workplace
Collaboration Services instance specified in the previous screen. Specify the
following WebSphere Application Server information and then click Next.
v WAS server name -- Specify the WebSphere Application Server name, such
as WebSphere_Portal.
v WAS cell name, located in the installedApps directory for wps.ear -- Specify
the cell name. To determine the cell name check
c:\<installeddir>\AppServer\config\cells. This can be found by navigating
Chapter 8 Rich Client Installation and Configuration
311
to the WebSphere installedApps directory and searching for wps.ear
associated with the WebSphere Portal instance you are installing to, and
providing its parent directory name.
v WAS server BOOTSTRAP_ADDRESS -- Specify a bootstrap address or
accept the default.
v WAS server SOAP connector port -- Specify a SOAP connector port or
accept the default.
Note: The BOOTSTRAP_ADDRESS and SOAP variables and values are
typically set in the WebSphere Administrative Console and also found
in the serverindex.xml file. A sample Windows path to serverindex.xml
is as below:
C:\Program Files\WebSphere\AppServer\config\cells\aria\nodes\abx
A sample i5/OS path to serverindex.xml is as below:
/QIBM/UserData/WebAS5/base/<instanceName>/config/cells/<cellName>/nodes/<nodeNam
To simplify the process of obtaining your BOOTSTRAP_ADDRESS and
SOAP_CONNECTOR_ADDRESS, use the grep command on the
serverindex.xml. Sample command syntax to find the BOOTSTRAP port
number and SOAP connector port number associated with the
WebSphere_Portal server for the i5/OS platform is shown below. Note
that the term myinstance refers to the Workplace Collaboration Services
instance specified in previous steps.
/qibm/proddata/webas5/pme/bin/dspwasinst -instance myinstance
-server WebSphere_Portal | grep ’Name service port’
/qibm/proddata/webas5/pme/bin/dspwasinst -instance myinstance
-server WebSphere_Portal | grep ’Soap port’
11. Specify the HTTP server document root associated with the Workplace server
to use for provisioning rich client updates to the desktop and click Next.
12. Click Next after the panel indicates the server has been reached.
13. Verify the summary information and click Next to start the installation.
14. When prompted by the installation program, insert the second CD and click
OK.
15. When installation is complete, restart the server as prompted and click Finish.
Related tasks
Installing the provisioning server
Rich client installation and configuration checklist
Configuring the provisioning server for secure installation and
update with SSL
You can configure the rich client provisioning server for Secure Sockets Layer (SSL)
if the WebSphere Application Server and the HTTP server are already configured
to use SSL.
For information on configuring the WebSphere Application Server and the HTTP
server to use SSL, see the IBM Workplace Collaboration Services Information
Center.
If you want users to download the IBM Workplace rich client technology from the
provisioning server over HTTPS, specify the URL Provider settings for SSL
312
Installation and Upgrade Guide
provisioning using the following procedure. This procedure also assumes that you
will want the user to obtain rich client component updates over HTTPS.
You will need to specify a URL resource for the Workplace Client Installer
Download Server and then repeat the process to specify a URL for the Workplace
Client Provisioning Server.
1. Log in to the WebSphere Administrative Console (for example
https://yourWASServer:9091/admin) using an administrative user name and
password.
Click Resources → URL Providers.
Set the scope to Cell.
If there is a node name specified, remove it and click Apply.
Click Default URL Provider.
Click Additional Properties - URLs.
Click Workplace Client Installer Download Server.
Change the Specification setting to link to https://yourserver, for example
https://apple.lotus.com. Do not change the JNDI name or any other fields.
9. Click OK.
10. Click Resources → URL Providers.
2.
3.
4.
5.
6.
7.
8.
Set the scope to Cell.
If there is a node name specified, remove it and click Apply.
Click Default URL Provider.
Click Additional Properties - URLs.
Click Workplace Client Provisioning Server.
Change the Specification setting to link to https://yourserver, for example
https://apple.lotus.com/lwpupdate/wct). Do not change the JNDI name or
any other fields.
17. Click OK.
18. Click Save.
19. Restart the Application servers.
Related tasks
Installing and configuring the provisioning server
Rich client installation and administration checklist
11.
12.
13.
14.
15.
16.
Configuring for optimal rich client performance
To achieve optimal performance when working with the IBM Workplace rich client,
allow larger message sizes (approximately 10MB), and enable rich client download
for the user policy, you can configure HTTP server and Microsoft Windows
settings as described in the two links below. These steps are best performed after
provisioning server installation and before rich client download and installation.
Windows system settings for rich client performance
Inbound and Outbound mail size configuration
After provisioning server installation, you can also make administrative
adjustments for the following capabilities:
Synchronizing and replicating rich client data through the HTTP server
Chapter 8 Rich Client Installation and Configuration
313
Suppressing the rich client Trust Certificate dialog
Using operating system single sign-on and synchronizing passwords
Configuring the provisioning server for secure update with SSL
Related tasks
Rich client installation and configuration checklist
“Connecting HTTP and SIP services on the rich client provisioning server” on
page 267
“External HTTP server checklist” on page 261
Installing and configuring the provisioning server
Configuring a trust certificate for IBM Workplace rich client
A Trust Certificate dialog appears as a final step during IBM Workplace rich client
installation and when the client interacts with a server over the SSL protocol and a
certificate for that server does not exist in the user list of trusted servers. To
simplify the user experience by suppressing the Trust Certificate dialog, you can
create a configuration file that configures the necessary certificate and then add the
user’s server(s) certificate to the user list of trusted servers. This is done by
creating a site certificates file, adding it to the list of files sent to the client during
rich client installation, and adding the certificates to the IBM Workplace server’s
Workplace Client Certificate Store.
Note: Use the ikeyman tool provided with WebSphere to create the sitecerts.jks site
certificates file. Be sure to specify the JKS format when creating the site
certificate .jks file. Use the version of ikeyman provided with the IBM HTTP
server to extract the certificate .arm files .
Note: Certificates are distributed to all IBM Workplace client desktops on a
server-scheduled basis.
1. Extract the public certificates for the truststore file. Extracting a certificate from
one keystore file and adding it to a truststore file is not the same as exporting
the certificate and then importing it. Exporting a certificate copies all the
certificate information, including its private key, and is normally only used if
you want to copy a personal certificate into another keystore file as a personal
certificate. If a certificate is self-signed, extract the certificate and its public key
from the keystore file and add it to the target truststore file. If a certificate is
CA-signed, verify that the CA certificate used to sign the certificate is listed as
a signer certificate in the target truststore file. The keystore file must already
exist and contain the certificate to be extracted. note:
Note: Do this task for WAS server and for the HTTP server.
a. Start the key management utility (iKeyman), if it is not already running.
b. Open the keystore file from which the public certificate will be extracted.
(.kdb file on the HTTP server and .jks file on the WAS server)
c. Select Personal Certificates.
d. Click Extract Certificate.
e. Click Base64-encoded ASCII data under Data type.
f. Enter the Certificate File Name and Location.
g. Click OK to export the public certificate into the specified file.
314
Installation and Upgrade Guide
A certificate file (*.arm) that contains the public key of the signed personal
certificate is now available for the target truststore file. Note the location of
both these files because you need them in the next step.
2. Create a site certificates file. This file e is a key database file that contains both
public keys and private keys. Public keys are stored as signer certificates while
private keys are stored in the personal certificates. The keys are used for a
variety of purposes, including authentication and data integrity. You can use
both the key management utility (iKeyman) and the keytool utility to create
keystore files.
Note: This procedure is done only on the WAS server.
a. Start the iKeyman utility, (WAS Ikeyman only) if it is not already running.
b. Open a new key database file by clicking Key Database File > New from
the menu bar.
c. Select the Key Database Type: JKS (default), . This is the key file format
when you configure the SSL setting for your application.
d. Type in this file name - sitecerts.jks - and location (preferably /etc).
e. Click OK to continue.
f. Type in password to restrict access to the file. This password is used as the
key file password when you configure the SSL setting for your application.
g. Click OK to continue. The tool displays all of the available default signer
certificates. These certificates are the public keys of the most common
certificate authorities (CAs). You can add, view or delete signer certificates
from this panel.
A new SSL site certificate trust file is created.
3. Now you can import signer certificates - either CA-signed certificates not
contained already in the site certs.jks file or self-signed certificates. These
certificates were extracted as .arm files in step 1. A signer certificate is the
trusted certificate entry that is usually in a truststore file. You can import a
certificate authority (CA) root certificate from the CA, or a public certificate
from the self-signed personal certificate of the target into your truststore file, as
a signer certificate.
a. Start the key management utility (iKeyman), if it is not already running.
b. Open the sitecerts.jks (created in step 2) The Password Prompt window
displays.
c. Type the password and click OK.
d. Select Signer Certificates from the drop down list.
e. Click Add.
f. Click Data type and select Base64-encoded ASCII data, as described in step
1.
g. Type a certificate file name and location for the CA root digital certificate or
click Browse to select the name and location and click OK.
h. Type a label for the importing certificate and click OK.
The Signer Certificates field now displays the label of the signer certificate you
just added.
4. Import the server’s public certificate into the server’s Workplace Client
Certificate Store as a trusted certificate. To import the certificate into the trusted
root store, it must be in a file visible to your browser.
a. Log in to the IBM WebSphere Administrative Console as an administrative
user (one who has been associated with the pkiAdmin role).
Chapter 8 Rich Client Installation and Configuration
315
b. Click Lotus Workplace → Workplace Client Certificate Store. You will see
the current contents of the trusted root store.
c. Click Import certificate from file under Additional actions to display the
import screen.
d. Select the file (for example keyfile.arm) containing the certificate, and click
Next to display the certificate(s) in the current file.
e. Select the certificate to import and check the Trust check box.
f. Click Finish. Repeat for each .arm file you extracted.
5. Place the sitecerts.jks site certificates file with the rich client installation
program on the HTTP server. The default installation directory for the rich
client installation program on the HTTP server is as follows:
<root>\Httpserver\htdocs\en_US\lwpinstall\wct
6. Locate and edit the download applet’s files list properties file (filesList.props)
to add site certificates to the file’s properties for the configurations that you
want. The default file path for the download applet on the WebSphere
Application Server is as follows:
<root>\WebSphere\AppServer\installedApps\<server>\wctInstall.ear\wctinstall.war
For example, the content of this filesList.props file is shown below:
win32.ie.downloads.files=setup_wct_platform.exe
win32.ie.downloads.location=$host$/lwpinstall/wct/
win32.ie.downloads.execute=setup_wct_platform.exe
win32.mozilla.downloads.files=setup_wct_platform.exe
win32.mozilla.downloads.location=$host$/lwpinstall/wct/
win32.mozilla.downloads.execute=setup_wct_platform.exe
linux.mozilla.downloads.files=setup_wct_platform.bin
linux.mozilla.downloads.location=$host$/lwpinstall/wct/
linux.mozilla.downloads.execute=setup_wct_platform.bin
becomes this:
win32.ie.downloads.files=setup_wct_platform.exe,sitecerts.jks
win32.ie.downloads.location=$host$/lwpinstall/wct/
win32.ie.downloads.execute=setup_wct_platform.exe
win32.mozilla.downloads.files=setup_wct_platform.exe,sitecerts.jks
win32.mozilla.downloads.location=$host$/lwpinstall/wct/
win32.mozilla.downloads.execute=setup_wct_platform.exe
linux.mozilla.downloads.files=setup_wct_platform.bin,sitecerts.jks
linux.mozilla.downloads.location=$host$/lwpinstall/wct/
linux.mozilla.downloads.execute=setup_wct_platform.bin
7. Restart the servers.
Related concepts
Rich client configuration overview
Related tasks
Rich client installation and configuration checklist
Synchronizing data through the HTTP server
You can configure the IBM Workplace rich client to use a remote IBM HTTP server
or HTTPS (HTTP with Secure Sockets Layer, or SSL) to synchronize data between
the rich client and the IBM WebSphere Portal Server. By encrypting all transmitted
data, as well as authenticating the identity of the server, HTTPS offers greater
security than that of HTTP.
316
Installation and Upgrade Guide
For any IBM HTTP server, the location of the plugin-cfg.xml file that the HTTP
server will use is in the file <HTTP_install_root>/conf/httpd.conf, in an entry
called WebSpherePluginConfig. The administrator initially creates entries in the
httpd.conf file when setting up a remote HTTP server to work with the IBM
WebSphere Application Server.
A remote HTTP server is defined as an HTTP server that resides on a different
machine than the WebSphere Application Server. A remote HTTP server has a
different DNS name than the WebSphere Application Server.
HTTPS on the external HTTP server is required in the event of network
deployment or a remote HTTP server.
Note: To configure the rich client to use HTTPS for both provisioning and data
synchronization, specify ″https″ and the SSL port number in the user’s
Portal URL field in the Connectivity options page available from the rich
client Login screen (for example,
https://server.ibm.com:443/lwp/MyWorkplace/MyStuff).
If the HTTP server is remote, or you have configured the user’s system to use a
local HTTP server instead of the WebSphere Application Server embedded HTTP
server for rich client synchronization and replication, perform the following steps:
Note: A remote HTTP server is defined as an HTTP server that resides on a
different machine than the WebSphere Application server. A remote HTTP
server has a different DNS name than the WebSphere Application server.
1. Enable HTTP on your external HTTP server, following the documentation
supplied by your HTTP server vendor.
2. Extract the certificate used on the HTTP server (either self-signed or signed)
from the HTTP server’s keystore, using the ikeyman tool and help supplied
with your HTTP server.
3. Add that extracted certificate as a Signer to the Server Trust store that
WebSphere Portal server is using; for example
was_home/etc/DummyServerTrustFile.jks with a password of WebAS.
4. Perform the following tasks using the WebSphere Application Server
Administrative Console.
a. Add the HTTP server port to the virtual hosts parameter for default_host;
for example http://yourWASServer:9091/admin by clicking Environment →
Virtual Hosts → default_host → Addtional Properties - Host Aliases → New.
b. Click Host Name: and enter either * or the HTTP server name.
c. Click Port: and enter either 443 or your HTTPS port number.
d. Click OK.
e. Click Save.
5. Regenerate the HTTP server’s plugin configuration file (as in a previous topic),
http://yourWASServer:9091/admin by clicking Environment → Update Web
Server Plugin and then clicking OK.
6. If working with remote HHTP, copy the HTTP server’s plugin configuration file
(plugin-cfg.xml) from the WebSphere Application Server to the local HTTP
server directory.
7. Restart the HTTP server.
8. Restart the WebSphere Portal Server and Workplace server.
Related concepts
Chapter 8 Rich Client Installation and Configuration
317
HTTP server overview
Related tasks
Rich client installation and configuration checklist
Configuring the rich client for remote HTTP server use
Remote IBM HTTP server settings
See “Connecting HTTP and SIP services on the rich client provisioning server” on
page 267 for configuring the HTTP server for an IBM Workplace rich client
environment.
Related concepts
System settings for optimal rich client performance
Connecting to an HTTP server
Related tasks
Rich client installation and configuration checklist
“External HTTP server checklist” on page 261
Synchronizing data through the HTTP server
Inbound and Outbound mail size adjustment
You can adjust the inbound and outbound maximum mail size for rich client users
as described below.
1. Log in to the WebSphere Administrative Console (for example
https://yourWASServer:9091/admin) using an administrative user name and
password.
2. Click Lotus Workplace → Mail Cell-wide settings → Filters for SMTP Inbound
Connections.
3. For each of the connection types (anonymous, authenticated, trusted, and
suspect]), click the link to each and change the Maximum inbound message
size (KB) field value to 20000 (approximately 20 MB).
4. Click Lotus Workplace → Mail Cell-wide settings → SMTP Outbound/Local
Delivery.
5. Click Maximum size of an outbound message (KB) and change the value to
20000 (approximately 20 MB).
6. Scroll to the top of the main area, and click Save.
7. Click Save on the resultant screen to save these changes to the master
configuration.
8. Log out of the WebSphere Administrative Console.
Related concepts
Rich client configuration overview
System settings for optimal rich client performance
Related tasks
Rich client installation and configuration checklist
Microsoft Windows system settings for rich client performance
Maximize system resources for Microsoft Windows user background tasks as
described below:
1. Click Start → Settings → Control Panel → System.
2. Click the Advanced tab and the Performance Options option.
318
Installation and Upgrade Guide
3. Ensure that the Background Processes option is selected.
4. Click the virtual memory Change option. Ensure that the Initial Size is equal
to the Recommended Size and the Maximum Size is set to 4095.
Note: If the machine’s physical memory is more than 4 GB (4096 MB), the
maximum allowed size of virtual memory is 4095 MB. Set the Initial
Size and Maximum Size limits to 4095 MB.
5. Continue to click OK until no more dialogs appear.
6. If you will not be using Internet Information Services (IIS), remove it now by
performing the following tasks:
a. Click Start → Settings → Control Panel → Add/Remove Programs.
b. Click the Add/Remove Windows Components option.
c. Uncheck Internet Information Services (IIS).
d. Click Next.
e. Ensure that the Remote Administration Mode option is enabled.
f. Click Next.
g. Click Finish.
h. Close the Add/Remove Programs panel.
Related concepts
Rich client configuration overview
System settings for optimal rich client performance
Related tasks
Rich client installation and configuration checklist
Enabling operating system single sign-on
Single sign-on (SSO) lets users use one user name and password to authenticate
with the operating system and with IBM Workplace rich client capabilities. When
you set up single sign-on for the rich client user, the user name and password are
stored in the user’s personal credential store.
To download the most up-to-date information center, go to
http://www.lotus.com/ldd/notesua.nsf/find/workplace.
Enabling single sign-on (SSO) with the operating system allows the user secure
access to the rich client’s personal credential store without requiring an additional
authentication prompt. This single sign-on feature is a system-wide service. If is
enabled, and upon successful authentication with the operating system, the rich
client personal credential store can be accessed without any additional login
prompts.
Note: The user’s operating system login password and the rich client personal
credential store password must be identical in order for single sign-on to
work.
The user can choose to enable or disable the installed single sign-on feature using
security preferences.
This feature is supported on Microsoft Windows 2000, Microsoft Windows XP, and
RedHat Enterprise Linux 3.
Chapter 8 Rich Client Installation and Configuration
319
If single sign-on is not enabled, users can use the Change password preference,
available from the File → Preferences → Security menu, to change the password
stored in the personal credential store. The operating system’s user name and
password values are not affected.
If single sign-on is enabled and a user changes the password used to authenticate
with the operating system, the installed rich client capabilities detect this change at
startup and automatically reset the client password to match the new operating
system password. When single sign-on is enabled, the Change password
preference setting available from File → Preferences → Security is not enabled.
The login credentials you supply to IBM Workplace Collaboration Services during
installation and setup are initially the same for the IBM Workplace browser client
and IBM Workplace rich client. The local credential store, however, stores the user
names and passwords for the browser client and rich client as separate credentials.
As a result, if you, or a user, enable single sign-on with the operating system in the
rich client or change the password for the rich client, these changes do not affect
the login information supplied to log in the browser client. The two do not remain
the same.
Related tasks
“Configuring Linux operating system single sign-on”
“Configuring Windows operating system single sign-on”
“Uninstalling single sign-on for Linux” on page 322
“Uninstalling single sign-on for Windows” on page 321
“Installing and configuring the provisioning server” on page 298
“Installing the IBM Workplace rich client” on page 326
Configuring Windows operating system single sign-on:
To configure the rich client user environment for single sign-on with Microsoft
Windows, perform the following tasks.
1. Make sure that the user has installed the rich client.
2. Make sure that the user has sufficient operating system privileges to modify the
Windows registry and install new services, or determine that you will perform
this installation for the user.
3. Navigate to the following directory:
rcp\eclipse\feature\com.ibm.rcp.security.sso.win32.feature\os\win32\x86
4. Run the ssoinstall.cmd file and then reboot the user’s system.
Note: Not all password changes can be detected. If an administrator changes a
user’s password, or the user changes the password using User Accounts
tools, the rich client and operating system passwords may not match.
Note: To disable this feature from the above directory, run the following file
and then reboot the user’s system:
rcp\eclipse\feature\com.ibm.rcp.security.sso.win32.feature\os\win32\x86\ssoremove.cmd
Related concepts
Configuring rich client operating system single sign-on
Configuring Linux operating system single sign-on:
These instructions are for RedHat Enterprise Linux 3, which uses a directory-based
configuration.
320
Installation and Upgrade Guide
The instructions assume you have some understanding of Linux System
Administration and Linux Security Administration, especially the configuration of
PAM (Pluggable Authentication Modules). See the Linux-PAM System
Administrator’s Guide (http://www.kernel.org/pub/linux/libs/pam/Linux-PAMhtml/pam.html#toc4) for related information.
To configure the rich client user environment for single sign-on with Microsoft
Windows, perform the following tasks.
Note: The rich client single sign-on feature is not intended for use with the root
user ID. The rich client single signon PAM module and the rich client single
signon daemon will ignore login requests from the root user ID.
1. Make sure that the user has installed the rich client.
2. In a Linux shell, log in as, or switch user (su), to root.
3. Navigate to the
rcp/eclipse/feature/com.ibm.rcp.security.sso.win32.feature/os/linux/x86
directory.
4. Run the installsso script to copy several components to the appropriate system
directories.
5. Navigate to /etc/pam.d in preparation for modifying the system’s PAM
configuration to add the rich client’s PAM module to the appropriate system
files.
6. Add the statements in bold shown in the sample below to either the gdm or
the xdm PAM configuration file.
Note: If the system is using the GNOME window manager, edit the gdm file. If
the system is using the KDE window manager, edit the xdm file. If in
doubt, edit both files.
Note: See the ″Linux-PAM System Administrator’s Guide″ for more details on
file format and content.
Sample /etc/pam.d/gdm file:
#%PAM-1.0
auth
required
auth
required
account
password
password
pam_unix2.so
nullok #set_secrpc
pam_rcpsso.so
required
required
required
debug
pam_unix2.so
pam_unix2.so
#strict=false
pam_rcpsso.so
session
required
pam_unix2.so
session
required
pam_devperm.so
session
required
pam_resmgr.so
session
required
pam_rcpsso.so
debug
debug # trace or none
debug
7. Add the following line to the passwrd file.
password
required
pam_rcpsso.s
debug
8. Reboot the user’s system.
Related concepts
Configuring rich client operating system single sign-on
Uninstalling single sign-on for Windows:
Chapter 8 Rich Client Installation and Configuration
321
Before uninstalling the rich client, you must uninstall the operating system single
sign-on feature (SSO) and then reboot the system.
1. Navigate to the
rcp\eclipse\feature\com.ibm.rcp.security.sso.win32.feature\os\win32\x86
directory.
2. Run the ssoremove.cmd program.
3. Reboot your system.
You can now proceed to uninstall the rich client.
Related concepts
Rich client single sign-on overview
Related tasks
Installing rich client single sign-on for Windows
Uninstalling the rich client
Uninstalling single sign-on for Linux:
Before uninstalling the rich client, you must uninstall the operating system single
sign-on feature (SSO) and then reboot the system.
1. Log in as root or switch user (su) to root.
2. Navigate to the
rcp/eclipse/feature/com.ibm.rcp.security.sso.win32.feature/os/linux/x86
directory.
3. Run the removesso script.
4. Navigate to the /etc/pam.d directory.
5. Edit the gdm or xdm file to remove references to pam_rcpsso.so.
Note: If you do not perform this step, you might not be able to log in later.
6. Reboot your system.
You can now proceed to uninstall the rich client.
Related concepts
Rich client single sign-on overview
Related tasks
Installing rich client single sign-on for Linux
Uninstalling the rich client
Configuring the provisioning server for secure installation and
update with SSL
You can configure the rich client provisioning server for Secure Sockets Layer (SSL)
if the WebSphere Application Server and the HTTP server are already configured
to use SSL.
For information on configuring the WebSphere Application Server and the HTTP
server to use SSL, see the IBM Workplace Collaboration Services Information
Center.
If you want users to download the IBM Workplace rich client technology from the
provisioning server over HTTPS, specify the URL Provider settings for SSL
provisioning using the following procedure. This procedure also assumes that you
will want the user to obtain rich client component updates over HTTPS.
322
Installation and Upgrade Guide
You will need to specify a URL resource for the Workplace Client Installer
Download Server and then repeat the process to specify a URL for the Workplace
Client Provisioning Server.
1. Log in to the WebSphere Administrative Console (for example
https://yourWASServer:9091/admin) using an administrative user name and
password.
2. Click Resources → URL Providers.
3. Set the scope to Cell.
4. If there is a node name specified, remove it and click Apply.
5. Click Default URL Provider.
6. Click Additional Properties - URLs.
7. Click Workplace Client Installer Download Server.
8. Change the Specification setting to link to https://yourserver, for example
https://apple.lotus.com. Do not change the JNDI name or any other fields.
9. Click OK.
10. Click Resources → URL Providers.
11. Set the scope to Cell.
12. If there is a node name specified, remove it and click Apply.
13. Click Default URL Provider.
14. Click Additional Properties - URLs.
15. Click Workplace Client Provisioning Server.
16. Change the Specification setting to link to https://yourserver, for example
https://apple.lotus.com/lwpupdate/wct). Do not change the JNDI name or
any other fields.
17. Click OK.
18. Click Save.
19. Restart the Application servers.
Related tasks
Installing and configuring the provisioning server
Rich client installation and administration checklist
Setting rich client installation program defaults
Administrators can alter the default values that are provided to users during rich
client installation and initial setup by editing the pluginvalues.props and
token_values.props properties files. This enables you to control download applet
behavior and the defaults supplied to the client installation program and client
initial setup. This is particularly useful when using the IBM Workplace
configurations listed below:
v Remote HTTP servers, which do not have the same IP address as the WebSphere
Portal server where Workplace is installed
v Network Deployments, which have more than one back-end server that can
service clients
v Alternate port configurations, such as altered BOOTSTRAP_ADDRESS endpoints
Note: In an application cluster, edited properties files must be copied to every
cluster mate.
Chapter 8 Rich Client Installation and Configuration
323
Note: If you are using a Network Deployment, see “Connecting HTTP and SIP
services on the rich client provisioning server” on page 267 for additional
settings in the pluginvalues.props and token-values.props.
The procedure to edit initial setup values for user desktops is as follows:
1. Install the rich client provisioning server on the IBM Workplace server.
2. On the IBM Workplace server, navigate to the <WebSphere Portal
home>/AppServer/installedApps/(cell)/wctInstall.ear/wctInstall.war directory.
3. Locate and edit the pluginvalues.props file in this directory to change the
following values. These values are provided to the user during rich client
installation and initial startup.
v plugins=plugin_customization
This setting specifies the name of the file that will be used to carry the
defaults to the client. Do not modify this setting.
v plugin_customization.com.ibm.workplace.configuration/defaulturl
=$host$/lwp/myworkplace
This setting specifies the Web address (URL) to which the client connects to
load the appropriate RCPML for the capabilities the user is able to use. In
other words, this URL specifies the provisioning server from which the rich
client will obtain features at install and at update. By default, the $host$
token defaults to the full DNS name of the system from which the client
installer was downloaded, including the HTTP or HTTPS port number that
was specified in the download (see token_values.props below). Change this
value only if the Workplace server does not have its default context root set
to ″lwp,″ or the RCPML server (or its HTTP server front end) is not the
server from which the user downloaded the client installer
v
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=$host-name$
This setting populates the rich client’s Workplace Server field during the
user’s initial setup. It specifies the WebSphere Portal server that the rich
client will connect to when running IBM Workplace applications. By default,
the $host-name$ token defaults to the full IP name of the system from which
the client installer was downloaded (see token-values.props below). Change
this value only if the server that has IBM Workplace installed is not the
server from which the user downloaded the rich client installation program.
v [optional]
com.ibm.workplace.security/com.ibm.wkplc.remote.server.port
=<BOOTSTRAP_ADDRESS>
This setting populates the rich client’s Port field during the user’s initial
setup. It specifies the BOOTSTRAP_ADDRESS of the WebSphere Portal
server that the rich client will connect to when running IBM Workplace
applications. If this value does not exist, the client will assume the default
port 2810. Change this value only if the IBM Workplace server has a
BOOTSTRAP_ADDRESS endpoint configuration that differs from the default
of port 2810 (such as for i5/OS servers or Network Deployments).
Note: The default Host (Server name) and Port on the user’s login
Connectivity screen is specified by the administrator in the WebSphere
Administrative Console using Servers → Application Servers → <server
name> → End Points → BOOTSTRAP_ADDRESS.
324
Installation and Upgrade Guide
Note: The BOOTSTRAP_ADDRESS and SOAP variables and values are
typically set in the WebSphere Administrative Console and also found
in the serverindex.xml file. A sample Windows path to
serverindex.xml is as below:
C:\Program Files\WebSphere\AppServer\config\cells\<cellName>\nodes\abx
A sample i5/OS path to serverindex.xml is as below:
/QIBM/UserData/WebAS5/base/<instanceName>/config/cells/<cellName>/nodes/<nodeName>
4. Locate and edit token-values.props to change the following values. These
values are provided to the user during rich client installation and initial
startup.
v host=getParameter
This setting specifies the value substituted for $host$ when values from
pluginvalues.props are downloaded to the user’s workstation. When the user
downloads the rich client installation program, the getParameter value forces
the download applet to use applet values provided by startdownloadjava.jsp, which is a URL of the form http[s]://full.dns.name:port, derived
from the user browser’s HTTP request header. This value differs from
$host-name$ because it is a URL used for WebSphere Portal page requests
that includes http[s]:// and the HTTP / HTTPS port number that were
included in the HTTP request header. The value can either point to an HTTP
server front-end for a WebSphere Portal server on which IBM Workplace is
installed or it can point directly to a WebSphere Portal server with IBM
Workplace installed.
If an HTTP port other than port 80 is used, it must be specified on this line.
An example is shown below:
host=http://yourHTTPServer:(HTTPportNumber)
v host-name=getParameter
This setting specifies the value substituted for $host-name$ when values
from pluginvalues.props are downloaded to the user’s workstation. When
the user downloads the rich client installation program, the getParameter
value forces the download applet to use applet values provided by
startdownload-java.jsp, which is a full host name derived from the user
browser’s HTTP request header. This value differs from $host$ in that it is
simply a full host name for remote requests; it does not include http[s]:// or
the HTTP / HTTPS port number included in the HTTP request header.
Note: In a Network Deployment environment, change the value of host-name
in the pluginvalues.props file from
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=
to
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=
the fully qualified DNS address of your DM Server>. Also create a directory
called wctprops under the http directory, (for example
c:\IBMHTTPServer\htdocs\en_US\wctprops) and place your modified
properties files fileList.props, pluginvalues.props, and token-values.props
there.
Note: Only the properties files on the HTTP server need to be updated.
5. While the IBM Workplace servers are down, locate and edit the
\websphere\appserver\config\cells\plugin-cfg.xml file as specified below:
a. Save a backup copy of the file as plugin-cfg.xml.ORIG.
b. Open plugin-cfg.xml and find the following string:
Chapter 8 Rich Client Installation and Configuration
325
PostSizeLimit=″10000000″
c. Change the value to ″-1″.
Note: When using an IBM HTTP server in conjunction with Workplace
Collaboration Services, set the PostSizeLimit value in the
plugin-cfg.xml file to -1. Do this for all servers in the cluster and then
regenerate the plugin-cfg.xml Web server plugin. This will enable you
to import large files, such as the installation guide PDF file.
Related concepts
HTTP server overview
Related tasks
Rich client installation and configuration checklist
Network Deployment overview
Provisioning server and HTTP server overview
Installing the provisioning server
Installing the rich client
Installing the IBM Workplace rich client
After the administrator installs the provisioning server on the IBM Workplace
server, the rich client user can install the rich client software on his or her
workstation. The user will need to know his Workplace Collaboration Services user
ID, password, and the Workplace server name and port.
The rich client installation screens display content in the language specified in the
operating system’s locale setting.
The instructions in the remainder of this topic are addressed to the end-user.
Note: Rich client installation requires a Java plugin installed in your Web browser
for site-specific defaults to be automatically provided during the initial setup
of the client. If you do not have a Java plugin, the rich client installer is
downloaded as a single executable file with no defaults. See your
administrator for details.
To install the IBM Workplace rich client on your desktop, perform the following
steps:
1. Start IBM Workplace Collaboration Services on your desktop and type your
user name and password.
2. Click the My Work tab.
3. Under Downloads, click IBM Workplace rich client.
4. Click Start Download.
Note: If Java is not enabled for your Web browser, clicking the link lets you
open the installation program directly or specify a location in which to
save it. Linux users will not be able to run the installation program,
setup_wct_platform.bin, because they do not have execution rights to
the .bin file. To reset execution rights for the installation program, Linux
users should save the installation executable to disk, then run the
following command:
chmod 755 setup_wct_platform.bin
326
Installation and Upgrade Guide
Note: Linux users may be prompted to download the Mozilla Web browser or
specify its directory if the installation program cannot find it. If so
prompted, download the browser or specify its location and then click
Next to continue. Linux users who do not see the Mozilla installation
screen, or that receive a Mozilla error message, should see the Release
Notes for current information.
5. Read the Welcome screen and click Next to continue.
6. Read the license agreement screen, accept the terms, and click Next to
continue.
7. Specify a directory in which to install the rich client and click Next to
continue.
Note: If you already have a rich client installation on this workstation, you
must install to a new directory to avoid conflicts with the existing
installation.
8. Read the preview information screen of what is to be installed, installation
directory, and space requirements and click Next to install the rich client.
9. When the installation summary screen appears, rich client installation is
complete. Read the summary screen and click Next to continue and perform
initial configuration and login.
10.
11.
12.
13.
14.
Note: If you click Cancel to exit the program, the system will perform initial
rich client configuration when you log in later.
At the Workplace login screen, enter your user name and password as
prompted. Unless you have been told otherwise by your system administrator,
accept the default Workplace server and port values that appear on this
screen. Click Next to continue.
The default Workplace server is the server from which you started the
installation program. The port value must correspond to the
BOOTSTRAP_ADDRESS port established by your administrator in the IBM
WebSphere Administrative Console. If the server name or port value is
incorrect, you will receive an unreachable server error.
Allow the system to perform security tasks for you, including access
verification and credential store initialization.
Unless you have been told otherwise by your system administrator, accept the
provisioning components server and click Next to continue.
Read the configuration summary screen and click Finish to complete the
configuration process and restart the rich client.
When the login screen appears again, enter your password, as prompted. You
can specify a Work status of online or offine; these are described in the rich
client help. Click Log in to continue.
Note: Unless you have been told otherwise by your system administrator,
accept the default server name and port that appear on the
Connectivity screen. The Connectivity settings enable you to specify a
different server or port. The Server name specified is used to supply
rich client updates to your workstation. It is also used to synchronize
your rich client libraries and other data with data on the server.
Specifying a different server name may result in lost libraries and
malfunctions with mail, calendar, and address book features. Changing
the server value is only supported if the server is known to be in a
clustered environment sharing the same data store. The Port value
corresponds to the setting on the Portal server to which your rich client
Chapter 8 Rich Client Installation and Configuration
327
is connecting. The default server name and port are specified by the
administrator in the WebSphere Administrative Console using the
Servers → Application Servers → approproate server name → End Points
→ BOOTSTRAP_ADDRESS sequence.
15. If the Trust Certificate screen appears and unless instructed otherwise by your
administrator, accept the defaults and click Yes to continue.
Note: The Trust Certificate screen adds a new certificate and establishes trust
to the provisioning server.
16. Click Finish to complete login and display the rich client user interface.
To download the most up-to-date information center, go to
http://www.lotus.com/ldd/notesua.nsf/find/workplace.
Related concepts
Rich client overview
Related tasks
Rich client installation and configuration checklist
Uninstalling the rich client
Setting certificate trust for rich client download and install
Upgrading rich client capabilities
Each time a user logs in to the IBM Workplace rich client, the system checks the
provisioning server to determine if there are updates available. If updates are
available, or if user policy settings have changed since his last login, the user is
prompted to update his rich client. This is also true when the user, while active
and working online in the rich client, selects an application from the Switcher bar.
Component update is associated to user policy settings. User policy settings are
automatically placed in a file (RCPML file format) for that user locally on his
machine. The RCPML file is an integral part of the rich client component access
process, and with few exceptions is automatically generated and not manually
edited.
For IBM Workplace rich client administrator -- To update to a new IBM
Workplace rich client release, uninstall the IBM Workplace rich client provisioning
server and reinstall the latest provisioning server from IBM. To change user access
to specific features, edit user policy.
For IBM Workplace rich client user -- After the administrator updates the
provisioning server, the user should log in to the rich client to access the latest rich
client capabilities. The user should not uninstall an old release and install a new
release of the rich client in order to access the latest release.
Related concepts
“Lotus Workplace 2.0.1 upgrade” on page 361
Related tasks
Rich client installation and configuration checklist
Updating the rich client using WEDM
“Updating rich client configuration files for Network Deployment” on page 354
Uninstalling the rich client provisioning server
Installing the rich client provisioning server
328
Installation and Upgrade Guide
Updating IBM Workplace rich clients using IBM WebSphere
Everyplace Device Manager
You can optionally use the IBM WebSphere Everyplace Device Manager (WEDM)
to provision rich client capabilities. WEDM enables you to push feature upgrades
and new features, to client machines by creating a software distribution job
through the WEDM Administrative Console. Please see the WEDM server
information center for related information, including WEDM installation
requirements.
You can optionally update rich client users machines with the latest capabilities to
which they have access using WEDM. To enable the provisioning server to use
WEDM, you must install the provisioning server using the standard procedure and
then configure it as described below.
At the end of the process described below, the following two events will occur on
the rich client systems being provisioned:
v The Workplace rich client will connect to the WEDM server to see if there are
any jobs to run five minutes after the rich client user logs in. It will also connect
hourly to see if there are new jobs to run. If a software distribution job is
applicable to the device, the feature will be pushed to the client, and this will
trigger provisioning of the rest of the features and plugins in the distributed
feature.
v When a pushed feature has been successfully provisioned, the rich client user
will be notified that new features have been installed and be offered the choice
to restart the rich client to take advantage of the new features.
IBM Workplace administrators can use WEDM to track and push rich client
application updates to IBM Workplace rich clients. To do this, WEDM 5.0.1 must
be installed and configured as a separate prerequisite. You can install WEDM 5.0.1
using the following procedure.
1. Read the current WEDM readme.txt for any updates to its installation
instructions.
2. Follow the installation instructions in the WEDM 5.0 Information center, which
can be found on the WEDM CD-ROM in
docs/<language>/InfoCenter/index.html. Be sure to perform the following
tasks:
a. Install all prerequisite software as documented in the WEDM release notes
and Information center.
b. Disable WebSphere security when installing the WEDM server.
c. Ensure that WebSphere Application Server (WAS), DB2, and the HTTP
server are running during the installation.
3. Download the WEDM V5.0 fixpack 1 from the support page at
http://www.ibm.com/software/pervasive/ws_everyplace_device_manager/support/.
4. Apply the WEDM V5.0 fixpack 1 to your WEDM 5.0 server using the
instructions in the readme file included with the fixpack. The resulting server is
a WEDM 5.0.1 server.
5. When you installed the rich client provisioning server on your IBM Workplace
server, the system created a directory called wedm_extensions in the root install
location you specified (for example, c:\program files\ibm\ibm workplace client
provisioning for Windows or /opt/IBM/IBM Workplace Client Provisioning for
UNIX). That directory contains a bin subdirectory, which houses the tools and
extensions necessary to extend WEDM for use with IBM Workplace. Navigate
Chapter 8 Rich Client Installation and Configuration
329
to that bin directory and use your preferred file sharing method, such as ftp, to
copy its contents to your WEDM bin directory (for example, c:\tivdms15\bin
on Windows).
6. Install the rich client provisioning server. Once the tools and extension files
have been copied to the WEDM bin directory, extend WEDM with the rich
client device profile using the following procedure:
a. Log in as an operating system administrator.
b. Use the IBM WebSphere Administrative Console to disable WebSphere
Application Server (WAS) security.
c. From a command line, navigate to your WEDM bin directory.
d. Type the command compinstall -file <path to this
file>\RCPPluginComponent.jar in the command line.
Note: If you receive an error when the system attempts to shut down and
restart the WAS server, security is not disabled.
e. Use the WebSphere Administrative Console to enable WAS security.
7. Create a new directory on the WEDM server. Copy the bundle registration tool
bundlereg.zip from the wedm_extensions directory (on the Portal server) to the
new directory and unzip bundlereg.zip file to it.
8. Register the feature bundles using the WEDM Administrative Console or
bundle registration tool (bundlereg.bat found in bundereg.zip) and set the
device class for the bundles to ″RCP.″ Supply the following information as
prompted.
Note: See the WEDM server Information Center for information on how to
register new software bundles to the server.
v Path to the WAS server install directory, for example c:\Websphere\
v Path to the WEDM server install directory, for example C:\TivDMS15\_jvm)
v Base Web address of the Eclipse Update site, for example
http://server.mycompany.com/lwpupdate/wct/.
v Web address of the WEDM server, for example: http://<my wedm server>/
v Path to the Eclipse update site at which the features_list.txt and
plugins_list.txt files reside, for example
C:\ibm\IBMHttpServer\htdocs\en_US\lwpupdate\wct\
v WEDM server administrator user name
v WEDM server administrator password
9. Create a software distribution job for the feature bundle to be pushed to the
rich client desktop(s). A process overview is provided below. For details on
how to create a software distribution job, see the WEDM server Information
Center.
v Create a new Workplace feature with associated plugins.
v To register the new feature and the associated plugins in the WEDM server
using the DM console, right-click Software and then New Software. Click
OSGI bundle to specify the software type. On the New Software Properties:
New Software Properties panel, select the four lines that pertain to the rich
client (RCP).
v Create and configure a job to push the new feature to a specific device as
shown below:
– On the main DM console screen, click Devices and click OK.
– Right-click on the target device and click Submit Job.
330
Installation and Upgrade Guide
– In the Submit Job: Attributes panel, set the Job Type to Software
Distribution.
– On the Submit Job: Job Parameters panel, click Add Group, select the
feature you want to update, click Next and then click OK. The job appears
in the Jobs view as Executable.
v Log in to the rich client or tell the user that he can now log in to the rich
client.
v When the provisioning information panel appears (this may take up to ten
minutes), click Yes and verify that the feature has been installed.
Related tasks
Configuring the provisioning server to use WEDM
Rich client installation and configuration checklist
Updating the rich client capabilities
Installing the provisioning server
Uninstalling the provisioning server
Configuring the provisioning server to use the WebSphere
Everyplace Device Manager
You can use the IBM WebSphere Everyplace Device Manager (WEDM) to provide
IBM Workplace rich client features, capabilities, and upgrades to users.
If you want to provide rich client features, capabilities, or updates using WEDM or
if you have already done so using the Eclipse update manager and want to switch
to WEDM, configure the Workplace server as described below.
Note: Updating the rich client from release 2.0.1 to 2.5 with WEDM is not
supported. Updates from release 2.0.1 to 2.5 must be done using the update
manager. Once all clients have been updated to 2.5, the provisioning server
can be configured to use WEDM for future updates.
Note: See the WEDM server Information Center for details on WEDM
configuration.
Use these instructions to set the rich client provisioning server equal to the Web
address of the WEDM server.
1. On the IBM WebSphere Portal Server, edit the requirements.xml file found in
the following directory by removing the comment designation from the
WEDM provider preference setting. Example:
<websphere_install_dir>\AppServer\installedApps\sugar\wps.ear\wps.war\themes\rcpml\
Edit the file to look as follows:
<requirements>
<preference
plugin="com.ibm.rcp.provisioning"
key="com.ibm.rcp.provisioning.feature.provider"
value="com.ibm.rcp.provisioning.wedm.provider.WEDMProvider"/>
</requirements>
2. Log into the WebSphere Administrative Console using an administrator user
name and password. Enter a URL such as
http://myservernam.abxdev.ibm.com:9091/admin.
3. Click Resources/URL Providers.
4. Click Node and delete its contents.
Chapter 8 Rich Client Installation and Configuration
331
5.
6.
7.
8.
9.
Click Apply to display the IBM Workplace client provisioning server URL.
Click Default URL Provider.
Click URLs.
Click on the entry for Workplace Client Provisioning server.
Edit the fields to read as follows:
v Name = Workplace client provisioning server
v JNDI Name = url/wctprovisioningurl
v Specification = <protocol>://<wedmserver
hostname>/dmserver/SyncMLDMServletAuthRequired Example:
http://freefall.abxdev.ibm.com/dmserver/SyncMLDMServletAuthRequired
10. Click Apply and Save.
11. Reboot your server.
Related tasks
Pushing rich client component updates using WEDM
Rich client installation and configuration checklist
Updating the rich client capabilities
Installing the provisioning server
Uninstalling the provisioning server
Uninstalling the rich client on the user desktop
Unless you have been instructed to uninstall the rich client on your desktop, you
will probably never need to perform this task. Your administrator will install all
rich client component updates on a central server and will make them available to
you. The process of updating from one release to another should be transparent to
you. When you log in to the IBM Workplace rich client, or when you use the
Switcher bar in the rich client, you will be notified of component updates. You do
not need to uninstall one version and install another to obtain the latest release.
See your administrator for details.
Uninstalling the rich client from a Windows system
Uninstalling the rich client from a Linux system
If you have been instructed to reinstall the rich client, note that you must uninstall
the IBM Workplace rich client before reinstalling either the same version or a more
recent version.
Related tasks
Installing rich client software on the desktop
Uninstalling Windows single sign-on
Uninstalling Linux single sign-on
Uninstalling the IBM Workplace rich client on Microsoft Windows
If instructed by your administrator, you can uninstall the IBM Workplace rich
client from a Microsoft Windows workstation using this procedure.
The uninstall program will prompt you to remove user data. If you click Yes, all
local data including application files for IBM Workplace Messaging and IBM
Workplace Documents, data replicated from the IBM Workplace server, the local
332
Installation and Upgrade Guide
document store, workspace configuration, and downloaded programs will be
deleted. Click Yes only if you are certain that there is nothing you want to keep.
Note: You must uninstall the IBM Workplace rich client before reinstalling the
same version or installing a more recent version.
1. Click Add/Remove Programs from the Control Panel.
2. Locate IBM Workplace rich client in the application list.
3. Click Remove.
4. Respond to the prompts that appear.
5. Click Finish to exit.
6. Delete the C:\Documents and Settings\<username>\wctpinstall-temp directory:
7. Restart the machine.
Related tasks
Uninstalling the rich client
Installing the rich client
Uninstalling the IBM Workplace rich client on Linux
If instructed by your administrator, you can uninstall the IBM Workplace rich
client from a Linux workstation using this procedure.
The uninstall program will prompt you to remove user data. If you click Yes, all
local data including application files for IBM Workplace Messaging and IBM
Workplace Documents, data replicated from the IBM Workplace server, the local
document store, workspace configuration, and downloaded programs will be
deleted. Click Yes only if you are certain that there is nothing you want to keep.
Note: You must uninstall the IBM Workplace rich client before reinstalling the
same version or installing a more recent version.
1. Navigate to the installation directory chosen during IBM Workplace rich client
installation.
2.
3.
4.
5.
Note: The default directory is /opt/IBM/Workplace rich client components.
Navigate to the _uninst subdirectory.
Run the ./uninstall.bin program.
Delete the Setup_wct_platform.bin file.
Restart the machine.
Related tasks
Uninstalling the rich client
Installing the rich client
Uninstalling the rich client provisioning server
For users to update to a new IBM Workplace rich client release, you must uninstall
the IBM Workplace rich client provisioning server and reinstall the latest
provisioning server from IBM. When the user logs in to the rich client, he will be
notified of component updates and be prompted to accept them.
Note: The system checks the provisioning server for updates each time the user
logs in to the rich client. It also checks the provisioning server for updates
Chapter 8 Rich Client Installation and Configuration
333
when the user switches applications using the rich client Switcher bar. When
the user logs in, the system also checks the RCPML file to determine what
capabilities are available to the user.
You must uninstall the rich client provisioning server from the IBM Workplace
server system before installing a new release.
Related tasks
Installing the provisioning server
Updating the provisioning server
Uninstalling the provisioning server from Windows
Uninstalling the provisioning server from UNIX
Uninstalling the provisioning server from i5OS
Updating the provisioning server using WEDM
Rich client installation and configuration checklist
Uninstalling the provisioning server using Windows
Use the following steps to uninstall the provisioning server from the IBM
Workplace server using Microsoft Windows.
Note: You must uninstall the provisioning server before reinstalling.
1. Click Add/Remove Programs from the Control Panel.
2. Locate IBM Workplace rich client provisioning components in the application
list.
3. When prompted, specify the language in which to display the screen text and
then click OK to continue.
4. Follow the directions on the screens.
5. If prompted, select all the rich client features to uninstall and then click Next to
continue.
6. Read the summary of what will be uninstalled and then click Next to continue.
7. Click Finish to exit.
Related tasks
Uninstalling the provisioning server
Updating the provisioning server
Installing the provisioning server
Uninstalling the provisioning server from UNIX
Use the following steps to uninstall the provisioning server from the IBM
Workplace server using UNIX.
Note: You must uninstall the provisioning server before reinstalling.
1.
2.
3.
4.
Open a command prompt window.
Navigate to the root install location the administrator specified during install.
Navigate to the _uninst directory.
Run the uninstaller.bin program.
5. Uninstall all features.
6. Exit the program.
Related tasks
Uninstalling the provisioning server
334
Installation and Upgrade Guide
Updating the provisioning server
Uninstalling the provisioning server from i5/OS
Use the following steps to uninstall the provisioning server from the IBM
Workplace server using i5/OS.
Note: You must uninstall the provisioning server before reinstalling.
1. Open a QShell session on the i5/OS system.
2. Start the i5/OS uninstall program, i5OSuninstall.sh, from the _uninst directory.
3.
4.
5.
6.
7.
8.
Note: The i5/OS uninstall.sh program is located in the /wct25/_uninst/
directory. For example, if your Workplace server is myLWP, it is located
in the /qibm/userdata/webas5/base/myLWP/wct25/_uninst/ directory.
Select the desired language by typing the associated number next to it and click
Enter. Enter 0 and click Return to continue.
Continue to the feature selection screen. By default all the components are
selected. Click Enter to continue or select specific options to uninstall.
Enter the administrative user ID.
Enter the administrative password followed by the confirmation password and
press Enter to continue.
Once all the components are removed, click 3 to exit the installation program.
Optionally delete the Logs directory using the following command, given that
your IBM Workplace server name is myLWP. rm -rf
/qibm/userdata/webas5/base/myLWP/wct25/
Related tasks
Uninstalling the provisioning server
Updating the provisioning server
Changing the search bar appearance
You can add a graphic image, such as your company logo, to the search bar in the
rich client user interface. The IBM Workplace graphic will still be visible. You can
also change the background color of the search bar.
1. To add your graphic to the search bar, replace the supplied brand.gif file with
your graphic. You must use the brand.gif file name and it must reside in the
rcp\rcp\eclipse\plugins\com.ibm.rcp.platform\brand.gif file path.
2. To replace the supplied color of the search bar with another color, change the
color values in the rcp\rcp\eclipse\plugins\com.ibm.rcp.platform\plugin.xml
file.
Note: The color values appear italicized in the following file excerpt.
<extension
point="org.eclipse.ui.themes">
<colorDefinition
label="%BlueBarBackgroundColorBegin"
value="152,200,248"
id="com.ibm.rcp.platform.BLUE_BAR_BACKGROUND_BEGIN">
<description>
</description>
</colorDefinition>
<colorDefinition
label="%BlueBarBackgroundColorEnd"
Chapter 8 Rich Client Installation and Configuration
335
value="152,200,248"
id="com.ibm.rcp.platform.BLUE_BAR_BACKGROUND_END">
<description>
</description>
</colorDefinition>
</extension>
Related tasks
Rich client installation and configuration checklist
Installing the rich client
336
Installation and Upgrade Guide
Chapter 9 Completing the Network Deployment Setup
This chapter provides information about steps to complete the setup of IBM
Workplace Collaboration Services in a Network Deployment environment.
Phase 9: Completing Network Deployment setup
To complete the IBM Workplace Collaboration Services setup in a Network
Deployment environment, a few additional steps are necessary.
v Update the WebSphere Portal EAR file for Network Deployment.
v Federate and cluster network nodes.
v Configure load balancing for SIP services and HTTP.
v Update rich client configuration files for Network Deployment.
v Update and distribute the WebSphere Application plug-in.
v Enable dynamic caching.
v Enable Search in the cluster.
v Enable Messaging in the cluster.
v Edit WebSphere settings for a Network Deployment.
v Apply fix packs to the Network Deployment servers.
When setup is complete, you can start IBM Workplace Collaboration Services.
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Updating the WebSphere Portal EAR file for Network
Deployment
Themes, screens, skins, and images are managed as part of the main IBM
WebSphere Portal enterprise application and are part of the WebSphere Portal EAR
file (wps.ear). The provisioning server installation copies these components into the
expanded version of the wps.ear on the WebSphere Application server. When
installing the provisioning server in a Network Deployment environment (cluster),
the archive copy of the wps.ear file in the WebSphere Application Server
configuration repository must be updated with this additional content. This topic
addresses these considerations.
The provisioning server adds content to the wps.ear deployed on the node where
it was installed. In order for that content to be replicated to additional nodes
during their federation and during application synchronization, you must
incorporate that content into the archive copy of wps.ear in the WebSphere
configuration directory.
Note: These instructions assume that you have installed the rich client
provisioning server using a Custom installation and that you installed
everything except the two HTTP content selections.
You must perform these steps on the first node (Node 1) before federation.
1. Stop the Portal server and start the server1 server.
© Copyright IBM Corp. 2002, 2005
337
On the Portal server, type the following command:
stopserver WebSphere_Portal
On the server1 server, type the following command:
startserver server1
2. Export the WebSphere Portal EAR file according to your network configuration
using the following sequence:
a. Change directories to the Application Server bin directory, for example
C:\WebSphere\AppServer\bin.
b. Use the wsadmin command to export the WebSphere Portal EAR file to a
temporary directory. All commands must be entered on one line. Example
syntax is shown below:
AIX, Linux, and Solaris
./wsadmin.sh -user <admin_user_id> -password < admin_password> -c
’$AdminApp export wps /tmp/wps.ear’
Note: <admin_user_id> is the administrator’s user ID and <admin_password>
is the administrator’s password.
Windows
wsadmin.bat -user <admin_user_id> -password < admin_password> -c
"$AdminApp export wps C:/temp/wps.ear"
3. Expand the wps.ear file that was created in the above step using the following
sequence:
a. Create the C:\Temp\wps_expanded directory for Windows or the
/tmp/wps_expanded directory for UNIX.
b. Use the EARExpander tool to expand the contents of the exported wps.ear
file. All commands must be entered on one line. Example syntax is shown
below:
AIX, Linux, and Solaris
./EARExpander.sh -ear /tmp/wps.ear -operationDir /tmp/wps_expanded
-operation expand
This creates the wps.war with its directories expanded in
/tmp/wps_expanded:
/tmp/wps_expanded/wps.war
Windows
EARExpander.bat -ear C:\Temp\wps.ear -operationDir
C:\Temp\wps_expanded -operation expand
This creates the wps.war with its directories expanded in
Temp\wps_expanded:
C:\Temp\wps_expanded\wps.war
4. Place the provisioning server content into the correct directory within the
expanded EAR.
The content that must be added for the provisioning server is in the following
directories:
AIX, Linux, and Solaris
v <install_root>/AppServer/installedApps/<nodename>/wps.ear/wps.war/themes/rcpml
v <install_root>/AppServer/installedApps/<<nodename>/wps.ear/wps.war/screens/rcpml
338
Installation and Upgrade Guide
v <install_root>/AppServer/installedApps/<nodename>/wps.ear/wps.war/skins/rcpml
v <install_root>/AppServer/installedApps/<nodename>/wps.ear/wps.war/images/apps
Windows
v <install_root>\AppServer\installedApps\<nodename>\wps.ear\wps.war\themes\rcpml
v <install_root>\AppServer\installedApps\<nodename>\wps.ear\wps.war\screens\rcpml
v <install_root>\AppServer\installedApps\<nodename>\wps.ear\wps.war\skins\rcpml
v <install_root>\AppServer\installedApps\<nodename>\wps.ear\wps.war\images\apps
Note: <install_root> represents the Workplace Collaboration Services root
installation directory and <node-name> represents the name used for the
first node (Node 1) of the cluster as specified during installation.
Place the content in the following directory:
AIX, Linux, and Solaris
/tmp/wps_expanded
Note: You must create the four subdirectories in the wps_expanded
subdirectories.
v wps.war/themes/rcpml
v wps.war/screens/rcpml
v wps.war/skins/rcpml
v wps.war/images/apps
Windows
C:\Temp\wps_expanded
Note: You must create the four subdirectories in the wps_expanded
subdirectories.
v wps.war\themes\rcpml
v wps.war\screens\rcpml
v wps.war\skins\rcpml
v wps.war\images\apps
5. Use the EARExpander command to collapse the EAR directory back into an
EAR file.
a. Rename the original wps.ear file (exported to the temp directory) to
wps.ear.original.
b. Run the EARExpander tool using the following arguments to create a new
archive copy of wps.ear in your temporary directory.
AIX, Linux, and Solaris
./EARExpander.sh -ear /tmp/wps.ear -operationDir /tmp/wps_expanded
-operation collapse
Windows
EARExpander.bat -ear C:\Temp\wps.ear -operationDir C:\Temp\wps_expanded
-operation collapse
Chapter 9 Completing the Network Deployment Setup
339
6. Update the WebSphere configuration directory with the new wps.ear archive
using the wsadmin command to update the WebSphere Portal EAR.
AIX, Linux, and Solaris
Change the directory to <install_root>/AppServer/bin and type the following:
./wsadmin.sh -user <admin_user_id> -password <admin_password> -c
’$AdminApp install /tmp/wps.ear {-update -appname wps}’
Windows
Change the directory to <install_root>\AppServer\bin and type the following:
wsadmin.bat -user <admin_user_id> -password <admin_password> -c
"$AdminApp install C:\Temp/wps.ear {-update -appname wps}"
7. Stop the server1 server and restart the Portal server.
Note: Updates to the configuration of a WebSphere Portal cluster must occur
on the Deployment Manager and be resynchronized with the other
nodes in the cluster. If updates are made to individual nodes in the
cluster, the updates will be lost when the master configuration on the
Deployment Manager resynchronizes with the nodes.
Related tasks
Phase 9: Completing Network Deployment setup
“IBM Workplace rich client installation and configuration checklist” on page
295
“Installing and configuring the provisioning server” on page 298
“Updating rich client configuration files for Network Deployment” on page 354
Federating and clustering network nodes
Copying files from Node 1 to subsequent nodes
To allow IBM Workplace Collaboration Services to function properly, several files
must be accessible to all nodes in the deployment.
1. To finish connecting the node to a remote DBMS server, copy the wmm.xml file
from Node 1 to complete the connection.
2. To use the node as a rich client provisioning server, copy the following
directories from Node 1:
This step must be done before federating the node to the cell.
<install_root>/PortalServer/shared/app/WEB-INF/tld
<install_root>/PortalServer/shared/app
<provisioning_server_installation_root>/wedm_extensions
Now perform the configuration tasks covered in ″Network Deployment installation
and configuration road map″ that are specific to this node.
Related tasks
Network Deployment installation and configuration road map
Federating and clustering network nodes
Related reference
Root installation directories
340
Installation and Upgrade Guide
Federating nodes to a cell
After you install IBM Workplace Collaboration Services on Network Deployment
nodes, use the addnode command to federate the nodes, which adds them to the
Network Deployment cell. The procedure is slightly different for Node 1 than it is
for Node 2 and subsequent nodes.
Attention: If you plan to install the rich client provisioning server on this node,
you must do so before federating a node. Installation of the provisioning server
will fail if you attempt to install after federating the node.
For more information on WebSphere Application Server and Network
Deployments, go to the WebSphere Application Server Information Center at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
Related concepts
“Phase 8: Rich client installation and configuration” on page 295
Related tasks
Unfederating a node from a cell
Network Deployment installation and configuration road map
Determining the SOAP port to use to connect to the Deployment Manager
Federating and clustering network nodes
Federating Node 1:
After you install IBM Workplace Collaboration Services on Node 1, use the
addnode command to federate the node, which adds it to the Network
Deployment cell. Depending on the size and location of the node that you
incorporate into the cell, this command can take a few minutes to complete. Follow
the steps for IBM AIX, Linux, and Sun Solaris or Microsoft Windows.
Attention: If you plan to install the rich client provisioning server on this node,
you must do so before federating a node. Installation of the provisioning server
will fail if you attempt to install after federating the node.
AIX, Linux, and Solaris:
Follow these steps to federate Node 1 running under AIX, Linux, or Solaris.
1. In the node’s addNode script file, increase the heap size to 512 MB, which is
the recommended size:
a. In a text editor, open the addNode script file, located in the
<install_root>/AppServer/bin directory.
b. Add the -Xmx512m option to each Java command.
c. Save and close the revised script file.
2. Open the node’s removeNode script file. Make the same changes to the
maximum heap size and save the file.
3. Run the following command from the node’s
<install_root>/PortalServer/rootscripts directory:
./stopWorkplaceServices.sh
4. (Linux only) On the Deployment Manager, add each node’s hostname and full
DNS hostname in the /etc/hosts file and save the file.
Without the node’s name in the hosts file, you will receive errors when you try
to add a node to the cell.
Chapter 9 Completing the Network Deployment Setup
341
5. On the Deployment Manager, open a command prompt and navigate to the
<install_root>/AppServer/DeploymentManager/bin directory.
6. Type the following command:
./startManager.sh
7. From the node you want to add, type the following command on a single line
from the <install_root>/AppServer/bin directory. The command is different for
the first node in the cluster.
./addNode.sh deployment_manager_hostport_number -username
admin_user_id -password admin_password -includeapps
After a node has been successfully added, a confirmation message displays.
Windows:
Follow these steps to federate Node 1 running under Windows.
1. In the node’s addNode batch file, increase the heap size to 512 MB, which is
the recommended size:
a. In a text editor, open the addNode batch file, located in the
<install_root>\AppServer\bin directory.
b. Add the -Xmx512m option to each Java command.
c. Save and close the revised batch file.
2. Open the node’s removeNode batch file. Make the same changes to the
maximum heap size and save the file.
3. Run the following command from the node’s
<install_root>\PortalServer\rootscripts directory:
stopWorkplaceServices.bat
4. On the Deployment Manager, open a command prompt and navigate to the
<install_root>\AppServer\DeploymentManager\bin directory.
5. Type the following command:
startmanager
6. From the node you want to add, type the following command on a single line
from the <install_root>\AppServer\bin directory. The command is different for
the first node in the cluster.
addnode deployment_manager_hostport_number -username
admin_user_id -password admin_password -includeapps
After a node has been successfully added, a confirmation message displays.
Related concepts
“Phase 8: Rich client installation and configuration” on page 295
Related tasks
Federating Node 2 and subsequent nodes
Updating the Deployment Manager after federating nodes
Unfederating a node from a cell
Network Deployment installation and configuration road map
Determining the SOAP port to use to connect to the Deployment Manager
Related reference
Root installation directories
Federating Node 2 and subsequent nodes:
342
Installation and Upgrade Guide
After you install IBM Workplace Collaboration Services on Node 2 and subsequent
nodes, use the addnode command to federate the node, which adds it to the
Network Deployment cell. Depending on the size and location of the node that
you incorporate into the cell, this command can take a few minutes to complete.
Follow the steps in this topic for IBM AIX, Linux, and Sun Solaris or Microsoft
Windows.
Attention: If you plan to install the rich client provisioning server on this node,
you must do so before federating a node. Installation of the provisioning server
will fail if you attempt to install after federating the node.
AIX, Linux, and Solaris:
Follow these steps to federate nodes running under AIX, Linux, or Solaris.
1. In the node’s addNode script file, increase the heap size to 512 MB, which is
the recommended size:
a. In a text editor, open the addNode script file, located in the
<install_root>/AppServer/bin directory.
b. Add the -Xmx512m option to each Java command.
c. Save and close the revised script file.
2. Open the node’s removeNode script file. Make the same changes to the
maximum heap size and save the file.
3. Run the following command from the node’s
<install_root>/PortalServer/rootscripts directory:
./stopWorkplaceServices.sh
4. (Linux only) On the Deployment Manager, add each node’s hostname and full
DNS hostname in the /etc/hosts file and save the file.
Without the node’s name in the hosts file, you will receive errors when you try
to add a node to the cell.
5. On the Deployment Manager, open a command prompt and navigate to the
<install_root>/AppServer/DeploymentManager/bin directory.
6. Type the following command:
./startManager.sh
7. From the node you want to add, type the following command on a single line
from the <install_root>/ApServer/bin directory.
./addNode.sh deployment_manager_hostport_number -username
admin_user_id -password admin_password
After a node has been successfully added, a confirmation message displays.
Windows:
Follow these steps to federate nodes running under Windows.
1. In the node’s addNode batch file, increase the heap size to 512 MB, which is
the recommended size:
a. In a text editor, open the addNode batch file, located in the
<install_root>\AppServer\bin directory.
b. Add the -Xmx512m option to each Java command.
c. Save and close the revised batch file.
2. Open the node’s removeNode batch file. Make the same changes to the
maximum heap size and save the file.
Chapter 9 Completing the Network Deployment Setup
343
3. Run the following command from the node’s
<install_root>\PortalServer\rootscripts directory:
stopWorkplaceServices.bat
4. On the Deployment Manager, open a command prompt and navigate to the
<install_root>\AppServer\DeploymentManager\bin directory.
5. Type the following command:
startmanager
6. From the node you want to add, type the following command on a single line
from the <install_root>\AppServer\bin directory. The command is different for
the first node in the cluster.
addnode deployment_manager_hostport_number -username
admin_user_id -password admin_password
After a node has been successfully added, a confirmation message displays.
Related concepts
“Phase 8: Rich client installation and configuration” on page 295
Related tasks
Federating Node 1
Updating the Deployment Manager after federating nodes
Unfederating a node from a cell
Network Deployment installation and configuration road map
Determining the SOAP port to use to connect to the Deployment Manager
Related reference
Root installation directories
Unfederating a node from a cell:
Follow these steps to unfederate (remove) a node from the cell.
Before you begin:
1. Stop Workplace Collaboration Services by typing the following commands from
the <install_root>\PortalServer\rootscripts directory:
IBM AIX, Linux, and Sun Solaris
./stopWorkplaceServices.sh
Microsoft Windows
stopWorkplaceServices.bat
2. On the Deployment Manager, open a command prompt and navigate to the
<install_root>\AppServer\DeploymentManager\bin directory.
3. Type the following command:
AIX, Linux, and Solaris
./startManager.sh
Windows
startmanager
Unfederating a node from the cell:
From the node you want to remove, type the following command on a single line
from the <install_root>\AppServer\bin directory.
AIX, Linux, and Solaris
344
Installation and Upgrade Guide
./removeNode.sh -user admin_user_id -password admin_password
Windows
removenode -user admin_user_id -password admin_password
where:
v admin_user_id is the WebSphere Application Server administrator user name.
v admin_password is the administrator user password.
After a node has been successfully removed, a confirmation message displays.
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Federating nodes to a cell
Related reference
Root installation directories
Determining the SOAP port to use to connect to the Deployment Manager:
If you do not know which SOAP port to use to connect to the Deployment
Manager, you can find it by performing the following steps:
1.
2.
3.
4.
Open the WebSphere Administrative Console for the Deployment Manager.
Select System Administration → Deployment Manager.
Select End Points in the Additional Properties table.
Select SOAP_CONNECTOR_ADDRESS.
Refer to the topic ″Installing in a Network Deployment,″ for additional installation
and setup information.
Related tasks
Opening the WebSphere Administrative Console
Installing in a Network Deployment
Creating the IBM Workplace Collaboration Services cluster
In a Network Deployment, you create a Workplace server cluster to provide load
balancing and better performance.
After you have installed IBM Workplace Collaboration Services on the first node
and federated the node to the cell, you can create the cluster. Then update the
Deployment Manager with cluster information. When you install other nodes, add
them to the cluster.
For more information on creating clusters, go to the WebSphere Portal Information
Center at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
Related tasks
Creating the cluster and adding Node 1
Updating the Deployment Manager with cluster information
Adding subsequent nodes to the cluster
Network Deployment installation and configuration road map
Federating and clustering network nodes
Creating the cluster and adding Node 1:
Chapter 9 Completing the Network Deployment Setup
345
Follow these steps to create an IBM Workplace Collaboration Services server
cluster, and then add the first node to the cluster.
Creating the Workplace Collaboration Services cluster:
1. On the Deployment Manager, open the WebSphere Administrative Console and
click Servers → Clusters.
2. Click New to open the Create New Cluster page.
3. Provide the following information:
Property
Description
Cluster name
Use a descriptive name; for example, LWPCluster.
Prefer local enabled
Select this option to improve performance by enabling client
requests to be sent to local EJBs.
Internal Replication
Domain
Select this option.
Select an existing
server to add to this
cluster
Select this option and then from the list, select Node 1.
Weight
Leave the default value of 2.
Create Replication
Entry in this Server
Select this option.
4. Click Next.
5. Provide the following information:
Property
Description
Name
Enter a name for the cluster member; for example,
WorkplaceServer01.
Node
Select the node name.
Weight
Leave the default value of 2.
Generate Unique
HTTP ports
Select this option.
Create Replication
Entry in this Server
Select this option.
6. Click Next and review the summary of changes.
7. Click Finish to complete the configuration.
8. Select Synchronize changes with Nodes, and then click Save.
You must save the configuration before adding any other nodes to the cluster.
Connecting Node 1 to the cluster:
1. On Node 1, open the DeploymentService.properties file, stored
in<install_root>\PortalServer\shared\app\config\services.
2. Enter the cluster name (for example, LWPCluster) as the value for
wps.appserver.name and save the file.
Verifying the cluster members:
1. To view the cluster topology, open the WebSphere Administrative Console on
the Deployment Manager and click Servers → Cluster Topology. The new
server cluster members display in the application server view.
2. Click Servers → Clusters → Server Cluster and start the clusters you defined.
346
Installation and Upgrade Guide
This may take a few minutes.
Now update the Deployment Manager with information about the new cluster.
Related concepts
Creating the IBM Workplace Collaboration Services cluster
Related tasks
Opening the WebSphere Administrative Console
Updating the Deployment Manager with cluster information
Adding subsequent nodes to the cluster
Installing in a Network Deployment
Related reference
Root installation directories
Updating the Deployment Manager with cluster information:
Follow these steps to add cluster information to the Deployment Manager. You
must already have created a cluster, and added the first node to the cluster.
1. On the Deployment Manager, navigate to the
<install_root>\WorkplaceServer\install directory, where <install_root> is the
root installation directory for IBM Workplace Collaboration Services.
2. Open the installDM.properties file with a text editor.
3. Add the cluster name as the value for ″lwp.clusterName=″ (for example,
lwp.clusterName=LWPCluster).
4. Save the file.
5. Open a command prompt window.
6. Navigate to the <install_root>\AppServer\bin directory.
7. Run the following command:
IBM AIX, Linux, and Sun Solaris
./setupCmdLine.sh
Microsoft Windows
setupCmdLine.bat
8. Navigate to the <install_root>\WorkplaceServer\install directory.
9. Run the following command:
AIX, Linux, and Solaris
./lwpDMconfig.sh >lwpDMconfig.log
Windows
lwpDMconfig.bat >lwpDMconfig.log
Check the log file and correct any errors before proceeding. You receive a
″Build Successful″ message when the update is completed without errors.
10. Restart the Deployment Manager.
Related tasks
Adding subsequent nodes to the cluster
Installing in a Network Deployment
Related reference
Root installation directories
Adding subsequent nodes to the cluster:
Chapter 9 Completing the Network Deployment Setup
347
After you have installed and set up IBM Workplace Collaboration Services on a
new node, add it to the cluster.
1. On the Deployment Manager, go to the WebSphere Administrative Console
and click Servers → Clusters.
2. Select the cluster you created for Node 1.
3. Select Cluster Member and click New.
4. Provide the following information, and then click Apply:
Property
Description
Name
Enter a name for the cluster member; for example,
WorkplaceServer02.
After these servers become part of the cluster, the WebSphere
Portal servers on these nodes are renamed to the name you
specify.
Node
Select the node name; for example, Node 2.
Generate Unique
HTTP ports
Select this option.
5. Click Next and review the summary of changes.
6. Click Finish to complete the configuration.
7. Select Synchronize changes with Nodes, and then click Save.
By default, automatic synchronization occurs between every node when a
change is made to the configuration of the cell, which is checked for updates
once every minute.
8. From the WebSphere Administrative Console, click Application Servers.
9. In the Name column, click the name of the additional Workplace server
running on the node; for example, WorkplaceServer02.
10. Click Process Definition in the Additional Properties section of the
Configuration tab for the server.
11. Click Java Virtual Machine in the Additional Properties section of the Process
Definition tab.
12. Click Custom Properties in the Additional Properties section of the Java
Virtual Machine tab.
13. Click pzn.root.dir.
14. Edit the path name in the Value field so that it refers to the node directory for
the new node. By default, this path name refers to the directory for the first
node added to the cell.
For example, in IBM AIX and Linux:
<install_root>/AppServer/wpcp/config/node_name/WebSphere_Portal/runtime
where node_name is the name of the Workplace node.
15. Click Apply, and then click OK.
16. Click wcm.root.dir.
17. Edit the path name in the Value field so that it refers to the node directory for
the new node. By default, this path name refers to the directory for the first
node added to the cell.
For example, in AIX and Linux:
<install_root>/AppServer/wpcp/config/node_name/WebSphere_Portal/author
18. Click Apply, and then click OK.
348
Installation and Upgrade Guide
Connecting the new node to the cluster:
To connect the new node to the cluster, perform these steps:
1. On the new node, open the DeploymentService.properties file, stored
in<install_root>\PortalServer\shared\app\config\services.
2. Type the cluster name (for example, LWPCluster) as the value for
wps.appserver.name.
3. Save the file.
Now perform the next steps covered in ″Network Deployment installation and
configuration road map.″
Related tasks
Opening the WebSphere Administrative Console
Creating the cluster and adding Node 1
Network Deployment installation and configuration road map
Related reference
Root installation directories
Updating the Deployment Manager after federating nodes
After you federate nodes to a cell, make the following adjustments on the
Deployment Manager.
Removing the Administrative Console application:
After you add Node 1 node to the cell, remove the Administrative Console
application from the Deployment Manager. You can no longer administer the node
locally.
1. From the WebSphere Administrative Console on the Deployment Manager, click
Applications → Enterprise Applications.
2. Page through the applications until you find the WpsAdminconsole
application.
3. Select the application, and click Uninstall.
4. Select Synchronize changes with nodes.
5. Save your changes.
Adding Virtual Host entries for HTTP:
If you used the default HTTP port values when installing on the node, the
Deployment Manager might require a virtual host entry for the port used to access
WebSphere Portal. Perform these steps after federating Node 1 and all subsequent
nodes.
1. From the WebSphere Administrative Console on the Deployment Manager, click
Environment → Virtual Hosts.
2. Click the default_host entry or the entry for the virtual host that is being used
to access the WebSphere Portal application.
3. Select Host Aliases.
4. On the Host Aliases panel, verify that one of the host name and port
combinations matches the values used to access WebSphere Portal (for example,
″*:9081″). If the Host Alias is correct, proceed to the last step.
To add a new Host Alias, click New.
Chapter 9 Completing the Network Deployment Setup
349
5. For each host alias, enter name ″*″ and <port>, where <port> represents the port
used by the HTTP server.
For example, with the following node values:
v Node1: HTTPS transport of 9444
v Node2: HTTP transport of 9083
v Node2: HTTPS transport of 9446
the Host Name and Port values should be *:9444, *:9083, *:9446.
6. Click OK, then save the changes.
7. Start the WebSphere Portal server and verify that it is operational by logging in
from a browser and typing the administrator user name and password.
Related tasks
Opening the WebSphere Administrative Console
Federating nodes to a cell
Network Deployment installation and configuration road map
Configuring load balancing for SIP services and HTTP
This topic describes how to configure the Network Dispatcher to set up load
balancing and failover of SIP services (used for instant messaging and Web
conferences). It also describes how to set up load balancing for an HTTP server
cluster. It assumes that you have already installed the Edge Server components on
a Network Dispatcher server, as described in Phase 2, and updated rich client
configuration files, as described in Phase 6. For more information about
configuring and troubleshooting, see the Edge components Information Center at
http://www-306.ibm.com/software/webservers/appserv/ecinfocenter.html.
Before you configure (Windows only)
On a Network Dispatcher server running on Microsoft Windows, disable the TCP
offloading function to avoid conflicts with the Network Dispatcher monitoring
activities.
1. Open the Network Adapter properties page.
2. Click Configure.
3. From the configuration page for the network adapter, click the Advanced tab.
4. For each of the Offload properties, change the value to Off.
5. Click OK to close all open dialog boxes.
6. Restart the server.
Now configure the Network Dispatcher using one of these methods:
v Using the command line
v Using the graphical user interface
v Using a configuration script
Configuring through the command line
The dsserver command is the most direct means for configuring the Network
Dispatcher.
1. Start the Network Dispatcher if it is not already running.
2. Type the following command to open the command line interface:
dscontrol
350
Installation and Upgrade Guide
3. Start up the executor with the following command.
dscontrol executor start
4. Define the NFA (non-forwarding address) of your machine with the following
command:
dscontrol executor set nfa <IP_address>
5. Once you are connected to the host and the executor is running, create a
cluster based on the cluster address you reserved with the following
command:
dscontrol cluster add <cluster_name>
6. Add an alias to your NIC with the following command:
dscontrol executor configure <cluster_address>
7. Add the ports with the following commands:
dscontrol port add <cluster_address>:80
dscontrol port add <cluster_address>:443
dscontrol port add <cluster_address>:5060
dscontrol port add <cluster_address>:5061
8. Set the sticky time for Ports 5060 and 5061.
dscontrol port set <cluster_address>:5060 stickytime 120
dscontrol port set <cluster_address>:5061 stickytime 120
9. Add the appropriate servers for each port:
dscontrol server add <cluster_address>:80:<Node1>
dscontrol server add <cluster_address>:80:<Node2>
dscontrol server add <cluster_address>:443:<Node1>
dscontrol server add <cluster_address>:443:<Node2>
dscontrol server add <cluster_address>:5060:<Node1>
dscontrol server add <cluster_address>:5060:<Node2>
dscontrol server add <cluster_address>:5061:<Node1>
dscontrol server add <cluster_address>:5061:<Node2>
10. Start the manager with the following command:
dscontrol manager start
11. Setup the appropriate advisors with the following command:
dscontrol advisor start http 80
dscontrol advisor start https 443
dscontrol advisor start connect 5060
dscontrol advisor start connect 5061
12. Use the following command to close the command line interface:
exit
Configuring through the graphical user interface
Before starting, you must have an additional static IP address on the same subnet
as the Network Dispatcher and nodes. This address must have a DNS entry for use
by clients. This cluster IP address is set up when you configure the load balancing;
do not set it manually through the operating system. The regular IP address used
by the Network Dispatcher is used for administration purposes and is called the
non-forwarding address (NFA).
1. Start the Network Dispatcher if it is not already running.
Chapter 9 Completing the Network Deployment Setup
351
2. Launch the Load Balancer graphical user interface (GUI). You can also run the
Load Balancer from a command line. For more information, see the Load
Balancer Administration Guide.
3. Right-click the Dispatcher entry and choose Connect to Host.
4. Select your machine name, then click OK.
5. Right-click the hostname and choose Start Executor.
6. Right-click the Executor and choose Add Cluster.
7. Enter the cluster name and the static IP address you have reserved for the
cluster. Enter the primary host for the cluster, select Configure this cluster?,
and click OK.
The cluster name will appear under the Executor.
8. Right-click the cluster name and choose Add Port.
9. Enter 80, choose MAC Based Forwarding, and click OK.
10. Right-click Port 80 and choose Add Server.
11. Enter the host name for Node 1, then click OK.
12. Repeat the previous two steps for Node 2 and all subsequent nodes
cluster.
13. Right-click the cluster name and choose Add Port.
14. Enter 443, choose MAC Based Forwarding, and click OK.
15. Right-click Port 443 and choose Add Server.
16. Enter the host name for Node 1, then click OK.
17. Repeat the previous two steps for Node 2 and all subsequent nodes
cluster.
18. Right-click the cluster name and choose Add Port.
19. Enter 5060, choose MAC Based Forwarding, and click OK.
20. Right-click Port 5060 and choose Add Server.
21. Enter the host name for Node 1, then click OK.
22. Repeat the previous two steps for Node 2 and all subsequent nodes
cluster.
23. Right-click the cluster name and choose Add Port.
24. Enter 5061, choose MAC Based Forwarding, and click OK.
25. Right-click Port 5061 and choose Add Server.
26. Enter the host name for Node 1, then click OK.
27. Repeat the previous two steps for Node 2 and all subsequent nodes
cluster.
28. Click Port 5060 and click the Configuration Settings tab.
29. Change the Sticky time entry to 120 seconds. Then click Update
Configuration.
30. Click Port 5061 and click the Configuration Settings tab.
in the
in the
in the
in the
31. Change the Sticky time entry to 120 seconds. Then click Update
Configuration.
32. Right-click the host entry and choose Start Manager. Click OK to accept the
defaults.
A Manager entry is added to the tree under the host.
33. Right-click the Manager and choose Start Advisor.
34. In the Start an advisor dialog box, choose HTTP as the Advisor name and
change the Port number to 80. Click OK.
352
Installation and Upgrade Guide
35. In the Start an advisor dialog box, choose HTTPS as the Advisor name and
change the Port number to 443. Click OK.
36. In the Start an advisor dialog box, choose Connect as the Advisor name and
change the Port number to 5060. Click OK.
37. Choose Connect as the Advisor name and change the Port number to 5061.
Click OK.
38. Right-click the Host entry and select Save Configuration File As. Accept the
default file name and click OK.
39. Test your configuration:
a. Click one of the advisors.
b. Click Refresh Statistics.
A ″-1″ entry under the ″load″ column suggests a connection cannot be
created on the specified port by the advisor. See the Load Balancer
Administration Guide, available from the Edge components Information
Center, at http://www306.ibm.com/software/webservers/appserv/ecinfocenter.html for
troubleshooting help.
40. Add the cluster name you entered to your network DNS tables to allow
clients to use the cluster name rather than an IP address when they access the
cluster directly.
Configuring with a command script
To use a script for configuring the Network Dispatcher, use the command:
1. Start the Network Dispatcher if it is not already running.
2. At a command prompt, run the following command:
dscontrol file newload myscript
where myscript represents the name of the script file.
Sample script
dscontrol set loglevel 1 dscontrol executor start
dscontrol cluster add 9.33.144.128 address 9.33.144.128 primaryhost 9.33.144.124
dscontrol cluster set 9.33.144.128 proportions 49 50 1 0
dscontrol executor configure 9.33.144.128 en0 255.255.254.0
dscontrol port add 9.33.144.128:5061 reset no
dscontrol port set 9.33.144.128:5061 stickytime 120
dscontrol server add 9.33.144.128:5061:wctnd006 address 9.33.144.126
dscontrol server set 9.33.144.128:5061:wctnd006 weight 15
dscontrol server add 9.33.144.128:5061:9.33.144.123 address 9.33.144.123
dscontrol server set 9.33.144.128:5061:9.33.144.123 weight 15
dscontrol port add 9.33.144.128:5060 reset no
dscontrol port set 9.33.144.128:5060 stickytime 120
dscontrol server add 9.33.144.128:5060:wctnd006 address 9.33.144.126
dscontrol server set 9.33.144.128:5060:wctnd006 weight 9
dscontrol server add 9.33.144.128:5060:9.33.144.123 address 9.33.144.123
dscontrol server set 9.33.144.128:5060:9.33.144.123 weight 9
dscontrol port add 9.33.144.128:80 reset no
dscontrol server add 9.33.144.128:80:wctnd007 address 9.33.144.127
dscontrol server set 9.33.144.128:80:wctnd007 weight 14
dscontrol server add 9.33.144.128:80:wctnd002 address 9.33.144.121
dscontrol server set 9.33.144.128:80:wctnd002 weight 14
dscontrol port add 9.33.144.128:443 reset no
Chapter 9 Completing the Network Deployment Setup
353
dscontrol server add 9.33.144.128:443:wctnd007 address 9.33.144.127
dscontrol server set 9.33.144.128:443:wctnd007 weight 14
dscontrol server add 9.33.144.128:443:wctnd002 address 9.33.144.121
dscontrol server set 9.33.144.128:443:wctnd002 weight 14
dscontrol manager start manager.log 10004
dscontrol advisor start Http 80 Http_80.log
dscontrol advisor connecttimeout Http 80 3dscontrol advisor timeout Http 80 3
dscontrol advisor start Https 443 Https_443.log
dscontrol advisor connecttimeout Https 443 3
dscontrol advisor timeout Http 443 3
dscontrol advisor start Connect 5061 Connect_5061.log
dscontrol advisor start Connect 5060 Connect_5060.log
Related tasks
“Network Deployment installation and configuration road map” on page 35
“Phase 9: Completing Network Deployment setup” on page 337
“Installing WebSphere Application Server Edge components” on page 53
“Updating rich client configuration files for Network Deployment”
Updating rich client configuration files for Network
Deployment
Three files are used to identify the endpoints for the different communication
protocols used by the rich client. These files are read by the download applet and
used to set the default server and port settings for the client. In a Network
Deployment environment these files should be deployed on the HTTP server(s)
and modified to identify the correct endpoints for the rich client to use.
These instructions assume that you have performed custom installations of the rich
client provisioning server on the HTTP server and on Node 1 as follows:
v On the HTTP server, you selected Update bundles and Installation files to be
installed on the HTTP server.
v On Node 1, you deselected Update bundles and Installation files.
Follow these steps to update the configuration files for a Network Deployment.
1. Create the <HTTPServerInstallDir>\htdocs\en_US\wctprops directory on the
HTTP server.
2. Copy the fileList.props, pluginvalues.props, and token-values.props from the
<install_root>\AppServer\installedApps\<Node 1
>yourNode\wctInstall.ear\wctinstall.war directory to the HTTP server’s or
servers’ <HTTPServerInstallDir>\htdocs\en_US\wctprops directory.
3. Modify the token-values.props file as below:
v Change the value of ″host=getParameter″ such that ″getParameter″=<the
fully qualified DNS address of the Network Dispatcher cluster>.
v Change the value of ″host-name=getParameter″ such that
″getParameter″=<the fully qualified DNS address of your Deployment Manager>.
Example syntax is shown below:
host=http://wctnd004.notesdev.ibm.com=<the Network Dispatcher cluster>
host-name=parachute.notesdev.ibm.com <the Deployment Manager>
4. Modify the pluginvalues.props file as below:
354
Installation and Upgrade Guide
v Replace the $host-name″ value in the
″plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=$h
string with <the fully qualified DNS address of the Deployment Manager>.
Example syntax is shown below:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.name=p
<the Deployment Manager>
v Add the following line:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.port=<The
bootstrap port of the Deployment Manager> (defaults to 9809)
Example syntax is shown below:
plugin_customization.com.ibm.workplace.security/com.ibm.wkplc.remote.server.port=9
<Default DM Bootstrap port>
v Add the following line:
plugin_customization.SIPSERVER=<the fully qualified DNS address of the
Network Dispatcher cluster>
Example syntax is shown below:
plugin_customization.SIPSERVER=dispatcher.notesdev.ibm.com <The
Network Dispatcher cluster>
5. Leave the fileList.props in its current state -- it does not need to be updated.
6.
7.
8.
9.
10.
11.
Open the WebSphere Administrative Console of the Deployment Manager.
Click Resources → URL Providers.
Set the scope to Cell.
Click Default URL Provider.
Click URLs.
Use the following information to specify the URL values.
Name
JNDI Name
Description
Specification
Workplace Client
Installer Download
Server
url/lwpprovisioningserver
Workplace Client
Installer Download
Server
http://<fully
qualified DNS
address of the
Network Dispatcher
cluster>
Workplace Client
Provisioning Server
url/wctprovisioningurlWorkplace Client
Provisioning Server
http://<fully
qualified DNS
address of the
Network Dispatcher
cluster>/lwpupdate/wct
Workplace Client
Plugin Values
url/wctpinstallpluginvalues
PluginValue
properties file
http://<fully
qualified DNS
address of the
Network Dispatcher
cluster>/wctprops/pluginvalues.pro
Workplace Client
Token Values
url/wctpinstalltokenValues
TokenValue
properties file
http://<fully
qualified DNS
address of the
Network Dispatcher
cluster>/wctprops/token-values.pro
Workplace Client
FilesList
url/wctpinstallfilesList
Install File List
http://<fully
qualified DNS
address of the
Network Dispatcher
cluster>/wctprops/filesList.props
Chapter 9 Completing the Network Deployment Setup
355
12. Modify the mime.types for the HTTP server(s) to handle *.props files using
the following sequence:
a. Open the <HTTPServer_Install_Dir>\conf\mime.types file.
b. Locate the following line in the file: text/plain asc txt
c. Change the line to read as shown below: text/plain asc txt props
d. Restart the HTTP server
Related tasks
“Phase 9: Completing Network Deployment setup” on page 337
“Installing and configuring the provisioning server” on page 298
Enabling dynamic caching
You must enable dynamic caching in your IBM Workplace Collaboration Services
cluster environment to synchronize the cached views and access rights for all
nodes. Otherwise, users might have different views or different access rights,
depending on which node handles the user’s request.
Enabling cache replication
1. Select Node 1 in the cluster and select Dynamic Cache Service from the
Additional Properties section (Servers → Application Servers →
WebSphere_Portal → Dynamic Cache Service)
2. Select Enable service at server startup and Enable cache replication.
3. Click the Enable cache replication link to go to the Internal Messaging view.
4. Select the Workplace Collaboration Services cluster as the domain for the
replicator and one of the server members as the replicator.
5.
6.
7.
8.
9.
Note: All cluster members must use these same replication settings:
v Select Runtime mode = Push only.
v Set the Push frequency to 1 second.
Apply the changes and click OK.
Repeat the above steps for all server members in the cluster.
Go to Environment → Internal Replication Domains → cluster_name.
Verify that DRS partition size and DRS pool size are set to 10.
Save the changes to the Deployment Manager’s master configuration by
clicking the Save link after the last modification.
Creating replicator entries for subsequent nodes
Perform these steps for Node 2 and every subsequent node you add to the cluster.
1. On the Deployment Manager, click Environment → Internal Replication
Domains.
2. Click PortalCluster.
3. Click Replicator Entries.
4. Click New.
5. Give this new replicator a name; for example, WorkplaceServer02.
6. Select the node you want to configure and enter the host name for this server.
You can only create one replicator on a server, so the list shows only those
servers that do not have a replicator.
356
Installation and Upgrade Guide
7. Select unique ports on this node for the replicator and client port such that
there are no port conflicts with other services on this node; for example, 7980
and 7981.
8. Click OK, then click OK again, and save your settings.
9. Click Servers → Application Servers → Name of Portal server node → Dynamic
Cache Service → Enable Cache Replication.
10. Keep the replication domain as PortalCluster and select the new replicator (for
example, WorkplaceServer02) from the list of replicators.
11. Click OK, then click OK again, and save your settings.
Related tasks
“Phase 9: Completing Network Deployment setup” on page 337
Enabling Search in the cluster
When using Portal Document Manager in a clustered environment, the search does
not work because the search index location is not available to all the machines in
the cluster. To enable Search for a clustered environment, edit the WCM.properties
file on each machine in the cluster to reference the shared WPCPIndex directory
that you created when you set up the Network Deployment environment.
Modify the WCM.properties file
Do this on every server in the cluster:
1. Navigate to the
<install_root>\AppServer\wpcp\config\WebSphere_Portal\author directory.
2. Open the WCM.properties file with a text editor.
3. Locate the following statement:
#wcm.indexedsearch.path=/
4. Remove the # comment marker:
wcm.indexedsearch.path=/
5. Add the path to the shared directory at the end of the statement; for example:
wcm.indexedsearch.path=Q:/WPCPIndex
Note: Always use a forward slash in this path, regardless of the operating
system.
6. Save your changes.
Update the search index
1. Navigate to the shared directory you specified in the wcm.indexedsearch.path
property, and if a search index file exists, delete it.
2. Update the search index.
You can either wait until the next scheduled update occurs, or you can change
the interval to the shortest possible time to force the update to occur sooner.
Refer to the ″Managing documents > Document Manager > Search″ topic in the
WebSphere Portal Information Center for details on setting the update interval.
3. Verify that the update process is complete by going to the directory where the
search index file is located and monitoring the disk space used by the file.
When the size of the file stabilizes, the update is complete.
Related tasks
“Phase 9: Completing Network Deployment setup” on page 337
Creating shared directories for a Network Deployment
Chapter 9 Completing the Network Deployment Setup
357
Enabling Messaging in the cluster
Follow these procedures to enable messaging and notifications in a Network
Deployment environment.
Enabling notifications
Follow these steps on Node 1 and all subsequent node servers to enable
notifications for Workplace Collaboration Services.
1. From the WebSphere Administrative Console, click Resources →
Mail_providers.
2. Clear the Node field content, then click Apply.
3. Click Built_in mail provider → Mail session.
4. Click New.
5. Provide values for the Mail session.
Field
Value
Name
Workplace Notifications
JNDI Name
mail/lwpadmin
Note: You must use the JNDI name shown above for notifications
to work.
Description
Workplace e-mail settings used for server notifications
Mail Transport Host
Specify the host name of the SMTP server on this node.
Typically, this is Mail_Server_1 (for example:
mailserver1.acme.com) or some other mail server
(mymailserver.acme.com).
Mail From
The administrator’s e-mail address (for example,
[email protected])
6. Click Save.
7. Restart the Workplace servers.
Mapping the Mail module to Mail servers
This step is done automatically when you add Node 1 to a cluster. Follow these
steps on Node 2 and all subsequent nodes to map the Mail module to the Mail
servers.
1. From the WebSphere Administrative Console, click Applications → Enterprise
Applications.
2. Page through the applications until you find Mail_wmmApp, then select it.
3. Under Additional Properties, select Map Modules to Application Servers.
4. Select the check boxes for all modules.
5. Select all Mail server servers.
6. Click Apply and then click OK.
7. Click Save.
8. Select Synchronize across nodes. Then click Save.
9. Restart the Workplace servers.
358
Installation and Upgrade Guide
Relocating wps.ear file to enable instant messaging failover
Follow these steps on Node 2 and all subsequent nodes to enable instant
messaging failover. This procedure is not needed for Node 1.
1. To finish configuring the node for instant messaging, copy the wps.ear
directory and subdirectories from this location on Node 2:
<was_root>/installedApps/<node1_name>/wps.ear
2. Place the wps.ear directory and its subdirectories in this location:
<was_root>/installedApps/<node2_name>
The final directory structure will look like this:
<was_root>/installedApps/<node2_name>/wps.ear/wps.war/themes/html/extension
Distributing embedded messaging files
Files related to the Embedded Messaging feature might exist on the Deployment
Manager server even though you did not select this feature when you installed the
Deployment Manager. For example, these files might have been installed when you
installed WebSphere Application Server Enterprise or fix packs.
If the files exist on the Deployment Manager, you must also copy them to each
node in the environment:
1. Search for the cm.jar and cmlmpl.jar files. By default, these files appear in the
<was_root>\lib directory.
2. If the files are not present on the Deployment Manager machine, no further
action is needed.
If the files are present, copy them to the <was_root>\lib directory on each node.
Related tasks
Opening the WebSphere Administrative Console
“Phase 9: Completing Network Deployment setup” on page 337
Editing WebSphere settings for a Network Deployment
Use the WebSphere Administrative Console to update settings on nodes in a
Network Deployment. Open the WebSphere Application Server administrative
console by typing the following URL from a browser window:
http://yourWASServer:9090/admin
where yourWASServer is the fully qualified DNS name of the WebSphere
Application Server.
Editing SIP cell-wide settings on all nodes
Make these changes on Node 1 and all subsequent nodes.
1. From the WebSphere Administrative Console, navigate to Lotus Workplace →
SIP cell-wide settings.
2. Enter your domain in the ″internal domains″ input box; for example:
acme.com
3. Save your changes.
Editing mail cell-wide settings on all nodes
Make these changes on Node 1 and all subsequent nodes.
1. From the WebSphere Administrative Console, navigate to Lotus Workplace →
Mail cell-wide settings.
Chapter 9 Completing the Network Deployment Setup
359
2. Enter values for the following:
v Domains that are considered local
v Default domain name
v Postmaster mail address
3. Scroll down to ″General Mail services.″
4. Enter DNS servers and the local path for the shared messaging directory,
qfilestore.
5. Save your changes.
Removing the wmm50jdbc provider for Node 2
Make these changes on Node 2 and any subsequent nodes.
1. From the WebSphere Administrative Console, click Resources → JDBC
Providers .
2. Click Browse and select Node 2.
3. Click Apply.
4. Select wmm50jdbc, then click Delete.
5. Save your changes.
Related tasks
Opening the WebSphere Administrative Console
Creating shared directories for a Network Deployment
“Phase 9: Completing Network Deployment setup” on page 337
Applying fix packs to the Network Deployment servers
Apply the following WebSphere Application Server fix packs to the Deployment
Manager and all nodes to ensure that Workplace and provisioning servers work
properly. Download the fix packs and install them in the order shown below.
1. PK00049
Download and install this fix pack first. This is a special version of PK00049 to
be used with IBM Workplace Collaboration Services. The fix pack can be
downloaded from http://www1.ibm.com/support/docview.wss?uid=swg24009362.
2. Download these fix packs from http://www.ibm.com/support/us/ and install
them in the order shown:
a. PQ88539
b. PQ90368
c. PQ87768
3. Download and install the additional iFix PK04318 from the same site. It should
be applied last.
Note: The PK04318 iFix must be installed after the administrator has installed the
provisioning server but before users download and install the rich client.
Related tasks
“Phase 9: Completing Network Deployment setup” on page 337
360
Installation and Upgrade Guide
Appendix A Upgrading from Lotus Workplace 2.01
This appendix contains information about upgrading to IBM Workplace
Collaboration Services from Lotus Workplace 2.01.
Lotus Workplace 2.0.1 upgrade
The installation program for IBM Workplace Collaboration Services 2.5 lets you
automatically upgrade from Lotus Workplace 2.0.1.
When the Workplace Collaboration Services installation program detects an
instance of Lotus Workplace 2.0.1 on the system, the user is prompted to choose
between installing a new instance of Workplace Collaboration Services or
upgrading the existing instance of Lotus Workplace 2.0.1. This prompt is not
displayed if you have an earlier version (or no version) of Lotus Workplace
installed. Furthermore, because the installation procedure uses information stored
in local properties files, you cannot upgrade if Lotus Workplace 2.0.1 is installed on
a different CPU from the one on which you are running the installation program.
When you choose to upgrade, the installation procedure preserves the existing
Lotus Workplace 2.0.1 binaries and prompts you to specify a directory in which to
install Workplace Collaboration Services. The Workplace Collaboration Services
images are then copied to that directory.
The upgrade procedure modifies the schemas of existing Lotus Workplace 2.0.1
databases and then transfers their contents to a single Workplace Collaboration
Services database. If you are upgrading from an Oracle deployment, the new
database retains its LotusWorkplace 2.0.1 name and is partitioned into five schemas
(LWPMSG25, LWPARC25, LWPLDS25, LWPLMS25, and LWPCOMM25). If you are
upgrading from an IBM DB2 deployment, the new database is named WRKPLC by
default.
The same HTTP and LDAP servers, application server topology, and database type
are used in upgrading from Lotus Workplace 2.0.1 to Workplace Collaboration
Services. The upgrade process updates the existing IBM WebSphere Application
Server and IBM WebSphere Portal Server instances.
The upgrade process migrates most Lotus Workplace 2.0.1 data to Workplace
Collaboration Services intact. “Lotus Workplace 2.0.1 data migration” on page 362
lists the kinds of data that are not automatically migrated and describes what you
need to do to preserve and restore that data.
Both single server to single server and network to network deployments are
supported.
“Upgrading to IBM Workplace Collaboration Services (single server)” on page 365
provides a basic road map of what you need to do before and after running the
installation program to complete the upgrade successfully for a single-server
deployment. Upgrading a Network Deployment describes the steps to upgrade a
Network Deployment.
Note: The upgrade procedure takes a rather long time to complete: plan on at least
three hours from start to finish, and more time if you have significant
© Copyright IBM Corp. 2002, 2005
361
amounts of data to migrate. A progress bar indicates the amount of time to
complete the first phase of the upgrade operation. After that, the installation
may take an additional two or more hours. To confirm that the installation
program is still running, look at the file
<temp_directory>/lwai/lwpinstalllog.txt.
Lotus Workplace 2.0.1 data migration
When you upgrade to IBM Workplace Collaboration Services 2.5, most Lotus
Workplace 2.0.1 data is migrated intact.
The following table lists the types of data that are not migrated intact and provides
recommendations for preserving that data.
Table 1. Data not migrated by the installation program
362
Type of data
Upgrade installer action
Recommendation
Custom skins
Skin files are not migrated,
but skin configuration is
preserved.
Before upgrading, export the
skin configuration. After
upgrading, copy the skin
files to the corresponding
location on the upgraded
server. Then in Microsoft
Windows use xmlaccess.bat
or in IBM AIX or Linux use
xmlaccess.sh to import the
exported skins. See the IBM
WebSphere Portal
information center at http://
publib.boulder.ibm.com
/pvc
/wp/502/ent/en/InfoCenter
/index.html for a description
of xmlaccess and sample
scripts.
Custom themes
Theme files are not migrated, Before upgrading, export the
but theme configuration is
theme configuration. After
preserved.
upgrading, copy the theme
files to the corresponding
location on the upgraded
server. Then in Windows
use xmlaccess.bat or in AIX
or Linux use xmlaccess.sh to
import the exported themes.
Custom portlets
Portlets other than those that
ship with Workplace
Collaboration Services are
not migrated.
Installation and Upgrade Guide
After upgrading, copy the
portlet module to
<wp_root>/InstallableApps.
Then log on to the upgraded
Workplace Collaboration
Services server and use IBM
WebSphere Portal
Administration to deploy the
portlets.
Note: You may need to
reconfigure portlet
permissions.
Table 1. Data not migrated by the installation program (continued)
Type of data
Upgrade installer action
Recommendation
Custom pages
Pages containing custom
portlets lose their portlet
references during migration
(because those portlets are
not deployed on the
upgraded Workplace
Collaboration Services
server).
Before upgrading, export the
custom pages to Workplace
Collaboration Services. After
upgrading, deploy the
custom portlets as described
above. Then use
xmlaccess.bat (Windows) or
xmlaccess.sh (AIX and
Linux) to import the
exported pages.
Note: Custom pages created
under
wps.My_Portal.My_Workplace
will be removed.
Customized Lotus Workplace All pages that shipped with
2.0.1 pages
Lotus Workplace 2.0.1 are
migrated in their original
form. Any customizations
that you have made to those
pages are not preserved.
Pages containing customized
Messaging or Calendar
portlets lose some of the
portlet settings during
migration (for example, the
number of lines per page in
the Messaging portlet’s Inbox
view or the default event
type in the Calendar
portlet)..
After upgrading, recreate the
customizations and manually
restore your page
permissions.
Customized permissions for
Lotus Workplace 2.0.1
portlets
Not all permission
configuration data for Web
modules and portlets are
preserved during migration
After upgrading, review
your configurations and
reconfigure permissions, as
needed.
Export schedule to use user
policy setting
The value of this field is not
migrated.
Before upgrading, make a
note of the value of this field
in each user policy that you
defined. After upgrading, use
the IBM WebSphere
Administrative Console to
manually reset this field.
Configuration settings for
additional servers
Configuration settings for
additional (non-default)
Lotus Workplace 2.0.1
servers are not migrated.
Before upgrading, make a
note of the properties and
task settings of the additional
servers. After upgrading,
reconfigure these servers.
Rich client configuration
Rich client configuration
settings and provisioning
files are not migrated.
Before upgrading, uninstall
the rich client installer. After
upgrading, install the rich
client 2.5 installer. Client-side
users will be automatically
upgraded when they connect
to the Workplace
Collaboration Services server.
Appendix A Upgrading from Lotus Workplace 2.01
363
Table 1. Data not migrated by the installation program (continued)
364
Type of data
Upgrade installer action
Recommendation
Activity Explorer
The Activity Explorer, which
was a technical preview
feature in is not supported in
Lotus Workplace 2.0.1, is not
migrated.
The Activity Explorer is
supported for use in
Workplace Collaboration
Services if you have
upgraded from a Lotus
Workplace 2.0.1 server that
never had the Activity
Explorer installed, or if you
have installed a new
Workplace Collaboration
Services rather than
upgrading.
Custom forms
Custom forms that you
created by using the forms
technical preview feature are
not migrated.
After upgrading, recreate the
forms.
Note: You should delete
pages containing forms
created under Lotus
Workplace 2.0.1.
Custom IBM WebSphere
Portal Server shared
resources
The installation program
After upgrading, copy
installs a clean version of the custom shared resources
WebSphere Portal Server
from their old location to the
image. Therefore, custom
Workplace Collaboration
shared resources are not
Services server.
migrated.
Customized property files for Property files that you
portlet services
modified in
<wp_root>/shared/app
/config on the Lotus
Workplace 2.0.1 server are
not migrated.
After upgrading, manually
recreate the customizations
on the Workplace
Collaboration Services server.
IBM Workplace Web Content Lotus Workplace 2.0.1
Management data
supports both Workplace
Web Content Management
2.0.1 and Web Content
Management 2.5. Repository
data is not migrated if you
install Web Content
Management locally under
Workplace Collaboration
Services system.
For information on
upgrading from Workplace
Web Content Management
2.5, see the Workplace Web
Content Management 2.5
information center. If you are
upgrading from Web Content
Management 2.0.1, you need
to install Web Content
Management 2.5 and copy
the data repository by
backing up and then
restoring the database or by
setting up a syndication
between the 2.0.1 and 2.5
systems.
Installation and Upgrade Guide
Table 1. Data not migrated by the installation program (continued)
Type of data
Upgrade installer action
Recommendation
templates
The installation program
migrates templates from
Lotus Workplace 2.0.1
adding the prefix migrated.
This renaming breaks their
connection to the Workplace
Collaboration Services
localization code.
After upgrading, move
customizations you made to
Lotus Workplace 2.0.1
templates to the
corresponding Workplace
Collaboration Services
templates. You can
recategorize the applications
created from Lotus
Workplace 2.0.1 templates by
using the template editor,
which is described in the
Workplace Collaboration
Services information center.
Note: When you upgrade an
Oracle deployment, instances
of templates that were
created on the Lotus
Workplace 2.0.1 server will
not be editable on the
upgraded Workplace
Collaboration Services server.
Instances of Lotus Workplace
2.0.1 templates that you
create after upgrading to
Workplace Collaboration
Services 2.5 should function
properly.
Upgrading to IBM Workplace Collaboration Services (single server)
Upgrading a single-server deployment from Lotus Workplace 2.0.1 to IBM
Workplace Collaboration Services 2.5 involves three steps:
1. Prepare to upgrade.
2. Run the installation program.
3. Perform post-installation tasks.
Preparing to upgrade
There are a few tasks you need to perform before running the installation program
to upgrade to IBM Workplace Collaboration Services 2.5 from Lotus Workplace
2.0.1. Some of these involve backing up Lotus Workplace 2.0.1 files in case you
encounter problems in the upgrade process and need to revert to Lotus Workplace
2.0.1 or in case you have customized the product and want to migrate your
customizations. There are some additional preparatory steps if you are upgrading a
Network Deployment.
All of these steps are applicable prior to upgrading a single-server deployment and
to an upgrade of the first node in a Network Deployment. Because subsequent
nodes in a cluster require a fresh installation of Workplace Collaboration Services,
the steps to create and configure an IBM DB2 database do not apply to the
installation of Workplace Collaboration Services on those nodes.
Appendix A Upgrading from Lotus Workplace 2.01
365
1. Make sure that you have sufficient disk space to perform the upgrade.
Because the Workplace Collaboration Services version and LotusWorkplace
2.0.1 images are installed on the same machine, you need at least 7.5 GB of
free disk space to perform the upgrade.
2. Make sure that the Lotus Workplace 2.0.1 server is running and that all
network connections are functioning.
3. If you are deploying IBM DB2, create a new Workplace Collaboration Services
database. (If you are upgrading a Network Deployment, you will already have
done this.)
4. If you are deploying either Oracle or IBM AIX (or both), download and apply
the patch in LO08102.zip, which is available at
ftp://ftp.software.ibm.com/software/lotus/fixes/workplace.
5. Export custom skins, themes, pages, and portlet applications. Use
xmlaccess.bat (Microsoft Windows) or xmlaccess.sh (IBM AIX or Linux) to
perform the export. See the IBM WebSphere Portal information center at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html
for a description of xmlaccess and sample scripts.
6. Back up Lotus Workplace 2.0.1 skin or theme files that you have customized.
7. If you used Lotus Workplace Messaging in Lotus Workplace 2.0.1, disable
Lotus Workplace Messaging.
8. Uninstall the IBM Workplace rich client installer. See the Workplace
Collaboration Services information center for instructions on uninstalling and
installing the rich client installer. You can install the rich client installer
upgrade after the Workplace Collaboration Services installation program has
completed. The transition for client-side users will be transparent when they
run Workplace Collaboration Services.
9. In the system directory, check that the properties settings in vpd.properties
match the actual Lotus Workplace 2.0.1 configuration. Then back up
vpd.properties.
10. The upgrade script looks in the Lotus Workplace 2.0.1
<wp_root>/config/wpconfig.properties and
<WebSphere_DeployMgr_root>/config/lwpprops.properties files to retrieve this
configuration and database information:
v host name, cell name, node name, SSO domain
v administrator user name and password
v database type, driver location, administrator user name and password
Note: For an Oracle deployment, make sure that the value of the DbDriverDs
property in wpconfig.properties is
oracle.jdbc.xa.client.OracleXADataSource. For a DB2 deployment, the
value of this property should be COM.ibm.db2.jdbc.DB2XADataSource.
Make sure that the IBM WebSphere Portal Implementation Classname
setting for wpcp50JDBC and wps50JDBC is the same as this
DbDriverDs setting.
Confirm that the values for these properties are up to date and that there are
no missing values. For example, if you removed password information from
these files, you need to restore that information. Similarly, if the information
used for creating databases is out of date, you need to bring it up to date.
Note: You can override these and other properties values by creating a
custom properties file that you reference in the command line when
you run the installation program. If you are deploying Oracle, you
366
Installation and Upgrade Guide
must use this file to specify the JDBC driver used to access the
Workplace Collaboration Services application database.
11. If you are upgrading a Network Deployment, you need to create a custom
properties file that specifies a value for the NDCellName system variable. You
reference this file in the command line when you run the installation program.
12. For an Oracle deployment, make sure that the environment for executing
database tasks has been set up correctly.
v IBM AIX, Linux
The following environment variables need to be set in the .profile (or
.bash_profile) for both the root and Oracle user accounts:
ORACLE_BASE=/opt/oracle
(or the equivalent for your UNIX environment).
ORACLE_HOME=$ORACLE_BASE/product/9ir2
(or the equivalent for your UNIX environment).
TNS_ADMIN=$ORACLE_HOME/network/admin
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
NLS_LANG <codepage>
where <codepage> is the string that specifies the language, territory, and
character set to be used for display on the client (for example,
American_America.UTF-8).
PATH=$PATH:$ORACLE_HOME/bin
v Linux
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/
lib:$ORACLE_HOME/ctx/lib:$ORACLE_HOME/jdbc/lib
v AIX
LIBPATH=[ORACLE_HOME]/lib32:[ORACLE_HOME]/jdbc/ lib
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/
jlib:$ORACLE_HOME/rdbms/jlib:$ORACLE_HOME/network/jlib export
ORACLE_BASE ORACLE_HOME ORA_NLS33 NLS_LANG PATH LD_LIBRARY_PATH
CLASSPATH TNS_ADMIN
v AIX, Linux
Check to see that the $NLS_LANG environment variable contains the
specification UTF-8 as the character set designation by issuing this command:
echo $NLS_LANG. If the response does not end in UTF-8, you need to reset the
property value to one that does.
v Windows
Check to see that the NLS_LANG environment variable contains the specification
UTF-8 as the character set designation. Do this by opening the registry,
looking under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME<ID>\ NLS_LANG
where <ID> is the unique number that identifies Oracle Home (for ecample,
Home0). If the key value does not end in UTF-8, you need to reset it to one
that does.
13. For an Oracle deployment, you need to enter the following SQL commands in
the command line
ALTER TABLE LWPCOMM.CDO_CDO ADD TEMPLATEDATA2 CLOB;
UPDATE LWPCOMM.CDO_CDO SET TEMPLATEDATA2=TO_CLOB(TEMPLATEDATA) WHERE TEMPLATEDATA IS NOT NULL
ALTER TABLE LWPCOMM.CDO_CDO DROP COLUMN TEMPLATEDATA;
ALTER TABLE LWPCOMM.CDO_CDO RENAME COLUMN TEMPLATEDATA2 TO TEMPLATEDATA;
Appendix A Upgrading from Lotus Workplace 2.01
367
14.
15.
16.
17.
18.
Note: LWPCOMM is the default schema name. If you have renamed this
schema, change the preceding code accordingly.
Make a note of the Export schedule to use field in your user policies, as this
property is not migrated automatically. You will have to reset this value
manually after the upgrade is complete.
If you have defined additional Lotus Workplace 2.0.1 servers, follow these
steps:
a. Start the IBM WebSphere Administrative Console.
b. Select Servers - Lotus Workplace Servers.
c. Select the server link for an additional server.
d. Select the Status tab and make a note of the services listed for the server.
This will allow you to create the same type of server (using the same
template) after the upgrade is complete.
e. Select the service configuration pages for the server and make a note of
their properties.
f. If you created any new export tasks for the server, select Task Scheduler
Service and make a note of the task names and current schedules.
g. Repeat steps c. through f. for each additional server.
Make sure that you have the appropriate versions of required software as
described in the IBM Workplace Collaboration Services information center.
Shut down all instances of the Lotus Workplace 2.0.1 IBM WebSphere
Application Server (server1, WebSphere_Portal, and LotusWorkplace_Server).
Do not shut down the database server or the LDAP server, as these must be
running throughout the installation process.
Back up the Lotus Workplace 2.0.1 databases. This is an especially important
step. The upgrade process alters Lotus Workplace 2.0.1 databases before
combining them into a single Workplace Collaboration Services 2.5 database.
The altered databases will no longer function properly if for some reason you
need to revert to Lotus Workplace 2.0.1, which you can do by simply restoring
your original, backed-up 2.0.1 databases.
Lotus Workplace 2.0.1 databases
Lotus Workplace 2.0.1 uses one or more of the databases listed in this table.
Depending on the type of deployment that you selected and the components that
you installed. Back up the databases that you have installed before migrating to
IBM Workplace Collaboration Services 2.5.
Database name
Description
Com
Common database
This database contains data used for
maintaining the infrastructure of IBM
Workplace Collaboration Services.
Delivery
Learning Delivery Server database
This database temporarily stores data about
students and specific course activities until
the system relays that data to the Learning
Server database for permanent storage.
368
Installation and Upgrade Guide
Database name
Description
LMS
Learning Server database
This database permanently stores data about
courses, students, and competencies for the
Learning portal.
Nagano
Messaging database
This database stores data about user
messaging accounts and stores as the mail
that users receive.
Arc
Messaging Archive database
The Archive feature uses this database to
track archived mail messages. This database
contains links to the archived content, which
is stored as ZIP files on the file system.
Note: An IBM Cloudscape database (SQL) is created automatically during
installation. It contains schemas for all components and is typically used in a
single-server configuration for demonstrations only. Because it is designed
for use only in demonstration installations, this database should not be used
for production data. The upgrade process copies an existing Lotus
Workspace 2.0.1 database to the Workspace Collaboration Services server.
There are up to four IBM WebSphere Portal Server databases you should also back
up:
Database name
Description
WPS50
IBM WebSphere Portal Server database
WPCP50
IBM WebSphere Portal Content Publishing
database
feedback
Feedback database
This database stores information that Portal
Server uses in generating site activity
analysis reports.
Likeminds
LikeMinds Personalization database
This database stores and analyzes user
transactions on a Web site and makes
recommendations to users based on that
analysis.
Upgrading an IBM DB2 deployment
Follow these steps to upgrade an IBM DB2 deployment:
1. Make sure that you have installed fixpack7a on both the DB2 server and client.
2. Create and configure an empty WRKPLC DB2 database to which your Lotus
Workplace 2.0.1 data will be transferred.
To create the database on the DB2 system, execute the following command
from the DB2 command line processor:
db2 => CREATE DATABASE WRKPLC USING CODESET UTF-8 TERRITORY US COLLATE
USING SYSTEM WITH "Lotus Workplace"
Appendix A Upgrading from Lotus Workplace 2.01
369
Configure the database by executing the following script, which you need to
run as DBA from the DB2 database server command line:
disconnect all;
connect to WRKPLC user <db2admin_name> using <db2admin_password>;
update database manager configuration using intra_parallel no;
!db2set db2_rr_to_rs=yes;!db2set db2_inlist_to_nljn=yes;
!db2set db2_evaluncommitted=yes;
alter bufferpool ibmdefaultbp size 16384;
update dbm config using mon_heap_sz 1024;
update db cfg for WRKPLC using maxappls 100;
update db cfg for WRKPLC using maxfilop 96;
update db cfg for WRKPLC using mincommit 3;
update db cfg for WRKPLC using applheapsz 4096;
update db cfg for WRKPLC using locklist 1024;
update db cfg for WRKPLC using locktimeout 10;
update db cfg for WRKPLC using maxlocks 70;
update db cfg for WRKPLC using dbheap 4096;
update db cfg for WRKPLC using stmtheap 8192;
update db cfg for WRKPLC using num_iocleaners 10;
update db cfg for WRKPLC using num_ioservers 8;
update db cfg for WRKPLC using logbufsz 32;
update db cfg for WRKPLC using sortheap 4096;
update db cfg for WRKPLC using app_ctl_heap_sz 1024;
update db cfg for WRKPLC using logfilsiz 10000;
update db cfg for WRKPLC using logprimary 25;
update db cfg for WRKPLC using logsecond 64;
commit;
disconnect all;
Specifying properties values
If you are upgrading a Network Deployment, you need to supply a value for
NDCellName. You do this by creating a properties file that you reference when
you run the installation program.
If you are deploying Oracle, you need to set the database property that specifies
the JDBC driver used to access the Workplace Collaboration Services application
database. You can optionally change the default schema names that are assigned to
an Oracle database to avoid schema name collisions during upgrade. You do this
by creating a separate properties file that you reference when you run the
installation program.
You can change default database properties values, such as the IBM Workplace
Collaboration Services single-source database name (WRKPLC), or override custom
properties values that you have set in Lotus Workplace 2.0.1, such as the database
administrator name or password by creating a properties file (or using the one
required for an Oracle deployment) that you reference when you run the
installation program.
Note: Changes that you make to default property values may not be preserved in
subsequent database upgrades.
When upgrading a Network Deployment, follow these steps:
1. Create a properties file (for example, wpprops.properties).
2. Include this statement: NDCellName=<Lotus_Workplace 2.0.1 ND cell_name>
3. Save the file. For example, in Microsoft Windows, save the file to the C drive as
c:\wpprops.properties. For example, in Microsoft Windows, save the file to the
C drive as c:\wpprops.properties.
370
Installation and Upgrade Guide
4. To change default database properties, create a separate properties file (for
example, dbprops.properties).
5. To specify a value for a property, type <property>=<value>. For example, you
can change the following Workplace Collaboration Services IBM DB2 database
properties by changing the value:
v LWP25.DbName=MYDATABASE (the name of the Workplace Collaboration Services
database: the default is WRKPLC.)
v LWP25.DbUser=xxx (the Workplace Collaboration Services database’s admin
user name: the default is the Lotus Workplace 2.0.1 COM database’s admin
user name.)
v LWP25.DbPassword=xxx (the Workplace Collaboration Services database’s
admin password: the default is the Lotus Workplace 2.0.1 COM database’s
admin password.)
v LWP25.DbAppUser=xxx (the Workplace Collaboration Services database’s
application user name: the default is the Lotus Workplace 2.0.1 COM
database’s application user name.)
v LWP25.DbAppPassword=xxx (the Workplace Collaboration Services database’s
application user name: the default is the Lotus Workplace 2.0.1 COM
database’s application user password.)
For an Oracle deployment, include this entry:
LWP25.DbURL=jdbc:oracle:[email protected]<tns entry alias> where <tns entry alias> is the
database alias used for the existing Lotus Workplace 2.0.1 application schema.
To change these default Oracle schema names, change the value:
v LWP25.DbArcSchema=LWPARC25 (the new ARC schema name.)
v LWP25.DbArcSchemaPW=LWPARC25 (the new ARC schema password.)
v LWP25.DbComSchema=LWPARC25 (the new COM schema name.)
v LWP25.DbComSchemaPW=LWPARC25 (the new COM schema password.)
v LWP25.DbLDSSchema=LWPARC25 (the new LDS schema name.)
v LWP25.DbLDSSchemaPW=LWPARC25 (the new LDS schema password.)
v LWP25.DbLMSSchema=LWPARC25 (the new LMS schema name.)
v LWP25.DbLMSSchemaPW=LWPARC25 (the new LMS schema password.)
v LWP25.DbMsgSchema=LWPARC25 (the new MSG schema name.)
v LWP25.DbMsgSchemaPW=LWPARC25 (the new MSG schema password.)
6. Save the file. For example, in Microsoft Windows, save the file to the C drive as
c:\wpprops.properties. For example, in Microsoft Windows, save the file to the
C drive as c:\dbprops.properties.
7. When you start the installation program, if you have created properties files for
both Network Deployment and database properties specifications, type the
following instruction (Windows): install.bat -W
fixupArchiveProps.upgradeWpconfigOverride=c:\wpprops.properties -W
fixupArchiveProps.upgradeDbprops=c:\dbprops.properties.
Otherwise, just specify the -W switch appropriate to your deployment.
Disabling Lotus Workplace Messaging
If Lotus Workplace Messaging is enabled in Lotus Workplace 2.0.1, you need to
disable inbound mail and ensure the message queue is empty before you begin the
upgrade process.
1. Disable inbound mail.
2. Check the status of the message queue.
Appendix A Upgrading from Lotus Workplace 2.01
371
3. Expedite pending messages.
4. Remove dead messages.
5. Delete orphaned messaging accounts.
Disabling inbound mail:
Before you upgrade, disable inbound mail and ensure the message queue is empty.
Disable inbound mail, report the status of the queue, and then take any manual
steps necessary to process pending messages. The message queue normally
empties without intervention.
Messages that are in the queue and have Unprocessed, Delivered, Undeliverable,
or Completed as the delivery state are automatically removed from the queue.
Messages that have Ready as the delivery state are also automatically removed
from the queue. Messages that have Retry as the delivery state require manual
intervention. (Retry messages usually indicate server unavailability.) If the LDAP
directory server that is configured for IBM Workplace Collaboration Services is
unavailable, inbound mail is marked with the delivery state Handler Retry and the
message state is Unprocessed.
Messages in the DeadEnd delivery state are processed and automatically removed
if a valid Internet address has been configured on the messaging server to receive
the dead messages. Otherwise, you must manually remove dead messages.
To disable inbound mail, complete these steps:
1. Type the following Web address in a browser to start the IBM WebSphere
Administrative Console: http://<servername>.<domain>.com:9091/admin
2. Complete these steps to disable inbound mail from Workplace Collaboration
Services 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. To disable inbound mail from servers and from Internet mail clients:
a. click Servers → Application Servers → Mail_Server_1.
b. Under Additional properties, click Workplace Mail Services.
c. On the Configuration tab, click SMPT Inbound Service, and then in select
Stopped in the Initial State field.
4. Stop and restart the IBM WebSphere Portal server and the Mail server server so
the user policy changes take effect.
5. Follow these steps to verify the configuration changes:
372
Installation and Upgrade Guide
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. Check the message queue.
Checking the message queue:
After you disable inbound mail, perform these steps to report the status of any
messages in the message queue. You can report the status to the server console or
to a file. If there are many messages in the queue, report the status to a file. 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 IBM WebSphere Application Server, the IBM WebSphere Portal Server,
and IBM Workplace Collaboration Services.
2. From the <was_root>\bin directory, type one of these commands to start the
Lmadmin tool:
v In Microsoft Windows, lmadmin -user <username> -password <password>
-port 8882
v In IBM AIX or Linux, ./lmAdmin.sh -user <username> -password <password>
-port 8882
3. Confirm that you see a message indicating that the SOAP process is connected
to the Workplace Collaboration Services server. If the SOAP process is not
connected, see the Workplace Collaboration Services information center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp? for information
about starting the Lmadmin command service.
4. Perform one of these tasks:
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. Expedite pending messages.
Expediting pending messages:
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 these steps to identify pending messages, to
resolve the server problem, and to resend the pending messages.
1. In the queue, look for messages that have the delivery state Ready and the
message state Retry.
2. Look at the recipient lists to determine the domain and the server, 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 that have the delivery state Handler Retry and the
message state Unprocessed. These messages indicate that the LDAP directory
server 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 these
steps to force a retry of each pending message:
a. Type this Lmadmin command to list the IDs of the pending messages: lm
mail getPendingMessages
Appendix A Upgrading from Lotus Workplace 2.01
373
b. Copy the ID of a pending message to the clipboard.
c. Type this 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 b and c for each pending message.
5. Remove dead messages.
Removing dead messages:
In the message queue, dead messages have the message state Dead and the
delivery state DeadEnd.
1. Type this command to delete any dead messages:lm mail /reapDeadMessages
-300
2. Delete orphaned message accounts.
Deleting orphaned messaging accounts:
Follow these steps to delete orphaned messaging 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.1 databases. If you have
difficulty deleting an orphaned account, you can leave it in the messaging
database.
1. Type this Lmadmin command to list orphaned accounts and their associated
external IDs: lm listaccounts /orphan
2. For each orphaned account, perform these steps:
a. Copy the external ID from the list to the clipboard.
b. Type this command to delete the account: lm deleteaccounts -externalid
<id>where <id> is the external ID pasted from the clipboard. For example:
lm deleteaccounts -externalid 08213593F24F53BBCDE0D1CE323ALF000026
Running the installation program for a single-server
deployment
After you have performed the necessary tasks to prepare for upgrading, you need
to run the Workplace Collaboration Services installation program.
Run the Workplace Collaboration Services installation program and follow these
steps:
1. Choose the upgrade option at the prompt.
2. At the prompt, select the products you have licensed.
3. Sign the license agreement.
4. Specify the installation location, making sure that it is not the location in which
2.0.1 is installed.
5. Select single deployment as the type of deployment that you want to upgrade.
After the installation program finishes, perform post-installation tasks to complete
the upgrade.
374
Installation and Upgrade Guide
Completing an upgrade
Depending on the details of your deployment, you may have to perform some
additional tasks after the installation program finishes to complete the migration of
your data from Lotus Workplace 2.0.1 to IBM Workplace Collaboration Services.
The following list is applicable to the single server in a single-server upgrade and
to the individual nodes in a Network Deployment.
1. Start the Workplace Collaboration Services server and verify that the
Workplace Collaboration Services components are working properly and that
your Lotus Workplace 2.0.1 data has been migrated and is functioning as
expected.
2. If you are running IBM DB2, you can issue the following commands on the
DB2 server to optimize the database:
db2
connect to WRKPLC user db2admin using <your_db2admin_password>
reorgchk update statistics on table all
terminate
db2rbind <database_name> -1 db2rbind.out -u <db2_admin> -p <password>
3. If you modified any property files in <wp_root>/shared/app/config on the
Lotus Workplace 2.0.1 server, enter those changes in the corresponding
property files on the Workplace Collaboration Services server.
4. If you customized any portal shared resources in Lotus Workplace 2.0.1, copy
these from their old location to the Workplace Collaboration Services server.
5. Restart the Workplace Collaboration Services server.
6. Import custom skins, themes, and pages (in that order) to the appropriate
location on the Workplace Collaboration Services server. Use xmlaccess.bat
(with Microsoft Windows) or xmlaccess.sh (with IBM AIX or Linux) to import
the custom skins, themes, and pages that you exported prior to running the
installation program. See the IBM WebSphere Portal information center at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html
for a description of xmlaccess and sample scripts.
7. Restore and reconfigure custom portlets, reconfiguring portlet permissions as
needed. Copy the portlet module to <wp_root>/InstallableApps, and then log
in to the Workplace Collaboration Services server and use Portal
Administration to install the portlets.
8. After an upgrade, the Bookmarks portlet does not appear when you log in to
Workplace Collaboration Services as a non-administrator. Follow these steps to
make the Bookmarks appear:
a. Log in to IBM WebSphere Portal Server using a Portal administrator’s
account (for example, wpsadmin).
b. Select Administration.
c. Select the Access tab.
d. Select Resource Permissions.
e.
f.
g.
h.
Select Portlets.
Locate the Bookmarks portlet (by using the Title contains search field).
Open Assign Access (key icon).
Open Edit Role for User (pencil icon).
i. Click Add.
j. Select All authenticated portal users, then click OK.
Appendix A Upgrading from Lotus Workplace 2.01
375
k. Click Done.
9. Re-enter values for the Export schedule to use field in each user policy you
configured in Lotus Workplace 2.0.1.
a. Log in to the IBM WebSphere Administrative Console.
Select Lotus Workplace --> Users --> Manage User Policies.
Click a policy to open it.
Under Additional Properties, click Mail Export Details.
In the Export schedule to use field, select an export task, then click Apply
and OK.
10. Check your configuration and WebSphere Administrative Console settings to
verify that they were migrated correctly. Some settings may have changed
during the migration process because of changes in system defaults or
requirements between Lotus Workplace 2.0.1 and Workplace Collaboration
Services.
11. Set up IBM Workplace Collaborative Learning.
12. You can perform the following operations on templates:
v Delete Lotus Workplace 2.0.1 default templates that you have not
customized, as these are duplicated in Workplace Collaboration Services.
v Migrate customizations you made to Lotus Workplace 2.0.1 templates to
their Workplace Collaboration Services counterparts. You can then delete
the customized Lotus Workplace 2.0.1 templates.
v Review the access control page for migrated custom templates, which may
allow Editor access to more users than the Workplace Collaboration Services
default.
v Edit Workplace Collaboration Services templates to move applications
created from templates by changing the categories to which they belong, as
the Lotus Workplace 2.0.1 default categories and Workplace Collaboration
Services default categories differ.
v Test your migrated custom templates to see if they work properly and then
remove the migrated prefix.
b.
c.
d.
e.
For information about templates, template categories, and the template editor,
see the IBM Workplace Collaboration Services information center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?.
13. Install the IBM Workplace rich client installer. This step is not applicable at
this point to nodes in a Network Deployment as they will have done this
earlier in the installation process. For information about installing the rich
client installer, see the IBM Workplace Collaboration Services information
center at http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?.
14. Delete the Lotus Workplace 2.0.1 databases that the upgrade process modified,
as these are no longer usable; but do not delete the 2.0.1 databases that you
backed up prior to upgrading.
Upgrading a Network Deployment
Upgrading a Network Deployment involves the following steps:
1. Make sure that the clocks on all servers are synchronized using a single time
source to assure proper log correlation.
2. Stop all servers in the cluster, including the Deployment Manager and the
HTTP server used by the cluster.
376
Installation and Upgrade Guide
3. Back up the Lotus Workplace 2.0.1 databases. This is an especially important
step. The upgrade process alters Lotus Workplace 2.0.1 databases before
combining them into a single Workplace Collaboration Services 2.5 database.
The altered databases will no longer function properly if for some reason you
need to revert to Lotus Workplace 2.0.1, which you can do by simply restoring
your original, backed-up 2.0.1 databases.
4. If you are deploying IBM DB2, create a new Workplace Collaboration Services
database.
5. Create shared directories that all the nodes in the cluster can access.
6. Install a new Deployment Manager.
7. Install the remote HTTP server.
8. Upgrade the first node in the cluster (Node 1).
9. Copy the upgraded Node 1 cell level configuration to the Deployment
Manager.
10. Create a new IBM WebSphere Portal cluster.
11. Update the Deployment Manager with cluster information.
12. Install an additional node.
13. Perform Network Deployment clean-up:
a. Configure the remote HTTP server.
b.
c.
d.
e.
f.
g.
h.
Enable dynamic caching.
Distribute Embedded Messaging files.
“Modifying properties files” on page 396
Remove JDBC provider configuration from node configuration.
“Modifying the messaging queue file store location” on page 397.
Modify cell-level URL providers to point to the remote HTTP server
Enable Messaging in the cluster.
i. Apply server fixpacks.
14. Complete the upgrade.
Creating shared directories for a Network Deployment
upgrade
1. Back up the following shared directories that you created for Lotus Workplace
2.0.1:
v qfilestore
v lms_juru
v lms_courses
v WPCPIndex
v logs
v packages
v content (if your deployment includes IBM Workplace Collaborative Learning
and you are not using FTP for course transfer)
2. Copy the contents of the Lotus Workplace 2.0.1shared directory to a new
directory on the Deployment Manager server.
3. Delete the contents of the Portal Document Management index (WPCPIndex)
directory in the new location so that the Workplace Collaboration Services
server can create a new search index.
Appendix A Upgrading from Lotus Workplace 2.01
377
Installing a new Deployment Manager
Perform the following steps to install and configure a new Deployment Manager:
1. Install the Deployment Manager.
2. Enable LDAP security.
3. Install the database client on the Deployment Manager. For IBM DB2, use the
DB2 command line to issue this command:
db2 => catalog database WRKPLC at node <node_name>
where
<node_name> is the node name that was created to catalog Lotus Workplace
2.0.1 databases. For Oracle, no steps are required.
4. Install IBM Workplace Collaboration Services on the Deployment Manager
Installing the Deployment Manager
A Network Deployment cell is a group of servers (known as nodes) that are
managed by a special WebSphere Application Server called the Deployment
Manager. Unlike the nodes in an IBM Workplace server installation, the
Deployment Manager does not use WebSphere Portal software.
In a Network Deployment, you designate one server as the Deployment Manager,
which should be a dedicated system. It hosts the WebSphere Administrative
Console and provides a single point of administrative control for all elements in
the WebSphere Application Server cell.
Installing the Deployment Manager software:
To install the WebSphere Application Server Deployment Manager, perform the
following steps.
For more information about installing the WebSphere Application Server
Deployment Manager in a WebSphere Portal cluster, see the WebSphere Portal
Information Center on the Web at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
1. Log in to the server as a user with administrative privileges.
2. Locate the CD for WebSphere Application Server Deployment Manager.
IBM AIX
CD 1-17 (Version 5.0)
Linux
CD 1-14 (Version 5.0)
Windows 2000
CD 1-13 (Version 5.0)
Windows 2003
CD 1-15 (Version 5.0.2)
3. Run the installation program.
AIX and Linux
./<cd_root>/wasnd/<operating_system>/<platform>/install
Microsoft Windows
<cd_root>\wasnd\win\nt\launchpad.bat
where:
378
Installation and Upgrade Guide
<cd_root> is the root directory of the CD.
4. When selecting the features for the ″IBM WebSphere Application Server
Network Deployment Version 5,″ select Deployment Manager.
5. When typing the node, host, and cell names, the host name is the name of the
server on which you are installing the Network Deployment Edition. To form
the node and cell names, append the words ″Manager″ and ″Network″
respectively, to the host name. For example:
Node name: acmeManager
Host name: acme
Cell name: acmeNetwork
6. Locate the CD for WebSphere Application Server Version 5.0 Enterprise Edition.
AIX
CD 1-5 (Version 5.0)
Linux
CD 1-3 (Version 5.0)
Windows 2000
CD 1-1 (Version 5.0)
Windows 2003
CD 1-2 (Version 5.0.2)
7. Run the installation program.
AIX and Linux
./<cd_root>/was/<operating_system>/<platform>/install
Windows
<cd_root>\was\win\install.bat
The WebSphere Application Server Enterprise installation program
automatically detects the existing Network Deployment installation and
provides the option to extend it with the Enterprise extensions.
Applying fix packs to the Deployment Manager:
After installing the base version of the Deployment Manager software, apply the
following fix packs to ensure that IBM Workplace Collaboration Services works
properly.
AIX
Network Deployment fix packs for AIX:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-18
v Enterprise second fix pack level (Version 5.0.2), CD 1-10
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-18
v Enterprise second cumulative fix pack level (Version 5.0.2.2), CD 1-10
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6)
Linux
Network Deployment fix packs for Linux:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-19
v Enterprise second fix pack level (Version 5.0.2), CD 1-8
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-19
v Enterprise second cumulative fix pack level (Version 5.0.2.2), CD 1-8
Appendix A Upgrading from Lotus Workplace 2.01
379
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6)
Windows
Network Deployment fix packs for Windows:
v Network Deployment second fix pack level (Version 5.0.2), CD 1-19
v Enterprise second fix pack level (Version 5.0.2), CD 1-7
v Network Deployment sixth cumulative fix level (Version 5.0.2.6), CD 1-19
v Enterprise second cumulative fix pack level (Version 5.0.2.2), CD 1-7
v Enterprise sixth cumulative fix pack level (Version 5.0.2.6)
Enabling LDAP security on the Deployment Manager
Enable LDAP security on the Deployment Manager by following these steps:
1. Open the WebSphere Application Server administrative console for the
Deployment Manager by typing the following URL from a browser window:
http://dmname:9090/admin
where dmname is the fully qualified DNS name of the Deployment Manager.
2. Click Security → User Registries → LDAP.
3. Enter the values in the fields listed below:
Property
Description
Server User ID
The uid of the WebSphere Portal administrator; for example,
wpsadmin
Server User Password
The password of the user specified in the previous field.
Type
The type of LDAP directory to be used; for example,
IBM_Directory_Server
Host
The fully qualified host name of the LDAP server; for example,
ids51ldap.acme.com
Base Distinguished
Name
The base distinguished name of the directory service, indicating
the starting point for LDAP searches of the directory service; for
example,
l=Nashville,st=Tennessee,c=US,ou=SE,o=Sales,dc=acme,dc=com
Bind Distinguished
Name
The fully qualified distinguished name that the application server
must use to bind to the LDAP directory; for example,
uid=wpsbind,cn=Users,l=Nashville,st=Tennessee,c=US,
ou=SE,o=Sales,dc=acme,dc=com
Bind Password
The password of the user specified in the previous field.
Reuse Connection
Select the check box.
Ignore Case
Select the check box.
SSL
Select the check box if you want to use SSL to secure IBM
Directory Server access. Otherwise, leave the check box clear.
4. Click Apply.
5. Click Advanced LDAP Settings.
6. Enter the values in the fields listed below:
380
Property
Description
User Filter
Add the mail attribute; for example,
(&(|(uid=%v)(mail=%v))(objectclass=inetOrgPerson))
Installation and Upgrade Guide
Property
Description
Group Filter
Add the group attribute; for example,
(&(cn=%v)(objectclass=groupOfUniqueNames))
User ID Map
Add the entry *:uid.
Group ID Map
Add the entry *:cn
Group Member ID
Map
Add the group mapping attribute; for example,
groupOfUniqueNames:uniqueMember
7. Click OK.
8. Click Security → Authentication Mechanisms → LTPA.
9. Enter the values in the fields listed below:
Property
Description
Password
Supply the password.
Confirm Password
Confirm the password.
10. Click Apply.
11. Click Single Signon (SSO).
12. Enter the values in the fields listed below:
Property
Description
Enabled
Select the check box.
Requires SSL
Clear the check box.
Domain Name
The domain name; for example, .acme.com. (The period before the
domain name is required.)
13.
14.
15.
16.
Click OK.
Save your changes.
Click Security → Global Security.
Enter the values in the fields listed below:
Property
Description
Enabled
Select the check box.
Enforce Java 2 Security Clear the check box.
Active User Registry
17.
18.
19.
20.
Choose LDAP.
Click OK.
Save your changes.
Log out and close the browser window.
Shut down the Deployment Manager
(/WebSphere/DeploymentManager/bin/stopManager) and restart it
(/WebSphere/DeploymentManager/bin/startManager).
After enabling security on the Deployment Manager, you will be prompted for
the administrative name and password when you stop and start the
Deployment Manager.
Appendix A Upgrading from Lotus Workplace 2.01
381
Installing IBM Workplace Collaboration Services on the
Deployment Manager
Follow these steps to install IBM Workplace Collaboration Services on the
Deployment Manager.
1. Log in to the server as a user with administrative privileges.
2. In a command prompt window, navigate to the
<drive>:\WebSphere\DeploymentManager\bin directory and stop the
Deployment Manager using the command:
stopmanager -user <admin_name>-password <admin_password>
3. IBM AIX and Linux: Source the setupCmdLine.sh located under the
<install_directory>/WebSphere/DeploymentManager/bin directory:
# . ./setupCmdLine.sh
4. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
5. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
6. Enter the appropriate command to start installation.
AIX and Linux
./install.sh
Microsoft Windows
install.bat
7. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click Next.
8. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
9. At the License Agreement, click I accept the terms, and click Next.
10. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory (recommended examples are shown below), and then
click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
AIX
/usr/IBM/Workplace
Linux
/opt/IBM/Workplace
Windows
c:\Program Files\IBM\Workplace
11. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
12. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Deployment Manager, and then click Next.
13. At the panel ″Enter the fully qualified host name for this installation,″ confirm
that the directory is the one in which the new Deployment Manager has been
installed. Then click Next.
14. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide the user name and password you used to log in to the server.
Confirm the password, and then click Next.
382
Installation and Upgrade Guide
15. At the panel ″Setup has located the IBM WebSphere Deployment Manager,″
verify that the location shown is where you installed the Deployment
Manager, and then click Next.
16. At the panel ″IBM Workplace requires administrator access to the WebSphere
Deployment Manager,″ provide the administrator ID and password you used
for the Deployment Manager, and then click Next.
17. At the panel ″WebSphere Deployment Manager Settings,″ enter the node and
cell name for the Deployment Manager. Then click Next.
18.
19.
20.
21.
If you don’t know the node and cell name, navigate to the WebSphere
\config\cells directory and look for the following names:
v The cell name is shown in <was_root>\config\cells\<cellname>
v The node name is shown in
<was_root>\config\cells\<cellname>\nodes\<nodeName>.
At the panel ″Select the database type,″ select the type of DBMS system you
are using; for example, IBM DB2 Universal Database.
Click Next.
At the panel ″IBM Workplace database connection information,″ enter the
name and password for the database administrator on this server. Then click
Next.
At the second panel for ″IBM Workplace database connection information,″
provided the following database information, and then click Next.
Field
LWPDBDriver
LWPDbLibrary
Description
Specify the database driver class or JDBC
provider for the Workplace Collaboration
Services database (for example, for DB2,
COM.ibm.db2.jdbc.app.DB2Driver).
Specify the database driver class and enter
the location of the zip file that has the
database driver class. Examples:
DB2:
LWPDBName
LWPDBUrl
db2.java./zip (for example,
D:/IBM/SQLLIB/java/db2java.zip)
Enter the database name (for example,
WRKPLC).
Specify the JDBC URL for Workplace
Collaboration Services. For DB2, the URL
would be in the form
jdbc:db2:<database_name>), where
<database_name> is the value of LWPDBName
(for example, for DB2, jdbc:db2:wps50).
22. At the panel ″Summary Information,″ verify that the values you entered are
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
23. The installer displays the final screen, which shows the location of the
installation logs.
24. Click Finish to complete the installation. The installation should take roughly
ten minutes.
Appendix A Upgrading from Lotus Workplace 2.01
383
Installing the HTTP server
Follow these instructions to install IBM HTTP Server (IHS) on IBM AIX, Linux, or
Microsoft Windows. Install the new version of IHS on the system where you
installed the version of IHS used by Lotus Workplace 2.0.1.
1. If you are setting up a remote HTTP server, ensure that the machines that will
host Workplace Collaboration Services or the provisioning server and the
HTTP server are in the same Internet domain.
2. Download the IBM HTTP Server version that corresponds to the operating
system of your server from the IBM Web site (http://www306.ibm.com/software/webservers/httpservers/).
3. Follow the instructions to download the appropriate file to a temporary
directory.
4. Extract the files from the .tar or .zip file to another temporary directory.
For example, for IBM HTTP Server 2.0.42.2 for Linux, use the following
command:
tar -xf HTTPServer.linux.20422.tar
5. Open a command prompt window and enter the following command:
IBM AIX, and Linux
From the <was_root>/bin directory, enter:
./setupCmdLine.sh
Microsoft Windows
From the <was_root>\bin directory, enter:
setupCmdLine.bat
6. Change to the temporary directory in which the extracted files are stored.
7. Enter the following command to start the installation program:
AIX
java -jar setup.jar -console
Linux
java -jar setup.jar
Windows
java -jar setup.jar
8. Select the language in which to run the installation and click Next.
9. Accept the license agreement and click Next.
10. Select the installation directory; for example, /opt1/IBMHttpServer for Linux
or C:\IBMHttpServer for Windows. Then click Next.
11. Select Typical and click Next.
12. Type a valid administrative user name and password, confirm the password,
and click Next.
13. At the Summary panel, click Next.
14. At the Installation Complete panel, click Finish.
15. Set up httpd.conf for IBM Workplace Collaboration Services:
a. Connect to the directory where you installed IHS; for example,
/opt1/IBMHttpServer for Linux or C:\IBMHttpServer for Windows.
b. Connect to the conf directory.
c. Open httpd.conf with a text editor.
d. Add the following lines at the bottom of the file: (Windows)
384
Installation and Upgrade Guide
LoadModule was_ap20_module "<location_of_installed_server> \AppServer\bin\mod_was_ap20_htt
WebSpherePluginConfig <location_of_installed_server> \AppServer\config\cells\plugin-cfg.xm
AddType application/zip.jar
(AIX and Linux)
LoadModule was_ap20_module "<location_of_installed_server> \
/AppServer
/bin/mod_was_ap20_http.so"
WebSpherePluginConfig <location_of_installed_server> /AppServer/config/cells/plugin-cfg.xm
e. Update the Web server plug-in.
f. Restart HTTP.
16. If you are using IBM HTTP Server Version 2.0.42.2 for Windows, follow these
steps to download and apply patch PQ92124 for IBM HTTP Server version
2.0.42.2:
a. Download PQ92124 from this site:
http://www-1.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&q1=PQ92124&uid=swg24008098&
The patch is labeled for HTTP Server Version 2.0.42.1, but also works with
Version 2.0.42.2.
b. Apply the fix by replacing the afpa.sys file with the newer version
provided by the patch.
c. Restart the server.
Upgrading the first node (Node 1)
1. If you are deploying IBM DB2, use the DB2 command line to issue this
command:
db2 => catalog database WRKPLC at node <node_name>
where
<node_name> is the node name that was created to catalog Lotus Workplace
2.0.1 databases.
2. Complete the relevant steps described in “Preparing to upgrade” on page 365.
3. Run the installation program.
4. Install the IBM Workplace rich client provisioning server. If you install the rich
client provisioning server in a Network Deployment, you must do so on Node
1 before adding (federating) that node into the cluster. The procedure for doing
this is described in Installing and configuring the provisioning server and related
links in the Workplace Collaboration Services information center.
Installing IBM Workplace Collaboration Services on Node 1
After preparing to upgrade Node 1, follow these steps. The process takes at least
three hours to complete.
1. Insert the IBM Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation.
2. Change to the LWPServer directory of the installation DVD (for example,
D:\LWPServer).
3. Enter the appropriate command to start the installation.
IBM AIX and Linux
./install.sh
Microsoft Windows
install.bat
Appendix A Upgrading from Lotus Workplace 2.01
385
4. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
5. When you are ready to proceed with the installation, click Next at the
Welcome panel.
6. Select Upgrade the existing instance of IBM Workplace and click Next.
7. At the panel ″Select the Workplace products that you have licensed,″ select all
the products for which you have licenses, and then click Next.
8. At the License Agreement, click I accept the terms, and click Next.
9. At the panel ″Click Next to install IBM Workplace to this directory,″ specify an
installation directory on the new IBM Workplace Collaboration Services server
(recommended examples are shown below), and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
AIX
/usr/IBM/Workplace
Linux
/opt/IBM/Workplace
Solaris
/opt/IBM/Workplace
Windows
c:\Program Files\IBM\Workplace
10. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
11. At the panel ″The installer can configure either the Deployment Manager or a
Node,″ select Node, and then click Next.
12. At the panel ″Enter the fully qualified host name for this installation,″ enter
serverfullDNSname (your server’s full hostname) for the installation. Then click
Next.
13. At the panel ″Enter the IBM Workplace administrative user ID and password,″
provide a name and password for the Workplace Collaboration Services
administrator.
Confirm the password, and then click Next.
14. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
15. The installer displays the final screen, which shows the location of the
installation logs.
16. Click Finish to complete the installation.
After installation has completed, you can confirm that the new Workplace
Collaboration Services server is working correctly on Node 1 by staring the server
and accessing it using the host name of Node 1, specifying port 9081.
Copying Node 1 cell level configuration to the Deployment
Manager
When you upgrade the first node in a cluster (Node 1), the Lotus Workplace 2.0.1
cell level configuration is migrated to IBM Workplace Collaboration Services.
Because the Deployment Manager has been configured as a new server and its cell
386
Installation and Upgrade Guide
level configuration will be used in the new Network Deployment, you must
overwrite the configuration files on the Deployment Manager with files migrated
on the Node 1 system.
1. Navigate to the AppServer/config/cells/<node1_name> directory on Node 1; for
example, (Microsoft Windows) c:\Workplace25\AppServer\config\cells\ABLE.
2. Copy the following files to the
DeploymentManager/config/cells/<deployment_manager_cell_name> directory;
for example, (Windows)
C\Workplace25\DeploymentManager\config\cells\tewksburyNetwork:
v lwp-sync-collabcell.xml
v lwparchive.xml
v lwpcertstore.xml
v lwpdirsearch.xml
v lwplicense.xml
v lwpmailcell.xml
v lwpspamfilter.xml
v messaging.xml
Creating a new IBM WebSphere Portal cluster
Follow these steps to add (federate) the first node (Node 1) to the Deployment
Manager and then create a cluster to which you can add additional nodes:
1. Log on to the Deployment Manager node and start the server.
a. Connect to the DeploymentManager\bin directory; for example (Microsoft
Windows) cd c:\Workplace25\DeploymentManager\bin.
b. Start the server by running the startManager batch file or script; for
example (Windows) startManager.bat
2. Add (federate) Node 1 to the Network Deployment.
a. Log on to Node 1.
b. Open
<wp_root>/shared/app/config/services/DeploymentService.properties with
a text editor.
c. Edit the wps.appserver.name property to specify the name of the Portal
cluster that you are about to create; for example,
wps.appserver.name=LWPCluster.
d. Connect to the <wp_root>/bin directory and run the addNode batch file or
script, using the following parameters: (Windows) addnode
<deployment_manager_host> <port_number> -usernameadmin_user_id
-password admin_password -includeapps
where:
v <deployment_manager_host> is the Deployment Manager host name.
v <port_number> is the Deployment Manager SOAP connector-address. The
default value is 8879.
v admin_user_id is the WebSphere Application Server administrator user
name.
v admin_password is the administrator user password.
For example, (Windows) addNode tewksbury.lotus.com 8879 -username
wasadmin -password wasadmin -includeapps
Appendix A Upgrading from Lotus Workplace 2.01
387
3. Uninstall WpsAdminconsole. The WpsAdminconsole application was installed
automatically to WebSphere Application Server. Once a node is added to a cell,
you cannot locally administer it any longer. The WpsAdminconsole Enterprise
Application must be removed from the cell’s master configuration to avoid Web
server plug-in configuration problems.
a. In the Administration Console on the Deployment Manager, open the
Applications -> Enterprise Applications view.
b. Page through the applications until you find the WpsAdminconsole
application.
c. Select to uninstall that application, making sure the Synchronize changes
with nodes check box is checked.
d. Save your changes.
4. Create a cluster.
a. Log on to the Deployment Manager server and open the WebSphere
Administrative Console.
b. Select Servers --> clusters and then click New.
c. Enter the cluster name. This must be the same name as the one you
specified when you added Node 1 to the Network Deployment (step 2.c.
above); for example, LWPCluster.
d. Select the Create Domain for this cluster check box.
e. Select the Select an existing server to add to this cluster radio button, and
then select WebSphere_Portal server instance for Node 1; for example,
tewksburyNetwork/ABLE/WebSphere_Portal.
f. Select the Create Replication Entry in this Server check box.
g. Click Next (since you will not be adding any more servers at this point).
h. Click Finish.
i. Click Save.
Updating the Deployment Manager with cluster information
Follow these steps to add cluster information to the Deployment Manager. You
must already have created a cluster, and added the first node to the cluster.
1. On the Deployment Manager, navigate to the <iwp_root>\install directory,
where <iwp_root> is the root installation directory for IBM Workplace
Collaboration Services.
2. Open the installDM.properties file with a text editor.
3. Add the cluster name as the value for ″lwp.clusterName=″ (for example,
lwp.clusterName=LWPCluster).
4. Save the file.
5. Open a command prompt window.
6. Navigate to the <was_root>\bin directory, where <was_root> is the root
WebSphere Application Server installation directory.
7. Run the following command:
IBM AIX and Linux
./setupCmdLine.sh
Microsoft Windows
setupCmdLine.bat
8. Navigate to the <iwp_root>\install directory.
9. Run the following command:
388
Installation and Upgrade Guide
AIX and Linux
./lwpDMconfig.sh
Windows
lwpDMconfig.bat
10. Restart the Deployment Manager.
Installing IBM Workplace Collaboration Services on an
additional node
After you have upgraded the first node (Node 1) in a Network Deployment, follow
these steps to install IBM Workplace Collaboration Services on another node (Node
2):
1. Log on to the system as an administrator where Node 2 of the Lotus
Workplace 2.0.1 server resides.
2. Run the installer.
a. Insert the Workplace Collaboration Services installation DVD into the
DVD-ROM drive of your workstation and go to the LWPServer directory
(for example, D:\LWPServer).
b. Enter the appropriate command to start installation.
IBM AIX and Linux
./install.sh
Microsoft Windows
install.bat
c. At the panel ″Select a language to be used,″ select the language for the
installation program, and then click OK.
d. Click Next at the Welcome panel.
e. Select Install a new instance of IBM Workplace and click Next.
f. At the panel ″Select the Workplace products that you have licensed,″ select
all the products for which you have licenses, and then click Next.
g. At the License Agreement, click I accept the terms, and click Next.
h. At the panel ″Click Next to install IBM Workplace to this directory,″
specify an installation directory (recommended examples are shown
below), and then click Next.
The characters in the directory path name must be single-byte coded (8 bit)
characters from the ISO 8859-1 West European (Latin-1) character set.
AIX
/usr/IBM/Workplace
Linux
/opt/IBM/Workplace
Solaris
/opt/IBM/Workplace
Windows
c:\Program Files\IBM\Workplace
i. At the panel ″IBM Workplace supports different deployment topologies,″
select Network Deployment, and then click Next.
j. At the panel ″The installer can configure either the Deployment Manager or
a Node,″ select Node, and then click Next.
Appendix A Upgrading from Lotus Workplace 2.01
389
k. At the panel ″Enter the fully qualified host name for this installation,″
enter the full hostname used by the existing Lotus Workplace 2.0.1 server
on the node for the installation. Then click Next.
l. At the panel ″Enter the IBM Workplace administrative user ID and
password,″ provide a name and password for the Workplace Collaboration
Services administrator.
Confirm the password, and then click Next.
m. At the panel ″Summary Information,″ verify that the administrator ID is
correct.
If they are correct, click Install to start the installation process. Otherwise,
click Back to correct the settings.
n. The installer displays the final screen, which shows the location of the
installation logs.
o. Click Finish to complete the installation.
3. Disable LDAP security with the Configuration Wizard
a. Log in to the Workplace Collaboration Services server.
b. Start IBM Cloudscape by running the following command from the
<wp_root>\rootscripts\subtasks directory:
IBM AIX and Linux
./startNetworkServer.sh
Microsoft Windows
startNetworkServer.bat
c. Open a command prompt and navigate to the <wp_root>\rootscripts
directory, where <wp_root> is the root WebSphere Portal Server installation
directory.
d. Stop all Workplace Collaboration Services servers with the following
case-sensitive command.
AIX and Linux
./stopWorkplaceServices.sh
Windows
stopWorkplaceServices.bat
e. Restart the Cloudscape network server by running the following command
from the <wp_root>\rootscripts\subtasks directory:
AIX and Linux
./startNetworkServer.sh
Windows
startNetworkServer.bat
f. Restart the IBM WebSphere Application Server by running the following
the following command from the <was_root>\bin directory:
AIX and Linux
./startServer.sh server1
Windows
startServer.bat server1
g. Navigate to the <wp_root>\config\wizard directory.
h. Type the command for the mode in which you want the wizard to run.
Note: Online help is not available in console mode.
Linux
390
Installation and Upgrade Guide
To run the wizard with the graphical user interface:
./configwizard.sh
Aix and Linux
To run the wizard in console mode (without the graphical user interface):
./configwizard.sh -console
Windows
To run the wizard with the graphical user interface:
configwizard.bat
To run the wizard in console mode (without the graphical user interface):
configwizard.bat -console
i. At the Welcome screen, click Next to start the wizard.
j. At the panel ″Select a language to be used,″ select the language you want
to see when running this wizard, and then click OK.
k. Shoose Disable security, and then click Next.
l. Enter the following values:
WasAdminID=<admin_name>WasAdminPwd=<admin_password> where
<admin_> refers to the user name and password you specified as the
WebSphere® Application Server administrator user name and password
when you intitiated the installation process.
m. Click Next.
n. Enter the path to the wpconfig.properties file; for example,
D:\WebSphere\Portal\Server\config\wpconfig.properties
o. Leave all the default settings, enter the Workplace Collaboration Services
administrator password, then click Next.
p. Click Next. LDAP security is now disabled.
4. Having installed a fresh copy of Workplace Collaboration Services on the
Lotus Workplace 2.0.1server where Node 2 resides, you need to copy some
configuration files to the new installation. As an example, for a Windows
installation, where the Lotus Workplace 2.0.1 installation directory for the
node is c:\workplace201 and the new Workplace Collaboration Services
installation directory is c:\workplace25, copy these files from
c:\workplace201\AppServer to c:\workplace25\AppServer:
c:\workplace201\AppServer\ssc_database.dat,
c:\workplace201\AppServer\ssc_database.hsh,
c:\workplace201\AppServer\ssc_database.properties,
c:\workplace25\AppServer\pkiConfig.xml
to c:\workplace25\AppServer
Note: pkiConfig.xml should be the same as the one on Lotus Workplace 2.0.1
Node 1. If not, copy the file from Lotus Workplace 2.0.1 Node 1.
Copy the spam filter data file from
c:\workplace201\AppServer\lsfdata\data\svrdb.mgw.vvdmb to
c:\workplace25\AppServer\spamdata\data\svrdb.mgw.vvdmb
5. Enable LDAP security
a. Make sure that the Cloudscape server and server1 are still running.
b. Launch the Configuration Wizard again and select Run Wizard again.
c. Select Enable LDAP security, then click Next.
d. Select the type of LDAP directory server used by Lotus Workplace 2.0.1
servers; for example, IBM Directory Server.
e. Click Next.
Appendix A Upgrading from Lotus Workplace 2.01
391
f. Enter the path to the helper file wpconfig.properties on the Lotus
Workplace 2.0.1 server; for example,
c:\WebSphere\PortalServer\config\wpconfig.properties.
g. Click Next.
h. Navigate through the remaining Wizard screens, making sure that the
property values are correct and correcting any that are not. (The value for
LWPDBAdminPassword can be any nonempty string.) Click Next to
proceed from one screen to the next.
i. Click Next to to begin enabling LDAP security.
j. When the Configuration Wizard finishes, stop the Cloudscape server and
server1. LDAP will be enabled when you restart the server.
6. Catalog the new Workplace Collaboration Services database (WRKPLC) on
Node 2 For IBM DB2, use the DB2 command line to issue this command:
db2 => catalog database WRKPLC at node <node_name>
where<node_name> is the node name that was created to catalog Lotus
Workplace 2.0.1 databases.
For Oracle, no steps are required.
7. Connect to the WebSphere Portal Server database and to the Workplace
Collaboration Services database (WRKPLC)
a. Start the Cloudscape network server (as in Step 3.e. above).
b. Start the WebSphere Application Server (as in Step 3.f. above).
c. Run the Configuration Wizard (as in Steps 3.g. -3.h. above).
d. Select Connect to a database.
e. Type the full distinguished name (DN) of the WebSphere Portal Server
administrator; for example,
uid=wpsadmin,cn=users,l=Westford,st=Massachusetts,c=US,
ou=Lotus,o=Software Group,dc=IBM,dc=com
f. Type the administrator password.
g. Type the LDAP administrator’s full distinguished name and password.
h. Select the type of database for the WebSphere Portal Server. This must be
the same as the type used by Lotus Workplace 2.0.1; for example, IBM
DB2 Universal Database.
i. Click Next.
j. Enter the path to the helper file wpconfig.properties on the Lotus
Workplace 2.0.1 server; for example,
c:\WebSphere\PortalServer\config\wpconfig.properties.
k. Click Next.
l. Navigate through the remaining Wizard screens, making sure that the
property values are correct and correcting any that are not. Click Next to
proceed from one screen to the next.
1) In screen 6 of the Wizard, you may need to enter a new value for
WpsDBNode.
2) In screen 8 of the Wizard, enter <wp_root>/wpcp/v5.0/runtime/lib as
the value for WpcpResourceUrl; for example,
c:\\Workplace\PortalServer\wpcp\v5.0\runtime\lib.
m. Click Next to execute the task.
n. When the task completes, click Run Wizard again.
o. Select IBM Workplace Connection to database
392
Installation and Upgrade Guide
p. Select the database type for the database that was created when you
upgraded Node 1; for example, IBM DB2 Universal Database.
q. Enter an appropriate value for LWPDBLibrary; for example,
c:\IBM\SQLLIB\java\db2java.zip.
r. Edit the following property values:
LWPDBName (the name of the new Workplace Collaboration Services
database, WRKPLC by default). LWPDbURL (the database URL for the new
Workplace Collaboration Services database; for example,
jdbc:db2:WRKPLC). LWPDBAdminUser (the user name of the Workplace
Collaboration Services database administrator; for example, db2admin. The
default is the Lotus Workplace 2.0.1 LWPCOM database administrator’s
user name.) LWPDBAdminPassword (the Workplace Collaboration Services
database administrator’s password. The default is the Lotus Workplace
2.0.1 LWPCOM database administrator’s password). LWPABAppUser (the
Workplace Collaboration Services database application user name. The
default is the Lotus Workplace 2.0.1 LWPCOM database application user
name). LWPDBAppPassword (the Workplace Collaboration Services
database application user password. The default is the Lotus Workplace
2.0.1 LWPCOM database application user password).
s. Click Next to execute the task.
t. Close the Wizard.
u. Stop server1.
v. Stop the Cloudscape network server.
8. Copy wmm.xml from Node 1 from <wp_root>/shared/app/wmm/wmm.xml
to the same location on Node 2.
9. Install the IBM Workplace rich client provisioning server.
a. Copy the following directories from Node 1 to Node 2:
<wp_root>/shared/app<rich_client_root>/wedm_extensions.
Note: <rich_client_root> must be the same directory as the
<rich_client_root> on Node 1.
10. Add (federate) Node 2 to the Deployment Manager.
Attention: If you plan to install the rich client provisioning server on this
node, you must do so before federating a node. Installation of the
provisioning server will fail if you attempt to install after federating the node.
a. Make sure the new Deployment Manager is running on the new
Deployment Manager node.
b. On the Deployment Manager node, open a command prompt and navigate
to the <was_root>\DeploymentManager\bin directory.
c. Type the following command:
AIX and Linux
./startManager.sh
Windows
startmanager
d. Log on to the system where the Lotus Workplace 2.0.1 Node 2 resides.
e. Connect to the <wp_root>/shared/app/config/services.
f. Using a text editor, open Deployment.Services.properties and edit the
wps.appserver.name property to specify the name of the Portal cluster that
you created when you federated Node 1; for example,
wps.appserver.name=LWPCluster.
Appendix A Upgrading from Lotus Workplace 2.01
393
g. Connect to the <was_root>/bin directory; for example,
c:\Workplace\25\AppServer\bin.
h. Run the addNode batch file or script:
AIX and Linux
./addNode.sh deployment_manager_host port_number -username admin_user_id -password admin_pass
Windows
addnode deployment_manager_host port_number -username
admin_user_id -password admin_password
where:
v deployment_manager_host is the Deployment Manager host name.
v port number is the Deployment Manager SOAP connector-address. The
default value is 8879.
v admin_user_id is the WebSphere Application Server administrator user
name.
v admin_password is the administrator user password.
After a node has been successfully added, a confirmation message
displays.
11. Add Node 2 to the cluster.
a. Make sure the new Deployment Manager is running on the new
Deployment Manager node.
b. Log on to the WebSphere Administrative Console and click Servers →
Clusters.
c. Click the name of the cluster that you created when you federated Node 1;
for example, LWPCluster.
d. Select Cluster Member, then click New.
e. Privovide values for the following properties, and then click Apply:
Member Name (for example, WorkplacePortalServer02. After this server
becomes part of the cluster, the WebSphere server on this node is renamed
to the name you specified). Node (Select the node name for this node; for
example, Node 2.) Generate Unique HTTP ports (Select this check box.)
f. Click Next and review the summary of changes.
g. Click Finish to complete the configuration.
h. Select Synchronize changes with Nodes, then click Save.
Configuring the HTTP server
You must place an updated version of the Deployment Manager plugin-cfg.xml file
on the remote HTTP server and on all nodes in the Network Deployment. Follow
these steps to create the plugin-cfg.xml file, and then distribute it.
1. Make sure the Dweployment Manager is running on the Deployment
Manager node.
2. Open the WebSphere Application Server Administrative Console.
3. Choose Environment → Update Web Server Plugin, then click OK.
4. Log on to the system where you installed IHS 2.0.42.2.
5. Stop all HTTP servers.
6. Back up plugin-cfg.xml on the IBM WebSphere Application Server
(<was_root>/config/cells/plugin-cfg.xml). This is the plugin configuration file
used by Lotus Workplace 2.0.1 Network Deployment. If you want to revert to
Lotus Workplace 2.0.1, you will need this file in its original form.
394
Installation and Upgrade Guide
7. Copy the updated HTTP plug-in (plugin-cfg.xml) from the Deployment
Manager server to the remote HTTP server directory. That is, copy from
<deployment_manager_install_location>/config/cells/plugin-cfg.xml to
<WebSphere_Application_Server_install_location>/config/cells/plugin-cfg.xml in
the WebSphere Application Server directory on the remote HTTP server.
8. Open plugin-cfg.xml on the remote HTTP server with a text editor, and
replace the Deployment Manager directory name with the WebSphere
Application Server directory name; for example, replace Deployment Manager
with AppServer.
9. Save the file.
10. Connect to the /bin subdirectory of the directory in which you installed IHS
2.0.42.2 and issue the following command to affirm that the server is working
correctly:
(Microsoft Windows) apache -k start (IBM AIX and Linux) # ./apachectl start
Enabling dynamic caching
You must enable dynamic caching in your IBM Workplace Collaboration Services
cluster environment to synchronize the cached views and access rights for all
nodes. Otherwise, users might have different views or different access rights,
depending on which node handles the user’s request.
Enabling cache replication
1. Select Node 1 in the cluster and select Dynamic Cache Service from the
Additional Properties section (Servers → Application Servers →
WebSphere_Portal → Dynamic Cache Service)
2. Select Enable service at server startup and Enable cache replication.
3. Click the Enable cache replication link to go to the Internal Messaging view.
4. Select the Workplace Collaboration Services cluster as the domain for the
replicator and one of the server members as the replicator.
5.
6.
7.
8.
9.
10.
Note: All cluster members must use these same replication settings:
v Select Runtime mode = Push only.
v Set the Push frequency to 1 second.
Apply the changes and click OK.
Repeat the above steps for all server members in the cluster.
Go to Environment → Internal Replication Domains → cluster_name.
Verify that DRS partition size and DRS pool size are set to 10.
Apply the changes and then click OK.
Save the changes to the Deployment Manager’s master configuration by
clicking the Save link after the last modification.
Creating replicator entries for subsequent nodes
Perform these steps for Node 2 and every subsequent node you add to the cluster.
1. On the Deployment Manager, click Environment → Internal Replication
Domains.
2. Click PortalCluster.
3. Click Replicator Entries.
4. Click New.
5. Give this new replicator a name; for example, WorkplaceServer02.
Appendix A Upgrading from Lotus Workplace 2.01
395
6. Select the node you want to configure and enter the host name for this server.
You can only create one replicator on a server, so the list shows only those
servers that do not have a replicator.
7. Select unique ports on this node for the replicator and client port such that
there are no port conflicts with other services on this node; for example, 7980
and 7981.
8. Click OK, then click OK again, and save your settings.
9. Click Servers → Application Servers → Name of Portal server node → Dynamic
Cache Service → Enable Cache Replication.
10. Keep the replication domain as PortalCluster and select the new replicator (for
example, WorkplaceServer02) from the list of replicators.
11. Click OK, then click OK again, and save your settings.
Distributing Embedded Messaging files
Files related to the Embedded Messaging feature might be installed on the
Deployment Manager machine even if you did not select this feature when you
installed the Deployment Manager. For example, these files might be installed
when you install WebSphere Application Server Enterprise or fixes on the
Deployment Manager machine.
Follow these steps to check for files related to the Embedded Messaging feature in
your environment and take the appropriate measures:
1. On the Deployment Manager system, search for the cmm.jar and cmmlmpl.jar
files. By default, these files appear in the <was_root>/lib directory. If these files
are not present on the Deployment Manager machine, no further action is
needed.
2. If these files are present, copy them to the <was_root><was_root>/lib directory
on each node; for example, c:\WebSphere\AppServer
Modifying properties files
It is necessary to modify a number of properties files in order for team spaces and
search to function correctly in the cluster. You must make these modifications on
all nodes.
1. Change http://<node_DNS> to http://<ihs_root_DNS> in the following files:
v lwpae.properties
v lwpagenda.properties
v lwpchatroom.properties
v lwpformsstorage.properties
v lwplistadapter.properties
v lwppdmadapter.properties
v lwpaistorage.properties
v lwpteamtasklist.properties
v lwpworkplaceurl.properties
These files reside in the following directories:
v (Microsoft Windows) c:\<lwp_root>\properties
v (IBM AIX) /usr/<lwp_root>/properties
v (Linux) /opt/<lwp_root>/properties
396
Installation and Upgrade Guide
2. Modify the WCM.properties file by changing the line
#wcm.indexedsearch.path=/ to wcm.indexedsearch.path=<path>\WPCPindex
where <path> is the path to the WPCPIndex shared directory folder you created
earlier in the installation process.
WCM.properties resides in the following directories:
v (Windows)
c:\<was_root>\wpcp\config\WebSphere_Portal\author\WCM.properties
v (AIX)
/usr/<was_root>/wpcp/config/WebSphere_Portal/author/WCM.properties
v (Linux)
/opt/<was_root>/wpcp/config/WebSphere_Portal/author/WCM.properties
Removing JDBC provider configuration from node
configuration
Make these changes on Node 2 and any subsequent nodes.
1. From the WebSphere Administrative Console, click Resources → JDBC
Providers .
2. Click Browse and select Node 2.
3. Click Apply.
4. Select wmm50jdbc, then click Delete.
5. Save your changes.
Modifying the messaging queue file store location
It is recommended that you create a separate messaging queue file store directory
for IBM Workplace Collaboration Services. You created this directory (qfilestore)
when you created shared directories earlier in the installation process. Make these
changes on Node 1 and all subsequent nodes.
1. From the WebSphere Administrative Console, navigate to Lotus Workplace →
Mail cell-wide settings
2. Scroll down to ″General Mail services.″
3. Change ″Network path of the mail service queue directory″ to the shared
directory created for the Workplace Collaboration Services mail queue; for
example, N:\nd_share\qfilestore.
4. Click OK and then Save.
Modifying cell-level URL providers to point to the remote
HTTP server
After you have federated the system, modify the following cell-level URL
providers to use the URL for the remote HTTP server instead of the Deployment
Manager.
1. From the Deployment Manager WebSphere Administrative Console, click
Resources → URL Providers.
2. Switch to the cell level and click Default URL Provider → URLs.
3. Click LMS_URL.
4. Update the URL to use the value of your HTTP server (for example,
http://web1.acme.com/lms-lmm).
Appendix A Upgrading from Lotus Workplace 2.01
397
5.
6.
7.
8.
9.
Note: Removing the port number (9081) from the URL assumes that the
external HTTP server uses port 80. If the HTTP server uses a different
port number, you should replace :9081 with the specific port number.
Save your changes.
Click Workplace Client Installer Download Server.
Update the URL to use the value of your HTTP server, then save your changes.
Click Workplace Client Provisioning Server server.
Update the URL to use the value of your HTTP server, then save your changes.
Mapping the Mail module to Mail servers
This step is done automatically when you add Node 1 to a cluster. Follow these
steps on Node 2 and all subsequent node servers to map the Mail module to the
Mail servers.
1. From the IBM WebSphere Administrative Console on the Deployment
Manager, click Applications → Enterprise Applications.
2. Page through the applications until you find Mail_wmmApp, then select it.
3. Under Additional Properties, select Map Modules to Application Servers.
4. Select the check boxes for all modules.
5. Select all Mail server servers.
6. Click Apply and then click OK.
7. Click Save.
8. Select Synchronize across nodes.
9. Click Save.
10. Restart the IBM Workplace Collaboration Services servers.
Applying fix packs to the Network Deployment servers
Apply the following IBM WebSphere Application Server fix packs to the
Deployment Manager and all nodes to ensure that IBM Workplace Collaboration
Services and provisioning servers work properly. Download the fix packs and
install them in the order shown below.
1. PK00049
2.
3.
4.
5.
Download this fixpack from http://www1.ibm.com/support/docview.wss?uid=swg24009362. This is a special version of
PK00049 to be used with IBM Workplace Collaboration Services.
Download the remaining fixpacks from from
http://www.ibm.com/support/us/.
PQ88539
PQ90368
PQ87768
PK04318
Note: You must install this last patch after installing the server and the rich client
installer but before end users provision.
398
Installation and Upgrade Guide
Appendix B Completing Optional Post-installation Tasks
After you complete installing and setting up IBM Workplace Collaboration
Services, you can choose to perform some additional configuration tasks for your
site.
Optional post-installation tasks
After you have completed installing and setting up IBM Workplace Collaboration
Services, you can choose to perform some additional configuration tasks for your
site, including:
v Customizing attributes.
v Using multiple LDAP directories.
v Changing the LDAP server name or port after configuration.
v Changing the IBM Workplace Collaboration Services context root.
For more information about administering and configuring individual products,
see the IBM Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Customizing attributes
You can customize the user and group attributes that IBM Workplace Collaboration
Services uses in the following ways.
v Configure optional directory attributes for user policies and messaging.
v Map lookaside attributes to LDAP attributes.
v Customize the attributes People Finder displays.
v Customize the attributes that Directory Search displays.
For information on customizing People Finder and Directory Search attributes, see
the IBM IBM Workplace Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?.
Related concepts
“Optional directory attributes for user policies and messaging”
Related tasks
“Mapping lookaside attributes to custom LDAP attributes” on page 401
Optional directory attributes for user policies and messaging
You can set up optional attributes to use with user policies and IBM Workplace
Messaging. Some optional attributes must be in the LDAP directory.
User policy attribute
The user policy attribute, ibm-lwpUserPolicy, is stored in member profiles in the
IBM WebSphere Member Manager. The attribute stores the name of the user policy.
Use the setUserPolicy command to change the value assigned to the attribute.
If you use a policy attribute in LDAP, you must either extend the LDAP directory
schema or use an existing attribute that is equivalent to the ibm-lwpUserPolicy
attribute in WebSphere Member Manager. You map the WebSphere Member
© Copyright IBM Corp. 2002, 2005
399
Manager attribute to the LDAP attribute so that WebSphere Member Manager uses
the LDAP attribute instead.
Group mail attribute
You can extend the LDAP schema to include a mail attribute for group records.
Then if a group uses the mail attribute in LDAP, IBM Workplace Messaging uses
the attribute value as the e-mail address for the group. The attribute
ibm-primaryEmail in WebSphere Member Manager maps to the LDAP attribute mail
and is configured, by default, to apply to groups.
If you do not extend the LDAP schema, the e-mail address is derived from the
common name (CN) of the group. If a common name contains only ASCII letters,
numbers, underscores, and dash characters, Messaging takes the name and
appends the local domain name to the common name. If a common name contains
spaces, then Messaging must encode the e-mail address. To avoid encoded group
e-mail addresses, add a mail attribute to group records, or add another common
name value that does not contain spaces. For example, add ″acme_support″ as an
additional common name for the LDAP group ″acme support″.
E-mail aliases attribute
An e-mail alias is an alternate user name that can be used in e-mail addresses. For
example, the user [email protected] can have the mail aliases
[email protected] or [email protected] To populate the ibm-otherEmail
attribute, which is the attribute that WebSphere Member Manager uses for e-mail
aliases, use the Lmadmin UpdateAccount command.
The WebSphere Member Manager supports multiple mail addresses using the
ibm-primaryMail attribute. The e-mail alias attribute can reside in WebSphere
Member Manager or the LDAP directory. At installation, the alias attribute is
configured to be a WebSphere Member Manager attribute.
Mail-forwarding attribute
Use the ibm-forwardingEmail attribute in the WebSphere Member Manager to store a
single value for a forwarding e-mail address. To change the forwarding e-mail
address, use the Lmadmin UpdateAccount command.
WebSphere Member Manager stores the mail-forwarding attribute, but you can
map the attribute to a mail-forwarding attribute in LDAP.
Mail cell attribute
Use a mail cell attribute for directory lookups and for routing mail to other mail
systems in the same domain. Use an existing LDAP attribute or extend the LDAP
schema to create a new attribute to hold the cell name for each user.
Mail list object
Create a mail list object in an LDAP directory so that you can create mail lists that
contain e-mail addresses that are not in the LDAP directory. If your mail
infrastructure contains, for example, IBM Workplace Messaging and IBM Lotus
Notes e-mail addresses, create the mail list object so that users can send mail to
groups. Because standard groups in LDAP contain only distinguished names,
groups contain the names of only those users who are in the LDAP directory.
400
Installation and Upgrade Guide
Group mailing lists contain e-mail addresses and may include external Internet
addresses that are not listed in the LDAP directory.
Creating a mail list object in the LDAP directory:
You can extend the LDAP schema to create a mail list object in the LDAP directory.
Unlike LDAP groups that can contain only distinguished names of users in the
LDAP directory, mail lists can contain external e-mail addresses.
1. Extend the LDAP schema by creating the ibm-mailListMember attribute. This
multi-valued attribute holds the e-mail addresses for the members of the list.
Insert the following attribute in your LDAP directory:
(
1.3.18.0.2.4.3014
NAME ’ibm-mailListMember’
DESC ’Mailing List member entries’
EQUALITY caseIgnoreIA5Match
SUBSTR caseIgnoreIA5SubstringsMatch
USAGE userApplications
)
2. Extend the LDAP schema by creating the object class ibm-mailList using the
schema below.
(
1.3.18.0.2.6.557
NAME ’ibm-mailList’
DESC ’Used to store Mailing List entries for IBM Lotus Email.’
STRUCTURAL
SUP top
MUST ( cn $ mail )
MAY ( ibm-mailListMember $ description )
)
3. Assign the required attributes cn and mail to the object class. The cn attribute
value must be a short descriptive name for the mail list. The mail attribute is
the e-mail address assigned to the list.
4. Optional: Type e-mail addresses in the place reserved for ibm-mailListMember.
How multiple e-mail addresses are entered depends on the user interface of
your LDAP tools. IBM Directory Server puts the different values on separate
lines without additional delimiters.
5. Optional: Enter comments about the list in the place reserved for description.
6. Optional: Create an instance of the object class for each mail list.
Mapping lookaside attributes to custom LDAP attributes
If you use an LDAP directory, some attributes that IBM Workplace Collaboration
Services uses are stored in the LDAP directory. These attributes are mapped to IBM
WebSphere Member Manager attributes, with the mapping defined in the
<wp_root>\wmm\wmmLDAPServerAttributes.xml file. Other attributes that do not
typically correspond to LDAP attributes are stored in the lookaside database. The
<wp_root>\wmm\wmmLAAttributes.xml file defines the attributes that are stored
in the lookaside database. The content of these two files varies slightly depending
on which LDAP directory you configure to work with Workplace Collaboration
Services.
If you add a custom person attribute to your LDAP directory that is the equivalent
of an attribute stored by default in the lookaside database, you can map the
lookaside attribute to the LDAP attribute so that the LDAP directory attribute is
used instead. Then other applications can use the attribute, and you can also
populate the attribute using LDAP directory administration tools. If you map a
Appendix B Completing Optional Post-installation Tasks
401
lookaside attribute to an LDAP attribute, no data is transferred from the lookaside
database to the LDAP directory. Rather, the repository for the attribute changes.
Examples of person attributes that are stored in the lookaside database by default
that you might want to map to LDAP attributes are: ibm-middleName,
ibm-personalTitle, and ibm-forwardingEmail.
Note: All group attributes are stored in the LDAP directory.
To map a lookaside attribute to a custom person LDAP attribute, follow these steps
after you connect Workplace Collaboration Services to an LDAP directory:
1. Using a text editor, open the file <wp_root>\shared\app\wmm\wmm.xml and
search for the tag <supportedLdapEntryType name=″Person″.
2. In the wmm.xml file, add the custom object class that defines the custom
person attribute to objectClassesForRead and objectClassesForWrite.
3. Open the file <wp_root>\wmm\wmmLAAttributes.xml and then remove the
attributeMap tag for the lookaside attribute.
4. Open the file <wp_root>\wmm\wmmLDAPServerAttributes.xml and then add
the same attributeMap tag that you deleted in Step 3 but change the
pluginAttributeName value to the LDAP attribute name.
5. Restart WebSphere_Portal and Mail_Server_1 .
Related tasks
“Example of mapping ibm-MiddleName to IBM Tivoli Directory Server
middleName”
Example of mapping ibm-MiddleName to IBM Tivoli Directory Server
middleName:
The following example shows how to map the lookaside attribute
ibm-MiddleName to the IBM Tivoli Directory Server attribute middleName,
defined in the ePerson auxiliary object class.
1. Open <wp_root>\shared\app\wmm\wmm.xml, search for
<supportedLDAPEntryType name=″Person″, and then add ePerson as a value
for objectClassesForRead and objectClassesForWrite:
<supportedLdapEntryType name="Person"
rdnAttrTypes="uid "
objectClassesForRead="inetOrgPerson;ePerson "
objectClassesForWrite="inetOrgPerson;ePerson"
searchBases="cn=users,dc=acme,dc=com"/>
2. Open <wp_root>\wmm\wmmLAAttributes.xml, and then remove the following
attributeMap tag:
<attributeMap wmmAttributeName="ibm-middleName"
pluginAttributeName="ibm-middleName"
applicableMemberTypes="Person"
dataType="String"
valueLength="128"
multiValued="true"/>
3. Open <wp_root>\wmm\wmmLDAPServerAttributes.xml, and then add the
attributeMap tag you deleted in step 2, but specify middleName as the
pluginAttributeName value:
<attributeMap wmmAttributeName="ibm-middleName"
402
Installation and Upgrade Guide
pluginAttributeName="middleName"
applicableMemberTypes="Person"
dataType="String"
valueLength="128"
multiValued="true"/>
4. Restart the IBM WebSphere Portal Server and mail server.
Multiple LDAP directories
IBM Workplace Collaboration Services supports multiple LDAP directories in two
contexts. You can make additional searchable LDAP directories available to mail
users. The users can then use the Directory Search feature to search for names in
these directories, in addition to an LDAP directory configured for Workplace
Collaboration Services, when they complete tasks such as addressing e-mail.
Searches of these additional directories are direct-to-LDAP searches that are
independent of Member Manager. You set up additional searchable LDAP
directories from the WebSphere Administrative Console after you set up Workplace
Collaboration Services. For more information about additional searchable
directories, go to the IBM Workplace Collaboration Services information center.
In addition, if your organization’s LDAP directory is not supported, or if you use a
pilot version of Workplace Collaboration Services, you can install an LDAP
directory specifically for Workplace Collaboration Services and use IBM Tivoli
Directory Integrator to integrate it with your organization directory. Directory
coexistence has the following advantages:
v The organization and Workplace Collaboration Services directory, the
organization legacy mail system, and IBM Workplace Messaging can use the
same domain name space for mail addressing.
v Person records in the organization directory can be automatically copied, and
then continually updated in the organization directory.
v Automatic account creation in IBM Workplace Messaging can be done through
the organization mail system administrative console.
v You can choose whether to migrate mail from organization mail accounts on a
per account basis.
For more information on coexisting LDAP directories, see the IBM Workplace
Collaboration Services Information Center at
http://publib.boulder.ibm.com/infocenter/lwpphelp/index.jsp?
Changing the LDAP host name or port number after
configuration
Complete these steps to change the host name or port number for the LDAP
directory server. The change must point to a replica of the original LDAP directory.
If the new LDAP directory location is not a replica, users’ unique identifiers are
lost and users will not be able to authenticate and access data they previously
created.
1. Log in to the server as a user with administrative privileges.
2. From the WebSphere Administrative console on the WebSphere Portal port (for
example, 9091 on Microsoft Windows), click yourNode → Security → User
Registries → LDAP, and update the host and port values. Click OK to save
your changes.
3. Stop IBM Workplace Collaboration Services.
Appendix B Completing Optional Post-installation Tasks
403
4.
5.
6.
7.
For more information, see ″Starting and stopping IBM Workplace Collaboration
Services″ in Chapter 3.
Open wmm.xml, stored in the <wp_root>\shared\app\wmm directory, and
change the values for ldapHost and ldapPort. Save your changes.
If you are using the LDAP directory for messaging, you might need to modify
the messaging.xml file.
a. Open messaging.xml, stored in the <was_root>\config\cells\node name
directory.
b. Change the values for name and port to reflect the correct values. Save your
changes.
Check the log file to be sure the command was successful.
Restart the application servers for the changes to take effect.
Related concepts
Optional post-installation tasks
Related tasks
Starting and stopping IBM Workplace Collaboration Services
Related reference
Root installation directories
Changing the installed context root
Although IBM Workplace Collaboration Services is installed with the default
context root /lwp, you can change it after installation to better suit the needs of
your organization.
Attention: If you want to change the context root, you must do so before you
transfer data from the default Cloudscape database to another DBMS
product as described in Phase 5.
Before choosing a new context root, be sure to take the following requirements into
consideration:
v When specifying the WpsContextRoot property, do not specify a value that is the
same as a directory existing in a portlet WAR directory. For example, if you set
the context root for Workplace Collaboration Services to be /images and there is
also a portlet with the directory structure /myPortlet.ear/myPortlet.war/images,
this could cause a conflict if the portlet encodes context root references to
resources in its own /images directory. In this situation, the portlet would be
unable to display images because Workplace Collaboration Services would look
for the image resources according to its own context root path instead of using
the directory path specified by the portlet WAR file.
v You cannot set the context root to only /. Workplace Collaboration Services
requires a full path, for example, /lwp/workplace.
1. Stop Workplace Collaboration Services as described in the topic, ″Stopping
Workplace Collaboration Services.″
2. Locate the <install_root>/PortalServer/config/wpconfig.properties file and
create a back-up copy before changing any values.
3. Use a text editor to open the wpconfig.properties file and enter values that are
appropriate for your environment, using the table that follows for guidance.
Note: When modifying this file:
404
Installation and Upgrade Guide
v Do not change any settings other than those that are specified in the
table. For instructions on working with this file, see the WebSphere
Portal topic, ″Configuration properties reference″ at
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html
for a complete properties reference, including default values.
v Use / instead of \ for all platforms.
v Some values, shown here in italics, might need to be modified for
your environment.
Property
Description
WpsContextRoot
The context root or base URI. All URLs beginning with this path will
be reserved for Workplace Collaboration Services. The value of this
property is part of the URL that is used to access Workplace
Collaboration Services from a browser. Example:
http://hostname.domain.com:9081/lwp/workplace
WpsDefaultHome
The default Workplace Collaboration Services page. This is the page
for users who are not logged in. The value of this property is part of
the URL that is used to access Workplace Collaboration Services from
a browser. Example:
http://hostname.domain.com:9081/lwp/workplace
WpsPersonalizedHome
The home page for users who have already logged in to the portal.
This page cannot be accessed by anonymous users. The value of this
property is part of the URL that is used to access Workplace
Collaboration Services from a browser. Example:
http://hostname.domain.com:9081/lwp/myworkplace
PortalAdminId
PortalAdminPwd
The user name of the IBM WebSphere Portal administrator.
The password of the WebSphere Portal administrator.
WasUserid
The user ID for IBM WebSphere Application Server security
authentication.
WasPassword
The password for WebSphere Application Server security
authentication.
DbUrl
The database URL used to access the wps50 database with JDBC.
DbUser
The database user name.
DbPassword
The database user’s password.
DbDriver
The Java class name for the JDBC provider that WebSphere Portal
uses to communicate with its databases.
DbLibrary
The fully qualified directory path name where the classes for the
JDBC provider are located.
4. Save and close the file.
5. Open a command prompt window and navigate to
<iwp_root>/PortalServer/config.
6. Enter the following commands to configure the Workplace Collaboration
Services address:
IBM AIX, Linux, and Sun Solaris
./WPSconfig.sh modify-context-root
Microsoft Windows
WPSconfig.bat modify-context-root
Appendix B Completing Optional Post-installation Tasks
405
Note: Check the output for any error messages before proceeding with the next
task. If any of the configuration tasks fail, verify the values in the
wpconfig.properties file.
7. Start Workplace Collaboration Services as described in the topic, ″Starting
Workplace Collaboration Services.″
You have now successfully changed the Workplace Collaboration Services context
root. Verify that the new context root is valid by typing the new Web address in a
browser, using the following format:
http://<hostname.domain.com>:<port_number>/<WpsContextRoot>/
<WpsDefaultHome> or <WpsPersonalizedHome>
For example, if you performed the previous steps using the sample values, the
resulting Web address for Workplace Collaboration Services would be:
http://<hostname.domain.com>:<port_number>/home/ibm
The personalized Web address for users who are logged in would be:
http://<hostname.domain.com>:<port_number>/home/myibm
If you are using an external Web server with WebSphere Application Server, you
must regenerate the Web server plug-in settings after modifying the Workplace
Collaboration Services context root.
406
Installation and Upgrade Guide
Appendix C Reference Information
This appendix contains reference information related to installing and setting up
IBM Workplace Collaboration Services.
Reference information
This following topics contain information that you might want to refer to during or
after installation.
v Root installation directories
v Installation logs
v Installed folders
v Port assignments on IBM i5/OS
v Related product information
Root installation directories
The default installation directories for the products used with IBM Workplace
Collaboration Services are as follows.
Installation Root for IBM Workplace Collaboration Services
<install_root>
IBM AIX, Linux, and Sun Solaris
/opt/IBM/Workplace
Microsoft Windows
[drive]:\Program Files\IBM\Workplace
IBM i5/OS
/QIBM/UserData/WebAS5/Base/<instance>
where <instance> is the name of your IBM Workplace Collaboration Services
instance.
Workplace Collaboration Services <iwp_root>
IBM AIX, Linux, and Sun Solaris
/opt/IBM/Workplace/WorkplaceServer
Microsoft Windows
[drive]:\Program Files\IBM\Workplace\WorkplaceServer
IBM i5/OS
/QIBM/UserData/WebAS5/Base/<instance>/WorkplaceServer
where <instance> is the name of your IBM Workplace Collaboration Services
instance.
© Copyright IBM Corp. 2002, 2005
407
WebSphere Application Server <was_root>
AIX, Linux, and Solaris
/opt/IBM/Workplace/AppServer
Windows
[drive]:\Program Files\IBM\Workplace\AppServer
i5/OS
/QIBM/UserData/WebAS5/Base/<instance>
where <instance> is the name of your Workplace Collaboration Services instance
WebSphere Portal Server <wp_root>
AIX, Linux, and Solaris
/opt/IBM/Workplace/PortalServer
Windows
[drive]:\Program Files\IBM\Workplace\PortalServer
i5/OS
/QIBM/UserData/WebAS5/Base/<instance>/PortalServer
where <instance> is the name of your Workplace Collaboration Services instance
IBM HTTP Server <ihs_root>
AIX, Linux, and Solaris
/opt/IHS
Windows
[drive]:\Program Files\IBM HTTP Server 2.0
i5/OS
/www/<instance>
where <instance> is the name of the IBM HTTP Server instance.
Installation logs
The IBM Workplace Collaboration Services installation program records
information in a log file about the installation and configuration tasks it performs.
This file is created in the log subdirectory of the Workplace Collaboration Services
program directory that you selected during installation. On IBM AIX, Linux, Sun
Solaris, and Microsoft Windows, the log file is created in the following location:
IBM AIX
<install_root>/WorkplaceServer/log
Linux
<install_root>/WorkplaceServer/log
Sun Solaris
408
Installation and Upgrade Guide
<install_root>/WorkplaceServer/log
Microsoft Windows
c:\<nstall_root>\WorkplaceServer\log
Log file name
The following log file is created:
v lwpinstalllog.txt - This file contains installation information, in English only.
Open the log file using any text editor. Each log entry begins with the date and
time of an action.
Installation logs on i5/OS
On IBM i5/OS, the IBM Workplace Collaboration Services installation program
creates two log files - one for product installation, and one for instance
configuration. The log files are:
v productInstalllog.txt - This file contains product installation information, in
English only. You can find it in the following directory:
/tmp/Installshield/lwai
v lwpinstalllog.txt - This file contains instance configuration information, in
English only. You can find it in the following directory:
<install_root>/WorkplaceServer/log
Installed folders
This section describes the installed folders on an IBM Workplace Collaboration
Services server that includes IBM Workplace Collaborative Learning.
IBM Workplace Home (in the<iwp_root> directory)
Folder
Description
_jvm
ant
bin
cloudscape
IBM Cloudscape database
config
Configuration scripts and files for LDAP and
Database configuration
doc
Folder for standalone documentation, such
as the IBM Workplace Collaboration Services
information center and the Installation
Guide
install
Configuration scripts and files for IBM
WebSphere Deployment Manager
installations
java
Learning/help
Folder for the Collaborative Learning guides
Learning/lms-juru
Collaborative Learning Juru index files
license
License files
log
Installation log files, installation and
uninstallation response files
Appendix C Reference Information
409
Folder
Description
lwp_ext
Workplace Collaboration Services extension
libraries
lwp_lib
Workplace Collaboration Services shared
libraries
properties
Workplace Collaboration Services property
files
qfilestore
Folder for storing mail messages prior to
delivery
registryTools
security
sip_ext
Workplace Collaboration Services libraries
spamdata
tools
uninstall
Uninstallation files
upgrade
wpcpresource
WebSphere Application Server Home (in the<was_root> directory)
Folder
bin
classes
installableApps
lib
updates
IBM WebSphere Portal Server Home (in the<wp_root> directory)
Folder
installableApps
shared
update
wmm
410
Installation and Upgrade Guide
Port assignments on IBM i5/OS
Table 2. WebSphere Application Server and IBM Workplace Collaboration Services ports.
This table shows the WebSphere Application Server and Workplace Collaboration Services
internal port assignments as an offset to the base port specified for use with Workplace
Collaboration Services. These ports are bound non-specific.
To determine the specific port number, add the number listed in the table below to the base
port number you specified when configuring Workplace Collaboration Services. For
example, if the base port number for your Workplace Collaboration Services instance is
30000, the Internal HTTP port would be 30009.
Offset from base
port number
Application server
Description
0
WebSphere_Portal
Name service port
1
WebSphere_Portal
SOAP service port
2
WebSphere_Portal
Data replication service client port
3
WebSphere_Portal
Internal Java Message Service server port
4
WebSphere_Portal
Queued Java Message Service server port
5
WebSphere_Portal
Direct Java Message Service server port
6
WebSphere_Portal
SAS SSL server authentication listener port
7
WebSphere_Portal
CSIV2 server authentication listener port
8
WebSphere_Portal
CSIV2 mutual authentication listener port
9
WebSphere_Portal
Internal HTTP port
10
WebSphere_Portal
Administrative console port
11
WebSphere_Portal
Administrative console SSL-enabled port
12
WebSphere_Portal
Internal HTTP SSL-enabled port
13
Server1
Name service port
14
Server1
SOAP port
15
Server1
Data replication service client port
16
Server1
Internal Java Message Service server port
17
Server1
Queued Java Message Service server port
18
Server1
Direct Java Message Service server port
19
Server1
SAS SSL server authentication listener port
20
Server1
CSIV2 server authentication listener port
21
Server1
CSIV2 mutual authentication listener port
22
Server1
Internal HTTP port
23
Server1
Internal HTTP SSL-enabled port
24
Server1
Administrative console port
25
Server1
Administrative console SSL-enabled port
26
SIP
SIP container TCP port
27
SIP
SIP container TLS port
28
MTA
Name service port
29
MTA
SOAP port
Appendix C Reference Information
411
Table 2. WebSphere Application Server and IBM Workplace Collaboration Services
ports (continued).
This table shows the WebSphere Application Server and Workplace Collaboration Services
internal port assignments as an offset to the base port specified for use with Workplace
Collaboration Services. These ports are bound non-specific.
To determine the specific port number, add the number listed in the table below to the base
port number you specified when configuring Workplace Collaboration Services. For
example, if the base port number for your Workplace Collaboration Services instance is
30000, the Internal HTTP port would be 30009.
30
MTA
Data replication service client port
31
MTA
CSIV2 mutual authentication listener port
33
MTA
Internal HTTP port
34
MTA
Internal HTTP SSL-enabled port
35
MTA
Administrative console port
36
MTA
Administrative console SSL-enabled port
37
MTA
Spam filter classification port
38
MTA
Spam filter learning port
39
SIP
Name service port
40
SIP
SOAP port
41
SIP
Data replication service client port
42
SIP
SAS SSL server authentication listener port
43
SIP
CSIV2 server authentication listener port
44
SIP
CSIV2 mutual authentication listener port
45
SIP
Internal HTTP port
46
SIP
Internal HTTP SSL-enabled port
47
SIP
Administrative console port
48
SIP
Administrative console SSL-enabled port
50
SIP
IMA proxy port
51
MTA
Spam filter classification port
52
MTA
Spam filter learning port
53
WebSphere_Portal
DMAP unicast port
Table 3. Other ports
Offset from base
port number
Application Server
Description
49
IBM Cloudscape
Cloudscape network server
Table 4. Other IBM Workplace Collaboration Services ports.
This table shows the other port assignments used by Workplace Collaboration Services. All
of these ports are bound to a specific IP address unless otherwise noted.
412
Port number
Application Server
Description
25
MTA
SMTP
110
MTA
POP3
Installation and Upgrade Guide
Table 4. Other IBM Workplace Collaboration Services ports (continued).
This table shows the other port assignments used by Workplace Collaboration Services. All
of these ports are bound to a specific IP address unless otherwise noted.
143
MTA
IMAP
465
MTA
SMTP SSL
993
MTA
IMAP SSL
995
MTA
POP3 SSL
5060
SIP
SIP TCP
5061
SIP
SIP TLS
8080
SIP
HTTP Tunnel
8081
SIP
HTTP Tunnel SSL
Related concepts
Reference information
Related product information
Refer to the following sources for additional product information.
IBM Workplace Collaboration Services Release Notes
The Release Notes describe known limitations, problems, workarounds,
hardware and software requirements, supported hardware and software
versions, and capacity planning for this release of Workplace Collaboration
Services.
For the latest version of the Release Notes, go to
http://www.lotus.com/doc.
IBM WebSphere Administrative Console documentation
One of the ways you can configure Workplace Collaboration Services is by
specifying settings in the WebSphere Administrative Console. For
administrative console help, open the console and click the ″i″ icon next to
the setting.
IBM WebSphere Application Server Information Center
The WebSphere Application Server Enterprise Information Center provides
information on WebSphere Application Server, security, and Network
Deployments. HTML or PDF versions of the WebSphere Application Server
Information Center are on the Web at
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp. (The Version
5 Information Center includes information on the 5.0, 5.0.1, and 5.0.2
versions.)
IBM WebSphere Portal Information Center
The WebSphere Portal for Multiplatforms Version 5.0 Information Center
provides information on WebSphere Portal, including security; WebSphere
Member Manager; and portlet management. HTML or PDF versions of the
WebSphere Portal for Multiplatforms Information Center are on the Web at:
http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html.
IBM DB2 Universal Database Information Center
The DB2 Version 8 Information Center provides information on DB2
products, including installing and using DB2 servers and DB2 clients. The
HTML or PDF versions are on the Web at http://www-306.ibm.com/cgibin/db2www/data/db2/udb/winos2unix/support/v8pubs.d2w/en_main.
Appendix C Reference Information
413
IBM HTTP Server Information Center
The IBM HTTP Server Information Center provides information on using
the IBM HTTP Server to handle client HTTP requests. HTML or PDF
versions of the HTTP Server Information Center are on the Web at:
http://www-306.ibm.com/software/webservers/httpservers/library.
IBM Directory Server documentation
The IBM Directory Server 5.2 documentation provides information on
deploying the IBM Directory Server as an LDAP server. The
documentation is on the Web at:
http://publib.boulder.ibm.com/tividd/td/IBMDirectoryServer5.2.html.
IBM Lotus Domino documentation
Workplace Collaboration Services works with a Lotus Domino 6.5 LDAP
server. For information on configuring an LDAP server on Domino, see the
Lotus Domino documentation and Release Notes at
http://www.lotus.com/doc.
IBM Workplace Collaborative Learning Help
IBM Workplace Collaboration Services includes Collaborative Learning
Help, which is installed during the product installation as part of
Collaborative Learning. The Collaborative Learning Help includes:
Student Help -- Provides information on how to use the Student interface
to log in, enroll in a course, display and complete course activities, and
view student progress reports.
Course Administration Help -- Provides information on how to use the
Administrator interface to add users and courses to the system, create
course offerings, and track student progress.
Authoring Tool Help -- Provides information on how to use the authoring
tool to create and manage course content.
This help is accessed from the Help button on the Student and
Administrator user interfaces when you log in to the Collaborative
Learning ″Learning Server.″ Besides being able to access Collaborative
Learning features with the Collaborative Learning portlets, students and
administrators can also access the Learning Server Student and
Administrator user interfaces by logging in directly to the Learning Server
with a supported browser. The Web address, user name, and password are
provided during installation. The user name and password are the same
ones that are used for accessing Workplace Collaboration Services.
Accessing Collaborative Learning directly from the Learning Server gives
you access to additional features not provided by the Collaborative
Learning portlets.
The installation program installs these files in the
<iwp_root>\Learning\help directory.
IBM Workplace Collaborative Learning Guides
Collaborative Learning includes the following guides in PDF file format:
Administrator’s Guide -- Explains system administrator and course
administrator tasks.
Content Guide -- Explains how to integrate course content into
Collaborative Learning.
Customization Guide -- Explains how to customize the Collaborative
Learning user interface and functionality.
414
Installation and Upgrade Guide
Authoring Tool Guide -- Explains how to use the Collaborative Learning
Authoring Tool to create course content for Collaborative Learning. This
guide is included in the AuthoringToolGuide.zip file that is installed on the
server when you choose the authoring tool utility when running the
Collaborative Learning Client Installer.
Database Architecture Guide -- Explains the database schema used with
Collaborative Learning.
The installation program installs these files in the
<iwp_root>\Learning\help directory.
To obtain updates of this documentation, go to
http://www.lotus.com/doc.
IBM Workplace Collaborative Learning API and Web Services Documentation
This documentation describes how to use the Application Programming
Interface (API), which provides developers with access to many features of
Collaborative Learning. It uses the Simple Object Access Protocol (SOAP)
to provide access to Collaborative Learning from any system that supports
HTTP, and it supports many different programming languages.
The installation program installs these files in the
<iwp_root>\Learning\help directory.
Related concepts
Reference information
Appendix C Reference Information
415
416
Installation and Upgrade Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2002, 2005
417
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Office 4360
One Rogers Street
Cambridge, MA 02142
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
IBM, the IBM logo, AIX, Cloudscape, DB2, DB2 Universal Database,
Domino, Domino Designer, Everyplace, i5/OS, iSeries, Lotus,
Lotus Notes, Notes, OS/400, POWER, POWER4+, Tivoli, WebSphere,
Workplace, Workplace Client Technology, Workplace Collaborative Learning,
Workplace Documents, Workplace Managed Client,Workplace Messaging,
Workplace Team Collaboration and Workplace Web Content Management
Intel and Pentium are trademarks of Intel Corporation in the United States, other
countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
418
Installation and Upgrade Guide
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of
others.
Notices
419
420
Installation and Upgrade Guide
Part Number: BU00MML
Program Number: 5724-L21
G210-1961-00
(1P) P/N: BU00MML
Printed in USA
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement