# Server name. Edit this to change the artifacts naming.serverName: jboss-server# JBoss home directory.home: /opt/jboss/wildfly# Parent Wildfly image for the generated container image.fromImage: docker.io/jboss/wildfly:10.1.0.Final# JBoss home directory in the target image.targetImageHome: /opt/wildfly# Configuration file path from source VM.configurationFile: /opt/jboss/wildfly/standalone/configuration/standalone.xml# Ports list to expose on the generated container image.ports:- name: management-http port: 9990- name: management-https port: 9993- name: ajp port: 8009- name: http port: 8080- name: https port: 8433- name: txn-recovery-environment port: 4712- name: txn-status-manager port: 4713# List of deployments files to copy.deployments: directory: /opt/jboss/wildfly/standalone/deployments applications: - test.war# List of modules to copy in rsync filter format.# Note: files under '/system/layers/base/' are JBoss/Wildfly binaries and should be copied only if they have been modified.modules:- '- system/layers/base'# External paths required for running the JBoss server or apps.additionalFiles: []# Sensitive data which is filtered out of the container image.# If includeSensitiveData is set to true the sensitive data is mounted on the container.sensitiveData: includeSensitiveData: false sensitiveDataPaths: - /opt/jboss/wildfly/standalone/configuration/application-roles.properties - /opt/jboss/wildfly/standalone/configuration/application-users.properties - /opt/jboss/wildfly/standalone/configuration/application.keystore - /opt/jboss/wildfly/standalone/configuration/mgmt-groups.properties - /opt/jboss/wildfly/standalone/configuration/mgmt-users.properties
[[["容易理解","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 (世界標準時間)。"],[],[],null,["# Customize migration plan for JBoss servers\n==========================================\n\nYou should review the migration plan file that resulted from creating a migration.\nCustomize the file before executing the migration. The details of your migration\nplan are used to extract the workload container artifacts from the source.\n\nThis section describes the contents of the migration and the kinds of\ncustomizations that you might consider before you execute the migration and generate\ndeployment artifacts.\n\nBefore you begin\n----------------\n\nThis document assumes that you've already [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\nMigration plan structure\n------------------------\n\nThe migration plan for a JBoss workload has the following structure, which\nyou can customize as described in the following sections. \n\n # Server name. Edit this to change the artifacts naming.\n serverName: jboss-server\n # JBoss home directory.\n home: /opt/jboss/wildfly\n # Parent Wildfly image for the generated container image.\n fromImage: docker.io/jboss/wildfly:10.1.0.Final\n # JBoss home directory in the target image.\n targetImageHome: /opt/wildfly\n # Configuration file path from source VM.\n configurationFile: /opt/jboss/wildfly/standalone/configuration/standalone.xml\n # Ports list to expose on the generated container image.\n ports:\n - name: management-http\n port: 9990\n - name: management-https\n port: 9993\n - name: ajp\n port: 8009\n - name: http\n port: 8080\n - name: https\n port: 8433\n - name: txn-recovery-environment\n port: 4712\n - name: txn-status-manager\n port: 4713\n # List of deployments files to copy.\n deployments:\n directory: /opt/jboss/wildfly/standalone/deployments\n applications:\n - test.war\n # List of modules to copy in rsync filter format.\n # Note: files under '/system/layers/base/' are JBoss/Wildfly binaries and should be copied only if they have been modified.\n modules:\n - '- system/layers/base'\n # External paths required for running the JBoss server or apps.\n additionalFiles: []\n # Sensitive data which is filtered out of the container image.\n # If includeSensitiveData is set to true the sensitive data is mounted on the container.\n sensitiveData:\n includeSensitiveData: false\n sensitiveDataPaths:\n - /opt/jboss/wildfly/standalone/configuration/application-roles.properties\n - /opt/jboss/wildfly/standalone/configuration/application-users.properties\n - /opt/jboss/wildfly/standalone/configuration/application.keystore\n - /opt/jboss/wildfly/standalone/configuration/mgmt-groups.properties\n - /opt/jboss/wildfly/standalone/configuration/mgmt-users.properties\n\nTo add information as needed, review your migration plan details and guiding\ncomments.\n\nSpecifically, consider edits around the following sections.\n\n### Specify the Docker image\n\nOn the migration plan, we generate a Docker community image tag based on the\nJBoss version. The JBoss version is detected and converted to a\nmajor version (minor versions are not supported). If we fail to detect a JBoss\nversion, then `fromImage` will contain an empty string.\n\nOn the migration plan, the `fromImage` field represents the Docker Image tag\nused as the base of the container image.\n\nThe original JBoss versions detected on the source VM are contained in\n`discovery-report.yaml` which is generated by the initial discovery.\n\nIf you want to change the Docker community image, or provide your own docker image,\nyou can modify the `fromImage` tag in your migration plan using the following format: \n\n```yaml\n# Parent Wildfly image for the generated container image.\n fromImage: docker.io/jboss/wildfly:10.1.0.Final\n```\n\nThe `targetImageHome` field specifies the path of the JBoss home directory in\nthe target image, and is derived from the `fromImage` field. You don't need to\nchange the value of this field unless you use a JBoss image with a different\nJBoss home value.\n\n### Specify applications\n\nTo exclude applications from the container image, remove them from the application\nlist.\n\n### Specify modules\n\nThe `module` list contains a list of existing JBoss modules marked with either a\nplus or a minus sign. Only modules marked with a plus sign will be added to the\ngenerated container image. The modules that are marked with a minus sign, for\nexamples, `(/system/layers/base)` are already present in the community image,\nand will not be overwritten unless you re-mark them with a plus sign.\n\n### Configure sensitive data migration\n\nIn order to upload sensitive data to the repository, you need to set the\n`includeSensitiveData` field on the migration plan to `true`.\nThe secrets are uploaded in `secrets.yaml`.\n\nThe `sensitiveDataPaths` field specifies the lists of files to filter out from\nthe migration plan. These files may contain sensitive information such as\ncertificates, secret store, users, and passwords used by JBoss. If you remove a\nfile path from the `sensitiveDataPaths` field, the file is uploaded to the\nimage.\n\nWhat's next\n-----------\n\n- Learn how to [execute the migration](../execute-the-migration-plan)."]]
