6.3.2 Reason for maintaining separate development and active environments
When you develop a service template in a separate environment from the active environment, each environment has its own set of service share properties.
- When the development and active environments are the same
-
A given service share property has one value within the JP1/AO system. When you change the value of a service share property in the service template editor, the change affects release service templates in addition to development service templates.
- When the development and active environments are different
-
The values of service share properties are managed separately in the active and development environments. When you change the value of a service share property in the service template editor, the change only applies to the service share property associated with the development service template. It does not affect the service share property associated with the release service template.
Therefore, we recommend that you keep the development and active environments of the service template separate. This allows you to prevent changes made during development from affecting the service share properties of the service template after release.