Is it possible to maintain orchestration's version history in WMC..? Lets say today I have an orchestration (v1.0) developed and published to production appliance. Next month i release the updated version of the same orchestration (v1.1) developed and published to the prod appliance again. Can I have both these versions of orchestrations maintained in WMC? or do i have to rely on external repositories? Please share your input. Thanks in advance.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-03-01T19:43:50Z by SystemAdmin
Pinned topic Maintaining Orchestration version history
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-01T19:43:50Z at 2013-03-01T19:43:50Z by SystemAdmin
SystemAdmin 110000D4XK224 PostsACCEPTED ANSWER
Re: Maintaining Orchestration version history2013-03-01T19:43:50Z in response to SystemAdminIt is possible to maintain both versions on the same appliance. You'll want to export the project from Studio (rather than publish directly from Studio) and upload the resulting .par file to the appliance. When the WMC prompts you to upload the .par file, specify a different version number than what's already on the appliance.
Of course, it doesn't hurt to have a source control system to keep any work that's going on between versions backed up and centralized.