Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Microsoft project code named "Velocity" offers many options for specifying and storing the configuration details that are used by the cache cluster and the client application. This section of the document set describes the configuration options available and considerations for selecting them.
As seen in the following diagram, cache-based applications have the option of specifying configuration information programmatically or by using an application configuration file. There are three options available for storing cluster configuration settings: in XML, in a SQL Server Compact data file, or in a SQL Server 2005 or later database. You can choose the option that best meets the needs of your application and infrastructure.
.gif)
In This Section
The following topics provide more information about the options.
| Topic | Description |
|---|---|
Describes important considerations for choosing configuration storage options in the cache client and cluster. |
|
Describes how to use an XML-based client configuration file. Also provides an overview of the required XML configuration elements in the application configuration file. |
|
Provides an overview to programmatic cache client configuration. |
|
Describes what files are involved when you select this option. Also provides an overview of the XML configuration elements in the ClusterConfig.xml. |
|
Describes how a SQL Server Compact data file is used to store cluster configuration. |
|
Describes what is involved when you select SQL Server to manage cluster configuration details. |
See Also
Other Resources
Configuration Settings (Velocity)
Configuring the Cache Client with XML (Velocity)
Administration Guide (Velocity)
Programming Guide (Velocity)