This topic was created by a BMC Contributor and has not been approved. More information.
LAMP stands for Linux, Apache, MySql, and PHP — the principal components to build a viable, general-purpose web server. This page presents an effective way to create individual packages in BMC Server Automation for the deployment of such web servers.
It makes more sense to use a Patch Analysis Job in 'Install Mode' to push out the RPMs so you make sure to get all the dependencies. If you don't include all the dependencies (which may vary for each target), you will end up with a failed Deploy Job and/or a broken installation. After that installation is done, you can use BLPackages to put out the configurations for each of the components.
To deploy a LAMP web server
- In the Depot, create a new RPM for each application and all of the dependent RPMs that need to be deployed.
For more information, see Deploying files and applications using packages and depot objects.
- For each application, create a BLPackage that includes all of the required RPMs, listed in the order that ensures all dependencies are covered.
For more information, see Adding a BLPackage to the Depot.
- Create a Deploy Job of each BLPackage for each application.
For more information, see Creating and modifying Software and BLPackage Deploy Jobs.
- Optionally, create a Batch Job of each of the Deploy Jobs that make up the entire LAMP stack.
For more information, see Creating and modifying Batch Jobs.
The following is a list of the dependent RPMs for deploying each member of the LAMP stack.
Sample importable BLPackage
The attached sample Install LAMP.zip includes a Batch Job that contains the following elements.
This BLPackage was exported from a BMC Server Automation 8.1 environment.