PATH_TO_BINARYAPPSCANNER를 binaryAppScanner.jar 파일의 경로로 바꿉니다. 예를 들어 binaryAppScanner.jar를 설정하는 동안 /tmp를 대상 디렉터리로 지정한 경우 /tmp/wamt/binaryAppScanner.jar에서 사용할 수 있습니다.
생성된 아티팩트 검토
생성된 마이그레이션 아티팩트는 지정된 출력 경로에서 제공됩니다. 플러그인 및 마이그레이션 계획에 따라 생성된 아티팩트에는 컨테이너 이미지를 빌드하기 위한 하나 이상의 Dockerfile과 하나 이상의 Kubernetes 배포 사양이 포함됩니다.
또한 Migrate to Containers CLI는 생성된 모든 이미지를 단일 단계로 빌드 및 배포하는 데 사용할 수 있는 Skaffold 구성을 생성합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(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)."]]