How to ignore Dependencies folder when doing GMU migrateOut and MigrateIN.
I tried using "-includeOnlyServicePolicy" but I am getting an error.
Just to clarify, --includeOnlyServicePolicy works with migrateOut, but if you use that you will get ONLY the service policy, no dependencies, so subsequent use of manageMappings will not have anything to work with. If you use --includeOnlyDependencies, you will get ONLY the dependencies and no service, so migrateIn will not look like it does anything from a policy view, but it will actually migrate environment type things like private keys, etc. If you use neither option you get both service policy export and dependencies by default. Just went through that.
Do you have the full migrateOut command you're using? I don't have extensive experience with GMU but I have recently been engaged in similar issues. I doubt it's the "-includeOnlyServicePolicy" switch that's causing your problem. It's likely some other aspect of your migrateOut. I do not believe that switch can be used for anything but migrateOut. I've found the command output to be pretty good about telling you what the problem is. Specifically what error are you getting?
I wanted to ignore few dependencies which came out from migrateOut. i modified the mapping.xml file and that solved my issue.
It seems "-includeOnlyServicePolicy" doesn't work with migrateOut, I was referring to CA Documentation migrateOut command - CA API Gateway - 9.2 - CA Technologies Documentation.
Thanks for your help.
Retrieving data ...