SCOM Connector and 2019 Compatibility
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2020 05:45 AM
Hello,
I found this article stating how to configure the SCOM Connector for the New York release of ServiceNow and it does not list SCOM 2019 as supported.
This article lists SCOM 2019 as supported but is for the Orlando release of ServiceNow.
I have two questions...
- Is the SCOM Connector fully compatible with the New York release of ServiceNow?
- I've been advised that bi-directional support does not work with SCOM 2019 and the Orlando release of ServiceNow due to API changes in SCOM 2019. Is this accurate?
Thank you!
- Labels:
-
Event Management
-
Orchestration (ITOM)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2020 06:18 AM
Hi,
Yes that is correct - SCOM 2019 is not officially supported in NY, however, there were not platform changes in Orlando to support 2019. That said, it hasn't been tested or certified by ServiceNow (ie...support won't help) - but backporting the connector from Orlando to NY should work.
As for bi-directional functionality, that is correct (not functional) due to some API changes on the SCOM side. I believe they are working on overhauling the whole connector, timeline TBD.
Thanks,
-Ryan

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2020 12:40 PM
Ryan,
Has there been any update on this?
Specifically, I'm asking if SCOM 2019 is fully supported in Paris.
I see it listed under supported; however, it also lists "Note: When working with the SCOM 2019 version, bi-directional is not enabled". Does this mean bi-directional for SCOM 2019 is not supported?
If it is not supported, is there a supported workaround?
Thank you,
-Jennifer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2020 09:12 AM
Hi Jennifer,
Development has fixed this in Quebec, however its a simple change to the ScomJS mid server script include.
where we add in the condition for 2019 as a version... code would look like this starting on line 24 ::
var version = this.getParamValue("scom_version", "2007");
if (version == "2016" || version == "2019")
version = "2012";
Development has also confirmed that the DLL's from 2012/2016/2019 are all the same so as long as you have one of those sets of DLL's on the mid (as per documentation) then this will work.
Hope this helps!
-Ryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2021 05:30 AM
Ryan,
Is the fix mentioned above (Paris), updating the MID Server Script Include, to allow the bi-directional to work with SCOM 2019?
Thanks
Derek