I've created 2 Component templates in 2 different directories w/ the same name.
I've tried to update the second one w/ the information that I've modified in the other and I've got a successful update.
I really don't get it.
1 of 1 people found this helpful
when you say 'mapping.xml' on the file server - do you mean the mapping.xml file that is created when you do an export, into the location you specify in the export command ?
the mapping.xml is used during the import if you need to change something during import - target group, associated blpackages, etc. you don't need to use it.
i'm also not sure what you mean by 'xml linking both objects.' if you export and object, and then go change the object in BSA, the exported xml is not updated - there's no link there. it's totally independent at that point. so when you use that xml to import you are importing the version of the object that you exported. and then you can delete the files you used to do the import.
1- Yes, I mean that mapping.xml
2- Yes, I already know that, also, it is necessary to change this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapping SYSTEM "file://bladelogic.com/dtds/Import-Mapping.dtd">
<!--This is the path to the group into which the object will be imported-->
Because by default, it is pointing to the exporting group, I don't know why.
3.-Yes, I understand that, but, if I have 2 environments and I want to update some object within the importing environment, which is the link between exported and imported objects? I mean, I suppose there must be some link between them in order to establish the connection and perform the updating process...
I really appreciate your help
1 of 1 people found this helpful
i'm not sure what you mean by 'link between the exported and imported objects'
you start the blcli and connect to the exporting env and run the export.
you start the blcli and connect to the importing env and run the import
between those two steps you might be copying the exported files around, or maybe you can connect to both env from the same place. there is no communication from the exporting env to the importing env.
Yes Bill, I understand that, I'm focused on the update thing, I found out that BSA is able to update an object, even if they are created as new, with different name, placed in different folders (I mean that is not necessary to do the importExport process before in order to get the update blcli working...), so I guess that when it comes to do an updateByName process, they dont have to be related in any way and I thought they had to...
So now I understand that:
- There's no link left between exported and imported files after importExport process.
- In order to update such an object, you only need another object of the same kind with the same name in a different directory
- There's no relation between importExport and Update blicli's
Am I right?
It was just that I missunderstood some points during the proccess because the documentation about the import export process isnt really extended
Thank you for your help
what 'update' blclis are you referring to ?
I'm using updateByName Template "MyTemplate" "MyTemplate" $Path_To_Exporting_Env $PAth_To_Importing_Env
I think Template is the only space that has this 'update' type of command. the other object types don't have this and there is no way to 'update' an existing depot software, deploy job, etc.