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
Device Registration on page 6-4
)
•
Chapter 11, UCA Server Optional APIs
)
•
Profile retrieval (see
Chapter 7, XML Profile for Configuration
•
Desktop launch (see
CA50 Login - Post-deployment on page 4-2
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:
1.
The client calls the DeviceRegistration Web Service method (
) to let the server know that it is present.
2.
The server adds the device information to a table for identification and checks if the device is authenticated
directly, or if the user must login. If the device is authenticated, the server immediately builds and sends the
XML profile to the client (
step 5
). If the device is not authenticated, the server proceeds to the user login
process (
step 3
).
3.
The server sends back an XML command to browse to a Web page to begin the login process.
4.
The client posts back user input while proceeding through the login process.
5.
When the login process reaches the point where the server has enough information, it begins building the XML
profile to send back to the client.
6.
The server uses the user's role and primary group to determine which base profile to use to build the user
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.
7.
The base profiles are located in the following directory in the default installation:
\Program Files\Motorola\UCA Server\Profiles. The profiles can be configured on the UCA Server Console >
System Settings > System.Profile.Path.
8.
Once the base profile is chosen, the server begins modifying the base profile with data specific to the user that
is logging in.
9.
The server assigns a phone extension to the user based upon his or her primary group and writes it to the
profile.
10.
The server collects any user preferences specific to the user and writes it to the profile.
11.
The resulting profile, which was built from a base profile, is sent (returned) to the CA50 device.
12.
The client processes the XML profile and configures the CA50 device.
13.
When the configuration is complete, the client displays the desktop. At the desktop the user has several
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.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......