# Upload File

During **Microflow** or **Process Flow** development, integration logic often depends on **external artifacts**, such as:

* **JAR files** for Java Tasks
* **WSDL / XSD files** for Web Service Tasks

Instead of uploading these files individually for each node, ONEWEB provides an **Upload File facility at the application level**.\
Once uploaded, files can be **reused and referenced across multiple nodes and flows**, simplifying management and maintenance.

This centralized approach improves **reuse, consistency, and version control** for integration artifacts.

***

### Purpose of Upload File Facility

The Upload File feature is designed to:

* Centralize management of shared artifacts
* Reuse the same JAR or WSDL/XSD across multiple Microflows or Processes
* Update artifacts without reconfiguring individual nodes
* Reduce duplication and configuration errors

This is especially important in **enterprise‑scale integrations**, where a single library or service definition may be used by many flows.

***

### Uploading Files at Application Level

External artifacts are uploaded **once per application** and made available to all eligible flows.

At the application level, users can upload:

* Java **JAR files**
* Web Service **WSDL / XSD files**
* Other supported integration artifacts

After upload, files are stored centrally and can be selected from configuration panels in Microflow and Process nodes.

<figure><img src="/files/1BQgMPyCfrp44lqiHmt4" alt=""><figcaption></figcaption></figure>

***

### Referencing Uploaded Files in Nodes

Once artifacts are uploaded, they can be reused directly in node configurations without re‑uploading.

#### Java Task

* Java Tasks reference uploaded **JAR files**
* Users select the required JAR from the list of uploaded artifacts

<figure><img src="/files/J4dRpditls0BUcwCB9WS" alt=""><figcaption></figcaption></figure>

#### Web Service Task

* Web Service Tasks reference uploaded **WSDL / XSD files**
* Service definitions are selected from the centrally managed artifact list

This ensures that all nodes reference a **single, authoritative version** of an artifact.

<figure><img src="/files/mPQ95a3sIUORciwoQYoG" alt=""><figcaption></figcaption></figure>

***

### Benefits of Centralized File Upload

Using the Upload File facility provides several advantages:

* **Ease of maintenance**\
  Updating an artifact automatically affects all nodes that reference it
* **Consistency**\
  Ensures all Microflows and Processes use the same artifact version
* **Reusability**\
  One artifact can be shared across multiple flows and nodes
* **Cleaner configuration**\
  Node configurations focus on logic, not file management

***

### Best Practices

To ensure reliable and maintainable integrations:

* Upload shared JAR and WSDL files at the **application level**
* Use meaningful file names and maintain versioning discipline
* Avoid embedding JAR files directly inside multiple Java Nodes
* Update shared artifacts carefully to prevent unintended runtime impact
* Validate Microflows and Processes after updating shared files

Following these practices reduces integration risk and improves operational stability.

***

### Summary

The **Upload File** feature in ONEWEB enables centralized management of external integration artifacts used across **Microflow Designer** and **Process Designer**.

With this capability, users can:

* Upload JAR and WSDL/XSD files once per application
* Reuse artifacts across multiple Microflows and Processes
* Simplify maintenance and version updates
* Maintain clean and consistent node configurations

Centralized artifact management is a key enabler for **scalable, maintainable, and enterprise‑grade integrations** in ONEWEB.


---

# 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/oneweb-platform-th/designer-reference/microflow-designer/upload-file.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.