Let's say you have a profile on "server1" and you want to migrate the profile to "server2". On server1, you will want to stop the services associated with the profile. For example, if the profile is a management profile, you will want to stop the deployment manager.

${WAS_INSTALL_ROOT}/profiles/your_dmgr_server/bin/stopManager.sh

If the profile contains one or more application servers, you'll want to stop the node agent and stop the application servers.

${WAS_INSTALL_ROOT}/profiles/profile_name/bin/stopNode.sh
${WAS_INSTALL_ROOT}/profiles/your_profile/bin/stopServer.sh server_name

Create a backup of the profile on server1.

${WAS_INSTALL_ROOT}/bin/manageprofiles.sh -backupProfile -profileName <name of the profile> -backupFile /path/to/backup.xml

On server2, install WebSphere Application Server or WebSphere Network Deployment Server. Then on server2 restore the profile from the backup you created on server1.

${WAS_INSTALL_ROOT}/bin/manageprofiles.sh -restoreProfile -backupFile /path/to/backup.xml

On server2, update the following files, updating HOSTNAME to have server2 instead of server1.

• ${WAS_INSTALL_ROOT}/profiles/your_dmgr_profile/config/cells/your_cell/nodes/your_node/variables.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/installedFilters/wlm/your_server/target.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/installedFilters/wlm/dmgr/target.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/node-metadata.properties

If the profile on server1 had a DNS cname such as server1-dmgr.example.com there are two options here.

1. You can update the DNS cname to point to the hostname / IP address of server1
2. You can create a new DNS cname such as server2-dmgr.example.com that points to the hostname / IP address of server2

If you go with option 2, then you'll need to update the following files on server2, replacing the old cname with the new cname.

• ${WAS_INSTALL_ROOT}/profiles/your_profile/properties/wsadmin.properties
• ${WAS_INSTALL_ROOT}/profiles/your_profile/conf1/nodes/your_node/serverindex.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/serverindex.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/servers/your_server/plugin-cfg.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/overlaynodes.config
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/security.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/installedFilters/wlm/your_server/target.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/installedFilters/wlm/dmgr/target.xml
• ${WAS_INSTALL_ROOT}/profiles/your_profile/logs/AboutThisProfile.txt
• ${WAS_INSTALL_ROOT}/profiles/your_profile/properties/sas.client.props

If the server certificate in each key.p12 file contains Subject Alternative Names (SANs), then you'll want to renew the server certificate, adding server2.example.com to the list of Subject Alternative Names (SANs) and generate a new key.p12 file. How to do this is beyond the scope of this article. Once you have the updated key.p12 file, copy the updated key.p12 file on server2.

• ${WAS_INSTALL_ROOT}/profiles/your_profile/etc/key.12
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/key.12
• ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/key.12

On server2, if the profile is a management profile, you will want to start the deployment manager.

${WAS_INSTALL_ROOT}/profiles/your_dmgr_server/bin/startManager.sh

On server2, if the profile contains one or more application servers, you'll want to start the node agent and start the application servers.

${WAS_INSTALL_ROOT}/profiles/profile_name/bin/startNode.sh
${WAS_INSTALL_ROOT}/profiles/your_profile/bin/startServer.sh server_name

You can now see if you are able to log into the WebSphere admin console on server2. You will either want to clear your web browsers cookies and cache or open an InPrivate tab.