Lifecycle Managment with Governance Publisher

WSO2 Governance Registry (WSO2 G-Reg) is a fully open source product for SOA governance. In G-Reg 5.0.0 release, we have introduced a revolutionary enterprise publisher and store for asset management. As I explained in my previous post, the Lifecycle of an asset is one of the critical requirements of enterprise asset management.

G-Reg Publisher Lifecycle Management: 

With WSO2 Governance Registry 5.3.0, we have introduced a new Lifecycle management feature for publisher application as well. After enabling lifecycle management in the publisher, you will be able to see new lifecycle management UI as below.



This lifecycle management can be enabled for one asset type or all the generic asset types(RXT based). If you are enabling this for all the assets, you have to change 'lifecycleMgtViewEnabled' value as true in the asset js file located in the GREG_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default directory. By default, this publisher based lifecycle management has been disabled.


If you want to enable publisher lifecycle management for a specific asset type, you have to add above attribute(lifecycleMgtViewEnabled:true) under lifecycle option in the asset js file.
       meta: {
            ui: {
                icon: 'fw fw-rest-service'
            },
            lifecycle: {
                commentRequired: false,
                defaultAction: '',
                deletableStates: ['*'],
                defaultLifecycleEnabled: false,
                publishedStates: ['Published'],
                lifecycleMgtViewEnabled:true
            }
        },

G-Reg Publisher Lifecycle Inputs: 

If you are using G-Reg 5.3.0, you can pass asset authors inputs from publisher UI to backend executor using "transitionInput'. Using lifecycle configurations, we can define this "transitionInput" for the each lifecycle operation available in a given state. 

Example Lifecycle 'transitionInput' configuration:

<data name="transitionInput">
        <inputs forEvent="Promote">
              <input name="URL" required="true" label="Endpoint URL" tooltip="APIM Endpoint URL"/>
              <input name="Username" required="true" label="Business Username" tooltip="Business owner name"/>
        </inputs>                            
 </data>

Post a Comment

Popular posts from this blog

Yield Price Sri Lanka - Android Application

Manage SOAPAction of the Out Message

How to clean Registry log (REG_LOG) table