Compatibility

This version is NOT backwards compatible with previous versions of the Netcetera 3DS Server.

Upgrade Notes

• Starting from this release by default transactions are not logged to a DB if it is configured to store 3DS Server configuration. Default behavior is to log them into a file only. With a new property threedss.logging.storage.type set to file,db 3DS Server will continue logging transactions to a file and store them to a table in the DB as it was in previous releases. Find other possible values for this property on Configuration Properties page.
• From this release on a new data model is used to store transaction logs in a DB. The old transaction logs are not automatically migrated to the new data model after the admin app is installed and is started up. It means they are not available in the transaction search results of the admin application. Only new transactions are visible there. To migrate old transactions run Transaction Logs Migration CLI Tool (3dss-cli-log-migration-tool/bin/3dstrxmigration.sh in the delivery package).
• When using custom log4j2 configuration, the logging pattern of Transaction-Message-Appender must be adjusted as it's defined in default log4j2 configuration file.
• In previous releases a fixed list of 3DS Server instances was configured in threedss.instance.endpoints property in the admin configuration properties. With Service Discovery introduced in this release 3DS Server instances register and unregister themselves in the Admin application upon their startup and shutdown respectively. In DB based configuration scenario add next properties to application.properties of 3DS Server to enable service discovery:

  eureka.client.enabled=true
  eureka.client.serviceUrl.defaultZone=http(s)://<admin-app-hostname>:<admin-app-port>/eureka

  Note that in some complex network configurations eureka.instance.homePageUrl property should be configured as well. Find more details about service discovery configuration on Configuration Properties page.

  Additionally add next configuration property to the application.properties of the Admin application to enable service discovery:

  eureka.client.serviceUrl.defaultZone=http(s)://localhost:${server.port}/eureka

  Note that the url is pointing to the same Admin application instance as it's running an embedded Eureka discovery server.

  threedss.instance.endpoints can be removed from the application.properties.

• In Configuration Properties ds-client.cached-instance-expiry.days and mpi.ds-client.cached-instance-expiry-in-days are replaced by ds-client.cached-instance-expiry.seconds and mpi.ds-client.cached-instance-expiry-in-seconds respectively. Update the properties and their values (convert days to seconds) in the application.properties if custom values were previously configured.
• Starting from this release, the 3DS Server is able to store completely overlapped card ranges received from different schemes. For this purpose, the directory server URL was added to the key in addition to start and end range values. In case EhCache is configured to store session and card ranges data the EhCache configuration should be updated with a new search attribute:

  <searchAttribute name="directoryServerUrl" expression="key.getDirectoryServerUrl()"/>

  in the searchable section of pResCardRangeData cache. Find an example of EhCache configuration file on EhCache Configuration page. Note such update should be done after all 3DS Server are down to avoid ehcache replication problems between 3DS Server instances of the new and an old version.

• In case Redis is configured to store session and card ranges data, pres_card_range_data and pres_ds_data indexes should be removed before starting using this release. Note such update should be done after all 3DS Server instances are down to avoid incompatibility problems between 3DS Server instances of the new and an old version. In order to minimize the downtime the upgrade to the 2.3.0.0 version should happen minimum one hour after the last preparation response was received so that the new preparation request (initiated from the 2.3.0.0 instance) is not blocked by the Directory Server. An alternative is to start freshly the 2.3.0.0 instances to a new, empty Redis instance and shut down the old 3DS Server instances and Redis one once the 2.3.0.0 instances are up and running.

Changes