Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Migration assistance

There is currently no automated migration tool, primarily due to differences in the data structure used for storing configuration.

For now, migration of configuration needs to be done by manually adding configuration in JEMH Cloud.

You will need to do ground up configuration of JEMHC.

In progress

We have been adding some config section-exports in JEMH, (e.g. image blacklisting) but as yet have not added the import aspect to JEMHC.

...

In JEMH Server/DC its possible to use regular expressions to match Project keys that should be handled through this particular Notification Mapping. In JEMHC, we avoid regular expressions and simplify things, enabling users to ‘pick’ all or nominated projects.

...

TemplateSets

JEMH Server/DC templates are not compatible with JEMHC.

...

  • JEMH-7550 / JEMHC-2385 : Test Case Export All / Import ZIP

Auditing

No historic audit history will be retained during transition to cloud.

We don’t support migrating audit history from JEMH Server/DC to JEMHC, in Server/DC customer is able to retain unlimited volumes of data. In JEMHC (with customer opt-out) we can store the most recent 100 inbound and outbound messages for your diagnostic purposes.

...