Enabling P2P communication between MicroStrategy portlets

To enable P2P communication, you install a plug-in—which provides a basic MicroStrategy portlet and a MicroStrategy master portlet—and make a few configuration settings. A MicroStrategy master portlet can both send and receive messages, while a basic MicroStrategy portlet can only receive messages. MicroStrategy master portlets can communicate with both MicroStrategy and non-MicroStrategy portlets.

 

MicroStrategy master portlets can initiate P2P communication from Folder browsing, History List, Search, Prompts, Report, and Document pages.

 

Once P2P has been enabled, the portal administrator configures the P2P settings for a MicroStrategy master portlet. He or she determines the default content that will be displayed in the master portlet and whether to predefine the target portlet for that master portlet or to allow users to specify the target portlet. The portal designer sets this preference by specifying whether the Send To option should be visible for the master portlet.

 

If you are using Internet Explorer 6 or 7 as your browser, there are cross-domain restrictions that do not exist for IE8 or Firefox. Additional steps are included with the steps for enabling portlet-to-portlet communication to address these restrictions.

 

To enable portlet-to-portlet communication:
 

  1. Install the portlet-to-portlet plug-in

    The portlet-to-portlet plug-in is packaged as one of two ZIP files under
    Portlets/plugins in the MicroStrategy installation folder.

 

 

 

Extract the contents to the plugins folder in the root MicroStrategy Web installation folder.

 

  1. Configure settings for basic MicroStrategy portlets

    Specify
    the MicroStrategy Web Base URL and the MicroStrategy Web Task URL. Steps for configuring these settings in each supported portal are found in the Configuring Default Settings topic of the respective portal section of Building Dashboards with MicroStrategy Portlets.

 

  1. Configure settings for MicroStrategy master portlets

    These settings are required for portlet-to-portlet communication to work.

 

 

 

You select the default MicroStrategy Web page that should be displayed when you configure or personalize the configuration settings for the MicroStrategy master portlet.

 

 

  1. If you are using Internet Explorer 6 or 7 as your browser, you must perform the following to enable portlet-to-portlet communication

    1. Use the fully-qualified name, including the domain, when you specify the URLs for the MicroStrategy portlets. When you specify the MicroStrategy Web Base URL and the MicroStrategy Web Task URL above, you must use the fully-qualified name, including the domain.
    2.  

        • For example, in a J2EE environment using Apache Tomcat, the MicroStrategy Web Base URL might be www.yourcompany.com:8080/MicroStrategy/servlet/mstrWeb. In a .NET environment, this might be www.yourcompany.com/MicroStrategy/asp/Main.aspx.
           

        • For example, in a J2EE environment using Apache Tomcat, the MicroStrategy Web Task URL might be www.yourcompany.com:8080/MicroStrategy/servlet/taskProc. In a .NET environment, this might be www.yourcompany.com/MicroStrategy/asp/taskProc.aspx.
           

    3. Add a value to the value parameter.


      Open the configuration file under plugins/portlet2portlet/WEB-INF/microstrategy.xml in the Web installation directory. Locate the jsDocumentDomain context parameter, and add as the value of the value parameter the name of the second-level domain where MicroStrategy Web is installed (for example, microstrategy.com). Save your changes.

    4.  

      <application>

        <global>

          <parameter name="jsDocumentDomain" value=""/>

        </global>

        <controllers>

          <controller name="mstrWeb">

            <parameters>

              <parameter name="externalSecurityClass" value="com.microstrategy.web.portlets.CustomLoginESM"/>

            </parameters>

          </controller>

        </controllers>

      </application>

         

      Note: The MicroStrategy Web machine and the portal server machine must be in the same second-level domain. They do not have to be on the same machine.

       

    5. Use the fully-qualified name, including the domain, to access the portal server in the browser.
       

    6. If you are using Integrated (Kerberos) authentication, add the fully-qualified URL, including the domain, of the MicroStrategy Web server and the portal server as trusted sites on the client browser
      For a fuller explanation of this requirement, refer to Enabling Integrated Authentication in the MicroStrategy System Administration Guide.

    7.  

      Once P2P communication has been enabled, it occurs as follows:

       

      • If the Send To option is visible, a user right-clicks an object in the master portlet and selects Send To. All of the MicroStrategy portlets that display information from the same project as the master portlet are listed. The user chooses the target portlet with which the master portlet will communicate.
         
      • If the Send To option is not visible, a user left-clicks an object in the master portlet. The communication is sent to the target portlet previously defined by the portal designer.