Faults exhibit as no responder queue being visible within the Black Pear infrastructure:
1. Check the responder service is running
2. If there is no responder service, recheck the prerequisites and each step of the installation process: https://support.blackpear.com/hc/en-us/articles/360055099231-SystmOne-Responder-Installation
3. Check the following log files for errors:
- C:\node\pyrusconnect-responder\clinicalLibraryResponder.errors.log
- C:\node\pyrusconnect-responder\daemon\pyrusconnectresponder.err
4. Check the content of c:\node\pyrusconnect-responder\config\default.json:
{
"logging": {
"level": "error"
},
"clinicalSystemQueue": {
"address": [
"amqps://username:password@tatooine.blackpear.thirdparty.nhs.uk"
],
"requestQueue":"queue name"
},
"windowsService" : {
"name": "pyrusConnectResponder"
}
}
- items highlighted in green must be as agreed with Black Pear
- quotes must also be checked and potentially replaced by editing in notepad
5. Check the responder is using the latest version: c:\node\pyrusconnect-responder\package.json
6. Check whether Black Pear can see the responder and if not, run telnet
api.t.blackpear.com
5671
from a command prompt
0 Comments