ANALYSIS_PATH: the path where you saved the analysis
output
OUTPUT_ARTIFACTS_PATH: the path where you want
to save the generated artifacts
Generate migration artifacts for WebSphere workloads
To generate migration artifacts for WebSphere workloads, in addition to the
analysis output path and the path where you want to save the generated
artifacts, you also need to specify the path to the binaryAppScanner.jar file
that you had set up when you created the migration plan.
To generate migration artifacts, run the following command:
Replace PATH_TO_BINARYAPPSCANNER with the
path to the binaryAppScanner.jar file. For example, if you specified /tmp
as your target directory while setting up the binaryAppScanner.jar, then it is available
at /tmp/wamt/binaryAppScanner.jar.
Review the generated artifacts
The generated migration artifacts are available in the
specified output path. Depending on your plugin and migration plan, the
generated artifacts contain one or more Dockerfiles that are used to build
container images, and one or more Kubernetes deployment specs.
Additionally, Migrate to Containers CLI generates a Skaffold configuration that you can
use to build and deploy all of the generated images in a single step.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Execute the migration\n=====================\n\nThis page describes how to generate the migration artifacts which you can use\nto deploy your workloads to the target cluster.\n\nGenerate migration artifacts\n----------------------------\n\nAfter you've customized your migration plan, to generate the artifacts, run the\nfollowing command: \n\n ./m2c generate -i \u003cvar translate=\"no\"\u003eANALYSIS_PATH\u003c/var\u003e -o \u003cvar translate=\"no\"\u003eOUTPUT_ARTIFACTS_PATH\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eANALYSIS_PATH\u003c/var\u003e: the path where you saved the analysis output\n- \u003cvar translate=\"no\"\u003eOUTPUT_ARTIFACTS_PATH\u003c/var\u003e: the path where you want to save the generated artifacts\n\n### Generate migration artifacts for WebSphere workloads\n\nTo generate migration artifacts for WebSphere workloads, in addition to the\nanalysis output path and the path where you want to save the generated\nartifacts, you also need to specify the path to the `binaryAppScanner.jar` file\nthat you had set up when you [created the migration plan](/migrate/containers/docs/m2c-cli/create-a-migration-plan#create_a_migration_plan_for_websphere_workloads).\n\nTo generate migration artifacts, run the following command: \n\n ./m2c generate \\\n -i \u003cvar translate=\"no\"\u003eANALYSIS_PATH\u003c/var\u003e \\\n -o \u003cvar translate=\"no\"\u003eOUTPUT_ARTIFACTS_PATH\u003c/var\u003e \\\n --volume \u003cvar translate=\"no\"\u003ePATH_TO_BINARYAPPSCANNER\u003c/var\u003e:/binaryAppScanner.jar\n\nReplace \u003cvar translate=\"no\"\u003ePATH_TO_BINARYAPPSCANNER\u003c/var\u003e with the\npath to the `binaryAppScanner.jar` file. For example, if you specified `/tmp`\nas your target directory while [setting up the `binaryAppScanner.jar`](/migrate/containers/docs/m2c-cli/create-a-migration-plan#set_up_the_binaryappscannerjar), then it is available\nat `/tmp/wamt/binaryAppScanner.jar`.\n\nReview the generated artifacts\n------------------------------\n\nThe generated migration artifacts are available in the\nspecified output path. Depending on your plugin and migration plan, the\ngenerated artifacts contain one or more Dockerfiles that are used to build\ncontainer images, and one or more Kubernetes deployment specs.\n\nAdditionally, Migrate to Containers CLI generates a Skaffold configuration that you can\nuse to build and deploy all of the generated images in a single step.\n\nWhat's next\n-----------\n\n- Learn more about the [migration artifacts](/migrate/containers/docs/review-deployment-files)."]]