You are viewing limited content. For full access, please sign in.

Question

Question

Forms High Security Solution Feature Request: Have Forms Sync between both databases

asked on September 20, 2018

Currently with the Forms High Security Solution you theoretically have to have an SSIS or similar sync of the "dbo.cf_business_processes" table between the internal Forms database and the Forms database in the DMZ in order for the "bp_id" of the business processes to match in both databases.  In practice however, not only are the rows in the "dbo.cf_business_processes" table read only; but there are reference constraints that conflict with any SQL query that tries to overwrite the data in the DMZ "dbo.cf_business_processes" table with the data in the "dbo.cf_business_processes" table from the internal Forms database.  

 

So in essence the current High Security solution is not viable for clients, as you basically have to copy the entire internal Forms database to the DMZ Forms instance, and reconfigure Forms each time that a client adds a business process that needs to be made available to the public anonymously.  

 

The Forms High Security solution needs a way to one way sync the business processes from the internal Forms instance to the DMZ Forms SQL instance in a way that is seamless to the client.  (Perhaps over the "lfrouting" port?)  

1 0

Answer

SELECTED ANSWER
replied on October 11, 2018

I ended up only doing the sync on the "cf_business_processes (dbo)" table, and then exporting the forms XML file from the internal Forms instance and importing it into the DMZ Forms instance in order to overwrite the existing form so that the form process modeler was still view-able, due to the process modeler objects not being in the "cf_business_processes (dbo)" table.  (But still keeping the same same business process ID in the database because the "cf_business_processes (dbo)" table is being synced)

Exporting the form from the internal Forms "MANAGE", "DOWNLOAD" tab; and Importing the from through the DMZ Forms instance "DESIGN", "UPLOAD" tab, and overwriting the existing business process in the DMZ allows us to keep the BP ID, but still import changes.  (And be able to view the form once it is imported)  

This will work for the client, as it only requires them to do an export and import of the forms in order to keep the BP ID.  (And they can view the form in the DMZ)

So the current workable workaround is to:

#1:  Create one way sync of the "cf_business_processes (dbo)" table

#2:  Export the business process XML from the internal forms instance through the browser interface.  ("MANAGE", "DOWNLOAD" for 10.3.1)

#3:  Import the business process XML into the DMZ Forms instance, and choose "OVERWRITE" so that you can actually view the business process objects in the "DESIGN" tab.  ("DESIGN", "UPLOAD")

 

0 0

Replies

replied on September 26, 2018

I was able to set up a workaround using transactional replication using SQL authentication and the SQL agent service account; the full details are in the following YouTube video tutorial:

https://www.youtube.com/watch?v=sbrUtfkkVUE

 

(The internal SQL instance has to be a full instance in order to be a publisher)  

0 0
SELECTED ANSWER
replied on October 11, 2018

I ended up only doing the sync on the "cf_business_processes (dbo)" table, and then exporting the forms XML file from the internal Forms instance and importing it into the DMZ Forms instance in order to overwrite the existing form so that the form process modeler was still view-able, due to the process modeler objects not being in the "cf_business_processes (dbo)" table.  (But still keeping the same same business process ID in the database because the "cf_business_processes (dbo)" table is being synced)

Exporting the form from the internal Forms "MANAGE", "DOWNLOAD" tab; and Importing the from through the DMZ Forms instance "DESIGN", "UPLOAD" tab, and overwriting the existing business process in the DMZ allows us to keep the BP ID, but still import changes.  (And be able to view the form once it is imported)  

This will work for the client, as it only requires them to do an export and import of the forms in order to keep the BP ID.  (And they can view the form in the DMZ)

So the current workable workaround is to:

#1:  Create one way sync of the "cf_business_processes (dbo)" table

#2:  Export the business process XML from the internal forms instance through the browser interface.  ("MANAGE", "DOWNLOAD" for 10.3.1)

#3:  Import the business process XML into the DMZ Forms instance, and choose "OVERWRITE" so that you can actually view the business process objects in the "DESIGN" tab.  ("DESIGN", "UPLOAD")

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.