Skip to main content

2024.2 to 2025.0

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

This chapter describes all required and optional changes for migrating the Solr search infrastructure as part of the upgrade to ADITO 2025.0.0.
It applies to both managed and unmanaged environments and covers all breaking changes introduced with Solr 9.7.

Follow the structured migration steps in Section 1.6 after reviewing all technical changes.

1.1. Solr: Introduction of ConfigSet adito_config_v9 and Automatic Upload​

What changed​

A new Solr ConfigSet named adito_config_v9 (version 9.0.0) has been introduced for Solr 9.7, based on Lucene 9.11. The ConfigSet is no longer bundled in the Docker image but is uploaded automatically by the ADITO server during collection creation or update.

Why it matters​

This decouples the index configuration from the image and ensures alignment with Solr 9.7. However, it requires a full index rebuild after ConfigSet updates.

  • Rebuild the Solr index once after each ADITO upgrade that modifies the ConfigSet.
  • Do not apply manual ConfigSet patches. The ADITO server manages updates automatically.

1.2. Solr: Enforcement of Basic Authentication​

What changed​

As of ADITO 2025.0.0, Solr access requires Basic Authentication. This applies to all interactions, including ConfigSet uploads and query operations.

Why it matters​

Without Basic Auth, the ADITO server will fail to connect to Solr, resulting in broken indexing and search functionality.

  • Define Basic Auth credentials in Solr and in the AliasConfiguration of ADITO.
  • For unmanaged systems, use the new image adito/solr:v9.7.3, which auto-configures Basic Auth (admin / adito).
  • Change the default password via the Solr Admin UI if needed.

1.3. Solr: Removal of Patch-Based Index Configuration​

What changed​

Index schema or configuration patches are no longer applied. Changes are managed via complete ConfigSet uploads initiated by the ADITO server.

Why it matters​

This reduces complexity and risk by centralizing schema and config updates in version-controlled ConfigSets.

  • Stop using patch-based updates.
  • Rely on the automatic ConfigSet deployment mechanism included in the ADITO server.

1.4. Solr: Standardized Use of Solr 9.7 Images​

What changed​

ADITO-managed environments now use the official solr:9.7.0 image, requiring an external ZooKeeper. Unmanaged systems use adito/solr:v9.7.3, which is based on solr:9.7.0, embeds ZooKeeper and auto-configures Basic Auth.

Why it matters​

Standardizing on official Solr releases improves maintainability, ensures compatibility with ConfigSet uploads, and enhances security.

  • Managed systems: Use solr:9.7.0 and deploy ZooKeeper separately.
  • Unmanaged systems: Use adito/solr:v9.7.3.
  • Remove obsolete environment variables such as: 
    SOLR_OPTS=-Dsolr.disableConfigSetsCreateAuthChecks=true

1.5. Solr: Parallel Operation for Canary Environments​

What changed​

ADITO 2024 and older versions are incompatible with Solr 9. Therefore, canary systems must run Solr 8 and Solr 9 in parallel.

Why it matters​

Indices and collection formats are not backward-compatible. Shared Solr usage across different ADITO versions is unsupported.

  • Deploy separate Solr 8 and Solr 9 containers with distinct hostnames or ports.
  • Ensure each ADITO version points to the correct Solr instance in its AliasConfiguration.
  • Decommission the Solr 8 instance once all systems are upgraded to ADITO 2025.0.0 or higher.

1.6. Migration Guide: Solr 9.7 and ADITO 2025.0.0​

This section summarizes required migration steps for managed and unmanaged environments upgrading to ADITO 2025.0.0 with Solr 9.7.

Migration Steps for Managed Systems​

  1. Delete existing Solr collections.
  2. Upgrade ADITO to version 2025.0.0.
  3. Rebuild the index using the ADITO UI or CLI after the upgrade.

Migration Steps for Unmanaged Systems​

  1. Delete existing Solr collections.
  2. Import the image adito/solr:v9.7.3.
  3. Remove deprecated config options: 
    SOLR_OPTS=-Dsolr.disableConfigSetsCreateAuthChecks=true
  4. Configure Basic Auth (admin / adito) in AliasConfiguration.
    202500_solr_indexSearch
    Figure: Basic Auth credentials in AliasConfiguration
  5. Upgrade ADITO to 2025.0.0.
  6. Rebuild the index using the ADITO UI or CLI after server startup.

Troubleshooting Startup or Collection Issues​

  • If collection creation or Solr startup fails: 
    sudo rm -rf /var/solr/data
    Then restart Solr and rebuild the index.

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