Enable users to publish file attachments to Lotus Quickr

Home

Enable users to publish file attachments to Lotus Quickr

Overview

Edit the configuration property settings of Activities to allow users to publish file attachments from an activity to an IBM Lotus Quickr library.
Before you can complete this procedure...

Have Lotus Quickr deployed in the environment
Know the fully qualified domain names of all the Lotus Quickr servers to publish to.
Decide which type of authentication to use between the Activities and Lotus Quickr servers

Single sign-on By default, the Activities feature assumes that SSO is configured between the Activities server and the Lotus Quickr servers. As a result, when Activities users select the Lotus Quickr servers that they want to publish file attachments to, they are not prompted for user names and passwords. To support this functionality, first enable SSO with Lotus Quickr.
Basic authentication If for some reason you do not want to or cannot set up SSO between the Activities and Lotus Quickr servers, Activities users are prompted for a user name and password when they try to publish file attachment to Lotus Quickr. To ensure that those credentials are not sent unprotected over HTTP...

Configure LC to force traffic on the Activities server to be sent over a secure channel.
Specify HTTPS as the protocol for the servers

To edit configuration files, use wsadmin. See Start the wsadmin client for details.

Enable users to publish file attachments from Activities to Lotus Quickr
Use wsadmin to access and check out the Activities configuration files.
Access the Activities configuration file:

Stand-alone deployment:
execfile("activitiesAdmin.py")

Network deployment:
execfile("profile_root/config/bin_lc_admin/activitiesAdmin.py")

If prompted to specify which server to connect to, type 1.
The information about which server to connect to is only used by wsadmin when you are running administrative commands to collect statistics.
Check out the Activities configuration files...
ActivitiesConfigService.checkOutConfig("<working_directory>",
"cell_name")
where:

<working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

Stand-alone deployment: From the file system...
WAS_HOME\profiles\profile_name\config\cells\

Network deployment: From wsadmin...
print AdminControl.getCell()

For example:
AIX/Linux:
ActivitiesConfigService.checkOutConfig("/opt/act/temp","foo01Cell01")
Microsoft Windows:
ActivitiesConfigService.checkOutConfig("c:/act/temp","foo01Cell01")
From the temporary directory to which you checked out the Activities configuration file, open the oa-config.xml file in a text editor.
Set the enabled attribute of the <PublishFile> element to true.
Create one <server> element for each Lotus Quickr server that you want to support. In the server element, specify the fully qualified domain name of the Lotus Quickr server that you want to allow your users to publish files to. Include the port number. For example:
<PublishFile enabled="true" allowCustomServers="false" requireSSO="true">
      <server>http://quickr.acme.com:8085</server>
      <server>http://quickr.southwest.acme.com:8080</server>
</PublishFile>
If you are not setting up single sign-on between the Activities and Lotus Quickr servers, specify the servers using the HTTPS protocol. For example:
<PublishFile enabled="true" allowCustomServers="false" requireSSO="false">
      <server>https://quickr.acme.com:8085</server>
      <server>https://quickr.southwest.acme.com:8080</server>
</PublishFile>
The first server that you specify in the list becomes the default server that is displayed in the Server field in the dialog box from which the user selects the Lotus Quickr library to which to publish a file. If a user selects a different Lotus Quickr server from the Server field, that server becomes the default.
If, instead of specifying a finite list of servers that users can save files to, you want users to be able to save files to any Lotus Quickr server hosted within a specific domain, set the allowCustomServers attribute to true .
For example:
<PublishFile enabled="true" allowCustomServers="true" requireSSO="true">
</PublishFile>
Perform this step only if you are setting up SSO between the Activities and Lotus Quickr servers. Keeping the value of this attribute set to false prevents users from typing in server names that specify the HTTP protocol instead of HTTPS.
If you decide to not set up SSO between the Activities and Lotus Quickr servers, change the value of the requireSSO attribute to false.
For example:
<PublishFile enabled="true" 
    allowCustomServers="false" 
    requireSSO="false">

    <server>https://quickr.acme.com:8085</server>
    <server>https://quickr.southwest.acme.com:8080</server>

</PublishFile>
When you make this change, perform the steps necessary to force the Activities server traffic to be sent over SSL.
Save and close the oa-config.xml file.
After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes for details.
Integrate Activities with IBM Lotus Quickr

Next topic:
Define a list of supported Lotus Quickr servers

Related tasks

Checking out the Activities configuration files
Apply property changes
Enable single sign-on for Lotus Quickr
Forcing traffic to be sent over SSL

+
Search Tips | Advanced Search