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

This example adds a logical (DefaultProxy2) and a physical (PROXY 1) proxy, and their settings, by using the WAP technique.

Code Example

Copy Code 
<characteristic type="PXLOGICAL">
  <parm name="PROXY-ID" value="www.adatum.com"/>
  <parm name="NAME" value="DefaultProxy2"/>
  <parm name="STARTPAGE" value="http://www.adatum.com"/>
  <parm name="DOMAIN" value=".adatum.com/"/>
  <parm name="DOMAIN" value=".contoso.com/"/>
  <parm name="TRUST"/>
  <characteristic type="PXPHYSICAL">
	 <parm name="PHYSICAL-PROXY-ID" value="PROXY 1"/>
	 <parm name="PXADDR" value="XXXXXXX"/>
	 <parm name="PXADDRTYPE" value="E164"/>
	 <parm name="TO-NAPID" value="NAP1"/>
	<characteristic type="PORT">
	 <parm name="PORTNBR" value="9201"/>
	</characteristic>
  </characteristic>
</characteristic>

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 OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

If you are using standard OMA Client Provisioning ("WAP Technique") format to add a WAP proxy then your provisioning XML document must be placed in a mxipcold_< package name>_< version>.provxml file (for example mxipcold_myprovfile_< version>.provxml).

When adding a physical proxy, you must add also the NAP whose NAPID is referred to by TO-NAPID in this same XML document.

See Also