Re: [Architecture] Process Store for text based process

[Ruchira Wageesha]

HI Shiva/Chathura,

I would recommend you to keep the adding/editing functionality in the
publisher side. Otherwise, you will have to re-implement most of the stuff
that we have done in the publisher.

You can do SSO between store and publisher. Hence, what you need to do is,
just display an edit link in the store. When that edit link is clicked, the
user will be redirected to the publisher's edit page of that specific
process. Since SSO is enabled, the user will not see much difference. i.e.
he will feel that the edit page was there in the store app itself, only
difference is, you see a page refresh.

Further, if you go with publisher, you have more freedom in the future to
improve your add/edit views as publisher UI has designed for that kind of
requirements. Otherwise, you will have to introduce your own left menu,
search, LC UIs etc. in the store side.

/Ruchira


On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
wrote:

> As Shiva has mentioned, we want to do both adding and displaying process
> models in the same UI, diverting from the current model of ES to have a
> separate publisher and a store. An example requirement would be: a user
> browsing a process model may want to add some details to certain sections
> of the model, so that he should be able to do it from the same UI.
> Similarly, a user may want to add a specialized version of a currently
> displaying model. Therefore, I think the adding/editing functionality has
> to be provided in the same UI, controlled by user's authorizations.
>
> Regards,
> Chathura
>
>
> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran 
> wrote:
>
>> Hi All,
>>
>> The Enterprise Store currently satisfies necessity to host
>> applications, gadgets and eBooks. Users are able to add new assets of the
>> given type or create their own asset type and work with the store. A
>> requirement has arose to develop a Process Store to host processes of all
>> types and visualize associations with processes whilst providing other
>> utility functions. I am currently working on building a Process Store to
>> address the requirement.
>>
>> After discussion with the stakeholder we have agreed to initially build
>> the store as an extension of the enterprise store and move the process
>> store out as an product in the future. The extension to be built will be
>> for textual based processes and in future will be able to support other
>> type of processes too.
>>
>> The extension to be built will have the following functionality:-
>>
>>
>>- Adding a text based process
>>- Editing a text based process
>>- View a text based process
>>- Search for a text based process
>>
>>
>>- Associate existing text based process to a new variant - The user
>>when adding a new process can associate the new process to a existing one
>>if the new process is a variant or similar to the existing process but a
>>variant.
>>
>>
>>- Navigating processes through associations - The user can navigate
>>through the associations to find similar processes or their variants.
>>
>>
>>- Visualizing associations in graph views - The associations between
>>the processes will be sketched or depicted. This will be developed using
>>JSPlumb.
>>
>> The processes will be built as an asset type of the Enterprise Store as
>> discussed and the utility functions of the store such as adding, editing,
>> viewing, searching and visualizing will be done in the store front rather
>> than navigating to the publisher.
>>
>> Thank you
>>
>> --
>> Shiva Balachandran
>> Software Engineer
>> WSO2 Inc.
>>
>> Mobile - +94 774445788
>>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com *

*email: ruch...@wso2.com ,   blog:
ruchirawageesha.blogspot.com ,
mobile: +94 77 5493444*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API Manager Authorization Server Decoupling

[Sanjeewa Malalgoda]

Hi Amila,
This is very valid use case and thanks for bring this up. Please find
comments inline.


On Mon, Sep 1, 2014 at 9:30 AM, Amila De Silva  wrote:

> Hi,
>
> Currently a development is going onto decouple Authorization Server from
> API Manager.
>
> In the existing design, creating Applications, generating & validating
> Tokens are done through non-standard interfaces and these operations are
> tightly coupled with the Key Manager ,which is the default Authorization
> Server in a typical API Manager Deployment.
>
> The ongoing effort is to identify such tightly coupled areas and provide
> extension points for them, allowing an external Authorization Server to
> issue and validate Access Tokens.
>
> There are 2 major Tasks involved in this.
>
> 1. Changing the way Applications are registered on the Store – An
> Application created in Store can have two types of Keys PRODUCTION and
> SANDBOX. When a user clicks on the Generate button,
>a. An Oauth app is created with the given key type
>b. An Application Access token is Generated
>
> When creating the OAuth app entries get written to IDN_CONSUMER_APPS and
> AM_APPLICATION_KEY_MAPPING tables.
> Access Token is generated by creating an entry in IDN_OAUTH2_ACCESS_TOKEN
> table.
>

> By providing the capability to plug-in a custom implementation for an
> Oauth app, users will be able to store/create Oauth Apps in their own
> Authorization Server, eliminating the need to keep Access Tokens in AM
> Tables.
>
In this case do we still need to maintain apps inside API Manager.
Applications, subscriptions and tokens are tightly coupled and inter
related. So how do we plan decouple these? First we might need to identify
the roles and tasks of authorization server. Following are required IMO
Create, update and maintains applications.
Maintains subscriptions.
Generate tokens and manage them.
Handle token validation, verification.

So from API Manager side we can provide interface to access authorization
server. Are we planning to create interface and decouple current
implementation as authorization server? Or are we going to consider
external common authorization server pluggability ?

Thanks,
sanjeewa.

>
> 2. Changes on Token Validation
> During an API Invocation, GW calls the KM to get the Key Validated. During
> the validation
>a. Token is checked for it's Validity- whether it is Active or not
>b. Subscription gets validated - If the API being invoked is subscribed
> by the Application that obtained the token.
>c. A JWT is generated using the default claims and the custom claims
> user has provided.
>
> As of now, all of these operations are performed by
> APIKeyValidationService running in KM. There can be scenarios where user
> needs to delegate , token validation to a different Authorization Server.
> To use in such scenarios, a service needs to be provided in KM, which only
> checks the state of the subscription.
>
> APIAuthenticationHandler which is responsible for calling KM and getting
> the token validated needs to be modified to call an external
> service/endpoint and fetch details(such as consumer key) about the client
> that obtained the token.
>
>
> Details about the design and the tasks will be provided in the mails to
> follow.
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

 blog
:http://sanjeewamalalgoda.blogspot.com/

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Siddhi CEP snapshot bug?

[Sriskandarajah Suhothayan]

Hi

When I looked at the sample code you have sent, I believe you have
misunderstood the way Siddhi Snapshot works.

Siddhi does not restore the queries or definitions when restoring, but it
will only restore the states on each query (e.g the partially matched
states in sequence/pattern query, events in windows, running average
values, etc..).
Here on your setup method, you have to create the Siddhi Manager and add
the Stream Definitions, Queries and then restore the state.

You can find a sample test case here
https://github.com/wso2-dev/siddhi/blob/master/modules/siddhi-core/src
/test/java/org/wso2/siddhi/test/management/PersistenceTestCase.java

Regards
Suho



On Mon, Sep 1, 2014 at 7:20 PM, Antonio Jesus Navarro  wrote:

> Hi all,
>
> I could not fix the problem.
>
> Someone can explain me what i'm doing wrong?
>
> Thanks in advance.
>
>
> 2014-08-13 9:53 GMT+02:00 Antonio Jesus Navarro :
>
> Hi Rajeev and Tishan,
>>
>> I add a couple of tests to show the two possible use cases described, one
>> using PersistenceStore implementation, and other using snapshot() and
>> restore(...) SiddhiManager methods.
>>
>> Thanks.
>>
>>
>> 2014-08-12 15:35 GMT+02:00 Tishan Dahanayakage :
>>
>> Hi Antonio,
>>> To clarify further can you please share your query with us?
>>>
>>> Thanks,
>>> Tishan
>>>
>>>
>>> On Tue, Aug 12, 2014 at 6:47 PM, Rajeev Sampath 
>>> wrote:
>>>
 Hi Antonio,


 On Tue, Aug 12, 2014 at 2:55 PM, Antonio Jesus Navarro <
 ajnava...@stratio.com> wrote:

> Hi all,
>
> Siddhi version 2.1.0-wso2v1 have new service called SnapshotService. I
> think this service is used to recover the siddhi context from an 
> unexpected
> shutdown. The service have a method to generate a byte array with snapshot
> data, and a method to restore this snapshot.
>
> Byte array generation works perfect. The byte array is generated with
> all Snapshotable elements. But I think there are a bug into the restore
> method. It iterates a snapshotable list of elements that in the first
> instance are empty, and the byte array is never setted to siddhiContext.
>
> In restore() method, it lets all the snapshotables (windows, patterns
 etc) to restore themselves instead of setting it in SiddhiContext by
 calling restore() on all of them. All the required components such as
 windows, patterns that has a state implements this functionality.

 When you are using Siddhi as a library, when restoring you'll have to
 call siddhiManager.setPersistStore() with whatever store implementation you
 have and then call restoreLastRevision() to restore it to the previous
 state.


 Thanks
 Rajeev



>  I am misunderstanding something? Or it is a bug?
>
> Thanks in advance.
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Rajeev Sampath
 Senior Software Engineer
 WSO2, Inc.; http://www.wso2.com.

 Mobile:
 * +94716265766 <%2B94716265766>*

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Tishan Dahanayakage
>>> Software Engineer
>>>  WSO2, Inc.
>>> Mobile:+94 716481328
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, re-transmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
 *WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Architecture mai

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dmitry Sotnikov]

Got it. Thanks Dimuthu!
On Sep 3, 2014 5:01 PM, "Dimuthu Leelarathne"  wrote:

> Hi Dmitry,
>
> Yes. It makes perfect sense. But the only problem is current
> implementation is not transferring each and every event when it happens.
> What I do is record the events and periodically send to the backend. The
> time period is large. (note: timestamp is recorded at the browser, so the
> actual time is preserved even though recording happens in 2 mins).
>
> So what happens if a person browse away or hit cancel/ok before the next
> time slice? We are going to loose some events, unless we use the unload
> method. That was why I am looking for it.
>
> Other option is to reduce the time slice but that would increase the
> recording period.
>
> Chanaka's solution worked when used properly!
>
> thanks,
> dimuthu
>
>
>
>
>
>
>
>
> On Wed, Sep 3, 2014 at 6:24 AM, Dmitry Sotnikov  wrote:
>
>> Quick thought (maybe not relevant or inferior to the current direction
>> ;)):
>>
>> Maybe instead of "abandoning events", we concentrate on events that show
>> success (and thus detect "failure" is "not achieving success")?
>>
>> For example, to invite team members you go through the following steps:
>> 1. Go to the team invitation page,
>> 2. Do something on the page (start filling out the forms to specify the
>> usernames/email addresses, roles, etc.),
>> 3. Send the invite,
>> 4. New member actually accepts and logs in,
>> 5. You add the user to an app,
>> 6. New member actually does something meaningful.
>>
>> If we have events for some of these steps but not all the way through #6
>> - we know that the overall scenario failed, and we can also track the
>> percentage of users that got lost on each step.
>>
>> Does this make sense?
>>
>> Dmitry
>>
>>
>> On Mon, Sep 1, 2014 at 4:46 AM, Chanaka Jayasena 
>> wrote:
>>
>>> Use "beforeunload" with jQuery bind to catch this event. It works with
>>> FF, Chrome, and IE 7+ but not supported by Opera. Following is a sample
>>> code.
>>>
>>> $(window).bind('beforeunload', function() {
>>> //put code to save data
>>> return "Give a message to alert the user. Or
>>> simply remove the return statement.";
>>> });
>>>
>>>  thanks,
>>> Chanaka
>>>
>>>
>>> On Mon, Sep 1, 2014 at 3:00 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
 Hi all,

 This feature is almost complete. But facing issues in identifying
 window abandoning events such as hitting the back button of the browser. Is
 there a possible way to do this? Otherwise background saving will have to
 done more frequently and would cause a lot more traffic.

 thanks,
 dimuthu



 On Fri, Aug 8, 2014 at 6:08 PM, Amila Maha Arachchi 
 wrote:

> Hi Dimuthu,
>
> Thanks for the explanation.
>
> With this kind of recording, I see another great advantage. That is to
> lineup all the activities done by a user. If we filter out activities of a
> user and sort them by time we'll get something like
>
> Clicked Create new application -> submitted application creation ->
> clicked application xyz -> clicker open button -> clicked repos and builds
> page etc.
>
>
> On Fri, Aug 1, 2014 at 11:25 PM, Dimuthu Leelarathne <
> dimut...@wso2.com> wrote:
>
>> Hi Amila,
>>
>> This is how you can do it. Let me tell you by example.
>>
>> App creation page loads (we record timestamp here). And only one of
>> the following happens and pls note we record all timestamps.
>>
>> 1 - App creation button clicked
>> OR
>> 2 - Page unloads (meaning user browsed away)
>> OR
>> 3 - You see 2 on the same page messages
>> OR
>> 4 - User hit cacle
>>
>> What you have to do is write queries to figure out which event occur
>> after the app creation page loads - 1,2,3 or 4th. You can also calculate
>> with what probability each of these events occur after app creation page
>> occur. You can also measure average times.
>>
>> thanks,
>> dimuthu
>>
>>
>> On Fri, Aug 1, 2014 at 7:32 PM, Amila Maha Arachchi 
>> wrote:
>>
>>> Hi Dimuthu,
>>>
>>> You have said that we want to know how much time did a user spend on
>>> completing an action. For this you need to publish an event when a 
>>> button
>>> is clicked. And then, how are you going to publish the finished event?
>>>
>>>
>>> On Thu, Jul 31, 2014 at 8:12 PM, Dmitry Sotnikov 
>>> wrote:
>>>
 Looks good. I assume that Timestamp is Date/Time and not just time
 (examples just have time - but I assume this is a typo).

 Dmitry


 On Thu, Jul 31, 2014 at 6:13 PM, Dimuthu Leelarathne <
 dimut...@wso2.com> wrote:

> Hi,
>
> In addition let me give you some samples
>
>
> Tenant Id | Username(email) | 

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dimuthu Leelarathne]

Hi Dmitry,

Yes. It makes perfect sense. But the only problem is current implementation
is not transferring each and every event when it happens. What I do is
record the events and periodically send to the backend. The time period is
large. (note: timestamp is recorded at the browser, so the actual time is
preserved even though recording happens in 2 mins).

So what happens if a person browse away or hit cancel/ok before the next
time slice? We are going to loose some events, unless we use the unload
method. That was why I am looking for it.

Other option is to reduce the time slice but that would increase the
recording period.

Chanaka's solution worked when used properly!

thanks,
dimuthu








On Wed, Sep 3, 2014 at 6:24 AM, Dmitry Sotnikov  wrote:

> Quick thought (maybe not relevant or inferior to the current direction ;)):
>
> Maybe instead of "abandoning events", we concentrate on events that show
> success (and thus detect "failure" is "not achieving success")?
>
> For example, to invite team members you go through the following steps:
> 1. Go to the team invitation page,
> 2. Do something on the page (start filling out the forms to specify the
> usernames/email addresses, roles, etc.),
> 3. Send the invite,
> 4. New member actually accepts and logs in,
> 5. You add the user to an app,
> 6. New member actually does something meaningful.
>
> If we have events for some of these steps but not all the way through #6 -
> we know that the overall scenario failed, and we can also track the
> percentage of users that got lost on each step.
>
> Does this make sense?
>
> Dmitry
>
>
> On Mon, Sep 1, 2014 at 4:46 AM, Chanaka Jayasena  wrote:
>
>> Use "beforeunload" with jQuery bind to catch this event. It works with
>> FF, Chrome, and IE 7+ but not supported by Opera. Following is a sample
>> code.
>>
>> $(window).bind('beforeunload', function() {
>> //put code to save data
>> return "Give a message to alert the user. Or
>> simply remove the return statement.";
>> });
>>
>>  thanks,
>> Chanaka
>>
>>
>> On Mon, Sep 1, 2014 at 3:00 PM, Dimuthu Leelarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> This feature is almost complete. But facing issues in identifying window
>>> abandoning events such as hitting the back button of the browser. Is there
>>> a possible way to do this? Otherwise background saving will have to done
>>> more frequently and would cause a lot more traffic.
>>>
>>> thanks,
>>> dimuthu
>>>
>>>
>>>
>>> On Fri, Aug 8, 2014 at 6:08 PM, Amila Maha Arachchi 
>>> wrote:
>>>
 Hi Dimuthu,

 Thanks for the explanation.

 With this kind of recording, I see another great advantage. That is to
 lineup all the activities done by a user. If we filter out activities of a
 user and sort them by time we'll get something like

 Clicked Create new application -> submitted application creation ->
 clicked application xyz -> clicker open button -> clicked repos and builds
 page etc.


 On Fri, Aug 1, 2014 at 11:25 PM, Dimuthu Leelarathne >>> > wrote:

> Hi Amila,
>
> This is how you can do it. Let me tell you by example.
>
> App creation page loads (we record timestamp here). And only one of
> the following happens and pls note we record all timestamps.
>
> 1 - App creation button clicked
> OR
> 2 - Page unloads (meaning user browsed away)
> OR
> 3 - You see 2 on the same page messages
> OR
> 4 - User hit cacle
>
> What you have to do is write queries to figure out which event occur
> after the app creation page loads - 1,2,3 or 4th. You can also calculate
> with what probability each of these events occur after app creation page
> occur. You can also measure average times.
>
> thanks,
> dimuthu
>
>
> On Fri, Aug 1, 2014 at 7:32 PM, Amila Maha Arachchi 
> wrote:
>
>> Hi Dimuthu,
>>
>> You have said that we want to know how much time did a user spend on
>> completing an action. For this you need to publish an event when a button
>> is clicked. And then, how are you going to publish the finished event?
>>
>>
>> On Thu, Jul 31, 2014 at 8:12 PM, Dmitry Sotnikov 
>> wrote:
>>
>>> Looks good. I assume that Timestamp is Date/Time and not just time
>>> (examples just have time - but I assume this is a typo).
>>>
>>> Dmitry
>>>
>>>
>>> On Thu, Jul 31, 2014 at 6:13 PM, Dimuthu Leelarathne <
>>> dimut...@wso2.com> wrote:
>>>
 Hi,

 In addition let me give you some samples


 Tenant Id | Username(email) | Item | Action  | Timestamp | Context
 (Application) | App Type | Comments
   450 | d...@aha.com | X-Button | Clicked | 12:09:40 | app1 | WAR |
 Additional data (optional)
  780 | d...@man.com | url of home page | loaded | 12:10:50 | none |
 no

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Amila De Silva]

Hi Chamila,

I think you have to start the TenantFlow and set the ID for the tenant
correctly before fetching the configuration. In the method
jsFunction_resumeWorkflow, this is done by calling
PrivilegedCarbonContext.startTenantFlow();

PrivilegedCarbonContext.getThreadLocalCarbonContext().setTenantDomain(tenantDomain,
true);



On Wed, Sep 3, 2014 at 10:47 PM, Chamila Adhikarinayake 
wrote:

> Actually the tasks are created with that executor for other tenants as
> well. but not inside the correct tenant domain in the BPS. They are created
> in carbon.super tenant domain and the related task can be viewed in
> workflow-admin ui only by login as super user.
>
> following is the reason I think that causes this.
>
> In the method jsFunction_addUser() in APIStoreHostObject following code is
> there to create the workflow
>
> WorkflowExecutor userSignUpWFExecutor =
> WorkflowExecutorFactory.getInstance()
>
> .getWorkflowExecutor(WorkflowConstants.WF_TYPE_AM_USER_SIGNUP);
>
> This WorkflowExecutor is created using carbon.super user configuration
> information in the registry. In the 'getWorkflowConfigurations()' method in
> WorkflowExecutorFactory class
> PrivilegedCarbonContext.getThreadLocalCarbonContext().getTenantDomain(); is
> used to get the domain name. (aslo tenant id). So even though there is a
> different tenant domain, these values do not change. So superuser conf is
> used and  the request is sent to the carbon.super tenant in BPS. not to the
> tenant's one. So I'm working on passing the correct domain info to this
>
>
> On Wed, Sep 3, 2014 at 9:06 PM, Nuwan Dias  wrote:
>
>> On Wed, Sep 3, 2014 at 9:02 PM, Chamila Adhikarinayake > > wrote:
>>
>>> Hi all,
>>> I'm creating user self signup feature for tenant store in API Manager.
>>> Current api manager provides only self signup facility for carbon.super
>>> store. To add tenant users, tenant admin has to manually add it through the
>>> carbon console.
>>>
>>> Following parts will be implemented
>>>
>>> *UI changes* (see attached images)
>>>
>>> 1. enable the sign-up button for tenant user store
>>> 2. add the domain name extension for the user name field in the user
>>> registration form. (this is appended to the user name)
>>>
>>> *User roles for tenants *
>>>
>>> Tenant signup configuration will be moved to the registry location
>>> '/_system/governance/repository/identity/sign-up-config'. This part is
>>> already implemented by Shariq for a IS component(See discussion in the
>>> thread "Provide support for self signup for tenants' APIStores" for more
>>> info on the configuration). But this resource needed to be created
>>> manually. So as a part of the implementation, This resource will be added
>>> with default values when creating a tenant. Default value will be
>>>
>>> 
>>>PRIMARY
>>>
>>>   subscriber
>>>   false
>>>
>>> 
>>>
>>>
>>> *Modification to current work-flow for tenant sign-up. *
>>>
>>> The current implemented method does not work when
>>> UserSignUpWSWorkflowExecutor is used in the work-flow. this can be only
>>> used with tenants signups for superuser. Existing code uses configuration
>>> in the carbon super user's registry entry
>>> '/_system/governance/apimgt/applicationdata/workflow-extensions.xml' for
>>> tenants as well ( see jsFunction_addUser() in
>>> org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject class. ). When
>>> registering a tenant user for different tenant, configuration in the
>>> tenant's workflow-extensions.xml needed to be used.
>>>
>>> I have implemented basic functionality[1] as requested by AmilaM (Users
>>> can signup for tenant stores. But Tenant admin has to manually add the
>>> registry entry with user roles to the given location. If this entry is not
>>> there, a default 'identity' user role is assigned to the user.  Only
>>> UserSignUpSimpleWorkflowExecutor for the workflow can be used with this. If
>>> UserSignUpWSWorkflowExecutor is used to connect to the BPS, the tenant
>>> approval tasks are not created properly)
>>>
>>
>> Do we know the reason for the tasks of the BPS not being created when the
>> UserSignUpWSWorkflowExecutor is used? We will need to dig into that IMO.
>>
>>>
>>> [1] https://wso2.org/jira/browse/APIMANAGER-2785
>>>
>>> Comments are highly appreciated
>>> Thanks,
>>> Chamila.
>>>
>>> --
>>> Regards,
>>> Chamila Adhikarinayake
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile - +94712346437
>>> Email  - chami...@wso2.com
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Associate Tech Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
>



-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Chamila Adhikarinayake]

Actually the tasks are created with that executor for other tenants as
well. but not inside the correct tenant domain in the BPS. They are created
in carbon.super tenant domain and the related task can be viewed in
workflow-admin ui only by login as super user.

following is the reason I think that causes this.

In the method jsFunction_addUser() in APIStoreHostObject following code is
there to create the workflow

WorkflowExecutor userSignUpWFExecutor =
WorkflowExecutorFactory.getInstance()

.getWorkflowExecutor(WorkflowConstants.WF_TYPE_AM_USER_SIGNUP);

This WorkflowExecutor is created using carbon.super user configuration
information in the registry. In the 'getWorkflowConfigurations()' method in
WorkflowExecutorFactory class
PrivilegedCarbonContext.getThreadLocalCarbonContext().getTenantDomain(); is
used to get the domain name. (aslo tenant id). So even though there is a
different tenant domain, these values do not change. So superuser conf is
used and  the request is sent to the carbon.super tenant in BPS. not to the
tenant's one. So I'm working on passing the correct domain info to this


On Wed, Sep 3, 2014 at 9:06 PM, Nuwan Dias  wrote:

> On Wed, Sep 3, 2014 at 9:02 PM, Chamila Adhikarinayake 
> wrote:
>
>> Hi all,
>> I'm creating user self signup feature for tenant store in API Manager.
>> Current api manager provides only self signup facility for carbon.super
>> store. To add tenant users, tenant admin has to manually add it through the
>> carbon console.
>>
>> Following parts will be implemented
>>
>> *UI changes* (see attached images)
>>
>> 1. enable the sign-up button for tenant user store
>> 2. add the domain name extension for the user name field in the user
>> registration form. (this is appended to the user name)
>>
>> *User roles for tenants *
>>
>> Tenant signup configuration will be moved to the registry location
>> '/_system/governance/repository/identity/sign-up-config'. This part is
>> already implemented by Shariq for a IS component(See discussion in the
>> thread "Provide support for self signup for tenants' APIStores" for more
>> info on the configuration). But this resource needed to be created
>> manually. So as a part of the implementation, This resource will be added
>> with default values when creating a tenant. Default value will be
>>
>> 
>>PRIMARY
>>
>>   subscriber
>>   false
>>
>> 
>>
>>
>> *Modification to current work-flow for tenant sign-up. *
>>
>> The current implemented method does not work when
>> UserSignUpWSWorkflowExecutor is used in the work-flow. this can be only
>> used with tenants signups for superuser. Existing code uses configuration
>> in the carbon super user's registry entry
>> '/_system/governance/apimgt/applicationdata/workflow-extensions.xml' for
>> tenants as well ( see jsFunction_addUser() in
>> org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject class. ). When
>> registering a tenant user for different tenant, configuration in the
>> tenant's workflow-extensions.xml needed to be used.
>>
>> I have implemented basic functionality[1] as requested by AmilaM (Users
>> can signup for tenant stores. But Tenant admin has to manually add the
>> registry entry with user roles to the given location. If this entry is not
>> there, a default 'identity' user role is assigned to the user.  Only
>> UserSignUpSimpleWorkflowExecutor for the workflow can be used with this. If
>> UserSignUpWSWorkflowExecutor is used to connect to the BPS, the tenant
>> approval tasks are not created properly)
>>
>
> Do we know the reason for the tasks of the BPS not being created when the
> UserSignUpWSWorkflowExecutor is used? We will need to dig into that IMO.
>
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-2785
>>
>> Comments are highly appreciated
>> Thanks,
>> Chamila.
>>
>> --
>> Regards,
>> Chamila Adhikarinayake
>> Software Engineer
>> WSO2, Inc.
>> Mobile - +94712346437
>> Email  - chami...@wso2.com
>>
>
>
>
> --
> Nuwan Dias
>
> Associate Tech Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

Excellent news, Manisha!

I am in Colombo starting Tue, Sept 9 - so demos and sync-ups will be quite
easy. :)

Dmitry


On Tue, Sep 2, 2014 at 11:46 PM, Manisha Gayathri  wrote:

> Hi Dmitry,
>
> Since Gayan is in support now, I will continue to work on this.
> The doc attached, contains the items completed by Gayan so far.
>
> I will be able to do a demo on next Monday with the completed items. And
> we will be able to ship the completed feature for M6.
>
> Thanks
> Manisha
>
>
>
> On Fri, Aug 15, 2014 at 7:18 AM, Gayan Dhanushka  wrote:
>
>> Hi Dmitry,
>>
>> I have scheduled a demo o Monday. I will do a sample implementation of
>> the two scenarios and give a demo to you on Monday.
>>
>> GayanD
>>
>>
>> On Fri, Aug 15, 2014 at 1:05 AM, Dmitry Sotnikov  wrote:
>>
>>> Yes, some sort of PoC would be good. I am not sure what you mean by
>>> showing the Type B messages on the page - so would be great to see it in
>>> action or at least on mockups...
>>> On Aug 14, 2014 8:02 PM, "Dimuthu Leelarathne" 
>>> wrote:
>>>
 Hi Dmitry,

 Please see my comments inline.


 On Thu, Aug 14, 2014 at 12:17 PM, Dmitry Sotnikov 
 wrote:

> Gayan and Dimuthu,
>
> From my perspective, one-off UX exceptions are bad, because they make
> the UI inconsistent.
>
> There are two types of messages:
> A. High-level external notifications of someone taking some action
> (e.g. "John created a new app") and
> B. Low-level ongoing processes happening in AF as result of what the
> current user clicks ("Creating initial GIT repository", etc.)
>
> Type A are more social and shown across team, and only when something
> is actually successfully finished.
>
> Spinning wheels / progress indications are only relevant to type B.
> These messages are only related to the current particular user and show
> work in progress, starting immediately once the user clicks something.
>
> So from my perspective, either we show both types in one pane, or have
> two different panes (or other UX metaphors) for the two types.
>

 What I am suggesting is a different approach. Which is to show the type
 B messages on the page itself where the information is related. For example
 the fact that build is in progress should be on the Build & Repo page
 itself. What if we do a POC for the same scenario

 1 - on the wall
 2 - on the page

 And see which is user friendly? I agree two panes are not going to be a
 good solution.

 thanks,
 dimuthu


> My understanding is that the current idea is to try to re-use the same
> App Wall for everything, right?
>
> Dmitry
>
>
>
> On Thu, Aug 14, 2014 at 9:39 AM, Gayan Dhanushka 
> wrote:
>
>> Hi Dimuthu,
>>
>> I tried a sample implementation to show the implementation on the
>> application wall. This was done by looking at the content of the message.
>> It was successful. But this may not be ideal since for different kind of
>> start-inprogress-ended messages we may need to have different logic.
>>
>> Meanwhile I can share some wire frames of the approach suggested
>> above to show the in progress activities on the pages themselves.
>>
>> Thanks
>> GayanD
>>
>>
>> On Thu, Aug 14, 2014 at 4:43 AM, Dimuthu Leelarathne <
>> dimut...@wso2.com> wrote:
>>
>>> Hi Gayan,
>>>
>>>
>>> On Wed, Aug 13, 2014 at 2:28 PM, Gayan Dhanushka 
>>> wrote:
>>>
 Hi Dimuthu,

 Following are a set of actions that we want to give
 "started-inprogress-ended" messages and places where we would put the
 spinning wheel and messages.

 1) Application Creation - User home near the application thumbnail
 (This is already implemented)
 2) Application Upload - Application creation page (This is already
 implemented. Spinning wheel is shown on the application creation page 
 until
 the application is uploaded)
 3) Build - Repos Builds page near last build status
 4) Deployment - Repos Builds page near last deploy id
 5) Promote / Demote - Lifecycle page under the particular version

 I am tentative on having an in progress state for resource creation
 since it does not take much time.


>>> It doesn't take much time in Dev setups. But takes considerable time
>>> in Cloud. I think for resources we need to give "started" and "ended"
>>> messages.
>>>
>>> @ Dmitry: What do you think about the new proposal? Giving
>>> progress-reporting on the page itself, rather than on the wall?
>>>
>>> We can do some wireframes and then can finalise. WDYT?
>>>
>>> thanks,
>>> dimuthu
>>>
>>>
>>> What are your thoughts?

 Regards
 Gayan
>>>

Re: [Architecture] AppFactory Custom URL improvement

[Udara Liyanage]

Touched, not typed. Erroneous words are a feature, not a typo.
On Sep 3, 2014 5:56 PM, "Samith Dassanayake"  wrote:
>
> Hi, I have started working on the $subject[1] and it will be done in two
phases
>
> Phase 1: Improve the usability
> In current implementation there are around 7 usability issues. Most of
these issues are caused due to, there is no proper indication of what is
happening when a user add or update a custom subdomain. For example when a
user adds a new custom subdomain and if it is failed, the error message
does not specify whether issue is caused due to the unavailability of
the subdomain or due to an internal server error etc... This is because
currently we are not checking whether requested URL is available or not,
before adding it. Therefore we will improve the behavior to reflect the
status(whether the mapping is in progress,  successful or unsuccessful) by
checking existence of the requested custom URL before adding or updating in
thread safe manner.

When a client call AddDomain REST API, it send a response with back end
error message in case API call fail for some reason. Is it possible to
display this error message so user get a better knowledge of what went
wrong.

Since there is no Update method for domain mapping from Stratos front, we
will remove and add when there is an update request, until update method is
available from Stratos side.

This should be added to Stratos. Could you please create a jira in Stratos
so update method will be implemented in next release.
>
> As an another improvement when one version is in production, we will make
it to be the one with the production URL. This will happen based on two
scenarios.
> 1. When promoting from Testing stage to Production, if there is no
version in production and production URL is specified, promoted version
will be mapped to the production URL based on the permissions granted to
the user.
> 2. When adding(or updating) a production URL, if there is a single
version(deployed) in Production stage, that version will be mapped to the
production URL.
>
> Currently If custom URL is not mapped to any version, when we go to
the URL it will respond with the status 404 since it is not mapped yet. We
will improve this behavior such that If the production URL is not mapped to
a version, we will map the URL to a page from WSO2  explaining that
the URL will go live once it is moved to production and with the further
instructions.
>
>
> Phase 2 : Support for complete custom URL
> In current implementation users can only specify the subdomain of the
custom URL, which will be mapped under the domain wso2apps.com. In the 2nd
phase we will allow users to add complete custom URL by having  domain
owner verification before setting up the custom domain. On app creation, we
will assign a production URL by default, in the format of
appid.tenantdomain.wso2apps.com and users can change the URL as they want,
based on the permissions and validity of the domain. I will update more on
this when this phase is started.
>
> [1] https://redmine.wso2.com/issues/3187
>
> Thanks,
> Samith
>
> --
> Best Regards
>
> Samith Dassanayake
> Software Engineer, WSO2 Inc.
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Nuwan Dias]

On Wed, Sep 3, 2014 at 9:02 PM, Chamila Adhikarinayake 
wrote:

> Hi all,
> I'm creating user self signup feature for tenant store in API Manager.
> Current api manager provides only self signup facility for carbon.super
> store. To add tenant users, tenant admin has to manually add it through the
> carbon console.
>
> Following parts will be implemented
>
> *UI changes* (see attached images)
>
> 1. enable the sign-up button for tenant user store
> 2. add the domain name extension for the user name field in the user
> registration form. (this is appended to the user name)
>
> *User roles for tenants *
>
> Tenant signup configuration will be moved to the registry location
> '/_system/governance/repository/identity/sign-up-config'. This part is
> already implemented by Shariq for a IS component(See discussion in the
> thread "Provide support for self signup for tenants' APIStores" for more
> info on the configuration). But this resource needed to be created
> manually. So as a part of the implementation, This resource will be added
> with default values when creating a tenant. Default value will be
>
> 
>PRIMARY
>
>   subscriber
>   false
>
> 
>
>
> *Modification to current work-flow for tenant sign-up. *
>
> The current implemented method does not work when
> UserSignUpWSWorkflowExecutor is used in the work-flow. this can be only
> used with tenants signups for superuser. Existing code uses configuration
> in the carbon super user's registry entry
> '/_system/governance/apimgt/applicationdata/workflow-extensions.xml' for
> tenants as well ( see jsFunction_addUser() in
> org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject class. ). When
> registering a tenant user for different tenant, configuration in the
> tenant's workflow-extensions.xml needed to be used.
>
> I have implemented basic functionality[1] as requested by AmilaM (Users
> can signup for tenant stores. But Tenant admin has to manually add the
> registry entry with user roles to the given location. If this entry is not
> there, a default 'identity' user role is assigned to the user.  Only
> UserSignUpSimpleWorkflowExecutor for the workflow can be used with this. If
> UserSignUpWSWorkflowExecutor is used to connect to the BPS, the tenant
> approval tasks are not created properly)
>

Do we know the reason for the tasks of the BPS not being created when the
UserSignUpWSWorkflowExecutor is used? We will need to dig into that IMO.

>
> [1] https://wso2.org/jira/browse/APIMANAGER-2785
>
> Comments are highly appreciated
> Thanks,
> Chamila.
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
>



-- 
Nuwan Dias

Associate Tech Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Kernel][MB] Request to upgrade H2 DB version from 1.2.140 to 1.3.175 or above

[Gayashan Amarasinghe]

Hi Asitha,

+1 for updating the H2 version. In fact we are looking into the process of
updating the 3rd party libraries in carbon 4.3.0. As a result H2 database
will also be updated.

Thanks.
/Gayashan


On Wed, Sep 3, 2014 at 6:13 PM, Asitha Nanayakkara  wrote:

> Hi
>
> For WSO2 MB 3.0.0 H2 message store implementation we require the support
> for ON DUPLICATE KEY UPDATE (similar to MySQL) function. This functionality
> is available in H2 version 1.3.175 onward[1].
>
> Currently in carbon kernel we use H2 version 1.2.140. Shall we upgrade the
> H2 version in carbon 4.3.0?
>
> [1] http://www.h2database.com/html/changelog.html
>
> Thanks
> --
> *Asitha Nanayakkara*
> Software Engineer
> WSO2, Inc. http://wso2.com/
> Mob: + 94 77 85 30 682
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Gayashan Amarasinghe*
Software Engineer | Platform TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +94718314517
Blog : gayashan-a.blogspot.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [Kernel][MB] Request to upgrade H2 DB version from 1.2.140 to 1.3.175 or above

[Asitha Nanayakkara]

Hi

For WSO2 MB 3.0.0 H2 message store implementation we require the support
for ON DUPLICATE KEY UPDATE (similar to MySQL) function. This functionality
is available in H2 version 1.3.175 onward[1].

Currently in carbon kernel we use H2 version 1.2.140. Shall we upgrade the
H2 version in carbon 4.3.0?

[1] http://www.h2database.com/html/changelog.html

Thanks
-- 
*Asitha Nanayakkara*
Software Engineer
WSO2, Inc. http://wso2.com/
Mob: + 94 77 85 30 682
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] AppFactory Custom URL improvement

[Samith Dassanayake]

Hi, I have started working on the $subject[1] and it will be done in two
phases

*Phase 1: Improve the usability*
In current implementation there are around 7 usability issues. Most of
these issues are caused due to, there is no proper indication of what is
happening when a user add or update a custom subdomain. For example when a
user adds a new custom subdomain and if it is failed, the error message
does not specify whether issue is caused due to the unavailability of
the subdomain or due to an internal server error etc... This is because
currently we are not checking whether requested URL is available or not,
before adding it. Therefore we will improve the behavior to reflect the
status(whether the mapping is in progress,  successful or unsuccessful) by
checking existence of the requested custom URL before adding or updating in
thread safe manner. Since there is no Update method for domain mapping from
Stratos front, we will remove and add when there is an update request,
until update method is available from Stratos side.

As an another improvement when one version is in production, we will make
it to be the one with the production URL. This will happen based on two
scenarios.
1. When promoting from Testing stage to Production, if there is no version
in production and production URL is specified, promoted version will be
mapped to the production URL based on the permissions granted to the user.
 2. When adding(or updating) a production URL, if there is a single
version(deployed) in Production stage, that version will be mapped to the
production URL.

Currently If custom URL is not mapped to any version, when we go to
the URL it will respond with the status 404 since it is not mapped yet. We
will improve this behavior such that If the production URL is not mapped to
a version, we will map the URL to a page from WSO2  explaining that
the URL will go live once it is moved to production and with the further
instructions.


*Phase 2 : Support for complete custom URL*
In current implementation users can only specify the subdomain of the
custom URL, which will be mapped under the domain wso2apps.com. In the 2nd
phase we will allow users to add complete custom URL by having  domain
owner verification before setting up the custom domain. On app creation, we
will assign a production URL by default, in the format of
appid.tenantdomain.wso2apps.com and users can change the URL as they want,
based on the permissions and validity of the domain. I will update more on
this when this phase is started.

[1] https://redmine.wso2.com/issues/3187

Thanks,
Samith

-- 
Best Regards

Samith Dassanayake
Software Engineer, WSO2 Inc.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Process Store for text based process

[Manfred Herrmann]

Hi Shiva,

a "process store" sounds like a store for "business process
definition/documentation". I am wrong?

If it is a "store for business process documentation", some questions about:

Is the main requirement of the stakeholder based on "easy access to process
definitions/documentation" for all employees?

What is a "text based process", "process model" and a "instance of a
process"?

How would you compare the "BPM process definition" (like bpmn and bpel)
with "text based process"?


Thank you very much


2014-09-03 12:43 GMT+02:00 Shiva Balachandran :

> Hi Sameera,
>
> We are currently looking at a single process model, which is text based
> processes therefore there will be one single asset type, Processes. People
> can create processes of this type and perform functions such as creating,
> viewing, associating and other functionality.
>
> Thank you.
>
>
>
> On Wed, Sep 3, 2014 at 3:22 PM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Hi Chathura,
>>
>> Will there be two asset types managed by the ES? (Process Models and
>> Processes)
>>
>> *Process Models*
>> - Created and managed by Process Model designers
>> - Visible in the store
>> - Can be extended by users by specifying a parent process model
>>   - Will this extended process model be stored as a new process model?
>> - Can original process model be modified by users?
>>
>> *Processes*
>> - Created from process models in the Store
>> - Created and managed by process consumers?
>> - Visible in the Store
>>
>> *Types of users*
>> - Process Model Designers
>> - Process Model Consumers?
>> - Process Consumers (Who is anyone that visits the Store front)
>>
>> Thank You,
>> Sameera
>>
>>
>> On Wed, Sep 3, 2014 at 2:52 PM, Chathura Ekanayake 
>> wrote:
>>
>>>
>>> On Wed, Sep 3, 2014 at 2:23 PM, Sameera Medagammaddegedara <
>>> samee...@wso2.com> wrote:
>>>
 Hi Shiva and Chathura,


 The processes will be built as an asset type of the Enterprise Store as
> discussed and the utility functions of the store such as adding, editing,
> viewing, searching and visualizing will be done in the store front rather
> than navigating to the publisher.
>
 Currently there are no utility methods in the Store app code base that
 will allow you to provide adding and editing capabilities.However,this can
 be done by using the carbon module which is provided with the ES.


 As Shiva has mentioned, we want to do both adding and displaying
> process models in the same UI, diverting from the current model of ES to
> have a separate publisher and a store
>
 Who will maintain and control the original version of the process? Will
 processes have a defined lifecycle?

>>>
>>>  Processes can be viewed, edited and deleted by any user with relevant
>>> permissions. Yes, processes have a lifecycle.
>>>
>>>
 An example requirement would be: a user browsing a process model may
> want to add some details to certain sections of the model, so that he
> should be able to do it from the same UI. Similarly, a user may want to 
> add
> a specialized version of a currently displaying model
>
 Would it be possible to model this as a user selecting a process then
 creating an instance of it with his own customizations? Where will these
 customizations be stored?

>>>
>>> This will not create a process instance. This scenario is creating a new
>>> process model by adding details to an existing model. The new model will
>>> also be stored in the store and the user has the option to add an
>>> association stating that this is a specialization of the previous model.
>>>
>>>

 Will there be two classes of users?
 - Process designers who create and publish the process
 - Process consumers that take a process ,create an instance of it
 ,configure or customize it and then combine it with other processes?

>>>
>>> There are process consumers (i.e. process participants) who most of the
>>> time just view the processes. However, other stakeholders (i.e. process
>>> designers, management staff, business analysts, etc.) may want to perform
>>> actions like view, navigate, visualize, analyze, edit and add process
>>> models.
>>>
>>>
>>>

 Thank You,
 Sameera


 On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
 wrote:

> As Shiva has mentioned, we want to do both adding and displaying
> process models in the same UI, diverting from the current model of ES to
> have a separate publisher and a store. An example requirement would be: a
> user browsing a process model may want to add some details to certain
> sections of the model, so that he should be able to do it from the same 
> UI.
> Similarly, a user may want to add a specialized version of a currently
> displaying model. Therefore, I think the adding/editing functionality has
> to be provided in the same UI, controlled by user'

Re: [Architecture] Process Store for text based process

[Shiva Balachandran]

Hi Sameera,

We are currently looking at a single process model, which is text based
processes therefore there will be one single asset type, Processes. People
can create processes of this type and perform functions such as creating,
viewing, associating and other functionality.

Thank you.



On Wed, Sep 3, 2014 at 3:22 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Hi Chathura,
>
> Will there be two asset types managed by the ES? (Process Models and
> Processes)
>
> *Process Models*
> - Created and managed by Process Model designers
> - Visible in the store
> - Can be extended by users by specifying a parent process model
>   - Will this extended process model be stored as a new process model?
> - Can original process model be modified by users?
>
> *Processes*
> - Created from process models in the Store
> - Created and managed by process consumers?
> - Visible in the Store
>
> *Types of users*
> - Process Model Designers
> - Process Model Consumers?
> - Process Consumers (Who is anyone that visits the Store front)
>
> Thank You,
> Sameera
>
>
> On Wed, Sep 3, 2014 at 2:52 PM, Chathura Ekanayake 
> wrote:
>
>>
>> On Wed, Sep 3, 2014 at 2:23 PM, Sameera Medagammaddegedara <
>> samee...@wso2.com> wrote:
>>
>>> Hi Shiva and Chathura,
>>>
>>>
>>> The processes will be built as an asset type of the Enterprise Store as
 discussed and the utility functions of the store such as adding, editing,
 viewing, searching and visualizing will be done in the store front rather
 than navigating to the publisher.

>>> Currently there are no utility methods in the Store app code base that
>>> will allow you to provide adding and editing capabilities.However,this can
>>> be done by using the carbon module which is provided with the ES.
>>>
>>>
>>> As Shiva has mentioned, we want to do both adding and displaying process
 models in the same UI, diverting from the current model of ES to have a
 separate publisher and a store

>>> Who will maintain and control the original version of the process? Will
>>> processes have a defined lifecycle?
>>>
>>
>>  Processes can be viewed, edited and deleted by any user with relevant
>> permissions. Yes, processes have a lifecycle.
>>
>>
>>> An example requirement would be: a user browsing a process model may
 want to add some details to certain sections of the model, so that he
 should be able to do it from the same UI. Similarly, a user may want to add
 a specialized version of a currently displaying model

>>> Would it be possible to model this as a user selecting a process then
>>> creating an instance of it with his own customizations? Where will these
>>> customizations be stored?
>>>
>>
>> This will not create a process instance. This scenario is creating a new
>> process model by adding details to an existing model. The new model will
>> also be stored in the store and the user has the option to add an
>> association stating that this is a specialization of the previous model.
>>
>>
>>>
>>> Will there be two classes of users?
>>> - Process designers who create and publish the process
>>> - Process consumers that take a process ,create an instance of it
>>> ,configure or customize it and then combine it with other processes?
>>>
>>
>> There are process consumers (i.e. process participants) who most of the
>> time just view the processes. However, other stakeholders (i.e. process
>> designers, management staff, business analysts, etc.) may want to perform
>> actions like view, navigate, visualize, analyze, edit and add process
>> models.
>>
>>
>>
>>>
>>> Thank You,
>>> Sameera
>>>
>>>
>>> On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
>>> wrote:
>>>
 As Shiva has mentioned, we want to do both adding and displaying
 process models in the same UI, diverting from the current model of ES to
 have a separate publisher and a store. An example requirement would be: a
 user browsing a process model may want to add some details to certain
 sections of the model, so that he should be able to do it from the same UI.
 Similarly, a user may want to add a specialized version of a currently
 displaying model. Therefore, I think the adding/editing functionality has
 to be provided in the same UI, controlled by user's authorizations.

 Regards,
 Chathura


 On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran 
 wrote:

> Hi All,
>
> The Enterprise Store currently satisfies necessity to host
> applications, gadgets and eBooks. Users are able to add new assets of the
> given type or create their own asset type and work with the store. A
> requirement has arose to develop a Process Store to host processes of all
> types and visualize associations with processes whilst providing other
> utility functions. I am currently working on building a Process Store to
> address the requirement.
>
> After discussion with the stakeholder we have agre

Re: [Architecture] Process Store for text based process

[Sameera Medagammaddegedara]

Hi Chathura,

Will there be two asset types managed by the ES? (Process Models and
Processes)

*Process Models*
- Created and managed by Process Model designers
- Visible in the store
- Can be extended by users by specifying a parent process model
  - Will this extended process model be stored as a new process model?
- Can original process model be modified by users?

*Processes*
- Created from process models in the Store
- Created and managed by process consumers?
- Visible in the Store

*Types of users*
- Process Model Designers
- Process Model Consumers?
- Process Consumers (Who is anyone that visits the Store front)

Thank You,
Sameera


On Wed, Sep 3, 2014 at 2:52 PM, Chathura Ekanayake 
wrote:

>
> On Wed, Sep 3, 2014 at 2:23 PM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Hi Shiva and Chathura,
>>
>>
>> The processes will be built as an asset type of the Enterprise Store as
>>> discussed and the utility functions of the store such as adding, editing,
>>> viewing, searching and visualizing will be done in the store front rather
>>> than navigating to the publisher.
>>>
>> Currently there are no utility methods in the Store app code base that
>> will allow you to provide adding and editing capabilities.However,this can
>> be done by using the carbon module which is provided with the ES.
>>
>>
>> As Shiva has mentioned, we want to do both adding and displaying process
>>> models in the same UI, diverting from the current model of ES to have a
>>> separate publisher and a store
>>>
>> Who will maintain and control the original version of the process? Will
>> processes have a defined lifecycle?
>>
>
> Processes can be viewed, edited and deleted by any user with relevant
> permissions. Yes, processes have a lifecycle.
>
>
>> An example requirement would be: a user browsing a process model may want
>>> to add some details to certain sections of the model, so that he should be
>>> able to do it from the same UI. Similarly, a user may want to add a
>>> specialized version of a currently displaying model
>>>
>> Would it be possible to model this as a user selecting a process then
>> creating an instance of it with his own customizations? Where will these
>> customizations be stored?
>>
>
> This will not create a process instance. This scenario is creating a new
> process model by adding details to an existing model. The new model will
> also be stored in the store and the user has the option to add an
> association stating that this is a specialization of the previous model.
>
>
>>
>> Will there be two classes of users?
>> - Process designers who create and publish the process
>> - Process consumers that take a process ,create an instance of it
>> ,configure or customize it and then combine it with other processes?
>>
>
> There are process consumers (i.e. process participants) who most of the
> time just view the processes. However, other stakeholders (i.e. process
> designers, management staff, business analysts, etc.) may want to perform
> actions like view, navigate, visualize, analyze, edit and add process
> models.
>
>
>
>>
>> Thank You,
>> Sameera
>>
>>
>> On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
>> wrote:
>>
>>> As Shiva has mentioned, we want to do both adding and displaying process
>>> models in the same UI, diverting from the current model of ES to have a
>>> separate publisher and a store. An example requirement would be: a user
>>> browsing a process model may want to add some details to certain sections
>>> of the model, so that he should be able to do it from the same UI.
>>> Similarly, a user may want to add a specialized version of a currently
>>> displaying model. Therefore, I think the adding/editing functionality has
>>> to be provided in the same UI, controlled by user's authorizations.
>>>
>>> Regards,
>>> Chathura
>>>
>>>
>>> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran 
>>> wrote:
>>>
 Hi All,

 The Enterprise Store currently satisfies necessity to host
 applications, gadgets and eBooks. Users are able to add new assets of the
 given type or create their own asset type and work with the store. A
 requirement has arose to develop a Process Store to host processes of all
 types and visualize associations with processes whilst providing other
 utility functions. I am currently working on building a Process Store to
 address the requirement.

 After discussion with the stakeholder we have agreed to initially build
 the store as an extension of the enterprise store and move the process
 store out as an product in the future. The extension to be built will be
 for textual based processes and in future will be able to support other
 type of processes too.

 The extension to be built will have the following functionality:-


- Adding a text based process
- Editing a text based process
- View a text based process
- Search for a text based process

>>

Re: [Architecture] Process Store for text based process

[Chathura Ekanayake]

On Wed, Sep 3, 2014 at 2:23 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Hi Shiva and Chathura,
>
>
> The processes will be built as an asset type of the Enterprise Store as
>> discussed and the utility functions of the store such as adding, editing,
>> viewing, searching and visualizing will be done in the store front rather
>> than navigating to the publisher.
>>
> Currently there are no utility methods in the Store app code base that
> will allow you to provide adding and editing capabilities.However,this can
> be done by using the carbon module which is provided with the ES.
>
>
> As Shiva has mentioned, we want to do both adding and displaying process
>> models in the same UI, diverting from the current model of ES to have a
>> separate publisher and a store
>>
> Who will maintain and control the original version of the process? Will
> processes have a defined lifecycle?
>

Processes can be viewed, edited and deleted by any user with relevant
permissions. Yes, processes have a lifecycle.


> An example requirement would be: a user browsing a process model may want
>> to add some details to certain sections of the model, so that he should be
>> able to do it from the same UI. Similarly, a user may want to add a
>> specialized version of a currently displaying model
>>
> Would it be possible to model this as a user selecting a process then
> creating an instance of it with his own customizations? Where will these
> customizations be stored?
>

This will not create a process instance. This scenario is creating a new
process model by adding details to an existing model. The new model will
also be stored in the store and the user has the option to add an
association stating that this is a specialization of the previous model.


>
> Will there be two classes of users?
> - Process designers who create and publish the process
> - Process consumers that take a process ,create an instance of it
> ,configure or customize it and then combine it with other processes?
>

There are process consumers (i.e. process participants) who most of the
time just view the processes. However, other stakeholders (i.e. process
designers, management staff, business analysts, etc.) may want to perform
actions like view, navigate, visualize, analyze, edit and add process
models.



>
> Thank You,
> Sameera
>
>
> On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
> wrote:
>
>> As Shiva has mentioned, we want to do both adding and displaying process
>> models in the same UI, diverting from the current model of ES to have a
>> separate publisher and a store. An example requirement would be: a user
>> browsing a process model may want to add some details to certain sections
>> of the model, so that he should be able to do it from the same UI.
>> Similarly, a user may want to add a specialized version of a currently
>> displaying model. Therefore, I think the adding/editing functionality has
>> to be provided in the same UI, controlled by user's authorizations.
>>
>> Regards,
>> Chathura
>>
>>
>> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran 
>> wrote:
>>
>>> Hi All,
>>>
>>> The Enterprise Store currently satisfies necessity to host
>>> applications, gadgets and eBooks. Users are able to add new assets of the
>>> given type or create their own asset type and work with the store. A
>>> requirement has arose to develop a Process Store to host processes of all
>>> types and visualize associations with processes whilst providing other
>>> utility functions. I am currently working on building a Process Store to
>>> address the requirement.
>>>
>>> After discussion with the stakeholder we have agreed to initially build
>>> the store as an extension of the enterprise store and move the process
>>> store out as an product in the future. The extension to be built will be
>>> for textual based processes and in future will be able to support other
>>> type of processes too.
>>>
>>> The extension to be built will have the following functionality:-
>>>
>>>
>>>- Adding a text based process
>>>- Editing a text based process
>>>- View a text based process
>>>- Search for a text based process
>>>
>>>
>>>- Associate existing text based process to a new variant - The user
>>>when adding a new process can associate the new process to a existing one
>>>if the new process is a variant or similar to the existing process but a
>>>variant.
>>>
>>>
>>>- Navigating processes through associations - The user can navigate
>>>through the associations to find similar processes or their variants.
>>>
>>>
>>>- Visualizing associations in graph views - The associations between
>>>the processes will be sketched or depicted. This will be developed using
>>>JSPlumb.
>>>
>>> The processes will be built as an asset type of the Enterprise Store as
>>> discussed and the utility functions of the store such as adding, editing,
>>> viewing, searching and visualizing will be done in the store front rather
>>

Re: [Architecture] Process Store for text based process

[Sameera Medagammaddegedara]

Hi Shiva and Chathura,

The processes will be built as an asset type of the Enterprise Store as
> discussed and the utility functions of the store such as adding, editing,
> viewing, searching and visualizing will be done in the store front rather
> than navigating to the publisher.
>
Currently there are no utility methods in the Store app code base that will
allow you to provide adding and editing capabilities.However,this can be
done by using the carbon module which is provided with the ES.

As Shiva has mentioned, we want to do both adding and displaying process
> models in the same UI, diverting from the current model of ES to have a
> separate publisher and a store
>
Who will maintain and control the original version of the process? Will
processes have a defined lifecycle?

An example requirement would be: a user browsing a process model may want
> to add some details to certain sections of the model, so that he should be
> able to do it from the same UI. Similarly, a user may want to add a
> specialized version of a currently displaying model
>
Would it be possible to model this as a user selecting a process then
creating an instance of it with his own customizations? Where will these
customizations be stored?

Will there be two classes of users?
- Process designers who create and publish the process
- Process consumers that take a process ,create an instance of it
,configure or customize it and then combine it with other processes?

Thank You,
Sameera


On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake 
wrote:

> As Shiva has mentioned, we want to do both adding and displaying process
> models in the same UI, diverting from the current model of ES to have a
> separate publisher and a store. An example requirement would be: a user
> browsing a process model may want to add some details to certain sections
> of the model, so that he should be able to do it from the same UI.
> Similarly, a user may want to add a specialized version of a currently
> displaying model. Therefore, I think the adding/editing functionality has
> to be provided in the same UI, controlled by user's authorizations.
>
> Regards,
> Chathura
>
>
> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran 
> wrote:
>
>> Hi All,
>>
>> The Enterprise Store currently satisfies necessity to host
>> applications, gadgets and eBooks. Users are able to add new assets of the
>> given type or create their own asset type and work with the store. A
>> requirement has arose to develop a Process Store to host processes of all
>> types and visualize associations with processes whilst providing other
>> utility functions. I am currently working on building a Process Store to
>> address the requirement.
>>
>> After discussion with the stakeholder we have agreed to initially build
>> the store as an extension of the enterprise store and move the process
>> store out as an product in the future. The extension to be built will be
>> for textual based processes and in future will be able to support other
>> type of processes too.
>>
>> The extension to be built will have the following functionality:-
>>
>>
>>- Adding a text based process
>>- Editing a text based process
>>- View a text based process
>>- Search for a text based process
>>
>>
>>- Associate existing text based process to a new variant - The user
>>when adding a new process can associate the new process to a existing one
>>if the new process is a variant or similar to the existing process but a
>>variant.
>>
>>
>>- Navigating processes through associations - The user can navigate
>>through the associations to find similar processes or their variants.
>>
>>
>>- Visualizing associations in graph views - The associations between
>>the processes will be sketched or depicted. This will be developed using
>>JSPlumb.
>>
>> The processes will be built as an asset type of the Enterprise Store as
>> discussed and the utility functions of the store such as adding, editing,
>> viewing, searching and visualizing will be done in the store front rather
>> than navigating to the publisher.
>>
>> Thank you
>>
>> --
>> Shiva Balachandran
>> Software Engineer
>> WSO2 Inc.
>>
>> Mobile - +94 774445788
>>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sameera Medagammaddegedara
Software Engineer

Contact:
Email: samee...@wso2.com
Mobile: + 94 077 255 3005
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB Connector for Meetup API

[Vanjikumaran Sivajothy]

looks good please send us a Detailed project plan.


On Wed, Sep 3, 2014 at 2:04 PM, Ananthaneshan Elampooran <
ananthanes...@wso2.com> wrote:

> Hi All,
>
> Myself (ananthanes...@wso2.com), Inshaf (ins...@wso2.com) and Sriashalya (
> asha...@wso2.com) have planned to develop the $subject.
> Please find the project plan below.
>
> *Introduction*
> The Meetup API provides simple RESTful HTTP and streaming interfaces for
> extending your community using the Meetup platform from your own apps. [1]
> 
>
> *Meetup API** Operations*
>
> Batch
>
> - Performs multiple API requests in batch
>
>
>  Boards
>
> - Listings of Group discussion boards
>
> - Listings of Group discussions
>
> - Listing Group discussion posts
> Categories
>
> - Returns a list of Meetup group categories
> Cities
>
> - Returns Meetup cities
> Dashboard
>
> - A dashboard of aggregated Meetup information for the authorized member.
> Events
>
> - Searches for recent and upcoming public events hosted by Meetup groups.
>
> - Recommends upcoming meetups for the authorized member.
>
> - Access Meetup events using a group, member, or event id.
>
> - Create event.
>
> - Update an existing Meetup.
>
> - Retrieve a single meetup.
>
> - Deletes a specified meetup.
>
> - Returns messages that appear under "Talk about this Meetup".
>
> - Posts messages that appear under "Talk about this Meetup".
>
> - Retrieve a single event comment or reply.
>
> - Retrieve a single event comment or reply.
>
> - Subscribe to notifications on updates to a given comment thread
>
> - Like a given Event comment.
>
> - Unlike a given Event comment.
>
> - Listing likes of a given event comment.
>
> - Accessing Meetup comments.
>
> - Allows members to posts rating for an event after it's occurred.
>
> - Lists attendance records for Meetup events.
>
> - Takes Member attendance for an Event.
>
> - Allows organizers of a group to note payments made by members for an
> event.
>
> - Add user to an event watch list to get notified when a spot becomes
> available.
>
> - Remove user from an event watch list.
>
>
>  Feeds
>
> - Retrieve the activity feed for a member's groups
> Groups
>
> - Fetch information about Meetup Groups.
>
> - API method for accessing meetup group comments.
>
> - Uploads a new Meetup Group photo.
>
> - Text, location, category and friend-based group searches.
>
> - Fetches a Meetup Group by urlname.
>
> - Edit their Meetup group information.
>
> - Group Topics Add.
>
> - Group Topics Remove.
>
> - Recommended Groups.
>
> - Similar groups.
>
>
>  Members
>
> - Access members of Meetup Groups.
>
> - Retrieve a single member.
>
> - Edit the authorized member's attributes.
>
> - Delete the specified member photo.
>
> - Uploads a photo to be associated with a Member.
> Messaging
>
> - Allows messaging-authorized requests to send messages between members.
> Meta
>
> - Returns the current API service status.
> Notifications
>
> - Returns all recent Meetup notifications for the authorized member.
>
> - Marks groups of notifications
>  as read.
>
> - Updates group and member-specific notification settings, POST method.
>
> - Updates group and member-specific notification settings, GET method.
> oEmbed
>
> - oEmbed implementation
> Photos
>
> - Delete specified event photo.
>
> - Returns comments on meetup photos.
>
> - Posts comments that appear below photos.
>
> - Returns photo albums associated with Meetup groups.
>
> - Returns photos by member, group, album, event, photo ID, or tagged
> member.
>
> - Creates photo albums within a Meetup group.
>
> - Uploads a photo for a given event.
> Profiles
>
> - Returns member profiles associated with a particular group.
>
> - Allows an authenticated member to join a group by creating a profile.
>
> - Update a member's group profile.
>
> - Retrieves a single group profile.
>
> - Deletes a member's group profile.
>
> - Approves one or more requests for group membership.
>
> - Declines one or more requests for group membership.
>
>
>  RSVPs
>
> - Query for Event RSVPs by event.
>
> - Creates or updates an existing RSVP.
>
> - Retrieve a single RSVP.
> Streams
>
> - Consuming using long-polling stream
>
> - Consuming using socket stream
> Topics
>
> - Returns a list of Meetup topic categories
>
> - API method for accessing meetup topics
>
> - Recommends suggestions for group topics based on a text search and
> optionally other topics
> Venues
>
> - Searches for public venues within a given geo space
>
> - Search for Meetup venues by one of your groups, events, or venue
> identifiers
>
> - Returns venues a group has previously hosted events at
>
> - Returns venues Meetup finds relevant to you based on location and
> category
>
> - Interface for creating new Meetup venues.
> Everywhere comments
>
> - Post comments
>
> - Get comments or comment for given id
>
> - Delete comment
> Everywhere communities
>
> - Get communities
>
> - Get community by id

[Architecture] ESB Connector for Meetup API

[Ananthaneshan Elampooran]

Hi All,

Myself (ananthanes...@wso2.com), Inshaf (ins...@wso2.com) and Sriashalya (
asha...@wso2.com) have planned to develop the $subject.
Please find the project plan below.

*Introduction*
The Meetup API provides simple RESTful HTTP and streaming interfaces for
extending your community using the Meetup platform from your own apps. [1]


*Meetup API** Operations*

Batch

- Performs multiple API requests in batch


Boards

- Listings of Group discussion boards

- Listings of Group discussions

- Listing Group discussion posts
Categories

- Returns a list of Meetup group categories
Cities

- Returns Meetup cities
Dashboard

- A dashboard of aggregated Meetup information for the authorized member.
Events

- Searches for recent and upcoming public events hosted by Meetup groups.

- Recommends upcoming meetups for the authorized member.

- Access Meetup events using a group, member, or event id.

- Create event.

- Update an existing Meetup.

- Retrieve a single meetup.

- Deletes a specified meetup.

- Returns messages that appear under "Talk about this Meetup".

- Posts messages that appear under "Talk about this Meetup".

- Retrieve a single event comment or reply.

- Retrieve a single event comment or reply.

- Subscribe to notifications on updates to a given comment thread

- Like a given Event comment.

- Unlike a given Event comment.

- Listing likes of a given event comment.

- Accessing Meetup comments.

- Allows members to posts rating for an event after it's occurred.

- Lists attendance records for Meetup events.

- Takes Member attendance for an Event.

- Allows organizers of a group to note payments made by members for an
event.

- Add user to an event watch list to get notified when a spot becomes
available.

- Remove user from an event watch list.


Feeds

- Retrieve the activity feed for a member's groups
Groups

- Fetch information about Meetup Groups.

- API method for accessing meetup group comments.

- Uploads a new Meetup Group photo.

- Text, location, category and friend-based group searches.

- Fetches a Meetup Group by urlname.

- Edit their Meetup group information.

- Group Topics Add.

- Group Topics Remove.

- Recommended Groups.

- Similar groups.


Members

- Access members of Meetup Groups.

- Retrieve a single member.

- Edit the authorized member's attributes.

- Delete the specified member photo.

- Uploads a photo to be associated with a Member.
Messaging

- Allows messaging-authorized requests to send messages between members.
Meta

- Returns the current API service status.
Notifications

- Returns all recent Meetup notifications for the authorized member.

- Marks groups of notifications
 as read.

- Updates group and member-specific notification settings, POST method.

- Updates group and member-specific notification settings, GET method.
oEmbed

- oEmbed implementation
Photos

- Delete specified event photo.

- Returns comments on meetup photos.

- Posts comments that appear below photos.

- Returns photo albums associated with Meetup groups.

- Returns photos by member, group, album, event, photo ID, or tagged member.

- Creates photo albums within a Meetup group.

- Uploads a photo for a given event.
Profiles

- Returns member profiles associated with a particular group.

- Allows an authenticated member to join a group by creating a profile.

- Update a member's group profile.

- Retrieves a single group profile.

- Deletes a member's group profile.

- Approves one or more requests for group membership.

- Declines one or more requests for group membership.


RSVPs

- Query for Event RSVPs by event.

- Creates or updates an existing RSVP.

- Retrieve a single RSVP.
Streams

- Consuming using long-polling stream

- Consuming using socket stream
Topics

- Returns a list of Meetup topic categories

- API method for accessing meetup topics

- Recommends suggestions for group topics based on a text search and
optionally other topics
Venues

- Searches for public venues within a given geo space

- Search for Meetup venues by one of your groups, events, or venue
identifiers

- Returns venues a group has previously hosted events at

- Returns venues Meetup finds relevant to you based on location and category

- Interface for creating new Meetup venues.
Everywhere comments

- Post comments

- Get comments or comment for given id

- Delete comment
Everywhere communities

- Get communities

- Get community by id

- Add community/community

- Delete community

- Get follower/followers

- Add follower/followers

- Delete follower

Everywhere containers

- Get container/containers

- Add container/containers

- Delete container/containers

- Get alerts

- Add alerts
Everywhere event seeds

- Editing events seeded to communities.

- Querying an event seeded to communities

- Removing all events seeded to communities

- Creating an event to seed to all communities
Everywhere events

- Editing e

Re: [Architecture] Process Store for text based process

[Chathura Ekanayake]

As Shiva has mentioned, we want to do both adding and displaying process
models in the same UI, diverting from the current model of ES to have a
separate publisher and a store. An example requirement would be: a user
browsing a process model may want to add some details to certain sections
of the model, so that he should be able to do it from the same UI.
Similarly, a user may want to add a specialized version of a currently
displaying model. Therefore, I think the adding/editing functionality has
to be provided in the same UI, controlled by user's authorizations.

Regards,
Chathura


On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran  wrote:

> Hi All,
>
> The Enterprise Store currently satisfies necessity to host
> applications, gadgets and eBooks. Users are able to add new assets of the
> given type or create their own asset type and work with the store. A
> requirement has arose to develop a Process Store to host processes of all
> types and visualize associations with processes whilst providing other
> utility functions. I am currently working on building a Process Store to
> address the requirement.
>
> After discussion with the stakeholder we have agreed to initially build
> the store as an extension of the enterprise store and move the process
> store out as an product in the future. The extension to be built will be
> for textual based processes and in future will be able to support other
> type of processes too.
>
> The extension to be built will have the following functionality:-
>
>
>- Adding a text based process
>- Editing a text based process
>- View a text based process
>- Search for a text based process
>
>
>- Associate existing text based process to a new variant - The user
>when adding a new process can associate the new process to a existing one
>if the new process is a variant or similar to the existing process but a
>variant.
>
>
>- Navigating processes through associations - The user can navigate
>through the associations to find similar processes or their variants.
>
>
>- Visualizing associations in graph views - The associations between
>the processes will be sketched or depicted. This will be developed using
>JSPlumb.
>
> The processes will be built as an asset type of the Enterprise Store as
> discussed and the utility functions of the store such as adding, editing,
> viewing, searching and visualizing will be done in the store front rather
> than navigating to the publisher.
>
> Thank you
>
> --
> Shiva Balachandran
> Software Engineer
> WSO2 Inc.
>
> Mobile - +94 774445788
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [App Factory] Improvements to application wall

[Manisha Gayathri]

Hi Dmitry,

Since Gayan is in support now, I will continue to work on this.
The doc attached, contains the items completed by Gayan so far.

I will be able to do a demo on next Monday with the completed items. And we
will be able to ship the completed feature for M6.

Thanks
Manisha



On Fri, Aug 15, 2014 at 7:18 AM, Gayan Dhanushka  wrote:

> Hi Dmitry,
>
> I have scheduled a demo o Monday. I will do a sample implementation of the
> two scenarios and give a demo to you on Monday.
>
> GayanD
>
>
> On Fri, Aug 15, 2014 at 1:05 AM, Dmitry Sotnikov  wrote:
>
>> Yes, some sort of PoC would be good. I am not sure what you mean by
>> showing the Type B messages on the page - so would be great to see it in
>> action or at least on mockups...
>> On Aug 14, 2014 8:02 PM, "Dimuthu Leelarathne"  wrote:
>>
>>> Hi Dmitry,
>>>
>>> Please see my comments inline.
>>>
>>>
>>> On Thu, Aug 14, 2014 at 12:17 PM, Dmitry Sotnikov 
>>> wrote:
>>>
 Gayan and Dimuthu,

 From my perspective, one-off UX exceptions are bad, because they make
 the UI inconsistent.

 There are two types of messages:
 A. High-level external notifications of someone taking some action
 (e.g. "John created a new app") and
 B. Low-level ongoing processes happening in AF as result of what the
 current user clicks ("Creating initial GIT repository", etc.)

 Type A are more social and shown across team, and only when something
 is actually successfully finished.

 Spinning wheels / progress indications are only relevant to type B.
 These messages are only related to the current particular user and show
 work in progress, starting immediately once the user clicks something.

 So from my perspective, either we show both types in one pane, or have
 two different panes (or other UX metaphors) for the two types.

>>>
>>> What I am suggesting is a different approach. Which is to show the type
>>> B messages on the page itself where the information is related. For example
>>> the fact that build is in progress should be on the Build & Repo page
>>> itself. What if we do a POC for the same scenario
>>>
>>> 1 - on the wall
>>> 2 - on the page
>>>
>>> And see which is user friendly? I agree two panes are not going to be a
>>> good solution.
>>>
>>> thanks,
>>> dimuthu
>>>
>>>
 My understanding is that the current idea is to try to re-use the same
 App Wall for everything, right?

 Dmitry



 On Thu, Aug 14, 2014 at 9:39 AM, Gayan Dhanushka 
 wrote:

> Hi Dimuthu,
>
> I tried a sample implementation to show the implementation on the
> application wall. This was done by looking at the content of the message.
> It was successful. But this may not be ideal since for different kind of
> start-inprogress-ended messages we may need to have different logic.
>
> Meanwhile I can share some wire frames of the approach suggested above
> to show the in progress activities on the pages themselves.
>
> Thanks
> GayanD
>
>
> On Thu, Aug 14, 2014 at 4:43 AM, Dimuthu Leelarathne <
> dimut...@wso2.com> wrote:
>
>> Hi Gayan,
>>
>>
>> On Wed, Aug 13, 2014 at 2:28 PM, Gayan Dhanushka 
>> wrote:
>>
>>> Hi Dimuthu,
>>>
>>> Following are a set of actions that we want to give
>>> "started-inprogress-ended" messages and places where we would put the
>>> spinning wheel and messages.
>>>
>>> 1) Application Creation - User home near the application thumbnail
>>> (This is already implemented)
>>> 2) Application Upload - Application creation page (This is already
>>> implemented. Spinning wheel is shown on the application creation page 
>>> until
>>> the application is uploaded)
>>> 3) Build - Repos Builds page near last build status
>>> 4) Deployment - Repos Builds page near last deploy id
>>> 5) Promote / Demote - Lifecycle page under the particular version
>>>
>>> I am tentative on having an in progress state for resource creation
>>> since it does not take much time.
>>>
>>>
>> It doesn't take much time in Dev setups. But takes considerable time
>> in Cloud. I think for resources we need to give "started" and "ended"
>> messages.
>>
>> @ Dmitry: What do you think about the new proposal? Giving
>> progress-reporting on the page itself, rather than on the wall?
>>
>> We can do some wireframes and then can finalise. WDYT?
>>
>> thanks,
>> dimuthu
>>
>>
>> What are your thoughts?
>>>
>>> Regards
>>> Gayan
>>>
>>>
>>> On Wed, Aug 13, 2014 at 12:28 PM, Dimuthu Leelarathne <
>>> dimut...@wso2.com> wrote:
>>>
 Hi Gayan,

 According to our offline discussion, then lets do this.

 1 - Identify and list all actions that we want to give
 "started-inprogress-ended" messages
 2