Skip to Content

Ollama connection in Jitterbit Studio

Introduction

An Ollama connection, created using the Ollama connector, establishes access to Ollama, either through Ollama Cloud or through a self-hosted Ollama server. Once a connection is configured, you can create instances of Ollama activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Create or edit an Ollama connection

A new Ollama connection is created using the Ollama connector from one of these locations:

An existing Ollama connection can be edited from these locations:

Configure an Ollama connection

Each user interface element of the Ollama connection configuration screen is described below.

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

  • Connection name: Enter a name to use to identify the connection. The name must be unique for each Ollama connection and must not contain forward slashes / or colons :. This name is also used to identify the Ollama endpoint, which refers to both a specific connection and its activities.

  • Connection type: Select the type of Ollama deployment to connect to, either Ollama Cloud or Self-Hosted:

    • Ollama Cloud: (Default.) Select this option to connect to models hosted by Ollama at https://ollama.com. When this option is selected, this field is visible:

    • Self-Hosted: Select this option to connect to an Ollama server that you install and run. When this option is selected, this field is visible:

      • Base URL: Enter the base URL of the Ollama server, including the protocol and port. The default is http://localhost:11434, which works only when the private agent runs on the same host as the Ollama server. Do not include an API path such as /api in the URL.

  • Optional settings: Click to expand additional optional settings:

    • API key: Enter a bearer token to send with each request. This field is visible only when Self-Hosted is selected. The local Ollama API does not require authentication, so this field is needed only when the Ollama server is behind a reverse proxy that requires a bearer token.

    • Timeout: Enter the maximum time in milliseconds to wait for a connection to be established and for a response to be received. The default is 60000 (60 seconds), and the minimum is 120. Increase this value for large models or long responses, particularly on self-hosted servers where a model may need to load into memory before responding.

    • Use Proxy Settings (Private Agent Only): When using a private agent, this setting can be selected to use private agent proxy settings.

  • Test: Click to verify the connection using the specified configuration. The test confirms that the URL points to an Ollama server and that any API key provided is accepted. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

  • Save: Click to save and close the connection configuration.

  • Discard changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

  • Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After an Ollama connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector Basics.

These activity types are available:

  • Register Tools: Registers tools with the specified Ollama model and is intended to be used as a source in an operation.

  • Prompt: Sends a prompt to the specified Ollama model and is intended to be used as a target in an operation.