I have the following scenario:
I created some workflows including multiple shared components. Everything is currently created on my LOCAL space. Now I want to move parts of it to our SERVER. HOWEVER, the challenge is the following. (a) I want to move all shared components into a collective folder on the server (different path structure then in my LOCAL space). (b) I want to rename some of the shared components, in order to fit the global environment. But I do not want to manually go through hundreds of instances in my workflows and change the names manually.
Acc. (a): I came up with an XML-read-change-write-flow to search for all settings.xml files in the the respective workflows, that contain a link (‘sourceURI’), and change that link from what ever it is, to the new location on the server.
Does somebody have a smarter idea?
Acc. (b): I can use my XML-read-change-write flow to even put a new referenced name for the shared component, by simply changing the name within the link-string. That is, the respective instance of the shared component than references to the renamed shared component. HOWEVER, opening the the workflow, that uses this shared component, I see that the ‘Component Name’ still is the original, but not the one, that I put into the link within the settings.xml. NOTE: the update of the shared component works, with the new link, but the name of the instance just shows a different name within the workflow. I guess in order for KNIME to know what to show on top of a component, in terms of ‘Component Name’, it must be stored somewhere.
Where is actually the ‘Component Name’ saved?
How can I change the ‘Component Name’, at best programmatically, not manually via unlink… ?
Thanks for your comments.