> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/getting-started/setting-up-the-odata-connector/configure-connection-between-flow-server-and-ifs-cloud.md).

# Configure connection between Flow Server and IFS Cloud

All flow servers and IFS Cloud instances that need to be connected are registered, registration of both systems can be done in any order. 

## Register Flow Server

Select ***Add Flow Server*** under ***Flow Server*** page.

<figure><img src="/files/hav9n0lNwZoK0TqFeIZQ" alt=""><figcaption><p>Add new Flow Server</p></figcaption></figure>

1. Give Flow Servers URL, designated flow server user and password.&#x20;
2. Flow user can be machine user or other flow user with ***AdministerBasicData*** Access Level.
3. Select ***Create*** and Flow Server registration is done!

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

## Register IFS Cloud configuration

Select ***Add New*** under ***Configurations*** page.

<figure><img src="/files/KkXd7Za5l4I6rHMCPfIe" alt=""><figcaption><p>Add new IFS Could configuration</p></figcaption></figure>

### General -tab

* Name: name of the configuration
* Service URI: base path to IFS Cloud instance
* IFS Version: IFSCloud
* Break workflow on error is initially set to No. Read more from&#x20;

{% content-ref url="/pages/4cnXC7Qr69g7KQCt3XVh" %}
[Response status handling](/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/response-status-handling.md)
{% endcontent-ref %}

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

### Auth -tab

{% content-ref url="/pages/5kblTXgAtVDZrAh2hSyJ" %}
[Authentication models](/flow-ifs-cloud-development-guidelines/flow-development-with-odata/configuration/authentication-models.md)
{% endcontent-ref %}

### Miscellaneous -tab

WIP: not sure what these do.

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

### Communication Log

Connector service can log all request that you can inspect from **Communication Log** page. Setup can be changed

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

{% hint style="info" %}
In production configurations logging could be disabled to optimize Connector performance.
{% endhint %}

## What happens when you add new IFS Cloud configuration

1. After you save configuration and **Design time** authentication is correct, OData Connector service will automatically start loading all available projections from IFS. It may take few minutes to have the projection list ready. After initial upload all available projections can be browsed in\
   &#x20;

   <figure><img src="/files/GtmjhEYjK4OEEyEdRiGP" alt=""><figcaption></figcaption></figure>
2. After adding new configuration Re-register each Flow Server using new OData Configuration.

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

{% hint style="info" %}
OData Connector service will refresh projection list from IFS on regular basis (every hour?) to find new projections.&#x20;
{% endhint %}

## Deleting and modifying configurations

1. When you remove a configuration, it is not automatically deleted from flow server. You must Unregister one OData Connector from the flow server by executing Unregister. Notice that all OData connectors are removed.<br>

   <figure><img src="/files/sjOQ6FXTNSwbEZ0sYfAA" alt=""><figcaption></figcaption></figure>
2. Re-register the flow server in OData Connector and all connectors are restored to flow server.
3. If you modify configuration name, Re-rgister the Flow server.


---

# 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.novacura.com/flow-ifs-cloud-development-guidelines/getting-started/setting-up-the-odata-connector/configure-connection-between-flow-server-and-ifs-cloud.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.