How can I discover / monitor a FilemakerPro server (port 5003) ?

2 messages Options
Embed this post
Permalink
Mark Dammer

How can I discover / monitor a FilemakerPro server (port 5003) ?

Reply Threaded More More options
Print post
Permalink
I am looking for a way to check the health of our FilemakerPro servers. They run on port 5003 TCP/UDP. Has anyone configured capsd / poller to work with FilemakerPro servers ?
thanks for any help,
Mark


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Ronny Trommer

Re: How can I discover / monitor a FilemakerPro server (port 5003) ?

Reply Threaded More More options
Print post
Permalink
Hi Mark,

you have several possibilities to monitor you application. For the  
5003 TCP port you can use a simple TCP-Monitor to check if a TCP  
session is possible or not. For UDP it is a little bit more trickier,  
because you have to implement the FilemakerPro application logic in  
your UDP monitor to check if the application works. If you running on  
Unix and you have Net-SNMP available there are a lot of nice things to  
monitor an application with "proc" or "extend" the Net-SNMP agent with  
your customized shell scripts to check if the application is still  
working. To detect a service TCP port you have to add the following to  
your capsd-configuration.xml:

     <protocol-plugin protocol="FileMaker-5003" class-
name="org.opennms.netmgt.capsd.plugins.TcpPlugin" scan="on">
         <property key="banner" value="*" />
         <property key="port" value="5003" />
         <property key="timeout" value="3000" />
         <property key="retry" value="1" />
     </protocol-plugin>

The next step is create a monitor in your poller-configuration.xml

     <service name="FileMaker-5003" interval="300000" user-
defined="false" status="on">
       <parameter key="retry" value="1" />
       <parameter key="timeout" value="3000" />
       <parameter key="port" value="5003" />
       <parameter key="banner" value="*" />
     </service>

     <monitor service="FileMaker-5003" class-
name="org.opennms.netmgt.poller.monitors.TcpMonitor" />


--
Ronny Trommer (Germany)
Web: http://www.open-factory.org
IRC: irc.freenode.org - #opennms

PGP key: 7ED9 1A00 0BD9 EB84 9F63  5808 B1BC E829 E383 98A0
Keyserver: keyserver.pgp.com

On Nov 4, 2009, at 11:09 AM, Mark Dammer wrote:

> I am looking for a way to check the health of our FilemakerPro  
> servers. They run on port 5003 TCP/UDP. Has anyone configured  
> capsd / poller to work with FilemakerPro servers ?


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss