Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menyesuaikan rencana migrasi untuk workload tradisional WebSphere
Sebelum memulai
Topik ini mengasumsikan bahwa Anda telah
membuat migrasi
dan memiliki file rencana migrasi.
Mengedit rencana migrasi
Setelah menyalin sistem file dan menganalisisnya, Anda dapat menemukan
rencana migrasi di direktori baru yang dibuat di jalur output
yang ditentukan: ANALYSIS_OUTPUT_PATH/config.yaml.
Edit rencana migrasi sesuai kebutuhan dan simpan perubahan.
Tinjau detail rencana migrasi dan komentar panduan untuk menambahkan informasi sesuai
kebutuhan.
Secara khusus, pertimbangkan pengeditan di sekitar bagian berikut.
Pilih aplikasi
Pada rencana migrasi, kolom aplikasi mewakili aplikasi yang akan dimigrasikan.
Jika tidak ingin memigrasikan semua aplikasi, Anda dapat menghapusnya.
scannerOptions:# Setting 'includeSensitiveData: true' will upload sensitive data, if exists, such as private keys, to the artifacts repositoryincludeSensitiveData:falsesourceAppServer:was90
[[["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,["# Customize migration plan for WebSphere traditional workloads\n============================================================\n\n| **Important:** The `websphere-traditional` plugin is now deprecated. For existing customers, this plugin is still supported till December 2023, after which it will no longer be available. If you're new to WebSphere workload modernization, then use the `websphere-container` plugin with the Migrate to Containers CLI instead.\n\nBefore you begin\n----------------\n\nThis topic assumes that you've already\n[created a migration](/migrate/containers/docs/m2c-cli/create-a-migration-plan)\nand have the migration plan file.\n\nEdit the migration plan\n-----------------------\n\nAfter you have copied the file system and analyzed it, you can find the\nmigration plan in the new directory that is created in the specified output\npath: \u003cvar translate=\"no\"\u003eANALYSIS_OUTPUT_PATH\u003c/var\u003e/`config.yaml`.\n\nEdit the migration plan as necessary and save the changes.\n\nReview your migration plan's details and guiding comments to add information as\nneeded.\n\nSpecifically, consider edits around the following sections.\n\nSelect applications\n-------------------\n\nOn the migration plan, the application field represents the applications to migrate.\nIf you do not want to migrate all applications, you can remove them. \n\n applications:\n - appName: hello-world-servlet-ear\n httpEndpoints:\n - httpPort: 9080\n httpsPort: 9443\n id: defaulthttpendpoint\n image:\n name: hello-world-servlet-ear\n path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/m4a-twas-ndNode01Cell/applications/Hello-World-Servlet.ear\n ...\n - appName: commons-ejb-ear-provided-ear\n httpEndpoints:\n - httpPort: 9080\n httpsPort: 9443\n id: defaulthttpendpoint\n image:\n name: commons-ejb-ear-provided-ear\n path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/m4a-twas-ndNode01Cell/applications/commons-ejb-ear-provided.ear\n sharedLibraries:\n - /opt/IBM/WebSphere/AppServer/sharedJars/commons-io-2.8.0.jar\n\nSet the scanner options\n-----------------------\n\nIn the migration plan, the `scannerOptions` field represents the argument to pass\nto the [IBM WebSphere Application Server Migration Toolkit for Application Binaries](https://www.ibm.com/support/pages/migration-toolkit-application-binaries).\nYou can edit the arguments. \n\n scannerOptions:\n # Setting 'includeSensitiveData: true' will upload sensitive data, if exists, such as private keys, to the artifacts repository\n includeSensitiveData: false\n sourceAppServer: was90\n\n| **Note:** In order to collect sensitive data, in the migration plan, under `scannerOptions`, modify the value of `includeSensitiveData:` to be `true`. Notice that `set includeSensitiveData: true` will cause uploading sensitive artifacts into the user repository. On `liberty` and `openliberty`, the sensitive data will be stored in a secret file artifact that is used when building app container.\n\nWhat's next\n-----------\n\n- Learn how to [execute the migration](../execute-the-migration-plan)."]]
