SAP Analytics Cloud – Landscape Architecture & Life-cycle Management
What should the landscape architecture of SAP Analytics Cloud look like and how does it compare with traditional on-premise landscapes? How should I manage the life-cycle of content in SAP Analytics Cloud? I address these and many other common life-cycle management questions in my article.
I first look at typical on-premise landscapes and then compare this to the Cloud, what’s the same and what’s different. The final architecture is determined by many factors and I present the most important things you need to know, including summaries of:
- Public and Private hosted editions
- SAP Analytics Cloud Test Service and its Preview option
- Quarterly Update Release and Fast Track Update Release cycles
I explain where each fit into the overall life-cycle, thus allowing you to determine the right architecture for your organisation. This includes explaining how and when you can transport objects between the different Services. Here between the Preview Service and the regular Quarterly Release Cycle (QRC):
and here between the Quarterly Release Cycle and the ‘Fast Track’:
(the ‘Fast Track’ is not provisioned by default)
I also present why multiple environments are need at all and what can be achieved, albeit in a limited fashion, within a single environment when managing the life-cycle of content.
I present the typical landscape options chosen by most other customers and the most common path of adoption. Thus, giving you some guidance on what your next step on your SAP Analytics Cloud journey might be:
Content Namespaces are also an important concept to understand and I present some recommendations on how to manage this to avoid known issues and reduce the risk for your projects.
I also present the options for transporting objects around the landscape and I finish with a Best Practice Summary.
Your feedback is most welcome. Before posting a question, please do read the article carefully and take note of any replies I’ve made to others. Please hit the ‘like’ button on this article or comments to indicate its usefulness.
Matthew Shaw @MattShaw_on_BI