If you have recently upgraded from Actional Intermediary 10 to Aurea Monitor 12, you'll find that clustering is not recommended on 12.x and you should not be using it. Clustering enabled any Service Group changes to be automatically updated on all load-balanced members. We have answered some FAQs for when you need an automated method to push all changes to load-balanced nodes, or how to create your own automated job to do this.
Why is clustering no longer recommended?
The configuration replication using clustering is no longer supported with Launcher as it doesn't fit the new architecture.
What are the specific steps Aurea now recommends to push changes to all load balanced nodes?
Refer to the KB article, Clustered Intermediary Instances Don't Replicate The Configuration, for specific steps you need to follow to deploy using an export profile.
Manually exporting then importing service group changes is time-consuming and subject to errors. Is there a way to automate any changes made on one node to the others?
You may use the export profile features to distribute the configuration to other Intermediary instances. Refer to the KB article, Clustered Intermediary Instances Don't Replicate The Configuration, for more information on deployment strategy using an export profile.
Why does Clustering Configuration still have a page on the Admin GUI if it is no longer used?
There is one use case where clustering is still required in 11.x & 12.x versions. Refer to the KB article, Intermediary | Why/When to use an Intermediary cluster, to check for applicability and steps for 11.x+ versions.
Is there any way to automate the export/import and/or replication across nodes without having to log on to each server and perform the manual tasks? Maybe an API we can call or some other workaround?
Out of the box, there isn't any tool to automate this however both AI and Monitor server provides DeploymentTask/ExportTask API that you may use to automate the deployment. Please refer to the WSDL bundled with anttask.zip (you will find the WSDL under WSDL folder after extracting it).