# Directory Structure

<table data-header-hidden><thead><tr><th width="201"></th><th></th></tr></thead><tbody><tr><td>Directory</td><td>Description</td></tr><tr><td>bin</td><td><p>Directory for the scripts to start/stop ISM</p><p>run.sh - start ISM processes.</p><p>stop.sh - stop ISM processes.</p><p>servicex64.bat - register ISM RuleCache as windows service.</p><p>ismadmin/ismadmin.bat - ISM Administration script</p></td></tr><tr><td>custom</td><td><p>Directory for custom classes, custom functions, and the default tasks</p><p>New tasks can be added automatically once the class files are located in this directory.</p><p>flow.jar - default tasks</p></td></tr><tr><td>data</td><td><p>Directory for cache and other ISM data.</p><p>schema.xml - ISM DB schema file.</p><p>license.txt - ISM license file</p><p>Flow-Report-Template.docx - Flow report template</p></td></tr><tr><td>jetty-9.4.7</td><td>Admin UI web server directory</td></tr><tr><td>lib</td><td>Directory for ISM libraries</td></tr><tr><td>Properties</td><td><p>Directory for configuration</p><p>ism.xml - ISM main configuration file</p><p>logback.xml - Configuration for logging</p><p>sftp.config.yml - sFTP server configuration file</p></td></tr><tr><td>logs</td><td><p>Directory for log files</p><p>admin.log - Admin script log file</p></td></tr><tr><td>tmp</td><td>Directory for storing temporary files for web service generation</td></tr><tr><td>wildfly-10.1.0.Final</td><td>Directory for ISM main runtime process</td></tr></tbody></table>

&#x20;

## Admin Script

·       Unix/linux - ismadmin

·       Windows - ismadmin.bat

&#x20;

·       Start admin processes.

$>ismadmin pmgr start

&#x20;

·       Stop admin processes.

$>ismadmin pmgr stopall

&#x20;

·       Update DB schema

$>ismadmin schema import schema\_file -m update/skip

·       Update - overwrite the existing table.

·       Skip - skip if the table exists.

&#x20;

## H2 directory

&#x20;

<table data-header-hidden><thead><tr><th width="169"></th><th></th></tr></thead><tbody><tr><td>Directory</td><td>Description</td></tr><tr><td>bin</td><td><p>Directory for the scripts to start/stop h2</p><p>This directory is used in unix/linux environments</p><p>h2-1.4.193.jar - h2 library</p><p>start.sh - start h2</p><p>stop.sh - stop h2</p></td></tr><tr><td>service</td><td><p>Directory for windows service management.</p><p>This directory contains scripts for windows service.</p></td></tr></tbody></table>

&#x20;

## jetty-9.4.7 directory

&#x20;

<table data-header-hidden><thead><tr><th width="171"></th><th></th></tr></thead><tbody><tr><td>Directory</td><td>Description</td></tr><tr><td>bin</td><td><p>Directory for the scripts to start/stop jetty</p><p>jetty.sh - start/stop jetty processes.</p><p>servicex64.bat - register jetty process as windows service.</p></td></tr><tr><td>etc</td><td><p>Directory for jetty properties</p><p>xnarum.xml - ISM properties</p></td></tr><tr><td>lib</td><td><p>Directory for jetty library.</p><p>ext directory contains JDBC libraries.</p><p>(*) Put the JDBC driver of the target database, if not exists</p></td></tr><tr><td>resources</td><td>Directory for logging properties</td></tr><tr><td>webapps</td><td>Directory for Admin UI application</td></tr><tr><td>work</td><td><p>Directory for deployed applications.</p><p>.war files of webapps directory are uncompressed under this directory while jetty is starting.</p></td></tr></tbody></table>

&#x20;

## Wildfly-10.1.0.Fnial directory

&#x20;

<table data-header-hidden><thead><tr><th width="168"></th><th></th></tr></thead><tbody><tr><td>Directory</td><td>Description</td></tr><tr><td>bin</td><td><p>Directory for the scripts to start/stop wildlfy</p><p>start.sh - start wildfly process.</p><p>service-jboss.bat - register wildfly process as windows service.</p><p>add-user.sh - create a new user. Admin user is generated with this script</p><p>jboss-cli.sh - jboss admin client batch/interactive script.</p></td></tr><tr><td>modules</td><td><p>Directory for wildfly module libraries</p><p>com/ism/jdbc directory contains jdbc libraries for ISM</p></td></tr><tr><td>Standalone</td><td>Directory for ISM runtime module and other applications.</td></tr></tbody></table>

&#x20;

### Standalone directory

&#x20;

<table data-header-hidden><thead><tr><th width="176"></th><th></th></tr></thead><tbody><tr><td>Directory</td><td>Description</td></tr><tr><td>configuration</td><td><p>Directory for configuration of standalone instance</p><p>standalone.xml - main configuration file</p><p>logback.xml - Configuration for logging</p></td></tr><tr><td>data</td><td>Directory for runtime data</td></tr><tr><td>deployments</td><td><p>Directory for the applications</p><p>xnarum.ear - ISM main application</p><p>api.war - ISM REST application</p></td></tr><tr><td>log</td><td>Logging directory</td></tr><tr><td>tmp</td><td><p>Directory for uncompressed applications</p><p>File under deployments are uncompressed under this directory.</p></td></tr></tbody></table>


---

# Agent Instructions: 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://ism-docs.xnarum.com/directory-structure.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.