Highlighted
Outstanding Contributor.
Outstanding Contributor.
84 views

Service Manager SMIS integration with OO 2020.02

Hello!

I am using an integration manger to integrate with OO but I am getting this error in logs, has anyone encountered this error in OOB configuration?

05/05/2020 09:16:13 SMIS [INFO][SMOOController]: SMOO scheduler starts.05/05/2020 09:16:13 SMIS [ERROR][SMOOController]: Error calling method: doSoapRequest in class: com/hp/ov/sm/server/utility/SoapClient Exception (com.sun.xml.messaging.saaj.SOAPExceptionImpl: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed)
05/05/2020 09:16:13 SMIS [ERROR][SMOOController]: TypeError: response has no properties
05/05/2020 09:16:13 SMIS [ERROR][SMOOController]: Error calling method: doSoapRequest in class: com/hp/ov/sm/server/utility/SoapClient Exception (com.sun.xml.messaging.saaj.SOAPExceptionImpl: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed)
05/05/2020 09:16:13 SMIS [ERROR][SMOOController]: TypeError: response has no properties
05/05/2020 09:16:13 SMIS [ERROR][SMOOController]: TypeError: UUIDList has no properties

Labels (2)
0 Likes
2 Replies
Highlighted
Respected Contributor.
Respected Contributor.

Re: Service Manager SMIS integration with OO 2020.02

Within the integration you created, are you able to successfully click on the Verify Connection link within the integration manager and receive a "Verification succeeded" message? If not, then your SM is prevented from communication with the box your are attempting to connect with. Your current step would be to get the message to display "Verification succeeded". The system you are attempting to communicate with may be blocking a port, etc.

 

Joe

SM 9.64

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Service Manager SMIS integration with OO 2020.02

Hi @nolejj,

I can make a telnet connection from SM system to OO system, we have internal firewall in data centre and that was a problem when I started to configure integration because ports 8080, 8443, 8081 and 8445 were blocked between this two instances.

I have tracked the problem in ScriptLibrary: WSCentralServiceService
In function:invoke

Where system is doing doSOAPRequest something breaks I can't find a reason there, when I put it in try catch block it says that resultXML can't serialize since didn't doSOAPRequest didn't return anything.

Best regards,
Dino

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.