TMS Application Monitoring?

[phil.caiazzo]

I had an “odd” request from a customer that I can’t seem to find an answer:

Basically the customer has a TMS and is wondering if we can monitor the “application” of TMS…not necessarily the box / server that it resides on.

Is there a tool available (within Cisco or on the market) that allows users to monitor the actual TMS “application” that runs on that box? 

Thanks for any help / insight anyone can provide.

Phil

[daleritc]

No, there isn't per say a tool available from Cisco or on the market that allows an administrator to monitor the TMS application specifically on the server. However, TMS is web based server application based on MS technologies, i.e. .Net, IIS, Windows Services, SQL. Therefore, and in addition to monitoring the health of the server itself, you could use those same tools to monitor the TMS Windows Services themselves. And since the TMS application is dependent upon the TMS db, you can also utilize third party tools to monitor the TMS SQL db on the SQL Server.

[Marius Nedregaard]

Hi Phil,

Cisco offer several different types of tools that can do this within Cisco.

I would recommend you to read and obtain more information about "Prime Collaboration Assurance 9.5" - This tool offer detailed monitoring of all telepresence infrastructure, endpoints, routers, swithces firewalls - in other words most Cisco equipment.

Read more on this link: http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps12363/data_sheet_c78-728390.html

And on this link:

http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.5/assurance/guide/Cisco_Prime_Collaboration_Assurance_Guide_9_5.pdf

Ask your Cisco reseller for a trial.

//Marius

[daleritc]

@Marius: True, but Prime (PCA) isn't monitoring the TMS application itself. It can monitor the 'box' and it gives you a 'one' management feel since you can cross launch into the TMS UI via PCA. But again, Prime isn't monitoring the TMS application itelf.

Dale

[Wayne DeNardi]

If you have some sort of SNMP monitoring System (HP Openview, Tivoli, etc), you can monitor TMS with the tms.mib that comes with TMS (on the Installation CD, or can be found in the downloaded TMS zip file).

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

[daleritc]

@Wayne: That doesn't monitor the TMS application itself either. Using a third party SNMP tool as you mention, along with the tms.mib, only monitors the SNMP traps thrown to the application as outlined in the MIB file. Again, nothing to do with monitoring the TMS application itself

Dale

[Wayne DeNardi]

Thanks Dale,

Yes, I realise that... but it all depends on what Phil/Phil's customer means by "monitor" TMS.

Phil, are you able to let us know in any more detail what you/your customer would actually like to "monitor" in regards to the TMS application?  Is there anything they're specifically looking for that hasn't been mentioned in this thread already?

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

[thobonho]

Hi Phil,

TMS consists of 3 parts: a database, a front-end and a few services. All of these can be checked in one single line:

curl -k --ntlm --user username:password https://TMS_IP/tms/default.aspx?pageId=114

In return (if TMS is up of course), you'll get the htlm code of the TMS Server Maintenance page in which you can parse TMS services status. Wrap this up in a loop that sends a notification when something unexpected occurs, and you have your TMS monitoring application.

Happy coding!

Thomas

[daleritc]

Hi Thomas,

I think he’s actually looking for something more than the services though...although as both of us have somewhat said in this thread...TMS is just an SQL db, front end and some services.

And an example of a third party tool would be:

SolarWinds

ManageEngine

HP OpenView

There’s actually quite a few out there…this is just a few off the top of my head.

On the MS side, I haven’t checked out lately what kind of tools they have since some of the third party tools are much better IMO but I reckon SCOM (Systems Center Operation Manager) is MS’s answer to this. However, they also have lighter tools as well, e.g. performance monitoring tools and SQL Server monitoring tools.

At the end of the day though, if our ticketing service was able to throw an email or SMS to a TMS Admin…when and if any of his or her TMS services went down…then that would certainly help. Meaning we do open a ticket when a service goes down (TMSServiceDiagnostic Service does that) but you have to have your head in the UI so has to see it, i.e. seen in the TMS Tickets. And what if the TMSServiceDiagnostic Service dies?

This is just a couple reasons why I suggest third party tools