Theory Of Operation - Motorola CA50 Developer & User Manual

6 - 6 CA50/UCA Client & Server Developer & User Guide

Theory of Operation

The following lists the basic process the CA50 client executes at start up:
•
Registration (see
•
Authentication/login (see
•
Profile retrieval (see
•
Desktop launch (see
The following sequential steps are an overview of the events that occur when a CA50 powers on, runs the UCA
client application and a user logs in:
The client calls the DeviceRegistration Web Service method
1.
The server adds the device information to a table for identification and checks if the device is authenticated
2.
directly, or if the user must login. If the device is authenticated, the server immediately builds and sends the
XML profile to the client
process (step
The server sends back an XML command to browse to a Web page to begin the login process.
3.
The client posts back user input while proceeding through the login process.
4.
When the login process reaches the point where the server has enough information, it begins building the XML
5.
profile to send back to the client.
The server uses the user's role and primary group to determine which base profile to use to build the user
6.
profile. This relationship, tying the user's role and group to a specific base profile, is defined by creating a
profile association through the UCA server Web Console.
The base profiles are located in the following directory in the default installation:
7.
\Program Files\Motorola\UCA Server\Profiles. The profiles can be configured on the UCA Server Console >
System Settings > System.Profile.Path.
Once the base profile is chosen, the server begins modifying the base profile with data specific to the user that
8.
is logging in.
The server assigns a phone extension to the user based upon his or her primary group and writes it to the
9.
profile.
The server collects any user preferences specific to the user and writes it to the profile.
10.
The resulting profile, which was built from a base profile, is sent (returned) to the CA50 device.
11.
The client processes the XML profile and configures the CA50 device.
12.
When the configuration is complete, the client displays the desktop. At the desktop the user has several
13.
options. Among them are options to launch a business application, place a phone call, change walkie-talkie
channels, enter Do not disturb mode or set preferences.
Device Registration on page
Chapter 11, UCA Server Optional
Chapter 7, XML Profile for
CA50 Login - Post-deployment on page
(step 5). If the device is not authenticated, the server proceeds to the user login
3).
6-4)
APIs)
Configuration)
4-2).
(page 6-4) to let the server know that it is present.