Performance Collection Types

This page is accessed via Configuration and Administration > Power Data > Diagnostics > Performance Collection Types.

This page lists the type of performance collections supported by Oracle Transportation Management. These types are used to check performance, and email the results if desired, using Performance Collection.

The following performance collectors are suppressed from the selection list when in a secure mode:

• ENTITY BEAN CACHES: Deprecated.
• JVM DUMP: Provides a current thread dump of the JVM. Similar to a kill -3 on UNIX systems.

These collectors provide information regarding system performance:

• ALERTS: Summary status regarding various critical system resources, including: database connection health, workflow queue backup, workflow mediation backup, object lock contention and startup errors.
• APP-TIER COMMUNICATION: Health of server to server health from the standpoint of OTM business components. This includes peer-to-peer communication between business components on separate servers via RMI, as well as peer-to-peer communication between business components and UI components via Signed Servlet.
• CONNECTION POOLS: Performance statistics for each connection pool, including active connections and average wait time.
• EVENT QUEUES: Current state of workflow queues, including queue backup and thread usage.
• FILE USAGE: A list of tracked files using the most system resources. By default, this list is limited to files larger than 1 MB, ordered by largest to smallest. These parameters can be controlled by the glog.filetracking.collector.minFileSize and glog.filetracking.collector.fileOrder properties.
• FILES: A detailed list of each managed file. An Open file cannot be deleted. FILES is not part of the Standard collectors sent to Collect Diagnostic Logs. It must be explicitly requested.
• INBOUND MESSAGES: Performance statistics for inbound integrations: transmissions and transactions.
• JVM MEMORY: Shows heap, non-heap, and memory pool usage, along with garbage collection information.
• LONG RUNNING TASKS: An overview of active long running tasks in the system.
• MANAGERS: Performance statistics for main edit screens in OTM.
• MAIL COMMUNICATION: Tracks registered Mail Senders and use cases of unregistered mail senders. This includes a summary of any invalid mail senders, why they were used, and how often they were used. All registered mail senders and mail domains are also included.
• MAIL QUOTA: Displays the overall mail quota, quota group configuration, total mail counts, blocks and drops over time, mail counts, blocks and drops by quota group over time, and mail counts by notify function, notify subject, and mail component over time.
• MEDIATOR: Performance statistics for the workflow mediator. The mediator is used to synchronize access to business objects.
• N-TIER TESTS: Performance stats for tests that cover the UI, business and database tiers.
• OBJECT LOCKS: Performance statistics for object locks. Object locks are used to synchronize access to business objects.
• OPEN CONNECTIONS: Information on open database connections. This is used in tandem with Tracked Connection properties.
• OPEN PROCESSES: Tracks all open processes, their branches, locks, and deadlocks.
• OPTIMIZATION SOLVERS: Performance statistics for classes of optimization problems OTM planning has solved.
• OTM CACHES: Status and statistics for UI and business component caches.
• OUTBOUND MESSAGES: Performance statistics on outbound integration requests, by external system.
• PENDING DML: Information regarding pending insert, update or delete SQL statements.
• REPORTS: Performance statistics regarding report generation.
• SCA MESSAGES: Performance statistics on Scalability refresh messaging (via JMS).
• SCA ROUTING: Deprecated.
• SERVERS: Provides server status across a Scalability network.
• SESSION METHODS: Performance statistics regarding session bean method calls.
• SQL STATEMENTS: Identification of the most expensive SQL statements. Note that Estimated Response is a calculated measure of performance, not an elapsed time for query execution.
• THREADS: Status of all threads used by the system.
• WEB CONTAINER: Performance statistics for web sessions maintained by the servlet container.
• WEB-TIER COMMUNICATION: Health of server to server health from the standpoint of OTM UI components. This includes peer-to-peer communication between UI components on separate servers via Signed Servlet, as well as peer-to-peer communication between UI components and business components via RMI.

Adding a Performance Collection Type

1. Enter a unique Performance ID for the performance collection type.
2. Enter a Java Plugin. The diagnostic system allows user-defined diagnostic packages to be added to configuration and performance metrics. A user-defined diagnostic must map to a Java class implementing a particular interface. This class is then added to Java Plugins with either a CONFIGURATION CAPTURE or PERFORMANCE CAPTURE use type. Once the plugin record exists, the corresponding collection type can be added.
3. Optionally, enter Additional Arguments and a Description.
4. Click Finished.