I would like to have 2 Servoy installations communicate with each other.
The obvious way would have the 2 share a table but what about Servoy Sequences?
Any help would be appreciated.
Hi Briggsy,
What do you mean exactly with ‘communicating with each other’ ?
You want some sort of Instance Messager functionality? Or do you just want to share the same data ?
Also do you mean with ‘Servoy installation’ Servoy Server or Servoy Client ?
As for Servoy Sequences, you don’t have to use them you know
You can use Database Managed sequences instead.
Hi thanks for the quick response,
2 different companies, 2 Servoy server installations, each having there own database.
I am looking for a type of EDI (manufacturing) data interchange to share the same data.
I will not use Servoy Sequences and use Database Managed sequences instead (perfect).
I was thinking of a third remote database to share data.
Does anyone know of a way one server could log-on to another one.
I am at a standstill trying to have live data available to 2 Servoy server installations but keep security at its highest.
I can share a database but then all of the security is in the database and not in Servoy.
Sharing a database does not require Licenses between the Servoy Servers but if the servers communicated 2 licenses would be required, right? Am I kind of thinking about a “Multi Developer” scenario but using a “Multi Server” log-in?
Thanks in advance for the help.
Are you doing reads and writes in both directions?
Typically, especially since you have multiple sites, it’s best to develop a loosely coupled system for this type of application. This prevents one site from being reliant on the other, in case of server being down at one site, or the network being down, etc.
There a number of ways to do that. EDI type apps usually use some sort of standard data transfer file (XML) and a transport layer (usually HTTP). You could have one instance login as a headless client and request info from the other when necessary, caching the results in a local database.
How “Live” does the information really need to be?
greg.
How “Live” does the information really need to be?
You are right. It really does not need to be 100% live but loosely coupled is the right way to do it.
You could have one instance login as a headless client and request info from the other when necessary, caching the results in a local database.
How would you suggest I just update the data cached and not request the whole xml transfer file?
I’d need to know more about what you are trying to accomplish.
- Is one system just referencing information from the other?
- Is it a two way sync?
- How often does the data need to be refreshed?
All these effects the complexity significantly. I would typically have a field in the table like “last_sync” (datetime) and use it build a comparison value, then have a batch processor periodically process the updates on the server.
greg.
Greg you are asking all the right questions,
Yes it is a 2-way sync.
One company is a warehouse facility and the other company owns the product.
The product once manufactured is delivered to the warehouse. Each product (piece) is serialized. (2 pieces per truck, large product)
The product is released by the owner and shipped to their customer directly.
The pieces are manufactured at random and brought to the Warehouse
The Warehouse produces an inventory list online (smart client).
The owner selects which one off of the list to ship to their client and, at present, faxes this shipping list back to the warehouse.
The owner wants their own Servoy Server for other solutions and at the same time wants to automate their selection for shipping (no faxes)
At present time there about 10,000 records the inventory table, 75% shipped, 25% ready to ship.
I hope this is not too long, but I want to start off in the right direction. I could share an Inventory table but as you pointed out a loose connection is better.
I am not absolutely sure on how to sync a 10,000 record table and keep all of the relations intact.
Thanks for your help
From your description, it sounds like it might be best (easiest?) to provide a Web-client solution on the warehouse Servoy server that they login to from the other location and select items to release.
g.
I found a link to the Daffodil Replicator.
http://opensource.replicator.daffodilsw.com/index.html
Replicator supports bi-directional data replication by either capturing a data source snapshot or synchronizing the changes.
If anyone has any experience with this open source Java tool I would sure like to here from you.
Best would be to use Mobilink in this situation. We can bundle it with Servoy licenses, I can be contacted by email for more information and pricing.