As described earlier in the bootstrapping strategy, WBCV architects were intending to implement continuous harvesting as part of their release cycle and continuous integration solution. To achieve this, WBCV architects leveraged the Harvester Ant utility to invoke the Ant targets responsible for carrying out a harvesting job. The idea was that during preproduction and production deployments, new services and APIs would also be harvested ensuring that:
The catalog would not only contain services already published in production but also services in draft status. This would give curators visibility over assets that required additional metadata before being published.
Provide curators with the ability to enforce a lightweight policy during production deployment whereby only assets with complete metadata would be published. For the initial releases of the solution the intention was to do this manually. However, the intention was to automate this task later...