Spectrum Data Publisher - 10.02.03.PTF_10.2.304

Document ID : KB000073156
Last Modified Date : 24/04/2018
Show Technical Document Details
Issue:
Spectrum Data Publisher - missing tenant ID does not produce error.
The connector needs to validate the tenant ID and log an error; otherwise, it fails silently and it's very difficult to troubleshoot.
Environment:
CA Spectrum 10.2.3 and CA Digital Operational Intelligence
Cause:
Currently if you leave the tenant ID blank or if you enter it incorrectly, the SpectrumPublisher error handling does not log any ERROR message.
Resolution:
This issue has been addressed in the Spectrum_10.02.03.PTF_10.2.304 patch.
Please contact CA Spectrum Support for a copy of the Spectrum_10.02.03.PTF_10.2.304 patch.
Additional Information:
This fix includes following changes.
Logging:
Info Logging details will now display the number of Alarms data and inventory models are coming from Spectrum with newly created, updated and deleted info.
And number of Alarms data and inventory models being sent to Digital Operational Intelligent for Synchronization with new created, updated and deleted info.
 
Input validation in ConnectorConfig.xml: 
This will now validate the following fields for empty values. If user does not enter anyone these values, error will be displayed in logging and application will not start sync data from Spectrum to Digital Operational Intelligent.
And in case for the field DestinationDefaultTenant, it will not validate for empty check if multi-tenancy details are added in MultitenancyConfiguration configuration section.
 
<SpectrumConfiguration>
    <OneClickHostname> </OneClickHostname>
    <OneClickPort></OneClickPort>
    <OneClickProtocol></OneClickProtocol>
  </SpectrumConfiguration>
 
  <DestinationConfiguration>
    <DestinationHostname> </DestinationHostname>
    <DestinationPort></DestinationPort>
    <DestinationProtocol></DestinationProtocol>
    <DestinationDefaultTenant></DestinationDefaultTenant>
    <DestinationEntitiesPerPayload></DestinationEntitiesPerPayload>
  </DestinationConfiguration>