Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
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.
services. Web applications are therefore set up at specific paths in the root level of the website to match
these hardcoded URLs.
n
/cdm is for systems supporting the Cisco OneButtonToPush calendar service.
n
/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.
Software files for system upgrades and log files for the services are stored outside of this database.
The database runs on a Microsoft SQL Server 2008 or 2005. 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.
remote from Cisco 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.
within the context of the application.
Note that if Cisco TelePresence Management Suite Provisioning Extension is used, this extension stores its
information in a separate database.
information in a separate database.
Credentials and permissions
During the installation of Cisco TMS, the sa account on the SQL server is automatically chosen to create and
access the database, but by choosing a custom installation different credentials may be used. Note that the
account used to run and upgrade Cisco TMS must have db_owner permissions to the tmsng database, while
a user that also has access to master.mdf is required for creating the tmsng database the first time.
access the database, but by choosing a custom installation different credentials may be used. Note that the
account used to run and upgrade Cisco TMS must have db_owner permissions to the tmsng database, while
a user that also has access to master.mdf is required for creating the tmsng database the first time.
Windows services
Cisco TMS relies on a set of Windows services to run at all times on the server or servers. The function of
each of these services is described below.
each of these services is described below.
TMSLiveService
This backend service:
n
Starts and stops scheduled conferences.
n
Monitors ongoing conferences and the updated status of those conferences.
n
Executes commands against ongoing conferences.
LiveService acts as the backend for conference monitoring while the client-side applet, Conference Control
Center, acts as the front-end for interacting with ongoing calls.
Center, acts as the front-end for interacting with ongoing calls.
Cisco TMS Administrator Guide (14.3.2)
Page 17 of 342
Cisco TMS overview
Cisco TMS components