By Richard Carlton
You are invited to a livestream webinar ... to learn about speeding up FileMaker performance.
You are invited to help us test these performance improvements in front of a live audience.
Test File: FileMaker CRM
File Size: 15 GB
Total Record Count: 10.3 million
We tried this 3 years ago...and FileMaker Cloud survived 108 active users. How about we go for 200? We need your help! During the live event... we will ask that you login to the CRM. We want to have as many people logged on as possible.
Can FileMaker Cloud survive? We are using the largest AWS Virtual Server allowed by Law.
February 22nd, 2019 - 1:00pm PST
[FOR IMMEDIATE RELEASE]
24U releases 24U Toolbox Plug-In 3.0 for FileMaker 17
The popular toolbox of external functions for FileMaker® 17 now can convert rich-text to HTML with CSS
Prague, CZ — October 30, 2018 — 24U Software has released version 3.0 of 24U Toolbox Plug-In, and update of their popular toolbox of useful external function for daily use in FileMaker Pro 13 thru 17
The new version adds convert rich-text to HTML with CSS, support for Native iOS FM Go apps and Support for FileMaker Cloud.
24U Toolbox Plug-In 3 can convert rich-text to HTML with CSS, producing much cleared and customizable results than GetAsCSS. By producing clean dynamic HTML content the websites will render faster and rank higher in search engines.
What's new in this version:
- Get rich text as HTML to generate crystal clean HTML and CSS
- Support for Native iOS FM Go apps
- Support for FileMaker Cloud
About 24U Toolbox Plug-In:
24U Toolbox Plug-In is a robust FileMaker Pro plug-in which allows your FileMaker Pro databases to:
- Execute FileMaker or System shell scripts to automate tasks inside/outside of FileMaker Pro
- Execute SQL commands to develop faster and keep your solution clean
- Match & replace regular expressions to find & replace text fast using patterns
- Merge data values into text while maintaining styling to apply templates quickly and easily
- Lookup DNS name for IP & vice versa to find out who is connecting from where
- Get current public IP to know more about clients and discover potential security attacks
- Define global keyboard shortcuts to avoid unnecessarily excessive use of script triggers
- Obtain precise microsecond timestamps to measure nearly unmeasurable chunks of time
- Get the type of a FileMaker variable to let your scripts make the right decisions
- Share variables between databases to avoid creating too many external data sources
Mac: Any Intel Mac, 4 GB RAM, Mac OS X 10.10 Yosemite, FileMaker Pro 16 Advanced or newer.
Windows: 1.6 GHz processor, 4 GB RAM, Windows 8.1 or newer, FileMaker Pro 16 Advanced or newer.
FileMaker Cloud: EC2 Instance type: t2.medium, FileMaker Cloud 17 or newer.
Mac: Any Intel Mac since 2008, 2048 MB RAM, Mac OS X 10.10 Yosemite, FileMaker Pro 13.
Windows: 1 GHz processor, 2048 MB RAM, Windows 7, FileMaker Pro 13.
FileMaker Cloud: EC2 Instance type: t2.small, FileMaker Cloud 16.
Availability and Pricing of 24U Toolbox Plug-In 3.0
24U Toolbox Plug-In 3.0 is immediately available for download free of charge as a fully functional 14-days trial version, which can be activated after purchasing a license.
Licenses for 24U SimpleHasp Plug-In start at US$49 per user, $499 per server. Volume discounts are available for 5 or more users.
Existing customers can upgrade to the new version at 30 % off the regular prices. Until 13 November 2018 customers can upgrade at 50 % off the regular prices!
More information: https://www.24usoftware.com/Toolbox/
About 24U Software
With a team of full-time testers, web, plug-in, Mac, Windows, Linux, iOS, and Android native app developers, and FileMaker certified developers, led by the FileMaker DevCon 2015 Developer Cup champion, 24U excels in taking care of existing FileMaker solutions, optimizing their performance, identifying and resolving potential issues and liabilities, improving reliability, stability and scalability, integrating them with other systems including various hardware devices, and extending them beyond expectation.
As a platinum member of the FileMaker Business Alliance, we help global businesses around the world to maintain sustainable growth by working with their in-house developers or completely taking care of the maintenance and development of their business solutions.
Software Division Manager, 24U s.r.o.
(c)2018 24U s.r.o. All rights reserved. 24U, 24U Software, and FM Bench are trademarks of 24U s.r.o. FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries. All other trademarks are the property of their respective owners. Pricing and availability are subject to change without notice.
By Richard Fincher
I'm just trying out FMS17 on a virgin Windows Server Essentials 2016 install, which I do not plan to use for any other task except hosting FMS17.
I'm looking to switch off or block all ports and services which aren't needed for Filemaker Server. The ones I'm planning to open for FMS are 80, 443, 5003, 16000. The other ones which seem to be open separately from FMS are :
PORT STATE SERVICE
53/tcp open domain
88/tcp open kerberos-sec
135/tcp open msrpc
389/tcp open ldap
445/tcp open microsoft-ds
464/tcp open kpasswd5
593/tcp open http-rpc-epmap
636/tcp open ldapssl
3268/tcp open globalcatLDAP
3269/tcp open globalcatLDAPssl
3389/tcp open ms-wbt-server
I'll be placing IP restrictions on 3389 (for my RDP), regarding switching off the rest, it occurred to me that parts of the OS may need to use some of these services to do what they need to do (e.g. allow administrator to login to windows?)
Will be using a firewall external to windows itself, rather than the Microsoft firewall.
By Peter Wagemans
Because I have only 1 external IP address in the office here, I have set up a reverse proxy on my Sophos UTM 9 firewall, they call it WAF or Web Application Firewall. In this setup, you define a number of "real" web servers with their internal IP addresses, you also define a number of "virtual" web servers by DNS name m type ( http or https ) and port ( 80, 443, or whatever you would like). This works great if you want to host different web servers on different internal machines. BTW they are all VMs.
I also configured this for FileMaker Server, so everything https related is nicely routed to the fms machine. That also works great, apart from 1 small thing. The client complains about the certificate.
There is nothing wrong with the certificate, as this works fine when I connect to the server internally ( using the same DNS name of course ). Everything nicely green. It only goes wrong when contacting it externally.
FileMaker shows an error dialog that it cannot verify the identity of the server. See screen 1. When I click on "View Certificate" it shows perfectly fine certificates, as shown in screen 2, 3 and 4.
There must be something wrong with the way the firewall is implementing the reverse proxy. I think I configured it correctly: I am passing the host headers, and the virtual filemaker site is correctly associated with the wildcard certifcate, just like the regular virtual apache web site that I am running as well and which gives not problems whatsoever. Someone at the Sophos forum indicated that perhaps the firewall is inserting some certificate information that is not making FileMaker itself happy.
It appears to me that FileMaker is using 2 technologies here, one that is a custom FileMaker certificate client, which is detecting something it doesn't like, and the "View Certificate" dialog is almost certainly using standard system software ( webkit? ) and decides everything is fine. They are not agreeing with each other, that is for sure.
Are there any IT people on this forum who have set up something like this? Any help is very much appreciated.
I'm seeing a "FileMaker Script Engine process has terminated abnormally" error when I attempt to register modules on Filemaker Cloud 1.17 using Scriptmaster 5.1 Unfortunately, the database stops responding when it encounters this error, forcing me to close the database. I noticed a similar issue on the forum related to Filemaker Server 17 that was fixed in 5.1. Could there still be an issue for Filemaker Cloud 1.17?
EDIT: 5.09 works, as mentioned in my post below. I suggest that people use Scriptmaster 5.09 on Filemaker Cloud until this is fixed.
EDIT 2: There is potential to corrupt data if we attempt to close the database when it is not responding after attempting to register a module with Scriptmaster 5.1. It takes a while before Filemaker will close the database, and it warned me of possible corruption when I re-opened it and attempted to register another module. In testing, I wasn't able to replicate the issue after I sent a disconnect request for the Client thread running the module registration step and turned off Script Engine plugins until I saw the thread had been disconnected. I was able to install 5.09 afterward and confirm that scriptmaster was working once installed.
Who Viewed the Topic1 member has viewed this topic:kurucay2000