I am getting others folders while exporting specific folder. So, Is there any to exclude additional folder details ?
Am referring document: migrateOut command - CA API Gateway - 9.2 - CA Technologies Documentation
Example:There are three folders having both Service & Policies OTK MyCustomFolder1 MyCustomFolder2
Command : Export specific folder e.g. MyCustomFolder1$ ./GatewayMigrationUtility.sh migrateOut --argFile commonarguments.properties --folderName /MyCustomFolder1 -d MyCustomFolder1 --format directory
Expecting Result :/dependencies/rootFolder/MyCustomFolder1
Actual result: Other folder information are coming as part of specific folder migrateout/dependencies/rootFolder/MyCustomFolder1/rootFolder/MyCustomFolder2/rootFolder/OTK
Depending on what assertions are in the main service policy, the GMU process will export out dependency encapsulated assertion that have backing policies located in other folder structures. If you want to exclude them from the migrateIn then use the manageMapping command to ignore the elements you don't want moved.
What would be a efficient path to achieve this? So we like to set services, policies, etc. from the exported folder to newOrExisting, but all dependencies outside this folder to Existing. This could be theoretically anything a developer could create (e.g. generic building blocks).
If you are going to use just the existing dependencies from the destination system, then I would just skip exporting them by including the option --includeOnlyServicePolicy.
Stephen HughesBroadcom Support
Thank you Stephen for the quick reply,
folder_OTK is still coming even though there are no OTK assertions used inside MyCustomFolder1. Also included Fragment policy doesn't have any OTK assertions.
How it is possible? if so, Am I missing something.
The only way I have seen the OTK being pulled during a migrateOut is if an encapsulated assertion exists that is OTK. What in the OTK folder is being pulled?
Observed OTK even though for an empty folder e.g. Test
Please have a look and advice.
Step-1: Create empty folder e.g Test without any service/policy in Gateway via policy manager.
Step-2: Run GMU migrateout for specific folder e.g. Test
./GatewayMigrationUtility.sh migrateOut --argFile commonarguments.properties --folderName Test -d tmpOut --format directory
Step-3: Observed Other folders too
The output will pull the directory structure for root out to the file system but if you look at the XML files that are produced and will be created if imported only a folder_Test.xml file exists. All the other folders are blank.
I can still see OTK folders e.g. folder_Customizations, folder_Policy+Fragments. Am I missing something in migrateOut command(<GatewayMigrationUtility.sh migrateOut> --folderName /Test -d tmpOut --format directory).
Could you please advice