Creating correlated elements does not always require the use of the Service Configuration Manager, there is another option for those situations where you have fixed structures and well formed element names. The example is around a monitoring tool such as Netcool or T/EC. Anytime an alarm comes in for a server it shows up under a hosts bucket within this adapter.
On the service model side, anytime an element is created (by Service Configuration Manager or by hand, by script, etc) that is a server, you would like it to automatically correlate to the host.
For this example, we will create a demonstration adapter. The demo adapter has a branch of element that are more application centric than server centric, but for a correlation example, we can make that work. The elements are named like DNS and Email, they have a class of: prog. For our example, when someone creates an element of class: blog, we will try to automatically correlate the name of the blog class element to the corresponding prog class element under the demonstration adapter.
1) Create a demonstration adapter, all the default settings are typically adequate. After it is created, start the adapter.
2) Under Administration\Metamodel, right-click on Classes and select Create Class
For the name, I used: blog, the only other setting I did was to select a different icon instead of formula_org
3) After you create it and close that dialog, re-open the newly created class by right-clicking on it and selecting Properties, then, Relationship Templates
4) Press the Create a new class correlation rule
5) Enter Blog Test as the Name, do as you wish for Description
6) Press the "..." next to Relationship Target Root Element and drill into the Demonstration adapter, to Phila-Internet_Server-1 (should see children such as DNS, Mail, etc), Press OK on the Phila element.
The feature we are using is creating a source relationship that is FIXED, meaning, we know the location where the element will be created, we know the class of the element and the names of the elements will be the match.
7) The last thing we need to do is update the Relationship Template text, all we need to change is "someClass" to "prog"
8) Save the correlation rule by press OK.
To test that this works, if you create an element under Service Models, with a class of "blog" (Step 2) and name the element one of the following (DNS, Mail, News, Web), the element should automatically get correlated with the demonstration adapter element (Step 6 and 7).
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.