Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Following Complete the following steps are mandatory to enable the ConnectionsExpert Profiles and Community widgets.

Table of Contents

...

Important Basic Information

To add the ConnectionsExpert widgets, you will need to perform the following steps. Click on the link for more information.

...

Check-out the LotusConnections-config.xml file and add the following lines in the 

<resources></resources>

sectionSection:

Code Block
<!-- panagenda ConnectionsExpert --> 
<widgetBundle name="com.panagenda.ce.widgets" prefix="ceWidgets"/>
<!-- panagenda ConnectionsExpert -->

...

Copy the following files into the strings directory within your customization directory (<cnxshare>/customization/strings):(CONNECTIONS_SHARED/customization/strings):

View file
namecom.panagenda.ce.widgets.properties
height250

English:German:Spanish:Dutch:
View file
namecom.panagenda.ce.widgets_en.properties
height250

View file
namecom.panagenda.ce.widgets_de.properties
height250

View file
namecom.panagenda.ce.widgets_es.properties
height250

View file
namecom.panagenda.ce.widgets_

...

nl.properties
height250

Configure the AJAX Proxy

To allow the widgets to connect to your ConnectionsExpert appliance, you need to configure the AJAX proxy by editing the proxy-config.tpl:

...

<!-- BEGIN CUSTOMIZATIONS HERE -->

sectionSection:

Code Block
<!-- panagenda ConnectionsExpert -->
      <proxy:policy url="https://<yourYOUR_CE_url>URL/*" acf="none" basic-auth-support="true">
                  <proxy:actions>
                          <proxy:method>GET</proxy:method>
                          <proxy:method>POST</proxy:method>
                  </proxy:actions>
                  <proxy:headers>
                          <proxy:header>content-type</proxy:header>
                          <proxy:header>accept-encoding</proxy:header>
                          <proxy:header>User-Agent</proxy:header>
                          <proxy:header>Accept.*</proxy:header>
                          <proxy:header>Content.*</proxy:header>
                          <proxy:header>Authorization.*</proxy:header>
                          <proxy:header>X-Method-Override</proxy:header>
                          <proxy:header>If-.*</proxy:header>
                          <proxy:header>Pragma</proxy:header>
                          <proxy:header>Cache-Control</proxy:header>
                          <proxy:header>X-Update-Nonce</proxy:header>
                  </proxy:headers>

                  <proxy:cookies>
                          <proxy:cookies>cookie>LtpaToken</proxy:cookie>
                           <proxy:cookie>LtpaToken<cookie>LtpaToken2</proxy:cookie>
                          <proxy:cookie>LtpaToken2<cookie>panagenda_gadget</proxy:cookie>
                  </proxy:cookies>
      </proxy:policy>
<!-- panagenda ConnectionsExpert -->

Change <yourYOUR_CE_url> into URL into your ConnectionsExpert FQDN or IP address.

...

Code Block
<!-- panagenda ConnectionsExpert -->
  <widgetDef
       defId="widgetCommunityUsage"
       description="widgetCommunityUsage.desc"
       bundleRefId="ceWidgets"
       modes="view fullpage"
       showInPalette="true"
       themes="wpthemeThin wpthemeNarrow wpthemeWide wpthemeBanner"
       uniqueInstance="true"
       resourceOwnerWidget="true"
       loginRequired="true"
       url="https://<yourYOUR_CE_urlURL/gadgets/communitystats.xml">
        <itemSet>
               <item name="res_id" value="{resourceId}"/>
       </itemSet>
   </widgetDef>
  <!-- panagenda ConnectionsExpert -->

Change <yourChange YOUR_CE_url> URL into your ConnectionsExpert FQDN or IP address.

...

Code Block
<!-- panagenda ConnectionsExpert -->
  <widgetDef
      defId="widgetProfilesCommunities"
      bundleRefId="ceWidgets"
      primaryWidget="false"
      modes="view"
      themes="wpthemeWide"
      loginRequired="true"
      url="https://<yourYOUR_CE_urlURL/gadgets/mycommunities.xml">
  </widgetDef>
  <!-- panagenda ConnectionsExpert -->

Change <yourChange YOUR_CE_url> URL into your ConnectionsExpert FQDN or IP address.

...

Code Block
execfile("newsAdmin.py")
NewsWidgetCatalogService.addWidget(title="CE Profile Community widget", text="CE Profile Community widget", url="https://<yourYOUR_CE_urlURL/gadgets/mycommunities.xml", categoryName=WidgetCategories.NONE, isGadget=FALSE,appContexts=[WidgetContexts.EMBEDXP], policyFlags=[GadgetPolicyFlags.TRUSTED], prereqs=["profiles"])
NewsWidgetCatalogService.addWidget(title="CE Community Usage widget", text="CE Community Usage widget", url="https://<yourYOUR_CE_urlURL/gadgets/communitystats.xml", categoryName=WidgetCategories.NONE, isGadget=FALSE,appContexts=[WidgetContexts.EMBEDXP], policyFlags=[GadgetPolicyFlags.TRUSTED], prereqs=["communities"])

Change <yourChange YOUR_CE_url> URL into your ConnectionsExpert FQDN or IP address.

...

Code Block
NewsWidgetCatalogService.enableWidget("<widgetWIDGET_id>ID")

Refresh the cache to enable the changes:

...

  • Profiles Widget Title: widgetProfilesCommunities

  • Community Widget Title: widgetCommunityUsage

  • Community Widget Description: widgetCommunityUsage.desc

You In addition to the provided languages (see Copy String Files section), you can also add other languages by creating new property files using following syntax: com.panagenda.ce.widgets_XX.properties (Example: com.panagenda.ce.widgets_deru.properties). 

Widget Layout

You can customize the look and feel of the widget by providing your our CSS customization. Therefore you need to add your customizations into ceWidgets/custom.css file and copy it into your Community customization directory (<cnxshare>CONNECTIONS_SHARED/customization/communities/ceWidgets). 

...

Code Block
<proxy:headers>
  <proxy:header><customheader>CUSTOM_header_name><HEADER</proxy:header>
</proxy:headers>
<proxy:cookies>
  <proxy:cookie><customcookie>CUSTOM_cookie_name<COOKIE</proxy:cookie>
</proxy:cookies>

...

Code Block
<itemSet>
  <item name="cookie" value="<customCOOKIE_cookie_name>NAME"/>
</itemSet>

Disable Community Overview Widget

...

You can test the AJAX proxy using the following URL: https://<connectionsYOUR_CONNECTIONS_url>URL/communities/ajaxProxy/https/<yourYOUR_CE_url>URL/gadgets/communitystats.xml

...

Check your custom.css file for issues. Also, check the widget-config.xml for issues related to itemset section. Use following URL to access your custom.css file: https://<connectionsYOUR_CONNECTIONS_url>URL/communities/ceWidgets/custom.css.

...