cancel
Showing results for 
Search instead for 
Did you mean: 

How to distinguish multi-tenant applications of different stages once registered via SaaS service?

pieterjanssens
Active Participant

Subaccounts:

- Provider Test

- Provider Production

- Subscriber 1 Test

- Subscriber 1 Production

These subaccounts are all part of the same global account on the same data center.

Once the application is registered via the SaaS service, there is no indication from which subaccount it is served, so (at least from the UI) I cannot distinguish between test and production deployments.

What is the best-practice to deal with this? I'm looking for a solution in the cockpit.

alperdedeoglu
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi piejanssens,
Can you elaborate a bit more?
Do you have same approuter url for two different stages?

pieterjanssens
Active Participant
0 Kudos

Hi adedeoglu,

No, provider app 'test' and provider app 'production' are both the same apps, but at different versions.

They each have their own approuter. Since it's the same app, they share the same name and the same module ID's. This is all fine since they are in different subaccounts, but how do we distinguish test from production in the saas registry.

I guess using mta extensions per stage and using a different displayName (and xsappname ?) is one option.
Ideally, it would be great if we were able to set the 'plan'. So that it's the same app you are subscribing to, but the plan being test/production is then targetting different subaccounts (as each provider app plan is coming from a different subaccount).

Accepted Solutions (1)

Accepted Solutions (1)

gregorw
Active Contributor

Have you tried to give the app a different name using a .mtaext file. That way you could define different names for Dev, QA and Production.

pieterjanssens
Active Participant
0 Kudos

Tested and this works (I went with a different description which is visible in the list of services in the service marketplace).
Having a the possibility to do this via service plan would be my preferred way: https://influence.sap.com/sap/ino/#/idea/296661

Answers (0)