Hi Aditya,

We don't recommend to use properties files to maintain endpoints. :) We use
registry projects to maintain those. BTW You can achieve your requirement
in several ways,

1) You can create separate registry projects per environment and separate
car files which has the registry resources per environments. Then you can
refer the message stores / data sources from the registry in the ESB Config
car file. This is the most common way to achieve your requirement.

2) You can use maven profiles to build your car files. therefore you can
use maven replacer-plugin to replace your endpoints in the build time.
Please find the blog[2] which describe changing endpoints in the build


On Thu, Mar 8, 2018 at 10:14 AM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Respected Sir,
> Where do we to store connection details with third party systems or db in
> wso2.
> Suppose we have developed a service in wso2 which inserts some record in
> db.
> For that we need to define the connection details of db in some properties
> file or something similar, how do we  do this? so that while migrating from
> one environment(development) to another(Pre-prod) , the third connection
> details will be fetched from the respective properties file. And we do not
> have to change it in datasource manually for each environment.
> or we should not be required to change IP and port details of the
> endpoints to be called in each environment manually.
> Please guide how do we use properties file in wso2 esb.
> Is there any documentation regarding this?
> Thanks and Regards,
> Aditya
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

*Madhawa Gunasekara*
Senior Software Engineer
WSO2 Inc.; http://wso2.com

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
linkedin: *http://lk.linkedin.com/in/mgunasekara
Dev mailing list

Reply via email to