Ever wonder how you might be able to create a mobile app with data you already have in your FileMaker solution? I have, too! As it turns out, it’s not too outlandish of an idea thanks to the FileMaker Custom Web Publishing with XML API.
Applets now are required to contain additional information in their .jnlp files to document the files used, either external or local. But if you are working with older code, such as the FileMaker 11 Server Admin Console, the required manifest information is missing and your applet will halt with an exception like this:
java.lang.SecurityException: Missing required Permissions manifest attribute in main jar: http://localhost:16000/admin-client-lib/admin-console-client.jar at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) at com.sun.javaws.Launcher.run(Unknown Source) at java.lang.Thread.run(Thread.java:744)
FileMaker Server Advanced allows external systems to connect to its hosted database files via ODBC and JDBC. The remote systems can then run SQL commands against the hosted databases. Often the hard part is getting all the infrastructure ready for this. That includes the correct extended permissions on the FileMaker database file, needed drivers, firewall settings, etc.