Licensing after product retirement

Tone

Hi,

We have an application built with version 100.14 of the Java Map SDK.

However this product is planned for retirement in november 2028, will we still be able to buy licenses for it after this date ?

RexHansen

Hi Tone,

The short answer to your question is yes - until July 2030. More details...

Legally, the ArcGIS Maps SDK for Java (the last release being 200.6) will be retired November 2028, documented here: https://support.esri.com/en-us/products/arcgis-maps-sdk-for-java/life-cycle

ArcGIS Runtime SDK for Java 100.14 was retired May 1, 2026, documented here: https://support.esri.com/en-us/products/arcgis-runtime-sdks/life-cycle If a product is retired, it's no longer supported by Esri - which means no further technical and product support.

Technically, ArcGIS Runtime SDK for Java 100.x and ArcGIS Maps SDK for Java 200.x can be licensed with ArcGIS named users and license strings (delivered via deployment packs).

Technically, these Java SDKs will continue to be able to be licensed with ArcGIS named users - no plans to change at this time - but also no guarantees that retired products are going to continue to support this approach with updates to ArcGIS Online or Enterprise in the future.

License strings are delivered in deployment packs for all supported versions, currently 100.x, 200.x, and 300.x. If you purchase a Native Maps SDK Standard deployment pack today, you will get Standard license strings for 100.x/200.x (same string) and 300.x. Technically you can buy more deployment packs that unlock 100.x/200.x until 200.8 is retired (July 2030). In general, license strings are perpetual, they don't expire, but that does not mean the products they license are supported perpetually/indefinitely. The primary purpose for the license string approach is to support clients that are offline for long periods of time/indefinitely and/or are accessed by users that do not have an ArcGIS identity/named user.

I'll state for the record, it's best to update your apps to use an SDK that is supported. If you're using an SDK that has been deprecated (eg Java), you may need more time to transition to another SDK/client technology. The product lifecycle for Runtime/Native Maps SDKs is purposefully long and includes an LTS release at the end of a major release cycle to provide a substantial runway for any migrations/transitions.

View solution in original post

RexHansen

Hi Tone,

The short answer to your question is yes - until July 2030. More details...

Legally, the ArcGIS Maps SDK for Java (the last release being 200.6) will be retired November 2028, documented here: https://support.esri.com/en-us/products/arcgis-maps-sdk-for-java/life-cycle

ArcGIS Runtime SDK for Java 100.14 was retired May 1, 2026, documented here: https://support.esri.com/en-us/products/arcgis-runtime-sdks/life-cycle If a product is retired, it's no longer supported by Esri - which means no further technical and product support.

Technically, ArcGIS Runtime SDK for Java 100.x and ArcGIS Maps SDK for Java 200.x can be licensed with ArcGIS named users and license strings (delivered via deployment packs).

Technically, these Java SDKs will continue to be able to be licensed with ArcGIS named users - no plans to change at this time - but also no guarantees that retired products are going to continue to support this approach with updates to ArcGIS Online or Enterprise in the future.

License strings are delivered in deployment packs for all supported versions, currently 100.x, 200.x, and 300.x. If you purchase a Native Maps SDK Standard deployment pack today, you will get Standard license strings for 100.x/200.x (same string) and 300.x. Technically you can buy more deployment packs that unlock 100.x/200.x until 200.8 is retired (July 2030). In general, license strings are perpetual, they don't expire, but that does not mean the products they license are supported perpetually/indefinitely. The primary purpose for the license string approach is to support clients that are offline for long periods of time/indefinitely and/or are accessed by users that do not have an ArcGIS identity/named user.

I'll state for the record, it's best to update your apps to use an SDK that is supported. If you're using an SDK that has been deprecated (eg Java), you may need more time to transition to another SDK/client technology. The product lifecycle for Runtime/Native Maps SDKs is purposefully long and includes an LTS release at the end of a major release cycle to provide a substantial runway for any migrations/transitions.

Tone

Hi RexHansen, thank you for your reply.

Yes we are currently evaluating our options relatively to this application, 2030 would allow us to migrate the app to another SDK.

We are using licence strings.

When is 200.8 scheduled for release, and do you have a link to a page documenting it ?

It is stated here that 200.6 will be the last release of ArcGIS Maps SDK for Java