Home

 

Add third-party links via the XML configuration file


Overview

You can extend the Profiles business card by adding links to applications from another vendor.

To edit configuration files, use wsadmin.

You can specify links to services acquired from another vendor in the...

The service reference must have a person_card_service_url_pattern attribute and a person_card_service_name_js_eval attribute. Without these attributes, the service link does not display in the inline or pop-up business cards.


Extend the Profiles business card

  1. Use wsadmin to access and check out the Lotus Connections configuration files.

    1. Access the Lotus Connections configuration file:

      • Stand-alone deployment:

          execfile("connectionsConfig.py")

      • Network deployment:

          execfile("DMGR_PROFILE/config/bin_lc_admin/connectionsConfig.py")

        If prompted to specify which server to connect to, type 1.

        This information is not used by wsadmin when you are making configuration changes.

    2. Check out the Lotus Connections configuration files...

      LCConfigService.checkOutConfig("<working_directory>","cell_name") where:

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

      • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: From the file system...

            PROFILE_HOME/config/cells/

        • Network deployment: From wsadmin...

            print AdminControl.getCell()

        For example:

          LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
          LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

  2. Open the LotusConnections-config.xml file, and modify it to include the following attributes:


    Third-party service reference attributes

    Attribute Description
    person_card_service_url_pattern Represents the URL pattern that is used when users click the service link. The ampersand character (&) must be expressed using the actual character in the pattern. This attribute takes a string value.The following parameters inside the URL pattern are placeholders. When the business card is rendered at runtime, the parameters are replaced by the real values.

    • {email}. The profile user's e-mail address.
    • {userid}. The profile user's user ID.
    • {uid}. The profile user's UID.
    • {displayName}. The profile user's full name.
    • {workPhoneNumber}. The profile user's work telephone number.

    person_card_service_name_js_eval

    Represents a JavaScript statement that is used by the framework to generate the text displayed in the business card for the given service.

    This attribute takes a string value.

    You can add a resource string as the value for this attribute. The resource string must include "generalrs." before the resource bundle key. See Adding custom strings to Lotus Connections for information about how to add resource strings to the business card.

    For example:

      <sloc:serviceReference serviceName="googleService"
                             href="http://www.google.com"   
                             enabled="true"
                             ssl_href="http://www.google.com"   
                             ssl_enabled="false"
                             person_card_service_url_pattern="/search?hl=en&amp;q={email}&amp;btnG=Google+Search"
                             person_card_service_name_js_eval="'Google Me'"/>
      
      <sloc:serviceReference serviceName="quickr"
                             href="http://quickrdomino.tap.ibm.com/servlet"   
                             enabled="true"
                             ssl_href="https://quickrdomino.tap.ibm.com/servlet"   
                             ssl_enabled="true"
                             person_card_service_url_pattern="/QuickrEntry?email={email}"
                             person_card_service_name_js_eval="generalrs.label_personcard_quickrlink"/>
      
      <sloc:serviceReference serviceName="communities"
                             href="http://wd40.lotus.com/communities"   
                             enabled="true"
                             ssl_href="https://wd40.lotus.com/communities"   
                             ssl_enabled="true"
                             person_card_service_url_pattern="/service/html/allcommunities?email={email}"
                             person_card_service_name_js_eval="generalrs.label_personcard_communitieslink"/>
      
      <sloc:serviceReference serviceName="profiles"
                             href="http://wd40.lotus.com/profiles"   
                             enabled="true"
                             ssl_href="http://wd40.lotus.com/profiles"   
                             ssl_enabled="true" 
                             person_card_service_url_pattern="/html/simpleSearch.do?searchFor={email}&amp;searchBy=email"
                             person_card_service_name_js_eval="generalrs.label_personcard_profilelink"/>
      

  3. Edit the service-location.xsd file to define the service names used. For example:

      <xsd:simpleType name="serviceNames">
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="activities" />
            <xsd:enumeration value="blogs" />
            <xsd:enumeration value="communities" />
            <xsd:enumeration value="directory" />
            <xsd:enumeration value="dogear" />
            <xsd:enumeration value="personTag" />
            <xsd:enumeration value="presenceAwareness" />
            <xsd:enumeration value="profiles" />
            <xsd:enumeration value="sametimeLinks" />
            <xsd:enumeration value="homepage" />
            <xsd:enumeration value="googleService" />
           <xsd:enumeration value="quickr" />
          </xsd:..>
        </xsd:..>
      

  4. After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying common configuration property changes for information about how to save and apply your changes.

 

Related tasks

Customizing the business card
Apply common configuration property changes

+

Search Tips   |   Advanced Search