> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/overview-and-basics/architecture/docbits-infor-on-premise-customer.md).

# DocBits Infor on Premise Customer

To send data to Infor onPremise customer we offer two ways Site2Site with IPsec or [WatchDog](https://docs.docbits.com/administration-and-setup/setup/watchdog)

Sending Data to Infor On-Premise Customer

To send data to an Infor on-premise customer, we offer two ways: Site-to-Site VPN with IPsec.

## IPsec (Internet Protocol Security) Site-to-Site VPN Configuration

### 1. Configuration Informations:

| **IPSEC VPN Setup**            |                              |
| ------------------------------ | ---------------------------- |
|                                | **Endpoint B**               |
| **Customer**                   | ***FELLOWPRO AG***           |
| **Name of Contact**            | ***Daniel Lopez***           |
| **Mail**                       | <daniel.lopez@fellowpro.com> |
| **Endpoint Hardware/Software** | ***StrongWAN***              |
| **Location of Firewall**       | ***Frankfurt***              |
| **Endpoint IP**                | ***46.101.133.158***         |
| **Network/Host 1**             | ***10.135.0.0/16***          |

### 2. For an IPsec site-to-site VPN, you need to configure and open the following ports:

1\. UDP port 500: Used for Internet Key Exchange (IKE) phase 1 and phase 2.

2\. UDP port 4500: Used for NAT traversal (NAT-T), allowing VPN traffic to pass through NAT (Network Address Translation) devices.

## Accessing Infor OS

• Authentication URL: <https://inforos.CustomerXYZad.net/>

• Data URL: <https://inforos.CustomerXYZad.net:7443/>

## Summary:

For setting up an IPsec site-to-site VPN, ensure the above ports and protocols are configured and open.

Use the provided URLs to access Infor OS for authentication and data.


---

# 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://docs.docbits.com/overview-and-basics/architecture/docbits-infor-on-premise-customer.md?ask=<question>&goal=<user_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.