WebSphere Portal FastPack
6.1 & 6.2
Fastpack Download contains:
fastpack 22.214.171.124 (dynaTrace 6.1 + 6.2)
This fastpack was created on WebSphere Portal 8.5 v35a
If any of the features do not work for an older version, please leave a comment below.
Download the free 30-day free Dynatrace & UEM trial to gain deep user insight, understand application performance across all tiers, identify performance and scalability bottlenecks and release new code faster.
Get your free license
User Experience KPIs Dashboard
Key Performance Indicators of the User Experience, including geographic performance, Visit Statistics, Slowest and Most Frequent User Actions, and Redirects per page. Redirects on pages are not desirable and are often avoidable. Please see the following if undesirable redirects are detected:http://www-10.lotus.com/ldd/portalwiki.nsf/dx/IBM_WebSphere_Portal_V_8.5_Performance_Tuning_Guide
This dashboard displays SLA compliance information based on Visits, User Actions and Server Side Transactions (PurePaths). Outside of Dynatrace's automatic baseline violation capabilities, a business may have it's own set of SLA's for performance. By setting thresholds in this dashboard, monitoring of SLA compliance can be achieved.
WebSphere Portal Portlet PerformanceThis dashboard tracks both the time for the render method and the render method + children for all portlets rendering, making it simpler to identify poor performing portlets and pages impacted by these portlets.
WebSphere Portal JSP PerformanceThis dashboard tracks both the time for the JSP method and the JSP method + children for all JSPs, making it simpler to identify poor performing JSPs and pages impacted by these JSPs. _Default jsp is used for Themes, so theme performance can also be tracked.
WebSphere Portal MonitoringThis dashboard provides a view of the performance of the Portal hosts, processes as well as Portal Application performance. In addition to User Action and Request performance, this dashboard provides a view of the Login Performance. This is presented in context of process/host/transaction alerts.
WebSphere Portal Process PerformanceProcess Performance concentrates specifically on the performance of the WebSphere Portal Process, including heap/GC statistics, layer breakdown - which layers of code are consuming the most time - web container and JVM threads, JDBC Pool. This is presented in context of both process/host/transaction alerts as well as functional health of the system - Passed/Failed transactions, transaction rate and failure types.
Database PerformanceThe Database Health dashboard provides a high level view of database activity. Slow SQL statements provides the ability to identify and troubleshoot the slowest queries in the system. Database Time vs. Count provides a view of query performance compared to load. Pool usage and Pool % are health indicators of the JDBC connection pool. Additionally, with a host agent on the database, database host info can be seen in context, including CPU, Memory, Disk I/O, Disk Utilization and Network I/O.
WebSphere Portal Page Request Performance
Individual Page Requests are analyzed across several dimensions, including JSP time, Render time, Performance Hotspots, Exceptions and more. Select a page in the top right Page dashlet and the other dashlets will refresh to show data in context of that page.
JCR Query InsightThis is not a dashboard, but rather an example of the insight they WebSphere Portal Fastpack provides into the JCR database queries. Out-of-the-box, Dynatrace captures all DB queries, including JCR queries, typically beginning with "Select Distinct". However, these specific queries, even with Bind Variable capturing enabled, can be somewhat obtuse for developers to decipher. To help understand the JCR queries, the fastpack captures the method argument for executeXPathQuery() which provides meaningful context to the correlating query.
Just download and import the FastPack on your Dynatrace Server (see Plugin Management).Either configure your commerce agents' name to start with "WSPortalAppServer", as listed in the WebSphere Portal Server agent group, so they will be mapped to the system profile contained in the fastpack, or copy the profile to match your application and modify the contained agent groups and mappings.To use UEM you will need to match your webserver's agent name to start with "WSPortalWebServer", as listed in the WebSphere Portal HTTP Server agent group, or adopt accordingly. Also make sure to enable the UEM and webserver sensor in the agent configuration (disabled by default).
Feel free to contribute any changes on Github