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>

















































Comments








Post a Comment























Popular posts from this blog









XSLT - Modify Date and DateTime value





















If you want to perform date and time related opertions with XSLT 'date' or 'dateTime' values, you can use 'xs:yearMonthDuration' or 'xs:dayTimeDuration' function to achieve this. You can add or reduce years, months, date, hours or even minutes through those functions.     xs:yearMonthDuration   For this function input value is year month duration and it should be passed in  ISO_8601 format    n- the [n] is replaced by the value for each of the date and time elements  P - The duration designator(for period).    nY- the number of years.   nM- the number of months.    ex: xs:yearMonthDuration('P1Y2M')  - 1 Year and 2 Months   ex:  xs:yearMonthDuration('-P1Y2M')  - Negative 1 Year and 2 Months   xs:dayTimeDuration   For this function input value is day time duration and it also needs to be passed in  ISO_8601 format   n- the [n] is replaced by the value for each of the date and time elements  P - The duration designator(for period).   nD- the








Read more










Integrate With Mutual Certificate Authentication based Service





















There are many ways to secure a Service/API using different Authentication mechanisms. Mutual Certificate authentication(AKA: Client Certificate Authentication) is one of the ways to secure Service or API. Recently I was trying to integrate with an API which is secured using Mutual Certificate Authentication. In this scenario, the backend service team gave me their certificate-based on PKCS#12. When integrating this backend system with WSO2 Platform, we have to use 'Multi-HTTPS transport'. With this 'Multi-HTTPS transport', it will grant great flexibility to define different SSL profiles with separate trust stores and key stores for different IPs or hosts. This custom SSL profile can be implemented for Client to Synapse Runtime(Client --> ESB) or Synapse Runtime to Backend(ESB --> Backend). If it is Client to ESB, then you have to define custom SSL Profiles in the transportReceiver section. In my use-case, it was for ESB to Backend. So I had to add custom SSL prof








Read more










Yield Price Sri Lanka - Android Application




















Image







 " Yield Price Sri Lanka " is an Android based application which helps users to check Market Price Information using their mobile devices. This application concept is based on person X( will update his name after approvals) and I did slight modifications on the application to support in a low cost infrastructure.   Using this " Yield Price Sri Lanka " application, you can check prices of various goods instantly, without going to the market. I am updating price information in Daily & Weekly basis according to the Colombo Manning Market prices.   Initial application was developed to support English language only. With current latest version we are supporting English, Tamil and Sinhalese languages.   This application will update price information in real time and when describing the application's back-end(server) architecture, it has developed to serve JSON based output with many concurrent requests without blocking any request. Within the mobile Application wh








Read more