This Topic explains why Microsoft System Center products becomes more important then ever before.
The layers are further defined as follows:
- Service Delivery Layer: Represents those Service Management activities that require input and interaction with the business and service owner. The components are not only responsible for that interaction, but also the translation of business requirement into technology and operational capabilities. This layer represents the business perspective on the basis of IT.
- Software Layer: Provides the applications and software that support a business activity (for example, CRM). The Software Layer consumes Virtual Machines (VM) services from the Infrastructure Layer and may consume application services from the Platform Layer.
- Platform Layer: Provides a set of platform-level (above operating system(OS) level) building blocks which can be consumed by the Software Layer. It consumes hypervisor services from the Infrastructure Layer and is managed by the Management Layer.
- InfrastructureLayer: Provides resilient hypervisor services to the Platform Layer and is managed by the Management Layer. The Infrastructure, Platform, and Software Layers represent the enabling technology perspective within IT.
- Operations Layer: Represents Service Management and operational processes carried out by IT operations and support staff.
- Management Layer: Provides management services to the Infrastructure, Platform, and Software Layers. It is comprised of the suite of management tools necessary to support IT Service and Operations Layer and implements the operational processes. The Management Layer provides a baseline set of capabilities to the Infrastructure Layer and an incremental set to the Platform Layer and the Software Layer. The Operations and Management Layers represent the operational perspective within IT.
A key tenet of the Reference Architecture is that it helps IT strategists and solution architects to make good design decisions. The guidance will only cater to the difference between the best practices of traditional IT and dynamic IT. For example, guidance on designing the directory services or change management processes already exists, so we will not duplicate that but will instead highlight what is different or new for a Private Cloud.
Examples of the principles are as follows:
- Use virtualization to abstract applications from hardware.
- Focus on Mean-Time-to-Restore-Service instead of avoiding hardware failure.
- Have a meaningful understanding of infrastructure’s health state.
- Automate “detect and respond” processes.
- Homogenize your hardware infrastructure to reduce complexity.
- Encourage desired consumer behavior.
When you keep this model in mind, you can see what this means for Microsoft System Center Virtual Machine Manager for example :
With Microsoft Product code “Concero” you get a hybrid Cloud Managementtool wich brings privat and public Cloud togehter in one Console.
More Microsoft System Center products becomes integraded.
For example, in System Center Virtual Machine Manager 2012 you can deploy your virtual application as a Service wich is sequenced by Microsoft APP-V 4.6
With this System Center 2012 Cycle you are ready for the future with Cloud technology.