Hi all! While testing the WSO2 ESB during the last day I realized that there are different views regarding the application of configuration changes during development and production. The current implementation seems to concentrate on the development perspective. With just a few clicks you can define some new proxy services or change existing content based routing rules for example. All changes will be active immediately and can be tested. During development this is really what you want. In pre-production or production this is rather the opposite of what you want. There changes shall be bundled (some kind of change package) and applied at a certain point in time. Each change should be versioned and part of a history. It than should be possible to revert (fall back) to any former version. What do you think of the following idea:
If an administrator logs in to the administration console, everything is read-only by default. If he would like to change any option, he had to open a new change package. He can then change as many options as he like. Every change will be part of the opened change package, but not applied to any running instance of the esb. If the administrator decides to activate a change package, a new configuration version will be created and all changes will be applied. In some kind of history view the admin could change to any of the former version and activate that. What do others think about this suggestion? Maybe one could also consider between two modes of the administration application - development (current behaviour) and production (my suggestion) and switch between them. Currently I only see one problem. What should be considered to be the configuration? Only synapse.xml? Probably not. What about registry/repository? This is one aspect which might favour the usage of the internal registry/repository. From a business perspective it doesn't matter whether an endpoint definition or a routing rule changes. The impact might be the same. Regards, Eric -- Eric Hubert Software Architect Associate Director Research & Development _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
