Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Internet Information Services Web Server and Applications
Microsoft Internet Information Services (IIS) is used as the primary web server for hosting web content, web services,
and web applications that make up the user and external service interfaces of Cisco TMS.
and web applications that make up the user and external service interfaces of Cisco TMS.
TMS sites are configured to run under a specific Application Pool to isolate them from other activity that may be
hosted on the IIS Server.
hosted on the IIS Server.
Cisco TMS is developed using the Microsoft .NET platform. Some additional IIS components are therefore required for
Cisco TMS to work properly. These components are installed by Windows during the Cisco TMS installation.
Cisco TMS to work properly. These components are installed by Windows during the Cisco TMS installation.
All web-related files are stored on the server in the location specified during the installation. Installation creates the
virtual directories described below.
virtual directories described below.
tms
This is the authenticated web application where all user facing web content is hosted. http://<server>/tms is the
landing page for user interaction with Cisco TMS.
landing page for user interaction with Cisco TMS.
Authentication is required for all access to this application, and users authenticate through IIS. By default, both
Windows Authentication and Basic Authentication are enabled.
Windows Authentication and Basic Authentication are enabled.
tms/public
The tms/public component is a web application and directory structure for all content and services that must be
accessible to systems without authentication. Examples of such content are call feedback and phone books.
accessible to systems without authentication. Examples of such content are call feedback and phone books.
Anonymous Authentication must be enabled for this component. All other authentication modes must be disabled.
external
External is the web application and directory structure for all content and services that use authentication at the web
server level. It is primarily used for external facing APIs for server integrations.
server level. It is primarily used for external facing APIs for server integrations.
cdm and pwx
Some managed system types have hardcoded URLs for where they can post information or query for services. Web
applications are therefore set up at specific paths in the root level of the website to match these hardcoded URLs.
applications are therefore set up at specific paths in the root level of the website to match these hardcoded URLs.
■
/cdm is where CTS/TX systems post their feedback and status updates.
■
/pwx is where Polycom devices post their feedback and status updates.
tmsagent
The tmsagent web application serves as a proxy to handle requests intended for the Cisco TelePresence
Management Suite Provisioning Extension.
Management Suite Provisioning Extension.
The tmsng SQL Database
All operational and system configuration data is stored in the SQL database, by default named tmsng. Software files
for system upgrades and log files for the services are stored outside of this database.
for system upgrades and log files for the services are stored outside of this database.
The database runs on a Microsoft SQL Server. The SQL server can be on the same server as or remote from Cisco
TMS, and all references to find the database server are via registry keys defined during setup on the server platform.
TMS, and all references to find the database server are via registry keys defined during setup on the server platform.
Users never directly authenticate or interact with the database. All interaction with the database is executed within
the context of the application.
the context of the application.
19
Cisco TelePresence Management Suite Administrator Guide
Cisco TMS Overview