Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How to migrate customize life cycle to other environment

We want to customize life cycle for our special case. But we have multiple environments, like dev env and test env.
If we develop a life cycle on dev env, how to migrate it to test env also? Must directly insert to RAM DB something?
Thanks.

0 votes



One answer

Permanent link
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
<server>/<context>/internal/masterLifecycles
for Atom feed of masters,  and for a specific configuration of a
<server>/<context>/internal/masterLifecycles/mc_asset_com.ibm.ram.type.businesscase
For a community lifecycle:
<server>/<context>/internal/communities/<communityID>/lifecycles

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,019

Question asked: Nov 08 '12, 4:12 a.m.

Question was seen: 5,414 times

Last updated: Nov 08 '12, 9:18 a.m.

Confirmation Cancel Confirm