> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/workflows/as2/setting-up-an-as2-server.md).
# Setting up an AS2 Server
An AS2 protocol is a file transfer protocol commonly used to securely transfer EDI files from one partner to another.
In this document, we will learn how to setup an AS2 Server in Astera.
### Configuring the AS2 Setup
1. To setup an AS2 Server go to the *Server Explorer*, right-click on *DEFAULT* and select the *AS2 Setup* option.
2. The *AS2 setup* configuration page will open, as shown below.
Let’s look at the different configuration options provided here.
* *Server URL* – This is the URL of your server where the AS2 service is active, listening for calls from your partner to transmit an EDI file.
* *AS2 ID* – A unique identifier which would allow our partner to identify our request to send a file.
* *Server Upload Directory* – Directory where we want to store all files sent through the AS2 request.
* *Public Certificate Path* – File path where our public certificate is stored.
* *Private Certificate Path and Password* – File path where the private certificate is stored along with its password.
{% hint style="info" %}
**Note:** We can manage our certificates on the[ *Certificate Store*](/api-flow/api-publishing/develop/certificate-store.md)*.*
{% endhint %}
Now, let’s configure our AS2 Server:
3. Our AS2 server setup has now been configured. We can now save it and make use of our AS2 service to send and receive EDI files in Astera.
This is how an AS2 server can be setup to send and receive EDI files in Astera.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.astera.com/workflows/as2/setting-up-an-as2-server.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.