How to migrate customize life cycle to other environment
One answer
No simple way to do it today: import and export asset lifecycles and policies (34506)
The following is "at your own risk" kind of thing ... make sure to put your sit belt and helmet on ;=)
Backup first!!!!
For the workflow (if you made any changes), Open (from the Eclipse client) the lifecycle project, and from the Process Configuration Source tab, copy the <configuration-data> over... but, the fragile thing here, are the id= kind of thing. If you copy it all, you should be fine, if you pick and choose, make sure that these are consistent.
For the lifecycle itself (in RAM), you can GET/PUT on these URLs ... but you will have to send Accept: application/rdf+xml
Also make same policy governors are loaded
The following is "at your own risk" kind of thing ... make sure to put your sit belt and helmet on ;=)
Backup first!!!!
For the workflow (if you made any changes), Open (from the Eclipse client) the lifecycle project, and from the Process Configuration Source tab, copy the <configuration-data> over... but, the fragile thing here, are the id= kind of thing. If you copy it all, you should be fine, if you pick and choose, make sure that these are consistent.
For the lifecycle itself (in RAM), you can GET/PUT on these URLs ... but you will have to send Accept: application/rdf+xml
Also make same policy governors are loaded
<server>/<context>/internal/masterLifecyclesfor Atom feed of masters, and for a specific configuration of a
<server>/<context>/internal/masterLifecycles/mc_asset_com.ibm.ram.type.businesscaseFor a community lifecycle:
<server>/<context>/internal/communities/<communityID>/lifecycles