I have installed WSO2 Identity server and WSO2 API manager according to documentation of Products Clustering & Deployment Guide "Configuring the Pre-Packaged Identity Server 5.1.0 with API Manager 1.10.0". According to this configuration WSO2 IS and WSO2 AM use common registry data-source (for governance and configuration).
Later in WSO2 IS I have added additional tenant - for example vu.lt.
And now when I login to WSO2 IS and WSO2 AM management console as super-tenant admin, all works OK.
When I login to WSO2 IS management console as admin of vu.lt tenant - all is OK.
But when I login to WSO2 AM as admin of vu.lt tenant I get a little strange view: the header of page is from Identity Manager, but content is from API manager.
After some tests I found out that css file (main.css) is loaded from governance part of registry .../governance/repository/theme/admin/main.css. It means that main.css is loaded from data-source. The same css is loaded when I login from WSO2 IS. The same happen if install one more server (for example BPS) and configure it to use common registry space.
Maybe this situation is not very bad, but I don't know which consequences can I get later.
So, the question is: could I have common registry space in multi-tenancy environment or I have configured something wrong.
Finally I would like to install WSO2 IS, BPS, AM and DAS with LDAP user store and to use this system for Identity Management purposes in our university. I'm not sure which configuration of registry space should I choose: common governance and different configuration, or maybe common configuration too, like in "Configuring the Pre-Packaged Identity Server 5.1.0 with API Manager 1.10.0"?