To automate this process we enabled it as a cron job, checking the server every few minutes. $script = $fm->newPerformScriptCommand( $fmLayout, $scriptName) $fmx = exec("ps aux | grep 'mxdbc_listener'") #!/usr/bin/php -q SetProperty( 'username', FM_USER ) Using the PHP API, we triggered a FileMaker script in a monitoring/logging database, which sent the email via SMTP, a process we already used on other databases on that server and knew would work. Since the server resided inside a firewall, we switched to an internal FileMaker process instead.
Filemaker pro advanced java code#
When we moved the code to the server it failed to generate an email. This could then be written as a shell script, or in our case, a PHP command line script with the option to send an email. If the process went offline, the Terminal showed an empty process. Targeting one specific process required adding “grep”, such with this command: ps aux | grep 'mxdbc_listener' Using “ps” we could view different processes. The command line script was something that could be automated. While the Activity Monitor provided a good user interface to see all system processes, we needed to automate and script the scenario.
Filemaker pro advanced java mac os#
(Since the servers run on Mac OS X, this solution is not cross-platform.)Īctivity Monitor showed all FileMaker Server processes, when filtered by “fm”: We needed a method to monitor the fmxdbc_listener process. Unless someone happened to watch the process, hours or days could pass before anyone noticed this problem. But, in our non-perfect world, sometimes this process failed.Įven though the configuration setting remained checked in the Admin Console, the process simply stopped, and our database no longer would accept incoming connections from the Java app. This process worked seamlessly, as long as FileMaker’s “fmxdbc_listener” process remained active. This required Server Advanced, and enabling ODBC/JDBC in the server settings: The sending application used FileMaker’s client driver, which allowed it to send SQL insert statements to the FileMaker database via FileMaker Server. One of our development projects required enabling ODB/JDBC and sending data via JDBC (Java Database Connectivity). Sending data to FileMaker from external sources poses interesting options and challenges.