Here's a couple of things you must have, to have a successful implementation of BladeLogic.


  1. Basic capacity & performance in infrastructure.  This includes things as simple as having enough memory for the app servers, correctly configuring the relevant amount of memory for an app server per the amount of memory in the app server’s OS.
  2. At least one motivated, capable BladeLogic user to maintain use cases and drive adoption.  Historically this has been the original team that bought BladeLogic.  These individuals are usually enabled on several use cases and “BladeLogic Culture” by the POC or initial implementation, from existing motivated, capable BSA experts. 
  3. At least one important use case, tied to a key, or at least relevant business initiative.
  4. Buy-in, or at least cheerful cooperation from OS platform owners & L2 users, who can make or break agent coverage and ongoing health.
  5. Support & cooperation from the database team, on whose service BSA depends.
  6. Use Case Subject Matter Experts, whose skills, especially design & ongoing support/troubleshooting will ultimately decide whether a use case is sufficiently functional & valuable to keep doing.