Page History

Panel

borderColor	#bab6b9
title	Follow Our Example User Story

So far, David Stringer worked in the Designer's test environment. He created several forms, a BPMN model, mapping diagrams and configured the instance list of the service. Now he wants to continue developing the service while his business colleagues are supposed to test the first version. Therefore, David needs to deploy the service.

You are going to help him with that task.

Divinfo

Classicon	e2e-vers2false

Expand

title	Good to Know

Expand

title	: Why deploy a service?

Deploying a service is necessary to make it available to users. During development, a service is created and tested in a test environment. After successful testing, the service is deployed to the production system where it can be run by the appropriate user groups.

Especially in fusion teams, developers want to make a finished feature or an intermediate state of a service available to other team members for testing while they continue to work on the same service. This is easily possible in the Designer by using the test environment for developing, and deploying to the test server only when necessary. You only need to deploy your service if you want to allow other team members to test new features or if you want to run regeression tests against your test server.

For further details on testing and deploying, refer to to Working with the Test Environment and Deploying a Service in the Designer guide.

The Deployment Controls and the Deployment Properties are located on the service details page.

Click on the Service panel tab (service name) to open the details page. Scroll down to section deployment properties and click icon to enable edit mode.

Select the deployment target Container. The container name is determined automatically and corresponds to the name of the service.
Enter a version number for your service.