Hi Gokul, What was the way that you followed in giving the AF team a UES integrated BAM pack? AFAIK we are going to have the pack you provided in AF. There were some complications regarding that pack too. I think AF will be needing at least that integration for the BAM+UES integration.
Ranga, please correct me if I am wrong. Thanks. Gayan. Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd On Mon, Sep 23, 2013 at 5:18 PM, Balakrishnan Gokulakrishnan <[email protected] > wrote: > Hi all, > > We have been working to get complete UES support for the upcoming BAM > 2.4.0 release, for enabling custom gadget creation and publication through > the portal and store UES apps respectively. However, since the UES features > that we have currently do not not fully support multitenancy, we are facing > several issues that prevent us from achieving an end-to-end solution with > UES, such as the absence of tenant isolation for published artefacts. In > addition, listing currently deployed dashboards, having the dashboards > deployed to the tenant-specific spaces etc will not be achievable for > tenants with the current version of UES. Further to offline discussion with > the UES team we learned that it would take a considerable effort to > retrofit these capabilities to UES as of now, and that the above features > will be added to UES with the release of the Enterprise Store. > > Consequenty, we have 3 ways of moving forward with UES integration for > this release of BAM: > > 1. Remove the current BAM dashboard components and add UES, but this will > mean the dashboard capability will be available solely to the supertenant. > Tenants will be unable to carry out even rudimentary tasks such as deploy > toolboxes with dashboards, list available dashboards and so on. (i.e. > visualization support limited to the supertenant) > > 2. Keep the current BAM dashboard as is and push UES support to the next > release (2.5.0), so that there is a complete working solution in MT > scenarios for this release and the BAM visualization components will be > cleanly UES-based in the next release. (i.e. there will be no UES support > in the upcoming 2.4.0 release). > > 3. Keep the current BAM dashboard as is and provide UES support only for > the supertenant. Tenants will be limited to the existing BAM dashboards for > visualization while the supertenant has access to the portal and store > apps. (i.e. best of both worlds approach) > > We are looking at proceeding with option 3, since it will allow us to > introduce UES for the supertenant in the upcoming release itself and then > have the full-fledged UES-based visualization component in the next > release. Limitations to this approach include the supertenant having to > consult two lists of deployed artefacts (one in the current BAM dashboard > and one in the UES portal), and an increased distribution size. > > WDYT? > > Thanks, > -- > *Balakrishnan Gokulakrishnan* > Software Engineer, > WSO2, Inc.; http://wso2.com > Tel: 0094 11 214 5345 | Fax: 0094 11 214 5300 > > Twitter: http://twitter.com/gokulbs > Mobile: 0094 77 593 5789 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
