Day-To-Day Health

Let’s looks at several key tasks that traditionally constitute the bulk of the application manager’s time, specifically in relation to Fusion Applications. This includes various recommendations to help you make sure that the most amount of time is spent on items that achieve the most meaningful results.

Patching

Chapter 10 outlined the Fusion Applications patching tools and pointed to the patch guide listed in the product documentation for fine detail. We’ll therefore not discuss specific tooling here, but will instead consider what it takes to outline a healthy patching strategy.

At a high level, patching is of two types, mainly categorized based on need. The first, reactive patching, occurs when something isn’t working as designed and a fix is needed so that business users can continue to use a feature in their work. Although commonly an urgent problem, it also might involve just a simple inconvenience or the use of a temporary workaround. The alternative to this is proactive patching, for which solutions to one or more known problems are bundled and scheduled for application before any of these issues are actually experienced by users. This type of patch is commonly recommended by software vendors to ensure that any reported problems are not side-symptoms of already fixed issues. It also helps to ensure that any additional fixes needed are made on the latest code line, and a reduced complex dependency analysis to ensure backward compatibility.