# List of Scripts

### **List of Scripts**

There are six scripts or shell command in order to **manage** the **Web Application:**

**register-application.sh**

To register the application to run, this shell command has to be **executed only once**. This script read data in \[***ports-all.ini***] file and register all ports in this file. For example if \[***ports-all.ini***] has the following content: 8787,8888,8989

This will register the Web Application to be used in ports: *8787,8888,8989*. Comma is used to separate ports. The **ini**'s files are in the same directory as the scripts.

**unregister-application.sh**

To unregister application, this shell command has to be **executed only once**.

**start-all.sh**

This command will start a **multi-thread** Web Application Server where each port will be attended by a different (**Gem**) process. Following the previous example three **Gem processes** will be created to attend each port.

**stop-all.sh**

This command will stop all **Gem processes** serving on all ports. The **Web Application** will **no** longer answer http requests.

**start-zn.sh**

This command is similar to \[*start-all.sh*] but instead of starting a **Gem Process** for each port it only start a subset of all ports. The subset is defined in \[**zn-ports.ini**] file.

**stop-zn.sh**

This command is similar to \[*stop-all.sh*] but instead of stop all **Gem Process** in each port it only stop a subset of all ports. The subset is defined in \[**zn-ports.ini**] file.


---

# 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://bpmflow.gitbook.io/project/orbeon-integration/orbeon-persistence-layer-for-gemstone-s/manage-persistence-layer/list-of-scripts.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.