...
The Event Process Life Cycle Management refers to the deployment of an Event Process in various environments like Development, Testing, Staging, and Production. The user does not have to create different Event Processes for different environments; instead the user can simply specify the properties for service instances comprising Event Processes for various environments in a single Event Process.
...
This way service instances can have 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.
Figure 1: Environment Properties Tab reflecting FileReader configuration
| Note |
|---|
The Environment Properties appear after configuring the microservice. The configurable properties appear under Environment properties, which can be further configured to set environment specific configuration by accessing from this section. |
| Tip |
|---|
Refer the Define Named Configuration and utilize EPLCM section to work with a sample. |
Defining Named Configurations for Different Environments
...
In the figure below, the environment of the event process is changed from Development to Testing. A pop-up is shown asking the user if any missing configurations should be copied to the new environment. If the user chooses Yes, the configuration used in the event process, here test (Port) and ConnectionConfig (Resource) are copied to Testing environment.
Figure 2: Message dialog pop-up when changing the target environment of an event process
...
- Take a flow containing File Reader and Display components. Configure the File Reader providing different inputs in different environments as mentioned in the above section. Select the Target Environment in the Environment Properties tab of the Event Process. The environment specific properties for the service instances in the flow can be viewed from the Environment Properties table view present below the Target Environment section.
- Do the CRC and launch the flow. When the flow is launched in development environment, the contents from the dev.txt will be read and these messages can be viewed in the display. Similarly when launched in testing environment the contents from the test.txt will be read and these messages can be viewed in the display.
Figure 3: Display showing messages received from file reader in different environments
| Note |
|---|
These properties cannot be edited from the table provided. But they can be edited from the CPS of the specific service instance and form the deployment tab of the service instance in the properties view. |
| Tip |
|---|
Refer the Define Named Configuration and utilize EPLCM section to work with a sample. |