Users building and supporting enterprise applications require end-to-end visibility, but most apps are composed of different services hosted in different environments and managed by different teams, which leads to a tendency for teams to be siloed with their own views and tools.
Today's enterprise companies continue to innovate on top of existing systems and require improvement and visibility into legacy systems such as the mainframe.
Resources are often under pressure, transactions volumes are increasing, new applications significantly increase mainframe workloads, and many mainframe applications are absolutely vital to business.
If there is a problem, how do IT Ops teams identify where the problem is located, and who to call? Teams need to manage complexity and quickly get a clear picture of all of the components on which their business applications run.
IBM and AppDynamics have already created a strong partnership across a number of different areas. Now, AppDynamics has partnered with IBM to provide transaction visibility into the mainframe subsystems using the IBM z APM Connect product offering.
The integration extends the visibility of AppDynamics Map iQ and Diagnostic iQ into mainframe subsystems, such as MQ, CICS, IMS DB, and DB2, allowing for faster problem identification. Data sharing facilitates collaboration between siloed groups and enables operations, developers, and DevOps teams to understand Mainframe dependencies and performance.
Note: The Mainframe Agent will consume 1-5 C++ SDK instances in the Controller. As this requires a purchase of AppDynamics licenses, this will already be covered.
The Mainframe licensing requires the use of 1 AppDynamics Pro license for every 16 Value Units of Mainframe capacity in addition to the IBM license requirements for the IBM z APM Connect product.
Mainframe Technology Support
- CICS via HTTP calls
- CICS
- CICS to CICS transactions
- MQ
- AppDynamics can detect backend calls made from any language agent to IBM MQ running on z/OS for either JMS or Native MQ applications (Native MQ may need additional configuration).
- JMS rules or Custom Correlation for non-JMS MQ messages are required for correlation.
- NOTE: The addition of a correlation token in the message, while done to MQ specification, may cause issues for applications not expecting additional information to be contained in the MQ message.
- CICS to IMS DB
- CICS to DB2
As shown in this diagram:
Getting Started
Requirements include a z/OS Mainframe, AppDynamics and a gateway box.
Customers interested in the new feature can contact AppDynamics (email: techpartners @ appdynamics.com).
