Topic
1 reply Latest Post - ‏2013-03-01T19:43:50Z by SystemAdmin
SystemAdmin
SystemAdmin
224 Posts
ACCEPTED ANSWER

Pinned topic Maintaining Orchestration version history

‏2013-02-27T16:52:10Z |
Hi,

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.
Updated on 2013-03-01T19:43:50Z at 2013-03-01T19:43:50Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    224 Posts
    ACCEPTED ANSWER

    Re: Maintaining Orchestration version history

    ‏2013-03-01T19:43:50Z  in response to SystemAdmin
    It 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.