Update custom extensions in containerized developer toolkit environment

You can update custom extensions in a containerized developer toolkit environment.

1. A copy of the runtime is already extracted as part of your fresh or upgrade mode setup of your developer toolkit. However, if you want to re-extract the runtime from your Docker container to your host machine, run the following command:
   ./om-compose.sh extract-rt
   A copy of the runtime is re-extracted to the devtoolkit_docker directory, which is the default runtime location.
2. Develop your customizations by using the extracted runtime. For more information, see the relevant topics under Developing.
3. Build your customization package.

   After you complete the customizations, build your customization package as an InstallService-able JAR by using the devtoolkit_extensions.xml file.

   From the extracted runtime/bin directory, run the following command after you complete developing your customizations in this runtime directory.
   bash ./sci_ant.sh -f ../devtoolkit/devtoolkit_extensions.xml export

   The customization package is exported as extensions.jar in the parent directory of your runtime directory.
   Review the generated extensions.jar to make sure that it has all the extensions that you have developed.

4. Update your existing developer toolkit environment with the generated extensions.jar by running the following command:
   ./om-compose.sh update-extn <full_path_to_extensions.jar>
   This command applies the customizations to your developer toolkit environment, rebuilds, and redeploys your applications.

   By default, the application removes the Application Server container and creates a new one.

   This command also reintegrates your developer toolkit environment with the Sterling™ Intelligent Promising Inventory Visibility and Sterling Store Engagement cloud tenants.