Pinned topic Clone configuration
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Can someone explain me use of clone configuration action in WMC console...? What is the purpose?
Updated on 2011-02-22T23:22:55Z at 2011-02-22T23:22:55Z by SystemAdmin
Clone configuration2011-02-17T15:15:28ZThis is the accepted answer. This is the accepted answer.Cast Iron projects may use configuration properties (name/value pairs) that are external to the project and whose values are modifiable in the runtime environment using the WMC. If your project does not use configuration properties, there is no need to clone a configuration.
One of the most common uses of configuration properties is to support the definition of an endpoint. For example, a database enpoint may use configuration properties to contain values for the Database Name, Server, Port, User Name, and Password. While the project is under developement, the a development database instance is used. When the project is initially published, the default values defined in Studio for the propertries will be in the Default configuration.
In the runtime, if you would like to use the same project version with another database instance, clone the configuration giving it a name. Modify the configuration property values of the clone to point to the second database instance.
This lets you use the same project version in multiple configurations (e.g., UAT and Training).
Start only 1 project2011-02-19T12:28:25ZThis is the accepted answer. This is the accepted answer.Just a note to that, while you can clone a project, you can only start one project at a time, between the original project and the cloned project. That's because both projects will have the same orchestration name.
Cloned Project Configurations2011-02-21T13:07:50ZThis is the accepted answer. This is the accepted answer.More than one configuration of a project can be started at a time. Usually, the problem with starting multiple configurations is an HTTP listener conflict. Whenever, you try to deploy orchestrations that begin with an HTTP Receive Request activity that references the same URL, the first will successfully start and subsequent ones will fail (the system log will indicte that the URI is in use).
If you need multiple concurrent configurations, make sure that the same URL is not referenced. You can make all or part of the listening URL a configuration property.
Project configurations2011-02-22T23:22:55ZThis is the accepted answer. This is the accepted answer.What is the behavior if more than 1 configurations of a project is started and the starter activity is "Schedule Job"?
Say...Project A version 10 is deployed.
I make some change to Project A, create version 11 and deploy it in the same environment against same end points.