---
schema_version: "1"
id: aa20b646a1cf44f78e649ef49e475b7f7093ad67f6809d1024959f08063e63a6
title: Using Anypoint Studio to Configure MuleSoft Vectors Connector 1.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mulesoft-vectors-connector/latest/mulesoft-vectors-connector-studio.md
canonical_url: https://docs.mulesoft.com/mulesoft-vectors-connector/latest/mulesoft-vectors-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1699c4a567e7d2cee02ab44878a30f806740aab9d6736091bc3de934b67f09bf
description: MuleSoft Documentation Site
release: "1.1"
latest: true
---
---
product: MuleSoft Vectors Connector
version: 1.1
is-latest-version: true
---

# Using Anypoint Studio to Configure MuleSoft Vectors Connector 1.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure shared libraries](#configure-shared-libraries).

4.  [Configure a source for the connector’s flow](#configure-source).

5.  [Add a connector operation to the flow](#add-connector-operation).

6.  [Configure a global element for the connector](#configure-global-element).

7.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[MuleSoft Vectors Connector Reference](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/mulesoft-vectors-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure Anypoint Connector for MuleSoft
Vectors (MuleSoft Vectors Connector):

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add MuleSoft Vectors Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and add the required dependencies to the project’s
`pom.xml` file:

1.  In **Mule Palette**, click **(X) Search in Exchange**.

2.  In **Add Dependencies to Project**, type `mulesoft vectors` in the search field.

3.  Click **MuleSoft Vectors Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure Shared Libraries

To reduce the overall size of the connector and avoid adding dependencies that are not required, all
the optional libraries are removed from the connector and only the required ones can be added
depending on the specific use case. You can use the Mule Maven plugin to add the required
dependencies to the project’s `pom.xml` file. For more information about how to configure shared
libraries, see
[Configure Shared Libraries](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept#configure-shared-libraries).

### Embedding Models

#### Configuration

```xml
...
<sharedLibraries>
	<sharedLibrary>
		<groupId>dev.langchain4j</groupId>
		<artifactId>langchain4j-core</artifactId>
	</sharedLibrary>
    ...
</sharedLibraries>
...
<dependencies>
	<dependency>
		<groupId>dev.langchain4j</groupId>
		<artifactId>langchain4j-core</artifactId>
		<version>1.0.1</version>
	</dependency>
    ...
</dependencies>
...
```

### Vector Stores

#### Connections

- Azure AI Search

- AlloyDB

- Chroma

- Elasticsearch

- Milvus

- Amazon OpenSearch

- PGVector

- Pinecone

- Qdrant

- Weaviate

- MongoDB Atlas

- Ephemeral File

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-azure-ai-search</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-azure-ai-search</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-community-alloydb-pg</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-community-alloydb-pg</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-chroma</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-chroma</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-elasticsearch</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-elasticsearch</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-milvus</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-milvus</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-opensearch</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-opensearch</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-pgvector</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-pgvector</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

> [!NOTE] You can’t use Pinecone with Milvus or Qdrant.

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-pinecone</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-pinecone</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-qdrant</artifactId>
  </sharedLibrary>
  <sharedLibrary>
      <groupId>io.grpc</groupId>
      <artifactId>grpc-netty-shaded</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-qdrant</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  <dependency>
      <groupId>io.grpc</groupId>
      <artifactId>grpc-netty-shaded</artifactId>
      <version>1.65.1</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-weaviate</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-weaviate</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
  <sharedLibrary>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-mongodb-atlas</artifactId>
  </sharedLibrary>
  ...
</sharedLibraries>
...
<dependencies>
  <dependency>
      <groupId>dev.langchain4j</groupId>
      <artifactId>langchain4j-mongodb-atlas</artifactId>
      <version>1.0.1-beta6</version>
  </dependency>
  ...
</dependencies>
...
```

```xml
...
<sharedLibraries>
		<sharedLibrary>
			<groupId>dev.langchain4j</groupId>
			<artifactId>langchain4j</artifactId>
		</sharedLibrary>
    ...
</sharedLibraries>
...
<dependencies>
		<dependency>
			<groupId>dev.langchain4j</groupId>
			<artifactId>langchain4j</artifactId>
			<version>1.0.1</version>
		</dependency>
    ...
</dependencies>
...
```

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with MuleSoft Vectors Connector:

- **HTTP > Listener**

  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**

  Initiates a flow when a time-based condition is met

For example, to configure an **HTTP > Listener** source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of the **HTTP > Listener** source in the app.

6.  On the **General** tab, specify the connection information for the connector.

7.  On the **TLS** tab, optionally specify the TLS information for the connector.

8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for MuleSoft Vectors Connector, follow these steps:

1.  In **Mule Palette**, select **MuleSoft Vectors Connector** and then select the operation to add.

2.  Drag the operation onto the Studio canvas, next to the source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target vector stores and embedding providers.

You can reference a configuration file that contains ANT-style property placeholders (recommended),
or you can enter your authorization credentials in the global configuration properties. For
information about the benefits of using property placeholders and how to configure them, see
[Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

To configure the global element for MuleSoft Vectors Connector, follow these steps.

1.  Select the operation in the Studio canvas.

2.  On the properties screen for the operation, click the Add (**+**) icon to access the global
    element configuration fields.

3.  Choose from these configs.

    - Embedding Config

    - Store Config

    - Transform Config

4.  Fill out the fields depending on the operation type.

5.  Click **OK**.

## Configure Additional Connector Fields

After you configure a global element for the connector, configure the other required fields. The
required fields vary depending on which connector operation you use.

For detailed configuration information for each operation type, see
[MuleSoft Vectors - Additional Configuration Information](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/mulesoft-vectors-additional-config).

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible on the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  operating system console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [MuleSoft Vectors Connector Reference](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/mulesoft-vectors-connector-reference)

- [Salesforce Help](https://help.salesforce.com)