Deployment of Rules, Rule Sets, and PASDefs

This means that several PASes can share a single registry image and, at the same time, the registry image can also be used to store Rules, Rule Sets, or PASDefs for other BMC AMI Ops Automation PASes that do not share the registry image. This is the concept of a central repository for your Rules, Rule Sets and PASDefs. All the Rules, Rule Sets, and PASDefs reside in the central repository from which you can deploy them to remote registries for the BMC AMI OpsA PASes to use.

You can deploy based on levels: Rules, Rule Sets, and PASDefs. During deployment, you must set the following two options:

• Replace (YES | NO) objects in the target PAS

• Activate (YES | NO) objects in the target PAS.

  You can choose to deploy without activating (ACTIVATE=NO) and wait for the next cold start of the PAS or use some other manual means to activate the Rules or Rule Sets. If you choose ACTIVATE=YES, the object(s) and all lower level object(s) are deployed and activated at one time.

To determine what deployment level is needed (Rule, Rule Set, or PASDef) you need know the highest level that was changed. The PASDef is at the highest level and the Rule is at the lowest level.

For example, if you create a new Rule and add it to an existing Rule Set, the highest level that was changed was the Rule Set level. Therefore you must deploy and activate the Rule Set. If, however, a new Rule Set was also created for the new Rule and you added the Rule Set to an existing PASDef, then you must deploy and activate the PASDef.

Deploy tagged items

You can initiate the DEPLOY process on any of the following BMC AMI OpsA views:

• PASDEF
• RULESET
• RULES

You can use deployment to store definitions in a different local BMC AMI OpsA registry or, to send the definitions to a different AOPlex  within the current CASPlex.

The DEPLOY command copies the tagged Rules, Rule Sets, or PASDefs to another system by using CAS-to-CAS communications. It invokes a series of dialogs that sends the tagged items to another target (typically another AOplex) without requiring you to export and import the Rules registry to another CAS.

On any of the views, enter the TAG (T) line command next to the definitions you want to deploy, enter DEPLOY on the COMMAND line, and press ENTER. The Deployment dialog is displayed and you can enter values for the deployment.

Manage and monitor the deployment process

You can use the DPLYMNT view to monitor and manage the deployment process. The DPLYMNT view displays a list of deployment requests along with status information about each request. From the DPLYMNT view, you can perform the following actions:

• Stop, start, delete, and cancel deployment requests by using the line commands
• See details about a deployment request by using the Select line command, which displays additional information about the request
• See details about the status of a deployment request by hyperlinking from the status, which displays the LOGDEPLM view.

Automating Deployment for RULES, RULESET, or PASDEFs

You can also automate deployment. Instead of manually using the DEPLOY commands on the RULES, RULESET, or PASDEF views, you can use  distributed sample REXX EXECs to export and import the deployment packages. Copy the sample EXECs from the BBSAMP data set and modify the EXECs to export and import registry items whenever the EXECs are scheduled. The two distributed EXECs are:

• QDPLEXPT
• QDPLIMPT
  
  

QDPLEXPT

This sample EXEC exports a RULE, RULESET, or PASDef to a partitioned data set (PDS) member that you create and specify. The EXEC triggers a deployment package to be built and saves it in the specified PDS.

A Host Server must be available to use this EXEC and the Host Server must have access to the PAS that is running the modified EXEC. You can use the EZAOSOL view to identify which Host Server the export process will use. The PAS performing the export, as well as the PAS that will be performing the import, must each have a Host Server identified using the EZAOSOL view for the PAS.  The sample EXEC includes detailed instructions for editing the EXEC in the comments section.  

QDPLIMPT

This sample EXEC imports a previously exported deployment package. The EXEC triggers a deployment package to be read from the specified PDS and deployed into the PAS that is running the import EXEC. The deployment package includes instructions for whether to replace existing items and activate the items once they are deployed.

A Host Server must be available to use this EXEC and the Host Server must have access to the PAS that is running the modified EXEC. You can use the EZAOSOL view to identify which Host Server the export process will use. The PAS performing the export, as well as the PAS(es) that will be performing the import, must each have a Host Server identified using the EZAOSOL view for the PAS.  The sample EXEC includes detailed instructions for editing the EXEC in the comments section.