Creating a MediaWiki on RHEL 6.3 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). 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 a MediaWiki service blueprint, you can create a service and service offering based on the required deployment model. The MediaWiki service blueprint supports the following service deployment models:
Deployment model | Description |
|---|---|
Single-tier | In the single-tier deployment model, MediaWiki is installed on a single instance of a server along with Apache, PHP, and MySQL. |
Multi-tier | In the multi-tier deployment model, MediaWiki is installed on a single instance of a server along with Apache. PHP and MySQL will be installed on another instance of a server. |
To create a service
- From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
- In the Service Catalog, click Create a New Service
. - Enter the service name.
- For Type, select a service type.
- Business service — Services that customers use and that show the customer view of services, such as email or an online store.
Technical service — Supporting IT and infrastructure resources required to support business services that are not visible to customers, such as servers, applications, and network CIs.
- Enter a description of the service.
- Do one of the following actions:
- To create the service offering, click Apply.
- To create the service offering later, click Save to save your selections and close the window.
To create a service offering
- From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
- From the Service Catalog, edit or create a service.
In the Service Offering tab, a default service offering is available, which you can edit. - Click Create a New Service Offering.
In the General Information tab, define the options described in the following table.
Option
Description
Default Service Offering
Enable this option to make the selected service offering the default for the service. Unless users select a different service offering, the default service offering is used.
Name
A short, descriptive name for the service offering.
Description
A more detailed description of the service offering.
Service Blueprint
Specify the software and hardware to associate with the service offering by selecting one of the available blueprints.
Service Deployment Definition
Specify how to deploy the selected service blueprint. From the list, select a service deployment definition that is available for the chosen service blueprint.
- Add a Base Customer Price to define the amount charged to the customer for the service offering.
- Add a Base Deployment Cost to define the amount that it costs to provide the service offering.
- Click Apply.
This action activates the Options tab. You now also can create a requestable offering (for example, a request definition or a post-deploy action). For additional information, see Creating-a-requestable-offering in the BMC Cloud Lifecycle Management online technical documentation.
To create options and option choices for the service offering
In the BMC Cloud Lifecycle Management Administrator console, you can add options and option choices for the service offering.
To create options
For the MediaWiki Content-Pack, you can create options to set up the authentication type and enable upload and caching.
In the MediaWiki environment you can set up any one of the following authentication types:
- Traditional Wiki - The user can edit the MediaWiki content. This authentication type is the default in MediaWiki. No user logon is required for this authentication type.
- Account creation required - This authentication type provides accountability for MediaWiki. You need to create an account to access MediaWiki for this authentication type.
- Authorized editors only - Only approved users can edit the content. In this authentication type, the MediaWiki content and page history are available for public users.
- Private Wiki - An approved user group can view or edit the MediaWiki content.
To create options for the service blueprint:
- Launch BMC Cloud Lifecycle Management Administration console and click Service Catalog from workspace.
- Click Option Editor. This displays Option Editor window.
- Click Add
to add a New Option.
Enter the Option Name, Option Type and Option Description.
- Click OK to create this option.
Once you have created the option, you need to create an option choice.
To create option choices
After you have created the option, you need to create an option choice.
To create an option choice, complete the following steps:
- Navigate to the Option Editor and select the created option name to create option choice.
- Click Add
to add a new option choice.
- Enter Option Choice and Description.
- Click OK.
This creates the option choice.
To configure the option choices
To configure the Option Choice with the service blueprint, complete the following steps:
- Open Option Editor.
- Select the option created for the service blueprint .
- Select the option choice and click Option Choice Blueprint Configuration Editor
.
- Click Add
to add new blueprint configuration for the selected option choice.
- Select Custom Action from the blueprint configuration list.
- Select Action Type as Script and enter the NSH script name in Action.
- Click OK.
Repeat step 1 through step 7 for each of the following option choices. For each option choice, you need to enter the corresponding NSH script name in the Action field as listed in the table below:
Option choice | NSH script |
|---|---|
Account creation required | MediaWikiAccountCreationRequired |
Authorized editors only | MediaWikiAuthorizedEditorsOnly |
Private Wiki | MediaWikiPrivateWiki |
Enable uploads | MediaWikiEnablingUploads |
Enable caching | MediaWikiEnablingCaching |
The process to create and configure an option and option choice for a service blueprint is complete. For additional details, see Service-Catalog-options-and-option-choices in the BMC Cloud Lifecycle Management online technical documentation.
To provision a service
After you have created the service and the service offering, you need to specify the following Parameters to provision a MediaWiki service:
- Access Workspaces > Service Instances to display the Service Instances workspace, and then click the New Service Request icon.

- In the New Service Request dialog box, click the server provisioning service that you want to request.
In the Submit Request dialog box, specify the following Parameters:
Parameter
Description
DataBase Name
Name of the database created for MediaWiki.
DataBase password
Database password for MediaWiki database user.
Confirm
Confirmation of database password for MediaWiki database user.
DataBase prefix
Prefix for database table names.
DataBase user name
Database user name to access the MediaWiki database.
MySql root password
Password for MySql database for root user.
Confirm
Confirmation of password for MySql database for root user.
Webserver port
MediaWiki webserver port.
Wiki Admin User Password
Password for admin user to access MediaWiki.
Confirm
Confirmation of password for admin user to access MediaWiki.
Wiki Admin UserName
Admin user name to access MediaWiki.
WikiName
Name of wiki that appears on title bar of the browser.
Click Next.

- Enter the data in the required fields to complete the 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 the service request to see detailed information.
For more detailed procedures, see Requesting cloud services.
To validate the provisioned components
After provisioning the blueprint, you can validate the MediaWiki components setup in your environment.
Component name | How to verify | Results |
|---|---|---|
Verify MediaWiki webpage | Open MediaWiki URL using any browser: http://hostname:portnumber/mediawiki | The browser displays the MediaWiki default webpage. Note: If the MediaWiki webpage is not displayed, ensure that Apache is running and the Apache port specified in the URL is correct. |
Apache installation | To check whether Apache is installed, run the following command: rpm -qa | grep -i httpd
| The command displays the following output: httpd-tools-2.2.15-15.el6_2.1.x86_64 httpd-2.2.15-15.el6_2.1.x86_64
|
Apache port | To verify the Apache port, run the following command: netstat -atpn | grep -i httpd or grep -i "^Listen" /etc/httpd/conf/httpd.conf | The command displays the port number on which Apache is running. |
Verify httpd service status | To verify httpd service status, run the following command: service httpd status | The command displays the process ID for the httpd service: httpd (pid xxxx) is running Note: If process ID is not displayed, ensure that the MySQL service is running. |
httpd service restart | To restart httpd service, run the following command: service httpd restart | The httpd service restarts. |
MySQL Installation | To check whether MySQL is installed, run the following command: rpm -qa | grep -i mysql-server | The command displays the following output: MySQL-server-5.6.13-1.rhel5
|
Verify MySQL service | To verify MySQL service status, run the following command: service mysqld status | The command displays the following output: mysqld ( pid xxxxx ) is running. |
Restart MySQL service | To restart MySQL service, run the following command: service mysqld restart | The MySQL service restarts. |
PHP Installation | To check whether PHP is installed, run the following command: rpm -qa | grep -i php
| The command displays the following output: php-5.3.3-3.el6_2.8.x86_64 php-gd-5.3.3-3.el6_2.8.x86_64 php-xml-5.3.3-3.el6_2.8.x86_64 php-cli-5.3.3-3.el6_2.8.x86_64 php-pdo-5.3.3-3.el6_2.8.x86_64 php-pear-1.9.4-4.el6.noarch php-common-5.3.3-3.el6_2.8.x86_64 php-mysql-5.3.3-3.el6_2.8.x86_64 php-pecl-apc-3.1.9-2.el6.x86_64 php-intl-5.3.3-3.el6_2.8.x86_64 |
Verify Enable upload | To verify whether uploads are enabled, run the following command: grep -i EnableUploads /var/www/html/mediawiki/ LocalSettings.php Open the LocalSettings.php file and check the value for $wgEnableUploads. | If the value for $wgEnableUploads is set to true, uploads are enabled. |
Verify Enable caching | To verify whether caching is enabled, run the following command: grep -i MainCacheType /var/www/html/mediawiki/ LocalSettings.php | The command displays CACHE_ACCEL, which means caching is enabled. If the output shows CACHE_NONE, caching is disabled. |
Considerations for a MediaWiki multi-tier environment
In MediaWiki multi-tier environment, your MediaWiki server is provisioned on one instance and the MediaWiki database is provisioned on a separate instance. You need to execute the MediaWiki option on the MediaWiki server ONLY.
To verify the MediaWiki server:
- Go to Service Instance > MyServices > Servers.
- Check that the selected MediaWiki server contains the Deployed Software as Apache and PHP.

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-services in the BMC Cloud Lifecycle Management online technical documentation.