Question
Anthem
US
Last activity: 27 Jul 2019 7:32 EDT
How to avoid Listener ID changes for every Listener restart (via SMA) @ PRPC731.?
Hi Team,
Restart of a Listener during the maintenance period has been impacting the Listener ID based monitoring (as Listener ID changes for every Listener restart).Please suggest below :
1) How to stop new files processing without having to STOP/RESTART a Listener during the maintenance period ?
2) How to avoid Listener ID changes for every Listener restart (via SMA) ?
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
How to stop new files processing without having to STOP/RESTART a Listener during the maintenance period ?
It sounds like you're asking how you can stop a file listener from processing files without issuing the stop command. I can only think of two ways to stop a file listener from processing. 1) Stop it in SMA / Listener management. 2) Shutdown the node.
How to avoid Listener ID changes for every Listener restart (via SMA)
I'm not sure what specifically you mean by this. Can you provide screen shots showing this? Can you also explain your monitoring and how this impacts it?
Anthem
US
How to stop new files processing without having to STOP/RESTART a Listener during the maintenance period ?
It sounds like you're asking how you can stop a file listener from processing files without issuing the stop command. I can only think of two ways to stop a file listener from processing. 1) Stop it in SMA / Listener management. 2) Shutdown the node.
Hmm,not helpful suggestion.The reason we are going for a STOP/RESTART a Listener would be to avoid the processing of new files during the maintenance period.Any alternate suggestions ?
How to stop new files processing without having to STOP/RESTART a Listener during the maintenance period ?
It sounds like you're asking how you can stop a file listener from processing files without issuing the stop command. I can only think of two ways to stop a file listener from processing. 1) Stop it in SMA / Listener management. 2) Shutdown the node.
Hmm,not helpful suggestion.The reason we are going for a STOP/RESTART a Listener would be to avoid the processing of new files during the maintenance period.Any alternate suggestions ?
How to avoid Listener ID changes for every Listener restart (via SMA)
I'm not sure what specifically you mean by this. Can you provide screen shots showing this? Can you also explain your monitoring and how this impacts it?
We are monitoring the status of a Listener (based on listener ID) via HP BSM Synthetic Transaction setup.Listener ID gets changed during STOP/RESTART of the Listener via SMA / Listener management.
If the Listener ID gets changed,monitoring gets stopped and unwanted email alert gets generated.
Pegasystems Inc.
US
You can't stop the processing of a file listener without stopping it or the node. Perhaps a better alternative for you is to stop the process that is placing the files in the processing directory.
As far as the Listener ID, can you provide a screen shot or a document showing this?
Anthem
US
As far as the Listener ID, can you provide a screen shot or a document showing this? Please refer to the attachment.