Forming a Java Support Strategy
Not sure where to start in setting a strategy for Java in your organisation ? Some devs have some great ideas but don't know if that will apply across the enterprise ? With the recent changes to the Java landscape, organisations have had it thrust upon them to form a Java strategy - in both deployment as well as support. The alternative is to do nothing and let it all play out with reactive steps required as the implications are revealed.
It doesn't appear that Oracle is aggressively pursuing customers to sign up to their Java SE Subscriptions, nor do they appear to be targeting ISVs (application vendors) to be part of their Java ISV program. A similar quietness can also be found with many application vendors who only appear to share information when prodded on their support capabilities around their application's use of Java.
Maybe Java is just seen as the domain of the technical world that should deliver but never be seen. After all, Java is a development tool and runtime environment, it is not something that customers have a lot of visibility of. However, business leaders need to be aware of the risks that doing nothing may bring in this era of change.
Pebble IT in response to being asked by several organisations about the imminent changes to Java have built a new service that we title simply as a 'Java Review'.
The outcomes of a Java Review by Pebble IT is to provide visibility into the usage of Java throughout the organisation, and to quantify the difference in commercial arrangements and support coverage options that are available to the organisation. This results in a holistic Java strategy for Oracle and non-Oracle applications across the entire organisation, for both the desktop and server environments.
Why are these outcomes important ? To give you visibility and context of your exposure to risks related to your organisation's deployment of Java. Some risks that you may have but currently are unaware of are:
You may be on a release of Java that you are no longer entitled to update. This means that if there is a major security vulnerability announced (and Java has a long history in this space) or another problem is encountered with a Java internal, you will not be able to readily fix it; or
You may use an application from a vendor that cannot provide you a fix to the application without first performing a major upgrade to a release that is compatible with a supported version of Java. Application vendors will always state that there is a fix or new feature available, but the prerequisite to that is that you must update to the compatible version of the application. Whether that requires its own unplanned and un-budgeted upgrade project will depend on many factors.
Not the end of the world agreed, but a hidden danger does lurk within your IT ecosystem that would not be revealed until an unplanned event or series of events occurs. We have designed the Java Review to be a simple and achievable exercise that is inexpensive to perform and can deliver positive outcomes in risk mitigation and corporate compliance.
Please reach out to us to learn more at firstname.lastname@example.org or click here to see our contact details.