Re: [Architecture] Unified Governance Metadata models and APIs for WSO2 Platform

Hi Subash, This is regarding the questions you asked about application versions. Current AF versions are not right and needs to be redone in future on what we finalise on Greg. I have documented some thoughts that were on my mind Application versions can use, - APIs - an association to a API

[Architecture] WSO2 MB Proposed RDBMS Design for Andes Context Store

Hi, Following is the RDBMS design for WSO2 MB 3.0.0. Andes context store. *Design Considerations*​ - MessageStore and AndesContextStore can be two different types of storage servers. Hence isolated from MessageStore related Database tables. - In current Implementation *bindings* table

Re: [Architecture] WSO2 MB Proposed RDBMS Design

According to an offline chat I had with PrabathA SQL triggers should be avoided since SQL triggers execute outside SQL transactions. On Thu, Jul 24, 2014 at 6:30 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi, According to mail arch@ Removing Global Queue from MB, maybe we need to update

Re: [Architecture] WSO2 MB Proposed RDBMS Design

If you use triggers, you cannot have a database engine independent design. On Fri, Sep 12, 2014 at 1:21 PM, Asitha Nanayakkara asi...@wso2.com wrote: According to an offline chat I had with PrabathA SQL triggers should be avoided since SQL triggers execute outside SQL transactions. On Thu,

Re: [Architecture] WSO2 MB Proposed RDBMS Design

In addition, triggers, usually, are like stored procedures in its context and at times, might store some good portion of your business logic within the database layer which makes them less visible to someone who's evaluating a particular high-level business use-case just by looking at some code

[Architecture] [AF] WSO2 Cloud Authenticator

Hi All In AF we are using mutual ssl authentcator which will login a provided user to the system. But since with AWS ELB we cannot use this authentication we are decided to implement $subject. Here client will send a username and encrypted secret in header. Server will validate the secret and if

Re: [Architecture] WSO2 MB Proposed RDBMS Design for Andes Context Store

Hi Hasitha, With this we can not get a clear idea on how data is going to store. It would be better if you can give the flow of a message on these and how subscriptions stored. Note: Please send these mails the architecture. Thanks Shammi On Fri, Sep 12, 2014 at 1:13 PM, Asitha Nanayakkara

[Architecture] AppFactory Custom URL improvement - Phase 2 - Add complete custom URLs

In current implementation users can only specify the subdomain of the custom URL, which is mapped under the domain wso2apps.com. In the 2nd phase of usability improvement for custom URL, we will allow users to add complete custom URL by having domain owner verification before setting up the

Re: [Architecture] AppFactory Custom URL improvement - Phase 2 - Add complete custom URLs

Samith, Why do we need validationkey.sampleapp.userdomain.com and not sampleapp.userdomain.com http://validationkey.sampleapp.userdomain.com/ just CNAME record? Adding either of them would require the same DNS ownership of the domain, right? Dmitry On Fri, Sep 12, 2014 at 2:58 PM, Samith

Re: [Architecture] AppFactory Custom URL improvement - Phase 2 - Add complete custom URLs

Samith, If you are thinking of keeping DNS validation as a separate operation (thinking it might be useful for other Cloud services to provide custom endpoints may be, I'm just assuming) then asking user to create a CNAME or TXT record for validationkey.yourdomain.com would be enough. Otherwise

[Architecture] [BPS] Moving the artifact storage from Registry to BPS corresponding DB ( BPS_DB )

Hi, In business process server, artifacts are deployed with a version number. In a clustered environment, in order to avoid the possibility of same artifact having different version numbers assigned by both worker nodes and master node, we have to make sure that only the master node is allowed