Running integrations locally in a Docker container

You can run basic integrations and extended integrations locally in a Docker container. 

To run basic integrations, you must install and configure the local connector.

You can run extended integrations in Oomnitza Cloud, or you can use the local connector to run extended integrations locally. 

For extended integrations, you can use the local connector to achieve the following objectives:

• To access systems that cannot be accessed from the Oomnitza Cloud
• To store credentials locally. That is, you don’t want to store connection credentials in the Oomnitza Cloud.
• To connect to systems such as Microsoft Endpoint Configuration Manager (MECM), Lightweight Directory Access Protocol (LDAP), and VMWare VCenter

Configuring the local connector to run in managed mode

You configure the local connector to run in managed mode when you want the local connector to deliver the asset and the user data for extended integrations. That is, you don’t want to use the cloud connector to manage the delivery of data.

In managed mode, the scheduling, mapping, and other parameters are configured in the Oomnitza cloud and the local connector points to them and maintains the credentials. The reasons for running the local connector in managed mode are as follows:

• You want to store credentials locally rather than storing the credentials in the Oomnitza Cloud.
• You want to access systems behind firewalls or in local data centers that are not accessible from the Oomnitza Cloud.

Useful links

Running integrations locally in a Docker container

Configuring the local connector to run in managed mode