Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
539 views

UCMDB ServcieNow integrations

Jump to solution

Hi,  I'm tring to make an integration between Ucmdb (version 10..11Cup9 CP17) to (at this moment the development instance of serviceNow (version Kingston) .

When defining the OOB push integration as described in the documentation, It always gives a successfull result
both when filling correct figures and also when filling in fake connection figures) . It even states that it created a CI in ServiceNow (result is based on the integration TQL) but the CI is not available in ServiceNow?

Any Ideas what might cause this? 

When checkking the logfile I get this 

<2018-03-23 15:13:01,194> [DEBUG] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Starting Push to Service-Now...
<2018-03-23 15:13:01,266> [INFO ] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Create SN Stub for table:cmdb_ci_win_server
<2018-03-23 15:13:02,263> [DEBUG] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Stub:15
<2018-03-23 15:13:02,350> [DEBUG] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Left retry count:3
<2018-03-23 15:13:02,350> [DEBUG] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Do operation...:insert
<2018-03-23 15:13:05,048> [DEBUG] [AdHoc:AD_HOC_TASK_PATTERN_ID-6-1521814379450] - Error while executing:insert
Traceback (most recent call last):
File "pushToServiceNow", line 264, in retryHandler
AxisFault: org.apache.axis2.AxisFault: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: UCMDB ServcieNow integrations

Jump to solution

The end conclusion on this case is that Global support has confirmed that ucmdb version 10.11 is not compatible with the Jakarta version of ServiceNow.

Atleast 10.22 cp 22 needs to be used. 

View solution in original post

0 Likes
3 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB ServcieNow integrations

Jump to solution

Hello there,

 

from the error I would say that SNOW is running with SSL and you need to ad those certificates to the UCMDB truststore.

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: UCMDB ServcieNow integrations

Jump to solution

validating at Servicenow i understand that ssl is using a standard key so validation should not be standard and not needed to configure.

as we are using ucmdb v 10.11 I'm wondering if the oob integration for servicenow is actually compatibel with the current version on Servicenow.  is there any one who has experiance with the standard servicenow integration  (not the enhanced one that is introduced in ucmdb 10.22) with servcicenow version Jakarta or Kingston?

or knows that the mentioned integration is not compatible with those newer versions? If so what did you do to integrate ucmdb 10.11 with servicenow Jakarta/kingston

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: UCMDB ServcieNow integrations

Jump to solution

The end conclusion on this case is that Global support has confirmed that ucmdb version 10.11 is not compatible with the Jakarta version of ServiceNow.

Atleast 10.22 cp 22 needs to be used. 

View solution in original post

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.