Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Creating a JBoss 7.1 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 JBoss service blueprint, create a service and service offering based on the available deployment model. The JBoss service blueprint supports the following service deployment models:

Deployment model

Description

Single-tier

In the single-tier deployment model, JBoss, JDK and MySQL are installed on a single instance of a server.

Multi-tier

In the multi-tier deployment model, JBoss and JDK are installed on one instance of a server and MySQL is installed on a separate instance of a server. 

Standalone model

In the standalone deployment model, only JBoss and JDK are installed on a single instance of a server. MySQL is not installed.

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

  1. Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
    serviceinstances_request1.png
  2. In the New Service Request dialog box, click the server provisioning service you want to display in the Submit Request dialog box.
    serviceinstances_request_submit.png
  3. 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.
  4. 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 JBoss along with MySQL components setup in your environment.

Component name

How to verify

Results

OpenJDK or JDK installation

To check if OpenJDK or JDK is installed, run the following command:

java --version

It displays the JDK version.

 

JBoss directory verification

To verify JBoss directory under /opt, run the following command:

ls -ld /opt/jboss-as-7.1.1.Final

The JBoss directory is present.

JBoss port number verification

To verify JBoss listening ports (default port is 8080, 9990 and ajp port is 8009), run the following command: 

netstat -atpn | grep java | grep -v grep

The command output contains a list of port numbers.

JBoss server URL

To verify JBoss server, run the following command.

http://jbossserver:8080/
or
http://jbossserver:9990/

It displays the JBoss server page.

IPtables rules

To create IPtables rules for accessing 8080, 9990 and 8009 ports, run the following command:

iptables -A INPUT -p tcp --dport 8080 -j ACCEPT
iptables -A INPUT -p tcp --dport 9990 -j ACCEPT
iptables -A INPUT -p tcp --dport 8009 -j ACCEPT
service iptables save

IPtables rules are create at the following location:

/etc/sysconfig/iptables

 

 

 

Start JBoss service

To start JBoss service, run the following command:

/etc/init.d/jboss-as-standalone.sh start

chkconfig jboss-as-standalone.sh on

Starts the JBoss service.

 

MySQL Installation

To check if MySQL has been installed, run the following command:

rpm -qa | grep -i mysql-server

It displays the MySQL installation details.

Start MySQL service

To start the MySQL service, run the following command:

service mysqld start

Note: You can use this command when MySQL service is not running.

Starts the MySQL service.

Restart MySQL service

To restart the MySQL service, run the following command:

service mysqld restart

Note: You can use this command when MySQL service is not responding.

Restarts the MySQL service.

Where to go next

Once 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 the cloud end user can perform to manage your cloud services, see Managing-cloud-resources in the BMC Cloud Lifecycle Management online technical documentation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*