Highlighted
Honored Contributor.
Honored Contributor.
541 views

SHR 9.40 data collection fails from Sitescope

Hello



We have installed SHR 9.40 and try to integrate OMi 10 (RTSM) and Sitescope 11.30.
In SHR the integration with OMi (RTSM and events) works so far but the integration with Sitescope fails.
I have already checked the integration settings in sitescope and this looks okay.
In the troubleshooting guide there is not mentioned much about this issue.
And in the logs there are not many entries beside this below.

Do you have any idea? any experiences with this integration?

 

--
2015-08-27 10:35:00,012  INFO, com.hp.bto.bsmr.collection.collector.sis.da.SISDataAcquisitionApiCollector.collectData , Collecting data from VMI708AS.MAIN.ROOT.BKW-FMB.CH for the range Wed Aug 19 13:42:09 CEST 2015 to Wed Aug 19 14:42:09 CEST 2015
2015-08-27 10:35:00,057 ERROR, com.hp.bto.bsmr.collection.collector.sis.da.SISDataAcquisitionApiCollector.collectData , Failed to collect data for SIS server VMI708AS.MAIN.ROOT.BKW-FMB.CH for time interval Wed Aug 19 13:42:09 CEST 2015 to Wed Aug 19 14:42:09 CEST 2015
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.ClassCastException: com.sun.proxy.$Proxy106 cannot be cast to com.mercury.sitescope.platform.configmanager.interfaces.IMonitorConfig
 faultActor:
 faultNode:
 faultDetail:
        {http://xml.apache.org/axis/}hostname:VMI708AS

java.lang.ClassCastException: com.sun.proxy.$Proxy106 cannot be cast to com.mercury.sitescope.platform.configmanager.interfaces.IMonitorConfig
        at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
        at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
        at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2973)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:332)
        at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
        at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
        at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
        at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
        at org.apache.axis.client.Call.invoke(Call.java:2767)
        at org.apache.axis.client.Call.invoke(Call.java:2443)
        at org.apache.axis.client.Call.invoke(Call.java:2366)
        at org.apache.axis.client.Call.invoke(Call.java:1812)
        at com.mercury.sitescope.api.data.APIDataAcquisitionImplSoapBindingStub.getData(APIDataAcquisitionImplSoapBindingStub.java:234)
        at com.hp.bto.bsmr.collection.collector.sis.da.SISDataAcquisitionApiCollector.collectData(SISDataAcquisitionApiCollector.java:214)
        at com.hp.bto.bsmr.collection.collector.sis.da.SISDataAcquisitionApiCollector.collectData(SISDataAcquisitionApiCollector.java:180)
        at com.hp.bto.bsmr.collection.collector.sis.da.SISDataAcquisitionApiCollector.collect(SISDataAcquisitionApiCollector.java:165)
        at com.hp.bto.bsmr.collection.collector.SISCollector.collect(SISCollector.java:53)
        at com.hp.bto.bsmr.collection.collector.AbstractCollector.execute(AbstractCollector.java:208)
        at com.hp.bto.bsmr.collection.utils.scheduler.BSMRStatefulJob.execute(BSMRStatefulJob.java:17)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
2015-08-27 10:37:00,320  INFO, com.hp.bto.bsmr.collection.collector.sis.SISXMLDataProcessor.process , Initiating XML processing for Server VMI708AS.MAIN.ROOT.BKW-FMB.CH

0 Likes
1 Reply
Highlighted
Super Contributor.
Super Contributor.

Re: SHR 9.40 data collection fails from Sitescope

It looks like you have an SSO or proxy server that must be configured for your environment?

 

I've not seen this error before. However, I can see this in the error itself.

 

There are 9.40 hot-fixes available from support and the 9.41 patch that address issues with SiteScope collections.

 

Just be careful with the patch. I've seen it wreak havok in custom environments, where SHR is distributed to 2 or 3 servers for the application, Business Objects and the Sybase DB.

Best Regards,

~ Michael Stollaire
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.