ACCESS Configuration Service Provider Example for OMA DM

4/8/2010

You can use the ACCESS object to capture the information represented by CM_Networks and CM_Mappings.

The following example can be used as a template to configure settings for the ACCESS Configuration Service Provider. It shows how to use the ACCESS object to provision a destination network based on URL domains. The ACCESS object in this example provisions Internet and Work connections, lists the domains that are reachable on these networks, as well as the connectivity objects and proxy or VPN connections that can be used to connect to these domains.

Code Example

<add>
  <CmdID>8000</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Internet/Domains/Domain0/DomainName</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>https://*.*</Data>
  </Item>
</add>
<add>
  <CmdID>8001</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Internet/ConRefs/Domain0/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>GSM-CSD1</Data>
  </Item>
</add>
<add>
  <CmdID>8002</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Internet/ConRefs/Domain1/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>GPRS1</Data>
  </Item>
</add>
<add>
  <CmdID>8003</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Internet/ConRefs/Domain2/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>MS-PROXY1</Data>
  </Item>
</add>
<add>
  <CmdID>8004</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/Domains/Domain0/DomainName</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>https://*</Data>
  </Item>
</add>
<add>
  <CmdID>8005</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/Domains/Domain1/DomainName</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>https://*.msd.com</Data>
  </Item>
</add>
<add>
  <CmdID>8006</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/ConRefs/ConRef0/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>MSCorpNetPPP1</Data>
  </Item>
</add>
<add>
  <CmdID>8007</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/ConRefs/ConRef1/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>MSWiFi1</Data>
  </Item>
</add>
<add>
  <CmdID>8008</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/ConRefs/ConRef2/ConRef</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>chr</Format>
    </Meta>
    <Data>MS-VPN1</Data>
  </Item>
</add>
<add>
  <CmdID>8009</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/ACCESS/Work/Ports/0/PortNbr</LocURI>
    </Target>
    <Meta>
      <Format xmlns='syncml:metinf'>int</Format>
    </Meta>
    <Data>123</Data>
  </Item>
</add>

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.

See Also

Reference

ACCESS Configuration Service Provider
CM_Mappings Configuration Service Provider
CM_Networks Configuration Service Provider