> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.206/help-center-index/faqs/installer-faqs/oim-and-system-installed-on-same-machine.md).

# Can the application be installed on the same machine where one of the end system is installed?

### Description

Can <code class="expression">space.vars.SITENAME</code> and an end system that is being used in integration be installed on the same machine? For example: If an integration is created between System A and System B, then A and B are the end systems. If the <code class="expression">space.vars.SITENAME</code> is installed on the same machine where System A or System B is hosted then same machine is being used for end system and application.

### Solution

<code class="expression">space.vars.SITENAME</code> can be installed on the same machine where one of the end system is installed. However, the machine on which <code class="expression">space.vars.SITENAME</code> is being installed must fulfill the [Installation Prerequisites](/v7.206/getting-started/prerequisites.md#installation-prerequisites). It is preferable to have separate VM's for both, as the system may take up more resources if the number of users accessing it increases. In such scenario, it would be necessary to ensure that <code class="expression">space.vars.SITENAME</code> gets its required share of resources or it will affect the performance of <code class="expression">space.vars.SITENAME</code>


---

# 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.opshub.com/v7.206/help-center-index/faqs/installer-faqs/oim-and-system-installed-on-same-machine.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.