Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SCOM 2012 service SaaS

1,397 views

Published on

SCOM 2012 SaaS

Published in: Technology
  • Be the first to comment

  • Be the first to like this

SCOM 2012 service SaaS

  1. 1. SCOM 2012 as Service offering
  2. 2. SCOM as SaaS • X is an organization who provides a service to many different customers •X’s are typically providing the service to other customer companies •The same principles often apply to one organization inside a company providing a service to other ‘customer’ organizations inside the same company
  3. 3. Common Requirements •Separate access to view/edit data by customer •Allow customers to access their data over an untrusted network connection (i.e. Internet) •Allow non-AD users access •Keep track of assets and work items by customer •CSC’s want to be able to manage data across customers
  4. 4. Scenario #1 •We have multiple customers but they don’t need to interact with Operation Manager at all. •We simply need a way to monitor, operate, report, etc. to a particular customer •Views and reports should be filterable, sortable by customer
  5. 5. Scenario #1 Solution • Create a new List for ‘Customers’ • Add a new enum data type ‘Customer’ property to classes like Servers, Services and endpoints etc. and bind it to the ‘Customers’ list • Use this new ‘Customer’ property to filter and sort in views and reports • Optionally create queues and groups based on the ‘Customer’ property
  6. 6. Scenario #2 •Same as Scenario #1 but we need to send reports to our customer
  7. 7. Scenario #2 Solution •Do everything in Scenario #1 Solution •Create a Linked Report for each customer where you set the Customer parameter to a particular customer •Set up a schedule to automatically generate the report and put it on a SharePoint site, file share, or email it to your customer in .pdf, .xlsx, or .html format
  8. 8. Scenario #3 •We want end users at our customers’ sites to be able to use the self-service portal
  9. 9. Scenario #3 Solution • Set up permissions −Integrate with FIM 2010 SSO mapped to Client's AD account −Put each customer user account in an AD user group Mapping • Access to Customer Experience Portal (CxP)
  10. 10. Scenario #4 • We want people at our customer’s site to be able to view (not create or edit) their own dashboards, alerts, etc. • We want keep the data separated by customer so that customers only see their own data • We want to be able to see combined views of all customers’ data
  11. 11. Scenario #4 Solution • Do the same as Scenario #1 solution • Create groups which logically represent each customers Servers, Services and endpoints • Create queues which logically represent each customers Servers, Services and endpoints • Create views for each customer using the groups and queues as criteria • Create user roles based on Operator user role profile for each customer and scope them to the groups and queues and grant them only the views corresponding to them
  12. 12. Deployed Architecture
  13. 13. Operations Manager Infrastructure The management server is the focal point for administering the management group and communicating with the database. When you open the Operations console and connect to a management group, you connect to a management server for that management group. Depending on the size of your computing environment, a management group can contain a single management server or multiple management servers. The operational database is a SQL Server database that contains all configuration data for the management group and stores all monitoring data that is collected and processed for the management group. The operational database retains short-term data, by default 7 days The data warehouse database is a SQL Server database that stores monitoring and alerting data for historical purposes. Data that is written to the Operations Manager database is also written to the data warehouse database, so reports always contain current data. The data warehouse database retains long-term data. The Gateway server are located in the trusted boundary of the agents and can partcipate in the mandatory mutual authentication. This send Agents data to SCOM MS server over untrusted network.
  14. 14. SCOM 2012 Components Agents An Operations Manager agent is a service that is installed on a computer. The agent collects data, compares sampled data to predefined values, creates alerts, and runs responses. A management server receives and distributes configurations to agents on monitored computers. Services On a monitored computer, the Operations Manager agent is listed as the System Center Management Health service. The System Center Management Health service collects performance data, executes tasks, and so on. Management Packs The workflows that the System Center Management service runs are defined by management packs. Management packs define the information that the agent collects and returns to the management server for a specific application or technology. For example, the BizTalk Server Management Pack contains rules and monitors that collect and evaluate events and operations that are important to ensuring the health and efficiency of the BizTalk Server application.
  15. 15. SCOM Gateway Server SCOM Agent Data How it works 1 5 Monitor, Support, SLA, Reports and Dashboard Clients Server Infra of CSC Offerings Operations Management Over Http /Https X Global SCOM Services Bus X Client Compartment
  16. 16. Supported ConfigurationAgents • 3,000 agents reporting to a management server • 2,000 agents reporting to a gateway server • 15,000 agents (Windows, UNIX or Linux) in a single management group Linux and UNIX Monitoring • 500 UNIX or Linux computers managed by each management server participating in the resource pool • 100 UNIX or Linux computers managed by each gateway server participating in the resource pool • 10 maximum members in each resource pool (management server or gateway server) used for monitoring UNIX or Linux computers Network Monitoring • 2,000 network devices (~25k monitored ports) managed by 2 resouce pools • 1,000 network devices (~12.5k monitored ports) managed by a resource pool with 3 or more management servers • 500 network devices (~6.25k monitored ports) managed by a resource pool with 2 or more gateway servers Application Performance Monitoring (APM) • 700 agents for Application Performance Monitoring in a single management group • 400 applications for Application Performance Monitoring in a single management group Consoles • 50consoles total [includes desktop/web/SharePoint] URL Monitoring • 3000 URLs monitored by each management server participating in the resource pool • 10 maximum members in each resource pool (management server) used for URL Monitoring
  17. 17. UI Architecture
  18. 18. Consistent Experience – Desktop Console
  19. 19. Consistent Experience – Web Console Desktop Console
  20. 20. Consistent Experience – SharePoint Desktop Console Web Console
  21. 21. Global Service Monitor 2 1
  22. 22. Active Alerts Top 10 SQL Servers with most Alerts SQL Alerts Generated in the last 24 hours SQL Server Database State Top 10 SQL Servers with highest CPU Utilization
  23. 23. SatyaSrv.contoso.comInstance 1 SQL Server Availability over last 24 hours SQL CPU Utilization over last 24 hours SQL Memory Usage in KB Total Memory Used on Server Total Memory Used by SQL 80 % 90 % Total Memory: 50,000 KB Disk Storage Data Files: 17.6 GB 66 % 2% Log Files: 6.93 GB SQL Server Properties
  24. 24. Q & A
  25. 25. 25April 9, 2015 Thank You M Senthil Kumar www.msenthilkumar.net

×