> 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/manage-the-pentaho-system/manage-the-pentaho-server/remove-sample-data-from-the-pentaho-server.md).

# Remove sample data from the Pentaho Server

By default, Pentaho provides a sample data source and a solution directory filled with example content. These samples are provided for evaluation and testing. Once you are ready to move from an evaluation or testing scenario to development or production, you can remove the sample content. Follow the instructions below to completely remove the Pentaho sample data and solutions:

1. Stop the Pentaho Server.
2. Delete the `samples.zip` file from the `/pentaho-server/pentaho-solutions/system/default-content` directory.

   If you performed a manual WAR build and deployment, then the file path is: `/pentaho-server/pentaho-solutions/system`.
3. Edit the `/pentaho/WEB-INF/web.xml` file inside of the deployed `pentaho.war`.

   As laid down by the Pentaho graphical installer and archive packages, this path should be `/pentaho-server/tomcat/webapps/pentaho/WEB-INF/web.xml`. If you performed a manual WAR build and deployment, then you must adjust the path to fit your configuration.
4. Remove the `hsqldb-databases` section from the `/pentaho/WEB-INF/web.xml` file:

   ```xml
   <!-- [BEGIN HSQLDB DATABASES] -->
       <context-param>
           <param-name>hsqldb-databases</param-name>
           <param-value>sampledata@../../data/hsqldb/sampledata</param-value>
       </context-param>
   <!-- [END HSQLDB DATABASES] -->
   ```
5. Remove the `hsqldb-starter` section from the `/pentaho/WEB-INF/web.xml` file:

   ```xml
   <!-- [BEGIN HSQLDB STARTER] --> 
   <listener> 
   <listener-class>org.pentaho.platform.web.http.context.HsqldbStartupListener</listener-class> 
   </listener> 
   <!-- [END HSQLDB STARTER] -->
   ```
6. Remove the `SystemStatusFilter`:

   **Note:** This is not part of the Pentaho samples; it provides error status messages that are only useful for development and testing purposes, and should be removed from a production system.

   ```xml
   <filter>
       <filter-name>SystemStatusFilter</filter-name>
       <filter-class>com.pentaho.ui.servlet.SystemStatusFilter</filter-class>
       <init-param>
           <param-name>initFailurePage</param-name>
           <param-value>InitFailure</param-value>
           <description>This page is displayed if the PentahoSystem fails to properly initialize.</description>
       </init-param>
   </filter>
   ```
7. Remove the filter mapping for the `SystemStatusFilter`:

   ```xml
   <filter-mapping>
       <filter-name>SystemStatusFilter</filter-name>
       <url-pattern>/*</url-pattern>
   </filter-mapping>
   ```
8. Save and close the `web.xml` file.
9. Delete the `/pentaho-server/data/` directory.

   This directory does not exist if you installed Pentaho with the installation wizard. It contains a sample database, control scripts for that database, the environment settings it needs to run, and SQL scripts to initialize a new repository.
10. Restart the Pentaho Server.
11. Log into the Pentaho User Console with the administrator user name and password and go to the Browse Files page.
    1. In the **Folders** pane, expand the **Public** folder and click to highlight the folder containing the Steel Wheels sample data. Click **Move to Trash** in the **Folder Actions** pane and confirm the deletion.
    2. Highlight the folder containing the Pentaho Operations Mart sample data. Click **Move to Trash** in the **Folder Actions** pane and confirm the deletion.

Your Pentaho Server instance is now cleaned of samples and development/testing pieces, and is streamlined for production.


---

# 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:

```
GET https://docs.pentaho.com/pdia-admin/9.3-administer/manage-the-pentaho-system/manage-the-pentaho-server/remove-sample-data-from-the-pentaho-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.