Configuration¶

Connection Manager requires two types of configuration as shown below:

System Specific Configuration¶

The system-specific configuration provides the procedures for the OEM vendors to install CAPI and developers or operators to use Connection Manager. Each device vendor must install their own API SDK/Binary path, name, and version at the specified location in the registry/file system as per the respective operating system (OS) requirements.

Windows¶

You can update the parameters into the Windows registry under a common registry key as shown below:


HKEY_LOCAL_MACHINE\\Software\\WiMax\\CommonAPI\\Libs\\Manufacturer\\DeviceFamily
Path=Path
Extension=xyz
Version=2.0

Macintosh¶

You can update the parameters into the plist file. The wimax_drivers.plist file present in the /Library/Preferences/ directory as shown below:


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" 
"http://www.apple.com/DTDs/PropertyList 1.0.dtd">
<plist version="1.0">
<dict>
<key>Manufacturer</key>
<array>
 <string>Extension</string>
 <string>Path/</string>
 <string>Version</string>
 <string>Release Date</string> <!-- Optional -->
</array>
</dict>
</plist>

Linux¶

You can update the parameters into the wimax_drivers.txt file in the /usr/local/wimax/ directory as shown below:


<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
 <dict>
  <key>Manufacturer</key>
   <array>
    <string>Extension</string>
    <string>Path/</string>
    <string>Version</string>
    <string>Release Date</string> <!-- Optional -->
   </array>
 </dict>
</plist>

Manufacturer and Device Family values are controlled by each device manufacturer. Connection Manager will enumerate ALL entries from the registry/filesystem and load each SDK to check for supported devices of the manufacturer.

Go to Top

CM Configuration¶

The following are the sample codes to configure Connection Manager:


<ConnectionManagerConfiguration>
  <Properties class="com.xohm.daemon.Properties">
     <Attribute name="daemonPort" type="int" value="9824" />
  </Properties>
  <Properties class="com.xohm.upgrades.autoupdate.Properties">
    <Attribute name="updateServerUrl" type="String" 
            value="http://upgrades.xohm.com:7003/sus/services/UpdateService" />
    <Attribute name="downloadFolder" type="String" value="downloads" />
  </Properties>     
  <Properties class="com.xohm.wimax.Properties">
    <Attribute name="listenPort" type="int" value="9825" />
  </Properties>
  <Properties class="com.xohm.wimax.base.Properties">
    <Attribute name="debug" type="boolean" value="true" />
    <Attribute name="numberOfLogs" type="int" value="30" />
    </Properties>
  <Properties class="com.xohm.wimax.session.Properties">
    <Attribute name="networkScanRetryCount" type="int" value="10" />
    <Attribute name="logStatisticsEvery" type="int" value="30" />
    <Attribute name="checkConnectedEvery" type="int" value="1000" />
    <Attribute name="checkConnectedRetryCount" type="int" value="3" />
  </Properties>
  <Properties class="com.xohm.wifi.Properties">
    <Attribute name="listenPort" type="int" value="9826" />
  </Properties>
</ConnectionManagerConfiguration>

The following explains the attributes and their functions used in Connection Manager:

daemonPort – port on which the CM service listens.
updateServerUrl – name of the update server.
downloadFolder – where CM stores the downloaded software.
listenPort – port on which the WiMAX manager listens on.
wimaxDebug – debug file if the value is true.
numberOfLogs – number of days used for each log.
networkScanRetrycount – number of times CM retries to scan the network.
logStatisticsEvery – time interval after which CM should log connection status.
checkConnectedEvery – time interval that CM should check if connected to the network or not.
checkConnectedRetrycount – number of times CM retries to check if connected or not.
listenPort – port on which the WiFi manager listens.

Next Topics

CM Application API
Getting Started
Architecture

Also available in: HTML TXT