Install the non-English version of the SharePoint widget for Communities 

Install the Microsoft™ SharePoint widget so that Community owners can make it available for members to use in languages other than English.


Before starting


Note: This widget requires that you install the IBM Connections plug-in for Microsoft SharePoint before you use the widget.

Before starting, familiarize yourself with how to install widgets for the Communities application. For details, see this topic: Enable custom widgets for Communities. To enable the widget for languages other than English, you should also be familiar with enabling custom strings for widgets, described in this topic: Add custom strings for widgets and other specified scenarios.


About this task


Enable the language strings so that the widget can display in languages other than English, then install the SharePoint widget so that community owners can make the widget available in a community. Community members can then upload and share documents from a SharePoint server.


Procedure

  1. Follow the steps for adding a resource bundle to the LotusConnections-config.xml file, documented in the topic Add custom strings for widgets and other specified scenarios.

    1. Extract spwidgets.files_res.zip and copy the spwidgets_res file to a resources directory.

    2. Check out the LotusConnections-config.xml file.

    3. Add the following line of code into the <resources> element block to register the resource bundle for the SharePoint widget: 

        <resources>
        <widgetBundle prefix="spwidgets_res" name="com.ibm.connections.sp.files.resources"/> </resources>

    4. Check in the LotusConnections-config.xml file.

  2. Follow the steps for checking out the widgets-config.xml, described in the topic Enable custom widgets for Communities.

    1. Add the xml definition for the SharePoint widget to the Communities section of the widgets-config.xml: 

        <widgetDef defId="SharePointFiles" description="SharePointFilesDesc"
        bundleRefId="spwidgets_res" modes="edit view search fullpage" uniqueInstance="true" url="/SPWidgets/SPFiles/SPFiles.xml?version={version}" helpLink="Using_the_SharePoint_widget_lc3" iconUrl="/SPWidgets/SPFiles/images/spSite.png"> </widgetDef>

    2. Check in the widgets-config.xml file as documented in the custom widgets topic.

  3. Install the SharePoint widget ear file on the same server as the Communities application, as follows:

    1. Log in to the WAS console.

    2. Select Install New Application and browse for the name of the SharePoint ear file you downloaded from the IBM Connections catalog web site:

      .

    3. Accept the installation defaults, but select the server or servers where the Communities application is installed. Accept the installation defaults, but select the server or servers where the Communities application is installed. If you are using an IHS server, select that as well or you will not be able to access the SharePoint widget after you install it.

    4. Save the configuration changes.

        A confirmation screen confirms that the application SharePointContent is installed.

    5. Select Applications -> Enterprise Applications and start the application SharePointContent.

  4. Restart the Communities application.

      Note:

      If your SharePoint Server and IBM Connections hosting the Communities application are not in the same domain, add the domain of the SharePoint server to the DNS settings of the IBM Connections server. Otherwise, your users are presented with an error when trying to create a new community on a server with the SharePoint widget deployed.

  5. If IBM Connections is configured to use single sign-on with IBM Tivoli Access Manager, configure a transparent path junction for the Sharepoint widget if you want to get Sharepoint documents in Connections communities under TAM. Follow the steps for configuring a transparent path junction in the topic Enable single sign-on for Tivoli Access Manager. Run this server task to enable the TAM junction: 

      'server task <WebSEAL-instance-name> create -t ssl -h <backend-server-name> -x -p <backend-server-port> -i -b ignore -f -A -2 -F <ltpa-token> -Z <ltpa-password> /SPWidgets'

  6. If IBM Connections is configured to use a reverse proxy that directs all IBM Connections traffic to a single server, add some mapping rules so that the widget will be accessible.

    1. Refer to the topic Configure a reverse caching proxy for instructions on adding mapping rules.

    2. In the Mapping Rules section, add the following reverse pass rules for the SharePoint widget: 

        ReversePass http://<httpserver>/SPWidgets* http://<proxyserver>/SPWidgets*
        ReversePass https://<httpserver>/SPWidgets* https://<proxyserver>/SPWidgets*

        where <httpserver> is the host name of the HTTP server. The HTTP server is usually IBM HTTP Server, but could be a load balancer or another proxy, depending on your deployment. <proxyserver> is the host name of the proxy server.


What to do next


Once the SharePoint widget is available for the Communities application, a community owner can click the Community Actions button for the community and add the SharePoint widget to the community from the widget panel.

For information on enabling languages, see the topic Enable users to set a language preference.


Parent topic

IBM Connections Widget for Microsoft SharePoint

Related tasks
Enable custom widgets for Communities
Add custom strings for widgets and other specified scenarios
Enable users to set a language preference

+

Search Tips   |   Advanced Search