Creating an Apache Tomcat on RHEL service offering

This topic describes the tasks that you must perform in BMC Cloud Lifecycle Management to create the service offering that the end user can then use to provision the application infrastructure (for example, an OS and an application package).

Note

Although services and service offerings are bundled with the zipkits, you might want to use the procedures to create a service and service offering to create or edit these artifacts.

It includes the following topics:

To create the service and the service offering

In the BMC Cloud Lifecycle Management Administrator console, you must add a service and a service offering.

For Apache Tomcat service blueprint, you can create a service and service offering based on the available deployment model. The Apache Tomcat service blueprint supports the following service deployment models:

Deployment model	Description
Single-tier	In the single-tier deployment model, Apache Tomcat, JDK and MySQL are installed on a single instance of a server.
Multi-tier	In the multi-tier deployment model, Apache Tomcat and JDK are installed on one instance of a server and MySQL is installed on a separate instance of a server.

To create a service

Excerpt named creatingservice was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

To create a service offering

Excerpt named creatingserviceoffering was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

To make the provisioning request

Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
In the New Service Request dialog box, click the server provisioning service you want to display in the Submit Request dialog box.
Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
Click Submit. The request is added to the Pending Activity list in the Service Instances window.

The request status is displayed in the Pending Activity list of the Service Instances window. You can double-click on the service request to see its detailed information.

For more detailed procedures, see Requesting-cloud-services and Requesting-cloud-services-in-the-legacy-console.

To validate the provisioned components

After provisioning the blueprint, you can validate the Apache Tomcat along with MySQL components setup in your environment.

The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Where to go next

After you have created the service offering, the cloud end user can request a service offering from the My Cloud Services console. To view a list of tasks that the cloud end user can perform to manage your cloud services, see Managing-cloud-resources in the BMC Cloud Lifecycle Management online technical documentation.