# Install ONEWEB Process Server

This section describes how to **deploy the ONEWEB Process Server (Process Runtime / BPM Runtime)** on WildFly using the **WildFly Management Console**.

The Process Server is responsible for executing workflows, business processes, and runtime process logic created using ONEWEB Process Designer.\
Before deployment, specific **database configuration values** must be prepared to ensure correct runtime behavior.

***

#### Prerequisite: Database Configuration for Process Server

Before deploying the Process Server, configure the following values in the database table:

```
bpm.wf_t0_property
```

These properties define logging configuration and class loader behavior for the process runtime.

| Property Name             | Property Value                      | Description                                    |
| ------------------------- | ----------------------------------- | ---------------------------------------------- |
| `bpm.ge.log4j.properties` | `/<oneweb>/common/log4j.properties` | Log4j configuration path for Process Server    |
| `bpm.ge.classLoader.urls` | `/<oneweb>/pd/Files/`               | Upload directory for process‑related artifacts |

> Ensure that the referenced directories exist and that the application server has appropriate read/write permissions.

***

#### Step 1: Access WildFly Management Console

Log in to the **WildFly Management Console** using a web browser.

By default, the console is available at:

```
http://<Application Server IP>:9990
```

Use an administrator account with deployment privileges.

***

#### Step 2: Navigate to the Deployment Panel

1. From the Management Console dashboard, navigate to the **Deployment** panel
2. Click **Add** to deploy a new application archive

The Deployment panel is highlighted in the example below:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FxMzeEwz8bdsaIX45Ud3H%2F0?alt=media" alt=""><figcaption></figcaption></figure>

***

#### Step 3: Upload the Process Server WAR File

1. Select **Upload new deployment**
2. Click **Next**
3. Choose the ONEWEB Process Server WAR file

The package name follows this format:

```
ONEWEB.PR.x.x.x.x.YYMMDD24HHMM.wildfly.war
```

Example upload screen:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fh17hCGYq3KH4RikmGn5g%2F1?alt=media" alt=""><figcaption></figcaption></figure>

After selecting the file, click **Next** to continue.

***

#### Step 4: Enable the Deployment

1. Select **Enable** to activate the Process Server immediately after deployment
2. Click **Finish** to complete the deployment process

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F7h4prIUEJo4d4VOm0YkC%2F2?alt=media" alt=""><figcaption></figcaption></figure>

Wait until the confirmation message indicates that the application package has been deployed successfully.

***

#### Step 5: Verify Process Server Deployment

After deployment is complete, verify that the Process Server runtime is accessible.

Open a web browser and navigate to:

```
http://<Application Server IP>:<Port>/BPMREST
```

A successful response confirms that the ONEWEB Process Server has been deployed and initialized correctly.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FqmkI2am82KdGyC0pix1r%2F3?alt=media" alt=""><figcaption></figcaption></figure>

***

#### Deployment Result

After completing the above steps:

* ONEWEB Process Server is deployed on WildFly
* Workflow and business process execution services are active
* Integration with Process Designer and BPM components is enabled
* The platform is ready to execute process‑driven applications


---

# 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://docs.onewebstack.com/getting-started/platform-configuration/platform-components-overview-and-management/install-oneweb-process-components/install-oneweb-process-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.