> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/engines.md).

# Engines

At the initial data sync, although your engine data has been migrated, engines are not connected to the Cortex XSOAR 8 tenant.

To connect the engines to both Cortex XSOAR 6 and 8, you need to update the Cortex XSOAR 6 `d1.conf` file on each machine where an engine is installed with the new Cortex XSOAR 8 engine configuration and IP address.

{% hint style="info" %}

### Note

* Before updating the file, we recommend copying your existing settings in case you need to revert.
* Any engine that you have connected during the UAT phase remains connected after the switchover date. There is no need to change the configuration again.
* The Cortex XSOAR 6 engine is supported up to 30 days after the switchover date to resolve any potential engine migration issues. To have a definitive engine in the XSOAR 8 environment, you need to deploy XSOAR 8 Engines. For more information, see [Install an engine](/cortex-xsoar-8-saas/onboard-cortex-xsoar/deployment-steps/step-2.-set-up-an-engine.md).
  {% endhint %}

1. Update your Cortex XSOAR 6 instance.
   1. Go to Settings → **ABOUT** → **Troubleshooting**.
   2. In the **Server Configuration** section, click **Add Server Configuration**.
   3. Add the following key and value:

      | Key                            | Value  |
      | ------------------------------ | ------ |
      | `migration.op.engines.enabled` | `true` |
   4. Save the server configuration.
2. In Cortex XSOAR 8, download the engine configuration file to get the new engine attribute values.
   1. Go to the **Engines** page.
   2. For each engine, select **Download Configuration**.
   3. Copy the values for the following attributes:
      * `http.authentication.header`
      * `ServerPublic`
      * `EngineURLs`
3. On the engine machine, edit the Cortex XSOAR 6 `d1.conf` file by adding the attribute values you copied in step 2.
   1. On the machine on which you installed the engine, navigate to the `d1.conf` file:

      | Installation Type | Location                                                                                                                                                                                                                                                                                   |
      | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
      | RPM, DEB, Shell   | <p><strong><code>/usr/local/demisto</code></strong></p><p>If using multiple engines, the location is <strong><code>/usr/local/demisto/</code></strong><em><strong><code>name of the engine></code></strong></em>. For example, <strong><code>/usr/local/demisto/d1\_e1</code></strong></p> |
      | ZIP               | Same folder as the binary.                                                                                                                                                                                                                                                                 |

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you have a Shell installation, you can update the <code>d1.conf</code> file directly from the <strong>Engines</strong> page. For more information, see <a href="/spaces/gHZkkpS9tCAU2tRJlYSx/pages/Rc4FXWwfAnCoNDKZbL6L">Configure engines</a>.</p></div>
   2. Add the following attributes (the values are taken from step 2).

      ```programlisting
      {
        "additionalurls": {
          "migration": {
            "engineHeaderKey": "<The value of the Cortex XSOAR 8 http.authentication.header attribute>",
            "serverPublicKey": "<The value of the Cortex XSOAR 8 ServerPublic attribute>",
            "urls": [
              "<The value of the Cortex XSOAR 8 EngineURLs attribute>"
            ]
          }
        }
      }
      ```
   3. Save the file.
   4. Run the following commands:

      `sudo systemctl stop demisto`

      `sudo systemctl start demisto`

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>We recommend waiting at least 5 seconds between stopping and starting the engine.</p></div>
4. Verify that the engines are connected and working.

   In your firewall configuration, ensure that you have enabled access to `EngineURLs` in the following format:

   `api-<xsoar-tenant>.crtx.<region>.paloaltonetworks.com`

   For more information, see [Enable access to Palo Alto Network resources](/cortex-xsoar-8-saas/onboard-cortex-xsoar/deployment-steps/step-1-activate-cortex-xsoar/enable-access-to-palo-alto-networks-resources.md).


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/engines.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.