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
. Once a UCA server IP address is loaded, the CA Menu automatically launches the
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
Development and Deployment Checklist on page 2-1
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.
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: ......