1. Basic PSM 3.0 Training
Pat Kulenkamp
February 14, 2014

2. Training Agenda What is PTC System Monitor? Installing PSM 3.0
High Level Overview
Core dynaTrace Application Overview
Product Solution Overview
Installing PSM 3.0
Sizing and Placement Recommendations
Deployment Options
Pre-installation Setup
Server Installation Process
Collector Installation Process
Agent Installation Process
Getting Around the dynaTrace Client
The dynaTrace Client
The Start Center
The Cockpit
The View
The Menu
System Profiles
Filter/Status Line
Sessions

3. Training Agenda - Continued
Capturing Data
What Needs to be Collected
Sessions
DynaTrace Support Archives
Collecting Integrity Specific Information
PSM Resources

4. Chapter Agenda – What is PTC System Monitor?
High Level Overview
Core dynaTrace Application Overview
Product Solution Overview

5. What is PTC System Monitor (PSM)?
High Level Overview

6. What is PTC System Monitor (PSM)?
PSM is a custom solution that can be split into two parts:
The core dynaTrace monitoring application which backs the entire solution.
The custom Product Solution (for Windchill, Integrity etc.) that has been built on top of it
The dynaTrace Product:
Centralized multi-server system monitoring
Out of the Box monitoring for generic servers
Out of the Box notifications for common incidents
The Customized Product Solution:
Custom hooks into product
Custom notifications for core Server components
Custom notifications for end user operations
Custom actions for when incidents occur
Powered By

7. Why Use Compuware dynaTrace?
Scalable architecture
Can monitor multiple servers at the same time.
Customizable & modular configuration
Custom plugins/scripts.
Custom dashboards, incidents, sensors.
Wholistic monitoring of application, system and environment
End to end transaction visability (Database, OS, JVM)
Strings all data together for quick root cause analysis
Always-on, low overhead and in-depth monitoring
Self managing overhead
Real-time and interactive data analysis
Heap and Thread Dump analysis
Instant PurePath analysis and comparison

8. PTC System Monitor Benefits
Reporting
Diagnostics
Dashboard
Customer Benefits
Customer Problem Statement
PSM Capabilities
Customer Benefits
Lack of visibility to end-user problems
Report on SLAs per business transaction
Reduces customer effort
Improves MTTR
Transparency for Admin
Troubleshooting is time consuming
Continuous 24x7 system monitoring through Sensors
No visibility into server health status
Alert and Drill-down Dashboard capabilities
Technical Support Benefits
Reporting
Diagnostics
Dashboard
TS Problem Statement
PSM Capabilities
TS Benefits
Troubleshooting techniques are complex
PurePath technology
Improves TSE efficiency
Streamlines communication with R&D
Fewer Long Running Cases
Lack of Production Ready Diagnostic Tools
Built-in diagnostic tools operate in real-time and on historical data.
Communicating data to PTC is time-consuming and iterative.
Session data is easily exported for remote diagnostic analysis.
© 2011 PTC

9. PTC System Monitor Fundamentals
How the PSM functions
PSM is a separate server-client system powered by dynaTrace that monitors Windchill and/or Sharepoint
stays on if Windchill/Sharepoint is down
Licensed for PTC software monitoring only, but can be expanded to monitor other systems with further license purchases from dynaTrace
Continuously gathers Java/.NET method data and samples O/S metrics – “flight data recorder”
A separate database stores a subset of collected data depending on configurable parameters (for example: incident definitions)
Dashboards are accessible via URL for remote monitoring
Store and export incident data automatically and easily for use by PTC for diagnostic analysis
Customizable for specific customer requirements and custom source code
Future support for Sharepoint/MKS/FlexPLM is still being scheduled.

10. What is PTC System Monitor (PSM)?
Core dynaTrace Application Overview

11. dynaTrace Components There are 5 main dynaTrace components: Server
Agent(s)
Collector(s)
Analysis Server (Optional)
Client (Installed or Webstart)
Stand alone dedicated application server that requires a good physical server.
Real time analysis and reporting.
Requires an enterprise database referred to as the ‘Performance Warehouse’.
*The Performance Warehouse only stores Time Series data (how long an action took etc.).
Lightweight, compact and native object that is deployed on each server that is to be monitored and it resides within the application JVM.
Uses very little memory (under 50MB) and managed CPU overhead (under ~2%).
Auto upgrades.
Communicates directly with the Collector.

12. dynaTrace Components Collector(s)
Collects all data from Agents and sends it to the server.
Not lightweight but not as big as the server. Does not necessarily need a dedicated machine.
Must be local to all Agents that are being monitored. Can be remote from the DT Server (WAN).
Install a collector for each geographical location of servers being monitored.
Analysis Server (Optional)
Used to analyze proprietary dynaTrace heap and thread dumps.
If not analyzing these dumps this server is not needed.
Customers don’t need to install this. More for internal upper support and Development.
Client
Thick Java client that can be installed locally or deployed from the DT Server webpage on demand via Webstart.
Exact same client whether its installed or deployed.
Auto upgrades for minor releases.
There is also a WebUI directly on the server but this has limited reporting functionality.

13. Solution Overview Instant Notifications/ Actions Custom Scripts
Simple dashboards with
drill down capabilities
Custom Scripts
Product
Database
dynaTrace Server
Product Servers
(Integrity/Windchill etc.) with embedded Agents
dynaTrace Client
Collector
Performance
Warehouse
Administrator
Always On Monitoring
Time Series Data only

14. What is PTC System Monitor (PSM)?
Product Solution Overview

15. Product Solution Hierarchy
Below is an overview of what is included in the Product Solution.
The solution is delivered in the form of a Fastpack which is essentially an install package
There are separate solutions for each product (different Fastpack for every product)
Most of the elements below are designed and customized to work with the specific product.
Fast Pack
Profile
Sensors
Incidents
Measures/ Thresholds
Business Transactions
Agent Mappings
Tasks/ Monitors
License
Plugins
Dashboards
Dashlets
Dashboard Filter
Product Solution
Install package

16. Terminology
FastPack
Developed by each PTC sector (Windchill, Integrity etc.) and contains the entire Product implementation for dynaTrace.
The PSM Installer provides the option to install one or more fastpacks during the installation of the PSM Server.
Fastpacks can also be installed against an existing PSM server. There are two methods for doing this:
If you have a PSM client installed double click on the fastpack to automatically launch the client and install
In any PSM client (installed or webstart) go to Settings->Server Settings->Plugins and select Install plugin
A fastpack Includes the following:
PSM License
System Profile
Business Transactions
Measures/Thresholds
Incidents
Sensors
Tasks/Monitors
Customized Dashboards
Customized Plugins

17. Terminology Profiles/Configurations
The profile contains all the Sensors, Incidents, Measure definitions/thresholds that work with a specific Product.
Many Agents can map to a single Profile if they share the same thresholds.
Configurations can enable and disable sensors on the fly. Example: ‘Debugging’ Configuration.

18. Terminology Agent/Agent Mapping
The actual application servers that are being monitored are referred to as Agents (the PSM agent is installed on them).
The profile that an Agent sends information to is defined by an Agent Mapping. An agent mapping has 2 sides:
The Profile Definition:
The JVM instrumentation line: agentpath:"C:/Progra~1/dynaTrace/DTAgent/agent/lib64/dtagent.dll"=name="Integrity_Server",server=dtserver:9998
In the mapping example above an application server will map to the profile if the name specified in the instrumentation line starts with Integrity_

19. Terminology
Sensors
Define entry points (a method/function) in the Product code for dynaTrace to start tracking.
A sensor can also optionally define return arguments and function parameters to capture.

20. Terminology PurePaths SQL Query Details
Start to Finish transaction recording.
Can cross multiple Agents to build a full end to end transaction (such as a client and server agent)
A sensor defines the starting point (entry point) of a purepath
A PurePath captures method calls and return/argument values as defined by the sensor
A PurePath automatically captures method execution/suspension times.
SQL Query Details

21. Terminology Monitors/Tasks
Monitors can be configured to execute on remote machines on a scheduled basis
Monitors store the resulting data in measures that can be tracked over time and used as a data points for Incidents.
Tasks can be configured to execute on remote machines on a scheduled basis and execute a plugin/task.
Tasks do not capture any measure data however.

22. Terminology
Measures
Single data point that is captured from either a PurePath or a Monitor (i.e. How long an operation took)
Thresholds levels can be defined for each measure.
The server will store measure data for each agent in the Performance Warehouse (database) as Time Series data
Can capture method return value, argument values, exec time, etc.
Measures can be based off of the Invocation of a certain method (i.e. How many times did methodA() get called)

23. Terminology Measures - Resolution Duration
Measures will get averaged out and purged over time.
This is referred to as Resolution Duration
High Resolution equates to minute by minute data
Medium Resolution equates to hour by hour data
Low Resolution equates to day by day data
Can be configured to whatever resolution is desired
- Settings -> dynaTrace Server - > Performance Warehouse -> Storage Management

24. Terminology Business Transactions Logical grouping of PurePaths
Can be used as a basis for Incidents
Enhances visibility into usage of the product
Can filter out PurePaths based on criteria
Can be used as chart measures
- Each product has a number of key Out-of-the-Box Business Transactions

25. Terminology Dashboards/Dashlets
Dashboards are views that display a set of information
Dashboards are composed of Dashlets which organize and display data in different ways (ie. a graph or a chart).
Dashboards can be locked down with view permissions.
Can be opened from the ‘Dashboard’ menu or from right clicking in a Dashboard and selecting ‘Show in Dashboard’.

26. Terminology Incidents
An event that you would like to be notified on or take action on.
Define incident criteria based off one or more Measures/Business Transactions.
Notifications include pop-ups in the DT client, s, etc.
Actions can include:
Thread Dump
Heap Dump
dynaTrace Session Dump
Integrity API Execution
Generic Command Execution (script)
More...

27. Chapter Agenda – Installing PSM 3.0
Sizing and Placement Recommendations
Deployment Options
Pre-installation Setup
Server Installation Process
Collector Installation Process
Agent Installation Process

28. Sizing and Placement Recommendations
Installing PSM 3.0
Sizing and Placement Recommendations

29. Sizing & Placement Recommendations
Components Review
PSM Server
PSM Collector
PSM Agents
Performance Warehouse Database
PSM Client
Analysis Server (optional)*
*Note: An Analysis server is not useful in an Integrity environment as the PSM configuration for Integrity does not utilize dynaTrace proprietary heap/thread dumps.
Before we get started lets briefly review the various PSM components.
As described in the PSM Concepts module, there are 5 PSM components that you will need in your environment:
The PSM Server,
At least one PSM Collector,
Agents installed on any application server that requires monitoring, a database to house the performance warehouse,
and a PSM client.
When monitoring Windchill you can also install the optional Analysis server.

30. Sizing & Placement Recommendations
Deployment Best Practices
In a production environment, it is recommended to install the PSM server and collectors on separate hardware from the Application Server (Windchill or Integrity). This allows PSM to operate when the Application Server hardware is down.
You can monitor both Integrity and Windchill using the same PSM server. To do this you need to install the fastpacks for both Integrity and Windchill.
Demo/test install can be done monolithically on single laptop or Virtual Machine with at least 6 Gb ram and sufficient disk space for installation (6 Gb), session storage (10 Gb) and Performance Warehouse (10 Gb).
It is mandatory to use one or more standalone collector processes rather than using the built-in (embedded) collector in the Server process. 
The Analysis Server is optional and is only used in a Windchill configuration to analyze dynaTrace proprietary heap/thread Dumps from large JVM Heaps.
In a production environment, it is recommended to install the PSM server and collectors on separate hardware from the Application Server (Windchill or Integrity). This allows PSM to operate when the Application Server hardware is down.
You can monitor both Integrity and Windchill using the same PSM server. To do this you need to install the fastpacks for both Integrity and Windchill.
For a demo or test PSM environment, all components can be installed on the same machine or VM provided that there is enough disk space and memory available.
It is recommended use one or more standalone collector processes rather than using the built-in (embedded) collector in the Server process. 
The Analysis Server is optional and is only used to analyze Memory Leak Dumps from large JVM Heaps in a Windchill configuration.

31. Sizing & Placement Recommendations
Base Recommendations - PSM Server
64-bit System
CPU:
at least two CPUs dedicated to Server
Memory:
6 to 14 Gb physical memory (4 to 12 Gb allocated to the heap), depending on application usage and number of servers being monitored
Note: In default deployments, the main site Collector JVM (heap size 1 to 2 Gb) is usually running as a separate process on the same host as the PSM Server. Add this to memory requirement when needed.
Storage Space:
Recommend starting with GB depending on frequency of stored session creation.
Session storage can take significant disk space over time.
Note: Sessions are not stored in the Performance Warehouse database, they are stored on the file system.

32. Sizing & Placement Recommendations
Base Recommendations - PSM Collector
64-bit System
1 Gb heap recommended for low usage, 2 Gb for large usage
Collector should be local to its agents (in the same LAN), however the Collector can send data over WAN to the PSM server.
Agent load can be balanced by using multiple collectors if network or host resources require.
Collector can be located on separate hardware/VM from the PSM server, but the default installation is to locate the two processes on the same host.
Recommend no firewalls between agents and collectors
The embedded collector is not supported for production environments.

33. Sizing & Placement Recommendations
Base Recommendations - Performance Warehouse Database
The size and location of the database is dependent on how many measures you capture and how high the resolution is for stored data.
Typically, allow 20 GB of disk space for the data files and transaction logs generated yearly from a medium-sized environment.
The database can be installed either on the same server that will be used for the PSM server or on a server that is available through the network.

34. Sizing & Placement Recommendations
Base Recommendations - Analysis Server (optional)
The Analysis Server is only useful for Windchill environments if dynatrace heap dump analysis’ will be performed.
An Analysis server is not useful in an Integrity environment as the PSM configuration for Integrity does not utilize dynatrace heapdumps.
There are two situations where you should refrain from installing the Analysis Server on the PSM Server machine.
Memory dumps are too large. If you need to analyze huge memory dumps (eg. 16 GB) and don't have enough additional memory to assign heap to the Analysis Server, you have to run the Analysis Server on a separate machine.
High CPU Usage of the dynaTrace Server. If the dynaTrace Server already has a high constant CPU usage post processing memory dumps will lead to data loss (skipped events, not analyzed PurePath, ...)
The amount of memory available to the analysis server must be as large as the largest monitored JVM plus 25%. For example, if your largest monitored JVM is 4 Gb, the Analysis Server should be configured for 5 Gb in order to process memory dumps.
*Note: The Analysis Server is usually in stand-by mode rather than actively running, unless a thread or heap dump is being analyzed.

35. Sizing & Placement Recommendations
PSM Deployment Guide
To assist with sizing, PTC provides a spreadsheet you can use to obtain PTC recommendations for PSM Server and Collector requirements, server storage, and database storage.
Download the spreadsheet from the PTC System Monitor Resource Page using the following link and save the spreadsheet locally:

36. Sizing & Placement Recommendations
Using the PSM Deployment Guide
Provide values in the “Fill in Deployment Numbers Section”
The tool will automatically calculate the values required to determine the size of your deployment
Under “Recommended Deployment Scenario” click on the Size to see the recommended server requirements for your environment
Please see the “Sizing Guidelines” section of the Windchill Installation and Usage guide for more information: /en/PSMInstallUsageGuide- Windchill.pdf 

37. Installing PSM 3.0
Deployment Options

38. Single Host Configuration
Deployment Options
Single Host Configuration
In this configuration, the system monitoring software is installed on the same host as the application server.
Single Host
Application Server
(Windchill, Integrity etc.)
PSM Client
PSM Collector
Port 2020 or 2021 for Installed Client
Port 8020 or for Webstart Client
PSM Server
A single host configuration is appropriate if you will be monitoring a single server, or if you are a first time user of the PTC System Monitoring software who wants to investigate its usage with the least amount of configuration required. However, it is recommended to install the PSM server and collectors on separate hardware from the Application Server .

39. Desktop Virtualized Installation
Deployment Options
Desktop Virtualized Installation
This configuration is particularly advantageous if you have a limited amount of memory in virtual machines but can accommodate the use of the PTC System Monitor on the host machine
Host Machine
Virtual Machine(s)
Application Server
(Windchill, Integrity etc.)
Port 9999
PSM Client
PSM Collector
PSM Server
In cases where the application you are monitoring exists on a virtual machine, consider installing the PSM Server and Collector on the machine housing the VM (primary usage would be with VMware Workstation only, not with the enterprise level VMware ESX or Microsoft Hyper-V configurations).

40. Production and Test Configurations
Deployment Options
Production and Test Configurations
For production and test environments, PTC recommends that you install the dynaTrace Server and Collector on a separate machine.
Main Site Server LAN
Application Servers (Windchill, Integrity etc.)
System Monitoring Server
Agents
PSM Client
Port 9999
PSM Collector
Port 2020 or 2021 for Installed Client
Port 8020 or for Webstart Client
PSM Server
Use of a separate system provides the ability to monitor, measure, and alert administrators of both application and infrastructure related issues.
*Note: This type of configuration is required in cases where you are using Integrity clustered application servers. This environment treats the system monitor as a neutral party

41. Windchill Remote File Servers
Deployment Options
Windchill Remote File Servers
When connecting to a Windchill environment that has remote servers where you want to monitor the file servers, you must install a DynaTrace Collector locally with the remote file server
Main Site Server LAN
Windchill Application Servers
Remote File Server WAN
System Monitoring Server
PSM Client
Port 9998 or 9999
PSM Collector
Port 2020 or 2021
PSM Server
Windchill File Server
Port 6698 or 6699
PSM collector
*Note: There can be multiple Windchill remote file servers; EACH remote server requires its own collector.

42. Pre-installation Setup
Installing PSM 3.0
Pre-installation Setup

43. Pre-installation Setup
Database Setup
Prior to the installation of PSM, a database needs to be created to house the Performance Warehouse. This can be either an Oracle or MsSQL database.
Recommended Settings for the Database:
Feature
Required/Optional
Description
Read/Write Permission
Required
r/w of data must be possible for the dynaTrace user
Collation
the database needs to use a case insensitive collation
Create/drop tables, indexes
for schema creation/upgrade and deletion
UTF 16 compatible charset/codepage
Optional
a non UTF16 compatible charset ("Test Connections" checks compatibility) can lead to problems using measure names which are using the full UTF16 char set spectrum
Note: All pre-configured measures included in the Windchill and Integrity fastpacks do not have special characters in their names. As such UTF 16 is only required if you plan on creating your own custom measures with special characters in the name.

44. Pre-installation Setup
Download the PSM 3.0 Installation Package
Download PTC System Monitor 3.0 from the PTC Software Download Page
The download package is listed under the Windchill PDMLink, FlexPLM, Windchill ProjectLink, Servigistics Service Center, and Integrity products
All product links download the same package

45. Pre-installation Setup
Extract the PSM 3.0 Installation Package
After you have downloaded the installation package extract it into a temporary folder.
The resulting folder structure can be seen below:
The plugin directory contains an agent plugin file for each product:
These files are used to by the PSM installer when installing the agent for a product
The PTCFastPacks directory contains a fastpack for each product:
The PSM installer will install fastpacks based on product selection during the server installation

46. Pre-installation Setup
Java Requirements
To run the PSM Installer, you must have Java 5 or Java 6 in your path.
Additionally, your system must meet the following Java requirement to run PTC System Monitor components after they are installed:
PTC System Monitor requires that Java 6 or higher is installed and that JAVA_HOME is correctly set.
There is an issue with Java 6 update 26 on Windows. The native file selector dialog fails. This affects using Webstart Clients. PTC recommends that you use Java 6 with update 27 or later.

47. Pre-installation Setup
Open TCP Ports
The following list shows the default communication ports for PSM. Firewalls between components must be configured to allow communication to pass through.
Client-to-Server Port 2020 (ssl 2021) TCP
Collector-to-Server Port 6698 (ssl 6699) TCP
Agent-to-Collector Port 9999 TCP
Server Default Webpage Port 8020 (ssl 8021) TCP

48. Server Installation Process
Installing PSM 3.0
Server Installation Process

49. Starting the Installation
Installation Process
Starting the Installation
Open a command prompt window on the system where you want to install the dynaTrace components.
On Windows 7 right click on the command prompt option and select Run as administrator
Navigate to the directory containing the PSMInstaller.jar and execute java –jar PSMInstaller.jar to launch the Installer GUI.
Select the Component(s) to install on the host:

50. Server Configuration – Location and Connection
Installation Process
Server Configuration – Location and Connection
Installation Directory will be shared with Collector if both are being installed.
Keep default values for ports and the Bind Addresses ( ) whenever possible.
Set password for the “admin” user account.

51. Server Configuration - LDAP
Installation Process
Server Configuration - LDAP
Three Options for managing PSM User and Group Access
Manage users and groups through PSM Client (locally on PSM server)
Connect to a Windchill Directory Server
Use pre-defined default values where applicable
Connect to Corporate Ldap
Use pre-defined default values

52. Server Configuration – Performance Warehouse Database
Installation Process
Server Configuration – Performance Warehouse Database
Three Database Options
Embedded
Should never be used for a production or Test environment (demo purposes only)
Oracle
SQLServer
*Note: Use the connection information for the database you setup during pre-install here.

53. Server Configuration - Email
Installation Process
Server Configuration -
Provide connection details for your SMTP server in order to receive notifications from PSM.
Username and Password is not required if you have an open SMTP server.

54. Server Configuration - Products
Installation Process
Server Configuration - Products
Select the product(s) that you want PSM to monitor.
The Fastpack (default configuration) will be installed for any product selected.
You can monitor multiple products on the same PSM server.

55. Server Configuration – Database Monitoring
Installation Process
Server Configuration – Database Monitoring
The PSM installer has the option to configure database monitoring capabilities for the product(s) being monitored
All products can be configured to monitor it’s backing database (Oracle or MSSQL)
With the exception of Integrity, the installer will automatically present a database monitoring configuration pane for each product selected:

56. Server Configuration – Extended Integrity Monitoring
Installation Process
Server Configuration – Extended Integrity Monitoring
When Integrity is selected as a product you will be asked what monitoring you want to configure
Based on your selection you will be prompted with the appropriate monitoring configuration panes
The Database Monitoring configuration pane is almost identical to the other product panes
The Additional Monitoring pane has two purposes:
Under Integrity Monitors you can select the additional Integrity metrics that you would like to track in PSM (Licensing, Connections etc.)
Under Connection Properties you can specify (or import) the Integrity credentials required by PSM to connect to the Integrity server(s) and gather the additional metrics. Note: See the following KCS article for information on the import file format:

57. Collector Installation Process
Installing PSM 3.0
Collector Installation Process

58. Collector Configuration – Connection information
Installation Process
Collector Configuration – Connection information
Installation Directory will be shared with PSM Server if both are being installed.
Set hostname/IP address or “localhost” for the PSM Server
Set Port to match the PSM Server if it was changed during the server installation.
*Note: The installer must be able to connect to the PSM server specified here to proceed (unless the collector and server are installed at the same time)

59. Collector Configuration – Product selection
Installation Process
Collector Configuration – Product selection
Select the Product(s) that will be connecting through this collector.
This is used to determine if any additional configuration is required on the PSM collector
Multiple products can connect through the same collector

60. Collector Configuration – Integrity Connection Properties
Installation Process
Collector Configuration – Integrity Connection Properties
If Integrity is selected on the previous pane then you will be prompted for Integrity connection properties
These settings allow the PSM collector to connect to the Integrity server(s) and gather additional metrics
If you have already set these properties during a separate PSM server install, you can import the generated is_conn.properties file from <PSM home>/server/conf
*Note: For more information in regards to the is_conn.properties file please see the following article:

61. Agent Installation Process
Installing PSM 3.0
Agent Installation Process

62. Agent Configuration – Fastpack Selection
Installation Process
Agent Configuration – Fastpack Selection
Select the fastpack(s) that are installed on the PSM server
This will limit the product selection on the next pane to agents that work with the selected fastpacks.

63. Agent Configuration – Product Selection
Installation Process
Agent Configuration – Product Selection
Select the product(s) that you want to install PSM agents to.
If you have two different applications on the same machine (ie. Integrity server and Integrity client) you can select multiple agents to install
You will be required to specify the product directory for every product selected
The following require further input which will be covered in the next slides:
Integrity Server
Windchill 10.x
Windchil 9.1

64. Agent Configuration – Integrity Server
Installation Process
Agent Configuration – Integrity Server
When installing an agent on an Integrity Server you will be prompted for the following additional information:
API Settings: you can set these properties to have the installer modify the Integrity Servers IntegrityClientSite.rc file to allow for API connections.
JMX Monitoring: enabling JMX on the Integrity server allows for PSM to monitor for deadlocks as well as gather heapdumps and stacktraces in cases where the API does not work.
*Note: In order to setup JMX monitoring via the PSM installer you must first create jmxremote.password (copy jmxremote.password.template) in <Integrity Server>/jre/lib/management

65. Agent Configuration – Windchill 10.x Server
Installation Process
Agent Configuration – Windchill 10.x Server
When installing an agent on a Windchill 10.x Server you will be prompted for the following additional information:
PSM Server Connection Settings: these settings will allow Windchill web services to connect to the PSM server
Windchill Built-in Monitoring Capabilities: you can have the installer disable duplicate Windchill monitoring capabilities by selecting yes here. This will set the following in the Windchill db.properties file: wt.pom.traceTiming.enable=false
*Note: The installer will test the PSM Server connection settings. As such the settings must be valid and the PSM server must by running in order for the installer to continue.

66. Agent Configuration – Windchill 9.1 Server
Installation Process
Agent Configuration – Windchill 9.1 Server
When installing an agent on a Windchill 9.1 Server you will also be prompted for the Tomcat Home directory as Tomcat is installed in it’s own directory

67. Agent Configuration – Collector Connection Settings
Installation Process
Agent Configuration – Collector Connection Settings
Lastly you will need to specify the connection settings for the collector that the agent will connect to
The installer will test these settings so they must be valid and the collector must be running

68. Chapter Agenda – Getting Around the dynaTrace Client
The Start Center
The Cockpit
The View
The Menu
System Profiles
Filter/Status Line
Sessions

69. Getting Around the dynaTrace Client
There are two types of dynaTrace clients that can be used with PSM:
Webstart client
Hosted on the PSM server
Can be accessed via Server host>:8020/ or PSM Server host>:8021/
Contains custom help specific to the PSM solution
Does NOT autolaunch when dynaTrace proprietary files are double clicked (sessions, plugins etc.)
Installed client
Must be manually installed on a client machine (can be any machine with access to the PSM server)
You can download the client installer at (bottom of the page)
Contains standard dynaTrace help, NOT PSM specific help
Will autolaunch when dynaTrace proprietary files when double clicked (sessions, plugins etc.)
*Note: besides the points mentioned above, both clients have the exact same functionality.

70. Getting Around the dynaTrace Client
The Start Center
By default the Start Center opens every time you start the dynaTrace client
Generally this can just be closed but it does have some useful functionality:
Alerts you of various configuration options that should be set/changed
Under Deployment Health you can launch dynaTrace Self-Monitoring health dashboards. These dashboards give an overview of the performance of PSM components such as server and collector
After closing it can be launched again by clicking the green play button at the top left corner of the client.

71. Getting Around the dynaTrace Client
The Cockpit
Starting point to open up any individual dashlet or view.
By default the Cockpit is located on the left of the client
Gives access to Overview, Profiles and Sessions. Not Dashboards.
The Cockpit can be pinned or unpinned to give more real-estate to the view that you have opened

72. Getting Around the dynaTrace Client
The View
Dashboards, dashlets and any other views will be displayed here
If multiple views are opened they will be tabbed across the top

73. Getting Around the dynaTrace Client
The Menu
Dashboard
Open existing dashboards
Create your own custom dashboards
Modify dashboard properties
Run reports
Exit the client
Tools
Import Session
Manage plugins
Fullscreen the client (F11)
Settings
Access to both PSM client and server specific settings
Password change

74. Getting Around the dynaTrace Client
System Profiles
Product Profiles can be found in the cockpit under System Profiles
By default a PSM server has at least the dynaTrace Self-Monitoring profile
Other profiles for PTC products are generally installed by the PSM installer but can also be installed manually
Profiles contain information such as Buisness Transactions and purepath information

75. Getting Around the dynaTrace Client
Filter/Status Line
Global data source filter (Unless overridden at the dashlet level)
In the example below:
‘Integrity Overview’ is the Dashboard
‘PTC Integrity Server’ is the System Profile
‘From last 1 hour’ is the timeframe
‘Business Transaction Item – New’ is a custom filter for that specific data
*Tip: Not seeing the data you expected? Check the filter!

76. Getting Around the dynaTrace Client
Sessions
Contains all timeseries and PurePath data for a specific timeframe.
Can be manually captured by right clicking on a profile and selecting Session Storage->Store Session
Automatically generated by many Incidents
Can be exported to a single file by a customer and sent into support.
Stored on the dynaTace server filesystem, not in the database.

77. Chapter Agenda – Capturing Data
What Needs to be Collected
Sessions
DynaTrace Support Archives
Collecting Integrity Specific Information

78. What Needs to be collected
Capturing Data
What Needs to be collected

79. Capturing Data What Needs to be Collected Sessions
What is a Session?
Gathering for a Specific PurePath or Business Transaction
Gathering for a Given Timeframe
Incident Actions
DynaTrace Support Archives
What is a DynaTrace Support Archive?
Gathering a DynaTrace Support Archive
Collecting Integrity Specific Information
How to Contact PTC Support for PSM issues
In this web based training module we will be covering: PSM component sizing and placement recommendations
PSM component deployment options
Pre-installation setup

80. What Needs to be Collected
In order for PTC Support to Investigate issues detected in PSM, the following set of data should be collected:
An exported session containing PSM data related to the issue
Sessions are a package of purepaths and measures for a given period of time
A dynatrace support archive
The support archive contains important information about the PSM environment such as logs, settings and system profiles.
Integrity or Windchill specific information
The presentation will describe in detail where and how to gather this data.

81. Capturing Data
Sessions

82. Sessions What is a Session?
A “session” in PSM is a set of diagnostic data captured from a system profile.
Sessions are not stored in the Performance Warehouse, but are locally stored on the PSM Server or PSM client.
Information types contained in a sessions can include:
PurePath Session: represents the combined information about PurePaths and Time Series (sampled data) within a given time period
Memory Dump: contains analysis data about the number, size and class of allocated objects and their references
Thread Dump: is a collection of data for thread analysis including CPU time information
Sampling (CPU): provides statistical data of all threads currently being serviced by the CPU
There are 3 types of session:
Live: a Purepath session performed on live data in the server cache
Stored: any of the 4 information types above, stored on the client or Server
Offline: A session that was stored on the client, and can be accessed without the server.

83. Gathering for a Specific PurePath or Business Transaction
Sessions
Gathering for a Specific PurePath or Business Transaction
If there is a specific purepath or business transaction that needs to be investigated, right click on it and select Export. In the dialog that appears, specify a location to save to and set Content to “Purepaths and time series”
*Note: when possible do not remove confidential strings from the session. This would result in SQL being stripped from the session which could be very important to the investigation.

84. Gathering for a Given Timeframe
Sessions
Gathering for a Given Timeframe
If you want to export a session for a given period of time, right click on the system profile and select Session Storage->Export Session. In the dialog that appears, specify a location to save to, the timeframe to save for, and set Content to “Purepaths and time series”
*Note: when possible do not remove confidential strings from the session. This would result in SQL being stripped from the session which could be very important to the investigation.

85. Sessions Incident Actions
Most Incidents are configured with an action that will automatically store a related session on the PSM server when they occur.
To find the related session match up the Incident start time with the time stamp on the session under Session Storage.
Right click on the session and select “Export Session”
In the dialog that appears, specify a location to save to, leave default values for timeframe, and set Content to “Purepaths and time series”
*Note: when possible do not remove confidential strings from the session. This would result in SQL being stripped from the session which could be very important to the investigation.

86. DynaTrace Support Archives
Capturing Data
DynaTrace Support Archives

87. DynaTrace Support Archives
What is a DynaTrace Support Archive?
A “dynaTrace support archive” is a zip file containing information specific to the dynaTrace environment. The packaged files provide a good overview of your PSM environment/setup.
The following information is gathered:
Any system profiles stored on the dynaTrace server
Log files from the dynaTrace server and any connected collector (including plugin logs)
DynaTrace licensing information
An export of dashboards stored on the dynaTrace server
DynaTrace configuration files
A “dynaTrace support archive” can also be collected for the dynaTrace client, but in most cases this is not necessary to debug issues.

88. DynaTrace Support Archives
Gathering a DynaTrace Support Archive
To gather a “dynaTrace support archive” :
double click on “System Information” in the “Cockpit”
In the dashlet that appears, right click on the PSM server name and select “Package All Included Files”
Give a filename and location to save to.

89. Collecting Integrity Specific Information
Capturing Data
Collecting Integrity Specific Information

90. Collecting Integrity Specific Information
In Integrity Configurations, PSM Incidents will automatically generate related Stacktraces and/or Heapdumps on the Integrity server.
*Note: Integrity configurations do not utilize dynaTrace proprietary thread dumps or memory dumps, instead stacktraces and heapdumps will be generated in <Integrity Server Path>/ bin.
If an Incident occurs that you would like Integrity support to investigate, gather any heapdumps (*.hprof) or “stacktrace” files from Integrity Servers “bin” directory that were generated around that time:
*Note: Stacktraces are cumulative, so if time has passed since the Incident occurred, it is possible that the Stacktrace will have a newer datestamp than the Incident
You can see if an Incident will generate a heapdump or stacktrace, by right clicking on the Incident, selecting “Edit Incident Rule”, and selecting “Advanced Configuration” on the “Actions” tab:

91. PSM Resources
The main resource page for PSM is:
On this page you will find documentation, training material, demonstration videos, and other useful information
See the PSM Hub on KCS for a lot more useful information:
This article was developed by the Integrity PSM team, but a lot of the information is relevant to other platform solutions as well
The PSM Installer can be downloaded from the PTC Software downloads page:
The download package is listed under the Windchill PDMLink, FlexPLM, Windchill ProjectLink, Servigistics Service Center, and Integrity products