GridGain Developers Hub

Migration

Overview

Previous versions of Web Console relied on an external MongoDB database to store configuration information. Starting in Web Console 2019.10, MongoDB is no longer a required dependency and migration scripts are included with the product.

Migrating from a Previous Version of Web Console (8.x) to Web Console 2019.x and higher

If you are migrating from a previous version of Web Console 8.x based on MongoDB:

  1. Configure the MongoDB database name for migration by creating an environment variable MIGRATION_MONGO_DB_URL=mongodb://localhost:27017/console Alternatively, if you use configuration files, add migration.mongo.db.url: mongodb://localhost:27017/console to your application.properties or application.yml

  2. Start Mongo DB on the same host as the Web Console application.

  3. Start the Web Console by launching web-console.{sh|bat}. Data will be migrated during startup.

  4. Remove "migration.mongo.db.url" from the settings after the migration.

Migration from a Previous Version of Web Console (2019.x and higher) Zip Installation

Configuration settings for Web Console are saved in the work directory. When upgrading to a new Web Console version, simply copy or move the old work directory into the new Web Console installation location.

  1. If Web Console is currently running, stop the application and navigate to the Web Console installation directory

  2. Download and unpack the new version of Web Console to a new folder.

  3. Copy or Move the work directory from the original Web Console installation to the new directory.

  4. Start the new Web Console.

  5. Archive the original Web Console installation folder in case a rollback is required.

Migration from a Previous Version of Web Console (2019.x and higher) Docker with Internal Persistence

If you are migrating to a newer Docker image of Web Console 2019 and you used persistence within the container, follow these steps to preserve the Web Console configuration information.

  1. Get the Container IDs of the running Web Console Backend and Frontend containers

    docker ps

  2. Stop the current Web Console Docker container

    docker stop $frontend_container_id
docker stop $backend_container_id

  3. Copy the work directory from Backend Docker container to a temporary location

    docker cp $backend_container_id:/opt/gridgain-web-console-server/work

  4. Pull the new Docker images from DockerHub

    docker pull gridgain/gridgain-web-console-backend:latest
docker pull gridgain/gridgain-web-console-frontend:latest

  5. Start the new Web Console using the Docker Deployment instructions with External Volumes (RECOMMENDED).

  6. Remove the old Web Console Docker containers

    docker rm $frontend_container_id
docker rm $backend_container_id

Migration from a Previous Version of Web Console (2019.x and higher) Docker with External Storage

If you are migrating to a newer Docker image of Web Console 2019 and you used storage outside of the Docker container, follow these steps to preserve the Web Console configuration information.

  1. Get the Container IDs of the running Web Console Backend and Frontend containers

    docker ps

  2. Stop the Web Console docker containers

    docker stop $frontend_container_id
docker stop $backend_container_id

  3. Pull the new Docker images from DockerHub

    docker pull gridgain/gridgain-web-console-backend:latest
docker pull gridgain/gridgain-web-console-frontend:latest

  4. Start the new Web Console using the Docker Deployment instructions with External Volumes.

© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.

Last updated on Jan 26, 2024