Hi,
Is there a way to make an identical copy of an element with only another name. This element is using connection strings which makes it probaly tricky to do this.
I think you might want to generate an active backup element.
The DELT is probably the best approach but just to give you another option.
What you also could do is duplicate the element and use Copy Element Data | DataMiner Docs to get all the data from the original element. And past it to the second one (also explained in the article). Then it's just a matter of setting up the element connections manually again and you would be good to go.
Note that this approach is a hard set. This means that the connector might not behave completely as you would expect it. eg you have login credentials, a login button and a login status, when you apply the data from one element to another it will copy over the credentials and the login status but the button would not be pressed. This means that the status might state "Connected" while the command hasn't actually been send. So you might want to restart the element afterwards to update those settings.
Either way it's a bit risky so best to test this out in a demo environment.
Hi Gerwin,
If you are referring to SNMP Community strings then when duplicating an element those should be "pre-filled" and then creating the element should apply them.
However, if with connection strings you are also referring to credentials for HTTP or SSH or other communications that are stored in parameters then I do not believe there is a generic way of achieving what you are after.
The only thing I can think of is to use the Copy Element Data Tool to copy all parameters from one element to another but if the credentials are with the type password, those may not work.
Given that is table data it should work nicely with the Copy Element Data Tool.
What I am unsure of is if a duplicate element will also bring along the element connection mapping and that could be desired or not.
Hi Gerwin,
Another option is use a DELT export. You could create a DELT export from the element (including element data) and import it in another DMA in the cluster. Once the DELT export is created, you will need to rename the original element.
The constraint here is that you need a DMS with at least 2 DMAs. You will not be able to import in the same DMA.
Hope it helps.
That seems like an option, however we don’t want to rename the orginal element, can we tweak something in the delt export to give the import an new name?
You can rename the original elements afterwards. The workflow could be as follows:
– Export the element to a DELT package
– Rename the original element
– Import the DELT package in another DMA in the cluster. This will create the duplicate element
– Rename the duplicate element
– Rename the original element to its original name
Won’t the exported element have the same DataMinerId/ElementId as the original one?
Even if you rename it and place it on a different agent of the cluster it could present some issues.
Hi,
Indeed, I performed a small test and the DMA does not allow me to import the DELT package in the same DMS (only replace it). For a moment I thought that the imported element will be created with a new element ID. This procedure will only work if you import the element to a different cluster.
No it’s a table filled with information pulled from other elements through element connection strings.