Before deploying the managed client you
need to setup your Workplace server so that it uses an external HTTP server.
Setting up the Domino server to provide services for Workplace is actually
fairly easy. For my test environment my Domino server is running on the
same server as the workplace server but the you can use the same proceedure
for remote HTTP servers, you just need to copy the plugin config file from
the workplace server to the Domino server.  I’m going to concentrate
on the single server option.

The first requirment for using the Domino
server as the workplace HTTP server is that you are using Internet Site
Documents. If your not already using Internet Site Documents on your Domino
server then go ahead and convert them over now.  It’s easy and much
handier for administration.  The only gotcha is the inbound SMTP document
but a quick trip to Chris Linfoot’s entry
on that will help you out.

Once you have your internet site document
sorted out open your HTTP document and go to the configuration tab and
add in the following to the DSAPI Filters section : c:progra~1ibmworkplaceappserverbindomino5_http.dll
This is the path from the default install of Workplace, If you have changed
your paths then change it as required. Make sure you don’t put any spaces
in the path as Domino will think that you have entered two seperate DSAPI
filters.  In the ‘Allowed Methods’ section below turn on everything,
including the WEBDAV option.

Now before restarting the HTTP server
you need to tell Workplace to regenerate the Plugin-cfg.xml file.  Load
up the portal administration site and open the ‘Environment –> Update
Web Server Plugin’ section and then click the OK button, in a few moment
the plugin will be refreshed and then you can restart the Domino HTTP server.
 You should see a message during the restart saying that the Websphere
DSAPI Plugin has loaded successfully.

If everything has worked correctly you
should now be able to access your Workplace server using http://yourserver/lwp/workplace

Next Stage : Installing the Managed
Client.

Integrating the WorkPlace SSO with Domino
is required if you want to surface Domino portlets within the Workplace
environment without forcing the user to login again for each portlet.Setting
up the SSO integration is also one of the easiest steps in getting WorkPlace
and Domino working together.

The first step is to export the ltpa
keys from Workplace. To do this you load up the Workplace Administration
console and go to the security section and then open the ‘Authentication
Mechanisims -> LTPA’ section. Then enter in a path and filename for
where the keys should be exported and click the export button.  One
important point is that this file location is ON THE SERVER not on your
local client so you will need to get the file you have exported and put
it onto your local machine for the next step.

Got the file? Good. Open up your Domino
Directory and go to the server –> Web –> Internet Sites. If your
not using Internet Sites for your http configuration then you should go
to the web configuration view instead.  If you already have a WEB
SSO document then open it for editing and if not then create a new one
( for non internet sites users you create a new WEB SSO configuration document
by opening a server document and selecting the Create Web –> Web SSO
option ).

Fill in the domain name using .domainname.com
( don’t forget the dot infront of it ) and select the Domino servers that
will participate in the SSO config.  Then using the ‘Keys…’ action
menu select the Import option.  Select the file you exported in the
steps above and then enter the password ( this password is specified during
the LDAP changeover that you would have done earlier ).  Once imported
ok save the document and then restart the HTTP server.

Next Stage : Using the Domino HTTP server
to serve the Workplace pages.