AppTracker - How it Works
At some point applications will no longer be required. Managing standalone application retirements is not a complex task, but it's important that everyone in the organisation has visibility of what is live, and what has been retired. This is particularly useful when new applications are being requested as it may be that a retired application can be reinstated, rather than it being created again from scratch.
One area AppTracker can add value to the retirement process is where application dependencies are involved. Let's say we have a version of the Java Runtime which is a dependency for seven business critical Java applications. How do we put controls in place to trigger alerts if someone decides to create a new package for the latest version of Java Runtime, and retire the original Java Runtime package?
With AppTracker we can run custom scripts on a schedule. In this case we'd write a script which runs daily and looks for applications with are:
a) A dependency
b) Process is set to "Retired"
As soon as the original Java Runtime package is set to "Retired" in AppTracker, it will meet the above criteria an email alert will be sent out to the relevant teams. This Java Runtime upgrade can hopefully be stopped before it goes live, saving potential problems for those seven business critical Java applications.
As described above, there are some real benefits to using a workflow tool when retiring applications, however in most cases these do not result in a time-saving.
To see what savings are possible for your organisation please refer to our ROI Calculator.