Hi Imesh,
Sorry for the late response. Here is the JIRA [1].
[1] https://wso2.org/jira/browse/PPC-7
Thanks,
Raj.
On Tue, Sep 22, 2015 at 9:48 PM, Imesh Gunaratne wrote:
> Hi Raj,
>
> Can you please report a JIRA for this with the relevant information?
>
> Thanks
>
> On Wed,
Hi Raj,
Can you please report a JIRA for this with the relevant information?
Thanks
On Wed, Sep 16, 2015 at 12:55 PM, Rajkumar Rajaratnam
wrote:
> Hi Guys,
>
> Have we fixed the two issues discussed in this thread? If not, better to
> track it via a JIRA.
>
> Thanks,
>
Hi Guys,
Have we fixed the two issues discussed in this thread? If not, better to
track it via a JIRA.
Thanks,
Raj.
On Thu, Sep 10, 2015 at 4:53 PM, Pubudu Gunatilaka wrote:
> Hi,
>
> +1 for this approach
>
> What we initially thought was to list down all the parameters in
What I meant is, why don't we do this?
if CONFIG_PARAM_LOCAL_MEMBER_HOST is set {
{{ CONFIG_PARAM_LOCAL_MEMBER_HOST
}}
} else {
127.0.0.1
}
Thanks.
On Thu, Sep 10, 2015 at 3:59 PM, Rajkumar Rajaratnam
wrote:
> Any reason to treat the following config parameters
Hi Raj,
if CONFIG_PARAM_LOCAL_MEMBER_HOST is set {
> {{ CONFIG_PARAM_LOCAL_MEMBER_HOST
> }}
> } else {
> 127.0.0.1
> }
+1 for this approach. This way we can pass only required parameters.
On Thu, Sep 10, 2015 at 10:16 AM, Rajkumar Rajaratnam
wrote:
> What I meant
Hi,
+1 for this approach
What we initially thought was to list down all the parameters in the
module.ini file which are not default values. User can either override
those values from environment variables or use the module.ini file.
Thank you!
On Thu, Sep 10, 2015 at 10:16 AM, Rajkumar
Any reason to treat the following config parameters differently, than other
config parameters?
CONFIG_PARAM_CLUSTERING=false
CONFIG_PARAM_DOMAIN=wso2.carbon.domain
CONFIG_PARAM_WKA_MEMBERS=[127.0.0.1:4000]
CONFIG_PARAM_LOCAL_MEMBER_HOST=127.0.0.1
CONFIG_PARAM_LOCAL_MEMBER_PORT=4000
Hi,
I think API Manager's master-datasources.xml.template is messed up. For
example, same db username/password parameter is used for all the databases
and jdbc/WSO2REG_DB is defined twice with two different if-checks, why?
Please check and fix [1]. Please check other modules also.
[1]
Hi Raj,
Yah..Seems some old reference is there in the
master-datasources.xml.template which will not affect the configurations,
if the parameters are defined correctly in the cartridge definition. Please
ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL.
Please refer [1] for the sample
On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu wrote:
> Hi Raj,
>
> Yah..Seems some old reference is there in the
> master-datasources.xml.template which will not affect the configurations,
> if the parameters are defined correctly in the cartridge definition. Please
>
10 matches
Mail list logo