Menu, toolbar and Icons of SCTS DM
1.1 Menu
1.1.1 Configuration
The Configuration menu can be used to save the changes in the devices, to clear the session pane and to remove all the configured devices.
1.1.2 Settings
The Settings menu can be used to start stop or configure transport servers. It can also be used to view the state of various transport servers. The Settings menu can be used to set the logs path. By default, the logs are saved in the path where SCTS DM is installed. The settings menu is also used to select the type of OBEX service the client has to use to connect to the obex server.
1.1.3 Tools
Currently available tool in the Tools menu is the ‘Credentials calculator’ and WBXML – XML converter.
1.1.4 Help
The Help menu has the guides which help in configuring the tool as a normal client/server or a test client/server. The Help menu can be used to report a bug to the SCTS team, which will prompt the user as to what are the necessary information that has to be sent to the SCTS team.
1.2 Toolbar
The various toolbar items are context sensitive. For example the ‘ + Add Device’ will add a ‘Client Device’ if the focus is on the ‘Client Devices’ object or will Add a ‘Server Device’ if the focus is on the ‘Server Devices’ object.
1.3 Icons
SCTS DM has different icons to represent the various internal objects. The icons corresponding to the different internal objects are shown below.
Device Management tree
DM Accounts
Connection objects
Commands
Server Device:
Client Device:
Session with Errors:
Session without Errors:
Test passed
Test failed
Not Tested
Optional Test
Not supported
Posted in: Mobile-OMA| Tags: OMA SCOMO DM Menu Toolbar Icon SCTS ServerFunctional Components and Interfaces in SCOMO
1 SCOMO Server
The SCOMO Server is a logical entity which is dedicated to issue SCOMO Operations to the device or consume the SCOMO Alerts from the device.
2 SCOMO Client
The SCOMO Client is responsible for executing SCOMO Operations. It consumes the Software Component delivered to the device and is expected to relay SCOMO Alerts conveying a success or failure result back to the SCOMO Server .
3 The Device Management Client
The DM Client component makes it possible to initiate software component management in the device from a DM server. The DM Enabler provides support for device discovery and parameter setup by the DM Client component. The SCOMO enabler provides a management object for software components that the DM Client component provides access to, such that the DM server can manipulate it. The DM client interacts with a Software Component Agent in the device that is responsible for conducting the management activities using a delivered software component management object. The DM client employs the Generic Alert [DMPRO] mechanism to communicate the final notification comprising the status of the management activity. ScoMo does not define or specify the Device Management Client
4 Alternate Download Client
The alternate download client is an optional feature that may exist on the device and used for downloading software components to the device when the DMPRO is not being used for such downloads. The alternate download client may support DLOTA or something else. SCOMO does not define or specify the alternate download client
5 The Device Management Server
The SCOMO architecture requires the DM server component to support device discovery, determination of an appropriate software component and delivery of a software component management object to the device over Large Object downloads if the device can support that. It also facilitates receipt of a final notification from the device employing the Generic Alert mechanism. SCOMO does not define or specify the Device Management Server.
6 The Alternate Download Server
The Alternate Download Server is an optional feature of the device management system that makes it possible to download software management objects using the alternate download mechanism, such as DLOTA. The Download Server is not defined or specified within the scope of SCOMO
7 External Management Infrastructure
The Device Management System comprises of a set of external management components over and above the device management server that participate in the overall process of managing devices. The external management infrastructure is used but not defined or specified within the scope of the SCOMO.
Definitions of OMA-SCOMO
| Interface | See [OMA-DICT]. |
| Content Provider | An entity that provides data which forms the basis of a service. |
| Device | See [OMA-DICT] |
| Device Management | Management of the Device configuration and other managed objects of Devices from the point of view of the various Management Authorities. Device Management includes: - Setting initial configuration information in Devices - Subsequent updates of persistent information in Devices - Retrieval of management information from Devices - Processing events and alarms generated by Devices |
| Device Management System | A background system capable to interact with a (set of) Device(s) for the purpose of Device Management. |
| Enterprise | A business with deployment and Management Authority for WLAN Bearers, Local Wired Bearers, computers, Devices, software, and employees. |
| Enterprise Device Management Server | Part of the Device Management System that is under administration of an Enterprise Management Authority. |
| Management Authority | An entity that has the right to perform a specific Device Management function on a Device or manipulate a given data element or parameter. For example, the Network Operator, handset manufacturer, enterprise, or Device owner may be the authority or share authority for managing the Device. One Management Authority may own all Device resources or may share or delegate all or parts of these with/to other Management Authorities |
| Management Object | A data model for information which is a logical part of the interfaces exposed by DM components |
| Software Component Management Object | A management tree object defined for software components which will be used for delivering and managing software components within client device. |
| Software Component Activation | The process which results in services or resources a software component embodies to be made accessible to other entities (including the end-user). |
| Software Component Deactivation | The process which results in services or resources a software component embodies to be made inaccessible to other entities (including the end-user). . |
| Service Provider | An entity that provides and administers a service to a Subscriber and/or User. The Network Operator is often a Service Provider. |
| Software Originator | The entity that creates, directly or through a third party, software and/or data targeted for use in a Device, Platform or Base Station. In the event that the software and/or data is controlled by a Regulatory Agency, the Software Originator is responsible for obtaining any Regulatory Agency license and Label. |
| Subscriber | The individual or organisation that is paying for service. |
| User | The individual who is in possession of and operates the Device. |
| SCOMO Alert | SCOMO specific alerts which convey the result of SCOMO Operations via DM Generic Alert mechanism [DMPRO]. |
| SCOMO Operations | Download, Install, Update, Remove, Activate and Deactivate operations which may be invoked on a Software Component MO as well as inventory queries. |