Chapter 3. Workplace Managed Client 2.6 on Linux installation and configuration 83
7. The uninstaller pauses for a few minutes while the SCI is uninstalled. When
finished, it displays a successful uninstallation message. Click Finish.
Figure 3-16 SCI uninstaller successful uninstallation message
8. Restart the Workplace Collaboration Services server.
9. If you operate a remote HTTP server, run the uninstaller on the HTTP server.
Repeat steps 1-8, bearing in mind that certain steps might be omitted
because different components are being removed.
3.1.6 Configuring access to the Managed Client and setting policies
One of the most attractive features of the client from an administrator’s point of
view is its centrally-managed deployment model. In this section, we put the
managed into Managed Client.
Perform the following steps:
1. Open a browser at the WebSphere Application Server administrative console.
Note: Even if you do not want or require a sophisticated setup, you must at
least enable the client’s download link on the Workplace welcome page.
84 IBM Workplace Managed Client 2.6 on Linux
2. Navigate to IBM Workplace Software → Users → Manage User Policy.
3. Open the Default User Policy. This is the set of policies for the core set of
Workplace applications. A section of the page appears in Figure 3-17.
Figure 3-17 The default user policy page
4. The most essential setting for Managed Client use is in the Allowed clients
section. Select the Rich client option. Additionally, note that you cannot
disable the browser client.
5. A number of other settings for the core Workplace applications are available
on this page. A full discussion is outside the scope of this book, but here are
some of the more important policies:
– Allow mail enables or disables mail. Similar options exist for the calendar
and address book.
– Allow import/export of files sets whether users can import and export to
and from the file system into document libraries.
– Allow Workplace Designer gives access to the Workplace Designer tool.
– Allow Notes Application plug-in grants access to the Managed Client
Notes plug-in. Note that at the time of writing, the Notes plug-in for Linux is
in a late-beta stage of development.
Tip: The URL to the console is generally of the form
isv4.cam.itso.ibm.com is the fully qualified domain name of your
WebSphere server. Log in as the administrator.
Chapter 3. Workplace Managed Client 2.6 on Linux installation and configuration 85
6. Click OK to save the user policy.
WebSphere supports the creation of additional user policies. For example, you
might want to roll out the Managed Client to only a few departments.
To achieve this, create a user policy covering only the users in that department.
For example, if rich client access is disabled in the default profile but enabled in
the department’s profile, just that department has access to the rich client.
By combining profiles, almost any configuration is possible. However, a full
discussion of Workplace user policies is outside of the scope of this book.
Configuring access to Managed Client applications
Access to Managed Client applications is controlled chiefly by the policies on
each application’s portal page. This section outlines the basic concepts;
however, a full description of portal security is outside of the scope of this book.
We simply outline how you can apply portal security concepts to Managed Client
Important: We do configure policies for access to individual Managed Client
applications in the WebSphere administration console. For that functionality,
see the following section.
Tip: Access to any portal application is also governed by the policies on its
portal page. The Managed Client shares exactly the same access control
86 IBM Workplace Managed Client 2.6 on Linux
Perform the following steps:
1. Using a browser, log in to Workplace as the WebSphere Portal administrator.
Click the Administration link at the top of the page. This opens the Portal
administration console, as shown in Figure 3-18.
Figure 3-18 Portal Administration console