Upgrading from version 6.6 to version 6.7
Consider the following information when upgrading from Diffusion™ version 6.6 to version 6.7.
Upgrading your applications
- Server-side components
-
Recompile all Java™ application components that are deployed to the Diffusion server, such as authorization handlers, against the new version diffusion.jar file. This file is located in the lib directory of your new Diffusion server installation.
Some features that your Java application components might use have been removed or deprecated. Pay attention to new deprecation warnings and compilation failures that occur during recompilation and review the API changes information in the following section to see if these changes affect your applications.
- Clients
-
You can choose not to recompile your client applications and continue to use client libraries from a previous release. If you choose to use client libraries from a previous release, ensure that the libraries are compatible with the new server. For more information, see Interoperability.
You can choose to upgrade your client applications to use the new client libraries. To do this, recompile the client applications against the client libraries located in the clients directory of your new Diffusion server installation and repackage your client application with the new library.
Your client applications may use features that have been removed or deprecated. Review the API changes information in the following section to see if these changes affect your applications.
Note that the local install method for the Python client has changed. See the Client basics page for Python for details.
API changes
Further information about removed or deprecated features is available in the release notes provided online at http://docs.diffusiondata.com/docs/6.11.2/ReleaseNotice.html
| API affected | Deprecated feature | Suggested alternative |
|---|---|---|
| All SDKs | Routing topics | Use session trees. |
| All SDKs | Fan-out | Use remote topic views. |
| Java & NET clients | All methods that use callbacks | Use CompletableFutures (for Java) or task based variants (for .NET). |
| Java client | ClientControl.sessionIdFromString | Diffusion.sessionIdFromString |
| Java client | ClientControl.setQueueEventHandler(QueueEventHandler) | setQueueEventHandler(QueueEventStream) |
| Java client | ClientControl.setSessionPropertiesListener(SessionPropertiesListener) | setSessionPropertiesListener(SessionPropertiesStream) |
| Java client | TopicControl.addMissingTopicHandler(String, MissingTopicHandler) | addMissingTopicHandler(String, MissingTopicNitificationStream) |
| Java client | TopicControl.newSpecification | Diffusion.newTopicSpecification |
| API affected | Removed feature | Suggested alternative |
|---|---|---|
| All SDKs | MessagingControl feature interface | All functionality is available through the Messaging feature. |
| Java, Android, C, JavaScript clients | Unused TopicAddFailReason values: INITIALISE_ERROR, TOPIC_NOT_FOUND, USER_CODE_ERROR | none |
Upgrading your server installation
- Use the graphical or headless installer to install the new version of
Diffusion
.
For more information, see Installing the Diffusion server.
- Contact DiffusionData for an updated license file.
- You can copy most of your existing configuration files from the etc directory of your previous installation to the etc directory of your new installation.