Hi I'm Lisa and this is Sathya, were with HP Cloud Service Automation and today were going to show you how cloud service automation can provision and flex a three-tier application. So were going to start coming in as consumers with the consumer portal. Sathya what are we looking at here? So we are looking at the consumer portal when the consumer logs into the cloud service automation this is where he comes in on a dashboard. So you can see under the popular services you have a three-tier application and he can go from there directly to provisioning to that three-tier application.
Okay so this is where were going to order this service.
Any service requests you want to do you have to have a subscription because that's useful for the consumer to understand why this was created, what was created. So let's take this from a health insurance company prospective so we can make some context when we are defining these applications.
Okay so here were just going to create a health insurance application.
And as an insurance application there is no end date it will be going for all the time. So we don't have to have an end date specified for that. So it starts form today and it never expires. So that means if my organization gets bought out by somebody that's when I come back here and say I don't need this but until then it's fine.
So as we said this is multi-tier, three-tier application so you can see there is a database component, there is a web server component and an application component and the load balancer is basically to provide a continues access to the application. So even when the server is down the server will pick up the load and you can balance the performance and availability of that application.
So let's connect to the database. So the database has multiple components. One is the actual server where the database is hosted. So that's the server provisioning. So we can define whether you want a small system, a large system, medium system depending on how big I want to create it. And also the service level where you can say that, whether you want this to be a very secure environment, high available and what kind of environment do you need to provide for the backup and power supplies you want so you want a DR and all those things can be combined and provided into a service-level concept.
So will have different service levels so will just take it as a small end server from the point of provision of this server.
Okay and those different options would probably have different prices associated with them and so you would have to choose you have to balance how much security you want versus how much you want to pay. Correct.
And then that is a server so typically when somebody says three-tier application here is the database server but you need to install a database and you have to install an application and everything but here we are installing the application but also providing the functionality where a database is created on that system. So will go ahead and configure a database name so that means this database is created for this particular application and then that can be used by the application on the day on the day itself. It doesn't have to be like you have to go through another three days of a DBA trying to fix something it's already down here so that means you are already ahead of your provisioning process.
And then next is the web server. We need to define so web server again has multiple different technologies as from a software prospective we can use Apache we can use ISS there are multiple ready ways of applications that can be used as a web server. So once you define the application that you want to use here again you define the number of serves that means each tier like you have a database tier you have a web service tier in web service tier you can have one web server or multiple web servers. That said a very good example when we talking about the insurance agents and agents offices. So in the main center you have a database which is secure and each of the offices can have their own application server and web server. That means they are not constrained by somebody's heavily using that, there performance will still be guaranteed that they can still utilize the systems.
Okay very cool.
So and again after the web services you still have the application server and the application server has a very identical capability of selecting different application server what you want to use and also number of servers and the size of the server you want to use. So this is more like your designing how your application should sit and then run it. So once you design that, all you need to do is go ahead and request your service.
To learn more information about HP cloud service automation or to see more video demos please visit our web site.