68 IBM Workplace Managed Client 2.6 on Linux
3.1.3 The installation process
In this section, we describe how to install the SCI on a non-clustered Workplace
Collaboration Services server with either a local or remote external HTTP server.
The only difference between the two scenarios is that a remote HTTP server
requires you run the SCI twice, each time with slightly different options. We
attempt to make the instructions as simple as possible. However, when following
these instructions, you might skip certain steps depending on whether you are
running the SCI on the Workplace Collaboration Services server or HTTP server.
The SCI is distributed on a pair of CDs. We assume that you are comfortable
with mounting and unmounting CDs in Linux.
Perform the following steps:
1. The installer executable, named setupLinux.bin, is on disk 1 in the top-most
folder. Whether you copied the CD contents to your disk or are working
directly from CD, run the installer now by either double-clicking its icon in a file
manager or entering its full path into a terminal.
Important: Owing to loose coupling between WebSphere and the HTTP
server, the instructions can be easily tailored to any HTTP server.
Note: If you operate a clustered deployment, use this section as a reference,
but consult the information center for full details about the differences between
the procedure for a clustered installation:
For information center documentation about the installation on non-clustered
deployments, see:
Tip: If your server has only one CD drive, it might be prudent to copy the
entire contents of each CD to a temporary location on your server’s hard drive,
for example, disk 1 to /opt/sci/disk2 and disk 2 to /opt/sci/disk2.
Chapter 3. Workplace Managed Client 2.6 on Linux installation and configuration 69
2. First, select a language for the installation process, as shown in Figure 3-1. In
this guide, we select English.
Figure 3-1 Language selection
Tip: The SCI also has a command line mode. Access this using the
-console switch:
./setupLinux.bin -console
This can be useful if, for example, you use Telnet or SSH to access your
Workplace Collaboration Services server or are on a high latency link to
your Workplace Collaboration Services server.
We assume that you use the graphical installer.
Important: Of course, you can run the installer as the root user. However,
it can (and, many UNIX purists argue, should) be run as whatever user has
read/write access to the WebSphere folder.
Whatever the case, it is highly unlikely that the SCI will attempt anything
dangerous if you run it as the superuser.
70 IBM Workplace Managed Client 2.6 on Linux
3. The next dialog box, shown in Figure 3-2, welcomes you to the installer. Click
Figure 3-2 SCI welcome
4. At the dialog box containing the licenses associated with the SCI and its
technologies, if you agree to the license terms, click Next.
Chapter 3. Workplace Managed Client 2.6 on Linux installation and configuration 71
5. Now, the SCI prompts for an installation location (Figure 3-3). Because most
SCI components integrate with WebSphere Portal and the HTTP server, this
leaves only the installation logs and the uninstaller to be placed in this
location. The default value should be OK. Click Next.
Figure 3-3 SCI installation location prompt
72 IBM Workplace Managed Client 2.6 on Linux
6. Select a typical installation or a custom installation, as shown in Figure 3-4. If
you operate a local HTTP server, select Typical, click Next, and proceed to
step 7.
If you operate a remote HTTP server, select Figure 3-4. On the following
page, select only WebSphere Portal content, IBM WebSphere
Everyplace® Device Manager, and IBM Workplace Collaboration
Services Contents. With the appropriate components selected, click Next.
Figure 3-4 Typical or Custom installation selection

Get IBM Workplace Managed Client 2.6 on Linux now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.