Is there an easy way to copy a discovery pattern?

[edgood1]

I want to use our existing "Linux - Server" pattern to server as the identity pattern for another Class of servers which run a Linux-like operating system. The pattern is essentially the same but with a few more shared libraries included which are specific to the linux-like devices.

I can't use the existing Linux server pattern as the identity pattern/probe because it seems to be bound to the cmdb_ci_linux_server table. My thought is that if I can create a copy that is bound to my custom class I can effectively do the same type of discovery on the linux-like devices and have them properly classify in their own class.

I tried copying the pattern text to a new one with no luck. Is there an easy solution to this in the Kingston release?

[richardbrounste]

In London, ServiceNow introduced a new feature that allows you to package a Discovery pattern and export it.

For Kingston and earlier, it is necessary to identify all the resources (pattern or probes and sensors) including every entry for an SSH script or PowerShell script.  All of these entries will need to be written to an update set and then can be exported.

You don't want to just copy the Pattern Text. That can be problematic.  The entry in the sa_pattern table is what needs to be saved to the update set.

[johnnyjava]

Yeah, copying the NDL (pattern text) into another one doesn't do it.

Try going to sa_pattern.list in the navigator and then opening the records there. You can change the name and then use the right-click option to Insert and Stay that new record. Be sure to deactivate the old one, if you no longer wish to run it.

Once you have your new record, you can change the target class on it.

[johnnyjava]

Yeah, copying the NDL (pattern text) into another one doesn't do it.

Try going to sa_pattern.list in the navigator and then opening the records there. You can change the name and then use the right-click option to Insert and Stay that new record. Be sure to deactivate the old one, if you no longer wish to run it.

Once you have your new record, you can then change the target class on it.

Update: You also need to update the sys_id in the metadata header tho or else pattern section navigation gets broken. We wrote a UI Action to handle it and override the default insert & stay action.

[Henrik Jutterst]

Just what I was looking for. Thanks for contributing with the answer.