Storing Your Service Information Data
This content and the technology described is outdated and is no longer being maintained. For more information, see Transient Fault Handling.
Your service information data consists of two parts: a description of your Microsoft Azure environment including subscriptions, hosted services, roles, and storages accounts, and a description of the scale groups you have defined.
You can configure the Autoscaling Application Block to use one of the two XML-based service information store implementations included with the block: the BlobXmlFileServiceInformationStore class or the LocalXmlFileServiceInformationStore class. You can also use your own custom rules store by implementing the IServiceInformationStore interface.
Both of the provided XML-based rules store implementations expect the rules to conform to the XML schema defined in the http://schemas.microsoft.com/practices/2011/entlib/autoscaling/serviceModel namespace. If you have installed the Autoscaling Application Block in your Visual Studio project by using NuGet, you can find the AutoscalingServiceModel.xsd schema file in the root folder of the project.
Many XML editors allow you to use an XML schema file to provide validation and other support when you edit a document that is bound to the schema.
If you are using the BlobXmlFileServiceInformationStore class, you should save the XML document with your rules to the Azure blob that you specified in your configuration settings. If you are using the LocalXmlFileServiceInformationStore class, you should save the XML document with your rules as the local file that you specified in your configuration settings.
There are a number of tools available to help you upload files to Azure blob storage. For a list of such tools, see the Deployment/Storage tab on the Azure Tools page.
Other than the XML schema, the Autoscaling Application Block does not provide any support for editing rules or saving rules to a rules store. For an example of one approach to providing a UI for editing and saving service information data, see the section "Editing and Saving Service Information Data" in Chapter 5, "Making Tailspin Surveys More Elastic" of the Developer's Guide.
The content of the store should always be encoded using UTF-8 (with or without the byte order mark (BOM)).
Last built: June 7, 2012