Skip to content
Switch branches/tags
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Oracle Coherence to Hazelcast migration tool.

Supported Coherence and Hazelcast versions

  • Oracle Coherence 12.1.3-0-0
  • Hazelcast 3.6

Installation (maven)

mvn package


java -jar cohe2hazel-1.0-SNAPSHOT.jar ${cache}.xml ${operational}.xml


java -jar cohe2hazel-1.0-SNAPSHOT.jar coherence-cache.xml tangosol-coherence.xml

Output: Generated output.xml file is a base for main Hazelcast configuration.


Java 1.7 

Migrating Oracle Coherence configuration to Hazelcast

If your Coherence application is based on XML configuration, the migration can be partially automated using the cohe2hazel project.

The cohe2hazel project tries to transform the Coherence operational and the cache configuration files to the hazelcast.xml (hazelcast-config-3.6) configuration file using XSLT processor. During the transformation the Coherence operational config file is transformed to the Hazelcast network section and the Coherence cache config file to the hazelcast map section. This transformation is especially helpful when your cache configuration contains a lot of cache definitions (also parameterized ones) .


To execute the transformation you need to run cohe2hazel with proper input parameters, which are paths to both configuration files: your Coherence operational xml (for example tangosol-coherence.xml) and cache xml (coherence-cache.xml).

ConfigTransformer main method performs 3 operations:

  • Transforms Coherence operational xml and creates network.xml as an output,
  • Transforms Coherence cache xml and creates cache.xml as an output,
  • Merges previously created xml files into a single output.xml.

Generated output.xml file is a base for main Hazelcast configuration. For more information please refer to Hazelcast documentation - configuration section.

Currently, due to difference in the API of both products it is not possible to automatically migrate the whole configuration so please be aware that the configuration will be migrated only in limited way.

Rules/assumptions for Coherence configurations

As the transformation is based on XSLT, currently it assumes that main XML configuration elements have proper namespaces for the operational file: <coherence ... xmlns="" … > for the cache file: <cache-config … xmlns="" … >

Multifile configuration is not supported, cache / operational configuration must be in a single file within the cache configuration file only a single schema reference is allowed (recursive schemas are not supported).

Operational / Networking settings

Transformation of the Coherence operational file is currently very limited and supports only a basic identity, the unicast and multicast listeners section conversion.

  • Member-identity element is converted into Hazelcast where name value is taken from cluster-name and the password is set to dev-pass as a default.
  • The unicast / multicast sections are converted into the Hazelcast element.
  • For Coherence unicast, the Hazelcast members are extracted using the well-known-addresses section and address / socket-address elements.
  • For Coherence multicast-listener the Hazelcast multicast element is created with the following properties: multicast-group, -port, -time-to-live and timeout-seconds (if present). As a default both Hazelcast tcp-ip / multicast outputs are disabled (enabled="false").

Cache definitions

All Coherence caches are transformed to Hazelcast elements based on the following rules:

  • All Hazelcast maps except replicated map will have in-memory-format set to binary. The replicated map has in-memory-format set to object.
  • Coherence distributed-scheme, optimistic-scheme and transactional-scheme are mapped to Hazelcast map.
  • Invocation-scheme, overflow-scheme, proxy-scheme currently are not transformed.
  • Coherence near-scheme is converted to Hazelcast map with the near-cache section where the main map attributes are obtained from back-scheme and the near-cache from the front-scheme.

Migrating / resolving cache parameters:

  • Backup-count is converted to the same Hazelcast attribute backup-count.
  • High-units are converted to max-size where units number and the max-size policy is based on Coherence unit-calculator.
  • Eviction-percentage is converted to the same Hazelcast attribute. Transformation is executed only for LRU, LFU types.
  • Expiry-delay is converted to time-to-live-seconds, units are calculated to seconds.

Service definitions

Currently there is no way to automatically migrate Coherence services. A Coherence cache timeouts/threads count and other services parameters should be manually merged and moved to Hazelcast client configuration.

Questions or comments? Contact us.

If you are interested in any changes to this tool or our experience in migrating Oracle Coherence projects to Hazelcast you may contact us at


Oracle Coherence to Hazelcast migration tool




No releases published


No packages published