Contact 1C and MySQL?

Question

MySQL

I am going through practice at the enterprise, it is necessary to make a conclusion of orders and their statuses on the site. All order data is stored in 1s. The 1c programmer from the enterprise said that he would create an ftp server. Which will throw .xml files. And somehow I will have to enter this information into MySQL. Well, for speed, he will not throw off the entire database, but only what has changed (in his words). How can this be implemented without participation in automatic mode? Maybe there is an easier way?
After asking him why it is impossible to connect directly to 1s. He answered (that he remembered) that 1s is a file database. (Something like that). And a direct connection is not secure.
I must say right away that when I opened Google, I immediately stumbled upon some web services. And did not understand who should create it?

Answer 1

Well, write a script that will spoil the information in the work base for a day at most

Answer 2

Well, in this case, you can parse xml either by curl at the address, or there is some other special xml parser in php that works by dom (I don’t remember what it’s called).

Answer 3

Let him transfer the base to the cheekbone instead of dt-chi, a normal firewall and directly unload, he is afraid for security, put kerio if finances allow, then squid.

Answer 4

It seems to me alone that it would be much more reasonable to switch from file 1C to MSSQL and the simplest replication, to transfer certain fields of the "customer orders" table. And further in Google "Replication MSSQL> MySQL".
As I understand it, they were going to send you a complete exchange file. How many people they have working in 1C and how big they are, as well as how much information is clogged there, you have not indicated. But there is one problem here. These exchanges are quite large (our uncompressed xml weighs 700 meters on average), if the IS is actively used and it takes a long time to parse them and it is cumbersome, especially if they are also compressed. The data will be transmitted once a day, well, two maximum. Also, they will still have a shitty cloud of unnecessary information.
From here, I see the following conclusions:
A - continue in the same spirit and your server will parse these xmls for quite a long time and the information will be rarely updated
B - force them to switch to MSSQL / PostgreSQL C
- So that their 1C programmer writes an individual exchange that will upload at least to the same txt /xml customer orders with the fields you need.