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 NAP Configuration Service Provider. It shows how to use the NAP object to provision two connections, a RAS connection and a GPRS connection. The RAS connection is provisioned using the NAP0 node.

Code Example

Copy Code 
<atomic>
<CmdID>8000</CmdID>
  <add>
	<CmdID>8001</CmdID>
	<Item>
	<Target>
		<LocURI>./Vendor/MSFT/NAP/NAP0/NAPID</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MSCorpNetPPP1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8002</CmdID>
	<Item>
	<Target>
		<LocURI>./Vendor/MSFT/NAP/NAP0/NAME</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>MSCorpNetPPP1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8003</CmdID>
	<Item>
	<Target>
		<LocURI>./Vendor/MSFT/NAP/NAP0/ADDR</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>+14255551212</Data>
	</Item>
  </add>
  <add>
	<CmdID>8004</CmdID>
	<Item>
	 <Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP0/ADDRTYPE</LocURI>
	 </Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>E164</Data>
	</Item>
  </add>
  <add>
	<CmdID>8005</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP0/AUTHINFO/AUTHTYPE</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>PAP</Data>
	</Item>
  </add>
  <add>
	<CmdID>8006</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP0/AUTHINFO/AUTHNAME</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>mydomain\myuser</Data>
	</Item>
  </add>
  <add>
	<CmdID>8007</CmdID>
	<Item>
	 <Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP0/AUTHINFO/AUTHSECRET</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>mysecret</Data>
	</Item>
  </add>
  <add>
	<CmdID>8008</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP0/BEARER/BEARERTYPE</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>CSD</Data>
	</Item>
  </add>
</atomic>
<atomic>
<CmdID>8009</CmdID>
  <add>
	<CmdID>8010</CmdID>
	<Item>
		<Target>
		<LocURI>./Vendor/NAP/NAP1/NAPID</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>GPRS1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8011</CmdID>
	<Item>
	<Target>
		<LocURI>./Vendor/MSFT/NAP/NAP1/NAME</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>GPRS1</Data>
	</Item>
  </add>
  <add>
	<CmdID>8012</CmdID>
	<Item>
	<Target>
		<LocURI>./Vendor/MSFT/NAP/NAP1/ADDR</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>
operator-specific URL</Data>
	</Item>
  </add>
  <add>
  <CmdID>8013</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP1/ADDRTYPE</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>APN</Data>
	</Item>
  </add>
  <add>
	<CmdID>8014</CmdID>
	<Item>
	<Target>
	 
<LocURI>./Vendor/MSFT/NAP/NAP1/BEARER/BEARERTYPE</LocURI>
	</Target>
	<Meta>
		<Format xmlns='syncml:metinf'>chr</Format>
	</Meta>
	<Data>GPRS</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