Multitier architecture (often referred to as n-tier architecture) or multilayered architecture is a client-server architecture in which presentation, application processing, and data management functions are physically separated.
Before we start create blueprint for multi-tier application we need to check if our user has correct role. For blueprint development we need that roles
|Application architect To successfully add software components to the design canvas, you must also have business group member, business group administrator, or tenant administrator role access to the target catalog.||Assemble and manage composite blueprints.|
|Infrastructure architect To successfully add software components to the design canvas, you must also have business group member, business group administrator, or tenant administrator role access to the target catalog.||Create and manage infrastructure blueprint components. Assemble and manage composite blueprints.|
|XaaS architect||Define custom resource types. Create and publish XaaS blueprints. Create and manage resource mappings. Create and publish resource actions.|
|Software architect To successfully add software components to the design canvas, you must also have business group member, business group administrator, or tenant administrator role access to the target catalog.||Create and manage software blueprint components. Assemble and manage composite blueprints.|
To check our roles we need go to the Administration –> Users & Groups –> Directory Users and Groups
In search provide username and edit by click on it .
As we have correct roles assigned we can create blueprint for multi-tier application.
First step is to create a software component which will install our app
Software Component is a simple piece of code which we can run on 5 different Lifecycle of deployment
|Life Cycle Actions||Description|
|Install||Install your software. For example, you might download Tomcat server installation bits and install a Tomcat service. Scripts you write for the Install life cycle action run when software is first provisioned, either during an initial deployment request or as part of a scale out.|
|Configure||Configure your software. For the Tomcat example, you might set the JAVA_OPTS and CATALINA_OPTS. Configuration scripts run after the install action completes.|
|Start||Start your software. For example, you might start the Tomcat service using the start command in the Tomcat server. Start scripts run after the configure action completes.|
|Update||If you are designing your software component to support scalable blueprints, handle any updates that are required after a scale in or scale out operation. For example, you might change the cluster size for a scaled deployment and manage the clustered nodes using a load balancer. Design your update scripts to run multiple times (idempotent) and to handle both the scale in and the scale out cases. When a scale operation is performed, update scripts run on all dependent software components.|
|Uninstall||Uninstall your software. For example, you might perform specific actions in the application before a deployment is destroyed. Uninstall scripts run whenever software components are destroyed.|
For software component we need to fill in 4 Step:
- General Tab where we need to provide the Name, ID, Description and for which element we are creating this.
2. Properties Tab is place where we can create a new item for our code
3. Action here is the all fun where software components get LifecycleAction. For every element we can creat Bash, cmd or powershell script.
4. Last element is only confirmation for that what we created in previous steps
After software compontent is created we can merge all element in one multi-tier blueprin. In blueprint we need to add the VM container, and software component as well
After creation the blueprint is ready to request