Hi Chandana,
Sorry for the delay, I was bit busy with some other stuff and couldn't
check it immediately. I added the tenant flow, and it worked! As it was
working when we disable the cache, I have thought it's something related to
cache, and didn't try to add the tenant flow. Anyhow now it
Hi Sinthuja,
Since you haven't initiated the correct tenant flow in the first place,
resource has been cached in the wrong tenant space. Therefore you must
access other tenant user's registry correctly by starting correct tenant
flow.
Regards,
Chandana
On Jun 2, 2016 1:15 PM, "Sinthuja
Hi Chandana,
I also had a doubt about starting the tenant flow, but it was working when
we disable the cache, hence I thought the issue is not related to tenant
flow. And if it's related to tenant flow, it shouldn't have worked even if
we disable the cache. Anyhow let me add the tenant flow part
Hi Sinthuja,
Everytime when you are accessing the registry of another tenant, you must
start the tenant flow using particular tenant user beforehand and close it
after performing the registry operation. I don't see any code used here to
start a super tenant flow before accessing the super tenant
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
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" 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
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
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" wrote:
> Hi All,
>
> We are developing a shared dashboard feature for Dashboard Server. This
> feature allows the dashboard
Yes. I tested with 4.5.4 carbon-registry version.
On Wed, Jun 1, 2016 at 10:16 PM, Sinthuja Ragendran
wrote:
> Looping in registry team. Is this the known issue? Megala, I think you
> tested with 4.5.4 carbon-registry version.
>
>
>
> On Wed, Jun 1, 2016 at 10:08 PM, Megala
Looping in registry team. Is this the known issue? Megala, I think you
tested with 4.5.4 carbon-registry version.
On Wed, Jun 1, 2016 at 10:08 PM, Megala Uthayakumar wrote:
> Hi All,
>
> We are developing a shared dashboard feature for Dashboard Server. This
> feature allows
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
12 matches
Mail list logo