cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronize configuration in the database between different servers

Former Member
0 Kudos

Hi,

I'm searching for a solutions for the differences in 'configuration' between the production environment and the other environments (like test en local). With the differences I mean the manually added classificatons / catalogs / changes in the email templates / etc. I don't mean the products / orders / users that is sensitive data and I don't want that in my local environment. How should I handle this, export specific database tables or are there other automatic ways to synchronise this?

I know that there is also an option that you should make for every change of the classificatons / catalogs etc. an impex file. Is that the way how you should handle this? Because that creates the problem that someone without any 'programming' knowledge can't add something of the catalogs / classificatons models.

How do you handle this?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

You should not do this on database level, this is not intended to be done in the hybris architecture and you run in danger to interfere with changes in the architecture of the persistence layer.

Yes, you should use impex for different configurations of local / test / production systems if you really want / need them. Impex is the way to get initialization data into the platform.

I'd not consider these things "configuration", that's production data you need to run your specific implementation of hybris. Configuration to me is anything that would set up the environment of a hybris deployment (smtp server, db server, file system locations of hot folders etc etc.).

I'd be concerned that this leaves you with systems that are different, should it really be local/test/production - from a testing / QA point of view, how could you ensure that a system behaves the same between local/test/production environment if you have different data sets?

Personally, I would see to have the local / test / production systems as similiar as possible, at least for anything outside customer/order data/products that could eventually be too large for a local system.

Former Member
0 Kudos

Hi Konrad,

Yes that was my question, how can I ensure that the production server has everything the same as the local / test servers without the customer / orders / products. So the answer is what I suggest, we should do everything with impex files otherwise it is impossible to have the different servers in sync. (or we should override the whole database, but that is not an option, because than we have also the customer / order / products.

Thanks for your answer

Former Member
0 Kudos

Hi Konrad,

Could you please give me some more information about the synchronisation of the production data (without the products/customers/orders) with the other servers, how do you handle this in your company? Are you only using impex files and when you add new functionality you create a new impex file?

I think the last sentence is the way to do it, but then you need are dependent of someone who has the knowlegde of impex file.

Thanks for your answer.