Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Administering Rules across multiple sysplexes: deployment and AOPlexes

You can define as many AOPlexes in your system as you need. An AOPlex might be one 

BMC AMI Ops Automation

 PAS or it might contain many PASes.

Related topic

Automating with Rules

Regardless of the level of registry sharing in an AOPlex, you have the ability to deploy Rules and Rule Sets to remote registries. This ability means that several PASes can share a single registry image and, at the same time, the registry image can also be used to house Rules and Rule Sets for other BMC AMI OpsA PASes that do not share the registry image.

The following is an example of how you might administer Rules across multiple sysplexes.
GUID-ACDA6E0D-4DDF-4755-9185-FCDFB783749E-low.png

The level of registry sharing and how centralized you want to make your Rules management is up to you. With deployment, it can be as centralized or as de-centralized as your needs dictate.

Warning

Important

An AOPlex cannot span across sysplex boundaries. This is a limitation of using the RTCS registry. However, if your CASes are connected by way of TCP/IP, you can access, edit, add, and deploy Rules on another sysplex. For more information about the AOPlex, refer Customizing-BMC-AMI-Ops-Automation-after-installation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3.01