Re: [otrs] otrs Digest, Vol 83, Issue 3

Hello Samuel, The best way we've found to that is as follow. 1. Take into account that you have data tables and config tables. Data tables are the ones you just mentioned and config tables are tables like group, user, role, group-role, and so on. 2. When you work on development (test) systems, you need to know where the changes are applied so you can move them to the production system when needed. Config is mantained in ZZZAuto files and you can move that from one server to another. 3. Backup and update individual tables when you need to pass changes (dynamic fields, permissions, groups, roles, etc) 4. Never move or update data tables (ticket, article, faq,dynamic_field_value). 5. Processes, ACLs and stats you can export and import, but need to have config data first (dynamic Fields, Process Configuration) We have not found a better way of doing so, you just need to be sure your systems are kept syncronized after a pass to production. Regards 2015-08-12 15:14 GMT-06:00 Samuel Diniz Casimiro < samuel.casimiro@camara.leg.br>:

Hi guys,

Thank you so much. But I think I wasn't clear enough.

Imagine I already have two environments, both operational and identical at time zero: one for testing and one for production.

Every time a request for change OTRS configuration arrives (some new configuration, a new dynamic field, a new ACL, new process, everything about configuration etc), I need to implement it, test it and then deploy it to production, like any other application.

In other words, I need to export/import all configuration data on a regular basis, but should leave the other production data intact (history of tickets, articles etc...). So drop the database is not an option.

Any idea?

Thanks

-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of otrs-request@otrs.org Sent: Wednesday, August 12, 2015 5:37 PM To: otrs@otrs.org Subject: otrs Digest, Vol 83, Issue 3

Send otrs mailing list submissions to otrs@otrs.org

To subscribe or unsubscribe via the World Wide Web, visit http://lists.otrs.org/cgi-bin/listinfo/otrs or, via email, send a message with subject or body 'help' to otrs-request@otrs.org

You can reach the person managing the list at otrs-owner@otrs.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of otrs digest..."

Today's Topics:

1. Deploy OTRS configuration from test environment to production environment (Samuel Diniz Casimiro) 2. Re: Deploy OTRS configuration from test environment to production environment (Leonardo Certuche) 3. Re: Deploy OTRS configuration from test environment to production environment (Jay) 4. Re: Deploy OTRS configuration from test environment to production environment (Jay)

----------------------------------------------------------------------

Message: 1 Date: Wed, 12 Aug 2015 19:53:36 +0000 From: Samuel Diniz Casimiro Subject: [otrs] Deploy OTRS configuration from test environment to production environment To: "otrs@otrs.org" Message-ID: <672ca87f292e4c39aec7638498e5f9bc@urca1.redecamara.camara.gov.br> Content-Type: text/plain; charset="us-ascii"

Hi everyone!

I'm using OTRS 4.0.11.

Because of some company policies, I need to set up to environments, one for testing and another for production (operational).

The problem is: How to export the required configuration data from test env. and deploy it into production env?

I know I could copy and paste the ZZZAuto.pm file, but is that enough? Is there any database configuration data I should also take care? If so, how?

I know I could use the provided backup.pl script, but I don't want to backup/restore all the data, only the configuration data. Is there any way to do so?

Thanks in advance,

Samuel