Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.
Going Enterprise? An Introduction to Enterprise Application Management   Stephen Feldman ( [email_address] )  Director Bla...
Who is this presentation geared for? <ul><li>System Administrators </li></ul><ul><li>Functional Administrators </li></ul><...
<ul><li>Better understanding of the various Blackboard architectural components. </li></ul><ul><li>Tips to point you in th...
<ul><li>Are race car drivers really professional athletes? </li></ul><ul><li>What’s a flying buttress? </li></ul><ul><li>C...
<ul><li>Managing an enterprise application takes a lot of work, planning and coordination. </li></ul><ul><li>Applications ...
Where does your institution fit?
Performance Maturity Model <ul><li>Most institutions fall under Level 1 </li></ul><ul><ul><li>Less then 20% qualify for Le...
Performance Maturity Model <ul><li>Implementing most of the Blackboard Reference Architecture components will help clients...
What is the Blackboard Reference Architecture?
Dell Multi-Purpose Reference Architecture
Dell Multi-Purpose Reference Architecture
Sun Multi-Purpose Reference Architecture
Going enterprise means you understand the ingredients…
Alternative Performance Configurations: Multi-Home Clustering Academic Suite Vista/CE Learning System
Alternative Performance Configurations: Distributed Load-Balancing and Clustering Academic Suite Vista/CE Learning System
Alternative Performance Configurations: Server Virtualization (Linux/Windows)
Alternative Performance Configurations: Server Virtualization (Solaris)
Going enterprise means knowing enough to be dangerous… <ul><li>Understand the components of the architecture. </li></ul><u...
Going enterprise means you build up knowledge in key areas… <ul><li>How well do you know the traffic behavior on the syste...
Going enterprise means you know how to work your way out of a brown paper bag… <ul><li>Issues will occur…be prepared. </li...
<ul><li>Operations guide and plan for managing the system </li></ul><ul><ul><li>Detailed information about the application...
<ul><li>Capacity planning guides should contain… </li></ul><ul><ul><li>Manage your deployment architecture </li></ul></ul>...
<ul><li>Disasters are unpredictable, but you can be proactive with your planning to minimize the impact </li></ul><ul><li>...
<ul><li>An enterprise system does not take care of itself. </li></ul><ul><li>An enterprise system runs 24 x 7 (365 days a ...
<ul><li>Essential operational tools </li></ul><ul><ul><li>Ticket/Issue Tracking System </li></ul></ul><ul><ul><li>Knowledg...
Want More? <ul><li>To view my resources and references for this presentation, visit  </li></ul><ul><li>www.scholar.com </l...
Questions? Steve Feldman Director, Software Performance Engineering and Architecture [email_address]
Próxima SlideShare
Cargando en…5
×

Sfeldman bbworld 07_going_enterprise (1)

  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Sfeldman bbworld 07_going_enterprise (1)

  1. 1. Going Enterprise? An Introduction to Enterprise Application Management Stephen Feldman ( [email_address] ) Director Blackboard Performance Engineering 07/10/07
  2. 2. Who is this presentation geared for? <ul><li>System Administrators </li></ul><ul><li>Functional Administrators </li></ul><ul><li>Helpdesk/Support Personnel </li></ul><ul><li>Project Champions </li></ul><ul><li>Anyone at the end of the day who is accountable for the success of your institution’s Blackboard implementation. </li></ul>
  3. 3. <ul><li>Better understanding of the various Blackboard architectural components. </li></ul><ul><li>Tips to point you in the right direction to manage various components of the stack. </li></ul><ul><li>Direction of troubleshooting issues that might occur. </li></ul><ul><li>Ideas around planning. </li></ul><ul><li>Tools that could be of useful assistance. </li></ul>What will you attain from this presentation?
  4. 4. <ul><li>Are race car drivers really professional athletes? </li></ul><ul><li>What’s a flying buttress? </li></ul><ul><li>Chemical reaction of adding water to baking soda </li></ul><ul><li>Playing Inspector Gadget </li></ul><ul><li>Rocky wasn’t a boxing champion, he was a planning champion </li></ul><ul><li>Fire is truly the most essential tool for mankind </li></ul>Presentation agenda
  5. 5. <ul><li>Managing an enterprise application takes a lot of work, planning and coordination. </li></ul><ul><li>Applications aren’t for techies, but for real users. </li></ul><ul><ul><li>Users are the greatest stakeholders that are often forgotten. </li></ul></ul><ul><ul><li>Where do they fall from a priority perspective? </li></ul></ul><ul><li>The application should run in a manner that’s seamless to your users. </li></ul><ul><ul><li>Your users should be aware, but not invested in your success. </li></ul></ul><ul><ul><li>You should be invested in the success of your users. </li></ul></ul><ul><li>It doesn’t require formal training… </li></ul><ul><ul><li>You do not have to be an accomplished DBA, network architect or application administrator to be successful. </li></ul></ul><ul><ul><ul><li>These resources should be available to assist you in time of need. </li></ul></ul></ul><ul><ul><li>You need to understand basic premises about the application from both the business and technical perspective. </li></ul></ul><ul><ul><ul><li>Understanding the business objectives can make the technical aspects of the position quite easy. </li></ul></ul></ul>Going enterprise doesn’t mean going PRO
  6. 6. Where does your institution fit?
  7. 7. Performance Maturity Model <ul><li>Most institutions fall under Level 1 </li></ul><ul><ul><li>Less then 20% qualify for Level 2 </li></ul></ul><ul><ul><ul><li>Mostly an issue over resources </li></ul></ul></ul><ul><ul><li>Less then 2% qualify for Level 3 </li></ul></ul><ul><ul><li>Less then 1% fall in the range of Level 4 or 5 </li></ul></ul><ul><li>Why? </li></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Capabilities/Resources </li></ul></ul><ul><ul><li>Level of Effort </li></ul></ul>
  8. 8. Performance Maturity Model <ul><li>Implementing most of the Blackboard Reference Architecture components will help clients transcend to Level 2 and 3 taking into account: </li></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Capabilities/Resources </li></ul></ul><ul><ul><li>Level of Effort </li></ul></ul><ul><li>Essentially we have identified components that focus on improving operational performance. </li></ul>
  9. 9. What is the Blackboard Reference Architecture?
  10. 10. Dell Multi-Purpose Reference Architecture
  11. 11. Dell Multi-Purpose Reference Architecture
  12. 12. Sun Multi-Purpose Reference Architecture
  13. 13. Going enterprise means you understand the ingredients…
  14. 14. Alternative Performance Configurations: Multi-Home Clustering Academic Suite Vista/CE Learning System
  15. 15. Alternative Performance Configurations: Distributed Load-Balancing and Clustering Academic Suite Vista/CE Learning System
  16. 16. Alternative Performance Configurations: Server Virtualization (Linux/Windows)
  17. 17. Alternative Performance Configurations: Server Virtualization (Solaris)
  18. 18. Going enterprise means knowing enough to be dangerous… <ul><li>Understand the components of the architecture. </li></ul><ul><li>Learn about their purpose and function </li></ul><ul><ul><li>All of the vendors have well documented knowledge base resources for both developers and system administrators. </li></ul></ul><ul><ul><li>They have support sites for common issues that reveal themselves in log messages. </li></ul></ul><ul><ul><ul><li>Reminder: Know where these systems log messages. </li></ul></ul></ul><ul><ul><ul><li>Tip: Google isn’t always your friend, but often the vendors who develop our components have great KB areas. </li></ul></ul></ul><ul><li>Start simple…learn basic commands and progress to advance administrative functions. </li></ul>
  19. 19. Going enterprise means you build up knowledge in key areas… <ul><li>How well do you know the traffic behavior on the system? </li></ul><ul><ul><li>What’s the busiest hour of the day? </li></ul></ul><ul><ul><li>What’s the busiest day of the week? </li></ul></ul><ul><ul><li>What’s the busiest week of the year? </li></ul></ul><ul><ul><li>Are there key events to be aware of that affect user behavior? </li></ul></ul><ul><ul><li>How long do users spend in the system? </li></ul></ul><ul><ul><li>Where do users spend their time? </li></ul></ul><ul><ul><li>What operations do they perform the most? </li></ul></ul><ul><li>How does behavior correlate to system resource utilization? </li></ul><ul><li>How well do you understand growth from user generated data and system generated data? </li></ul><ul><li>What is your institution’s policy on retaining data? </li></ul>
  20. 20. Going enterprise means you know how to work your way out of a brown paper bag… <ul><li>Issues will occur…be prepared. </li></ul><ul><li>Identify a methodology for problem resolution </li></ul><ul><li>Characteristics of a good methodology for resolving issues: </li></ul><ul><ul><li>Reliable </li></ul></ul><ul><ul><li>Deterministic </li></ul></ul><ul><ul><li>Practical </li></ul></ul><ul><ul><li>Finite </li></ul></ul><ul><ul><li>Predictive </li></ul></ul><ul><ul><li>Efficient </li></ul></ul><ul><ul><li>Impact Aware </li></ul></ul><ul><ul><li>Measurable </li></ul></ul>
  21. 21. <ul><li>Operations guide and plan for managing the system </li></ul><ul><ul><li>Detailed information about the application environment. </li></ul></ul><ul><ul><li>Summary of integration with external systems </li></ul></ul><ul><ul><li>Hardware diagrams, invoices, maintenance numbers. </li></ul></ul><ul><ul><li>Personas about roles and responsibilities </li></ul></ul><ul><ul><li>Log of activity, work completed, upgrades, maintenance. </li></ul></ul><ul><ul><li>Routine Operations </li></ul></ul><ul><ul><ul><li>Daily, Weekly, Monthly, Quarterly, Annually or Other </li></ul></ul></ul><ul><ul><li>Summary of support tickets and issues </li></ul></ul>Going enterprise means you are a planning champion…
  22. 22. <ul><li>Capacity planning guides should contain… </li></ul><ul><ul><li>Manage your deployment architecture </li></ul></ul><ul><ul><li>Handling adoption and growth </li></ul></ul><ul><ul><li>Archiving data </li></ul></ul><ul><ul><li>Maintenance windows and tasks </li></ul></ul><ul><ul><li>Integrating with external systems </li></ul></ul><ul><ul><li>Redundancy and failover </li></ul></ul><ul><ul><li>Business processes </li></ul></ul><ul><ul><li>Upgrades </li></ul></ul><ul><ul><li>Rolling out new features </li></ul></ul>Going enterprise means you are a planning champion…
  23. 23. <ul><li>Disasters are unpredictable, but you can be proactive with your planning to minimize the impact </li></ul><ul><li>Put a plan together…Practice the plan (regularly) </li></ul><ul><ul><li>Introduce new employees to the plan </li></ul></ul><ul><ul><li>Interview exiting employees to address the plan </li></ul></ul><ul><li>Get buy-in from your team and your boss </li></ul><ul><li>Put disaster recovery in your team’s budget </li></ul><ul><li>Build-in capabilities for redundancy and failover </li></ul>Going enterprise means you have a disaster recovery plan…
  24. 24. <ul><li>An enterprise system does not take care of itself. </li></ul><ul><li>An enterprise system runs 24 x 7 (365 days a year) </li></ul><ul><ul><li>Ask yourself, do you work 24 x 7 (365 days a year)? </li></ul></ul><ul><li>Administrative responsibilities from a time, event and/or milestone perspective should be documented and practiced. </li></ul><ul><ul><li>Processes should be repeatable and reliable. </li></ul></ul><ul><ul><li>Responsibilities should be clearly defined. </li></ul></ul><ul><ul><li>Processes should have workflows </li></ul></ul><ul><ul><li>Workflows have decision trees </li></ul></ul>Going enterprise means you have operating procedures…
  25. 25. <ul><li>Essential operational tools </li></ul><ul><ul><li>Ticket/Issue Tracking System </li></ul></ul><ul><ul><li>Knowledge Management System </li></ul></ul><ul><li>Essential administrative tools </li></ul><ul><ul><li>Application management tools </li></ul></ul><ul><ul><li>Database management tools </li></ul></ul><ul><li>Performance management tools </li></ul><ul><ul><li>Profiling and debugging tools </li></ul></ul><ul><ul><li>Log analytics and behavior modeling tools </li></ul></ul><ul><li>Quality Assurance Process </li></ul><ul><ul><li>Development/Test Environment </li></ul></ul><ul><ul><li>Test Cases and Test Procedures </li></ul></ul><ul><ul><ul><li>Test Acceptance </li></ul></ul></ul><ul><ul><li>Daily/Hourly Checks </li></ul></ul><ul><ul><ul><li>Is the application environment running? </li></ul></ul></ul>Going enterprise means you have tools to make your job easier…
  26. 26. Want More? <ul><li>To view my resources and references for this presentation, visit </li></ul><ul><li>www.scholar.com </li></ul><ul><li>Simply click “Advanced Search” and search by s_feldman and tag: ‘ bbworld07 ’ </li></ul>
  27. 27. Questions? Steve Feldman Director, Software Performance Engineering and Architecture [email_address]

×