I'm hoping someone has had a look at this and has seen a way of making it work that I just can't see.
I've been reviewing the documentation for 4.3 and as far as I can tell with the new UA 'feature'
- The agent installation destination moves away from the existing structure (meaning any existing references, scripts, autodeploys need thrown away or updated dependent on how you progress UA)
- You can't attach new versions to existing instances post update unless you are using Oracle Hotspot JRE (that's about 1% of our estate)
- The rules in the rulebook for Java require an Application/Tier/Node to be defined, doesn't that mean one rule for each application node? That's 1,200 rules for us for each new agent version?? I'm sure I must have that wrong but can't see how it's meant to work.
Even if we wanted to use the above and use it for new deploys:
- we would need to maintain two deployment solutions and config
- there is more overhead creating rules than there is running a script to update a host
- we sized our AppD requirements based on original definition so now need at least double the capacity on every host
This is poor, even for AppD which is already very poor at providing means for managing the environment, roles, permissions and config.
... View more