As we know Service Provider Foundation is the API of VMM. SPF is a web service that can execute tasks against VMM server and WAP just connects to SPF to communicate with VMM so we have the following communication path VMM<->SPF<->WAP. Continue reading “Working in VMM like Service Provider Foundation and Windows Azure Pack”
Tag: Service Provider Foundation
SCOM APM for Orchestrator, SPF, SMA and WAP
Orchestrator, Service Provider Foundation, Service Management Automation and Windows Azure Pack are all web applications or web services or both. They are all monitored by IIS 8 Management Pack in Operations Manager but that MP can only provide monitoring to certain levels to solve these limitations in SCOM (SP1 and R2 for IIS8) we have Application Performance Monitoring (APM). This blog post does not aim to show you some advanced features in APM but rather to show you how to enable some advanced monitoring for those services. As SMA and WAP are available only in R2 I will use the R2 wave. Let’s start with enabling APM for every service:
Service Provider Foundation
Open SCOM console. Go to Authoring pane. Start Add Monitoring Wizard.
Select .NET Application Performance Monitoring
Give a friendly name to the application and create new management pack where the settings for this application will be saved.
Click on Search and add the two web service in SPF – VMM and Admin. Click OK.
It is always a good practice to put Environment.
Accept the default settings. The idea is to fine tune these settings depending on the performance of the application in your environment. If you have more than one environment (development, test, production and etc.) these settings can be different because some environments will have less resources than other and the application can perform slowly because of that. SPF is only web service and because of that does not have portal so client-side monitoring is not relevant. On summary page click Create and wait until the APM for SPF is created.
And the result is:
From now on when you have data for a long term period you can fine-tune the APM settings. You can even set exceptions for some methods.
Orchestrator Web Service and Console
Orchestrator has Web Service and Console (Web Application).
One Web service and Web application (portal) added,
Orchestrator has web application but do not enable client-side monitoring for now.
To enable client-side monitoring you need first have to check if the web application could be enabled for this client side monitoring. This is done trough a task Check Client-Side Monitoring Compatibility which is available in Monitoring Pane –> Application Monitoring –> .NET Monitoring –> IIS 8.0 ASP.NET Web Application Inventory View. Select the web application you would like to test and execute the task from the Task pane.
I’ve enabled the client-side monitoring for the Orchestrator console but even I didn’t received any error in SCOM or on the Orchestrator portal no performance counters were shown from client-side:
Windows Azure Pack
You need to add all found Web Applications for Windows Azure Pack:
I am not using WAP intensively in this environment so I do not have so much data:
Because I do not have even database created for WAP you can see the performance exception created for that:
APM can very useful to public user portal like Tenant Site in WAP:
Because of that I’ve tried to check if client-side monitoring can be enabled but unfortunately the check returned negative results:
Service Management Automation
Service Management Automation is part of Orchestrator setup but can be connected to WAP.
Only one web service is available so no client-side monitoring will be available:
As a summary I hope this will help you in providing advanced monitoring for these Web Services and Application as they are of the Microsoft Cloud OS and critical for Cloud Providers. What I would like to see in the future instructions or possibility from Microsoft on how to enable client-side monitoring for at least the Tenant Site.
Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 5 Service Provider Foundation and Service Reporting)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 1 Operations Manager)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 2 Service Manager)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 3 Virtual Machine Manager)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 4 Orchestrator and Service Management Automation)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 5 Service Provider Foundation and Service Reporting)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 6 App Controller)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 7 Data Protection Manager)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 8 Configuration Manager)
- Install All System Center 2012 R2 Preview Components and Windows Azure Pack Preview (Part 9 Windows Azure Pack)
Next on the line is Service Provider Foundation which also part of Orchestrator.
We have to install some prerequisites:
We now have the option to generate self-signed certificate trough the installation:
Usage endpoint now can be installed trough the installer:
In SPF 2012 R2 there are a lot of more APIs for VMM.
There is another role in the Orchestrator installation media but I hadn’t resources to install it so I will just show you the first installation screens. This new role is Service Reporting which is like a Data Warehouse for hosting providers from which they can get data for billing Tenants. As far as I know it requires Windows Azure Pack to work but there might be a way to use it without it we just have to learn more about this role.
Small improvements on the installation experience of SPF by adding Usage endpoint installation and generating self-signed certificate.
Update Rollup 1 for System Center 2012 Service Pack 1
Yes it is true. The freshly released Service Pack 1 of System Center 2012 has update rollup. Here are the fixes:
App Controller (KB2790935)
Copying a .vhd file between Windows Azure storage accounts may be unsuccessful, and you receive a "Retrieved data is complete" warning message. This issue occurs if the .vhd file already exists on the destination or if the .vhd file is mapped to an existing virtual machine.
The import of Virtual Machine Manager (VMM) library server certificates may be unsuccessful for VMM library servers that are clustered.
Data Protection Manager (KB2791508)
Client backups fail when there is a case difference between the client computer name on the computer and the client computer name that is stored in Active Directory.
Operations Manager (KB2784734)
Agentless Exception Monitoring (AEM) in Operations Manager may provoke an increase in reporting threads and choke points.
After the Alert Attachment Management Pack (Microsoft.SystemCenter.AlertAttachment.mpb) is imported, you create a dashboard that contains an alert widget. When you click an alert, the Operations Manager console may crash.
When a Windows PowerShell module uses the Monitoringhost.exe process on an x86-based client that is running Windows 8, more than 800 megabytes (MB) of memory may be consumed.
After an application domain is created, adding another application domain may be unsuccessful.
Operations Manager – UNIX and Linux Monitoring (Management Pack Update)
When multiple process monitors are used to target the same computer or group, processes may incorrectly monitor some template instances. Additionally, problems with the monitored processes may not be detected. This issue occurs when each process monitor uses the same name as the process even though different argument filters are used in each process monitor.
Note After the updated Microsoft.Unix.Process.Library.mpb file is imported, all existing Process Template instances must be edited and saved for the fixed behavior to take effect.
Service Provider Foundation (KB2785476)
The OperatingSystemId property on a virtual hard disk (VHD) object is always set to NULL.
Virtual machine usage metrics are not aggregated at hourly intervals and are missing basic usage metrics such as network sent and receive I/O operations per second (IOPS).
Virtual Machine Manager (KB2792925 – Console; KB2792926 – VMM Server)
When a logical unit number (LUN) is unmasked on an iSCSI array, the VMM service may crash.
When a node is put in maintenance mode, virtual machines in the cluster change to a status of "Unsupported Cluster Configuration."
When an add-in that uses multiple DLL files is imported into the VMM console, the add-in is not imported. Additionally, you receive the following error message:
Add-in cannot be installed
When an add-in is imported into the VMM console on a server that is running Windows Server 2008 R2, the add-in is not imported.
When an add-in is imported into the VMM console, the console may crash.
Instructions and download find here.
Orchestrator and Service Provider Foundation
If you want to know about the new feature in System Center 2012 SP1 named Service Provider Foundation there is a great article on Technet Wiki. The title of the article is Cloud Resource Management with System Center 2012 Service Pack 1 (SP1) – Orchestrator and Service Provider Foundation.