Recovering or resetting parts of the developer toolkit

Procedure to recover or reset parts of your developer toolkit environment.

It is possible that, as part of using your developer toolkit environment, which consists of 4 containers, one or more of these containers or related data could be corrupted because of incorrect usage. One way to recover from this is to do fresh setup after running the wipe-clean command, as documented in Setting up the containerized developer toolkit environment. However, this removes your complete setup. Therefore, to only resurrect the containers that are corrupted or to set up only the affected part, refer the instructions in this topic.

If your MQ Server container or setup is corrupted or you want to set up MQ again, perform the following steps:

  1. Remove your MQ server container by running the following command:
    docker rm -f om-mqserver
  2. If MQ data is corrupted, remove the MQ data using the following command:
    docker volume rm docker_var_mqm
  3. From the compose directory, run the following command:
    ./om-compose.sh update-extn "" --skip-initrt

    Your DB data, application server, and runtime files remain intact. If your MQ data is not retained, you must add your custom queues again.

If your Liberty application server container is corrupted or you want to set up Liberty again, perform the following steps:
  1. Remove your corrupted Liberty application server container by running the following command:
    docker rm -f om-appserver
  2. From the compose directory, run the following command:
    ./om-compose.sh update-extn "" --skip-initrt

    Your application server container is recreated. Your DB and MQ data as well as runtime files remain intact.

If your OM runtime container is corrupted and you want to retain your DB or MQ data, perform the following steps:

  1. Remove the corrupted runtime container by running the following command:
    docker rm -f om-runtime
  2. Optionally, remove your extracted runtime directory as a new runtime directory will get extracted in the next step.
  3. From the compose directory, run the following command:
    ./om-compose.sh setup-upg

    Your environment is set up again in upgrade mode recreating you runtime and application server containers. Your DB and MQ data remain intact.

However, if your OM database server is corrupted, as of now, there is no straight-forward way to recover your data. You must perform wipe-clean and run a fresh setup.