Re: [Dev] [APIM][IS as a KeyManager] Cyclic dependency between IS and APIM

Actually these two are needed for two different scenarios. 1. Store calls KM for token regeneration. KM then invalidates the older key from gateway cache. Therefore KM needs to know where the GW is. 2. Gateway calls KM for token validation. Therefore GW needs to know where KM is. So I don't thin

Re: [Dev] [PPaaS] Clustering WSO2 applications across multiple network partitions on Apache Stratos

As i had offline discussion with Nirmal, got it cleared..We are using an AWS LB to front the LBs which got spawn across multiple regions. In that case, we will use the same hostname to access the cluster through AWS LB (it will use Round Robin to choose one of our LB). So, we will need to make same

[Dev] [APIM][IS as a KeyManager] Cyclic dependency between IS and APIM

Hi All, In an IS as a Key Manager configuration, there's a cyclic dependency scenario, where you need to specify Gateway URL in IS side and IS's URL in APIM side. Can't we make it one way? -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +947

Re: [Dev] [PPaaS] Clustering WSO2 applications across multiple network partitions on Apache Stratos

Hi Reka, Sorry, your question is not much clear to me. But as you know, we do not use hazelcast clustering to join with LBs. On Sat, May 24, 2014 at 11:23 PM, Reka Thirunavukkarasu wrote: > Hi > > On Sat, May 24, 2014 at 11:06 PM, Nirmal Fernando wrote: > >> Hi Akila, >> >> It's the instances

Re: [Dev] [PPaaS] Clustering WSO2 applications across multiple network partitions on Apache Stratos

Hi On Sat, May 24, 2014 at 11:06 PM, Nirmal Fernando wrote: > Hi Akila, > > It's the instances in a cluster that resides in one hazelcast domain not > all the cartridge instances. > > And in a multi-region deployment, we should use public IPs of members as > well-known addresses. That's all we h

Re: [Dev] [PPaaS] Clustering WSO2 applications across multiple network partitions on Apache Stratos

Hi Akila, It's the instances in a cluster that resides in one hazelcast domain not all the cartridge instances. And in a multi-region deployment, we should use public IPs of members as well-known addresses. That's all we have to do. On Sat, May 24, 2014 at 8:52 PM, Akila Ravihansa Perera wrote:

Re: [Dev] New Feature for WSO2 Governance Registry - Exemption to Life-cycle Policies for a particular period (RM Feature- #477)

Hi, Yes. I think it is. I have handled this time validation inside the constructor of DefaultLifeCycle.java class itself, so that whenever a lifecycle is taken in to account, time validity will be checked and relevant actions will be taken. So even when an API call is triggered, and when the associ

Re: [Dev] Enabling auto merging functionality in GITHUB for ESB components

Hi Malaka, It is already added. Will enable it. On Friday, May 23, 2014, Malaka Silva wrote: > I guess we may need carbon-mediation as well? > > > On Fri, May 23, 2014 at 6:32 PM, Vanjikumaran Sivajothy wrote: > > Thank you. > > Best Regards, > Vanji > > > On Fri, May 23, 2014 at 5:04 AM, Mahe

[Dev] [PPaaS] Clustering WSO2 applications across multiple network partitions on Apache Stratos

Hi, In Private PaaS we have different Apache Stratos clusters created for each WSO2 service (for eg - AS, ESB, IS, APIM). If clustering is enabled at the service deployment, each instance in the same cluster will update its axis2.xml with well known members' IP addresses in that cluster. Basically

Re: [Dev] [Social] Documentation around how to cluster social components.

Hi Amila, I do agree with you on the Cassandra cluster ( where we should be pointing to a external Cassandra ring). there are parts of Appfactory deployment publishing wall msgs ( using social component) (e.g. when a application is deployed/failed application server will send a wall msg) Ther

Re: [Dev] [Social] Documentation around how to cluster social components.

Ramith, I think you are trying something wrong. AF at the moment ships social component and an embedded cassandra. Thats why you have this problem. Ideally you should be using an external cassandra. Then there is nothing to worry when creating an AF cluster. On Thu, May 22, 2014 at 11:50 AM, Man

[Dev] WSO2 Identity Server 5.0.0 Released!

*WSO2 Identity Server 5.0.0 Released!* The WSO2 Identity Server team is pleased to announce the release of version 5.0.0 of the WSO2 Identity Server (IS). WSO2 Identity Server is an open source Identity and Entitlement management server. It supports a wide array of authentication protocols such a

[Dev] Error Messages with their status codes in EMM Android Agent

Hi All, Here I have summarized all status code currently we ara handling in EMM Android Agent. EndpointUse case/ ReasonResponse - StatuscodeStatusMessage TitleMessage Action1 /oauth2/token Login with valid credentials200Success-- 2Invalid username/password400FailAuthenitcation FailedIncorrect lo

Re: [Dev] [Appfactory][Clustering] ELB 2.1.1 goes to a endless loop when a member leaves.

Hi , We could observe following exception when creating a tenant. TID: [0] [Carbon] [2014-05-24 14:47:47,259] ERROR {org.apache.cassandra.service.AbstractCassandraDaemon} - Exception in thread Thread[hz.wso2.af.domain.instance.cached.thread-6,5,wso2.af.domain.instance] {org.apache.cassandra.servi

[Dev] WSO2 Business Rules Server (BRS) 2.1.0 Released!

The WSO2 Business Rules Server (BRS) 2.1.0 Released!May 2014 The WSO2 BRS team is pleased to announce the release of version 2.1.0 of the Open Source Business Rules Server (BRS). WSO2 Business Rules Server (WSO2 BRS) is to be your Business Rule Management System (BRMS). Our ultimate goal is to pr