Tip:
Highlight text to annotate it
X
In this tutorial, we are going to show you how to create an Apache application package
inside BladeLogic. We will create a software deploy job and add the package to the product
catalog. Finally, as proof of concept, we will use the Apache application package in
a service blueprint. Download the MSI
Get the MSI. We simply went to the Apache website and downloaded the MSI that we wanted
to use. Searched for Apache HTTPD for Windows and
searched for the Download link. Selected Stable Release > Binaries > win32
because we want to install on Windows Select a Microsoft Software Installer package
from the list, that is, an MSI. Download it to a folder where you can easily
access it. Discover the parameters you’ll need to install
the MSI properly. If you simply ran the MSI, you’d learn that
there are bunch of parameters you’d need to add.
Admin’s email address Server name
Port to run on You can feed all these parameters into the
MSI running from the silent installer Here’s how to get the input names
Open command window Change to directory
and run msiexec /I (for install) msi name /L*v ApacheInstaller.log
Pipes out a bunch of the information to a log file
Scan through log, looking for PROPERTY CHANGE values that look like inputs
For example – SERVERADMIN and SERVERNAME Create the folder structure inside BSA
We’re first going to create the folder structure inside the Depot
Open the Bladelogic Console Click Depot.
Create a Depot folder and name it CSM_Applications. Now create folders to sort out your operating
systems, for example, Windows, Linux, and so on. For now I’ll just create a Windows
2008 folder. Add the software to the Depot.
Right-click the Windows 2008 folder. Select New > Software, and then select MSI
package. Browse to locate the MSI package.
Add MSI customization properties and finish the MSI package.
We know that to get the MSI to install properly, we must specialize some customization properties.
These are inputs to the MSI file. We’re going to create two name/pairs.
Enter SERVERADMIN, then select a value. Type in admin@ and then you’ll want to select
the name of the server, for example, in BladeLogic, TARGET>HOST and add it.
SERVERNAME and also add the HOST property Find the SERVERPORT as well
Click Finish to complete the wizard. Create the BLPackage. It functions as a wrapper
around the MSI. It’s a powerful way to group multiple files
and installers and configurations together in one package. Also, we will modify the BLPackage
later to parameterize our package. Right-click the Windows 2008 folder.
Select New > BLPackage, and then select MSI package.
We’ll name it Apache for Windows Select Depot software and browse to the MSI
we just added. Click Finish.
It’ll create a new BLPackage in the Windows 2008 directory.
Deploying the package Open the BLPackage.
You can add other commands or assets, as needed. But we’re just going to deploy it.
Right-click it and select Deploy. Name the deploy job and add it to the Jobs/CSM_Applications
folder. It’ll create a job in CSM_Applications.
Modify the deploy job For this Apache deploy job, we must modify
it. We’ll select the job and scroll down the
Properties list and modify 3 properties: PRODUCT_MANUFACTURER
PRODUCT_NAME PRODUCT_VERSION
Run the Publish Catalog Job Under Jobs, select CSM_Publish_Product_Catalog
> Publish_Product_Catalog_Job. Review the results. You should see one entry.
Go to CLM Console. If CLM is open, log out and log back into
the console. Open the Service Designer.
Create a new blueprint or open an existing blueprint.
Create a new application blueprint. Name it Apache.
Select Software Packages and click New to add a package.
Select the package from the list. Now you have an Apache blueprint.
We can modify this blueprint later if we need to, for example, to request a specific port
in Apache.