What we have been following is that, we keep endpoints and any other
environment specific configurations on the registry and have different
registry environments for dev, qa and prod with identical content with
the configuration to the respective values.
I think the cApp also addresses this, not sure whether it is production
ready, and discovery too :-)
Ruwan
On 12/6/10 12:27 PM, Srinath Perera wrote:
can we take old to new endpoint mapping as a input when we migrate and
use that to fix the endpoints?
--Srinath
On Mon, Dec 6, 2010 at 12:21 PM, Supun Kamburugamuva<[email protected]> wrote:
I would like to know the solutions that we have for moving a development
environment ESB configuration to a production environment.
The main concern is with the Endpoints.
One solution would be to store the Endpoints in the registry and have two
registries for dev and prod. When the configuration is migrated from dev to
prod the endpoints should not get migrated. But this requires an endpoint
configuration change to be done in two places.
Any ideas and solutions?
Thanks,
--
Supun Kamburugamuva
Technical Lead
WSO2 Inc.; http://wso2.org
E-mail: [email protected]; Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Ruwan Linton
Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
