Symbian OS Communications (779884), страница 78
Текст из файла (страница 78)
The DM framework willcall CommitAtomicL() to signify the successful end of the transaction,all commands within the transaction should be persisted before thismethod completes. The DM framework will call RollbackAtomicL()386OMA DEVICE MANAGEMENTto signal the end of the transaction and to request that the DM adapter rollsback all commands handled within the transaction.
The DM adapter must,within RollbackAtomicL(), return a new status for each successfullyhandled command indicating if the command was rolled back or not.There is one unique interface method that is used by the DM frameworkto signal to the DM adapter that there are no more commands within thetransaction, or within the current DM session:void CompleteOutstandingCmdsL()When this method is called, the DM adapter must handle any remaining commands that it has been sent. This is specific to commands that aredeferred for later handling, this typically occurs when the DM adapteris not able to action the DM command without information provided inother DM commands. It is not recommended that DM commands aredeferred by DM adapters unless it is necessary – in the case of most DMadapters deferring commands will not be necessary.The handling of DM commands on the ConRef link node is a specialcase and is worth considering separately. The implementation presentedhere assumes that the access points are stored under the URI ‘./NAP’in the management tree, and that the LUID for each of the unnamednodes is the ID in the CommsDat database for the access point.
It ishighly recommended that any DM adapter that utilizes a ConRef linkstyle node verifies this assumption to prove the solution will work onall the targeted devices. Translating from the passed ConRef value to anaccess point ID is achieved by using the passed value as the URI for a callto GetLuidAllocL(): the returned LUID is stored as the account data.If the passed value is the keyword INTERNET, then the account data is setto zero.
Translating from the access table number to the management treeURI requires a lookup of all the children to the ‘./NAP’ node and findingthe one that has an LUID that matches the value stored in the accountdata. A call to the following method will provide an array of child nodenames and their LUIDs for the passed URI:void GetMappingInfoListL(const TDesC8& aURI, CArrayFix<TSmlDmMappingInfo>&aSegmentList)A search through the array will determine if the stored value hasan access point in the management tree.
The child node name in theTSmlDmMappingInfo object does not include the full URI, and so thenode name must be prepended by the rest of the URI prior to the resultbeing returned. If the account data is zero, then the keyword INTERNETis returned.Most DM adapters that only manage settings, such as our exampleXMPP DM adapter, do not need to support the full set of DM Commands.SUMMARY387Therefore, the Copy and Execute interfaces are not supported to reducethe complexity of the DM adapter, and the data for the XMPP settings istoo small to need the support of the streaming interfaces. However, theseinterface methods must be implemented by the DM adapter regardless ofwhether they are supported.
A suitable error message should be used toshow that the command failed.As is always the case, the DM adapter will require testing. Unit testswill prove that the DM adapter code is sound, does not leak memory andthat all the code can be reached, but does not prove that the DM adaptercan be used by a DM server to access the settings data. There are threeways to test with a DM server: the first is to use the SyncML ConformanceTest Suite (SCTS) provided by the OMA (available as open source fromsourceforge.net ), search for freely available DM servers, or one of thecommercially available DM servers.12.4.2 OMA-specified Management ObjectsThe OMA has started to standardize management objects to allow forgreater compatibility between devices. The DevInfo, DevDetail andDevice Management Account management objects are specified as partof the OMA DM specification, but work has begun on a number of othermanagement objects, including connectivity MOs, a software componentMO and a firmware update MO.
A complete list and information on theseMOs can be found on the OMA website.12.5 SummaryIn this chapter we have learnt how about:• the basic principles behind device management• how to describe our manageable settings in terms of DFProperties,and the attributes of those settings• how to implement a DM adapter to manage settings for our application.Section IVDevelopment Tips13Setting Up for DevelopmentIn this chapter we describe a number of ways of attaching hardware to theemulator to enable developers to use the technologies listed in Section IIof this book. We will describe methods for attaching Bluetooth hardware,IrDA hardware or telephony hardware to the emulator, and a number ofways of connecting the emulator to an IP network.Table 13.1 shows the technologies from Section III, and which of thebearer technologies below you can use for testing.
Obviously in somecases you’ll need extra infrastructure for testing, for example OMA DMneeds a device management server. To prevent this chapter becomingunmanageably long, and to keep the focus on Symbian OS, we won’tcover setting up servers for testing here – there’s plenty of informationalready on the Internet about that topic.Important note applying to all sections: when configuring serial portson the emulator, note that Windows and Symbian OS use differentnumbering schemes – COM1 on Windows is COMM::0 on SymbianOS, COM2 is COMM::1, etc.13.1 BluetoothThere are three main ways of connecting Bluetooth hardware to theSymbian emulator – one uses USB and the other two use a serial port.At this point we should mention that when using a serial port, thereare two protocols that can be used to communicate between SymbianOS and the Bluetooth hardware – called BCSP and H4.
The hardwarewill support one or the other, so you need to know which protocol issupported to be able to configure it.392SETTING UP FOR DEVELOPMENTTable 13.1 Technologies from Part 3TechnologyBearer technologyMessagingTo use POP3, IMAP4 and SMTP, follow the steps inthe ‘Network connections for IP’ section.Follow the steps in the ‘Telephony’ section to allowreception of SMS messages.To test reception of SMS and MMS messages on theS60 emulator, you can also use the functionalitycontained in Tools->Utilities->Events->Messagingevents to insert fake SMS and MMS messagesdirectly into the messaging store.SendAsTo use SendAs over Bluetooth, follow the steps inthe ‘Bluetooth’ section.To use SendAs over infrared, follow the steps in the‘IrDA’ section.To use SendAs over SMS, follow the steps in the‘Telephony’ section.To use SendAs over MMS, follow the ‘Using a seriallink to a mobile phone’ method in the ‘Networkconnections for IP’ section.To test the SendAs ‘to flickr’ service, follow the stepsin the ‘Network connections for IP’ section.OBEXTo use OBEX over Bluetooth, follow the steps in the‘Bluetooth’ section.To use OBEX over infrared, follow the steps in the‘IrDA’ section.HTTPFollow the steps in the ‘Network connections for IP’section.OMA DeviceManagementFollow the steps in the ‘Network connections for IP’section.13.1.1 Setting up the Easy Way – Using the SDK ConfigurationDialogsIn the S60 3rd edition emulator, go to the ‘Tools’ menu and choose‘Preferences’, then select the ‘PAN’ tab, enable Bluetooth and choose theappropriate HCI type and port number.BLUETOOTH393For the UIQ3.0 SDK, launch the SDKConfig app, go to the ‘Communications’ tab and select the appropriate COM port.
If you need to changethe HCI in use, you’ll need to edit the configuration file manually.13.1.2 Setting up the Manual Way – Editing the Configuration FileUsing Bluetooth hardware with a serial connectionThere are two options for connecting Bluetooth hardware using a serialport – one uses a traditional RS-232 port, the other uses Bluetooth hardware packaged as a compact flash (CF) or PC card.The first option is to use the same hardware as the Symbian Bluetooth team use for testing and development: Casira pods from CambridgeSilicon Radio (CSR).
The Casira pods have a replaceable CSR BlueCoremodule inside, and both serial and USB interfaces on the back. Sinceconnecting hardware to the emulator via USB is far more difficultthan using a simple serial port, the supported option is the serialport.The second option is far better if you travel a lot and need a portablesolution.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
