Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Personalizar plano de migração para cargas de trabalho do WebSphere tradicional
Antes de começar
Para seguir este tópico, é necessário criar uma migração e
ter o
arquivo do plano de migração.
Editar o plano de migração
Depois de copiar o sistema de arquivos e analisá-lo, encontre o plano de modernização no novo diretório criado no caminho de saída especificado: ANALYSIS_OUTPUT_PATH/config.yaml.
Edite o plano de migração conforme necessário e salve as alterações.
Revise os detalhes e os comentários de orientação do plano de migração para acrescentar informações conforme necessário.
Mais especificamente, considere editar as seguintes seções:
Selecionar aplicativos
No plano de migração, o campo de aplicativo representa os aplicativos a serem migrados.
Se você não quiser migrar todos os apps, faça a remoção deles.
scannerOptions:# Setting 'includeSensitiveData: true' will upload sensitive data, if exists, such as private keys, to the artifacts repositoryincludeSensitiveData:falsesourceAppServer:was90
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 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)."]]
