Is it required that a forms portal server in the DMZ, set up to work from a single database with an internal server, have access to all data sources the public forms require? For instance, if a form requires a lookup from a data source on another SQL server, must we open a connection from the DMZ server to that SQL server or use a linked server or is there a way to use it so that the internal server has access to this data source and can pass/act as the DMZ's agent?
Question
Question
Question about forms portals and DMZ connections to other SQL servers.
Replies
Hi Kylie,
It is supported from Forms 11 Update 1(https://support.laserfiche.com/kb/1014301/list-of-changes-for-forms-11-update-1 ) to use routing service to execute lookup rule as a proxy
- Now support using the routing service as a proxy for executing lookup rules in a DMZ high security mode configuration.
So one can configure DMZ Forms to use internal routing service as a lookup proxy. Then DMZ Forms won't require connection to data source as internal routing service will do the job for it. While an extra port needed to be opened between DMZ machine and internal machine for lookup communication.
Are there any instructions out there for configuring the DMZ forms to use the internal routing service as a lookup proxy?
The official documentation is being prepared and DMZ whitepaper will be updated when ready. Before that, you can refer to following instructions for configuration.
After configuring Forms following DMZ whitepaper, perform following steps to configure DMZ Forms to use internal routing service as lookup proxy:
1. Open port 8174 (default) between DMZ Forms machine and internal Forms machine for lookup communication
2. Modify DMZ Forms web.config (C:\Program Files\Laserfiche\Laserfiche Forms\Forms\Web.config)
- under appSettings node, find EnableRoutingLookupProxy and set its value to true
- locate WCF client configuration block, for lookup endpoint, change the localhost references to internal Forms server. For example,
<endpoint address="net.tcp://{InternalForms}:8174/lookup" binding="netTcpBinding" bindingConfiguration="timeoutBinding" contract="FormsModel.SharedContracts.IRoutingLookupService" name="" />
(replace {InternalForms} with your internal Forms server's name)
Thanks for the above information.
For Clarification, the Forms 11 release states:
- Now support using the routing service as a proxy for executing lookup rules in a DMZ high security mode configuration.
The High Security Mode includes two SQL servers, one in the DMZ and another internal. What this particular setup is the Standard DMZ Configuration: Two Forms Servers, One SQL Server. Will this lookup still work with this setup?
Hi Karim,
Yes, it does work with Standard DMZ configuration.
Thank you for bring this up. The release note looks misleading. We will update it for clarity.
I'm showing the Forms 11 DMZ whitepaper was updated December 2022, but I am not seeing these instructions in there. Any idea when it will be added?
Will the Forms 11 DMZ whitepaper be updated with this information?
Also, do you first have to configure FormsConfig to work with a database and then go in and change the endpoint value or can you change the endpoint value first and then go to FormsConfig to change the other settings needed in a DMZ configuration?