As discussed in Jiving with Java 1, 2 and 3, Java offers agility and faster time to market while lowering mainframe costs. IT need to evolve their monitoring practices and tools to include Java on z. Without integrated monitoring that includes Java Environments, it is only a matter of time before Java applications will cause significant services disruptions.
In the 2016 BMC Mainframe Research survey, respondents were asked what challenges they see in running Java on the mainframe. Over 600 respondents said these 5 critical systems management responsibilities were their top concerns:
- Problem Diagnosis
- Skills Availability
Playing Nice with Others – The Case for Systems Management for Java on z
Java on the mainframe is, or will likely be, playing a crucial role in your organization. Java-based critical services provide customer-facing engagement as businesses want to be closer to their customers and in a personalized way. Given the nature of digital business, they must be available (24 x 7) on the channels their customers use. Java is a different animal compared to legacy technologies such as CICS, IMS, DB2 and MQ. It adds significant complexity for IT as it can run nearly anywhere in the mainframe environment and its resource consumption can negatively impact the performance and availability of existing workloads. Here are five best practices to deploy Java on z while mitigating risk to critical business services.
- Integrate Java monitoring and management with your existing mainframe management technologies.
- Identify automatically where Java is running across the entire mainframe environment. This is critical because the rate of Java adoption is fast, and you may not be aware that dev ops is deploying a new JVM in 10 minutes which could impact the performance and availability of critical business services.
- Leverage a centralized alarm and alert management system that eliminates non-relevant issues – so you can quickly drill down to address actual problems before they impact service delivery.
- Employ systems management software that identifies the relationships between Java and other mainframe technologies, and then guides you to the answers to performance issues to help with knowledge transfer and provide quick time to value for new mainframe professionals.
- Monitor and measure how much Java zIIP-eligible work actually runs on zIIPs to determine whether Java is really reducing costs. If there isn’t enough zIIP capacity, Java will run on a GP engine, which not only eliminates the expected cost savings but also has the potential to increase your MLC software costs.
Java on the mainframe has great potential for further enhancing the value of a platform which continues to be the mainstay of organizations around the globe. But without an integrated systems management system that includes Java environments, Java management challenges will put delivery of critical business services at risk. IT systems management teams should examine their readiness for managing Java on the mainframe, and upgrade their tools and practices to effectively support Java on z.
For information on a systems management solution that is optimized for Java click here.
- A Mainframe MLC Cost Management Maturity Model — 5 Steps to Reducing Costs
- Baseball and the Art of MLC Cost Management
- Five Essentials for Proactive Automated Mainframe Operations
- BMC and Compuware Solution Integration Changes the MLC Game
- Mainframe Sub-Capacity Monthly License Charges Is NOT Usage-Based Pricing