A service is a single instance of the Extension Designer that can host multiple flows or artifacts that perform specialized tasks. You can create several services that run across multiple processes, rather than across multiple endpoints. The distribution allows you to scale horizontally to avoid performance issues, as well as group related flows into a single service. For example, Change Based Testing and Risky Code Changes would likely be grouped in a Change Management service. See Important Concepts and Terminology for additional information.
In this section:
Services must belong to a category. The purpose of categories is to keep services organized; they have no effect on the functionality of the service (see Extension Designer Best Practices).
Extension Designer ships with three types of services out of the box:
You can also create your own categories:
Click Delete Category to remove a category from Extension Designer.
You cannot delete a category if it contains services. In addition, the categories shipped with Extension Designer (Process Intelligence Engine, DTP Workflows, and Policy Center Practices) cannot be deleted.
You can rename a category by clicking its name in the editor and making your changes.
To delete a service, click the Delete button and confirm that you want to delete the service when prompted.
When the service has been created, you can begin creating flows. See Working with Flow.
Use the debugging mechanism to verify that data is flowing properly and that nodes are functioning as expected.
You can access log files for Extension Designer and the database server in the <DTP_ENTERPRISE_PACK_HOME>/logs directory.
After you've designed your service, click Deploy and choose a deployment option to deploy it to Extension Designer. If you edit a node or make other changes to the flow, the Deploy button will be active so that you can push your changes. Changed nodes will also be flagged (see Working with Nodes).
You can implement multiple instances of the same flow when in your services, but if your flows contain endpoint nodes, then the UUID must be different. Otherwise, only the first instance of the flow will be read. Click the refresh icon to generate a new UUID.
Endpoint nodes expose a service endpoint that encapsulates all the functionality necessary to create a full-stack web component. See Working with Nodes for additional information about nodes.
You can only work with a service in one browser window or tab at a time. Interacting with the same instance of service in multiple windows or tabs may return an error if you attempt to deploy the service from one instance after making changes in another.