Integration - Connect

Monitor Connect framework by checking that Connect service is available and the error log is clean and no messages are stuck retrying.

Multiple Instances: Yes (per Connect server)

Interval: Every 5 minutes (288 times per day)

Status

Expression

Critical

If (Web services (SOAP Gateway) response != HTTP 200) or (Connect Alert log file size != 0kb) or (Application messages with unresponding routing address > 0)

Impact	The Connect server is not started.
Suggestion	Look for more information in the Connect server alert log file. Contact IFS Consultant or IFS Partner for further investigation.

If not status Critical.

Unknown

Missing application response.

Metric & Service	Command line example
Web services (SOAP Gateway)	java -jar application-monitoring-metrics-cli.jar http -url=http(s)://<server>:<managed_server_port>/fndext/soapgateway?test=true -match=response -oeq=200 -dc
Connect Alert log file size	java -jar application-monitoring-metrics-cli.jar file -file="<ifs_home>mws/instance/<instance_name>/logs/connectserver/ifsalert.0.log" -match=filesize -ca=0 -do
Application messages with unresponding routing address	java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -request=APPL_MESSAGES_WITH_RETRIES -ca=0 -do