---
schema_version: "1"
id: 10000bbaadd1ed3df6dd42566c59af162ba8ed5582060482301c7c3a9853072d
title: Upgrading and Migrating A2A Connector to Version 1.x
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/a2a-connector/1.0/a2a-connector-upgrade-migrate.md
canonical_url: https://docs.mulesoft.com/a2a-connector/1.0/a2a-connector-upgrade-migrate
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a6e915b39255e7251e54bc1cd08cf4a6462130d25065c7ede9115ed70b2e5dec
description: MuleSoft Documentation Site
release: "1.0"
latest: false
---
---
product: A2A Connector
version: 1.0
---

# Upgrading and Migrating A2A Connector to Version 1.x

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

Upgrade Anypoint Connector for Agent2Agent (A2A) (A2A Connector) to version 1.x.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><p>0.x</p></td><td><p>1.x</p></td></tr></tbody></table>

## Changes in This Release

- There is now a clear distinction in the naming between client and server operations/sources.

- A2A Connector now supports the new **A2A Client - Send Stream Message**, **A2A Client - Task
  Resubscribe**, **A2A Server - Send Push Notification**, **A2A Server - Update Task Artifact**, and
  **A2A Server - Update Task Status** operations.

- A2A Connector now supports the new **A2A Server - On Task Stream Listener** source.

- In the **A2A Server - On Push Notification Set Listener** source, **Response Timeout** is now
  **Push notification request timeout**, and **Response Timeout Unit** is now **Request Timeout
  Unit**.

- Push notifications on the A2A server side are no longer supported unless the **A2A Server - On
  Push Notification Set Listener** source is defined.

- The server now performs out-of-the-box context ID and task ID validations for tasks associated
  with the application.

- The server now supports task cancellation via the `tasks/cancel` method.

- A2A Connector now includes the `A2A:TASK_NOT_CANCELABLE` and `A2A:UNSUPPORTED_OPERATION` errors
  for all operations.

- A2A Connector no longer includes the `A2A:TASK_ALREADY_COMPLETED` error for all operations.

- A2A Connector now uses the A2A Java SDK for request and response validations, which enhances
  reliability.

- In the Server connection type, **Card** is replaced with either **Card Json** or **Card Path** to
  define the agent card.

- The **Agent Card**, **Agent Skill**, **Agent Capabilities**, **Agent Extension**, **Agent
  Provider**, **Security Requirement**, **Http Security Scheme**, **Api Key Security Scheme**,
  **Oauth2 Security Scheme**, **Oauth2 Flows**, **Implicit Oauth2 Flows**, **Oauth2 Scope**,
  **Password Oauth2 Flows**, **Client Credentials Oauth2 Flows**, **Authorization Code Oauth2
  Flows**, and **Open Id Connect Security Scheme** types are no longer supported.

## Requirements

Ensure your system meets the following compatibility requirements before you perform the upgrade:

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.9.8 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr><tr><td><p>A2A protocol</p></td><td><p>0.3.0</p></td></tr></tbody></table>

## Upgrade Prerequisites

Before you perform the upgrade, create a backup of your files, data, and configuration in case you
need to restore to the previous version.

## Upgrade Steps

Follow these steps to perform the upgrade to version 1.x:

1.  In Anypoint Studio, create a Mule project.

2.  In the **Mule Palette** view, click **Search in Exchange**.

3.  In **Add Dependencies to Project**, enter `a2a` in the search field.

4.  In **Available modules**, select **A2A Connector** and click **Add**.

5.  Click **Finish**.

6.  Verify that the A2A Connector dependency version is 1.x in the `pom.xml` file in the Mule
    project.

Studio upgrades the connector automatically.

## Post-Upgrade Steps

After you install the latest version of the connector, verify that your error handling is updated to
work with the minor changes in error codes in this version of the connector.

## Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.

2.  Verify that there are no problems in the project `pom.xml` file.

3.  Test the connection to verify that the operations work.

## Revert the Upgrade

If it is necessary to revert to the previous version of A2A Connector, change the A2A Connector
dependency version in the project’s `pom.xml` file to the previous version.

You must update the project’s `pom.xml` file in Anypoint Studio.

## See Also

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

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