I recently watched a TechEd Las Vegas session entitled “Integration of Cloud Solutions from SAP” in which details were provided on the upcoming NetWeaver Cloud-based Integration as a Service (IntaaS). In this presentation, there were some interesting details not only about the IntaaS but also about more general NetWeaver Cloud-related topics.
There is a list of personas or roles that will be involved in this new offering:
Customer Side
SAP
Since integration plays a critical role in hybrid (OnPremise/OnDemand integrations), these roles are very important.
POV
The ability of SaaS solutions to support multi-tenancy is critical. NetWeaver Cloud supports this functionality and applications which run on this platform could also support it as well. The efficient administration of multi-tenancy is also very important and increases in significance as the number of tenants supported by a particular application starts to rise.
NetWeaver Cloud provides various tools to provide this functionality.
Note: I know that the NetWeaver Cloud tools dealing with tenant support are still in their early stages and that changes in their design are to be expected in the future.
It is important that such tenant-related tools are harmonized on UI and platform.
I’ve used the current set of web-based NetWeaver Cloud tenant administration tools during the configuration of custom Identity Providers and I find the tools quite good.
[SOURCE]
I was therefore a bit surprised when I was looking at the IntaaS presentation and saw that their tenant-based tools are Eclipse-based.
I have no idea what functionality is provided by these IntaaS tenant administration tools or if there is an overlap between the existing web-based tools. It is important, however, to assure that administrators don’t have a multiple environments – or even worse centralized vs. decentralized tools – to deal with tenant administration.
There is still other important tenant-related functionality that is missing in NetWeaver Cloud. For example, the ability to set tenant-specific HTTP destinations – as used by the Cloud Connectivity Service – comfortably via UI is still unavailable. Currently, destinations are set in Eclipse or via command line without any association with tenants. Another example of this gap concerns multi-tenancy in the integrated database schema.
Although these gaps currently exist, SAP is hopefully aware of the critical importance of multi-tenant support. If we are lucky, the current bi-monthly releases will hopefully soon be bringing improvements in this area.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
10 | |
7 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |