> For the complete documentation index, see [llms.txt](https://docs.cloudio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudio.io/setting-up-the-cloudio-platform/platform-installation/installing-the-servers/installing-and-configuring-the-jboss-wildfly-server/deploying-the-war-file.md).

# Deploying the WAR file

## Deploying the WAR file in standalone mode

1. Login to the console with the credentials of the management user.  

![](/files/-M-J2x-8nwUb5L4RytCV)

 2\. Click **Deployments**.

 3\. To add the ROOT.war file, click **Add**.

 4\. Upload the required WAR file.

 5\. In the **Verify Deployments** screen, verify the name and runtime name of your WAR file. 

**Note:** Do not select the Enable checkbox.

 6\. Access your application using [http://localhost:8080](http://localhost:8080/).

![Create deployment ](/files/-M-J3a872SBaBDLJkaxe)

{% hint style="info" %}
Change the RAM size in standalone.conf file in the bin folder in case of any memory issue.
{% endhint %}

## Deploying the CloudIO WAR file

1. Create a folder named cloudio using the following command: *\*\*$ mkdir /cloudio*
2. Deploy the WAR file. After installing the platform, the io.properties file is auto-generated in the cloudio folder.
3. Paste the log4j.properties file in cloudio folder.
4. Update the log4j file with valid log file path and paste it in tomcat's lib folder.
5. Restart **WildFly**

```
log4j.rootLogger=debug, R
log4j.logger.com.rapapp.platform.server=debug
log4j.logger.com.rapapp.platform.server.script=debug
log4j.logger.com.rapapp.platform.server.rest=debug
log4j.logger.com.ibatis=debug
log4j.logger.java.sql=debug
log4j.logger.org.quartz=debug
log4j.logger.org.apache=debug
log4j.logger.org=debug
log4j.logger.com.rapapp.platform.installer=debug
log4j.logger.io.cloudio=debug
# Console output
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{DATE} %5p %c{1}:%L - %m%n
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=<log_file_path>
# Ex: /u02/tomcat_home/workers12/worker1/logs/io.log
log4j.appender.R.MaxFileSize=10240KB
log4j.appender.R.MaxBackupIndex=10
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d{DATE} %5p %c{1}:%L - %m%n
```


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.cloudio.io/setting-up-the-cloudio-platform/platform-installation/installing-the-servers/installing-and-configuring-the-jboss-wildfly-server/deploying-the-war-file.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.