ANALYSIS_PATH: jalur tempat Anda menyimpan output
analisis
OUTPUT_ARTIFACTS_PATH: jalur tempat Anda ingin
menyimpan artefak yang dihasilkan
Membuat artefak migrasi untuk workload WebSphere
Untuk membuat artefak migrasi untuk workload WebSphere, selain
jalur output analisis dan jalur tempat Anda ingin menyimpan artefak
yang dihasilkan, Anda juga perlu menentukan jalur ke file binaryAppScanner.jar
yang telah Anda siapkan saat membuat rencana migrasi.
Untuk membuat artefak migrasi, jalankan perintah berikut:
Ganti PATH_TO_BINARYAPPSCANNER dengan
jalur ke file binaryAppScanner.jar. Misalnya, jika Anda menentukan /tmp
sebagai direktori target saat menyiapkan binaryAppScanner.jar, direktori tersebut akan tersedia
di /tmp/wamt/binaryAppScanner.jar.
Meninjau artefak yang dihasilkan
Artefak migrasi yang dihasilkan tersedia di
jalur output yang ditentukan. Bergantung pada plugin dan rencana migrasi Anda, artefak yang dihasilkan berisi satu atau beberapa Dockerfile yang digunakan untuk mem-build image container, dan satu atau beberapa spesifikasi deployment Kubernetes.
Selain itu, CLI Migrate to Containers menghasilkan konfigurasi Skaffold yang dapat Anda
gunakan untuk mem-build dan men-deploy semua image yang dihasilkan dalam satu langkah.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 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)."]]
