|
|
|
|
|
|
TeamHeadquarters is a collaborative web application, so:
The processing load is shared between the server, network, and client.
Other users and applications may be sharing the same resources.
The basic system requirements assume that TeamHeadquarters is not negatively affected by other applications competing for resources. This is an important factor when planning an implementation.
Hardware requirements are listed here.
TeamHeadquarters uses browser-side caching techniques to optimize network activity. As a result, stream sizes can vary from large (i.e. 500K) for initial log-in or larger reports, down to very small (i.e. 4k) for things like opening a small folder.
Sufficient network capacity is essential for web applications like TeamHeadquarters. Consider any routine consumers of network capacity, such as large file transfers, when planning your implementation.
Internet Explorer is used as the TeamHeadquarters client. Some client-side processing relies on the MSXML parser, for things like cached data management and column sorting. Therefore, performance is impacted by both processor and memory.
Multi-tasking on the client can cause performance issues, when too many applications are being used concurrently.
TeamHeadquarters runs as a web site, available to the users via Internet Information Services.
User authentication is handled by IIS and Active Directory.
Authentication options can vary between Basic Windows Authentication, Integrated Authentication, and Digest Authentication.
SSL certificates can be used to govern the privacy of your information as it is travelling over the network(s). The Entry On-Demand service is offered under an SSL certificate.
For On-Premises customers, it is important to ensure the physical security of the server. Your system and database backups should be physically and logically secured, as if they are the actual database.
