|BRPM Automation Info|
|Type: Resource Automation|
|RPM Compatible Version: 4.3 and higher|
|Integration type: BAA/BSA|
Created by: Fred Breton
This resource automation provides a list of provisioning actions. This list will depend of the blueprint that has been defined in the same step. In BSA side an action is a BlPackage and the list of action provided is the list of package found in Depot/BRPM/Provisioning/<blueprint name>. If no blueprint is defined, then action are coming from the BlPackage found in Depot/BRPM/Provisioning/Generic
Those package has to be named with the following rule: <action name>-<OS> where <OS> has to be a value we can find in the OS property of the object server or it has to be Unix. This extension is used to specify for which OS the BlPackage has been created for. As it is easy to have package that can run in any Unix flavour, it is possible to use extension Unix to specify that the package is for all Unix. So, you may have several BLPackages with the same action name and different OS extension. The resource automation provides a list of non duplicated action names.
You need to create an integration server pointing to your BladeLogic server to point the API (if not already done). FromSystem > Integrations, click Create new Integration at the right side of your screen:
Server Name: <up to you>
Server URL: <BladeLogic Webservice url; example: https://bl-appserver:9843>
Username: <BLadeLogic user>
password: <password of previously defined user>
Details: role: <role you want to use; example BLAdmins>
authentication_mode: <example: SRP>
If you want to create a new automation category for BSA associated resource automation and automation follow the documentation Managing automation categories.
Instruction for importing the resource automation:
- Click on the link bsa_provgetaction.rb to download the resource automation
- Copy the file to your BRPM server in
<BRPM install dir>/WEB-INF/lib/script_support/
Automation category is one you may have created (requirements) and you may need to create the associated directory, or one already existing.
- From the BRM Console you need to import the resource automation, Environment -> Automation, click on Import scripts from Library on the right top of the screen.
- Select the integration server (the BAA/BSA server you'll connect to), to use as -> resource automation, and the Category in which you've classified your resource automation.
- A list of non already imported resource automation should appear. Check the box associated with the script you want to import. Click import button.
The following files that are script libraries that need to have been copied on <BRPM install dir>/WEB-INF/lib/script_support folder of your BRPM server: bsa_utilities.rb and script_helper.rb (the last one replacing the file provided with the product) . After those files have been added to the environment, you need to restart BRPM.
Automation script that use this resource automation as an external resource for an argument needs to have at least an other argument named Target_Blueprint that has to be valuated before bsa_getaction resource automation can populate its list.
*Note: This is a community supported content