Re: [Architecture] [Update] Appfactory Support for PHP Applications

Hi all, This is the update for the PHP application type support in Appfactory. 1. *Subscription on deployment* Requirement: An application would subscribe to a particular cartridge in Stratos in 2 ways. 1. At the tenant creation - Applications deployed in the servers that

Re: [Architecture] ESB Connector | Yammer

Hi Vanji, We dont have a much progress from the last place we stopped. But we are working on it now and we will be finishing it soon. Thanks, Manil On Tue, Sep 2, 2014 at 1:26 PM, Vanjikumaran Sivajothy va...@wso2.com wrote: Hi Manil, Is there any update on your connector project progress?

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

Hi all, The RXT configuration is loaded just like any other registry resource. The same caching principals work for it. Are we trying to solve another problem here? Or did something actually break how registry caching works? Thanks, Senaka. On Tue, Sep 16, 2014 at 7:25 AM, Pulasthi Supun

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

Hi Azeez, Yes that can be done, that would reduce the number of DB calls further. We can simply keep an entry for each RXT type that will keep a parity bit as a value. Once a update is done the listener can query the exact RXT type that was changed and only load that value. Regards, Pulasthi On

Re: [Architecture] Integrating BAM with EMM

Hi Inosh, And you need to extract parameter fields in the Application level and note that these field set should be fixed for all the events. You can send custom key-value pairs as well inside a separate string map . (Refer https://docs.wso2.com/display/BAM241/Data+Publisher) Thanks. *Maninda

[Architecture] Stopping the load artifacts call from accessing the database each time

Hi All, Currently when working with RXT's each time the loadGovernanceArtifacts method is called it in turn will call the DB to load the RXT's, this is to load any changes done to the RXT's . This a major performance hit especially in APIM since when loadGovernanceArtifacts is called multiple

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

For this type of problem, caching coupled with loading only the changed parts is the way to go. On Tue, Sep 16, 2014 at 10:53 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi All, Currently when working with RXT's each time the loadGovernanceArtifacts method is called it in turn will call the

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

On Tue, Sep 16, 2014 at 11:28 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi Azeez, Yes that can be done, that would reduce the number of DB calls further. We can simply keep an entry for each RXT type that will keep a parity bit as a value. Once a update is done the listener can query the

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

Hi Shariq, Yes that is why we are using the cache. the cache will be distributed. When node 1 changes the RXT it will flip the parity bit in the cache entry that correspondence to the changed RXT, then the listener will be called in node 2 since the entry was changed. And within the listener the

Re: [Architecture] [AF] WSO2 Cloud Authenticator

For server side it is in authenticators.xml. For client side it is in appfactory.xml. On Sep 17, 2014 9:42 AM, Manjula Rathnayake manju...@wso2.com wrote: Hi Danushka, How does the secret is shared among nodes? is it by a configuration file that is set in all nodes? thank you. On Fri,

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

Yes, Will be using the listener API provided in the javax.cache Regards, Pulasthi On Tue, Sep 16, 2014 at 11:53 AM, Afkham Azeez az...@wso2.com wrote: I presume you are using the listener API provided by javax.cache. On Tue, Sep 16, 2014 at 11:47 AM, Pulasthi Supun pulas...@wso2.com wrote:

Re: [Architecture] [Update] Appfactory Support for PHP Applications

On Tue, Sep 16, 2014 at 7:54 AM, Madhawa Bandara madh...@wso2.com wrote: Hi all, This is the update for the PHP application type support in Appfactory. 1. *Subscription on deployment* Requirement: An application would subscribe to a particular cartridge in Stratos in 2 ways.

Re: [Architecture] Stopping the load artifacts call from accessing the database each time

On Tue, Sep 16, 2014 at 11:47 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi Shariq, Yes that is why we are using the cache. the cache will be distributed. When node 1 changes the RXT it will flip the parity bit in the cache entry that correspondence to the changed RXT, then the listener

Re: [Architecture] Integrating BAM with EMM

Hi Inosh, With the proposed refactoring discussions there is a high chance that most of the existing code get migrated to components. Hence is it possible to move this stat publisher logic into Java components and call them through API layer or some other generic point rather than adding them in

Re: [Architecture] Integrating BAM with EMM

Hi Dilshan, Stat publisher component is written in Java, and there will be APIs to publish each event to BAM. With current implementation of EMM, Jaggery will call these APIs when it is necessary to publish data. And this call will happen in a separate thread[1] and inside java publishing