on 08-24-2021 10:12 PM
Hi All, I was curious on how everyone is organizing their folder structures in SAC when only using a single tenant. Are you connecting to multiple HANA/BW non-prod/prod environments and if so what are you finding the best way to separate stories/apps connecting to these different environments. We're old school BOBJ customers with dedicated servers for each of our non-prod environments and trying to wrap our head around how other customers are making this transition when on a single tenant. The big sticking point is migrating/transporting objects isn't possible or doesn't make sense when using a single tenant but on the other hand need users to test these (ideally in a QA environment).
Thank you for any help you can provide!
Hi Josh,
I'd highly recommend going thru this whitepaper for LCM topics (both in one tenant and multi-tenants): SAP-BusinessObjects-Cloud-Lifecycle-Management-whitepaper-2018.pdf (sapanalytics.cloud)
Jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Jay, I've actually seen this document. What I am trying to understand is how organizations are handling a scenario where a user can access multiple environments within a single tenant. I am guessing we need to use teams to control this but how does version management work (or doesn't it in this scenario)? Are users creating directly against prod?
Hi Josh,
Candidly a single tenant scenario is not the recommended/target scenario, especially in mixed landscape situations (DEV/QA/PRD).
That being said, when a customer does decide to do this we use Teams and access to folders to separate things, however, that also has limitations/restrictions.
Something that will be released soon (and already is if you're on Fast Track) is the concept of Workspaces which will allow this separation more seamlessly. Details of that will be available soon.
Jay
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.