> 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-admin/9.3-administer/pentaho-developer-center-overview-cp/platform-javascript-apis/osgi-artifacts-deployment-visapi-reference.md).

# OSGi artifacts deployment

Pentaho is built on top of an [OSGi](https://www.osgi.org/) container ([Apache Karaf](https://karaf.apache.org/)). You can use the OSGi container as a simple modular approach at both development time and runtime, reducing complexity and facilitating deployment. Pentaho supports deployment of the OSGi container via dropping files into the deploy folder. Hot deployment is supported. Artifacts are automatically installed and activated. They remain activated, even after restarts of the product. Replacing an artifact in the deploy folder will reinstall it. Deleting it, will uninstall it.

The deployer handles ZIP and TGZ files, such as those files generated by the `npm pack` command. You can include web resources described by a `package.json` file within the ZIP and TGZ files. You can contain multiple web packages in a single archive, to provision visualization’s dependencies for example.

Depending on the Pentaho product, the Karaf deploy folder is located in the following directory:

* **PDI**

  `system/karaf/deploy`
* **Pentaho Server**

  `pentaho-solutions/system/karaf/deploy`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-admin/9.3-administer/pentaho-developer-center-overview-cp/platform-javascript-apis/osgi-artifacts-deployment-visapi-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.