...
When a Service instance is dragged and dropped in the Orchestration editor, the default environment is set to development. To configure a different environment, select the Target Environment in the Environment Properties tab of the Event Process comprising the service instance.
| Note |
|---|
Click somewhere in the Orchestration editor away from the service/route/port to find the Environment Properties tab in the Properties view. |
Hereafter, the environment dependent service properties will be written to the corresponding env.xml file and will be picked up from that file when Event Process is launched in that particular environment.
You can specify these properties for more than one environment by switching the Target Environment label in the properties of an event process. Configuring service instances for different environments is made easy, since easy as the configuration properties of the service instance in a new environment will be picked up from the previously configured environment when the CPS is opened.
This way service instances can have different a different set of properties while running on different environments. For example, a File Reader instance can be configured to read from a dev.txt file in a Development environment and from a test.txt file in a Testing environment.
...