This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Lifecycle Management of SOA Artifacts

Below described is how WSO2 products interact with each other and how to use WOS2 Governance Registry's lifecycle management feature to manage SOA artifacts in different environments.

Say, for example, you have 3 (three) ESB environments: "Dev","QA", and "Prod." In these environments, development work is done on "Dev" and for testing purposes, the artifacts under the "Dev" environment should be moved (copied) to the "QA" environment. Once the QA work has been done, the artifacts in the "QA" environment should be moved (copied) to the "Prod" environment. To automate this to some extent so that we have minimum user interaction in this process, we propose introducing WSO2 Governance Registry as a control mechanism for this process. With this solution, all the 3 (three) ESB environments will take to WSO2 Governance Registry, and each of these ESB environments will look there for SOA artifacts from the registry. We used a concept called "registry mounting" to produce such a scenario in which each of the 3 (three) ESB instances is mounted to 3 (three) different collections in the registry.

Governance Registry then uses its lifecycle management feature to move the SOA artifacts from one environment to another. You can use use a simple lifecycle with 3 (three) states (Development, QA, and Production) and in each state transition, contents are copied to the next environment.

For demonstration purposes, an environment where we have 3 (three) ESB instances was used, and each of these instances was mounted to Governance Registry.

Next, we created a Proxy Service in the "Dev" environment and used the deployment synchronizer feature of WSO2 products to transfer it to Governance Registry.

Using the deployment synchronizer, the ESB instance in the QA environment was able to find the new Proxy Service (which was copied to the "QA" location in Governance Registry) and deploy it in that instance.

You can find more details about this subject, including webinar slides and a complete recording on the topic, here.