Sherlock 2.0 Root Out the Errors

Continuing on with new things coming in Sherlock 2.0, we’ve provided great enhancements around what we log within the inspection process. This was important to us because we want Sherlock to be another trusted source of information. If Sherlock is missing data about your SAP BusinessObjects platforms, then the value is diminished. To that end, let’s get specific on capturing what Sherlock is doing within your environment.

Each time Sherlock inspects SAP BusinessObjects, it gets really specific on individual components of the architecture. All of that is our secret sauce. However, while there is a ton of value in being able to report on this content, it’s easy to overlook the fact that there is content within a platform that just doesn’t work any longer. Maybe a universe changed at some point, deleting objects, and is now causing wide spread “Obsolete objects have been removed from query” errors. Perhaps a universe is simply gone. Even worse, there may be orphaned objects in the CMS database that are no longer in the Input or Output File Stores.

Take the following for example. While inspecting a report, Sherlock was not able to open it, so we alert here:

blog005901

What exactly does this mean? Sherlock didn’t actually choke. When SAP BusinessObjects tried to present the report to Sherlock for inspection, it determined that there was an error.

What do you do with this information? Take action with the report. Chances are if Sherlock found it a user can too. This creates opportunities to better understand how aged content is used in your environment, what is broken, what is stale, and what can ultimately be rolled off to preserve resources.

While this post doesn’t really say “hey look at all the cool new data Sherlock exposes” (yet…stay tuned), what we do want to convey is, we are taking great steps to help you keep your environment in tip top shape.

If you haven’t already, go catch up on the twitter promo and get a chance to win iFanboy stuff.

Leave a Reply