PTC has an ISV License of dynaTrace and they redistribute dynaTrace with their Windchill and Integrity solutions as a tool they call PTC System Monitor (aka PSM).

This page contains a set of instructions on enabling the User Experience Management (UEM) component of Dynatrace on PTC PSM systems. Choose below for instructions for PSM 3.0 or PSM 4.0

 

PTC System Monitor 4.0 is a packaged version of dynaTrace 6.1 customized to monitor PTC solutions.

PTC System Monitor covers only the dynaTrace Java Agents.

The following describes steps you can follow to add UEM to PTC System Monitor 4.0.

  1. PTC customers with UEM licenses should have a dynaTrace PTC ISV License which includes UEM Visits Volume obtained from licensing.dynatrace@compuware.com. For UEM POC's a regular temporary POC license key should be used with enough Java agents to cover the customer's full Windchill deployment of Method Servers, Background Method Servers, etc.
  2. For PoCs make sure you backup the original license key shipped by PTC before installing a PoC key, don't forget to revert to this ISV key after the PoC
  3. Download this PSM UEM Knowledge Sensor Pack ->com.dynatrace.diagnostics.knowledgesensor.js.windchill.dtcs
  4. Import the downloaded PSM UEM Knowledge Sensor Pack (Figure A) and Choose option to Apply to all Profiles when prompted

  5. Edit Windchill Profile, choose the Method Server Agent Group, and make sure User Experience Sensor Pack is Placed (Figure B). If the User Experience Sensor is not checked in this panel then the Method Servers will have to be restarted to enable this Sensor Pack after the following steps have been completed.
  6. Edit the Windchill System Profile and Set User Experience Sensor to Active in the Method Server Agent Group (Figure C)
    1. If a web server agent is installed on the apache web server, please repeat steps 5 & 6 for the web server agent group
  7. Check Measure Request Response Sizes in Servlet Sensor of Windchill Profile Method Server Agent Group (Figure D)
  8. Edit User Experience Agent Location to /Windchill/ptc1/   (Figure E
    1. NOTE: If a web server agent is installed on the apache web server, set the Agent Location to /Windchill/
  9. Edit User Experience Monitor Request Path to /Windchill/ptc1/ (Figure E
    1. NOTE: If a web server agent is installed on the apache web server, set the Agent Location to /Windchill/
  10. Edit User Experience enabling Calculate Bandwidth refresh Rate (Figure E)
  11. Edit User Experience Tag User Visits with: Return Value of *.getRemoteUser    (Figure E)
  12. Edit User Experience Managed Captured Content Basic action capturing and disable all Event Handlers (to avoid any conflicts with integrated Authoring Tools) (Figure F)
  13. Edit User Experience Managed Captured Content enabling Basic XHR Detection and ExtJS (Figure G)
    1. Re-Open the UEM settings in Debug mode and set Custom configuration properties to "extjs.xhr=true|generic.xhr=true" (Figure E)
    2. Delete the / from Debug agent location. (Figure E)
    3. Apply changes, close the configuration and exit debug mode.
    4. If supporting IE 8 or earlier, additional configuration may be required for ExtJS. See dynatrace documentation
    5. Please note, in some instances, enabling extJS can cause some issues. If issues are detected, start by disabling extJS.
  14. Edit User Experience Managed Captured Content JavaScript Packs Additional Packs choosing featurehash=1 option (Figure G)
  15. If there is a hardware load balancer, add “True-Client-IP” to the header so the client locations and IP addresses are correctly tracked.
  16. Optionally Add Web Server Agents for Apache Web Server

Note: For UEM with PSM 4.0, it is no longer to modify the UEM Business Transaction as it is in PSM 3.0

 

 

Figure A

 

 

Figure B

 

 

Figure C

 

 

Figure D

 

 

Figure E

 

 

Figure F

 

 

Figure G

PTC System Monitor 3.0 is a packaged version of dynaTrace 5.5 customized to monitor PTC solutions.

PTC System Monitor covers only the dynaTrace Java Agents.

The following describes steps you can follow to add UEM to PTC System Monitor 3.0.

  1. PTC customers with UEM licenses should have a dynaTrace PTC ISV License which includes UEM Visits Volume obtained from licensing.dynatrace@compuware.com. For UEM POC's a regular temporary POC license key should be used with enough Java agents to cover the customer's full Windchill deployment of Method Servers, Background Method Servers, etc.
  2. For PoCs make sure you backup the original license key shipped by PTC before installing a PoC key, don't forget to revert to this ISV key after the PoC
  3. Download this PSM UEM Knowledge Sensor Pack ->com.dynatrace.diagnostics.knowledgesensor.js.windchill.dtcs
  4. Import the downloaded PSM UEM Knowledge Sensor Pack (Figure A) and Choose option to Apply to all Profiles when prompted

  5. Edit Windchill Profile, choose the Method Server Agent Group, and make sure User Experience Sensor Pack is Placed (Figure B). If the User Experience Sensor is not checked in this panel then the Method Servers will have to be restarted to enable this Sensor Pack after the following steps have been completed.
  6. Edit the Windchill System Profile and Set User Experience Sensor to Active in the Method Server Agent Group (Figure C)
    1. If a web server agent is installed on the apache web server, please repeat steps 5 & 6 for the web server agent group
  7. Check Measure Request Response Sizes in Servlet Sensor of Windchill Profile Method Server Agent Group (Figure D)
  8. Edit User Experience Agent Location to /Windchill/ptc1/    (Figure E
    1. NOTE: If a web server agent is installed on the apache web server, set the Agent Location to /Windchill/
  9. Edit User Experience Monitor Request Path to /Windchill/ptc1/ (Figure E)
    1. NOTE: If a web server agent is installed on the apache web server, set the Agent Location to /Windchill/
  10. Edit User Experience enabling Calculate Bandwidth refresh Rate (Figure E)
  11. Edit User Experience Tag User Visits with: Return Value of *.getRemoteUser    (Figure E)
  12. Edit User Experience Managed Captured Content Basic action capturing and disable all Event Handlers (to avoid any conflicts with integrated Authoring Tools) (Figure F)
  13. Edit User Experience Managed Captured Content enabling Basic XHR Detection and ExtJS (Figure G)
    1. Re-Open the UEM settings in Debug mode and set Custom configuration properties to "extjs.xhr=true|generic.xhr=true" (Figure E
    2. Delete the / from Debug agent location. (Figure E
    3. Apply changes, close the configuration and exit debug mode.
    4. Please note, in some instances, enabling extJS can cause some issues. If issues are detected, start by disabling extJS.
  14. Edit User Experience Managed Captured Content JavaScript Packs Additional Packs choosing featurehash=1 option (Figure G)
  15. If there is a hardware load balancer, add “True-Client-IP” to the header so the client locations and IP addresses are correctly tracked.
  16. Optionally Add Web Server Agents for Apache Web Server

 

UEM Business Transactions

The PTS PSM fastpack modified some of the key UEM business transactions.  As a result, they do not show up in dashboards.   To revert the business transactions to their original state, please change the settings as shown in (Figure H).
This is the list of Business Transactions to modify:

 

  • User Action Apdex by Country
  • User Actions by Apdex performance zone and Country
  • Visits by Client Family
  • Visits by Client Type
  • Visits by Landing Pages
  • Visits by Operating System
  • Visits by User Experience and Country

 

 

Figure A

 

Figure B

 

Figure C

 

Figure D

Figure E

 

Figure F

Figure G

 

Figure H

 

 

 

 

 

 

 

  1. Anonymous (login to see details)

    Dan,

    Thank you for putting this all in 1 place. 

     

    Steve