Motorola CA50 Developer & User Manual page 108

5 - 2 CA50/UCA Client & Server Developer & User Guide
The static menus can also refer to dynamic menus that are downloaded from the UCA server on demand via Web
service calls.
The UCA client application is designed to get almost all of its information from the UCA server. An exception to this
rule is staging information required at the site deployment such as Store Number, UCA server IP address and
Language. This staging information is loaded into the CA50 by scanning MSP generated Rapid Deployment bar
codes. The UCA client application uses these values to connect the CA50 to the UCA server and go through the
logon process. When the user is logged in, the server sends the client profile data containing the user's device
configuration, any personal settings and the menus that user can access. Some menus are not downloaded at
login time but are only available by making Web service calls. These are especially important for dynamic data,
such as phone lists, since those lists contain only extensions that are currently logged in.
NOTE The UCA client application cannot be launched from the CA50 CA Menu until a valid UCA server address
is loaded into the device. For details about how to load this information onto a CA50, see
Rapid
UCA client after a reboot.
NOTE 1. For a complete checklist outlining all the development and deployment activities required to implement
a CA50 solution, see the
2. For a table listing the most commonly requested topics within this manual, see the Quick Startup Guide
on the last page of the manual.
Deployment. Once a UCA server IP address is loaded, the CA Menu automatically launches the
Development and Deployment Checklist on page
Appendix F,
2-1.