The Lifecycle Management(LCM) plays a major role in SOA Governance. WSO2 Governance Registry Lifecycle Management supports access control at multiple levels in lifecycle state.
1. Permissions
1.1 Check items with permissions configuration
<permissions>
<permission roles=""/>
</permissions>
1.2 State Transitions by transitionPermission configuration
<data name="transitionPermission">
<permission forEvent="" roles=""/>
</data>
2. Validations
2.1 Check items by he validations configuration
<validations>
<validation forEvent="" class="">
<parameter name="" value=""/>
</validation>
</validations>
2.2 State Transitions by transitionValidations
<data name="transitionValidation">
<validation forEvent="" class="">
<parameter name="" value=""/>
</validation>
</data>
3. Resource Permissions at each environment
<permission roles=""/>
4. State transition approvals with voting procedure
<data name="transitionApproval">
<approval forEvent="Promote" roles="" votes="2"/>
</data>
Use case
Just think how book is produce from writing to market. Book will have it’s own Book Life Cycle [2] and it main contain Acquisitions, Editorial, Production and Marketing
1. Permissions
1.1 Check items with permissions configuration
<permissions>
<permission roles=""/>
</permissions>
1.2 State Transitions by transitionPermission configuration
<data name="transitionPermission">
<permission forEvent="" roles=""/>
</data>
2. Validations
2.1 Check items by he validations configuration
<validations>
<validation forEvent="" class="">
<parameter name="" value=""/>
</validation>
</validations>
2.2 State Transitions by transitionValidations
<data name="transitionValidation">
<validation forEvent="" class="">
<parameter name="" value=""/>
</validation>
</data>
3. Resource Permissions at each environment
<permission roles=""/>
4. State transition approvals with voting procedure
<data name="transitionApproval">
<approval forEvent="Promote" roles="" votes="2"/>
</data>
Use case
Just think how book is produce from writing to market. Book will have it’s own Book Life Cycle [2] and it main contain Acquisitions, Editorial, Production and Marketing
- In Acquisitions state it will have some element or items such as Proposal, Submit manuscript, Peer Review, Approved by editorial board and Launched in to editorial department
- Editorial state will contains Copyediting, Author review, typesetting and design, Page proofs ready, Proofreading and Final Author review
- Book is printing and Shipped are event can be found in Production
- Marketing state consist with Moving book in to warehouse, picking publication date, book announced, moving the book to the book stores and promotion continues
It is not only the life cycle, Book contains it’s own attribute (schema) [1]. You can define new asset type to WSO2 GREG. Asset can have custom lifecycle. Let added Book asset type to WSO2 GREG with RXT.
Here is Book RXT file [3]
Loading RXT https://gist.github.com/Madhuka/4f0a28341bfe25f362f17f9f09cfb7f6 ....
Here is Book Life Cycle file [4]
Loading LifeCycle https://gist.github.com/Madhuka/46cb1cdf225592c2b6c268d09e9001e9 ....
Add Both file to WSO2 Greg as it is show in below screen shoot
Adding Life Cycle to Greg 5.4.0
Adding custom Artifact type
Done!!
Now login to to Publisher and then you can add Books as below
Once you added all the data, You can see your book as below
You can start life Cycle management by clicking life Cycle button
You can see Book life cycle move as below
Once it publish you can see it in you book store as below
It is good to go for your own artifacts and life cycles.
View comments