Hi, I am being implemented workflow extension for rest of the BPELs which are deployed in the BPS. Following execution steps were identified from existing BPEL of each workflow.
- ApplicationCreation Calling form AF add.jag ApplicationExecutor.java Calling form BPS Service: ApplicationManagementService Operation: publishApplicationCreation - DeployArtifact Calling from AF add.jag Calling from BPS Service: ApplicationDeployer Operation: deployArtifact - CreateArtifact Calling from AF I was unable to found any places which is being called from the AF. Calling from BPS Service: ArtifactCreator Operation: CreateArtifact - GovernanceBPEL Calling from AF lifeCycle.jag Calling from BPS Service: CustomLifecyclesChecklistAdminService Operation: invokeAspect Service: ApplicationManagementService Operation: updateRxtWithRemoteState If there will be any other concerns please mention. Thanks. On Mon, Sep 21, 2015 at 1:13 PM, Manjula Rathnayake <manju...@wso2.com> wrote: > Hi Lahiru, > > As Danushka mentioned, lets focus only on 2nd option where we configure > workflows for all tenants not per tenant. Few reasons to choose option 2, > 1. If we allow per tenant workflows, we need to enable mechanism to > upload, configure AF runtime servers and it should not cause any issues to > other tenants or AF setup. > 2. Usually, enterprises has their own workflows for application creation, > go production etc and those will be configured at AF deployment level and > enforce for application developers. > 3. Option 1 is a nice to have feature and it requires considerable effort > and option 2 still addresses the issues of having workflows running in a > separate BPS nodes(bulkiness of the AF deployment) etc. > > So +1 for second option. > > thank you. > > > On Mon, Sep 21, 2015 at 11:34 AM, Lahiru Manohara <lahir...@wso2.com> > wrote: > >> Hi All, >> >> The AppFactory workflow extension we can implement this in two ways. >> 1. Each tenant can configure which workflow will execute in the >> AppFactory. >> 2. Same configuration for all tenant. >> >> If we use second option, we have two implementation ways. >> 1. We can keep the configuration in Carbon registry. >> 2. We can keep the configuration in AF database. >> >> If we are going to implement second option, we have to consider where can >> we give option to select the workflow type. The first option we can >> configure workflow type form the Carbon dash board from this location Home >> > Resources > Browse. >> >> ​Appreciate your feedback on this. >> >> Thanks and regards. >> >> >> On Fri, Sep 11, 2015 at 5:35 PM, Lahiru Manohara <lahir...@wso2.com> >> wrote: >> >>> >>> -- >>> Best regards, >>> >>> *Lahiru Manohara* >>> *Software Engineer* >>> Mobile: +94716561576 >>> WSO2 Inc. | http://wso2.com >>> lean.enterprise.middleware >>> >> >> >> >> -- >> Best regards, >> >> *Lahiru Manohara* >> *Software Engineer* >> Mobile: +94716561576 >> WSO2 Inc. | http://wso2.com >> lean.enterprise.middleware >> > > > > -- > Manjula Rathnayaka > Associate Technical Lead > WSO2, Inc. > Mobile:+94 77 743 1987 > -- Best regards, *Lahiru Manohara* *Software Engineer* Mobile: +94716561576 WSO2 Inc. | http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
