Skip to main content

2024.2 to 2025.0

1. Solr: Mandatory Upgrade to Solr 9.7 with Breaking Changes​

What changed​

ADITO 2025 upgrades the internal Solr client and Docker images to Solr version 9.7. This introduces incompatibility with previous ADITO versions and Solr servers below 9.7 due to significant changes in collection management and ZooKeeper integration.

Why it matters​

Older ADITO versions (2024.x.x and earlier) cannot operate with Solr 9.7 or higher and require Solr 8. Running multiple ADITO systems with different versions on the same Solr server or sharing indices across versions is no longer supported.

  • Ensure your Solr server is upgraded to version 9.7 or higher when migrating to ADITO 2025.0.0.
  • Do not attempt to share Solr indices between ADITO 2024 and ADITO 2025 systems.
  • Plan separate Solr instances for canary or parallel systems with different ADITO versions.
  • Remove old Solr data volumes if errors occur during startup or collection creation to avoid incompatibility issues.

1.1. Solr: New ConfigSet adito_config_v9 and Automatic Upload​

What changed​

A new ConfigSet adito_config_v9 version 9.0.0 is introduced for Solr 9.7, based on Lucene standard 9.11. ConfigSets are no longer bundled with Docker images. Instead, ADITO server uploads and manages the ConfigSet automatically during collection creation or updates.

Why it matters​

This change simplifies ConfigSet management and ensures consistency with Solr 9.7 requirements. However, it requires rebuilding the index after each ConfigSet update triggered by ADITO version upgrades.

  • Rebuild the Solr index once after each ADITO upgrade that changes the ConfigSet.
  • Remove any manual ConfigSet patching, as it is deprecated and replaced by direct uploads.

1.2. Solr: Mandatory Basic Auth for Solr Access​

What changed​

Starting with ADITO 2025.0.0, Basic Authentication is mandatory for Solr access. The ADITO server uses Basic Auth to upload ConfigSets and communicate with Solr.

Why it matters​

Without Basic Auth, the ADITO server cannot upload or update the ConfigSet, breaking Solr integration. This applies to both managed and unmanaged systems.

  • Configure Basic Auth credentials in Solr and in ADITO’s AliasConfiguration for index search.
  • For unmanaged systems, use the new adito/solr:v9.7.3 image which sets up Basic Auth automatically with default user admin and password adito.
  • Change default credentials via Solr Admin UI as needed.

1.3. Solr: Discontinuation of Patches for Collections​

What changed​

From ADITO 2025.0.0 onwards, patches to index schema or configuration are no longer applied. Instead, changes are handled by uploading the updated ConfigSet directly.

Why it matters​

This change streamlines maintenance and reduces complexity by centralizing configuration updates through ConfigSets.

  • Stop applying manual patches or incremental updates to Solr collections.
  • Use the automatic ConfigSet upload mechanism provided by the ADITO server.

1.4. Solr: Official Solr 9.7 Images and New Unmanaged Image​

What changed​

Managed ADITO systems now use the official Solr image solr:9.7.3 with a separate ZooKeeper. Unmanaged systems use a new image adito/solr:v9.7.3 that includes embedded ZooKeeper and auto-configures Basic Auth.

Why it matters​

This aligns ADITO with official Solr releases and improves security and manageability through Basic Auth and ZooKeeper separation.

  • For managed systems, switch to solr:9.7.3 and deploy a separate ZooKeeper instance.
  • For unmanaged systems, import and use adito/solr:v9.7.3.
  • Remove deprecated environment variables such as SOLR_OPTS=-Dsolr.disableConfigSetsCreateAuthChecks=true as Basic Auth is now mandatory.

1.5. Solr: Step-by-Step Migration to Solr 9.7 and ADITO 2025.0.0​

What changed​

Detailed steps for upgrading both managed and unmanaged systems to ADITO 2025 with Solr 9.7 have been provided.

Why it matters​

Following these steps ensures a smooth migration without data loss or downtime.

Managed Systems:

  1. Delete existing Solr collections.
  2. Upgrade ADITO to version 2025.0.0.
  3. Rebuild the entire index once after upgrade.

Unmanaged Systems:

  1. Delete existing Solr collections.
  2. Import new Solr image adito/solr:v9.7.3.
  3. Remove deprecated environment variables related to ConfigSet auth checks.
  4. Configure Basic Auth in AliasConfiguration with default credentials (admin / adito).
    202500_solr_indexSearch
  5. Upgrade ADITO to 2025.0.0.
  6. Rebuild the index once after system startup.

Troubleshooting:

  • If errors occur during Solr startup or collection creation, delete the /var/solr/data volume to remove incompatible old data.
  • Restart Solr and rebuild the index.

1.6. Solr: Parallel Operation with Different Solr Versions for Canary Systems​

What changed​

Canary systems running ADITO 2024 or older alongside ADITO 2025 require separate Solr 8 and Solr 9 containers due to incompatibility.

Why it matters​

Solr 8 and Solr 9 cannot coexist on the same Solr instance for different ADITO versions, nor can indices be shared.

  • Provision separate Solr 8 and Solr 9 containers with distinct ports or DNS names.
  • Configure AliasConfigurations to point to the appropriate Solr server per ADITO version.
  • Remove the old Solr instance after full migration to ADITO 2025 or higher.

2. Variable Calculation Changes: $sys.selectionGroups and $sys.selectionGroupRows Recalculation​

What changed​

The system variables $sys.selectionGroups and $sys.selectionGroupRows are now recalculated upon selection changes, providing more dynamic behavior.

Why it matters​

This improves responsiveness of state processes that depend on selection group variables but requires awareness of selectionType settings.

  • As this behaviour is overriden by selectionType 'MULTI', use selectionType 'UNBOUND' to enable correct evaluation of StateProcess on selection changes.
  • Ensure StateProcess checks for the existence of these variables as they are not available when opening records in preview mode.
  • Adjust logic to accommodate recalculation behavior.
  • Currently, it only makes sense to use the variables within a $sys.presentationmode equals filter.

3. Removal of Deprecated Functions: question.showDialog() and question.closeDialog()​

What changed​

The deprecated functions question.showDialog() and question.closeDialog() have been removed in ADITO 2025.0.0.

Why it matters​

Removing deprecated APIs cleans up the codebase and prevents usage of obsolete methods.

  • Refactor any code using these functions to use supported alternatives.
  • Verify dialogs function correctly after migration.

4. Web Service Properties Visibility: Filtered Display in Designer​

What changed​

Web service process properties in the Designer are now displayed conditionally based on the property style, showing only meaningful fields.

Why it matters​

This reduces clutter and improves usability by hiding irrelevant properties.

  • Refer to the following visibility rules:

Always visible:

  • publishAsWebservice
  • style

Visible if style != NONE:

  • loginTypeId
  • jditoWebserviceUser
  • restrictedRoles

Visible if style = REST:

  • restAcceptedMimeType
  • restDeliveredMimeType

Visible if style = SOAP_DOCUMENT or SOAP_RPC:

  • wsdl
  • soapOmitEmptyResult
  • soapUseRawXmlResult

5. Removal of Experimental Flag: enableCloudServiceAliasDefinition​

What changed​

The experimental flag enableCloudServiceAliasDefinition has been removed from ADITO Designer options as of version 2025.0.0.

Why it matters​

Cloud Service Alias creation is now fully supported without requiring this flag, simplifying configuration.

  • Create Cloud Service Aliases directly without enabling any experimental options.

image
Figure: Experimental flag removal in ADITO Designer

image
Figure: Creating Cloud Service Aliases without experimental flag