Welcome to this series of hands on tutorials from the SAP HANA Academy
I'm Philip Mugglestone
in this series. We're covering the SAP Business Technology Platform
in this video tutorial, we're going to look at sub accounts.
Now previously we've had a tour of the cockpit for global accounts.
What we now might want to do is to create a sub account or even a directory.
Now it's actually very straightforward and easy to do.
Basically the thing you need to remember is that you
can have any number of sub accounts or directories.
Every sub account needs to map 1 to 1 to a regional data center.
So basically an infrastructure provider.
So you do need to give quite some thought when you're creating a new sub account
as to exactly which region and provider you want to create
it in based on the services that ultimately you want to
actually use and configure within that sub account and it may
be that you create multiple sub accounts in different regions and providers
to get access to all the services you need for your project.
So we've got different ways that we can actually create a sub account.
For example, we could use a booster.
So one simple booster here is the one that's to create an account for development.
So we can actually start it
and you see checking that we've got the right compatible
providers and regions and checking we've got the right entitlements.
If not
then if we click on this we get information on that.
We can then hit next
and it will actually propose us
the different entitlements we might want to use.
So maybe one SAP BTP, Cloud Foundry runtime
will have the connectivity service in the destination service.
Okay, that makes sense.
And it will prompt us to create a sub account name
and then we can choose which provider
that we've got entitlements to and which region within
that provider we actually want to create it.
So maybe I'm going to do that in us East Amazon Web Services
that's gonna be us10,
so that's how I can select it.
And then we've got the sub domain that will be basically,
it's kind of the the unique ID of this sub account within this data center,
this provider own region.
So this absolutely has to be unique.
And then as we're using
SAP BTP, Cloud Foundry runtime it's actually gonna provide us
an organization and the space now I would highly recommend
not to go with the default as they look here.
I would create a sub account name that's kind of more meaningful to you, for example,
I might call it SAP HANA Academy development
and then I would set in general the sub domain
to the same thing.
So it's something that's meaningful to you and also for the Org name,
the SAP BTP, Cloud Foundry runtime organization,
which is 1 to 1 mapping with the sub domain.
Um I would also make these two identical,
particularly if you're gonna work with multi tenant applications later.
You'll need to have done this otherwise things get very complicated.
So let's go ahead and hit next.
We can also add in the emails of any
administrators we want for this environment or any developers,
we want to configure directly.
So I'll add in a developer that I want to be able to work with this
and I'll hit next
and then we'll be able to confirm,
notice it sets up your own email as an admin and developer generally, anyway,
I will hit finish
and now you can see it goes through the process of creating a sub account,
enabling the SAP BTP, Cloud Foundry environment
assigning the service quotas to the sub account,
creating a SAP BTP, Cloud Foundry runtime space,
adding the users that we specified,
creating the service instances of the destination and the connectivity service
and assigning any role collections that are relevant as well.
So I'll take a couple of minutes
and once that's completed then you should be
able to navigate to your new sub account.
So you can see our sub accounts being created using the sub domain that we specified.
We've got SAP BTP, Cloud Foundry runtime enabled with a space
and if we look at the service instances,
we can see we've got a destination
instance and connectivity instance.
So it's basically done exactly what it said
and if we look at our members, so for our users we can see that it's assigned
the additional user as well as ourselves
in this case is a space developer.
So that's what the booster does. It does a lot of steps for you
now. It may be that you just want to create a sub account manually.
You can also do that, you get more control
so let's just have a quick look at that
let's go back to our global account,
go to the account Explorer.
Now, you can see we've actually got a sub account in here.
What we can do is actually create a sub account
manually through this option,
then we can give it a name.
Maybe we'll call this test for us again,
I'm gonna make sure the sub domain is meaningful to me,
it does have to be unique within the data center.
Now in this case I'm gonna choose maybe I'll do it in a different
infrastructure provider to this case and maybe we can do it
us east but of Azure because we use different services there
so I can then hit create
now before I do that
there are advanced options.
If you actually want this to be used in productive scenarios,
you can choose use for production,
you can see more details here on what that means.
And also if you want to have access to
beta features which you would not do in production,
then you can use this flag here to say I want this sub
account to be able to access beta services and if you want,
you can also set up labels with their values for the sub account.
Let's hit create.
So now we can see the creation is pending, we've got two tiles,
one for Azure and one for our Amazon Web Services it's doing the onboarding
and if we click on the tile
we can see that we've got a sub account but notice
in this case we haven't created the kind of foundry environment,
we've not accessed SAP BTP, Kyma runtime or anything
that's something we would need to do manually.
There are no service instances or subscriptions set up at this point
and in fact there are no entitlements, really just some very standard default ones.
So if we want to make entitlements available,
we need to use the configure entitlements
and then for example add the services that we
want to be made available within this sub account.
So again we do that manually,
you can do it all manually in this way and we'll see in a later video tutorial,
you can do all of this using a command line or an API as well.
This is using the cockpit.
Let's go back to our overview.
Now it might be,
we want to group these two together for example as a directory
so what we can do is just simply create a new directory,
maybe call this project one
and then we'll create
and then what you can do when you're working in this list view,
you can actually just drag and drop your sub accounts
into the directory so you can move it like this
so I can have one of my sub accounts in this directory
or maybe all of them totally up to you of course you can also view it
so you get the ability to structure your environment if you want to move it here,
we need to choose actions and then move.
And then again I can move it into its new parent which might be project one.
So you can set up your own tree structures by using directories.
And of course what you can also do at
the directory level is you can set up specific users
and you can also sped up entitlements.
I won't do that here, but it's something that's absolutely possible.
So in this video tutorial we've seen how you can get started working with sub account
and directories. We created a couple of sub accounts.
One of them we did actually using a booster,
one of them.
We did manually we created a directory and we
put both of our sub accounts into that directory.
You can find more video tutorials on our Youtube channel
if you'd like to be informed as soon as new video tutorials are published,
then please subscribe.
Thanks for watching