Integrate your business

  1. Install plug-ins to use Connections in other applications

  2. Install plug-ins to use other applications in Connections

  3. Use plug-ins from Connections in other products

  4. Use plug-ins from other products with Connections

Integrate with other products

Extend Connections to work with the following products:

    Connections Plug-in for IBM Notes
    Access Connections content from within your IBM Notes client. This combined plug-in installs sidebar applications so that you can access and interact with activities, status updates, and files without leaving your Notes client.

    Connections Portlets for IBM WebSphere Portal
    Use the Connections portlets to bring the collaborative power of Blogs, Activities, Bookmarks, Profiles, Wikis and Tags to your WebSphere Portal environment.

    Connections Desktop Plug-ins for Microsoft Office and Microsoft Windows
    Use the Connections Plug-in for Microsoft Office and Microsoft Windows to integrate your collaboration tools. You can post mail messages to activities or get the benefit of Profiles in your Outlook client. Bring capabilities of the Activities, Blogs, and Profiles applications to your office applications, such as Microsoft Word, and add files from Windows Explorer to an activity in seconds. Use the Microsoft Outlook Social Connector to interact with your Connections network.

    Connections Plug-in for Microsoft SharePoint
    Use the Connections Plug-in for Microsoft SharePoint to integrate Connections collaboration services with Microsoft SharePoint.

Use these other products from within Connections:

    Connections Widget for Microsoft SharePoint
    Use the Connections Widget for Microsoft SharePoint to access Microsoft SharePoint documents from a community.

    IBM Lotus Quickr
    Use the Connections Connector for Quickr to integrate Lotus Quickr places with communities. Community members can use different types of Lotus Quickr places to organize and share project files, post comments to a blog, and work collaboratively on team documents.

Install Connections before attempting to install and use the plug-ins. The plug-ins rely on the functionality of the applications provided in the Connections application.

  • Do not configure Connections to prevent email addresses from being displayed. If you hide email addresses, the extensions will not function, with the exception of the Connections Portlets for IBM WebSphere Portal and the connectors for Communities. Connections Connector for Quickr can be installed and will function in an Connections deployment that is configured to prevent email addresses from being displayed:


    Install plug-ins to use Connections in other applications

    You can access your Connections data from within other products by adding plug-ins to those other products.


    Connections Portlets for WebSphere Portal

    Install this package makes the following portlets available to your portal users:

    Activities Collaboration tool for collecting, organizing, sharing, and reusing work related to a project goal.
    Activity Stream Integration portlet that lets you monitor and interact with people and content that you are following.
    Blogs Online journals you can use to deliver timely information with a personal touch.
    Bookmarks Social bookmarking tool used to save, organize, and share Internet and intranet bookmarks.
    Tags Meaningful keywords you can use to find associated content.
    Profiles Directory of colleagues you can use to build a network and locate expertise.
    Wikis Repository for sharing and collaborating on pages of interest to your group.
    Forums View and contribute to discussion topics.
    Community View basic community information like the description, tags, and community owners. Perform basic community actions from the portlet.
    Blogs Summary Choose a view to see a snapshot of recent, latest, or featured blog activity
    Profiles Summary View a summary of information about your colleagues.
    Forums Summary View a list of forums that you can access.
    Bookmarks Summary View a list of bookmarks you can access.

    You can also deploy community pages, which are portal pages associated with communities from Connections communities. Portlets on community pages are automatically scoped to the community membership and display content from the community in the portlets.

    For example, if your community contains a forum, adding the forum portlet to a community page lets portal users view and interact with the forum content from a Portal application.

    Uninstall any previous versions of the portlets before you install. Upgrading from previous versions is not supported.


    What's New in the Connections Portlets for WebSphere Portal

    This release of Connections Portlets for WebSphere Portal includes some new and updated features.

    These features are new in this release:

    • An Activity Stream portlet that lets you post, view, and interact with updates in Connections when in a single sign-on environment.

    • Updates to Blogs portlet to support Ideation Blog on community pages in Portal.

    • Support for Connections 4.5 servers.


    Deploy the Connections Portlets

    Deploy the Connections to bring social business to your portal applications.

    Follow these instructions to install, configure, and deploy the Connections portlets for IBM WebSphere Portal.

    If you plan to deploy Connections portlets on anonymous pages that do not require authentication, find out more in the article Use IBM WebSphere Portlet Factory portlets in an anonymous IBM WebSphere Portal page in the IBM Web Experiences wiki. Follow the steps for setting up anonymous access in the Enable session IDs for anonymous users article from the IBM WebSphere Portal wiki.

    Restriction: In order to use common directory services, Portal must be configured to use a federated LDAP. Use of a stand-alone LDAP is not supported.


    Update from a previous release

    If you are installing from a previous release where you installed the Portal application archive (PAA) with the Portal Solutions Installer, update the installation to get the newest features. This installation method was available starting with the Connections Portlets for WebSphere Portal version 3.0.1.1 Refresh. If you installed a previous version of the Connections portlets using the manual installation, you cannot update the installation. You must uninstall the portlets and then reinstall using the complete installation steps.

    1. If you installed the Communities VMM Adapter to integrate Community membership, execute:
      ConfigEngine remove-SNPortletsVMM \
          -DWasPassword=[was-admin-password] \
          -DPortalAdminPwd=[portal-admin-password]

    2. Run the following commend:
      ConfigEngine uninstall-paa \
          -DappName=SNPortlets \
          -DforceUninstall=true \
          -DWasPassword= [was-admin-pwd] \
          -DPaaRootPath= [paa-install-root] \
          -DPortalAdminPwd= [portal-admin-pwd]

    3. Do one of the following:

      • If you are uninstalling on WebSphere Portal 7.0.0.2, manually delete the Connections Portlets assembly directory, SNPortlets, from the [paa-install-root] folder.

      • If you are uninstalling on WebSphere Portal 8, execute the following command to delete the Connections Portlets assembly files from the [paa-install-root] folder:
        ConfigEngine delete-paa \
            -DassemblyList=SNPortlets \
            -DWasPassword= [was-admin-pwd] \
            -DPortalAdminPwd= [portal-admin-pwd]

        Check to make sure the SNPortlets directory has been deleted from the [paa-install-root] folder. If you get a message that files are being used by another application or are unable to delete the SNPortlets directory, stop WebSphere Portal and manually delete the SNPortlets directory.

    4. Restart WebSphere Portal.
    5. Follow the instructions in Installing the Connections Portlets for WebSphere Portal to install the new version of the Connections Portlets.

    6. If you have the Search Integration configure, follow the instructions in the prerequisites section of Deploying search integration to update the search prerequisites.

    7. If you installed the Communities VMM Adapter to integrate Community membership, execute the command in step 1 of Configuring the Connections repository for VMM to reconfigure the Communities VMM Adapter.


    Import a certificate to support SSL

    Import a certificate so that Connections and WebSphere Portal can communicate over Secure Socket Layer (SSL).

    In order for WebSphere Portal to communicate with Connections over Secure Sockets Layer (SSL), the WebSphere Portal Server must trust the signer of the SSL certificate for Connections. This might be set up by default in your WebSphere infrastructure if you use SSL certificates that are issued by a commonly recognized authority. If you use self-signed certificates, the default certificate or a signer that is not recognized by your WebSphere Portal Server, you must import the SSL certificate from Connections to your WebSphere Portal Server.

    Import the SSL keys into the Portal server as follows:

    1. Log in to WAS admin console.

    2. Navigate to Security > SSL certificate and key management > Key stores and certificates.

    3. Add the certificates to the appropriate truststore as configured in SSL Configurations. To view the SSL configuration and determine the appropriate truststore, navigate to: Security > SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > ['Trust Store Name']

      For example, in a stand-alone deployment you navigate to NodeDefaultTrustStore > Signer certificates for adding certificates. If NodeDefaultSSL Settings points to 'CellDefaultTrustStore', you add a certificate to 'CellDefaultTrustStore'.

    4. Click Retrieve from port.

    5. Enter the host and SSL port that is used by your Connections server. The default SSL port is 443. Give the alias a name, for example, Connections.

      For example:

      Host:  connections.example.com
      Port:  443
      Alias:  connections

    6. Click Retrieve signer information.

    7. Click OK.

    8. Click Save.


    Update the portlet theme

    Update the theme profile for the Connections portlets to functions properly.

    If you are deploying on WebSphere Portal 7.0.0.2, make sure that you deployed the fast theme, as described in the article Install a new theme in the WebSphere Portal wiki.

    By design, the default themes for Portal 7.0.0.2 and Portal 8.0 do not load Dojo in view mode. This helps to render the theme faster. Because the Connections portlets depend on different capabilities, you must use a profile that includes the Dojo capabilities. For the portal default theme, the PAA installer is automatically assigning the "Full" profile. However, that profile includes more capabilities than the portlets need. In order to create a highly optimized setup, the rest of this article describes which dependencies the portlets have and how you can add them to your custom theme profile.

    If you do not add these modules to your theme profile used for the pages that contain the Connections portlets, you can still deploy and configure the Connections portlets on a Portal 7 server, but some features will not work as expected. You can not deploy and configure the Connections portlets on a Portal 8 server. An error warns you that the modules are missing.

    1. Follow the steps in the article Add or removing a ready to use module to a theme to in the WebSphere Portal wiki. Portal 7.0.0.2:

      • wp_liveobject_framework
      • dijit_form_16
      • dijit_theme_tundra_16
      Portal 8.0:

      • wp_liveobject_framework
      • dijit_form_17

      if you are using a custom profile, add the modules to that profile.

    2. Stop and restart the Portal server.

    3. To specify a theme profile at the page level, you can override the default theme.

      For example, if the theme is using the profile_deferred.json profile, you can specify a custom profile for specific portal pages. Follow the steps for Set a profile override on a page in the WebSphere Portal wiki.


    Configure authentication for the portlets

    Set up single sign-on integration between Connections and WebSphere Portal using third-party security products, or configure basic authentication to enable access to the portlets.

    Connections uses single sign-on (SSO) to secure the transfer of user ID and password information used authenticate with the system. With SSO, users can switch to different applications without needing to authenticate again. SSO is automatically enabled when Connections is installed on a single WebSphere Application Server profile or when different profiles are federated into the same cell.

    Configure basic authentication allows the manual entry of user credentials in the personalize mode of the portlets. Basic authentication for the portlets can only be supported if single sign-on is not already enabled between WebSphere Portal and Connections. If single sign-on is enabled (through LTPA, Kerberos or another mechanism), it takes precedence. If single sign-on is enabled, the basic authentication credentials that are entered in the personalize mode of the portlets are ignored.

    Configure single sign-on for users is recommended over using basic authentication for user interactions. If you use basic authentication for the portlets, every user must type in their personal credentials manually in the personalize mode of the portlets or shared credentials can be supplied from the Credential Vault. Basic authentication can be especially useful for trials of the portlets before you have a chance to configure some form of single sign-on, but is not recommended for production use.


    Enable single sign-on for the portlets for a stand-alone LDAP server

    Before you install the Connections Portlets for IBM WebSphere Portal, enable single sign-on (SSO) between Connections and WebSphere Portal.

    This task describes the steps that are required to enable SSO between Connections and WebSphere Portal when they are on different WAS cells. Applications that are deployed on servers within the same WAS cell are enabled by default for SSO.

    Set the realm name in the LTPA token to that of the LDAP server before you export the LTPA token.

    For example, if you connect to an LDAP server at ldapserver.example.com over port 389, then you must set the realm name to ldapserver.example.com:389. If you must change the realm name, see the topic Changing the realm name.

    To allow SSO between Connections and WebSphere Portal...:

    1. On the server where Connections is installed, enable SSO:

      1. Log in to WAS admin console as an administrator, expand Security > Global security.

      2. Expand Web and SIP security and then click Single sign-on (SSO).

      3. Enter the domain name .

        Ensure that the domain name you enter is valid: on the node where WebSphere Portal is installed, log in to WAS admin console as an administrator, click Security > Global security > Web and SIP security > Single sign-on (SSO) and verify that the domain name is present.

    2. On Connections deployment manager node...:

      1. Log in to WAS admin console as an administrator.

      2. Click Security > Global security > LTPA, and then in the Cross-cell single sign-on section, provide values for the following fields:

        • Password – Type a secure password that you will remember. You must provide this password later, when you export the key file

          Confirm the password.

        • Fully qualified key file name – Specify a valid path and a name for the file that stores the exported keys

      3. Click Export keys.

    3. On the node where WebSphere Portal is installed...:

      1. Log in to WAS admin console as an administrator and click Security > Global security > LTPA.

      2. In the General properties section, provide values for the following fields:

        • Password – Type the password that you used for the Connections key file that you exported

          Confirm the password.

        • Fully qualified key file name – Name of the Connections key file that you exported

      3. Click Import keys

    4. Restart all the nodes.


    Configure single sign-on for portlets with TAM and SPNEGO

    Configure Connections portlets to use single sign-on with IBM Tivoli Access Manager and SPNEGO.

    Single sign-on (SSO) enables users to log in to an Connections application and switch to other applications within the product without having to authenticate again.

    There are several different ways to configure SSO. This procedure describes an approach that uses the Kerberos authentication protocol. This authentication method allows Tivoli Access Manager and users web browsers to prove their identities to one another in a secure manner. After users sign in to their Active Directory Windows client systems, they are automatically signed into both Tivoli Access Manager and Connections.

    Configure Connections and WebSphere Portal to share a single Deployment manager saves on administration time by combining administration tasks for the two applications. Establishing a single-sign on environment benefits the users by creating a more seamless environment between the two applications.

    Follow these steps to configure single sign-on.

    1. Before federating Portal as a managed node of the Deployment manager of Connections, make sure the realms match between Connections Deployment manager and Portal. If you must change the realm names so they match, follow the steps in Changing the realm name.

    2. Perform the following steps to collect files from the primary node and copy them to the Deployment manager:

      1. From the <wp_profile_root>/ConfigEngine directory of the primary node, run this task: ConfigEngine.bat collect-files-for-dmgr -DWasPassword=password . This task creates a compressed file containing all the files which must be copied to the Deployment manager. The compressed file, named filesForDmgr.zip, is placed in the <wp_profile_root>/filesForDmgr directory.

      2. Stop the Deployment manager.

      3. Expand each of the files in the filesForDmgr.zip file into the correct location on the Deployment manager based on the directory names within the compressed file.

        The directory names in the compressed file are based on the typical default directory names. The directory that is called AppServer/profiles/Dmgr01 is used to identify the Deployment manager profile root, and the AppServer directory is used to identify the Deployment manager installation root directory. If the Deployment manager was installed into the default directory (AppServer) and the profile was created in the default directory (AppServer/profiles/Dmgr01), then the compressed file can be expanded directly into the directory above the AppServer directory; for example /IBM/WebSphere.

      4. Start the Deployment manager.

    3. To augment a Deployment manager profile, run the following command from the <AppServer_root>/bin directory:
      manageprofiles.bat \
          -augment \
          -templatePath  c:/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment \
          -profileName Dmgr01

    4. Restart the Deployment manager.

    5. Add the same Portal administration group as an administrators group on the Connections Deployment manager.

    6. Run the following command from the <wp_profile_root>/bin directory to federate the primary node:
      addNode.bat DmgrHostname dmgr_port \
          -includeapps \
          -includebuses
      -username was_admin_user
      -password was_admin_password

      For example:

      addNode.bat dmgrhost.cn.ibm.com 8879 \
          -includeapps \
          -includebuses \
          -username adminuser \
          -password adminpwd

    7. On the Portal server, run syncNode.bat and then restart the Deployment manager and all node agents.

    8. To configure the IBM HTTP Server with Single Sign-On, delete and re-add the web server on WAS admin console in order to remap all applications, including Portal, and import the Portal certificate into IBM HTTP Server.
    9. Skip this step if you are deploying on Portal 8. To Configure the same SPNEGO single sign-on for Portal and Connections:

      1. Create user for Portal host server on AD

      2. Create keytab file for Portal server on AD:
        ktpass -out path_to_keytab –princ SPN
          -mapuser account_name -mapOp set –pass account_password
        Where:

        • path_to_keytab is the file path where you want to store the generated keytab file.
        • SPN is the Kerberos service principal name.
        • account_name is the service account name.
        • account_password is the password that is associated with the service account.

        For example:

        ktpass -princ HTTP/portal.cn.ibm.com@cn.ibm.com \
            -out c:\portal.keytab \
            -mapuser portaluser \
            -mapOp set \
            -pass Passw0rd
      3. Merge the portal keytab into the merged Connections keytab by running the ktab command with the following switch:
        -m source_keytab_name destination_keytab_name
        Where:

        • source_keytab_name is the name of the keytab file on the source system.
        • destination_keytab_name is the name of the keytab file on the destination system.

        For example:

        c:\IBM\WebSphere\AppServer\java\jre\bin>ktab.exe \
            -m y:\SPNEGO\portal.keytab y:\SPNEGO\merged.keytab
      4. Recreate the krb5.conf file with the new merged keytab file:
        $AdminTask createKrbConfigFile
          {
          -krbPath appserver\java\jre\lib\security\krb5.conf
          -realm REALM
          -kdcHost kdc_hostname
          -dns dns_hostname
          -keytabPath path_to_keytab
        }

        For example:

        wsadmin.bat -user adminuser -password adminpwd
        $AdminTask createKrbConfigFile {-krbPath y:\SPNEGO\krb5.conf \
            -realm CN.IBM.COM \
            -kdcHost AD.cn.ibm.com \
            -dns cn.ibm.com \
            -keytabPath y:\SPNEGO\merged.keytab}

      5. Enable SPNEGO single sign-on by configuring Kerberos in WAS admin console, following the steps in the Enabling single sign-on for Tivoli Access Manager with SPNEGO topic.

      6. Synchronize the node and restart the Deployment manager node. If you cannot manage the Portal node on WAS admin console, manually synchronize the node and restart the Deployment manager node.
    10. Configure Tivoli Access Manager on the Portal server, following the directions in the article that corresponds to your Portal server: in the IBM WebSphere Portal product wiki.

      For the connections integration with the portlets, it is important that WebSEAL session cookies are sent to the junction server. This can be defined by adding the -k option to the commands that create a junction.

      For example, on Portal 7:

      server task default-webseald-TAMhost.cn.ibm.com create \
          -t ssl \
          -b filter \
          -A \
          -F C:\WASLTPA.key \
          -Z password  \
          -h dmgrhost.cn.ibm.com \
          -c all \
          -f \
          -k \
          -j \
          -J trailer /wpsv70
        ConfigEngine.bat run-svrssl-config \
          -Dwp.ac.impl.PDAdminPwd=password
      ConfigEngine.bat validate-pdadmin-connection \
          -DWasPassword=password \
          -Dwp.ac.impl.PDAdminPwd=password
      ConfigEngine.bat enable-tam-all \
          -DWasPassword=password


    Configure single sign-on with Tivoli Access Manager

    Configure Connections portlets to use single sign-on with IBM Tivoli Access Manager.

    Single sign-on (SSO) enables users to log in to an Connections application and switch to other applications within the product without having to authenticate again.

    There are several different ways to configure SSO. This authentication method allows Tivoli Access Manager and users web browsers to prove their identities to one another in a secure manner.

    Configure Connections and WebSphere Portal to share a single Deployment manager saves on administration time by combining administration tasks for the two applications. Establishing a single-sign on environment benefits the users by creating a more seamless environment between the two applications.

    Follow these steps to configure single sign-on.

    1. Before federating Portal as a managed node of the Deployment manager of Connections, make sure the realms match between Connections Deployment manager and Portal. If you must change the realm names so they match, follow the steps in Changing the realm name.

    2. Perform the following steps to collect files from the primary node and copy them to the Deployment manager:

      1. From the <wp_profile_root>/ConfigEngine directory of the primary node, run this task: ConfigEngine.bat collect-files-for-dmgr -DWasPassword=password . This creates a compressed file containing all the files which must be copied to the Deployment manager. The compressed file, named filesForDmgr.zip, are placed in the <wp_profile_root>/filesForDmgr directory.

      2. Stop the Deployment manager.

      3. Expand each of the files in the filesForDmgr.zip file into the proper location on the Deployment manager based on the directory names within the compressed file. The directory names in the compressed file are based on the typical default directory names. The directory that is called AppServer/profiles/Dmgr01 is used to identify the Deployment manager profile root, and the AppServer directory is used to identify the Deployment manager installation root directory. If the Deployment manager was installed into the default directory (AppServer) and the profile was created in the default directory (AppServer/profiles/Dmgr01), then the compressed file can be expanded directly into the directory above the AppServer directory; for example /IBM/WebSphere.

      4. Start the Deployment manager.

    3. To augment a Deployment manager profile, run the following command from the <AppServer_root>/bin directory:
      manageprofiles.bat -augment \
          -templatePath  c:/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment \
          -profileName Dmgr01

    4. Restart the Deployment manager.

    5. Add the same Portal administration group as an administrators group on the Connections Deployment manager.

    6. Run the following command from the <wp_profile_root>/bin directory to federate the primary node:
      addNode.bat DmgrHostname dmgr_port \
          -includeapps \
          -includebuses
      -username was_admin_user
      -password was_admin_password

      For example:

      addNode.bat dmgrhost.cn.ibm.com 8879 \
          -includeapps \
          -includebuses \
          -username adminuser \
          -password adminpwd

    7. On the Portal server, run syncNode.bat and then restart the Deployment manager and all node agents.

    8. To configure the IBM HTTP Server with Single Sign-On, delete and re-add the webserver on WAS admin console in order to re-map all applications, including Portal, and import the Portal certificate into IBM HTTP Server.
    9. Configure Tivoli Access Manager on the Portal server, following the directions in the article that corresponds to your Portal server: in the IBM WebSphere Portal product wiki.

      For the connections integration with the portlets, it is important that WebSEAL session cookies are sent to the junction server. This can be defined by adding the -k option to the commands that create a junction.

      For example, on Portal 7:

      server task default-webseald-TAMhost.cn.ibm.com create \
          -t ssl \
          -b filter \
          -A \
          -F C:\WASLTPA.key \
          -Z password  \
          -h dmgrhost.cn.ibm.com \
          -c all \
          -f \
          -k \
          -j \
          -J trailer /wpsv70
        ConfigEngine.bat run-svrssl-config -Dwp.ac.impl.PDAdminPwd=password
      ConfigEngine.bat validate-pdadmin-connection \
          -DWasPassword=password \
          -Dwp.ac.impl.PDAdminPwd=password
      ConfigEngine.bat enable-tam-all \
          -DWasPassword=password


    Configure single sign-on for portlets with SiteMinder and SPNEGO

    Configure Connections portlets to use single sign-on with Computer Associates' SiteMinder and SPNEGO.

    1. Enable SiteMinder and SPNEGO for Connections, following the steps in Enabling SiteMinder and SPNEGO.

    2. Enable and configuring single sign-on for HTTP requests using SPNEGO following the steps in this Enable and configuring single sign-on for HTTP requests using SPNEGO.
    3. Configure SiteMinder following the steps in this Configure eTrust SiteMinder.
    4. Merge all the keytab files to make the Deployment manager aware of the SPNs for each node.

      The following example demonstrates the procedure for merging keytab files.

      Assuming that you already created the following keytab files:

      • krb5.keytab on the Deployment manager
      • krb5NodeA.keytab on Node A
      • krb5NodeB.keytab on Node B

      Run the ktab command with the following switch:

      -m source_keytab_name> destination_keytab_name

      where source_keytab_name is the name of the keytab file on the source system and destination_keytab_name> is the name of the keytab file on the destination system.

      Step 1: merge the keytab file on Node A into the keytab file on the Deployment manager:

      # ./ktab -m /etc/krb5NodeA.keytab /etc/krb5.keytab
      Merging keytab files:   source=krb5NodeA.keytab   destination=krb5.keytab
      Done! 

      Step 2: merge the keytab file on Node B into the keytab file on the Deployment manager:

       # ./ktab -m /etc/krb5NodeB.keytab /etc/krb5.keytab
      Merging keytab files:   source=krb5NodeB.keytab   destination=krb5.keytab
      Done! 

      For more information, go to the Use the ktab command to manage the Kerberos keytab file topic in the IBM WebSphere Application Server 8 information center.

    5. Configure the Virtual Member manager (VMM).

      1. If you did not already done so, follow the instructions in Configuring portlets to use common directory services, to copy sonata.services.xml to <wp_root>\config\cells\<cell name>\

      2. Edit sonata.services.xml to use KerberosAuthenticator+ instead of DefaultAuthenticator.

      3. Add all IIS, Portal, and Connections servers SPN as attributes.

      For example:

      <sonataServices name="KerberosAuthenticator+">
        <attribute key="IISKerberosSPN" value="HTTP/wti-iis.spnego1.mul.ie.ibm.com@SPNEGO1.MUL.IE.IBM.COM"/>
        <attribute key="WebKerberosSPN" value="HTTP/dslvm326.spnego1.mul.ie.ibm.com@SPNEGO1.MUL.IE.IBM.COM"/>
        <attribute key="WebKerberosSPN" value="HTTP/dslvm442.spnego1.mul.ie.ibm.com@SPNEGO1.MUL.IE.IBM.COM"/>
        <attribute key="WASKerberosSPN" value="HTTP/dslvm443.spnego1.mul.ie.ibm.com@SPNEGO1.MUL.IE.IBM.COM"/>
        <attribute key="CookieTimeout" value="60"/>
      </sonataServices>


    Configure single sign-on for portlets with SPNEGO

    Configure Connections portlets to use single sign-on with SPNEGO.

    Single sign-on (SSO) enables users to log in to an Connections application and switch to other applications within the product without having to authenticate again.

    There are several different ways to configure SSO. This procedure describes an approach that uses the Kerberos authentication protocol. This authentication method allows users web browsers to prove their identities to one another in a secure manner. After users sign in to their Active Directory Windows client systems, they are automatically signed into Connections.

    Configure Connections and WebSphere Portal to share a single Deployment manager saves on administration time by combining administration tasks for the two applications. Establishing a single-sign on environment benefits the users by creating a more seamless environment between the two applications.

    Follow these steps to configure single sign-on.

    1. Before federating Portal as a managed node of the Deployment manager of Connections, make sure the realms match between Connections Deployment manager and Portal. If you must change the realm names so they match, follow the steps in Changing the realm name.

    2. Perform the following steps to collect files from the primary node and copy them to the Deployment manager:

      1. From the <wp_profile_root>/ConfigEngine directory of the primary node, run this task: ConfigEngine.bat collect-files-for-dmgr -DWasPassword=password. This creates a compressed file containing all the files which must be copied to the Deployment manager. The compressed file, named filesForDmgr.zip, will be placed in the <wp_profile_root>/filesForDmgr directory.

      2. Stop the Deployment manager.

      3. Expand each of the files in the filesForDmgr.zip file into the proper location on the Deployment manager based on the directory names within the compressed file. The directory names in the compressed file are based on the typical default directory names. The directory AppServer/profiles/Dmgr01 is used to identify the Deployment manager profile root, and the AppServer directory is used to identify the Deployment manager installation root directory. If the Deployment manager was installed into the default directory (AppServer) and the profile was created in the default directory (AppServer/profiles/Dmgr01), then the compressed file can be expanded directly into the directory above the AppServer directory; for example /IBM/WebSphere.

      4. Start the Deployment manager.

    3. To augment a Deployment manager profile, run the following command from the <AppServer_root>/bin directory:
      manageprofiles.bat -augment \
          -templatePath  c:/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment \
          -profileName Dmgr01

    4. Restart the Deployment manager.

    5. Add the same Portal administration group as an administrators group on the Connections Deployment manager.

    6. Run the following command from the <wp_profile_root>/bin directory to federate the primary node:
      addNode.bat DmgrHostname dmgr_port \
          -includeapps -includebuses
      -username was_admin_user
      -password was_admin_password

      For example:

      addNode.bat dmgrhost.cn.ibm.com 8879 -includeapps -includebuses -username adminuser -password adminpwd

    7. On the Portal server, run syncNode.bat and then restart the Deployment manager and all node agents.

    8. To configure the IBM HTTP Server with Single Sign-On, delete and re-add the webserver on WAS admin console in order to re-map all applications including Portal, and import the Portal certificate into IBM HTTP Server.

    9. To Configure the same SPNEGO single sign-on for Portal and Connections.

      1. Create user for Portal host server on AD.

      2. Create keytab file for Portal server on AD:
        ktpass -out path_to_keytab –princ SPN
          -mapuser account_name \
            -mapOp set –pass account_password
        Where:

        • path_to_keytab is the file path where you want to store the generated keytab file.
        • SPN is the Kerberos service principal name.
        • account_name is the service account name.
        • account_password is the password that is associated with the service account.

        For example:

        ktpass -princ HTTP/portal.cn.ibm.com@cn.ibm.com \
            -out c:\portal.keytab \
            -mapuser portaluser \
            -mapOp set \
            -pass Passw0rd
      3. Merge the portal keytab into the merged Connections keytab by running the ktab command with the following switch:
        -m source_keytab_name destination_keytab_name
        Where:

        • source_keytab_name is the name of the keytab file on the source system.
        • destination_keytab_name is the name of the keytab file on the destination system.

        For example:

        c:\IBM\WebSphere\AppServer\java\jre\bin>ktab.exe \
            -m y:\SPNEGO\portal.keytab y:\SPNEGO\merged.keytab
      4. Recreate the krb5.conf file using the new merged keytab file:
        $AdminTask createKrbConfigFile
          {
          -krbPath appserver\java\jre\lib\security\krb5.conf
          -realm REALM
          -kdcHost kdc_hostname
          -dns dns_hostname
          -keytabPath path_to_keytab
        }

        For example:

        wsadmin.bat -user adminuser -password adminpwd
        $AdminTask createKrbConfigFile {-krbPath y:\SPNEGO\krb5.conf -realm CN.IBM.COM -kdcHost AD.cn.ibm.com -dns cn.ibm.com -keytabPath y:\SPNEGO\merged.keytab}

      5. Enable SPNEGO single sign-on by configuring Kerberos in WAS admin console, following the steps in the Enabling single sign-on for the Windows desktop topic.

      6. Synchronize the node and restart the Deployment manager node. If you cannot manage the Portal node on WAS admin console, manually synchronize the node and restart the Deployment manager node.


    Change the realm name

    When you configure Connections portlets to use single sign-on, you may need to change the Portal realm name to match the one used in Connections.

    1. In WAS admin console, change the realm name.

      For example, from defaultWIMFileBasedRealm to AD.cn.ibm.com:389.

    2. Configure Portal to use the new realm name as the default realm:

      1. Use a text editor to open the wkplc.properties file, which is located in the <wp_profile_root>/ConfigEngine/properties directory.

      2. For defaultRealmName, type the realmName property value you want to use as the default realm.

      3. Save your changes to the wkplc.properties file.

      4. Run the following task from the <wp_profile_root>/ConfigEngine directory, to set this realm as the default realm:
        ./ConfigEngine.sh wp-default-realm -DWasPassword=password

      5. Stop and restart all necessary servers to propagate your changes.

    3. The default Portal administrator user ID is a file-based user ID which is unlikely to exist in your Connections realm. Follow these steps to change the WAS/Portal administrator user ID to an available user ID in the Connections realm.

      1. Run the following command from the <wp_profile_root>/ConfigEngine directory to replace the existing WebSphere Application Server administrative user ID and group ID with the new user and group.
        ./ConfigEngine.sh wp-change-was-admin-user \
            -DWasPassword=password \
            -DnewAdminId=newadminid \
            -DnewAdminPw=newpassword \
            -DnewAdminGroupId=newadmingroupid

        You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.

        The task is intended to run against a running server. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.

      2. Verify that the task completed successfully. In a clustered environment, restart the deployment manager, the node agents, and WebSphere Portal servers. In a stand-alone environment, restart the server and WebSphere Portal servers.

      3. Run this task to replace the old WebSphere Portal administrative user ID and group ID with the new user and group:
        ./ConfigEngine.sh wp-change-portal-admin-user \
            -DWasPassword=password \
            -DnewAdminId=newadminid \
            -DnewAdminPw=newpassword \
            -DnewAdminGroupId=newadmingroupid

        You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.

        The task is intended to run against a running server. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.


    Enable basic authentication

    Configure basic authentication for the Connections portlets. Use basic authentication if you are not using single sign-on for authentication.

    Configure basic authentication allows the manual entry of user credentials in the personalize mode of the portlets. Basic authentication for the portlets is only supported if single sign-on is not already enabled between WebSphere Portal and Connections. If single sign-on is enabled, the basic authentication credentials that are entered in the personalize mode of the portlets are ignored.

    The Activity Stream portlet does not support basic authentication.

    If you use basic authentication for the portlets, every user must type in their personal credentials manually in the personalize mode of the portlets or shared credentials can be supplied from the Credential Vault.

    If a user changes a valid user ID and password, the user must log out of Portal and log in again to refresh the credentials. If a user enters credential incorrectly, or updates an expired password, logging out and logging back in is not required.

    1. Set the authenticationMethod property to basicAuth in the file \WEB-INF\lcaccelerator\properties\lcaccelerator.properties in the deployed portlets war.

    2. Make sure that your changes are applied to all cluster members. Apply changes in the WAR file, redeploy the WAR, and synchronize the changes to all cluster members from the WebSphere deployment manager.

    3. If you change deployed applications, save the file, then restart the portlets application or the application server.

    After you configure basic authentication, you can enable the portlets in one of the following ways:

    • Users can log in to portlets using the Personalize mode.

    • The Portal administrator can configure the portlets using the credential slot

    To configure the portlets through a system slot:

    1. In Portal Server Administration choose Administration > Access > Credential Vault.

    2. Click Add a vault slot.

    3. Choose a vault and vault segment from select drop-down.

    4. Choose a vault resource to associate with the system slot. If no vault resource is associated with the vault slot, create a vault resource.

    5. Enter a vault slot name. This is the name that is seen in the configuration mode of the portlets.

    6. Check Vault Slot is shared.

    7. Enter a shared user ID and password to be stored in the system slot.
    8. (To confirm changes made ) For Portal 8, the AdmgrIN_SLOTS virtual resource requires access permissions. Assign AdmgrIN_SLOTS "All Authenticated users" permissions. The AdmgrIN_SLOTS can be found under the virtual resource in the Resources Permissions Portlet

    The settings on the personalize mode of the portlets overrides the settings in configuration mode. To enable the personalize mode in the portlets, the Portal administrator must perform step 1 and enable basic authentication.


    Install the Connections Portlets for WebSphere Portal

    Install the Connections Portlets for IBM WebSphere Portal using the Portal Solutions Installer.

    Use the portlets, you can access only those Connections offerings that you already installed and configured. Note the following restrictions and prerequisites before you install:

    • You must uninstall any previous versions of the portlets before you install. Upgrading from previous versions is not supported. Before you run the PAA Solution installer, manually clear configuration settings from the previous installations.

      For example, remove any existing settings for the DynaCache, REP, search jars, or VMM configuration.

    • To enable LTPA single sign-on between an Connections feature and a WebSphere Application Server configured for stand-alone LDAP, complete the steps in the section Configuring authentication. to enable single-sign on before you start the installation.

    • When Single Sign-On is enabled between Portal and Connections, the Portal administrator who installs and configures the Connections portlets must be a valid Connections user.

      For example, the user you assign to manage the Virtual Member manager, as set using the -DICdsxAdminId parameter from Step 5, can be made a Portal administrator by following the steps in the article How to assign a new portal administration group aside from wpsadmins in the IBM WebSphere Portal wiki. You can also create a Connections profile for the default Portal administrator in the Connections profiles database by following the steps in the topic Adding LDAP data to the Profiles database.

    • Anonymous Portal users can access the Connections portlets and are treated as anonymous Connections users. However, authenticated Portal users must also be valid Connections users or they will get an error when they try to access a Connections portlet.

    1. If you are installing the Connections Portlets on WebSphere Portal 7.0.0.2, you must first install the Solution installer for WebSphere Portal. You can download the solution installer from the Greenhouse catalog. The PAA installer is already available on Portal 8.

    2. Download the Portlets Archive Install file, SNPortlets.paa. cd following directory:

      • AIX : [wp_profile_root]/ConfigEngine
      • Linux: [wp_profile_root]/ConfigEngine
      • Solaris: [wp_profile_root]/ConfigEngine
      • Windows: [wp_profile_root]\ConfigEngine

    3. Install the PAA, following the instructions for your operating system.

      • This task can be run with the server running or stopped.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options

      • If you are installing in a clustered environment, complete the installation steps on the primary node and then on all additional nodes.

      • Make sure that all node agents are running during the installation.

      AIX, Linux, or Solaris:

      ./ConfigEngine.sh install-paa \
          -DPAALocation=[location-to-paa]/SNPortlets.paa \
          -DWasPassword=[was-admin-pwd]  \
          -DPortalAdminPwd=[portal-admin-pwd]

      Windows:

      ConfigEngine.bat install-paa \
          -DPAALocation=[location-to-paa]/SNPortlets.paa  \
          -DWasPassword=[was-admin-pwd] \
          -DPortalAdminPwd=[portal-admin-pwd]

      z/OS: Complete the following steps:

      1. In the Portal configuration panel, select Application configuration tasks.

      2. Select Configure content with Solution Installer.

      3. Select Install and deploy a solution.

      4. Select Define variables.

        Press F1 to display the help panel if you need assistance defining the variables.

      5. Generate the customization jobs.
      6. Follow the Customization dialog instructions for submitting the customization jobs.
    4. Register the PAA.

      • Start the server before running this task.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system.

      • If you are installing in a clustered environment, complete the installation steps on the primary node and then on all additional nodes.
      ConfigEngine deploy-paa -DappName=SNPortlets \
          -DWasPassword=[was-admin-pwd]  \
          -DPortalAdminPwd=[portal-admin-pwd]

      If you are deploying to a clustered environment and your PAA file contains XMLAccess script files, add the following two parameters to the deploy-paa task:

      • -DmaxTimeToWait
      • -DmaxAppTimeToWait
      These values define the time that the wplc-wait-for-sync-to-complete task waits to synchronize your nodes. The default values are -DmaxTimeToWait=30 and -DmaxAppTimeToWait=5. The values are in minutes. If your clustered environment requires a longer synchronize time, add these parameters to your deploy-paa task with values that meet your requirements.
    5. Configure the portlets.

      • Start the server before running this task.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system.

      • If you are installing in a clustered environment, complete the installation steps on the primary node and then on all additional nodes.

      If you are installing on WebSphere Portal 7.0.0.2, execute:

      ConfigEngine configure-SNPortlets \
                   -DICversion=4.5 \
                   -DICblogsHomepageHandle=[homepagehandle]  \
                   -DICemailSetting=[emailSetting] \
                   -DICtagSearchType=mysearch \
                   -DICdsxAdminId=[dsxAdminId] \
                   -DICdsxAdminPwd=[dsxAdminPwd]
                   -DICbaseURLunsecured=[baseURLunsecured] \
                   -DICbaseURL=[baseURL]
                   -DPaaRootPath=[paa-install-root] \
                   -DWasPassword=[was-admin-pwd] \
                   -DPortalAdminPwd=[portal-admin-pwd]

      For example:

      ConfigEngine configure-SNPortlets \
                   -DICversion=4.5 \
                   -DICblogsHomepageHandle=homepage  \
                   -DICemailSetting=email-exposed \
                   -DICtagSearchType=mysearch \
                   -DICdsxAdminId=fadams \
                   -DICdsxAdminPwd=passw0rd  \
                   -DICbaseURLunsecured=http://connections.example.com \
                   -DICbaseURL=https://connections.example.com  \
                   -DPaaRootPath=[paa-install-root] \
                   -DWasPassword=[was-admin-pwd] \
                   -DPortalAdminPwd=[portal-admin-pwd]

      If you are installing on WebSphere Portal 8, run:

      ConfigEngine configure-SNPortlets \
                   -DICversion=4.5 \
                   -DICblogsHomepageHandle=[homepagehandle]  \
                   -DICemailSetting=[emailSetting] \
                   -DICtagSearchType=[tagSearchType] \
                   -DICdsxAdminId=[dsxAdminId] \
                   -DICdsxAdminPwd=[dsxAdminPwd]
                   -DICbaseURLunsecured=[baseURLunsecured] \
                   -DICbaseURL=[baseURL]
                   -DWasPassword=[was-admin-pwd] \
                   -DPortalAdminPwd=[portal-admin-pwd]

      For example:

      ConfigEngine configure-SNPortlets \
                   -DICversion=4.5 \
                   -DICblogsHomepageHandle=homepage  \
                   -DICemailSetting=email-exposed \
                   -DICtagSearchType=mysearch \
                   -DICdsxAdminId=fadams \
                   -DICdsxAdminPwd=passw0rd  \
                   -DICbaseURLunsecured=http://connections.example.com \
                   -DICbaseURL=https://connections.example.com  \
                   -DWasPassword=[was-admin-pwd] \
                   -DPortalAdminPwd=[portal-admin-pwd]

    6. Restart the server so that all changes take effect.

    7. If you are installing in a clustered environment, resynchronize the nodes.
    8. Follow the steps in Configuring common directory services for your security configuration to complete the configuration.

    9. Verify that the portlets are successfully installed.
    10. Follow the steps in Updating the portlet theme to assign a performance-optimized profile to the pages so that they meet portlets requirements.

      By default, if a full profile exists in the theme, it is assigned to the pages. As the full profile loads more content than what is required for the portlets, make sure to perform these steps before you go live with your solution.


    Installation options

    These options allow you to customize your installation.


    Table 1. Default properties to install the portlets for a standard deployment.

    Property Value
    -DPaaRootPath The location of the paa root directory where all PAA archive assemblies are copied when they are installed. In WebSphere Portal 7.0.0.2, the path is[websphere-home-path]/paa

    For example, C:\IBM\WebSphere\paa. In WebSphere Portal 8, the path is [WasUserHome]/paa.

    For example, C:\IBM\WebSphere\wp_profile\paa.

    -DPAALocation The location to the SNPortlets.paa archive on the Portal Server file system. -DWasPassword is WAS admin password.
    -DPortalAdminPwd The WebSphere Portal admin password.
    -DappName The name of the application to install. This must always be set to SNPortlets.
    -DICversion The version number of the Connections server the portlets will connect to. Allowed values are '4.0' or '4.5'.
    -DICblogsHomepageHandle The Blogs home page handle for your Connections deployment. The default is homepage.
    -DICemailSetting Set to email-exposed or email-hidden depending on whether the Connections server is configured to expose user email addresses or to hide them.
    -DICtagSearchType Set to search or mysearch, depending on whether you want the tag cloud to display tags only for public content or tags for public content as well as for content the logged-in user contributed.
    -DICdsxAdminId The user ID that is set in the dsx-admin role for the Profiles and Communities services.
    -DICdsxAdminPwd The password for the dsx-admin user.
    -DICbaseURLunsecured The unsecured base URL for the Connections server
    -DICbaseURL The secured base URL for the Connections server.
    -DICpersonCorrelationAttribute Specify the corresponding person relative distinguished name attribute.
    -DICpersonCorrelationAttributeType Assign a value of mail or uniqueId to specify whether the correlation attribute represents an email address or unique identifier.
    -DICcommunityRdnAttribute Specify the corresponding community relative distinguished name attribute.

    For example, cn.

    -DICmaxSearchResults A maximum of results the connections repository returns on a single query.

    For example, 120.

    -DICldapTypeTDS Specify True if you are using Tivoli Directory Server as your LDAP, or specify False if you are using a different LDAP.

    For example, Microsoft Application Dictionary Services or Novell Data Studio.

    -DICrunAsAdmin The default is false. This attribute determines if adapter runs in admin mode or non-admin mode.
    -DICpumaFilterClassname Always set to com.ibm.connections.vmm.adapter.filter.VMMPrincipalFilter
    -DICpumaFilterPosition Usually set to 120.
    -Drepository.id The LDAP repository identifier from the federated repository to configure the group repository relationship. To determine what repository identifier is set for a particular LDAP,

    1. Log in to WAS administration console and navigate to: Security > Global Security.

    2. Under the User account repository section, click Configure for Federated repositories.

    3. In the Related Items section, select Manage repositories. All of the LDAP repositories are listed on this page and the repository IDs are listed under the Repository Identifier column.


    Table 2. To confirm changes made properties for the configure-SNPortlets command

    Property Value
    -DICportletWebapp The name of the Connections Portlets web application that is deployed after you execute the deploy-paa command. You can log in to WAS admin console under the enterprise applications screen to determine the correct setting. The default value is PA_icWEFPtlts.
    -DICshowContentTitleInPortlet true
    -DICshowForumSummaryFiltersInCommunity false
    -DICdojoLayers
    -DICconnectionsContextRoot The connections context root used for making requests for resources by the Activity Stream portlet. The default is connections.
    -DICopenLinksInNewWindow Set a new Resource Environment Property that controls whether or not Connections links open in a new browser window or in the same browser window. This is primarily used by the Activity Stream portlet. The other portlets may be updated in a future release to use this property. The default setting is true.


    Table 3. Service URLS for use with different host names

    Property Value
    -DICactivitiesURL https://connections-activities.acme.com
    -DICprofilesURL https://connections-profiles.acme.com
    -DICcommunitiesURL https://connections-communities.acme.com
    -DICblogsURL https://connections-blogs.acme.com
    -DICbookmarksURL https://connections-bookmarks.acme.com
    -DICforumsURL https://connections-forums.acme.com
    -DICwikisURL https://connections-wikis.acme.com
    -DICsearchBaseURL https://connections-search.acme.com


    Table 4. Parameters to define the context roots used for your Connections deployment.

    Property Value
    -DICprofilesContextRoot profiles
    -DICactivitiesContextRoot activities
    -DICcommunitiesContextRoot communities
    -DICblogsContextRoot blogs
    -DICbookmarksContextRoot dogear
    -DICforumsContextRoot forums
    -DICwikisContextRoot wikis
    -DICsearchContextRoot search
    -DICfilesContextRoot files.


    Table 5. To confirm changes made properties to specify when running the configure-SNPortletsVMM command

    Property Value
    -DICcommunitiesCacheSize 1024
    -DICcommunitiesCacheLifetime 600
    -DICmembersCacheSize 1024
    -DICmembersCacheLifetime 600
    -DICentitiesCacheSize 1024
    -DICentitiesCacheLifetime 86400


    Configure common directory services for your security configuration

    Configure the common directory services to work with your security configuration.

    Connections portlets use the common directory services to enable directory lookup from Connections in the IBM WebSphere Portal environment. This enables type-ahead for finding names. Common directory services are enabled and configured automatically as part of the installation process. Follow this procedure to configure the directory services for your security configuration.

    Restriction: In order to use common directory services, Portal must be configured to use a federated LDAP. Use of a stand-alone LDAP is not supported.

    Follow these steps to configure common directory services for the Connections portlets.

    1. Do the following to copy the configuration files:

      • For a single server: On the IBM WebSphere Portal Server, copy the following files:

        • directory.services.xml
        • directory.services.xsd
        • sonata.services.xml
        • sonata.services.xsd
        From <wp_profile-dir>/paa/SNPortlets/components/SNPortlets/config/templates/deployment, to: <portalInstallRoot>\wp_profile\config\cells\<cell>\ .

      • For a clustered deployment: On the primary IBM WebSphere Portal Server, copy the files from <wp_profile-dir>/paa/SNPortlets/components/SNPortlets/config/templates/deployment, to the dmgrGR directory at: <dmgrGR install root>\profiles\<dmgr profile name>\config\cells\<cell>\.

    2. If you are using LTPA SSO, skip this procedure because no change is required. For other types of authentication, edit sonata.services.xml and change the sonataServices tag, <sonataServices name="DefaultAuthenticator">, to the appropriate value for the name attribute.

      • SPNEGO: <sonataServices name="KerberosAuthenticator">
      • Tivoli Access Manager: <sonataServices name="TAMAuthenticator">
      • SiteMinder: <sonataServices name="SiteMinderAuthenticator">
      • Tivoli Access Manager and SPNEGO: <sonataServices name="KerberosAuthenticator">

        On a Portal 8 server, use <sonataServices name="TAMAuthenticator">

      • SiteMinder and SPNEGO: <sonataServices name="KerberosAuthenticator+">
    3. (Clustered deployment only) Login to dmgrGR admin console and navigate to the System Administration > Nodes. Select both WebSphere Portal nodes and click Full Resynchronize.

    4. Restart the Portal server after you update directory.services.xml or restart all of the servers for a clustered deployment.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Using_the_Profiles_database_as_the_user_directory_ic45


    Configure a global proxy for POC

    Configure a global proxy for POC to handle URL redirections.

    This procedure only applies if you are deploying the Connections portlets on Portal 7 servers. Skip these steps if you are deploying on Portal 8 servers.

    You must configure a global proxy in order to address content in the Connections portlets.

    To set up the global proxy:

    1. Follow the instructions in the article Global proxy configuration in the IBM WebSphere Portal wiki.

    2. When you configure the global proxy, add the following line to the proxy definition:
      <proxy:policy url="{$ibm_connections_policy}" acf="none" basic-auth-support="true">
              <proxy:actions>
                  <proxy:method>GET</proxy:method>
                  <proxy:method>HEAD</proxy:method>
                  <proxy:method>POST</proxy:method>
                  <proxy:method>PUT</proxy:method>
                  <proxy:method>DELETE</proxy:method>
              </proxy:actions>
              <proxy:cookies>
                  <proxy:cookie>LTPA</proxy:cookie>
                  <proxy:cookie>LTPA2</proxy:cookie>
                  <proxy:cookie>LtpaToken</proxy:cookie>
                  <proxy:cookie>LtpaToken2</proxy:cookie>
                  <proxy:cookie>JSESSIONID</proxy:cookie>
                  <proxy:cookie>PD-H-SESSION-ID</proxy:cookie>
                  <proxy:cookie>PD-S-SESSION-ID</proxy:cookie>
                  <proxy:cookie>SMSESSION</proxy:cookie>
              </proxy:cookies>
          </proxy:policy>


    Configure the portlets on a page

    By default, the installation process creates sample pages for the different portlets. You can customize those pages to fit your needs or remove them and create new pages. This article describes how to configure the Connections portlets on a WebSphere Portal page

    Restriction: Do not place multiple instances of the same portlet on a page.

    For example, putting two blog portlets on a page might result in unexpected behavior and is not supported.

    Connections portlets can be configured on multiple pages with different filtering and display options. Community Pages (see Community Pages) affect portlets that are configured on those pages. By default, Connections portlets that are placed on a community page filter the user's view to display content from that community. A link to a piece of content from a community resolves to a community page if there is an appropriate portlet to display the content on a matching community page.

    For example, if the Blogs portlet is configured on a "New Employees" community page, the page renders a link in WebSphere Portal to blog entries from that community (see Addressing Connections content). If an appropriate community page is not found, links to the content in WebSphere Portal use a set of default pages to display Connections content.

    You can organize the pages any way you like and can even hide them from your Portal site's main navigation so that users cannot directly navigate to them. The following procedure creates one page for each service under a label named "Connections" under the pre-defined "Home" page in WebSphere Portal. You can move the Connections pages or create them elsewhere in your WebSphere Portal site structure. It is only important that the unique names for the pages remain the same.

    1. Define a label to contain the default pages.

      1. Define a label to contain the default pages.

      2. Click Administration > Portal User Interface > Manage Pages.

      3. Navigate to the page where you want to add a portlet.

        For example, navigate to Home.

      4. Click New Label. A label is a container for WebSphere Portal pages that does not itself contain content. Alternatively, create a page if you want to place portlets or content on the page.
      5. Enter Connections for the title.

      6. Click OK.

    2. Define page unique names that indicate the portal page users are directed to in order to view content from the Connections services. These unique names are used in the Content resolver component that handles the Portal page look up The lookup retrieves the appropriate page when a user selects Connections search results from the WebSphere Portal Search Center, selects items from the Connections summary portlets, or uses the URLs described in the Addressing Connections content section. For each of the rows in the table, do the following:

      1. Define a page for each service to serve as a default page for content of that type.

      2. Click the Connections label you created in the prior step.

      3. Click New Page, enter the title and unique name and create the page by clicking OK. The are suggested names, but you can modify them for your deployment.


        Table 6. Suggested page and portlet titles

        Page Title Unique Name Portlet Title
        Profiles ibm.conn.profiles Profiles
        Activities ibm.conn.activities Activities
        Blogs ibm.conn.blogs Blogs
        Bookmarks ibm.conn.bookmarks Bookmarks
        Forums ibm.conn.forums Forums
        Wikis ibm.conn.wikis Wikis

        Do not deploy an Activities portlet or a Forums summary portlet on an anonymous page. The portlet page must require users to authenticate.

    3. Add portlets to corresponding pages:

      1. Click the pencil icon (Edit Page Layout) next to a page.

      2. Click Add Portlets.

      3. Type the portlet title in the Search box and click Search.

      4. Select the check box next to the appropriate portlet, then click OK.

      5. Click Done.
    4. Follow these steps to give users access to the page.

      1. Navigate to Administration > Access > Resource Permission > Pages > Content Root. Navigate to the first page that contains an Connections Portlet.

      2. Click the Assign Access button for the entry.

        For example, to allow non-admin users to access the portlets, set the role "Privileged User" to "All authenticated users." To allow anonymous access, set the role "User" to "Anonymous Portal User."

      3. Click Apply and then Done.

      4. Repeat Steps a-d for each page that contains an Connections Portlet.

      Page access may be inherited. If page access is not inherited in your site structure, click the key icon (Edit access) next to each page and add at least user access for each user or group that will view Connections content in WebSphere Portal.


    Testing the Ajax proxy configuration

    Test the configuration of the application-specific Ajax proxy to manage authentication for the Connections portlets.

    Connections portlets now use an application-specific Ajax proxy as the mechanism for forwarding security headers and cookies with each REST service call to authenticate the request with the Connections server. The proxy is configured as part of the installation process. Use the following test URLs to verify that the application-specific proxy configuration is working.

    If you are in an SSO environment, you must first open a new browser window and log in to Portal as a Connections user.

    • If you have a web server that is configured for Portal as well as Connections, use: http://<WP_Server>/wps/<CONNECTIONS_PORTLETS_CONTEXT_ROOT>/proxy/https/<CONNECTIONS_SERVER_BASE_URL>/profiles/atom/profileService.do

      For example, http://myportalwebserver/wps/PA_icWEFPtlts/proxy/https/myconnectionswebserver/profiles/atom/profileService.do

    • If you have a web server that is configured for Connections but not for Portal, use: http://<WP_Server:Port>/wps/<CONNECTIONS_PORTLETS_CONTEXT_ROOT>/proxy/https/<CONNECTIONS_SERVER_BASE_URL>/profiles/atom/profileService.do

      For example, http://myportalserver:10039/wps/PA_icWEFPtlts/proxy/https/myconnectionswebserver/profiles/atom/profileService.do

    • If you do not have web servers that are configured for either Portal or Connections, use: http://<WP_Server:Port>/wps/<CONNECTIONS_PORTLETS_CONTEXT_ROOT>/proxy/https/<CONNECTIONS_SERVER_BASE_URL:port>/profiles/atom/profileService.do

      For example, http://myportalserver:10039/wps/PA_icWEFPtlts/proxy/https/myconnectionsserver:9444/profiles/atom/profileService.do

    In an SSO environment:

    • If you are prompted to save or open a document or a feed renders in the browser, then the proxy is properly configured.

    • If you are prompted to enter a user name and password, then the proxy is properly configured but SSO is not enabled.

    • If you receive a 403 error in response, then the proxy is not properly configured.

    • If you receive a 500 or any other response code, the proxy was properly configured but something else is not working.

    In a non-SSO environment:

    • Enter the user name and password of a Connections user.

    • If you are prompted to save or open a document or a feed renders in the browser, then the proxy is properly configured

    • If you receive a 403 error in response, then the proxy is not properly configured.

    • If you receive a 500 or any other response code, the proxy was properly configured but something else is not working.


    Set public render parameter-sharing for the Connections portlets

    Public render parameters are set by default during installation but you can manually set these parameters when you deploy new portal pages. These parameters communicate what content to render when navigating between portlets and from Connections content accessed from the search center portlet.

    The Connections detail portlets use public render parameters to communicate what content to render when navigating between the portlets and from Connections content that is accessed from the Search Center portlet. The default sharing scope for all public render parameters is the global scope. To prevent sharing of public render parameters between pages and to avoid undesirable behavior in rendering content in the portlets, define a unique scope for each page that contains an Connections detail portlet.

    For information on defining scopes for public render parameters, see this article on Public Render parameters in the IBM WebSphere Portal wiki.


    Remove the Connections portlets

    OPTIONAL: If you no longer want the Portlets that are installed, you can remove them from IBM WebSphere Portal.

    Follow these steps to remove the Connections portlets.

    All of the required and optional parameters for the installation script are described in the topic Installation Options

    1. cd following directory:

      • AIX: [wp_profile_root]/ConfigEngine
      • Linux: [wp_profile_root]/ConfigEngine
      • Solaris: [wp_profile_root]/ConfigEngine
      • Windows: [wp_profile_root]\ConfigEngine

    2. Run the following commands, using the command format for your operating system

      • AIX, Linux, or Solaris: ./ConfigEngine.sh
      • Windows: ConfigEngine.bat
      ConfigEngine remove-SNPortlets \
                   -DWasPassword=[was-admin-pwd] \
                   -DPaaRootPath=[paa-install-root] 
                   -DPortalAdminPwd=[portal-admin-pwd]
      ConfigEngine remove-SNPortletsSearch 
                   -DWasPassword=[was-admin-pwd] 
                   -DPaaRootPath=[paa-install-root] 
                   -DPortalAdminPwd=[portal-admin-pwd]
      ConfigEngine remove-SNPortletsVMM 
                   -DWasPassword=[was-admin-pwd] 
                   -DPaaRootPath=[paa-install-root] 
                   -DPortalAdminPwd=[portal-admin-pwd] 
      ConfigEngine remove-paa 
                   -DappName=SNPortlets 
                   -DforceRemove=true 
                   -DWasPassword=[was-admin-pwd] 
                   -DPaaRootPath=[paa-install-root] 
                   -DPortalAdminPwd=[portal-admin-pwd]
      ConfigEngine uninstall-paa 
                   -DappName=SNPortlets 
                   -DforceUninstall=true 
                   -DWasPassword=[was-admin-pwd] 
                   -DPaaRootPath=[paa-install-root] 
                   -DPortalAdminPwd=[portal-admin-pwd]

    3. Do one of the following:

      • If you are uninstalling on WebSphere Portal 7.0.0.2, manually delete the Connections Portlets assembly directory, SNPortlets, from the [paa-install-root] folder.

      • If you are uninstalling on WebSphere Portal 8, execute the following command to delete the Connections Portlets assembly files from the [paa-install-root] folder:
        ConfigEngine delete-paa -DassemblyList=SNPortlets -DWasPassword=[was-admin-pwd] -DPortalAdminPwd=[portal-admin-pwd]


    To confirm changes made and recommended configuration

    Depending on your deployment, follow these steps to optimize the Connections portlets.

    The following are some optional configuration steps you can take to enhance the deployment of Connections portlets for IBM WebSphere Portal.


    Community Pages

    Integrate Connections Communities into your Portal site to enhance your portal's social collaboration capabilities.

    You integrate Communities by associating a set of portal pages with a community. These types of portal pages are called Community Pages. By associating a set of portal pages with a community in Connections, all of the Connections portlets on those pages automatically render their content within the context of that community. One or more communities can be integrated into your portal site. You can associate different sets of pages in your portal site with the appropriate community. The community can be public, moderated, or private.

    Before you add portlets to a community page, make sure that the corresponding widget exists in the community.

    For example, before you add a Blogs portlet to a community page, make sure that the Connections community contains a blog. If not, add the Blogs widget to the Connections community using the browser interface.

    Restriction: Ideation blogs are not supported for community pages. If your Connections community contains an Ideation blog widget, it does not display if the Blogs portlet is deployed on a community page.

    Some of the ways the portlets on a Portal community page interact with an Connections community include:

    • Clicking a profile user name or photo in a Profiles summary portlet displays profile detail in the target portlet.

    • Clicking a View all link in a Profiles summary portlet displays a list of community members in the target portlet. This link works only if there is a Profiles detail portlet on the page.

    • Clicking the View all link in a Blogs summary portlet displays all entries in a community blog in the Blogs detail portlet on a community page.

    • Clicking the entry in a Blogs summary portlet displays the detail of that entry in the Blogs detail portlet on a community page.

    • When a user hovers over an entry in a Blogs summary portlet, a pop-up displays, with a link that allows a user to read the entry.

    • Clicking Read for an entry in the Blogs summary portlet shows the selected entry details in the Blogs detail portlet.

    Follow the steps for configuring and mapping community pages for your version of IBM WebSphere Portal.


    Map a community page to a community

    Map a community page to an Connections community so the portlets can interact with community content.

    Follow the steps to map the community pages to a community based on what WebSphere Portal Server you are using.

    1. To map community pages to a community on a WebSphere Portal 7 server:

      1. Log into Portal as an administrator.

      2. Navigate to the page to map to a community.

      3. Click Actions > Edit Page Properties.

      4. Expand the Advanced options section and click I want to set parameters.

      5. Add the following new parameters:

        Parameter Key Parameter Value
        ibm.community.id The ID of the connections community. To get this value, open the Connections community in a browser and copy the ID following communityUid= in the community URL.
        ibm.community.home Set to TRUE if the page is identified as the home page for the community. There can be only one home page. In the case where there are multiple homepages set, the first page is selected.
        ibm.community.page Set to FALSE if this is the home page; otherwise, set to TRUE.

        If you are creating a page which has a parent page that is mapped to a community, follow steps c and d , but you must explicitly set the parameters set in step e. To do this, click the Edit icon for each parameter, click OK, then explicitly set the parameters.

    2. To map community pages to a community on a WebSphere Portal 8 server, create a community association using the XML configuration interface (xmlaccess command). When defining the association in the XML import file, use the <content-mapping-info> element, and specify a content mapping scope of ibm.connections for an individual nested <content-mapping> element. For details and an example, refer to the topic on Manage community associations in the WebSphere Portal product wiki.

    3. Assign access to the page. If the community has restricted membership, you can secure the page so that only members of the community can see the page in the Portal navigation. You can also access assign on community pages mapped to public or moderated communities, but doing so does not restrict access to the content in the community. There are other mechanisms, including APIs, mobile clients, connectors and search and portlets on other pages which may expose the content outside the community page. Membership lists in Connections communities should have the correct level of access to community content and Portal pages should reflect that level . Before you use communities for access control on pages, follow the steps in Integrating community membership with Portal security.

      1. Navigate to Administration > Manage Pages and find the community page for which you want to set access.

      2. Click Set Page Permission (lock icon).
      3. Uncheck Allow Inheritance for all rows and click Apply.

      4. Click on the Edit Role button in the Privileged User and User columns and make sure no users or groups are added that you do not want to access this page.

      5. Click on the Edit Role button in the Privileged User or User column, depending on what level of access you want to grant to community members.

        See the Roles topic for a description of roles in WebSphere Portal.

      6. Click Add.

      7. Change Search by to displayName.

      8. Enter the name of the community in the search box and click Search.

      9. Check the box next to the group representing the community and click OK. If successful, the group appears in the list of members in the role and a message indicates that the members were successfully added to the role.

    4. Before adding portlets to your community page, make sure that the corresponding widget exists in the community.

      For example, before you add a Blogs portlet to the community page, make sure the Connections community contains a blog. If not, add the Blogs widget to the Connections community using the browser interface.

    If the portal administrator configures a portlet with a new connections server URL for a community page, then the changes will take effect only after the community page is configured with a valid community ID for the new connections server, by editing the portal page parameters settings to include the new community ID.


    Integrate community membership with Portal security

    Configure the Virtual Member manager to integrate information from Connections communities with your WebSphere Portal environment.

    Starting with version 6.1, IBM WebSphere Application Server uses a component called Virtual Member manager (VMM) to manage information about community membership. VMM provides an interface that enables communication between WebSphere Portal and any repository, whether federated repositories, a stand-alone repository, or your own custom user registry. You can configure VMM to recognize Connections as a repository so that Portal can access community user and group information from Connections communities.

    For example, after VMM is configured, users can select Connections private or public communities as groups when they assign security roles or access rights.

    For more information about the architecture of VMM, see the article Virtual Member Manager Integration from the IBM WebSphere Portal wiki.

    For more information about configuring a user repository for VMM, see the white paper Set up a custom user repository from IBM Developer Works.

    After configuring Connections to work with VMM, user can:

    • Search for Connections public and private communities by name (represented as groups in WebSphere)
    • Resolve public and private community membership for particular users (represented as group membership in WebSphere)
    • Display the WebSphere users that are members of a particular Connections public or private community

    The following are some known limitations:

    • When you use the VMM get operation to get a single identifier and querying by name, instead of using the unique externalID, nothing is returned if more than one community name matches the query.

    • The operation to display WebSphere users that are members of a particular Connections community can have a performance impact for large groups.
    • Tivoli Directory Integrator is recommended for populating user data into Connections. When you use the profile data population wizard, a user's email might not be populated into the Communities database. A user might not appear in the proper communities until they have logged in to Communities, used a feature from the Communities service, or their profile is synchronized with Tivoli Directory Integrator.


    Prerequisites

    In order to configure the VMM to recognize an Connections repository, the following must be true:

    • IBM WebSphere Portal must be installed and verified

    • Connections must be installed and verified to work
    • Hidden email is supported. In the 3.0.1.1 refresh, it is not mandatory any longer to have email enabled.
    • Single sign-on must be configured between Connections and Portal. Follow the steps in Configuring single sign-on.

    • Connections and WebSphere Portal must share a common LDAP.

    • Import the SSL certificate from WebSphere Portal Server to Connections. Follow the steps in Importing a certificate to support SSL with the following differences:

      • Log in to WAS admin console for the Connections server, rather than the Portal server.

      • Enter the host, port, and alias for the Portal server.

        For example:

        Host : portal.example.com
        Port : 10025 (SOAP default port on Portal. Please specify appropriate port if non default is used)
        Alias : Portal Certificate (Admin can choose any appropriate alias)

    • If you are deploying on WebSphere Portal 7.0.0.2, install Fixpack PM51981 to avoid problems with private community pages. You can download the Fixpack from Fix Central.

    • Update the VMM schema so that PersonAccount on the Portal server includes personCorrelationAttribute. In a clustered environment, run this command on the Deployment manager. To open the scripting interface, refer to the article Opening a console window for interactive scripting in the Portal wiki. In the scripting interfaces
      $AdminTask addIdMgrPropertyToEntityTypes {-name <personCorrelationAttribute> -dataType string -entityTypeNames PersonAccount} 
      Then:
      $AdminConfig save
      For example, if the personCorrelationAttribute matches ibm-entryUuid, use:
      $AdminTask addIdMgrPropertyToEntityTypes {-name ibm-entryUuid -dataType string -entityTypeNames PersonAccount}    $AdminConfig save

      Portal must be running while you execute this command. Restart the server to apply the changes.


    Configure the Connections repository to work with VMM

    Complete these tasks to configure the Connections User Repository adapter. When configuration is complete, you can verify that it is working by logging in to WebSphere Portal as an administrator. Open the Users and Groups portlet from the Administration tab. Search for groups that must be present as communities in your Connections deployment. If you find the correct groups and the members of the groups are listed, the deployment is successful.

    Make sure that you configured common directory services when you installed the portlets. Common directory services are a requirement for configuring the VMM adapter.


    Deploy libraries for the Connections portlets

    Deploy libraries required to integrate information from Connections profiles and communities with your WebSphere Portal environment.

    Make sure that you configured common directory services when you installed the portlets. Common directory services are a requirement for configuring the VMM adapter.

    The way you deploy libraries depends on your deployment configuration. There are two different scenarios for deploying libraries on Portal server and Connections:

    • Cross-cell deployment
    • Single-cell deployment
    Find the scenario that matches your deployment and follow those steps for deploying libraries.

    Do not overwrite existing jar files. Back up the AppServer/lib/ext on the Portal server before you begin.

    • For a cross-cell deployment, copy the jars (excluding com.ibm.ws.wim.adapter.connections.forwarding.jar) from [wp_profile-dir]/paa/SNPortlets/components/SNPortletsVMM/shared/WAS/lib to AppServer/lib/ext on the Portal server.

    • For a single-cell deployment:

      1. Create a folder with the name vmm if does not already exist in the AppServer/lib/ext directory.

      2. Copy the jars com.ibm.ws.wim.adapter.base.jar and com.ibm.ws.wim.adapter.connections.forwarding.jar from [wp_profile-dir]/paa/SNPortlets/components/SNPortletsVMM/shared/WAS/lib to AppServer/lib/ext on the Portal server.

      3. Copy the jars (excluding com.ibm.ws.wim.adapter.base.jar and com.ibm.ws.wim.adapter.connections.forwarding.jar) from [wp_profile-dir]/paa/SNPortlets/components/SNPortletsVMM/shared/WAS/lib to AppServer/lib/ext/vmm on the Portal server.

    In a cluster environment copy the jars to each node.


    Configure the Connections repository for VMM

    Configure the Connections repository for the Virtual Member manager (VMM) so that you can integrate communities with Portal security.

    This task is done when the server is stopped. In a cluster, you can change the configuration files directly on the deployment manager and then synchronize the changes to all cluster nodes.

    1. Configure VMM.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system:

        AIX, Linux, or Solaris:

        ./ConfigEngine.sh <parameters>

        Windows:

        ConfigEngine.bat <parameters>

      • If you are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.

      If you are installing on WebSphere Portal 7.0.0.2, execute:

      ConfigEngine configure-SNPortletsVMM \
           -DICpersonCorrelationAttribute=ibm-entryUuid  \
           -DICpersonCorrelationAttributeType=uniqueId \
           -DICcommunityRdnAttribute=cn \
           -DICmaxSearchResults=120  \
           -DICldapTypeTDS=true \
           -DICrunAsAdmin=false \
           -DICpumaFilterClassname=com.ibm.connections.vmm.adapter.filter.VMMPrincipalFilter  \
           -DICpumaFilterPosition=120 \
           -DPaaRootPath=[paa-install-root] \
           -DWasPassword=[was-admin-pwd] \
           -DPortalAdminPwd=[portal-admin-pwd]

      If you are installing on WebSphere Portal 8, execute:

      ConfigEngine configure-SNPortletsVMM \
           -DICpersonCorrelationAttribute=ibm-entryUuid \
           -DICpersonCorrelationAttributeType=uniqueId  \
           -DICcommunityRdnAttribute=cn \
           -DICmaxSearchResults=120 \
           -DICldapTypeTDS=true \
           -DICrunAsAdmin=false  \
           -DICpumaFilterClassname=com.ibm.connections.vmm.adapter.filter.VMMPrincipalFilter \
           -DICpumaFilterPosition=120  \
           -DWasPassword=[was-admin-pwd] \
           -DPortalAdminPwd=[portal-admin-pwd]
    2. Configure the VMM Repository.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options.
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system.

      • You must stop the WebSphere Portal Server before you run the following command; otherwise, the command script fails.

      • If you are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.
      ConfigEngine wp-create-cur \
           -DWasPassword=[was-admin-pwd] \
           -Dfederated.cur.id=connections  \
           -Dfederated.cur.adapterClassName=com.ibm.ws.wim.adapter.connections.ConnectionsAdapter  \
           -Dfederated.cur.isExtIdUnique=true \
           -Dfederated.cur.supportExternalName=false  \
           -Dfederated.cur.supportPaging=false \
           -Dfederated.cur.supportSorting=false  \
           -Dfederated.cur.supportTransactions=false \
           -Dfederated.cur.baseDN=o=connections

      If you are reinstalling the portlets after you remove them using the steps in Removing the Connections portlets, make sure that the VMM repository does not already exist.

      1. Log in to the WebSphere Administrative Server console.

      2. In the section Global securities > Federated repositories > Manage repositories look for a Connections repository. If one exists, delete it.

    3. Update the Repository Group Repository Relationship

      • All of the required and optional parameters for the installation script are described in the topic Installation Options
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system.

      • You must stop the WebSphere Portal Server before you run the following command; otherwise, the command script fails.

      • If you are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.
      ConfigEngine wp-update-group-repository-relationship \
           -DWasPassword=[was-admin-pwd]  \
           -Drepository.id=[ldap-identifier] \
           -Drepository.forgroups=connections
      Repeat for every LDAP repository that is configured in Federated Repositories for WebSphere Application Server. Where:

      • These default properties can be used to install the portlets for a standard deployment.
      • -DPaaRootPath is the location of the PAA root directory where all PAA archive assemblies are copied when they are installed. In WebSphere Portal 7.0.0.2, the path is [websphere-home-path]/paa.

        For example: C:\IBM\WebSphere\paa In WebSphere Portal 8, the path is [WasUserHome]/paa

        For example, C:\IBM\WebSphere\wp_profile\paa

    4. If you are installing in a clustered environment, resynchronize the nodes.

    If the Virtual Member Manager is not working, for example, if community groups are not displaying on the Portal server, first check the timeout settings on the Portal and Connections servers to make sure that they are compatible.

    1. Log in to WAS admin console and change to: Security > Global Security > Authentication > LTPA and record the value of the timeout setting.

    2. On the Portal server:

      1. Change to [wp profile directory]\config\cells\[cellname] on a stand-alone server, or [dmgr profile directory]\config\cells[cellname] in a clustered environment.

      2. Open sonata.services.xml.

      3. Update the value of <attribute key="CookieTimeout" value="60" /> to a timeout value that is 80 - 90% of the value that is set for the LTPA timeout setting you recorded in the previous step.

    3. On the Connections server:

      1. Change to [appsvr profile directory]/config/cells/[cellname]/LotusConnections-config/ for a stand-alone environment and [dmgr profile directory]/config/cells/[cellname]/LotusConnections-config/ in a clustered environment.

      2. Open LotusConnections-config.xml.

      3. Update the <customAuthenticator name="DefaultAuthenticator"/> element to:
        <customAuthenticator name="DefaultAuthenticator">     <attribute key="CookieTimeout" value="24" />
        </customAuthenticator>
        Set the value of CookieTimeout to the same value you set in sonata.services.xml on the Portal service.

      4. Restart Connections and Portal.
    In addition to checking the timeout settings, do the following:

    1. Make sure that the Connections server can resolve the Portal server's host name either by DNS setting (under LAN properties) or by adding an entry in the host file on the Connections Server. The host file is typically at C:\Windows\System32\drivers\.

    2. Delete the Portal SSL certificate that is imported on the Connections server earlier and import a new one.


    Verify impersonation configuration

    The impersonation feature lets you access another user's system as though you are that user so that you can test user access. Impersonation is configured as part of the installation process. Use this procedure to confirm that it is working as expected.

    The impersonation feature lets you access another user's system as though you are that user. Follow these steps to confirm the feature is working correctly.

    1. Log in as any non-admin user.

    2. Create a page, for example, JonesxxPage.

    3. Click Actions > Share page.

    4. Select Group search from drop-down.

    5. Enter a search string and verify that the results come from communities the user belongs to rather than from all communities.

    6. Perform a similar test for each node.


    Configure search integration

    Connections search integration in IBM WebSphere Portal allows users to perform search queries and view query results for Connections content within the context of their portal environment.

    This integration point is enabled by configuring the portal search center component to include Connections content as part of the related search results. You also must configure a component to allow the navigation from the portal search center to the portlets so that users can view the Connections-related search results.


    Understanding the search architecture

    Portal currently provides the following two search frameworks. The one you use depends on whether you value performance or ease of maintenance.

      • Search Service
        Search Service is a live search and uses REST (along with other technologies) to search on a target information source and fetch the matching results. Connections/Portal integration uses the "Remote Content Server Search Service Type" (referred to as RCSS type), using the ATOM/REST APIs exposed by Connections. This approach would tag relevance score of connections content, in isolation, to the portal relevance score. It is a federated approach in which the search is federated between Portal and Connections instances.
      • Search Collections
        Search Collections use a seedlist framework to crawl and index all of the Connections data locally on a Portal server. The advantage of this approach is that it removes extra network traffic to the Connections server during the search process, making information retrieval fast. One disadvantage is that the crawler must run frequently to synchronize local content with all the latest content on the Connections server. It can do a better relevance ranking of search results, as search results (including Portal and Connections) are served by the Portal engine only.


    Excluding Connections Portlets from Portal default search indexing

    Exclude the Connections portlets from the default Portal search indexing.

    If you are integrating with WebSphere Portal 8.0, portlets are excluded from portal search by default and you do not must specifically exclude them.

    By default, on WebSphere Portal 7.0 servers, the Portal search crawler crawls all the portal pages and active portlets on them. Since Connections uses its own seedlists for search, you can exclude the Connections portlets from the default portal indexing. The default crawler user is the default Portal admin user. This user might not be a Connections user, so to exclude the Connections Portlets from the Portal indexing; this user must not have access to Connections portlets. To achieve this, create a separate group which lists all Connections users who have access to Connections portlets. Make sure that the crawler user is not part of this group. Connections portlets must be assigned access permission to this group instead of to the 'All Authenticated Portal users group'. When the crawler runs, the default portal indexing excludes Connections portlets.


    Deploy search integration prerequisites

    Follow these steps to configure search integration.

    1. Configure Search.

      • All of the required and optional parameters for the installation script are described in the topic Installation Options
      • Follow the pattern from Step 3 for running the ConfigEngine command for your operating system.

      • If you are installing in a clustered environment, complete the installation steps on the primary node and then on all additional nodes.

      If you are installing on WebSphere Portal 7.0.0.2, execute:

      ConfigEngine configure-SNPortletsSearch \
           -DPaaRootPath=[paa-install-root] \
           -DICversion=4.0  \
           -DWasPassword=[was-admin-pwd] \
           -DPortalAdminPwd=[portal-admin-pwd]

      If you are installing on WebSphere Portal 8, execute:

      ConfigEngine configure-SNPortletsSearch \
           -DICversion=4.0 \
           -DWasPassword=[was-admin-pwd]  \
           -DPortalAdminPwd=[portal-admin-pwd]

    2. If you are installing in a clustered environment, resynchronize the nodes.


    Configure search using Remote Content Server Search Service Type (RCSS)

    Use the Remote Content Server Search Service Type (RCSS) to implement live search for Connections content from an IBM WebSphere Portal application.

    Consider these issues before you configure RCSS:

    • RCSS search is not supported when your deployment is configured to use Tivoli Access Manager and SPNEGO or Computer Associates' SiteMinder and SPNEGO.

    • Users who are registered in an LDAP that is common between Connections and WebSphere Portal can be granted administration rights in Portal to configure RCSS using scopes API over http.

    Search Service is a live search and uses REST to search on a target information source and fetch the matching results. Connections and WebSphere Portal integration uses RCSS to use the ATOM/REST APIs exposed by Connections. This approach correlates a relevance score for Connections content with the Portal relevance score. It is a federated approach where the search is federated between Portal and Connections instances.

    1. Click the Administration link in the header of the portal page.

    2. In the Manage Search section, click New Search Service.
    3. Name the service appropriately so that it is easily identifiable, provide this value in the Service Name field.
    4. Configure the search service using the following parameters. Possible values for the parameters are provided in the Parameter Value column.

      Parameter Key Parameter Value
      SearchRequestUrl /atom/search/results
      RestServiceUnSecureUrl /search
      ContentType RemoteContent
      QueryParam includeField=wikiLabel&includeField=pageLabel&includeField=community_id&query
      IgnoreAllSourcesSearch false
      RestServiceSecureUrl /search
      StartParam start
      AllSourcesParam scope
      QueryLangParam queryLang
      DisplayProviderId ConnRCSS
      RequestLocaleParam locale
      LocationParam scope
      RequestLocationType /atom/scopes

    5. Log out and log in again before you create scopes for the RCSS service that you configured.

    The RCSS component does not use the keystore managed by WebSphere Application Server. If you try to set the RestServiceSecureProtocol property to https and the RestServiceSecurePort property to the SSL port for the Connections server when you configure the RCSS search service, you cannot to retrieve the search scopes from Connections and thus cannot complete the search configuration. You see SSL handshake errors in the WebSphere Portal SystemOut logs even though you imported the Connections SSL certificate into WAS SSL certificate truststore. If you encounter this problem, follow the additional configuration steps that are documented in this tech note.


    Configure a search collection

    Search Collections use a seedlist framework to crawl and index all of the Connections data locally on a WebSphere Portal Server.

    Ensure that these Connections seedlists are available with basic authentication. Depending on your security configuration, basic authentication might be the default or can be accomplished with an additional virtual host in your HTTP server, by addressing a WebSphere node directly, or by altering Tivoli Access Manager or SiteMinder configuration to open a basic authentication protected endpoint.

    To configure a search collection, you specify one content source for each Connections seed list. Each Connections service (for example, Profiles, Communities, or Blogs) exposes its own seed list so there is one content source per Connections service.

    1. Click the Administration link in the header of the portal page.

    2. In the Manage Search section, click Search Collection.

    3. Click New Collection.

    4. Define the location of the collection on the portal file system and name it with an easily identifiable value.

    5. Click OK to create the collection and create the associated folders and files on the file system.

      The path must not point to an existing directory.

    6. Click Collection to view the metadata of the collection created.

    7. Select

      Seedlist Provider as the Content source type.

    8. Provide the name and the seedlist URL of the Connections service. A

      Seedlist URL has the form: https://<connection_server_name>:port/<service_name>/seedlist/myserver

      For example: https://connections.ibm.com:9444/activities/seedlist/myserver.

      If Connections is configured to use Tivoli Access Manager and SPNEGO security, or just SPNEGO, configure the seedlist URL and host without Tivoli Access Manager, using IHS host only.

    9. Click the Security tab and enter your Connections administrator credentials so that you can access the specific service seedlist URL. Click the small Create button next to the form.

    10. Click Create to create the corresponding Content Source to enable crawling over the service defined.

    11. Create other Connections services Activities, Blogs by repeating steps 1 - 10.

      You can either select to run the crawler on the complete set or on individual service

    12. Ensure that these seedlists are available with basic authentication. Depending on your security configuration, this might be the default or might be accomplished with an additional virtual host in your HTTP server, by addressing a WebSphere node directly, or by altering Tivoli Access Manager or SiteMinder configuration to open a basic authentication protected endpoint.


    Set the Search Scope

    Define search scopes for the content from Connections that is returned from a search in IBM WebSphere Portal applications.

    After the service or collection is defined, you can optionally define search scopes to make available to users. A search scope defines different levels of granularity at which the search is executed from the Portal user interface.

    1. Click the Administration link in the header of the portal page.

    2. In the Manage Search section, click Search Scope.

    3. Click New Scope.

    4. Specify a name for the scope and click Select Location to select the services and collections to include. This view enables you to mix and match various services and content sources and to define the granularity of the search scope.


    Displaying action buttons and links for anonymous users

    Edit style sheets to display action buttons and links for anonymous users.

    By default, some action buttons or links in anonymous view, such as Login to Start a Wiki, Login to Start a Forum or Login to Flag as Inappropriate do not display for anonymous users. If you want anonymous users to see these buttons and links, edit the style sheets to display the action buttons. After you change the styles in the style sheet, the following actions display in portlets for users who access the portlets anonymously:

    • Wikis – Log in to Start a Wiki
    • Forums – Log in to Start a Forum
    • Forums – Log in to Start a Topic
    • Blogs – Log in to Flag as Inappropriate

    1. Open the style sheet connectionsportlet.css or connectionsportletRTL.css from the lcaccelerator\css folder where the Connections portlets are installed.

    2. For any component to display action buttons for anonymous users, change the attribute display from none to inline. The choices are:
      .activitiesAnonymous{
      	display:none;
      }
        .wikisAnonymous{
      	display:none;
      }
        .blogsAnonymous{
      	display:none;
      }
        .dogearAnonymous{
      	display:none;
      }
        .forumsAnonymous{
      	display:none;
      }
        .profilesAnonymous{
      	display:none;
      }
        .copAnonymous{
      	display:none;


    Configure the Connections business card

    Enable the Connections Business Card so that users can access Connections data such as a person's profile information.

    The Connections Business Card used by the portlets now supports the configuration where the email address is hidden in Connections. Follow the steps in the IBM WebSphere Portal product documentation for enabling the business card:

    To configure the Connections business card:

    1. Search the Connections LDAP directory for the user whose profile you want to enable in WebSphere Portal and then add that user to the portal LDAP directory.

    2. Ensure that ibm-primaryEmail is mapped to the appropriate attribute (for example, mail or email) in the LDAP, and that the email address in the Connections LDAP matches the email address in the portal LDAP.
    3. Familiarize yourself with how to run the ConfigEngine command for your platform.

      See Installing the Connections Portlets for WebSphere Portal for details.

    4. Run the following command to configure the Connections business card:
      ConfigEngine configure-ConnectionsBizCard \
           -DICbaseURLunsecured =[baseURL] \
           -DURLProviderName=[URL-provider-name] \
           -DWasPassword=[was-admin-pwd]

      The default name for [URL-provider-name] is Default URL Provider.

    5. To test that the card is configured correctly, open one of the Connections portlets on WebSphere Portal and search for a person. Then, hover on the user's name to make sure the business card displays for this user. If not, the Connections business card is not configured properly.

    6. Run the following command to remove the configuration for the Connections business card:
      ConfigEngine remove-ConnectionsBizCard \
           -DURLProviderName=[URL-provider-name] \
           -DWasPassword=[was-admin-pwd]

      The default name for [URL-provider-name] is Default URL Provider.

    When the Connections business card is integrated in Portal, it affects the styles of the skin of the portlets.

    For example, the width of the area where the portlet title is shown is decreased. To resolve this issue, install interim fix PM24072 on the Portal server. You can download the Fixpack from Fix Central.


    Configure links to open Connections in same browser window

    You can configure the portlets so that when a user clicks a Connections link it opens Connections in the same browser window rather than the default, which is to open in a new window.

    When you configure the portlets, you can enable an option that allows users to access the full Connections application from a portlet. Follow these steps to configure the option to open Connections in the same browser rather than opening a new window.

    1. Open the lcaccelerator.properties file, which is located at: <portal-profile-home>\installedApps\<node>\PA_icWEFPtlts.ear\snor.pf.portlets.war\WEB-INF\lcaccelerator\properties.

    2. Set the openExternalLinksInNewWindow property to false.

    3. Save your change and restart WebSphere Portal.


    Enable logging for the Connections portlets

    In order to diagnose and resolve errors that occur with the Connections Portlets, you must enable logging.

    When you configure WebSphere Portal to write the trace and message logging for the Connections portlets, the messages are logged in the trace.log. The file is updated when an error occurs or if trace logs are created. The file is created in the following directory: <portal_server_root>\log. You can enable tracing for each portlet separately. The log classes used for the portlets are as follows:

      Activities portlet:

      • com.ibm.lconn.activities.detail
      • com.ibm.lconn.activities
      • com.ibm.lconn.commons.service
      • com.ibm.lconn.profiles.service

      Blogs portlet:

      • com.ibm.lconn.blog.detail
      • com.ibm.lconn.blog.summary
      • com.ibm.lconn.blog.service
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      Bookmarks portlet:

      • com.ibm.lconn.dogear.detail
      • com.ibm.lconn.dogear.summary
      • com.ibm.lconn.dogear.service
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      Profiles portlet:

      • com.ibm.lconn.profiles
      • com.ibm.lconn.profiles.summary
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      Tags portlet:

      • com.ibm.lconn.tagsi.service
      • com.ibm.lconn.common

      Wikis portlet:

      • com.ibm.lconn.wiki
      • com.ibm.lconn.wiki.service
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      Forums portlet:

      • com.ibm.lconn.forum.detail
      • com.ibm.lconn.forum.summary
      • com.ibm.lconn.forum.service
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      Community Overview portlet:

      • com.ibm.lconn.communityOverview
      • com.ibm.lconn.communityOverview.service
      • com.ibm.lconn.profiles.service
      • com.ibm.lconn.common

      VMM adapter:

      • com.ibm.ws.wim.adapter.connections.network.*
      • com.ibm.ws.wim.adapter.*
      • com.ibm.connections.vmm.adapter.filter.*

      The recommended logging level is all.

      For additional information on debugging issues with the Virtual Member Manager adapter, see this tech note.

      Connections Server: VMM adapter - Sonata Trace specification for sonata/authentication

      • com.ibm.connections.httpClient.*
      • com.ibm.connections.directory.services.*
      • com.ibm.ws.security.*
      • org.apache.commons.httpclient.*
      • SonataHttpHeader
      • SonataHttpBody

      Portal Server: VMM adapter - Sonata Trace specification for sonata/authentication

      • com.ibm.connections.httpClient.*
      • org.apache.commons.httpclient.*
      • SonataHttpHeader
      • SonataHttpBody

      Inter-portlet Navigation (Piece of Content handler)
      com.ibm.lconn.lcaccelerator.search.resolver.*

      The recommended logging level is all.

      Search center portlet (display provider):
      com.ibm.lconn.lcaccelerator.search.display.*

      The recommended logging level is all.

      Configuration Properties Helper:
      com.ibm.lconn.lcaccelerator.profiles.rep.*

      The Configuration Properties Helper retrieves all of the configuration settings from the Resource Environment Provider and makes them available to the portlets.

      Type-ahead:

      • com.ibm.connections.directory.services.*
      • com.ibm.connections.httpClient.*
      • com.ibm.websphere.wim.*
      • com.ibm.ws.wim.*

      The type-ahead builder is used to manage the members/owners. This uses the directory services to function. The recommended logging level is all.

      REST Call logging:

      1. Open the file <installed war>\WEB-INF\lcaccelerator\properties\loggerServiceMapping.properties

      2. Set the property TPA_REST_LOG_FLAG to true.

      3. Restart the Application war from the WAS admin console.

      This will enable logging of details of the REST service calls to a separate log file These logs will get generated at <installed war>/WEB-INF/logs/RESTCallLogs.log.

    You can specify the following log levels: info, fine, finer, finest, and all. To enable logging for one or more of the Connections portlets, do the following:

    1. Log into WebSphere Portal as the Administrator

    2. Navigate to Administration > Portal Analysis > Enable Tracing .

    3. In the Append these trace settings field, specify the log level for the desired log class and click the add button (+):

      For example, com.ibm.lconn.activities.summary=fine

    4. Repeat step 3 for each log class to log.

    5. Log out of portal and log back in.


    Example

    For example, if you wanted to enable the finest log level for the Activities Detail portlet, you would add these three logging settings:

    • com.ibm.lconn.activities.detail=finest
    • com.ibm.lconn.activities.service=finest
    • com.ibm.lconn.profiles.service=finest
    If you wanted to enable the fine log level for the Bookmarks Summary portlets, you would add these logging settings:

    • com.ibm.lconn.dogear.summary=fine
    • com.ibm.lconn.dogear.service=fine


    Pinning portlet content to a tag

    Specify a tag to pin for an Connections portlet to show content that is associated with that tag.

    If you want the content of a portlet scoped to a specific tag, you can set a page parameter to the tag.

    Each portlet can be pinned only to a single tag.

    1. Edit the portal page that contains the Connections portlets. For details on editing page parameters, see this Portal wiki article.

    2. Set the page parameter for each portlet to pin to a tag.


      Table 7. Tag pin parameters

      Portlet Parameter
      Activities Detail ibm.tag.pin.activities.detail
      Blogs Detail ibm.tag.pin.blogs.detail
      Blogs Summary ibm.tag.pin.blogs.summary
      Bookmarks Detail ibm.tag.pin.bookmarks.detail
      Bookmarks Summary ibm.tag.pin.bookmarks.summary
      Forums Detail ibm.tag.pin.forum.detail
      Forums Summary There is no page parameter for this portlet. You can set a pin option from the Edit Shared Settings panel.
      Wikis Detail ibm.tag.pin.wikis.detail
      Global Page Pin ibm.tag.pin.all

      Use the global tag pin to specify a common tag to use as a filter for all Connections portlets on the page. Tags that you specify for individual portlets override this global tag pin.

    3. Save the page changes.

    4. Log out of WebSphere Portal and then log back in to refresh the portlets so that you can see content that is pinned to the specified tag.


    Enable anonymous access

    By default, the pages that are deployed by the installer require authenticated access. You can optionally enable anonymous access to the pages and portlets.

    Enable or disable anonymous access for the sample pages and configure WebSphere Portal to enable sessions for all anonymous users.

    The Activity Stream portlet does not support anonymous access in this release.

    Enable anonymous access can significantly increase memory consumption and negatively affect performance.

    For more details, see the article about enabling anonymous access for WebSphere Portal.

    1. To enable anonymous access, run the following task to run the xmlaccess script. The task enables anonymous access on the sample pages and creates the public.session REP property in WP NavigatorService, setting the value to true.

      • Portal 8:
        ConfigEngine enable-anonymous-page-access \
             -DWasPassword=[wasadminpwd] \
             -DPortalAdminPwd=[portaladminpwd]
      • Portal 7:
        ConfigEngine enable-anonymous-page-access \
             -DPaaRootPath=C:\IBM\WebSphere\paa \
             -DWasPassword=[wasadminpwd] \
             -DPortalAdminPwd=[portaladminpwd]

    2. To disable anonymous access, run the following command:

      • Portal 8:
        ConfigEngine disable-anonymous-page-access \
             -DWasPassword=[wasadminpwd] \
             -DPortalAdminPwd=[portaladminpwd]
      • Portal 7:
        ConfigEngine disable-anonymous-page-access \
             -DPaaRootPath=C:\IBM\WebSphere\paa \
             -DWasPassword=[wasadminpwd] \
             -DPortalAdminPwd=[portaladminpwd]


    Disable redirect to Connections for content resolution

    Configure portlets to display an error page when a page cannot be found to render Connections content.

    By default, the portlets are configured to redirect users to Connections when a page in portal can't be found to render Connections content.

    1. Run this command to configure the portlets to redirect users to an error page in Portal when a page cannot be found to render Connections content:
       ConfigEngine disable-poc-redirect-to-connections \
           -DWasPassword=[was-admin-password]

    2. Run this command to re-enable the portlets to redirect users to Connections when a page in portal cannot be found to render Connections content:
        ConfigEngine enable-poc-redirect-to-connections -DWasPassword=[was-admin-password]


    Configure unique names

    Customize the default unique names for pages and the Connections portlet application ID for your environment to customize where users are redirected to render Connections content in WebSphere Portal.

    Use these steps for configuring unique names if you are deploying more than one of the same type of portlet on a page or if you want to deploy portlets to an existing page that already has a unique name.

    1. Run this command to customize page names:
       ConfigEngine poc-customize-unique-names \
           -DWasPassword=[was-admin-password]
      Use any of these optional parameters


      Table 8. To confirm changes made parameters for specifying unique page names

      Property Value
      -DICportletAppId Different Portlet App ID for the Connections Portlets if the default, com.bowstreet.portlet.WebAppRunner2_snor.pf.portlets, is customized.
      -DICpocErrorPageUniqueName Specifies the unique name for the error page users should be taken to in Portal when no page can be found to display content from Connections.
      -DICblogsStandalonePageUN Set the unique name of the page that contains the Blogs portlet. The default is ibm.conn.blogs.
      -DICwikisStandalonePageUN Set the unique name of the page that contains the Wikis portlet. The default is ibm.conn.wikis.
      -DICforumsStandalonePageUN Set the unique name of the page that contains the Forums portlet. The default is ibm.conn.forums.
      -DICactivitiesStandalonePageUN Set the unique name of the page that contains the Activities portlet. The default is ibm.conn.activities.
      -DICprofilesStandalonePageUN Set the unique name of the page that contains the Profiles portlet. The default is ibm.conn.profiles.
      -DICbookmarksStandalonePageUN Set the unique name of the page that contains the Bookmarks portlet. The default is ibm.conn.bookmarks.

    2. If you have multiple detail portlets that are deployed on a single stand-alone page, run the previous command and set the unique names for the pages to the same value.

      For example:

      ConfigEngine poc-customize-unique-names -DICblogsStandalonePageUN=ibm.conn.common.standalone.page -DICwikisStandalonePageUN=ibm.conn.common.standalone.page -DICprofilesStandalonePageUN=ibm.conn.common.standalone.page -DWasPassword=password
      This indicates that blogs, wikis, and profiles detail portlets are deployed on a page with the unique name ibm.conn.common.standalone.page.

    3. To remove the unique name customizations, run:
      ConfigEngine remove-poc-customized-unique-names -DWasPassword=[was-admin-password]


    Configure and wiring the Tags portlet

    After you install and deploy the Connections portlets, configure and wire the Tags portlet so it works in concert with other portlets in an IBM WebSphere Portal application.

    When you deploy the Tags portlet, note that if you are also deploying a Bookmarks portlet there is a difference in how tags display. The Bookmarks portlet by default returns active tags for the last 30 days. If this does not match what displays in the Tags portlet, you can change the configuration settings for Bookmarks.

    For example, you can increase the setting from 30 days to 180 days to display more tags.

    For information about changing the Bookmarks configuration, follow the steps in the topic Changing view and link thresholds and change the value of the sinceWhen.activeTags.

    Follow these steps to configure and wire the Connections Tags portlet.


    Wiring the Tags portlet

    The Tags portlet allows users to view content that is tagged with the tag selected from the portlet to aid in the discovery of content.

    Add the Connections portlets to a Portal page before you proceed with wiring. The Tags portlet must be deployed on the same page with at least one other Connections portlet. Read How the Tags portlet interacts with the other Connections portlets for information about how the Tags portlet communicates with the other Connections portlets.

    Follow these steps to wire the Tags portlet to other Connections portlets so that the Tags portlet can filter Connections content that is displayed in the other Connections portlets.

    Only the detail portlets can be wired to the Tags portlet. The summary portlets cannot be wired to the Tags portlet.

    1. From the Edit Layout page of the page that contains the Tags portlet and at least one other Connections detail portlet, click the Wires tab.

    2. Set the following wire from the Tags portlet to the corresponding Connections portlets on the page:

      Source Portlet Sending Target Page Target Portlet Receiving Wire Type
      Tags Selected Tag {current page} {Blogs|Profiles|Wikis|Bookmarks|Forums|Activities} Selected Tag Public

    3. Click Add.

    4. If you have the Tags portlet that is deployed on a page with one Connections detail portlet and want the Tags portlet to show tags that are associated with the view in the details portlet, set the following wire:

      Source Portlet Sending Target Page Target Portlet Receiving Wire Type
      {Blogs|Profiles|Wikis|Bookmarks|Forums|Activities} Tags Payload {current page} Tags Tags Payload Public

    5. Click Add.

    6. Click Done.


    How the Tags portlet interacts with the other Connections portlets

    This topic describes how the Tags portlet interacts with the other Connections portlets.

    The Connections Tags portlet allows users to locate content in the other Connections portlets (Activities, Blogs, Bookmarks, Wikis and Profiles). Selecting a tag from the Tags portlet causes the Connections portlets to reload to display the content from the Connections applications that are tagged with the selected tag. This interaction between the Tags portlet and other Connections portlets is enabled through portlet wiring to send the information that the Connections portlets must request the proper feeds filtered by the selected tag.

    There are two modes of operation with regards to the interaction between the tags and the other Connections portlets: one-way and two-way communication mode. In one-way communication mode, the Tags portlet sends a wire to the other Connections portlets to update their view according to a selected tag. In two-way communication mode, the other Connections portlets can also send a wire to the Tags portlet to update its view as well according to the view being displayed.

    Tags are not supported for Forums or Profiles that are deployed on a community page.


    One-way Communication Mode

    One-way communication mode is enabled when the Tags portlet is set to communicate with multiple instances of the Connections application portlets. This mode is enabled when more than one application is selected in the Shared Settings panel of the Tags portlet. In this mode, the Tags portlet uses the Connections home page Search API to obtain an aggregated tag feed of the selected applications using the search URL set in the Tags portlet configure panel. To properly configure one-way communication mode for tag filtering, the following items are required:

    1. The search URL is properly configured in the Tags portlet configuration panel.

    2. At least two applications that you want represented in the Tags must be selected in the Tags portlet shared settings panel.

    3. The wiring must be configured to send a wire from the Tags portlet to the applications selected in step 2.

      See Wiring the Connections portlets for instructions on how to set up portlet wiring.


    Two-way Communication Mode

    Two-way communication mode is enabled when the Tags portlet is set to communicate with a single Connections application portlet. This is enabled when only one application is selected in the Shared Settings panel of the Tags portlet. In this mode, the Tags portlet uses the corresponding application API to obtain the tag feed of the selected application using the application URL set in the Tags portlet configure panel. Like the one-way communication mode, the Tags portlet sends a wire to the Connections application portlet when a tag is selected. In addition, the Connections application portlet sends a wire to the Tags portlet to refresh the tags to show the tags relevant for the view selected. An example of this is when you drill down into an activity from the “My Activities” view in the Activities portlet, a wire is sent to the tags with information to show the tags specific to the activity selected. To properly configure two-way communication mode for tag filtering, the following items are required:

    1. The application URL of the Connections application you want to represent in the tags must be set in the Tags portlet configuration panel.

    2. The single application that you want represented in the tags must be selected in the Tags portlet shared settings panel.

    3. The wiring must be configured to send a wire from the Tags portlet to the Connections application selected in step 2 and the wiring from the Connections application portlet must be configured to send a wire to the Tags portlet to render tags for the view that is selected in the application portlet.

      See Wiring the Connections portlets for instructions on how to set up portlet wiring.


    Optimizing the page layout for the Tags portlet

    On WebSphere Portal, optimize the page layout to use a smaller column width for the Tags portlet.

    WebSphere Portal allows administrators and page editors to control the page layout for every page in the Portal environment. If the page layout includes a multi-column format, the size of each column can be set to optimize the layout to best accommodate the portlets on the page. The best layout of a page that contains the Connections tags portlet uses a smaller column width for the tags portlet that leaves more screen real estate for the main content portlets with which it interacts.

    1. Enable the Edit Layout portlet to display the option to control the column size.

      1. Log in to WebSphere Portal as the administrator

      2. In the Administration section, go to Portlet Management > Portlets.

      3. Locate the Edit Layout portlet. Search by title using edit layout as the search text.

      4. Click the Configure Portlet icon.

      5. Set showAdvancedOption to yes.

      6. Click OK to save the changes.

    2. Set the column size:

      1. Log in to WebSphere Portal as the administrator

      2. In the Administration section, click Portlet Management > Manage Pages.

      3. Open a page that contains the Tags portlet.

      4. Navigate to the page that contains the portlets and click the Edit Page Layout option for the page.

      5. Click Show layout tools.

      6. In the header of the column that contains the Tags portlet, click Not Set.

      7. Enter the pixel size for the width of the portlet.

        For example, 180 pixels.

      8. Click OK to save your settings.


    Addressing Connections content from a portlet

    Use custom URIs to identify, access, and display Connections in a portlet.

    Beginning with version 6.0.1, IBM WebSphere Portal uses Piece of Content (POC) URIs to identify and address specific pieces of content in Connections. Using a POC URI, you can precisely identify what content you want to display in a portlet.

    For example, when a user clicks a link in a blogs summary portlet, the POC URI identifies the blog content and displays it in the Blogs detail portlet. In earlier versions of Portal, this connection would be made using a standard URL to identify the target page of the content. URLs were limited and did not allow access to precise information about the state of a piece of content. The evolution to POC URIs provides a greater precision for identifying, retrieving, and displaying content. The URI specifies the identity of the content, not the location of the view of the document. The location of the view to the document is called the portal URL, or URL, and the information that is contained in this URL is the navigational state, or state.

    For detailed information about the creating and using custom URIs to access content, see the article Leveraging WebSphere Portal V6 programming model: Part 5. Accessing portal content with custom URLs on IBM developerWorks .


    Configure portlets to address content

    To configure the portlets so you can address content between them, edit environment variables.

    Use URIs to identify, access, and display Connections content and profiles in a portlet. IBM WebSphere Portal uses Piece of Content (POC) URIs to identify and address specific pieces of content in Connections independent of the page used display the content. Using a POC URI, you can precisely identify what content you want to display without knowing where it is displayed in your WebSphere Portal Server at the time you generate a link.

    For example, when a user clicks a link in a blogs summary portlet, the POC URI identifies the blog content. Clicking a link that uses a POC URI displays the blog entry in the Blogs detail portlet on the appropriate page. The evolution to POC URIs provides a greater precision for identifying, retrieving, and displaying content. The URI specifies the identity of the content, not the location of the view of the document. The location of the view to the document is called the portal URL, or URL, and the information that is contained in this URL includes the navigational state, or state.


    Configure navigation between portlets

    Use URIs to identify, access, and display Connections content and profiles in a portlet.

    Use URIs to identify, access, and display Connections content and profiles in a portlet. IBM WebSphere Portal uses Piece of Content (POC) URIs to identify and address specific pieces of content in Connections independent of the page used display the content. Using a POC URI, you can precisely identify what content you want to display without knowing where it is displayed in your WebSphere Portal Server at the time you generate a link.

    For example, when a user clicks a link in a blogs summary portlet, the POC URI identifies the blog content. Clicking a link that uses a POC URI displays the blog entry in the Blogs detail portlet on the appropriate page. The evolution to POC URIs provides a greater precision for identifying, retrieving, and displaying content. The URI specifies the identity of the content, not the location of the view of the document. The location of the view to the document is called the portal URL, or URL, and the information that is contained in this URL includes the navigational state, or state. When you work with a POC URI, you do not must be aware of the page in Portal where a piece of content displays, you must know some identifying data about the piece of content to create the URL. The correct WebSphere Portal page to display the content is retrieved after the user clicks a link using a POC URI format.

    The POC resolver handles navigation in following manner.

    • If the piece of content is community content:

      • Search the community page for a detail portlet to render the content.

      • If no static community page is found, search for a stand-alone page.

      • If no stand-alone page is found, navigate to an error page.

    • If the piece of content is from a stand-alone page rather than from a community:

      • Search the stand-alone page for a detail portlet to render the content.

      • If no stand-alone page is found, navigate to an error page.

    For detailed information about the creating and using custom URIs to access content, see the article Leveraging WebSphere Portal V6 programming model: Part 5. Accessing portal content with custom URLs on IBM developerWorks.

    The following steps are an example of how you can wire portlets in an application. You can apply these steps to wiring any of the Connections portlets in an application.

    1. To configure navigation to community pages, ensure that you have set the correct properties when you define the community page as described in Mapping a community page to a community.

    2. To configure navigation for content not inside a community, or for which a community page does not exist, ensure that you have create default pages for each service as described in Configuring the portlets on a page.

    You can configure and customize certain aspects that are related to navigation by editing the resource environment provider. For details, see Configure a resource environment provider for POC (Refresh).

    • Portlet IDs
    • Page names for stand-alone pages
    • Default page to display when a target page is not available


    Custom URI syntax

    Understand the syntax for creating a custom URI to access a piece of content.


    POC URI Syntax

    Construct a POC URI to address Connections content. The syntax has this form:

    connections:<atom_uri>&commID=<community_id>&service=<service_name>&type=<content_type>

    commID, service, and type must be specified as parameters. Parameter names are case sensitive.


    Parameters

      connections
      connections is the scheme that identifies the type of content the URI is locating.

      atom_uri
      The path portion of the URI used to fetch the atom document for the content.

      commID
      (optional) Community ID. Needs to be specified if the content is community-based.

      service
      Identifies the Connections service.

      type
      Identifies the content type.

      For example, an activity or a wiki page.


    Table 9. Connections services and types

    Service Type Type specific parameters Description
    activities activity Opens a particular activity, showing the outline page in the appropriate activities detail portlet
    item Opens the activity outline page for the activity containing this item in the activities portlet. The atom_uri may refer to an activity todo, entry, section, comment, chat communication, or email communication.
    blogs blog Opens particular blog in the appropriate blog details portlet
    entry Opens a particular blog entry in the appropriate blog details portlet
    communities community Opens the community page for this community if one is available, otherwise directs to the configured error page.
    forums forum Opens a particular forum in the appropriate forum details portlet
    topic forumUuid (optional) Opens a particular forum topic entry in the appropriate forums details portlet
    profiles profile Opens the profile detail in the profiles portlet
    wikis wiki Opens a particular wiki in the appropriate wiki details portlet
    page Opens a particular wiki page in the appropriate wiki details portlet
    file wikiLabel

    pageLabel

    Opens the attachments listing page for the parent wiki page in the wikis portlet. The atom_uri may be the URI of any attachment on the page, obtained from the attachment Atom entry. The portlet will list all attachments for that wiki page.


    POC Servlet

    The piece of content (POC) servlet checks for authentication. The /poc mapping does not require authentication but recognizes if valid authentication or single-signon information is present. If that case, the resolver framework will redirect to /myportal; otherwise, it redirects to /portal. In many usage scenarios it is appropriate to address the /poc mapping, because it detects potential authentication information automatically. In any case, access control to the actual page and portlets to which the POC URI resolves is enforced by the portal. The POC servlet default path is

    http://<server>:<port>/wps/poc?uri= 

    Use the POC Servlet with the POC URI to access content as follows:

    POC URI:http://<server>:<port>/wps/poc?uri=connections:<atom_uri>&commID=<community_id>&service=<service_name>&type=<content_type>


    Sample URI

    POC URI to address a forum topic:
    http://<server>:<port>/wps/poc?uri=connections:forums/atom/topic?topicUuid=da99c49f-d2d0-47d9-9f18-1f32cf9e108c&type=topic&service=forums&commID=9425353dfea-484c-1234-1f2f7d51e517&forumUuid=6864a28b-dfea-484c-9fd8-1f2f7d51e517
    
    
    
     
    
    
    


    Connections Desktop Plug-ins for Microsoft Windows

    Use the plug-ins to share files and information between Microsoft Windows applications and Connections or IBM SmartCloud.

    The following features are available from Microsoft Windows Explorer:

    • Upload local files to Connections or IBM SmartCloud from Windows Explorer or from your desktop
    • Share uploaded files with people or communities in Connections or IBM SmartCloud
    • Work on files locally and publish them to Connections or IBM SmartCloud
    • View people's contact details and get in touch with them
    • Pin, follow, or like files and folders
    • View or contribute comments for a file
    • Lock a file when you are editing it to prevent file conflicts
    • View and restore files from the trash
    • Share folders with Communities

    The following features from Microsoft Office (Word, Excel, PowerPoint):

    • Features added to Word:

      • Add a document to Files or Communities

      • Attach a document to an Activity or Wiki page
      • Publish a document to a Blog entry

      • Add someone's profile information from Connections into a document

      • Add a bookmark from Connections into a document

      • Add a URL from a document as a bookmark in Connections

      • Search for content in Connections
    • Features added to PowerPoint:

      • Add a presentation to Files or Communities

      • Attach a presentation to an Activity or Wiki page

      • Search for content in Connections
    • Features added to Excel:

      • Add a spreadsheet to Files or Communities

      • Attach a spreadsheet to an Activity or Wiki page

      • Search for content in Connections

    The following features are available from Microsoft Outlook:

    • Add an email to Files or Communities

    • Attach an email to an activity or wiki page

    • Search for content in Connections
    • View social activities for email recipients and people in your network

    • Invite people to your Connections network
    • View Connections Business Card for email senders and recipients in Outlook 2010

    If you previously installed any version of the Connections Plug-in for Microsoft Office and Microsoft Windows, installing this plug-in silently removes the Microsoft Explorer features from the older plug-ins.

    You have two options for installing the plug-in. Individual users can install the plug-in, or you can perform a silent installation to install the plug-in for a group of users.


    Performing a user installation

    Users can install the IBM Desktops plug-ins for Microsoft Windows following these steps.

    When you install the plug-in, you can choose to install all components, or customize the installation. You must at least install the plug-in for Microsoft Windows Explorer. If you are using this plug-in with IBM SmartCloud rather than with Connections, you can run the installation command from a command line and specify a parameter that loads a profile which will change some of the branding in the user interface from Connections to IBM SmartCloud.

    1. Download the plug-in from the Connections catalog at the following website:
       https://greenhouse.lotus.com/catalog
    2. Extract the file.

    3. Double-click IBMConnectionsDesktop.exe to launch the installation program.

    4. If you only want the install the plug-in for Microsoft Explorer, choose not to install the Microsoft Office or Microsoft Outlook plug-ins. In the Custom Setup panel, click the icon next to Microsoft Office or Microsoft Outlook, and then click This feature will not be available to not install those plug-ins. The Microsoft Explorer plug-in is always installed.

    5. Click Finish to complete the installation.

    6. If prompted, reboot your computer.

    To change the branding so that IBM SmartCloud rather than Connections displays in the Microsoft Office ribbon, the navigator in Windows Explorer, and context menus, install as follows:

    1. Open a command window.

    2. Open a command prompt and navigate to the directory where you saved IBMConnectionsDesktop.exe.

    3. Enter the following command:
      IBMConnectionsDesktop.exe -smartCloudProfile
    4. Complete the rest of the installation.
    5. Reboot the system.

    To restore the original branding, load the default profile, which displays Connections in the user interface.

    1. Open a command window and navigate to the directory where the Connections Desktop Plug-ins for Microsoft Windows is installed.

      For example, C:\IBM\Connections Desktop Plugins.

    2. Enter the following command:
      DIConfig.exe -defaultProfile
    3. Reboot the system.


    Performing a silent installation

    Administrators can silently upgrade or install the Connections Desktop Plug-ins for Microsoft Windows from the command prompt. User notification is disabled during the silent installation, except in error cases such as notification of failed prerequisites.

    A silent installation uses the same installation program that the graphical user interface (GUI) version uses. However, instead of displaying a wizard interface, the silent installation reads all of your responses from parameters that you pass to the command line. In order for the installation to work successfully, you must run the silent installation from the directory where you extracted the plug-in files.

    1. Download the plug-in from the Connections catalog at the following website:
       https://greenhouse.lotus.com/catalog
    2. Extract the file.

    3. Open a command prompt and navigate to the directory where you saved IBMConnectionsDesktop.exe.

    4. Type IBMConnectionsDesktop.exe /Options(s) [PROPERTY=Value] The optional parameters and public property settings are listed in the following tables:


      Table 10. To confirm changes made parameters

      To confirm changes made parameters Description
      /install Install the plug-in.
      /uninstall Uninstalls the plug-in.
      /quiet Establishes Silent mode, which requires no user interaction.
      /norestart Prevents restart after the installation is complete.
      /promptrestart Prompts the user for restart if necessary.
      /forcerestart Always restarts the computer after installation.


      Table 11. Public properties

      Public property Description
      INSTALLDIR Directory where plug-ins are installed.

      For example,

      INSTALLDIR=C:\Progra~1\IBM\Connections Desktop Plugins
      ADDLOCAL To confirm changes made ly install components. If nothing is specified, all components are installed. The Windows Explorer feature is required and is always installed. Examples:

      • To silently install just the Microsoft Windows Explorer feature:
        IBMConnectionsDeskTop.exe /install /quiet ADDLOCAL=WindowsExplorer

      • To silently install the Microsoft Office feature:
        IBMConnectionsDeskTop.exe /install /quiet ADDLOCAL=WindowsExplorer,MicrosoftOffice

      • To silently install the Microsoft Outlook feature:
        IBMConnectionsDeskTop.exe /install /quiet ADDLOCAL=WindowsExplorer,MicrosoftOutlook

      • To disable Connections 3.0 or 3.01 features on Microsoft Window Explorers desktop:
        IBMConnectionsDeskTop.exe /install /quiet DSB_MS30X_EXPLORER

      • To disable Connections 3.0 or 3.01 features on Microsoft Window Explorers and install the Connections 4.5 plug-ins features for Windows Explorer:
        IBMConnectionsDeskTop.exe /install /quiet ADDLOCAL=WindowsExplorer DSB_MS30X_EXPLORER
      DSB_MS30X_EXPLORER If you previously installed an earlier version of the Connections 3.0.1 plug-in for Microsoft Office and Microsoft Windows, this option disables rather than uninstalls plug-in features. If this option is not specified, the earlier features are uninstalled silently.

      • To disable Windows Explorer features of the Connections 3.0.1 plug-in for Microsoft Office and Microsoft Windows and install all components of the Connections 4.5 plug-in:
        IBMConnectionsDeskTop.exe /install /quiet DSB_MS30X_EXPLORER

      • To disable Windows Explorer features of the Connections 3.0 or 3.0.1 plug-in and install the Windows Explorer feature of Connections 4.5 plug-in:
        IBMConnectionsDeskTop.exe /install /quiet ADDLOCAL=WindowsExplorer DSB_MS30X_EXPLORER
      -smartCloudProfile If you are using this plug-in with IBM SmartCloud rather than with Connections, you can run the installation command from a command line and specify a parameter that loads a profile which will change some of the branding in the user interface from Connections to IBM SmartCloud.
      IBMConnectionsDeskTop.exe /install /quiet -smartCloudProfile

      If you install with this profile, IBM SmartCloud displays instead of Connections in the Microsoft Office ribbon, in the navigation pane for Windows Explorer, and in context menus.


      Table 12. Samples of silent installation commands

      Description Example
      Silent installation with restart and INSTALLDIR property
      IBMConnectionsDesktop.exe /install /quiet /forcerestart
      INSTALLDIR=C:\Progra~1\IBM\Sample
      Silent uninstall with no restart
      IBMConnectionsDesktop.exe /uninstall /quiet /norestart 

    5. Reboot the computer.


    Repairing or removing the Connections Desktop plug-ins

    Users experiencing problems with the plug-in can use the Repair function to correct it or use the Remove feature to uninstall the plug-in.

    1. Navigate to the Add/Remove Programs panel from your Microsoft Windows control panel.

    2. Select Connections Desktop Plug-ins for Microsoft Windows and choose one of the following:

      1. Select Change , then Next, and finally Repair to correct an installation.

      2. Select Remove to remove the plug-in from your system.

    3. Confirm your choice and complete the operation.
    4. Reboot your computer.


    Update the desktop plug-ins configuration data

    Use a configuration tool to update the Connections Desktop Plug-ins for Microsoft Windows after you migrate from an Connections 3.0.1.1 server to a Connections 4.x server, or to configure client support for some of the Connections components.

    If you are using the Connections Desktop Plug-ins for Microsoft Windows and you switch from a Connections 3.0.1.1 server to a Connections 4.5 server, you must run a configuration tool to refresh the plug-in features. If not, you might experience some unexpected behavior.

    For example, file locking does not work properly and you cannot see the file locking details when you inspect the properties of a file.

    You can also use the configuration tool to configure client support for Connections components. Perform this operation for each user account whenever you remove a component from or add a component to a Connections server. These are the components you can add or remove.

    • Bookmarks

    • Activities
    • Blogs

    • Search
    • Wikis

    Component names are not case-sensitive.

    Depending on how you are using the plug-ins, you might want to load a profile that customizes the branding for a deployment.

    For example, if you are connecting to an IBM SmartCloud server rather than to Connections, you can load a profile that replaces the Connections string with IBM SmartCloud in some parts of the user interface, such as the tab name in the Microsoft Office ribbon

    1. Open a command window and navigate to the directory where the Connections Desktop Plug-ins for Microsoft Windows is installed.

      For example, C:\IBM\Connections Desktop Plugins

    2. Enter DIConfig and specify any of the following options:

        -version version_number
        Specify either 3.0.1.1 or 4.5 to change the server version.

        For example,

        DIConfig.exe https://enterprise.example.com -version 4.5

        -addComponent component_name component_url component_url2
        Specify the component name and the component URL.

        For example,

         DIConfig.exe https://enterprise.example.com -addComponent Activities https://enterprise.example.com/activities 

        If you are adding Bookmarks, specify the Bookmarks component as the first URL and the URL for the bookmarklet that controls the Add Bookmark browser button as the second.

        For example:

         DIConfig.exe https://enterprise.example.com \
             -addComponent Bookmarks https://enterprise.example.com/dogear https://enterprise.example.com/bookmarklet

        -removecomponent component_name
        Specify the component name to be removed from the configuration.

        For example,

        DIConfig.exe https://enterprise.example.com -removeComponent Activities

        -smartCloudProfile
        Load a profile that replaces Connections in top-level menus with IBM SmartCloud.

        For example,

        DIConfig.exe -smartCloudProfile 
        This replaces Connections with IBM SmartCloud as the name of the tab in the Microsoft Office ribbon, in the context menus, and the Microsoft Windows navigation pane.

        Reboot after you run this option.

        -defaultProfile
        If you loaded a different profile to customize the branding of the plug-in, load the default profile that displays Connections in the Microsoft Office ribbon and context menus.

        For example,

        DIConfig.exe -defaultProfile 
        Replaces IBM SmartCloud with Connections as the name of the tab in the Microsoft Office ribbon, in the context menus, and the Microsoft Windows navigation pane.

        Reboot after you run this option.

    3. Repeat steps 1-2 for each desktop user account that is configured to use the desktop plug-ins.


    Preferences and policies for the Connections Desktop Plug-ins for Microsoft Windows

    Set preferences and policies to control how users interact with the Connections Desktop plug-in for Microsoft Windows.

    The following table shows preference and policy settings that control the behavior of the Connections Desktop plug-in for Microsoft Windows. These registry values are not created during installation. You must create the keys/values as needed. If a key/value does not exist, the appropriate default is assumed. Setting values to anything other than the values listed in the table produces unpredictable results.

    For 64-bit computers, the registry settings are stored in HKLM/SOFTWARE/Wow6432Node/IBM instead of in HKLM/SOFTWARE/IBM (used for 32-bit computers).


    Table 13. Registry keys for Connections Desktop plug-in for Microsoft Windows.

    Enter registry keys with no line breaks. They are formatted for readability in the tables.

    Key/SubKey:

    (HKLM/SOFTWARE/IBM) or

    (HKLM/SOFTWARE/Wow6432Node/IBM on 64-bit)

    Name (Type = String) Values Description
    Social Connectors/Settings Hide ShellExt 0 – Display Context Menu (Default)

    1 – Do not display Context Menu

    Controls the default visibility preference of the Windows Explorer context menu extension.

    Set this value overrides a user preference if the policy is also set to Disable (value = 1)

    Social Connectors/Settings Hide ShellExt Policy 0 – Enable Preference (Default)

    1 – Disable Preference

    Controls whether users can modify the preferences value.

    HKCU/SOFTWARE/Microsoft/Windows/

    CurrentVersion/Explorer/

    HideDesktopIcons/ClassicStartMenu

    32-bit OS {A0D85EDF-50B5-4B12-9D74-0D69E6729A11}

    64-bit OS {21034BDC-B57E-400b-A5D5-2B1E98502805} Type = DWORD

    0 – Show (Default)

    1 – Hide

    Controls hiding of the Desktop Icon when using the classic Start Menu. This must be set per user (HKCU).

    HKCU/SOFTWARE/Microsoft/

    Windows/CurrentVersion/Explorer/

    HideDesktopIcons/NewStartPanel

    32-bit OS {A0D85EDF-50B5-4B12-9D74-0D69E6729A11} 64-bit OS {21034BDC-B57E-400b-A5D5-2B1E98502805} Type = DWORD 0 – Show (Default)

    1 – Hide

    Controls hiding of the Desktop Icon when using the default Start Menu. This must be set per user (HKCU).
    Social Connectors/Settings Hide Desktop Icon Policy 0 – Enable Preference (Default)

    1 – Disable Preference

    Controls whether users can modify the value via the General tab of the Preferences dialog.
    Social Connectors/Settings SendLink MailApp mailto – Use mailto: protocol <MAPI program> - Registered name of email program

    Example: IBM Notes

    Set the default email application in the General tab of the Preferences dialog.

    If set to mailto the mailto: protocol is used instead of MAPI.

    Social Connectors/Settings UnpublishedPrompt 0 – Do not display prompt

    1 – Display prompt (Default)

    Controls the default setting of the unpublished draft warning.

    Set this value will override the user's preference if the policy is also set to Disabled.

    Social Connectors/Settings UnpublishedPrompt Policy 0 – Allow Hiding (Default)

    1 – Disable Hiding

    Controls whether end users can elect to hide the unpublished draft warning.
    Social Connectors/Settings ShowInfoBubbles 0 – Do not show Alerts

    1 – Show Alerts (Default)

    Controls the default setting for alerting that local drafts need to be saved.
    Social Connectors/Settings ShowInfoBubbles Policy 0 – Enable Preference (Default)

    1 – Disable Preference

    Controls whether users can change the ShowInfoBubbles preference.
    Social Connectors/Settings MonitorWarnOnClose 0 – Do not warn on close

    1 – Warn on close (Default)

    Controls display of warning message when drafts monitor is closed.
    Social Connectors/Settings MonitorWarnOnClose Policy 0 – Enable Preference (Default)

    1 – Disable Preference

    Controls whether warning dialog can be suppressed by users.
    Social Connectors/Settings EnableCacheCleanup 0 – Disable Cache Cleanup (Default)

    1 – Enable Cache Cleanup

    Default setting for enabling/disabling cache cleanup.
    Social Connectors/Settings EnableCacheCleanup Policy 0 – Enable Preferences (Default)

    1 – Disable Preferences

    Controls whether users can change any of the Cache settings.
    Social Connectors/Settings CacheAge <days> - number of days

    Min – 1 (Default)

    Max – 100

    Files not accessed within the specified number of days will be deleted.
    Social Connectors/Settings CacheFrequency <minutes> - number of minutes

    Min – 5

    Max – 1,440

    Default –120

    How often to check temporary files in minutes.
    Social Connectors/Settings ScanIgnoreExtensions <Comma separated extensions> List of extensions to ignore changes on. This list will be merged with any user preferences unless the policy is set to Disable.

    Example: gif, jpeg, mpg

    Change this setting requires that you restart your computer for the changes to take effect.

    Social Connectors/Settings ScanIgnoreExtensions Policy 0 – Enable Preference (Default)

    1 – Disable Preference

    Set the policy to disable will prevent users from adding file extensions to the ignore list.
    Social Connectors/Settings Password Save Policy 0 – Allow Saving (Default)

    1 – Do not Allow Saving

    Controls whether users can persist passwords locally. Passwords are stored in the Windows Credential Store.
    Social Connectors/Settings Default Auth Type 0 – Basic Authentication (Default)

    1 – Custom

    Controls the default authentication type in the Add Site dialog.
    Social Connectors/Settings Default Auth Type Policy 0 – Enable Authentication dropdown (default)

    1 – Disable Authentication dropdown

    Set the policy to disable will prevent users from selecting and changing the authentication type in the Add Site dialog.
    Social Connectors/Settings Default Auth Ext {EA483EAD-9E64-4ECC-BDDD-BF8B1D72A1C6} – Siteminder

    {4B9448AB-DF3D-4859-A3CA-365389096497} – SPNEGO

    {B5BAD66C-CF6F-4FA5-9BC7-EF36C76D331A} – TAM

    {FB5CF435-95ED-4FE6-BB7D-95F82DB65C5C} – TAM+SPNEGO

    {CCD9158D-BCD9-4DCD-81B2-48E21D670F5C} – SiteMinder+SPNEGO

    Controls which custom authentication module will display by default.

    For example, to use Tivoli Access Manger authentication, set this to {B5BAD66C-CF6F-4FA5-9BC7-EF36C76D331A} and then set Default Auth Type to Custom.

    Social Connectors BasicAuthEncoding (Type is DWORD) 28591 - (ISO8895-1) (Default)

    65001 - (UTF8)

    Select encoding type for credentials when using basic authentication.
    Social Connectors LFFilesRoot <path to existing directory>

    %HOMEPATH%\ LFFiles (Default)

    Default root directory for downloaded files. This must be set to a non-shared local directory on the client system. Once set, it only affects newly added servers, communities, or people.

    Change this setting requires that you restart your computer for the changes to take effect.

    Social Connectors/Settings Disable Activities String

    Default – null (not in registry)

    0 – Enable Activities (Default)

    1 – Disable Activities

    Set this value to 1 hides all of the user interface options related to the Activities feature, such as Add to Activities.

    This setting affects the Explorer, Office, and Outlook plug-ins.

    You might use this setting if you have no sites available that support Activities.

    Social Connectors/Settings Disable Blogs String

    Default – null (not in registry)

    0 – Enable Blogs (Default)

    1 – Disable Blogs

    Set this value to 1 hides all of the user interface options related to the Blogs feature, such as Add to Blogs.

    Menu items and ribbon controls will be hidden.

    This setting affects the Explorer, Office, and Outlook plug-ins

    You might use this setting if you have no Sites available that support Blogs.

    Social Connectors/Settings Disable Bookmarks String

    Default – null (not in registry)

    0 – Enable Bookmarks (Default)

    1 – Disable Bookmarks

    Set this value to 1 hides all of the user interface options related to the Bookmarks feature, such as Insert Bookmark.

    Menu items and ribbon controls are hidden.

    This setting affects the Explorer, Office, and Outlook plug-ins

    You might use this setting if you have no Sites available that support Bookmarks.

    Social Connectors/Settings Disable Profiles String

    Default – null (not in registry)

    0 – Enable Profiles (Default)

    1 – Disable Profiles

    Set this value to 1 disables all of the user interface options related to the Profiles feature, such as Invite to my network.

    Menu items and ribbon controls are visible but disabled.

    This setting affects the Explorer, Office, and Outlook plug-ins.

    You might use this setting if you have no Sites available that support Profiles.

    Social Connectors/Settings Disable Wikis String

    Default – null (not in registry)

    0 – Enable Wikis (Default)

    1 – Disable Wikis

    Set this value to 1 hides all of the user interface options related to the Wikis feature, such as Add to Wikis.

    Menu items and ribbon controls are hidden.

    This setting affects the Explorer, Office, and Outlook plug-ins.

    You might use this setting if you have no Sites available that support Wikis.

    Social Connectors/Settings Disable Search String

    Default – null (not in registry)

    0 – Enable Search (Default)

    1 – Disable Search

    Set this value to 1 hides all of the user interface options related to the Search feature.

    Menu items and ribbon controls are hidden.

    This setting affects the Explorer, Office, and Outlook plug-ins

    You might use this setting if you have no Search service available.

    Social Connectors/Settings Disable Community Bookmarks String

    Default – null (not in registry)

    0 = community bookmarks enabled, allows adding bookmarks to community bookmarks (Default)

    1 = community bookmarks disabled, prohibits adding bookmarks to community bookmarks.

    Set this value to 1 hides all of the user interface options related to the Community bookmarks feature.

    Menu items and ribbon controls are hidden.

    This setting affects the Office plug-ins.

    You might use this setting if you have no Communities support or no Community Bookmarks support.

    Social Connectors/Settings Disable Groups String

    Default – null (not in registry)

    0 = groups enabled, allows sharing with Groups where appropriate in sharing dialogs (Default)

    1 = groups disabled, will disable sharing with groups where appropriate in sharing dialogs

    This setting disables the ability for users to share with groups. This corresponds to the server policy.

    There is no "Disable Groups Policy" setting.

    Social Connectors/Settings Disable Public Sharing String

    Default – null (not in registry)

    Default behavior is enabled for public sharing

    0 = public sharing enabled, will allow sharing with Everyone (Public) or Everyone in Organization (for SmartCloud) where appropriate in sharing dialogs (Default)

    1 = public sharing disabled, disables sharing with Everyone (Public) or Everyone in Organization (for SmartCloud) where appropriate in sharing dialogs

    This setting disables the ability for users to share with Everyone (Public) for Connections, or with Everyone in Organization for SmartCloud.

    There is no "Disable Public Sharing Policy.”

    Social Connectors/Settings Sharing Intent String Default – null (not in registry)

    Default behavior is Sharing Intent enabled

    0 = sharing intent setting is not checked

    1 = sharing intent setting is checked (Default)

    This setting sets the default value for the sharing intent setting on new file and new folder dialogs.
    Social Connectors/Settings Sharing Intent Policy String

    Default – null (not in registry)

    0 = user can change the sharing intent setting (Default)

    1 = user cannot change the sharing intent setting

    This setting controls whether the user can change the default value for the sharing intent setting on new file and new folder dialogs. If the policy is set, the user cannot change the setting.
    Social Connectors/Settings Sharing Propagation String

    Default – null (not in registry)

    0 = sharing propagation setting is not checked

    1 = sharing propagation setting is checked (Default)

    This setting sets the default value for the sharing propagation setting on new file and new folder and sharing dialogs.
    Social Connectors/Settings Sharing Propagation Policy String

    Default – null (not in registry)

    0 = user can change the sharing propagation setting (Default)

    1 = user cannot change the sharing propagation setting

    This setting controls whether the user can change the default value for the sharing propagation setting on new file and new folder and sharing dialogs. If the policy is set, the user cannot change the setting.
    Social Connectors/Settings Encryption String

    Default – null (not in registry)

    0 = Encryption setting is checked

    1 = Encryption setting is not checked (Default)

    This setting sets the default value for the Encryption setting on New File dialogs.
    Social Connectors/Settings Encryption Policy String

    Default – null (not in registry)

    0 = user can change the Encryption setting (Default)

    1 = user cannot change the Encryption setting

    This setting controls whether the user can change the default value for the Encryption setting on New File dialogs. If the policy is set, the user cannot change the setting.
    Social Connectors/Settings DefaultConnectURL <server url> Enter the URL to use as the default site URL in the Connect to a Site dialog.
    Social Connectors/Settings DefaultConnectName <server display name> This display name is the default server display name in the Connect to a Site dialog.
    Social Connectors/Settings Help URL

    http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Using_the_IBM_Connections_Desktop_Plugins_for_Microsoft_Windows_lv45 (Default)

    “http://” or “https://” is required as part of the url

    The url for help for the entire product.
    Social Connectors/Settings HelpConnectURL

    http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Using_the_IBM_Connections_Desktop_Plugins_for_Microsoft_Windows_lv45 (Default)

    “http://” or “https://” is required as part of the url

    The URL for help on the Connect to Site dialog. This setting overrides the setting for HelpURL
    Software\IBM\Social Connectors\Settings DefaultConnectURL String

    Default - null

    The URL that shows by default in the Connect to Site dialog for a new server.
    Software\IBM\Social Connectors\Settings DefaultConnectName String

    Default - null

    The name that will show by default in the Connect to Site dialog for a new server


    Table 14. Outlook Social Connector Settings Default settings

    Key/SubKey (HKLM/SOFTWARE/IBM) or (HKLM/SOFTWARE/Wow6432Node/IBM on 64-bit) Name (Type = String) Values Description
    Social Connectors/Office/OSC MaxFriends <friends> - number of friends

    Min – 100

    Max – 9999

    Default - 500

    Maximum number of friends that can be downloaded from the user's network to create outlook contacts. Values that are entered are rounded up to the next 100.

    For example, 111 would be treated as 200.

    Social Connectors/Office/OSC MaxNews <items> - number of news items

    Min – 100

    Max – 9999

    Default - 500

    Maximum number of activities that are downloaded from the news feed and stored in the outlook cache via OSC framework. Values that are entered are rounded up to the next 100.

    For example, 111 would be treated as 200.

    Social Connectors/Office/OSC DaysSince Min – 1

    Max – 14599 (year 1970)

    Default - 14

    When you receive news activities, this setting specifies how many days to go back in time from the current day.
    Social Connectors/Office/OSC HashedSearchParm hashEmail The name of the property in a users profile to compare with the HashEmail. Can be used to test hash email lookup is working when server cannot be configured
    Social Connectors/Office/OSC HashFunction Default – SHA1

    Other values are MD5 or CRC32MD5

    The hash algorithm used compare the email addresses. This value is passed to Outlook and it returns a hashed value of the email address using this type.
    Social Connectors/Office/OSC EnableDynamicActivities 0 – Disable DynActivities (Default)

    1 – Enable DynActivities

    Enable getting dynamic news items for users. This setting requires that the server be configured to handle the Hashed SearchParam
    Social Connectors/Office/OSC EnableDynamicContacts 0 – Disable DynContacts (Default)

    1 – Enable DynContacts

    Enable getting dynamic contacts. This setting requires that the server be configured to handle the Hashed SearchParam
    Social Connectors/Office/OSC EnableContacts 0 – Disable Contacts (Default)

    1 – Enable Contacts

    Get contacts for Profiles Network and create Outlook contacts


    Table 15. Outlook Social Connector Settings per host name (Provider) overrides of Default values. This allows per server settings.

    Key/SubKey (HKLM/SOFTWARE/IBM) or (HKLM/SOFTWARE/Wow6432Node/IBM on 64-bit) Name (Type = String) Values Description
    Social Connectors/Office/OSC MaxFriends <friends> - number of friends

    Min – 100

    Max – 9999

    Default - 500

    Maximum number of friends that can be downloaded from the user's network to create outlook contacts. Values that are entered are rounded up to the next 100.

    For example, 111 would be treated as 200.

    Social Connectors/Office/OSC MaxNews <items> - number of news items

    Min – 100

    Max – 9999

    Default - 500

    Maximum number of activities that are downloaded from the news feed. These are stored in the outlook cache via OSC framework. Values that are entered are rounded up to the next 100.

    For example, 111 would be treated as 200.

    Social Connectors/Office/OSC DaysSince Min – 1

    Max – 14599 (year 1970)

    Default - 14

    When you subscribe to news activities, this setting specifies how many days to go back in time from the current day.
    Social Connectors/Office/OSC HashedSearchParm Default - hashEmail The name of the property in a users profile to compare with the HashEmail. Can be used to test hash email lookup is working when server cannot be configured.
    Social Connectors/Office/OSC HashFunction Default – SHA1

    Other values are MD5 or CRC32MD5

    The hash algorithm used compare the email addresses. This value is passed to Outlook and it returns a hashed value of the email address using this type.
    Social Connectors/Office/OSC EnableDynamicActivities 0 – Disable DynActivities (Default)

    1 – Enable DynActivities

    Enable getting dynamic news items for users. This setting requires that the server be configured to handle the Hashed SearchParam.
    Social Connectors/Office/OSC EnableDynamicContacts 0 – Disable DynContacts (Default)

    1 – Enable DynContacts

    Enable getting dynamic contacts. This setting requires that the server be configured to handle the Hashed SearchParam.
    Social Connectors/Office/OSC EnableContacts 0 – Disable Contacts

    1 – Enable Contacts (Default)

    Get contacts for Profiles Network and create Outlook contacts.


    Manage policies and preferences with a group policy

    Use a group policy administrative template to manage preferences and policies across an enterprise.

    To set policies and preferences for a group of users, use the Group Policy Administrative Template. This console provides a single user interface through which to manage Group Policy across an enterprise. To use the template, load it into the Group Policy Management Console snap-in.

    1. To start the Group Policy Management Console, open a command line window and enter gpedit.msc .

    2. Select Computer Configuration > Administrative Templates.

    3. Right-click on the Administrative Templates node and select Add/Remove Templates.

    4. Select Add.

    5. Navigate to the installation directory for the plug-ins.

      For example, C:\(x86)\IBM\Connections Desktop Plugins.

    6. Select the appropriate template for your Windows version (

      For example, IBMConnections.adm or IBMConnections64.adm).


    Results

    There will be two newly created nodes with the following new entries:

    • Computer Configuration > Administrative Templates > Classic Administrative Templates (Admgr) > Connections Desktop Plug-ins for Microsoft Windows

      • Temporary File Cleanup - Enable/Disable Cleanup
      • Temporary File Cleanup - Policy
      • Temporary File Cleanup - Minimum File Access Time
      • Temporary File Cleanup - Cleanup Frequency
      • Hide Shell Extension
      • Hide Shell Extension - Policy
      • Hide Desktop Icon - Policy
      • Hide Desktop Icon - New Start Panel
      • Hide Desktop Icon - Classic Start Menu
      • SendLink MailApp
      • SendLink MailApp - Policy
      • Unpublished Prompt
      • Unpublished Prompt - Policy
      • Show Information Bubbles
      • Show Information Bubbles - Policy
      • Monitor Warn On Close
      • Monitor Warn On Close - Policy
      • Scan Ignore Extensions
      • Scan Ignore Extensions - Policy

      • Password Save - Policy
      • Default Authentication Type
      • Default Authentication Extension
      • Basic Authentication Encoding Type
      • Cache Directory Root
      • Help URL
      • Connect to Site Help URL
      • Connect to Site Server URL
      • Connect to Site Server Name
      • OSC - Maximum Number of Friends
      • OSC - Maximum Number of News Items
      • OSC - Period of Time for News Feed
      • OSC - Hash Search Parameter
      • OSC - Hashed Email Function
      • OSC - Enable Dynamic Activities
      • OSC - Enable Dynamic Contacts
      • OSC - Enable Contacts

      • Disable Activities Support

      • Disable Blogs Support

      • Disable Wikis Support

      • Disable Bookmarks Support

      • Disable Community Bookmarks Support

      • Disable Profiles Support

      • Disable Search Support
      • Encrypt Files
      • Encrypt Files -Policy
      • Share Intent
      • Share Intent - Policy
      • Share Propagation
      • Share Propagation - Policy

      • Disable Groups Support

      • Disable Public Sharing Support

    • User Configuration > Administrative Templates > Classic Administrative Templates (Admgr) > Connections Desktop Plug-ins for Microsoft Windows

      • Hide Desktop Icon - New Start Panel
      • Hide Desktop Icon - Classic Start Menu


    Configure dynamic feeds for the Outlook Social Connector

    Configure the Connections Profiles server and the Connections Outlook Social Connector provider to support dynamic feeds to bring data from Connections to the outlook client via the Microsoft Outlook Social Connector.

    By default, the Connections OSC provider does not have the dynamic contacts capabilities enabled. The Connections server must be configured to support this feature. Dynamic contacts capability can potentially make many server requests and so server load is reduced by disabling the capability until the server supports the required information.

    Dynamic contacts are those members not in the authenticated user’s network. As Microsoft Outlook switches emails, the sender’s email address is sent to the OSC providers to check whether that email address exists on the server. The Connections server must do an additional step to populate its repository with a hash of the Profiles members email address. For security purposes, the OSC does not provide the email address in plain text. Instead, it is hashed according to your specified function, either as MD5 or SHA1. To improve efficiency, the Connections OSC provider designates any hashed email address as not available when the server returns no information for that address. This hashed email address is kept in memory for the life of the Microsoft Outlook process and is not requested again until Microsoft Outlook restarts.

    To enable the dynamic features for the Connections OSC provider, create the following registry settings that are described in detail in the topic Connections 4 IBM Preferences and policies for the Connections Desktop Plug-ins for Microsoft Windows.

    • Dynamic Contact Lookup – This dynamic feature allows the authenticated user to look up the picture, name, and job title for the OSC user.
    • Dynamic Contact Activities – This dynamic feature allows the authenticated user to retrieve the activities for the OSC user.


    Configure the Profiles server to support feeds

    Configure the Connections Profiles server to support dynamic feeds in Microsoft Outlook Social Connector.

    To configure support for dynamic feeds for an Connections 4 server, edit properties in the profiles-types.xml and profiles-config.xml files.

    1. Navigate to the configuration files in the following location: WebSphere/AppServer/profiles/<AppSrv>/config/cells/<serverNodeCell>/LotusConnections-config.

    2. Edit the file profiles-types.xml in a text editor and add a <property> for the attribute hashEmail:
      <property>
        <ref>hashEmail</ref>
        <updatability>readwrite</updatability>
        <hidden>false</hidden>
        <fullTextIndexed>true</fullTextIndexed>
      	</property>

    3. Edit the file profiles-config.xml file in a text editor and Add a <simpleAttribute> to the <profileExtensionAttributes> element.
      <simpleAttribute extensionId="hashEmail" length="40"/>

    4. Save your changes and close the configuration files.

    5. Restart the connections server so the changes take effect.
    6. Populate the new attribute. This code sample demonstrates how to produce the hash with a simple Java™ method:
      String hash = hashString(email,"MD5");  // SHA-1       public static String hashString(String text, String alg)  throws NoSuchAlgorithmException, UnsupportedEncodingException
         {
            MessageDigest md = MessageDigest.getInstance(alg);
            md.update(text.getBytes("iso-8859-1"), 0, text.length());
            // convert the byte-array into a hex-string
            byte[] hash = md.digest();
            StringBuffer buf = new StringBuffer();
            for( int i=0; i < hash.length; i++ )
            {
               int b = hash[i];
               if( b < 0 )
                  b = 256 + b;
               if( b < 16 )
                  buf.append("0");
               buf.append(Integer.toHexString(b));
            }
            return buf.toString();
         }

      The result is a web page with only the hashed email returned.

    To configure support for dynamic feeds for a Connection 3.x server....

    1. Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
      app_server_root\profiles\Dmgr01\bin
      You must start the client from this directory or subsequent commands that you enter do not execute correctly.

    2. Start the Profiles Jython script interpreter.

      1. Access the Profiles configuration files: execfile("profilesAdmin.py") If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.

      1. Check out the Profiles configuration files: ProfilesConfigService.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.

          AIX/Linux only: The directory must grant write permissions or the command does not complete successfully.

        • cell_name is the name of the WAS cell that is hosting the Profiles application. This argument is required. It is also case-sensitive, so type it with care. To determine cell name, run wsadmin command: print AdminControl.getCell()

    3. Open profiles-config.xml in an editor and add a simpleAttribute to the profileExtensionAttributes element. To do so, search for
      <profileDataModels> 	  	<profileExtensionAttributes>
      and add:
      <simpleAttribute extensionId="hashEmail" length="40"/> 
    4. Indicate that the extension is editable by extending the apiModel element. To do so, search for
      <apiConfiguration> 	
      	<apiModel profileType="default">
      and add:
      <editableApiExtensionAttribute extensionIdRef="hashEmail"/>

    5. After you edit the files, check the configuration files back in, and you must do so in the same wsadmin session in which you checked them out for the changes to take effect.

      See Applying property changes in Profiles for information about how to save and apply your changes.

    6. To populate the new attribute, you must perform an HTTP PUT to the profileExtension.do URL for each user. To verify that the attribute is correctly populated, you can test each entry using the following URL pattern:
      https://<servername>/profiles/atom/profileExtension.do?extensionId=hashEmail&email=<email address>

      The result is a web page with only the hashed email returned.

      The following code sample shows how to create the attribute value using MD5 hashing.

      MD5 Hashing Sample   // (C) Copyright IBM Corp. 2010 - All Rights Reserved.
      //
      // DISCLAIMER:
      // The following source code is sample code created by IBM Corporation.
      // This sample code is provided to you solely for the purpose of assisting you // in the use of Lotus Connections. The code is provided 'AS IS', without warranty or // condition of any kind. IBM shall not be liable for any damages arising out of your // use of the sample code, even if IBM has been advised of the possibility of // such damages.
      //  // Return a MD5 hash of the first argument   package com.ibm.sample;
      import java.io.UnsupportedEncodingException;
      import java.security.MessageDigest;
      import java.security.NoSuchAlgorithmException;
        public class Hash
      {
        public static String hashString(String paramString1, String paramString2)
      	throws NoSuchAlgorithmException, UnsupportedEncodingException
        {
          MessageDigest localMessageDigest = MessageDigest.getInstance(paramString2);
          localMessageDigest.update(paramString1.getBytes("iso-8859-1"), 0, paramString1.length());
          byte[] arrayOfByte = localMessageDigest.digest();
            StringBuffer localStringBuffer = new StringBuffer();
          for (int i = 0; i < arrayOfByte.length; i++)      {
            int j = arrayOfByte[i];
            if (j < 0)
              j = 256 + j;
            if (j < 16)
              localStringBuffer.append("0");
            localStringBuffer.append(Integer.toHexString(j));
          }
          return localStringBuffer.toString();
        }
      }


    Connections Plug-in for Microsoft SharePoint

    The Connections Plug-in for Microsoft SharePoint brings Connections applications such as searching by tag, searching by profile, and viewing business cards, into the SharePoint environment. Install the Connections Widget for Microsoft SharePoint so that Connections users can access documents from a SharePoint server.

    The Connections Plug-in for Microsoft SharePoint provides the following applications:

    • Profiles search for finding people in your organization. If colleagues you find with a Profiles search are in your SharePoint directory, you can add them to your SharePoint group or site.
    • Business card for getting contact and social networking information about users in your organization. From the business card, you can create a mail message to this colleague or open their blog, bookmarks, or full profile.
    • Tag cloud for finding content that is stored on Connections servers. Clicking a tag launches a search that matches against all Connections services.

      For example, clicking a new-hire tag might return a community and a blog post.

    • The Connections Widget for Microsoft SharePoint is a widget that you install separately on an Connections server so that community members can upload, view, and share documents that are stored on a Microsoft SharePoint server.

    To get started, download the plug-in from the Connections catalog website: https://greenhouse.lotus.com/catalog.


    Install the Connections Plug-in for Microsoft SharePoint

    The Connections Plug-in for Microsoft SharePoint brings Connections features such as searching by tag, searching by profile, and viewing business cards, into the SharePoint environment.

    Connections Plug-in for Microsoft SharePoint requires Microsoft SharePoint 2010.

    Install language packs for Microsoft SharePoint to the server farm before you install this plug-in. The plug-in automatically installs language pack solutions for all the supported languages that are installed in the server farm. If you install more language packs to the server farm after you install the plug-in, run the configuration wizard again to make the additional languages available to the plug-in.

    Follow these steps to install the plug-in.

    1. On your SharePoint server, extract the plug-in contents to a location you can remember.

      For example, C:\IBM\Lotus\Connections.

    2. Run the Install.bat program to launch the plug-in installation and configuration wizard
    3. Review the URLs for accessing the Connections Profiles and Search servers. The URLs are automatically supplied, based on the Profiles Server URL, but you can change them if necessary.

    4. Modify the settings for the Profiles search.

    5. Click OK to complete the installation. Information from the installation is logged to plugin directory\logs\install-<timestamp>.log.

      If you must modify your configuration after you install, navigate to where you extracted the plug-in files for installation. Then, run ModifyPluginConfig.bat This command launches the plug-in configuration wizard and allows you to change your settings or install additional language packs. Update information is logged to plugin directory\logs\update-timestamp.log.

    If anonymous authentication is enabled in the Internet Information Services (IIS) manager, then the API used by the SharePoint widget does not work as expected. To check whether anonymous authentication is enabled in IIS:

    1. Go to Start > Administrative Tools > Internet Information Services (IIS) Manager.

    2. In the Connections section, expand the server, and then expand Sites.

    3. Select the SharePoint site. The default is SharePoint - 80.

    4. Double-click the icon for Authentication.

    5. Check to see whether there is an entry for Anonymous Authentication.

    If anonymous authentication is not actually needed on this SharePoint server, you can disable it in IIS. However, if anonymous authentication is required then you must disable anonymous authentication for only the URL pattern used by the plug-in API, as follows:

    1. Create a supplemental web configuration file that is called webconfig.IBMConnections.xml. For instructions on creating the configuration file, see the Microsoft article on creating a supplemental configuration file. Add this code:
      <?xml version="1.0" encoding="utf-8"?>
      <actions>
        <remove path="configuration/location[@path='_layouts/lcphandler.ashx']" />
        <add path="configuration">
          <location path="_layouts/lcphandler.ashx" allowOverride="false">
            <system.web>
               <authorization>
                   <deny users="?" />
           </authorization>
            </system.web>
          </location>
        </add>
      </actions>

    2. Place the file in the \CONFIG folder of the SharePoint server. The default location for SharePoint 2010 is C:\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG and the default location for SharePoint 2007 is C:\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG .

    3. Open the SharePoint 2010 Management Shell

    4. Run the command stsadm -o copyappbincontent

    5. Repeat steps 2-4 on all front-end web servers.


    Deploy the Connections Plug-in for Microsoft SharePoint

    After you install the plug-in, you activate the Connections features to make them available from Microsoft SharePoint.

    To enable the Connections plug-in, deploy the features to the Microsoft SharePoint server farm. You can complete the deployment from the Central Administration site or from the Management Shell.

    See the Microsoft documentation for further details.

    1. Follow the instructions that are provided by Microsoft to deploy the following solutions:

      • ConnectionsPluginCore.wsp - Required for business card integration, the profile search and tag cloud web parts, and the Connections SharePoint widget.
      • ConnectionsPluginCore_LCID.Tivoli Workload Scheduler for PeopleSoft where LCID is a Microsoft locale ID. Required for any languages that are in use in the server farm. Refer to the Microsoft documentation for the list of SharePoint supported languages and their LCID. If deploying solutions using Management Shell, refer to the Microsoft documentation for deploying language pack solutions. Deploy the ConnectionsPluginCore.wsp solution before you deploy any language pack solutions. The Connections plug-in supports only the languages that are supported by Connections 3.0.
      • ConnectionsProfileSearch.wsp - To confirm changes made , provides the profile search web part.
      • - ConnectionsTagCloud.wsp - To confirm changes made , provides the tag cloud web part.

    2. Activate the Connections features. The Connections Tag Cloud and Search Connections Profiles features are installed when their solutions are deployed. However, they must be activated before the web parts display in the Web Part Gallery. These features are scoped to the Site Collection level, so for a particular site collection, you can activate the web parts from Site Settings > Site Collection Administration > Site Collection Features. The features can also be activated using the Management Shell using the Enable-SPFeature command.

      For more information about the Management Shell command, refer to the Microsoft documentation.

    3. To enable the Connections Profiles business card on your SharePoint site, make the following changes to your master page:

      • Near the beginning of the page, register a tag for the Connections profile user control:
        <%@ Register TagPrefix="Connections" tagname="ProfileScript" src="~/_controltemplates/ConnectionsProfileScript.ascx" %>

      • At the end of the master page body, include the Connections profile user control:
        <Connections:ProfileScript ID="ConnProfileScript" runat="server"/>

      For more information about customizing master pages, refer to the Microsoft documentation.


    Uninstalling the Connections Plug-in for Microsoft SharePoint

    Deactivate the Connections features and uninstall the plug-in to remove it from Microsoft SharePoint.

    Follow these steps to uninstall the plug-in.

    1. To disable business card integration, remove the tags that you added to your master page:

      • Remove the tag for the Connections profile user control from the header of the page:
        <%@ Register TagPrefix="Connections" tagname="ProfileScript" src="~/_controltemplates/ConnectionsProfileScript.ascx" %>

      • Remove the Connections profile user control tag from the footer of the body of the master page:
        <Connections:ProfileScript ID="ConnProfileScript" runat="server"/>
    2. Deactivate the Connections features. Deactivate the Connections Tag Cloud and Search Connections Profiles features from all Site Collections. For a particular site, you can deactivate the features from Site Settings > Site Collection Administration > Site Collection Features. You can also deactivate features with the Disable-SPFeature command from the Management Shell.

      For more information, see the Microsoft documentation.

    3. Retract all Connections solutions from the Microsoft SharePoint server farm. You must retract all Connections plug-in solutions from the server farm. You can do this from the Central Administration site or from the Management Shell. Retract all ConnectionsPluginCore(<LCID>).wsp language pack solutions before you remove ConnectionsPluginCore.wsp. Refer to the Microsoft documentation for retracting solutions.

    4. Navigate to the folder where you extracted the plug-in files for installation and run Uninstall.bat. The uninstallation program removes all plug-in solutions and plug-in properties from the server farm. Uninstall information is logged to plugin directory\logs\uninstall-timestamp.log.


    Connections Plug-ins for IBM Notes

    Use the Connections Plug-ins for IBM Notes to have easy access to Connections content from the Notes sidebar.

    Use the Connections Plug-ins for IBM Notes to have easy access to Connections content from the Notes sidebar. You can do the following from the sidebar applications:

    • Collaborate on a project using the Activities sidebar.
    • Display Activities to-do items in the Notes calendar.
    • Bookmark a Notes document and add it to your bookmark collection in Connections.

    • Find and interact with colleagues by expanding a person's business card.
    • Upload files for your own use or to share with others
    • Keep up with your network by posting status updates and reading updates from people you follow.

    • Search across the Connections applications.


    Upgrading the IBM Notes client after installing IBM Connection plug-ins for IBM Notes

    If you installed the Connections plug-ins for IBM Notes and you are updating your IBM Notes client to 9.0, make sure that Connections is selected on the Notes installation panel when you upgrade.

    While you upgrading the existing Notes client to IBM Notes 9.0, make sure that Connections is checked on the Notes installation panel. Otherwise, you do not get the sidebar applications for Activities, Files, and Status Updates. The sidebar applications depend on the Connections Business Card plug-in.

    For example, if you have Connections plug-ins for IBM Notes installed with Notes 8.5.3, then you upgrade the Notes 8.5.3 client to IBM Notes 9.0, select Connections as an installation option. If you do not select Connections, the Activities and Status Updates sidebar applications will not display after you upgrade the client.

    1. Make sure that your IBM Notes client is closed before you begin the upgrade.

    2. Start the IBM Notes 9.0 installer.

    3. Select Connections on the Custom Setup panel.

    4. Click Finish.


    Install the Connections Plug-ins for IBM Notes

    Install the Connections Plug-ins for IBM Notes to access Files, Activities, Status Updates and business card integration from your IBM Notes client.

    There are two ways to install the Connections Plug-ins for IBM Notes. A user can install plug-ins for a Notes client using the InstallShield wizard, or an administrator can perform a silent installation for all plug-in users.


    Install the Plug-ins on a Windows client

    Install the plug-ins so that the Connections features are integrated with the IBM Notes client.

    1. Download the Connections Plug-ins for IBM Notes from the Connections catalog at the following web site:
       https://greenhouse.lotus.com/catalog
    2. Unzip ConnectionsAddonInstaller.zip and click Setup.exe.

    3. Make sure your IBM Notes client is closed before beginning the installation.

    4. Accept installation prompts for installing the plug-ins.

    5. Click Finish to complete the installation.


    Silently installing the Connections Plug-ins (Windows)

    Administrators can silently install the Connections plug-ins from the command prompt. A silent installation uses the same installation program that the graphical user interface (GUI) version users. However, instead of displaying a wizard interface, the silent installation reads all your responses from parameters that you pass to the command line. In order for the installation to work successfully, you must run the silent installation from the directory where you unzipped the plug-ins files.

    1. Make sure your IBM Notes client is closed before beginning the installation.

    2. Open a command window.

      For example, choose Run from the Microsoft Windows Start menu and type cmd, then click OK.

    3. Specify the path for the downloaded and unzipped installation file for the plug-in.

      For example, c:\<download_folder>.

    4. Enter setup.exe /s /v" /qn" to begin the installation.


    Install the Plug-ins on a Mac client

    Install the Mac version of the Connections Plug-ins for IBM Notes so that it is integrated with the IBM Notes client.

    Consider the following before you install:

    • If you run the unsigned installer on Mac 10.7.5 or newer, turn off the GateKeeper first before running the installer. To turn off the GateKeeper, got to System Preferences > Security & Privacy and Click Anywhere as the value for Allow applications downloaded from.

    • If you are installing a subset of the plug-ins with the signed installer on Mac 10.7.5 or later, turn off GateKeeper, then delete the _CodeSignature from xpd.addon-mac.pkg/Contents/_CodeSignature.

    1. Download the Connections Plug-ins for IBM Notes from the Connections catalog at the following web site:
       https://greenhouse.lotus.com/catalog
    2. Extract ConnectionsAddonInstaller_Mac.zip.

    3. Make sure your IBM Notes client is closed before beginning the installation.

    4. Double-click xpd.mac-addon.pkg to launch the installation program.

    5. Accept installation prompts for installing the plug-ins.

    6. Click Finish to complete the installation.


    Silently installing the Connections Plug-ins (Mac)

    Administrators can silently install the Connections Files plug-in from the command prompt. A silent installation uses the same installation program that the graphical user interface (GUI) version users. However, instead of displaying a wizard interface, the silent installation reads all your responses from parameters that you pass to the command line. In order for the installation to work successfully, you must run the silent installation from the directory where you unzipped the plug-in files.

    1. Make sure your IBM Notes client is closed before beginning the installation.

    2. Open a terminal window.

    3. Specify the path for the downloaded and unzipped installation file for the plug-ins.

      For example, /ConnectionsAddonInstaller_Mac.

    4. Enter sudo Installer -pkg package name -target destination volume to begin the installation. Where:

      • package name is xpd.addon-mac.pkg, the name of the installer.
      • destination volume is the disk where IBM Notes was installed.

      For example: sudo Installer -pkg xpd.addon-mac.pkg -target Macintosh_HD

    5. Enter your password at the prompt to begin the installation. When the installation completes, a terminal message displays The install was successful.


    Viewing the log files

    Use the log files to help you resolve problems with the installation.

    If you encounter any errors during the installation or configuration process, review the log files for troubleshooting information. On Windows, the logs for the plug-in are stored in the default temp directory for users.

    For example, on Windows XP, the directory is: C:\documents and settings\<username>\Local Settings\temp\rcp_addon_install.txt\.

    To view the logs on a Mac, follow these steps.

    1. Change to the directory where Notes is installed.

    2. Navigate to /Contents/MacOS/rcp/deploy/instalHistory.

    3. Find the zip file. It's name will be similar to this: Notes_8.5.3FP4_ADDON_INSTALL_1311563867253.zip or Notes_8.5.3FP4_ADDON_UNINSTALL_1311572948964.zip.
    4. Unzip the file and navigate to /colutil/tmp to access the log.

    There is a configuration which can prevent users from uploading, downloading, or sharing files. Users will be able to view files, but, when trying to upload, download, or share a file will see this error message: "A problem with the server was encountered". This is most likely because an SSL setting called "Forced confidential" is enabled in LotusConnections-config.xml on the Connections server and it creates a conflict on the Notes client. To correct this problem, set the following Files configuration setting in the plugin_customization.ini file. This setting applies to all versions of Notes.

    1. Open the plugin_customization.ini file for the Notes client in a text editor. The file is stored in: <Notes Install>/framework/rcp/plugin_customization.ini

      On Mac, your path might be different depending on where you installed Notes.

      For example, your path might be: /Applications/Notes.app(or or Lotus Notes.app or IBM Notes.app)/Contents/MacOS/rcp/eclipse/features/plugin_customization.ini

    2. Add this line:
       com.ibm.documents.connector.service/ENABLE_SSL=true
    For detailed information on managing security settings, see this article on Create a Connections server document in the IBM Notes/Domino wiki.


    Customize the installation of the Connections plug-ins

    Customize the installer by editing the install.addon.xml file to install a custom set of Connections plug-ins for an IBM Notes client.

    Activities and Status Updates depend on the Business Card plug-in. Do not remove the Business Card plug-in if you are installing Activities or Status Updates.

    Customize the installer to install parts of the plug-ins so that they are integrated with the IBM Notes client.

    For example, if you do not want to deploy Status Updates, you can exclude that plug-in from the installation by commenting it out in the install.addon.xml file.

    1. Open install.addon.xml in a text editor from the /deploy folder.

      For example,

      • Windows: /ConnectionsAddonInstaller/deploy
      • Mac: /ConnectionsAddonInstaller_Mac/xpd.mac-addon.pkg/Contents/deploy
      .

    2. Comment out the plug-ins you do not want to deploy or uncomment the plug-ins you do want to deploy.

      For example, if you don't want to install Status Updates plug-in, comment out the Status Updates plug-in.

      For example:

      <!-- Below is the Status Updates plug-in install block, comment it out if you don't want to install Status Updates plug-in. -->
      <!-- Status Updates -->
      <!--
      <feature action="install" id="com.ibm.lconn.statusupdates.feature" match="equivalent" shared="true" version="4.5.0.20130224-1730"/>
      -->
      <!-- Status Updates -->

    3. Click setup.exe/xpd.mac-addon.pkg to start the installation.


    Connecting to a Connections server

    Log into Connections servers to access Connections content from the sidebar applications.

    These steps describe how a user can connect to a Connections server. To provision this for a group of servers, use a policy.

    For more information, see the article on Create a Connections settings document in the IBM Domino wiki.

    For information on configuring the plug-in to work with SSL, see the article on Use INI settings to configure the Connections features that are available in the IBM Lotus Notes client in the Connections wiki.

    You need the following information to connect to the Connections server:

    • The Web address of the Connections server (not just the server name, but the full Web address, like https://activities.example.com)

    • The username and password you use to log into Connections.

    When you first open a Connections panel in the sidebar, if a connection to the server is not available, you are prompted to verify connection information. The following steps describe how to log in from the Activities panel of the sidebar:

    1. In the Activities panel of the sidebar, click Show Connections preferences to open the Connections preferences window.
    2. Fill in the following fields in the Connections Server Settings section:

      Field Description
      Server URL Type the Web address of the Connections server, beginning with either https:// or http://

      For example: https://enterprise.example.com

      If you know that the server requires a secure, encrypted connection, begin the address with https://

      Some administrators change the context roots that are used to access Connections features. If the web address that you normally use to access the Activities feature has a value other than <server_name>/activities, specify the server URL using a syntax similar to this: http://enterprise.example.com/activities

      Your administrator might have already provided a value for this field using an administrative policy. If so, do not change the value.

      User name Type your user name for logging in to the Connections server.
      User password Type the associated password.

    3. Only required if you are instructed to perform this step by your administrator: If Tivoli Access Manager or Computer Associates eTrust SiteMinder are configured in your environment, click Advanced, and then select the appropriate option.


    Results

    The Activities sidebar should now display a list of your activities. Connecting to the Activities server also creates the necessary connection for the Files and Status Updates applications.

    The next time you log in to Notes, you are logged in to the Connections server automatically.


    Uninstalling the Connections Plug-ins for Lotus Notes

    Uninstall the Connections plug-ins to remove them from your Lotus Notes client.

    If you are planning to uninstall the Notes client, uninstall the Connections plug-ins first.

    You can remove the plug-ins from a single client or run a command to remove them from all plug-in users.

    1. To remove plug-ins from a single Windows client:

      1. From the Microsoft Windows Control Panel, select Add or Remove Programs (on Vista, it is called Programs and Features), then select Connections Plug-ins for Lotus Notes..

      2. Click Remove (on Microsoft Windows 7 and Vista, it is called Uninstall), and then click Yes to confirm your choice.

    2. To silently remove plug-ins from Windows clients:

      1. Make sure your Lotus Notes client is not running.

      2. Open a command prompt window.

        For example, choose Run from the Microsoft Windows Start menu and type cmd, then click OK.

      3. Specify the path for the downloaded and unzipped installation file for the plug-ins.

        For example, c:\<download folder>.

      4. Enter setup.exe -s -x -v"/qn" to remove the plug-ins.

    3. To remove the plug-ins from a single Mac client:.

      1. Open the folder where you unzipped the ConnectionsAddonInstaller_Mac.zip file.

      2. Click unistaller.app, and then click Yes to confirm your choice.

    4. To silently remove the plug-ins from Mac clients:

      1. Make sure your Lotus Notes client is not running.

      2. Open a terminal window.

      3. Specify the path for the downloaded and unzipped installation file for the plug-ins.

        For example, /ConnectionsAddonInstaller_Mac/uninstaller.

      4. Enter ./addonUninstall -rcphome '/Applications/<App_Name.app>/Contents/MacOS' -addonID IBMConnectionsPluginsforLotusNotes to remove the plug-ins. <App_Name.app> is Notes.app, Lotus Notes.app, or IBM Notes.app.


    Install plug-ins to use other applications in Connections

    Enhance Connections by installing plug-ins so used other applications from within Connections.

    You can use other products from Connections by adding these plug-ins.


    IBM Lotus Quickr Library widgets for Connections

    Connections communities can interact with IBM Lotus Quickr libraries using two new widgets.

    • The "Linked Quickr Library" widget links to an existing Lotus Quickr Library.

    • The "Quickr Library" widget creates a new Lotus Quickr Library.

    A "Linked Quickr Library" widget surfaces an existing Lotus Quickr library. Members of the community can read and manage library documents based on their roles in the Lotus Quickr place that contains the library. An administrator or user with a Manager role in the place must add community members as place members before the members can access the library. Membership changes are not synchronized between the community and place, an administrator must update both.

    A "Quickr Library" widget creates a new Lotus Quickr place with a library, and surfaces that library in the community. When the place is created, community members are synchronized to Lotus Quickr and made place members. Any membership changes in the community are synchronized to the place. But membership changes in the place are not synchronized to the community.

    For example, if you add a member to the community, that change is synchronized and they are added to the place. But adding a user to the place will not add them to the community. When the community is deleted, the place and library are deleted.

    A community can only have one of each widget.

    Download the widgets from the IBM Lotus and WebSphere Portal Business Solutions Catalog.

    See the following topics for help adding the widgets to a community:

    See the following topics for steps required to configure your environment, steps for installing and configuring the widgets, and steps for uninstalling the widgets:


    Configure single sign-on between the Connections and Lotus Quickr servers

    You must configure single sign-on between the Connections and Lotus Quickr servers before you can add Lotus Quickr Library widgets to Connections communities.

    Both servers must be configured to use the same LDAP.

    1. On the Connections server, open WAS admin console.

    2. Navigate to Security > Global Security > Web and SIP Security > Single sign-on.

    3. Make sure single sign-on is enabled.

    4. Set the domain name to the common domain name suffix of the two servers.

      For example, if the two servers are connections.my.enterprise.com and quickr.my.enterprise.com, the domain name for SSO could be .my.enterprise.com.

    5. Navigate to Security > Global Security > LTPA.

    6. Under cross-cell single sign-on type a password that you will use later, and the location and name of a key file name to export to, for example C:\my.keys

    7. On the Lotus Quickr server, open WAS admin console.

    8. Navigate to Security > Secure administration, applications, and infrastructure > Web Security > Single sign-on.

    9. Make sure single sign-on is enabled.

    10. Set the domain name to the same one set for the Connections server.

    11. Copy the key file that you exported from Connections in Step 6 to the Lotus Quickr server.

      For example, copy the C:\my.keys file from the Connections server to a directory on the Lotus Quickr server.

    12. In the console, navigate to Security > Secure administration, applications, and infrastructure > Authentication mechanisms and expiration.

    13. Under cross-cell single sign-on enter the password you used in Step 6 to export the keys.

    14. Enter the path and file name of the key file on the Lotus Quickr server and click Import keys.

    15. Restart Lotus Quickr server.


    Add Connections URLs to the Lotus Quickr Resource Environment provider

    You must add Connections server URLs to the Lotus Quickr Resource Environment provider before you can add Lotus Quickr Library widgets to Connections communities.

    Add any allowed Connections server URLs.

    For example, if the server allows http and https URLs, you must add both.

    1. On the Lotus Quickr server, open WAS admin console.

    2. Navigate to Resource Environment > Resource Environment Providers.

    3. Open QuickrDocumentLibraryConfig.

    4. Select Custom Properties.

    5. If your Connections server allows http, add new entry with name "pdmConfig.connIntg.host" and server URL value, such as "http://yourserver.com:9080" In deployments with web servers, the URL value should use the web server port, such as "http://yourserver.com:80". If you have TAM enabled on the Connections server, replace yourserver.com with the TAM sever hostname.

    6. If your Connections server allows https, add new entry with name "pdmConfig.connIntg.secure.host" and server URL value, such as "https://yourserver.com:9443" In deployments with web servers, the URL value should use the web server ssl port, such as "https://yourserver.com:443". If you have TAM enabled on the Connections server, replace yourserver.com with the TAM sever hostname.

    7. Save settings and restart the Lotus Quickr server.


    Install and configuring the IBM Lotus Quickr Library Widgets

    Download the Lotus Quickr library widgets and then install and configure them.

    Before you can use the widgets:

    • You must configure single sign-on between the Connections and Lotus Quickr servers.

      See the topic Configuring single sign-on between the Connections and Lotus Quickr servers.

    • You must add Connections server URLs to the Lotus Quickr Resource Environment provider.

      See the topic Adding Connections URLs to the Lotus Quickr Resource Environment provider.

    • To use the Linked Lotus Quickr library widget there must be an existing Lotus Quickr place with a library in the Lotus Quickr deployment.

    • You must install all prerequisites.

      See the Lotus Quickr Library widget page on the IBM Lotus and WebSphere Portal Business Solutions Catalog website.

    1. In SiteMinder environments only, perform the follow tasks on the IBM connections server:

      1. Copy the US_export_policy.jar and local_policy.jar files from wherever you unpackaged the unrestricted.zip file when configuring SiteMinder. Paste it in the following directory, overwriting the existing versions of those files:
        <websphere_application_server>/java/jre/Lib/Security

      2. Copy the sm_jsafe.jar and sm_jsafeJCE.jar files from the Siteminder ASA crypto-libraries installation directory. Paste it in the following directory, overwriting the existing versions of those files:
        <websphere_application_server>/java/jre/lib/ext

      The Lotus Quickr server must be protected by SM TAI only. All other TAIs should be removed or disabled.

      For details on using and configuring eTrust SiteMinder with Lotus Quickr, see the article Use eTrust SiteMinder with Lotus Quickr in the IBM Quickr wiki.

    2. Download the Lotus Quickr Library widget war file from the IBM Lotus and WebSphere Portal Business Solutions Catalog web site.

    3. Install the widget war file.

      1. Log in to the WebSphere Administrative Console on the Connections server.

      2. Navigate to Applications > Application Types > WebSphere enterprise applications.

      3. Click Install.
      4. Browse and select the comm.communitylibrary.war file, click Next, and then click Next again.

      5. In Step 1 of the installation wizard, click Next without changing anything.

      6. In Step 2, select the cluster and web server (if there is one), and then click Next.

      7. In Step 3 of the installation wizard, in the Target Resource JNDI Name column, click Browse and select communities. Then click Apply. The field is populated with the value jdbc/sncomm. Then check the box and click Next.

      8. In Step 4, check the box and then click Next without changing anything.

      9. In Step 5, type /quickr/connector in the Context Root field, and then click Next.

      10. In Step 6, click Finish.

      11. Open the Quickr widget application (comm_communitylibrary_war), and navigate to Modules > Manage Modules > Quickr Library Connector.

      12. In the Class loader order section, change Classes loaded with parent class loader first to Classes loaded with local class loader first (parent last), then click OK to save.

      13. Click Save to save all changes. In clusters you must wait for synchronization to complete before continuing. Check the systemout.log in the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent directory (on Linux servers) to check for the synchronization completed successfully message.

      14. In the list of applications, select the Lotus Quickr Library widgets application (comm_communitylibrary_war) and then click Start to start it.

    4. Create a J2C authentication alias for the Lotus Quickr administrator.

      1. On the Connections server, log into WAS admin console, expand Security, and then select Global Security.

      2. Expand Java Authentication and Authorization Service.

      3. Select J2C authentication data.

      4. Click New.

      5. Type an alias name (for example ...CellManager01/quickradmin), and specify the user ID and password credentials of a Lotus Quickr administrator.

        If the Lotus Quickr administrative user is not available to Connections (meaning not in the LDAP or defaultFileBasedRepository), then you must add them to the defaultFileBasedRepository. Navigate to Users and Groups > Manage Users, and then create a user with the Lotus Quickr administrator ID and password.

        In a Siteminder environment, the Quickr administrative user must be a valid Siteminder user.

      The server generates a J2C alias with a cell name and the alias name you provided, for example: ...CellManager01/quickradmin. You must use this generated alias, including the cell name.

    5. Copy the widget configuration files to the Connections configuration directory.

      1. Navigate to the widget \resources_config directory:
         \IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\cell_name\comm_communitylibrary_war.ear\comm.communitylibrary.war\resources_config

      2. Copy the communities-quickr-library-config.xml and communities-quickr-library-config.xsd files to the \LotusConnections-Config directory:
        \IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config

        In clustered deployments, copy the files to the \LotusConnections-Config directory on the deployment manager node.

    6. Add the widget resource bundle to LotusConnections-config.xml.

      1. Navigate to the widget resources directory:
        \IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\cell_name\comm_communitylibrary_war.ear\comm.communitylibrary.war\resources
        In clusters, navigate to the directory on any node.

      2. Copy the contents of the \resources directory to the IBM\Connections\data\shared\customization\strings directory (in clusters, copy to the deployment manager computer).

      3. Check out and open LotusConnections-config.xml.

        See Editing configuration files.

      4. Add the following line of code into the <resources> element block to register the resource bundle for the Quickr Library widget:
        <widgetBundle name="com.ibm.quickr.communitylibrary.resources" prefix="quickrCommunityLibrary_res" />

    7. Add the following widget xml definitions to the widgets-config.xml file, editing values to reflect your environment. In clustered deployments, edit widgets-config.xml on the deployment manager node.

      See steps and most attribute descriptions in the topic Enabling custom widgets for Communities:

      <widgetDef bundleRefId="quickrCommunityLibrary_res" defId="LinkedQuickrCommunityLib"  description="LinkedQuickrCommunityLibDesc" primaryWidget="false"  url="/quickr/connector/com.ibm.quickr.communitylibrary.xml" modes="view edit fullpage"
      iconUrl="{contextRoot}/nav/common/images/iconFiles16.png" uniqueInstance="true"  displayLoginRequired="true"
      helpLink="http://www.lotus.com/ldd/lcwiki.nsf/dx/Using_the_Linked_Lotus_Quickr_library_widget_ic40">
      <itemSet>
      <item name="iframeLoadTimeout" value="30000" />
      </itemSet>
      </widgetDef>
        <widgetDef bundleRefId="quickrCommunityLibrary_res" defId="QuickrCommunityLib" description="QuickrCommunityLibDesc" primaryWidget="false" url="/quickr/connector/com.ibm.quickr.communitylibrary.xml" modes="view fullpage"
      iconUrl="{contextRoot}/nav/common/images/iconFiles16.png" uniqueInstance="true" displayLoginRequired="true"
      helpLink="http://www.lotus.com/ldd/lcwiki.nsf/dx/Using_the_Lotus_Quickr_library_widget_ic301">
      <itemSet>
      <item name="iframeLoadTimeout" value="30000" />
      </itemSet>
      <lifecycle remoteHandlerURL="remoteHandlerURL/quickr/connector/lifecycle"  remoteHandlerAuthenticationAlias="remoteHandlerAuthenticationAlias">
      <event>widget.added</event>
      <event>widget.removed</event>
      <event>community.members.added</event>
      <event>community.members.removed</event>
      <event>community.updated</event>
      <event>community.visibility.changed</event>
      <event>community.prepare.delete</event>
      <event>community.members.modified</event>
      </lifecycle>
      </widgetDef>
      Where:

      • In IBM Tivoli Access Manager environments the widgetDef url value must explicitly specify the Quickr server Tivoli Access Manager junction URL.

        For example, this sample assumes a URL such as https://yourserver.com:port/lotus and only the /quickr/connector/com.ibm.quickr.communitylibrary.xml part is specified. In Tivoli Access Manager environments you must specify the entire URL, for example https://tam.hostname.com:port/lotus/quickr/connector/com.ibm.quickr.communitylibrary.xml.

      • The itemSet.item.value attribute is the number of milliseconds Internet Explorer browsers wait to determine if the Lotus Quickr library loaded successfully before showing an error. If Internet Explorer users are seeing only the error page, you can try increasing this value to resolve the issue, particularly if they can see the library in the Firefox browser.
      • {contextRoot} is a variable automatically populated with the Connections directory.
      • Replace remoteHandlerURL with the URL of the Connections server on which the widget is installed, for example: https://yourserver.com:9443. If you have IBM Tivoli Access Manager enabled on Connections server, replace yourserver.com with the IBM Tivoli Access Manager sever hostname.
      • Replace remoteHandlerAuthenticationAlias with the Connections J2C authentication alias used to talk to the servlet. The alias connectionsAdmin is the default for all widgets.

    8. On the Connections server, open communities-quickr-library-config.xml and update the Lotus Quickr information for your environment, for example:
      <host>quickr.example.com</host>
      <port>10040</port>
      <sslPort>10035</sslPort>
      <useSSL>false</useSSL>
      <authentry>CellManager01/quickradmin</authentry>
      <ownersRole>Managers</ownersRole>
      <membersRole>Editors</membersRole>
      <publicRole>Readers</publicRole>
      Where:

      • <host> is the Lotus Quickr server hostname. If you have IBM Tivoli Access Manager enabled on Lotus Quickr server, replace yourserver.com with the IBM Tivoli Access Manager sever host name.
      • <port> is the http port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
      • <sslPort> is the https port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
      • <useSSL> is whether or not to use http or https in communicating with the Lotus Quickr server. If this is set to "true", the Lotus Quickr server must have a certificate that is trusted by the Connections server.

        See Secure communications using Secure Sockets Layer in WAS 6.1 documentation for more information.

      • <authentry> is the full name of the J2C authentication alias for the Lotus Quickr administrator that you created in Step 3.

      • For <ownersRole>, <membersRole>, and <publicRole> the role names can be either the role title in English or the id field returned for the roles feed. If anonymous access is not allowed, the publicRole element should be omitted or empty. The publicRole is applied in both public and moderated communities, but is not in restricted communities

    9. In clustered environments, perform a full synchronization of the Connections cluster.

    10. Restart Connections.

    11. If you had IBM HTTP Server installed before you installed the Lotus Quickr widget, follow instructions in Mapping applications to IBM HTTP Server to map the Lotus Quickr widget application to the IBM HTTP Server.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Mapping_applications_to_IBM_HTTP_Server_ic45 /ldd/lcwiki.nsf/dx/Enabling_single_signon_for_SiteMinder_ic45


    Migrating from an earlier version of the Quickr Library widgets

    Follow these steps to migrate from the 4.0 version of the Quickr library widget.

    1. In SiteMinder environments only, perform the follow tasks on the IBM connections server:

      1. Copy the US_export_policy.jar and local_policy.jar files from wherever you unpackaged the unrestricted.zip file when configuring SiteMinder. Paste it in the following directory, overwriting the existing versions of those files:
        <websphere_application_server>/java/jre/Lib/Security

      2. Copy the sm_jsafe.jar and sm_jsafeJCE.jar files from the Siteminder ASA crypto-libraries installation directory. Paste it in the following directory, overwriting the existing versions of those files:
        <websphere_application_server>/java/jre/lib/ext

    2. Download the 4.5 version of the Lotus Quickr Library widget war file from the IBM Lotus and WebSphere Portal Business Solutions Catalog web site.

    3. Install the widget war file.

      1. Log in to the WebSphere Administrative Console on the Connections server.

      2. Navigate to Applications > Application Types > WebSphere enterprise applications.

      3. Click Install.
      4. Browse and select the comm.communitylibrary.war file, click Next, and then click Next again.

      5. In Step 1 of the installation wizard, click Next without changing anything.

      6. In Step 2, select the cluster and web server (if there is one), and then click Next.

      7. In Step 3 of the installation wizard, in the Target Resource JNDI Name column, click Browse and select communities. Then click Apply. The field is populated with the value jdbc/sncomm. Then check the box and click Next.

      8. In Step 4, check the box and then click Next without changing anything.

      9. In Step 5, type /quickr/connector in the Context Root field, and then click Next.

      10. In Step 6, click Finish.

      11. Open the Quickr widget application (comm_communitylibrary_war), and navigate to Modules > Manage Modules > Quickr Library Connector.

      12. In the Class loader order section, change Classes loaded with parent class loader first to Classes loaded with local class loader first (parent last), then click OK to save.

      13. Click Save to save all changes. In clusters you must wait for synchronization to complete before continuing. Check the systemout.log in the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent directory (on Linux servers) to check for the synchronization completed successfully message.

      14. In the list of applications, select the Lotus Quickr Library widgets application and then click Start to start it.

    4. Create a J2C authentication alias for the Lotus Quickr administrator.

      1. On the Connections server, log into WAS admin console, expand Security, and then select Global Security.

      2. Expand Java Authentication and Authorization Service.

      3. Select J2C authentication data.

      4. Click New.

      5. Type an alias name (for example quickradmin), and specify the user ID and password credentials of a Lotus Quickr administrator.

        If the Lotus Quickr administrative user is not available to Connections (meaning not in the LDAP or defaultFileBasedRepository), then you must add them to the defaultFileBasedRepository. Navigate to Users and Groups > Manage Users, and then create a user with the Lotus Quickr administrator ID and password.

        In a Siteminder environment, the Quickr administrative user must be a valid Siteminder user.

      The server generates a J2C alias with a cell name and the alias name you provided, for example: cell01\quickradmin. You must use this generated alias, including the cell name.

    5. To preserve the configuration settings from the 4.0 deployment, copy the values from \IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config. No additional changes are needed. Otherwise, follow these steps to copy the widget configuration files to the Connections configuration directory.

      1. Navigate to the widget \resources_config directory:
         \IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\cell_name\comm_communitylibrary_war.ear\comm.communitylibrary.war\resources_config

      2. Copy the communities-quickr-library-config.xml and communities-quickr-library-config.xsd files to the \LotusConnections-Config directory:
        \IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config

        In clustered deployments, copy the files to the \LotusConnections-Config directory on the deployment manager node.

      3. Follow the steps in the article Enable single sign-on for Siteminder to add /lotus/mycontenthandler/!ut/ to the list of unprotected URLs.

    6. If you followed the steps in the Connections 4.5 migration topic Saving your customizations, you can skip the remainder of this step. If not, follow these steps to copy the resource files from the 4.0 deployment and add the widget resource bundle to LotusConnections-config.xml.

      1. Navigate to the widget resources directory:
        \IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\cell_name\comm_communitylibrary_war.ear\comm.communitylibrary.war\resources
        In clusters, navigate to the directory on any node.

      2. Copy the contents of the \resources directory to the IBM\Connections\data\shared\customization\strings directory (in clusters, copy to the deployment manager computer).

      3. Check out and open LotusConnections-config.xml.

        See Editing configuration files.

      4. Add the following line of code into the <resources> element block to register the resource bundle for the Quickr Library widget:
        <widgetBundle name="com.ibm.quickr.communitylibrary.resources" prefix="quickrCommunityLibrary_res" />

    7. On the Connections server, open communities-quickr-library-config.xml and update the Lotus Quickr information for your environment, for example:
      <host>quickr.example.com</host>
      <port>10040</port>
      <sslPort>10035</sslPort>
      <useSSL>false</useSSL>
      <authentry>cell01/quickradmin</authentry>
      <ownersRole>Managers</ownersRole>
      <membersRole>Editors</membersRole>
      <publicRole>Readers</publicRole>
      Where:

      • <host> is the Lotus Quickr server hostname. If you have IBM Tivoli Access Manager enabled on Lotus Quickr server, replace yourserver.com with the IBM Tivoli Access Manager sever host name.
      • <port> is the http port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
      • <sslPort> is the https port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
      • <useSSL> is whether or not to use http or https in communicating with the Lotus Quickr server. If this is set to "true", the Lotus Quickr server must have a certificate that is trusted by the Connections server.

        See Secure communications using Secure Sockets Layer in WAS 6.1 documentation for more information.

      • <authentry> is the full name of the J2C authentication alias for the Lotus Quickr administrator that you created in Step 3.

      • For <ownersRole>, <membersRole>, and <publicRole> the role names can be either the role title in English or the id field returned for the roles feed. If anonymous access is not allowed, the publicRole element should be omitted or empty. The publicRole is applied in both public and moderated communities, but is not in restricted communities

    8. In clustered environments, perform a full synchronization of the Connections cluster.

    9. Restart Connections.

    10. If you had IBM HTTP Server installed before you installed the Lotus Quickr widget, follow instructions in Mapping applications to IBM HTTP Server to map the Lotus Quickr widget application to the IBM HTTP Server.


    Uninstalling the Lotus Quickr Library widgets

    Uninstall the widget war file, and remove the definitions and resources.

    1. Uninstall the widget war file.

      1. Log into WAS admin console on the Connections server.

      2. Navigate to Applications > Application Types > WebSphere enterprise applications and search for "comm.communitylibrary.war".
      3. Uninstall comm.communitylibrary.war.

    2. Remove the widget definition added to widgets-config.xml during widget configuration.

    3. Remove the resources added during widget configuration.

      1. Remove the resources files added during install to the Connections Data\shared\customization\strings directory.

      2. Remove the communities-quickr-library-config.xml and xsd files from the LotusConnections-Config directory.

      3. Check out LotusConnections-config.xml.

      4. Remove the following line of code in the <resources> element block:
        <widgetBundle prefix="quickrCommunityLibrary_res" name="com.ibm.quickr.communitylibrary.resources" />

    4. Remove J2C alias for Lotus Quickr administrative user, if not still in use for something else.

      1. Navigate to Security > Global Security > Java Authentication and Authorization Service > J2C Authentication Data.

      2. Select the J2C alias for Lotus Quickr administrator and click Delete.

    5. Restart the Communities application. In network deployments, make sure the node synchronizes before restarting Commnunities.


    Connections Widget for Microsoft SharePoint

    Install the Connections Widget for Microsoft SharePoint to share documents from a SharePoint server with community members.

    You must install Connections Plug-in for Microsoft SharePoint in order to use this widget.

    Install the SharePoint widget and make it available to community owners. A community owner can then add the widget to a community so that community members can view and edit files uploaded from a SharePoint server.


    Install the SharePoint widget for Communities

    Install the Microsoft SharePoint widget so that Community owners can make it available for members to use.

    These instructions are for installing the Connections Widget for Microsoft SharePoint for an English-language deployment. To make the widget available in other languages, follow the installation instructions in the topic Installing the non-English version of the SharePoint widget for Communities.

    This widget requires that Connections Plug-in for Microsoft SharePoint be installed before you use the widget. Before you begin, familiarize yourself with how to install widgets for the Communities application. For details, see this topic: ../com.ibm.connections.doc/admin/c_admin_communities_add_custom_widgets.html

    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.

    1. Follow the steps for checking out the widgets-config.xml, documented here: ../../com.ibm.connections.doc/t_admin_communities_develop_custom_widgets.html.

      1. Add the xml definition for the SharePoint widget to the Communities section of the widgets-config.xml:
        <widgetDef defId="SharePoint Documents" description="SharePointFiles" modes="edit view fullpage" uniqueInstance="true"
        url="/SPWidgets/SPFiles/SPFiles.xml?version={version}"
        helpLink="http://www-10.lotus.com/ldd/lcwiki.nsf/dx/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.

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

      1. Log into the Websphere Application Server console.

      2. Select Install New Application and browse for the name of the SharePoint ear file you downloaded from the Connections catalog web site: https://greenhouse.lotus.com/catalog.

      3. Accept the installation defaults, but select the cluster 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 will confirm that the application SharePointContent is installed.

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

        If starting the SharePointContent application produces errors in the WAS console, wait and try again. The installation might not be distributed to each application server.

    3. To see the widget on the Customize palette for Communities, restart the Deployment Manager, restart the server cluster, and restart the Communities application.

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

    4. If 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 Enabling 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' 

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

      1. Refer to the topic Configuring 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.

    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.

    You can configure the widget to change how users interact with the widget. To make configuration changes:

    1. Copy the sharepoint-library-config.xml and sharepoint-library-config.xsd files from the configuration folder where the SharePoint widget is installed into the LotusConnections-Config directory on the Connections server.

    2. Edit any of the variables in the sharepoint-library-config.xml file.

      Variable Description
      maxUploadSize The maximum size in MB of a file that can be uploaded through the SharePoint widget to the SharePoint server.

      This does not apply to SPNEGO and TAM configurations.

      uploadTimeout Number of seconds before an upload will timeout. For an infinite timeout, specify 0 seconds.
      authenticationType Specified the default authentication type that will be selected during widget editing, allowed values are: Windows, SPNEGO, SiteMinder, TAM, Forms, Web single sign on.
      hideAuthenticationOptions Prevents the community owner from changing the default authentication type by hiding the authentication.

    3. Save the changes and synchronize the nodes.

    4. Stop and restart the SharePointContent application.

    To support file uploads from SharePoint to Connections that exceed 50MB, edit a supplemental web configuration file. Perform these steps on all front end web servers.

    1. Copy the webconfig.IBMConnections.xml file from the configuration folder where the SharePoint widget is installed to the SharePoint CONFIG directory.

      For example: C:\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG.

    2. Open webconfig.IBMConnections.xml in an editor and change the value of the MaxRequestSize variable. Note that the value is defined in KB, not MB.

    3. Save the changes and apply the changes to the web server.

      1. Open a command window and navigate to a BIN directory.

        For example:

        c:\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

      2. Enter stsadm -o copyappbincontent

      3. Click Run.


    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.

    This widget requires that you install the Connections plug-in for Microsoft SharePoint before you use the widget. Before you begin, familiarize yourself with how to install widgets for the Communities application. For details, see this topic: ../../com.ibm.connections.doc/admin/t_admin_communities_develop_custom_widgets.html. To enable the widget for languages other than English, you should also be familiar with enabling custom strings for widgets, described in this topic: ../../com.ibm.connections.doc/customize/t_admin_profiles_add_custom_strings.dita.

    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.

    1. Follow the steps for adding a resource bundle to the LotusConnections-config.xml file, documented in the topic Adding 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 LotusConnections-config.xml.

      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 LotusConnections-config.xml.
    2. Follow the steps for checking out the widgets-config.xml, described in the topic Enabling 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 fullpage" uniqueInstance="true"
          url="/SPWidgets/SPFiles/SPFiles.xml?version={version}"
          helpLink="http://www-10.lotus.com/ldd/lcwiki.nsf/dx/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 WAS console.

      2. Select Install New Application and browse for the name of the SharePoint ear file you downloaded from the Connections catalog web site: https://greenhouse.lotus.com/catalog.

      3. Accept the installation defaults, but select the cluster 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.

        If starting the SharePointContent application results in errors in the WAS console, wait and try again. The application might not be distributed to all application servers.

    4. To see the widget on the Customize palette for Communities, restart the Deployment Manager, restart the server cluster, and restart the Communities application.

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

    5. If 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 Enabling 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 Connections is configured to use a reverse proxy that directs all Connections traffic to a single server, you must add some mapping rules so that the widget will be accessible.

      1. Refer to the topic Configuring 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.

    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 Enabling users to set a language preference.

    Related tasks:

    /ldd/lcwiki.nsf/dx/Enabling_custom_widgets_for_Communities_ic45 /ldd/lcwiki.nsf/dx/Adding_custom_strings_for_widgets_and_other_specified_scenarios_ic45 /ldd/lcwiki.nsf/dx/Enabling_users_to_set_a_language_preference_ic45


    Connections Connector for Lotus Quickr

    As administrator, you can enable IBM Lotus Quickr integration with the Communities application, allowing community members to organize and share files, and collaborate on documents from a central location.

    Integration with Lotus Quickr gives the communities in your organization a place to store and manage files. Communities associated with a team place in Lotus Quickr can aggregate updates in the community overview page, making it easier to stay current with projects and work collaboratively.

    Restriction: The new community library "draft review" feature is not supported by the Quickr connectors. The Quickr round trip editing integration will not appear within the browser for libraries that have this feature enabled.

    The Activities application can also be integrated with Lotus Quickr, allowing users to publish documents from an activity to a Lotus Quickr space.

    For more information, see Integrating Activities with IBM Lotus Quickr.

    The following prerequisites currently apply to Lotus Quickr integration with Communities:

    • The Lotus Quickr server and the Connections server must be using the same LDAP server.

    • The Lotus Quickr server and the Connections server must be in the same domain.
    • Single sign-on (SSO) must be enabled between WebSphere Application Server and Lotus Quickr. In addition, the realm name specified in the SSO configuration for both systems must match.

      For more information, see Enabling single sign-on for Lotus Quickr.

    • When using the REST API interface to create Lotus Quickr places, the user must be registered as an administrator on the Lotus Quickr server.

    Integration between Communities and Lotus Quickr is currently supported for Lotus Quickr services for WebSphere Portal and Lotus Quickr services for Lotus Domino . To find out what versions of Lotus Quickr are supported for this release of Connections, see Detailed system requirements for Connections. CAUTION:

    After you have installed the Connections Connector for Lotus Quickr, it is important that the owner of a Lotus Quickr place does not delete the place or change the membership of the place using the Lotus Quickr APIs. In addition, the Lotus Quickr administrator must not use administrative commands to delete a place or change the membership of a place. These actions might disrupt the synchronization that is carried out by the connector.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Enabling_single_signon_for_Lotus_Quickr_ic45 /ldd/lcwiki.nsf/dx/Integrating_Activities_with_IBM_Lotus_Quickr_ic45


    Install the Connections Connector for Lotus Quickr

    Install the Connections Connector for Lotus Quickr either in silent mode or by using the installation wizard.


    Use the Lotus Quickr connector installation wizard

    Install the Connections connector for Lotus Quickr to bring file-sharing capabilities and collaboration functionality to your communities.

    • You must install the Lotus Quickr connector on the Deployment Manager server. The Deployment Manager then synchronizes the changes to the remaining nodes.

    • When you plan your integration, ensure that Lotus Quickr and Connections use the same protocol – http or https.

    1. Download the connector from the Connections catalog on the following website to the Connections Deployment Manager computer:
       https://greenhouse.lotus.com/catalog

    2. From the Connector Install Directory, open the Quickr directory and run the executable file to launch the installation wizard for your deployment using one of the following commands.

      • AIX, Linux, and Linux on System z :
        install.sh

        Windows:

        install.bat

    3. Select the packages to install and click Next.
    4. Review and accept the license agreement by selecting I accept the terms in the license agreements. Then, click Next to continue.

    5. Location where you want to install the connector in the Installation Directory field, and then click Next.

    6. Select the features to install, and then click Next.

    7. Specify which Lotus Quickr deployment type you want to use.

    8. Select the Quickr Integration Selection options to enable for your deployment.

    9. Under Configuration Settings, enter the host name of the Lotus Quickr server in the Quickr server host name field.

      For example: quickr.example.com

      If your Lotus Quickr solution is integrated with IBM Tivoli Access Manager or if it uses a proxy server, then you must specify the Tivoli Access Manager or proxy server address instead of a direct remote HTTP or Lotus Quickr server address.

    10. Enter the Lotus Quickr server port number in the Quickr server port field.

      For example: 80

    11. Enter the number of the port to connect to the Lotus Quickr application over SSL in the Quickr server ssl port field.

      For example: 9443

      Do not leave this field blank. If SSL is not configured, enter 443 as the SSL port.

    12. Enter the authentication alias created by the installer for the superuser to use for managing Lotus Quickr in the J2C authentication user name field. This user name is required to authenticate.

      For example: admin Notes:

      1. If you are installing the connector in a Lotus Quickr for Lotus Domino deployment, the user provided here must have permission to create places on the Lotus Quickr server. If the Lotus Quickr server is configured to allow anyone with server access to create places, then permission does not have to be explicitly set for the user.

        For information about granting access to create places on the Lotus Quickr server, go to the following web page:

        Specify who can create places on the server

      2. In a Lotus Quickr for Lotus Domino deployment, the superuser must also be listed as an administrator on the Lotus Quickr server.

        For information about giving administrator access to more users, go to the following web page:

        Specify administrators

    13. Enter the password that is associated with the authentication alias that you provided in the previous step in the J2C authentication password field, and then click Next to continue.

    14. On the Install Locations panel, specify the location of the Connections installation home directory in the Connections install home directory field and click Validate.

      For example: C:\IBM\Connections

      The Connector libraries install location and Connector configuration install location fields are automatically populated when you specify the directory where Connections is installed.

    15. Click Next to continue.
    16. Review the summary of the information that you entered. To edit information, click Back. To start the installation, click Next.
    17. Review the results of the installation and click Finish to complete the installation process.

    After you run the installation wizard, there are a number of steps that you must perform to complete the networked installation.

    See the topic Completing the installation of the LotusQuickr connector for more information.

    By default, Connections will not pass cookies and authorization-related headers to or from external servers for feeds. To enable trusted feeds from the Lotus Quickr server for Communities, configure the Ajax proxy with the settings that you want.

    For more information, see Supporting Lotus Quickr authenticated feeds.


    Complete the installation of the Lotus Quickr connector

    When you install the Connections connector for Lotus Quickr in a network environment, you must perform a number of steps on the Deployment Manager server to complete the installation.

    Install the Lotus Quickr connector on the Deployment Manager server.

    For information about how to install the connector, see Installing the Connections Connector for Lotus Quickr.

    After you install the Lotus Quickr connector on the Deployment Manager server, perform the following steps to complete the network installation.

    1. Log in to WAS admin console for the Deployment Manager.

    2. Select System administration > Nodes, select All nodes, and then click Full Resynchronize.

    3. Select System administration > Node agents.

    4. Select the nodes that were updated, and then click Stop.

    5. Start the nodes on each node machine.

    The Lotus Quickr Delayed Synchronizer propagates community membership changes to associated Lotus Quickr places if the Lotus Quickr server is down when a community change occurs. In a networked environment, edit the communities-quickr-config.xml file to ensure that the Lotus Quickr Delayed Synchronizer is only enabled on one server.

    For more information, see Configure delayed synchronization.


    Install the Lotus Quickr connector in silent mode

    Install the IBM Lotus Quickr connector for Communities in silent mode when you want to use a response file to automate installation.

    In addition to modifying the default response files, you also can generate a silent response file with Installation Manager.

    See: Recording a response file with Installation Manager.

    To install the Lotus Quickr connector in silent mode on a AIX, Linux, or Linux on System z platform....

    1. Open a command prompt and change to one of the following directories.

      • AIX, Linux, or Linux on System z:

        LC_Connector_Install_IM\IM\linux

        Windows:

        LC_Connector_Install_IM\IM\windows

    2. Enter one of the following commands to install the connector:

      • AIX, Linux, or Linux on System z:

        install.silent.sh

        Windows:

        install.silent.bat

    To install the Lotus Quickr connector in silent mode on an IBM i platform....

    1. Download and extract the IBM Lotus Quickr Connector installation file, CQ.rsp.
    2. Customize the CQ.rsp file by inserting comment characters at the beginning of all "Installation Manager" related lines. If don't have Installation Manager 1.5.3 installed on the system, refer to the Information Center article on the Installation Manager.
      <repository location='/temp/LC_Connectors_Quickr_Install_IM/ConnectorsQuickr'/>
      
      

      The repository location '/LC_Connectors_Quickr_Install_IM/ConnectorsQuickr' is in the Lotus Quickr Connector installation package after extraction. <offering id='com.ibm.lotus.connectors.quickr' version='VERSION_DATE' profile='IBM Connectors for Quickr' features='quickr.conn' installFixes='none'/>

      The offering id and version should be coordinated to the repository.xml which in the Lotus Quickr connector installation package. <!-- Specify environment parameters for IBM Connectors for Quickr installation. --> <profile id='IBM Connectors for Quickr' installLocation='/QIBM/ProdData/Lotus/ConnectorsQuickr'> <data key='eclipseLocation' value='/QIBM/ProdData/Lotus/ConnectorsQuickr'/>

      The installLocation is user self define. <!-- Specify the host name of Lotus Quickr Server --> <data key='user.wiki.host' value='Quickr server_Hostname'/> <!-- Specify the port number of Lotus Quickr Server --> <data key='user.wiki.port' value='HTTP Port Number'/> <!-- Specify the SSL port number of Lotus Quickr Server --> <data key='user.wiki.ssl.port' value='SSL Port Number'/> <!-- Specify the authentication alias created by the installer for the superuser to use for managing Lotus Quickr in the J2C authentication user name field --> <data key='user.quickr.authUsername' value='User_Name'/> <data key='user.quickr.authPassword' value='User_PassWord'/> <!-- Specify WAS Deployment Manager profile's bin location --> <data key='user.was.userhome.bin.location' value='/QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/dmgr/bin'/>

      The location should be matched with the exact dmgr's location of the Connections environment that the Lotus Quickr is being integrated with. <!-- Specify the Connections installation location --> <data key='user.quickr.lcLocationPath' value='/QIBM/ProdData/Lotus/Connections'/>

      The location should be matched with the exact Connections installation location of the Connections environment that the Lotus Quickr is being integrated with. <!-- Specify the WEB-INF\lib directory for the Communities application as the location where the connector libraries will be installed --> <data key='user.quickr.commLibPath' value='/QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/dmgr/config/cells/cell_name/applications/Communities.ear/comm.web.war/WEB-INF/lib'/>

      The location should be matched with the exact Communities application's location of the Connections environment that the Lotus Quickr is being integrated with. <!-- Specify the LotusConnections-config directory at the WAS cell level as the location to install the connector configuration files --> <data key='user.quickr.configPath' value='/QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/dmgr/config/cells/cell_name/LotusConnections-config'/>

      The directory should be matched with the exact LotusConnections-config directory of the Connections environment that the Lotus Quickr is being integrated with. <!-- Specify the installation location for IBM Connectors for Quickr --> <data key='user.connectors.installlocation' value='/QIBM/ProdData/Lotus/ConnectorsQuickr'/> <data key='cic.selector.nl' value='en'/> </profile>

      The location should be matched with the exact installation location for IBM connectors for Quickr. <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/QIBM/Proddata/IBM/SSPShared'/>

    3. From a CL command line, run the STRQSH command to start the Qshell command shell.

    4. Change to the Installation Manager tools directory: IM_root/eclipse/tools.

    5. Run the following command to install the Lotus Quickr Connector.
      imcl input /temp/ConnectorsQuickr/CQ.rsp  -log /temp/CQInstall.log -acceptLicense


    Supporting Lotus Quickr authenticated feeds

    By default, the Connections proxy is configured to allow cookies, headers or mime types, and all HTTP actions to be exchanged among the Connections applications. It also prevents HTTP GET requests from non-Connections services and prevents all cookies or headers from being directed to the applications.

    To edit configuration files, you must use the IBM WebSphere Application Server wsadmin client.

    See Starting the wsadmin client for details.

    To make changes to the traffic that is allowed from other services, for example, to enable trusted feeds from the IBM Lotus Quickr server for Communities, you must explicitly configure it. Feeds for private communities in Lotus Quickr Domino and all feeds in Lotus Quickr Portal require authentication. By default, Connections will not pass cookies and authorization-related headers to and from external servers for feeds.

    The following policy allows GET requests to be passed to any web address. To allow users to have access to all websites, remove the comments from around this policy.

    For example, users who add a feed to a community will see a 403 error where the feed results should be displayed unless you perform this step. Be sure that the policy is listed as the last policy in the configuration file.

    <!--proxy:policy url="*" acf="none" basic-auth-support="true">
     <proxy:actions>
      <proxy:method>GET</proxy:method>
     </proxy:actions>
     <proxy:headers/>
     <proxy:cookies/>
    </proxy:policy
    When uncommented, this policy specifies that feeds can exchange GET methods with non-Connections hosts. The empty <proxy:cookies/> and <proxy:headers/> elements mean that cookies and headers are not allowed. To allow a host to exchange cookies or headers, or to perform PUT, POST, or DELETE methods, you must add a new policy that supports this.

    To create a policy that provides support for Lotus Quickr authenticated feeds...:

    1. Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
      app_server_root\profiles\Dmgr01\bin

      You must start the client from this directory or subsequent commands that you enter do not execute correctly.

    2. Open a command-line window, start the wsadmin tool, and then use the following commands to access the Connections configuration files:
      execfile("<$WAS_HOME>/profiles/<dmgrGR>/bin/connectionsConfig.py")
      execfile("<$WAS_HOME>/profiles/<dmgrGR>/bin/communitiesAdmin.py")

    3. Check out the proxy configuration file

      LCConfigService.checkOutProxyConfig("working-directory", "cell-name")

      ...where...

      • working-directory is the temporary working directory to which the configuration TPL and XSD files are copied. The files are kept in this working directory while you make changes to them.

        AIX/Linux only: The directory must grant write permissions or the command will not run successfully.

      • cell-name is the name of the WAS cell hosting the Connections application. This argument is required. It is also case-sensitive, so type it with care.

    4. Open the proxy-config.tpl file in a text editor.

    5. Add the following <proxy:policy> entry before the default policy, replacing quickrserver.example.com with the host name of your Lotus Quickr server. Be sure to insert the custom policy earlier in the code than the default policy, if one exists.

      If a web server is not used with Lotus Quickr, then a port number is required in the URL. The default ports in a non-clustered environment are 10040 for http and 10035 for https.

      <proxy:policy url="http://quickrserver.example.com/*" acf="none" basic-auth-support="true" auth-support="true">
        <proxy:actions>
         <proxy:method>GET</proxy:method>
        </proxy:actions>
        <proxy:headers>
         <proxy:header>User-Agent</proxy:header>
         <proxy:header>Accept*</proxy:header>
         <proxy:header>Content*</proxy:header>
         <proxy:header>Authorization*</proxy:header>
        </proxy:headers>
        <proxy:cookies>
         <proxy:cookie>JSESSIONID</proxy:cookie>
         <proxy:cookie>LtpaToken</proxy:cookie>
         <proxy:cookie>LtpaToken2</proxy:cookie>
        </proxy:cookies>
      </proxy:policy>
      You should also include an HTTPS policy to allow for users who choose to use or are forced to use an SSL connection.

      For example:

      <proxy:policy url="https://quickrserver.example.com/*" acf="none" basic-auth-support="true" auth-support="true">
        <proxy:actions>
         <proxy:method>GET</proxy:method>
        </proxy:actions>
        <proxy:headers>
         <proxy:header>User-Agent</proxy:header>
         <proxy:header>Accept*</proxy:header>
         <proxy:header>Content*</proxy:header>
         <proxy:header>Authorization*</proxy:header>
        </proxy:headers>
        <proxy:cookies>
         <proxy:cookie>JSESSIONID</proxy:cookie>
         <proxy:cookie>LtpaToken</proxy:cookie>
         <proxy:cookie>LtpaToken2</proxy:cookie>
        </proxy:cookies>
      </proxy:policy>
      Depending on your configuration, the <proxy:policy> section might require more or less detail. The following table lists some common cookies and headers that might be required under different configurations.


      Table 16. Common cookies or headers

      Cookie/Header Description
      SMSESSION SiteMinder session cookie that passes SiteMinder credentials to Lotus Quickr.
      PD-H-SESSION-ID Non-secure Tivoli Access Manager session cookie that passes Tivoli Access Manager credentials to Lotus Quickr.
      PD-S-SESSION-ID Secure Tivoli Access Manager session cookie that passes the secure version of the Tivoli Access Manager cookie to Lotus Quickr.
      WWW-AUTHENTICATE Secure socket layer (SSL) header that passes SSL authentication when connecting to a secure Lotus Quickr deployment.

    6. After making your changes, save and close the proxy-config.tpl file.

    7. To check in the proxy-config.tpl file:
      LCConfigService.checkInProxyConfig("working-directory", "cell-name")

    8. To exit the wsadmin client, type exit at the prompt.

    9. Stop and restart the application servers hosting Connections.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Applying_property_changes_in_Communities_ic45 /ldd/lcwiki.nsf/dx/Starting_the_wsadmin_client_ic45


    Edit the Lotus Quickr configuration file

    You can edit settings in the IBM Lotus Quickr configuration XML file to change the values that you entered at install time or to add a custom place type.

    The Quickr Connector cannot use the string customization mechanism that the core product uses.

    When you install the Connections connector for Lotus Quickr, you can specify whether to enable support for Lotus Quickr wiki and team place templates. You can also specify the host, ports, user ID, and passwords to use. The installer then updates the configuration file with this information.

    Each enabled place type shows up as a separate associated application in the Communities user interface. A maximum of five associated applications can be shown. If you need to change the information you supplied at install time, for example, if you want to disable a template that you enabled during installation, or add custom place types, you can do so by editing the communities-quickr-config.xml file. You can also edit the configuration file to change the roles associated with a Lotus Quickr place type.

    For more information, see Configure roles for Lotus Quickr places.

    When editing the communities-quickr-config.xml file, note that for each <comm:QuickrPlaceType> element, the name attribute must be unique. The <comm:managedApplicationTypeID> must also be unique and it cannot be changed. It must be 24 bytes or less.

    You use the <comm:placeTemplate> template to create a place. The <comm:server> element must match the name of a <comm:QuickrServer> element. The <comm:resourceBundleName> entry is the name of a property file on the Communities application classpath for strings presented in the user interface. The property file must have the following keys:

    • label.applicationName
    • label.applicationShortName
    • str.place.title - The value may contain a {0} placeholder for the name of the community.
    For <comm:ownersRole>, <comm:membersRole>, and <comm:publicRole> the role names can be either the role title in English or the ID field returned for the roles feed. If anonymous access is not allowed, the <comm:publicRole> element should be omitted or left empty.

    The <comm:contentFeedLink> element is the name of the link field in a place entry to be used for the place's feed. This is an optional field. For IBM Lotus Domino server, always use content as the value. For WebSphere Portal wikis, wikis and blogs are valid values. For WebSphere Portal team places, valid values are "wikis", "blogs", and "documentLibraries".

    To edit the configuration information for Lotus Quickr integration, complete the following steps:

    1. Use a text editor to open the communities-quickr-config.xml file from the following location on the file system of the Deployment Manager:

      C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\<cell_name>\LotusConnections-config

    2. Make the required changes in the file.

      For example:

      <comm:QuickrPlaceType name="DominoWiki" enabled="true">
          <comm:managedApplicationTypeID>QuickrDominoWiki</comm:managedApplicationTypeID>
          <comm:placeTemplate>Wiki</comm:placeTemplate>
          <comm:server>Domino</comm:server>
          <comm:resourceBundleName>com.example.lconn.comm.quickr.resources.QuickrWikiResources
          </comm:resourceBundleName>
          <comm:ownersRole>Manager</comm:ownersRole>
          <comm:membersRole>Editor</comm:membersRole>
          <comm:publicRole>Reader</comm:publicRole>
          <comm:contentFeedLink>content</comm:contentFeedLink>
      </comm:QuickrPlaceType>
      <comm:QuickrPlaceType name="PortalTeamPlace" enabled="true">
          <comm:managedApplicationTypeID>QuickrPortalTeamspace</comm:managedApplicationTypeID>
          <comm:placeTemplate>Team Place</comm:placeTemplate>
          <comm:server>Portal</comm:server>
          <comm:resourceBundleName>com.example.lconn.comm.quickr.resources.QuickrTeamspaceResources
          </comm:resourceBundleName>
          <comm:ownersRole>Managers</comm:ownersRole>
          <comm:membersRole>Editors</comm:membersRole>
          <comm:publicRole>Readers</comm:publicRole>
          <comm:contentFeedLink>documentLibraries</comm:contentFeedLink>
      </comm:QuickrPlaceType>
            <!--   ****************************************************************************************************         Multiple QuickServer entries are allowed.
          For each comm:QuickrServer, the name attribute must be unique.
          comm:host is the server hostname.
          comm:port is the http port number.
          comm:sslPort is the https port number.
          comm:authentry is the name of the authentication alias resource created within the WAS      Admin console     comm:serverType must match the name of a QuickrServerType
      ****************************************************************************************************           -->
          <comm:QuickrServer name="Domino">
              <comm:host>commdev01.example.com</comm:host>
              <comm:port>80</comm:port>
              <comm:sslPort>443</comm:sslPort>
              <comm:useSSL>true</comm:useSSL>            <comm:authentry>MyCell/DominoAlias</comm:authentry>
               <comm:useSSO>true</comm:useSSO>   		   <comm:serverType>Domino</comm:serverType>
          </comm:QuickrServer>
          <comm:QuickrServer name="Portal">
              <comm:host>commdev01.example.com</comm:host>
              <comm:port>10038</comm:port>           <comm:authentry>MyCell/PortalAlias</comm:authentry>
      		   <comm:serverType>Portal</comm:serverType>
          </comm:QuickrServer>

    3. Save your changes and then apply them:

      1. Log in to WAS admin console for the Deployment Manager.

      2. Select System administration > Nodes, select all the nodes, and then click Full Resynchronize.

      3. From the main Integrated Solutions Console page, select Servers > Clusters.

      4. Select the check box for the cluster that contains the nodes that you updated, and then click Stop.

      5. Select the cluster and click Start.

    4. Place the properties file in the Communities classpath.

      \profiles\AppSrv0xxx\installedApps\xxxCell\Communities.ear\comm.web.war\WEB-INF\classes\

      Where AppSrv0xxx and xxxCell must match the profile name and cell name for your deployment.

      For example, if your communities-quickr-config.xml file contains <comm:resourceBundleName>com.ibm.lconn.comm.quickr.resources.QuickrTeamspace2Resources</comm:resourceBundleName>, then create the folder structure com\ibm\lconn\comm\quickr\resources within \installedApps\<cellname>\Communities.ear\comm.web.war\WEB-INF\classes\. Place QuickrTeamspace2Resources.properties in this directory, for example \profiles\AppSrv01\installedApps\localCell01\Communities.ear\comm.web.war\WEB-INF\classes\com\ibm\lconn\comm\quickr\resources\QuickrTeamspace2Resources.properties. Make sure that QuickrTeamspace2Resources.properties file contains the three keys.

      For example:

      • label.applicationName=Europe Teamspace Wiki
      • label.applicationShortName=Teamspace Wiki
      • str.place.title=Europe Wiki for {0}

    5. After the properties files are in place for all nodes, restart Communities.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Starting_the_wsadmin_client_ic45


    Configure roles for Lotus Quickr places

    Edit settings in the IBM Lotus Quickr configuration XML file to change the roles that are associated with Lotus Quickr place types.

    When you install the Connections connector for Lotus Quickr, you can specify whether to enable support for Lotus Quickr wiki and team place templates. The installer then updates the communities-quickr-config.xml configuration file with this information. To change the roles that are associated with a Lotus Quickr place type, you can do so by editing the configuration file.

    For example, you might want to configure settings so that when users create a Lotus Quickr place that is associated with a community, the owners of the community are also owners of the Lotus Quickr place.

    For more information about editing settings in the communities-quickr-config.xml file, see Editing the Lotus Quickr configuration file.

    To edit the roles that are associated with Lotus Quickr place types...:

    1. Use a text editor to open the communities-quickr-config.xml file from the following location on the file system of the Deployment Manager:

      C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\<cell_name>\LotusConnections-config

    2. Look for the section of the file that lists the <comm:QuickrPlaceType> entries and update the values of the <comm:ownersRole>, <comm:membersRole>, and <comm:publicRole> elements for each entry as required.

      The following code is just one example of a <comm:QuickrPlaceType> entry.

      <comm:QuickrPlaceType name="DominoTeamspace" enabled="true">             <comm:managedApplicationTypeID>QuickrDominoTeamspace</comm:managedApplicationTypeID>             <comm:placeTemplate>h_StdPlaceType</comm:placeTemplate>             <comm:server>DefaultServer</comm:server>             <comm:resourceBundleName>com.ibm.lconn.comm.quickr.resources.QuickrTeamspaceResources</comm:resourceBundleName>             <comm:ownersRole>Superuser</comm:ownersRole>             <comm:membersRole>Editor</comm:membersRole>             <comm:publicRole>Reader</comm:publicRole>             <comm:contentFeedLink>content</comm:contentFeedLink>     </comm:QuickrPlaceType> 
      The following roles are supported.

      • Lotus Quickr services for Lotus Domino:

        • Author

        • Editor
        • Manager
        • Reader
        • Superuser
      • Lotus Quickr services for WebSphere Portal:

        • Contributors

        • Editors
        • Managers
        • Readers

      If anonymous access is not allowed, the <comm:publicRole> element must be omitted or left empty.

    3. Save your changes and then apply them:

      1. Log in to WAS admin console for the Deployment Manager.

      2. Select System administration > Nodes, select all the nodes, and then click Full Resynchronize.

      3. From the main Integrated Solutions Console page, select Servers > Clusters.

      4. Select the check box for the cluster that contains the nodes that you updated, and then click Stop.

      5. Select the cluster and click Start.


    Enable SSL access to the Lotus Quickr server

    To enable the use of Secure Sockets Layer (SSL), you must manually edit the communities-quickr-config.xml configuration file.

    To secure access between the Communities server and the IBM Lotus Quickr server, perform the following steps.

    1. On the file system of the Deployment Manager, use a text editor to open the communities-quickr-config.xml file from the following subdirectory:

      <WAS_HOME>/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config/communities-quickr-config.xml

    2. Set the <comm:useSSL> element to true as follows:
      <comm:useSSL>true</comm:useSSL>

    3. Save your changes and then apply them by completing the following steps.

      1. Log in to WAS admin console for the Deployment Manager.

      2. Select System administration > Nodes, select all the nodes, and then click Full Resynchronize.

      3. From the main Integrated Solutions Console page, select Servers > Clusters.

      4. Select the check box for the cluster that contains the nodes that have been updated, and then click Stop.

      5. Select the cluster and click Start.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Starting_the_wsadmin_client_ic45


    Integrate with SiteMinder and Tivoli Access Manager

    If you enabled Connections to use Computer Associates' SiteMinder or IBM Tivoli Access Manager for user authentication and single sign-on (SSO), and you configured your deployment for integration with Lotus Quickr, you must manually edit the communities-quickr-config.xml configuration file to disable the use of SSO. SSO must also be disabled when you use SPNEGO; otherwise the Lotus Connectors will not function properly.

    When integrating Lotus Quickr with Connections, note that you must perform additional steps to secure Lotus Quickr when Tivoli Access Manager is enabled.

    For more information, go to the following web page:

    Configure TAM and WebSEAL with Lotus Quickr

    To disable SSO for Lotus Quickr...:

    1. Use a text editor to open the communities-quickr-config.xml file from the following subdirectory on the file system of the Deployment Manager.

      <WAS_HOME>/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config/communities-quickr-config.xml

    2. Set the <comm:useSSO> element to false as follows:
      <comm:useSSO>false</comm:useSSO>

    3. For a Tivoli Access Manager environment only, add a junction in contextPath as follows:
      <comm:QuickrServerType name="Domino">
               <comm:contextPath>QuickrD_Junction/dm/atom/</comm:contextPath>
               <comm:publicEntry  id="oid:null"><member type=&quot;user&quot; dn=&quot;Anonymous&quot;/&gt;</comm:publicEntry>
               <comm:publicEntry  id="oid:null"><member type=&quot;user&quot; dn=&quot;Default&quot;/&gt;</comm:publicEntry>
      </comm:QuickrServerType>

    4. Save your changes and then apply them by doing the following:

      1. Log in to WAS admin console for the Deployment Manager.

      2. Select System administration > Nodes, select All nodes, and then click Full Resynchronize.

      3. From the main Integrated Solutions Console page, select Servers > Clusters.

      4. Select the check box for the cluster containing the nodes that have been updated, and then click Stop.

      5. Select the cluster and click Start.
    Related tasks:

    /ldd/lcwiki.nsf/dx/Enabling_single_signon_for_SiteMinder_ic45 /ldd/lcwiki.nsf/dx/Enabling_single_signon_for_Lotus_Quickr_ic45


    Use the Lotus Quickr Delayed Synchronizer

    The IBM Lotus Quickr Delayed Synchronizer propagates community membership changes to Lotus Quickr places if the Lotus Quickr server is down when changes in community membership are made.

    You can edit configuration property settings to control the delayed synchronization task, and use administrative commands to mark the communities containing links to Lotus Quickr Wikis or Teamspaces for full membership synchronization. Marking a community in this way forces a full membership and visibility (public or private access) synchronization to the Lotus Quickr Teamspace or Lotus Quickr Wiki server the next time that the synchronization task runs.


    Configure delayed synchronization

    When you install the IBM Lotus Quickr connector, the delayed synchronization task is automatically configured with default settings. To change those settings to values that better suit your deployment, you need to edit the <QuickrDelayedSync> settings in the communities-quickr-config.xml file.

    The Lotus Quickr Delayed Synchronizer reconciles inconsistencies in membership synchronization between a Lotus Quickr place and its associated community. A community's membership might go out of synchronization from time to time, for example, if the Lotus Quickr server is down when new members are being added to or deleted from a community. The Delayed Synchronizer looks at all the communities that have been modified in the past 14 days to check if the membership between the communities and the associated Lotus Quickr places has fallen out of synchronization. The synchronizer then propagates any changes to the Lotus Quickr place at a later time.

    To configure delayed synchronization between Lotus Quickr places and their associated communities... on the file system of the Deployment Manager:

    1. Navigate to the following subdirectory to locate the communities-quickr-config.xml file:
      <WAS_HOME>/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config/
      communities-quickr-config.xml

    2. Open the file with a text editor and navigate to the end of the file to locate the QuickrDelayedSync settings. The QuickrDelayedSync task information looks similar to the following:
      <comm:QuickrDelayedSync enabled="true">
      <comm:startDelay value="60"/> <!-- minutes -->
      <comm:taskInterval value="60"/> <!-- minutes -->
      <comm:daysBackToScan>14</comm:daysBackToScan>
      </comm:QuickrDelayedSync>

    3. Update the settings as required. The following table displays information regarding the QuickrDelayedSync properties and the type of data that you can enter for them:


      Table 17. QuickrDelayedSync properties

      Property Description
      QuickrDelayedSync.enabled Enables synchronization to occur. This property takes a Boolean value: true or false.
      QuickrDelayedSync.startDelay The delay in minutes before the task starts. This property takes an integer value.
      QuickrDelayedSync.taskInterval The delay in minutes between consecutive tasks. This property takes an integer value.
      QuickrDelayedSync.daysBackToScan Limits the search for community changes. The default value of 14 indicates that only communities that have been modified in the past two weeks will be checked for missed propagations. This property takes an integer value.

    4. Save your changes to the communities-quickr-config.xml file.

    5. To apply your changes, stop and restart the Communities server.

    When you have multiple WebSphere Application Servers running the Communities application, you must ensure that the Lotus Quickr Delayed Synchronizer is only enabled on one server by doing the following:

    1. On the file system of the Deployment Manager, open the communities-quickr-config.xml file in a text editor. Edit the file so that the <comm:serverToRunOn> element contains a string in the following format:

      cellname\nodename\servername

      For example:

      <comm:serverToRunOn>acmeNode01Cell\acmeNode01\server1</comm:serverToRunOn>

    2. Save your changes and then apply them by doing the following:

      1. Select System administration > Nodes, select all the nodes, and then click Full Resynchronize.

      2. From the main Integrated Solutions Console page, select Servers > Clusters.

      3. Select the check box for the cluster containing the nodes that have been updated, and then click Stop.

      4. Select the cluster and click Start.


    Marking a community for synchronization

    The IBM Lotus Quickr Delayed Synchronizer should automatically propagate changes after a Lotus Quickr server outage; however, in unusual circumstances, such as restoring a Lotus Quickr place from backup, you might want to force a full synchronization to occur. You can mark an Connections community that contains links to a Lotus Quickr Wiki or Teamspace so that the synchronizer performs a full synchronization between the membership of the place and the membership of its associated community when the synchronization task next runs.

    To use administrative commands, you must use the wsadmin client.

    See Starting the wsadmin client for details.

    The Lotus Quickr Delayed Synchronizer propagates community membership changes to associated Lotus Quickr places if the Lotus Quickr server is down when a community change occurs. The synchronizer also grants or removes public access to match the associated community's visibility. The synchronizer runs hourly by default.

    You need to ensure that the delayed synchronization task is only enabled on one server in the cluster.

    For more information, see What to do next in the topic Configuring delayed synchronization.

    To mark a community for synchronization....

    1. start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
      app_server_root\profilesDmgr01\bin
      where app_server_root is the WebSphere Application server installation directory and Dmgr01 is the Deployment Manager profile directory, typically dmgr01.

    2. Start the Communities Jython script interpreter
      execfile("communitiesAdmin.py")
      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.

    3. Use the ManagedAppService.addLinkProperty command to update the association between a community and a remote application by adding the NEEDS-TO-BE-SYNCED key property and setting it to true.

      When fetching a link for a community application, to fetch a Lotus Quickr Portal Wiki, use QuickrPortalWiki, and to fetch a Lotus Quickr Portal team place, use QuickrPortalTeamspace.

      For example:

      wsadmin>bycommname=CommunitiesService.fetchCommByName("<community name>")
      wsadmin>link=ManagedAppService.fetchLinkByCommApp(bycommname,"QuickrPortalWiki")
      wsadmin>link2=link.get(0)
      wsadmin>ManagedAppService.addLinkProperty(link2,"NEEDS-TO-BE-SYNCED","true")


    Results

    The Lotus Quickr Delayed Synchronizer performs a full membership synchronization between the Lotus Quickr place and the associated community when the synchronization task is next run.


    Uninstalling the Lotus Quickr connector

    Use the uninstaller to remove the Connections Connector for Lotus Quickr from your system.

    To uninstall the Lotus Quickr connector:

    1. Run the uninstaller by doing one of the following:

      • AIX, Linux, or Linux on System z:

        1. Open a command prompt and change to this directory:

          InstallationManager_directory/eclipse/

        2. Enter the following command:

          chmod +x launcher

        3. Then enter the following command:

          ./launcher

        Windows:

        1. Open a command prompt and change to this directory:

          InstallationManager_directory/eclipse/

        2. Enter the following command:

          launcher.exe

      Alternatively, double-click the launcher.exe file in the eclipse directory.

    2. Select the language to use for the uninstallation process and click Next.
    3. Review the summary panel to verify that the applications to remove are present. To make any changes, click Back to edit the values that you input. Click Next to begin the uninstallation process.
    4. Review the results of the uninstallation and click Finish to close the wizard.


    Uninstalling the Lotus Quickr connector in silent mode

    Uninstall the IBM Lotus Quickr connector for Communities in silent mode when you want to use a response file to automate the procedure for removing the connector from your system.

    Before starting the following procedure, you need to install the Installation Manager.

    For more information, see Installing the Lotus Quickr connector in silent mode.

    To uninstall the Lotus Quickr connector in silent mode on the AIX, Linux, or Microsoft Windows platforms....

    1. Open a command prompt and enter one of the following commands.

      • AIX, Linux, or Linux on System z:
        generate_other_responsefile.sh

        Windows:

        generate_other_responsefile.bat

    2. Click Uninstall in the first panel and complete the uninstall process. After you do this, a response file named LC.rsp is generated in the following directory:

      \LC_Connectors_Install_IM\ConnectorsQuickr

    3. Change to one of the following directories.

      • AIX, Linux, or Linux on System z:

        LC_Connector_Install_IM\IM\linux

        Windows:

        LC_Connector_Install_IM\IM\windows

    4. Start the silent uninstall.

      1. Change to one of the following directories.

        • AIX, Linux, or Linux on System z:

          .\InstallationMananger\eclipse

          Windows:

          C:\IBM\Installation Manager\eclipse

      2. Enter one of the following commands to uninstall the connector.

      • AIX, Linux, or Linux on System z:
        ./IBMIM --launcher.ini silent-install.ini -input <LC_HOME>/silentResponseFile/LC_uninstall.rsp -log ./uninstall.log

        Windows:

        .\IBMIMc.exe --launcher.ini silent-install.ini -input <LC_HOME>\silentResponseFile\LC_uninstall.rsp -log .\uninstall.log

    To uninstall the Lotus Quickr connector in silent mode on the IBM i platform....

    1. On a CL command line, run the STRQSH command to start the Qshell command shell.

    2. Change to the Installation Manager tools directory: IM_root/eclipse/tools.

    3. Run the following command to retrieve the Lotus Quickr connector version and installation directory where the Lotus Quickr connector is installed.
      imcl listInstalledPackages -long 

    4. Run the following command to uninstall the Lotus Quickr connector. Use the Lotus Quickr connector version and installation directory you retrieved in the previous step.
      imcl uninstall com.ibm.lotus.connectors.quickr_VERSION_DATE -installationDirectory Lotus_Quickr_connector_installation_directory


    Upgrading the Lotus Quickr connector

    To upgrade to a newer version of the Connections Connector for Lotus Quickr, uninstall the existing connector before installing the new connector.

    When you upgrade to a new version of the Lotus Quickr connector, the existing connector data is preserved. However, if you customized the configuration files for the previous version of the connector, you need to make those configuration changes again after installing the new version of the connector.

    1. Uninstall the existing Lotus Quickr connector.

      For more information, see Uninstalling the Lotus Quickr connector.

    2. Install the new version of the Lotus Quickr connector.

      For more information, see Installing the Connections Connector for Lotus Quickr.

    Repeat any customization changes that you made to the previous configuration if required.


    creating a list of supported Lotus Quickr servers for Communities

    You can provide a list of the supported IBM Lotus Quickr servers to the proxy server to ensure that it honors any requests made for access to one of the supported Lotus Quickr servers. This is an optional task.

    You must have Lotus Quickr deployed in your enterprise before you can perform this procedure. You must also have administrative access to the IBM WebSphere Application Server where the Communities application is installed.

    1. Go to WAS admin console for the server hosting the Deployment Manager.

    2. Expand Resources > Resource Environment, and then click Resource Environment Providers.

    3. Click QuickrWhitelistProvider from the list, and then click Custom properties.

    4. Create one custom property for each Lotus Quickr server to enable users to access. To create a custom property, enter values in the following fields:

      If you upgraded a stand-alone deployment which was already configured to integrate with Lotus Quickr to a network deployment, you must recreate these custom properties for the provider on the cluster's cell. The custom properties must be redefined because they are lost when you federate the node into a cluster.

        name
        Create a property name that begins with the term allow.

        For example:

        allowQuickrPrimary.example.com

        value
        Specify the fully qualified domain name of the Lotus Quickr server or its IP address. Do not specify the protocol, nor any port numbers.

        To enable users to access several servers within a specific domain, specify the parent domain in this field. You must start the string with a period (.).

        For example, if you were to specify .example.com, the proxy would allow the file to be published to all the servers that are available from subdomains of example.com.

        The provider does not convert IP addresses to domain names nor the other way around. If the server is requested using both identifiers, create two properties: one property that specifies the domain name in the value field and one that specifies the IP address in the value field.

    5. Repeat the previous step for every Lotus Quickr server to add to the list of supported servers.


    Use plug-ins from Connections in other products

    Get help using the plug-ins that bring the capabilities of Connections to other products.


    Use the Connections Portlets for WebSphere Portal

    Use the Connections Portlets for WebSphere Portal to interact with Connections from a Portal application.


    Personalizing a portlet

    Specify or edit the login name and password you use to access Connections.

    Personalize options are available when basic authentication is in use. The personalize options are not available if the deployment is configured to use single-sign on.

    If you do not know the user name and password for accessing an Connections service, consult with your Connections administrator. To personalize a portlet:

    1. Select Personalize from the portlet menu.

    2. Enter a User Name and Password or update this information if your password changes.

    3. Click OK to save your changes or Cancel to return to the view without saving your changes.


    Import the Connections certificate for your browser

    Import the security certificate for Connections to avoid warnings from your browser.

    In order to view bookmark and activity icons, you must import a security certificate. If you do not, your browser will put up security alerts when it displays Connections icons. Additionally, the Activity Stream portlet will not work correctly if you do not import the certificate. You will be prompted with an error message to access Connections and install the security certificate if it is not detected.

    Follow the steps for the browser you are using.

    1. To install a certificate for Microsoft Internet Explorer version 6.x:

      1. Open the Internet Explorer browser and navigate to your Connections Server over https.

        For example: https://connections.acme.com:9443/activities .

      2. Click the Certificate icon.

      3. Click Install Certificate.
      4. Follow the steps in the Install Certificate wizard. Keep the default settings and respond "Yes" to the security warning.
      5. Following the installation, log onto the IBM WebSphere Portal server running the Connections portlets and verify you do not get the security warning when you use the Activities, Bookmarks, or Activity Stream portlets.

    2. To install a certificate for Microsoft Internet Explorer version 7.x and later:

      1. Open the Internet Explorer browser and navigate to your Connections Server over https.

        For example: https://connections.acme.com:9443/activities .

      2. Click the Certificate Error dropdown.

      3. Click View Certificates.

      4. Click Install Certificate.
      5. Follow the steps in the Install Certificate wizard. Keep the default settings and ignore any security warning.
      6. Following the installation, log onto the IBM WebSphere Portal server running the Connections portlets and verify you do not get the security warning when you use the Activities, Bookmarks, or Activity Stream portlets.

    3. To install a certificate for Firefox Mozilla version 3x and later:

      1. Open Firefox Mozilla browser and navigate to your Connections Server over https.

        For example: https://connections.acme.com:9443/activities . You will be prompted with a security warning.

      2. Click the Or you can add an Exception link on the security dialog box.

      3. Click Add Exception.

      4. Click Get Certificate.
      5. Follow the steps in the Install Certificate wizard.
      6. Following the installation, log onto the IBM WebSphere Portal server running the Connections portlets and verify you do not get the security warning when you use the Activities, Bookmarks, or Activity Stream portlets.


    The Activities portlet

    With the Activities portlet, you can view and create activities, and work with to do items.


    Use the Activities portlet

    Use the Activities portlet to interact with the Connections Activities features. Use activities to organize your collaborative work without leaving your IBM WebSphere Portal environment.

    The Activities Detail portlet has two views, My Activities and To Dos List.

    The My Activities view displays activities that you created or that you belong to. From the My Activities view you can:

    • Click Start an Activity to create an activity. Assign it a title and optionally enter a description, goal, or tags. Add members for your activity and save it to add it to your list.

    • Click Completed to view completed activities.

    • Click High priority to view activities that are flagged as needing your immediate attention.

    • Click Medium priority to view activities that are not as pressing.
    • Sort the view by clicking the column header for Last Updated or by Due Date.

    Click an activity name to open it. From the activity, you can:

    • Click Add to do item to create a to-do item. You can assign it to yourself or to another user. You can also optionally assign a priority, due date, tags, and a description.

    • Click Add Entry to add an entry to the activity.

    • Click Add Section to create a section to keep your activity organized.
    • Respond to a to-do item by marking it complete, or click More to add a comment, edit, or delete the to-do item.

    • If you are the activity owner, click Members to add members to the activity. You can assign a member owner, author, or reader access.
    • View emails and chat transcripts that are saved to the activity. Comment on this content or create associated to do items.


    Edit the shared settings for the Activities portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal wiki. Settings you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet:


    Configure the Activities portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Display icon to open Connections in a browser window Display an icon that opens Connections in a browser so users can fully access the application.
    Display link to open Connections in a browser window Activity title links to open the recent updates page for that activity in a browser window.
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the check box to display paging controls in the header as well as the footer of the page.


    The Activity Stream portlet

    Find out what is new in your network and the wider organization using the activity stream views available from the Activity Stream portlet.


    Use the Activity Stream portlet

    Make sure you have imported the Connections security certificate for your browser or this portlet will not work properly. For details, see Importing the Connections certificate for your browser.

    The Activity Stream portlet has three possible modes for displaying information: Homepage Experience, Community Experience, and Profile Board Experience. The mode controls what types of activity you see in the portlet. When the Activity Stream portlet is added to a page, it will default to the Homepage Experience mode unless the page is a community page, in which case it defaults to the Community Experience mode and displays updates from the associated community. To see the Profile Board experience, you must explicitly configure that option for the portlet.

    You can use the activity stream to view the latest news stories and updates from across Connections. The updates are displayed in list format, making it easy for you to scan through the entries and quickly identify the updates that are most important to you. Interact with and respond to content faster.

    Only one Activity Stream portlet on a portal page is supported.

    A variety of views are available in the Activities Stream portlet. The views available depend on the mode you choose.

    Select a view from the Show list. The following views are available when you are viewing the Homepage Experience mode for the Activity Streams portlet:

    View Description
    I'm Following Displays updates related to the people and content that you are following.
    Status Updates Display the latest status update messages from across your organization.
    My Notifications Display the latest notifications that you received and sent in Connections.
    @Mentions Displays messages that mention you directly.

    This feature requires Connections 4.5 or later. The view does not display if you are using Connections 4.0.

    Action Required Displays your latest to-do items from Activities, network and community invitations, requests to join moderated communities, and any third-party events requiring an action on your part.
    Saved Display the updates that you saved.
    Discover Display the latest public updates from all the applications.

    For details, see the Homepage Views article in the Connections wiki.

    By default, all updates display in the view. To filter the view, for example, to see only the updates for communities you follow when you are using the Homepage Experience mode, click a component name in the Filter By list.

    There is no Filter By option in the Community Experience.

    Follow these guidelines for working with content in the activity stream.

    • To show that you like an update or a comment on a status update, click Like, if this feature is enabled for your deployment. You can tell how many people liked an update or comment from the number that displays next to the Like icon. Click the icon to see who liked the update or comment.

    • To comment on an update, hover over the update and click Comment. Enter your comment in the field, and then click Post.

    • To mention a colleague in your comment and share the comment directly with them, enter the at (@) symbol followed by the person's name, and then select the person's name from the drop-down list that displays. When you post the comment, the person's name is linked to their profile. A message is also posted to the person's profile to let them know that you mentioned them.

      This feature may not be available in your deployment.

    • To delete a comment that you added, hover over the comment, click the Delete comment icon, and click Delete.

    • To save an update for following up later, hover over the update and click Save this.

    • To stop receiving updates about an item or person, click Stop Following.

    • To access more options for working with an update, hover over the update and click it. The options that display depend on the type of update you are looking at and what is enabled in terms of embedded experience.

      For example, to share a status update with the people who are following you, click Repost. To close the window, click the X icon or click anywhere outside the window.


    Edit the settings for the Activities Stream portlet

    You can personalize the portlet to show the mode and features to see. If you have at least editor access for the page and for the portlet choose Edit Shared Settings and choose what displays by default when users access the portlet.

    For more information about access levels, see the WebSphere Portal wiki. To edit the settings for yourself, choose Personalize from the portlet menu and choose what to display. Settings in the Personalize panel overwrite settings in the Edit Shared Settings panel. If you have administrator access to the Portal application, you can also set these options by choosing Configure from the portlet menu. Options set using the Configure panel apply to all portlets but can be overwritten by settings made in the Edit Shared Settings or Personalize panels.

    Choose the mode for the portlet.

    If you do not explicitly select a mode, no radio buttons appear as selected and the portlet defaults to the Homepage Experience for a stand-alone portlet, or the Communities Experience for a portlet on a community page.

    Mode Description
    Homepage Experience Homepage Experience is the default unless the Activity Stream portlet is placed on a Community page.
    Communities Experience Communities Experience is the default when the Activities Stream portlet is placed on a Community page. Choose Recent Updates or Status Updates to view updates from the community that is associated with the Portal page.
    Profile Board Experience Profile Board Experience displays the stream as you would see it on a Connections profile associated with the page for a profile that's displayed in the profiles portlet. To use the Profile Board experience, either navigate to a profile or identify the user you want to follow and pin the user's profile in the Profiles portlet.

    1. Add the Profiles portlet to the page containing the Activity Stream portlet. Depending on how the Profiles portlet is configured, you might see a message that you need to pin a user to display their activity in the Activity Stream portlet.
    2. Configure the Activity Stream portlet to show the Profile Board experience.

    3. To view the profile board for a person:

      • In the Profiles portlet, click on a profile picture in the Network section of the profile being displayed, or click any name in the Same Manager, People Managed or Full Report-to Chain views. Or, click Find a Profile to search for and choose the person whose board you want to view.

      • Choose Edit Shared Settings from the portlet menu on the Profiles portlet and select Always pin to the current profile or Dynamically pin to the most recently selected profile.

        Selecting Always pin to the current profile always displays the profile of the person selected when the pin is applied. Selecting Dynamically pin to the most recently selected profile allows the administrator to dynamically pin to the last profile viewed in the Profiles portlet at any given time.

    Choose which of the following features to display in the portlet:

    • Status Updates displays a text box so you can enter a status update.

    • Activity Stream displays updates about content you are following.
    • Embedded Experience allows you to view and interact with content.


    The Blogs portlet

    The Connections Blogs detail portlet gives you access to your blogs from within IBM WebSphere Portal.


    Purpose

    Use the Blogs portlets to interact with the Connections Blogs feature so you can read or contribute to blogs without leaving the IBM WebSphere Portal environment. You can also view and contribute to Ideation Blogs you can access. Ideation blogs, unlike standard blogs, are used to generate and promote ideas in a community.

    • If the Blogs portlet is deployed on a community page, Ideation blogs can display in the portlet if the Show Ideation blog in this community option is checked on the Edit shared settings.

      The option to show ideation blogs is not available as a setting if the Blogs portlet is on a stand-alone page or if there is no Ideation blog in the associated community.

    • If the Blogs portlet is deployed on a stand-alone page, and you are in the My Blogs view, you can click a blog to see the entries but you cannot click entries created by other users. To enter comments, vote for an idea, or recommend an entry, open Blogs in the web application.
    • Pin options in the Blogs Edit Shared Settings mode are not available from the My Blogs view of the portlet. You can pin the Blogs portlet only from the public views (Latest Entries and All Blogs.)

    The Blogs Detail portlet has three views, Latest Entries, All Blogs, and My Blogs.

    The Latest Entries view displays recent entries and comments posted to blogs. From this view, you can:

    • Click an entry to read it. If comments are enabled, you can add a comment.

    • Click an idea to read it or vote on it.

    • Click the name of a contributor to view the associated business card.
    • Sort the view by Date, Title, Likes/Votes, Comments, or Visits.

    The All Blogs view lists all blogs for your organization. From this view, you can:

    • Click the name of a blog to open it and view the entries.

    • Click the name of an Ideation Blog to open it so that you can view the ideas and view voting activity.
    • Vote on an idea.

    • Click More to view details for the blog, such as a description or tags.

    • Click the name of a blog owner to view the associated business card.

    The My Blogs view lists blogs for which you are an owner or member. From this view, you can:

    • Click the name of a blog to open it. You can view the entries and comments or create an entry.

    • Click the name of an Ideation Blog to open it so that you can view the ideas and view voting activity.

    • Click Settings to edit the basics for a blog, including the title, description, and tags. You can also add blog owners, authors, or draft users.

    • Click Start a Blog to start a new blog.

      You cannot create an Ideation Blog from the Blogs portlet because it must be created within a community.


    Edit the shared settings for the Blogs portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet:


    Configure the Blogs portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Profile photos for Latest Entries Displays author pictures next to blog entries.
    Display icon to open Connections in a browser window Display an icon that opens Connections in a browser so users can fully access the application.
    Display link to open Connections in a browser window Opens Connections in a browser window so that users can interact with the full application.
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the check box to display paging controls in the header as well as the footer of the page.


    The Blogs Summary portlet

    The Connections Blogs Summary portlet gives you a targeted view of your blogs activity from within IBM WebSphere Portal.


    Purpose

    Use the Blogs Summary portlet to display a targeted view of blogs, such as most popular blogs.

    The Blogs Summary portlet has two views:

    • Recommends displays the most recommended blogs.
    • Date displays blogs with the newest first.


    Edit the shared settings for the Blogs Summary portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information on access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet:


    Configure the Blogs Summary portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Homepage Handle Enter the Homepage Handle for your Blogs deployment.
    Display link to open Connections in a browser window Opens Connections in a browser window so that users can interact with the full application.


    The Bookmarks portlet

    The Connections Bookmarks portlet gives you access to your bookmarks from within IBM WebSphere Portal.


    Use the Bookmarks portlet

    use the Bookmarks portlet to access your Connections bookmarks without leaving the IBM WebSphere Portal environment. The portlet has two views, All Bookmarks and My Bookmarks.

    The All Bookmarks view displays bookmarks you created as well as bookmarks shared with you by others in your organization. The My Bookmarks view displays only the bookmarks that you created. You can click the More option for a bookmark to edit or delete it.

    From the All Bookmarks or the My Bookmarks view you can:

    • Click a bookmark to visit the web page.

    • Click More to view details about the bookmark.

    • Click the name of a bookmark owner to view the associated business card.
    • Sort the view by clicking the column header for Date or by Popularity.

    The My Blogs view lists blogs for which you are an owner or member. From this view, you can:

    • Click the name of a blog to open it. You can view the entries and comments or create an entry.

    • Click the name of an Ideation Blog to open it so that you can view the ideas and view voting activity.

    • Click Settings to edit the basics for a blog, including the title, description, and tags. You can also add blog owners, authors, or draft users.

    • Click Start a Blog to start a new blog.

      You cannot create an Ideation Blog from the Blogs portlet because it must be created within a community.


    Edit the shared settings for the Bookmarks portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. You can choose either My Bookmarks, All Bookmarks, or both.


    Configure the Bookmarks portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the check box to display paging controls in the header as well as the footer of the page.


    The Bookmarks Summary portlet

    The Connections Bookmarks Summary portlet gives you a targeted view of your bookmarks from within IBM WebSphere Portal.


    Use the Bookmarks Summary portlet

    Use the Bookmarks Summary portlet to integrate a specific view of Bookmarks into a Portal application. The portlet has three views:

    • Public Bookmarks lists all public bookmarks. This is the only view where you can filter the bookmarks by pinning a tag.
    • Most Popular Bookmarks lists the web pages most frequently bookmarked.
    • Most Visited Bookmarks lists the bookmarks that receive the most clicks.


    Edit the shared settings for the Bookmarks portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet.


    The Profiles Portlet

    The Connections Profiles portlet gives you access to your profile and network information from within IBM WebSphere Portal.


    Use the Profiles portlet

    Access your profile and network information without leaving the IBM WebSphere Portal environment. The portlet has two views, Status Updates and My Profile.

    From the Status Updates view, you can:

    • Post your status
    • View your status history
    • View the status for other people in your network

    • Comment on other people's status

    • Delete comments or status you posted

    • Search Profiles by name, tag, or keyword
    From the My Profile view, you can:

    • View and update your profile information (This feature takes you to Connections Profiles)
    • View report-to chain for yourself or your colleagues
    • View network information for yourself or your colleagues

    • Search Profiles by name, tag, or keyword

    • Invite people to join your network
    • View, accept, or decline invitations to join other networks
    • Send email to colleagues or display their business card


    Edit the shared settings for the Profiles portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. Choose which views to display in the portlet. You can choose Status Updates or My Profile.


    Configure the Profiles portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Enable this will provide link to the External Connections UI for editing profile Displays an Edit Profile link so that users can update their profiles in the Connections web application.
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the checkbox to display paging controls in the header as well as the footer of the page.


    The Profiles Summary portlet

    Use the Connections Profiles summary portlet to add a targeted view of profile and network information to an IBM WebSphere Portal application.


    Use the Profiles portlet

    Use the Connections Profiles summary portlet to add a targeted view of profile and network information to an IBMWebSphere Portal application. The portlet has two views, Status Updates and My Profile.

    From the Status Updates view, you can:

    • Post your status
    • View your status history
    • View the status for other people in your network

    • Comment on other people's status

    • Delete comments or status you posted

    • Search Profiles by name, tag, or keyword
    From the My Profile view, you can:

    • View and update your profile information (This feature takes you to Connections Profiles)
    • View report-to chain for yourself or your colleagues
    • View network information for yourself or your colleagues

    • Search Profiles by name, tag, or keyword

    • Invite people to join your network
    • View, accept, or decline invitations to join other networks
    • Send email to colleagues or display their business card


    Edit the shared settings for the Profiles portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. Choose which views to display in the portlet. You can choose Status Updates or My Profile.


    Configure the Profiles portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Enable this will provide link to the External Connections UI for editing profile Displays an Edit Profile link so that users can update their profiles in the Connections web application.
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the check box to display paging controls in the header as well as the footer of the page.


    The Tags portlet

    The Connections Tags portlet gives you access to your profile and network information from within IBM WebSphere Portal.


    Use the Tags portlet

    Us the Tags portlet to access Connections content by user-defined tags, or keywords. You can see tags for all Connections content or associate tags with a narrower content source, such as a blog or community.


    Edit the shared settings for the Tags portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Choose Edit Shared Settings from the portlet menu and choose the Connections applications for which you want to display tags.


    Configure the Tags portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description

    • Include tags for public content only

    • Include tags for public content and private content
    Specify whether to display tags for public content only or for public as well as your private content.


    The Wikis portlet

    The Connections Wikis portlet brings the collaborative power of an Connections wiki to IBM WebSphere Portal.


    Use the Wikis portlet

    Use the Wikis portlet to interact with the Connections Wikis feature so you can access content without leaving the IBM WebSphere Portal environment.


    Edit the shared settings for the Wikis portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. You can choose to display:

    • All wikis

    • A list of all wiki pages for this community (default)

    • The currently selected wiki page

    • The most recent wiki page for this community


    Configure the Wikis portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Display icon to open Connections in a browser window Display an icon so users can open Connections in a browser window to access the full application.
    Display link to open Connections in a browser window Allow links from the wiki to open Connections in a browser window.
    Display page controls only in bottom bar Hides the page controls at the top of the window. Clear the check box to display paging controls in the header and footer of the page.


    The Community Overview portlet

    Use the Community Overview portlet to display information from an Connections community in an IBM WebSphere Portal application.


    Use the Community Overview portlet

    Use the Community Overview portlet to display any of the following information from an IBM Community:

    • Community icon
    • Community name
    • Community owners
    • Tags
    • Community description
    • Community Type

    A portlet page that contains a community overview portlet has membership that is scoped to the community membership. If you leave the community, you no longer have access to the portal page and are taken to the home page for the portal application.


    Edit the shared settings for the Community Overview portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which information from the community you want to display in the portlet.


    The Forums portlet

    The Connections Forums portlet brings the collaborative power of an Connections forum to IBM WebSphere Portal.


    Use the Forums portlet

    Use the Forums portlet to interact with Connections Forums content without leaving the IBM WebSphere Portal environment. You can read topics, create new topics, or comment on topics.


    Edit the shared settings for the Forums portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. You can choose to display:

    • All forum topics for this community (default)

    • The most recent forum topic for this community

    • The currently selected forum topic for this community


    Configure the Forums portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Display icon to open Connections in a browser window Display an icon so users can open Connections in a browser window to access the full application.
    Display page controls only in bottom bar Hides the page controls in the header of the window. Clear the check box to display paging controls in the header as well as the footer of the page.


    The Forums Summary portlet

    The Connections Forums summary portlet displays a targeted view of Forums in your WebSphere Portal application.


    Use the Forums summary portlet

    Use the Forums Summary portlet to insert a targeted view of Forums content in a WebSphere Portal application. Choose one of the following views:

    • All Topics lists all of the forums topics for the logged-in user. It does not list public forum topics.

    • Open Questions lists the questions that await answers in the forum.

    • Answered Questions lists the answered questions in the forum.

    • Topics Followed by User lists the topics that the logged-in users asked to follow.

    The Forums Summary portlet displays forum entries for the logged-in user only and does not display public forum entries that are not associated with the user.


    Edit the shared settings for the Forums Summary portlet

    You must have at least editor access for the page and for the portlet to be able to edit shared settings for Connections features.

    For more information about access levels, see the WebSphere Portal product wiki. Settings that you enter on this page can be overridden by settings on the Personalize page for a portlet. Choose Edit Shared Settings from the portlet menu and choose which view to display in the portlet. You can also choose to display topics that are filtered by a tag you specify, turn on or off the display of replies in the portlet, and specify the number of topics to display.


    Configure the Forums portlet

    You must have administrative access to the portlet to be able to configure it. Choose Configure from the portlet menu and configure these options:

    Option Description
    Display link to open Connections in a browser window Display a link so users can open Connections in a browser window to access the full application.


    Use the Connections Desktop Plug-ins for Microsoft Windows

    Use the plug-ins to share files and information between Microsoft Windows applications and Connections or IBM SmartCloud.

    The following features are available for Microsoft Windows Explorer:

    • Upload local files from Windows Explorer or from your desktop
    • Share uploaded files with people, communities, or folders in Connections
    • Work on files locally and publish them to Files, communities, Activities, or Wikis
    • View people's contact details and get in touch with them
    • Pin, follow, or like files and folders
    • View or contribute comments for a file
    • Lock a file when you are editing it to prevent file conflicts
    • View and restore files from trash
    • Share folders with Communities

    The following features are available for Microsoft Office (Word, Excel, PowerPoint):

    • Features added to Word:

      • Add a document to Files or Communities

      • Attach a document to an Activity or Wiki page
      • Publish a document to a Blog entry

      • Add someone's profile information into a document

      • Add a bookmark from Connections into a document

      • Add a URL from a document as a bookmark in Connections

      • Search for content in Connections
    • Features added to PowerPoint:

      • Add a presentation to Files or Communities

      • Attach a presentation to an Activity or Wiki page

      • Search for content in Connections
    • Features added to Excel:

      • Add a spreadsheet to Files or Communities

      • Attach a spreadsheet to an Activity or Wiki page

      • Search for content in Connections

    The following features are available for Microsoft Outlook:

    • Add an email to Files or Communities

    • Attach an email to an activity or wiki page

    • Search for content in Connections
    • View social activities for email recipients and people in your network

    • Invite people to your Connections network
    • View Connections business card for email senders and recipients in Outlook 2010


    Limitations

    Some features are not available when you are connecting to an IBM SmartCloud server.

    For example:

    • Type-ahead is not available to assist you in finding a group name.

    • Type-ahead is not available to assist you in entering the names of external users in the Add to File dialog and the Share dialog.

    • If you are uploading a file or email to Activities, the option to create a new activity is not available.


    Connecting to an Connections site

    You must provide information about Connections servers or IBM SmartCloud server before you can share files and information between Microsoft Windows and Connections or IBM SmartCloud.

    After you connect to an Connections or IBM SmartCloud site, you can interact with that site from Microsoft Office, Microsoft Outlook, and Windows Explorer.

    1. Do one of the following:

        1. Open a document in a Microsoft Office application or Microsoft Outlook.

        2. Click the Connections tab.

        3. Click Connect to a site.
        1. Open Microsoft Windows Explorer.

        2. Right-click Connections in the navigation pane.

        3. Select Connect to a site.

    2. In the Site URL field type the URL you use to connect to Connections or IBM SmartCloud.

      For example, https://connections.server.com or https://connections.server.com:port.

    3. In the Display name field, type the name to display for this site in Microsoft Windows applications.

    4. Enter the user name and password you use to log in to that Connections site. Select Remember this password if you do not want to enter it each time you log in or restart your operating system.

    5. Select an authentication type if there is a reason to change it from the default. By default, the plug-in authenticates with the Connections server using basic authentication. If you are connecting to an IBM SmartCloud site, choose IBM SmartCloud Authentication as the authentication type. If your enterprise uses a different authentication type, you might be instructed to edit the authentication setting.


    Use the Connections plug-in for Microsoft Office

    Use this plug-in to share files and information between Connections and Microsoft Word, Excel, and PowerPoint.

    The Connections Desktop Plug-ins for Microsoft Windows provides the following features for Microsoft Office (Word, Excel, PowerPoint):

    • Features added to Word:

      • Add a document to Connections Files or Communities

      • Attach a document to an Activity or Wiki page
      • Publish a document to a Blog entry

      • Add someone's profile information from Connections into a document

      • Add a bookmark from Connections into a document

      • Add a URL from a document as a bookmark in Connections

      • Search for content in Connections
    • Features added to PowerPoint:

      • Add a presentation to Connections Files or Communities

      • Attach a presentation to an Activity or Wiki page

      • Search for content in Connections
    • Features added to Excel:

      • Add a spreadsheet to Connections Files or Communities

      • Attach a spreadsheet to an Activity or Wiki page

      • Search for content in Connections


    Add documents to Files

    Add Word, Excel, and PowerPoint documents to the Files application.

    This topic provides one way to add Microsoft Office documents to the Files application. You can also add documents from the File tab in Office applications by clicking Save & Send and then Send to Connections.

    1. Open the document.

    2. Click the Connections tab.

    3. Click Files.

    4. If you connect to more than one site, select a site to upload the document to.

    5. Type tags which you can use to find the document in Connections.

    6. Choose to share the file with no one, or with specific people or communities, or with everyone.

    7. Choose whether to allow other people who can see the document to share it with other people. This option is not available if you choose to share with everyone.

    8. (IBM SmartCloud only) Choose whether the file can be shared with people outside of your organization. You are not able to disable this option if you are sharing with an external community.

    9. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    10. Click Upload.


    Add documents to Communities

    Add Word, Excel, and PowerPoint documents to Connections communities.

    This topic provides one way to add Microsoft Office documents to a community. In Microsoft Office 2010, you can also add documents from the File tab in Office applications by clicking Save & Send and then Send to Connections.

    1. Open the document.

    2. Click the Connections tab.

    3. Click Communities.

    4. If you connect to more than one site, select a site to upload the document to.

    5. Type the community name or select one using the dropdown.

    6. Choose whether to upload the document directly to the community, or upload it to My Files in the Files application and share it with the community from there.

    7. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    8. (IBM SmartCloud only) Choose whether people outside of your organization can see this file.

    9. Click OK.


    Add documents to Activities

    Add Word, Excel, and PowerPoint documents to an activity.

    This topic provides one way to add Microsoft Office documents to an activity. You can also add documents from the File tab in Office applications by clicking Save & Send and then Send to Connections.

    1. Open the document.

    2. Click the Connections tab.

    3. Click Activities.

    4. If you connect to more than one site, select a site to upload the document to.

    5. Do one of the following:

      • Click Browse to find an existing activity, then do one of the following:

        1. Select My activities and choose from the list of activities you own or are a member of. The list includes community activities.

        2. Select Search, then type characters to use to search for activities. The results include community activities.

        3. Click OK.

      • Click Create new activity, then:

        1. Type a name, tags, and a goal for the activity.

        2. To confirm changes made ly add a due date.

        3. Add people or communities as members with specified access.

        4. Click Create.

      Create a new activity is not available if you are connecting to a SmartCloud site.

    6. If you are adding the document as a To Do item, by default, the task is assigned to Anyone (shared), meaning any member of the activity can perform the task, and then check it off after it is completed. To assign the to-do item to a specific member, click Choose a person, and then perform one of the following actions:

      • Standard activity:

        • To assign the to-do entry to a specific person, select Individual activity members, and then select the persons name from the list. To find people, scroll through the alphabetic list of names or type a person's name into the Type to filter this list field.

        • If the activity is shared with a community, then you can assign the to-do item to a community member by selecting Community: community_name where community_name is the name of the community, and then selecting the persons name from the list.

        • If a person is a member of a group that belongs to the activity, then you must add the person as an individual activity member before you can add them.
      • Community activity to which all community members were added:

        • Select the persons name from the list. To find people, scroll through the list of names or type a person's name into the Type to filter this list field.
      • Community activity to which only a subset of community members were added:

        • Select Individual activity members, and then select the persons name from the list. To find people, scroll through the alphabetic list of names or type a person's name into the Type to filter this list field.
        • (IBM SmartCloud only) To assign the to-do entry to a person who is not an explicit member of the community activity, click Assign to New Member. Select a role to assign to the member that you are adding, and then begin typing the person's name or email address into the second field. As you type, a list of matching names is displayed. Click a name in the list to add that person, and then click Save. When the to-do entry is assigned to someone who is not a community member, that person is automatically added as an explicit member to the community.

        • To assign the to-do entry to a community owner, select community_name (community owners) where community_name is the name of the community, and then select the owners name from the list.
        • (IBM SmartCloud only) To assign the to-do entry to both community owners and individual members, select owner names from the community_name (community owners) list where community_name is the name of the community, and then select individual names from the Individual activity members list. Your selections are remembered as you switch between each list.

    7. Add a due date.

    8. Change the title, and add tags, a description, and new section. Type-ahead for the Tags and Section fields returns matches as you type if you want to keep tags and section names consistent.

    9. Mark the to-do item as private if you do not want other members to see it.

    10. Click Upload.


    Add documents to Wikis

    Add Word, Excel, and PowerPoint documents to a wiki. The document is added to a wiki page as an attachment.

    This topic provides one way to add Microsoft Office documents to a wiki. You can also add documents from the File tab in Office applications by clicking Save & Send and then Send to Connections.

    1. Open the document.

    2. Click the Connections tab.

    3. Click Wikis.

    4. If you connect to more than one site, select a site to upload the document to.

    5. Do one of the following:

      • Select Wikis, and then expand the wiki that you want and select a page.

      • Select Search, and type characters to use to search for a wiki.

      • Select an existing wiki page.

    6. Change the file name.

    7. Click Upload. If you selected an attachment, it is replaced by the uploaded document.


    Add Word documents to Blogs

    Add Word documents to a blog. The document is added as a new blog post.

    Word documents must use a blog template before you can upload them as a blog post. Use the blog post template when you create a document by selecting it from the list of templates.

    For example, in Microsoft Word 2010, choose File, New and then choose Blog Post from the list of templates and create a document. To convert an existing document to a blog post, create a document with the blog post template, and then copy the content into that new document.

    Follow these steps to post a Word document as a blog post in Connections.

    1. Open the document in Word.

    2. Click the Connections tab.

    3. Click Blogs.

    4. If you connect to more than one site, select a site to upload the document to.

    5. Click Browse.

    6. Select a blog and click OK.

    7. Edit the entry title and add tags.

    8. Select Post as draft to post the document as a draft only.

    9. Click Upload.

      The conversion process might remove or change some of the formatting present in the Word document.

    You can also convert an existing document to the blog template within Word. Click File > Save & Send > Publish as Blog Post. This Microsoft feature reopens the document using the Microsoft blog template.


    Add profiles to Word documents

    Add people's Connections profiles to Word documents.

    This feature is not available on IBM SmartCloud.

    1. Open the document.

    2. Click the Connections tab.

    3. Click in the document where you want to place the profile information, and then click Profile Information.

    4. If you connect to more than one site, select a site from which to insert the profile information.

    5. Do one of the following:

      • Start typing a name and then select the best match.

      • Click the arrow icon and select from people you have recently interacted with, people you are following, or people in your network.

      • Select the name of a person and click to view their business card.

    6. Click OK.


    Add bookmarks to Word documents

    Add bookmarks to Word documents.

    This feature is not available on IBM SmartCloud.

    1. Open the document.

    2. Click the Connections tab.

    3. Click in the document where you want to place the bookmark information, and then click Bookmarks.

    4. If you connect to more than one site, select a site to upload the document to.
    5. Show bookmarks from the My Bookmarks, My Watchlist, or Popular Bookmarks lists.

    6. Start typing the name of a bookmark to narrow the list.

    7. Click Insert.


    Add bookmarks from Word documents

    Add bookmarks to Connections or IBM SmartCloud from URLs in Word documents.

    1. Open the document.

    2. Click the Connections tab.

    3. If there is a URL in the document you want to create the bookmark for, highlight it. If you don’t highlight a URL, you must type it in when you create a bookmark.

    4. Click Bookmark URL in, and then select one of the following:

      Option Description
      Bookmarks To add a bookmark in Bookmarks, select an Connections site, then fill out the fields for the bookmark. Select Make Bookmark Public to create a bookmark that everyone can access. Leave it cleared to create a bookmark that only you can access.

      This feature is not available if you are connecting to a SmartCloud site.

      A Community To add a bookmark to a community, select an Connections site. Then, start typing a community name and select or search on it. Or use the arrow icon to select from lists. Fill out the fields for the bookmark. Select Add to important bookmarks to add the bookmark to the important bookmarks list in the community.
      An Activity

      Do one of the following:

      • Click Browse to find an existing activity. Then, either select My activities and choose from the list of activities you own or are a member of. The list includes community activities. Or select Search, then type characters to use to search for activities. The results include community activities. Then, click OK.

      • Click Create new activity, then:

        1. Type a name, tags, and a goal for the activity.

        2. To confirm changes made ly add a due date.

        3. Add people or communities as members with specified access.

        4. Click Create.
      • Create a new activity is not available if you are connecting to a SmartCloud site.


    Searching from Office for Connections content

    Search for Connections content without leaving your Microsoft Office applications.

    Find content in Connections using the Search feature.

    1. Enter a search term in the search bar on the Connections ribbon. The default is to search all of Connections and return matching results. If you connect to more than one site, you can select a different server to search.

    2. To refine a search, click Advanced Search. The Advanced Search opens in a browser window. Use the Advanced Search filters to refine your search.


    Use the Connections plug-in for Microsoft Outlook

    Use this plug-in to share files and information between Connections or IBM SmartCloud and Microsoft Outlook.

    The following features are available for Microsoft Outlook:

    • Add an email to Files or Communities

    • Attach an email to an activity or wiki page

    • Search for content in Connections
    • View social activities for email recipients and people in your network

    • Invite people to your Connections network
    • View Connections business card for email senders and recipients in Outlook 2010


    Viewing user business cards

    From Microsoft Outlook email, you can view a business card from someone in your network or organization. Business cards list people's contact information as well as links to their social content.

    This feature is not available on IBM SmartCloud.

    1. Open an Outlook message.

    2. Right-click an email address and select Connections > View Business Card. If you are connected to multiple sites, select the site to retrieve the card from. You can also right-click an unopened email and click View Business Card.


    Add Outlook emails to Files

    Add Microsoft Outlook emails to the Files application.

    1. Open Microsoft Outlook.

    2. Select the email from a view, such as Inbox.

    3. Click the Connections tab.

    4. Click Files.

    5. If you connect to more than one site, select a site to upload the document to.

    6. Type tags which you can use to find the document in Connections.

    7. Choose to share the file with no one, or with specific people or communities, or with everyone.

    8. Choose whether to allow other people who can see the document to share it with other people.

    9. (IBM SmartCloud only) Choose whether the file can be shared with people outside of your organization.

    10. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    11. Click Upload. This adds the complete email file, including any attachments, as one document.


    Add Outlook emails to Communities

    Add Microsoft Outlook emails to a community.

    1. Open Microsoft Outlook.

    2. Select the email from a view, such as Inbox.

    3. Click the Connections tab.

    4. Click Communities.

    5. If you connect to more than one site, select a site to upload the document to.

    6. Type the community name or select one using the dropdown.

    7. Choose whether to upload the document directly to the community, or upload it to My Files in the Files application and share it with the community from there.

    8. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    9. Click OK. This adds the complete email file, including any attachments, as one document.


    Add Outlook emails to Activities

    Add Microsoft Outlook emails to an activity.

    1. Open Microsoft Outlook.

    2. Select the email from a view, such as Inbox.

    3. Click the Connections tab.

    4. Click Activities.

    5. If you connect to more than one site, select a site to upload the document to.

    6. Do one of the following:

      • Click Browse to find an existing activity, then do one of the following:

        1. Select My activities and choose from the list of activities you own or are a member of. The list includes community activities.

        2. Select Search, then type characters to use to search for activities. The results include community activities.

        3. Click OK.

      • Click Create new activity, then:

        1. Type a name, tags and a goal for the activity.

        2. To confirm changes made ly add a due date.

        3. Add people or communities as members with specified access.

        4. Click Create.

      Create a new activity is not available if you are connecting to a SmartCloud site.

    7. If you are adding the email as a To Do item, by default, the task is assigned to Anyone (shared), meaning any member of the activity can perform the task, and then check it off after it is completed. To assign the to-do item to a specific member, click Choose a person, and then perform one of the following actions:

      • Standard activity:

        • To assign the to-do entry to a specific person, select Individual activity members, and then select the persons name from the list. To find people, scroll through the list of names or type a person's name into the Type to filter this list field.

        • If the activity is shared with a community, then you can assign the to-do item to a community member by selecting Community: community_name where community_name is the name of the community, and then selecting the persons name from the list.

        • If a person is a member of a group that belongs to the activity, then you must add the person as an individual activity member before you can add them.
      • Community activity to which all community members were added:

        • Select the persons name from the list. To find people, scroll through the list of names or type a person's name into the Type to filter this list field.

          If the activity has more than 500 members, you can click Next to see more names.

          The filter searches the names on the current page only. If there are multiple pages, click Next until you get to a page with names in the same alphabetic range as the name you are looking for, and then type the name into the filter box.

      • Community activity to which only a subset of community members were added:

        • Select Individual activity members, and then select the persons name from the list. To find people, scroll through the list of names or type a person's name into the Type to filter this list field.

          If the activity has more than 500 members, you can click Next to see additional names.

          The filter searches the names on the current page only. If there are multiple pages, click Next until you get to a page with names in the same alphabetic range as the name you are looking for, and then type the name into the filter box.

        • (IBM SmartCloud only) To assign the to-do entry to a person who is not an explicit member of the community activity, click Assign to New Member. Select a role to assign to the member that you are adding, and then begin typing the person's name or email address into the second field. As you type, a list of matching names is displayed. Click a name in the list to add that person, and then click Save. When the to-do entry is assigned to someone who is not a community member, that person is automatically added as an explicit member to the community.

        • To assign the to-do entry to a community owner, select community_name (community owners) where community_name is the name of the community, and then select the owners name from the list.
        • (IBM SmartCloud only) To assign the to-do entry to both community owners and individual members, select owner names from the community_name (community owners) list where community_name is the name of the community, and then select individual names from the Individual activity members list. Your selections are remembered as you switch between each list.

    8. Add a due date.

    9. Change the title, and add tags, a description, and new section.

    10. Mark the to-do item as private if you do not want other members to see it.

    11. Click Upload. This adds the complete email file, including any attachments, as one document.


    Add Outlook emails to Wikis

    Add Microsoft Outlook emails to a wiki.

    1. Open Microsoft Outlook.

    2. Select the email from a view, such as Inbox.

    3. Click the Connections tab.

    4. Click Wikis.

    5. If you connect to more than one site, select a site to upload the document to.

    6. Do one of the following:

      • Select My wikis, then expand the wiki that you want and select a page.

      • Select Search, and type characters to use to search for a wiki. In the results, expand the wiki that you want and select a page.

    7. Change the file name.

    8. Click Upload. This adds the complete email file, including any attachments, as one document.


    Add users from your social network to Outlook emails

    When you compose a Microsoft Outlook message, you can search Profiles for a name and insert it into one of the address fields in your message.

    This feature is not available for IBM SmartCloud users.

    1. Create a message.

    2. Click Connections > Insert Profile Email.

    3. If you connect to more than one Connections site, select a site to look for the person.

    4. Enter a name or email and then select the user. Or click the arrow icon and select from people you have recently interacted with, people you are following, or people in your network.

    5. Select an action:

      • Add to TO

      • Add to CC

      • Add to BCC

      • Add to Subject
      • Message (to add the address to the body of the message)
      You can also click to view their business card.

    6. Check the Add to Outlook Contacts option if you want to add this user to Outlook contacts.


    Results

    The email address is inserted in the field that you selected.


    Searching from Outlook for social content

    Search for Connections or IBM SmartCloud content without leaving your Microsoft Outlook client.

    Find content in Connections or IBM SmartCloud using the Search feature.

    1. Enter a search term in the search bar on the Connections ribbon. The default is to search all of Connections and return matching results. If you connect to more than one site, you can select a different server to search.

    2. To refine a search, click Advanced Search. The Advanced Search opens in a browser window. Use the Advanced Search filters to refine your search.


    Use Connections with the Outlook Social Connector

    Use the Microsoft Outlook Social Connector to stay in contact with your Connections network.

    The Outlook Social Connector features are not supported by IBM SmartCloud. You must be connected to an Connections site to use these features.


    Connect with your network

    Use the Outlook Social Connector with Connections, you can do the following:

    • Add people to your network
    • View your network from your Outlook client
    • View all interaction you share with a colleague in your network, including email, attachments, meetings, and feeds

    This plug-in requires Outlook Social Connector version 1.1 or higher. If you have not already done so, you must upgrade the default version of OSC for your Microsoft Office application, or install it for the first time.

    For information about Outlook Social Connector and instructions on how to download the correct software, see this OSC article on the Microsoft website.


    The Connections OSC provider

    One of the different features of the Connections OSC provider and other OSC providers is that it supports multiple servers where most providers connect to only one server. You can connect to up to four servers, which can be helpful if your organization maintains Connections servers for internal and external use.

    Once the Connections Desktop Plug-ins are configured to connect to at least one Connections server, you can enable those servers in Account Settings for Microsoft Outlook so that you can integrate contacts from those servers in your social networks available from your Outlook client.


    Enable the OSC provider

    After you configure Microsoft Office to connect to an Connections server, you can then enable the Outlook Social Connector to bring network contacts into Microsoft Outlook.

    After the Connections Desktop plug-ins are configured to connect to at least one Connections server, start the Preferences for the Connections plug-ins to ensure that server are available for the OSC configuration in Microsoft Outlook.

    1. Click Preferences on the Connections ribbon and click Outlook Social Connector. This section lists the servers that are configured for the Connections Desktop plug-ins.

    2. Check up to four the servers that you would like to have available for the OSC.

    3. Open Microsoft Outlook and view Account Settings. One way to do that is to click the View tab and click People Pane > Account Settings in Microsoft Outlook 2010.

    4. The Account Setting dialog contains all of the OSC providers that are installed for the system. The OSC Providers that are already checked are previously configured. Check up to four providers to configure and click Connect to begin receiving the social information for those networks.

      If Microsoft Outlook was already running when you selected servers for OSC from the Preferences panel, restart Microsoft Outlook to connect to the changes.


    Add Connections to Outlook as a social network

    Add Connections to Microsoft Outlook as a social network.

    To perform these steps, you must be connected to an Connections site.

    For more information, see Connecting to an Connections site.

    1. Open Outlook.

    2. Choose one of the following:

      • Office 2007: Tools > Social Network Account Setting .
      • Office 2010: View > People Pane > Account Settings.

    3. Select an Connections site.

    4. Click Connect.

    5. Click Finish.


    Results

    You can now view information about contacts in your network in the People Pane. You can also open the Connections folder in your Contacts list to view and manage your network.


    Inviting people to join your Connections network from Outlook

    Invite people to your Connections network from your Outlook client.

    As you are working in Outlook, you can interact with people you would like to include in your Connections network.

    1. Invite people to your network in the following ways:

      Option Description
      From the business card If you view the business card of a contact who is a colleague in your Connections deployment, click Invite to Network to send them a request to join your network.
      From an Outlook view Right-click the sender's name and choose Connections > Invite to My Network, and then select a site. A request to join your network is sent to the person.
      From a profile photo, or from a name in To, Cc, or Bcc fields of a mail message Right-click the photo or name and choose Connections > Invite to My Network, and then select a site. A request to join your network is sent to the person.

      If a person is not a Connections member, a notification informs you that you cannot add or remove them from your network.

    2. Add an optional message with your invitation.

    3. Click Also Follow (Receive Updates) if you want updates from this person to display in your update list on your Connections home page. If the invitation is in pending status, "Network invitation sent. Click to cancel invitation" displays.

    4. If the person is already in your Connections network, Remove from My Network displays instead of an invitation. Click to remove the person from your network.


    Viewing your Connections network contacts in Outlook

    In Microsoft Outlook, view your entire Connections network, or see your interaction with one colleague.

    From your Microsoft Outlook client, you can view your entire network or select a contact and view interaction with a colleague.

    1. Select Contacts to change to that view.

    2. Click an Connections site in the My Contacts list to view your Connections network.

    3. Select a colleague to view interaction with that person. The Person Pane displays all of the activities you share with this colleague.

    4. The All Items view displays email, attachments, and meetings you have in common, as well as recent status updates for this person.


    Use the plug-in for Microsoft Windows Explorer

    Use this plug-in to upload and work with files in Connections from Microsoft Windows Explorer.

    Features added to Windows Explorer:

    • Upload local files to the Files application from Windows Explorer or from your desktop.
    • Share uploaded files with people, communities, or folders in your network or organization.
    • Work on files locally and publish them to the Files application.
    • View people's contact details and get in touch with them. (This feature is not available in IBM SmartCloud.)
    • Pin, follow, or like files and folders that are shared with you.
    • View or contribute comments for a file that is shared with you.

    • Add files directly to Communities, specific Wiki pages, and Activities.
    • Lock a file when you are editing it to prevent file conflicts.
    • View and restore files from the trash.
    • Share folders with Communities.

    To perform any of these tasks, you must be connected to an Connections or IBM SmartCloud site.

    For more information, see Connecting to an Connections site.


    Manage Connections files from Windows Explorer

    Manage your Connections files from Windows Explorer.

    After you install Connections Desktop Plug-ins for Microsoft Windows you see an Connections folder in the navigation pane of Windows Explorer. From this folder, you can view and access all of your Connections files from your desktop. For any file, you can:

    • Double-click a file to open a local copy of the file.

    • Right-click a file and select Open in browser to start Connections in a browser window so that you can access the file details and download link.

    To work with plug-in features, you must be connected to an Connections or IBM SmartCloud site.

    For more information, see Connecting to an Connections site. For each site you connect you, you will get a corresponding folder with the following contents.


    Table 18. Folders for managing Connections files

    Folder Description
    My Files A list of all the files you published to Files.
    Pinned Files Files that you pinned for easy retrieval.
    Shared with Me Files that were shared with you.
    Shared by Me Files that you shared with people or communities.
    My Folders Folders that you created. You can drag files into folders. To remove a file from a folder, right-click the file name and click Remove from folder.
    Pinned Folders Folders that you pinned for easy retrieval.
    Folders Shared with Me Folders that other shared with you.
    Communities Communities that you belong to and public communities. This folder does not automatically display all of the communities you can access. Add the communities to access from your desktop. Click the icon for a community to view associated files. To add a new community, right-click Community in the navigation pane, choose Add, then type the name of a community to add.
    People This folder lists files that were shared with you, organized by the person who shared them. The folder does not automatically display all of the people who shared files with you. Add the people who shared files to track from the desktop. Click a profile picture to see the associated files. To add a new person to their folder, right-click People in the navigation pane, choose Add, then type the name of a person.
    Trash Move a file to the trash hides it from all folders and it no longer appears in searches. When you move a file to trash, all of the file's versions, recommendations, and comments move to trash, and the file is hidden from people with whom you have shared it. If a file is restored from the trash, it is added back to the folders it was previously in, and all data is restored. When you restore a file from trash, all versions, recommendations, and comments are restored, and people with whom you have shared the file can see it again.

    The Trash folder contains subfolders for trash from My Files, each community, and each person. Only subfolders that contain deleted files are displayed.


    Uploading files

    Add files to the Files application so that you can store them or share them with others.

    Upload files from your desktop and add them to the Files application. You can upload them to the Files application, where you can make them public, keep them private or share them with people or communities you specify. You can upload a file to a community so that all members of the community can access the file. You can also upload to an activity to make it available to activity members or to a wiki to make it available to wiki members.

    If you get an error when you upload PDF files, check with your administrator. If Connections is running in a Tivoli Access Manager or Tivoli Access Manager and SPNEGO security environment, the administrator must make sure that the parameter suppress-dynurl-parsing-of-posts is set to yes on the TAM server to allow for the proper uploading of PDF documents.


    Uploading a file to the Files application

    Add files to the Files application so that you can store them or share them with others.

    1. Right-click a file name from Windows Explorer and select Connections > Add to Files. Alternatively, you can drag a desktop file to My Files in the Connections section of your Windows Explorer navigation pane or paste a file into the same section.

    2. If you connect to more than one site, select a site to upload the document to.

    3. Add tags to help you more easily find the document.

    4. Select any of the following choices:

      Option Description
      No one (visible only to me) Make the file private. Only the owner can see and edit it.
      People or Communities

      Share the file with specific people or a community. Perform these steps:

      1. Select a Person or a Community.

        To share with a public community, you must be using Connections 3 or higher.

      2. Select the as Reader or as Editor access level:

        • Readers can read or download a file. They can add files to folders to which they have Contributor access, be notified of changes to the file, and share the file with other people.

        • Editors can read, edit, download, upload a new version, and set properties on the file. They can add files to folders to which they have Contributor access, be notified of changes to the file, and share it with other people.

      3. Perform one of the following tasks:

        • To share with people, click in the field to display the names of people you recently shared files with. If the person you are looking for is displayed, select them. If they are not displayed, type a name or email address, and then select the person.

          If you are connecting to IBM SmartCloud, type-ahead is not available when you are searching for someone external to your organization.

        • To share with a community, start typing the name of the community, and then select the community when it displays.

          When you share a file with a public community the file becomes public.

      When you share a file with people or a community, the option Allow others to share this file is enabled by default. You can disable this if you do not want others to share the file. This option is not available if you make a file public.

      Public (visible to everyone)

      If you are connecting to a SmartCloud server this option is Everyone in organization.

      Make the file visible to everyone, even people who are not logged in.

      An administrator can configure the system so that everyone must log in, or only a certain group of people can log in. In this case public files are only available to users who are able to log in.

    5. (IBM SmartCloud only) Choose whether the file can be shared with people outside of your organization.

    6. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    7. Click Upload.


    Uploading a file to a community

    Add a file to a community to share it with community members.

    1. Right-click a file name from Windows Explorer and select Connections > Add to Communities. Alternatively, you can drag a file from Windows Explorer or from the desktop and drop it into the File folder for the target community, or paste a file to the same destination.

      Dragging a file or pasting a file into a community directly uploads the file into the community instead of sharing it with the community.

    2. If you connect to more than one site, select the site to which you want to upload the file.

    3. Type the name of the community, and then select it. Or click the arrow icon next to the Community field and select a community that you are a member of.

    4. Choose one of the following:

      • Upload to community to upload to a selected community. Choose this option if you intend to share a file only with members of the community.
      • Upload to My Files and share with community. Choose this option if you want to share with colleagues who are not members of the community as well as sharing with community members.

    5. (IBM SmartCloud only) If you choose Upload to My Files and share with community, you are offered an option to share the file with people outside of the organization.

    6. (IBM SmartCloud only) Choose to encrypt the contents of the file.

    7. Click OK to upload the file. When you open the activity in Connections, your file is in the community.

      A file that is shared with or uploaded to a community inherits the visibility of that community.

      For example, if the community is public all files within the community are also automatically public.


    Results

    To add a file to a community that already displays in your Connections navigation pane, expand the community list so you can see the Files folder for the target community and drag in a file to upload it to the community.


    Uploading a file to an activity

    Add a file to an activity to share it with other activity users.

    1. Right-click a file name from Windows Explorer and select Connections > Add to Activities.

    2. If you connect to more than one site, select a site to upload the file to.

    3. Do one of the following:

      • Click Browse to find an existing activity, then do one of the following:

        1. Select My activities and choose from the list of activities you own or are a member of. The list includes community activities.

        2. Select Search, then type characters to use to search for activities. The results include community activities.

        3. Click OK.

      • Click Create new activity, then:

        1. Type a name, tags, and a goal for the activity.

        2. To confirm changes made ly add a due date.

        3. Add people or communities as members with specified access.

        4. Click Create.

      Create a new activity is not available if you are connecting to a SmartCloud site.

    4. If you are adding the file as a To Do item, by default, the task is assigned to Anyone (shared), meaning any member of the activity can perform the task, and then check it off after it is completed. To assign the to-do item to a specific member perform one of the following actions:

      • Standard activity:

        • To assign the to-do entry to a specific person, select Individual activity members, and then select the person's name from the list. To find people, scroll through the alphabetic list of names or type a person's name into the Type to filter this list field.

        • If the activity is shared with a community, then you can assign the to-do item to a community member by selecting Community: community_name where community_name is the name of the community, and then selecting the persons name from the list.

        • If a person is a member of a group that belongs to the activity, then you must add the person as an individual activity member before you can add them.
      • Community activity to which all community members were added:

        • Select the persons name from the list. To find people, scroll through the alphabetic list of names or type a person's name into the Type to filter this list field.

          If the activity has more than 500 members, you can click Next to see additional names.

          The filter searches the names on the current page only. If there are multiple pages, click Next until you get to a page with names in the same alphabetic range as the name you are looking for, and then type the name into the filter box.

      • Community activity to which only a subset of community members were added:

        • Select Individual activity members, and then select the persons name from the list. To find people, scroll through the alphabetic list of names or type a person's name into the Type to filter this list field.

          If the activity has more than 500 members, you can click Next to see additional names.

          The filter searches the names on the current page only. If there are multiple pages, click Next until you get to a page with names in the same alphabetic range as the name you are looking for, and then type the name into the filter box.

        • To assign the to-do entry to a community owner, select community_name (community owners) where community_name is the name of the community, and then select the owners name from the list.
        • (IBM SmartCloud only) To assign the to-do entry to both community owners and individual members, select owner names from the community_name (community owners) list where community_name is the name of the community, and then select individual names from the Individual activity members list. Your selections is remembered as you switch between each list.

    5. Add a due date.

    6. Change the title, and add tags, a description, and new section. Type-ahead for the Tags and Section fields returns matches as you type if you want to keep tags and section names consistent.

    7. Mark the to-do item as private if you do not want other members to see it.

    8. Click Upload.


    Uploading a file to a wiki

    Add a file to a wiki to share it with other wiki users.

    1. Right-click a file name from Windows Explorer or the desktop and select Connections > Add to Wikis.

    2. If you connect to more than one site, select a site to upload the document to.

    3. Do one of the following:

      • Select My wikis, and then expand the wiki that you want and select a page.

      • Select Search, and type characters to use to search for a wiki.

      • Select an existing wiki page attachment.

    4. Change the file name.

    5. Click Upload. If you selected an attachment, it is replaced by the uploaded document.


    Sharing a file with additional people or communities

    If you upload a file to the Files application, you can share it with other people and communities from Explorer.

    When you share files, roles determine how others can interact with the file. Owners can share their files with people or communities. People can have Reader or Editor access to the file. Communities have Reader access. If you are connecting to an Connections 4.0 server or higher, communities can also have Editor access.

    • Readers can read, comment on, download, and recommend a file, be notified of changes to the file, and share the file. They can add a file to one of their folders, or to a folder to which they have Contributor access.

    • Editors can read, edit, comment on, download, recommend, upload a new version of, and set properties on the file. They can be notified of changes to the file, and share it. Editors can also add a file to a folder of theirs, or to a folder to which they have Contributor access.

    1. Right-click the file in the Connections section of Explorer and select Share.

    2. To share the file with everyone, select Public.

      In SmartCloud this option is Everyone in organization.

    3. To share with people or communities, select People or Communities and specify the people or communities you want to share the file with. Type-ahead helps you locate the people or communities you want to share with.

      If you are connecting to IBM SmartCloud, type-ahead is not available when you are searching for someone external to your organization.

    4. Add an optional message to describe the file. This message is shared with the people or communities you specified.

    5. Click Share to share the file. An email notification is sent to the people listed in the dialog.


    Viewing file details in a browser

    If you upload a file to the Files application, you can start Connections in a browser and view your file.

    1. Navigate to a file you uploaded to the Files application, for example, a file in the My Files node of Connections.
    2. Right click the file and select Open in browser.

    3. If prompted to log in, enter your Connections user name and password.
    4. View your file in the My Files application.

    From the Files application, you can perform all available actions on the file.

    For example, you can download the file for viewing or editing, upload a new version, or share the file with others. Refer to the Files application help for descriptions of all available actions.


    Publishing local drafts

    Publish updates to your files from Explorer or from the Drafts monitor.

    If you change a local version of a file that you posted to Connections, you can publish your changes as a new version of the file. Publish a new version from Explorer, or use the Files monitor to view all drafts and publish changes.


    Publishing drafts from the Drafts monitor

    Publish updates to your files from the Drafts monitor.

    When you download a file from Connections and edit the file, a notification message in the system tray informs you that a new draft was created. You can view all of your files in the draft state from the Drafts monitor. From the monitor, you can open a draft, publish your changes to Connections, or delete a draft.

    1. Click the Connections icon in the system tray to open the Drafts monitor. The Drafts monitor lists all of the files you have with unpublished changes.
    2. Right click a draft and select one of the following to work with a draft:

      • Open draft to open a local copy of the file for editing.
      • Publish to publish your changes as a new version of the file. You are prompted to add an optional change summary. People with whom you shared the file are notified that the file was changed. The notification is enabled by default, but you can disable it.

      • Delete draft to permanently remove the local draft. Deleting a draft does not affect the version of the file that is published to Connections.


    Publishing drafts from Explorer

    If you revise a local copy of a file, you can publish the changes or upload a new file.

    If you change the local copy of a file that you downloaded from Connections, you can publish the changes so they appear as a new version of the file or you can upload a new copy of the file.

    • If you have editor access, you can publish your local draft as a new version. Right click the file and choose Publish local draft. You are prompted to add an optional message and choose whether to notify others by email.

    • To discard the changes that you made to this file, right-click the file and choose Delete local draft. You are notified that the changes you made to the draft will be discarded.

    • To upload a new version, right-click a file and choose Upload New Version. Browse for a file to upload as a new version.


    Connecting to others using the business card

    Use the business card to view peoples' contact details and get in touch with them.

    The business card provides a useful snapshot of a user's Connections profile information.

    This feature is not supported by IBM SmartCloud.

    The business card provides links to the Connections applications that are used by the person so that you can perform a number of actions.

    For example, if your administrator configured email addresses to display, you can send an email.

    1. To access a person's business card, right-click their name in any Connections dialog, or for example the People section, and select View business card.

    2. Use the business card to perform the following tasks:

      • Click the name of a person to open their Connections profile.

      • Add the person as a colleague by selecting the Invite to My Network icon, typing an invitation message, and clicking Send invitation.
      • Follow a person by selecting the Follow icon. You will receive notifications about this person’s activities.
      • Send the person an email by clicking Send E-mail icon.

        This option is not available if your administrator configured Connections to prevent email addresses from being displayed.

      • Download a person’s vCard by choosing More Actions > Download vCard and specify a path where you want to save the vCard.

      • Access the applications that are associated with a person by clicking More Actions and selecting an application.

        For example, you can view a person’s full profile by clicking Profiles.


    Following files and folders

    You can receive notification when changes are made to a file or folder.

    When you follow a file or folder, notifications are sent to your home page when the file or folder is updated.

    To track file and folder changes:

    1. Option Description
      To be notified when a file is added to a folder Right-click a folder and select Properties. Check Follow this folder.

      By default this is selected for folders that you own and public folders.

      To be notified when a file is edited or commented on Right-click a file and select Properties. Check Follow this file.

      By default this is selected for files that you own and public files.

    2. To stop following:

      • Right-click a folder and select Properties. Clear Follow this folder.
      • Right-click a file and select Properties. Clear Follow this file.


    Viewing properties for a file or folder

    You can pin, follow, or recommend a file or folder from the properties panel.

    When you view the properties for a file or folder, you can view information about the file version and sharing. You can also pin, follow, or recommend the file or folder.

    Right-click a file and choose Properties. The following options are available from the Properties panel:

    1. Option Description
      File name, description, and tags If you have permission, you can edit these fields to rename the file, add or edit a description, or add or edit tags.
      Sharing details Click Sharing details to see who the file is shared with.

      If you own the file or have sharing rights, you can add people or communities to share with.

      Likes Click Like this file to like a file. You can also view the number of likes.
      Pin Click Pin this file to add a file to Pinned Files in the navigation pane.
      Follow Click Follow this file if you want notifications about changes to a file or folder added to your Notifications list in the Connections browser application.
      Comments Click the Details link to view information about comments.

      Depending on your access, you can add a comment, follow, or stop following a comment, or open a comment in a browser.

      Versions Click the Details link to view information about versions.

      From the versions panel, you can double-click a version to open it. Depending on your access you can delete a version or restore a previous version.

      Downloads Click the Details link to view information about downloads.

      Right-click a person’s name to see available actions such as viewing a business card or sending a link to the file or folder.

      Encrypted (SmartCloud only) Specifies whether file is encrypted or not.
      Lock Lock a file to prevent others from editing it. Unlock the file to make it available for editing.

    Right-click a folder and choose Properties. The following options are available from the Properties panel:

    1. Option Description
      Folder name and description If you have permission, you can rename the folder or edit the description.
      Sharing details Click Sharing details to see who the folder is shared with.

      If you own the folder or have sharing rights, you can add people or communities to share with.

      Pin Click Pin this folder to add a folder to the Pinned Folders folder in the navigation pane.
      Follow Click Follow this folder if you want notifications about changes to a folder added to your Notifications list in the Connections browser application.


    Searching Connections from Microsoft Office and Outlook

    Search for Connections content from Microsoft Word, Excel, PowerPoint, and Outlook.

    To perform these steps, you must be connected to an Connections site.

    For more information, see Connecting to an Connections site.

    1. Open a document or email.

    2. Click the Connections tab.

    3. In the Search section, select an Connections site to search if you connect to more than one.

    4. Type characters in the search field and click the magnifying glass icon to search those characters.

    5. Click Open Advanced Search to open Connections and search from there.


    Set preferences for Connections plug-ins for Microsoft Windows

    Set preferences for the Connections plug-ins for Microsoft Office, Microsoft Outlook, and Microsoft Windows Explorer.

    Open a document in any Microsoft Office application or from Microsoft Outlook, click the Connections tab, and then click Preferences. Or from Microsoft Windows Explorer, right-click Connections, and then click Preferences.


    Table 19. General preferences

    Preference Description
    Email settings Select Use Mail application and specify an email provider, such as IBM Notes. This is the email that the plug-in uses for notifications. Select Use mailto: protocol to use the default email.
    Show Desktop icon Places an icon for the plug-in on your desktop.
    Show Windows Explorer Context Menu Extension This controls whether the Connections context menu displays when you right-click a desktop file.


    Table 20. Connections site preferences

    Preference Description
    Site URL The URL for the Connections or IBM SmartCloud server you are connecting to.
    Display name The name of the server.
    User name The user name that you use to log in to Connections or IBM SmartCloud.
    Password The password that you use to log in to Connections or IBM SmartCloud.
    Authentication type By default, the plug-in authenticates with the Connections server using basic authentication. If you are connecting to an IBM SmartCloud server, select IBM SmartCloud Authentication. If your administrator implemented an alternate authentication mechanism in the environment in which the Connections server is running, you might be instructed to edit the authentication settings.


    Table 21. Outlook Social Connector preferences

    Preference Description
    Outlook Social Connector Provider Select up to four servers to add to the Outlook Social Connectors (OSC). Adding Connections servers to OSC makes Connections profiles available in Outlook contacts and in the People Pane. Once a server is added to OSC, it cannot be removed by clearing the server name here. If Outlook is open, restart it to see the changes.


    Table 22. Downloaded files preferences

    Preference Description
    Alert me when I save a draft When this option is enabled, a message notifies you when you save a draft.
    Enable automatic deletion of drafts When this option is enabled, unpublished drafts are deleting on the schedule you specify.
    Ignore local changes made to files with these extensions Specify extensions for types of files you do not want to save as drafts.


    Use the Connections Status Updates Plug-in for IBM Notes

    Status Updates let you keep up with your Connections network from the Notes client.

    The Status Updates application lets you:

    • Post your status so that colleagues can see what you are working on
    • View status updates for your colleagues and comment on them

    • Clear your status

    • Forward a post via email
    • View your board or someone else's board
    • Work with updates from the system tray, even when you are not working in Notes

    What’s new in this release? Using new features, you can:

    • Attach a local file to your status update so you can easily share it with colleagues

    • Search for people or communities using a new search bar with typeahead support
    • Post status updates to a community you can access
    • View all updates from your activity stream
    • Recommend posts using the Like button


    Work with Status Updates

    Keep up-to-date with what is happening in your network with the Status Updates sidebar application.


    Purpose

    Do the following to work with your status updates:


    Table 23. Working with Status Updates

    Task Steps
    Manage your status Do any of the following:

    • Enter a status message and click Post to publish it.

    • Click Reset to clear your current update.

    • Right-click an update you posted and choose Delete to remove it.
    Share a photo or a file with others To share a photo or file, enter the text for an update, then click Attach a File. Browse for a local file. The file is appended to your post so that others can view or download it.
    Interact with other people in your network Do any of the following:

    • To comment on an update, click Add comment, enter your comment and click Post Comment.

    • To view all of the status updates for one person, click the name of the person to view their board. You can also change the search scope to People and begin to type the name or email of a colleague. The type-ahead feature returns matches. Choose the matching name to view all updates from that person.

    • Click a file attachment that a colleague has posted to open the file in an appropriate application.
    Recommend posts and comments To recommend a post, open the entry or comment and click Like to recommend it. Click Undo if you no longer want to recommend it.
    Interact with communities you can access Do any of the following:

    • To post an update to a community you can access, use the search bar to find the community. You can change the scope to search all communities, public communities, or communities for which you are a member. Status updates you post to a community display in the Recent Updates view of the community.

    • Choose the I’m Following > Communities view from the application menu to view all recent updates to these communities.
    Change the view in the application window To change views, click the menu icon for the application and choose from one of these views:

    • I’m Following displays all updates for people and content you are following. You can also choose to filter what displays so you can view a more targeted list of updates.
    • Status Updates displays status updates but no other notifications from colleagues.
    • Discover displays updates and other activities from your colleagues, whether they are in your network or not.
    • Recent Communities lets you pick a community you accessed recently to view recent updates posted to that community.
    • Connections Preferences opens the preference page where you set the server URL and log-in credentials for connecting to an Connections server.
    View a colleague’s profile in Connections To view a profile in Connections, right-click an update and select Open in Browser. Connections opens in the default Web browser so you can view and interact with the profile for the person you selected.
    Forward a status update To forward a status message using Lotus Notes, right-click an entry and choose Forward this Entry. The comment is inserted into an email form.
    Work with updates from the system tray Do any of the following:

    • To update your status when you are not working in Notes, right-click the Status Updates icon in your system icon tray and select Update Status. Enter your status and click Update.

    • To view status updates when you are not working in Notes, right-click the Status Updates icon in your system icon tray and select View Status Updates. This opens your Notes client with the Status Updates application open.


    Use the Connections Files plug-in for Notes

    Use the Connections Files plug-in for IBM Notes to have easy access to your files or community files from the Notes sidebar.

    The Connections Files plug-in lets you upload and access files from the sidebar of your Notes client. After installing the sidebar application you can:

    • Upload files for your own use or to share with others.
    • Drag and drop an attached file or a file from your desktop to Files.
    • Drag and drop or copy and paste a file from Files to your desktop.
    • Send an HTML link to a file.

    • Search for people or communities.
    • Sort files for easier browsing.
    • Detach the Files window from the Notes sidebar.

    • Open Connections Files in a browser.

    What’s new in this release?

    • Lock files to prevent others form editing them.

    • Use enhanced search to search the full directory for people.


    Uploading a file in Connections

    Add files to Connections Files so that you can store them or share them with others.

    1. To browse for a file to upload, do the following:

      1. Click Upload to My Files from the panel menu or click the File Upload icon on the toolbar of the Files panel.

      2. In the File field type the file path or browse for the file.

      3. In the Name field type a file name if browsing does not add one. Or change the name of the file.

    2. To drag and drop a file to upload, do the following:

      1. Drag a file from your desktop or drag a file attachment to the Files sidebar application.
      2. Drop the file.

    3. Select any of the following choices:

      Option Description
      No one (private) Make the file private. Only the owner can see and edit it.
      People/Communities (give specific file permissions to others)

      Share the file with specific people or a community. Perform these steps:

      1. Select a Person or a Community.

        To share with a public community you must be using Connections 3.

      2. Select the as Reader or as Editor access level:

        • Readers can read or download a file. They can add files to folders to which they have Contributor access, be notified of changes to the file, and share the file with other people.

        • Editors can read, edit, download, upload a new version, and set properties on the file. They can add files to folders to which they have Contributor access, be notified of changes to the file, and share it with other people.

      3. Perform one of the following tasks:

        • To share with people, click in the field to display the names of people you have recently shared files with. If the person you are looking for is displayed, select them. If they are not displayed, type a name or email address, and then select the person.

        • To share with a community, start typing the name of the community, and then select the community when it displays.

          When you share a file with a public community the file becomes public.

      Public (visible to everyone)

      Make the file visible to everyone, even people who have not logged in.

      An administrator can configure the system so that everyone must log in, or only a certain group of people can log in. In this case public files are only available to users who are able to log in.

    4. Click OK.

    To replace a file you have uploaded with a newer version, do the following:

    1. Right click the file and select Upload New Version.
    2. Browse for a new version of the file.

    3. Add an optional change summary.

    4. Click OK to replace the existing file with a newer version.


    Sharing a file

    Share a file with others using the Connections Files plug-in for IBM Notes.

    When you share a file, you can give people Reader or Editor access. You can give communities Reader access.

    You can also share files that have been shared with you if the owner allows it, but you cannot make them public. Only owners can make a file public.

    To see who has access to your files, right-click a file and click Sharing details.

    Do any of the following to share a file:

    Option Description
    To share a file when you upload it

    1. Click Upload to My Files.

    2. Type the file path or browse for the file.

    3. Type a file name.

    4. Select No one to keep the file private, select People if you want to specify people to share with or select Public to share with everyone.

    5. Click OK.
    To share a file after you upload it

    1. Right-click a file name and select Share File.

    2. Select People if you want to specify people to share with or select Public to share with everyone.

    3. Click Share to share the file.
    The type of notification a share recipient receives depends on what you have configured for notifications in Connections.
    To email a link to a file

    1. Right-click a file name and select Copy Link.

    2. Paste the link into an email.
    3. Send the mail to one or more people.
    To copy a file so you can include it in an email

    1. Right-click a file name and select Copy.

    2. Create an email.

    3. Right-click in the body of the email message and select Paste. .

    4. Add any additional text to the mail and send it.


    Locking files in Connections

    Lock files to prevent people from editing them.

    The Owners and Editors of files can lock and unlock those files.

    For example, if you upload a file you are the owner and can lock and unlock that file. If you give a person Editor access to the file, they can also lock and unlock it. When you lock a file, people can still download and read it, but only you can upload new versions of it.

    When a file is locked it cannot be edited, but it can still be deleted.

    1. Right-click a file in the sidebar application and choose Lock File.

    2. To unlock the file, click More Actions > Unlock File


    Searching for files

    Use search criteria to find files by keyword, or associated with people or communities of interest to you. You can also sort the files to make browsing for a file easier.

    1. Do any one of the following to find files:

      Option Description
      To find files you uploaded Click My Files > My Files to browse your uploaded files.
      To find files people shared with you Click My Files > Shared With Me to view files shared by other people specifically with you. Files shared with you might also be public.
      To find files you shared with people Click My Files > Shared By Me to view files you shared with specific people. Files shared by you might also be public.
      To find files associated with a person or community

      Search for the name of the person or community to see files associated with them or click the view menu, choose Other Files, and choose the name of the person or community.

      To search for public communities you must be using Connections 3 or higher.

      To search for files

      Select one of the search scopes: People, My Communities, Communities or Files in this View Type characters into the search field. Connections returns files associated with the person or community you specify, or with those characters in the title, description, or file contents. If you do not see a match for a person, click Search directory to search the complete directory in an attempt to find the person.

      To search for public communities you must be using Connections 3 or higher.

    2. Do any of the following to sort the list of files, to make it easier to browse:

      Option Description
      To show files by name Click My Files > Sort by > Name to view an alphabetical list of files. Select this menu item again to reverse the sort order.
      To show most recent files Click My Files > Sort by > Most Recent to view a list of files with the most recently updated file first on the list. Select this menu item again to toggle the sort order so that the most recently updated file is last on the list.


    Opening Files in a new window or in a browser

    Access the full Files capabilities by opening Connections Files in a browser window or display the Files plug-in in a window that is independent from the Notes sidebar.

    The Connections Files plug-in for Notes provides a subset of the full Files capabilities. If you require features that are not available in the sidebar application, you can launch Connections Files from the sidebar application. You can also choose to display the Files plug-in in a window that is separate from the Notes client sidebar so you can resize it or move it to a different location.

    1. To open Connections Files in a browser window, click Open in Browser from the panel menu. Connections Files opens in the web browser specified in your Notes preferences. If you have set the Notes preference for Web browser to open web pages as a tab within Notes, you will not be required to log into Files. If your preferences are set to open web pages in an external browser, you may need to log into Connections.

    2. To open the Files plug-in in a new window, click Open in New Window from the panel. To return the Files plug-in to the Notes sidebar, choose Dock from the panel menu.


    Set Connections server preferences for Files

    You can provide your Connections password or specify the address of the server in the Connections preferences page.

    If you are already using the Connections Activities sidebar application, the preferences should already be set for you to access Connections Files. If you need to modify the settings, the Connections Server Settings section of the preference page contains the information required to log in to the Files panel of the sidebar. To set the server preferences, complete the following actions:

    1. From the panel menu, select Preferences.
    2. Fill in the following fields in the Connections Server Settings section:

      Field Description
      Server URL Type the Web address of the Connections activities server, beginning with either https:// or http://

      For example: https://enterprise.example.com

      If you know that the server requires a secure, encrypted connection, begin the address with https://

      Some administrators change the context roots that are used to access Connections features. If the Web address that you normally use to access the Activities feature has a value other than <server_name>/activities, specify the server URL using a syntax similar to this: http://enterprise.example.com/activities

      Your administrator might have already provided a value for this field using an administrative policy. If so, do not change the value.

      User name Type your user name for logging into the Connections server.
      User password Type the associated password.

    3. Click Apply to save your changes, and then click OK to close the Preferences window.


    Results

    The next time that you use Notes, the new settings are used to log you in to Connections automatically.


    Use the Connections Activities plug-in for IBM Notes

    Access the Connections applications from within the Notes client.

    You can access your Connections data from within the Notes client by choosing to install the Connections feature while installing the Notes client. The product documentation for the Activities sidebar is included in the Notes client help system.


    Use plug-ins from other products with Connections

    Get help using the plug-ins that bring the capabilities of other products into Connections.


    Use the Connections Connector for Lotus Quickr

    Access the Connections applications from within Lotus Quickr.

    You can create, view, and manage access to a Lotus Quickr place from within an Connections community by installing the Lotus Quickr connector. The product documentation for the connector is included in the Lotus Quickr connector help.


    Use the Connections Plug-in for Microsoft SharePoint

    Use the Connections Plug-in for Microsoft SharePoint to bring Connections features such as searching by tag, searching by profile, and viewing business cards, into the SharePoint environment.

    After an administrator installs and deploys the Connections Plug-in for Microsoft SharePoint, users will be able to:

    • Search Connections Profiles to find people in your organization. If colleagues you find with a Profiles search are in your SharePoint directory, you can add them to your SharePoint group or site.
    • View a colleagues Connections Business Card to get contact and social networking information about users in your organization. From the business card, you can create a mail message to this colleague or open their blog, bookmarks, or full profile.

      If the Connections uses hidden email, the business card does not display. Also, if you are using the SharePoint plug-in with SiteMinder single-sign-on and you see an error for loading data for the business card, check the security settings for your browser and make sure the setting to access data sources across domains is enabled.

    • Use the tag cloud to find content that is stored on Connections servers. Clicking a tag starts a search that matches against all Connections services.

      For example, clicking a new-hire tag could return a community and a blog post.

    If your administrator deployed the Connections Widget for Microsoft SharePoint, you can access SharePoint files from an Connections community.


    Use the SharePoint widget

    Access Microsoft SharePoint documents from within an Connections community. Documents you upload to the widget from SharePoint are available to all members of the community.

    Use the SharePoint widget to include SharePoint documents in your community. To access the widget, you must have the user name and password you use to access your SharePoint server. if you do not have this information, consult your SharePoint administrator.

    1. After you add the SharePoint widget to your community, log in to the SharePoint server with your Sharepoint user name and password.

    2. To add a document, click Upload a Document and specify a file to upload and a destination folder.

    3. To create a folder, click New Folder and enter a folder name and description.

    4. To open the SharePoint server click Go to SharePoint.

    5. Click the folder menu to do any of the following:

      1. Click Open to expand the folder and view subfolders and documents.

      2. Click Upload document to and browse for a document to add to the folder.

      3. Click Edit Properties to change the folder name.

      4. Click Delete to permanently remove the folder and all of its contents.

    6. Click a document name and perform any of these operations:

      1. Click Download this document to open a document for viewing or editing. The document opens in its native application.

        For example, if the document is a Microsoft Word document, it opens in Microsoft Word.

      2. Click Upload new version and browse for the file to replace the document with a newer version.

      3. To change the properties of a document, such as the name, click Edit properties. Edit the properties and save the changes.

      4. Click Delete to permanently remove the file from the SharePoint widget.

    7. To create a feed of the SharePoint documents list, click Feed for SharePoints Documents List, copy the feed data, and paste it into your feed reader.


    Use the Linked Lotus Quickr library widget

    Use the Linked Quickr Library widget to work with documents in an existing Lotus Quickr Library from an Connections community.

    Perform the following tasks to add a Linked Lotus Quickr Library widget to a community.

    1. Open the community.

    2. Click Community Actions > Customize.

    3. In the Add Content section, click Linked Quickr Library and then close the section. A Linked Quickr Library widget is added to the community.

    4. In the widget menu, select Edit.

    5. Type a title for the library as it displays in the community.

    6. Type or paste the direct URL of the library. To copy the URL, open the library in Lotus Quickr and click Show links.

    7. Click Save.

    8. Click the library title in the widget to open the library as in full application mode.

    9. For help using the library, click the Help link.


    Use the Lotus Quickr library widget

    use the Quickr Library widget to create a Lotus Quickr Library and work with it in an Connections community.

    Perform the following tasks to add a Lotus Quickr Library widget to a community.

    1. Open the community.

    2. Click Community Actions > Customize.

    3. In the Add Content section, click Quickr Library and then close the section. A Quickr Library widget is added to the community.

    4. Click the link in the widget. It is the name of the community.