Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

The following example can be used as a template to configure settings for the PROXYconfiguration service provider. The PROXY object in this example defines a proxy connection from MSCorpNetPPP1 and MSWiFi1, both of which connect to the Work metanetwork. The example specifies "itgproxy" as the proxy server and specifies 80 as the port number. Because it has already been configured using the ACCESS configuration service provider, no URL mapping is required.

Code Example

Copy Code 
<atomic>
<CmdID>8000</CmdID>
  <add>
	<CmdID>8001</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/PROXYID</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MS-PROXY1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8002</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/NAME</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MS-PROXY1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8003</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/ADDR</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>itgproxy</Data>
	</Item>
  </add>
  <add>
	<CmdID>8004</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/ADDRTYPE</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>IPV4</Data>
	</Item>
  </add>
  <add>
	<CmdID>8005</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/PORTS/PORT0/Services/SERVICE0/ServiceName</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>HTTP</Data>
	</Item>
  </add>
  <add>
	<CmdID>8006</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/PORTS/PORT0/PortNbr</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>int</Format>
	</Meta>
	<Data>80</Data>
	</Item>
  </add>
  <add>
	<CmdID>8007</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/CONREFS/CONREF0/ConRef</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MSCorpNetPPP1</Data>
	</Item>
  </add>
	<CmdID>8008</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/PROXY/PROXY0/CONREFS/CONREF1/ConRef</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MSWiFi1</Data>
	</Item>
  </add>
</atomic>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the SyncBody node in an OMA DM provisioning file. For more information about the syntax of the provisioning file, see OMA DM Provisioning Files.

You must also configure the ACCESS Configuration Service Providerbefore using this example.

See Also