Concerning service development, we recommend to deploy service repositories in a development, test, and productive environment.This scenario is depicted in the figure below.

Figure: Configuration Management

  1. Typically, developers start their services locally or deploy them to a development host for testing.
  2. If the unit tests succeed, the service repository/package is exported from the development environment and then imported into the test environment. After adapting the test settings such as host names, user names, passwords, and so forth, further tests may follow (integration-, regression-, and user acceptance tests).
  3. The last step in this scenario is to import the tested repository/package and settings into the productive environment. Again, settings might be adapted.
  4. After the productive system is running, the repository/package and settings might be exported and stored in a version control tool. However, another option is just to backup the productive configuration.

For details regarding service deployment, refer to Deployment of E2E Composite Services.

  • No labels