Fix RPCBrokerCheck.py log file generation
Fix RPCBrokerCheck.py log file generation

When creating the connection header for the RPCBrokerCheck.py.in file, it
was copied from another OSEHRA script.  The log file given to the
connect function was not changed, which will overwrite an important log.

Change the log file to be unique to the RPC Broker check.

OSEHRA-Id: http://issues.osehra.org/browse/OAT-107
Change-Id: Ic02eb05fe34091e3423d50ac2652152a3a07f6e7

mdgeek/VistA-FHIR-CWF,mdgeek/VistA-FHIR-CWF,timmvt/VistA_tt,mdgeek/VistA-FHIR-CWF,josephsnyder/VistA,shabiel/VistA,shabiel/VistA,shabiel/VistA,shabiel/VistA,shabiel/VistA,josephsnyder/VistA,mdgeek/VistA-FHIR-CWF,apexdatasolutions/VistA,OSEHRA-Sandbox/VistA,timmvt/VistA_tt,OSEHRA/VistA,apexdatasolutions/VistA,OSEHRA/VistA,OSEHRA-Sandbox/VistA,josephsnyder/VistA,josephsnyder/VistA,OSEHRA-Sandbox/VistA,OSEHRA/VistA,timmvt/VistA_tt,mdgeek/VistA-FHIR-CWF,timmvt/VistA_tt,timmvt/VistA_tt,shabiel/VistA,OSEHRA-Sandbox/VistA,OSEHRA-Sandbox/VistA,OSEHRA/VistA,josephsnyder/VistA,OSEHRA/VistA,OSEHRA-Sandbox/VistA,mdgeek/VistA-FHIR-CWF,apexdatasolutions/VistA,apexdatasolutions/VistA,apexdatasolutions/VistA,josephsnyder/VistA,OSEHRA/VistA