AnsweredAssumed Answered

GMU Policy migration: How to deal with Global Resourses

Question asked by RemcoDekker on Feb 8, 2018
Latest reply on Dec 13, 2018 by Stephen_Hughes

We like to use external tools for our Policy Migration and storing in version control system (Git). The way to go is using the GMU and a basic sample is in docops: Version Control Example - CA API Gateway - 9.2 - CA Technologies Documentation 


What we are facing now is how to deal with dependency objects. The most clear example is for XML schema's from the Global Resources. The GMU is only facilitating on exporting folder, service or policy. The schema's must be migrated within a bundle including a dependency on a specific XML schema.


What I see here is:

1. Exporting a service build from a WSDL importing several schemas creates a bundle including all resources referred withing this WSDL (this is ok, we have all references)

2. Exporting a service with an Validate XML assertion referring a XML schema from Global resources does include this resources. However it does not include the imported schema's within this referred XML schema resource (this is not ok).

3. Theoretically the XML schemas could be reused and the current version on a system should be deployed in a controlled manner depending on the Git branch.


Above will result in a problem migrating these kind of dependency objects. Some times we are missing deeper nested referenced schema's (runtime issues!). This can only be found analyzing and validating the schema on missing dependencies. Also we would like to migrate the schema's separatly independent from the services. Migrating a service only needs to fail if the referred objects are missing on the target gateway. It seems we need a mix of GMU and Restman calls here?


Does any of you have tips and best practices how to deal with this specific issue and other dependencies in general?