Hi Sinthuja,

I would like to review this implementation. Can you please point me the
code block, which is used to access the super tenant registry when tenant
user has logged in? Have you started super tenant flow before accessing the
super tenant's registry?

Regards,
Chandana
On Jun 2, 2016 12:00 PM, "Sinthuja Ragendran" <sinth...@wso2.com> wrote:

> Hi Chandana,
>
> Dashboards are stored in registry as shown in the attached image
> (registry_dashboards.png) and as you can see there test and test1 are the
> dashboards that are configured for that tenant. And each of the dashboard
> resources (lets say test resource in the screenshot) will have the full
> dashboard.json configuration and within that we have a property to mention
> whether the particular dashboard is shared or not ("shareDashboard":true).
>
> When a tenant logs in, we load the super tenants dashboards and display
> only the dashboards which have the above mentioned property to the tenant
> along with own tenants dashboards.
>
> But we don't get the list of dashboards/resources from the collection in
> path /_system/config/ues/dashboards/ (test and test2 as per the screenshot)
> from super tenants registry immediately when the tenant is logging in, and
> it's empty. And this happens if there is no dashboards created in super
> tenant during the time of tenant creation. In case lets assume, I have
> created a tenant when super tenant already have 'abc' dashboard, then I can
> get the 'abc' dashboard correctly. But it doesn't happen in other way
> around, where the tenant is created first and then the dashboard is created
> afterwards and shared from the super tenant space. And again after 15mins
> (when the cache gets cleared) I could see the dashboards are returned
> correctly from the /_system/config/ues/dashboards. Also if we disable the
> caching, it works without any problem. Hence I believe it's something wrong
> with caching.
>
> Thanks,
> Sinthuja.
>
> On Thu, Jun 2, 2016 at 7:13 AM, Chandana Napagoda <chand...@wso2.com>
> wrote:
>
>> Hi Sinthuja,
>>
>> From the registry point of view, we are not replicating one tenant's
>> resources into another tenant's registry. I would like to know how you guys
>> set one resource visible to other tenants?
>>
>> Regards,
>> Chandana
>> On Jun 1, 2016 11:47 PM, "Sinthuja Ragendran" <sinth...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I did some further testing, and it looks like we are replicating the
>>> super tenant cache entries to tenant cache, when the tenant is loading at
>>> the first time. Because if I first create the dashboard (a registry
>>> resource) in super tenant and configured it to be shared by all nodes, and
>>> secondly if I create the tenant and try to login, then I can see my shared
>>> dashboards. But if I create the tenant first and secondly I configure the
>>> share option in the dashboard, then I'm not seeing the dashboard. Therefore
>>> I believe that there is simply a cache replication issue.
>>>
>>> Can we get a fix for this issue?
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Wed, Jun 1, 2016 at 10:51 PM, Megala Uthayakumar <meg...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We are using super-tenant registry to load the dashboards in other
>>>> tenants. We are using following code.
>>>>
>>>> superTenantRegistry = new carbon.registry.Registry(server, {
>>>>     system: true,
>>>>     tenantId: carbon.server.superTenant.tenantId
>>>> });
>>>>
>>>> Thanks.
>>>>
>>>> Regards,
>>>>
>>>> Megala
>>>>
>>>>
>>>> On Wed, Jun 1, 2016 at 10:47 PM, Chandana Napagoda <chand...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> How are you sharing the asset between all the tenants? Is it a public
>>>>> visible asset?
>>>>>
>>>>> Regards,
>>>>> Chandana
>>>>> On Jun 1, 2016 10:08 PM, "Megala Uthayakumar" <meg...@wso2.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We are developing a shared dashboard feature for Dashboard Server.
>>>>>> This feature allows the dashboard created from super-tenant to be shared
>>>>>> among all the tenants. We have observed following behavior when 
>>>>>> developing
>>>>>> this feature.
>>>>>>
>>>>>> When we create a shareable dashboard in super-tenant mode and if we
>>>>>> immediately login to portal as a different tenant-user. Shared database 
>>>>>> is
>>>>>> not visible in the tenant mode. We were able to see the shared dashboard 
>>>>>> in
>>>>>> other tenants after we restart the server.
>>>>>>
>>>>>> However after we disable registry caching, we were able to see the
>>>>>> shared dashboard in tenant mode immediately after login without requiring
>>>>>> to restart the server. Is it possible to get the same type of behavior
>>>>>> without disabling registry cache?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Regards,
>>>>>> Megala
>>>>>> --
>>>>>> Megala Uthayakumar
>>>>>>
>>>>>> Software Engineer
>>>>>> Mobile : 0779967122
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Megala Uthayakumar
>>>>
>>>> Software Engineer
>>>> Mobile : 0779967122
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Associate Technical Lead
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>
>
> --
> *Sinthuja Rajendran*
> Associate Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to