Jedox Ideas

Let us know how we can make Jedox even better!

Add a new idea Subscribe
Status Future Consideration
Workspace Jedox Platform
Categories Other
Created by Guest
Created on Jul 2, 2019

RELATED IDEAS

Automate environment migration (Web reports, database, security ...)

Automate by scripts or the web console, imports and exports from one environment to another (Web reports, database, security ...) without performing a restart of Jedox Setup (“Repair”)
  • ADMIN RESPONSE
    Jul 15, 2022

    Hi. This is a good idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog. If you can add further information about the context of this feature, please add it here so we can evaluate it more fully.


    As first step we are working towards a feature that would allow an environment to be synchronised. This would allow, for example, a development environment to be reset based on the current production environment state. We understand the request goes far beyond this and we are still considering a more comprehensive migration strategy.

  • Guest
    Reply
    |     Jul 7, 2022

    Hello, is there any update on this feature?

    With the synchronization on cloud, it should be standard by now, and it is one of the biggest pain points from customers it and dev teams not to be able to track changes and have a supported development flow where users can collaborate in the development in a supportive environment.

    One Customer even ask if we're serious that this is not existing since it's one of the key features to guarantee the push of features to production.

    Also, we as developer would really appreciate an update here to avoid human errors. Also linked to JS-I-737 - GIT for svs and macros.


    thank you!

  • Guest
    Reply
    |     Jun 19, 2020

    This comes quite close to what we would like to see as well.

    It should be possible to link servers with each other to enable the following features:

    • Diff between the servers (difference of rules, templates, integrator jobs) to see directly where and if we have a different status on both servers

    • Sync two servers. Not only relevant for a sequential backup without shutting down the servers but also to use the testenvironment with the latest production data

    • Enable Migration Kits. It should be possible to tag Integrator jobs, templates, databases (cubes dims etc.) to a current developement process. The process should automatically move all linked components to the target server incl. log who when and what was migrated, comment function, unroll functionality etc.

    All this would realy benefit the overall developement process in a radical way. Especially on larger projects with several consultants it would reduce migration issues.

  • Guest
    Reply
    |     Jul 2, 2019
    Would love to have the ability to synchronize environments ... every so often we need to ensure that our QA environment is identical to production and vice versa (if a bunch of changes are being promoted).