How are you manually provisioning and scaling your webMethods Integration Server environments, or via tools like Ansible, Puppet, Attune, PDQ Deploy or Terraform?
Old companies usually keep doing whatever they have been doing past 20 years. They are usually reluctant to make any changes. If you are looking for most up to date technology for scaling webMethods products, you can use webMethods helm charts.
What’s your preferred method for monitoring, log aggregation, and alerting (especially across hybrid or multi-cloud deployments)?
There are a lot of options here. It depends on where your application runs (kub8, docker, azure, aws, etc) and what you have available in your tech stack. You can push your logs to 3rd party, monitor your environment with products like dynatrace or rely on Command Central. Command Central is part of webMethods stack and can monitor, update licenses, start/stop/restart instances create new one, in other terms it can usually do everything you can with admin UI of each app.
Are you using CI/CD pipelines to deploy changes to Software AG products? If so, how do you handle state management and rollbacks?
This is a very broad topic. As long as you keep your packages versioned, you don’t need to worry about the rollbacks, you can simply deploy the old version or push the old version somewhere like artifectory. Not sure what you mean by state management here. If you use helm charts, you can version your infrastructure code as well (helm charts are basically a repository for Infrastructure as a Code, you can version control everything and rebuild all of your environment in literaly 2 seconds)
Any recommendations for automating license checks, service restarts, or cleanup routines?
If you need service restarts, that means you have bad code. You are probably overthinking the other items here.
You can manage your licenses in your kub8 cluster or through Command Central or you can monitor the logs. No need to overthink this though. In worse case scenario, you need to update the license files once in a year. Even if you automate it, you might break it while working on something else. If you need to automate it consider deploying your products to kubernetes.
Looking to share ideas, scripts, or playbooks that have helped improve uptime and reduce toil in managing enterprise integration infrastructure.
In the past, the scripts, automated tasks etc, weren’t readily available. If you need any of these items, consider deploying your products to kubernetes and using helm charts and version control everything (code and infrastructure). Using helm charts you can automatically scale your pods, configure them to self heal (it basically kill the pod and recreates it immediately) and also can isolate your cluster from the outside world hence provide additional security.