|
Installation and Deployment |
|
|
|
|
|
||
|
Installation and Deployment |
|
|
|
|
|
|
Installation and Deployment
|
Installation and Deployment |
|
|
|
|
|
||
|
Installation and Deployment |
|
|
|
|
|
|
CallData can be configured using several methods. Determining which method is right for you depends on several factors, such as available resources (financial & technical), number of Client Application users, level of technical expertise, and volume of phone activity within your organization.
There are three methods of deploying CallData: Localized, Partially Distributed and Fully Distributed. Explanations of each method are provided below.
Localized (1 server): CallData Service, SQL Server & Client Application all run on one computer.
With localized distribution the CallData service, SQL Server & the client application all run on the same computer.
Benefits
| ► | Most cost effective |
| ► | Simplest to administrate |
Drawbacks
| ► | Decreased performance in environments with high phone activity |
| ► | Requires users to have access to the server to access the client application |
Partially Distributed (2 servers): Any combination where two of the components run on the same server & the third component is run on another server. 
Example (CallData service & client application are ran on one server & the SQL Server is ran on another server.)
In this example, the CallData service and the client application are installed on the same computer and the SQL database is hosted on another computer.
The second server doesn't have to be the SQL Server. Partial distribution can be run with any configuration as long as two components are running on one server and the third component is running on a second server. It does not have to be like the diagram above, where server 1 runs the CallData Service & the Client Application and server 2 is the SQL Server.
Benefits
| ► | Better performance compared to localized configuration. |
Drawbacks
| ► | Requires two servers, which ultimately increases the cost compared to localized configuration. |
Fully Distributed (3 servers): CallData Service, SQL Server & Client Application each run on separate servers.
Using a fully distributed configuration provides the best performance, although it's costlier than a localized or partially distributed configuration.
With a fully distributed configuration, each component is ran on a separate computer.
Benefits
| ► | Maximum performance |
Drawbacks
| ► | Highest cost |
| ► | Increased degree of complexity |
See Also: