Modifying a Configuration File
If you use configuration files to store provider/listener configurations, rather than storing them in the database, the Web.config file of the Web service is updated, as described below.
For each Web service (provider), a config section in the Microsoft.Ccf section group has been defined. The name of the section is the namespace prefix type name of the provider, without the Microsoft.Ccf prefix, as shown in the following example.
<configSections>
<sectionGroup name="Microsoft.Ccf">
<section name="Csr.WebServices.Providers.CcfInfrastructure.Application"
type="Microsoft.Ccf.Common.Providers.Configuration.ProviderConfigurationHandler, Microsoft.Ccf.Common.Providers" />
</sectionGroup>
</configSections>
In this section, provider definitions are created. Converted appSettings are keyed to provider attributes, as necessary. Refer to the following example.
<Microsoft.Ccf>
<Csr.WebServices.Providers.CcfInfrastructure.Application defaultProvider="AzManApplicationProvider">
<providers>
<add name = "SqlApplicationProvider"
type = "Microsoft.Ccf.Csr.WebServices.Providers.CcfInfrastructure.SqlApplicationProvider, Microsoft.Ccf.Csr.WebServices.Providers"
connectionString = "Server=CCFSQL;Integrated Security=true;Database=CcfInfrastructure;Pooling=false"
/>
<add name = "AzManApplicationProvider"
type = "Microsoft.Ccf.Csr.WebServices.Providers.CcfInfrastructure.AzManApplicationProvider, Microsoft.Ccf.Csr.WebServices.Providers"
connectionString = "Server=CCFSQL;Integrated Security=true;Database=CcfInfrastructure;Pooling=false"
azManStore = "msxml://C:\CCF\DemoData\AzManCCF.xml"
/>
</providers>
</Csr.WebServices.Providers.CcfInfrastructure.Application>
</Microsoft.Ccf>
Show: