KB214883: How to Display a User Who is Currently Logged into MicroStrategy on the Report Page Using the MicroStrategy Web SDK

By default, when users log into a project, the current user will be displayed in Strategy 9.4.1:

 
However, this information is not available on all pages, such as the report page:

The following technote article provides steps on how to add information on the connected user to other pages such as the report page:

 
Using the Web Customization Editor to create a plug-in:
Strategy Web SDK provides a Web Customization Editor that can be used to create a customization plug-in. The following steps guide you in creating the plug-in and deploying it.

1. Launch the Web Customization Editor.
2. Click on Strategy Web Configuration inside the Application Settings view to expand the hierarchical tree. The expanded list comprises the different settings that can be modified to perform customizations.
3. Click on Pages to expand the list of pages used in Strategy Web.
4. Double-click report (Report Execution). This opens the Basic Properties editor in the right frame.
5. Click the Template Properties tab at the bottom in the right frame to make changes to the Default page template for this page.
6. Right-click the content page section and select Edit current file.
7. On the Edit Page Section dialog, click the Yes button to edit Report_Content.jsp.
8. A tab opens with the code for Report_Content.jsp.
9. Before this line of code:
   

   
   <% // this map is used for drag and drop mapping // %>

   
    
   Add this line of code:
   JSP:
   

   
   Current user logged in: <web:connectionValue property="userName"/>

   
    ASP:
   

   
   Current user logged in: <web:connectionValue mproperty="userName" runat="server"/>

   
    
   
10. Save your changes.
11. Refresh the browser to see the applied changes.

 
The example provided in this document is provided “as-is” to the user and assumes that the user:

• Can program, compile (e.g. javac, jikes, etc.), and execute Java programs
• Can configure environment variables (e.g. JAR files, property files, etc.)
• Have all the necessary tools to create Java applications (JDK, IDE, etc.)
• Has access to the Strategy SDK documentation.
• Has read the customization warning at the bottom of this document

 
PREREQUISITES:
For the sample to work, the Strategy Web JAR files must be accessible by the Java Runtime
Environment. The Strategy Web JAR files can be found under:

• Strategy Web Universal (JSP): {web_root}/WEB-INF/lib directory.
• Strategy Web (.NET): Program Files\Common Files\Strategy directory.

 
Note:
More elaborate programs will require additional library files and are out of the scope of this document.
 
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://resource.microstrategy.com/msdz/).
 
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at http://www.microstrategy.com/Support/ContactUs.asp.
 
CUSTOMIZATION WARNING:
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.