> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/archived-merged-pages/pentaho-data-services-archive/publish-a-pentaho-data-service.md).

# Publish a Pentaho Data Service

To publish your data service, save the transformation containing the data service to the Pentaho Repository.

Perform the following steps to validate that your data service has been published:

1. Since the Pentaho Repository is in the Pentaho Server ensure any external assets needed by the transformation can be accessed remotely, even if the transformation is run by a different user.
2. Open a browser, go to the Pentaho Server, and log in. If you have installed the Pentaho Server locally, the URL is usually `localhost:8080`.
3. Validate that your data service was published by listing the data services on the server, as shown in the following example:

   ```
   http://<*Pentaho Server Host:Port*>/pentaho/kettle/listServices

   ```

You are now ready to share the data service with others.


---

# 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.pentaho.com/pdia-data-integration/archived-merged-pages/pentaho-data-services-archive/publish-a-pentaho-data-service.md?ask=<question>&goal=<endgoal>
```

`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.