Moving WAS dmgr profile from one server to another

1. Backup your old WAS configurations , profiles and install_directory before any changes

2. Transfer the backup files from old server to new server ,  into the directory /opt/


3. In new server , for profiles , work in  /opt/IBM/WebSphere/AppServer/bin

For Dmgr01 profile ;

Run;

./manageprofiles.sh -restoreProfile -backupFile /opt/2.15Dmgr01profiles.zip


INSTCONFSUCCESS: Success: The profile was successfully restored.

Now the restoration of Dmgr01 profile completed successfully.


4. Don't start the WAS processes, only start the wsadmin with jython scripting

Go to directory /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin in new server and run;

./wsadmin.sh -conntype NONE -lang jython


WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7031I: For help, enter: "print Help.help()"
wsadmin>

Now , wsadmin is started


5. Run the script ; AdminTask.changeHostName ('[-interactive]')

<<<<<<
*Node Name (nodeName): Node Name of the Profile
*Host Name (hostName): New host name
System Name (systemName): (optional)
Regenerate Certificates (regenDefaultCert):(optional)
>>>>>


wsadmin>AdminTask.changeHostName ('[-interactive]')
Change Host Name

Change the host name of a node

*Node Name (nodeName): CellManager01                              
*Host Name (hostName): was2
System Name (systemName): was1
Regenerate Certificates (regenDefaultCert):

Change Host Name

F (Finish)
C (Cancel)

Select [F, C]: [F] F
WASX7278I: Generated command line: AdminTask.changeHostName('[-nodeName CellManager01 -hostName was2 -systemName was1 ]')
''
wsadmin>


6. Save the changes with AdminConfig.save()


wsadmin>AdminConfig.save()                              
''
wsadmin>

7. Start the Deployment manager and then open the admin console to see the changes you made.