> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/isd-spinnaker/opsmx-intelligent-software-delivery-isd-platform-spinnaker/release-notes/additional-resources/previous-releases/isd-3.12/opsmx-intelligent-software-delivery-platform/system-setup/applications/add-services/add-services-and-pipelines.md). # Add services and pipelines After creating the main application, you need to add the components to the application. These components are known as services/microservices. A microservice is always associated with an application. To know more about how to create an application, click [here](https://docs.opsmx.com/products/opsmx-intelligent-software-delivery-platform/system-setup/applications/add-applications). ## To add services, follow the steps given below: 1. After clicking the Save and Next button, the following screen will appear: ![](/files/V7khm2FDMXUEDsJbiwnd) 2\. Enter the Service Name in the text box and click **Save**. The following options screen will appear: ![](/files/NozbGCtOufG95DhtJH2x) In the above image, a pipeline test\_Service has been created along with the service*.* Click the test\_Service pipeline to make changes to the pipeline. After clicking, the following options will appear: ![](/files/9zhAunvIzH9b2N5hSHbs) **Type:** Select the type of gate using the drop-down, the options are Approval, Verification, Test Verification, and Policy. A gate is an access point that allows you to stop the pipeline to automatically go to the next stage. A gate helps you to manually intervene and verify or approve a stage of the pipeline before moving on to the next stage in the sequence. The following are the options: ### **Approval Type** If you select the gate type as "**Approval**", you can do the following: * Select the connector from the drop-down. The available connectors are: * JIRA * GIT * AUTOPILOT * SONARQUBE * JENKINS * AQUAWAVE * APPSCAN * Select the Account from the drop-down. * Select the template from the drop-down. ![](/files/263k5Mj7ztLcnAKSB6p4) ### **Verification Type** If you select the gate type as "**Verification"**, you can do the following: * Select or add a Log Template. To know more about log templates click [here](https://docs.opsmx.com/autopilot/analysis-setup/templates/log-template). * Select or add a Metric Template. To know more about metric templates click [here](https://docs.opsmx.com/autopilot/analysis-setup/templates/metric-template). ![](/files/3HXpjWiETHX3K5WyaBpX) ### **Test Verification Type** If you select the gate type as "**Type Verification**" you can only add a log template as shown below: ![](/files/n3uhMgceEantHlWgroLU) ### **Policy Type** If you select the type "**Policy**" you will be to select the Policy from the Policy Configuration field as shown below: ![](/files/JWxGluCEupfh0l7tjJ0U) * After selecting the type some common fields appears irrespective of the type selected. They are as follows: ![](/files/AJSPC3oxufgOYoZn84tA) * **Environment:** Any gate is associated with an environment. An environment can be a testing environment, a staging environment, or a production environment. Each environment is distinct and will have different credentials. Based on the environment the stages of a pipeline will vary. Click the drop-down and select Add Environment and then enter the name of the environment. * **Gate Name:** Enter the name of the gate in the text box. * Click **Save** to add the gate. You can add multiple gates to one service. Click the **Add New Gate** button as shown below: * When you are trying to add a second gate you can set the dependency of the new gate on a previous gate. To do so, select the previous gate from the **Depends On** drop-down. * After adding multiple gates to a service the Pipeline View will appear as shown below: ![](/files/7h5sKeYlO7lr7eqx29GF) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.opsmx.com/isd-spinnaker/opsmx-intelligent-software-delivery-isd-platform-spinnaker/release-notes/additional-resources/previous-releases/isd-3.12/opsmx-intelligent-software-delivery-platform/system-setup/applications/add-services/add-services-and-pipelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.