Posted: 16 Mar 2021 18:15 EDT Last activity: 16 Mar 2021 18:21 EDT
Until Pega7, SMA was a separate lightweight war installation and during scenarios where the Pega DB is overloaded either due to a one-off listener/batch processing, we had the option to access SMA and interrupt/stop the relevant requestor towards quickly restoring application performance.
In Pega 8, Admin studio is bundled under the same WAR Installation, so if the DB is running hot and if we want to turn off something, is there a way to handle SMA Operations outside? Without having to login to the application?Because when the PegaRULES DB is running hot, the dev studio login doesn't work/ is extremely slow and consequently we won't be able to perform these admin operations(like stopping agents for example) towards quickly restoring application performance
Has anyone else come across the same situation in Pega 8.x