Skip to Content

Nakisa Tenants Configuration

Hi,

I am configuring Nakisa for the first time for a simple build for the purposes of publishing a couple of Org Structures. All is going OK as it can and I have only a couple of issues I am trying to sort out.

I am struggling with understanding the “Tenants Configuration” so I need some guidance from anyone who have used this feature.

Build Scenario

I am required to have several published Org Structures due to multiple companies existing in the overall org structure.

  • Company A, will have view access to all the underlying structures (ie ALL)
  • Company B is a sub structure of A that I require a separate publish/ build for. (ie separate URL that will be put on separate companies
    intranet site)

Issues

Enter Nakisa and select a build name and publish this build this exists as the default published structure as per following URL.

http://sapXXX:XXXXX/OrgChart/default.jsp

How does the tenant config work in relation to assigning a URL to a build? I tried a few things but none of them seem to work. Do I not need multiple
builds for multiple tenant publishes (ie Can I have one build and several tenant entries….how does this link back to a parent org unit)


I checked all of the Nakisa documentation and there is nil in relation to how this works, one would think that since this is new
functionality that some documentation would exist around how this works. Unless I missing something ?

Any help much appreciated.

Thanks

Image1.jpg (33.7 kB)
Image2.jpg (55.5 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 30, 2013 at 01:44 PM

    Hi Mark,

    We had the same question this past summer, and approached Nakisa directly. From my understanding, the multi-tenant functionality is developed and enabled in the product, but it is not certified for release to customers. Hence, the lack of official documentation (a little frustrating, I know).

    That's not to say it doesn't work if you configure it, but Admin Guide documentation with the configuration steps required most likely will not be coming until it is certified for customer use.

    Cheers!

    Matthew

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 08, 2013 at 09:14 AM

    Hi Mark

    Is there any reason why you are not using Roles or Structural Authority to separate access to the same Org Structure or even segregate access into two hierarchies in the same Build or Instance. For Instance use authorities from the back end, or your own if staged build, as one option or create a second hierarchy with a different route Org Unit as a second option with both hierarchies separate by roles in security linked to employees in each company code.

    There is also the option to use dynamic authorisations to drive access to parts of the structure but this is more difficult.

    As for Tenancy we did get it to work of sorts but used in a training scenario rather than for a production scenario. We didn't test to the nth degree but did have some success and would second the comment above that you should think about the impact on resources the more tenants you create. I think the key is the order in which you activate tenancy, i.e.

    1.) Enable Multi-Tenancy in Application Wide Settings (Save and Publish important bit)

    2.) Create Tenants (Provider can be left as standard and Domain didn't need to set anything here)

    3.) Create an Admin account for each Tenant and assign to the respective Tenant (Save and Publish)

    There is a Tenants folder in the Published XML directory so this suggests you can configure and publish each Tenant separate to the original Master Build.

    We tried this in a Tutor/Student scenario and the main issue was performance, though mainly due to poor sizing and also sometimes the configurations didn't appear to update but other times they did.

    This is from Nakisa instructions and without extensive testing but we did have some success, hope it works for you.

    I think this will be a good blog subject so I might have a go of publishing our findings over the next week or two.

    Regards

    Stuart

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 06, 2014 at 04:07 AM

    Sorry All,

    I ran out of time to try and solve this due to other project commitments, so we went with what we had as I could not get the Tenants Configuration to work in the end.

    Thanks all for your responses they gave me some more insight into what this functionality is supposed to do.

    Regards,

    Mark

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 12, 2015 at 10:40 AM

    Dear Mark,

    Thank you very much for your work, I know it's not finish yet, but thanks for giving me a clue on how to perform the multi tenant configuration.

    I guess I am going to continue your work on my thread

    Regards,

    Bobbi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.