Solution Types in SAP BUSINESS ByDesign
What is a solution? A solution is really the package of development for the SAP
Cloud Applications Studio.
It'll have the collection of different development objects or artifacts that you will build and
create and maintain. And then we can use these to move this content to other tenants, whether it be a test or production, etc.
Now there are three types of solutions that we'll talk about. First one is a solution template,
the second is a customer-specific solution, and the third is a patch solution
Solution template. A solution template contains development objects that will be there for
reuse, meaning you can apply them to other solutions.
The development of a solution template would continue through different upgrades. So if you
have a solution template you can continue to maintain it through each release. And this content then can continue to be updated and deployed over and over again.
This means that if I have a customer-specific solution, I would take a solution template, I would
apply it to that customer-specific solution, and then I could continue to maintain the template, and keep applying it to the solution and keep the content updated in that customer-specific solution.
One restriction around solution templates is they cannot contain items, that requires what we
call “Admin Mode”.
This is things that consider analytics, forms, a few other items, which we'll see when they come
up. So this is something that I can develop on either my partner development tenant, on a
customer's test tenant, and I can apply it to any customer's specific solution. So I can reuse something ideally, something that I think I might use often or want to use more than once, I would put it in the
solution template. And then we'll need to further use it in the customer-specific solution.
Now, what is a customer-specific solution?
This is the main type of solution that we'll work within the Cloud Applications Studio.
A customer-specific solution is exactly that. It's a solution that's only for one particular
customer.
That means if I develop something for customer A, I cannot take that same customer-specific solution, and deploy it to customer B's tenant.
This type of reuse of a customer-specific solution is not allowed. If I have that type of scenario,
I would want to use a solution template, in which case I would develop as much as I possibly can in that template, and then I could
apply it to customer A's tenant as well as to customer's B's tenant.
So a customer-specific solution, it can contain any kind of content, including anything that
requires Admin Mode. And then I can apply that to a customer's production tenant or to other
test tenants.
One thing about these solutions is that we can only develop either in a partner development
tenant or in a customer's test tenant.
Now I would not be able to create new solutions in a customer's production tenant. We'll see a
little bit more about that when we get to the lifecycle.
But for now, we'll use a customer-specific solution in our test tenant.
The third type of solution is a patch solution. Now this still relates to a customer-specific
solution.
But a patch solution is after we've initially deployed the customer-specific solution, how do we
maintain it going forward?
A patch solution will be created off of any customer-specific solution, and then we would then
make our changes and updates within this patch solution
Cloud Applications Studio.
It'll have the collection of different development objects or artifacts that you will build and
create and maintain. And then we can use these to move this content to other tenants, whether it be a test or production, etc.
Now there are three types of solutions that we'll talk about. First one is a solution template,
the second is a customer-specific solution, and the third is a patch solution
Solution template. A solution template contains development objects that will be there for
reuse, meaning you can apply them to other solutions.
The development of a solution template would continue through different upgrades. So if you
have a solution template you can continue to maintain it through each release. And this content then can continue to be updated and deployed over and over again.
This means that if I have a customer-specific solution, I would take a solution template, I would
apply it to that customer-specific solution, and then I could continue to maintain the template, and keep applying it to the solution and keep the content updated in that customer-specific solution.
One restriction around solution templates is they cannot contain items, that requires what we
call “Admin Mode”.
This is things that consider analytics, forms, a few other items, which we'll see when they come
up. So this is something that I can develop on either my partner development tenant, on a
customer's test tenant, and I can apply it to any customer's specific solution. So I can reuse something ideally, something that I think I might use often or want to use more than once, I would put it in the
solution template. And then we'll need to further use it in the customer-specific solution.
Now, what is a customer-specific solution?
This is the main type of solution that we'll work within the Cloud Applications Studio.
A customer-specific solution is exactly that. It's a solution that's only for one particular
customer.
That means if I develop something for customer A, I cannot take that same customer-specific solution, and deploy it to customer B's tenant.
This type of reuse of a customer-specific solution is not allowed. If I have that type of scenario,
I would want to use a solution template, in which case I would develop as much as I possibly can in that template, and then I could
apply it to customer A's tenant as well as to customer's B's tenant.
So a customer-specific solution, it can contain any kind of content, including anything that
requires Admin Mode. And then I can apply that to a customer's production tenant or to other
test tenants.
One thing about these solutions is that we can only develop either in a partner development
tenant or in a customer's test tenant.
Now I would not be able to create new solutions in a customer's production tenant. We'll see a
little bit more about that when we get to the lifecycle.
But for now, we'll use a customer-specific solution in our test tenant.
The third type of solution is a patch solution. Now this still relates to a customer-specific
solution.
But a patch solution is after we've initially deployed the customer-specific solution, how do we
maintain it going forward?
A patch solution will be created off of any customer-specific solution, and then we would then
make our changes and updates within this patch solution
0 comments:
Post a Comment